* RAOF continues to not be an archive admin.02:02
* RAOF continues to need to resolve that situation.02:02
mwhudsonyes please, an AA in my timezone (ish) would be useful at times :-)03:08
Mirvthanks doko. yes still some problem somewhere..05:27
MirvRAOF: right, sounds familiar to me from some months ago..05:30
Mirvseb128: morning! if you're about, please try if you can find some time to get this Qt & KDE transition through.. we're now down to very small selection of update_output.txt I think06:20
Mirvnot counting eg amd64 list that lists some kde language packs, the update_output.txt claims for example i386: camitk-actionstatemachine, camitk-imp, itksnap, jacktrip, kde-spectacle, kubuntu-desktop, kubuntu-full, libcamitk4, libcamitk4-dev, lubuntu-qt-desktop, lxqt-config, nifti2dicom, nifti2dicom-dbg, nomacs, plasma-discover, qnifti2dicom, reminders-app06:21
Mirvit's starting to be really hard for me to see any problems with those, but for reminders-app I believe it should be removed as I asked in bug #1606531 - it's the only package still depending on transitional package qtdeclarative5-quicklayouts-plugin removed in yakkety-proposed06:23
ubot5bug 1606531 in reminders-app (Ubuntu) "RM: transitional QML module packages" [Undecided,New] https://launchpad.net/bugs/160653106:23
Mirvothers have picked up Qt 5.6 dependency during build time so they'd need to migrate too, but I don't see any problems with them06:23
Mirvlxqt-config needed rebuild to transition to libkf5screen7 from libkf5screen606:39
Mirvlubuntu-desktop refuses to install because of some (weird?) problem in installing usb-modeswitch, but I can't see why lubuntu-desktop itself would be required to migrate at the same time06:39
Mirvmaybe that's noise in update_output, I've never been good in parsing that file06:40
Mirvbut reminders-app (source and binaries) needs to be removed from yakkety, so please do that06:40
Mirvwe'd definitely need a more eastern archive admin..07:11
UkikieMirv: Howdy.07:18
MirvUkikie: oh hi!07:19
Mirvok, so Lubuntu and Kubuntu seeds need to be updated to not depend on obsolete packages07:52
Mirvmeanwhile, archive admins still please remove reminders-app from yakkety07:52
sil2100We still had that in the archives?07:54
Mirvsil2100: yes, I've asked for its removal at bug #160653107:59
ubot5bug 1606531 in reminders-app (Ubuntu) "RM: transitional QML module packages" [Undecided,New] https://launchpad.net/bugs/160653107:59
MirvI have updated Kubuntu and Lubuntu meta packages and plasma-discover's erronous transitional packages.08:18
MirvI'm still worried about the remaining packages in update_output.txt and would welcome help in understanding the list and if any of it is serious or not08:19
cjwatsonLocutusOfBorg: Thanks for dealing with Haskell.09:28
LocutusOfBorgcjwatson, please wait for it to finish before thanking me ;)09:28
cjwatsonLocutusOfBorg: Are you working in order on http://people.canonical.com/~ubuntu-archive/transitions/ghc.html ?  Some surprisingly high-up red there.09:29
cjwatsonLocutusOfBorg: Oh, it normally takes a week or so, I wasn't rushing you :)09:29
LocutusOfBorgactually I took a different approach09:29
LocutusOfBorgsee in update_excuses what was uninstallable09:29
LocutusOfBorgand rebuild them09:30
cjwatsonI find that inordinately hard on my brain.09:30
LocutusOfBorgnow, I'm sorting the unbuildable packages and retrying them in the right order09:30
cjwatsonThe transition tracker is a much easier format.09:30
LocutusOfBorgyes, I know thanks, but I prefer to see logs, and understand them this time09:30
LocutusOfBorgnext time for sure I'll see the tracker and trust it ;)09:30
LocutusOfBorgthe main goal is to understand things now09:31
cjwatsonIt is true that there are a couple of things on the tracker that you have to know to ignore.09:31
cjwatsonagda* on some architectures and xcffib (due to lack of versioned-provides support in that ben instance) IIRC.09:32
LocutusOfBorgactually I could build-and-retry-build until stuff is sorted out I guess09:33
LocutusOfBorgeach time waiting for dinstall09:33
LocutusOfBorgbut I prefer the slow "check-each-package" method09:33
LocutusOfBorgBTW the graphic might have one single big "retry all builds" button instead of clicking on each architecture09:34
cjwatsonI just use ubuntu-build for that.09:34
LocutusOfBorgand also one "no change rebuild and upload" :)09:34
cjwatsonAnd a script for that :)09:34
LocutusOfBorgyep me too09:34
cjwatsonLocutusOfBorg: The problem with not going in order by layers is that you can end up duplicating builds if something in a higher layer fails on some architectures.09:34
LocutusOfBorgbut it might unify the "rebuild messages"09:34
cjwatsonI don't care about that.09:35
cjwatsonLocutusOfBorg: e.g. there's a lot of noise from haskell-vector failing to build on a few arches, which needs to be sorted out before rebuilding anything that b-ds on it09:35
cjwatsonExciting that it manages to run out of memory on the big arches.09:36
Mirvcjwatson: can you remove src:reminders-app and its binaries from yakkety?09:36
cjwatsonsorry, I know you're looking around desperately for an AA but I think that's more phone context than I have time to import into my brain at the moment ...09:37
cjwatsonwell, maybe this one is simple, moment09:37
Mirvcjwatson: it is simple, no reverse depends and has lived only in click space since 201409:38
Mirvhas an old transitional dependency being dropped, so it would be time to get rid of it for good09:39
cjwatsonMirv: ok, done that one but I'm not going to look at the rest of that bug at the moment09:39
Mirvcjwatson: no problem, none of that other is urgent09:40
Mirvand sorry for sounding desperate, it's just because I am :)09:41
Mirvbut making progress too09:41
cjwatsonLocutusOfBorg: you probably want to chase up haskell-vector with #debian-haskell if you haven't already; the discrepancy in which arches it manages to succeed on between Debian and Ubuntu is odd, but maybe it needs to be just a whitelist of arches with good enough compiler support or something instead09:41
LocutusOfBorgactually I'm retrying them09:43
LocutusOfBorglets see how they go09:43
cjwatsonI doubt that will make any difference, but ICBW.09:43
LocutusOfBorgmoved to #-haskell09:48
=== mcasadevall is now known as NCommander
=== kip_ is now known as kip_brb
Mirvwhen some archive admin reads the whole today's backlog, I'd like to add I don't know if there's any fix for fulfilling camitk's powerpc dependency which fails to build in proposed due to something not related to these landings: https://launchpad.net/ubuntu/+source/camitk/4.0.0~beta-2build1 -> https://launchpad.net/ubuntu/+source/insighttoolkit4/4.10.0-dfsg1-2ubuntu110:38
Mirvso I'd like to ask considering any measures needed for getting the transition done regardless10:39
LocutusOfBorgcamitk is not a blocker for the transition I guess10:40
LocutusOfBorgMirv, do you have another opinion? AFAIR I did the rebuilds correctly, and they wre stuck because of qt transition10:40
LocutusOfBorgno need to retry itk410:41
MirvLocutusOfBorg: well they show up in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt , and I noticed it built in release pocket but not in proposed, so it would block10:41
* Mirv needs to go for 45mins now10:41
MirvLocutusOfBorg: but yes I think the release pocket camitk should work fine and I have it installed on my yakkety-proposed, I'm just wondering about the update_output.txt10:42
Mirvso maybe that's noise10:42
LocutusOfBorgthey show up there, because the qt is not over10:42
LocutusOfBorgfor sure you don't need to remove powerpc, since it is already removed, neither retry itk4 there10:44
LocutusOfBorga no change rebuild against qt for every arch might be needed, but please talk to qt folks10:44
LocutusOfBorgI can say, from *my* itk4 side, everything should be good and in place10:45
MirvLocutusOfBorg: there's no qt folks but me10:46
LocutusOfBorgoh... ok :)10:46
MirvLocutusOfBorg: ok, I'll try to fix everything else and see if that keeps visible in the output.txt or not in the easy autohinter section10:46
LocutusOfBorgthanks, but AFAIK you might need a  no-change rebuild for it and itksnap10:47
LocutusOfBorgand nifti2dicom10:47
LocutusOfBorg(I didn't try the above, I don't know how you uploaded the transition and which packages needs rebuilds)10:48
=== kip_brb is now known as kip_
Mirvwhy is btw publisher runs taking >1h nowadays at times? and almost never the 15-20mins it used to be11:41
LaneyMirv: looks like there are quite some issues remaining12:00
=== maclin1 is now known as maclin
acheronukMirv: a package for frameworks backport took 3hrs to publish on LP yesterday. despite people saying it's fine, it's clear there is some big issue with the publisher12:04
MirvLaney: yep, help would be welcome fixing those. many are being fixed, but there is for example /usr/bin/ld.gold: --secure-plt: unknown option on powerpc that comes from GCC6, and I don't know how to even workaround that https://launchpadlibrarian.net/277744096/buildlog_ubuntu-yakkety-powerpc.ubuntu-ui-toolkit_1.3.2030+16.10.20160726.4_BUILDING.txt.gz12:06
Mirvacheronuk: ack.12:07
MirvLaney: and I don't know what would be actually wrong with many of the packages that LocutusOfBorg mentioned, I'm trying a no-change rebuild now even though I can't find anything wrong with the packages and I have them installed on my yakkety-proposed12:07
Mirvacheronuk: I think it's been getting worse and worse, but there has been some amount of issues for weeks12:09
LaneyMirv: camitk is the new insighttoolkit4 no?12:10
LaneyMirv: And the previous one didn't build on powerpc/ppc64el either, so that shouldn't matter12:11
LocutusOfBorgmy transition is fine12:11
acheronukMirv: definitely. that was just an extreme example yesterday, but indeed it's been frequently > 1hr for many weeks now and even perhaps degrading more12:12
LocutusOfBorgat least AFAICT12:12
LaneyLocutusOfBorg: Which one?12:12
LocutusOfBorginsighttoolkit4 rebuilds12:12
MirvLaney: it build depneds on libinsighttoolkit4. so yes I think those shouldn't matter, but can you explain why they are shown in the update_output.txt among with packages that actually have installibility problems? in the Trying easy from autohinter section.12:12
MirvLocutusOfBorg: for better or no change, now the rebuilds (I did in a silo) are copied over.12:13
LaneyI think this ffmpeg is going to clear out some of them (libwebp5 -> 6)12:14
Mirvok, and we're getting the kde langpack updates right now too. but that leaves that one powerpc problem preventing ubuntu-ui-toolkit rebuild to fix a s390x problem that would prevent the whole promotion, at minimum12:14
Mirv..unless you could force ubuntu-ui-toolkit-autopilot/s390x uninstallability (coming from the upstart problem and newest removals for s390x for it) to get this inch forward before world breaks again12:15
cjwatsonacheronuk: What package name?12:16
Mirvcjwatson: for example https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-073/+sourcepub/6786564/+listing-archive-extra12:16
Mirvthat's probably 1.5h by now12:16
Mirvsince build finished12:16
cjwatsonI want specifically acheronuk's example from yesterday.12:16
cjwatsonAnyway, the thing is normally that it isn't anything very specific, it's death by a thousand cuts.12:17
acheronukcjwatson:  kxmlgui in https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks I think?12:20
acheronukmaybe LP rounds to hrs after a point, but it did clearly say when still unpublished "Finished 3 hours ago (took 3 minutes, 48.5 seconds)"12:22
cjwatsonThe >1hr run just recently seems to have been mostly due to some very large libreoffice publications which took a long time to shift around internally.12:22
acheronukseems quite consistently closer to the 1hr than the old 20 (ish) mins nowadays. i.e. when it publishes in the 20 mins or so it used to, it's a surprise, rather than the norm12:26
cjwatsonThe Kubuntu PPAs are some of our largest, so you're going to see a somewhat skewed view.12:28
cjwatsonLooking for the kxmlgui case.12:29
acheronukcjwatson: yes, I know is a perception thing as well12:29
cjwatsonacheronuk: As I suspected, the kxmlgui case is an anomaly.  There's a weekly window where we do more time-consuming cleanup and when the normal publisher doesn't run, and you happened to run into that.12:31
cjwatsonStarts at 0559 on Sundays and normally takes a few hours.12:31
cjwatsonUnrelated to Mirv's question.12:32
acheronukcjwatson: understood, and I except things like can/do happen. just that on top of the quite clear degrading of the times over the last few weeks/months made that one stand out!12:32
cjwatsonAnyway, as far as I can tell there are no easy fixes.  We do have a plan to restructure things so that we can scale much better, but it is quite a large piece of work so no timescale yet.12:33
cjwatsonThat's "diskless PPAs", so we'd start serving files out of the cloud and wouldn't have to rely so much on shifting lots of files onto a single giant system.12:34
acheronukcjwatson: again, understood. sometimes there is a simple cause and a simple fix. sometimes, like this as it sounds, it's not that easy.12:35
acheronukit's just a tad frustrating when trying to build anything together with a complicated/long dependency tree12:37
cjwatsonThis is a case of suffering from our own success.12:37
cjwatsonAnd I don't mind looking into it because sometimes there is an obvious cause.12:37
cjwatsonI would love to get time for diskless PPAs.  With any luck it will be months not years ...12:38
ogra_can someone bump the score on https://code.launchpad.net/~ogra/+snap/kernel-test-snap/+build/2573 ? it tells me it will start in 20min since about 3h now ... (and i'm having the same issue with all arm builds since friday)12:55
cjwatsonogra_: done13:07
ogra_thanks ... is there an archive rebuild going on ?13:07
ogra_(since this happens since friday already)13:08
ogra_(also for arm64)13:08
cjwatsonarm64 and armhf are the same builder pool.13:08
cjwatsonMaybe we need to make another attempt to get approval for more Moonshot hardware now that we're actually using it.13:11
ogra_well, something changed since friday, before my arm builds were rather fast13:17
ogra_ARGH ... and i forgot to bzr push before triggering the build ... sigh13:17
cjwatsonogra_: Just looks like more builds happening really.13:21
ogra_hmm, k13:22
ogra_cjwatson, could you bump https://code.launchpad.net/~ogra/+snap/kernel-test-snap/+build/2575 too ? sorry, the firt one was actually wasted13:22
cjwatsonSee, now you're not stuck in traffic, you *are* traffic ;-)13:23
LocutusOfBorgcjwatson, do you happen to know what is going on there? https://launchpad.net/ubuntu/+source/haskell-http-link-header/1.0.1-1build3/+build/1056947713:28
cjwatsonLocutusOfBorg: Nope.13:29
cjwatsonLocutusOfBorg: You could try cancelling it and seeing if it works on a different builder; sagari has somewhat different hardware from the others.13:29
LocutusOfBorgthat was my wondering.13:30
LocutusOfBorgrescheduling, but I can't force a particular builder13:30
cjwatsonNo, but you have an 8/9 chance13:30
LocutusOfBorgfair enough :p thanks13:31
cjwatson(I can force it if I have to, but it's cumbersome so I'd rather not bother)13:31
LocutusOfBorgnah, it is fine13:32
Mirvcan someone figure out why usb-modeswitch refuses to install on yakkety-proposed? it's a real mystery to me.13:36
Mirvoh, ok, the -data has Breaks on usb-modeswitch << 2.4.013:37
Mirvso that breaks installing lubuntu-qt-desktop, shown also in update_output.txt but should be noise since it's not related to Qt and KDE upgrading13:38
Mirvdoes anyone know, that if update_output.txt does list eg lubuntu-qt-desktop there as being uninstallable, will it need manual intervention from archive admin via hints if I'd like Qt & KDE to migrate?13:39
Mirvoh, but, new lubntu-qt-desktop is required so that its erronous dependencies on obsolete KDE packages would be dropped :(13:40
Mirvcyphermox: would it be a really quick job for you to update usb-modeswitch in Ubuntu, ie sync with Debian, so that ^ blocker for Qt and KDE transition would be gone?13:40
Mirvit starts to seems I need to fix all of proposed for all packages before this is going to work :(13:41
cyphermoxmost definitely not a quick job right now13:41
Mirvhmm, I wonder if I could revert usb-modeswitch-data then13:41
cyphermoxand I really don't understand why it's a blocker for anything, it really shouldn't be, especially not Qt/KDE stuff13:41
Mirvcyphermox: because lubuntu-qt-desktop depends on installability of usb-modeswitch, and lubuntu-qt-desktop needs to be updated to drop KDE dependencies that are broken13:42
Mirvso if lubuntu-qt-desktop cannot be installed, update_output.txt claims it's Qt's / KDE's fault13:42
Mirvalso lubuntu-qt-desktop could temporarily lose its usb-modeswitch dep, that'd be another workaround13:43
MirvI'll just go and do something if no-one wants to help13:43
xnoxplease remove dbus-cpp... should be for yakkety13:47
cyphermoxMirv: I would suggest you revert -data, it's the best thing to do13:48
LaneyIs it intentional that component-mismatches wants to promote the first alternative of an or-ed dependency group if one of the others is in main already?13:50
Laneyi.e. should I fix the report or the package?13:50
Mirvcyphermox: ok, thank you13:52
cjwatsonLaney: component-mismatches doesn't care what's already in main; it does a from-scratch analysis with germinate13:53
cjwatsonLaney: making it care about the current component overrides would produce weird hysteresis, I think13:53
cjwatson(and would be difficult anyway ...)13:54
Laneycjwatson: Righto.13:54
Mirvstill not anyone willing to decipher the update_output.txt remaining problems? so I was interested in why in the autohinter section eg camitk / itksnap would be listed, and also if there's any possibility of ignoring s390x installability issue of ubuntu-ui-toolkit-autopilot for one time if it seems the real fix would take another week or so.14:42
Mirvthroughout the day I've been able to progress on my own though in many places, but it may be I'm at the end of the road now14:43
LaneyMirv: I uploaded ffmpeg and some other bits to progress it somewhat (should fix camitk)14:44
MirvLaney: ok, thank you. what was the problem with it?14:45
Laneywebp transition14:45
Mirvoh so probably somewhere from the depths of that libinsighttoolkit14:46
LaneyI forgot the chain, but something in there was depending on libwebp514:46
LaneyNo doubt there are one or two other bits left for that one; didn't check14:47
Mirvanyway, it may be that the UITK s390x issue would be the last one after things settle, but I can't rebuild UITK because of powerpc GCC6 issue, and I can't seem to find a workaround to force it. a real fix would probably be something in qtbase, updating of which would relaunch thousands of autopkgtests and probably find both flaky tests and gcc6 issues, postponing this migration by another week or14:47
Laneywhich hint block are you looking at?14:47
MirvLaney: easy: 260+0: a-56:a-31:a-3114:48
Laneyok, let's see14:48
jbichaif you need webp first, more uploads are needed https://people.canonical.com/~ubuntu-archive/transitions/html/auto-libwebp.html14:49
Laneyjust need a minute to set up the script on snakefruit, since my PC is out of reach14:49
jbichabug 161006614:49
ubot5bug 1610066 in gst-plugins-bad1.0 (Ubuntu) "gst-plugins-bad1.0 ftbfs on yakkety" [High,New] https://launchpad.net/bugs/161006614:49
Mirvnow search for "easy: 245+0: a-47:a-30:a" but actually just search for qtbase in reverse, the last hit is the best looking hint block15:24
MirvI need to rest now.15:24
LaneyMirv: I think the plasma-discover depends on packagekit >= 1.0 is going to cause you trouble15:59
seb128not close to see the end of that transition...16:05
seb128Laney, did you get a reply from the unity8 team about click and yakkety?16:06
LaneyNothing useful16:07
LaneyI'm not happy about this being pushed back again after it was agreed16:07
seb128I don't think any agreement was changed16:09
seb128the phone team is not planning devices on yakkety and is fine getting that to regress16:09
seb128the issue is the new usecase of our (desktop) team wanting unity8 on the default install this cycle now16:10
LaneySo a new requirement is making the previous agreement insufficient16:10
seb128well it's up to us16:11
seb128we can declare that we don't need click16:11
seb128it's just that today we only have click as a working package installer in unity816:11
LaneyWe have to either do it, or undo what's happened in proposed16:11
seb128no gnome-software working nor snaps dash integration16:11
LaneyAssuming this plasma dependency is legitimate, that implies some work there16:12
seb128willcooke, ^ we need to make a call on that16:12
willcookeseb128, on what exactly?  Your "no g-s working.." comment has confused me16:14
seb128willcooke, read the backlog from 16:59 on16:15
willcookeI did, I'm still not sure what you're asking16:15
willcookeis it "do we move to PK 1.0" in 16.10?16:16
seb128willcooke, but summary is that the pkgkit 1.0 transition in yakkety-proposed blocks other things including qt/kde stack16:16
willcookein which case, yes16:16
willcookeyes we move16:16
willcookeend of16:16
willcooketedg is hoping to land support in u8 by EOW16:16
seb128so no way to install packages today under unity8-desktop16:16
seb128which is fine16:16
Laneyif it generates pressure to get the work done faster16:16
seb128dobey said it was some thousand lines of code to review and was probably not going to be that easy16:16
seb128but let's see16:17
Laneyit's the right call for our team imho16:17
* Laney gives Mirv a shoulder massage16:17
seb128Laney, either that, or it creates pressure on our team to fix things that we broke16:17
willcookeattent_e looked at what was needed to get g-s working under u8 too16:17
seb128but yeah, I agree we should do it16:17
seb128just be ready to get some heat for breaking things16:18
willcookebut if ted_g is working on a u8 native option, so much the better16:18
seb128and have to figure a way out16:18
LaneyIt's not as if there hasn't been an interminable amount of warning about this problem16:18
seb128well as said we (desktop) are in charge now of seeding that new session and getting it to work16:18
willcookeLaney, +1 - we've been talking about it from before this cycle even started16:18
seb128so it's selftwarning at this point16:18
seb128but we haven't really been on top of that work (yet)16:19
seb128anyway the session is what it is16:19
seb128then we can start discussing bugs between unity8 team and us16:19
seb128Laney, willcooke, thanks for pushing and acking, I think landing it now is the right thing, we delayed enough16:29
Laneyseb128: merci16:29
seb128the number of transitions/work that still need to land start being a bit concerning but I guess we can sort out after feature freeze starts16:29
wxlinfinity: a member of our lubuntu team has created merge proposals to implement qt-driven images for lubuntu. this is the future of lubuntu, so it would be really great to have. what's the timeline on this? https://code.launchpad.net/~tsimonq2/ubuntu-cdimage/lubuntu-next-image/+merge/301203 https://code.launchpad.net/~tsimonq2/livecd-rootfs/lubuntu-next-image/+merge/30120217:40
=== ochosi_ is now known as ochosi
bdmurraytjaalton: Could you have a look at bug 1610434?20:25
ubot5bug 1610434 in xorg-lts-xenial (Ubuntu) "Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial" [High,Triaged] https://launchpad.net/bugs/161043420:25
doko_we need somebody to track the OpenGLes build failures on arm64 ... and remove the packages which don't build anymore22:30
doko_this is a blocker for transitions, e.g. https://launchpad.net/ubuntu/+source/tulip/4.8.0dfsg-2build422:30

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