| -queuebot:#ubuntu-release- New binary: pyrit [arm64] (focal-proposed/universe) [0.5.1+git20180801-2] (no packageset) | 00:01 | |
| -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:03 | |
| -queuebot:#ubuntu-release- New binary: vmfs6-tools [arm64] (eoan-backports/universe) [0.1.0-3~ubuntu19.10.1] (no packageset) | 00:05 | |
| -queuebot:#ubuntu-release- New binary: vmfs6-tools [armhf] (eoan-backports/universe) [0.1.0-3~ubuntu19.10.1] (no packageset) | 00:06 | |
| 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? | 00:35 |
|---|---|---|
| * 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? | 01:53 | |
| -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) | 02: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:19 | |
| -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:20 | |
| -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:21 | |
| -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) | 05:22 | |
| ginggs | tarzeau: you should add a link to debian bug #919786 in your colmap ppc64el removal bug | 07:34 |
| ubot5 | Debian bug 919786 in ftp.debian.org "RM: ceres-solver [arm64 ppc64el] -- ROM; newer release FTBFS on arm64 and ppc64el" [Normal,Open] http://bugs.debian.org/919786 | 07:34 |
| tarzeau | ginggs: i agree | 07:37 |
| sil2100 | jibel: hey! Are you also able to reproduce LP: #1861912 ? | 08:56 |
| ubot5 | Launchpad bug 1861912 in ubiquity (Ubuntu) "file system creation in partition failed in auto-resize install 18.04.4" [Critical,Confirmed] https://launchpad.net/bugs/1861912 | 08:56 |
| jibel | sil2100, on it, I didn't try 32bit builds | 08:58 |
| === andrewc is now known as Guest2175 | ||
| 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? ^ | 08:59 |
| jibel | sil2100, first try, cannot resize "Invalid argument". I'll reformat the machine and try again | 09:14 |
| sil2100 | darn | 09:18 |
| 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:24 |
| sil2100 | It will be terrible if we'll have to re-spin and re-test | 09:25 |
| 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:26 |
| 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:27 |
| 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:28 |
| * sil2100 needs to AFK for a bit | 09:29 | |
| juliank | Question is, did it create the partition or not? | 09:29 |
| juliank | Partition 5 sounds like an extended one? | 09:30 |
| juliank | For that we do need a syslog I guess | 09:31 |
| 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:32 |
| 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:33 |
| juliank | It's trying to installing to sdb | 09:34 |
| juliank | And then it fails formatting sdb5 because sdb5 is mounted | 09:35 |
| juliank | There was no sdb5 prior to install start | 09:35 |
| 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:36 |
| juliank | although it should not have had a FS on it | 09:37 |
| 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 1965031424-256060162047 254095130624 logical ext4 /dev/sdb5 | 09:38 |
| juliank | So it's not a problem of creating partitions | 09:39 |
| 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:40 |
| juliank | I don't see sdb5 being mounted in the kernel log, though | 09:41 |
| 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:44 |
| juliank | mwhudson: It did not resize sdb1 at all, there was enough space left | 09:45 |
| 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:46 |
| 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:47 |
| juliank | Certainly the guided options want to install on sda they say | 09:48 |
| 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:49 |
| juliank | at least that's what it says you did | 09:50 |
| 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:51 |
| 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:52 |
| juliank | I guess that's a suboption of install alongside? | 09:53 |
| 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:02 |
| juliank | Of course, mwhudson's log may be misleading and the original bug report might be different | 10:03 |
| 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:10 |
| juliank | Partman wrongly, instead of resizing partitions on your SSD, tries to install into the "free" space of your USB stick | 10:11 |
| 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:12 |
| juliank | Yes, but sda is fully filled up | 10:13 |
| juliank | sdb has free space: 254096269312 | 10:14 |
| juliank | sda free space: 1073152 | 10:15 |
| juliank | Not sure what the units are | 10:15 |
| juliank | Seem like bytes | 10:16 |
| juliank | So sdb has 254 GB contiguous free space | 10:17 |
| juliank | sda only 1MB | 10:17 |
| juliank | Let me reboot into my USB stick | 10:19 |
| juliank | I don't get such options because it does not recognize my FDE setup | 10:26 |
| juliank | I should try forwarding the USB stick to a VM | 10:27 |
| -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:34 | |
| -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:57 | |
| -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] | 10:58 | |
| -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:04 | |
| -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-440 [amd64] (bionic-proposed) [440.44-0ubuntu0.18.04.1] | 11:07 | |
| -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-440 [i386] (bionic-proposed) [440.44-0ubuntu0.18.04.1] | 11:07 | |
| juliank | It does not recognize the installation in my VM either | 11:14 |
| juliank | oh fun | 11: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:14 |
| 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:16 |
| 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:21 |
| jibel | and the bug likely exists in previous point releases | 12:22 |
| 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:23 |
| jibel | IDK, there is not enough information in the bug report. | 12:25 |
| 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:26 |
| sil2100 | Let's try to get that info then, but until we know more I am not treating this as a blocker | 12:27 |
| sil2100 | Per our earlier discussions with jibel | 12:29 |
| 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:35 |
| 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:36 |
| juliank | I'm going to install this once more | 12:38 |
| 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:39 |
| 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:40 |
| sil2100 | coreycb: please remember that bionic-updates is 'frozen' until we're done with 18.04.4! | 12:41 |
| coreycb | sil2100: ah right, ok thanks for the reminder | 12:42 |
| 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:57 |
| 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? | 12:59 |
| 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:19 |
| ubot5 | Ubuntu bug 1862017 in rdkit (Ubuntu) "[remove] Please remove old stale binary postgresql-11-rdkit from focal" [Undecided,New] | 13:19 |
| 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:20 |
| rbalint | rbasak, could you please check the ec2-instance-connect uploads in your SRU cycles? we already discussed the changes to some extent :-) | 13:45 |
| rbalint | rbasak, ah i see you have a short day today | 13:47 |
| rbalint | rbasak, at least the changes are small, but i'll try to find someone else if they can't fit in today | 13:48 |
| -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:04 | |
| -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:05 | |
| 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:06 |
| ubot5 | bug 1862017 in rdkit (Ubuntu) "[remove] Please remove old stale binary postgresql-11-rdkit from focal" [Undecided,New] https://launchpad.net/bugs/1862017 | 14:06 |
| -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:17 | |
| === andrewc is now known as Guest60112 | ||
| -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:28 | |
| -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [5.3.0-40.32~18.04.1] (kernel) | 14:29 | |
| -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:30 |
| ubot5 | Ubuntu bug 1861452 in curtin (Ubuntu Eoan) "sru curtin 2020-01-30 - 19.3-17-g50ffca46-0ubuntu1" [Undecided,Confirmed] | 14:30 |
| -queuebot:#ubuntu-release- Unapproved: rtl8821ce (eoan-proposed/universe) [5.2.5.2.1.30816.20190425-0ubuntu1 => 5.5.2.1-0ubuntu1~19.10.1] (no packageset) | 14:46 | |
| -queuebot:#ubuntu-release- Unapproved: rtl8821ce (bionic-proposed/universe) [5.2.5.2.1.30816.20190425-0ubuntu1~18.04.1 => 5.5.2.1-0ubuntu1~18.04.1] (no packageset) | 14:48 | |
| 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:50 |
| sil2100 | paride: sweet, thanks! | 14:51 |
| sil2100 | jibel: btw. do you remember who usually did the netboot tests? Was it also you? | 14:51 |
| 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:52 |
| paride | the test run takes some time on arm64 so I kept it simple | 14:53 |
| sil2100 | paride: thanks! So convenient ;) | 15:13 |
| 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) ? | 15:47 |
| ubot5 | bug 1862017 in rdkit (Ubuntu) "[remove] Please remove old stale binary postgresql-11-rdkit from focal" [Undecided,New] https://launchpad.net/bugs/1862017 | 15:47 |
| -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:00 | |
| jibel | sil2100, I'm doing amd64 and i386 but cannot cover other archs | 16:18 |
| -queuebot:#ubuntu-release- New binary: brltty [s390x] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core) | 16:27 | |
| -queuebot:#ubuntu-release- New binary: brltty [ppc64el] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core) | 16:29 | |
| -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1032.35~16.04.1] (kernel) | 16:31 | |
| -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:34 | |
| -queuebot:#ubuntu-release- New binary: brltty [armhf] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core) | 16:35 | |
| -queuebot:#ubuntu-release- New binary: brltty [amd64] (focal-proposed/main) [6.0+dfsg-4ubuntu3] (core) | 16:37 | |
| -queuebot:#ubuntu-release- Unapproved: glib2.0 (eoan-proposed/main) [2.62.3-2~ubuntu19.10.1 => 2.62.4-1~ubuntu19.10.1] (core) | 16:49 | |
| -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:07 | |
| -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [s390x] (focal-proposed/universe) [0.1.9-2] (no packageset) | 17:25 | |
| -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [amd64] (focal-proposed/universe) [0.1.9-2] (no packageset) | 17:28 | |
| -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [ppc64el] (focal-proposed/universe) [0.1.9-2] (no packageset) | 17:31 | |
| -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [arm64] (focal-proposed/universe) [0.1.9-2] (no packageset) | 18:04 | |
| -queuebot:#ubuntu-release- New binary: python-deeptoolsintervals [armhf] (focal-proposed/universe) [0.1.9-2] (no packageset) | 18:05 | |
| -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] | 18:30 | |
| rharper | rbasak: around ? | 19:26 |
| -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1069.79] (kernel) | 19:40 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1069.79] | 20:40 | |
| -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (eoan-proposed) [19.3-17-g50ffca46-0ubuntu1~19.10.1] | 22:07 | |
| -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (bionic-proposed) [19.3-17-g50ffca46-0ubuntu1~18.04.1] | 22:12 | |
| -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [19.3-17-g50ffca46-0ubuntu1~16.04.1] | 22:16 | |
| -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:23 | |
| -queuebot:#ubuntu-release- New binary: stk [armhf] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio) | 23:26 | |
| -queuebot:#ubuntu-release- New binary: stk [arm64] (focal-proposed/universe) [4.6.1+dfsg-3] (i386-whitelist, ubuntustudio) | 23:27 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!