Hello release team,
songwrite is currently orphaned and has an RC bug #672210. The problem is
that the version of songwrite is much too old, in fact upstream has since
october 2007 (!) moved from songwrite to songwrite2. IMHO, fixing #672210
would require to upload a *new* package songwrite2, and
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gcpegg. This version fixes RC bug #680014 which
affects all 64-bit architectures. It also fixes an unreported path bug
in the init.d script that would affect all us
Your message dated Wed, 04 Jul 2012 06:08:09 +0100
with message-id <1341378489.3769.10.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#680151: unblock: libsvn-notify-mirror-perl/0.03800-2
has caused the Debian Bug report #680151,
regarding unblock: libsvn-notify-mirror-perl/0.03800-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Release Team
libsvn-notify-mirror-perl FTBFS with subversion 1.7.5 in unstable.
This is bug #678791. This does not (yet) affect
On Tue, Jul 03, 2012 at 07:26:23PM +0100, Adam D. Barratt wrote:
> With those changes, please feel free to go ahead; thanks.
Done, I just uploaded a package with those changes, thanks for the fast
response.
Regards
Javier
signature.asc
Description: Digital signature
On Tue, Jul 03, 2012 at 12:59:39AM +0200, Cyril Brulebois wrote:
> Hello,
>
> Wouter Verhelst (02/07/2012):
> > No, this isn't a request for a freeze exception, yet. I'd just like to
> > test the waters before I start working on this: […]
>
> I think the [2] pointer in the freeze announce covers
On Tue, 2012-07-03 at 00:44 +0300, Yavor Doganov wrote:
> At Sun, 01 Jul 2012 00:02:17 +0100,
> Adam D. Barratt wrote:
> > On Fri, 2012-06-29 at 21:20 +0300, Yavor Doganov wrote:
> > > Uploading gnustep-base/1.22.1 with the libobjc4 patch will allow
> > > the package to be built with gcc-4.7 on x86
tags 679350 +moreinfo +unreproducible
thanks
I cannot reproduce the crash but there is a patch if someone can. Else
can this bug be downgraded to important.
I was thinking of raising an NMU but I'm not sure if I feel comfortable
for just one bug.
And of course I have copied the maintainer.
--
Hi release team,
I suggest we remove libggi from Wheezy. It's totally obsolete these days,
dead upstream and RC-buggy since 1.5 years (608981).
Removing it would involve the following packages:
GGI-related and to be removed along, no rev-deps on their own:
libgiigic
libggimisc
libggiwmh
libggigcp
On Tue, 2012-07-03 at 09:46 +0200, Michal Čihař wrote:
> I'd like to upload colorhug-client 0.1.11-1 to unstable and get freeze
> exception for it. It's new upstream release which fixes few annoying
> bugs (most notably broken dark offsets calibration). The package
> contains tool for managing Colo
On 03/07/2012 19:55, Adam D. Barratt wrote:
On Tue, 2012-07-03 at 19:41 +0200, Tshepang Lekhonkhobe wrote:
Rule #7 at freeze policy page[1] is not very clear to me: is it
sufficient to only use reportbug (with "unblock" pseudo-package), or if
I can do that AND send a request to the mailing list.
On Mon, 2012-07-02 at 22:39 +, Tzafrir Cohen wrote:
> There's no real changelog. However the difference between pre18 and
> pre20 is not big.
>
> pre19:
> https://gitorious.org/spandsp/spandsp/commit/926c6eec0a2955dffccea3992232d0a064f4a5f6
> A bugfix commit. IIRC the fix in t4_rx.c was discov
severity 677328 important
thanks
On Tue, 2012-07-03 at 20:31 +0100, Nicholas Bamber wrote:
> The broken packages have been removed from arm* testing.
s/testing//. On that basis, the bug's only "important" and doesn't
require (nor indeed qualify for) an -ignore tag.
Regards,
Adam
--
To UNSUB
The broken packages have been removed from arm* testing.
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ff3489b.7040...@periapt.co.uk
This is one I raised and people are asking me to upgrade the w3c stuff
which requires fixing it. It probably just requires a slight application
of xargs, but the XML world in Debian is pretty dead and quite a lot is
going on already and XML is not my top focus. So altogether I would
rather look at
On Tue, 2012-07-03 at 10:08 +0200, Ivo De Decker wrote:
> Based on this hint by jcristau, subversion 1.7 will not be in wheezy.
It's a little early to be making such an absolute statement. The block
is there to give chance for the reverse dependencies to be triaged and
fixed.
> Is it
> acceptabl
Your message dated Tue, 03 Jul 2012 19:52:52 +0100
with message-id <1341341572.28943.18.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#680091: RM: nuitka/0.3.22.1+ds-1
has caused the Debian Bug report #680091,
regarding RM: nuitka/0.3.22.1+ds-1
to be marked as done.
This means that
On Tue, 2012-07-03 at 19:58 +0200, Javier Fernández-Sanguino Peña wrote:
> I have prepared a new cron release (3.0pl1-124) which includes fixes for the
> following bugs:
>
> - #679106 - critical - /etc/init.d/cron stop may kill unrelated processes
> - #679062 - important - remove obsolete /etc/c
On Tue, 2012-07-03 at 19:23 +0200, Tshepang Lekhonkhobe wrote:
> Please unblock package wajig. The change improves multi-arch
> handling slightly and fixes a related exception.
The source package appears to have grown a bunch of cruft:
-rw-r--r-- 0/0 55262 2012-07-02 19:06 wajig-2.7.1/d
Dear Release Managers,
I have prepared a new cron release (3.0pl1-124) which includes fixes for the
following bugs:
- #679106 - critical - /etc/init.d/cron stop may kill unrelated processes
- #679062 - important - remove obsolete /etc/cron.daily/standard on upgrade
It also includes some minor
On Tue, 2012-07-03 at 19:41 +0200, Tshepang Lekhonkhobe wrote:
> Rule #7 at freeze policy page[1] is not very clear to me: is it
> sufficient to only use reportbug (with "unblock" pseudo-package), or if
> I can do that AND send a request to the mailing list.
It says "either by X or Y"; that mean
Rule #7 at freeze policy page[1] is not very clear to me: is it
sufficient to only use reportbug (with "unblock" pseudo-package), or if
I can do that AND send a request to the mailing list. I think it would
better to get rid of the last 2 sentences, since they add to the confusion.
Also, I saw
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package wajig. The change improves multi-arch
handling slightly and fixes a related exception.
diff -Nru wajig-2.7/debian/changelog wajig-2.7.1/debian/changelog
--- w
Mike Gabriel (03/07/2012):
> The next Debian Edu release 6.0.5+r1 depends on a security fix in
> GOsa² (src:package gosa):
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665950
>
> A new squeeze compliant version of gosa (2.6.11-3+squeeze2) has now
> been provided by the gosa maintainer.
>
>
Your message dated Tue, 3 Jul 2012 16:30:49 +0200
with message-id <20120703143049.gd26...@mraw.org>
and subject line Re: Bug#680092: nmu: ogre_1.7.4-5
has caused the Debian Bug report #680092,
regarding nmu: ogre_1.7.4-5
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Tue, 3 Jul 2012 16:30:21 +0200
with message-id <20120703143021.gc26...@mraw.org>
and subject line Re: Bug#680093: nmu: k3d_0.8.0.2-18
has caused the Debian Bug report #680093,
regarding nmu: k3d_0.8.0.2-18
to be marked as done.
This means that you claim that the problem has been
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Please binNMU k3d 0.8.0.2-18 in mipsel. I believe that this is a
transient error particular to mipsel, related with Python support or
dependencies: it's the same situation explained for my n
Dear release team,
The next Debian Edu release 6.0.5+r1 depends on a security fix in
GOsa² (src:package gosa):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665950
A new squeeze compliant version of gosa (2.6.11-3+squeeze2) has now
been provided by the gosa maintainer.
May I ask you to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Please binNMU ogre 1.7.4-5 in mipsel. ogre-1.8 is very similar, has
been rebuilt a couple of days ago without problems. Neither 1.7 nor
1.8 fail in any other architectures, so I believe tha
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Nuitka is a new and actively developed project. But it is not yet a good fit
for a stable Debian release because of its yet experimental and evolving
nature. So please remove it from wheezy.
T
On Mon, Jul 02, 2012 at 11:46:27PM +0200, Steinar H. Gunderson wrote:
> I'm looking to see if it would be possible to get a freeze exception for
> snappy (producing libsnappy1 and libsnappy-dev). testing has had 1.0.4-1 for
> a long time; 1.0.5-1, a new upstream release (containing mostly performan
Your message dated Tue, 3 Jul 2012 14:14:00 +0200
with message-id <20120703121400.ga31...@radis.cristau.org>
and subject line Re: Bug#671853: Transition: cpl
has caused the Debian Bug report #671853,
regarding Transition: cpl
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 3 Jul 2012 14:15:24 +0200
with message-id <20120703121524.ga31...@radis.cristau.org>
and subject line Re: Bug#615513: Bit from the Release Team: armhf and s390x
has caused the Debian Bug report #615513,
regarding release.debian.org: armhf inclusion into the archive as a rele
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package fonts-sil-padauk
This package provides a fonts udeb. There should be few impact on D-I
as the package is in the graphical installer images and the update
will just pr
Hello Damyan,
redirecting to ia64@buildd.d.o + wb team:
Damyan Ivanov (03/07/2012):
> Due to #679680 in libatomic-ops-dev, firebird2.5 failed to build on
> ia64.
>
> The bug is fixed in version 7.3~alpha1+git20120701-1, but I am not
> sure what would be the best way to ensure that it is prese
Due to #679680 in libatomic-ops-dev, firebird2.5 failed to build on
ia64.
The bug is fixed in version 7.3~alpha1+git20120701-1, but I am not
sure what would be the best way to ensure that it is present on the
buildd. Adding a versioned build-dependency would mean firebird2.5
won't be buildable
Roger Leigh schrieb am Tuesday, den 03. July 2012:
> Hi,
>
> We've been defaulting to dependency based for new installs for
> several years. Since last week, sysv-rc unconditionally uses
> dependency-based boot. file-rc is the last package using
> static sequencing.
>
> I'd like (for wheezy+1)
Hi,
We've been defaulting to dependency based for new installs for
several years. Since last week, sysv-rc unconditionally uses
dependency-based boot. file-rc is the last package using
static sequencing.
I'd like (for wheezy+1) to remove the static sequence numbers
entirely. To do this, we nee
On Mon, Jul 02, 2012 at 11:46:27PM +0200, Steinar H. Gunderson wrote:
> The debdiff between 1.0.5-1 and 1.0.5-2 is simple, and I'll be putting it
> upstream as soon as it goes through code review at work.
Oh, and I also have a fix for the build failure on hurd-i386 (it fixes a
division by zero in
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking package fracplanet/0.4.0-3
The version fixes FTBFS 653584 caused by the
configuration target being phony by mistake.
It also makes sure the proper flags are pass
Yaroslav Halchenko (02/07/2012):
> I guess you might like then to adjust
> http://release.debian.org/wanna-build.txt to make it explicit to not
> use a uniform channel via reportbug and research first for the proper
> point of contact to seek gb requests
I think it's explicit already, if one can
Hi,
just after freeze I heard that emacs24 got a freeze-exception [1]. I
maintain magit which is an add-on to emacs. Since magit does not support
xemacs21 or emacs22 it has to maintain an explicit list of supported
emacs versions as per debian emacs policy [2].
If we release wheezy with emacs24 I
Dear release team,
Based on this hint by jcristau, subversion 1.7 will not be in wheezy. Is it
acceptable to tag these bugs (and maybe others caused by svn 1.7)
wheezy-ignore?
# 20120627
# 1.7 causes breakage in reverse deps
# e.g. 678845 678203 678137 678791 678760 678559 678783 678773
block sub
Hi
I'd like to upload colorhug-client 0.1.11-1 to unstable and get freeze
exception for it. It's new upstream release which fixes few annoying
bugs (most notably broken dark offsets calibration). The package
contains tool for managing ColorHug device and there are no reverse
dependencies.
Not att
Am 03.07.2012 00:12, schrieb Adam D. Barratt:
On Wed, 2012-06-27 at 19:34 +0100, Adam D. Barratt wrote:
On Wed, 2012-06-27 at 02:52 +0200, Sebastian Reichel wrote:
NEW:
libfsotransport 0.11.1-2
libgsm0710mux 0.11.2-1
No longer NEW thanks to speedy processing by ftp-team. :-)
uploaded:
45 matches
Mail list logo
