Processed: block 614726 with 614458 606717

2011-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: block 614726 with 614458 606717 Bug #614726 [release.debian.org] FFmpeg 0.6 transition Was blocked by: 614958 554340 614996 554310 614725 614954 614727 614952 612482 614953 614446 614957 614956 Added blocking bug(s) of 614726: 606717 and 614458

Processed: block 614726 with 614467

2011-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: block 614726 with 614467 Bug #614726 [release.debian.org] FFmpeg 0.6 transition Was blocked by: 614958 606717 554340 614458 554310 614996 614725 614954 614727 614952 612482 614953 614957 614446 614956 Added blocking bug(s) of 614726: 614467

Processed: block 614726 with 554061 614433 614447 555784 614457 556672

2011-03-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: block 614726 with 554061 614433 614447 555784 614457 556672 Bug #614726 [release.debian.org] FFmpeg 0.6 transition Was blocked by: 614958 554310 614725 614467 614727 612482 614953 606717 554340 614458 614996 614954 614952 614957 614446 614956

Re: How to update developers-reference (Re: [SRM] upload of debian-reference/2.46 to stable)

2011-03-01 Thread Osamu Aoki
Hi, I read developers-reference but what I am seeing is a bit dirrefent. Read on On Mon, Feb 28, 2011 at 09:26:01PM +0100, Philipp Kern wrote: Hi, On Mon, Feb 28, 2011 at 09:36:30PM +0900, Osamu Aoki wrote: stable-proposed-updates is defined as:

NEW changes in proposedupdates

2011-03-01 Thread Debian FTP Masters
Processing changes file: samba_3.5.6~dfsg-3squeeze2_i386.changes ACCEPT Processing changes file: samba_3.5.6~dfsg-3squeeze2_amd64.changes ACCEPT Processing changes file: samba_3.5.6~dfsg-3squeeze2_armel.changes ACCEPT Processing changes file: samba_3.5.6~dfsg-3squeeze2_ia64.changes ACCEPT

Re: How to update developers-reference (Re: [SRM] upload of debian-reference/2.46 to stable)

2011-03-01 Thread Philipp Kern
On Tue, Mar 01, 2011 at 10:33:22PM +0900, Osamu Aoki wrote: Well, I just uploaded 2.46 to stable for debian-reference. This seems to be gone into stable-updates per some information I got as mail from Debian FTP Masters as: | Date: Mon, 28 Feb 2011 20:04:20 + | From: Debian FTP Masters

Re: How to update developers-reference (Re: [SRM] upload of debian-reference/2.46 to stable)

2011-03-01 Thread Adam D. Barratt
On Tue, March 1, 2011 13:33, Osamu Aoki wrote: On Mon, Feb 28, 2011 at 09:26:01PM +0100, Philipp Kern wrote: every package will enter stable-proposed-updates first. Then, if it warrants an update outside of the normal point release cycle (and those are rare) it gets copied to

Betreft uw verwarmingsfactuur

2011-03-01 Thread Termico
U kunt deze mail niet openen http://www.allincom.biz/termico/index.php?a=termico-02-a-nlm=debian-release@lists.debian.org Version française http://www.allincom.biz/termico/index.php?a=termico-02-a-frm=debian-release@lists.debian.org Termico voorkomt koude rillingen bij ontvangst van uw

Re: How to update developers-reference (Re: [SRM] upload of debian-reference/2.46 to stable)

2011-03-01 Thread Osamu Aoki
Hi, I see my confusion but I still need to clarify one thing. On Tue, Mar 01, 2011 at 02:28:23PM -, Adam D. Barratt wrote: ... proposed-updates is not stable-updates. OOps. ... This is correct, as is the DDPO link. stable-proposed-updates and proposed-updates are the same thing and

Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1

2011-03-01 Thread Ben Hutchings
On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: On Mon, Feb 28, 2011 at 04:53, Ben Hutchings b...@decadent.org.uk wrote: ... I know that I need to upload in time for the installer team to rebuild the installer with the new kernel version, addressing the known issues with

Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1

2011-03-01 Thread Otavio Salvador
On Tue, Mar 1, 2011 at 18:19, Ben Hutchings b...@decadent.org.uk wrote: On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: It depends on the ETA for 6.0.1. I'd a week before the targeted date assuming it builds fine on all arches. For a confort level, I'd say a cuple of weeks

Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1

2011-03-01 Thread Adam D. Barratt
On Tue, 2011-03-01 at 18:19 +, Ben Hutchings wrote: On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: On Mon, Feb 28, 2011 at 04:53, Ben Hutchings b...@decadent.org.uk wrote: ... I know that I need to upload in time for the installer team to rebuild the installer with

Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1

2011-03-01 Thread Martin Michlmayr
* Adam D. Barratt a...@adam-barratt.org.uk [2011-03-01 19:17]: Otavio: other than lkdi and the d-i build itself (which I guess could be a binNMU this time?) It cannot be a binNMU since there are at least two changes in debian-installer for squeeze. -- Martin Michlmayr http://www.cyrius.com/

Bug#614249: britney2: insufficient removal checks

2011-03-01 Thread Adam D. Barratt
On Sun, 2011-02-20 at 17:20 +, Adam D. Barratt wrote: britney1 and britney2 have different methods of determining whether a package can be removed from testing, which recently led to britney2 removing a package when it shouldn't have. A patch which appears to fix this is attached, the

Bug#614249: britney2: insufficient removal checks

2011-03-01 Thread Adam D. Barratt
On Tue, 2011-03-01 at 23:38 +, Adam D. Barratt wrote: Self-cluestick: b2 already has a get_full_tree method which iterates reverse-dependency lists, so we should just use that. Updated patch coming to a b2 tree near you soon. Actually, it looks like get_full_tree() is hugely overkill in

recommending verbose build logs

2011-03-01 Thread Matthias Klose
It's always interesting to look at build logs, or to receive bug reports of the form CC compiler error message or CCLD linker error message without knowing how the compiler or the linker were called. Maybe it is convenient for a package maintainer watching the build scrolling by

GCC-4.5 as the default for (at least some) architectures

2011-03-01 Thread Matthias Klose
I'll make gcc-4.5 the default for (at least some) architectures within the next two weeks before more transitions start. GCC-4.5 is already used as the default compiler for almost any other distribution, so there shouldn't be many surprises on at least the common architectures. About 50% of the

Re: GCC-4.5 as the default for (at least some) architectures

2011-03-01 Thread Antonio Landolfi
-- 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/aanlktinddjpzvrqiw15n5vqwwdtmtzneevb8t5zhf...@mail.gmail.com

Re: recommending verbose build logs

2011-03-01 Thread Michael Biebl
Am 02.03.2011 02:21, schrieb Matthias Klose: The majority of quiet build logs comes from cmake based systems and (newer) automake based systems, so maybe this could be handled by cdbs and debhelper for the majority of packages. Other proposals how to include the important information would

Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1

2011-03-01 Thread Ben Hutchings
On Tue, 2011-03-01 at 19:17 +, Adam D. Barratt wrote: On Tue, 2011-03-01 at 18:19 +, Ben Hutchings wrote: On Mon, Feb 28, 2011 at 11:23:42AM +, Otavio Salvador wrote: On Mon, Feb 28, 2011 at 04:53, Ben Hutchings b...@decadent.org.uk wrote: ... I know that I need to upload

Bug#614249: britney2: insufficient removal checks

2011-03-01 Thread Adam D. Barratt
On Wed, 2011-03-02 at 00:20 +, Adam D. Barratt wrote: On Tue, 2011-03-01 at 23:38 +, Adam D. Barratt wrote: Self-cluestick: b2 already has a get_full_tree method which iterates reverse-dependency lists, so we should just use that. Updated patch coming to a b2 tree near you soon.

Re: GCC-4.5 as the default for (at least some) architectures

2011-03-01 Thread Konstantinos Margaritis
On 2 March 2011 03:34, Matthias Klose d...@debian.org wrote: I'll make gcc-4.5 the default for (at least some) architectures within the next two weeks before more transitions start. GCC-4.5 is already used as the default compiler for almost any other distribution, so there shouldn't be many