Re: Hint: uploading to experimental instead of unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ludovic Brenta a écrit :
> In Bug#239769 opened against music123, Xavier Grave wrote:
>> using a temporary vector and apply sort on it fix the bug and respect
>> command line order. This is implemented in version 16.2 and should be
>> uploaded when 16.0-1 reaches testing.
>
> Here is a hint, just for the record.
>
> In this situation, you (the package maintainer) can upload a new version
> to experimental instead of unstable. For this the only change you need
> to make to the package is in the first line of debian/changelog. In this
> case it should read:
>
> music123 (16.2-1) experimental; urgency=low
>
> Also, remember that packages in experimental never migrate to testing
> (or to unstable, for that matter), so you will have to re-upload to
> unstable at a later point in time with a new version number:
>
> music123 (16.2-2) unstable; urgency=low
>
> * Satisfied with the new features, upload to unstable.
OK, thanks for the hint.
Does the upload to experimental closes bug as upload to unstable does ?
I didn't find a clear statement (at least for me) about this one the
web. There is a fixed-in-experimental tag, but does it propagate when
the package is uploaded to unstable ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkuU6TYACgkQVIZi0A5BZF4CawCgpYoIQoIc5j9dHv2exQAJmqCr
8+gAnAgjPIhV1qCklFbC2CRmpUph7bwC
=ugTs
-----END PGP SIGNATURE-----
Reply to: