[12:50] <angretlam> Hi all.
[16:35] <d0cK> hey there anyone on a cigarette break want to spend a second for helping me in a jack firewire related issue?
[16:40] <d0cK> I shortly type it down, if anyone read it and know a fast way to point me on the right direction it would be greatly appreciated:
[16:41] <d0cK>  /dev/shm/jack-1000  directory is missing.


[15:55] <pleia2> popey: people keep joining the #ubuntu-doc channel asking about google code-in things, and no one who lurks there seems to know anything about it, can you clue us in?
[15:56] <wxl> pleia2: ask them to provide a link to their task instance. there must be something in the description that suggests that for some reason
[15:56] <pleia2> they seem to be having a really poor experience since no one is hanging out there to help them out, I had never even heard about tutorials.ubuntu.com
[15:56] <pleia2> wxl: I am not around enough to pitch in here, I usually see the messages after they've left
[15:56] <pleia2> it would be good if someone leading this could join
[15:56] <wxl> ah actually that's the hint i need
[15:58] <pleia2> at least an email to ubuntu-doc telling us that students would be pointed our direction would have been nice
[15:58] <wxl> i'm not sure that's the case
[15:58] <popey> Hm
[15:58] <popey> Are there tasks which point students to that channel?
[15:59] <pleia2> I don't even know where the tasks are
[15:59] <wxl> popey: i'd start by looking at the tutorials one
[15:59] <wxl> as that's something one of the students (or more) mentioned
[15:59] <pleia2> all I've found was https://community.ubuntu.com/t/ubuntu-participation-in-google-code-in/271 announcing it back in October
[15:59] <wxl> s/\(one\)/\1s/
[15:59] <pleia2> it's a lot of people though, coming in through webchat
[16:00] <pleia2> https://irclogs.ubuntu.com/2017/12/30/%23ubuntu-doc.html
[16:00] <pleia2> https://irclogs.ubuntu.com/2017/12/29/%23ubuntu-doc.html
[16:00] <pleia2> usually no one talks there :)
[16:00] <popey> I'd rather we pointed people at the #ubuntu-google  channel
[16:01] <popey> As we all hang out there
[16:02] <popey> We can edit the tasks to use an active channel
[16:03] <pleia2> thank you
[16:03] <pleia2> I mean, I think the team would be happy to help if 1) we were told 2) we had anything to do with tutorials.ubuntu.com
[16:04] <wxl> yeah that would be a bit problematic XD
[16:09] <popey> I think it was just assumed that the doc channel was were the people who look after tutorials site hung out
[16:26] <pleia2> according to https://insights.ubuntu.com/2017/01/20/tutorials-ubuntu-com-goes-live/ it looks like it's a Canonical-driven thing that communicates mostly via GitHub
[16:28] <pleia2> the docs team works on help.ubuntu.com, which still uses launchpad, bzr, the wiki and the ubuntu-doc mailing list
[16:30] <wxl> popey: you working on fixing those? i can help now if need be
[16:31] <popey> I'll take  a look now
[16:31] <wxl> i'll work from the bottom up, you go top down :)
[16:31] <wxl> i'll just change to ubuntu-google? or leave well enough alone?
[16:31] <wxl> s/leave well enough alone/remove the IRC reference altogether/
[16:32] <wxl> the way i read it, it suggests that the channel is a resource for help in re: keeping to ubuntu doc styles?
[16:32] <popey> i just changed the last line
[16:32] <popey> "* Join the IRC channel #ubuntu-doc on freenode"
[16:33] <pleia2> where are these tasks?
[16:33] <wxl> what did you change it to?
[16:33] <wxl> pleia2: example https://codein.withgoogle.com/dashboard/tasks/6319153562517504/
[16:33] <wxl> they're all on the GCI website
[16:34] <wxl> of course you probably won't even be able to see that
[16:34] <pleia2> wxl: doesn't seem public :\
[16:34] <wxl> remove the "dashboard" from the URL
[16:34] <pleia2> ok
[16:34] <pleia2> ah, https://codein.withgoogle.com/tasks/?sp-organization=5133577048031232
[16:34] <popey> i just changed -doc to -google
[16:34] <popey> done ~20 of them
[16:35] <wxl> aw shoot
[16:35] <popey> (there are 80)
[16:35] <popey> ( just searched for 'tutorial' in the task dashboard)
[16:36] <popey> seems I missed some, as some have the web chat link at the top
[16:36] <popey> I'll do  keep going on them :)
[16:36] <wxl> i'll look out for that
[16:46] <popey> Thanks for letting us know about the mistake pleia2
[16:46] <popey> Much appreciated!
[16:46] <pleia2> just learned that the channel is mentioned on https://tutorials.ubuntu.com/tutorial/tutorial-guidelines#9
[16:46] <pleia2> "Join the #ubuntu-doc channel on Freenode IRC to chat with the doc team and share your thoughts
[16:47] <pleia2> so this seems like a pretty awful mess, there's never been any discussion about this site with the docs team, but they tell people to talk to us x_x
[16:47] <wxl> yeah we'll need to talk to those folks
[16:47] <pleia2> I'm dropping an info email to the ubuntu-doc list now in case anyone else is as confused as I am
[16:49] <popey> To be fair, the people who maintained that site are actually in the -doc channel
[16:49] <wxl> hm
[16:50] <wxl> here's that tutorial https://github.com/canonical-websites/tutorials.ubuntu.com/blob/master/tutorials/community/tutorial-guidelines.md
[16:50] <wxl> you could certainly file an issue against it, pleia2. that might be a good start
[16:50] <pleia2> popey: why don't they respond to any of the questions?
[16:51] <popey> over the last few days, probably afk on vacation mostly
[16:51] <popey> I don't always reply on irc unless pinged directly
[16:51] <wxl> caldav and didirocks are the big contributors to that particular tutorial
[16:51] <popey> looks like that line was added about a month ago.
[16:52] <wxl> yep and by caldav
[16:52] <wxl> aka, in our world, davidcalle
[16:52] <popey> I think the assumption was just that documentation = -doc channel, so that was the default sane place to point people on irc
[16:53] <wxl> or davidc3 on launchpad
[16:54] <pleia2> the topic of the channel is pretty clear as to what the team is for ;) I don't think the team would mind other documentation efforts joining it, but no one told us
[16:54] <pleia2> feels a little unsettling to have our channel hijacked, and it makes us look bad
[16:55] <pleia2> can't imagine it looks great when students join and we have no idea what they're talking about either
[16:55] <wxl> he doesn't appear to be on the docs team so that may have something to do with not spreading the word XD
[16:55] <pleia2> I'll include David on this email I send to the doc team
[16:56] <wxl> yeah well, honestly, it's kind of been an issue in general over the past week due to the holidays. the timing sucks
[16:57] <popey> I don't think the intention was to hijack anything.
[16:57] <popey> Just point people at the most appropriate channel.
[16:58] <wxl> oh i agree with that


[13:12] <nibbon_> what's the special spell to perform an early microcode update? I tried following this https://docs.kernel.org/x86/microcode.html#early-load-microcode but didn't work
[13:13] <nibbon_> I'm trying to build a initramfs to boostrap a system via tftp
[13:55] <vic-thor> can anyone point me some documentation or something about how the linux-firmware package is created?
[13:55] <vic-thor> all i find are packages which already contain the binaries
[15:34] <ogra> vic-thor, what else would you expect ? it is firmware ... there are no sources available for any of the files in there
[15:38] <vic-thor> where do they come from, for example
[15:38] <vic-thor> how does it the linux-firmware "official" git gets filtered
[15:38] <vic-thor> which files are included and which not
[15:55] <ogra> i guess from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[15:59] <vic-thor> yes, but how to go from the all whole of that to the "chosen ones" in the ubuntu package
[16:05] <ogra> "chosen ones" ?
[16:07] <ogra> i'm pretty sure the ones in the ubuntu package are from a simple tarball download from that repo (plus perhaps some extra ones added that are proven to be on their way into the kernel.org repo in the near future)
[16:58] <vic-thor> no, the files on the git are much, much more
[16:59] <vic-thor> then yes, there are some extras and some other tweakings, but from the official one thre is pruning for sure
[17:46] <tomreyn> vic-thor: this is more a topic for #ubuntu, not exactly kernel related. see https://launchpad.net/ubuntu/+source/linux-firmware for more information on how the package is built.
[17:47] <tomreyn> hmm okay it says it's managed by the kernel team, so i guess asking here is not wrong
[18:58] <klebers> juergh, ^


[08:29] <yang> I received Utilite Computer, and I don't get any picture on TV, via HDMI-out ?
[08:30] <yang> I assume that even if there is no OS installed on it, there should be a picutre via HDMI-out ?
[08:30] <yang> How should I proceed ?


[02:41] <snail> we'll looking for a senior networky-type person http://vacancies.vuw.ac.nz/positiondetail.asp?p=6689
[20:31] <ajmitch> morning
[20:41] <Atamira> morning


[03:05] -queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [17.03.2-0ubuntu1~16.04.1 => 17.03.2-0ubuntu3~16.04.1] (no packageset)
[04:00] <tsimonq2> slangasek: Finished my last round of initial triaging of the Qt 4 bugs; https://is.gd/pRDB9o should be good now for a while.
[04:04] <slangasek> doko: ocrmypdf> your 5.5-2ubuntu1 didn't show much in the way of test failures because tesseract-ocr and ghostscript were missing from the build-dependencies... I added them and now I see what you mean (and regretted having done so).  Do you think it's better that I upload this package with this horrible testsuite that leaves dozens of tesseract processes spinning and eating CPU, or just leave
[04:04] <slangasek> it as-is?
[04:22] <slangasek> tsimonq2: will someone update the kubuntu seeds to drop ksaneplugin from 'supported'?
[04:34] <tsimonq2> slangasek: I don't have access myself, but yes.
[04:40] <tsimonq2> slangasek: processing> Many thanks.
[04:42]  * slangasek nods
[04:42] <slangasek> now I move on to debugging node-mapnik autopkgtest failures, and am reminded that the quoting rules for debian/tests/control are both undocumented and terrible
[04:50]  * tsimonq2 doesn't want to have my name on nodejs anymore, make it go awaaaaaaaaaaay
[04:50] <tsimonq2> :)
[04:50] <tsimonq2> I mean, I'll follow through with this one, but... :/
[05:12] -queuebot:#ubuntu-release- New binary: choqok [s390x] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: choqok [ppc64el] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:14] -queuebot:#ubuntu-release- New binary: choqok [amd64] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: choqok [i386] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New: accepted choqok [amd64] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:18] -queuebot:#ubuntu-release- New: accepted choqok [ppc64el] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:18] -queuebot:#ubuntu-release- New: accepted choqok [i386] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:18] -queuebot:#ubuntu-release- New: accepted choqok [s390x] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:19] -queuebot:#ubuntu-release- New binary: choqok [arm64] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: choqok [armhf] (bionic-proposed/universe) [1.6-1.isreally.1.6-2.1] (no packageset)
[05:19] <tsimonq2> slangasek: Can you please RM src:gcompris? Scott K just removed from Debian, Debian bug 893464
[05:22] <tsimonq2> slangasek: (For future ref, does following Debian on package removals even when the package has a delta need a bug?)
[05:39] <slangasek> tsimonq2: generally no bug needed, as long as I can figure out that the package isn't being maintained in Ubuntu
[05:39] <tsimonq2> slangasek: OK cool.
[05:47] -queuebot:#ubuntu-release- New: accepted choqok [arm64] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:47] -queuebot:#ubuntu-release- New binary: mir [s390x] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[05:47] -queuebot:#ubuntu-release- New: accepted choqok [armhf] (bionic-proposed) [1.6-1.isreally.1.6-2.1]
[05:51] -queuebot:#ubuntu-release- New: accepted virtualbox-hwe [source] (bionic-proposed) [5.2.8-dfsg-5ubuntu18.04.1]
[05:56] -queuebot:#ubuntu-release- New binary: mir [ppc64el] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[06:01] -queuebot:#ubuntu-release- New binary: mir [i386] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[06:06] -queuebot:#ubuntu-release- New binary: mir [amd64] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[06:11] -queuebot:#ubuntu-release- New binary: puma [s390x] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:12] -queuebot:#ubuntu-release- New binary: puma [i386] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:12] -queuebot:#ubuntu-release- New binary: puma [ppc64el] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:13] -queuebot:#ubuntu-release- New binary: puma [armhf] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:14] -queuebot:#ubuntu-release- New: accepted puma [armhf] (bionic-proposed) [3.6.0-1ubuntu3]
[06:14] -queuebot:#ubuntu-release- New: accepted puma [ppc64el] (bionic-proposed) [3.6.0-1ubuntu3]
[06:14] -queuebot:#ubuntu-release- New binary: puma [amd64] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:14] -queuebot:#ubuntu-release- New: accepted puma [i386] (bionic-proposed) [3.6.0-1ubuntu3]
[06:14] -queuebot:#ubuntu-release- New: accepted puma [s390x] (bionic-proposed) [3.6.0-1ubuntu3]
[06:15] -queuebot:#ubuntu-release- New binary: puma [arm64] (bionic-proposed/universe) [3.6.0-1ubuntu3] (no packageset)
[06:25] -queuebot:#ubuntu-release- New: accepted puma [amd64] (bionic-proposed) [3.6.0-1ubuntu3]
[06:25] -queuebot:#ubuntu-release- New: accepted puma [arm64] (bionic-proposed) [3.6.0-1ubuntu3]
[06:27] <slangasek> tsimonq2: on the nodejs front, is node-tape anything that's on your radar? Debian bug #893337
[06:28] <tsimonq2> slangasek: Ah, I hadn't seen that; thanks.
[06:29] -queuebot:#ubuntu-release- New binary: virtualbox-hwe [i386] (bionic-proposed/multiverse) [5.2.8-dfsg-5ubuntu18.04.1] (no packageset)
[06:29] <tsimonq2> slangasek: Is that already badtested?
[06:29] <slangasek> tsimonq2: it is not.
[06:29] <tsimonq2> slangasek: Do you plan on badtesting it?
[06:29] <slangasek> the version in -proposed has regressed the tess
[06:29] <tsimonq2> Ah.
[06:29] <slangasek> no
[06:29] <tsimonq2> Gotcha.
[06:30] <slangasek> (I plan on removing it from -proposed, if no one cares about it)
[06:31] -queuebot:#ubuntu-release- New binary: mir [arm64] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[06:31] <tsimonq2> My vote is do it .
[06:35] -queuebot:#ubuntu-release- New binary: mir [armhf] (bionic-proposed/main) [<IP_ADDRESS>-0ubuntu1] (desktop-core)
[06:37] -queuebot:#ubuntu-release- New binary: virtualbox-hwe [amd64] (bionic-proposed/multiverse) [5.2.8-dfsg-5ubuntu18.04.1] (no packageset)
[06:37] <slangasek> tsimonq2: done.
[06:38] <tsimonq2> slangasek: cool
[06:59] <tsimonq2> slangasek: Can I please get "force-badtest node-class-utils/0.3.5-1" added to hints? It's regressed in release: http://autopkgtest.ubuntu.com/packages/n/node-class-utils
[07:04] <tsimonq2> Thanks.
[07:27] <tsimonq2> General note: sbuild should migrate now with this new upload.
[07:34] <acheronuk> slangasek: ksaneplugin removed from Kubuntu supported
[07:34] <slangasek> acheronuk: cheers
[09:31] -queuebot:#ubuntu-release- New: accepted pyxs [source] (artful-proposed) [0.4.1+dfsg1-0ubuntu1~17.10.0]
[09:32] -queuebot:#ubuntu-release- New: accepted pyxs [source] (xenial-proposed) [0.4.1+dfsg1-0ubuntu1~16.04.0]
[09:32] -queuebot:#ubuntu-release- New binary: pyxs [amd64] (artful-proposed/none) [0.4.1+dfsg1-0ubuntu1~17.10.0] (no packageset)
[09:34] -queuebot:#ubuntu-release- New binary: pyxs [amd64] (xenial-proposed/none) [0.4.1+dfsg1-0ubuntu1~16.04.0] (no packageset)
[09:44] -queuebot:#ubuntu-release- New: accepted pyxs [amd64] (artful-proposed) [0.4.1+dfsg1-0ubuntu1~17.10.0]
[09:44] -queuebot:#ubuntu-release- New: accepted pyxs [amd64] (xenial-proposed) [0.4.1+dfsg1-0ubuntu1~16.04.0]
[10:16] -queuebot:#ubuntu-release- New: accepted rax-nova-agent [source] (artful-proposed) [2.1.12-0ubuntu2~17.10.0]
[10:21] -queuebot:#ubuntu-release- New: accepted rax-nova-agent [source] (xenial-proposed) [2.1.12-0ubuntu2~16.04.0]
[10:46] -queuebot:#ubuntu-release- New binary: rax-nova-agent [amd64] (artful-proposed/universe) [2.1.12-0ubuntu2~17.10.0] (no packageset)
[10:47] -queuebot:#ubuntu-release- New binary: rax-nova-agent [amd64] (xenial-proposed/universe) [2.1.12-0ubuntu2~16.04.0] (no packageset)
[11:00] -queuebot:#ubuntu-release- New: accepted rax-nova-agent [amd64] (artful-proposed) [2.1.12-0ubuntu2~17.10.0]
[11:00] -queuebot:#ubuntu-release- New: accepted rax-nova-agent [amd64] (xenial-proposed) [2.1.12-0ubuntu2~16.04.0]
[11:23] <cjwatson> slangasek: I guess I should technically ask for a feature freeze exception for versioned Provides support in germinate?  Though I've just deployed it on nusakan and I'm not sure changing it in the distro is risky by comparison :)
[11:25] <sil2100> cjwatson: I guess it would be good to have that documented with an FFe ;)
[11:26] <cjwatson> sil2100: repurposing https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/1758004 for that then
[11:26] <cjwatson> I've diffed full germinate output before and after that change and confirmed that every resulting difference is correct
[11:27] <cjwatson> (basically python{,3}-cffi-backend, some e2fsprogs transitional library packages dropping out, and some espeak packages dropping out because espeak-ng is now sufficient)
[11:28] <cjwatson> (the last doesn't affect images, only extra output)
[11:36] <sil2100> cjwatson: I approved the FFe o/ Thanks!
[11:37] <sil2100> (oh well formallities)
[11:38] <cjwatson> thank you
[14:53] <LocutusOfBorg> jamespage, hello, can you please do a python-msgpack/msgpack-python switch and merge from debian?
[14:54] <LocutusOfBorg> I can do it, but I have no way of testing the work
[14:54] <LocutusOfBorg> see https://packages.qa.debian.org/p/python-msgpack/news/20180323T133924Z.html
[14:54] <LocutusOfBorg> and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893844
[15:00] <LocutusOfBorg> jamespage, something like that https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8875622/+listing-archive-extra
[15:00] <LocutusOfBorg> even if renaming the package makes my brain segfault for upgrade path
[15:01] <jamespage> LocutusOfBorg: yes but won't be today...
[15:03] <LocutusOfBorg> I can do it, I'm already testing the upgrade path
[15:04] <LocutusOfBorg> that packaging should provide msgpack and python-msgpack so we should be safe
[15:04] <LocutusOfBorg> but in case, I would like to do a no-change rebuild of reverse-deps to be safe
[15:31] -queuebot:#ubuntu-release- New binary: ubuntu-wallpapers [amd64] (bionic-proposed/main) [18.04.0-0ubuntu1] (ubuntu-desktop)
[15:58] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.39.3+really2.35 => 2.40] (no packageset)
[15:59] <sergiusens> tjaalton: mind accepting ^
[16:33] -queuebot:#ubuntu-release- New source: python-msgpack (bionic-proposed/primary) [0.5.4-0ubuntu2]
[16:40] -queuebot:#ubuntu-release- Unapproved: xdg-user-dirs (xenial-proposed/main) [0.15-2ubuntu6 => 0.15-2ubuntu<IP_ADDRESS>] (core)
[16:46] <tjaalton> sergiusens: where's artful?
[16:47] <sergiusens> tjaalton: coming soon
[16:47] <tjaalton> how soon :)
[16:48] <tjaalton> I'm practically EOW
[16:53] <sergiusens> 10'
[17:03] <sergiusens> tjaalton: done
[17:04] -queuebot:#ubuntu-release- Unapproved: snapcraft (artful-proposed/universe) [2.35+17.10 => 2.40+17.10] (no packageset)
[17:48] <sergiusens> slangasek: mind accepting snapcraft into -proposed please? I think I might have missed Timo and his EOW warning
[18:11] <slangasek> sergiusens: sure, I will look at it
[18:16] <sergiusens> thank you very much
[18:17] <slangasek> sergiusens: you're wanting to land this in -proposed before the current one is released to -updates?
[18:19] <sergiusens> slangasek: if that is artful, yes, please pop 2.35+17.10  out of circulation; it will not even work on artful
[18:19] <slangasek> ok
[18:29] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (artful-proposed) [2.40+17.10]
[19:00] -queuebot:#ubuntu-release- New sync: python-certbot-dns-cloudflare (bionic-proposed/primary) [0.22.0-1]
[19:01] -queuebot:#ubuntu-release- Unapproved: neutron (artful-proposed/main) [2:11.0.3-0ubuntu1 => 2:11.0.3-0ubuntu1.1] (openstack, ubuntu-server)
[19:01] -queuebot:#ubuntu-release- New sync: python-certbot-dns-dnsimple (bionic-proposed/primary) [0.22.0-1]
[19:01] -queuebot:#ubuntu-release- New sync: python-certbot-dns-digitalocean (bionic-proposed/primary) [0.22.0-1]
[19:01] -queuebot:#ubuntu-release- New sync: python-certbot-dns-google (bionic-proposed/primary) [0.22.0-1]
[19:02] -queuebot:#ubuntu-release- New sync: python-certbot-dns-rfc2136 (bionic-proposed/primary) [0.22.0-1]
[19:05] <tjaalton> slangasek: re nss-pem; the pkg I uploaded merges src:nss source in it, but maybe it would be best to do the other way round instead (nss-pem is <100k unpacked), though that might end up being a permanent diff to debian since I doubt mike would accept that either..
[19:06] <tjaalton> "talk to upstream.." (which finally rejected it some years ago)
[19:21] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.40]
[19:23] <slangasek> tjaalton: hey, so, I was surprised when you said that was how you were handling nss-pem; I think duplicating the source of such a security-sensitive codebase as nss is not a great option
[19:23] <slangasek> tjaalton: I understand that you can't use the existing nss package because the libraries/headers are not made public by the Debian maintainer
[19:24] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.4.0-0ubuntu7.1 => 2:8.4.0-0ubuntu7.2] (openstack, ubuntu-server)
[19:24] <slangasek> tjaalton: but I don't understand why we're considering that decision by the Debian maintainer binding for what Ubuntu does.  Why do we not take a decision to support these as public interfaces, regardless of what Debian has decided, and carry a delta?
[19:25] <slangasek> it's not like we're creating our own shared libraries here... upstream is already shipping shared libraries, they just aren't shipped in /usr/lib
[19:44] <tjaalton> slangasek: well nss-pem needs static libs, of non-public interfaces that haven't changed in many years
[19:45] <tjaalton> sure we can carry a delta, if that's ok. but would that be packaging the headers/static libs on a separate package as proposed?
[19:47] <tjaalton> feel free to drop current nss-pem and I'll create a proper one, and can upload nss too with the new pkg
[19:51] <tjaalton> slangasek: put something in bug #1751140 so that it's not lost :)
[19:53] <slangasek> tjaalton: oh, these are interfaces that are currently not exposed at all in any of the shared objects, including those in /usr/lib/nss?
[20:00] <tjaalton> not all no
[20:04] <tjaalton> nssb can't be shared or there would be a circular dep
[20:08] <slangasek> ok
[20:08] <slangasek> let me ponder a bit more then
[20:10] <tjaalton> i might have more in emails from the redhat folks, need to check later..
[20:25] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (artful-proposed) [2.9.0-1ubuntu3.2]
[20:26] <tjaalton> slangasek: there's one thing though that might help with the decision; redhat is actively replacing nss with openssl, but certmonger hasn't been ported yet but it will be, at some point
[20:27] <tjaalton> so, could be the path of least effort is to provide only freeipa-client in the archive, and I'll put the rest in a ppa
[20:27] <slangasek> tjaalton: well, if you choose to withdraw this from the archive, that certainly spares me from having to make any decision, true ;)
[20:28] <tjaalton> just need to advise folks doing upgrades to enable the ppa
[20:29] <slangasek> I don't think there's any obligation that you do this
[20:29] <slangasek> I hate to encourage use of ppas
[20:29] <tjaalton> well, for freeipa-server users..
[20:29] <slangasek> and would rather figure out the right way to accept nss-pem
[20:29] <tjaalton> sure
[20:56] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (artful-proposed) [2:11.0.3-0ubuntu1.1]
[20:57] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.4.0-0ubuntu7.2]
[21:11] <LocutusOfBorg> [18:33:42] <LocutusOfBorg> please accept python-msgpack, it follows the same renaming that Debian did
[21:11] <LocutusOfBorg> [18:33:49] <LocutusOfBorg> msgpack-python -> python-msgpack
[21:11] <LocutusOfBorg> [18:33:54] <LocutusOfBorg> there aren't new binaries
[23:29] <tsimonq2> infinity: Did you have any luck figuring out the critical Lubuntu install bug?
[23:29] <tsimonq2> infinity: If not, might you have notes so I can take a look?
[23:33] <slangasek> tsimonq2: pointer to this?
[23:34] <tsimonq2> sec
[23:36] <tsimonq2> slangasek: bug 1754174
[23:36] <slangasek> ah that one's still around?
[23:37] <tsimonq2> I guess so
[23:41] -queuebot:#ubuntu-release- New binary: gcc-defaults-ports [amd64] (bionic-proposed/universe) [1.175ubuntu1] (ubuntu-desktop)
[23:41] -queuebot:#ubuntu-release- New binary: gcc-defaults-ports [i386] (bionic-proposed/universe) [1.175ubuntu1] (ubuntu-desktop)


[01:49] <souldessin> I will second the using of a command line editor. Personally, I use Emacs. After a little bit of configuring, I can start editing on any computer as if I was working on it for years. Instead of spending the time fighting to get a GUI, work towards getting a better feel for a terminal where it will do exactly what you tell it.
[05:53] <cpaelzer> good morning
[06:09] <lotuspsychje_> morning cpaelzer
[06:19] <utkarsh2102> \o
[06:38] <cpaelzer> good morning
[08:19] <mirespace> good morning
[09:04] <papopepo> hello
[09:31] <utkarsh2102> \o
[10:38] <athos> Good morning :)
[10:38] <athos> not entirely sure if I crafted this one right, but would anyone mind triggering this test:
[10:38] <athos> https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=amd64&arch=arm64&arch=armhf&arch=ppc64el&arch=s390x&package=libreoffice&trigger=nss/2%3A3.68.2-0ubuntu1&trigger=libreoffice/1%3A7.3.1~rc1-0ubuntu3
[10:39] <utkarsh2102> athos: done!
[10:40] <athos> thanks ;)
[11:16] <mirespace> how do you test changes in other architectures? Would it be easier doing a recipe?
[12:08] <ahasenack> good morning
[12:09] <mirespace> hi ahasenack
[12:10] <ahasenack> hi nmir
[12:10] <ahasenack> hi mirespace
[12:10] <mirespace> :)
[12:37] <ahasenack> hi server guys, I could use reviews on freeradius and samba so I can hopefully upload them before feature freeze tomorrow
[12:41] <athos> ahasenack: I will take freeradius. If nobody takes samba by the time I am done, I will do that one as well
[12:43] <athos> I will just need to step out for an hour or so now to solve some covid booster issues (the government did not enter my data into their system for some reason :/) and will jump right into it ;)
[12:43] <sergiodj> I can take samba
[12:43] <sergiodj> I was planning to take a look at it anyway
[12:45] <ahasenack> thanks athos
[12:45] <ahasenack> thanks sergio
[12:52] <cpaelzer> thanks athos and sergiodj for these fast reviews
[13:08] <ahasenack> athos: sergiodj I'll trade and go over the postgresql prs
[13:09] <sergiodj> ahasenack: thanks
[14:15] <athos> thanks :)
[14:18] <sergiodj> cpaelzer: ahasenack has reviewed and approved my postgresql-13 MRE.  would you like to take a look or can I go ahead and upload it?
[14:30] <cpaelzer> sergiodj: I'll have a look after a call I'm in
[14:31] <cpaelzer> sergiodj: not that I expect anything to be wrong, but better look before than complain after
[14:35] <kanashiro> aride, I am not sure what happened but the test script for the HA iSCSI target resources is missing from the main branch in server-test-scripts repo
[14:35] <kanashiro> paride, ^
[14:36] <paride> hmm
[14:36] <paride> let me check
[14:36] <kanashiro> if you check the merge commit here it will not be present in any branch: https://github.com/canonical/server-test-scripts/pull/151
[14:37] <kanashiro> I can restore the branch I used to implement this (I removed it after the merge)
[14:42] <paride> kanashiro, just to cross-check, what's the HEAD of the branch where you developed resource_iscsi_target_test.sh? b397eb0f9936eb3db52e138d7884d09e5356de5e ?
[14:43] <kanashiro> paride, yes, that's the commit hash
[14:43] <paride> yes that
[14:44] <paride> kanashiro, OK, I'm not sure of what happened TBH. I have a copy of the branch locally, re-merging it
[14:45] <kanashiro> paride, thanks
[14:46] <paride> kanashiro, done and I retriggered ha-agent-virsh-jammy-resource_iscsi_target to be sure it's all fine
[14:46] <kanashiro> awesome ;)
[14:48] <sergiodj> cpaelzer: ack
[15:01] <paride> kanashiro, test passed, all good
[15:01] <kanashiro> \o/
[15:04] <sergiodj> bryyce: hey, is it OK if I get the openvpn merge?
[15:08] <bryyce> sergiodj, sure
[15:08] <sergiodj> bryyce: thanks
[15:57] <ahasenack> sergiodj: oops, sorry about the d/changelog version mess. I reconstruct the changelog from git commits, but that doesn't have the version, which I have to paste in everytime. This time I missed "some numbers", heh
[15:58] <sergiodj> ahasenack: np; I saw the right version in the PPA, so I knew that this was just a small hiccup in the merge process
[16:46] <smoser> ahasenack: still appropriate here to request import packages ? i'd like to have dracut imported.
[16:46] <ahasenack> sure
[16:47] <ahasenack> smoser: added to the import queue, I'll let you know when it's done
[16:52] <xnox> athos:  one can specify multiple arches simultaniously?!
[16:53] <xnox> athos:  i used to always generate one click per arch.
[17:04] <ahasenack> wait, what?
[17:04] <ahasenack> autopkgtest retries?
[17:05] <smoser>  /o\
[17:14] <teward> any of the server guys got any good *up to date* guide on how to integrate LDAP / Active Directory access into a server env?  Everything I find has not been updated since 2013, or Canonical whitepapers that're hiding behind a subscribewall...
[17:17] <athos> xnox: yeah, from the results, it just picked up the first param
[17:20] <ahasenack> teward: I wrote something for the ubuntu server guide, would be interested in your opinion/results
[17:20] <teward> ahasenack: link?  'cause Google is failing me hardcore today
[17:20] <teward> (is it sssd driven?)
[17:20] <teward> (just curious)
[17:20] <ahasenack> yes
[17:20] <ahasenack> teward: https://ubuntu.com/server/docs/service-sssd
[17:21] <teward> ahasenack: thanks, i'll let you know.  this may be one of the few times I have to AD integrate the system at FT job, because it's going to be PAM integrated with JupyterHub which can use PAM for authentication >.<
[17:21] <ahasenack> it's also doable with just samba components, sure
[17:21] <ahasenack> if you are planning in using a samba server joined to the domain, then maybe using winbind is best
[17:22] <ahasenack> in any case, we went through some great lenghts to get realmd/adcli updated and in ubuntu main to get that working
[17:22] <ahasenack> but there are many knobs to turn, obviously
[17:22] <ahasenack> the simple case is what is in the guide, maybe a good enough starting point
[17:23] <teward> all we need is the user PAM integration
[17:24] <teward> no shares, etc. in use here :P
[17:24] <ahasenack> so a workstation authenticating against AD?
[17:24] <teward> server authenticating against AD in this case, but ye.
[17:24] <ahasenack> then I would take the sssd approach
[17:24] <teward> yep
[17:24] <teward> that's the plan
[17:24] <ahasenack> it handles sid/uid translation automatically. With winbind you have to pick a range
[17:25] <teward> yeah the only guides I found were pam_ldap nss_ldap (2013 in the WIki), winbind (2015), and i know SSSD is a newer way so i was hunting the docs
[17:25] <ahasenack> just beware if you are doing that inside containers (lxd), because they have a limited uid/gid range, and the range sssd picks is quite high
[17:25] <teward> there USED to be a whitepaper on this with SSSD but i'm lazy :P
[17:25] <teward> ahasenack: how fortunate this is a VM :P
[17:26] <ahasenack> should be fine
[17:26] <teward> but yeah indeed.  i'm waiting on the VMware person to deploy the system then i'll have access, will let you know how my progress goes
[17:27] <ahasenack> sergiodj: I didn't remove the dh_perl override because I wasn't sure if the normal debhelper call included that -a parameter used in the override (dh_perl -a), do you know?
[17:27] <ahasenack> otherwise I'll do a build without the override and see how dh_perl is called
[17:29] <pksato> Hello, I have a issue with php-fpm and email() function, and I not have a current plan on install any replacemente to mail(). Ubuntu 20.04.3 php from ondrej. System email is working as intended.   But mail() don't  nooting, no email, no error, just 'silence'. Any direction?
[17:31] <sergiodj> ahasenack: that "-a" parameter is used for arch-dependent rules, and given that the override is for dh_perl-arch, then yeah, the "-a" should be added automatically
[17:32] <sergiodj> it's a good idea to build the package without it just to confirm, but if it's too much trouble then I'm OK with keeping the override there FWIW
[17:32] <ahasenack> ok
[17:33]  * sergiodj -> lunch
[17:40] <ahasenack> smoser: done https://code.launchpad.net/ubuntu/+source/dracut
[17:40] <ahasenack> (and will be kept up-to-date from now on)
[17:41] <smoser> thank you.
[18:13] <pksato> my issue with php mail() solved. After 'moving' msmtprc to other directory, start showing apparmor error logs. add new dir to apparmor and start sending mail. :P.
[19:27] <teward> ahasenack: looks like it worked fine, but i have a question on sssd - can you restrict it so only certain AD groups can actually login?
[19:28] <ahasenack> probably, there are many tunables for sssd.conf
[19:28] <ahasenack> also be sure to check the provider-specific manpages, i.e., sssd-ad
[19:50] <sergiodj> OK, vsftpd MP is up, and realmd MP has just been reviewed
[19:51] <sergiodj> now onto investigating what's going on with the grafana snap
[21:05] <utkarsh2102> sergiodj: I'll take vsftpd :)
[21:09] <sergiodj> utkarsh2102: thanks
[22:19] <kilroy> so I thought I set up the GRE tunneling correctly, but they won't talk to one onther
[22:22] <kilroy> https://0bin.net/paste/JPvpb1RN#8D7HrKppIqCtMFVYzndtAFO-xRBiBEY6SI/YGvSsc/j
[22:33] <sdeziel> kilroy: are you seeing your GRE packets showing in tcpdump on both sides?
[22:33] <kilroy> let me check
[22:36] <kilroy> I think so?
[22:37] <sdeziel> kilroy: `sudo tcpdump -ni any proto gre` should provide a definitive answer
[22:39] <kilroy> no I am not seeing anything
[22:41] <sdeziel> kilroy: can you share the steps you've done to configure both sides?
[22:41] <kilroy> on server 1 ping <IP_ADDRESS> (server 2)
[22:41] <kilroy> on server 2 ping <IP_ADDRESS> (server 1)
[22:41] <kilroy> oh config
[22:41] <kilroy> sorry I thought you said capture
[22:42] <kilroy> I used this https://www.xmodulo.com/create-gre-tunnel-linux.html
[22:43] <sdeziel> kilroy: cool, I just tested with the same reference. My only divergence were: replace gre0 by gre1 (like you) and omit the `local` part as this one is then autofilled by the kernel
[22:44] <kilroy> I only used gre1 because I could not use gre1 and do you want me to remove the gre1 and try with out the local part
[22:44] <sdeziel> kilroy: `permaddr <IP_ADDRESS>` in your paste is something I don't see here
[22:44] <kilroy> yea I don't know were that came from
[22:45] <kilroy> might of been from me testing
[22:45] <sdeziel> kilroy: yeah, you can try leaving the local part out, one less source of possible mistake
[22:45] <kilroy> ok
[22:46] <sdeziel> kilroy: it is only useful if you have multiple IPs locally and want your GRE traffic to come from a specific one
[22:48] <kilroy> I am trying two remote servers
[22:51] <kilroy> I think it is working now
[22:52] <sdeziel> kilroy: cool now if you want to have that tunnel brought up on boot, you might want to put it in Netplan
[22:53] <kilroy> netplan? is that that .yaml file that I never touch because I end up breaking it?
[22:53] <sdeziel> kilroy: here's an example https://termbin.com/ylt2
[22:54] <kilroy> ok thank you so much sdeziel
[22:54] <sdeziel> kilroy: you are weldome
[22:54] <sdeziel> welcome*
[22:55] <kilroy> now that is working I just need to figure out step 2
[22:55] <sdeziel> kilroy: lastly, the `local: <IP_ADDRESS>` in the above is to please netplan and let the kernel autoselect the right source (same as omitting the local param in your `ip tunnel` command)
[22:56] <kilroy> ah
[22:57] <sdeziel> what's step 2?
[22:58] <kilroy> make it so website traffic goes from server 2 to server 1 with out messing up the current website
[22:58] <kilroy> make it so website traffic goes from server 2 to server 1 with out messing up the current website on server 2
[23:02] <sdeziel> OK, good luck and pipe up if you run into some problem
[23:23] <kilroy> ok thank you again sdeziel


[12:13] <jbicha> darkxst: could you respond to https://lists.ubuntu.com/archives/ubuntu-release/2013-June/002428.html too?
[12:31] <SonikkuAmerica> (Are we in or out? I'd like to know so I can mess with testing myself)
[12:33] <jbicha> I believe darkxst has said we're in for Alpha1
[12:33] <SonikkuAmerica> Awesome. ( Hey, I just got here. :) )
[12:34] <SonikkuAmerica> I need to see if the GNOME 3.8 session menu got itself fixed...
[12:37] <jbicha> what was broken?
[12:39] <SonikkuAmerica> (This is with the PPA btw) I can't seem to change my online status... I click it, and the session menu disappears, then the whole top bar acts as if my mouse button was held down (when it's not_
[12:39] <SonikkuAmerica> )
[15:17] <q_> bjsnider, with apt-get remove , and restored the xorg.conf file back to it's original
[15:17] <q_> which, was blank
[15:17] <bjsnider> remove what?
[15:18] <q_> nvidia driver, this was from yesterday
 qubit01, i asked you how you removed the nvidia driver
[15:18] <bjsnider> what was the package name
[15:18] <bjsnider> install mesa-utils and run glxinfo
[15:19] <qubit01> it was from nvidia ppa, package name was nvidia-current nvidia-settings
[15:19] <qubit01> ok
[15:19] <qubit01> Xlib:  extension "GLX" missing on display ":0"
[15:20] <qubit01> Error: couldn't find RGB GLX visual or fbconfig
[15:21] <bjsnider> well, that's obviously a problem
[15:23] <bjsnider> you should be using nouveau
[15:23] <bjsnider> modinfo|grep nouveau
[15:25] <qubit01> modinfo , missing file name
[15:26] <bjsnider> i'm sorry
[15:26] <bjsnider> lsmod|grep nouveau
[15:26] <qubit01> i borked it ?
[15:26] <qubit01> ahh
[15:27] <qubit01> nothing
[15:27] <qubit01> thanks for the help by the way
[15:27] <bjsnider> ok, so maybe it's still blacklisted
[15:27] <qubit01> do I need xserver-xorg-video-nouveau
[15:27] <bjsnider> pastebin /var/log/Xorg.0.log
[15:28] <bjsnider> that package is installed by default
[15:28] <qubit01> I think by installing the nvidia drivers it might have removed it
[15:28] <qubit01> ?
[15:28] <bjsnider> no, i tdoesn't
[15:28] <bjsnider> the module gets blacklisted
[15:30] <qubit01> https://www.refheap.com/16058
[15:30] <bjsnider> you'r' eusing xorg-edgers
[15:32] <qubit01> how can you tell, and what is the default for 13.04 ?
[15:32] <bjsnider> you have hybrid graphics
[15:32] <qubit01> I may have been a little tipsy when I tried this
[15:32] <qubit01> trying to get 3d acceleration for vmware player
[15:35] <bjsnider> qubit01, run the command dkms status
[15:37] <qubit01> nvidia-304, 304.88, 3.8.0-25-generic, x86_64: installed
[15:37] <qubit01> virtualbox, 4.2.10, 3.8.0-25-generic, x86_64: installed
[15:37] <bjsnider> now uname -r
[15:38] <qubit01> 3.8.0-25-generic
[15:38] <bjsnider> apt-get purge nvidia-304
[15:38] <bjsnider> then reboot
[15:39] <bjsnider> you should be using the intel chip for graphics afterwards
[15:39] <bjsnider> if you're concerned with stability, edgers is not an appropriate choice
[15:39] <qubit01> ok, dpkg -l | grep nvidia reports https://www.refheap.com/16059
[15:39] <qubit01> what does the ii mean, removed ?
[15:40] <qubit01> do I need to purge the others as well ?
[15:40] <bjsnider> you can get rid of settings
[15:41] <qubit01> ok rebooting
[15:45] <qubit01> bjsnider, you fixed it you brilliant bastard!
[15:45] <bjsnider> no big deal
[15:45] <bjsnider> i am a bastard though
[15:46] <qubit01> so the issue was I still had nvidia drivers installed ?
[15:47] <bjsnider> when you install one of the nvidia-xxx packages, they redirect libgl to the nvidia version. your chipset was choosing intel as the gpu, so you were mixing the intel graphics driver with nvidia's glx libs. that doesn't work
[15:48] <bjsnider> removing the nvidia package linked the glx libs back to the standard mesa ones, which intel does use
[15:48] <bjsnider> so previously, you were getting a picture on the monitor and whatnot, but no opengl
[15:49] <qubit01> ahh i see, good to know!
[15:49] <qubit01> now, sadly, back to work :(
[15:49] <qubit01> what are you up to ?
[15:50] <bjsnider> working, watching wimbledon
[15:52] <bjsnider> i'd still purge xorg-edgers though. it's not stable at all
[15:56] <qubit01> the mesa-utils package ?
[15:56] <qubit01> dpkg -l | grep edgers
[15:56] <qubit01> ii  mesa-utils                                8.0.1+git20110129+d8f7d6b-0ubuntu2+edgers                              amd64        Miscellaneous Mesa GL utilities
[16:23] <bjsnider> well, where did you get xorg-server 2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
[16:24] <bjsnider> that's from a ppa


[13:58] <fz420> 有国人吗？
[13:58] <bazhang> fz420, in #ubuntu-cn
[13:59] <fz420> 大家好，谁能帮你解决个问题？打开http://localhost/blog/   显示Error establishing a database connection这样的信息
[13:59] <fz420> 本地安装了WP
[13:59] <bazhang> fz420, english here, #ubuntu for english support #ubuntu-cn for Chinese support
[13:59] <fz420> 谁能SSH过来帮帮忙
[13:59] <bazhang> !cn | fz420
[14:00] <fz420> oh!sorry
[21:32] <Tm_T> !isitoutyet
[21:32] <Tm_T> ):
[21:33] <phillw> Hi, who / where should I ask about having a channel logger installed?
[21:37] <moshe742> hey there, can you please get me cloaked? i am a new member of ubuntu and my wiki page is https://wiki.ubuntu.com/Moshenahmias
[21:37] <Tm_T> phillw: which channel is this? there's current usage of the bots in https://wiki.ubuntu.com/IRC/Bots
[21:38] <moshe742> i want also the ability to use my ubuntu e-mail and as i understand it you can help by making it happen (correct me if i'm wrong)
[21:39] <phillw> Tm_T it is for #lubuntu, we have recently gotten an ubot, but adding the logging would allow people to search through the logs for answers etc.
[21:40] <phillw> at present it is a bit more dependant on my being logged on all the time (which I cannot be) and keeping a set of logs on my own system, which is of no help if I am not active.
[21:41] <Tm_T> moshe742: IIRC your "ubuntu email" should already work
[21:41] <moshe742> how can i check that?
[21:41] <Tm_T> moshe742: send test email to<EMAIL_ADDRESS>[21:42] <moshe742> as i understand i can't send a mail to the ubuntu mail if its re-directed to the same account, is this right?
[21:42] <pleia2> moshe742: if you're using gmail, yeah, gmail will eat the message you sent to yourself
[21:42] <rww> phillw: The bot's called ubuntulog, and you'd want to email the Canonical sysadmins at<EMAIL_ADDRESS>to get #lubuntu added to its channel list.
[21:43] <phillw> thanks rww
[21:43] <Tm_T> rww: you quick, you (:
[21:43] <pleia2> moshe742: I'll send you a test email if you'd like :)
[21:43] <moshe742> i would like it:)
[21:43] <pleia2> there you go
[21:44] <phillw> while I am here, I've been told I should ask to be 'cloaked', why should I want to do that?
[21:44]  * phillw waves at pleia2 :-)
[21:44] <pleia2> hey phillw :)
[21:44] <phillw> I'm still busy learning :-)
[21:44] <pleia2> phillw: you can go to #freenode to get an unaffiliated cloak
[21:45] <pleia2> (have to be an ubuntu member before you get an ubuntu cloak)
[21:45] <rww> phillw: cloaking hides your IP address from other users, and expresses affiliation with a project (if you have a project cloak like ubuntu/member/whatever). They're entirely optional, though.
[21:45] <moshe742> so now you will give me an ubuntu cloak?
[21:46] <pleia2> moshe742: a council member needs to see it and then pass it along to staff, just be patient until one of them comes by :)
[21:46] <phillw> pleia2: I've not got testimonails from ubuntu people on my wiki page yet to ask for ubuntu membership :-\ Seems all the people I know are not ubuntu members :-\
[21:46] <pleia2> phillw: people don't need to be ubuntu members to give you testimonials :)
[21:47] <rww> topyli, Pici, jussi: cloak request for https://launchpad.net/~moshegrey ^^^
[21:47] <moshe742> so should i stay here till such time or he/she will see it any way eventually?
[21:47] <pleia2> moshe742: yep
[21:47] <moshe742> yep to staying?
[21:47] <pleia2> yes
[21:48] <pleia2> sorry
[21:49] <moshe742> ok, so what are their names? or which council do you mean?
[21:49] <phillw> pleia2: hmm, that was what I read as it being. let me go do this ask for the log-bot and I'll try catch up with you when you are less busy, on a quieter channel. (tries to stay on topic :-) )
[21:50] <pleia2> moshe742: the people rww just called to look at your request
[21:50] <pleia2> the IRC Council
[21:50] <moshe742> ah, ok, thanks:)
[21:51] <moshe742> and i got the mail so it works, thanks:)
[21:51] <pleia2> great :)


[00:08] <liushuyu> tsimonq2: I am not sure how it happened, but the upload https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu6 is missing one of the patches. To avoid this being a Git repository de-sync issue, I have prepared https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-vvv-1.68/+sourcepub/15699493/+listing-archive-extra ...
[00:09] <liushuyu> ... so that you may do a source copy
[00:09] <liushuyu> (If you download https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-vvv-1.68/+sourcefiles/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu5/rustc-1.68_1.68.2+dfsg0ubuntu1-0ubuntu5.debian.tar.xz, you will find there is a patch fixing libgit 1.7 inside)
[02:09] <vorlon> jbicha: libnss-myhostname is in components-mismatches because gnome-control-center has grown a recommends on it.  We've intentionally kept this package out of the install.  Can this be dropped?
[03:57] <tsimonq2> liushuyu: ack, will look/sponsor in less than 12 hours unless someone else gets to it
[03:58] <tsimonq2> liushuyu: would recommend a bug with ubuntu-sponsors regardless :)
[07:02] <liushuyu> I have opened a sponsorship bug for the current situation with rustc-1.68: https://bugs.launchpad.net/ubuntu/noble/+source/rustc-1.68/+bug/2049577
[07:02] -ubottu:#ubuntu-devel- Launchpad bug 2049577 in rustc-1.68 (Ubuntu Noble) "Backport libgit2 1.7 fix for rustc-1.68 on Noble" [High, New]
[08:04] <LocutusOfBorg> liushuyu, tsimonq2 I didn't fix it up, because somebody told me rust-1.68 was scheduled for removal
[08:04] <LocutusOfBorg> and I'm pretty sure you need to disable a patch to make it build
[09:49] <schopin> tsimonq2: fwiw it's doubtful that things will ever get to a syncable state for Rust (unless we actually take over in Debian, I guess?), for the simple reason that we're moving way faster than they are :)
[09:50] <schopin> And I'm aware that for the people that keep asking us for ETAs on various versions that statement might sound a bit odd :-P
[10:42] <LocutusOfBorg> schopin, kernel folks are blinking :D
[12:02] <ginggs> @pilot in
[12:45] <seb128> ginggs, hey, did you get any luck/reply about those python build issues I mentioned in response to the noble archive rebuild email?
[12:52] <ginggs> seb128: no answers :( i guess not a common failure then
[12:52] <ginggs> LocutusOfBorg: diaspora-installer hinted
[12:54] <LocutusOfBorg> ta
[13:00] <seb128> ginggs, ack, thanks
[14:11] <schopin> vorlon: do you know whether we'll see a new pam upstream release before feature freeze in Noble? Wondering whether I should upload the patch for LP: #2045250 now or just wait for upstream.
[14:11] -ubottu:#ubuntu-devel- Launchpad bug 2045250 in Ubuntu on IBM z Systems "pam_lastlog doesn't handle localtime_r related errors properly" [High, New] https://launchpad.net/bugs/2045250
[15:34] <jamespage> mfo: hey - thanks for the py3.12 fixes into eventlet - I uploaded a new upstream release today which includes those and has full 3.12 support :)
[15:47] <vorlon> schopin: sorry, I have no idea
[15:47] <vorlon> schopin: it's nothing I'm working on right now in Debian
[15:48] <schopin> vorlon: I actually just had a look. The release I was looking for is actually 1.5.3 which has been out for a while and has hit experimental a couple of days ago.
[15:48] <schopin> meanwhile upstream has released 1.6.0 less than an hour ago.
[16:00] <vorlon> schopin: haha
[16:02] <ginggs> @pilot out
[16:02] <ginggs> thank you for flying Ubuntu Air!
[16:15] <jbicha> @pilot in
[17:25] <mdeslaur> schopin, vorlon: pam 1.6.0 fixes a security issue, I will be publishing updates to the stable releases this pm, should I upload the security fix only to noble, or should we consider 1.6.0?
[17:26] <vorlon> mdeslaur: off the cuff I think you should just upload to noble; release happening today doesn't mean we're getting it uploaded as maintenance to devel in the near future
[17:27] <mdeslaur> vorlon: ack
[17:27] <mdeslaur> schopin: do you want to include my fix in your upload, or just upload after me?
[17:28] <schopin> mdeslaur: please go ahead without me, I need to look into all the various versions anyway :)
[17:28] <mdeslaur> schopin: ack, thanks!
[17:28] <mdeslaur> vorlon: thanks!
[17:57] <liushuyu> Hi ubuntu-devel, can someone help me check why https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#gdb (SRU) has not migrated? The tests are all green now
[17:59] <liushuyu> The corresponding SRU bug is https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041396
[17:59] -ubottu:#ubuntu-devel- Launchpad bug 2041396 in gdb (Ubuntu Jammy) "gdb 12.1 generates SIGILL on armhf" [Undecided, Fix Committed]
[18:00] <sudip> liushuyu: its still in verification-needed stage
[18:00] <sudip> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
[18:02] <liushuyu> Okay, so I need to wait for the verification
[18:03] <sudip> liushuyu: you should test the package from poposed according to the test plan and add the verification report
[18:03] <sudip> and then update the tags
[18:06] <liushuyu> I see. According to the wiki, it sounds like someone other than the uploader should do the verification test. Is it enough that I (who proposed the fix) performed test and determined the updated package to be fixed?
[18:12] <sudip> liushuyu: I think its ok for you to test
[18:17] <bdmurray> liushuyu: In an ideal world other people would perform the verification but that doesn't always happen.
[18:17] <bdmurray> liushuyu: The important thing is to "show your work" when verifying the bug.
[18:18] <tsimonq2> liushuyu: Looks like LocutusOfBorg took care of your request :) although it falls onto me as the person that signed the upload, the constructive criticism I would have for you in the future is, ensure the changelog describes all changes made. I had no idea that patch existed or needed to be included, because there was no changelog entry. Instead of simply grabbing your package, I pulled the current
[18:18] <tsimonq2> copy from proposed, changed the deps myself, and added your changelog entry. Partly my mistake for not sitting through the 2 hour local build, partly your mistake for the changelog. I'm glad it's sorted now. :)
[18:30] <tsimonq2> seb128 (cc mkukri): I disagree with you on bug 2049188. More often than not, Debian maintainers are not inclined to accept this class of patches, if the issue is not present on Debian. In fact, vendor patches are specifically forbidden per Debian Policy. This definitely needs to be a delta, until Debian upstreams this part of our dpkg delta.
[18:30] -ubottu:#ubuntu-devel- Bug 2049188 in hiredis (Ubuntu) "hiredis FTBFS on ppc64el" [Undecided, New] https://launchpad.net/bugs/2049188
[18:30] <tsimonq2> seb128: The *vast* majority of the time I would agree with you on this point, in this case I do think a delta would be acceptable.
[18:31] <liushuyu> tsimonq2: Yes. The changelog issue is my fault. That is also why I corrected the issue in the newer revision of the package
[18:31] <tsimonq2> liushuyu: Live and learn :D
[18:32] <tsimonq2> liushuyu: Anyway, thanks for your work and persistence on that. Thanks again for following up on your upload :D
[18:33] <vininim> I'm getting the following error while trying to run git-ubuntu: fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled
[18:34] <tsimonq2> vininim: IME that can be ignored. The repo should still be cloned and usable, yeah?
[18:34]  * tsimonq2 tries to find some git-ubuntu docs on actually "signing in" in some capacity...
[18:34] <liushuyu> tsimonq2: Thank you for uploading and helping me understand the issue. We always learn something new everyday
[18:35] <vininim> That's the second error: Unable to find imported repository. I thought it was related to the first one.
[18:36] <tsimonq2> liushuyu: of course :)
[18:36] <tsimonq2> vininim: hmmmmmm which package are we talking about here?
[18:36] <vininim> tsimonq2: pipewire-jack
[18:37] <tsimonq2> vininim: Ah, okay! I know what the problem is :)
[18:37] <tsimonq2> vininim: `git ubuntu clone` only supports source packages, not binary packages, to my understanding.
[18:37] <tsimonq2> vininim: So instead of running `git ubuntu clone pipewire-jack`, try `git ubuntu clone pipewire` - that should do the trick.
[18:38] <tsimonq2> For future reference: https://packages.ubuntu.com/noble/pipewire-jack shows the source package name on the right side.
[18:38] <vininim> Oh, it worked. Thanks.
[18:38] <tsimonq2> (Otherwise, you can run `$ apt-cache showsrc pipewire-jack` in a terminal. :) )
[18:38] <tsimonq2> No worries!
[18:40] <tsimonq2> ginggs, jbicha: You guys are great, the queue looks awesome :)
[18:51] <tsimonq2> https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu7/+build/27651974 ah yes started 10 hours ago
[18:56] <liushuyu> 10 hours is actually quite fast for building rustc on an emulated RISC-V system
[18:57] <liushuyu> (Is there a way to fast-forward though time so that I don't have to wait?)
[19:03] <tsimonq2> When you figure that out, let me know. :D
[19:04] <arraybolt3> liushuyu: Yes, there is, it's called sleep :)
[19:25] <liushuyu> arraybolt3: But that is somewhat uncontrollable, you can't fast-forward a specific amount of time. The alarm-clock method isn't always reliable, the time-travel may overshoot into unspecified future
[19:26] <liushuyu> I have added a verification report: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041396/comments/15
[19:26] -ubottu:#ubuntu-devel- Launchpad bug 2041396 in gdb (Ubuntu Jammy) "gdb 12.1 generates SIGILL on armhf" [Undecided, Fix Committed]
[19:30] <cpete> liushuyu: an additional bug is that experienced time is not guaranteed to be less than the traveled time
[19:30] <liushuyu> cpete: Exactly
[19:38] <rbasak> vininim: explanation here: https://bugs.launchpad.net/git-ubuntu/+bug/1761821
[19:38] -ubottu:#ubuntu-devel- Launchpad bug 1761821 in git-ubuntu "Spurious error message: fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled" [Medium, Triaged]
[19:38] <mfo> jamespage, hey o/ re: py3.12/eventlet
[19:38] <mfo> jamespage, sure, happy to help
[19:39] <mfo> jamespage, glad there's a new upstream version with those, that's good news
[19:41] <mfo> jamespage, btw, you probably noticed that too, but mentioning just in case you also look at py3.12 for nose -- there's still a hunk in python-eventlet's d/rules to ignore nose.config SyntaxWarnings on py3.12, that can go away too if that is fixed in nose
[19:41] <mfo> :)
[19:42] <mfo> reference: (PYTHONWARNINGS="$$([ $$i != 3.12 ] ...
[20:05] <liushuyu> Ah, the struggle has finally coming to an end https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu7/+build/27651974
[20:21] <jbicha> @pilot out