=== blahdeblah_ is now known as blahdeblah
=== Ionic is now known as Guest60904
[00:40] <tsimonq2> slangasek, cjwatson: Is MoM broken? Last update was like 40  hours ago it seems...
[00:56] <stanford_ai> I'm trying to run tensorflow on GPU, so I followed the instructions on the tensorflow official website, to install it with conda. But I get this error: ImportError: libcuda.so.1: cannot open shared object file: No such file or directory
[01:08] <teward> stanford_ai: that's less a development issue and more of a support issue, you might wish to take that question to #ubuntu (namely, "how do I install CUDA so that I can use tensorflow on GPU?"_
[01:13] <cjwatson> tsimonq2: yeah it's on my list
[01:13] <cjwatson> there are a few things that break MoM and need manual intervention
[01:15] <cjwatson> tsimonq2: I usually leave it until a weekday to sort out; but I've fixed the first thing that broke so it may work soon.  Failing that it'll keep emailing me until I fix it, so I'm not going to forget
=== Ionic is now known as Guest39373
[02:23] <tsimonq2> cjwatson: ack, thanks.
=== Ionic is now known as Guest47032
[03:58] <TxLiunx> hello anyone on that could respond. I am test my system. I had to reload everything.
[04:00] <Unit193> TxLiunx: Perhaps you are seeking the support channel, #ubuntu?
[04:04] <TxLiunx> thanks, just checking if hexchat is working
=== Ionic is now known as Guest61516
=== Ionic is now known as Guest404
=== Ionic is now known as Guest81995
[07:05] <smb> stgraber, not that I were wishing I had not (touched fan). But I saw this recently (indirectly while waiting on iproute2 tests), iirc only i386. And the test itself looks to succeed, its just sd_bus_open_system that suddenly comes via stderr
=== zumbi_ is now known as zumbi
[07:22] <smb> stgraber, the thing that is done around when the message is produced is a "systemd-resolve --status" call... the second attempt, so I read the log, is then successful
[07:50] <acheronuk> merges.ubuntu.com has not updated since Saturday morning. who to query about that?
[07:59] <Unit193> acheronuk: "yeah it's on my list" || "there are a few things that break MoM and need manual intervention" || "I usually leave it until a weekday to sort out; but I've fixed the first thing that broke so it may work soon. Failing that it'll keep emailing me until I fix it, so I'm not going to forget"
[07:59] <acheronuk> Unit193: ok. thank you :)
[08:00] <Unit193> (Scrollback here.)
[08:00] <Unit193> acheronuk: Sure thing.
[08:01] <acheronuk> Unit193: I thought I had scrolled back, but probably did it in #ubuntu-desktop in error or something
=== Guest10613 is now known as RAOF
[10:27] <seb128> hum, I think that's not possible but I'm asking in case. Can we query launchpad for tags using a regexp? e.g bugs tagged "verification-needed*"?
[10:47] <jbicha> is there anyone besides Laney who can look into http://appstream.ubuntu.com/cosmic/ ? it hasn't updated in a week
[11:49] <ricotz> seb128, https://bugs.launchpad.net/bugs/+bugs?field.tag=verification-needed
=== King_InuYasha is now known as Son_Goku
[12:38] <ahasenack> when a package is known to not work with python 3.7, is this an acceptable change to d/control for us?
[12:38] <ahasenack> -X-Python3-Version: >= 3.0
[12:38] <ahasenack> +X-Python3-Version: >= 3.0, <= 3.6
[12:39] <ahasenack> plus a link to the upstream bug tracking 3.7 progress
[13:27] <seb128> ricotz, that was an example, I want to use tags like with a "keyword-<idnumber>" and script list those and extract the "idnumber". One way is to have 2 tags, one "keyword" to have a way to query then iterate over the tags from the corresponding bugs and do the split, but I was wondering if I can do without the second tag
[13:27] <seb128> jbicha, slangasek iirc was mentioning the issue/a service that didn't get restarted after an outage or something
[13:28] <seb128> jbicha, but I don't know if he/others have a knowledge of the service and how to handle it
[14:23] <stgraber> smb: I fixed this issue by setting allow_stderr in the fan package
[14:23] <stgraber> smb: so if systemd feels like being noisy, that won't cause a failure anymore
[14:24] <smb> stgraber, Yep I saw that after replying. I pulled your change into the related git repo already
[14:29] <stgraber> smb: thanks!
[16:00] <slangasek> seb128: sorry, it wasn't me mentioning it, I know nothing about appstream.u.c
[16:09] <sil2100> oSoMoN: hey!
[16:09] <sil2100> oSoMoN: remind me - is libreoffice-l10n basically always just a mirror of libreoffice?
[16:09] <oSoMoN> sil2100, hey
[16:09] <oSoMoN> sil2100, both packages are built from the same sources
[16:10] <oSoMoN> they are separate packages because at some point in time LP wasn't able to cope with everything together
[16:10] <sil2100> oSoMoN: since I'm looking at libreoffice-l10n for xenial in the SRU queue (for the trigger changes) and there's a lot of changes besides the  trigger change, as the uploaded libreoffice-l10n follows what's was in libreoffice
[16:10] <oSoMoN> not sure if this is still the case
[16:10] <sil2100> While no libreoffice-l10n uploads have been done for a while there
[16:10] <sil2100> Ok
[16:11] <tjaalton> xnox: hi, i'm testing 389-ds on cosmic, and noticed that the configured instance isn't started after a reboot, in fact systemd somehow doesn't even know about it, although everything should be the same as before reboot
[16:12] <sil2100> oSoMoN: it's a bit tricky since now basically if I accept the trigger changes upload to xenial, I'd have to 'assume' that all the libreoffice security updates that are pulled in with this upload have been successfully tested for the libreoffice-l10n package as well
[16:12] <oSoMoN> sil2100, yeah, I think I talked to bdmurray_ about it a couple of weeks ago, strictly speaking the libreoffice-l10n update is not needed as there won't be version conflicts with a newer libreoffice, but I uploaded it for consistency, so it's up to you, feel free to reject if you don't want it
[16:13] <sil2100> oSoMoN: if you don't mind I'd reject it personally, since I have no idea if in some freak accident the -l10n generated binaries will suddenly go crazy on the missed security changes
[16:13] <sil2100> Certainly not something I'd like to get in without verification
[16:13] <oSoMoN> sil2100, that's absolutely fine by me
[16:13] <oSoMoN> better to be on the safe side
[16:13] <sil2100> (and there are no SRU tracking bugs for those as those are security uploads)
[16:13] <sil2100> oSoMoN: thanks!
=== bdmurray_ is now known as bdmurray
[17:13] <tjaalton> xnox: correction, it's just not started on boot
=== Ionic is now known as Guest67474
[18:41] <seb128> slangasek, sorry, wrong memory, indeed it was not you https://irclogs.ubuntu.com/2018/08/22/%23ubuntu-release.html#t08:47
[18:41] <seb128> slangasek, do you know if anyone in foundations has knowledge of that service? nobody does in desktop and Laney is still away for a full week
[18:42] <slangasek> seb128: no idea, sorry
[18:42] <seb128> :/
[19:47] <xnox> tjaalton, fun. i have no idea about 389-ds - can you open a detailed bug report or drop me an email?
[19:47] <xnox> tjaalton, such that i could help investigating it....
[19:53] <tjaalton> xnox: sure
[22:41] <mwhudson> hah er i guess https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1789170 translates to "we use systemd now"?
[22:41] <ubottu> Launchpad bug 1789170 in console-setup (Ubuntu) "/etc/default/console-setup doesn't affect number of TTY's" [Undecided,New]