Bug#600545: marked as done (unblock: puppet/2.6.2-1)
Your message dated Mon, 25 Oct 2010 21:46:42 +0200
with message-id <4CC5DEA2.7010704@debian.org>
and subject line Re: unblock: puppet/2.6.2-1
has caused the Debian Bug report #600545,
regarding unblock: puppet/2.6.2-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.)
--
600545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600545
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: freeze-exception
Hello release team!
I am writing on behalf of the puppet packaging team. We would like to request a
freeze exception for the puppet 2.6.2-1 package. The existing version in
Squeeze contains too many severe bugs, including a few RC regressions. If we
ship the version that is in Squeeze, puppet will be unusable for a very long time
in Debian.
How we got here was a case of bad timing. The upstream release of puppet 2.6.0
arrived (July 20th) right before the Debian freeze (August 6th). This resulted
in the package transitioning into Squeeze and then almost immediately after, we
froze. This was an unfortunate situation as the 2.6.0 version of the software
turned out to be significantly buggy and unsuitable for release. In fact, the
RC bug #597399 was filed which pointed out some severe regressions from the
previous version. Puppet 2.6.2 primarily is a bug fix release to fix a number
of usability issues, documentation fixes and license clarifications.
We attempted to go through a process of cherry-picking a number of commits from
2.6.1/2 to 2.6.0 to fix these important bugs, but there are still a large
number of unfixed issues in the debian package. Continuing to do this would
result in a Debian version of puppet that differs from both 2.6.0 and 2.6.1
which would be difficult to support in the long run, and confusing for the
users.
We also did some packaging restructuring for after 2.6.0 but have decided that
in the interests of fixing only the necessary bits for release, we have
reverted the packaging restructuring for the 2.6.2 version that we would like
to enter into Squeeze.
Let us know if you have any questions, and thank you very much for your hard
work on Squeeze, it is very appreciated!
unblock puppet/2.6.2-1
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
> I am writing on behalf of the puppet packaging team. We would like to
request a
> freeze exception for the puppet 2.6.2-1 package. The existing version in
> Squeeze contains too many severe bugs, including a few RC regressions.
If we
> ship the version that is in Squeeze, puppet will be unusable for a
very long time
> in Debian.
>
> How we got here was a case of bad timing. The upstream release of
puppet 2.6.0
> arrived (July 20th) right before the Debian freeze (August 6th). This
resulted
> in the package transitioning into Squeeze and then almost immediately
after, we
> froze. This was an unfortunate situation as the 2.6.0 version of the
software
> turned out to be significantly buggy and unsuitable for release. In
fact, the
> RC bug #597399 was filed which pointed out some severe regressions
from the
> previous version. Puppet 2.6.2 primarily is a bug fix release to fix a
number
> of usability issues, documentation fixes and license clarifications.
>
> We attempted to go through a process of cherry-picking a number of
commits from
> 2.6.1/2 to 2.6.0 to fix these important bugs, but there are still a large
> number of unfixed issues in the debian package. Continuing to do this
would
> result in a Debian version of puppet that differs from both 2.6.0 and
2.6.1
> which would be difficult to support in the long run, and confusing for the
> users.
>
> We also did some packaging restructuring for after 2.6.0 but have
decided that
> in the interests of fixing only the necessary bits for release, we have
> reverted the packaging restructuring for the 2.6.2 version that we
would like
> to enter into Squeeze.
>
> Let us know if you have any questions, and thank you very much for
your hard
> work on Squeeze, it is very appreciated!
unblocked
Cheers
Luk
--- End Message ---
Reply to: