/srv/irclogs.ubuntu.com/2019/12/20/#ubuntu-release.txt

dokocomponent-mismatches are out of date, last regenerated 2019-12-18 17:5003:26
-queuebot:#ubuntu-release- New source: backport-iwlwifi-dkms (bionic-proposed/primary) [7906-0ubuntu3~18.04.1]07:28
LocutusOfBorghttps://launchpad.net/ubuntu/+source/llvm-toolchain-9/1:9.0.1~+rc3-2/+build/1827258108:00
LocutusOfBorganybody knows what happened here?08:00
tjaaltonthe builder needs a kick08:01
tjaaltonthere were some issues yesterday08:01
=== andrewc is now known as Guest42747
LocutusOfBorgthanks, I hope somebody can do it without having to restart the full build08:09
* LocutusOfBorg leaves08:09
RikMillssil2100 or apw: on LP: #1856531 could we get the armhf/arm64 release binaries removed now? gone in debian. plus cleanup in -proposed if needed08:47
ubot5Launchpad bug 1856531 in libgit2 (Ubuntu) "Please RM julia arm64 and armhf binaries" [Undecided,New] https://launchpad.net/bugs/185653108:47
RikMillsjulia binaries that is08:47
tjaaltonsil2100: image built! \o/09:25
sil2100tjaalton: sweet!09:38
sil2100RikMills: I'll try looking into that, but no promises09:39
RikMillsno problem. I expect steve will tonight if you can't09:39
tjaaltonsil2100: one thing with the fwupd mess is that our dell team has used a newer version of fwupd-signed, so they're asking to bump it's version to match the one that built against fwupd 1.2.10. fwupd-signed itself has no other diff than the changelog between 1.2..1.909:41
tjaaltonI don't know why the current one in proposed used the version from cosmic09:42
tjaaltonprobably because it was uploaded 6mo ago09:43
tjaaltonor something09:43
-queuebot:#ubuntu-release- Unapproved: fwupd-signed (bionic-proposed/main) [1.2~ubuntu18.04.1 => 1.10~ubuntu18.04.1] (no packageset)09:54
tjaaltonsil2100: ^ just a rebuild and allows the dell team to move to an archive version09:55
tjaaltonalso allows upgrade to eoan, their version is newer than what's in disco..09:56
-queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.13 => 20101020ubuntu543.14] (core)10:37
-queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.14]10:39
sil2100tjaalton: I'm actually thinking about if maybe it wouldn't be a good idea to include the fwupd 1.2.10-1ubuntu2~ubuntu18.04.2 that's in the bionic queue first, and do the -signed bump for that version10:51
tjaaltonsil2100: yeah, probably10:52
tjaaltonas ycheng already hit the bug it's supposed to fix10:52
cjwatsonLocutusOfBorg: Sorry, ended up having to retry it10:54
cjwatson(Which was a bit unnecessary in fact, but I misdiagnosed because buildd-manager seemed otherwise functional)10:55
sil2100Problem is, the later series don't have the fix yet, and accepting it would invalidate testing they did already on their -proposed versions10:55
sil2100eh, I guess I'll accept bionic for now and see how the rest goes later today10:55
tjaaltoncool10:56
tjaaltonit's in focal at least10:56
tjaaltonand eoan queue10:57
sil2100Yeah, it's missing a fwupd-signed bump, but we can push that ourselves if needed10:58
sil2100(in eoan)10:58
tjaaltonright, I added a comment on the bug10:58
sil2100Anyway, will poke Ken later today and probably accept the eoan ones too - if not, we'll just do that next year ;)10:58
sil2100Thanks!10:58
-queuebot:#ubuntu-release- Unapproved: fwupd-signed (bionic-proposed/main) [1.2~ubuntu18.04.1 => 1.10~ubuntu18.04.2] (no packageset)10:59
tjaaltonexcellent10:59
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.2]11:07
-queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.2 => 1.2.10-1ubuntu2~ubuntu18.04.2] (desktop-core)11:11
-queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.2 => 1.2.10-1ubuntu2~ubuntu18.04.2] (desktop-core)11:11
-queuebot:#ubuntu-release- Unapproved: rejected fwupd-signed [source] (bionic-proposed) [1.10~ubuntu18.04.1]11:12
-queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.2 => 1.2.10-1ubuntu2~ubuntu18.04.2] (desktop-core)11:14
-queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.2 => 1.2.10-1ubuntu2~ubuntu18.04.2] (desktop-core)11:14
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.2]11:16
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.2]11:16
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.2]11:16
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [i386] (bionic-proposed) [1.2.10-1ubuntu2~ubuntu18.04.2]11:16
-queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (bionic-proposed) [1.10~ubuntu18.04.2]11:17
rbalintsil2100, could you please drop systemd from focal-proposed? LP: #185712311:47
ubot5Launchpad bug 1857123 in systemd (Ubuntu) "IPv4 addresses are not assigned in LXC with systemd 244.1" [Undecided,New] https://launchpad.net/bugs/185712311:47
rbalintsil2100, this may hold back the armhf queue11:47
LocutusOfBorgcjwatson, no problem at all! thanks for using the stick!11:56
rbalintdoko, could you please drop systemd from focal-proposed?12:04
rbalintdoko, ^^12:04
sil2100uh, ok12:13
sil2100y12:15
sil2100rbalint: should be done12:16
rbalintsil2100, thanks!12:21
Laneyarmhf autopkgtest not looking good /o\12:37
* Laney smites the things12:44
Laneylooks better13:03
cascardoLocutusOfBorg: any ideas on the status of virtualbox migration? seth mentioned kopanocore blocking gsoap blocking virtualbox. how can I help?13:29
cascardoright now, I am trying to reproduce the kopanocore failure with a debug shell so I can investigate13:30
LocutusOfBorgthanks13:35
LocutusOfBorgcascardo, vorlon just a side note: that smoke test has been changed in the version in proposed13:37
LocutusOfBorgso, the version in release is probably buggy too13:37
LocutusOfBorgoh. looks like xnox did an upload one hour ago13:37
LocutusOfBorgthanks!13:37
xnoxcascardo:  i have been annoyed at kernel not migrating, chased it down to kopanocore this morning, and did an upload that should hopefully unbreak things13:38
xnox=)13:38
LocutusOfBorgdo you plan also to forward to debian?13:38
xnoxcascardo:  only need to wait and see if it will work or not13:38
LocutusOfBorgbtw thanks a ton, I couldn't figure out13:38
xnoxLocutusOfBorg:  once it is actually green and migrates, yes13:38
LocutusOfBorgthanks^213:39
LocutusOfBorg:D13:39
LocutusOfBorgin any case, the patch looks good even if it doens't work13:39
LocutusOfBorgbut shouldn't apt being non-interactive generally in autopkgtests env?13:39
cascardoxnox: Great! thanks a bunch!13:40
LocutusOfBorgvorlon, can we have python-envisage kicked out from release? reason is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93773013:40
ubot5Debian bug 937730 in src:python-envisage "python-envisage: Python2 removal in sid/bullseye" [Serious,Open]13:40
LocutusOfBorgI would like to have python-apptools migrate13:41
LocutusOfBorgxnox, http://autopkgtest.ubuntu.com/packages/k/kopanocore/focal/ppc64el13:51
LocutusOfBorgfail :/13:51
LocutusOfBorgI'm trying a build too13:51
xnoxsigh14:26
xnoxLocutusOfBorg:  yes it should be non-interactive, and it was failing for me when run interactively14:26
xnoxit passed when frontend was interactive14:27
xnoxLocutusOfBorg:  also, isn't our default mysql, mysql itself? and not mariadb14:27
xnoxapw cascardo:  the other alternative is to badtest kopanocore => it does work. Which will let virtualbox to migrate, which will unblock kernel14:29
cascardoxnox: I like the sound of that14:41
xnoxapw:  can you please badtest kopanocore? the tests pass interactively, we are failing to reproduce locally / understand why it doesn't start in adt tests.14:42
=== andrewc is now known as Guest66497
LocutusOfBorgsmoke                SKIP unknown restriction skippable14:53
LocutusOfBorgsigh:14:53
LaneyRemove the broken kopanocore from focal-proposed14:53
LocutusOfBorgLaney, considering that also the one in release is broken, I would prefer not doing it14:53
LocutusOfBorgI can workaround the test by removing that new check14:53
LocutusOfBorgbetter than going again python214:53
LocutusOfBorg:/14:53
=== hggdh is now known as QuosqueTandem
xnoxLaney:  remove broken kopanocore; rebuild old kopanocore against new gsoap; let that lot migrate; put kopanocore back in; try to fix it?15:06
xnoxLaney:  i can prepare a rebuild of old kopanocore in a bileto ppa.15:06
Laneywell I can't action that unfortunately, but seems better to me than letting an unknown thing migrate15:15
Laneyon the other hand I reproduced the failure, here is what is in the journal: https://paste.ubuntu.com/p/Jf9jGCRxJ8/15:15
Laneyit fails to stop and then the new one after the restart is busted15:15
-queuebot:#ubuntu-release- Unapproved: makedumpfile (eoan-proposed/main) [1:1.6.6-2ubuntu1 => 1:1.6.6-2ubuntu1.1] (core)15:15
LaneyI added pkill -f -9 kopano-server, and then it passes15:16
-queuebot:#ubuntu-release- Unapproved: makedumpfile (bionic-proposed/main) [1:1.6.5-1ubuntu1~18.04.3 => 1:1.6.5-1ubuntu1~18.04.4] (core)15:16
Laneyso the daemon does seem buggy in some way, to me15:16
-queuebot:#ubuntu-release- Unapproved: makedumpfile (xenial-proposed/main) [1:1.6.3-2~16.04.1 => 1:1.6.3-2~16.04.2] (core)15:17
Laneyprobably if it was a proper unit systemd would at least be able to fall back to SIGKILLing it15:22
Laneyxnox: as you wish, to proceed with the removal / later fixup maybe ask seb12_8 to remove the pkg15:23
* Laney is going to have super late lunch15:23
-queuebot:#ubuntu-release- New: accepted libglvnd [amd64] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted libglvnd [armhf] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted libglvnd [s390x] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted libglvnd [arm64] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted libglvnd [i386] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted libglvnd [ppc64el] (focal-proposed) [1.3.0-4]15:42
-queuebot:#ubuntu-release- New: accepted mdp [amd64] (focal-proposed) [3.5-1.1]15:42
-queuebot:#ubuntu-release- New: accepted nitime [amd64] (focal-proposed) [0.8.1-2]15:42
-queuebot:#ubuntu-release- New: accepted python-skbio [amd64] (focal-proposed) [0.5.5-3]15:42
-queuebot:#ubuntu-release- New: accepted libxcrypt [amd64] (focal-proposed) [1:4.4.10-7]15:42
-queuebot:#ubuntu-release- New: accepted pbcopper [amd64] (focal-proposed) [1.3.0+dfsg-1]15:42
-queuebot:#ubuntu-release- New: accepted nitime [amd64] (focal-proposed) [0.8.1-1]15:42
-queuebot:#ubuntu-release- Unapproved: makedumpfile (disco-proposed/main) [1:1.6.5-1ubuntu1.3 => 1:1.6.5-1ubuntu1.4] (core)15:51
santa_dear release wizards,16:00
santa_I would like to ask about current status of fuse vs fuse3 in ubuntu16:00
santa_I have been investigating something new from kde named kio-fuse16:01
santa_this thing, apparently requires fuse3 to be installed (it runs fusermount3, provided by fuse3 package)16:02
santa_this package, 'fuse3' is not co-installable with the 'fuse' package (which is version 2.x)16:03
santa_so I did an experimental kio-fuse package with 'fuse3' in 'Depends'16:05
santa_it works nice, but it uninstalls some other things which depend on 'fuse'16:06
santa_xdg-desktop-portal for instance iirc16:06
santa_so I checked the reverse depends of package 'fuse' and there's a fair amount of things affected16:07
santa_AND...16:07
santa_I found this: https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.016:07
santa_see the "Note to Packagers"16:08
santa_reading that, I have the impression that the packages which depend on 'fuse' should actually depend on 'fuse3' (since it's suposed to be backwards compatible)16:09
santa_and this way, everything would be co-installable, no matter if it was built against libfuse 2 or 316:10
santa_what do you think? am I missing something?16:11
santa_related, see the last sshfs-fuse upload: https://launchpad.net/ubuntu/+source/sshfs-fuse16:12
santa_RikMills: ↑16:12
RikMillssanta_: https://irclogs.ubuntu.com/2019/11/19/%23ubuntu-release.html#t18:5516:14
santa_or perhaps fuse3 should have a "Provides: fuse" if that works the way I think it works16:15
RikMillsfuse3 does have a provides fuse. its still broken16:16
seb128rikMills, https://launchpad.net/ubuntu/+source/gvfs/1.42.1-1ubuntu116:16
seb128looks like fuse3 is the way to go and we should just MIR it and revert the gvfs change16:16
RikMillsseb128: would that be why iso builds broke when sshfs-fuse ported to fuse3? kdeconnect on kubuntu iso wants sshfs-fuse16:20
seb128rikMills, could be yes16:20
santa_RikMills: thanks for the info16:21
santa_so what would be the solution to this, just changing the depends of all the affected packages?16:22
RikMillsseb128: I reverted the sshfs-fuse port for now, so I can revert that revert, I would be happy :)16:22
RikMills*if I can16:22
seb128someone needs to MIR fuse316:23
santa_what's MIR?16:23
seb128https://wiki.ubuntu.com/MainInclusionProcess16:24
* RikMills hides16:24
-queuebot:#ubuntu-release- Unapproved: binutils (eoan-proposed/main) [2.33-2ubuntu1.1 => 2.33-2ubuntu1.2] (core) (sync)16:24
cjwatsonA versioned Provides of fuse might help too?16:32
cjwatson(unversioned Provides don't satisfy versioned dependencies)16:32
cjwatsonDunno, I've only looked at this conversation and not anything more details16:33
cjwatson*detailed16:33
Laneyvorlon: I had a look at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/i386/c/clutter-1.0/20191219_103907_849c1@/log.gz - it seems to be that :i386 pins aren't generated; have you thought about this?16:43
santa_cjwatson: but they are not versioned depends, xdg-desktop-portal just depends of fuse, unversioned16:43
santa_(for example)16:43
cjwatsonNo idea then :)16:44
rbalintsil2100, i've rebuild and copied binutils for eoan if you could take a look16:52
=== ginggs_ is now known as ginggs
santa_hmm, sorry, correction: installing my kio-fuse experimental package doesn't uninstall xdg-desktop-portal, it's just that dpkg complains about it16:55
santa_so it seems the "Provides: fuse" actually works16:56
santa_... to some extent16:59
santa_but it would be still a problem for the isos right RikMills ?16:59
santa_hmm the way I see it right now the correct solution for handling this upgrade in debian would have been:17:02
santa_- not providing the "fuse" bin package in src:fuse17:02
santa_- adding a transitional dummy package "fuse" which would install "fuse3" in src:fuse317:03
santa_infinity: any comment about this? ↑ since you mentioned you were going to work on it17:06
RikMillssanta_: something on the iso build wasn't happy with the fuse dep being provide by fuse3, that is for certain17:09
santa_I guess it confuses the package manager17:10
RikMillsgvfs not liking its fuse depends being replaced by something from universe sounds plausible.17:13
vorlonLocutusOfBorg: python-envisage: done; and maybe you want to help figure out why this didn't get picked up on https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/rcbuggy-problem-packages.html17:19
vorlonLaney: :i386 pins: yes, I've thought about it :)  just haven't written it yet17:21
Laneynod17:24
vorlonLaney: do you know what's up with armhf autopkgtest queues?17:26
vorlonseems like it might be coming down now but not enough data points to know if that's an accident or if someone fixed something17:27
LaneyI did fix it by rebooting all of the lxd-armhf*17:27
vorlonah k17:27
Laneydidn't find out exactly what broke them, but there was a dodgy systemd from rbalint which wasn't helping after they recovered :-)17:28
Laneyshould have made that fall away too17:28
santa_RikMills: yep, I guess that "MIR" would be in place17:28
rbalintvorlon, could you please review/accept binutils to eoan?17:33
vorlonrbalint: looking.  did the changelog/content mismatch get fixed?17:34
rbalintvorlon, aslo maybe pam to get it released early next year?17:34
-queuebot:#ubuntu-release- Unapproved: flash-kernel (bionic-proposed/main) [3.90ubuntu3.18.04.2 => 3.98ubuntu5.3~18.04.1] (core)17:34
vorlon$ sru-review -s eoan binutils17:34
vorlonERROR: queue does not have a debdiff17:34
rbalintvorlon, it is a bin copy from -security only bileto ppa17:35
vorlonugh17:35
vorlonok17:35
rbalintvorlon, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3878/+packages17:35
rbalintvorlon, i forgot binutils and gccs are special, but sil2100 caught that17:35
* vorlon nods17:36
-queuebot:#ubuntu-release- Unapproved: accepted binutils [sync] (eoan-proposed) [2.33-2ubuntu1.2]17:42
=== andrewc is now known as Guest11720
-queuebot:#ubuntu-release- Unapproved: mutter (eoan-proposed/main) [3.34.1+git20191107-1ubuntu1~19.10.1 => 3.34.2-1ubuntu1~19.10.1] (desktop-core, desktop-extra)18:22
-queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (bionic-proposed/multiverse) [1.20190215-0ubuntu0.18.04.1 => 1.20190819-0ubuntu0.18.04.1] (no packageset)18:26
cascardoxnox: any thoughts on that kopanocore issue? I wonder if virtualbox can work with the gsoap version in release18:56
xnoxcascardo:  we can rebuild virtualbox against gsoap from release pocket, and let virtualbox migrate19:01
xnoxcascardo:  that's no different to rebuilding old kopacore19:02
xnoxcascardo:  let's see if i can do that.19:02
cascardoxnox: thanks!19:10
-queuebot:#ubuntu-release- Unapproved: u-boot (bionic-proposed/main) [2018.07~rc3+dfsg1-0ubuntu3~18.04.2 => 2019.07+dfsg-1ubuntu3~18.04.1] (core)19:34
xnoxhttps://launchpad.net/ubuntu/+source/virtualbox/6.1.0-dfsg-3build1 publishing22:49
xnoxhopefully should test & migrate22:49
xnoxonce migrated will upload another no change rebuild against the new abi22:49
sil2100waveform, bdmurray: I'm looking at the flash-kernel SRU and I'm a bit worried - so it seems like the bootscript that's in that SRU is actually that bootscript we have reverted for eoan?23:38
sil2100waveform, bdmurray: i.e. it's the one that was causing those weird boot issues on 3B23:38
sil2100I think we'll have to have a fresh look on that after new year's23:39
gQuigsare SRUs likely to be released over the holidays?  (I'm thinking of python-ldap to be specific)23:58
gQuigsnot a rush, just want to set expectations correctly..23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!