[00:32] vorlon: ack, thanks. [06:49] xnox: thanks to you :) [10:20] xnox, boxbackup merge/sync please? there is an openssl 1.1 build fix [10:20] also xonsh might be syncable now... [10:22] also meson and something more... [10:32] LocutusOfBorg: can try these. === TJ_Remix is now known as TJ- [11:00] ta [11:04] LocutusOfBorg: i beleive meson will require a merge, but can try doing force sync to see if it got better or not === Wryhder is now known as Lucas_Gray [11:12] xnox, yes that was my intention, prepare a merge and upload or not based on autopkgtests [12:06] the launchpad.net certificate has expired :( [12:06] or is it just me? [12:06] September 15, 2019 [12:07] I would say just you [12:07] bugs.launchpad.net has expired [12:07] that one is expired, indeed [12:07] yes, it only happens on bugs.lp.net [12:07] thought it was the same [12:07] just been flagged to #canonical-sysadmin channel [12:08] notAfter=Jun 25 12:00:00 2019 GMT === ricab is now known as ricab|lunch [12:36] x [12:37] sahid, hello, I fixed your python-ddt upload, otherwise cinder was not building at all [12:37] please be careful about your upstream tarballs next time :) [12:37] and sync from Debian if possible [12:37] mismatching tarballs are PITA to have [12:38] xnox, looks lie boxbackup needs help... [12:59] LocutusOfBorg: yes true i was actually working on it, how did you fixed it? [12:59] I can't see your change in ubuntu-server-dev [12:59] the problem is that debian.net does not provide doc with the tarball [13:00] and jamespage just proposed to me to use the one from debian experimental [13:03] sahid, LocutusOfBorg: pkg-openstack in debian generally snapshot from git, so they don't use a sdist generated tarball [13:04] hence why the version in experimental has the docs subfolder. [13:09] sahid, that one, syncing from experimental did the trick [13:10] I don't honestly care about how debian generated it :) it works [13:10] maybe bugging upstream about fixing their tarball is worth doing [13:24] LocutusOfBorg: in all cases thanks for your help on it :) === ricab|lunch is now known as ricab [13:38] LocutusOfBorg: yup - that was the next step (patch upstream to include docs folder in release sdist) [13:40] ok so now for a broader eoan question - I know python2.7 is going to universe this cycle; do we have an objective to remove all of the python-* packages in archive? [13:41] debian experimental seems to contain alot of pre-work towards that goal [13:41] LocutusOfBorg: python-ddt being a case in point - the reverse-depends list of binary:python-ddt is quite long [13:44] which is why we had not synced (yet) [14:34] jamespage, uploading a broken 1.2.1-0ubuntu1 makes no difference wrt syncing 1.2.1-1 from experimental... does it? [14:51] Working on some packaging and I'm having trouble getting some lintian-overrides to take. Any idea what I'm doing wrong? https://code.launchpad.net/~eeickmeyer/+git/raysession (I'm still learning) [14:55] Eickmeyer: I see you've created debian/source/lintian-overrides. I don't recall if this is a supported path (the path I'm used to is debian/source.lintian-overrides; debian/source/lintian-overrides may be supported nowadays but it looks jarring to me to include this in debian/source which is otherwise instructions to dpkg-source). But the real problem is that the overrides you're declaring there [14:55] are overrides for binary packages, not for the source [14:55] Eickmeyer: you need a debian/$binary_package.lintian-overrides for the binary-level overrides [14:56] vorlon: Thanks, I'll give that a shot. [14:57] vorlon: It's the path that Lintian prefers and documents nowadays [14:58] There's a pedantic-severity tag for using debian/source.lintian-overrides [14:58] (Not disagreeing with you about debian/$binary_package.lintian-overrides) [14:59] cjwatson, vorlon: Yeah, that's what I read in the documentation. [15:03] cjwatson: :) [15:32] @pilot in === udevbot changed the topic of #ubuntu-devel to: Archive: Open | 19.04 Released! | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Disco | If you can't send messages here, authenticate to NickServ first | Patch Pilots: tsimonq2 [15:33] https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040751.html [15:37] Wimpress, popey: Would someone with more experience with snaps than I be able to confirm that this bugfix works? bug 1802483 [15:37] bug 1802483 in libnotify (Ubuntu) "Notifications emitted by a snap with local files or desktop files use wrong namespace" [Medium,In progress] https://launchpad.net/bugs/1802483 [15:37] It's been in the sponsorship queue for a while. [15:41] That fix needs properly reviewing [15:42] Laney: I agree. [15:43] Bug 1770093 needs review from someone who works with Pi stuff more than I do; I have a Pi 3 and I'll circle back once I can get an SD card for it later this week, if needed. [15:43] bug 1770093 in ubiquity (Ubuntu) "Ubiquity crashes with mount points that are FAT16/32" [Undecided,New] https://launchpad.net/bugs/1770093 [15:45] sil2100: Poke on reviewing bug 1814118 when you get the chance. [15:45] bug 1814118 in rpi.gpio (Ubuntu Cosmic) "Make RPi.GPIO work on arm64" [Low,New] https://launchpad.net/bugs/1814118 [15:48] bluesabre: I'm looking at bug 1822380 and I wanted to get your feedback as to what's left here. I don't see any other debdiff specifically that needs sponsoring, so I'll unsubscribe sponsors, but it does seem there's a GTK bug here. [15:48] bug 1822380 in gtk+3.0 (Ubuntu) "Thunar right-click menu not expanded" [Low,Triaged] https://launchpad.net/bugs/1822380 [15:50] Hmm, it looks like the upstream GTK issue isn't getting much traction. https://gitlab.gnome.org/GNOME/gtk/issues/1843 [15:50] I'm willing to bet a Git bisect will reveal the issue. I'll circle back later this week when I look at Pi stuff. [15:52] Well, I do see a random patch from an obscure forum post. What could go wrong? :P [16:10] jamespage: Would you (or someone else with knowledge of the swift package) be able to take a look at bug 1827340? It's been in the sponsorship queue for a bit. [16:10] bug 1827340 in swift (Ubuntu) "swift-container package is missing Upstart and System V files for the container-sharder service" [Low,In progress] https://launchpad.net/bugs/1827340 [16:18] juliank: Debian bug 927876 's Ubuntu counterpart, bug 1766068, has been in the sponsorship queue for a bit. Would you be able to review the patch when you can? [16:18] Debian bug 927876 in command-not-found "zsh: Does not print 'command not found' message if handler does not match" [Important,Open] http://bugs.debian.org/927876 [16:18] bug 1766068 in command-not-found (Ubuntu) "Using Zsh, it doesn't show an error message when command not found" [Low,Triaged] https://launchpad.net/bugs/1766068 [16:22] cyphermox: Did you plan on driving the SRU for bug 1828948 as well? [16:22] bug 1828948 in dkms (Ubuntu Bionic) "OBSOLETE_BY in DKMS.CONF not work" [High,New] https://launchpad.net/bugs/1828948 [16:31] tsimonq2: yes [16:32] cyphermox: Sounds good, thanks. [16:34] vorlon: RE: lintian-overrides, that did not work. lintian is still throwing invalid errors on the binary. [16:35] Eickmeyer: I don't believe ' binary' is part of the expected content of the override [16:35] i.e. it should be $bin_pkg_name: $lintian_tag_name $other_info [16:36] vorlon: Thanks for the hint, will make the change. [16:46] vorlon: That didn't work. Does it need "#/usr/bin/python3" appended? [16:50] rather, #!/usr/bin/python3 [16:51] @pilot out === udevbot changed the topic of #ubuntu-devel to: Archive: Open | 19.04 Released! | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Disco | If you can't send messages here, authenticate to NickServ first | Patch Pilots: [16:52] https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040752.html [16:56] tsimonq2: I (very quickly) provided the links you requested. === laptop26 is now known as laptop2 [17:44] Eickmeyer: Thanks. [17:46] vorlon: Answered my own question. It needed the #! line too. Thanks! [17:50] is that the lintian thing? [17:50] sarnold: Yep. You can look for yourself at what it needed. [17:50] If you want... [17:50] woot [17:51] \o/ [18:41] ahasenack: We, the foundations team, would close bug 1810780 but it is assigned to you. Are you still planning on doing any work there? [18:41] bug 1810780 in lftp (Ubuntu) "FTBFS: missing zlib1g-dev" [Undecided,In progress] https://launchpad.net/bugs/1810780 [18:41] oh, ow [18:41] let me check [18:42] bdmurray: it can be closed. My mp was rejected because debian fixed in while it was in review, so no changes needed. [18:42] bdmurray: is cosmic still affected, though? [18:43] my mp was for disco [18:43] ahasenack: It could be but end of life for cosmic is near [18:44] I see. Well, I'm not working on that, and if this package needs an sru for another reason, the ftbfs fix is simple enough [18:44] I think this is fix released for disco, and a cosmic task may or may not be added [18:46] adjusted [19:31] tsimonq2: Sure, but note that Ubuntu is upstream, Debian is downstream [19:31] Debian tracks the latest LTS version of c-n-f, and software-properties [19:32] I'll be tracking stuff more aggressively post buster I think, as this improves quality for everyone === dannf` is now known as dannf [20:10] ahasenack: Thanks!