/srv/irclogs.ubuntu.com/2013/12/03/#ubuntu-release.txt

=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== charles_ is now known as charles
=== shadeslayer_ is now known as shadeslayer
shadeslayerhi, I was wondering, libkdcraw, marble and kdegraphics-thumbnailers are all valid candidates for moving, yet they haven't migrated over the last 3 days from -proposed14:03
shadeslayerany clue why?14:03
cjwatson"valid candidate" is only the first stage.  you have to look at update_output for the second14:04
cjwatsonhttps://wiki.ubuntu.com/ProposedMigration14:04
shadeslayerah14:05
cjwatsonin this case: libkdcraw/kdegraphics-thumbnailers leaves calligra, digikam, digikam-dbg, kipi-plugins, kphotoalbum, krita, kubuntu-full, showfoto uninstallable14:05
cjwatsonmarble/kdeplasma-addons leaves calligra-reports-map-element, digikam, digikam-dbg, kexi-map-form-widget, libkgeomap-dev, libkgeomap1, showfoto uninstallable14:05
cjwatsonunhandled soname changes?14:05
=== plars-away is now known as plars
cjwatsonlibkdcraw22 -> libkdcraw23 and libmarblewidget16 -> libmarblewidget17, so looks like it14:06
cjwatsoncalligra's still building14:07
cjwatsonat least digikam definitely needs a rebuild14:08
cjwatsonand kphotoalbum14:09
shadeslayerI see14:09
shadeslayermakes sense14:09
* shadeslayer can finally sort of understand update_output.txt \o/14:09
shadeslayercjwatson: question , what does 85 and 125 mean in : skipped: libkdcraw (85 <- 125)14:16
cjwatsonthey're done/remaining counters in the list of packages currently being iterated over14:17
shadeslayerah okay14:17
cjwatsonbut anyway, you don't want that bit - for packages involved in a transition, look for the first match following the "SUCCESS" line (which indicates the end of attempts to migrate sources one at a time, and the start of attempts to migrate groups)14:18
seb128I wonder if there are extra infos that could be put inline in that file to make easier to read/understand it14:19
cjwatsonI'd rather put a frontend on it the way packages.qa.debian.org does14:19
shadeslayer^^14:19
cjwatsonhttp://release.debian.org/migration/testing.pl etc.14:20
* seb128 basically does "look at the bottom of the page, for the source you are interested in, and try to install the packages listed on the arch lists"14:21
cjwatsonand if we avoid mucking about with the format of the raw file, it will make it easier to put that kind of frontend on top14:21
cjwatsonwhich is why I'm reluctant to touch it much14:21
seb128yeah, I'm not sure what makes it difficult to read/what would improve though :/14:21
shadeslayerseb128: well, it's just that you need to know how to read it :)14:22
shadeslayerif you look at it without knowing how to read it, then it doesn't make much sense14:22
seb128well, I sort of know how to find the info I want/need usually, but sometime I still manage to get it wrong14:23
seb128e.g when we had several transitions involved recently (e-d-s samba openchange) I managed to get really confused until Laney helped me14:23
xnoxyeah, when there are multiple transitions, it seems to try all possible intersections of those, which means one needs to read the "middle one" where all transitions are tried together.14:35
cjwatsonxnox: IME the most complete one is usually at the top14:40
cjwatsonwell, below the initial block ending in "SUCCESS"14:40
shadeslayercjwatson: does valgrind need fixing wrt arm64?14:51
shadeslayerdoesn't seem to be built for arm6414:51
cjwatsonDon't know, you'll need to give me some context14:51
shadeslayerhttps://launchpad.net/ubuntu/+source/valgrind/1:3.8.1-5ubuntu114:52
cjwatsonOh, presumably it needs to be ported14:52
shadeslayer^^ no arm64 causes https://launchpad.net/ubuntu/+source/digikam/4:3.5.0-0ubuntu3/+build/529698214:52
cjwatsondigikam should only try to use valgrind on arches where it's available14:52
shadeslayerack14:52
cjwatsonit's never been "works on every architecture" kind of software14:52
cjwatsoncompare https://bugs.launchpad.net/linaro-aarch64/+bug/123674814:53
ubot2Launchpad bug 1236748 in Linaro AArch64 cross-distro work "valgrind needs Aarch64 port" [Undecided,Triaged]14:53
cjwatsonhttps://bugzilla.redhat.com/show_bug.cgi?id=926688 suggests "several months of work"14:54
ubot2bugzilla.redhat.com bug 926688 in valgrind "valgrind: Does not support aarch64 in f19 and rawhide" [Unspecified,Closed: cantfix]14:54
shadeslayeryeah, 95K lines of ARM specific code14:54
* shadeslayer adds !arm64 to Build-Depends14:55
cjwatsonProbably the wrong answer14:55
shadeslayerhm?14:55
cjwatsonvalgrind has "Architecture: amd64 armel armhf i386 mips mipsel powerpc ppc64 s390x x32" - better to match that than to invent an inaccurate negative version14:56
cjwatsonthat'd just need to be updated for the next port14:56
shadeslayer*nod*14:57
cjwatsoncould somebody in ~ubuntu-sru please review partman-basicfilesystems/precise?  apw eyeballed it a few days ago15:20
stgrabercjwatson: doing so now15:21
arahello! could anyone in ~ubuntu-sru review https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=gnome-control-center, please?15:22
shadeslayerlikewise for kscreen as well ^^ , it has a MRE15:22
cjwatsonthanks.  I'd nag about grub2/precise as well but I'm currently waiting for upstream to reappear on IRC so I can jump on him about whether the latest iteration of the hotkey patch is ok15:22
cjwatsonI'll take gnome-control-center15:23
aracjwatson, thanks15:23
cjwatsonshadeslayer: saucy, presumably - libkscreen too?15:27
cjwatsonara: done15:27
shadeslayercjwatson: yep15:27
aracjwatson, thanks!15:27
cjwatsonstgraber: thanks15:31
shadeslayercjwatson: thx16:36
cjwatsonxnox: could you do another ubiquity/precise upload with the new partman-basicfilesystems in precise-proposed?17:28
cjwatsonshould be less busted now17:28
xnoxcjwatson: ack.18:01
=== barry` is now known as barry_
=== barry_ is now known as barry

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