=== pieq_ is now known as pieq
[09:03] <koza> hey, i am debugging a snap build issue on arm64 vs amd64. there is liberror-perl package as a stage-packages dependency that fails to resolve on arm64 but is downloaded on amd64. it is arch all in the archive. could you help me understand what arch all means, i.e. can I safely assume that packages with arch=all will resolve on all supported architectures just fine?
[09:32] <cjwatson> koza: Architecture: all means that the package is built on a single architecture but is then architecture-independent and published for all architectures.
[09:33] <cjwatson> So in other words yes.
[09:33] <koza> allright, so there should be no difference in how that package is handled across different architectures
[09:44] <juliank> koza: No, there might very well be differences
[09:44] <juliank> koza: The package is the same, but what it depends on might obviously be not Architecture: all
[09:45] <juliank> I'm not sure if it's possible for an Architecture: all package that depends on let's say an Architecture: amd64 i386 package to migrate to release pocket
[09:46] <juliank> But it's certainly possible that an Architecture: all package fails to install on one architecture, but isntalls fine on another.
[09:47] <juliank> (but yes, usually they should work on all archs)
[09:48] <koza> got it, thanks. i am running further tests but fyi from report that I have recieved liberror-perl fails as a stage-package on arm64
[09:49] <juliank> I mean, it probably shouldn't
[09:49]  * juliank is kind of wondering if we should build a main-extra where we put in linux-image-unsigned and similar build artefacts not meant for users to install
[09:50] <juliank> ooh, "build-only" might be a good name
[12:25] <juliank> Laney, sil2100 do we know why unattended-upgrades 0.90 from releasee was triggered by apt and debconf, rather than the upload in security or updates?
[12:25] <juliank> It picked the correct upload on May 6, but starting with debconf on May 8, it picked release pocket
[12:26] <juliank> s/know/have an idea/
[12:27] <juliank> Get:1 http://ftpmaster.internal/ubuntu xenial/main ppc64el unattended-upgrades all 0.90 [31.6 kB]
[12:27] <juliank> Get:8 http://ftpmaster.internal/ubuntu xenial-updates/main ppc64el libarchive-zip-perl all 1.56-2ubuntu0.1 [84.7 kB]
[12:27] <juliank> so, um, it's picking up some stuff from updates, just not u-u
[13:43] <sil2100> hm hmm
[13:58] <sil2100> THis is indeed very weird
[15:16] <seb128> sil2100, could you SRU review epiphany-browser/disco? it's just a standard GNOME stable update, should be easy. upstream is unhappy about us being outdated and even blogged about it so I would like to show them some movement from us today :)
[15:18] <sil2100> seb128: ACK, will do in a minute ;)
[15:18] <seb128> sil2100, thx!
[15:30] <Odd_Bloke> sil2100: infinity: Hello SRU vanguards, we've completed validation of the latest cloud-init SRU (in https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637) and it's now ready for release; could one of you take a look?  Thanks!
[15:30] <ubot5> Launchpad bug 1828637 in cloud-init (Ubuntu Disco) "sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco" [Undecided,Fix committed]
[15:33] <LocutusOfBorg> (if anybody cares, I would like to discuss debhelper 12 SRU in #-devel channel)
[15:41] <sil2100> Odd_Bloke: on it in a moment as well
[15:41] <Odd_Bloke> sil2100: Thanks!
[16:19] <juliank> sil2100, infinity: small single word (+automated mirror list update) python-apt SRU regression fix in xenial
[16:20] <juliank> * in xenial-proposed
[16:26] <sil2100> juliank: on it in a minute o/
[19:18] <juliank> thanks si
[19:18] <juliank> That was supposed to say "thanks sil2100", but he's gonme