Today is again about removing packages from testing as my hintfile says. We've discussed (in the RM team) policy a bit, and it seems that we agree that packages with Release Critical bugs open for more than 3 weeks without any kind of activity from the Maintainer warrant a removal from testing without prior notification. Tonight's work is then just doing the quite not fascinating work of going through this list and look for removal candidates.

Note that we will always give more time to Maintainers that need it to fix a bug, if he/she states so in the bug report. Needing time is perfectly okay. Not telling about it isn't.

Paid work burnt all my free time recenlty, that's why there wasn't a rc-bug-a-day for two days. I'm back with two removals, a couple of gcc-4.3 FTBFSes fixed. And 5 uploads for RG bugs from Sandro Tosi that were rotting in my mail client.

The bad news for tonight is that gcc-4.3 FTBFSes are now RC, since it's the default compiler on several architectures. That's almost 40 new RC we now have to deal with. The fun part will be that those RC will probably hinder some transitions to testing. Maintainers, please, fix your packages. There are still too many packages with RG bugs on them, open for many days, from maintainer that are otherwise quite active on IRC or the lists…

Today's RC bug was 470462, removal of a package that as a patch for a FTBFS and absolutely no maintainer answers (#417047).

I'm also quite excited because I have a mail with 9 nmudiff's for RG/RC bugs waiting to be processed from Sandro Tosi. I want MOAR !

There was no RC-Bug-A-Day yesterday, so two RC bugs for today:

• #463094 some missing ${subst:Stuff} in a debian/control;
• #456864 some other missing Build-Dependency causing a FTBFS.

I also plan to sponsor the requests piling in my @debian.org mailbox tonight too.

For today, a debian/copyright bug in tct was fixed.

Today's paid work ate all my time, so my RC/RG bug squashing was only made of uploading other's work.

Thanks again to Kartik and Kumar.

Today saw the removal (from testing) of:

• syslog-ng that has a really grave bug (loss of logs when the daemon is signaled with a SIGHUP) that is fixed-upstream for quite a while;
• w3c-libwww that the maintainer would like to get rid of, that had two RC. Sadly, I had to remove wmweather+ (its sole r-dep in lenny) that the maintainer still hasn't fixed, but it should be temporary.

All in all, that's 5 RC bugs that aren't in lenny anymore.

Note: I've been pretty busy today, I've seen mails to ask NMU sponsoring for RC/RG bugs, I will have a look, don't worry.

For today, 464893 was downgraded partly because gksu works fine for me for a long time, hence critical was completely overestimated, and partly because no matter how hard I try to reproduce the bug I can't. If you do, please follow up on the bug log.

Also, a new sponsored NMU for gnomesword (bug#461959), thanks to Kumar again :)

Today's work:

• I sponsored one more NMU from Kumar Appaiah for 454829.
• I also closed 458659 that wasn't reproducible, hence probably fixed in 5.7012-4 or 5.7012-5.

The interface was subtly broken for quite some time, because of a broken w-b synchronization script. It's fixed again, so those who stopped using it because it lagged for months can use it again, and know that I'm the one to prod if it's broken.

Also, a nice unknown feature is that if you want the state of $package in experimental, the following alias DWYM^[1]:

 http://experimental.debian.net/$package

While working on an stlport4.6 still not done ldbl128 transition (430305) I got bitten by 434691.

Of course, as stlport4.6 is a dead beast, only used by Debian's OOo (upstream uses an internal 4.5 tree), no patch exists yet. And Ubuntu didn't noticed the breakage yet either. So I'm with this on my hands:

g++-4.1 builds fine:

 artemis# g++-4.1 -fdiagnostics-show-option -pthread -fexceptions -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -frtti -O2 -fPIC complex.cpp -c -o ../lib/obj/GCC/ReleaseD/complex.o

g++-4.2 and g++-4.3 don't:

 artemis# g++-4.2 -pthread -fexceptions -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -frtti -O2 -fPIC complex.cpp -c -o ../lib/obj/GCC/ReleaseD/complex.o
 complex.cpp:27: error: 'float _STL::abs(const _STL::complex<float>&)' is not declared in '_STL'
 complex.cpp:32: error: 'double _STL::abs(const _STL::complex<double>&)' is not declared in '_STL'
 complex.cpp:39: error: 'long double _STL::abs(const _STL::complex<long double>&)' is not declared in '_STL'

 artemis# g++-4.3 -pthread -fexceptions -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -frtti -O2 -fPIC complex.cpp -c -o ../lib/obj/GCC/ReleaseD/complex.o 
 complex.cpp:27: error: 'float _STL::abs(const _STL::complex<float>&)' is not declared in '_STL'
 complex.cpp:32: error: 'double _STL::abs(const _STL::complex<double>&)' is not declared in '_STL'
 complex.cpp:39: error: 'long double _STL::abs(const _STL::complex<long double>&)' is not declared in '_STL'

Help for this particular problem would be much appreciated, because I see absolutely nothing wrong in that code (with my limited C++ skills I shall say).

EDIT: seems like I found the issue with a lot of luck, some using .... crack was causing the issue. So all in all, I fixed two RC bugs today even if I have to delay the NMU because of OOo-related transitions for a while.

I stupidly fell asleep last night, so there was no Day 6 yesterday.

Today, I sponsored 2 NMUs prepared by Sylvestre Ledru for two g++-4.3 FTBFS. If you're not a DD and that you have NMU ready for bugs like the g++-4.3 FTBFSes, I'll gladly sponsor them. I'll just need that you put the dsc files (with the corresponding diff.gz and also orig.tar.gz) available e.g. on Debian mentors.

#462702 and #471057 are gone.