/srv/irclogs.ubuntu.com/2011/06/16/#ubuntu-release.txt

=== maco2 is now known as maco
=== pitti_ is now known as pitti
=== warp10` is now known as warp10
=== doko_ is now known as doko
ogra_cjwatson, hmm, so my arm desktop images all end up around 1G ... and there seem to be no manifest files generated for them12:39
ogra_i thought it was a copying issue, but even sycamore doesnt have them12:40
cjwatsonOK, I'll have a look, thanks12:43
cjwatsonogra_: won't the size largely be due to switching from netbook to desktop?12:59
ogra_well, all other arches are around 700M13:00
ogra_surely we grew by switching to desktop13:00
ogra_the size isnt my issue, the missing manifests are :)13:00
cjwatsonfixed your manifest output13:01
cjwatson(livecd-rootfs 2.6)13:01
ogra_so i can find out what we have extra on arm13:01
ogra_thx !13:01
dokocjwatson: the list of sources with no binaries in the archive: http://paste.ubuntu.com/627926/13:02
dokonot yet right/complete.13:02
cjwatsonah, you missed udebs in your binary list13:02
dokoahh, good point13:02
dokos390-* and sparc-* packages can be sorted out13:03
dokolooking at things like: https://launchpad.net/ubuntu/+source/ubuntu-calendar-march/+publishinghistory  the sources are there, but not more the binaries. any idea why?13:03
dokoI don't understand the *-ruby packages yet13:04
cjwatsonI can't remember how to get at BPPH records in the UI13:07
* cjwatson pokes about in the API13:10
dokoare the apt.sources lines for downloading the debian-installer packages files?13:11
cjwatsonbinaries were removed with 'unmaintained upstream since hoary; if this is ever revived and somebody steps up to do the packaging work, it can be reintroduced'13:14
cjwatsonno obvious reason why the source package wasn't removed; I guess that was an accident13:14
cjwatsonubuntu.main_archive.getPublishedBinaries(binary_name='ubuntu-calendar-march') # and then poke about through the resulting collection of binary_package_publishing_history objects13:15
cjwatsondoko: just use main/debian-installer restricted/debian-installer etc. as components13:17
cjwatsonheh, and I removed the ubuntu-calendar-* binaries back in intrepid apparently, so my bad for missing the sources13:20
cjwatsonI've removed all six remaining ubuntu-calendar-* source packages now13:20
cjwatsonoh, and ubuntu-calendar too13:21
dokopitti:13:25
dokolanguage-pack-gnome-zh13:25
dokolanguage-pack-gnome-zh-base13:25
dokolanguage-pack-kde-zh13:25
dokolanguage-pack-kde-zh-base13:25
dokolanguage-pack-zh13:25
dokolanguage-pack-zh-base13:25
dokosource exists, but no binaries13:25
dokothe ruby packages are a lot of source renames13:28
dokocjwatson: filed https://bugs.launchpad.net/ubuntu/+bug/798195  will do the ftbfs checks later13:47
ubot4Launchpad bug 798195 in ubuntu "source packages in oneiric without binaries (affects: 1) (heat: 8)" [Undecided,New]13:47
pittidoko: oh, these source pkgs should be removed; doing now14:15
dokopitti: could you update the bug report above?14:16
pittiyep, will do14:16
ScottKAren't some of those the ones we removed binaries for during Lucid so we wouldn't have unsupportable binaries in an LTS?15:44
ScottKWhy the push to remove the source now?  My recollection was that we decided keeping the source was harmless.15:44
=== NCommand1r is now known as NCommander
nigelbskaet: And, here's the list I've promised :)17:42
nigelbhttp://paste.ubuntu.com/628055/17:42
skaetnigelb,  Thanks!  do you have the bug numbers associated with them?17:43
nigelbskaet: Not yet. tumbleweed is figuring that out :)17:43
skaetnigelb,  sounds good.  :)17:44
tumbleweedskaet: without being able to programattically link bugs to blueprints, I don't think this is going to be very workable18:03
skaettumbleweed, it feels like it should be scriptable,  just going to be a matter of figuring out the right launchpad API's to let us find and hook them up.18:05
tumbleweedthere are API methods for linking branches, but not bugs (that I can see). Bugs appear to be read only18:06
skaethmm... which version are you looking at?18:06
tumbleweeddevel, 1.0 has almost nothing for blueprints18:06
nigelbWhat are we trying to do, file bugs and then link them to the BP?18:07
skaetnigelb,  yup18:07
tumbleweedfind the bugs already filed18:07
nigelbtumbleweed: finding should be easy.18:07
tumbleweedand then link them :)18:07
nigelbworst case18:08
skaettumbleweed,   searching on the tag ftbfs under the oneiric bugs gives you the first pass.   Then for each of the bugs,  need to determine if the project is against universe18:08
nigelbwe can have it print out the bugs and we can link manually18:08
nigelbtumbleweed: oooh18:08
nigelbtumbleweed: talk to brian please? he has a selinium test thingy account18:08
nigelbtumbleweed: That can do this linking from the web ui.18:09
nigelbtumbleweed: iamfuzz on irc18:09
skaetIf its about 80,  I'll take a share.    If its going to be 780,  then yeah we need to do it programatically.18:09
* skaet heads out to lunch, biab18:09
tumbleweednigelb's list was ~80, which is manageable, yes. If it were more than that I'd say there are easier ways to get progress graphs (the FTBFS page on qa.ubuntuwire has CSV output that would be trivial to store and graph)18:11
nigelbtumbleweed: I wwas actually hoping to use harvest, bug in harvest prevented that.18:11
nigelb(I should file that bug)18:11
micahgnigelb: what's that list for?18:17
* micahg notices chromium18:17
nigelbmicahg: ftbfs, that's because of linking changes18:17
micahgah, ok18:18
nigelbmicahg: is the chromium failure correct in that way?18:18
micahgnigelb: yes, but I think it's fixed now18:19
nigelbwe scraped the list 2 days back18:19
micahgoh, wait, arm is still broke I think18:19
ogra_yes, hrm is working on an arm fix atm18:20
ogra_in a very heroic attempt :)18:20
ogra_err18:20
ogra_s/hgrm/hrw/18:21
ogra_heh18:21
micahgnigelb: I think gcc-4.6 + chromium on i386 is fixed in trunk ATM, will check18:21
nigelbogra_: heh, interesting spell-error ;)18:21
=== ArneGoet1e is now known as ArneGoetje
=== yofel_ is now known as yofel

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!