[01:20] <RAOF[m]> 406279
[01:32] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Xenial 16.04.5] has been marked as ready
[01:32] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Xenial 16.04.5] has been marked as ready
[01:34] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [18.3-9-g2e62cb8a-0ubuntu1~16.04.2]
[01:56] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (bionic-proposed) [18.3-9-g2e62cb8a-0ubuntu1~18.04.2]
[01:56] <blackboxsw> much thanks
[01:57] <blackboxsw> RAOF[m]: what's the [m] mean? (for future reference)
[01:57] <blackboxsw> hadn't seen that suffix before
[01:58] <RAOF[m]> blackboxsw: It means I haven't quite got the Matrix bridge to set my correct nick yet :)
[01:58] <blackboxsw> ha!
[01:58]  * blackboxsw was guessing "mobile" or "moderator"
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-settings [source] (bionic-proposed) [18.04.6]
[11:42] <_hc> rbasak:
[11:42] <_hc> circling back about fdroidserver SRU for bionic https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1758196
[11:42] <_hc> it has a debdiff with the changelog-only change for bionic, from cosmic/testing
[11:43] <_hc> I didn't see a way for me to upload that to bionic-proposed as a DD, I have no official Ubuntu status
[11:44] <rbasak> _hc: o/
[11:45] <rbasak> _hc: I'm only supposed to either sponsor or SRU-review but not both. So we need to find someone else who can sponsor. I've been asking in #ubuntu-motu but haven't found anyone yet :-/
[11:45] <_hc> o/
[11:45] <rbasak> It's on my list though.
[11:45] <_hc> I see, thanks!
[11:45] <_hc> interesting to see how different the Ubuntu workflow is from Debian
[11:45] <rbasak> _hc: as a DD you should be able to get upload access for your packages in Ubuntu without too much difficulty if you're interested.
[11:46] <_hc> interesting, yeah, sure
[11:47] <rbasak> _hc: not quite as I remembered it, sorry: https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess#Debian_Developers_applying_for_Per-Package_upload_rights
[11:47] <rbasak> For the first package you need to ask for PPU rights
[11:47] <rbasak> (which is a standard Ubuntu thing, not special for DDs; I guess the reason is because you need to be aware of Ubuntu release processes etc)
[11:48] <rbasak> _hc: but if you're interested, we do try to encourage DDs taking care of their packages in Ubuntu directly as much as possible.
[11:49] <_hc> one of these days, I'll find the time to do the PPU process, can't happen right now tho
[11:49] <apw> _hc, a quick look says your version number is suspect, as that would be higher than cosmic, 1.0.9-1~18.04.1 would be fine i think
[11:49] <rbasak> np. It's on my plate to find you a sponsor and get this landed
[11:51] <_hc> apw: ok, changing now
[11:51] <_hc> thanks
[11:56] <_hc> done
[12:06] -queuebot:#ubuntu-release- Unapproved: fdroidserver (bionic-proposed/universe) [1.0.2-1 => 1.0.9-1~18.04.1] (no packageset)
[12:07] <rbasak> ^ thanks for sponsoring. I'll SRU-review this now.
[12:07] <apw> rbasak, ping me if you have trouble
[12:07] <rbasak> ack
[12:25] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Xenial 16.04.5] has been marked as ready
[12:25] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Xenial 16.04.5] has been marked as ready
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted fdroidserver [source] (bionic-proposed) [1.0.9-1~18.04.1]
[12:28] <rbasak> _hc, apw: ^ thanks
[12:29] <rbasak> _hc: to set expectations for the future, please note that microrelease has a specific meaning for Ubuntu according to https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases "If all of the changes are appropriate for an SRU by the criteria above" so this won't necessarily be possible in the future unless you continue to be careful about the specific upstream changes that land.
[12:31] <rbasak> (bugfixes are fine; feature changes need to go through a different process; just because upstream classify something as a bugfix and not a feature by putting it into a microrelease doesn't mean that Ubuntu will concur)
[12:46] <ahasenack> hi, could someone please force badtest ocfs2-tools: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ocfs2-tools
[12:46] <ahasenack> here is the mp: https://code.launchpad.net/~ahasenack/britney/ocfs2-tools-hints-1.8.5-5ubuntu1/+merge/351928
[12:46] <ahasenack> with the reasoning
[13:54] <LocutusOfBorg> apw, please point 3? :)
[13:54] -queuebot:#ubuntu-release- New binary: ros-actionlib [amd64] (cosmic-proposed/universe) [1.11.14-3ubuntu1] (no packageset)
[14:51] <_hc> thanks for the review and getting fdroidserver to the next step!  I'll test it once the build lands.
[14:51] <_hc> in terms of the microreleases, I've been doing those with my Debian hat on, I imagine the criteria are similar
[14:52] <_hc> basically, i've been finding new mass test cases, then fixing bugs from that process.  It is amazing how many crazy things people do when building Android APKs
[14:52] <_hc> and we've got to parse it all
[14:53] <infinity> _hc: s/ when building Android APKs//
[14:54] <infinity> _hc: If there's a way to break software, humans will find it.  And developers will find it twice as fast.
[14:54] <infinity> I miss the days where "don't do that, then" was considered a reasonable response to a bug report. :P
[15:09] <tsimonq2> sil2100: Are you on debconf time or western world time?
[15:09] <tsimonq2> The international date line means that you could be almost a day ahead of me. :P
[15:10] <Trevinho> sil2100: hey, although you added me to the group for managing ci-ppa, it looks like i cant push sources there... ("The signer of this package has no upload rights to this distribution's primary archive"), which is true... but I thought that it would mean getting sponsored at publish time no?
[15:11] <tsimonq2> Trevinho: Do you have a copy of the email? (I assume you used dput.)
[15:11] <tsimonq2> Are you in ~ubuntu-dev otherwise?
[15:17] <Trevinho> tsimonq2: I'm not there in fact, but at the same time I think I was mistyping the cmd (no setting the PPA url :-D)
[15:17] <Trevinho> thus was correct... and sorry for bothering :)
[15:17] <sil2100> ;)
[15:18] <sil2100> tsimonq2: I'm on my regular EU timezone, sometimes slightly moved towards the US one because of the point-release
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base powerpc [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Xenial 16.04.5] has been marked as ready
[15:24] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Xenial 16.04.5] has been marked as ready
[15:24] <tsimonq2> sil2100: Ah. I didn't think EU people moved to a US timezone for point releases, only the other way around.
[15:25] <infinity> tsimonq2: People do whatever they need to do to get things done, there's no formal process.
[15:25] <infinity> (usually when I'm driving, the process is "don't sleep")
[15:26]  * apw worries for the lamppost
[15:28] <tsimonq2> infinity: Ah, makes sense.
[15:32] <sil2100> Yeah, no process for that, just staying around to get things done
[16:29] <keepguessing> I do not see Bionic listed here. http://changelogs.ubuntu.com/meta-release-lts
[16:30] <keepguessing> when would it be available. Is there some bug/issue blocking it?
[16:30] <infinity> keepguessing: There are a couple of things still being worked on to make sure the upgrade is as smooth as it can be.
[16:32] <keepguessing> infinity: can you point me to the issues or a way to track this?
[16:41] <infinity> keepguessing: Not sure there's a public bug to track the ubuntu-release-upgrader work in progress.  But it'll be ready when it's ready.
[16:48] <keepguessing> infinity: ok thanks.
[17:14] -queuebot:#ubuntu-release- New binary: golang-github-graph-gophers-graphql-go [amd64] (cosmic-proposed/universe) [0.0~git20180609.bb97385-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: golang-github-matryer-is [amd64] (cosmic-proposed/universe) [1.1.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: rust-unicase [ppc64el] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: zhcon [amd64] (cosmic-proposed/universe) [1:0.2.6-13] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: puppet-module-puppetlabs-haproxy [amd64] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: rust-unicase [s390x] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libbson-xs-perl [ppc64el] (cosmic-proposed/universe) [0.4.3-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-unicase [amd64] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: rust-unicase [i386] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: libbson-xs-perl [i386] (cosmic-proposed/universe) [0.4.3-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: golang-github-pzhin-go-sophia [amd64] (cosmic-proposed/universe) [0.0~git20180715.8bdc218-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: libbson-xs-perl [amd64] (cosmic-proposed/universe) [0.4.3-1] (no packageset)
[17:37] <ahasenack> hi, my bind9 upload, which bumped the soname, also needs a debian-installer rebuild (ppa at https://launchpad.net/~ahasenack/+archive/ubuntu/bind-merge-9.11.4/+packages). Would someone sponsor this for me? https://pastebin.ubuntu.com/p/HPVtSzkPK7/
[19:40] -queuebot:#ubuntu-release- New binary: rust-unicase [arm64] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[19:42] -queuebot:#ubuntu-release- New binary: libbson-xs-perl [arm64] (cosmic-proposed/universe) [0.4.3-1] (no packageset)
[19:42] -queuebot:#ubuntu-release- New binary: rust-unicase [armhf] (cosmic-proposed/universe) [2.1.0-1] (no packageset)
[19:44] -queuebot:#ubuntu-release- New binary: libbson-xs-perl [armhf] (cosmic-proposed/universe) [0.4.3-1] (no packageset)
[20:12] <blackboxsw> infinity: do you know if I remove regression-proposed tag on an SRU process bug once I've validated and provided verification-done-<series> tags?
[20:13] <blackboxsw> or do I leave the regression-proposed tag in place even though all verification is now done?
[20:15] <blackboxsw> namely on this bug https://bugs.launchpad.net/cloud-init/+bug/1784685
[20:59] <rbasak> blackboxsw: AIUI, regression-proposed is for a new bug filed against a package in -proposed reporting a regression. The original tracking bug would just be verification-failed, which would get removed when the SRU replacement lands in -proposed. The extra regression-proposed bug would get marked Fix Committed/Released, but would never be untagged since the bug was for something that had regressed
[20:59] <rbasak> in proposed. But no need to file a separate bug just for the sake of it. Only if someone actually wants to report it somewhere, etc.
[21:02] -queuebot:#ubuntu-release- Unapproved: maas (xenial-proposed/main) [2.3.0-6434-gd354690-0ubuntu1~16.04.1 => 2.3.4-6508-g4f77e30-0ubuntu1] (ubuntu-server)
[21:10] <ginggs> ahasenack: debian-installer sponsored
[21:11] <ahasenack> ginggs: thanks a lot
[21:51] -queuebot:#ubuntu-release- Unapproved: accepted xfce4-terminal [source] (bionic-proposed) [<IP_ADDRESS>-0ubuntu<IP_ADDRESS>]
[21:57] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (bionic-proposed) [3.28.1-0ubuntu<IP_ADDRESS>]
[22:04] -queuebot:#ubuntu-release- Unapproved: accepted gnome-menus [source] (bionic-proposed) [3.13.3-11ubuntu1.1]
[22:32] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (bionic-proposed) [2.10.5-1ubuntu1.1]
[22:41] -queuebot:#ubuntu-release- Unapproved: accepted aodh [source] (bionic-proposed) [6.0.1-0ubuntu1.1]
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (bionic-proposed) [3.28.3-1~ubuntu18.04.1]
[22:59] -queuebot:#ubuntu-release- Unapproved: rejected gnome-shell [source] (bionic-proposed) [3.28.3-0ubuntu<IP_ADDRESS>]
[23:14] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [s390x] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [ppc64el] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: golang-github-pzhin-go-sophia [amd64] (cosmic-proposed/universe) [0.0~git20180715.8bdc218-2] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [i386] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [amd64] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: ros-python-qt-binding [amd64] (cosmic-proposed/universe) [0.3.3-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: vulkan-headers [amd64] (cosmic-proposed/universe) [1.1.77-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: yaha [i386] (cosmic-proposed/universe) [0.1.83-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: yaha [amd64] (cosmic-proposed/universe) [0.1.83-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: yaha [s390x] (cosmic-proposed/universe) [0.1.83-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: r-cran-shinythemes [amd64] (cosmic-proposed/universe) [1.1.1+dfsg-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: isc-kea [s390x] (cosmic-proposed/universe) [1.4.0.P1-3] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: suitesparse [s390x] (cosmic-proposed/main) [1:5.3.0+dfsg-1] (edubuntu, kubuntu, ubuntu-desktop, ubuntugnome)
[23:26] -queuebot:#ubuntu-release- New binary: yaha [ppc64el] (cosmic-proposed/universe) [0.1.83-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: isc-kea [ppc64el] (cosmic-proposed/universe) [1.4.0.P1-3] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: suitesparse [ppc64el] (cosmic-proposed/main) [1:5.3.0+dfsg-1] (edubuntu, kubuntu, ubuntu-desktop, ubuntugnome)
[23:29] -queuebot:#ubuntu-release- New binary: suitesparse [amd64] (cosmic-proposed/main) [1:5.3.0+dfsg-1] (edubuntu, kubuntu, ubuntu-desktop, ubuntugnome)
[23:30] -queuebot:#ubuntu-release- New binary: pari [s390x] (cosmic-proposed/universe) [2.11.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: isc-kea [amd64] (cosmic-proposed/universe) [1.4.0.P1-3] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: pari [ppc64el] (cosmic-proposed/universe) [2.11.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [arm64] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: libqaccessibilityclient [armhf] (cosmic-proposed/universe) [0.2.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: pari [amd64] (cosmic-proposed/universe) [2.11.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: suitesparse [arm64] (cosmic-proposed/main) [1:5.3.0+dfsg-1] (edubuntu, kubuntu, ubuntu-desktop, ubuntugnome)
[23:41] -queuebot:#ubuntu-release- New binary: suitesparse [armhf] (cosmic-proposed/main) [1:5.3.0+dfsg-1] (edubuntu, kubuntu, ubuntu-desktop, ubuntugnome)
[23:55] -queuebot:#ubuntu-release- New binary: isc-kea [i386] (cosmic-proposed/universe) [1.4.0.P1-3] (no packageset)
[23:55] -queuebot:#ubuntu-release- New binary: pari [i386] (cosmic-proposed/universe) [2.11.0-1] (no packageset)


[10:49] <rawtaz> hi!
[10:51] <rawtaz> question: i am writing a conf for a third paty script which in turn starts a daemon. but it doesnt return a PID so i need to make a post-start script that grabs the pid. i can do that, but how should i hand the resolved PID of the final process to upstart so that it can keep track of things? should i e.g. put it in a file (pidfile maybe), and/or should i set a variable in the upstart conf, or something else?
[11:49] <rawtaz> not having very much success with this. i need to tell whatever upstart is which pid the executed process has. how can i do that?
[11:50] <rawtaz> so it tracks the right pid
[13:40] <JanC_test> rawtaz, maybe use start-stop-daemon  (you can't hand over the pid to upstart right now)
[13:41] <SpamapS> rawtaz: There are only two options. Either you make the process not "daemonize" (usually "foreground mode" in the options), or you carefully count the number of times it forks before being a daemon, and use 'expect fork' or 'expect daemon'.
[13:41] <SpamapS> rawtaz: a third option is to run the program in post-start, and in post-stop, you use the pidfile to kill it. THis means upstart does not keep track of the pid and can't do things like respawn.
[13:44] <rawtaz> JanC_test: start-stop-daemon is an ubuntu thing i believe :)
[13:44] <rawtaz> SpamapS: oh, didnt know about foreground mode, gonna check it out
[13:44] <rawtaz> SpamapS: yeah, but for some impossible-to-understand reason there's only two levels of forking supported. to me thats a big wtf but i guess it's the way it is
[13:45] <rawtaz> SpamapS: doing your third suggestion is what i ended up with, found a post on SO as well. having some trouble with it not binding correctly but that shouldnt be due to upstart :)
[13:46] <rawtaz> so i think it's okay. i guess this means upstart doesnt track the pid and have no control over the process, but thats fine i think, its not that important
[13:46] <rawtaz> thanks a lot for your help guys :)
[13:57] <SpamapS> rawtaz: np, and agreed, that is silly and they should fix it
[13:57] <SpamapS> rawtaz: or, if you feel like you might know enough C, you could of course fix it yourself :)
[13:58] <rawtaz> i could, if i did :D


[06:58] <dsofeir> Hello, I am placing a file network-config in the CIDATA ISO and it will not apply the config to the Ubunutu 18.04 netplan