[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681989: marked as done (unblock: shorewall-init/4.5.5.3-1 shorewall-core/4.5.5.3-1 shorewall/4.5.5.3-1 shorewall6/4.5.5.3-1 shorewall-lite/4.5.5.3-1 shorewall6-lite/4.5.5.3-1)

Your message dated Thu, 19 Jul 2012 16:42:27 +0200
with message-id <50081CD3.7040009@dogguy.org>
and subject line Re: Bug#681989: unblock: shorewall-init/4.5.5.3-1 shorewall-core/4.5.5.3-1 shorewall/4.5.5.3-1 shorewall6/4.5.5.3-1 shorewall-lite/4.5.5.3-1 shorewall6-lite/4.5.5.3-1
has caused the Debian Bug report #681989,
regarding unblock: shorewall-init/4.5.5.3-1 shorewall-core/4.5.5.3-1 shorewall/4.5.5.3-1 shorewall6/4.5.5.3-1 shorewall-lite/4.5.5.3-1 shorewall6-lite/4.5.5.3-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
681989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681989
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

New upstream point release
c.f. http://lists.debian.org/debian-release/2012/07/msg00093.html

unblock shorewall-init/4.5.5.3-1
unblock shorewall-core/4.5.5.3-1
unblock shorewall/4.5.5.3-1
unblock shorewall6/4.5.5.3-1
unblock shorewall-lite/4.5.5.3-1
unblock shorewall6-lite/4.5.5.3-1

- -- System Information:
Debian Release: 6.0.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJQBsaXAAoJECzXeF7dp7IPs+MP/jM6rXJqNhSDZ9qOlYoNWJDJ
jUIKEYhqBPRUtgsa/wvXwqUdBEFzEUxtjUUltRLlynTRS7CIvjDqMNEr22glddyY
A7HOcIuTcmFEoWnPK0R19qXMj4qfb8zmLeqasEXxjLRd2V7D3nDninTXXQyRiws2
cf9ftoqApVdsr6DB4RKxmstrwcsYeIl/WNAzkNzdAgMhZ86MxZefj3wrR+7No+aT
gdGvj345sE3Va/raAYaeEJ67oimJbMXqbosAc7LlXadQjaOvq3ImY8rSiLf+wQXE
SOfIG0tIOW4jj+vAGehp8z9kLKzHsaKI1LWf+cOGZGpEMT8CeeUskSfId/yV2a9+
U4BTd1wYskUYglaeKm9gjs5vR/IXetyVSzEUSCk8FPZO25PgUZ6vsCOAn9k9Djqw
7PM4Zp8noOF47HzBUlIOOIKeEyqTXG4MjRrGLIDLDk/yL7hMJaer/6bkM5COTkMs
eu0Xpws8FacG+vra/7IzJ33eoKNBOgEOcncT08HvynSJ/VeCCQmOlk55RhZumu7e
c5PclGiED4yAJ1JkrC0SSBEaxQBzZQnScU1s4OlqyEMAGeKfbZcyTkCAtGI5Kd7r
GLI8dtIkItnBnTbP3euyb5keXkXwAkqTX9D4dvVc+OkICjxCtKr00LaSzIOyoE6y
UJz1ex3Fln93oFY/9B7x
=McoC
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 19/07/12 16:19, Roberto C. Sánchez wrote:

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.



Ok, thanks for your work on this. Hopefully we will have simpler updates
in the future.


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.



Granted.

Regards,

--
Mehdi Dogguy مهدي الدڤي

--- End Message ---
Reply to: