Re: anna_1.68_source.changes ACCEPTED into unstable

[Holger Wansing]

Hi,

Cyril Brulebois  wrote:
> Hello,
> 
> Here are some answers. Feel free to (re)organize them in a wiki page
> under the DebianInstaller namespace. :)

If have documented the l10n-uploading procedere on the wiki, to be found at 
https://wiki.debian.org/DebianInstaller/Uploading


Holger

> Holger Wansing  (2018-08-10):
> > Yes, and I didn't read anything about that in the several
> > packaging/uploading docu. So that's mostly best practice, but no
> > strict packaging rule or the like?
> > 
> > Also, I don't know anything about tagging.  So, I need to know
> > something more about this tagging:
> > 
> > When do we use it?
> > Just for every new uploaded version, as it seems...
> > More circumstances, where to set tags?
> 
> I think most if not all packaging teams create tags when they upload a
> given revision of a source package; this even existed prior to git! :)
> 
> This makes it possible to identify what revision of source code was
> (probably, no absolute guarantee) used to create a given package,
> which limits the need for downloading entire history of source
> packages using debsnap and friends.
> 
> > Which tags do we use? The lightweighted or the annotated ones?
> > Looking at the existing tags, it seems that's annotated ones, but
> > without GPG signatur. Right?
> 
> I tend to use this when releasing:
> 
>   git commit -am 'releasing version $copied_from_changelog'
>   git tag -sm 'tagging version $copied_from_changelog' 
> $copied_possibly_adapted_from_changelog
> 
> If you don't have a GPG key handy (but then how would you debsign your
> upload?), you might want to use “git tag -am” instead of “git tag -sm”,
> which indeed creates an annotated tag, which still contains meta data
> like the tagger, a message, etc.; except for the GPG signature part.
> 
> Interesting points:
>  - you can mention the real/complete version in there;
>  - you can verifiy the GPG signature if you ever doubt the repository
>(remember we have rather broad access with many many users on
>alioth first and on salsa now);
>  - “git describe” doesn't use lightweight tags by default, one needs
>to pass “--tags”, so annotated/signed tags are better for that as
>well.
> 
> What about those versions?
>  - $copied_from_changelog: hopefully self-explanatory :)
>  - $copied_possibly_adapted_from_changelog: there are special
>characters that can be used in Debian version numbers, but cannot
>be used directly in git (like ':' and '~'), so we have to adjust
>for those.
> 
> Examples for ':' include apt-setup, busybox, tzsetup; depending on the
> habits of the person who uploads them, the epoch part (N:) is
> sometimes removed entirely (there can be a single version in the
> Debian archive of a given package, regardless of the epoch part,
> anyway). Usual replacement character is '%'.
> 
> Examples for '~' include all packages we backport using the usual
> scheme: $unstable_version~deb9u1. Usual replacement character is '_'.
> 
> People might use git-buildpackage which has some tagging options,
> but I tend to find the command line overly long, and it prefixes
> tags with a debian/ string, which we doesn't really make sense in a
> d-i context since most packages are Debian-specific anyway. We could
> arguable ship a configuration file in all packages, but I'm not sure
> we need more administrativia…
> 
> Maybe we should just have a tagging script in the scripts/ directory?
> I used to use “xsf-tag” in the X Strike Force:
>   https://salsa.debian.org/xorg-team/debian/xsf-tools/blob/master/xsf-tag
> 
> What do you think?
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: anna_1.68_source.changes ACCEPTED into unstable

[Holger Wansing]

Hi,

Cyril Brulebois  wrote:
> Hello,
> 
> Here are some answers. Feel free to (re)organize them in a wiki page
> under the DebianInstaller namespace. :)
> 
> Holger Wansing  (2018-08-10):
> > Yes, and I didn't read anything about that in the several
> > packaging/uploading docu. So that's mostly best practice, but no
> > strict packaging rule or the like?
> > 
> > Also, I don't know anything about tagging.  So, I need to know
> > something more about this tagging:
> > 
> > When do we use it?
> > Just for every new uploaded version, as it seems...
> > More circumstances, where to set tags?
> 
> I think most if not all packaging teams create tags when they upload a
> given revision of a source package; this even existed prior to git! :)
> 
> This makes it possible to identify what revision of source code was
> (probably, no absolute guarantee) used to create a given package,
> which limits the need for downloading entire history of source
> packages using debsnap and friends.
> 
> > Which tags do we use? The lightweighted or the annotated ones?
> > Looking at the existing tags, it seems that's annotated ones, but
> > without GPG signatur. Right?
> 
> I tend to use this when releasing:
> 
>   git commit -am 'releasing version $copied_from_changelog'
>   git tag -sm 'tagging version $copied_from_changelog' 
> $copied_possibly_adapted_from_changelog

Ok, understood.
And done.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: anna_1.68_source.changes ACCEPTED into unstable

[Cyril Brulebois]

Hello,

Here are some answers. Feel free to (re)organize them in a wiki page
under the DebianInstaller namespace. :)

Holger Wansing  (2018-08-10):
> Yes, and I didn't read anything about that in the several
> packaging/uploading docu. So that's mostly best practice, but no
> strict packaging rule or the like?
> 
> Also, I don't know anything about tagging.  So, I need to know
> something more about this tagging:
> 
> When do we use it?
> Just for every new uploaded version, as it seems...
> More circumstances, where to set tags?

I think most if not all packaging teams create tags when they upload a
given revision of a source package; this even existed prior to git! :)

This makes it possible to identify what revision of source code was
(probably, no absolute guarantee) used to create a given package,
which limits the need for downloading entire history of source
packages using debsnap and friends.

> Which tags do we use? The lightweighted or the annotated ones?
> Looking at the existing tags, it seems that's annotated ones, but
> without GPG signatur. Right?

I tend to use this when releasing:

  git commit -am 'releasing version $copied_from_changelog'
  git tag -sm 'tagging version $copied_from_changelog' 
$copied_possibly_adapted_from_changelog

If you don't have a GPG key handy (but then how would you debsign your
upload?), you might want to use “git tag -am” instead of “git tag -sm”,
which indeed creates an annotated tag, which still contains meta data
like the tagger, a message, etc.; except for the GPG signature part.

Interesting points:
 - you can mention the real/complete version in there;
 - you can verifiy the GPG signature if you ever doubt the repository
   (remember we have rather broad access with many many users on
   alioth first and on salsa now);
 - “git describe” doesn't use lightweight tags by default, one needs
   to pass “--tags”, so annotated/signed tags are better for that as
   well.

What about those versions?
 - $copied_from_changelog: hopefully self-explanatory :)
 - $copied_possibly_adapted_from_changelog: there are special
   characters that can be used in Debian version numbers, but cannot
   be used directly in git (like ':' and '~'), so we have to adjust
   for those.

Examples for ':' include apt-setup, busybox, tzsetup; depending on the
habits of the person who uploads them, the epoch part (N:) is
sometimes removed entirely (there can be a single version in the
Debian archive of a given package, regardless of the epoch part,
anyway). Usual replacement character is '%'.

Examples for '~' include all packages we backport using the usual
scheme: $unstable_version~deb9u1. Usual replacement character is '_'.

People might use git-buildpackage which has some tagging options,
but I tend to find the command line overly long, and it prefixes
tags with a debian/ string, which we doesn't really make sense in a
d-i context since most packages are Debian-specific anyway. We could
arguable ship a configuration file in all packages, but I'm not sure
we need more administrativia…

Maybe we should just have a tagging script in the scripts/ directory?
I used to use “xsf-tag” in the X Strike Force:
  https://salsa.debian.org/xorg-team/debian/xsf-tools/blob/master/xsf-tag

What do you think?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: anna_1.68_source.changes ACCEPTED into unstable

[Holger Wansing]

Hi,

Cyril Brulebois  wrote:
> Debian FTP Masters  (2018-08-09):
> >  anna (1.68) unstable; urgency=medium
> >  .
> >* Team upload
> >  .
> >[ Cyril Brulebois ]
> >* Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
> >  .
> >[ Updated translations ]
> >* Hebrew (he.po) by Yaron Shahrabani
> 
> Congratulations! :)
> 
> Now you need to remember tagging and pushing your tag. :)
> 
> (That's on me, I didn't explicitly mention that in our mail exchange.)

Yes, and I didn't read anything about that in the several packaging/uploading
docu.
So that's mostly best practice, but no strict packaging rule or the like?

Also, I don't know anything about tagging.
So, I need to know something more about this tagging:

When do we use it?
Just for every new uploaded version, as it seems...
More circumstances, where to set tags?

Which tags do we use? The lightweighted or the annotated ones?
Looking at the existing tags, it seems that's annotated ones, but without
GPG signatur. Right?



Holger



-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: anna_1.68_source.changes ACCEPTED into unstable

[Cyril Brulebois]

Debian FTP Masters  (2018-08-09):
>  anna (1.68) unstable; urgency=medium
>  .
>* Team upload
>  .
>[ Cyril Brulebois ]
>* Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
>  .
>[ Updated translations ]
>* Hebrew (he.po) by Yaron Shahrabani

Congratulations! :)

Now you need to remember tagging and pushing your tag. :)

(That's on me, I didn't explicitly mention that in our mail exchange.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

anna_1.68_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Aug 2018 20:00:09 +0200
Source: anna
Binary: anna
Architecture: source
Version: 1.68
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Description:
 anna   - anna's not nearly apt, but for the Debian installer, it will do 
(udeb)
Changes:
 anna (1.68) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
 .
   [ Updated translations ]
   * Hebrew (he.po) by Yaron Shahrabani
Checksums-Sha1:
 115a45c8258e8ec6a1f41b08548c29229e412495 1668 anna_1.68.dsc
 15c0a0ea06b7234889122ffa8a2c8f8d76e46fff 90348 anna_1.68.tar.xz
 f799c89460dd9a500e3f798a7abbd6e569d45ade 5460 anna_1.68_amd64.buildinfo
Checksums-Sha256:
 516234394ee9287635e1603448cc1f2ce47bcdefae6fcd5d1c22695910832fef 1668 
anna_1.68.dsc
 e51fa209d70be82e28f26fe0f3e99109e4007a755b0b9c5c5abc3646a46b97ed 90348 
anna_1.68.tar.xz
 15617986a9fd6d4d00b62411ab9783602c04fafe1f84731ea000495609008a82 5460 
anna_1.68_amd64.buildinfo
Files:
 5339847921b62e6a9dd79da7f8dbac2e 1668 debian-installer standard anna_1.68.dsc
 6404283978d8df3f558219009829a891 90348 debian-installer standard 
anna_1.68.tar.xz
 ef70352312b6c365a97bffca5b5250fe 5460 debian-installer standard 
anna_1.68_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAltsvz0ACgkQWfGHyhVu
sHakCQ/+IGffNhqXezxsy4HhJJFBFtG6HCBrfLBtyBTk7zx2hvXttwzceXixR9Qh
oWEqHaiuVcVZ5i4Iwx/39gSCrdhZyvi6bF4Gm9q3GukvXCVLdHzJ/Swpkm1w1S11
lD7NaL2QcONRX0XdB86C+DgDMkWeWzwgy0ddvVa50Ang8/4JBl6cfBsM/Hwx90JC
l8RO0jsMPFztRgUnmQVLJxBp3lOOIaHjV2tZ0RtdP7kI4/5CzxHZEQBMyMLC+8jS
beip3vQcTLYajFCmV3snYbOVhZyN9aKG4avTD7GEmgUMDl2B5s2H9nzmbBC3uZD7
I/lm4WrlGXoypH9Cs2LqBwUdUEW3YoZPhH6tUiv7ExC582WRpRcLvJQE7bVExo2r
ySRdG/z54Vv5H7OTtJfOorIlULiLnriVBRNuch21a3hvDzIAt3kSG4xUY0ksZGIb
g0vq9URTT7qyiLY7uefGut6pMTywEPdkGeELKgBNtYoBesYDoWbEnZ4v4Eusoint
toyGQc1KGGfsj2FHe4z8aQGKbrVwTQ4tE5ub1WQsLabAVKovUnbh1XXvWarJUy7Q
m2WkziQaWbcFvl+9N50mGRv4Rg6aF50KUV2PpWRhD0wQQiwSlTcRN3A79kj7pn0e
eJajstR7ICpWJhA5GQtCtFbq3gTpqBAnEkwAqZ78EFmsgCUT8VE=
=FJSS
-END PGP SIGNATURE-


Thank you for your contribution to Debian.