Re: Requesting freeze exception for uwsgi
On Sun, Jul 15, 2012 at 10:35 PM, Cyril Brulebois <firstname.lastname@example.org> wrote:
> Janoš Guljaš <email@example.com> (09/07/2012):
>> I've prepared a release 1.2.3+dfsg-2 (-1 in testing) but did not
>> upload to unstable as I want to consult about the changes.
> and thanks for checking with us.
>> To resolve the issue #680132 a binary package uwsgi-plugin-luajit
>> (built from src:uwsgi) must be removed from the archive, as luajit
>> will be removed from the Wheeze. There are no reverse dependencies for
> wheezy ;)
>> uwsgi-plugin-luajit (except for the meta package
>> uwsgi-app-integration-plugins which will be fixed in the same
>> release). I would like to ask is the procedure of removing a binary
>> package the same during the freeze?
> Yes, you just need to get the package removed from unstable, following:
>> The second change is applying an upstream patch regarding memory leak,
>> which is an important fix.
>> I am sending the diff for the 1.2.3+dfsg-2. Should I proceed with the
>> upload to unstable and ask for removal from ftpmaster?
> Looks good to me, even if the changelog could be a bit more descriptive
> WRT the changes for the removal; I'd suggest mentioning the package
> removed from build-deps, the package dropped from depends, and that all
> luajit occurrences were removed from debian/rules. That would make the
> reviewer more confident about the diff. ;) [ I am currently, but if
> somebody else ends up reviewing it, that means a bit of time figuring
> out all changes were intended. ]
Thanks for suggestions and help. I uploaded 1.2.3+dfsg-2, requested a
RM #681826 and a freeze exception #681827.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> -----END PGP SIGNATURE-----