[09:46] doko_: I filed a MIR for libfile-mimeinfo-perl, I think we should keep it === bjf[afk] is now known as bjf [15:51] * jdstrand starts perusing https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency === doko_ is now known as doko [16:37] cjwatson: hi. I'm looking at http://people.canonical.com/~ubuntu-archive/testing/ and am wondering what are producing those reports. I've looked in the ubuntu-archive-tools and bin on lillypilly (grepping for 'probs'), but don't see it. I'm not in group ubuntu-archive on lillypilly, so can't see the cronjob [16:38] cjwatson: more to the point, I am trying to figure out how to use all the reports to fix stuff (and though looking at the scripts would help) [16:40] * jdstrand notices https://wiki.ubuntu.com/ArchiveAdministration#Useful%20web%20pages [16:41] ~lp_archive/testing/ [16:41] cjwatson: nm, I think I can figure it out based on that page [16:42] (on cocoplum) [16:42] ah [16:42] cool [16:42] it doesn't give you a lot of drill-down information; IME it's best to set up a chdist configuration for the arch in question and then use 'chdist apt-get natty-armel install ' (then Ctrl-C) to see what the problem is [16:43] you may not be able to get it to zero, there are a few long-term problems there like usb-creator [16:43] cjwatson: are these things that you would typically fix yourself, do you poke people, file bugs, or some combination? [16:45] combination [16:46] with my archive admin hat on, I mostly look for ones that are due to archive inconsistencies (stale builds, things stuck in NEW, wrong components, etc.) [16:47] ok [17:40] cjwatson: is it safe to say that http://people.canonical.com/~ubuntu-archive/testing/* are things in main and restricted and not universe and multiverse? [17:51] jdstrand: yes === bjf is now known as bjf[afk] === bjf[afk] is now known as bjf [19:26] fyi, talked to the desktop team about vala 0.10 and they are going to have a meeting about it within the next few days. sounds like it will be resolved before alpha 2 [19:27] (vala 0.10 is nbs, but several things need to be ported to use 0.12) [20:03] cjwatson: so if a no change rebuild FTBFS, I'm thinking if the fix is obvious fix it, otherwise file a bug? [20:04] cjwatson: this happened on some universe packages in an effort to clear out the rdepends for some NBS [20:05] jdstrand, seems reasonable, not sure you need to file a bug or if things just get picked from regular archive rebuild tests [20:06] sounds reasonable [20:07] ok. I just was thinking I didn't want to spend all kinds of time on it, and it sounds like I should not [20:07] seb128, cjwatson: thanks [20:08] jdstrand, you should perhaps not bother with universe builds so early in the cycle [20:08] not sure if you try to clean nbs there? but starting with the CD ones seems reasonable [20:08] right - this is "archive admin on point for alpha-2 prep", so things on CDs should take priority [20:09] seb128: right-- I was doing the CD ones, and then there were just a couple of universe, so I said 'why not?' [20:09] I think I answered my question :) [20:09] ;-) [20:09] (all pertaining to evolution-data-server) [20:10] jdstrand, what about? libgdata7 rdepends? [20:10] seb128: well, I hadn't gotten to that yet. I was talking about libebook, etc [20:10] it's a control bug which still list it, it seems, cyphermox said he would check [20:10] k [20:21] do we make dvd isos for all milestones? [20:24] can I ask someone to pretty please accept haskell-utf8-string binaries? They were in the archive before (lucid) [20:28] jdstrand: if it's possible (it isn't always) === bjf is now known as bjf[afk]