[00:37] <Laney> broder: bet you're happy about UDS :-)
[00:38] <broder> i was initially disappointed about not getting to travel, but i'm over it now and pretty stoked
[00:38] <Laney> tour guide hat at the ready
[00:38] <broder> yep
[02:22] <ScottK> Be careful where you tour in Oakland.  You may not come back.
[02:29] <nigelb> Heh
[02:42] <broder> psh. it's cool - the hotel is right by the bart station, so the temptation to go into oakland is minimal
[02:44] <ScottK> That would be true BART station or not.
[04:31] <ScottK> broder: If you're still around, would you please sync unbound from unstable for me?
[05:21] <micahg> ScottK: I can sync unbound for you if you like
[05:21] <ScottK> micahg: Yes. Please.  syncpackage isn't working for me.
[05:21] <ScottK> I'm about to have a mess of security debdiffs too.
[05:22] <micahg> ScottK: well, I'll add this sync to that bug you opened so it has everything
[05:22] <ScottK> micahg: Great.  It's CVE-2011-4528
[05:22] <ScottK> Urg.
[05:22] <ScottK> Bug 907983
[05:28] <micahg> ScottK: done
[05:28] <ScottK> Thanks.
[05:28] <micahg> sorry, I haven't updated ubuntu-dev-tools to the version where it says in the bug who it's sponsored for
[05:28] <micahg> but you're in the precise-changes mail
[05:29]  * micahg knows you don't care about the paperwork :)
[05:30] <ScottK> No.
[05:30] <ScottK> But if you want to make it up to me you can upload the fix for lucid-security.
[05:31] <ScottK> (debdiff in the bug)
[05:31] <micahg> last time I tried that, I killed several hours and still didn't get it done, I"ll try to get someone to look at it in the morning though
[05:32] <ScottK> Thanks.
[05:43] <ScottK> micahg: If you have time, I'd appreciate it if you could look at oneiric for unbound.  There's a configure error where it can't find the python headers and I've no idea why (I think I'm just too tired)
[05:44] <micahg> ScottK: ok, will see if I have time
[05:44] <ScottK> Thanks.
[06:03] <micahg> ScottK: looks like a missing build-dep, works fine on a live system
[06:03] <ScottK> Weird.
[06:03] <ScottK> It build-depends on python-all-dev which was the first obvious choice.
[06:04] <ScottK> So that's not it.
[06:07] <ScottK> libpython2.6/2.7 are also pulled in.
[06:08]  * micahg is getting the chroot build log
[06:08] <ScottK> Missing -lssl
[06:08] <micahg> ah
[06:09] <ScottK> What about that?
[06:09]  * micahg is getting the chroot to not purge to check
[06:09] <ScottK> Dunno why that would work on a live system though.
[06:11] <micahg> BTW, the release version won't build either
[06:11] <micahg> I guess that's obvious considering the patch
[06:14] <micahg> wow, a whole bunch of stuff is broke
[06:15]  * micahg has no idea why this would work on a live system
[06:18] <ScottK> It built at one point.
[06:21] <micahg> in July when we had the autosync
[06:23] <micahg> not sure, it seems to think my installed python env is fine, but the chroot env is not
[06:24] <micahg> ah, it doesn't seem to be multiarch ready, but still that shouldn't work on the live system either unless I have some old hack installed
[06:26] <micahg> it also won't build twice in a row which is annoying, but that's for another discussion (happening on debian-devel)
[06:27] <ScottK> The next version (the one you just sync'ed over_ is multi-arched.
[06:28] <micahg> right
[06:28]  * ScottK is going to go to bed.
[06:28] <ScottK> Good night.
[06:29] <micahg> good night
[08:04] <dholbach> good morning
[08:10] <ajmitch> morning dholbach
[08:11] <dholbach> hi ajmitch
[09:56] <ondras> hi there
[09:58] <ondras> what can I do to get my packages to ubuntu? I already have a working PPA...
[10:20] <tumbleweed> ondras: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[10:21] <ondras> tumbleweed: ah, thanks!
[10:22] <ondras> tumbleweed: the bug should be filed even if the software is already packaged?
[10:22] <ondras> tumbleweed: with [needs packaging] prefix?
[10:36] <tumbleweed> ondras: did you miss the bit about going through debian?
[10:37] <tumbleweed> that really is the beast approach
[10:38] <ondras> yeah, I already sent them a RFS email
[10:38] <ondras> but according to #debian-mentors, this can take months or years
[10:38] <ondras> :/
[10:41] <tumbleweed> it's normally a lot faster than that
[10:41] <tumbleweed> what are you packaging?
[10:43] <ondras> tumbleweed: http://code.google.com/p/v8cgi/
[10:44] <ondras> (basically a wrapper around libv8 + several modules; somewhat similar to node.js but with different architecture/usage)
[10:45] <jporsini> tumbleweed, hum, I don't know what is the normal duration, but at least the package that I have submitted has taken ~2month to pass the debian ftpmaster step (and I was lucky to personnally know the debian sponsor which speedup a little bit the process)
[10:51] <tumbleweed> ondras: ah, that sounds like a non-trivial package
[10:51] <tumbleweed> jporsini: ftpmaster review is a lot faster than it used to be: http://ftp-master.debian.org/stat.html
[10:53] <jporsini> tumbleweed, yep, I was currently on this page, and you are right, it appears to be now very fast, definitively a good news, so forget my previous sentence:)
[10:53] <DktrKranz> just FTR, average time in Debian NEW during 2011 has been 3 days and 5 hours
[10:54] <ondras> tumbleweed: it is a multiple binary package, yes
[10:55] <ondras> tumbleweed: but it is a standalone software with basically no dependencies
[11:13] <tumbleweed> DktrKranz: and we appreciate it!
[11:35]  * Laney bakes DktrKranz a cake http://farm1.static.flickr.com/23/37895746_90c5c30ca9.jpg *
[11:35] <Laney> * disclaimer: I may not have baked that
[11:50] <jpds> Looks like cheese cake.
[11:52] <Laney> it does, and has put me right in the mood for some
[11:53]  * Laney eyes the build queues
[11:53]  * Laney goes to decorate the tree instead
[11:57] <geser> Laney: does this imply that you would have a undecorated tree if the build queues were empty?
[11:58]  * geser wonders if it's possible to deduce how full the build queues were from how much Laney decorated his tree?
[12:17] <Laney> geser: that is something we cannot know
[13:27] <mdeslaur> ScottK: I'm uploading your unbound fixes now, just as soon as I fix the oneiric ftbfs. I've added two more older cve fixes to the lucid package also.
[13:27] <ScottK> mdeslaur: OK.  I wasn't aware I'd missed any.  Thanks.
[13:28] <ScottK> mdeslaur: Please let me know what the solution is on oneiric once you sort it out.  It's got me confused.
[13:31] <mdeslaur> ScottK: I'm still poking at it...I suspect this is the fix: http://anonscm.debian.org/gitweb/?p=users/edmonds/unbound.git;a=commitdiff;h=650df562a19e196e9acbc4898559f2fa61a8d90e
[13:32] <mdeslaur> hrm, maybe not
[13:33] <ScottK> micahg said he got it to build on a non-minimal system, so it may just be a missing dependency.
[13:33]  * ScottK has NFC what though.
[13:34] <mdeslaur> huh
[13:36] <ScottK> [01:03:13] <micahg> ScottK: looks like a missing build-dep, works fine on a live system
[13:36] <ScottK> [01:03:32] <ScottK> Weird.
[13:36] <ScottK> Based on the failure though, I'm not sure how that's possible.
[13:39] <geser> is there a build log available somewhere?
[13:41] <ScottK> No, but just try to rebuild the oneiric unbound package.
[13:41] <ScottK> It dies pretty quickly in configure.
[13:41] <ScottK> Actually, i may have one
[13:43] <ScottK> I do.
[13:44] <ScottK> geser: http://kitterman.com/kubuntu/unbound.oneiric
[13:52] <mdeslaur> I think it's multiarch related, and I'm backporting a small change from the precise package
[13:55] <mdeslaur> hrm, that didn't work
[13:55]  * mdeslaur scratches head
[14:24] <geser> does the oneiric version build in a precise chroot? and does the precise version build in a oneiric chroot? (I don't have access to my pbuilders right now to test it myself)
[14:36] <ScottK> The precise version does not build on the oneiric chroot.
[14:37] <ScottK> The oneiric version builds on precise.
[14:38] <ScottK> mdeslaur: That (to me) points to a bug in another package.
[14:43] <geser> Could it be python itself? As this check tries linking with only python, on the other side (if it's really python) I wonder why no other package stumbled over it
[14:43] <ScottK> That's what I was thinking, but no idea.  It seems distinctly odd.
[14:47] <mdeslaur> ScottK: yeah, I tried the precise package on oneiric, and it failed as well
[14:47] <ScottK> But the other way around works (oneiric package on precise)
[14:48] <mdeslaur> yep, so it's something with oneiric
[14:48] <mdeslaur> I'm still poking at it
[14:48] <ScottK> Better you than me.  This is way over my head.
[15:01] <mdeslaur> well, I'm stuck...don't know what to try next
[15:03] <ScottK> Ask doko since it might be Python related?
[15:22] <ScottK> Reading -devel, I don't fell bad I didn't figure that out.
[15:22] <ScottK> fell/feel
[15:30] <mdeslaur> ScottK, geser: we need to build it with binutils from oneiric-updates
[15:30] <mdeslaur> ScottK: heh, I wouldn't have figured it out :P
[15:30] <ScottK> Great news though.
[15:31] <ScottK> It also explains why it built on micahg's system.  I'm sure he has -updates enabled.
[15:34] <mdeslaur> ScottK: yeah...thanks for suggesting I ask him
[15:35] <ScottK> It's ironic though since I suggested him for a reason entirely unrelated to the actual answer.
[15:35] <mdeslaur> I had tried rebuilding with -updates enabled in my schroot, but binutils wasn't updated in it
[20:03] <ScottK> tumbleweed: You're famous - http://askubuntu.com/badges/40/tumbleweed
[20:04] <tumbleweed> :)
[20:04] <tumbleweed> now I need to ask a question so I can earn it
[20:09] <tumbleweed> broder: maybe backportpackage should use -nc
[20:10] <tumbleweed> (just ran across one of those package that needs all its build deps to clean)
[20:11] <micahg> makes sense if there are no source changes
[20:12]  * micahg had one of those last night also
[20:13]  * tumbleweed does that for syncpackage too
[20:13] <tumbleweed> oh and sponsor-patch
[20:28] <broder> tumbleweed: makes sense to me
[20:32] <ajmitch> ScottK: you're using askubuntu now as well?
[20:33] <Laney> i answered some questions there a bit back
[20:33]  * micahg thinks ScottK mistook it for as kubuntu :)
[20:33] <ajmitch> heh
[20:33] <Laney> as kubuntu
[20:34] <Laney> want points? answer http://askubuntu.com/questions/90070/how-does-the-shutdown-button-works-without-asking-for-password
[20:34] <broder> that one's easy
[20:35] <Laney> exactly
[20:35]  * tumbleweed doesn't know why anyone bothers with askubuntu. jorge answers everything
[20:36] <ajmitch> not *quite* everything
[20:36] <ajmitch> just 95%
[20:36]  * ajmitch did at least get a free tshirt from them :)
[22:16] <Adri2000> hmm, I'm a bit out of date on this: is requestsync completly deprecated in favor of syncpackage?
[22:16] <Adri2000> (given that I have the necessary upload rights)
[22:18] <broder> yes
[22:18] <broder> for doing your own syncs
[22:18] <broder> for sponsoring syncs, you need to be sure to have a fairly recent version of syncpackage that supports it
[22:19] <broder> (either from precise or ppa:udt-developers/daily)
[22:19] <Adri2000> ok, thanks :)
[22:21] <EvilResistance> broder:  is there an easy way to determine what build-deps or required packages are defined in the debian/control file in a source package between versions (i.e. precise vs. oneiric versions)
[22:21] <EvilResistance> without me having to download the source packages and then diffing them
[22:21] <EvilResistance> s/them/the control file/
[22:22] <Laney> packages.ubuntu.com shows it, or UDD
[22:24] <EvilResistance> packages.ubuntu.com does show the dependent packages for the program to run, but i dont see any refs about the build-deps... what's UDD?
[22:25] <Laney> http://packages.ubuntu.com/source/precise/libproxy
[22:25] <Laney> UDD is the ultimate debian database, see udd.debian.org
[22:26] <EvilResistance> ah source that's what i forgot to look at :P
[22:26] <Laney> or they are in the Sources file in a repository
[22:26] <Laney> which you can query with e.g. grep-dctrl
[22:27] <nixmaniack> is there a way to get debian source via apt-get source in ubuntu?
[22:28] <tumbleweed> it's in the Sources files
[22:28] <tumbleweed> ah, Laney said that
[22:28] <tumbleweed> nixmaniack: we have pull-debian-source to make it easy
[22:28] <tumbleweed> but yes, you can have deb-src lines pointing at Ubuntu
[22:28] <tumbleweed> err at Debian
[22:29] <nixmaniack> tumbleweed, thanks for the help :)
[22:29] <tumbleweed> apt-get doesn't make that particularly user-friendly, though, you have to specify which release you are downloading from, whenever you download it
[22:29] <tumbleweed> also see chdist in devscripts
[22:29] <tumbleweed> but for most uses, pull-debian-source
[22:30] <nixmaniack> which default mirror it uses?
[22:33] <tumbleweed> the primary archive. But you can configure it (see ubuntu-dev-tools (5))
[22:34] <nixmaniack> tumbleweed, okay, got it.
[23:39] <EvilResistance> um... i'm getting a 500 error when trying to upload a backported package to a PPA for my use... is this a bug, or did it not upload?  https://pastebin.com/aPwzfQhU
[23:40] <EvilResistance> (using backportpackage btw)


[04:07] <lotuspsychje> good morning to all
[04:07] <lotuspsychje> quick jump-in before work
[04:13] <Bashing-om> What a wonderful thing - IRC - place brain in gear before going to work :)
[04:13] <lotuspsychje> yeah all this green on black hexchat giving me a boost lol
[04:15] <Bashing-om> ^ along with the black coffee .
[04:16] <lotuspsychje> morning rangemonger
[04:16] <rangemonger> sup?
[04:16] <lotuspsychje> did you fix your xen?
[04:16] <rangemonger> i did :D
[04:16] <lotuspsychje> rangemonger: what did the trick?
[04:17] <rangemonger> had to make a conf file to hide the pci devices i wanted to load in a vm
[04:17] <lotuspsychje> morning boshhead
[04:17] <boshhead> Hello all
[04:17] <boshhead> hi lotuspsychje :)
[04:18] <rangemonger> also had to modprobe xen-pciback, beforehand
[04:18] <lotuspsychje> rangemonger: so by default they show in the config?
[04:18] <boshhead> I have recently converted from a desktop PC running Ubuntu, to the new macbook pro 2016. But I still run linux in VMs and on my VPS.
[04:18] <boshhead> and by linux i mean ubuntu of course :P
[04:18] <lotuspsychje> boshhead: we had a user recently saying he managed to install ubuntu on a mac dualboot
[04:19] <lotuspsychje> on a recent mac
[04:19] <rangemonger> lotuspsychje: nope, i had to lspci, see what they were an add them manually
[04:19] <lotuspsychje> rangemonger: i see!
[04:19] <rangemonger> added them to modprobe.d
[04:19] <rangemonger> weird that kvm needed no such tweaking
[04:19] <lotuspsychje> rangemonger: yeah was wondering why that doesnt work by default?
[04:20] <rangemonger> vt-d just  works on kvm
[04:20] <rangemonger> the only thing i needed to do for kvm was add iommu to grub
[04:20] <lotuspsychje> rangemonger: maybe you should file a new bug, then resolve it right away how you fixxed?
[04:20] <lotuspsychje> help the community
[04:21] <rangemonger> i dont know, i think maybe virtman doesnt see what virtual pci slot it should add things to probperly, with xen
[04:21] <rangemonger> i think it tries adding them to ones that are taken
[04:22] <lotuspsychje> right
[04:22] <rangemonger> also virtman has tablet added as a default item, to a newly created vm, but if you remove it, its not listed as an available item to add back
[04:24] <rangemonger> i basically spun a 'buntu that was a bare lxde desktop, virtman, and almost nothing else
[04:25] <rangemonger> just basic things like randr and power management
[04:25] <rangemonger> ...remote desktop, ssh
[04:25] <rangemonger> thats about it
[04:26] <rangemonger> its basically like a bare metal hv
[04:27] <lotuspsychje> cool
[04:27] <lotuspsychje> i like the new 16.04 lubuntu alot
[04:28] <rangemonger> no one seems to be using 16.10
[04:30] <rangemonger> its funny because lubuntu based on lxqt has been "coming in the next" release for about 4 years now
[04:31] <boshhead> LTS editions are always nice, hard to beat 5 years of support :)
[04:32] <Ben64> yep
[04:32] <Ben64> been using them since 8.04
[04:33] <rangemonger> im to tempted by the new shinies :S
[05:03] <lotuspsychje> bbl working : (
[07:33] <ducasse> good morning all
[07:34] <rangemonger> morning
[09:16] <SebthreeBQM10HD> hi
[09:17] <rangemonger> yep...
[09:17] <SebthreeBQM10HD> who started this
[09:17] <SebthreeBQM10HD> oh a few in here actsauly
[12:44] <BluesKaj> Hiyas all
[12:46] <OerHeks> hello BluesKaj :-)
[12:46] <BluesKaj> Hi OerHeks
[13:03] <pauljw> Hi everyone
[22:07] <Slown> Hi
[22:09] <nicomachus> Slown: I highly suggest going for 16.04
[22:09] <nicomachus> the LTS relesase.
[22:09] <nicomachus> release*
[22:09] <Slown> ok I'll go with that
[22:10] <Slown> is ubuntu budgie official guys ?
[22:10] <nicomachus> it's supported until 2021.
[22:10] <nicomachus> never heard of it.
[22:10] <Slown> https://budgie-remix.org
[22:10] <Slown> take a look
[22:10] <Slown> very beautiful DE
[22:11] <nicomachus> I don't think any DE's are "official".
[22:11] <nicomachus> if you like it, try it.
[22:11] <nicomachus> you can install more than one and switch back and forth.
[22:11] <Slown> what do you mean ?
[22:11] <tgm4883> Slown: ubuntu budgie 16.10 is an official flavor
[22:11] <tgm4883> 16.04 is not
[22:11] <Slown> what ?
[22:12] <tgm4883> How is that not clear?
[22:12] <\9> budgie? who decided on that name?
[22:12] <Slown> I don't understand
[22:12] <Slown> why 16.10 is official
[22:12] <Slown> and not the 16.04
[22:12] <Slown> it's the same DE
[22:12] <tgm4883> Slown: because there's a process to applying to be an official flavor, and they did so in time for the 16.10 release, and did not for the 16.04 release
[22:13] <Slown> ok I understand
[22:13] <tgm4883> \9: you prefer bubuntu?
[22:13] <tgm4883> or budubuntu
[22:13] <nicomachus> that's awful. lol
[22:13] <tgm4883> how about budgiebuntu
[22:13] <Slown> too much
[22:14] <\9> i meant the name 'budgie' itself but whatever
[22:14] <tgm4883> :)
[22:14] <Slown> did they have a channel ?
[22:14] <\9> budubuntu would be funny
[22:14] <tgm4883> !flavor
[22:14] <ubot5`> Recognized Ubuntu flavors build on Ubuntu and provide a different user experience out of the box. They are supported both in #ubuntu and in their flavor channel. The current list is: !Edubuntu, !Ubuntu-GNOME, !Kubuntu, Ubuntu !Kylin, !Lubuntu, !Mythbuntu, Ubuntu !Studio, !Xubuntu, and Ubuntu !MATE
[22:14] <tgm4883> !budgie
[22:14] <tgm4883> I guess that needs updated
[22:15] <\9> !budubuntu
[22:16] <Slown> so If I download the 16.10 release
[22:16] <Slown> and I decide someday to back to the LTS version
[22:16] <Slown> is it recommended ?
[22:16] <Slown> and possible
[22:16] <tgm4883> it would be a reinstall
[22:17] <Slown> hmm ok
[22:20] <Slown> thank you guys
[22:21] <Slown> goodbye
[23:39] <Bashing-om> rebooting .. back on a bit


[00:41] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [amd64] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[00:43] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [ppc64el] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[00:43] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [s390x] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[00:44] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [armhf] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[00:46] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [arm64] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[01:10] -queuebot:#ubuntu-release- New binary: golang-github-containerd-stargz-snapshotter [riscv64] (lunar-proposed/universe) [0.12.0-2] (no packageset)
[01:19] <coreycb> bdmurray:  I've uploaded new versions of manila and horizon to lunar
[01:38] -queuebot:#ubuntu-release- Unapproved: accepted directx-headers [source] (jammy-proposed) [1.606.4-1~ubuntu<IP_ADDRESS>]
[03:02] -queuebot:#ubuntu-release- New binary: golang-step-linkedca [amd64] (lunar-proposed/universe) [0.19.0-1] (no packageset)
[03:07] -queuebot:#ubuntu-release- New binary: haskell-copilot-libraries [riscv64] (lunar-proposed/universe) [3.12-1build2] (no packageset)
[05:13] -queuebot:#ubuntu-release- Unapproved: accepted spirv-headers [source] (jammy-proposed) [1.6.1+<IP_ADDRESS>-1~ubuntu<IP_ADDRESS>]
[05:25] -queuebot:#ubuntu-release- New binary: swupdate [amd64] (lunar-proposed/universe) [2022.12+dfsg-1] (no packageset)
[05:46] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [source] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[05:50] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [amd64] (jammy-proposed/none) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[05:52] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [ppc64el] (jammy-proposed/none) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[05:52] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [s390x] (jammy-proposed/none) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[05:56] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [arm64] (jammy-proposed/none) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[05:59] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [armhf] (jammy-proposed/universe) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[06:35] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-14 [riscv64] (jammy-proposed/universe) [14.0.0-3~ubuntu<IP_ADDRESS>] (no packageset)
[07:10] <LocutusOfBorg> vorlon, I prefer to fix packages instead of patching cmake to introduce latomic regardless of the fact that is needed or not, and only for cmake
[07:10] <LocutusOfBorg> what happens to qmake? autotools? custom makefiles?
[07:11] <LocutusOfBorg> lets sort out the riscv64 packages that needs changes, and fix them properly, e.g. if you change atomic_bool to atomic_int, the latomic is not even needed, because the compiler can create the optimized code without needing of slow additional libraries
[07:11] <vorlon> if the argument is that the delta was wrong and the fix needed to land elsewhere, that's fine; it was presented to me as you didn't want to carry a delta
[07:12] <LocutusOfBorg> yes, I don't want to carry a cmake delta, and I'm willing to fix riscv64 packages as soon as I detect them
[07:12] <RikMills> vorlon: LocutusOfBorg apologies if my phrasing gave the wrong impression
[07:13] <LocutusOfBorg> simgear/flightgear had similar issues, and now have upstream patches
[07:14] <LocutusOfBorg> same for mujoco, fixed and now not requiring anymore the latomic link
[07:14] <LocutusOfBorg> https://github.com/deepmind/mujoco/pull/632
[07:14] -ubottu:#ubuntu-release- Pull 632 in deepmind/mujoco "Update cmakelist to fix a link failure on riscv64 (Debian/Ubuntu)" [Merged]
[07:14] <LocutusOfBorg> and this is where I discovered that latomic isn't essential on riscv64
[07:15] <LocutusOfBorg> btw as said, please point me to failures in case you see latomic foo!
[07:18] <vorlon> haskell-hopenpgp build restarted?
[07:32] <vorlon> LocutusOfBorg: ^^ is that your doing?
[07:33] <vorlon> apw: find-proposed-cluster updated if you want to have another look; made it a bit more featureful
[07:35] <vorlon> mitya57: am considering rolling back linphone-desktop temporarily to uncouple the bctoolbox transition from the qt transition
[07:36] <vorlon> since qt transition is blocked for a bit waiting on test results
[08:05] <LocutusOfBorg> vorlon, let me check
[08:05] <LocutusOfBorg> ok removed from the give-back list
[08:17] <LocutusOfBorg> hello, can any ubuntu-archive please process haskell-copilot-libraries and lambdabot?
[08:17] <seb128> LocutusOfBorg, hey, what 'process' means in that context?
[08:17] <LocutusOfBorg> binNEW
[08:17] <LocutusOfBorg> :D
[08:18] <LocutusOfBorg> accept, review
[08:18] <LocutusOfBorg> maybe in the opposite order :D
[08:18] <seb128> order shouldn't make a difference, they are going to be in the same publisher update
[08:19] <LocutusOfBorg> I mean, review-> accept
[08:19] <seb128> NEWed
[08:19] <LocutusOfBorg> not accept->review
[08:19] <seb128> lol
[08:19] <seb128> of course :)
[08:19] <LocutusOfBorg> :D
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [amd64] (lunar-proposed) [5.3.1-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [armhf] (lunar-proposed) [5.3.1-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [riscv64] (lunar-proposed) [5.3.1-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [arm64] (lunar-proposed) [5.3.1-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [s390x] (lunar-proposed) [5.3.1-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted lambdabot [ppc64el] (lunar-proposed) [5.3.1-1build2]
[08:19] <LocutusOfBorg> c'était une blague
[08:19] <LocutusOfBorg> :D
[08:19] <seb128> je ne suis pas encore réveillé ! :p
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [amd64] (lunar-proposed) [3.12-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [armhf] (lunar-proposed) [3.12-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [riscv64] (lunar-proposed) [3.12-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [arm64] (lunar-proposed) [3.12-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [s390x] (lunar-proposed) [3.12-1build2]
[08:19] -queuebot:#ubuntu-release- New: accepted haskell-copilot-libraries [ppc64el] (lunar-proposed) [3.12-1build2]
[08:20] <LocutusOfBorg> merci!
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [amd64] (lunar-proposed) [0.12.0-2]
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [armhf] (lunar-proposed) [0.12.0-2]
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [riscv64] (lunar-proposed) [0.12.0-2]
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [arm64] (lunar-proposed) [0.12.0-2]
[08:20] <LocutusOfBorg> profitez de votre café :D
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [s390x] (lunar-proposed) [0.12.0-2]
[08:20] -queuebot:#ubuntu-release- New: accepted golang-github-containerd-stargz-snapshotter [ppc64el] (lunar-proposed) [0.12.0-2]
[08:22] <LocutusOfBorg> nice! packages creating manpages on dh_auto_test target, and failing on riscv64!
[08:22] <LocutusOfBorg> efibootguard, you nasty guy!
[08:22]  * LocutusOfBorg santa writes that package on the naughty list
[09:10] -queuebot:#ubuntu-release- New binary: haskell-copilot [amd64] (lunar-proposed/universe) [3.12-1] (no packageset)
[09:10] -queuebot:#ubuntu-release- New binary: haskell-copilot [s390x] (lunar-proposed/universe) [3.12-1] (no packageset)
[09:11] -queuebot:#ubuntu-release- New binary: haskell-copilot [ppc64el] (lunar-proposed/universe) [3.12-1] (no packageset)
[09:13] -queuebot:#ubuntu-release- New binary: haskell-copilot [arm64] (lunar-proposed/universe) [3.12-1] (no packageset)
[09:13] -queuebot:#ubuntu-release- New binary: haskell-copilot [armhf] (lunar-proposed/universe) [3.12-1] (no packageset)
[09:46] -queuebot:#ubuntu-release- New: accepted golang-step-linkedca [amd64] (lunar-proposed) [0.19.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted haskell-copilot [arm64] (lunar-proposed) [3.12-1]
[09:46] -queuebot:#ubuntu-release- New: accepted haskell-copilot [ppc64el] (lunar-proposed) [3.12-1]
[09:46] -queuebot:#ubuntu-release- New: accepted pigx-rnaseq [amd64] (lunar-proposed) [0.1.0-1.1]
[09:46] -queuebot:#ubuntu-release- New: accepted haskell-copilot [amd64] (lunar-proposed) [3.12-1]
[09:46] -queuebot:#ubuntu-release- New: accepted haskell-copilot [s390x] (lunar-proposed) [3.12-1]
[09:46] -queuebot:#ubuntu-release- New: accepted haskell-copilot [armhf] (lunar-proposed) [3.12-1]
[09:46] -queuebot:#ubuntu-release- New: accepted swupdate [amd64] (lunar-proposed) [2022.12+dfsg-1]
[09:47] <LocutusOfBorg>   * Add Dep on sse2-support, to make sure luatex works
[09:47] <LocutusOfBorg>     correctly (Closes: #1023007).
[09:47] <LocutusOfBorg> texlive-bin ^^ vorlon
[09:48] <LocutusOfBorg> (this makes lots of things fail on i386, e.g. augeas)
[10:07] -queuebot:#ubuntu-release- New binary: haskell-copilot [riscv64] (lunar-proposed/universe) [3.12-1] (no packageset)
[10:09] <ginggs_> ubuntu-archive would someone please cleanup for https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-apt ?
[10:09] <ginggs_> old binaries left on riscv64: python3-apt-dbg (from 2.3.0ubuntu3)
[10:50] <cpaelzer> ginggs: done
[10:57] <ginggs> cpaelzer: thanks!
[11:07] <mitya57> vorlon: ok
[11:51] <bdrung> rbasak, apport 2.20.11-0ubuntu82.3 aged for seven days. Can you accept in -updates?
[13:22] -queuebot:#ubuntu-release- Unapproved: dotnet6 (kinetic-proposed/universe) [6.0.111-0ubuntu1~22.10.1 => 6.0.112-0ubuntu1~22.10.1] (no packageset)
[13:55] -queuebot:#ubuntu-release- Unapproved: dotnet6 (jammy-proposed/universe) [6.0.111-0ubuntu1~22.04.1 => 6.0.112-0ubuntu1~22.04.1] (no packageset)
[16:21] <Eickmeyer> Hi release team, and pinging vorlon (if you're at your desk or happen to see this): forked the Edubuntu seed to lp:~edubuntu-dev/ubuntu-seeds/+git/edubuntu, so if you could to change the script to point there per yesterday's meeting that would be lovely.
[16:21] <Eickmeyer> (also created a lunar branch)
[16:22] <vorlon> LocutusOfBorg: "add dep on sse2-support" in tex lololol
[16:22] -queuebot:#ubuntu-release- New: accepted haskell-copilot [riscv64] (lunar-proposed) [3.12-1]
[16:23]  * RikMills notes result of tech board election
[16:23] <RikMills> congrats to the winners
[16:24] <vorlon> ginggs: python3-apt-dbg cleaned up
[16:24] <vorlon> ginggs: (by someone else, before I tried to run the command, because update_excuses is stale now)
[16:27] <vorlon> Eickmeyer: updated
[16:31] <vorlon> LocutusOfBorg: so, how do we get haskell-hopenpgp built on armhf? this looks to me like the main blocker for ghc right now
[16:32] <vorlon> and 150m of inactivity in the test suite suggests this software is not particularly usable
[16:32] <vorlon> I could remove haskell-hopenpgp and haskell-hopenpgp-tools on armhf
[16:32] <vorlon> in fact I see no reason not to do that
[16:51] -queuebot:#ubuntu-release- Packageset: Removed dnprogs from i386-whitelist in lunar
[16:51] -queuebot:#ubuntu-release- Packageset: Removed sphinxcontrib-serializinghtml from i386-whitelist in lunar
[16:51] -queuebot:#ubuntu-release- Packageset: Added gcc-13 to i386-whitelist in lunar
[16:54] <LocutusOfBorg> vorlon, removing is the best option I would say
[16:54] <LocutusOfBorg> probably its the same in Debian
[16:54] <LocutusOfBorg> we gained lots of new packages on riscv64 and s390x, removing one on armhf is a great trade off
[16:55] <LocutusOfBorg> and lambdabot and lots of other packages are back!
[16:55] <Eickmeyer> vorlon: Thanks!
[16:55] <LocutusOfBorg> sadly haskell-gi* are still building on riscv, another big blocker I guess
[17:16] <ginggs> vorlon: thanks for looking at python3-apt-dbg, c.paelzer said he did it
[17:22] -queuebot:#ubuntu-release- New binary: php-wmerrors [amd64] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: php-wmerrors [armhf] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: php-wmerrors [s390x] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: php-wmerrors [ppc64el] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: php-wmerrors [arm64] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New: accepted php-wmerrors [amd64] (lunar-proposed) [2.0.0~git20221212.631dedd-1]
[17:28] -queuebot:#ubuntu-release- New: accepted php-wmerrors [armhf] (lunar-proposed) [2.0.0~git20221212.631dedd-1]
[17:28] -queuebot:#ubuntu-release- New: accepted php-wmerrors [s390x] (lunar-proposed) [2.0.0~git20221212.631dedd-1]
[17:28] -queuebot:#ubuntu-release- New: accepted php-wmerrors [arm64] (lunar-proposed) [2.0.0~git20221212.631dedd-1]
[17:28] -queuebot:#ubuntu-release- New: accepted php-wmerrors [ppc64el] (lunar-proposed) [2.0.0~git20221212.631dedd-1]
[17:38] -queuebot:#ubuntu-release- New binary: php-wmerrors [riscv64] (lunar-proposed/none) [2.0.0~git20221212.631dedd-1] (no packageset)
[18:01] -queuebot:#ubuntu-release- New binary: karchive [amd64] (lunar-proposed/universe) [5.101.0-1] (kubuntu)
[19:21] -queuebot:#ubuntu-release- New sync: ruby-image-processing (lunar-proposed/primary) [1.10.3-2]
[19:53] -queuebot:#ubuntu-release- Unapproved: accepted evince [source] (jammy-proposed) [42.3-0ubuntu3]
[20:06] -queuebot:#ubuntu-release- Unapproved: accepted manila [source] (kinetic-proposed) [1:15.1.0-0ubuntu1]
[20:14] -queuebot:#ubuntu-release- New binary: pgrouting [amd64] (lunar-proposed/universe) [3.4.2-1build1] (no packageset)
[20:15] -queuebot:#ubuntu-release- New binary: pgrouting [s390x] (lunar-proposed/universe) [3.4.2-1build1] (no packageset)
[20:16] -queuebot:#ubuntu-release- New binary: pgrouting [armhf] (lunar-proposed/universe) [3.4.2-1build1] (no packageset)
[20:17] -queuebot:#ubuntu-release- New binary: pgrouting [ppc64el] (lunar-proposed/universe) [3.4.2-1build1] (no packageset)
[20:23] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (kinetic-proposed) [4:23.0.0-0ubuntu1.1]
[20:26] -queuebot:#ubuntu-release- Unapproved: net-snmp (jammy-proposed/main) [5.9.1+dfsg-1ubuntu2.2 => 5.9.1+dfsg-1ubuntu2.3] (desktop-core, i386-whitelist, ubuntu-server)
[20:28] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (jammy-proposed) [4:22.1.0-0ubuntu2.1]
[20:28] -queuebot:#ubuntu-release- Unapproved: net-snmp (kinetic-proposed/main) [5.9.3+dfsg-1ubuntu1 => 5.9.3+dfsg-1ubuntu1.1] (desktop-core, i386-whitelist, ubuntu-server)
[20:30] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (focal-proposed) [3:18.3.5-0ubuntu2.1]
[20:41] -queuebot:#ubuntu-release- New binary: pgrouting [arm64] (lunar-proposed/universe) [3.4.2-1build1] (no packageset)
[21:00] -queuebot:#ubuntu-release- New: accepted pgrouting [amd64] (lunar-proposed) [3.4.2-1build1]
[21:00] -queuebot:#ubuntu-release- New: accepted pgrouting [armhf] (lunar-proposed) [3.4.2-1build1]
[21:00] -queuebot:#ubuntu-release- New: accepted pgrouting [s390x] (lunar-proposed) [3.4.2-1build1]
[21:00] -queuebot:#ubuntu-release- New: accepted pgrouting [arm64] (lunar-proposed) [3.4.2-1build1]
[21:00] -queuebot:#ubuntu-release- New: accepted pgrouting [ppc64el] (lunar-proposed) [3.4.2-1build1]
[21:55] <bdmurray> vorlon: did you see this kernel oops in the initramfs-tools test<EMAIL_ADDRESS>[21:56] -queuebot:#ubuntu-release- New source: llvm-toolchain-15 (jammy-proposed/primary) [1:15.0.6-3~ubuntu<IP_ADDRESS>]
[21:59] <vorlon> bdmurray: no.  did waveform see it? :)
[22:01] <bdmurray> Hmm, I also see it with 0.140ubuntu17<EMAIL_ADDRESS>[22:42] -queuebot:#ubuntu-release- New source: edubuntu-meta (lunar-proposed/primary) [23.04.1]
[22:42] <Eickmeyer> ^ 😁
[23:27] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [amd64] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:27] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [armhf] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:27] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [s390x] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:27] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [arm64] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:27] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [ppc64el] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:28] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-14 [riscv64] (jammy-proposed) [14.0.0-3~ubuntu<IP_ADDRESS>]
[23:38] <vorlon> jbicha: "until someone ports debian-installer away from GTK2" lol
[23:41] <vorlon> ubuntu-archive ubuntu-release fyi I'm starting to prepare for migrating snakefruit to ubuntu-archive-toolbox, which at the moment basically consists of re-rsyncing ~ubuntu-archive/public_html, which hasn't happened in a year


[01:44] <mup> PR snapcraft#2437 opened: repo,baseplugin: support trusting repo keys <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2437>
[05:35] <zyga> Good morning
[06:07] <mborzecki> morning
[06:34] <zyga> hey mborzecki  :)
[06:34] <mborzecki> zyga: hey hey
[06:35] <zyga> I'd love to land some boring stuff today
[06:35] <zyga> most blocked by https://github.com/snapcore/snapd/pull/6353
[06:35] <mup> PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6353>
[06:35] <mborzecki> zyga: which pr should i start with first?
[06:35] <zyga> I think this one is the only one I really need
[06:35] <zyga> though all the <simple> ones should be a moment to review
[06:36] <mborzecki> ack
[06:40] <mup> PR snapd#6355 closed: release: 2.37~pre1 <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6355>
[07:02] <mborzecki> zyga: one suggestion under #6349, other than that it's +1
[07:02] <mup> PR #6349: cmd/snap-update-ns: move XDG code to dedicated file <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6349>
[07:02] <zyga> looking
[07:03] <zyga> nice :)
[07:05] <zyga> pushed
[07:06] <zyga> I prepared another branch but I will need https://github.com/snapcore/snapd/pull/6346 as well
[07:06] <mup> PR #6346: osutil: add helper for loading fstab from string <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6346>
[07:08] <zyga> mborzecki: updated https://github.com/snapcore/snapd/pull/6346 based on your comment
[07:08] <mup> PR #6346: osutil: add helper for loading fstab from string <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6346>
[07:54] <mborzecki> zyga: regarding #6345 none of the patches that start to make use of FromSnapConfine in s-u-n user mounts are up yet, right?
[07:54] <mup> PR #6345: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6345>
[07:54] <mborzecki> zyga: same for freezer
[07:55] <zyga> mborzecki: the main branch is
[07:55] <zyga> mborzecki: the only use of --from-snap-confine is to lock/freeze
[07:55] <zyga> but that is arguably one of the last patches in this pile
[07:55] <mborzecki> zyga: mhm
[07:57] <mborzecki> btw. have dropped codecov?
[07:57] <mborzecki> s/have/have we/
[08:01] <zyga> I ... don't remember we did
[08:01] <zyga> but perhaps?
[08:02] <mborzecki> idk, haven't seen any coments being added to the new PRs
[08:02] <pstolowski> morning
[08:04] <mborzecki> pstolowski: heya
[08:04] <zyga> hey Pawel
[08:13] <zyga> pstolowski: hey, could you do a 2nd review for https://github.com/snapcore/snapd/pull/6353
[08:13] <pstolowski> zyga: sure
[08:13] <mup> PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6353>
[08:20] <Chipaca> moin moin
[08:20] <zyga> hey chipaca :)
[08:21] <zyga> Chipaca: can I bug you for one little review in the morning please? https://github.com/snapcore/snapd/pull/6346
[08:21] <mup> PR #6346: osutil: add helper for loading fstab from string <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6346>
[08:21] <Chipaca> zyga: you can bug me all you want
[08:21]  * Chipaca adds zyga to his ignore list
[08:22] <mborzecki> Chipaca: hey
[08:34] <zyga> re
[08:45] <Chipaca> should I have another coffee?
[08:45] <Chipaca> I should have another coffee.
[08:45]  * Chipaca obeys
[08:57] <zyga> Chipaca: I hear you
[08:57] <zyga> coffee is good
[08:57] <mup> PR snapd#6356 opened: overlord/snapstate: during refresh, re-refresh on epoch bump <Created by chipaca> <https://github.com/snapcore/snapd/pull/6356>
[08:58] <Chipaca> pedronis: ^_^
[08:58] <pedronis> Chipaca: thx
[08:58] <Chipaca> pedronis: and good morning
[08:59] <pedronis> we'll see if I get to it today
[08:59] <zyga> pstolowski: https://github.com/snapcore/snapd/pull/6353#issuecomment-453438414
[08:59] <mup> PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6353>
[09:00] <pstolowski> zyga: sure
[09:00] <zyga> thanks!
[09:00] <zyga> I didn't notice 2017 :)
[09:00] <mup> PR snapd#6353 closed: cmd/snap-update-ns: move existing code around, renaming some functions <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6353>
[09:01] <zyga> Chipaca: the pic in your response is lovely
[09:01] <zyga> feels like the way to spend time :)
[09:01] <Chipaca> zyga: :-)
[09:01] <mup> PR snapd#6346 closed: osutil: add helper for loading fstab from string <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6346>
[09:03] <pedronis> Chipaca: next on your list, I think, is snapshot user docs?  and maybe picking up/rework #6348? does that sounds right?
[09:03] <mup> PR #6348: snap: split alignment calculation and display for channels <Created by mvo5> <https://github.com/snapcore/snapd/pull/6348>
[09:04] <Chipaca> pedronis: I'd like to know what to do about #6034 also
[09:04] <mup> PR #6034: many: save media info when installing, show it when listing <⛔ Blocked> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6034>
[09:04] <Chipaca> pedronis: but, yes, snapshot user docs, info refactor, then maybe per-architecture info
[09:05] <pedronis> Chipaca: yes, I'm aware of 6034, but indeed needs discussion so it's blocked atm
[09:05] <Chipaca> pedronis: we're not going to have time to have that discussion before the town of capes, right?
[09:05]  * Chipaca hopes everybody packed capes
[09:06] <pedronis> likely not but we'll see
[09:07] <pedronis> Chipaca: also next week sprint is organized a bit differently, with lots of everybody sessions all in the morning, so I might not be busy all the time, just almost all the time
[09:07] <Chipaca> pedronis: also I notice you removed the block on #6280, does that mean it's gtg (pending 2nd review)?
[09:07] <mup> PR #6280: cmd/snap: make 'snap warnings' output yamlish <Created by chipaca> <https://github.com/snapcore/snapd/pull/6280>
[09:07] <Chipaca> pedronis: you're going to a sprint, and think you might not be busy all the time
[09:07] <Chipaca> *giggle*
[09:09] <pedronis> Chipaca: I should probably look at it again (6280) but is not blocked about the --unicode oddities vs non-ttys
[09:09] <Chipaca> pedronis: ah :-) ok
[09:09] <pedronis> Chipaca: mvo asked for gustavo's input but if I understand it is something that was discussed with him, no?
[09:09] <Chipaca> pedronis: yep
[09:09] <Chipaca> at the london sprint (!)
[09:09] <pedronis> also the general principle, if too wide for tabular/naive output, be yaml-like/parsable
[09:13] <niemeyer> Heya
[09:14] <pedronis> niemeyer: hi
[09:48] <zyga> brb
[09:51] <pedronis> Chipaca: can you remind me how to poke at the API with http ?
[09:52] <Chipaca> pedronis: http snapd:///v2/find name==go
[09:52] <Chipaca> pedronis: or, http --pretty=all snapd:///v2/find name==go | less -R
[09:53] <pedronis> Chipaca: thank you
[10:16] <Chipaca> huh, I thought snapshots were in 2.36
[10:17] <Chipaca> just had a user on 2.36.3 tell me it didn't work there
[10:31] <pedronis> Chipaca: no, they are not, not they client bits
[10:31] <pedronis> they are in 2.37
[10:34] <Chipaca> 2.37 is going to be a big'un
[10:39] <pedronis> pstolowski: hi, btw I started yesterday looking again at the hotplug-connect PR but didn't finish, we'll try to do so today
[10:40] <pstolowski> pedronis: ack, thanks
[10:59] <zyga> pedronis: added one suggestion to the doc you just shared, it was something on the back of my mind for several interfaces (e.g. optical drive is the same)
[11:02] <Chipaca> why isn't architecture in `snap version`?
[11:02] <pedronis> zyga: add it "all" to what?
[11:02] <pedronis> the plug, the slot?
[11:02] <zyga> to the interface, I will clarify my comment
[11:03] <zyga> well, to the slot side
[11:03] <zyga> if you have "all" you are the old legacy camera
[11:03] <zyga> if you don't have that you are a precise camera
[11:03] <zyga> either hotplug or gadget
[11:03] <pedronis> I was basing that on having a path or not
[11:04] <pedronis> but we can do both
[11:04] <pedronis> on the slot side, anyway this is a discussion to have
[11:04] <pedronis> those were just jumping points
[11:07] <zyga> that's good, it's the same idea
[11:07] <zyga> ah, I see it's on the following line
[11:08] <zyga> I'll retract my suggestion
[11:29] <mborzecki> any clue if we'll be merging master to 2.37 again?
[11:31] <zyga> master to 2.37?
[11:31] <zyga> never?
[11:31] <zyga> I think it is cherry picking from now on
[11:31] <mborzecki> hm ok
[11:31] <zyga> proxy leaking from test to test? https://www.irccloud.com/pastebin/cw3P0RWp/
[11:33] <zyga> soliciting 2nd review for https://github.com/snapcore/snapd/pull/6349
[11:33] <mup> PR #6349: cmd/snap-update-ns: move XDG code to dedicated file <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6349>
[11:33] <zyga> pstolowski: do you have a moment?
[11:38] <pstolowski> zyga: ok
[11:42] <zyga> mborzecki: https://github.com/snapcore/snapd/pull/6352#discussion_r
[11:42] <mup> PR #6352: many: remove .user-fstab files from /run/snapd/ns <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6352>
[11:43] <mborzecki> zyga: yup
[11:44] <mborzecki> zyga: wonder if that should use rm -f {} \: instead, so that find does not stop if there's a failure to remove
[11:45] <zyga> those are plain files
[11:45] <zyga> should remove fine
[11:45] <zyga> pushed
[11:45] <zyga> I think we only had -f to "fix" rm -f *.foo expanding to "*.foo"
[11:46] <mborzecki> it'd be good if Chipaca could take a look too
[11:46] <zyga> +1
[11:46] <zyga> I added him to the review now
[11:46] <zyga> +4, -16
[11:46] <zyga> :)
[11:47] <pedronis> pstolowski: +1 with a comment still, also would be good if you got reviews from mborzecki and mvo for it
[11:47] <mborzecki> hehe :)
[11:47] <pstolowski> pedronis: k
[12:20] <zyga> re
[12:20] <zyga> some kitchen emergency, all good now
[12:24]  * pstolowski lunch
[12:31] <zyga> I'm seeing one test fail often today;
[12:32] <zyga> tests/main/xdg-open-compat fails with ERROR 503 while talking to launchpad.nett https://www.irccloud.com/pastebin/74kd9yef/
[12:32] <Chipaca> zyga: .nett?
[12:33] <zyga> no, .net, just a typo
[12:35] <Chipaca> zyga: launchpad might be sad today
[13:01] <mup> PR snapd#6357 opened: cmd/snap-update-ns: make freezer mockable <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6357>
[13:05] <mup> PR snapd#6358 opened: cmd/snap-update-ns: close internal lock on error <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6358>
[13:05] <zyga> mborzecki, pstolowski: I would love a review for the two above, this would make the refactor purely a refactor with 0 new features or fixes
[13:06] <zyga> I broke the two patches out to make that true
[13:06] <zyga> they are both really tiny
[13:07] <mup> PR snapd#6349 closed: cmd/snap-update-ns: move XDG code to dedicated file <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6349>
[13:34] <diddledan> is the store api down (snap find foo isn't working) or just my system having issues?
[13:34] <diddledan> aha. it's gone through now
[13:34] <diddledan> transient
[13:34] <diddledan> ignore me
[13:34] <cmatsuoka> working for me
[13:34] <diddledan> :-)
[13:36] <zyga> re
[13:36] <diddledan> the knights who say "re"?
[13:36] <mup> PR snapd#6359 opened: tests: use double quotes for regex on listing test to match \\* <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6359>
[13:36] <diddledan> :-p
[13:36] <zyga> store down and wonky errors https://www.irccloud.com/pastebin/pj7DG1v2/
[13:37] <zyga> Chipaca: ^
[14:02] <pedronis> Chipaca: standup?
[14:02] <Chipaca> agh, yes
[14:02] <Chipaca> was distracted by CVEs
[14:02]  * Chipaca goes
[14:21] <ali1234> how do i tell my snapcraft.yaml that i want to stage-packages from 16.04?
[14:22] <diddledan> if you don't tell it you want `base: core18` it will use 16.04 by default (you are using multipass, right?)
[14:22] <ali1234> i don't know
[14:25] <zyga> diddledan: I don't think that's true
[14:25] <zyga> diddledan: if you use base: core18 you will use the new base and the new multipass builder
[14:25] <zyga> diddledan: but in absence of that I think you will build the old way
[14:25] <zyga> diddledan: I may be wrong, but that's what I think was the approach
[14:25] <ali1234> "Issues while validating snapcraft.yaml: The 'version' property does not match the required schema: 0 is not a valid snap version string."
[14:26] <diddledan> zyga: yes, which is why I caveated my comment with the multipass
[14:26] <zyga> right but multipass is not on uless you use base: *
[14:26] <zyga> but there's no published core16 base
[14:26] <ali1234> what is a valid version string then?
[14:26] <zyga> ali1234: perhaps "1"
[14:26] <zyga> not sure why 0 is rejected
[14:26] <ali1234> nope, 1 also does not work
[14:26] <diddledan> if you aren't knowingly using multipass then you'll use the old build which builds against your host. if you specify `base: core18` then you will use multipass
[14:27] <ali1234> i want to use 16.04 as base when building on 18.04
[14:27] <diddledan> the solution to use multipass correctly is `env SNAPCRAFT_BUILD_ENVIRONMENT=multipass snapcraft`
[14:30] <ali1234> yeah what happens is if you don't have "base:" in snapcraft.yaml it builds against the host
[14:30] <diddledan> not if you tell it to use multipass
[14:30] <ali1234> if you have "base" it installs multipass for you, then fails to work because it won't accept any version string
[14:31] <diddledan> the only `base` value that is accepted is `core18`. don't set it but tell snapcraft to use multipass
[14:32] <ali1234> if i set base: core18 then it still fails to accept the version string. but doing it your way works
[14:32] <ali1234> it is now launching a VM
[14:36] <ali1234> it seems to be stuck...
[14:36] <mup> PR snapd#6358 closed: cmd/snap-update-ns: close internal lock on error <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/6358>
[14:36] <zyga> ali1234: quick question, is there a reason you don't want to just say "base: core18"
[14:37] <ali1234> yes, the package isn't available in ubuntu 18.04, if it was i'd just install it normally
[14:38] <ali1234> "launch failed: timed out waiting for instance to respond"
[14:40] <ogra> instance failed instantly :)
[14:41] <zyga> ali1234: I'm not sure I understand
[14:41] <ali1234> which part?
[14:41] <zyga> ali1234: using base: core18 will just build your project against ubuntu 18.04 build system
[14:41] <zyga> ali1234: is that breaking your software?
[14:42] <ali1234> i dont have any software
[14:42] <diddledan> o_O
[14:42] <zyga> ali1234: which package is not available in 18.04?
[14:42] <ali1234> eagle
[14:43] <zyga> eagle?
[14:43] <ali1234> yes, eagle
[14:43] <zyga> and is it advailable in 16.04?
[14:43] <zyga> https://packages.ubuntu.com/search?keywords=eagle&searchon=names&suite=all&section=all
[14:43] <ali1234> yes
[14:43] <ogra> the CAD tool ?
[14:43] <ali1234> yes, the CAD tool
[14:43] <zyga> aaah
[14:43] <ali1234> which is non-free
[14:43] <zyga> well
[14:43] <zyga> that's not from the ubuntu archive :)
[14:43] <zyga> what are you trying to build?
[14:44] <ali1234> eagle
[14:44] <zyga> an eagle snap?
[14:44] <ali1234> yes
[14:44] <ali1234> specifically an eagle 6.6 snap
[14:44] <zyga> I think you can use base: core18 just fine, you need to teach your snapcraft.yaml about where to get eagle from
[14:44] <ali1234> the version that is available for ubuntu 16.04
[14:44] <zyga> unless eagle just plainly doesn't work on any other version of ubuntu
[14:44] <ali1234> it isn't available any more
[14:44] <ali1234> the only place it is available is the ubuntu package
[14:45] <diddledan> eagle isn't available for ubuntu 16.04 specifically - you download it from autodesk as a tarball
[14:45] <zyga> I think the error  you are seeing is unrelated to core18 or eagle and it would be the best to migrate to core18 for your software, integrate fetching the eagle .deb (however legal is that)
[14:46] <zyga> I'm not just saying this because core18 is better
[14:46] <ali1234> diddledan: no, it is available as an ubuntu package for 16.04
[14:46] <diddledan> nope
[14:46] <zyga> but because the old build model (building natively) is going away
[14:46] <zyga> snapcraft switched to build with multipass-managed virtual machines
[14:46] <ali1234> https://launchpad.net/ubuntu/+source/eagle/6.6.0-2
[14:46] <mborzecki> or migrate to kicad :)
[14:47] <diddledan> that's not available in xenial
[14:47] <zyga> i386?
[14:47] <ali1234> yes it is: https://launchpad.net/ubuntu/+source/eagle/
[14:47] <zyga> Eagle is a powerful IM client designed to fit in perfectly in an enterprise environment.
[14:47] <ali1234> yes, it's i386 only
[14:47] <zyga> weird
[14:48] <zyga> anyway, I'm back to coding
[14:48] <mup> PR snapd#6357 closed: cmd/snap-update-ns: make freezer mockable <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6357>
[14:49] <zyga> pstolowski: could you do a 2nd review for https://github.com/snapcore/snapd/pull/6345
[14:49] <mup> PR #6345: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6345>
[14:52] <ogra> ali1234, regarding your version issue, i can build just fine here using "version: 0" in a snap
[14:52] <ali1234> yes, here it won't accept any version string at all
[14:52] <ogra> did you put any quotes areound the version string or some such ?
[14:52] <ali1234> no
[14:52] <ogra> *around
[14:52] <ogra> very weird
[14:53] <ali1234> what is the most simple possible snapcraft.yaml that should always be guaranteed to build?
[14:53] <ogra> what snapcraft version isthat ?
[14:53] <ogra> $ snap info snapcraft|grep installed
[14:53] <ogra> installed:   3.0.1                (2374) 28MB classic
[14:53] <ali1234> whatever you get with 18.04
[14:53] <ogra> you dont use the snap ?
[14:53] <mup> PR snapd#6345 closed: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/6345>
[14:53] <zyga> \o/
[14:53] <zyga> thanks!
[14:54]  * ogra has long stopped using snapcraft from the archive ... never had issues
[14:54] <ali1234> snapcraft, version 3.0.1
[14:54] <diddledan> I try to use a snap if one is available unless I hit issues with it that I can't fudge
[14:54] <ogra> well, then i dont get why it doesnt work the same way as mine
[14:55] <ali1234> actually i do have it installed through snap: installed:   3.0.1                (2374) 28MB classic
[14:55] <ogra> probably some other typo in the snapcraft.yaml ? (and the version thingie just being fallout)
[14:58] <ali1234> this is my entire snapcraft.yaml: http://paste.ubuntu.com/p/cQZFmSnm49/
[14:58] <ogra> i doubt thats valid
[14:59] <ogra> better use snapcraft init and modify the created file then
[14:59] <mup> PR snapd#6360 opened: cmd/snap-update-ns: refactor of profile application <Per-user mount ns  🐎> <Created by zyga> <https://github.com/snapcore/snapd/pull/6360>
[14:59] <ogra> you are surely missing a lot of required fields
[15:00] <ogra> (description, confinement ... not sure but probably also grade)
[15:00] <diddledan> `version: 0` is actually invalid because snapcraft (or rather the python yaml parser) reads it as a number when it's expecting a string
[15:00] <ogra> diddledan, it doesnt for me
[15:00] <diddledan> replacing it with `version: '0'` works
[15:01] <ogra> i just took one of my snaps changed version to 0 and called snapcraft ... no errors for me
[15:02] <ali1234> okay i did "snapcraft init" and then "snapcraft" - it's hanging at launching the VM again
[15:04] <diddledan> ogra: with ali1234's yaml: https://www.irccloud.com/pastebin/OeZVLYOb/
[15:05] <ali1234> "snapcraft init" also generates a quoted version field
[15:05] <zyga> niemeyer: the wikipedia reference on that bug is fantastic
[15:05] <zyga> "That looks great. Just one thing: get rid of the duck."
[15:05] <zyga> :"D
[15:05] <ogra> diddledan, well, but that snapcraft.yaml is generalyl broken
[15:06] <diddledan> the rest of the brokenness is besides the point though. snapcraft _expects_ a string.
[15:06] <diddledan> if you managed to get a working build with a number then you've hit a bug
[15:06] <ali1234> i just tried removing the quotes from the generated snapcraft.yaml and it produces the same error
[15:07] <ali1234> the error message could be more helpful.
[15:09] <ali1234> is multipass using docker?
[15:09] <diddledan> no, kvm
[15:11] <ali1234> "multipass launch" works, it is actually doing something
[15:13] <ali1234> i can see qemu using CPU, it's still spinning though
[15:17] <ali1234> nope, failed
[15:20] <ogra> how ?
[15:20] <ogra> (surely different than before ?)
[15:20] <ali1234> nope, identical. it spins for about 8 minutes then says "launch failed: timed out waiting for instance to respond"
[15:22] <ali1234> now running it with verbose
[15:22] <ogra> have you tried a reboot ... or logout/login cycle, after installing multipass ?
[15:22] <ali1234> no
[15:22] <ogra> (did you wiggle the cable ?) :P
[15:23] <ali1234> https://paste.ubuntu.com/p/26DQgRrWKQ/
[15:24] <ogra> wow
[15:25] <ogra> classic snaps ... the pain ...
[15:25] <ogra> looks like it is somehow clashing with your deb-installed qemu
[15:26] <ali1234> i have qemu arm installed
[15:26] <ogra> there is a #multipass channel
[16:12] <ali1234> okay so multipass works now. how do i tell it to stage i386 packages?
[16:12] <ali1234> i tried "--target-arch=i386" but it had no effect. dpkg still only supports amd64 inside the instance
[16:13]  * cachio lunch
[16:15] <ali1234> ah there we go. run snapcraft with --debug, then run "sudo dpkg --add-architecture i386" inside the instance, then exit and run snapcraft again
[16:30] <zyga> I found a bug in go :)
[16:30] <zyga> but that's for next week
[16:30] <zyga> I'm happy I also found a workaround
[16:30] <Crocodillian> I'm trying to install spotify from snap, when it tries to download a core it says x509: certificate has expired or is not yet valid
[16:31] <Crocodillian> is ssl just broken on my system
[16:32] <zyga> Crocodillian: is the time set correctly?
[16:32] <zyga> perhaps some certs *are* invalid though
[16:32] <Crocodillian> no, it looks like my timezone is wrong
[16:32] <Crocodillian> thanks!
[16:39]  * cmatsuoka creates his first wine-based snap package
[16:39] <cmatsuoka> lots of room for improvements tho
[16:42]  * zyga takes a small break
[16:42] <mup> PR snapd#6361 opened: kvm: load required kernel modules if necessary <Created by gerboland> <https://github.com/snapcore/snapd/pull/6361>
[17:22] <zyga> mwhudson: hey
[17:22] <zyga> not sure if you are the person to go to
[17:22] <zyga> but I'm pretty much hopeless now :)
[17:22] <zyga> https://github.com/golang/go/issues/29689
[17:35] <mup> PR snapd#6362 opened: cmd/snap-update-ns: explicitly check for return value from parse_arg_u <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6362>
[17:35] <mup> PR snapd#6363 opened: cmd/snap-update-ns: save errno from strtoul <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6363>
[17:36] <mup> PR snapd#6364 opened: cmd/snap-update-ns: let the go parser know we are parsing -u <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6364>
[17:41] <mup> PR snapd#6365 opened: cmd/snap-update-ns: manually implement isspace <Per-user mount ns  🐎> <Created by zyga> <https://github.com/snapcore/snapd/pull/6365>
[17:41] <zyga> Chipaca: ^ (that last one is cool0
[17:42]  * Chipaca is suspicious of C code being called  "cool0"
[17:42] <Chipaca> zyga: is the C string being passed zero-terminated?
[17:43] <zyga> Chipaca: yes
[17:43] <Chipaca> zyga: does it still crash if you -O0?
[17:43] <zyga> look at https://github.com/zyga/go-bug-29689
[17:43] <zyga> isspace doesn't care
[17:43] <zyga> calling issspace(0) is enough
[17:43] <zyga> or whatever
[17:43] <zyga> ideas welcome :)
[17:44] <zyga> you can also shrink the reproducer even more if you want
[17:52] <Chipaca> zyga: yeah that's not a "minimal" reproducer
[17:52] <mborzecki> zyga: that go bug, doesn't crash here
[17:52] <Chipaca> still, strange
[17:52] <Chipaca> mborzecki: 1.10?
[17:52] <zyga> wait, you mean you can run my reproducer
[17:52] <zyga> and not crash>
[17:52] <mborzecki> 1.11.4
[17:52] <zyga> I triied on 1.10 and 1.11.4
[17:53] <zyga> and my keyboard seems to have some repeat issues sometimes, weird
[17:53] <zyga> mborzecki: go build && ./go-bug 1000
[17:53] <zyga> that doesn't crash for you?
[17:53] <zyga> maybe depends on locale/
[17:53] <mup> Bug #1000: There are too many bug reports in Malone <lp-foundations> <NULL Project:Invalid> <https://launchpad.net/bugs/1000>
[17:53] <mborzecki> uh, ok, that crashes
[17:54] <mborzecki> haven't passed any args before :P
[17:55] <zyga> :D
[17:55] <zyga> README
[17:55] <zyga> but that's good
[17:55] <zyga> it's just broken
[17:56] <mborzecki> hm, idk why but it doesn't crash under dlv, or maybe i'm not passing the command line args again
[17:57] <Chipaca> hm
[17:57] <Chipaca> zyga: if I remove the __attribute__ bit it no longer crashes
[17:58] <zyga> because that code doesn't run anymore
[17:58] <zyga> add printf to check
[17:58] <mborzecki> zyga: must be some weird libc interaction, when built statically it doesn't crash
[17:58] <zyga> perhaps the problem is related to how isspace is implemented
[17:58] <zyga> it uses a lookup table
[17:59] <zyga> perhaps that code runs before various relocations are applied?
[17:59] <zyga> but meh
[17:59] <zyga> not fun
[17:59] <zyga> and makes me think we should split out the C code to snap-run-in-namespace --user --snap-name
[18:00] <mborzecki> zyga: that's from s-u-n right?
[18:00] <zyga> yes
[18:01] <mborzecki> zyga: i recall having some issues with code crashing in isalpha in s-u-n back when i was working on parallel instances
[18:01] <mborzecki> would crash unless i build the binary statically
[18:02] <Chipaca> building it statically has it not working again
[18:02] <zyga> ha
[18:02] <zyga> interesting
[18:02] <Chipaca> zyga: what is it that calls bootstrap()?
[18:02] <zyga> not working?
[18:03] <zyga> Chipaca: the dynamic linker
[18:03] <Chipaca> zyga: as in it isn't called
[18:03] <zyga> look at main.go
[18:03] <zyga> er
[18:03] <zyga> bootstrap.go
[18:03] <zyga> it's explained there
[18:03] <zyga> *MAGIC*
[18:06] <mborzecki> zyga: looking at glibc implementation, macro black magic f****ery, but it looks liek there's an array of points to actual functions that implement each op
[18:06] <zyga> you mean issspace/
[18:06] <zyga> isspace?
[18:06] <mborzecki> zyga: yeah
[18:07] <zyga> it looks like a single function call + array lookup on the result
[18:16] <mborzecki> zyga: right, so it's a LUT indexed by char, the table is in thread specific data (?), and that's set up by some early locale init
[18:17] <mborzecki> zyga: wonder what would hapend if i  add setlocale(LC_ALL, "") somewhere early
[18:18] <mborzecki> zyga: and it works now :P
[18:19] <mborzecki> zyga: https://paste.ubuntu.com/p/X2vgcX5Fr8/
[18:21] <Chipaca> zyga: so
[18:21] <Chipaca> zyga: you got a reply :-)
[18:22] <mborzecki> hah, makes sense
[18:25] <mup> PR snapcraft#2435 closed: Appstream desktop <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2435>
[18:34] <mborzecki> zyga: something to keep you busy on the flight, dump .preinit_array and .init_array and see where bootstrap ends up and where locale tables are set up
[18:37] <mup> PR snapcraft#2438 opened: rust plugin: new link for rustup <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2438>
[18:51] <zyga> Chipaca, mborzecki: so we were just lucky so far
[18:53] <mborzecki> zyga: and built statically, cause we had to
[18:53] <zyga> I think I will write a snap-lowlevel-exec
[18:53] <mborzecki> haha
[18:54] <zyga> I'm serious
[18:54] <zyga> this sucks
[18:54] <zyga> we can drop the c code from snap-update-ns this way
[18:54] <mborzecki> zyga: srsly, maybe we should take a look at what podman/docker/crio
[18:54] <zyga> we did
[18:54] <zyga> they do setns the same way
[18:55] <mborzecki> same preinit_array trick?
[18:55] <zyga> at least AFAIK
[18:55] <zyga> I can be wrong
[18:55] <mborzecki> zyga: otoh, there's no pressing need to fix it right away, so we can take time and research
[18:56] <zyga> yeah
[18:56] <zyga> as long as we don't need to call more functions :)
[18:56] <zyga> can you review https://github.com/snapcore/snapd/pull/6365 please
[18:56] <mup> PR #6365: cmd/snap-update-ns: manually implement isspace <Per-user mount ns  🐎> <Created by zyga> <https://github.com/snapcore/snapd/pull/6365>
[18:56] <zyga> I'm still pushing out the user-mount patches
[18:56] <mup> PR snapd#6352 closed: many: remove .user-fstab files from /run/snapd/ns <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6352>
[18:59] <mborzecki> zyga: even if you drop isspace, there's still islower & isdigit in the code
[18:59] <zyga> but it doesn't crash
[18:59] <zyga> perhaps doesn't need a table the same way?
[18:59] <zyga> I'm after getting fixes in place :)
[18:59] <mborzecki> zyga: i suppose you need to use a snap name with instance key
[18:59] <zyga> oh
[18:59] <zyga> I see
[19:02] <mborzecki> wrapping it up
[19:02] <mborzecki> zyga: pedronis: save travel
[19:02] <zyga> thank you!
[19:02] <mborzecki> s/save/safe/ :)
[19:02] <mborzecki> enjoy the summer
[19:02] <zyga> HAHA
[19:02] <zyga> I think I will :)
[19:50] <mup> PR # closed: core-build#11, core-build#22, core-build#26, core-build#37
[19:51] <mup> PR # opened: core-build#11, core-build#22, core-build#26, core-build#37
[19:58] <mup> PR snapd#6366 opened: cmd/snap-discard-ns: fix name of user fstab files <Per-user mount ns  🐎> <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6366>
[19:59] <mup> PR snapd#6367 opened: cmd/snap-update-ns: allow switching to user mount namespace <Created by zyga> <https://github.com/snapcore/snapd/pull/6367>
[20:37] <mup> PR core#38 closed: Add another pi-config option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/38>
[20:37] <mup> PR core#83 closed: move most of the ubuntu-core config deb into the snap snap build <Created by mvo5> <https://github.com/snapcore/core/pull/83>
[20:37] <mup> PR core#98 closed: Add force_turbo rpi option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/98>
[20:38] <mup> PR core#38 opened: Add another pi-config option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/38>
[20:38] <mup> PR core#83 opened: move most of the ubuntu-core config deb into the snap snap build <Created by mvo5> <https://github.com/snapcore/core/pull/83>
[20:38] <mup> PR core#98 opened: Add force_turbo rpi option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/98>
[20:55] <diddledan> is mup ok?
[20:55] <diddledan> 4 successive "this was closed.. oh no, psych! it's open really :-p" messages
[21:00] <mup> PR snapcraft#2439 closed: snap: add xslt dependencies for lxml <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2439>
[21:03] <mup> PR snapcraft#2439 opened: snap: add xslt dependencies for lxml <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2439>
[21:19] <mup> PR snapd#6368 opened: tests: check denials considering all the log lines instead of last 100 lines <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/6368>
[22:22] <om26er> popey, ping
[22:48] <mup> PR snapd#6369 opened: Add check for snap binaries dir not being in path <Created by liamg> <https://github.com/snapcore/snapd/pull/6369>


[04:23] <user|75> In the middle of kubuntu update and on lock screen. Blank doesn't seem to work when I googled. Anyone know what it is?
[04:24] <user|75> Install from DVD iso
[04:24] <user|75> Live session user
[07:40] <forcefull> hey, I just installed kubuntu, and for some reason bluetooth gets automatically turned on when I boot the system. is there a way to turn that off?
[07:53] <weedmic> go to system settings>type blue tooth>edit it at will
[07:53] <weedmic> forcefull: ^
[07:59] <forcefull> weedmic: well if system settings would open :) will relog in to see if that fixes it
[08:02] <forcefull> weedmic: thanks :) one issue down. do you have any idea about the non-centered windows?
[08:03] <forcefull> oh I should meantion that I am on the kubuntu-ppa/backports plasma. this still happens on kubuntu 23.04 "proper"
[08:12] <weedmic> forcefull: pls post a link to a pic of "non centered windows" - I do not know what you mean.  i also have no idea what "kubuntu-ppa/backports plasma".  plasma sounds like kde to me though.
[08:13] <forcefull> weedmic: the kubuntu team pushes newer plasma releases (and backports them to older distro releases) on the launchpad.net platform
[08:16] <forcefull> weedmic: and this is what happens when I open windows which are not maximized https://paste.opensuse.org/pastes/57b13259a532
[08:16] <forcefull> (but system settings is configured to centered for new windows)
[08:30] <weedmic> how is that not centered forcefull?
[08:30] <weedmic> because they are tiled after the first one, but only ?near? the centre?
[08:30] <forcefull> weedmic: oO the first window (lowest) is centered all the other ones are offcenter
[08:30] <forcefull> yes
[08:34] <weedmic> where did you find the center command - i'm not having luck b/c I have forgotten what it is in english
[08:35] <forcefull> system settings -> window management -> advanced
[08:35] <forcefull> but there is no command afaik
[08:36] <weedmic> somewhere near there I remember the word "tiled", if you find it, try to unclick it and see if they stack directly on eachother (which I believe is what you want).
[08:39] <weedmic> System Settings > Workspace Behavior > Desktop Effects - uncheck "present windows"
[08:40] <weedmic> if it doesn't work - put it back
[08:40] <forcefull> I can't even find that setting
[08:41] <weedmic> I stopped going there when they got rid of cube :( :(
[08:41] <forcefull> weedmic: nope, does nothing
[08:41] <weedmic> which part is missing "desktop effect"?
[08:42] <weedmic> o, try this - just a sec
[08:42] <weedmic> to restart plasma - (faster than a logout login) "killall plasmashell;plasmashell > /dev/null 2>&1 &"
[08:44] <forcefull> weedmic: you mean with the present window disabled?
[08:47] <weedmic> u lost me
[08:47] <forcefull> well, as I understand, I should disable the present windows setting (like you said above) and then afterwards restart plasma?
[08:48] <weedmic> i meant that some changes to setting require you to logout and log backin for the kde to reset - or one could just do that command
[08:48] <forcefull> ahh kk so I understood you correct
[08:48] <forcefull> brb (damn wayland shell)
[08:48] <weedmic> oic, by windows setting you meant desktopeffect - sorry my english for these terms is pretty limited
[08:48] <weedmic> and is basically calling everything "a number"
[08:49] <weedmic> I am not using wayland,
[08:50] <forcefull> weedmic: nope :S doesn't help
[08:50] <weedmic> "inxi -Gxx | grep compositor"  compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
[08:50] <forcefull> weedmic: command inxi not found ;)
[08:51] <forcefull> but I can definitely say I am on wayland
[08:51] <weedmic> sorry, no other ideas. I have mine at center, and opened 5 windows and they are on top of eachother - even with that checked.
[08:51] <weedmic> you can check with "inxi -Gxx | grep compositor"
[08:51] <forcefull> interesting. as this also happens to me with the normal plasma version which kubuntu ships
[08:52] <forcefull> weedmic: inxi is not installed, but grepping the plasma process, it says it's plasma
[08:52] <forcefull> wayland not plasma
[08:52] <forcefull> maybe it is wayland :S
[08:52] <forcefull> but need that, as I need fractional scaling
[08:52] <weedmic> as long as it works :)
[08:53] <forcefull> well it doesn't :P
[08:53] <weedmic> to me wayland is a compositor, like x or kwin
[08:53] <weedmic> it does, just you have not found the ?minutiae" you need - it exists
[08:53] <forcefull> yeah, I was only saying that maybe because I am on wayland, the centered thing doesn't work.
[08:54] <forcefull> I will still look around :)
[08:54] <weedmic> I have doubts that is possible.
[08:54] <weedmic> me too
[08:55] <forcefull> oh last question. can I change somewhere what happens when I lock the screen and/or close the lid?
[08:55] <forcefull> nothing under display or power management
[08:56] <forcefull> oh lol
[08:56] <forcefull> I am blind
[08:56] <weedmic> I have done mega changes under appearance, you may find the setting there (but may very well not find it).
[08:56] <weedmic> yes, but u found it.  i have my set to do nothing and have the display set to monitors 2 & 3 (at work), at home no comptuers close
[08:57] <forcefull> weedmic: thank you for the help :). need to go offline.
[08:57] <weedmic> enjoy rl
[08:57] <forcefull> weedmic: my problem is when my screen turns off, my laptop crashes
[08:57] <forcefull> hellp dell :(
[08:57] <weedmic> they just released a firware update for that, installed it 2 days ago.
[08:57] <forcefull> (they even sold the laptop with ubuntu)
[08:58] <forcefull> weedmic: doubt that, as my laptop is 5-6 years old. and even on windows the laptop crashes when it goes to sleep
[08:58] <weedmic> although it didn't affect me personally.  "Latitude_5430_1.13.1.exe"
[08:59] <weedmic> check for updates, if there are any firmware ones, it will tell you.  then read fwupdmgr to find out how to install it.
[08:59] <forcefull> damn I have a latitude 5490
[08:59] <weedmic> man:fwupdmgr
[08:59] <forcefull> weedmic: fwupdmgr tells me no update. so maybe it will still get released
[08:59] <weedmic> best of luck - they are playing lunch time over th espeakers
[09:00] <forcefull> let's hope. the crazy part to me is that only with kernel 6.0-6.2 got the laptop usable on linux :(
[09:00] <forcefull> so now heading off :) hf :D
[09:22] <user|59> Hello. Kubuntu stacks on login screen when password is expiried.
[09:22] <user|59> it's just doesn't show new password fields after password enter
[09:22] <user|59> I know how to change it another way, but I need it work in gui
[09:22] <user|59> The same problem in 22 and 20 kubuntu, but still can't find any answer in internet
[09:24] <weedmic> user|59: do you know the credentials of any "sudo group" member?
[10:16] <user|59> user|59: I know, But I wana make it work via GUI
[10:16] <user|59> I want change expired password via GUI
[10:37] <weedmic> user|59: if you have the credentials to any sudo user, you can drop to init3. reset the password for the user who cannot get in, and return to init 5 (or 7 where the gui login is) and type in the new password you just assigned.
[10:37] <weedmic> if you don't know any valid credentials, it only gets more difficult.
[11:09] <user|59> Ok I have sudo user credentials. But how make work this GUI options, so will appear fields for new password?
[11:13] <weedmic> user|59:  if you have the credentials to any sudo user, you can drop to init3. reset the password for the user who cannot get in, and return to init 5 (or 7 where the gui login is) and type in the new password you just assigned.
[11:19] <skramer> I seem to have an issue with one of my laptops running 22.04 recently. It boots up & I can log into Plasma. I am even able to type the pass for NetworkManager. But after that, nothing happens anymore.
[11:21] <skramer> In Personal Folderr, only the Pictures subfolder has it's icon. Rest of them is just standard blue. Also noticed that the volume control is crossed out.
[11:22] <user|59> weedmic : So, after it, next time when password expired, will expired password chaninging fine, and will GUI show me fields for new password?
[11:23] <skramer> What could be the reason for this issue? ...btw. SSH into the console works perfectly fine. I could do updates from there, starting a VirtualBox from console also works & I could connect to that VM via both, SSH and RDP
[11:24] <weedmic> my english is not powerful enough to get your meaning user|59.  What do you think is the difference between the "user password" and this "gui password"?  how can they not be the same?  is the gui perhaps the password on some external device - like a cloud server or something?
[11:25] <user|59> do you speak russian?
[11:26] <user|59> my english not so good too.
[11:26] <user|59> To change password is not a problem.
[11:26] <weedmic> po moemy, lucho zdesx razgovorovatx po-angliski
[11:26] <user|59> I wana fix this GUI bug
[11:26] <user|59> I wana see this fileds for new password
[11:27] <weedmic> perhaps, once you can login, you can make those changes.
[11:44] <weedmic> If I understood him in private chat correctly, the real issue for user|59 is that things are working, but... what he wants is when a user's password is to expire or has expired, he should be prompted at login to set a new password.  I think it is KDE sddm, but I cannot tell.  He has two pics he can post.
[11:44] <weedmic> user|59: i zabyl sprasit, izvenit moe ploxoj russkij yazyk.
[13:10] <BluesKaj> Hi all
[18:51] <user|14> Hello what are the system requirements for this os
[20:10] <mparillo> It might be a bit lighter than Ubuntu, but keep in mind that these are the MINIMUM requirements. https://help.ubuntu.com/community/Installation/SystemRequirements First thing I would do is get an SSD, second would be to double the RAM from 4 to 8 GB.
[21:04] <torm> Anyone know how to fix the default playback volume always being set to 100%?
[21:08] <torm> Never mind


[09:55] <soee> good miorning
[11:08] <BluesKaj> Hey all
[16:25] <shadeslayer> loads of fun installing Ubuntu on a Win8 machine today
[16:28] <ronnoc_> shadeslayer: any UEFI issues?
[16:30] <shadeslayer> yep
[16:31] <shadeslayer> secure boot was to blame 99% of them
[16:31] <shadeslayer> because as it turns out even if you load signed grub , you can't run commands from the grub prompt
[16:31] <shadeslayer> so things like ls won't work
[16:32] <shadeslayer> as well as drivemap
[16:32] <shadeslayer> becuase SB treats them as insecure binaries I guess
[16:32] <shadeslayer> then the chainloader command won't work because it can't find the windows 8 efi bootloader
[16:33] <shadeslayer> debugging from grub was made extremely hard due to Secure Boot
[16:33] <shadeslayer> so I had to disable it
[16:33] <shadeslayer> BUT
[16:33] <shadeslayer> if you just use K/Ubuntu, you can use Secure Boot
[16:33] <shadeslayer> a huge win if you ask me
[16:34] <shadeslayer> oh and the BIOS is funky, you have disable fast bios loading to change boot order
[22:42] <BarkingFish> evening guys :)  Long time no see.  Can someone please tell me what the security update to VLC is please?  I'm not getting any change data in apper, and I'm streaming using VLC right now.
[22:47] <TheLordOfTime> wouldn't it be in the changelogs?
[22:47] <TheLordOfTime> (sorry, but... it's a valid point)
[22:50] <BarkingFish> It would be, I'm sure - if I could remember how to get at them.  I have a memory like a colander and all the recall skills of a goldfish.
[22:53] <BarkingFish> nvm, found it - apparently it's something to do with a buffer overflow, which can allow arbitrary code to be executed, so I'm guessing it's probably something I shouldn't be ignoring right now :)
[22:53]  * BarkingFish closes his vlc stream and updates :)
[22:55] <TheLordOfTime> BarkingFish, :P
[23:07] <allee> afiestas: FYI the last libkscreen commit breaks compilation on quantal: http://paste.kde.org/645422/