Subject: okay, who reset the not-for-us list?
Date: Monday 18th February 2013 20:15:06 UTC (over 4 years ago)
I saw: Subject: Log for attempted build of gcc-snapshot_20130209-1 on m68k (dist=unstable) I thought: must investigate later. Now I see: Subject: Log for attempted build of qt4-x11_4:4.8.2+dfsg-11 on m68k (dist=unstable) I think, what the fuck? Let’s have a look, I’ve got an idea… [email protected]:~$ wanna-build -A m68k -d unstable --list=not-for-us Total 0 package(s) Okay please out, who was it? I’ve put a dozen or so packages in there with reason. I wrote on this list that I was monitoring these packages as well, so Debian changes that make them viable for us will not be lost. So, why is that list empty now? This is not making any fun. bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (257 (276) bugs: 0 RC, 178 (192) I&N, 79 (84) M&W, 0 (0) F&P) ‣ src:dash (84 (98) bugs: 3 RC, 39 (43) I&N, 42 (52) M&W, 0 F&P) ‣ src:mksh (1 bug: 0 RC, 0 I&N, 1 M&W, 0 F&P) http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit?