[00:01] -queuebot:#ubuntu-release- New binary: pyrit [arm64] (focal-proposed/universe) [0.5.1+git20180801-2] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: nanopb [arm64] (focal-proposed/none) [0.4.1-1] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: pyrit [armhf] (focal-proposed/universe) [0.5.1+git20180801-2] (no packageset)
[00:03] -queuebot:#ubuntu-release- New binary: nanopb [armhf] (focal-proposed/none) [0.4.1-1] (no packageset)
[00:05] -queuebot:#ubuntu-release- New binary: vmfs6-tools [arm64] (eoan-backports/universe) [0.1.0-3~ubuntu19.10.1] (no packageset)
[00:06] -queuebot:#ubuntu-release- New binary: vmfs6-tools [armhf] (eoan-backports/universe) [0.1.0-3~ubuntu19.10.1] (no packageset)
[00:35] <RAOF> bdmurray: Your lz4 upload to xenial/bionic appears to add a new public symbol without mentioning it in the .symbols file - this seems like it might result in code having a dependency on a newer liblz4-1 but the package not depending on a new-enough liblz4-1?
[01:53]  * RAOF presumes process-removals doesn't take multiple hours to run for other people. I wonder if it's highly sensitive to launchpad roundtrip latency?
[02:19] -queuebot:#ubuntu-release- New binary: linux-signed-azure-5.3 [amd64] (bionic-proposed/main) [5.3.0-1011.12~18.04.1] (no packageset)
[02:19] -queuebot:#ubuntu-release- New binary: linux-signed-gke-5.3 [amd64] (bionic-proposed/universe) [5.3.0-1012.13~18.04.1] (no packageset)
[02:19] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-5.3 [amd64] (bionic-proposed/main) [5.3.0-1012.13~18.04.1] (no packageset)
[02:19] -queuebot:#ubuntu-release- New binary: linux-signed-oracle-5.3 [amd64] (bionic-proposed/main) [5.3.0-1009.10~18.04.1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: puppet-module-puppetlabs-host-core [amd64] (focal-proposed/universe) [1.0.3-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: puppet-module-puppetlabs-sshkeys-core [amd64] (focal-proposed/universe) [1.0.3-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: pycdio [amd64] (focal-proposed/universe) [2.1.0-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: ruby-net-http-pipeline [amd64] (focal-proposed/universe) [1.0.1-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: ruby-msfrpc-client [amd64] (focal-proposed/universe) [1.1.2-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: ruby-nfnetlink [amd64] (focal-proposed/universe) [1.0.2-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: ruby-optimist [amd64] (focal-proposed/universe) [3.0.0-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: ruby-otr-activerecord [amd64] (focal-proposed/universe) [1.4.1-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: puppet-module-puppetlabs-selinux-core [amd64] (focal-proposed/universe) [1.0.4-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: pycdio [s390x] (focal-proposed/universe) [2.1.0-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: pycdio [ppc64el] (focal-proposed/universe) [2.1.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: pycdio [arm64] (focal-proposed/universe) [2.1.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: pycdio [armhf] (focal-proposed/universe) [2.1.0-1] (no packageset)
[07:34] <ginggs> tarzeau: you should add a link to debian bug #919786 in your colmap ppc64el removal bug
[07:37] <tarzeau> ginggs: i agree
[08:56] <sil2100> jibel: hey! Are you also able to reproduce LP: #1861912 ?
[08:58] <jibel> sil2100, on it, I didn't try 32bit builds
[08:59] <jibel> sil2100, I didn't encounter the problem on amd64
[08:59] <sil2100> jibel: yeah, this weirdly seems i386-specific
[08:59] <sil2100> mwhudson: did you manage to figure anything out regarding this bug? ^
[09:14] <jibel> sil2100, first try, cannot resize "Invalid argument". I'll reformat the machine and try again
[09:18] <sil2100> darn
[09:24] <sil2100> juliank: hey! You have any spare cycles to help us solve this weird i386 18.04.4 partman mystery? ^
[09:24] <juliank> aye
[09:25] <sil2100> It will be terrible if we'll have to re-spin and re-test
[09:26] <jibel> sil2100, I'm wondering if it's trying to create more primary partitions than allowed on mbr
[09:26] <jibel> sil2100, second try works after reformatting the machine
[09:27] <jibel> mwhudson, can you dump the partition table of the machine you had this issue and attach it to the bug report
[09:27] <jibel> ?
[09:27] <jibel> there is no partman logs in your logs
[09:28] <juliank> Feb  4 22:40:14 debconf (filter): <-- INPUT critical partman-basicfilesystems/create_failed
[09:28] <juliank> jibel: There is log in installer/debug, like this^
[09:28] <jibel> yeah but it doesn't say why
[09:28] <mwhudson> jibel: i am no longer near the machine unfortunately
[09:28] <juliank> debconf (developer): <-- SUBST partman-basicfilesystems/create_failed PARTITION 5
[09:29]  * sil2100 needs to AFK for a bit
[09:29] <juliank> Question is, did it create the partition or not?
[09:30] <juliank> Partition 5 sounds like an extended one?
[09:31] <juliank> For that we do need a syslog I guess
[09:32] <juliank> 1477:Feb  4 22:40:14 ubuntu-mate partman: /dev/sdb5 is apparently in use by the system; will not make a filesystem here!
[09:32] <jibel> I'd like to know if all the primary partitions were used before it tries to create the extended one in which case it couldn't
[09:33] <jibel> or if the partition is already busy
[09:33] <juliank> there weas one primary partition on sda and sdb each, as partman log file shows
[09:34] <juliank> It's trying to installing to sdb
[09:35] <juliank> And then it fails formatting sdb5 because sdb5 is mounted
[09:35] <juliank> There was no sdb5 prior to install start
[09:36] <juliank> So it successfully created this, and then it somehow got mounted as ext4
[09:36] <juliank> but given that it was an external USB drive, it seems plausible this was automounted
[09:37] <juliank> although it should not have had a FS on it
[09:38] <juliank> But parted tells us at the end that it does
[09:38] <juliank> parted_server: command_partition_info: partition found
[09:38] <juliank> parted_server: OUT: 5<PHONE_NUMBER>-256060162047<PHONE_NUMBER>24 logical ext4 /dev/sdb5
[09:39] <juliank> So it's not a problem of creating partitions
[09:40] <juliank> and in syslog you can see
[09:40] <juliank> Feb  4 22:40:14 ubuntu-mate partman: /dev/sdb5 is apparently in use by the system; will not make a filesystem here!
[09:40] <juliank> interestingly os-prober ran before that
[09:40] <juliank> but there was no sdb5 back then
[09:41] <juliank> I don't see sdb5 being mounted in the kernel log, though
[09:44] <mwhudson> i'm kind of amazed sdb5 is created given that sdb is mounted
[09:44] <mwhudson> but why is it trying to install to the install media at all?
[09:45] <juliank> mwhudson: It did not resize sdb1 at all, there was enough space left
[09:46] <juliank> Ah, but if that's the install media, created in a normal way, it will have a screwed up partition table
[09:46] <juliank> Also, it should create one partition there for the log storage
[09:47] <juliank> I'm not sure when that happens, I think casper should be doing that early at boot?
[09:47] <juliank> or does it just do that at ubiquity time?
[09:48] <juliank> Certainly the guided options want to install on sda they say
[09:49] <juliank> mwhudson: I guess you picked biggest free option?
[09:49] <juliank> and this one defaulted to sdb:
[09:49] <juliank> partman-auto/init_automatically_partition 50biggest_free__________/var/lib/partman/devices/=dev=sdb//1964244992-256060514303
[09:50] <juliank> at least that's what it says you did
[09:51] <juliank> It should not even consider that disk, though
[09:51] <mwhudson> juliank: the text said "install alongside"
[09:51] <mwhudson> juliank: auto partition creation is not in casper in bionic
[09:52] <juliank> ah ok
[09:52] <mwhudson> just disco+ (i think)
[09:52] <juliank> That said, the debconf debug log looks like you picked "Guided - use the largest continuous free space"
[09:53] <juliank> I guess that's a suboption of install alongside?
[10:02] <juliank> Anyway, so far AFAICT it only affects people who use a huge install medium that has more free space than the other disks in the system
[10:03] <juliank> Of course, mwhudson's log may be misleading and the original bug report might be different
[10:10] <juliank> So, jibel to reproduce you need to have a small hard disk, and a USB stick that's larger than that. e.g. 64 GB hard disk and 128 GB USB stick formatted with the ISO should trigger it
[10:10] <juliank> Or a larger hard disk with no free space works too
[10:10] <juliank> I do have a 128GB USB stick and no free space on my SSD, so I could try that
[10:11] <juliank> Partman wrongly, instead of resizing partitions on your SSD, tries to install into the "free" space of your USB stick
[10:12] <jibel> juliank, it is not the case of mwhudson bug, is it?
[10:12] <jibel> according to syslog his setup is
[10:12] <jibel>  sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[10:12] <jibel>  sd 6:0:0:0: [sdb] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[10:12] <jibel>  sd 7:0:0:0: [sdc] 30283008 512-byte logical blocks: (15.5 GB/14.4 GiB)
[10:13] <juliank> Yes, but sda is fully filled up
[10:14] <juliank> sdb has free space:<PHONE_NUMBER>12
[10:15] <juliank> sda free space: 1073152
[10:15] <juliank> Not sure what the units are
[10:16] <juliank> Seem like bytes
[10:17] <juliank> So sdb has 254 GB contiguous free space
[10:17] <juliank> sda only 1MB
[10:19] <juliank> Let me reboot into my USB stick
[10:26] <juliank> I don't get such options because it does not recognize my FDE setup
[10:27] <juliank> I should try forwarding the USB stick to a VM
[10:34] -queuebot:#ubuntu-release- New: accepted pycdio [amd64] (focal-proposed) [2.1.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted pycdio [armhf] (focal-proposed) [2.1.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted pycdio [s390x] (focal-proposed) [2.1.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted pycdio [arm64] (focal-proposed) [2.1.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted pycdio [ppc64el] (focal-proposed) [2.1.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted puppet-module-puppetlabs-host-core [amd64] (focal-proposed) [1.0.3-1]
[10:34] -queuebot:#ubuntu-release- New: accepted puppet-module-puppetlabs-sshkeys-core [amd64] (focal-proposed) [1.0.3-1]
[10:34] -queuebot:#ubuntu-release- New: accepted ruby-net-http-pipeline [amd64] (focal-proposed) [1.0.1-1]
[10:34] -queuebot:#ubuntu-release- New: accepted ruby-optimist [amd64] (focal-proposed) [3.0.0-1]
[10:34] -queuebot:#ubuntu-release- New: accepted puppet-module-puppetlabs-selinux-core [amd64] (focal-proposed) [1.0.4-1]
[10:34] -queuebot:#ubuntu-release- New: accepted ruby-nfnetlink [amd64] (focal-proposed) [1.0.2-1]
[10:34] -queuebot:#ubuntu-release- New: accepted ruby-msfrpc-client [amd64] (focal-proposed) [1.1.2-1]
[10:34] -queuebot:#ubuntu-release- New: accepted ruby-otr-activerecord [amd64] (focal-proposed) [1.4.1-1]
[10:57] -queuebot:#ubuntu-release- New: accepted nanopb [amd64] (focal-proposed) [0.4.1-1]
[10:57] -queuebot:#ubuntu-release- New: accepted nanopb [armhf] (focal-proposed) [0.4.1-1]
[10:57] -queuebot:#ubuntu-release- New: accepted nanopb [s390x] (focal-proposed) [0.4.1-1]
[10:57] -queuebot:#ubuntu-release- New: accepted nanopb [arm64] (focal-proposed) [0.4.1-1]
[10:57] -queuebot:#ubuntu-release- New: accepted nanopb [ppc64el] (focal-proposed) [0.4.1-1]
[10:58] -queuebot:#ubuntu-release- New: accepted pyrit [amd64] (focal-proposed) [0.5.1+git20180801-2]
[10:58] -queuebot:#ubuntu-release- New: accepted pyrit [armhf] (focal-proposed) [0.5.1+git20180801-2]
[10:58] -queuebot:#ubuntu-release- New: accepted pyrit [s390x] (focal-proposed) [0.5.1+git20180801-2]
[10:58] -queuebot:#ubuntu-release- New: accepted pyrit [arm64] (focal-proposed) [0.5.1+git20180801-2]
[10:58] -queuebot:#ubuntu-release- New: accepted pyrit [ppc64el] (focal-proposed) [0.5.1+git20180801-2]
[11:04] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-5.3 [amd64] (bionic-proposed) [5.3.0-1011.12~18.04.1]
[11:04] -queuebot:#ubuntu-release- New: accepted linux-signed-gke-5.3 [amd64] (bionic-proposed) [5.3.0-1012.13~18.04.1]
[11:04] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-5.3 [amd64] (bionic-proposed) [5.3.0-1012.13~18.04.1]
[11:04] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle-5.3 [amd64] (bionic-proposed) [5.3.0-1009.10~18.04.1]
[11:07] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-440 [amd64] (bionic-proposed) [440.44-0ubuntu<IP_ADDRESS>]
[11:07] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-440 [i386] (bionic-proposed) [440.44-0ubuntu<IP_ADDRESS>]
[11:14] <juliank> It does not recognize the installation in my VM either
[11:14] <juliank> oh fun
[12:14] <sil2100> juliank, jibel: did you manage to get more info regarding the auto-resize option?
[12:14] <juliank> sil2100: I don't manage to reproduce it, but it seems to only affect installs where your install medium's free space is larger than your disk's free space
[12:16] <juliank> sil2100: None of my installations are recognized by ubiquity, so I'll have to setup a new one I guess and then try to install alongside it
[12:21] <jibel> sil2100, I tried several combinations but cannot reproduce it
[12:21] <juliank> There definitely is a bug, but I don't think it's i386 or 18.04.4 specific
[12:21] <jibel> agreed
[12:22] <jibel> and the bug likely exists in previous point releases
[12:23] <sil2100> Ok, thanks guys
[12:23] <sil2100> Let's keep an eye out on this one then - but from what I understand so far, whenever the bug happens, existing partitions or user data doesn't get corrupted, right?
[12:25] <jibel> IDK, there is not enough information in the bug report.
[12:26] <jibel> from the original reporter we'd need at least the system installed and the partition table before his attempt to install side by side.
[12:27] <sil2100> Let's try to get that info then, but until we know more I am not treating this as a blocker
[12:29] <sil2100> Per our earlier discussions with jibel
[12:35] <juliank> jibel: I'd be fine with the after state too, FWIW
[12:35] <juliank> No corruption should be happening, except for maybe the install medium, but idk for sure
[12:36] <jibel> well, we don't even know if Michael issue and the original report are the same
[12:36] <juliank> right
[12:36] <juliank> that's why I asked if he used a larger install medium
[12:38] <juliank> I'm going to install this once more
[12:39] <juliank> hmm
[12:39] <juliank> I now get the option to delete my uubntu install and reinstall
[12:39] <juliank> but no alongside option
[12:40] <juliank> So I'll give up
[12:40] <coreycb> rbasak: hello, if you have time today we have a horizon SRU in the eoan unapproved queue that we'd like to get reviewed. also would like to see if pandas could get released to -updates for 1861124 and 1861148.
[12:41] <sil2100> coreycb: please remember that bionic-updates is 'frozen' until we're done with 18.04.4!
[12:42] <coreycb> sil2100: ah right, ok thanks for the reminder
[12:57] <rbasak> coreycb: I'm only half here today, so I'm not sure if I'll find time, sorry. If someone else can pick it up, please do.
[12:59] <coreycb> rbasak: ok thanks for getting back. sil2100, I see you're up for tomorrow, if you get a chance could take a look at those ^ SRUs?
[13:19] <cpaelzer> in case an archive admin is around, here is a removal for a small step to get rid of postgresql-11 => https://bugs.launchpad.net/ubuntu/+source/rdkit/+bug/1862017
[13:20] <cpaelzer> And if one has time, I don't fully understand why it isn't listed in https://people.canonical.com/~ubuntu-archive/nbs.html
[13:20] <cpaelzer> so if that is easy to explain I'd appreciate to know the answer :-)
[13:45] <rbalint> rbasak, could you please check the ec2-instance-connect uploads in your SRU cycles? we already discussed the changes to some extent :-)
[13:47] <rbalint> rbasak, ah i see you have a short day today
[13:48] <rbalint> rbasak, at least the changes are small, but i'll try to find someone else if they can't fit in today
[14:04] -queuebot:#ubuntu-release- New binary: wal2json [amd64] (focal-proposed/universe) [2.0-1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: wal2json [s390x] (focal-proposed/universe) [2.0-1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: wal2json [ppc64el] (focal-proposed/universe) [2.0-1] (no packageset)
[14:05] -queuebot:#ubuntu-release- New binary: wal2json [arm64] (focal-proposed/universe) [2.0-1] (no packageset)
[14:05] -queuebot:#ubuntu-release- New binary: wal2json [armhf] (focal-proposed/universe) [2.0-1] (no packageset)
[14:06] <cpaelzer> along the removal in bug 1862017 I asked above there also is wal2json in the focal new queue now (both part of the postgresql-11 removal)
[14:17] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (xenial-proposed/main) [4.15.0-1053.57] (kernel)
[14:17] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-87.87~16.04.1] (kernel)
[14:17] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-87.87~16.04.1] (kernel)
[14:17] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1068.73] (kernel)
[14:28] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [5.3.0-40.32~18.04.1] (kernel)
[14:28] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1068.73]
[14:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-87.87~16.04.1]
[14:28] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [arm64] (bionic-proposed/main) [5.3.0-40.32~18.04.1] (kernel)
[14:28] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (xenial-proposed) [4.15.0-1053.57]
[14:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-87.87~16.04.1]
[14:29] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.3.0-40.32~18.04.1] (kernel)
[14:30] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [5.3.0-40.32~18.04.1]
[14:30] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [5.3.0-40.32~18.04.1]
[14:30] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [arm64] (bionic-proposed) [5.3.0-40.32~18.04.1]
[14:30] <rharper> rbasak: hi, would you have time to look at getting the curtin  upload into -proposed, https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1861452 while we start QA and verification process? maas 2.7 is waiting on this for their release
[14:46] -queuebot:#ubuntu-release- Unapproved: rtl8821ce (eoan-proposed/universe) [<IP_ADDRESS>.1.30816.20190425-0ubuntu1 => <IP_ADDRESS>-0ubuntu1~19.10.1] (no packageset)
[14:48] -queuebot:#ubuntu-release- Unapproved: rtl8821ce (bionic-proposed/universe) [<IP_ADDRESS>.1.30816.20190425-0ubuntu1~18.04.1 => <IP_ADDRESS>-0ubuntu1~18.04.1] (no packageset)
[14:50] <paride> sil2100, powersj, I added a new jenkins job testing the bionic arm64 d-i image, so I can submit results for that one too :)
[14:51] <sil2100> paride: sweet, thanks!
[14:51] <sil2100> jibel: btw. do you remember who usually did the netboot tests? Was it also you?
[14:52] <paride> sil2100, I set it up to only run the "smoke-default" test, but I can easily add some more test cases if needed
[14:53] <paride> the test run takes some time on arm64 so I kept it simple
[15:13] <sil2100> paride: thanks! So convenient ;)
[15:47] <cpaelzer> anyone around to handle removal of postgresql-11-rdkit (bug 1862017) and accept new wal2json in new queue (binary renamed postgresql-11-wal2json->postgresql-12-wal2json) ?
[16:00] -queuebot:#ubuntu-release- New: accepted wal2json [amd64] (focal-proposed) [2.0-1]
[16:00] -queuebot:#ubuntu-release- New: accepted wal2json [armhf] (focal-proposed) [2.0-1]
[16:00] -queuebot:#ubuntu-release- New: accepted wal2json [s390x] (focal-proposed) [2.0-1]
[16:00] -queuebot:#ubuntu-release- New: accepted wal2json [arm64] (focal-proposed) [2.0-1]
[16:00] -queuebot:#ubuntu-release- New: accepted wal2json [ppc64el] (focal-proposed) [2.0-1]
[16:18] <jibel> sil2100, I'm doing amd64 and i386 but cannot cover other archs
[16:27] -queuebot:#ubuntu-release- New binary: brltty [s390x] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core)
[16:29] -queuebot:#ubuntu-release- New binary: brltty [ppc64el] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core)
[16:31] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1032.35~16.04.1] (kernel)
[16:34] -queuebot:#ubuntu-release- New binary: brltty [arm64] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core)
[16:34] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (xenial-proposed) [4.15.0-1032.35~16.04.1]
[16:35] -queuebot:#ubuntu-release- New binary: brltty [armhf] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core)
[16:37] -queuebot:#ubuntu-release- New binary: brltty [amd64] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core)
[16:49] -queuebot:#ubuntu-release- Unapproved: glib2.0 (eoan-proposed/main) [2.62.3-2~ubuntu19.10.1 => 2.62.4-1~ubuntu19.10.1] (core)
[17:07] -queuebot:#ubuntu-release- New: accepted brltty [amd64] (focal-proposed) [6.0+dfsg-4ubuntu3]
[17:07] -queuebot:#ubuntu-release- New: accepted brltty [armhf] (focal-proposed) [6.0+dfsg-4ubuntu3]
[17:07] -queuebot:#ubuntu-release- New: accepted brltty [s390x] (focal-proposed) [6.0+dfsg-4ubuntu3]
[17:07] -queuebot:#ubuntu-release- New: accepted brltty [arm64] (focal-proposed) [6.0+dfsg-4ubuntu3]
[17:07] -queuebot:#ubuntu-release- New: accepted brltty [ppc64el] (focal-proposed) [6.0+dfsg-4ubuntu3]
[17:25] -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [s390x] (focal-proposed/universe) [0.1.9-2] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [amd64] (focal-proposed/universe) [0.1.9-2] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [ppc64el] (focal-proposed/universe) [0.1.9-2] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [arm64] (focal-proposed/universe) [0.1.9-2] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [armhf] (focal-proposed/universe) [0.1.9-2] (no packageset)
[18:30] -queuebot:#ubuntu-release- New: accepted python-deeptoolsintervals [amd64] (focal-proposed) [0.1.9-2]
[18:30] -queuebot:#ubuntu-release- New: accepted python-deeptoolsintervals [armhf] (focal-proposed) [0.1.9-2]
[18:30] -queuebot:#ubuntu-release- New: accepted python-deeptoolsintervals [s390x] (focal-proposed) [0.1.9-2]
[18:30] -queuebot:#ubuntu-release- New: accepted python-deeptoolsintervals [arm64] (focal-proposed) [0.1.9-2]
[18:30] -queuebot:#ubuntu-release- New: accepted python-deeptoolsintervals [ppc64el] (focal-proposed) [0.1.9-2]
[19:26] <rharper> rbasak: around ?
[19:40] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1069.79] (kernel)
[20:40] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1069.79]
[22:07] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (eoan-proposed) [19.3-17-g50ffca46-0ubuntu1~19.10.1]
[22:12] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (bionic-proposed) [19.3-17-g50ffca46-0ubuntu1~18.04.1]
[22:16] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [19.3-17-g50ffca46-0ubuntu1~16.04.1]
[23:23] -queuebot:#ubuntu-release- New binary: stk [amd64] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)
[23:23] -queuebot:#ubuntu-release- New binary: stk [s390x] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)
[23:23] -queuebot:#ubuntu-release- New binary: stk [ppc64el] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)
[23:23] -queuebot:#ubuntu-release- New binary: stk [i386] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)
[23:26] -queuebot:#ubuntu-release- New binary: stk [armhf] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)
[23:27] -queuebot:#ubuntu-release- New binary: stk [arm64] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio)


[08:36] <Kilos> o/
[14:12] <Kilos> congrats svij
[14:37] <Kilos> must i call you sir now?
[15:47] <svij> you guys saw that before me…
[15:48] <svij> 2 pings in 2 channels and though "what the hell is going on" :D
[15:48] <Kilos> lol
[15:49] <svij> TIL: I'm not even subscribed to the loco-contacts list…
[16:34] <toddy> svij: than it was good that I have drop you the link to that mail. :)
[16:34] <svij> toddy: yep! :)
[16:35] <svij> toddy: and thanks for the nomination ;)
[16:36] <toddy> svij: You are welcome :)


[00:08] <Myrtti> http://www.jeffbridges.com/fish.html
[00:08] <Myrtti> poor fishie
[00:08] <Myrtti> ;___;
[00:24] <Myrtti> watch out for -offtopic
[00:24] <Myrtti> I didn't ban him after kicking
[01:29] <thegeek> how do i get back on offtopic
[01:30] <LjL> why can't you join it?
[01:30] <thegeek> banned
[01:30] <LjL> ah, i see, so are you asking how to evade a ban?
[01:30] <thegeek> so how
[01:30] <thegeek> and yes
[01:31] <LjL> well, we're not going to tell you, and also, we don't approve of ban evading.
[01:31] <LjL> please don't.
[01:31] <nickrud> if you ask ljl really nicely
[01:31] <thegeek> c'moom
[01:31] <thegeek> c'mon
[01:31] <LjL> thegeek: you've just made your ban longer by a week.
[01:32] <bazhang> thegeek, and dont talk about it in #ubuntu please
[01:32] <LjL> @mark #ubuntu-ops thegeek
[01:37] <thegeek> and LjL how long is my ban anyway
[01:37] <LjL> thegeek: longer by another week
[01:37] <thegeek> witch was the start
[01:38] <LjL> thegeek: you know, you're asking entirely the wrong questions.
[01:38] <thegeek> witch are the right
[01:38] <thegeek> then
[01:39] <LjL> thegeek: well, take it as a riddle... you have at least two weeks to think about it and solve it
[01:39] <thegeek> im sorry for flodding the channel
[01:40] <thegeek> and typing junk
[01:40] <LjL> which wasn't what you did to begin with
[01:40] <thegeek> and im sorry i tried to beg
[01:40] <thegeek> you to lift the ban
[01:41] <LjL> you're getting better, but this ban isn't going to be lifted now, so come back here to say these things in a while.
[01:41] <thegeek> okay
[01:42] <thegeek> and by while how long
[01:42] <bazhang> 2 weeks
[01:42] <LjL> thegeek: another week longer than the last time you asked
[01:42] <LjL> bazhang: no, that's three
[01:42] <bazhang> +1
[01:46] <LjL> @mark #ubuntu-ops thegeek So, three weeks it is. Deal!
[03:28]  * tritium bangs his head against the wall
[07:50] <jussi01> Flannel: thats an auto kick for me...
[07:51] <Flannel> yeah, I should've.  I marked him (no pun intended) though.
[07:51] <jussi01> hehe
[07:52] <Flannel> I'm listening to a new bluegrass CD--in a good mood.  I suppose its a good time to be mildly annoying ;)
[07:53]  * jussi01 tickles Flannel
[08:06] <hischild> May i offer a suggestion for the ubuntu bot here?
[08:06] <Flannel> hischild: Go ahead
[08:08] <hischild> Well i've noticed more then once that people seem to forget the pipe character when they want to use ubottu (i just did again). I was wondering if there is a reason why you also need the pipe when you only would use 1 thing, like !ask.
[08:08] <Flannel> hischild: If you're not directing it at anyone, you don't need a pipe, no:
[08:08] <Flannel> !ask
[08:09] <hischild> Flannel, if you can check, it's about half a screen back. !ask LoRdRapTuReZ is not recognized by ubottu as i forgot a pipe.
[08:09] <Flannel> hischild: Correct, because there's no "ask Lord..." factoid
[08:09] <hischild> are the factoids with spaces then? If they are there, then i have missed them and my question has been answered.
[08:09] <Flannel> yep
[08:09] <Flannel> let me... find one
[08:10] <Flannel> !help me
[08:11] <hischild> Ah yes i see. Then my question has been answered. Thank you
[08:11] <Flannel> and while we could probably add some fuzzy logic, when ubottu (and its ilk) are in use in 10+ channels at a time, etc, the extra processing is likely troublesome
[08:12] <hischild> I understand that yes. That's why i was wondering if it could be done always. However, when there are factoids that have spaces, i understand the need for the pipe. I suppose a better eye for the typing errors will do then.
[08:13] <Flannel> hischild: someone will generally see it and correct you if you don't catch it.
[08:13] <hischild> Flannel, as i do with others. I thank you for your help. I suppose i should leave this channel? :-)
[08:14] <Flannel> either that, or ubottu will kick and scream.  We've all done it, more often than some of us care to admit.
[08:14] <Flannel> Aye, thanks
[08:14] <hischild> The thanks belong to you Flannel.
[08:14] <hischild> !helpersnack | Flannel  ;-)
[08:21] <Gary> I see zloy was here again
[09:21] <Flannel> Whomever can: the floodbots don't seem to be working in kubuntu for proxy users
[09:21] <Flannel> (I don't know if they have to go into -proxy-users separately or something)
[09:33] <Flannel> anyone awake have -ot?
[09:34] <ikonia> yup
[09:41] <Myrtti> just woke up
[09:51]  * elkbuntu huggles Myrtti good morning.
[09:56] <Myrtti> how many times have I mentioned I just love flexitime?
[09:57] <elkbuntu> Myrtti, hehe
[10:02] <Myrtti> and also - insomnia sucks
[10:02] <elkbuntu> yah
[10:05] <elkbuntu> Flannel, realisticly, requiring quotes around the multi-word factoids or similar grouping techniques is probably the proper way to deal with the issue.
[10:05] <elkbuntu> since there are fewer grouped factoids than there are mistypings
[10:06] <Myrtti> O_____O i haz email
[10:08] <Myrtti> jussi01: WHERE ARE YOU
[10:09] <elkbuntu> i think he was heading to Perth today or something
[10:10] <ikonia> he is a world traveller
[10:10] <Myrtti> damnit. all my friends I can tall nonsense with are offline
[10:36] <Tm_T> morgen kids
[10:37]  * Tm_T woke up ~0530 to change diapers & stuff
[10:55] <Myrtti> blizzard
[10:58] <Myrtti> can we shut down -offtopic?
[11:05] <bazhang> that would be ideal.
[11:05] <bazhang> maybe a hour or two of mute
[11:10] <bazhang> yaa1 is about to be removed
[11:17] <elkbuntu> i suspect he was trolling
[11:17] <bazhang> no doubt
[11:18] <ikonia> bad advice too
[11:18] <ikonia> "recompile" password
[11:18] <ikonia> password is part of the shadow package and would be pretty dangerous to rebuild that on a live system
[11:19] <elkbuntu> ikonia, it was the only way to get rid of him
[11:19] <elkbuntu> and it was made quite clear it was the stupidest thing ever
[11:19] <ikonia> I don't doubt that
[11:20] <elkbuntu> to be honest, anyone who wants to make passwords overwritable by regular users deserves a b0rked system.
[11:21] <ikonia> yes, I was more thinking of watc ubuntu patches against "cracklib" for example, and rebuilding a native shadow package would just murder your system
[11:21] <ikonia> "what" ubuntu patches against that should read
[11:42] <ikonia> Panarchy is starting to be a real danger
[11:42] <ikonia> in #ubuntu
[11:58] <elkbuntu> wow,  -ot is kind of on-topic...
[11:58] <ikonia> ha ha
[11:59] <gnomefreak> 7.04 was feisty right?
[12:00] <ikonia> yup
[12:01] <gnomefreak> thanks
[12:57] <ikonia> does anyone know if fedora has any group contacts for their loco channels
[12:57] <ikonia> I've just noted that one of the guys that tried to troll #ubuntu yesterday is actually a channel operator for a fedora loco
[13:19] <Ursinha> ikonia, operator? gee.
[13:21] <ikonia> only a loco operator, but still, it's an official channel, and after speaking with him, he can't see why joining #ubuntu under a false nick (I found him via IP) and saying "hey guys fedora 10 is out, you should all check it out, it's quick etc etc) then parting because he KNEW it was wrong, is wrong
[13:21] <ikonia> not really the right way to represent the fedora project in my view
[13:33] <LjL> ikonia: about fedora, i could probably pass the message on... who was this person and what channel?
[13:34] <ikonia> LjL: been trying to contact the guys myself
[13:34] <ikonia> LjL: guy is GNuBoi (he has many false nicks too) he runs the #fedora-nepal channel
[13:35] <LjL> ikonia: they've known me for some time (not too much, but some), so they might listen. but wait, the name you mentioned doesn't sound new to me
[13:35] <ikonia> LjL no, he's known as an issue in fedora
[13:35] <ikonia> I nkow some of the core ops (known for a year or two) and he's a ban / been banned in the core channel too
[13:36] <ikonia> hence my surprise to find him running an official "loco" or whatever it's called
[13:36] <LjL> ikonia: ah ok, in that case you should probably be the one talking to them
[13:37] <LjL> ikonia: but you see
[13:37] <LjL> ikonia: our own locos can be troublesome
[13:37] <LjL> ikonia: how many countries are there in the world? many...
[13:37] <ikonia> yup, and I'd do the same (have done the same)
[13:37] <ikonia> point it out to the right people, if they choose to act on it thats there call
[13:37] <LjL> ikonia: you do remember that we've had "him" as a loco channel contact for a while, don't you?
[13:37] <ikonia> (as in I would highlight/have highlited the same here)
[13:38] <ikonia> send me a name to refersh my memory as I've got brain fade
[13:38] <ikonia> LjL: wasn't "he" dropped though ?
[13:39] <ikonia> infact I remember lodging a complaint about it
[13:39] <LjL> ikonia: hm let's say there was pressure, at the very least
[13:39] <ikonia> that was one of the request I logged
[13:39] <ikonia> and I still publicly stand by that
[13:40] <LjL> ikonia: but indeed, you've certainly done the right thing reporting this one to the fedora people, i'm merely saying that you shouldn't be *too* surprised they have people like that running local channel
[13:40] <ikonia> no no, I understand that, and its easy to ignore what the small channels are up to
[13:40] <LjL> ikonia: they certainly seem quite sane a bunch generally speaking
[13:40] <ikonia> most of the guys I've taljked to are fine
[13:41] <LjL> but, i need to find out where i know the GuiBoi name from. it's not from fedora...
[13:41] <LjL> Gnu even
[13:42] <ikonia> I've logged his other nicks in BT
[13:42] <LjL> ah, that'll be a timesaver
[13:42] <ikonia> he uses other nicks as he genuinly doesn't think it's a bad thing if they are caught as they are not "him"
[13:44] <ikonia> the BT front end needs an update to allow "search marks only"
[13:44] <ikonia> LjL: found the nicks ?
[13:45] <LjL> ikonia: yes, and i've found others in my logs
[13:45] <ikonia> oh really
[13:45] <LjL> ikonia: Ujjwol for instance
[13:45] <ikonia> yeah, I noted him
[13:46] <LjL> ikonia: oh, then i didn't see everything you put in the BT i guess
[13:46] <ikonia> LjL: if you have any idea who the right person to take it to is, I'm all ears, I don't think -ops are the right guys, I'm talking to the ambasadors
[13:46] <LjL> ikonia: no, i'd only know to try -ops
[13:46] <ikonia> seeing if the "bad representation" could be taken forward rather than the one incident
[13:47] <LjL> ikonia: as Ujjwol, he spammed quite badly, too...
[13:47] <ikonia> yup
[13:48] <ikonia> that was the thing that first highlighted me to him and I traced him back to his other nicks
[13:48] <ikonia> but its ok as he's "Ujjwol" not Gnuboi
[13:48] <ikonia> it's ok if Ujjwol gets banned
[13:48] <ikonia> (apprantly)
[13:48] <LjL> ikonia: would freenode staff agree about that? i'm really not sure cloaks (whether project or unaffiliated) are intended as a means to have to hosts to ban evade from...
[13:49] <ikonia> LjL: sorry, exaplin that again ?
[13:49] <ikonia> LjL: didn't quite understand that
[13:49] <LjL> ikonia: does he have a cloak on gnuboi?
[13:50] <ikonia> LjL: I've not seen one as he swaps between 4 IP's and mibbet
[13:50] <LjL> ikonia: ah wonderful
[13:50] <LjL> ikonia: so it might not be a problem to him, but, if Ujjwol gets banned, then GnuBoi gets banned too - unless they consistently use different IPs
[13:51] <ikonia> LjL: same ip's
[13:51] <ikonia> apparantly they are his nicks and he has them registered
[13:51] <ikonia> but they are personas
[13:51] <ikonia> eg: one is used to "announce" or spam new info
[13:51] <LjL> ikonia: erm, ok, but if they're on the same IP and the same account, then i really can't see how he'd find it "ok" for one to be banned...
[13:51] <ikonia> one is used to secretly get information ??????
[13:51] <ikonia> LjL because he's a moron child
[13:52] <ikonia> he thinks people don't know it's the same guy
[13:52] <ikonia> he was shocked beyond belief whenI confronted him
[13:52] <ikonia> he couldn't understand how I had tracked him
[13:52] <LjL> ikonia: that's quite wishful thinking, when you /NICK on them...
[13:53] <LjL> anyway, you're right, stupidity has no limits so i shouldn't be surprised
[13:54] <ikonia> I think he's just new to "computers" and jumping on the open source bandwagon
[13:54] <ikonia> spent 10 minutes tyring to tell me how evil microsoft was, but couldn't explain why
[13:56] <LjL> ikonia: what did #f-ops tell you about the issue anyway? i assume, they they don't really have a clue who the namespace contact is?
[13:56] <ikonia> LjL: they don't know the process, and he's a pain in #fedora to
[13:56] <ikonia> there advice was just "ban him"
[13:57] <LjL> ikonia: they should know the process, a few of them have fedora cloaks...
[13:57] <ikonia> I'll ask in -ops to see if there is a more unified opinion in a bit
[13:57] <ikonia> infact I'll to it now
[14:03] <ikonia> LjL: thanks !
[14:22] <Myrtti> I hate firefox
[14:24] <Pici> What did it ever do to you?
[14:25] <LjL> i hate firefox too
[14:29] <Myrtti> I want to have epiphany type addressbar and ability to make my own search input boxes
[14:30] <LjL> Myrtti: konqueror!
[14:30] <Myrtti> LjL: pft.
[14:30] <Pici> w3m!
[14:44] <Myrtti> coconut curry ♥
[15:40] <genii> Good morning, afternoon, or evening :)
[15:42] <LjL> you always assume it's not night
[15:43] <genii> LjL: I'd class "evening" as night ... :)
[15:56] <ikonia> LjL: infomed staff ?
[15:56] <LjL> ikonia: yes
[15:56] <ikonia> ta
[16:54] <Pici> lalala
[16:58] <ikonia> @mark crusher asking for ubuntu ultimate support again
[16:58] <Pici> again?
[16:59] <ikonia> yes he's done it before a week or so ago
[16:59] <LjL> ikonia: thanks to canonical's very efficient trademarks enforcement dep ;)
[16:59] <ikonia> hence why I marked it
[16:59] <Pici> ikonia: Also, you should put #ubuntu there, otherwise it'll add the log from -ops to the bt.
[16:59] <ikonia> I thought I had, sorry
[17:14] <Flannel> Howdy Crusher, how can we help you?
[17:14] <Crusher> i mean is ubuntu n ultimate edition different ?
[17:15] <ikonia> it is not made by ubuntu
[17:15] <ikonia> Crusher: it is nothing to do with ubuntu
[17:15] <LjL> of course they're different
[17:15] <LjL> if they were the same, why there would be two of the same thing?
[17:15] <ikonia> Crusher: there are links on the ultimate edition website about support, they can help you
[17:16] <Crusher> oh
[17:16] <Flannel> Crusher: Or, you can install a properly supported version of Ubuntu
[17:16] <ikonia> Crusher: you where told that twice in #ubuntu from ubottu
[17:17] <Crusher> ikonia:actually i was thinking of upgrading my OS to intrepid ibex....i m totally wrong then
[17:17] <ikonia> yes
[17:17] <ikonia> I suggest you rad about the distro you've installed
[17:17] <ikonia> read
[17:17] <LjL> Crusher: upgrading will probably break everything.
[17:17] <LjL> if you want Intrepid, install it from scratch.
[17:17] <Crusher> LjL: oh
[17:17] <LjL> it can be downloaded from http://www.ubuntu.com/
[17:20] <ikonia> Crusher: anything else you need ?
[17:20] <Crusher> ikonia: yeah i m in dilemma
[17:20] <ikonia> what can we help you with ?
[17:22] <Crusher> ikonia: i got this edition installed from  a DVD which contains lots of programs initially....even i've installed many of 'em
[17:23] <LjL> Crusher: is your internet connection particularly slow?
[17:23] <Crusher> ikonia: i don't want to get into trouble of downloading all of them again.....but i also want to use intrepid
[17:23] <Crusher> ikonia: yeah
[17:24] <Crusher> ikonia: i m from Nepal........Institute of Engineering
[17:24] <ikonia> Crusher: maybe speak to your teachers about using a faster connection, but I'm afraid we can't help you with that
[17:25] <LjL> Crusher: well, that's up to you really... in any case, moving to intrepid will require a lot of downloading.
[17:26] <LjL> Crusher: try asking in #ubuntu-np, perhaps they can help you obtain an intrepid DVD
[17:26] <Crusher> LjL: thank u ......
[17:28] <LjL> Crusher: welcome. anything else?
[17:29] <Crusher> LjL:can u really give me some links where i can learn much about LINUX things?
[17:29] <ikonia> Crusher: just do some googling or ask in the channel suggested
[17:29] <Crusher> LjL: i don't want to get messed up again....in confusion
[17:29] <LjL> there are no magical links. but if you want some generic linux help, try ##linux
[17:29] <ikonia> those guys are local to you
[17:29] <Crusher> okay
[18:00] <LjL> Crusher, if you don't have anything else, please leave this channel
[18:01] <Crusher> LjL: i got it....
[18:02] <Crusher> http://en.wikipedia.org/wiki/Ubuntu_Ultimate
[18:02] <ikonia> do you know how to leave the channel ?
[18:03] <ikonia> Crusher: why are you showing us that ?
[18:03] <Crusher> ikonia: i mean i got the clear view why u guys don't regard it as a ubuntu version ?
[18:04] <ikonia> well thats great, so if there is nothing else you need from us, you can leave and go on with your day
[18:04] <Crusher> ikonia: why sud i live? i mean wot's wrong joining it?
[18:04] <Pici> !idle | Crusher
[18:05] <Crusher> okayyyyyyyyy
[18:05] <Crusher> got it
[18:05] <LjL> it took only... how many hours?
[18:06] <Pici> @mark crusher ultamate edition stuffs
[18:06] <ikonia> nice comment
[18:07] <Pici> I could have sworn it was spelled Ultamate (not Ultimate) at some point in time too.
[18:18] <LjL> !shipit
[18:19] <LjL> !shipit ~= s/Hardy (8.04)/Intrepid (8.10)/
[18:19] <LjL> really?
[18:19] <LjL> !no shipit is a service that sends free Ubuntu, Kubuntu and Edubuntu CDs. See http://shipit.ubuntu.com/ and http://shipit.kubuntu.org and http://shipit.edubuntu.org - Shipit will send Intrepid (8.10) CDs
[18:26] <Pici> Hrm, I thought I fixed that one.
[18:28] <LjL> Pici: they could very well have kept sending LTS CDs
[18:41] <vorian> 34
[18:41] <vorian> oops :)
[18:42] <jdong> vorian: riding big wheels? *ducks*
[18:43] <vorian> weeeee
[18:43] <vorian> yus!
[20:02] <Myrtti> *yawn*
[20:37] <Ursinha> Myrtti, you seem always bored...
[20:37] <Myrtti> no, just tired
[20:50] <Myrtti> LjL: thanks
[20:53] <LjL> Myrtti: pity i can't do the same in #debian and ##linux where he also posted it
[21:17] <Myrtti> LjL: well, having read the debian developer email list lately, I'm not surprised they'd drool openly at that picture
[21:26] <LjL> Myrtti: to be fair, on #debian he was just sternly told to "spam elsewhere"
[21:27] <LjL> they "lol"'d a bit on ##linux on the other hand


[08:40] <cjwatson> wgrant: Does my amendment to https://code.launchpad.net/~cjwatson/launchpad/delay-ppa-publication/+merge/269090 look OK?
[08:40] <cjwatson> wgrant: Also, want me to do your pending QA?
[08:40] <wgrant> cjwatson: Ah, if you could.
[08:41] <wgrant> Sorry, been distracted the last couple of days...
[08:41] <wgrant> That MP looks better now, thanks.
[08:42] <cjwatson> OK, thanks.
[08:52] <cjwatson> wgrant: I seem to get "URL not allowed" surprisingly often
[08:52] <cjwatson> e.g. http://lies.example.com/ resulted in that
[08:52] <cjwatson> When I'd have expected "DNS lookup failed"
[08:53] <wgrant> Hm.
[08:53] <cjwatson> I mean, it's not actually breaking AFAICS, just surprising.
[08:54] <wgrant> Yeah
[08:54] <wgrant> I guess it falls afoul of the IP address restrictions because it has none.
[08:56] <cjwatson> Ah, could be.
[08:56] <wgrant> I'll need to refactor the rules to remove the positive dst assertion, I think.
[08:56] <cjwatson> http://www.ubuntu.com/ also gave me "URL not allowed" but that's more understandable.
[08:56] <wgrant> Which is possible if they get split up, I think.
[08:56] <wgrant> Right, that is intended.
[08:57] <wgrant> I expected the DNS error to happen before the ACL check, TBH.
[08:57] <cjwatson> Trying to think of a way to provoke a different error without actually having to bother setting up my own endpoint.
[08:58] <wgrant> You can get connection errors by using a host that doesn't listen on HTTPS.
[08:58] <wgrant> Or HTTP.
[08:58] <cjwatson> Oh that's true
[08:58] <wgrant> Has to be port 80
[08:58] <wgrant> And HTTPS is dodgy because of httplib, so 80 is better to test.
[09:01] <cjwatson> wgrant: https://oops.canonical.com/?oopsid=OOPS-86856e3812ab2bada21cf3f23ab8f83b
[09:01] <cjwatson> Though apparently not a regression.
[09:01] <wgrant> Hrmph.
[09:01] <wgrant> Did you provoke a timeout?
[09:02] <wgrant> It indeed shouldn't OOPS.
[09:02] <cjwatson> (That's from trying my ADSL, riva.dynamic.greenend.org.uk, which doesn't listen on HTTP but also apparently doesn't actually reject it)
[09:02] <wgrant> Ah.
[09:02] <wgrant> Right.
[09:02] <cjwatson> Useful misconfigurations FTW
[09:03] <cjwatson> Anyway, qa-ok since that's a pre-existing bug
[09:03] <cjwatson> Shall I file a bug?
[09:04] <wgrant> Please do.
[09:05] <wgrant> cjwatson: https://code.launchpad.net/~wgrant/launchpad/bug-1489674/+merge/269480
[09:08] <cjwatson> wgrant: https://bugs.launchpad.net/launchpad/+bug/1489792
[09:08] <mup> Bug #1489792: WebhookClient.deliver crashes if the endpoint times out <fallout> <oops> <Launchpad itself:Triaged> <https://launchpad.net/bugs/1489792>
[09:08] <wgrant> Thanks
[09:09] <cjwatson> wgrant: Mystifying, why is to_person ever a team there, let alone a private one?
[09:09] <wgrant> cjwatson: If the team has an email address.
[09:09] <cjwatson> Oh, right.
[09:09] <cjwatson> And we don't need this in BaseMailer too?
[09:10] <wgrant> BaseMailer already seems to touch other attributes without rSP
[09:10] <cjwatson> It does, but I wonder if it has hitherto only been called from scripts
[09:10] <wgrant> So I thought it must have done it globally somewhere else.
[09:10] <wgrant> That is possible indeed.
[09:12] <cjwatson> One of these days the word order in ZopelessDatabaseLayer vs. DatabaseFunctionalLayer will stop confusing me.  Or I'll crack and rename one of them.
[09:12] <wgrant> ZopelessDatabaseLayer needs to be renamed for two reason.
[09:12] <cjwatson> wgrant: Anyway, r=me but I should check whether any of my BaseMailer conversions are potentially affected.
[09:16] <cjwatson> I think team-mail for example can go wrong if you renew a team membership and one of the admins of the team is an inaccessible private team.
[09:16] <wgrant> Yep
[09:16] <cjwatson> get_recipients does rSP but BaseMailer doesn't.
[09:17] <cjwatson> Can you think of any reason not to plaster rSP over all recipient attribute accesses in mailers?
[09:18] <cjwatson> With BaseMailer, it's always a separate mail to each recipient so there should be no leakage.
[09:22] <wgrant> Indeed.
[09:22] <wgrant> Ideally you could do it higher.
[09:28] <cjwatson> Maybe in get_recipients?
[09:31] <wgrant> That might not help with eg. the rationale calculation in TeamMembershipMailer.
[09:32] <cjwatson> Which bit of it?
[09:33] <wgrant> It unusually grabbed the displayname directly for something.
[09:33] <wgrant> One of the templates had %%(blahblah)s because it was formatting the format stirng.
[09:34] <cjwatson> forExpiringMembership does admin.unique_displayname, if that's what you're thinking of
[09:35] <cjwatson> The stuff in TeamRecipientReason is fine because it always refers directly to the member or the team being operated on, rather than other members/admins of the same team; and when performing one of these operations you always have access to both the member and the team at hand.
[09:35] <cjwatson> team.teamowner is used, but that's constrained to be a public person.
[09:36] <wgrant> Eeh.
[09:36] <wgrant> Indeed, probably safe.
[09:36] <cjwatson> It's true that forExpiringMembership would need its own handling as well.
[09:37] <cjwatson> But it actually needs some special handling no matter what, because it tells you the names of the team's admins.  If you're in the bizarre situation of being a member of a team with some admins you aren't allowed to know about, the expiring membership mail shouldn't tell you
[09:38] <cjwatson> (Is this really a possible setup?)


[00:26] <ahayzen> AsciiWolf, i have a PPA with an update prepared, just reviewing the diff with others :-)
[07:33] <ginggs> doko mwhudson xnox: i'm trying numpy in https://bileto.ubuntu.com/#/ticket/4337
[08:53] <mwhudson> ginggs: oh, i just cheated and reduced the tolerance
[08:53] <mwhudson> ginggs: if what you're doing there works would be nice to remove my hack
[08:53] <mwhudson> uh increased the tolerance
[08:53] <mwhudson> whatever :)
[09:01] <ginggs> mwhudson: oh i didn't see that, I guess I can still upload meshio with your hack removed to ci-train-ppa-service/ubuntu/4337 to confirm
[09:02] <mwhudson> ginggs: would be great
[09:02] <mwhudson> come onnnnnnnnnnn autopkgtest.u.c tell me whether my retry of the meshio tests passed
[09:07] <Laney> mwhudson: someone should totally write a CLI tool to look up results directly :>
[09:07] <Laney> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/?format=json&prefix=hirsute/s390x/p/python-meshio
[09:09] <mwhudson> ah nice looks like it did work
[09:09] <mwhudson> Laney: is that url just something one has to know?
[09:09] <Laney> would have been better for such a tool if the URLs were the other way around
[09:09] <Laney> then you could prefix hirsute/p/python-meshio
[09:09] <Laney> um well it's the swift API
[09:10] <Laney> the same thing that the web frontend uses
[09:10] <Laney> no reason there couldn't be other clients to it as well
[09:12] <mwhudson> i guess i mean the AUTH_77e2ada1e7a84929a74ba3b87153c0ac bit
[09:12] <Laney> ah
[09:12] <Laney> that's like our username I guess
[09:13] <Laney> so yes, basically it's something you need to know one way or another
[09:13] <ginggs> mwhudson: same as here https://wiki.ubuntu.com/ProposedMigration#Testing_against_a_PPA
[09:13] <mwhudson> ginggs: oh right, i have seen that
[09:13] <mwhudson> i can certainly see why a cli client would be nice
[09:13] <Laney> the administrators of the cloud set up an account for autopkgtest to use
[09:14] <Laney> and we're allowed to upload stuff into it, everything ends up with that prefix
[09:16] <AsciiWolf> ahayzen, cool, great work! :-)
[10:10] <sil2100> teward, Eickmeyer: so I checked the agordejo package just now and the debian/watch file is still wrong
[10:10] <sil2100> teward, Eickmeyer: but I'll fix that, re-upload and approve
[10:11] <sil2100> Please be sure to always check with `uscan --report -v` if everything's working as it should
[10:17] -queuebot:#ubuntu-release- New source: agordejo (hirsute-proposed/primary) [0.1.1-0ubuntu1]
[10:20] <sil2100> Done
[10:21] -queuebot:#ubuntu-release- New: rejected agordejo [source] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:21] -queuebot:#ubuntu-release- New: accepted agordejo [source] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:25] -queuebot:#ubuntu-release- New binary: agordejo [amd64] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:25] -queuebot:#ubuntu-release- New binary: agordejo [s390x] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:26] -queuebot:#ubuntu-release- New binary: agordejo [ppc64el] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:31] -queuebot:#ubuntu-release- New binary: agordejo [armhf] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:35] -queuebot:#ubuntu-release- New binary: agordejo [arm64] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: agordejo [riscv64] (hirsute-proposed/universe) [0.1.1-0ubuntu1] (no packageset)
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [amd64] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [armhf] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [riscv64] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [arm64] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [s390x] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- New: accepted agordejo [ppc64el] (hirsute-proposed) [0.1.1-0ubuntu1]
[10:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (xenial-proposed) [2.02~beta2-36ubuntu3.29]
[10:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (xenial-proposed) [2.02~beta2-36ubuntu3.29]
[11:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.20]
[11:00] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.20]
[11:20] -queuebot:#ubuntu-release- Packageset: Added language-pack-kab to langpack in hirsute
[11:20] -queuebot:#ubuntu-release- Packageset: Added language-pack-kab-base to langpack in hirsute
[11:35] -queuebot:#ubuntu-release- Packageset: Added language-pack-gnome-kab to langpack in hirsute
[11:35] -queuebot:#ubuntu-release- Packageset: Added language-pack-gnome-kab-base to langpack in hirsute
[14:15] <cpaelzer> is there a ubuntu-release member around to look at (and if necessary discuss) https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/394114 ?
[14:45] <sil2100> cpaelzer: looking
[14:51] <LocutusOfBorg> haskell fixedd
[14:51] <LocutusOfBorg> mwhudson, <3
[15:01] <doko> juliank, Laney: could we shift the amount of armhf/arm64 autopkg testers towards armhf for a while again?
[15:02] <juliank> I should have stored the extra worker as an image
[15:02] <juliank> We can but it's 30 mins of work
[15:03] -queuebot:#ubuntu-release- New binary: s390-tools [s390x] (hirsute-proposed/main) [2.15.1-0ubuntu2] (core)
[15:03] <juliank> + node setup time to build lxd containers for all releases
[15:03] <juliank> like last time
[15:03] <juliank> this is why I felt it would be nicer if we build lxd worker images and like did dynamic lxd worker provisioning
[15:06] <Laney>  it's too manual, I'm not going to get into the habit of shuffling those all the time
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [amd64] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [armhf] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [riscv64] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [amd64] (hirsute-proposed) [0.0.7+ds-2]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [armhf] (hirsute-proposed) [0.0.7+ds-2]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [riscv64] (hirsute-proposed) [0.0.7+ds-2]
[15:08] -queuebot:#ubuntu-release- New: accepted ktuberling [amd64] (hirsute-proposed) [4:20.08.3-2]
[15:08] <Laney> they should also be monitored for health since they seize up from time to time, but it's all stuff we don't have :(
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [arm64] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [s390x] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [ppc64el] (hirsute-proposed) [0.0.7+ds-2]
[15:08] -queuebot:#ubuntu-release- New: accepted s390-tools [s390x] (hirsute-proposed) [2.15.1-0ubuntu2]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [ppc64el] (hirsute-proposed) [0.0.7+ds-1]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [s390x] (hirsute-proposed) [0.0.7+ds-2]
[15:08] -queuebot:#ubuntu-release- New: accepted ggd-utils [arm64] (hirsute-proposed) [0.0.7+ds-2]
[15:08] <xnox> AA s390-tools has new subpackages for the the opensource library to talk to key management
[15:09] <xnox> previously that was only possible using a proprietary java app, packaged as .exe, downloadable from ibm.com, from hidden urls, with a cryptic UELA. So very useful.
[15:15] <Eickmeyer[m]> sil2100: Yeah, I kinda stink at watch files, especially if they're not github or something easy. I also stink at regex, which is why I had no idea how to fix, so thanks. :)
[15:22] <sil2100> Eickmeyer[m]: hah, that's fine, I don't like hacking on debian/watch files as well ;p
[15:22] <sil2100> cpaelzer: merged o/
[15:30] -queuebot:#ubuntu-release- Unapproved: libreoffice (groovy-proposed/main) [1:7.0.2-0ubuntu1 => 1:7.0.3-0ubuntu<IP_ADDRESS>] (ubuntu-desktop) (sync)
[15:34] -queuebot:#ubuntu-release- Unapproved: u-boot (focal-proposed/main) [2019.07+dfsg-1ubuntu6 => 2020.10+dfsg-1ubuntu0~20.04.1] (core)
[15:37] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (xenial-proposed/main) [4.15.0-1088.101~16.04.1] (kernel)
[15:38] -queuebot:#ubuntu-release- Unapproved: u-boot (bionic-proposed/main) [2019.07+dfsg-1ubuntu4~18.04.1 => 2020.10+dfsg-1ubuntu0~18.04.1] (core)
[15:47] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (xenial-proposed) [4.15.0-1088.101~16.04.1]
[15:57]  * Laney DoSes the NEW queue
[15:57] -queuebot:#ubuntu-release- New source: oem-stella.cmit-butterfree-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:57] -queuebot:#ubuntu-release- New source: oem-stella.cmit-rhyhorn-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:57] -queuebot:#ubuntu-release- New source: oem-stella.cmit-ivysaur-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:57] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-baker-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-baldhere-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-bale-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-4.15 [amd64] (bionic-proposed/universe) [4.15.0-1088.101] (no packageset)
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.newell-adalbrechta-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.newell-cadyna-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.bachman-banner-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:58] -queuebot:#ubuntu-release- New source: oem-sutton.newell-adam-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.newell-cameo-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.newell-cara-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-addison-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-bailee-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-banning-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-camille-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.newell-candice-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-adken-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-camellia-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.newell-caralyn-meta (focal-proposed/primary) [20.04~ubuntu1]
[15:59] -queuebot:#ubuntu-release- New source: oem-sutton.simon-baird-meta (focal-proposed/primary) [20.04~ubuntu1]
[16:00] <Laney> I need to comment on all the LP bugs, will write an API script to do that in a bit
[16:11] <vorlon> so how many times today is someone going to do a mass-giveback of haskell ftbfs out of order?
[16:13] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-4.15 [amd64] (bionic-proposed) [4.15.0-1088.101]
[16:15] <LocutusOfBorg> vorlon, I'm giving them back with the correct order... maybe I have to put some sleep before one level and the other, but some level are not waiting for anything anymore
[16:15] <LocutusOfBorg> this is why I did a full pass of retries without waiting
[16:15] <vorlon> LocutusOfBorg: I've gotten two batches of emails this morning showing build failures for the lot
[16:16] <LocutusOfBorg> I'm rebuilding *now* that gold is fixed
[16:16] <LocutusOfBorg> not this morning ;)
[16:16] <vorlon> LocutusOfBorg: my morning not yours :)
[16:16] <LocutusOfBorg> but this morning was discussed on -devel
[16:16] <LocutusOfBorg> oooooh :D
[16:16] <LocutusOfBorg> because some have been retried ~12h ago and some were found to be succeeding now
[16:17] <LocutusOfBorg> btw I don't think the ghc no change rebuild was useful to be honest
[16:17] <vorlon> it is good to see light at the end of the tunnel, anyway
[16:20] <LocutusOfBorg> yep but slow armhf will make it uncandidate for another week
[16:20] <LocutusOfBorg> I would just kick it out to be honest...
[16:22] <vorlon> slow armhf for what packages?
[16:22] <vorlon> because https://people.canonical.com/~ubuntu-archive/transitions/html/ghc.html doesn't show armhf blocking
[16:22] <LocutusOfBorg> ghc itself
[16:22] -queuebot:#ubuntu-release- Unapproved: ec2-instance-connect (bionic-proposed/universe) [1.1.12+dfsg1-0ubuntu3~18.04.0 => 1.1.12+dfsg1-0ubuntu3~18.04.1] (no packageset)
[16:22] -queuebot:#ubuntu-release- Unapproved: ec2-instance-connect (xenial-proposed/universe) [1.1.12+dfsg1-0ubuntu3~16.04.0 => 1.1.12+dfsg1-0ubuntu3~16.04.1] (no packageset)
[16:22] <vorlon> ah
[16:22] <LocutusOfBorg> :)
[16:23] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (focal-proposed) [2020.10+dfsg-1ubuntu0~20.04.1]
[16:23] -queuebot:#ubuntu-release- Unapproved: ec2-instance-connect (groovy-proposed/main) [1.1.12+dfsg1-0ubuntu3 => 1.1.12+dfsg1-0ubuntu<IP_ADDRESS>] (core)
[16:23] -queuebot:#ubuntu-release- Unapproved: ec2-instance-connect (focal-proposed/main) [1.1.12+dfsg1-0ubuntu3 => 1.1.12+dfsg1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:32] -queuebot:#ubuntu-release- New binary: u-boot [amd64] (focal-proposed/main) [2020.10+dfsg-1ubuntu0~20.04.1] (core)
[16:42] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (bionic-proposed) [2020.10+dfsg-1ubuntu0~18.04.1]
[16:48] -queuebot:#ubuntu-release- New binary: u-boot [amd64] (bionic-proposed/main) [2020.10+dfsg-1ubuntu0~18.04.1] (core)
[16:49] -queuebot:#ubuntu-release- New binary: u-boot [riscv64] (focal-proposed/main) [2020.10+dfsg-1ubuntu0~20.04.1] (core)
[17:26] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [amd64] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [s390x] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [armhf] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [arm64] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: u-boot [arm64] (bionic-proposed/main) [2020.10+dfsg-1ubuntu0~18.04.1] (core)
[17:40] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [riscv64] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:52] -queuebot:#ubuntu-release- Unapproved: ruby2.5 (bionic-proposed/main) [2.5.1-1ubuntu1.6 => 2.5.1-1ubuntu1.7] (kubuntu, ubuntu-desktop, ubuntu-server)
[17:54] -queuebot:#ubuntu-release- New binary: prometheus-process-exporter [ppc64el] (hirsute-proposed/universe) [0.7.5-1] (no packageset)
[17:55] <vorlon> ok that's now the THIRD full set of ppc64el build failure logs I've gotten this morning because of someone batch-retrying all the haskell builds
[17:55] <vorlon> could whoever please not, it actually slows down the rebuilds due to the will-fail builds competing for buildd time with the ones that will succeed.  I'm happy to handle the retries in order as per https://people.canonical.com/~ubuntu-archive/transitions/html/ghc.html
[17:58] <vorlon> LocutusOfBorg: ^^ ?
[18:03] <vorlon> and this ghc changes ABI on amd64? :/
[18:05] <cjwatson> Also if you're doing batch rebuilds then you'll need to get them finished by end of tomorrow or wait for Sunday ...
[18:05] <cjwatson> (Due to the Boston datacentre work)
[18:06] <doko> the one I uploaded? that was a no-change rebuild to build with fixed gold on ppc64el
[18:20] <mwhudson> no rebuild of ghc was required for that
[18:20] <mwhudson> aiui anyway
[18:20] <Laney> we can remove that rebuild and restore the previous one, then retry
[18:20] <Laney> ?
[18:20] <mwhudson> i think so, yes
[18:20] <mwhudson> especially if the "no change" rebuild changes abi
[18:23] <doko> why does it change the ABI?
[18:23] <mwhudson> ARGH WHY IS NUMPY STILL IN PROPOSED
[18:23] <Laney> I don't know, but GHC isn't known for its stable ABIs exactly
[18:26] <Laney> I have to go, can someone arrange the ghc thing?
[18:30] <doko> mwhudson: because synced packages are adding triggers again :-/
[18:30] <mwhudson> doko: ah
[18:30] <mwhudson> i wonder if disabling sync is a good idea
[18:31] <mwhudson> of course we're going to lose all non-intel builders soon anyway
[18:31] <doko> mwhudson: did you retry those?
[18:31] <mwhudson> doko: no
[18:32] <mwhudson> doko: i think they'll pass with all-proposed=1
[18:32] <doko> ok, doing that
[18:33] <vorlon> mwhudson, Laney: I've already triggered rebuilds for the handful of packages affected on amd64, I think we should run with it
[18:35] <Laney> aren't they going to skew with the other arches?
[18:36] <Laney> or are we getting helpful uninstallability for some reason?
[18:36] <vorlon> skew in what sense?
[18:36] <doko> vorlon: the ghc build only finished on amd64 and ppc64el ...
[18:36] <Laney> pick up old ghc
[18:36] <vorlon> ah. lovely.
[18:36] <Laney> get ABIs from that
[18:36] <vorlon> then yeah
[18:36] <Laney> need a second rebuild...
[18:36] <vorlon> back it all out?
[18:36] <Laney> I would
[18:36] <vorlon> ok, doing
[18:36] <Laney> and just gb on ppc64el
[18:37] <doko> so removing the ppc64el binaries, and then copying to the same series to rebuild?
[18:38] <vorlon> removing ghc which we've asserted didn't need a rebuild; removing the 7 packages I had uploaded for the ABI change; restoring previous versions to -proposed for all 8 packages
[18:52] <mwhudson> vorlon: thanks
[18:52] <mwhudson> are haskell packages building on ppc64el now?
[18:53] <doko> queues are empty, I think the old packages need publishing first
[18:53] <vorlon> mwhudson: prior to the ghc revert, yes; waiting to see what happens post revert
[19:18] <LocutusOfBorg> vorlon, I'm not doing rebuilds
[19:18] <LocutusOfBorg> I was afk :)
[19:19] <LocutusOfBorg> I might had some old script running, but I'm not sure, and when I came back they were all finished
[19:21] <LocutusOfBorg> vorlon, please, restore libguestfs/1:1.42.0-11ubuntu1 on hirsute-proposed, wait for ocaml to publish, copy back 1:1.42.0-11ubuntu2 in proposed please?
[19:21] <LocutusOfBorg> so we disentangle ocaml and perl and everything?
[19:21] <cpaelzer> thanks sil2100
[19:31] <LocutusOfBorg> bdmurray, hello, do you have any vim news? the fact that builds only on riscv64 (due to disabled tests) is making riscv64 sad (e.g libguestfs)
[19:32] <bdmurray> I'm poking around with it now but am not getting anywhere quickly
[19:32] <LocutusOfBorg> ack, I hope some ubuntu-archive will then copy back the old libguestfs in proposed (and the old vim) to let some transition end
[19:33] <bdmurray> the old vim ftbfs in hirsute too
[19:38] <LocutusOfBorg> yes, but it is installable :)
[19:43] <doko> who is giving back vim/amd64 and hoping that the timeout gets solved? 10 expected, needed 18
[19:47] <rbalint> bdmurray, i've just updated LP: #1903849
[19:49] <rbalint> let me try a simple patch
[19:50] <doko> rbalint: disable it?
[19:50] <rbalint> doko, no, fix mouse in the test
[19:50] <rbalint> doko, if it was not a joke :-)
[19:55]  * doko throws some rotten cheese to rbalint ;p
[19:55] <rbalint> tasty response :-)
[19:57] <doko> ok, so just increasing the timeout for the failing amd64 test
[19:59] <vorlon> LocutusOfBorg: not doing rebuilds> ack, so who knows where those are coming from :/
[20:00] <vorlon> mwhudson: confirmed that previously ftbfs ppc64el packages are now building successfully after the ghc rollback; though I haven't checked which of these were actually affected by the bug, vs build-depending on packages that were
[20:01] <mwhudson> vorlon: cool, i did check that my linker fix fixed the package you mentioned in the debian bug report so at least 1 package is fixed by this!
[20:04] <LocutusOfBorg> mwhudson, I also gave back llvm-toolchain-snapshot on ppc64el in debian and ubuntu
[20:04] <LocutusOfBorg> maybe the fix is the same?
[20:04] <LocutusOfBorg> vorlon, any help for ocaml?
[20:05] <vorlon> LocutusOfBorg: looking now.  is libguestfs the only blocker?
[20:05] <LocutusOfBorg> yep
[20:05] <doko> snapshot is the not relevant for the release pocket
[20:05] <rbalint> doko, seems ok, locally, uploading
[20:05] <LocutusOfBorg> doko, is relevant to understand if the fix works or not
[20:05] <doko> rbalint: wait!
[20:06] <rbalint> doko,?
[20:06]  * rbalint waiting
[20:06] <vorlon> LocutusOfBorg: revert dance done
[20:06] <LocutusOfBorg> thanks
[20:06] <doko> rbalint: did you fix the timeout for the amd64 test?
[20:07] <rbalint> doko, no, but it does not fail in the timeout now, just in the test missing mouse support
[20:07] <doko> rbalint: that's what I have: https://paste.ubuntu.com/p/Rhv42PGFpj/
[20:07] <rbalint> doko, you can check my diff https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages
[20:08] <rbalint> mine is basically the same, without the timeout
[20:08] <doko> ok, that's the same fix, uploading
[20:10] <rbalint> doko how come i wrote on #ubuntu-devel that i'm looking into vim and you already looked into it in parallel?
[20:10] <rbalint> https://wiki.ubuntu.com/PlusOneMaintenanceTeam lists #ubuntu-devel for coordination
[20:12] <doko> rbalint: we should change that. probably should happen here like all other transition stuff
[20:18] <vorlon> doko, rbalint: agreed, I think this is the better channel for coordination
[20:20] <ginggs> mwhudson: so building numpy without  -std=c99 seems to have worked, https://bileto.ubuntu.com/excuses/4337/hirsute.html shows python-meshio/4.1.0-2 autokpkgtests passed on s390x where numpy/1:1.19.4-1 did not -- shall I publish, or wait for 1:1.19.4-1 to migrate first?
[20:20] <rbalint> @pilot in
[20:21] <rbalint> vorlon, doko ok, but then piloting should also be here
[20:23] <rbalint> vorlon, doko i've updated the wiki to use #ubuntu-release, but kept #ubuntu-devel for piloting
[20:25] <LocutusOfBorg> ginggs, publishing bileto reset autopkgtests
[20:26] <ginggs> LocutusOfBorg: that's why i asked
[20:32] <mwhudson> ginggs: yeah let's get what's there to migrate first
[20:34] <LocutusOfBorg> mwhudson, a test failed
[20:34] <LocutusOfBorg> but was already retried
[20:34] <mwhudson> lots of things fail because pandas and numpy are both in proposed still
[20:35] <mwhudson> so at a minimum anything that uses both needs to be retried
[20:36] <mwhudson> oh looks like the retries have succeeded already
[20:36]  * mwhudson crosses fingers
[20:36] <doko> same for scipy
[20:38] <mwhudson> yeah i was too lazy to retry all the scipy tests with numpy as a trigger / all-proposed=1
[20:38] <mwhudson> because i thought numpy was about to migrate :/
[20:39] <rbalint> vorlon, could you please merge https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/394123
[20:41] <rbalint> vorlon, and push back ruby-entypo-rails to -proposed? it will need newer ruby-defaults due to ruby-rubygems
[20:41] <vorlon> +# passed onece as a fluke
[20:41] <vorlon> rbalint: ^^ ?
[20:43] <rbalint> vorlon, thanks, fixed
[20:45] <doko> rbalint, bdmurray: looks like both the timeout and mouse issues are fixed in vim
[20:52] <LocutusOfBorg> vorlon, what about kicking fsl out? Updating fsl introduces new bugs: #936564, #966112.
[20:52] <LocutusOfBorg> ftbfs, blocking another transition
[20:52] <vorlon> LocutusOfBorg: so you mean kick it out of release because it's blocking a transition?
[20:52] <vorlon> looks ok to me
[20:52] <LocutusOfBorg> vorlon, I mean, its out from debian testing and needs sourceful fixes
[20:53] <LocutusOfBorg> vorlon, its a sad story
[20:53] <LocutusOfBorg> related to a sad bug https://bugs.debian.org/968730
[20:53] <LocutusOfBorg> basically they renamed a library without changing soname... so its broken at runtime now :/
[20:54] <vorlon> heh
[20:54] <vorlon> well job
[20:54] <LocutusOfBorg> I did no change rebuild stuff to "unbreak them at runtime"
[20:54] <vorlon> fsl removed
[20:54] <LocutusOfBorg> :/
[20:54] <LocutusOfBorg> thanks
[20:54] <vorlon> rbalint: I read 'ruby-entypo-rails' as 'ruby-entrails'
[20:55] <LocutusOfBorg> so at least now with my rebuilds the archive is again consistent, hopefully we will have a sourceful fix
[20:55] <vorlon> LocutusOfBorg: well, yuck - I would make the maintainer fix the package name before doing any rebuilds :)
[20:56] <LocutusOfBorg> vorlon, all itk4 reverse dependencies weren't linking anymore
[20:56] <LocutusOfBorg> and it was blocking 2/3 transitions
[20:56] <vorlon> rbalint: I'm trying to understand the ruby-entypo-rails situation - do you want me to roll back to 3.0.0-2 or remove it altogether?  also why did 3.0.0-3 previously pass in the release pocket and then regress?
[20:57] <vorlon> LocutusOfBorg: 0-day NMU then :)
[20:57] <LocutusOfBorg> lol true, but I don't want to change soname, trigger a transition, package split, go binNEW for a package I don't really care about, and the team is meh
[20:58] <vorlon> rbalint: ... because the autopkgtest run for ruby-entrails used the rails from -proposed, bah. ok
[20:58] <bdmurray> doko: fixed where?
[20:58] <LocutusOfBorg> btw the new release vorlon has the fix for cmake, and the wrong library name, but needs a transition
[20:58] <doko> see changes emails
[20:58] <LocutusOfBorg> so I hope before hirsute it will self heal
[20:59] <LocutusOfBorg> (dcmtk was the entangled transition, via plastimatch)
[21:00] <LocutusOfBorg> vorlon, isn't it better to also remove from proposed pocket? so it gets autosyncd
[21:01] <vorlon> LocutusOfBorg: are the changes from 5.0.8-6ubuntu1 upstreamed in Debian?
[21:02] <vorlon> LocutusOfBorg: they aren't in the distro; so I wouldn't be inclined to remove it from -proposed before we know that's fixed?
[21:02] <LocutusOfBorg> not needed anymore IIRC
[21:02] <vorlon> python2 instead of python is absolutely still needed
[21:02] <vorlon> in Ubuntu
[21:02] <LocutusOfBorg> oh wait, its one of the two rc bugs?
[21:02] <vorlon> yeah
[21:02] <LocutusOfBorg> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936564
[21:03] <LocutusOfBorg> ok let me commit on git the change if this is ok
[21:11] <LocutusOfBorg> vorlon, https://salsa.debian.org/neurodebian-team/fsl/-/commit/c1febf62b17d39a9d885aa679475dcd4292a980f
[21:37] -queuebot:#ubuntu-release- Unapproved: iptables (groovy-proposed/main) [1.8.5-3ubuntu<IP_ADDRESS> => 1.8.5-3ubuntu<IP_ADDRESS>] (core, i386-whitelist) (sync)
[21:48] <vorlon> LocutusOfBorg: cheers
[22:25] <mwhudson> ok i think numpy will migrate on the next run
[22:32] <bdmurray> How can I get whoopsie out of -proposed? The indicator sesion failure is unrelated to it.
[23:21] -queuebot:#ubuntu-release- New binary: node-arg [amd64] (hirsute-proposed/universe) [5.0.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-unicode-script [amd64] (hirsute-proposed/universe) [0.5.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-unicode-script [ppc64el] (hirsute-proposed/universe) [0.5.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-unicode-script [arm64] (hirsute-proposed/universe) [0.5.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-unicode-script [s390x] (hirsute-proposed/universe) [0.5.2-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-unicode-script [armhf] (hirsute-proposed/universe) [0.5.2-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New: accepted rust-unicode-script [amd64] (hirsute-proposed) [0.5.2-1]
[23:26] -queuebot:#ubuntu-release- New: accepted rust-unicode-script [armhf] (hirsute-proposed) [0.5.2-1]
[23:26] -queuebot:#ubuntu-release- New: accepted rust-unicode-script [arm64] (hirsute-proposed) [0.5.2-1]
[23:26] -queuebot:#ubuntu-release- New: accepted rust-unicode-script [s390x] (hirsute-proposed) [0.5.2-1]
[23:26] -queuebot:#ubuntu-release- New: accepted node-arg [amd64] (hirsute-proposed) [5.0.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [arm64] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [ppc64el] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [s390x] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [amd64] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [riscv64] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [armhf] (hirsute-proposed) [0.7.5-1]
[23:26] -queuebot:#ubuntu-release- New: accepted rust-unicode-script [ppc64el] (hirsute-proposed) [0.5.2-1]
[23:58] -queuebot:#ubuntu-release- New binary: linux-signed-gke-5.4 [amd64] (bionic-proposed/main) [5.4.0-1030.32~18.04.1] (no packageset)
[23:59] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (hirsute-proposed/main) [5.8.0-30.32+21.04.2+1] (core, kernel)
[23:59] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (hirsute-proposed/main) [5.8.0-30.32+21.04.2+1] (core, kernel)
[23:59] -queuebot:#ubuntu-release- New binary: linux-signed-oracle-5.4 [amd64] (bionic-proposed/main) [5.4.0-1030.32~18.04.1] (no packageset)


[08:44] <zequence> micahg: Oh
[08:44] <zequence> Cool
[10:10] <sakrecoer> hey
[10:10] <sakrecoer> do ubuntu ever organise meetings in physical realm?
[10:11] <sakrecoer> there is this http://ubuntu.meetup.com/ thing... but i can't figure out to what extend it is pushed by users on a local level..
[10:12] <sakrecoer> or wether its international events?
[12:38] <zequence> sakrecoer_Z: I haven't seen that before
[15:41] <zequence> DebConf videos http://meetings-archive.debian.net/pub/debian-meetings/2015/debconf15/