[01:08] <Logan> does anyone know what bugproxy is? e.g. this cryptic report at https://bugs.launchpad.net/ubuntu/+bug/1457146
[01:08] <Logan> appears to have something to do with...IBM?
[10:03] <cjwatson> taggart: The patch is there, but it's not in our configuration by default.  (That is, the patch introduces a way to turn off the Debian revision in the protocol handshake, but the default is to leave it in there.)
[10:25] <Quintasan> Hi
[14:40] <infinity> Logan: Yeah, it's a proxy from IBM's internal bug tracker.  Irksome that they picked a generic name.  Maybe we should force a rename on them.
[14:41] <infinity> wgrant: Do you know the right people to talk to to get IBM to fix their auth tokens and code to cope if we force an s/bugproxy/ibm-bugproxy/ rename on them?  That generic account name is irksome/confusing.
[16:00] <taggart> cjwatson: ok cool, I am updating a puppet module and I am going to setup "DebianBanner no" for both debian and ubuntu
[16:00] <taggart> cjwatson: and I am starting to wonder if that would be a good idea for the package
[16:09] <cjwatson> taggart: I wouldn't accept such a change
[16:09] <cjwatson> taggart: The existence of the option is a reasonably stable compromise :)
[22:43] <wgrant> infinity: You should probably rather get them to fix the displayname. The username is less interesting.


[01:02] <Noskcaj> bug 1388294
[01:13] <LinDol> hi all
[04:58] <darkxst> Noskcaj, thanks, though currently empathy is the only thing in main that requires it? no?
[04:59] <Noskcaj> i think i saw something else, forget what
[05:00] <Noskcaj> g-clocks, g-maps, empathy, all the variations of webkitgtk
[05:01] <darkxst> first two are universe
[05:02] <darkxst> Noskcaj, it wouldnt hurt to list all packages in main that have upstream support
[05:03] <darkxst> but are currently built against geoclue 1
[05:03] <Noskcaj> ok
[05:10] <Noskcaj> g-s-d also carries a revert
[05:16] <darkxst> the more the better
[05:17] <darkxst> though g-s-d is only in main for the schemas these days
[05:17] <darkxst> what about the qt5 positioning thing?
[05:19] <Noskcaj> ?
[05:19] <darkxst> libqt5positioning5-plugins
[05:19] <darkxst> seems odd that qt5 would be using obsolete libraries, but maybe it just is
[05:25] <Noskcaj> i'll look into it
[05:28] <darkxst> ok
[08:49] <GnomieHomie> Hi, I've been using Ubuntu 14.04, upgraded to 14.10 today and my system hangs on boot.
[08:49] <GnomieHomie> I see the start-up splash screen, then with all 3 dots highlighted, it hangs.
[08:50] <GnomieHomie> My system uses a Asus Maximus VI Hero motherboard, intel 4770k and Sapphire/AMD HD 7950. Nothing is overclocked (except the ram by just a little bit... to match the specs on the box it came in).
[08:51] <GnomieHomie> I normally use the official AMD drivers, rather than the OSS ones.
[08:52] <GnomieHomie> I can't boot to rescue mode - it won't bring up a terminal, etc, it just stops after a certain line. Currently, I'm using an live disc to access the system.
[08:53] <GnomieHomie> The last line that shows in rescue mode is: [    2.464692] Switched to clocksource tsc
[08:53] <GnomieHomie>  /var/log/dmesg shows the following after that line.
[08:53] <GnomieHomie> [    2.575723] init: Error while reading from descriptor: Broken pipe [    2.577537] init: failsafe main process (855) killed by TERM signal
[08:54] <GnomieHomie> .. and some other stuff that doesn't look suspect (though, I'm not sure if those lines I've pasted, are from me turning the PC off)
[08:55] <GnomieHomie> Pulling my hair out, open to any suggestions please :)
[08:56] <GnomieHomie> gdm log's last line is: /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/fglrx_drv.so: undefined symbol: LoadExtension
[09:01] <mgedmin> GnomieHomie, the 'failsafe ... killed by TERM' is normal, it doesn't break boot
[09:01] <mgedmin> the fglrx_drv error is definitely very suspicious
[09:01] <mgedmin> my laptop has intel video so I've no familiarity with amd's proprietary drivers
[09:01] <GnomieHomie> hmm, ok
[09:02] <mgedmin> can you check if the package versions you've got are up to date?
[09:02] <GnomieHomie> mgedmin: if it's display drivers, I could try reinstall/check for update, but for that, I would need to boot the system somehow.
[09:02] <mgedmin> how are you accessing the log files?
[09:03] <GnomieHomie> live disc
[09:03] <mgedmin> nm, found it in backlog
[09:03] <mgedmin> you can use chroot to install/remove packages
[09:03] <GnomieHomie> no idea how I would do that, any tips on what I should be googling (or want to tell me what to do)? Thanks.
[09:05] <mgedmin> open a terminal and sudo chroot /path/to/where/your/system/root/is/mounted /bin/bash
[09:05] <GnomieHomie> neato.
[09:05] <mgedmin> in there I'd run apt-show-versions | grep -v uptodate
[09:05] <mgedmin> to see if there are any packages not matching the version in ubuntu archives (outdated or locally installed or anything)
[09:06] <mgedmin> you may need to apt install apt-show-versions
[09:07] <GnomieHomie> okay, thanks heaps, I'll give things a whirl and let you know how I get on
[09:07] <mgedmin> ideally you'd find someone who has amd video and is running 14.10 successfully on irc, and figure out how your systems differ...
[09:11] <mgedmin> by the way, is the live system you're using also 14.10?
[09:12] <GnomieHomie> yes
[09:12] <GnomieHomie> no, I mean.
[09:12] <GnomieHomie> 14.04
[09:12] <GnomieHomie> I haven't downloaded an iso to test if 14.10 works as new
[09:19] <GnomieHomie> mgedmin: any idea how to enable network access within the chroot?
[09:19] <mgedmin> open a different terminal (so you've a system outside the chroot) and sudo mount --bind /etc/resolv.conf /path/to/chroot/etc/resolv.conf
[09:20] <mgedmin> s/a system/a shell/
[09:20] <GnomieHomie> sweet.
[09:21] <GnomieHomie> works well... loving this stuff *archives it for later*
[09:22] <mgedmin> note that if you end up having to install a kernel or grub from a live system like this, you also have to have more bind mounts
[09:22] <mgedmin> specifically /proc, /sys, /dev and /dev/pts
[09:22] <GnomieHomie> wow
[09:23] <GnomieHomie> ... mgedmin, at a guess, I figured I would reinstall gfx drivers, which uses intrafms (sp?) to put itself into the kernel.
[09:23] <mgedmin> no, I don't think they go into initramfs
[09:23] <GnomieHomie> Do I therefore need to do more binds, or should the install be OK as is?
[09:23] <mgedmin> should be fine
[09:33] <GnomieHomie> Hmm, I think it may well have been the gfx drivers, we'll see soon - I've uninstalled them.
[09:33] <GnomieHomie> Note to self, in future, before upgrade, uninstall proprietry drivers.
[09:34] <GnomieHomie> Install notes on the website say kernel supported up to 3.15, where-as Ubuntu is now at 3.16.
[09:34] <mgedmin> wait, did you install fglrx by hand?
[09:34] <mgedmin> instead of using ubuntu's own proprietary driver installer?
[09:34] <GnomieHomie> nah, there's an uninstall script
[09:34] <mgedmin> yeah, that can be a problem
[09:34] <GnomieHomie> Correction: Yes, I installed fglrx on my own.
[09:34] <mgedmin> but if you'd used ubuntu's jockey (iirc that's what it's called), then I'd expect the system to survive an upgrade
[09:34] <mgedmin> ah, ok
[09:34] <mgedmin> yes
[09:35] <GnomieHomie> well, wish me luck, see ya.
[11:06] <nlsthzn> so glad I found out about Alt+F2 then r to restart gnome-shell... some of the extensions sometimes go wonky and now I can sort them out in 2 seconds :)
[11:25] <tdg5> hello all, is there anyone here who can offer me some insight into what I would need to do to get a patch backported/added to the gnome-3-10 branch of the gnome-shell-extensioms project?
[11:29] <tdg5> I don't think it's something particular to my system, but the 3.10 version of the places-menu extension fails to load because it's missing a patch that seems to have only been added to 3.12+
[11:29] <tdg5> This is the missing patch: https://git.gnome.org/browse/gnome-shell-extensions/commit/extensions/places-menu/placeDisplay.js?h=gnome-3-12&id=e73752118d30a9c17a6403036ea33d6eb0e70e55
[16:02] <Gnomebuntuknilch> 014
[18:12] <MichaelTunnell> GNOME is reactivating wifi on reboot...is there a way in Ubuntu GNOME to force it to always be disabled?
[18:15] <MichaelTunnell> anyone?
[18:19] <MichaelTunnell> I suppose rfkill block is the best method for this with a soft block
[18:20] <Gnomebuntuknilch> MichaelTunnell: blacklist the drivermodul
[18:22] <MichaelTunnell> well need it to work if necessary at some point so blacklist is too permanent


[13:25] <zequence> infinity: finally got saucy uploaded
[19:29] <slangasek> so is there someone here that could do something about the fact that kernel.ubuntu.com includes no documentation of the mapping of gitweb urls to git repositories?
[19:30] <slangasek> finally found what I was looking for, but it was non-obvious and I had to browse to the top level of the gitweb for the repo in question to figure it out
[19:30] <slangasek> otoh maybe the problem is cking using non-standard repo names ;)
[21:07] <apw> slangasek, drop me an email to remind me :)  but yeah lets blame cking !
[21:18] <pentester> heey
[21:19] <pentester> is there anyone here?
[21:31] <infinity> zequence: Great, thanks.


[00:51] <DanaG> !clone
[00:55] <hotmonkeyluv> is there an .iso for 8.10?
[00:56] <JontheEchidna> Nope
[01:20] <hotmonkeyluv> JontheEchidna: thanks
[03:17] <travist120> Where can I find out information on Intrepid Ibex? (ie. what the plans are for it, new features, stuff like that)
[03:19] <RAOF> blueprints.launchpad.net/+ubuntu, generally.
[03:20] <RAOF> Although there may not be much there yet, the developers conference only just ended.
[03:21] <travist120> okay, thanks
[11:41] <klerfayt> hey can I get intrepid cd images from somewhere?
[11:45] <stdin> they haven't stared making the daily images yet
[22:48] <so1> hi
[22:48] <so1>  gcc-4.2-base and libtotem-plparser10 cannot be updated since a few days ... is that correct or did i miss something?
[22:48] <so1> removing gcc-4.2-base is not possible because many programs still depend on it ...
[22:48] <so1> and the libtotem one needs an unavailable package, 'perlapi' or something like that
[22:54] <so1> someone?
[22:56] <rsk> afaik perl is being upgraded
[23:14] <RAOF> so1: We're still at the point were no one really cares about those sort of problems.  They'll get fixed pretty much automatically.
[23:20] <so1> ah o


[00:02] -queuebot:#ubuntu-release- New binary: opensaml [riscv64] (groovy-proposed/universe) [3.1.0-2] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: libopenshot [riscv64] (groovy-proposed/universe) [0.2.5+dfsg1-2] (no packageset)
[00:06] -queuebot:#ubuntu-release- New binary: gftl-shared [riscv64] (groovy-proposed/universe) [1.0.7-1] (no packageset)
[03:19] -queuebot:#ubuntu-release- Unapproved: budgie-extras (focal-proposed/universe) [1.0.1-2 => 1.0.2-0ubuntu1] (personal-fossfreedom, ubuntu-budgie)
[05:14] -queuebot:#ubuntu-release- New binary: packetsender [s390x] (groovy-proposed/none) [6.2.6-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: libopenshot-audio [amd64] (groovy-proposed/universe) [0.2.0+dfsg1-3] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: packetsender [ppc64el] (groovy-proposed/none) [6.2.6-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: packetsender [amd64] (groovy-proposed/none) [6.2.6-2] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: packetsender [arm64] (groovy-proposed/none) [6.2.6-2] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: packetsender [armhf] (groovy-proposed/none) [6.2.6-2] (no packageset)
[05:39] -queuebot:#ubuntu-release- New binary: packetsender [riscv64] (groovy-proposed/universe) [6.2.6-2] (no packageset)
[07:48] <rbasak> bdmurray: thanks. Any situation where a sync like that would be acceptable?
[08:02] <Laney>  LocutusOfBorg: You definitely can make MPs against autopkgtest-cloud. I think if you push to a place without '+git' it would let you.
[08:02] <Laney> I'll look though.
[08:22] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (focal-proposed/main) [5.4.0-1019.19] (core, kernel)
[08:22] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (focal-proposed) [5.4.0-1019.19]
[08:22] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (focal-proposed/main) [5.4.0-40.44] (core, kernel)
[08:23] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (focal-proposed) [5.4.0-40.44]
[08:24] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (focal-proposed/main) [5.4.0-1019.19] (core, kernel)
[08:24] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (focal-proposed) [5.4.0-1019.19]
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-109.110] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.3.0-62.56] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-62.56] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-109.110] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.3.0-62.56] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-109.110]
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.3.0-62.56] (core, kernel)
[08:25] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-109.110]
[08:25] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (focal-proposed/main) [5.4.0-40.44] (core, kernel)
[08:26] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.3.0-62.56]
[08:26] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.3.0-62.56]
[08:26] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (focal-proposed) [5.4.0-40.44]
[08:26] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.3.0-62.56]
[08:26] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (eoan-proposed) [5.3.0-62.56]
[08:42] <LocutusOfBorg> thanks Laney :) https://code.launchpad.net/~costamagnagianfranco/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/386374
[08:46] <ginggs> ubuntu-archive: would someone please remove vtk7/7.1.1+dfsg2-4ubuntu3/riscv64 binaries from -release? it's blocking the r-base transition. the rebuild stalled, and now retrying hits the bsdextrautils mess. it should build fine once that is resolved
[08:47] <LocutusOfBorg> alternatively, we can remove bsdmainutils from groovy proposed pocket, not sure which one is best ^^
[08:47] <ginggs> why not both? :)
[08:48] <ginggs> \o/
[10:21] <seb128> ginggs, it seems to have a bunch of rdepends, we can't just remove it like that
[10:21] <LocutusOfBorg> also bsdmainutils?
[10:22] <ginggs> seb128: thanks :(
[10:22] <LocutusOfBorg> seb128, if we remove it, we can retry the vtk7 build and live happy
[10:23] <cpaelzer_> sil2100: rbasak: would one of you be able to today shed soem SRU-light onto open-vm-tools in focal-unapproved?
[10:23] <seb128> ginggs, sorry :/
[10:23] <cpaelzer_> This has an external deadline somewhen late in July, but I'm off in July quite a bit - so in case anything comes up I might be unavalilable and it will delay further
[10:23] <cpaelzer_> therefore starting to process it soon would be very helpful
[10:24] <seb128> LocutusOfBorg, removing something from proposed doesn't break the archive so is probably best
[10:27] <LocutusOfBorg> can you please do it then?
[10:28] <LocutusOfBorg> we can copy it back once vtk7 is built and migrates with r-* stuff
[10:28] <seb128> ^ ubuntu-archive, anyone is having an objection to do that?
[10:28] <seb128> or not only ubuntu-a :p
[10:32] <apw> seb128, if none of its reverse-depends are in -proposed removing something from there sounds tollerable
[10:34] <seb128> apw, do you know of an easy way to check that?
[10:34] <apw> seb128, no :)
[10:34] <seb128> :(
[10:35] <apw> some kinds of reverse-depends | rmadison combo i guess
[10:36] <seb128> right...
[10:37] <LocutusOfBorg> for i in `reverse-depends -r groovy src:bsdmainutils |grep \* |cut -f 2 -d " "`; do rmadison -u ubuntu -s groovy-proposed $i; done
[10:37] <LocutusOfBorg> is that what you want?
[10:43] <LocutusOfBorg> or we might disable the failing test on util-linux and reupload so it builds on riscv64
[10:43] <LocutusOfBorg> it might be even easier
[10:43] <LocutusOfBorg> in the meanwhile we fix it
[10:45] <seb128> LocutusOfBorg, right, I don't feel comfortable removing bsdmainutils without more data on the impact, maybe someone on +1 rotation can help there
[12:29] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [amd64] (bionic-proposed/main) [5.4.0-40.44~18.04.1] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [s390x] (bionic-proposed/main) [5.4.0-40.44~18.04.1] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [ppc64el] (bionic-proposed/main) [5.4.0-40.44~18.04.1] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-5.4 [arm64] (bionic-proposed/main) [5.4.0-40.44~18.04.1] (no packageset)
[12:35] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [amd64] (bionic-proposed) [5.4.0-40.44~18.04.1]
[12:35] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [ppc64el] (bionic-proposed) [5.4.0-40.44~18.04.1]
[12:35] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [arm64] (bionic-proposed) [5.4.0-40.44~18.04.1]
[12:35] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-5.4 [s390x] (bionic-proposed) [5.4.0-40.44~18.04.1]
[12:37] -queuebot:#ubuntu-release- Unapproved: vagrant (focal-proposed/universe) [2.2.6+dfsg-2ubuntu2 => 2.2.6+dfsg-2ubuntu3] (ubuntu-cloud)
[13:18] <cjwatson> bsdmainutils> wouldn't it be sufficient to fix the bsdextrautils ftbfs on riscv64, get it through NEW with the new binary in main, then retry man-db builds?
[13:19] <cjwatson> unless the vtk7 ftbfs is something other than the typical interaction with man-db that broke a bunch of things
[13:19] <cjwatson> the uname 2.6 test in util-linux didn't look like it was likely to make much sense on riscv64 anyway
[13:29] <LocutusOfBorg> cjwatson, yes https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4114/+packages
[14:45] <cpaelzer_> sil2100: I pinged this morning if there would be a chance to SRU look at open-vm-tools but got no reply so far, too busy today?
[14:45] <cpaelzer_> I also pinged rbasak but it turns out he it off today
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [arm64] (groovy-proposed) [1.4.6+dfsg-2ubuntu1]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [ppc64el] (groovy-proposed) [1.4.6+dfsg-2ubuntu1]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [s390x] (groovy-proposed) [1.4.6+dfsg-2ubuntu1]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [arm64] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [ppc64el] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [s390x] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [armhf] (groovy-proposed) [1.4.6+dfsg-2ubuntu1]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [amd64] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [riscv64] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [riscv64] (groovy-proposed) [1.4.6+dfsg-2ubuntu1]
[14:58] -queuebot:#ubuntu-release- New: accepted remmina [armhf] (groovy-proposed) [1.4.6+dfsg-2ubuntu2]
[14:59] -queuebot:#ubuntu-release- New: accepted nodejs [amd64] (groovy-proposed) [12.18.0~dfsg-3ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted nodejs [armhf] (groovy-proposed) [12.18.0~dfsg-3ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted nodejs [s390x] (groovy-proposed) [12.18.0~dfsg-3ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted nodejs [arm64] (groovy-proposed) [12.18.0~dfsg-3ubuntu1]
[14:59] -queuebot:#ubuntu-release- New: accepted nodejs [ppc64el] (groovy-proposed) [12.18.0~dfsg-3ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [amd64] (groovy-proposed) [2.35.2-4ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [armhf] (groovy-proposed) [2.35.2-4ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [ppc64el] (groovy-proposed) [2.35.2-4ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [arm64] (groovy-proposed) [2.35.2-4ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [s390x] (groovy-proposed) [2.35.2-4ubuntu1]
[15:00] -queuebot:#ubuntu-release- New: accepted util-linux [i386] (groovy-proposed) [2.35.2-4ubuntu1]
[15:01] <LocutusOfBorg> why has util-linux been accepted?
[15:02] <LocutusOfBorg> bileto 4114 is almost ready to land
[15:24] -queuebot:#ubuntu-release- New binary: linux-signed-kvm [amd64] (focal-proposed/main) [5.4.0-1018.18] (no packageset)
[15:26] -queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (focal-proposed) [5.4.0-1018.18]
[15:32] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (bionic-proposed/main) [4.15.0-1048.52] (kernel)
[15:59] <seb128> LocutusOfBorg, sorry it's me who approved it but the queue has no context or info, I just accepted a bunch of binNEW builds because that's what we usually do...
[16:00] <seb128> LocutusOfBorg, does it create any issue? it's not going to use more builder time since it was already built
[16:09] <vorlon> LocutusOfBorg: why building in bileto instead of the archive? using bileto silos is generally opaque to anyone trying to work on this in the archive
[16:09] <vorlon> and why is there a bumped version of vtk7 in that silo
[16:10] <vorlon> and how is it building anyway on riscv64 when the version in the archive dep-wait because bsdextrautils isn't available
[16:23] <LocutusOfBorg> seb128, it didn't harm to be honest
[16:23] <LocutusOfBorg> vorlon, the version in bileto had a "fixed util-linux"
[16:23] <LocutusOfBorg> and now I uploaded in the archive too, so meh, that bileto is useless
[16:26] <LocutusOfBorg> and I used bileto because I had now way to know if the test disable on riscv64 was "correct on first shot" and using the archive for riscv64 tests is sad, and ppa don't have it
[16:26] <LocutusOfBorg> (btw the fix was correctly on first attempt, Murphy's law did the job here)
[16:31] <LocutusOfBorg> if you have a way to test riscv64 specific fixes, please tell me :)
[17:16] -queuebot:#ubuntu-release- New binary: dnsdbq [amd64] (groovy-proposed/none) [2.1.1-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-mergedict [amd64] (groovy-proposed/none) [1.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: httpx [amd64] (groovy-proposed/none) [0.12.1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: speaklater [amd64] (groovy-proposed/none) [1.3-4] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: pykeepass [amd64] (groovy-proposed/none) [3.2.0-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: elementpath [amd64] (groovy-proposed/none) [1.4.4-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: python-tomlkit [amd64] (groovy-proposed/none) [0.6.0-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: libldac [amd64] (groovy-proposed/none) [<IP_ADDRESS>+git20180726-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: python-redisearch-py [amd64] (groovy-proposed/none) [0.9.0-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: audmes [amd64] (groovy-proposed/none) [0+git20200429-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: aerc [s390x] (groovy-proposed/none) [0.3.0-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: dnsdbq [s390x] (groovy-proposed/none) [2.1.1-2] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: node-redux [amd64] (groovy-proposed/none) [4.0.5-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: audmes [s390x] (groovy-proposed/none) [0+git20200429-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: requirement-parser [amd64] (groovy-proposed/none) [0.2.0-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: dpaste [amd64] (groovy-proposed/none) [0.4.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: aerc [amd64] (groovy-proposed/universe) [0.3.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: dpaste [s390x] (groovy-proposed/universe) [0.4.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: prometheus-openstack-exporter [amd64] (groovy-proposed/universe) [0.1.4-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: jsofa [amd64] (groovy-proposed/universe) [0~20190722-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: qbs [s390x] (groovy-proposed/universe) [1.16.0-2] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: aerc [ppc64el] (groovy-proposed/universe) [0.3.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: audmes [ppc64el] (groovy-proposed/universe) [0+git20200429-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: dnsdbq [ppc64el] (groovy-proposed/universe) [2.1.1-2] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: dpaste [ppc64el] (groovy-proposed/universe) [0.4.0-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: libldac [ppc64el] (groovy-proposed/universe) [<IP_ADDRESS>+git20180726-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: dnsdbq [riscv64] (groovy-proposed/universe) [2.1.1-2] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: libldac [riscv64] (groovy-proposed/universe) [<IP_ADDRESS>+git20180726-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: qbs [ppc64el] (groovy-proposed/universe) [1.16.0-2] (no packageset)
[17:35] <vorlon> LocutusOfBorg: testing riscv64-specific fixes: https://people.ubuntu.com/~wgrant/riscv64/
[17:36] -queuebot:#ubuntu-release- New: accepted aerc [ppc64el] (groovy-proposed) [0.3.0-1]
[17:36] -queuebot:#ubuntu-release- New: accepted dnsdbq [ppc64el] (groovy-proposed) [2.1.1-2]
[17:36] -queuebot:#ubuntu-release- New: accepted dpaste [ppc64el] (groovy-proposed) [0.4.0-1]
[17:36] -queuebot:#ubuntu-release- New: accepted libldac [riscv64] (groovy-proposed) [<IP_ADDRESS>+git20180726-1]
[17:36] -queuebot:#ubuntu-release- New: accepted audmes [ppc64el] (groovy-proposed) [0+git20200429-1]
[17:36] -queuebot:#ubuntu-release- New: accepted libldac [ppc64el] (groovy-proposed) [<IP_ADDRESS>+git20180726-1]
[17:37] -queuebot:#ubuntu-release- New: accepted dnsdbq [riscv64] (groovy-proposed) [2.1.1-2]
[17:37] -queuebot:#ubuntu-release- New: accepted qbs [ppc64el] (groovy-proposed) [1.16.0-2]
[17:37] -queuebot:#ubuntu-release- New: accepted aerc [amd64] (groovy-proposed) [0.3.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted audmes [s390x] (groovy-proposed) [0+git20200429-1]
[17:37] -queuebot:#ubuntu-release- New: accepted dpaste [amd64] (groovy-proposed) [0.4.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted jsofa [amd64] (groovy-proposed) [0~20190722-1]
[17:37] -queuebot:#ubuntu-release- New: accepted prometheus-openstack-exporter [amd64] (groovy-proposed) [0.1.4-1]
[17:37] -queuebot:#ubuntu-release- New: accepted requirement-parser [amd64] (groovy-proposed) [0.2.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted aerc [s390x] (groovy-proposed) [0.3.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted dpaste [s390x] (groovy-proposed) [0.4.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted qbs [s390x] (groovy-proposed) [1.16.0-2]
[17:37] -queuebot:#ubuntu-release- New: accepted dnsdbq [s390x] (groovy-proposed) [2.1.1-2]
[17:37] -queuebot:#ubuntu-release- New: accepted node-redux [amd64] (groovy-proposed) [4.0.5-1]
[17:37] -queuebot:#ubuntu-release- New: accepted audmes [amd64] (groovy-proposed) [0+git20200429-1]
[17:37] -queuebot:#ubuntu-release- New: accepted elementpath [amd64] (groovy-proposed) [1.4.4-1]
[17:37] -queuebot:#ubuntu-release- New: accepted libldac [amd64] (groovy-proposed) [<IP_ADDRESS>+git20180726-1]
[17:37] -queuebot:#ubuntu-release- New: accepted python-mergedict [amd64] (groovy-proposed) [1.0.0-1]
[17:37] -queuebot:#ubuntu-release- New: accepted python-tomlkit [amd64] (groovy-proposed) [0.6.0-1]
[17:37] -queuebot:#ubuntu-release- New binary: qbs [amd64] (groovy-proposed/universe) [1.16.0-2] (no packageset)
[17:37] -queuebot:#ubuntu-release- New: accepted dnsdbq [amd64] (groovy-proposed) [2.1.1-2]
[17:38] -queuebot:#ubuntu-release- New: accepted pykeepass [amd64] (groovy-proposed) [3.2.0-1]
[17:38] -queuebot:#ubuntu-release- New: accepted speaklater [amd64] (groovy-proposed) [1.3-4]
[17:38] -queuebot:#ubuntu-release- New: accepted httpx [amd64] (groovy-proposed) [0.12.1-1]
[17:38] -queuebot:#ubuntu-release- New: accepted python-redisearch-py [amd64] (groovy-proposed) [0.9.0-1]
[17:38] -queuebot:#ubuntu-release- New: accepted gftl-shared [riscv64] (groovy-proposed) [1.0.7-1]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [amd64] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [armhf] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [riscv64] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted libopenshot-audio [amd64] (groovy-proposed) [0.2.0+dfsg1-3]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [ppc64el] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [arm64] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted packetsender [s390x] (groovy-proposed) [6.2.6-2]
[17:38] -queuebot:#ubuntu-release- New: accepted gftl-shared [amd64] (groovy-proposed) [1.0.7-1]
[17:38] -queuebot:#ubuntu-release- New: accepted gftl-shared [ppc64el] (groovy-proposed) [1.0.7-1]
[17:38] -queuebot:#ubuntu-release- New: accepted libopenshot [arm64] (groovy-proposed) [0.2.5+dfsg1-2]
[17:38] -queuebot:#ubuntu-release- New: accepted opensaml [arm64] (groovy-proposed) [3.1.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted opensaml [riscv64] (groovy-proposed) [3.1.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted gftl-shared [arm64] (groovy-proposed) [1.0.7-1]
[17:39] -queuebot:#ubuntu-release- New: accepted libopenshot [riscv64] (groovy-proposed) [0.2.5+dfsg1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted gftl-shared [s390x] (groovy-proposed) [1.0.7-1]
[17:39] -queuebot:#ubuntu-release- New: accepted opensaml [armhf] (groovy-proposed) [3.1.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted libopenshot [armhf] (groovy-proposed) [0.2.5+dfsg1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted mplcursors [amd64] (groovy-proposed) [0.3-1]
[17:39] -queuebot:#ubuntu-release- New: accepted nanofilt [ppc64el] (groovy-proposed) [2.6.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted opensaml [ppc64el] (groovy-proposed) [3.1.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-tplink-plug-exporter [ppc64el] (groovy-proposed) [0.2.0+git20200622.cc4a731-1]
[17:39] -queuebot:#ubuntu-release- New: accepted libopenshot [s390x] (groovy-proposed) [0.2.5+dfsg1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted opensaml [amd64] (groovy-proposed) [3.1.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-tplink-plug-exporter [s390x] (groovy-proposed) [0.2.0+git20200622.cc4a731-1]
[17:39] -queuebot:#ubuntu-release- New: accepted nanofilt [amd64] (groovy-proposed) [2.6.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted opensaml [s390x] (groovy-proposed) [3.1.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted nanofilt [s390x] (groovy-proposed) [2.6.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted qdarkstyle [amd64] (groovy-proposed) [2.8.1+ds1-1]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-tplink-plug-exporter [amd64] (groovy-proposed) [0.2.0+git20200622.cc4a731-1]
[17:39] -queuebot:#ubuntu-release- New: accepted qdarkstyle [amd64] (groovy-proposed) [2.8.1+ds1-2]
[17:40] -queuebot:#ubuntu-release- New binary: dnsdbq [arm64] (groovy-proposed/universe) [2.1.1-2] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: audmes [arm64] (groovy-proposed/universe) [0+git20200429-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: dnsdbq [armhf] (groovy-proposed/universe) [2.1.1-2] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: audmes [armhf] (groovy-proposed/universe) [0+git20200429-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: libldac [arm64] (groovy-proposed/universe) [<IP_ADDRESS>+git20180726-1] (no packageset)
[17:42] <RikMills> vorlon LocutusOfBorg with new util-linux in proposed, I amd gettign several build fails with:
[17:42] <RikMills> --   Package 'libcryptsetup', required by 'mount', not found
[17:42] <LocutusOfBorg> mmm interesting
[17:42] -queuebot:#ubuntu-release- New binary: aerc [arm64] (groovy-proposed/universe) [0.3.0-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: dpaste [riscv64] (groovy-proposed/universe) [0.4.0-1] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: aerc [armhf] (groovy-proposed/universe) [0.3.0-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: libldac [armhf] (groovy-proposed/universe) [<IP_ADDRESS>+git20180726-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: audmes [riscv64] (groovy-proposed/universe) [0+git20200429-1] (no packageset)
[17:44] -queuebot:#ubuntu-release- New binary: dpaste [arm64] (groovy-proposed/universe) [0.4.0-1] (no packageset)
[17:45] -queuebot:#ubuntu-release- New binary: aerc [riscv64] (groovy-proposed/universe) [0.3.0-1] (no packageset)
[17:48] <vorlon> RikMills: that's a literal 'libcryptsetup'?  that's clearly the wrong package name :/
[17:49] <RikMills> LocutusOfBorg: libmount-dev should depend on libcryptsetup-dev?
[17:49] <RikMills> vorlon: yeah, less than helpful
[17:50] <RikMills> things that build fine before util-linux pubished to proposed, now fail with that
[17:58] <RikMills> 'Build with libcryptsetup-dev to enable dm-verity (Closes: #951048)'
[17:59] <vorlon> ah
[17:59] <RikMills> so yes, I guess the mount -dev package needs that
[17:59] <vorlon> I can upload the fix
[17:59] <RikMills> ty :)
[17:59] <vorlon> but this means it only impacts things that are using libmount-dev, not the mount package itself, phew
[17:59] -queuebot:#ubuntu-release- New binary: qbs [armhf] (groovy-proposed/universe) [1.16.0-2] (no packageset)
[17:59] <RikMills> yep
[18:01] <vorlon> was fixed in Debian in 2.35.2-6 fwiw
[18:02] <RikMills> ah. nice
[18:10] <RikMills> vorlon: would you perhaps have time to look at plasma-wayland-protocals and kwayland-server in NEW? LP: #1883501 LP: #1884120
[18:10] <RikMills> I cannot land new upstream plasma without those :(
[18:12] -queuebot:#ubuntu-release- New: accepted aerc [riscv64] (groovy-proposed) [0.3.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted dpaste [arm64] (groovy-proposed) [0.4.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted audmes [riscv64] (groovy-proposed) [0+git20200429-1]
[18:12] -queuebot:#ubuntu-release- New: accepted qbs [armhf] (groovy-proposed) [1.16.0-2]
[18:12] <RikMills> Andy Whitcroft was going to try to look this week, but is too busy :/
[18:12] -queuebot:#ubuntu-release- New: accepted aerc [arm64] (groovy-proposed) [0.3.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted audmes [arm64] (groovy-proposed) [0+git20200429-1]
[18:12] -queuebot:#ubuntu-release- New: accepted dnsdbq [arm64] (groovy-proposed) [2.1.1-2]
[18:12] -queuebot:#ubuntu-release- New: accepted dpaste [riscv64] (groovy-proposed) [0.4.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted libldac [armhf] (groovy-proposed) [<IP_ADDRESS>+git20180726-1]
[18:12] -queuebot:#ubuntu-release- New: accepted aerc [armhf] (groovy-proposed) [0.3.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted dnsdbq [armhf] (groovy-proposed) [2.1.1-2]
[18:12] -queuebot:#ubuntu-release- New: accepted audmes [armhf] (groovy-proposed) [0+git20200429-1]
[18:12] -queuebot:#ubuntu-release- New: accepted libldac [arm64] (groovy-proposed) [<IP_ADDRESS>+git20180726-1]
[18:13] -queuebot:#ubuntu-release- New: accepted qbs [amd64] (groovy-proposed) [1.16.0-2]
[18:19] <vorlon> Eickmeyer: why is redkite useful to have in the archive?  It's a GUI toolkit that nothing else in the archive or the NEW queue uses; and the packaging is non-standard, with only a static lib (no shared lib) and named as 'redkite' instead of 'libredkite-dev' as would be expected
[18:27] <vorlon> Eickmeyer: the add64 package description could use some improvement; 'Add64 is the result of my experiments [...]' package descriptions shouldn't be in the first person
[18:28] -queuebot:#ubuntu-release- New: accepted add64 [source] (groovy-proposed) [3.9.3-0ubuntu1]
[18:29] -queuebot:#ubuntu-release- Unapproved: python-oslo.policy (focal-proposed/main) [3.1.0-0ubuntu1 => 3.1.0-0ubuntu1.1] (openstack, ubuntu-server)
[18:35] -queuebot:#ubuntu-release- New binary: add64 [ppc64el] (groovy-proposed/none) [3.9.3-0ubuntu1] (no packageset)
[18:35] -queuebot:#ubuntu-release- New binary: add64 [s390x] (groovy-proposed/none) [3.9.3-0ubuntu1] (no packageset)
[18:39] -queuebot:#ubuntu-release- New binary: add64 [amd64] (groovy-proposed/universe) [3.9.3-0ubuntu1] (no packageset)
[18:40] -queuebot:#ubuntu-release- New binary: add64 [arm64] (groovy-proposed/universe) [3.9.3-0ubuntu1] (no packageset)
[18:41] -queuebot:#ubuntu-release- New binary: add64 [armhf] (groovy-proposed/universe) [3.9.3-0ubuntu1] (no packageset)
[18:54] -queuebot:#ubuntu-release- Unapproved: software-properties (focal-proposed/main) [0.98.9 => <IP_ADDRESS>] (core)
[18:57] -queuebot:#ubuntu-release- New binary: add64 [riscv64] (groovy-proposed/universe) [3.9.3-0ubuntu1] (no packageset)
[19:11] <vorlon> Eickmeyer: in fact, there is a lintian warning about this use of first-person
[19:12] -queuebot:#ubuntu-release- New: accepted add64 [amd64] (groovy-proposed) [3.9.3-0ubuntu1]
[19:12] -queuebot:#ubuntu-release- New: accepted add64 [armhf] (groovy-proposed) [3.9.3-0ubuntu1]
[19:12] -queuebot:#ubuntu-release- New: accepted add64 [s390x] (groovy-proposed) [3.9.3-0ubuntu1]
[19:12] -queuebot:#ubuntu-release- New: accepted add64 [arm64] (groovy-proposed) [3.9.3-0ubuntu1]
[19:12] -queuebot:#ubuntu-release- New: accepted add64 [ppc64el] (groovy-proposed) [3.9.3-0ubuntu1]
[19:13] -queuebot:#ubuntu-release- New: accepted add64 [riscv64] (groovy-proposed) [3.9.3-0ubuntu1]
[19:47] -queuebot:#ubuntu-release- New binary: nginx [s390x] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[19:48] -queuebot:#ubuntu-release- New binary: nginx [ppc64el] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[19:49] -queuebot:#ubuntu-release- New binary: nginx [amd64] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[19:52] -queuebot:#ubuntu-release- New binary: nginx [armhf] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[19:53] -queuebot:#ubuntu-release- New binary: nginx [arm64] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[20:10] <LocutusOfBorg> thanks vorlon for fixing it
[20:37] -queuebot:#ubuntu-release- New binary: nginx [riscv64] (groovy-proposed/main) [1.18.0-3ubuntu1] (ubuntu-server)
[20:38] <ricotz> please retry https://launchpad.net/ubuntu/+source/firefox/78.0+build1-0ubuntu1
[20:39] <ricotz> this got hit by the libmount-dev issue
[20:39] <ricotz> LocutusOfBorg, ^
[20:44] <Eickmeyer> vorlon: redkite is a GUI toolkit that is a prerequisite for another package I'm trying to bring in.
[20:44] <LocutusOfBorg> oh lol already done before looking at irc
[20:44] <Eickmeyer> vorlon: I'll fix Add64, please reject.
[20:44] <LocutusOfBorg> I'm going to give a mass retry
[20:51] <Eickmeyer> vorlon: I didn't get the lintian warning about it, so that surprises me. I do see that you accepted it anyhow. I'll fix with the next verison, it's actively developed.
[20:52] <Eickmeyer> vorlon: As for redkite... should I just rename the binary package as "libredkite-dev"?
[20:53] <Eickmeyer> vorlon: Back to Add64, I maintain the same package in Fedora, so I'm on top of it.
[21:24] <vorlon> Eickmeyer: yes, please name the package libredkite-dev.  What is going to be using redkite?
[21:25] <Eickmeyer> vorlon: A plugin called geonkick which is a kick drum synthesizer-type plugin.
[21:25] <Eickmeyer> Possibly more down the road.
[21:28] <vorlon> ok
[21:43] <seb128> vorlon, hey, to enable an extra package on i386 should we have the discussion on the discourse topic for record purpose etc? or is it fine to just add one directly to the whitelist?
[21:52] -queuebot:#ubuntu-release- New binary: rust-sequoia-openpgp [amd64] (groovy-proposed/universe) [0.17.0-5] (no packageset)
[21:53] -queuebot:#ubuntu-release- New binary: rust-sequoia-openpgp [ppc64el] (groovy-proposed/universe) [0.17.0-5] (no packageset)
[21:56] -queuebot:#ubuntu-release- New binary: rust-sequoia-openpgp [s390x] (groovy-proposed/universe) [0.17.0-5] (no packageset)
[22:00] -queuebot:#ubuntu-release- New binary: cmake-format [amd64] (groovy-proposed/universe) [0.6.10-2] (no packageset)
[22:03] -queuebot:#ubuntu-release- New binary: haskell-xdg-desktop-entry [amd64] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[22:05] -queuebot:#ubuntu-release- New binary: haskell-xdg-desktop-entry [ppc64el] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[22:09] <seb128> vorlon, I'm about to drop for the day but I was asking for gamemode (https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1883253/comments/3), if you reply here I will read the log tomorrow
[22:13] <seb128> (using that bug ^ would also work to discuss the topic)
[22:13] <seb128> but calling it a day for now, night
[22:17] -queuebot:#ubuntu-release- New binary: haskell-xdg-desktop-entry [arm64] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[22:17] -queuebot:#ubuntu-release- New binary: haskell-xdg-desktop-entry [armhf] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[22:18] -queuebot:#ubuntu-release- New binary: haskell-xdg-desktop-entry [s390x] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[23:42] <Eickmeyer> vorlon: Were you going to reject redkit?
[23:43] <Eickmeyer> *redkite
[23:56] <vorlon> Eickmeyer: I'll reject the current one due to the binary package name, yes
[23:56] <Eickmeyer> vorlon: Ok. I'll ask teward to upload a new version that's already fixed in git.
[23:58] -queuebot:#ubuntu-release- New: rejected redkite [source] (groovy-proposed) [0.8.1-0ubuntu1]
[23:58] <teward> Eickmeyer: dont expect any movement until the weekend on it from me.  Busy with stuff at the apartment tomorrow all day and not online
[23:58] <teward> (took a work day off too heh)
[23:59] <Eickmeyer> teward: Thats's OK.


[09:10] <Unit193> bluesabre: Dowh, #x
[09:13] <Unit193> (IOW, Xfce bug 13422 sounds fun.)
[10:38] <knome> xubuntu.org, www.xubuntu.org, xubuntu.com and www.xubuntu.com should now all redirect to https://xubuntu.org/
[10:39] <knome> if you notice any weirdness, ping me
[10:39] <Unit193> \o/
[10:39] <knome> (and i'll take the info further)
[10:39] <knome> next up is let's encrypt for our subdomains
[10:39] <Unit193> Gogo StartCom! :--D
[10:40] <knome> convince pleia2 if you feel like one is better than the other
[10:41] <Unit193> (I'm kidding, that's now generally untrusted.)
[10:41] <knome> ok, then sounds like our thing! (:
[10:45] <knome> pleia2, bug 1682797 for your convenience
[10:45] <knome> should set up the dev tracker too
[10:46] <knome> hmm.
[10:46] <knome> that means i should know my password.
[10:47] <Unit193> Well I don't!
[10:47] <knome> me neither...
[10:47] <Unit193> Also, I've seen a few tracker nicks drop in here, but only ones saying anything (that I remember or saw) were team members testing or playing.
[10:47] <knome> yep
[10:48] <knome> euuuuugghh.
[10:58] <knome> https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-a-roadmap is the new umbrella
[10:58] <knome> will be setting up other stuff later today
[11:03] <Unit193> [xubuntu-doc] Move lp:xubuntu-website/docs-startpage as a build target for xubuntu-docs: TODO  heh.
[11:04] <knome> yeah no.
[11:11] <knome> ok, i've also set up the sub-blueprints
[11:11] <knome> now to link them to the main one too
[11:12] <knome> done
[11:13] <knome> now to send a mail about this...
[11:13] <Unit193> I already got the emails.
[11:13] <knome> !conga-rats
[11:15] <knome> done
[11:17] <knome> time to get on with other things
[11:17] <knome> on and off for a while, then gone
[11:17] <knome> o/
[17:03] <pleia2> knome: thanks, I'll look into it in a bit


[05:24] <mborzecki> morning
[05:47] <mborzecki> mvo: is it equally hot at your location? it's ~8am and 26 degrees in the shade
[05:49] <mvo> mborzecki: its overcast here today so not hot yet
[05:49] <mvo> mborzecki: we had this last week :/
[07:02] <pstolowski> mornings
[07:05] <mvo> hey pstolowski
[07:18] <jamesh> pstolowski: hi.  I ran into a transient unit test failure in the "snap snapshot" tests, and it looks like you've had most involvement in them.  I filed https://bugs.launchpad.net/snapd/+bug/1832161 with the details
[07:18] <jamesh> seems like the regexp should be adjusted to account for different amounts of white space
[07:20] <pstolowski> jamesh: hi! thanks for the report, will investigate
[07:57] <mborzecki> pstolowski: hey
[08:00] <pstolowski> jamesh: https://github.com/snapcore/snapd/pull/6982 should fix i
[08:00] <pstolowski> *it
[08:18] <lss8> is there now a way to disable automatic snap update checks? I'd like to not auto update my snaps as I want to have control over my system and don't need automated updates
[08:18] <lss8> Chipaca ^updates could introduce security issues or there might be malicious updates which I don't want to automatically apply to my stable system
[08:21] <Chipaca> lss8: it seems like a rather poor strawman to me, if you trust the thing enough to install it, you trust it to refresh -- for any case where an update has introduced new vulnerabilities, there have been many that removed them
[08:22] <Chipaca> lss8: unless as I say you're vetting for a large fleet of devices in which case fair enough and there are tools for that
[08:22] <pstolowski> mborzecki: one question to #6980
[08:23] <Chipaca> lss8: for a single device, even for a small handful, you won't have a person full-time vetting things
[08:23] <lss8> Chipaca those are my personal servers and I do have time to run `snap refresh lxd` every once in a while
[08:23] <Chipaca> lss8: at which point you're arguing that existing, known security vulnerabilities are safer than unknown new ones
[08:24] <lss8> I just don't want LXD to update itself when the current release is perfectly stable for me
[08:24] <Chipaca> lss8: you can control when the refresh happens, and how often
[08:24] <Chipaca> lss8: you cannot turn it off
[08:24] <lss8> but.. there's no way to completely turn it off?
[08:24] <Chipaca> lss8: there is no way to opt in to being part of a botnet, no
[08:36] <Chipaca> I wish the forum would close topics after a couple of months of inactivity
[08:37] <Chipaca> six months later "I'm getting the same error: <a completely different error that shares one word (probably "the") with the original>"
[08:41] <jamesh> Chipaca: I think https://github.com/snapcore/snapd/pull/6954 is mostly ready.  It ballooned in size a bit adding the Ubuntu Core support though.  I could split that out into a separate PR pretty easily though by cutting off the final four commits
[08:41] <Chipaca> jamesh: I need to circle back to some reviews, yes, sorry for my delay
[08:41] <Chipaca> jamesh: I'll take a look and let you know, re splitting
[08:43] <jamesh> the Ubuntu Core support mainly involved installing the new unit files on core18 systems
[08:50] <pstolowski> Chipaca: hey, do you have a moment for https://github.com/snapcore/snapd/pull/6982 ?
[08:52] <Chipaca> pstolowski: sure
[08:58] <pstolowski> Chipaca: ty!
[09:17] <mborzecki> Chipaca: by the looks of it manjaro forums does close the topics after 90 days of inactivity, so maybe it's a configuration option or a feature of some newer version of discourse?
[09:26] <Chipaca> mborzecki: sadly I am only a moderator, not an admin
[09:27] <mborzecki> Chipaca: mhm, i know
[09:28] <mborzecki> Chipaca: looks like discourse https://forum.manjaro.org/t/snapd-is-not-working-since-downgrade-to-systemd-239-6-2-2-advised-in-the-security-update-on-2019-01-19/73774/37 doesn't it?
[09:30] <mborzecki> ha found the exact version even among <meta> tags: Discourse 2.3.0.beta11 - https://github.com/discourse/discourse version ace6ce046273799c866e85942182db7d77bed4d2
[09:30] <mborzecki> we use: Discourse 2.0.0.beta10 - https://github.com/discourse/discourse version 30fbf6fe8181426ff8cab81d10a26c61f635f4d6
[09:33] <jamesh> the downside of closing old topics is that people end up needing to start new topics about the same thing that lose all context from the old discussion
[09:34] <jamesh> it's not always a new user incorrectly diagnosing their bug
[09:34] <Chipaca> jamesh: true, and I may just be noticing the bad ones
[09:52]  * Chipaca brb
[11:20] <zyga> Good morning
[12:21] <pstolowski> hey zyga
[12:35] <Chipaca> #6958 could use another review
[12:52] <zyga> hey pawel  :)
[12:52] <zyga> how are you guys doing?
[12:56] <pstolowski> zyga: the weather is unbearable here, i envy you ;)
[13:29] <zyga> pstolowski: 16C
[13:31] <Chipaca> mvo: I just realied I should've reopened #6582 and targeted it to 2.40; done that now (pending rob's confirmation)
[13:33] <mvo> Chipaca: ok
[13:41] <zyga> pstolowski: and it rains
[13:41] <mvo> zyga: hey, how are you? how is the summit
[13:42] <zyga> pstolowski: I kind of wish it would be not raining so much because the hotel keeps us hostage
[13:42] <zyga> mvo: hey, good morning!
[14:00] <mborzecki> pstolowski: it's getting worse https://i.imgur.com/6MJHkqC.jpg
[14:01] <pstolowski> omg
[14:06] <Chipaca> pedronis, mvo: https://paste.ubuntu.com/p/BCXRzjcX5V/
[14:07] <Chipaca> magic
[14:13] <cachio> mborzecki, pstolowski you feel like me now
[14:13] <pstolowski> cachio: :)
[14:33]  * cachio afk
[14:36] <diddledan> update on centos  : "Job for var-lib-snapd-snap-core-6964.mount failed." See $insert-log-message-checking-message-here - updating 2.38.1 to 2.39.1
[14:42] <mvo> Chipaca: heh
[14:47] <mborzecki> diddledan: that's when the rpm snippets ran right?
[14:48] <mborzecki> diddledan: keep in mind you need to reboot after the update
[15:04] <zyga> mborzecki: o m g
[15:04] <zyga> 41C
[15:07] <mvo> zyga: where?
[15:07] <zyga> mvo: in pl
[15:11] <diddledan> thanks mborzecki
[15:14]  * Chipaca takes a break
[15:14]  * Chipaca does not miss 41°C weather
[18:15] <diddledan> is this a bug? devmode classic confinement snaps seemingly don't inherit environment variables from the calling shell while in stable they do
[18:36]  * cachio afk


[12:25] <bittin> https://www.youtube.com/watch?v=CBPefa0Ckq8 Ubuntu Q&A now
[14:41] <tomreyn> bittin: do you know what happened last time you posted conference links all over the place?
[14:41] <bittin> nope?
[14:44] <tomreyn> you got banned. if needed, this can be repeated.
[14:44] <bittin> sorry


[00:06] <mup> Bug #1532359 opened: intermittant test failure in TestStaticIPAddressManager.test_update_leases_handles_multiple_empty_ips <MAAS:New for lamont> <https://launchpad.net/bugs/1532359>
[20:48] <mup> Bug #1532478 opened: Can't add SM15K chassis - can't input management IP address of SM15k <oil> <MAAS:New> <https://launchpad.net/bugs/1532478>
[20:48] <mup> Bug #1532479 opened: Adding a SM15k node manually is requesting ipmitool package to be installed <oil> <MAAS:New> <https://launchpad.net/bugs/1532479>
[20:51] <mup> Bug #1532478 changed: Can't add SM15K chassis - can't input management IP address of SM15k <oil> <MAAS:New> <https://launchpad.net/bugs/1532478>
[20:51] <mup> Bug #1532479 changed: Adding a SM15k node manually is requesting ipmitool package to be installed <oil> <MAAS:New> <https://launchpad.net/bugs/1532479>
[20:55] <mup> Bug #1532478 opened: Can't add SM15K chassis - can't input management IP address of SM15k <oil> <MAAS:New> <https://launchpad.net/bugs/1532478>
[20:55] <mup> Bug #1532479 opened: Adding a SM15k node manually is requesting ipmitool package to be installed <oil> <MAAS:New> <https://launchpad.net/bugs/1532479>


[01:02] <tempubun> hi are there any ubuntu-ppc wizards/clever types here? my iBook is driving me insane with startx issues
[01:16] <tempubun> have checked xorg.conf carefully, re-ran dkpg-reconfigure xserver-xorg, checked for known ATI Rage issues, X still fails with signal 11, fatal server errors.
[01:18] <tempubun> the main error is "invalid io allocation", any suggestions?
[01:42] <tempubun> fixed, in /etc/X11/xorg.conf, set => Option "UseFBDev" "true" to "false", booted right up after that, happy me
[01:43] <pochu> tempubun: nice :)
[01:43] <tempubun> indeed
[01:43] <tempubun> i found the answer in the ubuntu-ppc forum hidden away as a reply to a similar fault on a different machine
[01:44] <tempubun> if that makes any sense ... pity that ubuntu will doscontinue support for ubuntu-ppc in 2008
[01:49] <pochu> tempubun: with dapper, yeah
[01:49] <pochu> but not with feisty
[01:50] <tempubun> so, feisty fawn will still have PPC support?
[01:50] <pochu> tempubun: ups, I think I've misunderstood you
[01:50] <tempubun> cos the way it reads in the community, there will be *no* future support of PPC by ubuntu, at all
[01:51] <pochu> tempubun: no, feisty won't support _officially_ PPC
[01:51] <pochu> but it will be supported by the community
[01:51] <tempubun> k, right, hmm that is a shame, cos ubuntu is the ducks guts as far as i am concerned and PPC is a good platform
[01:51] <tempubun> i was exclusively pclinux but not anymore
[02:36] <tempubun> anyone know a good and safe method of cleaning an apple iBook keyboard?
[02:53] <defendguin> i went through 2 weeks ago and submitted a few bugs and i haven't had any responses yet
[02:58] <tempubun> k, contact someone in the bug team
[03:02] <defendguin> i could do that
[03:24] <defendguin> some aren't even getting triaged
[04:23] <tempubun> does anyone know if the G3 iBook takes special laptop ram sticks?
[05:50] <bjoyce> hello
[06:25] <oranged> good day
[06:27] <oranged> just wondering if anyone knows the status of some drivers for the 'other' toshiba laptops ;)
[06:27] <oranged> the ones with the phoenix bios
[11:20] <mixandgo> hello, does suspend to ram work in edgy ? I get a black screen and freeze on resume
[11:21] <crimsun> Works For Me
[11:21] <mixandgo> crimsun, did you do anything special ?
[11:22] <crimsun> yes, I need POST_VIDEO=false in /etc/default/acpi-support
[11:22] <mixandgo> hmm...
[11:22] <crimsun> this is an i915GM
[11:23] <crimsun> [https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX41-2527 ]
[11:23] <mixandgo> I've got nvidia
[11:27] <mixandgo> crimsun, do I need to restart something after I make a change in acpi-suport ?
[11:32] <crimsun> I've always just rebooted
[11:41] <mixandgo> hmmm... I managed to resume just now
[11:41] <mixandgo> by putting that VBE thingy to flase


[09:40] <Dazev> Hi, one question, is mir to stay or is the ubuntu team switching to wayland with the 18.04 release?
[13:32] <tsdgeos> was a pleasure working for Canonical! /me waves


[04:56] <oneunderthesun> hello world?
[08:37] <Derf_the> Hello all, I have a 'desktop' that is locked -ignores mouse clicks- and will only show the wallpaper, no files are displayed. When I look at the file "desktop" using a file manager everything is still there.  The permissions are the standard 755's and this behaviour was unchanged by the upgradeing from U8.04 to U8.10.  Any hints as to how to get back to normal? [on a HP8510w]
[18:56] <maco> hey, i'm trying to update a help file in Seahorse, but i'm not sure how many of the files I need to touch.  there's no .pot, so do i need to update the message id's in every .po file?


[07:10] <alkisg> Hi, upgrading Trusty on i386, I got: installing libtxc-dxtn-s2tc0:i386 (0~git20131104-1) ...
[07:10] <alkisg> update-alternatives: error: alternative path /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0 doesn't exist
[07:12] <alkisg> I worked around it by symlinking the dir it's searching for, but it's probably wrong and needs to be changed...
[07:12] <alkisg> root@server:/usr/lib# ln -s i386-linux-gnu/ x86_64-linux-gnu
[10:25] <zyga> hi, what is the delay between a new package hitting Debian unstable and it showing up in Ubuntu?
[10:25] <zyga> I have a package that is in Debian now, I can find it in the ubuntu package pool but I cannot see it in any of the apt indices
[10:25] <zyga> the package in question is plainbox
[10:42] <pjotr> Hello, I'd like to file a bug but I don't know against which package.
[10:42] <pjotr> The bug is this: power management for the wireless chipset often causes slow, laggy or unresponsive wireless internet. So I always turn it off like this: https://sites.google.com/site/easylinuxtipsproject/internet#TOC-Disable-power-management-for-the-wireless-card (item 2.1, right column)
[10:43] <pjotr> But I think it would be better if power management for the wireless chipset, would be off by default. Against which package can I file this bug?
[10:44] <pjotr> cjwatson: maybe you know against which package I can file this bug?
[11:27] <cjwatson> zyga: plainbox is in Ubuntu now, it just had to go through NEW.  You're better off checking Launchpad than apt, as a rule.  The delay is typically no more than twelve hours or so
[11:35] <zyga> cjwatson: so ubuntu has NEW just like debian? I didn't know that
[11:35] <zyga> cjwatson: where can I find this on launchpad?
[11:35] <cjwatson> zyga: of course
[11:35] <geser> zyga: https://launchpad.net/ubuntu/saucy/+queue
[11:36] <cjwatson> zyga: https://launchpad.net/ubuntu/+source/<source package name>
[11:36] <zyga> aahhh
[11:36] <cjwatson> (in this case it was binary NEW so it will show up under the source)
[11:36] <zyga> one learns something new every day :)
[11:36] <cjwatson> (As well)
[11:36] <zyga> thanks :)
[11:36] <cjwatson> NEW for syncs gets waved through fairly rapidly as a rule, others may wait longer
[11:36] <cjwatson> geser: wrong series, too
[11:37]  * zyga feels that launchpad has lots of hidden, magic URLs
[11:37] <geser> cjwatson: thanks for reminding me to update my bookmark :)
[11:38] <cjwatson> zyga: https://launchpad.net/ubuntu/+source/<source package name> should be in every Ubuntu developer's browser configuration via a smart bookmark or whatever you prefer, IMO
[11:38] <zyga> woot, my first package in Ubuntu through Debian :)
[11:41] <zyga> cjwatson: I think that the proliferation of PPAs lessens the incentive to get into the core distribution so many people don't know about things like that
[11:42] <zyga> cjwatson: what made plainbox go to main instead of to universe?
[11:42] <zyga> ah, I take it back
[11:42] <cjwatson> zyga: it didn't
[11:42] <zyga> why is component main in one of the fields
[11:42] <zyga> ?
[11:43] <cjwatson> zyga: that's just quoting the Debian component
[11:43] <zyga> ah, ok
[11:43] <cjwatson> "these are just the package defaults" as the small print explains
[11:43] <zyga> cjwatson: since that packge has autopkg tests, will it automatically get tested in ci.ubuntu.com?
[11:43] <cjwatson> I assume so
[11:44] <cjwatson> https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-plainbox/
[11:44]  * zyga needs to file main inclusion request
[11:45] <zyga> oho
[11:45] <zyga> I see a small failure in adt scripts!
[11:45] <zyga> nice
[11:46]  * zyga goes to correct that
[11:46] <zyga> cjwatson: do you know if Debian has adt support?
[11:56] <cjwatson> zyga: people have been working on it but I don't *think* jobs are being automatically run as yet.  They'll probably end up on http://jenkins.debian.net/ if they are
[15:14] <xnox> zyga: i use http://pad.lv/u/<source package name>, more shortcuts at http://pad.lv/ it's not an official service run by launchpad, but it is quite handy.
[17:53] <arun__> guys, which kernel is the best?
[18:22] <xnox> NT
[18:22] <dobey> arun__: the one that works
[18:23] <nemo> so. the worrying error on installing blcr-dkms on a VM post-13.10 - is that a serious issue or not?
[18:23] <nemo> or just some random .deb prob that I can ignore?
[18:23] <arun__> dobey: which would be the best for a distro?
[18:28] <zyga> xnox: thanks for the tip, is there a list of shortcuts that it provides?
[18:29] <xnox> zyga: yeah, on the top page http://pad.lv
[18:51]  * zyga looks


[10:42] <ybon> popey: ping
[10:48] <twstddev>  Guys, does anybody experience troubles running the core applications in emulator after upgrading all system packages to the most recent ones? Creator creates packages for arm instead of i386.
[11:31] <popey> ybon: pong
[11:31] <ybon> :)
[11:31] <popey> ybon: tested the app last night and saw an odd effect
[11:31] <ybon> oh
[11:31] <ybon> tell me
[11:31] <popey> couldn't get a photo last night, dunno if it's your app or qt or what
[11:31] <ybon> (I've made some changes btw, do you want an updated click?)
[11:31] <popey> basically launched your app, but could see some artifacts on the screen
[11:31] <ybon> a photo?
[11:31] <popey> like the black ring  of the camera app icon
[11:32] <popey> like things were burned into the screen
[11:32] <popey> let me try again now I'm home
[11:32] <ybon> wow
[11:32] <ybon> never seen that
[11:33] <popey> right, do this.
[11:33] <popey> 1. open osm touch, 2. switch back to dash, 3. swipe back to osm touch directly from the dash. 4. Move map around.
[11:33] <popey> in the white (unpainted) areas of the map you can see reminants of the icons that are in the dash, like the black lens ring of the camera
[11:34] <ybon> oh
[11:34] <ybon> now I see what you mean
[11:34] <ybon> that a bug on QtLocation (one more)
[11:34] <ybon> it doesn't paint the background
[11:34] <popey> ahh
[11:34] <ybon> and there is no way to add a rectangle or whatever
[11:35] <ybon> it's already the case on the current version, btw
[11:35] <popey> ok
[11:35] <popey> how is this a bug in qtlocation?
[11:35] <popey> is it filed upstream?
[11:35] <ybon> it's the map that bugs
[11:35] <ybon> I don't know where to fill QtLocation bugs
[11:36] <ybon> I mean, a place to file them where someone will look at them
[11:36] <ybon> there are a bunch
[11:36] <ybon> like double-tap to zoom that doesn't work
[11:37] <ybon> no way to add mouse event on the map
[11:37] <ybon> no way to have device rotation working
[11:37] <popey> I'd be filing them upstream in the qt bug tracker.
[11:37] <popey> https://bugreports.qt-project.org
[11:38] <ybon> https://www.wetransfer.com/downloads/7f727eb98ac5dbecd1bb65d227677d1520140824113533/ad54a397fb9dee0e97b5c894e14197e920140824113533/3ec3d6 this is latest version, with some changes last night if you wanna have a look
[11:38] <ybon> oh, let me check this bug tracker
[11:42] <ybon> the thing is that I don't know if the issue is on Qt side or on our UT implementation :s
[11:46] <popey> k
[11:46] <popey> ybon: well, good question. could file a bug in launchpad and link to upstream bug
[11:48] <ybon> popey: I've made one some days ago https://bugs.launchpad.net/ubuntu/+source/qtlocation-opensource-src/+bug/1355459 but for now it doesn't have any answer
[11:48] <ybon> so I'm not sure it's the place to add more
[11:49] <ybon> on Qt bug tracker issues are quite old https://bugreports.qt-project.org/browse/QTMOBILITY-866
[11:50] <ybon> it seems to me that QtLocation is a planet with no galaxy
[11:50] <popey> hah
[11:50] <ybon> each time I try to understand who maintains this, I end lost in the black ;)
[11:52]  * popey goes to do his chores
[11:55] <ybon> this one seems a good summary of the situation https://bugreports.qt-project.org/browse/QTMOBILITY-1116 :p
[11:56] <ybon> "Rumor has it that MeeGo Harmattan has an QtLocation offline map plugin in a experimental repository."
[12:02] <ybon> nik90: ping
[12:02] <nik90> ybon: pong
[12:02] <ybon> :)
[12:03] <ybon> I'm about to release a new version of OSMTouch, I guess something need to be done on the debian/ part?
[12:03] <nik90> well with the new headers you drop support of trusty
[12:03] <nik90> so you will have to release it for utopic
[12:05] <ybon> humm, ok
[12:06] <ybon> maybe I will need your help, I've never played with that
[12:09] <ybon> nik90: also, any feedback on the version you tested yesterday? :)
[12:10] <ybon> And if anyone else want to test it before release https://www.wetransfer.com/downloads/7f727eb98ac5dbecd1bb65d227677d1520140824113533/ad54a397fb9dee0e97b5c894e14197e920140824113533/3ec3d6 is the last version
[12:10] <daker> mzanetti: dash locked again :D
[12:10] <nik90> it is pretty nice.. much better ui in my opinion.
[12:10] <ybon> I agree :)
[12:10] <nik90> I like the icons used, I will have to do some more testing
[12:10] <ybon> I've now switched (yesterday night) the popup to pages
[12:11] <ybon> so when you click on a POI marker it pushes a page on the stack
[12:11] <ybon> I think it's more fluid this way
[12:11] <ybon> Have you tested the bottom edge?
[12:12] <nik90> yup I did
[12:12] <ybon> cool
[12:12] <nik90> I have one suggestion
[12:12] <ybon> tell me
[12:13] <nik90> when you press the search icon, rather than show a blank page, may be it would be cool to show a 80% opaque rectangle over the current map and show results in that rectangle
[12:13] <nik90> kinda like an overlay above it
[12:14] <nik90> I am not fully sure how it would feel yet, but just an idea to experiment on
[12:14] <nik90> maybe it might break consistency with the other pages like the bottomedge
[12:14] <daker> wow 5days without charging and the battery is still 16% :D
[12:16] <ybon> nik90: I take note, I will make some tests
[12:16] <ybon> nik90: in the next version, I will add autocomplete
[12:16] <ybon> (with Photon)
[12:17] <ybon> so at this point, the seach field will only be a state of the header
[12:17] <nik90> ooh cool
[12:59] <jan> hi
[12:59] <jan> i have a question can someone help me?
[14:05] <rpadovani> Hey :-) Does anyone tried the new connectivity api on utopic desktop?
[14:35] <nik90> rpadovani: Hey, I haven't tried it yet. Why something not working as expected?
[14:35] <rpadovani> nik90, well, on computer doesn't work at all, I have to try on phone
[14:35] <nik90> rpadovani: may be you are missing the package it requires (not sure which one)
[14:36] <rpadovani> nik90, nope, it's qml-module-ubuntu-connectivity and I have installed it
[14:37] <nik90> oh ok


[13:26] <ahasenack> tjaalton: hi, around?
[13:27] <ahasenack> tjaalton: I saw that the freeipa dep8 tests errors are ignored now, in the test itself. I guess the intention is to not have it block other packages
[13:27] <tjaalton> ahasenack: yes
[13:28] <ahasenack> tjaalton: I'm working on fixing the samba+winbind startup issue, for now I'm trying to remove winbind from the test as it's not used, but I saw in catalina.out what looks like another problem:
[13:28] <ahasenack> Caused by: java.lang.UnsupportedClassVersionError: org/mozilla/jss/ssl/SSLSocketListener has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
[13:28] <ahasenack> does that ring a bell?
[13:28] <tjaalton> where's this from?
[13:28] <ahasenack> tjaalton: /var/log/pki/pki-tomcat/catalina.out
[13:29] <tjaalton> ah, you have the fresh libjss-java?
[13:29] <ahasenack> tjaalton: the test run fails like this: https://pastebin.ubuntu.com/p/gs26bM4F8Y/
[13:29] <tjaalton> which builds with jdk11 now
[13:29] <ahasenack> tjaalton: it's disco, I might
[13:29] <tjaalton> 4.5.1-1
[13:29] <ahasenack> yes, that one
[13:30] <tjaalton> dogtag itself needs to be fixed, it'll take a while until new resteasy3.0 with jackson2 provider is available (just uploaded it)
[13:30] <tjaalton> after that dogtag 10.6.8 should be fine, and I've fixed it to build with jdk11
[13:31] <tjaalton> now checking resteasy 3.6.2 if it can replace src:resteasy3.0..
[13:32] <ahasenack> tjaalton: as a workaround for the samba+winbind issue, my intention was to replace the test depends on "@" to a list of packages that excludes freeipa-server-trust-ad, which is what pulls winbind in
[13:33] <ahasenack> but I can't verify that the freeipa tests still run correctly because of the issue I pointed out above
[13:33] <tjaalton> the freeipa test isn't blocking samba, if that's what you're after
[13:33] <ahasenack> it is becuse samba's postinst fails when winbind is running
[13:33] <tjaalton> oh right
[13:33] <ahasenack> it's a samba bug
[13:34] <tjaalton> meh
[13:34] <ahasenack> https://pastebin.ubuntu.com/p/Yc4WPKxQXd/ is what I have, that doesn't trigger the samba bug
[13:34] <tjaalton> yeah that's fine, the ad stuff isn't used there anyway
[13:35] <ahasenack> that installs these packages: https://pastebin.ubuntu.com/p/8GTNNYjVnQ/
[13:35] <ahasenack> we don't get freeipa-tests
[13:35] <tjaalton> that's fine
[13:36] <ahasenack> ok
[13:36] <tjaalton> it's purpose is somewhat unclear to me anyway :)
[13:36] <tjaalton> upstream doesn't use it either
[13:36] <tjaalton> so might just as well drop it, maybe
[13:38] <ahasenack> tjaalton: I'll proposed this: https://pastebin.ubuntu.com/p/vnntfcNWwV/
[13:39] <tjaalton> upload away
[13:39] <ahasenack> I got some comments from<EMAIL_ADDRESS>(Alexander) on that issue, but no changes yet
[13:40] <tjaalton> ok
[13:40] <ahasenack> there is a lot of confusion, people see "winbind is running, this must be security = ad or = domain"
[13:58] <doko> didrocks: MIR team meeting
[14:55] <doko> tjaalton: dogtag-pki autopkg tests timing out on amd64, triggered by openjdk-8. could you have a look?
[14:55] <tjaalton> doko: it's WIP, migrating to jdk11
[14:55] <tjaalton> jss migrated, that's causing the timeout
[14:56] <doko> ta
[14:56] <ddstreet> xnox for systemd uploads, do you prefer to check patches into your ubuntu-core-dev systemd repo before a systemd patched pkg is uploaded to the queue?  or do you keep the systemd git up to date after the systemd pkg is sent to -updates?
[14:56] <ddstreet> also thnx for updating disco for the systemd dns bug
[14:57] <xnox> ddstreet, by the time it lands -updates, it's useless, as sru team need access to git repository to review the diff before accepting from unaprooved.
[14:57] <xnox> ddstreet, i'm not sure what your actual question is, but i suspect is that what you really want to know is that no actions are currently needed from you.
[14:58] <ddstreet> xnox i'm asking for future systemd sru uploads, should i instead bug you (or some other core dev) to push the patch into your git before I upload the systemd sru pkg
[14:58] <xnox> ddstreet, as there is a new systemd upload in cosmic unapproved queue with your edns patch; among 6 other bugs
[14:58] <xnox> ddstreet, and bionic is currently blocked on validating snapd specific changes, thus i'm not uploading anything there.
[14:58] <ddstreet> yep thnx for that - this was a question for future systemd sru uploads
[14:58] <xnox> ddstreet, it depends.
[14:59] <xnox> ddstreet, single-patch small srus can go in, however. the larger multi-bug srus have been "hard to review" by the sru team, thus I'm trying to present/show my work in one change per git commit linear format.
[14:59] <ddstreet> ah that makes sense sure
[14:59] <ddstreet> thanks
[15:00] <xnox> ddstreet, for non-urgent things, or staging things whilst there is an existing upload in proposed, git works great for that.
[15:01] <xnox> ddstreet, in general =) i'm very happy about anyone doing systemd work ;-) as long as it gets done from start to finish, and not like leave autopkgtest regressions in security uploads and the like ;-)
[15:01] <xnox> (and however they like)
[15:01] <xnox> and i try to minimize the amount of "boring" stuff they might need to do, after the hard part of figuring out what to fix is done.
[15:03] <ddstreet> xnox much thnx for all your systemd fixing and especially for helping me (and others on my team) apply fixes :)
[15:24] <brainwash> doko: please look into this packaging issue bug 1805197
[15:24] <brainwash> doko: comment #7
[15:43] <dijuremo> Hi, where would be the best place to get some help with Ubuntu 18.04 and grub problems. Seems like the grub package released with 18.04 does *not* have built-in XFS support.
[15:45] <nacc> dijuremo: you want #ubuntu, afaict (support, not development)
[15:48] <TJ-> dijuremo: are your referring to the UEFI signed version?
[15:49] <nacc> dijuremo: if so, it's LP: #1652822
[15:51] <dijuremo> #ubuntu was not helpful at all... :(
[15:52] <dijuremo> Yep, so pretty much I had found that bug, but is there a workaround? I am not so knowledgeable of grub
[15:53] <nacc> dijuremo: that bug lists some workarounds
[15:54] <nacc> cyphermox: --^ do yo uknow?
[15:54] <dijuremo> Do note that bug was opened 2016-12-27, so nothing really has happened in a long time...
[15:54] <dijuremo> The workarounds are *not* permanent, after any kernel install they require manual intervention
[15:55] <nacc> dijuremo: i never said they were?
[15:57] <dijuremo> nacc: I wanted to stick to XFS over ext4, guess this bug and stupid Dropbox are forcing me to change.
[15:57] <nacc> dijuremo: i mean you can do the workaround until the bug is fixed. It looks like Debian has fixed it
[15:59] <cyphermox> xfs is indeed not in the prebuilt grub uefi image
[15:59] <nacc> cyphermox: thanks for confirming
[16:13] <cjwatson> dijuremo: When you say "nothing has happened", I fixed that bug in Debian a bit over a month ago.  Just needs merging (although of course updating a stable release requires more care)
[16:21] <cyphermox> cjwatson: yup, will do soonish
[16:21] <cjwatson> Yep, not a nag :)
[16:21] <nacc> cjwatson: cyphermox: thanks!
[16:23] <cyphermox> :)
[17:01] <dijuremo> nacc: Cannot really do the workaround to deploy hudnreds of machine and risk an update breaking them all...
[17:19] <gQuigs> ubuntu minimal c loud images have grown a lot in cosmic/disco (http://cloud-images.ubuntu.com/minimal/daily/disco/20181129/) - seems to be the inclusion of snap:core/snap:lxd..   is that an intentional change?
[17:20] <rbasak> fginther: ^
[17:24] <nacc> dijuremo: understood
[17:34] <ahasenack> gQuigs: oldest one is http://cloud-images.ubuntu.com/minimal/daily/disco/20181129/ and shows 289M, do you know what the size was before?
[17:35] <gQuigs> ahasenack: just look at bionic - http://cloud-images.ubuntu.com/minimal/daily/bionic/current/
[17:37] <ahasenack> ok, so it's a comparison between distros, I thought initially it was a bump during the development cycle of disco
[17:42] <gQuigs> I think it may have happened during cosmic
[17:42] <gQuigs> dev
[17:43] <Odd_Bloke> gQuigs: rbasak: ahasenack: The increase in minimal image size is due to lxd migrating from a deb to a snap, which did indeed happen during the cosmic development cycle.
[17:57] <gQuigs> can we drop lxd from the minimal image?  it's not really minimal with it...   (report a bug here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/ ?)
[18:05] <Odd_Bloke> gQuigs: Please do report a bug, against the cloud-images project.
[18:05] <Odd_Bloke> gQuigs: https://bugs.launchpad.net/cloud-images/+filebug
[18:13] <gQuigs> will do, ty
[18:47] <gQuigs> reported -https://bugs.launchpad.net/cloud-images/+bug/1806752