On Wed, Jul 18, 2012 at 04:47:07PM +0200, Mehdi Dogguy wrote: > On 18/07/2012 16:22, Roberto C. Sanchez wrote: > >Package: release.debian.org Severity: normal User: > >release.debian.org@packages.debian.org Usertags: unblock > > > >-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > > > >Please unblock package shorewall > > > > You still didn't answer my question regarding this update: Why do they > _need_ to stay in sync apart the fact that upstream wants that? are > there any checks performed? > So, it turns out that this is all a big misunderstanding. Upstream "wants" the packages to stay in sync because he thinks that is what the distros "want." He has indicated that he is perfectly capable of simply releasing only the packages with actual changes for a point release, so long as the distros are OK with it. I assured him that from a Debian perspective, this is preferred. I asked him to check with the people who package Shorewall for the other distros and if they do not object, to start releasing only the package(s) with actual changes. To answer your second question, there are no checks performed. I'd like to recommend that you allow the current batch from unstable into testing since I already uploaded them and there is no way to take that back. Thanks for your time. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature