On 2016-07-24 14:42, Cyril Brulebois wrote: > Hi, > > Christian Seiler <christian@iwakd.de> (2016-07-23): > > On 07/23/2016 11:05 AM, Emilio Pozuelo Monfort wrote: > > > On 22/07/16 16:50, Christian Seiler wrote: > > >> nmu mksh_52c-2 . ALL . -m "Security: rebuild against newest dietlibc" > > >> nmu mksh_52c-2exp3 . ALL . experimental . -m "Security: rebuild against newest dietlibc" > > >> nmu util-vserver_0.30.216-pre3120-1.1 . ALL . -m "Security: rebuild against newest dietlibc" > > > > > > Scheduled. > > > > These packages have been building on _all_ architectures for a > > very long time now (nearly 2 hours on some), while they typically > > only have a build time of a couple of minutes (depending on the > > architecture). Could you please take a look? I think there's > > something wrong here and buildd resources are being wasted. > > > > (I just rechecked and the source packages of these binNMUs do > > build fine in a clean pbuilder env, so I don't really know what > > the problem could be though.) > > mksh seems installed now, various logs show: > Build needed 00:02:29, 16240k disc space > Build needed 00:02:37, 13340k disc space > Build needed 00:04:14, 17736k disc space > > Those builds started past 20:00 UTC, so I suspect whatever happened at > the time was fixed or so, and mksh built normally afterwards. The binNMU message included some yaml reserved signs, which are not properly escaped by the current code, so the builds actually fail to start after they have been taken to build. I have changed the message around that time yesterday, that's why it built so late. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature