[02:41] <excalibr> hello good moarning
[02:45] <fairuz> excalibr: hello
[03:31] <excalibr> umm since when askubuntu integrated with ubuntu main site?


[15:05] <doko> cjwatson, pitti: please can we shorten the time for the python-defaults migration from -proposed to -updates? I'd like to send a followup on python2.7 and offer a safe way for an upgrade (update to -updates before an update to natty )
[15:10] <lamont> cjwatson: if you get a chance today, please abuse royal and see if you can get it to fall over again, mk?
[15:10] <lamont> because if it does well, then, well.... we'll just have to put the maverick kernel on the rest of the ppc lineup
[15:13] <cjwatson> lamont: kubuntu build running again, then
[15:14] <lamont> ta
[16:35] <ScottK> Looks like we have a winner http://cdimage.ubuntu.com/kubuntu/daily-live/20101215.1/natty-desktop-powerpc.iso
[16:35] <cjwatson> oh good
[16:35] <cjwatson> that said royal seems to be NOT LISTENING again
[16:36] <ScottK> Falling over after the build is complete is progress, I guess.
[17:08] <lamont>  17:07:58 up 20:43,  1 user,  load average: 1.57, 1.48, 1.12 <-- royal likes me just fine...
[17:08] <cjwatson> uh, ok, maybe I was trying to talk http to it from the wrong angle
[20:55] <micahg> skaet: ping
[22:19] <micahg> skaet: ping re: 10.04.2 freeze schedule
[22:19] <skaet> micahg: pong.
[22:19] <skaet> sorry I missed you earlier.
[22:20] <skaet> what about the 10.04.2 freeze schedule?
[22:20] <micahg> skaet: hi, no problem, I was wondering if there will be the standard 2 day before freeze for 10.04.2 or if it'll be longer
[22:20] <micahg> i.e. freeze/generate images the Tuesday before release
[22:21] <skaet> micahg,  probably worth discussing a bit at the next LTS/SRU meeting I think.
[22:21] <micahg> skaet: should I join on Monday?
[22:21] <skaet> Unless its urgent,  I'll add it to the agenda.
[22:21] <micahg> skaet: nope, not urgent, just fact gathering for the xubuntu team
[22:22] <skaet> micahg:  doesn't look like we'll have quorum for a call this year.   (holiday time off starting for most...)
[22:22] <skaet> How about i make sure its on the agenda for the Jan 3 meeting?
[22:22] <micahg> skaet: sounds good, that still gives about a month to move on anything we need to take care of
[22:23] <skaet> micahg,  :)  that will be the plan then.
[22:23] <micahg> should I be at the meeting or just watch for the notes on ubuntu-devel?
[22:23] <skaet> it would be good if you're at the meeting.
[22:23] <micahg> skaet: ok, I'll plan on that then, thank you for your time
[22:24] <skaet> micahg, thank you for raising it.  :)
[22:27] <micahg> glad to help :)


[00:46] <mwhudson> what's going on with bsdmainutils and hexdump not being found in armhf autopkgtests?
[01:17] <xnox> ghc should be going green through to level 16.
[01:18] <xnox> vorlon:  the haskell-haskell-gi-base rollback was good, please rollback haskell-haskell-gi too now (level 17), after rebuilding 0.21.5 version of that the rest of level 18 should be just binNMUs
[01:19]  * xnox works off https://people.canonical.com/~ubuntu-archive/transitions/html/ghc-new.html
[05:22] -queuebot:#ubuntu-release- New binary: libextractor [amd64] (groovy-proposed/universe) [1:1.10-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: libextractor [s390x] (groovy-proposed/universe) [1:1.10-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: libextractor [arm64] (groovy-proposed/universe) [1:1.10-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: libextractor [ppc64el] (groovy-proposed/universe) [1:1.10-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: libextractor [armhf] (groovy-proposed/universe) [1:1.10-1] (no packageset)
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [amd64] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [armhf] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [ppc64el] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [s390x] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [arm64] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [riscv64] (groovy-proposed) [12.1.3ubuntu1]
[06:19] -queuebot:#ubuntu-release- New: accepted bsdmainutils [i386] (groovy-proposed) [12.1.3ubuntu1]
[07:33] <LocutusOfBorg> mwhudson, I *think* armhf chroot needs an update, to pick up the new bsdmainutils and util-linux versions. somewhat, the version they have installed is broken, and they are not prompted for the upgrade?
[07:33] <LocutusOfBorg> in any case, the new bsdmainutils I just uploaded should make everybody happy
[07:34] <LocutusOfBorg> now bsdmainutils requires bsdextrautils
[07:34] <LocutusOfBorg> so, everybody is happy (at least should be)
[08:10] <Laney> ok, it is britney upgrade time
[08:10] <Laney> I'm going to disable it and wait for any in-progress runs to finish
[08:11] <Laney> then I'll take a backup of data/ in case it goes horribly wrong, and then merge the branch and try a manual run of groovy
[10:01] -queuebot:#ubuntu-release- Unapproved: debhelper (focal-backports/main) [12.10ubuntu1 => 13ubuntu1] (core, i386-whitelist) (sync)
[10:01] -queuebot:#ubuntu-release- Unapproved: libvirt (focal-proposed/main) [6.0.0-0ubuntu8.1 => 6.0.0-0ubuntu8.2] (ubuntu-server, virt)
[10:01] -queuebot:#ubuntu-release- Unapproved: simple-scan (focal-proposed/main) [3.36.0-0ubuntu1 => 3.36.3-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[10:01] -queuebot:#ubuntu-release- Unapproved: budgie-extras (focal-proposed/universe) [1.0.1-2 => 1.0.2-0ubuntu1] (personal-fossfreedom, ubuntu-budgie)
[10:01] -queuebot:#ubuntu-release- Unapproved: vagrant (focal-proposed/universe) [2.2.6+dfsg-2ubuntu2 => 2.2.6+dfsg-2ubuntu3] (ubuntu-cloud)
[10:01] -queuebot:#ubuntu-release- Unapproved: orocos-kdl (focal-proposed/universe) [1.4.0-7build2 => 1.4.0-7ubuntu1] (no packageset)
[10:02] -queuebot:#ubuntu-release- Unapproved: im-config (focal-proposed/main) [0.44-1ubuntu1 => 0.44-1ubuntu1.1] (desktop-core, input-methods, personal-gunnarhj)
[10:02] -queuebot:#ubuntu-release- Unapproved: simple-scan (focal-proposed/main) [3.36.0-0ubuntu1 => 3.36.3-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[10:02] -queuebot:#ubuntu-release- Unapproved: libseccomp (focal-proposed/main) [2.4.3-1ubuntu<IP_ADDRESS> => 2.4.3-1ubuntu<IP_ADDRESS>] (core, i386-whitelist)
[10:02] -queuebot:#ubuntu-release- Unapproved: wslu (focal-proposed/main) [2.3.6-0ubuntu1 => 2.3.6-0ubuntu2~20.04.0] (core)
[10:08] <Laney> git reset --hard ubuntu/rebased
[10:08]  * Laney grits teeth
[10:08] <Laney> git push --force-with-lease origin master
[10:39] <Laney> ok first run underway
[10:42] <Laney> oh ok, it crashed :p
[12:20] -queuebot:#ubuntu-release- Unapproved: s390-tools (groovy-proposed/main) [2.12.0-0ubuntu5 => 2.12.0-0ubuntu5] (core)
[12:37] -queuebot:#ubuntu-release- New binary: linux-signed-kvm [amd64] (focal-proposed/main) [5.4.0-1020.20] (no packageset)
[13:22] -queuebot:#ubuntu-release- New: accepted ibus-typing-booster [amd64] (groovy-proposed) [2.8.2-2]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [amd64] (groovy-proposed) [3.13.3+dfsg1-1]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [armhf] (groovy-proposed) [3.13.3+dfsg1-1]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [riscv64] (groovy-proposed) [3.13.3+dfsg1-1]
[13:22] -queuebot:#ubuntu-release- New: accepted ibus-typing-booster [amd64] (groovy-proposed) [2.9.3-1]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [ppc64el] (groovy-proposed) [3.13.3+dfsg1-1]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [arm64] (groovy-proposed) [3.13.3+dfsg1-1]
[13:22] -queuebot:#ubuntu-release- New: accepted slepc [s390x] (groovy-proposed) [3.13.3+dfsg1-1]
[14:07] <Laney> ubuntu-archive can someone please merge lp:~laney/ubuntu-archive-tools/sru-report-excuses-xz ? should be relatively trivial
[14:47] <RikMills> Laney: britney will be working today? or shall I go for an early beer :)
[15:07] <Laney> yeah
[15:07] <Laney> grinding on
[15:08] <Laney> but if you're sitting around waiting for a run to finish, I'm concerned for you and you should go have a beer :-)
[15:12] <ahasenack> 46Mb output log already
[15:12] <ahasenack> normal size is 15Mb
[15:12] <ahasenack> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/groovy/2020-07-10/
[15:19] <Laney> grab yer popcorn
[15:24] <Laney> btw I forgot a configuration item and all of the requests for this run are going into the non-huge queue
[15:24] <Laney> whoopsie
[15:34] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-111.112] (core, kernel)
[15:34] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-111.112] (core, kernel)
[15:37] -queuebot:#ubuntu-release- New binary: slepc4py [s390x] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[15:39] -queuebot:#ubuntu-release- New binary: slepc4py [ppc64el] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[15:40] <vorlon> Laney: lp:~laney/ubuntu-archive-tools/sru-report-excuses-xz merged
[15:42] -queuebot:#ubuntu-release- New binary: slepc4py [amd64] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[15:43] <Laney> merci pour le merge
[15:43] <Laney> maybe one day this run will finish
[15:45] <vorlon> :)
[15:45] <vorlon> are there performance regressions, or is it just the fact that proposed is really Bad right now?
[15:47] <Laney> It's re-fetching all the results
[15:48] <Laney> with hindsight I could have probably continued to use the existing cache
[15:48] -queuebot:#ubuntu-release- New binary: slepc4py [armhf] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[15:48] -queuebot:#ubuntu-release- New binary: slepc4py [arm64] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[16:20] -queuebot:#ubuntu-release- Unapproved: pulseaudio (bionic-proposed/main) [1:11.1-1ubuntu7.9 => 1:11.1-1ubuntu7.10] (desktop-core, ubuntu-server)
[16:21] <vorlon> seb128: fyi https://launchpad.net/ubuntu/+source/jdupes/1.17.1-1ubuntu1
[16:22] <seb128> vorlon, ah, that would do I guess, thanks!
[16:45] -queuebot:#ubuntu-release- New binary: slepc4py [riscv64] (groovy-proposed/universe) [3.13.0-4] (no packageset)
[17:05] <ginggs> is neutral -> failed no longer a regression?
[17:09] <Laney> neutral didn't exist before, it was mapped to pass
[17:09] <Laney> they're basically ignored
[17:11] <ginggs> Laney: thanks, i was looking at https://autopkgtest.ubuntu.com/packages/p/python-loompy/groovy/amd64 which was blocking pandas, but not any more
[17:11] <LocutusOfBorg> mmm Laney I don't understand debci failure in armhf
[17:11] <Laney> yeah, so that should be alwaysfail now
[17:11] <LocutusOfBorg> so the hints needs a change?
[17:12] <Laney> I don't know anything about debci
[17:13] <Laney> please explain more verbosely and I'll look when I get back from being outside
[17:13] <LocutusOfBorg> debci 2.0 passed because of foo, then somebody did implement a testsuite that failed
[17:13] <LocutusOfBorg> and somebody else did this hint force-reset-test debci/2.7
[17:14] <LocutusOfBorg> now, if you look at bsdmainutils on excuses there is this:
[17:14] <LocutusOfBorg> autopkgtest for debci/2.13: amd64: Not a regression, arm64: Test in progress (will not be considered a regression), armhf: Test in progress, i386: Ignored failure, ppc64el: Not a regression, s390x: Not a regression
[17:14] <LocutusOfBorg> armhf : Test in progress, while I would have expected armhf: Test in progress (will not be considered a regression),
[17:15] <ginggs> Laney: I guess LP: #1818119 can be closed now
[17:15] <Laney> did that work before?
[17:15] <Laney> I think we just don't handle the reset-test hints when looking at RUNNING
[17:15] <Laney> ginggs: yeah
[17:15] <Laney> please do it, if you can
[17:15]  * Laney is out now
[17:16] <LocutusOfBorg> oh, Laney thanks! in any case, I need util-linux and bsdmainutils to migrate, so I'll ping in case this is not true
[17:16] <LocutusOfBorg> I don't understand why arm64 is "correct" and armhf isn't, but meh
[17:16] <LocutusOfBorg> new britney run just started yay
[17:17] -queuebot:#ubuntu-release- New binary: golang-github-biogo-store [amd64] (groovy-proposed/none) [0.0~git20200525.8c94ae1-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: golang-github-brentp-irelate [amd64] (groovy-proposed/none) [0.0~git20180801.1bf7c8f+ds-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: golang-github-digitalocean-go-qemu [amd64] (groovy-proposed/none) [0.0~git20200529.1b453d0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: golang-github-hashicorp-terraform-json [amd64] (groovy-proposed/none) [0.5.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: golang-github-cloudflare-circl [amd64] (groovy-proposed/none) [1.0.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: golang-github-gophercloud-utils [amd64] (groovy-proposed/none) [0.0~git20200508.b0167b9-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [amd64] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: golang-github-insomniacslk-dhcp [amd64] (groovy-proposed/universe) [0.0~git20200420.ed3125c-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: golang-github-logrusorgru-aurora [amd64] (groovy-proposed/universe) [1.1-12-ge9ef32dff3813d13d2c5b0c850af46bda56f4ca5-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: golang-github-otiai10-copy [amd64] (groovy-proposed/universe) [1.2.0-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: gophernicus [amd64] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: golang-github-mattn-go-tty [amd64] (groovy-proposed/universe) [0.0.3-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: golang-github-shenwei356-xopen [amd64] (groovy-proposed/universe) [0.0~git20181203.f4f16dd-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: golang-github-mozillazg-go-httpheader [amd64] (groovy-proposed/universe) [0.2.1-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: golang-github-openprinting-goipp [amd64] (groovy-proposed/universe) [0.0~git20200517.da79ff1-1] (no packageset)
[17:23] <LocutusOfBorg> Laney, bad bad...
[17:24] <LocutusOfBorg> lintian is considered for migration
[17:24] <LocutusOfBorg> but the new version isn't installable with main-only pocket
[17:24] <LocutusOfBorg>  lintian : Depends: libtext-levenshteinxs-perl but it is not installable
[17:24] <LocutusOfBorg>            Depends: libtext-xslate-perl but it is not installable
[17:24] <LocutusOfBorg>            Depends: libtime-duration-perl but it is not installable
[17:24] <LocutusOfBorg>            Depends: libtime-moment-perl but it is not installable
[17:24] <LocutusOfBorg> but according to https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_output_notest.txt
[17:24] <LocutusOfBorg> trying: lintian
[17:24] <LocutusOfBorg> accepted: lintian
[17:24] <LocutusOfBorg> is britney not considering correctly components?
[17:25] -queuebot:#ubuntu-release- New binary: fasttext [amd64] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [s390x] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: pybdsf [amd64] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: gophernicus [s390x] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: fasttext [ppc64el] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [arm64] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: gophernicus [ppc64el] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: fasttext [s390x] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: pybdsf [s390x] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [ppc64el] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [armhf] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: pybdsf [ppc64el] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: fasttext [armhf] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: gophernicus [armhf] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: gophernicus [arm64] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: gophernicus [riscv64] (groovy-proposed/universe) [3.0.1-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: fasttext [arm64] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: pybdsf [armhf] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: pybdsf [arm64] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: golang-github-ajstarks-svgo [riscv64] (groovy-proposed/universe) [2012-01-27-1] (no packageset)
[17:44] <xnox> Laney:  retry-autopkgtests-regressions seems to be borked against new britney
[17:44] <xnox> or whatever it uses as input
[17:52] -queuebot:#ubuntu-release- New binary: pybdsf [riscv64] (groovy-proposed/universe) [1.9.2-2] (no packageset)
[18:00] -queuebot:#ubuntu-release- New binary: fasttext [riscv64] (groovy-proposed/universe) [0.9.2-1] (no packageset)
[18:06] <vorlon> Laney: https://paste.ubuntu.com/p/Cm9295pZRM/
[18:19] <vorlon> Laney: possibly because it's pointing at your directory on people
[18:57] <Laney> lol
[18:58] <Laney> WHO REVIEWED THAT
[19:00] <Laney> oh yeah I did ~/... but I wasn't running as that user
[19:01] <Laney> ah no
[19:02] <Laney> I'll be back in abit to look at that, got to EAT!
[19:10] -queuebot:#ubuntu-release- New: accepted linux-signed-kvm [amd64] (focal-proposed) [5.4.0-1020.20]
[19:11] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-111.112]
[19:11] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-111.112]
[19:13] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-4.15 [amd64] (bionic-proposed/universe) [4.15.0-1080.90] (no packageset)
[19:27] <Laney> now then
[19:28] <xnox> vorlon:  can you process the other haskell-gi removal from proposed? https://bugs.launchpad.net/ubuntu/+source/haskell-haskell-gi/+bug/1886889
[19:29] <xnox> (cause of course it is split into two source packages)
[19:29] <Laney> who knew r-a-r had this whole caching thing
[19:29] <Laney> not me
[20:43] <Laney> LocutusOfBorg: thx for the report, ogre model stuff should be fixed with the next run, see https://people.canonical.com/~ubuntu-archive/laney/proposed-migration/update_excuses.html#lintian (that's a notest run though)
[20:47] <Laney> vorlon: xnox: https://code.launchpad.net/~laney/ubuntu-archive-tools/retry-autopkgtest-regressions-lzma-cache/+merge/387242 for retry-autopkgtest-regressions
[20:47] <Laney> vorlon: also, sru-report seems to have fixed itself
[20:47] <Laney> at least: I ran it manually and got output after many tens of minutes
[20:48] <Laney> (on snakefruit)
[20:49] <Laney> I'm going to have a bit of a weekend now, please keep leaving me nastygrams :>
[22:49] <vorlon> rolling back haskell-haskell-gi, which also has to be rolled back along with haskell-haskell-gi-base due to ansi-terminal
[22:50] <vorlon> xnox: ^^
[22:51] <vorlon> Laney: sru-report might be fixed because I fixed it, yes. :) Have a good weekend!
[23:02] <xnox> vorlon: thank you!!!! ❤
[23:14] -queuebot:#ubuntu-release- New binary: golang-github-digitalocean-go-qemu [amd64] (groovy-proposed/universe) [0.0~git20200529.1b453d0-2] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: golang-github-gophercloud-utils [amd64] (groovy-proposed/universe) [0.0~git20200508.b0167b9-2] (no packageset)
[23:15] -queuebot:#ubuntu-release- Unapproved: mutter (focal-proposed/main) [3.36.3-0ubuntu<IP_ADDRESS> => 3.36.3-0ubuntu<IP_ADDRESS>] (desktop-core, desktop-extra)
[23:16] -queuebot:#ubuntu-release- New binary: golang-github-insomniacslk-dhcp [amd64] (groovy-proposed/universe) [0.0~git20200621.d74cd86-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: golang-github-mattn-go-tty [amd64] (groovy-proposed/universe) [0.0.3-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: timekpr-next [amd64] (groovy-proposed/universe) [0.2.13-2] (no packageset)
[23:21] <xnox> vorlon:  can you please cleanup NBS of haskell-haskell-gi binaries from the 0.23.1-1 build? source got superseeded, but never built, hence there are lingering binaries published.
[23:21] <xnox> vorlon:  and my upload currently fails
[23:22] -queuebot:#ubuntu-release- New binary: timekpr-next [armhf] (groovy-proposed/universe) [0.2.13-2] (no packageset)
[23:22] <xnox> https://launchpadlibrarian.net/488075436/upload_19575998_log.txt
[23:22] <xnox> binary upload logs
[23:22] <tyhicks>  /quit
[23:22] <xnox> tyhicks:  was that too much haskell for you? =)
[23:23] <xnox> tyhicks:  sorry, if that was not informative enough chatter for the past few weeks =)
[23:23] <tyhicks> xnox: heh, any haskell is too much haskell for me ;)
[23:24] -queuebot:#ubuntu-release- New binary: timekpr-next [arm64] (groovy-proposed/universe) [0.2.13-2] (no packageset)
[23:24] <xnox> vorlon:  https://paste.ubuntu.com/p/mTqRX9Qzwy/
[23:24]  * tyhicks tries to get his /quit command right this time...
[23:28] -queuebot:#ubuntu-release- New binary: timekpr-next [s390x] (groovy-proposed/universe) [0.2.13-2] (no packageset)
[23:30] <vorlon> xnox: oh bother
[23:30] <xnox> We all love launchpad publication history!
[23:31] <vorlon> xnox: done, and also uploaded
[23:32] <xnox> Oooh, you can upload without rebuild?
[23:32] <vorlon> oh actually no, I was thinking sourceful reupload, which is pointless
[23:32] <vorlon> but the builds can be retried
[23:32] <xnox> Last time I just retried the build. To cause a reupload.
[23:32] <vorlon> yeah, done now
[23:32] <xnox> Tah
[23:36] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.5 => 1.37~18.04.6] (core)
[23:47] -queuebot:#ubuntu-release- New binary: timekpr-next [ppc64el] (groovy-proposed/universe) [0.2.13-2] (no packageset)
[23:48] -queuebot:#ubuntu-release- New binary: timekpr-next [riscv64] (groovy-proposed/universe) [0.2.13-2] (no packageset)


[08:00] <tnzk> hi, I'm learning how bzr merges branches now. I undestand bzr uses the algorithm called LCA Merge today.
[08:00] <tnzk> but what does it differ from Recursive Three-way Merge? It seems very similar to me.
[08:00] <tnzk> I mean the recursive three-way merge of Git.
[08:07] <fullermd_> Actually, I think the default is still plain 3-way merge, with LCA and weave as alternate options.
[08:09] <fullermd_> Vague memory says that the 'lca' variant uses per-file LCA's rather than full-tree?  But I wouldn't put much stock in my memory.
[08:10] <fullermd_> I don't think bzr does git-ish recursive-3-way.  At least not without a plugin I've never heard of.
[08:23] <tnzk> Oh I just read literally bzr wiki says that it *could* be the default...
[08:23] <tnzk> Am I right to think bzr uses plain 3-way merge by default, and with options it can merge by 'lca' which is more accurate than 'recursive' strategy of git.
[08:24] <fullermd_> "more accurate" is a bottomless pit of discussion   ;p
[08:27] <tnzk> indeed :p okay, I'll keep on learning. thank you.
[08:41] <fullermd_> Once upon a time, there were decent descriptions/discussions/etc on the revctrl wiki.
[08:41] <fullermd_> It was drowned in spam and them tossed away some years back, but there might be an archive somewhere.
[11:51] <quicksilver> I think bzr missing displays the wrong message.
[11:51] <quicksilver> bzr missing --theirs-only -r1234 bzr+ssh:/path/to/remove
[11:51] <quicksilver> displays
[11:51] <quicksilver> Other branch is up to date.
[11:52] <quicksilver> actually surely it means *this* branch is up to date. "My branch" as the command line options call it.
[11:53] <quicksilver> oh there we go
[11:53] <quicksilver> https://bugs.launchpad.net/bzr/+bug/250296
[11:53] <quicksilver> reported 2008 :(
[13:23] <tnzk> @fullermd: I've never heard about revctl wiki but it looks very valuable in the internet archive
[13:24] <tnzk> @fullermd: I wish I was then interested in this topic...


[12:58] <Peppep> Hi. I installed the latest development build with kernel <IP_ADDRESS>, and am unable to login. After about a second after entering the password, I'm back at login
[12:59] <Peppep> Currently in tty3 to get weechat running, can anyone give any troubleshooting tips?
[12:59] <BluesKaj> try nomodeset
[12:59] <BluesKaj> !nomodeset
[13:01] <Peppep> Hmm, okay. I've actually used nomodeset before, but then I didn't get passed Grub, and I was under the impression that the Nvidia drivers would be carried over to the new install. Thanks!
[13:12] <Peppep> I tried nomodeset and nouveau.modeset=0, but I still couldn't log in
[13:19] <Peppep> And updating from nvidia-390 to nvidia-410 did not help. Are there any logs I could check to get some indication about the culprit?
[13:39] <BluesKaj> Peppep, /var/log/syslog
[13:51] <Peppep> gsd-keyboard fatal io error 11, gsd-media-keys fatal io error 11 etc
[13:55] <Peppep> Unrecoverable failture in required component org.gnome.Shell.desktop. I know it's not much, and I'm trying to search other places, but I included a few of the errors here in case they are common and fixable
[14:03] <BluesKaj> Peppep, did you update and upgrade while in the VT/TTY?
[14:09] <Peppep> BluesKaj: The nvidia driver? Yes. Is that something I shouldn't do? :/
[14:11] <Peppep> But it doesn't seem to be running. When I do lshw c -video, the driver seems to be the Intel one for the integrated GPU (on Dell XPS 9560), not the Nvidia card
[14:11] <Peppep> running/loaded*
[14:13] <BluesKaj> Peppep, I sudo apt update && sudo apt upgrade ..all packages
[14:13] <BluesKaj> meant
[14:13] <Peppep> Oh, yeah, I did that as well. There wasn't anything to upgrade
[14:13] <BluesKaj> bummer
[14:17] <BluesKaj> definitely a hardware problem alright, dunno if the 410 nvidia driver is the corect one for your gpu if the 390 was the recommended driver in ubuntu-drivers... try, sudo ubuntu-drivers list
[14:18] <Peppep> 390 was the recommended one for 18.10 I believe, when I ran "ubuntu-drivers devices" 410 was recommended
[14:18] <Peppep> On 19.04
[14:53] <Peppep> BluesKaj: Any other ideas? I'm close to reinstalling 18.10  now. :/
[14:55] <BluesKaj> did some googling, but couldn't find anything applicable Peppep ...maybe 18.10 will work for you, altho it's more buggy than 18.04LTS
[14:57] <Peppep> The only theory I have is that some of the customizations I did to GNOME on 18.10 is incompatible with 19.04. But I don't know if it could cause fatal errors like this
[14:57] <Peppep> Since a lot of the syslog messages are related to GNOME
[14:58] <BluesKaj> which gnome customizations, like tweak or themes or?
[15:00] <Peppep> Mostly dash to dock, alttab changes etc. And I updated dash to dock from v17 to v19 because they added GNOME 3.32 support, so that shouldn't be it. But I had like 5-6 extensions
[15:01] <BluesKaj> not a gnome user so that's not my strong suit
[15:09] <Peppep> Tried deleting .gnome and .config/dconf/user in case it's related to the manual config. Fingers crossed. Thanks for the patience in any case
[15:12]  * BluesKaj crosses fingers
[15:12] <Peppep> Re 18.04 vs 18.10... I upgraded from 18.10 which was stable for me. I had to do nomodeset and a few other fixes initially, and I had to restart the network-manager service a few times, but overall I was happy
[15:12] <BluesKaj> ok
[15:12] <Peppep> But yeah, I could give 18.04LTS a shot in case it works perfectly out of the box
[15:12] <Peppep> Since it seems that I have to do a reinstall
[15:13] <BluesKaj> it's more mature and it receives more devel attention
[15:14] <Peppep> Yeah. Unfortunately I tend to run latest/beta versions of everything which sometimes causes hours and hours of troubleshooting like today :p
[15:15] <Peppep> Android Beta, Chrome Dev, Ubuntu 19.04 etc etc. And I'm not developing for any of those platforms, so I don't really have a good reason, other than wanting to have the newest stuff all the time
[15:15] <BluesKaj> well, if you like more edge then by all means Peppep
[15:17] <Peppep> In general, I do. But I'll use 18.04 until 19.04's official release. Then I'll do a live-boot before giving it another shot ;)
[15:18] <Peppep> Anyway, thanks again!
[15:18] <Peppep> BluesKaj++
[15:19] <Peppep> Hmm. Isn't there a karma system here? Crap
[15:19] <BluesKaj> hehe
[15:20] <Peppep> ;)
[15:21] <Peppep> loooooool
[15:21] <Peppep> After giving up
[15:21] <Peppep> Doing the final reboot
[15:21] <Peppep> It worked
[15:22] <Peppep> I'm officially on 19.04
[15:23] <BluesKaj> coolness!
[15:23] <tomreyn> being offficially on 19.04 is unlikely at this date, unless you can time travel
[15:24] <tomreyn> (but i'm glad you succeeded in fixing this issue)
[15:31] <Peppep> I'm not on official 19.04, I'm officially on (a) 19.04 (build)
[15:31] <Peppep> ;)
[15:31] <tomreyn> cool :) just making sure you're aware
[15:35] <Peppep> Oh, I'm way too aware, just spent hours troubleshooting since there's basically no possibilities of finding anyone else with similar issues at this stage.
[15:37] <Peppep> And for future reference, it was either the Intel driver (since I re-enabled my Nvidia card) or GNOME customizations from 18.10. Will disable to nvidia card again now to further narrow it down
[15:39] <tomreyn> gnome shell extensions are a good way to break gnome(-shell). generally, also on supported releases, use them at your own risk.
[15:39] <tomreyn> and surely disable them before anything else if there are any issues.
[15:40] <Peppep> Ah. I expected that they could cause issues, but not as fatally as this (stuck on login-screen)
[15:40] <Peppep> Was planning on disabling them before upgrading, but forgot about it, lol
[15:54] <Peppep> So my fingerprint reader is recognized in lsusb now (Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor)
[15:55] <Peppep> And I've enabled fingerprint auth in sudo pam-auth-update. But it still doesn't show up under Users. :/
[16:00] <OerHeks> according to https://launchpad.net/~fingerprint/+archive/ubuntu/fingerprint-gui and https://fprint.freedesktop.org/supported-devices.html, your "138a:0091 " is not there
[16:10] <Peppep> Ah :/
[16:12] <tomreyn> also https://www.dell.com/community/Linux-Developer-Systems/XPS-13-Fingerprint-reader-Linux-support/td-p/5090723
[16:13] <tomreyn> but then, fingerprint readers are not a safe authentication mechanism anyways. ;-)
[16:14] <OerHeks> a token or jubikey is my best access
[16:15] <OerHeks> or choose a password larger than 16 characters.. most rainbowtables stop there
[16:20] <BluesKaj> I didn't bother with fingerprint authentication on the Dell laptop
[16:22] <BluesKaj> my fingertips are almost calloused anyway ... drumsticks will do that
[16:24] <Peppep> Sometimes convenience wins over security unfortunately. But I'm getting there, step by step. Voluntarily by going from Windows to Linux, involuntarily by not being able to use fingerprints
[16:26] <Peppep> As of now, fp auth is pretty much the only thing Win10 wins on. Otherwise Ubuntu has better battery life, faster boot (and especially resume from sleep) ++
[16:27] <tomreyn> https://github.com/hmaarrfk/Validity91 is probably your best bet
[16:29] <tomreyn> 112x112 pixels, i wonder how brute forceable that is.
[16:29] <OerHeks> and unencrypted ..
[16:37] <Peppep> Is 112x112 a hardware limitation or just what they've been able to get so far? If the former, I agree, that's way more insecure than I was aware of
[16:41] <OerHeks> 180 x 256 pixels is more regular, mind that it should be encrypted before sending too
[16:56] <Peppep> BluesKaj tomreyn: It was the GNOME settings. I disabled the Nvidia card and the Intel drivers runs without issues
[16:57] <BluesKaj> Peppep, good stuff!
[17:04] <Peppep> The power consumption in 19.04 is even lower than in 18.10. Discharge rate at 3.9W-4.9W running weechat and powertop
[17:08] <Peppep> And wifi performence seems to be improved. Happy camper so far.
[17:08] <Peppep> Anyway, gtg, thanks guys!
[17:40] <Joe_from_next_do> Hello is the option for minimal installs still available in 1904? I didn't see it in my VM.
[17:45] <OerHeks> not in tasksel, only in ubiquity
[17:48] <Joe_from_next_do> Oh yes sorry I forgot to copy that. I'll go try it out again..
 The power consumption in 19.04 is even lower than in 18.10. Discharge rate at 3.9W-4.9W running weechat and powertop
[18:44] <erle-> nice
[18:44] <erle-> maybe that is also because of Gnome Shell efficiency
[18:45] <erle-> Is there a way to reboot everything except the kernel?
[18:45] <erle-> Important would be not to unmount /any/ file systems
[18:46] <erle-> to be more precise: boot live CD, do apt dist-upgrade and then reload everything (except kernel) so that the state if the live session stay intact (installed packets, settings in /home/ubuntu etc.)
[18:52] <erle-> Why was gnome-books not in Ubuntu before?
[18:52] <erle-> finally a reader that enables one to read epub without eyes hurting