Hi,
I noticed you have started a transition on the google-perftools side,
which can be seen through the excuses[1]:
| google-perftools (1.7-1 to 2.0-2)
|
| Maintainer: Daigo Moriwaki
| 58 days old (needed 10 days)
| out of date on i386: libgoogle-perftools0, libgoogle-perftools0-dbg,
Hello again Pascal.
Pascal Giard (25/05/2012):
> On Fri, May 25, 2012 at 1:12 PM, Julien Cristau wrote:
> > Scheduled.
>
> Thanks!
We're almost done, but #668793 gets in the way, through mlt. Once that
fixed, britney should be more or less happy to migrate the whole lot to
testing (with some h
Your message dated Mon, 28 May 2012 00:09:24 +0200
with message-id <20120527220924.gb23...@mraw.org>
and subject line Re: Bug#673059: transition: libindicator, libindicate
has caused the Debian Bug report #673059,
regarding transition: libindicator, libindicate
to be marked as done.
This means tha
Cyril Brulebois (24/05/2012):
> it seems like we have an uncoordinated transition, from libh323-1.21.0
> to libh323-1.24.0. The following packages need binNMUs:
> | # Broken Depends:
> | openam: openam [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x
> sparc]
> | openmcu: openmcu [amd6
I wonder whether I might be able to get some kind of response on my
proposal to upload a tiff with libtiff5-alt-dev. To help you make a
decision, I'm supplying the information you probably need. I'm hoping
you'll be able to give me a quick decision, or at least give me a quick
response indicating
On 27 May 2012 at 09:55, peter green wrote:
| >| At least for s390 the problem is not buildd resources. s390 has a 31bit
| >| address space, which g++ manages to exhaust compiling this insane source
| >| file. That can't be fixed by rescheduling.
|
| >So what do we do?
|
| My suggestion woul
Processing commands for cont...@bugs.debian.org:
> unblock 674541 with 645105
Bug #674541 [src:ruby1.8] ruby1.8: segfaults when compiled with gcc-4.7
674541 was blocked by: 645105
674541 was blocking: 645105
Removed blocking bug(s) of 674541: 645105
> block 645105 with 674541
Bug #645105 [release.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Please remove thoggen from testing. It's RC-buggy since 7 months, has
no rev-deps and the last maintainer upload was in 2008.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-relea
Your message dated Sun, 27 May 2012 14:08:56 +0200
with message-id <4fc21958.90...@dogguy.org>
and subject line Re: Bug#668654: transition: libmemcached
has caused the Debian Bug report #668654,
regarding transition: libmemcached
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tag 674750 pending
Bug #674750 [release.debian.org] transition: libnunit2.6
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
674750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674750
Deb
tag 674750 pending
thanks
Jo Shields (27/05/2012):
> Ben parameters as follows:
>
> Affected: .build-depends ~ /libnunit-cil-dev/
> Good: .depends ~ /libnunit2.6-cil/
> Bad: .depends ~ /libnunit2.5-cil/
I changed the affected line, but the tracker is at:
http://release.debian.org/transitions/
Hi,
On Samstag, 26. Mai 2012, Cyril Brulebois wrote:
> libextractor-python | python-extractor uninstallable: #674616
> doddle | FTBFS: #674333
> libextractor-java| FTBFS: #674359
I've just successfully rebuild these on sid/amd64 with the versions in
experimental and would be w
stay because of:
> > # Broken Depends:
> > magics++: libmagplus3 [amd64 armel armhf i386 ia64 kfreebsd-amd64
> > kfreebsd-i386 mipsel powerpc s390]
>
> I've just moved the tracker from ongoing to finished, and I'll
> investigate this magics++ thing later on.
Easily
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
We would really like to update the unit testing library in Wheezy from version
2.5.x to the stable 2.6 release. Unfortunately this requires a small ABI break.
One major factor for us in r
Hi,
On Sonntag, 27. Mai 2012, Cyril Brulebois wrote:
> This also means that vdr (and dozens of related packages) can't migrate,
eek.
> Alternative way of getting stuff unfucked at this point: reupload the
> old package (with an epoch, or with a $foo.really-is.$bar trick), until
> you're able to
Cyril Brulebois (26/05/2012):
> libextractor-python | python-extractor uninstallable: #674616
> doddle | FTBFS: #674333
> fossology| FTBFS: #674381
> libextractor-java| FTBFS: #674359
>
> (No, I didn't look into gnunet*, too much fail already.)
This also means that
Cyril Brulebois (21/05/2012):
> Tracker is at:
> http://release.debian.org/transitions/html/grib-api.html
grib-api was decrufted by ftpmasters, and could finally migrate to
testing:
grib-api | 1.9.16-2 | testing | source
grib-api | 1.9.16-2 | unstable | source
The old binari
| At least for s390 the problem is not buildd resources. s390 has a 31bit
| address space, which g++ manages to exhaust compiling this insane source
| file. That can't be fixed by rescheduling.
So what do we do?
My suggestion would be to drop the optimisation level to -O1 (and if that
fail
18 matches
Mail list logo
