[pkg-fso-maint] fso-abyss, fso-usaged, libfso*?

Luca Capello luca at pca.it
Sun Jul 19 10:45:48 UTC 2009


Hi Heiko!

On Tue, 14 Jul 2009 18:30:13 +0200, Heiko Stuebner wrote:
> Am Dienstag 14 Juli 2009 11:55:02 schrieb Heiko Stübner:
>> But that reminds me, I meant to send my changes for review. Will do this
>> afternoon.
>
> my changes to fso-frameworkd can be found on
> http://git.sntech.de/?p=fso-frameworkd.git;a=summary
>
> They consist of a merge of the upstream-source and changes to the
> patches to apply to the new source.

Some notes:

- what is the Git URL to clone from?

- your Git repository is missing tags, which causes problems if you use
  git-buildpackage (as you should).

- please sign the tags when creating them.

However, I would prefer if you do all your work on the official git.d.o
repository, creating a new branch like heiko-debian or similar, thus no
need to look for other external links.  Do not worry about making
errors, everyone does them and they can be fixed later.  If you actually
test your work as you do, there is no reason not to commit directly to
git.d.o :-D

> If anyone with more experience will do the "real" steps on
> git.debian.org I would be happy. (the snapshot-script in /debian would
> be the weapon of choice I presume, but didn't work when I tried it ...
> some pristine-tar error).

debian/snapshot-script was/is the one Joachim uses.  I do not remember
if we have decided a specific workflow WRT upstream sources with no
official released tarballs: FYI, I let git-buildpackage do all the work
of (re)creating them and then I commit the so-generated .orig.tar.gz to
the pristine-tar branch.  Basically, Debian being a do-ocracy, who does
the work decides :-)

Once I have access to your Git repository, I will import/merge your
patches into the official Debian repository, some comments:


- I tend to like "standard" messages for similar commits
  (i.e. consistency), e.g. if you refresh Debian-specific patches to a
  new upstream version, the commit message will always be in the same
  form "refresh patch $X to new upstream version".  This will help if
  you look for them in the logs.


- dropping a patch from the debian/patches/series file is not enough,
  you should also physically remove the patch file, see my own fault:

    http://git.sntech.de/?p=fso-frameworkd.git;a=commitdiff;h=0bef5d0dc09fe69aad3c041d7206f08ba19ef12c


- the debian/changelog for new upstream versions should contain the most
  significant changes, in this case something like

    * New upstream release:
      + milestone 5.1.
      + this is the first release to be used together with the Vala
        implementation.


I think it is enough for the moment :-D

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090719/49a0b288/attachment.pgp>


More information about the pkg-fso-maint mailing list