[01:56] <infinity> happyaron: *poke*
[05:47] <pitti> Riddell: FYI, kopete regression on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html - seems the package is FTBFS now
[05:48] <pitti> Riddell: kdepim-runtime also keeps failing on ppc64el; seems it only succeeded twice, so a very racy test; ignore, I suppose?
[05:48]  * pitti sets it to "always failed"
[06:27] <pitti> Riddell: and http://autopkgtest.ubuntu.com/packages/b/baloo-kf5/wily/armhf/ fails on the ABI compliance checker, this also looks real
[07:13] <pitti> sil2100: good morning
[07:13] <pitti> sil2100: thanks for the MP! as written there, I ran cron.daily.rtm last night; do the packages look ok to you?
[07:13] <pitti> sil2100: if so, I'll enable it in cron
[07:14] <pitti> sil2100: every Tuesday afternoon, I suppose
[07:16] <FourDollars> Why can I not see the latest trusty updates at https://code.launchpad.net/ubuntu/+source/network-manager?
[07:21] <FourDollars> Not from https://code.launchpad.net/network-manager neither. :-(
[07:22] <seb128> FourDollars, those packages are not maintained in those vcs and the autoimporter are sometime suboptimals
[07:22] <FourDollars> seb128: I need to fix some issue on trusty. Do you know where is the bzr repo?
[07:23] <seb128> FourDollars, none afaik, just get the source package and do a debdiff including your change
[07:24] <FourDollars> seb128: I saw lp:~network-manager/network-manager/ubuntu, lp:~network-manager/network-manager/ubuntu.vivid, lp:~network-manager/network-manager/ubuntu.precise at https://launchpad.net/ubuntu/+source/network-manager. But no lp:~network-manager/network-manager/ubuntu.trusty. It is weird.
[07:25] <seb128> check with cyphermox when he's online, maybe he has a vcs...
[07:25] <FourDollars> OK.
[07:49] <FourDollars> cyphermox: hi
[07:50] <jamespage> cjwatson, pitti: I think I know the answer to this question - the latest heat and keystone uploads for wily have broken versioning - they have not built yet and are stuck in proposed - is it possible to remove the source packages from proposed an then correct? thus avoiding bumping epoch
[07:51] <pitti> jamespage: right, please avoid bumping epoch at all cost, it will make the package forever not syncable
[07:51] <pitti> jamespage: yes, we can remove them from proposed
[07:51] <jamespage> pitti, awesome - that would be most helpful
[07:51] <pitti> jamespage: but the next upload can't re-use the same version number
[07:52] <jamespage> pitti, it won't - the upstream version number will be corrected, but it will be lower than the current one from dpkg's perspective
[07:52] <jamespage> is that ok
[07:52] <jamespage> ?
[07:52] <pitti> jamespage: I'm not entirely sure; you'll find out at next upload :)
[07:52] <jamespage> current == the one in proposed
[07:52] <pitti> jamespage: oh, 0rc1 →  0~rc1 :)
[07:53] <jamespage> pitti, yes...
[07:53]  * jamespage sighs
[07:53] <pitti> jamespage: removed
[07:53] <jamespage> pitti, thankyou
[07:54] <pitti> time and again, having -proposed is so immensely helpful
[07:56] <jamespage> pitti, agreed
[08:08] <sil2100> pitti: thanks for the test run! I'll triple check them in a moment and give you a sign :)
[08:10] <pitti> sil2100: nice!
[08:10] <pitti> sil2100: btw, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html → seems qtmir and -gles were published prematurely? looks like they are missing a new mir?
[08:10] <pitti> same for unity-system-compositor
[08:11] <pitti> infinity: is bug 1435466 still actually a blocker?
[08:12] <pitti> infinity: block-proposed I mean
[08:44] <infinity> pitti: There was one FTBFS on arm64 that I saw float by that I wanted to make sure wasn't a regression on other arches too.  I think once I've had a chance to play with that, I'll lift the tag
[08:45] <pitti> infinity: ack, thanks; I mostly wanted to know whether it was still justified, but sounds like it is
[09:04] <happyaron> infinity: hey
[09:04]  * happyaron back from dinner
[09:10] <seb128> jamespage, zul, there is a trivial patch for a typo fix in the package description on https://bugs.launchpad.net/ubuntu/+source/ironic/+bug/1451139 could you include it in the next ironic upload?
[09:18] <jamespage> seb128, yup
[09:19] <seb128> jamespage, thanks
[09:19] <seb128> jamespage, I'm assigning to you and unsubcribing sponsors, is that ok?
[09:25] <caribou> micahg: Got some bandwidth to sponsor the fix for LP: #1481737 ?
[09:45] <Riddell> pitti: I don't get the acc error in baloo, it's just running a dump of symbols isn't it? there's no actual comparison going on.  I can recreate the error but there's no output so I've no idea what it's problem is
[09:45] <cjwatson> jamespage: lower than a deleted package is OK, yes
[09:46] <Riddell> pitti: ah yes it's in logs/ "ERROR: can't access '/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so'"
[09:46] <pitti> Riddell: I have no idea what abi-compliacne-checker does
[09:46] <pitti> Riddell: x86_64? it only fails on armhf
[09:46] <pitti> Riddell: but yeah, some verbose output certainly would be useful, to be able to see what to actually fix
[09:47] <pitti> Riddell: baloo-kf5 itself didn't change, so I suppose it's due to a dependency change
[09:51] <pitti> Riddell: ah, nevermind -- it fails on amd64 too (in fact, all platforms)
[09:54] <Riddell> pitti: so probably a problem in the test, I'll look at it after I do some beta candidates testing
[09:56] <Laney> You renamed the library
[10:23] <LocutusOfBorg1> hi folks, how do you feel about a pbuilder merge?
[10:23] <LocutusOfBorg1> http://debomatic-amd64.debian.net/distribution#wily/pbuilder/0.217ubuntu1/buildlog
[10:23]  * LocutusOfBorg1 feels crazy
[10:23] <LocutusOfBorg1> but well, the delta is soo less now
[10:24] <alkisg> didrocks: hi, http://changelogs.ubuntu.com/changelogs/pool/universe/u/ubuntu-mate-meta/ubuntu-mate-meta_1.134/changelog mentions that you added fcitx in ubuntu-mate-core,
[10:24] <alkisg> this now runs on login and breaks at least the greek keyboard layout, could it please be removed again, or at least downgraded to suggests or recommends?
[10:26] <didrocks> alkisg: I did refresh the metapackage on flexiondotorg's request (he added it to the seed)
[10:27] <alkisg> Thank you
[10:27] <didrocks> alkisg: let me point you to the commit, one sec
[10:27] <flexiondotorg> alkisg, Hi
[10:27] <alkisg> flexiondotorg: could you please have a look at that?
[10:27] <alkisg> Hello
[10:28] <flexiondotorg> alkisg, That was added to ensure Japanese users were supported.
[10:28] <flexiondotorg> What is the issue?
[10:28] <alkisg> flexiondotorg: is it necessary to run in all users worldwide?
[10:28] <didrocks> http://bazaar.launchpad.net/~ubuntu-mate-dev/ubuntu-seeds/ubuntu-mate.wily/revision/18
[10:28] <alkisg> In Greece, the keyboard layout supports accented characters by pressing e.g. this: ";" + "a" = ά
[10:28] <didrocks> alkisg: recommends make sense, but IIRC, mate doesn't install recommends by default
[10:29] <didrocks> happyaron: this may be of interest for you ^ (fcitx issue with greek)
[10:29] <alkisg> Now if fcitx is installed, then this breaks, and produces this instead: ´α
[10:29] <flexiondotorg> Correct, Ubuntu MATE doesn't install recommends. I've manually resolved what is required in the seeds.
[10:29] <alkisg> So basically now with fcitx-bin preinstalled, we can't type in our language
[10:29] <didrocks> alkisg: I guess you have the same issue with the ubuntu desktop image, right?
[10:29] <alkisg> didrocks: ah I haven't tried it, I could check...
[10:29] <flexiondotorg> Sadly, there is still some package that I need to submit patches for.
[10:30] <didrocks> alkisg: do you mind trying? I think we can open a critical bug as it impacts all flavors installing it
[10:30] <flexiondotorg> Without doing that when the Ubuntu MATE seeds are parsed most of Unity get's pulled in.
[10:30] <alkisg> didrocks: I'll do so, but it's lunch time here, so I'll report back later on in the afternoon, in e.g. 5 hours
[10:30] <seb128> happyaron, ^fcitx creating compose issues, is that known?
[10:30] <didrocks> alkisg: that's fine :)
[10:31] <didrocks> seb128: already pinged him above
[10:31] <Laney> alkisg: Do you have /etc/xdg/autostart/fcitx-autostart.desktop?
[10:31] <happyaron> seb128: what compose issue?
[10:31] <seb128> happyaron, read backlog
[10:31] <didrocks> happyaron: please backlog, I pinged you
[10:31] <happyaron> ok
[10:31] <ogra_> alkisg, 5h ? wow, that even exceeds a typical spanish lunch
[10:31] <seb128> didrocks, oh, right, didn't notice that line
[10:31] <alkisg> ogra_: I like to hug a bit after lunch :P :D
[10:32] <ogra_> haha
[10:32] <Laney> TMI
[10:32] <flexiondotorg> seb128, didrocks fcitx-bin is only in the -live seed for ubuntu.
[10:32] <flexiondotorg> Where as I have it in the core package.
[10:32] <alkisg> Laney: in the process of troubleshooting, I removed fcitx-bin, which also removed the mate-core metapackage, I can reinstall it and check
[10:32] <flexiondotorg> So maybe all that is required is for Ubuntu MATE to move fcitx-bin into live.
[10:33] <happyaron> didrocks: well it's now using xkbcommon and should not have the problem of behaving differently to ibus
[10:33] <didrocks> happyaron: seems alkisg triggered some issue, I guess it worths a deep look
[10:33] <happyaron> Laney: that was fixed in debian yesterday, will syncpackage to Ubuntu today
[10:33] <happyaron> didrocks: will do
[10:37] <anestis> Laney: (this is alkisg on a client's pc): yes: fcitx-bin: /etc/xdg/autostart/fcitx-autostart.desktop
[10:37] <anestis> fcitx-bin      1:4.2.9-2
[10:42] <Laney> so I think with the next upload this will be removed and hopefully the bug won't happen for you any more
[10:42] <Laney> try removing it and restarting your session to see if no fcitx resolves the issue
[10:42] <Laney> but from what happyaro_n said it shouldn't happen anyway...
[10:42] <Laney> ho hum
[10:42] <alkisg> Removing fcitx does resolve the issue
[10:42] <alkisg> Thank you, I will test with newer images and report back
[10:43] <alkisg> I'll also test with the unity image, e.g. if we can't type our names in the installer it will be an issue...
[10:43] <alkisg> (i.e. if fcitx-bin is installed in the live image)
[10:44] <happyaron> don't have syncpackage command on this remote console, it's already handled in -3 at Debian
[10:44] <Laney> alkisg: try removing just that desktop file
[10:48] <alkisg> Hmmm I'm missing something... fcitx-bin 1:4.2.9-2 ==> `dpkg -L fcitx-bin | grep autostart` says that /etc/xdg/autostart/fcitx-autostart.desktop is there on one pc, and it isn't there on another...
[10:49] <alkisg> Maybe a package update happened without a version number bump?
[10:49] <Laney> It's deleted in that upload but the code to remove the file from upgrading systems was forgotten
[10:49] <Laney> that's what he handled in -3
[10:49] <alkisg> Gotcha :)
[10:50] <cjwatson> package updates without version number bumps aren't possible anyway
[10:51] <alkisg> Well, dpkg -L produces different results with the same dpkg -l version number
[10:51] <cjwatson> right, but as Laney says that's due to buggy conffile removal, not because there were two different packages with the same version number
[10:51] <alkisg> Ah, dpkg -L lists older conffiles that are not inside the .deb, I didn't know that, sorry
[10:54] <flexiondotorg> Laney, Is that fcitx-bin package sync/update going to happen and the images respun?
[10:55] <Odd_Bloke> cjwatson: Is there a way I can set up a VM that will behave the same as the Launchpad build slaves?  I'm still trying to get to the bottom of this disk image/loop device issue.
[10:56] <Laney> flexiondotorg: It's an upgrade issue only, so not really interesting for images
[10:56] <Laney> indeed systems installed from the beta images won't have the problem
[10:56] <flexiondotorg> Laney, Ah, great.
[10:57]  * alkisg waves, bb with info about the live session etc later on. Thanks all! :)
[10:58] <cjwatson> Odd_Bloke: so, I'm also still trying to get to the bottom of it (along with everything else), but the VM I set up fails in a different and earlier place ...
[10:58] <cjwatson> + umount chroot/root/config
[10:58] <cjwatson> umount: chroot/root/config: umount failed: No such file or directory
[10:58] <cjwatson> haven't got to the bottom of that yet
[11:05] <cjwatson> Odd_Bloke: I mean, in theory it's https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally and you can start with a cloud image, which is what I did
[11:05] <cjwatson> and I grabbed a wily amd64 chroot
[11:05] <cjwatson> Odd_Bloke: I'm still working on it though
[11:07] <Odd_Bloke> cjwatson: OK, cool; I've just noticed that there is a 'sync' switch on kpartx (that isn't documented in the manpage: bug 1298292) that waits until the partitions are created, so I'm building a livecd-rootfs that uses that to see if it makes any difference.
[11:08] <cjwatson> Odd_Bloke: oh, I even read the source and looked for that
[11:08] <Odd_Bloke> We aren't using it when we do stuff on our Jenkins instance in kvm, but maybe it's just a timing problem that this will work around.
[11:08] <cjwatson>         if (!udev_sync)
[11:08] <cjwatson>                 dm_udev_set_sync_support(0);
[11:08] <cjwatson> that could certainly be very relevant
[11:09] <cjwatson> I didn't notice it because the cookie stuff further down looked unconditional
[11:26] <jamespage> cjwatson, are you aware of any issues in debian infrastructure that might be causing uploads done in the last 24 hrs or so in Debian to not be noticed?
[11:26] <jamespage> tracker, rmadison, launchpad are all stale compared to ftp.debian.org
[11:27] <Laney> jamespage: There was a bug in mirrors being updated
[11:27] <Laney> I just asked in #debian-mirrors
[11:28] <Laney> Supposed to be fixed nowish
[11:28] <jamespage> ack
[12:04] <cjwatson> Odd_Bloke: sorry for the build delay, it's almost there now - there's an outage somewhere in the scalingstack infrastructure, reported
[12:05] <Odd_Bloke> cjwatson: No worries. :)
[14:53] <pitti> apw, infinity, Laney: FYI, first stabs at live test logtail: http://autopkgtest.ubuntu.com/running.html
[14:53] <pitti> page updates every 10 s (not by itself yet)
[14:53] <alkisg> didrocks, flexiondotorg, happyaron, Laney, I tested with the today's ubuntu wily unity i386 daily build, and while fcitx-bin was there in the live session, the autostart file wasn't there, so I didn't have a problem with that and the greek keyboard layout. So the problem I reported has already been tackled, thank you very much.
[14:53] <alkisg> The problem with unity-settings-daemon breaking the keyboard layout is still there, but that has been the case since 12.04, even with the dozens of bug reports filed for that, so I don't think that will be as easily fixed... let's hope it'll be fixed for 16.04. :)
[14:53] <pitti> apw, infinity, Laney: notice the amazing design, I spent two days on this!
[14:54]  * pitti adds a refresh header
[14:54] <Laney> pitti: handy
[14:54] <Laney> Do you store the full log as you go or just the tail?
[14:55] <pitti> Laney: just the tail
[14:55]  * Laney nod
[14:55] <pitti> Laney: right now the last 1 kB
[14:55] <pitti> I should probably bump that a bit
[14:56] <Laney> I was thinking of the way jenkins does it
[14:56] <pitti> Laney: well, I'd like to cap it a bit -- unlimited seems gross, as logs can sometimes get GBs
[14:56] <Laney> but anyway, this is cool - thanks
[14:56] <pitti> maybe 10 kB is right
[14:56] <pitti> Laney: there is lots missing there -- log size, design, auto-refresh, proper configuration, etc.
[14:57] <pitti> it's mostly just a prototype
[14:57] <apw> pitti, interesting
[14:57] <Laney> integration with the package page I suppose
[14:57] <pitti> libpng finished, I'll restart some new ones
[14:57] <pitti> Laney: that too
[15:00]  * pitti enables that for arm/ppc too
[15:00] <seb128> pitti, do you know if https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1441008 is an issue with the avahi systemd unit or a systemd issue?
[15:04] <pitti> seb128: (meeting, bbl)
[15:04] <seb128> pitti, no hurry, enjoy!
[15:23] <pitti> seb128: replied to the bug
[15:24] <seb128> pitti, thanks
[17:28] <sil2100> pitti: argh, almost forgot to poke you - the langpacks look fine :)
[17:29] <sil2100> pitti: you can enable the weekly runs of the job
[20:24] <Unit193> infinity: I presume you didn't see my openbox debdiff? ;P