-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1004.4] (core, kernel)00:10
-queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (disco-proposed/main) [5.0.0-1004.4] (core, kernel)00:10
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1004.4]00:12
-queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (disco-proposed) [5.0.0-1004.4]00:12
infinityOkay, the way things are looking, I think I'll just respin first thing in the morning instead of worrying about doing a hand-off, etc.00:12
infinityCause it'll be past NA bedtime by the time all this stuff is happy and moving.00:13
-queuebot:#ubuntu-release- Unapproved: debian-installer (disco-proposed/main) [20101020ubuntu569 => 20101020ubuntu570] (core)00:16
-queuebot:#ubuntu-release- Unapproved: rejected linux-gcp [sync] (disco-proposed) [5.0.0-1004.4]00:20
-queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (disco-proposed) [20101020ubuntu570]00:20
-queuebot:#ubuntu-release- Unapproved: thunar (disco-proposed/universe) [1.8.4-1 => 1.8.4-1ubuntu1] (mythbuntu, ubuntustudio, xubuntu)00:34
bluesabreinfinity: can you go ahead and approve the above thunar upload so it makes it into tomorrow's respin? :)00:35
bluesabreIncluding the (please) I forgot just now00:36
infinityI'll leave that to vorlon.00:37
* infinity sleeps for a few hours.00:38
bluesabreinfinity, vorlon, much appreciated :)00:39
vorlonbluesabre: rather large patch, and the header says it's 1/3. how sure are you this fixes the issue?00:39
vorlonoh, it's 3 patches serialized in 1 file  :P00:39
bluesabrevorlon: yes, the patch submitted upstream was a 3-parter (parts 2 and 3 are in the same patch), https://bugzilla.xfce.org/attachment.cgi?id=840800:39
vorlonbluesabre: so you've already tested this locally and confirmed it fixes?00:40
bluesabreas for how sure, I was 100% able to reproduce the issue before (was driving me nuts), and can no longer reproduce now00:40
-queuebot:#ubuntu-release- Unapproved: accepted thunar [source] (disco-proposed) [1.8.4-1ubuntu1]00:41
bluesabrevorlon: thanks a bunch!00:41
mwhudsoninfinity: about to release the hopefuly final subiquity to stable btw01:15
-queuebot:#ubuntu-release- Unapproved: runc (cosmic-proposed/universe) [1.0.0~rc4+dfsg1-6ubuntu0.18.10.1 => 1.0.0~rc7+git20190403.029124da-0ubuntu1~18.10.1] (no packageset)01:28
-queuebot:#ubuntu-release- Builds: Netboot amd64 [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Builds: Netboot arm64 [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Builds: Netboot armhf [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Builds: Netboot i386 [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Builds: Netboot ppc64el [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Builds: Netboot s390x [Disco Final] has been updated (20101020ubuntu570)01:31
-queuebot:#ubuntu-release- Unapproved: runc (bionic-proposed/universe) [1.0.0~rc4+dfsg1-6ubuntu0.18.04.1 => 1.0.0~rc7+git20190403.029124da-0ubuntu1~18.04.1] (no packageset)01:32
-queuebot:#ubuntu-release- Unapproved: runc (xenial-proposed/universe) [1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.2 => 1.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.1] (no packageset)01:35
-queuebot:#ubuntu-release- Unapproved: containerd (cosmic-proposed/universe) [0.2.5-0ubuntu2 => 1.2.6-0ubuntu1~18.10.1] (no packageset)01:39
-queuebot:#ubuntu-release- Unapproved: containerd (bionic-proposed/universe) [0.2.5-0ubuntu2 => 1.2.6-0ubuntu1~18.04.1] (no packageset)01:40
mwhudsoncan someon reject those containerd uploads? forgot something01:40
-queuebot:#ubuntu-release- Unapproved: containerd (cosmic-proposed/universe) [0.2.5-0ubuntu2 => 1.2.6-0ubuntu1~18.10.1] (no packageset)01:46
-queuebot:#ubuntu-release- Unapproved: containerd (bionic-proposed/universe) [0.2.5-0ubuntu2 => 1.2.6-0ubuntu1~18.04.1] (no packageset)01:50
-queuebot:#ubuntu-release- Unapproved: containerd (xenial-proposed/universe) [0.2.5-0ubuntu1~16.04.1 => 1.2.6-0ubuntu1~16.04.1] (no packageset)01:52
-queuebot:#ubuntu-release- Unapproved: docker.io (cosmic-proposed/universe) [18.09.2-0ubuntu1~18.10.1 => 18.09.5-0ubuntu1~18.10.1] (no packageset)01:57
-queuebot:#ubuntu-release- Unapproved: docker.io (bionic-proposed/universe) [18.09.2-0ubuntu1~18.04.1 => 18.09.5-0ubuntu1~18.04.1] (no packageset)01:59
-queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [18.09.2-0ubuntu1~16.04.1 => 18.09.5-0ubuntu1~16.04.1] (no packageset)02:01
=== s8321414_ is now known as s8321414
mwhudsoninfinity: released subiquity to stable now02:36
mwhudsonshould be ready for any iso testing people still have time for ...02:36
tewardmwhudson: does that happen to contain a fix for 1821966 and search domains?02:39
tewardjust curious :P02:39
mwhudsonteward: yes02:39
mwhudsonteward: although you should test tomorrow's daily to make sure!02:39
tewardwell then I'll test tomorrow's daily :P02:40
tewardmwhudson: any idea when the dailies generate?02:46
tewardso I know when tomorrow to test :p02:46
acheronukteward: disco dailies are turned off AFAIK04:41
-queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-ubuntu-dock (disco-proposed/main) [64ubuntu6 => 64ubuntu7] (ubuntu-desktop) (sync)06:26
-queuebot:#ubuntu-release- Unapproved: kopanocore (disco-proposed/universe) [8.7.0-2ubuntu1 => 8.7.0-2ubuntu2] (no packageset)06:51
LocutusOfBorgdoko, ^^ I tried to fix your kopanocore upload, but I'm not really sure about the fix...06:52
LocutusOfBorgmaybe the fix should go in src:apport?06:53
LocutusOfBorgmaybe juliank ^^ ? does apt need to read cputable?06:55
juliankLocutusOfBorg: yes, it does06:56
LocutusOfBorgdoes it have an apport profile?06:56
LocutusOfBorgI don't get why kopanocore fails testsuite in that way06:56
juliankI don't think it does06:57
LocutusOfBorgkopanocore fails because of that file being non accessable, the obviously fix is to add to the profile (looks like working on DebOMatic, but maybe that machine has no apport enforcement, not sure)06:58
-queuebot:#ubuntu-release- Unapproved: unattended-upgrades (disco-proposed/main) [1.10ubuntu4 => 1.10ubuntu5] (core)06:58
LocutusOfBorgand in any case kopanocore doesn't directly access that file, so it might be a dpkg/apt bug hidden somewhere?06:58
rbalint^one more fix for the errors seen in disco and also fixing slowness in bionic06:59
juliankLocutusOfBorg: I'm not sure why it's not accessible07:00
juliankdpkg ships that file, and apt requires it being present07:00
rbalintupstreadm review: https://github.com/mvo5/unattended-upgrades/pull/19007:00
gitbotmvo5 issue (Pull request) 190 in unattended-upgrades "Adjust only transitive dependencies in the fallback" [Open]07:00
rbalintjuliank, i really want to do pinning only and not adjustments in u-u07:01
juliankrbalint: well, then, do it I guess - I think the infra is there now, although a bit hacky07:04
LocutusOfBorgAppArmor parser error for /etc/apparmor.d/usr.sbin.kopano-search in /etc/apparmor.d/usr.sbin.kopano-search at line 39: missing an end of line character? (entry: /etc/ssl/openssl.cnf)07:07
rbalintjuliank, also i measured u-u to be much slower07:08
rbalintjuliank, needs to move to low level apt api first, it seems07:08
LocutusOfBorgdevil is hidden in the details07:08
* LocutusOfBorg grabs coffee and prepares a big hammer07:08
juliankrbalint: You should add an action group around the adjustment loop I think07:09
LocutusOfBorg+  signal (send) set=("term") peer=unconfined,07:09
LocutusOfBorgwhat is the problem on this?07:09
juliankrbalint: because this is wreaking havoc in recalculating installability each time you adjust one07:09
LocutusOfBorgoh no07:10
rbalintjuliank, the speed is not terrible and actiongroups caused problems with cache clear, thus i don't want to risk that now07:12
juliankWell, yes07:12
rbalintjuliank, the side effects of action groups are not crystal clear07:12
-queuebot:#ubuntu-release- Unapproved: kopanocore (disco-proposed/universe) [8.7.0-2ubuntu1 => 8.7.0-2ubuntu2] (no packageset)07:13
juliankWell, they are perfectly clear - the action group delays recalculating stuff in the dep cache07:13
juliankObviously, you can't re-initialize the depcache while you're holding an action group07:13
julianks/Obviously/It follows that/07:14
juliankaction groups should provide a drastic performance increase07:14
juliankswitching to low-level should offer basically no performance07:14
juliankProbably should raise an exception when clearing a cache that has an action group07:15
juliankrbalint: Or to be more clear, action groups, when released, re-calculate which packages are autoremovable and which are not07:18
juliankrbalint: So, if you re-initialize the cache while holding the action group, you'll end up with wrong autoremovable states07:20
juliankrbalint: But yes it will require some restructuring of u-u to work with that model07:22
juliankthough i do not understand _how_ it delays things07:23
juliankAh I see07:23
juliankThe code is super odd07:23
julianke.g. MarkInstall() keeps an ActionGroup during its call07:24
juliankso, if there is no other action group, it will be released at the end07:24
julianksame for set candidate version07:24
juliankrbalint: What this means is that each time you adjust the candidate, or mark something for install/remove, apt traverses the entire set of packages reachable from the installed ones and marks them as reachable07:25
juliankwhich is, um, slow07:25
rbalintjuliank, yes i can see that07:25
rbalintjuliank, and rather than trying to sped this up a bit i'd like to drop adjustments and use pinning07:26
juliankBut we can fix apt, so that Init() works with an actiongroup hold actually works well, then you can clear the cache as often as you like07:26
rbalintthat would also be wonderful and speed up other clients as well07:27
juliankrbalint: oh, but you still have to release the action group before determining which packages are auto-removable07:32
juliankBut I'm wondering if python-apt could not automatically manage an action group for you07:32
juliankbasically, keep an action group until you are looking at autoremovable states07:33
rbalintinfinity u-u 1.10ubuntu5 autopkg passed locally in bionic vm07:33
juliankit's a bit fragile if actiongroup behavior changes in the future07:34
rbalinthow about not changing it and seeing how u-u performs using pinning and low level apt api?07:35
rbalintmaybe automatic action group would just slow it down07:36
-queuebot:#ubuntu-release- Unapproved: base-files (disco-proposed/main) [10.1ubuntu8 => 10.1ubuntu9] (core)07:39
-queuebot:#ubuntu-release- Unapproved: rejected kopanocore [source] (disco-proposed) [8.7.0-2ubuntu2]07:43
juliankrbalint: I just thought I'd have apt set a dirty bit instead when it makes the "autoremovable" cache dirty, rather than recalculating right then; and then when requesting autoremovable state, recalc it if it's dirty.07:43
juliankshould be a nice gain for most users and avoid the need for action groups07:43
rbalintjuliank, it would help a lot if there were info on action to not use https://apt-team.pages.debian.net/python-apt/library/apt.cache.html?highlight=actiongroup#apt.cache.Cache.actiongroup07:44
-queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-ubuntu-dock [sync] (disco-proposed) [64ubuntu7]07:44
infinityLocutusOfBorg: That kapanocore change doesn't look sane to me.  At least, not from my reading of other apparmor profiles over the years.07:45
rbalintjuliank, ok, but can't i read autoremovable state of packages withot noticing the dirtyness?07:45
juliankrbalint: Well, I'd replace the fields in apt's cache with accessor methods07:45
rbalintjuliank, does not sound like a speedup...07:46
juliankthat do bool Garbage() { if (dirty) MarkAndSweep(); return Garbage; }07:46
juliankrbalint: It certainly is not a speedup for those who use action groups now, yes07:46
infinityjuliank: Can you review this u-u in the queue and give me a thumbs up or down?  It's a bit long for my python-hating brain this morning.07:47
juliankIt's also shorter than it looks because it's the same file two times07:48
juliankinfinity: I did look at it yesterday in github, and it looks ok07:49
juliank-            marking_succeeded = self.call_checked(function, pkg, **kwargs)07:49
juliank+            self.call_checked(function, pkg, **kwargs)07:49
juliankis the only thing I'm confused about07:49
infinity"it looks okay" shouldn't be followed by "but..." on another line. :P07:50
rbalintjuliank, i made minor edits07:50
-queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (disco-proposed) [1.10ubuntu5]07:50
infinity(already accepted it)07:50
infinityBut please, talk amongst yourselves, and if you have something better to upload, I'd like it in ~30m.07:50
-queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (disco-proposed) [10.1ubuntu9]07:51
juliankinfinity: Well, it's OK, it just looks slightly odd, but the variable is not used afterwards, so it's technically fine07:51
rbalintjuliank, yep, it was an obsolete assignment07:53
LocutusOfBorginfinity, you mean the first or the second upload?07:55
infinityLocutusOfBorg: The seonc.07:55
infinitysecond, too.07:55
infinity-  /etc/ssl/openssl.cnf r,07:56
infinity+  /etc/ssl/openssl.cnf r07:56
LocutusOfBorgdid you see the diff between -1 and -2 uploads?07:56
LocutusOfBorgI mean the good and the bad one07:56
infinity.... and?07:57
infinity-2 looks correct to me.07:58
LocutusOfBorg:( so I don't know...08:00
LocutusOfBorgLocutusOfBorg: ^^ seriously?20:0408:00
LocutusOfBorgvorlonwe're in final freeze. *critical fixes only*, not "sync new upstream versions to be in sync"08:00
LocutusOfBorg^^ vorlon I miss the context, I fixed other people syncs from experimental I didn't sync by myself from there08:01
LocutusOfBorgand if you mean mokutils a) its mostly a no change sync (modulo some maintainer field and vcs fields updated), and it is from unstable, and blame tsimonq2 for this :)08:02
LocutusOfBorgif you mean vala, I don't sync vala, for sure not from experimental :)08:02
* LocutusOfBorg would like to forbid experimental syncs08:02
infinity14:05 -queuebot:#ubuntu-release- Unapproved: rejected mokutil [sync] (disco-proposed)08:02
infinity          [0.3.0+1538710437.fb6250f-1]08:02
infinity14:06 < vorlon> not even new upstream version; but regardless, no08:03
infinityLocutusOfBorg: ^ That was the context.08:03
LocutusOfBorgwell, its a cosmetic change I sponsored for tsimonq2, in any case I don't think the end user will care about a wrong VCS field...08:03
infinityLocutusOfBorg: And how does one blame someone else for your upload?08:03
LaneyPerhaps don't upload cosmetic changes in final freeze.08:04
LocutusOfBorgyep sure, isn't VCS fields something end users care about?08:04
infinityLaney: I'll be in the office in ~30... Got distracted working from the hotel and didn't notice the time. :P08:04
LocutusOfBorgI mean, is debcheckout supposed to being run from ubuntu users?08:05
juliankit's not08:05
juliankI mean, think about it08:05
infinity"regular users" use binary packages.08:05
Laneyinfinity: I'mjust arriving into St PancrasinfI'm just arriving into St Pancras08:05
LaneyIf this even sends08:05
Laneysee if you can tell from that that I'm on a train08:05
infinityLaney: Hahaha.  It sent.  All the times.08:05
juliankThe Vcs field is only useful for devel08:06
juliankif at all08:06
LocutusOfBorginfinity, good point :) I would say "regular users don't use linux" probably :p08:06
Laney'k, see you soon08:06
juliankBecause the Vcs change often enough for a stable release to be outdated anyway, and we don't SRU Vcs field changes08:06
juliankAnd since we do not SRU Vcs field changes, it's also not appropriate for an upload during final freeze08:07
LocutusOfBorgjuliank, yep, I happen to use it on Ubuntu, because all my packages are in sync, so I don't care about it being a Debian tool, but meh, you are right08:07
juliankI could update the branch name in Vcs-Git for apt when doing stable releases, like I do debian/gbp.conf08:08
juliankbut I never bothered08:08
LocutusOfBorginfinity, wrt apparmor you were right, that warning was from the previous upload, so yes you are right08:09
LocutusOfBorgso any idea for this kopanocore upload?08:09
infinityLocutusOfBorg: I haven't looked at the issue(s), just noted that removing that comma was wrong. :P08:10
infinityLocutusOfBorg: Maybe I can poke later, after respin o'clock.08:10
LocutusOfBorgmaybe the first version of my upload in the queue was better... not sure if DebOMatic is enough to trigger this issue08:10
-queuebot:#ubuntu-release- Unapproved: rejected kopanocore [source] (disco-proposed) [8.7.0-2ubuntu2]08:11
juliankI don't really feel like it makes sense for packages to include files needed by apport implementation details in their apparmor profile08:13
juliankMaybe we should move the files the python hook needs like cputable into the python abstractions08:14
juliankbecause this does not affect only kopanocore - any crashing python app with a apparmor profile will fail to run the apport crash handler08:16
juliankLocutusOfBorg: ^08:16
LocutusOfBorgjuliank, so you can fix it?08:18
LocutusOfBorgand yes I agree that a general problem needs a general solution08:19
juliankI'm not entirely sure what we need08:20
julianklike we do know we need cputable08:20
juliankbut we'll probably also need read access to /var/lib/dpkg/status and /var/lib/apt/lists, and configuration files from apt08:21
sil2100jibel: morning o/08:21
sil2100jibel: did you notice LP: #1824905 during your testing so far?08:21
ubot5`Launchpad bug 1824905 in ubiquity (Ubuntu) "Long pause when selecting 3rd party drivers during install" [Undecided,Confirmed] https://launchpad.net/bugs/182490508:21
juliankLocutusOfBorg: FWIW, I don't think it's a huge issue, and I'd focus on finding out why kopanocore fails rather than making the apport hook work08:22
sil2100jibel: I wonder if that's reproducible only on specific hardware or maybe happens everytime08:22
* sil2100 downloads an iso08:22
juliankIt's unclear to me that just making the apport hook work (adding the file it needs) is the right approach08:22
juliankbecause under normal operation, it will not run, and you give the code access to files it does not _really_ need08:23
jibelsil2100, I commented on the bug report08:26
jibelsil2100, it's when ubuntu-drivers runs08:26
juliankSo I think we should leave that up to security team08:26
jibeland now it runs every time08:26
juliankI'll report a launchpad bug for that08:26
jibelsil2100, because we want to install free drivers too for example when running on vmware08:26
jibelsil2100, I think the fix is to add some feedback08:27
juliankLocutusOfBorg: reported https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/182496108:29
ubot5`Ubuntu bug 1824961 in apparmor (Ubuntu) "Blocks apport python hook from working" [Undecided,New]08:29
sil2100jibel: ah, hm, ok! Thanks08:30
sil2100jibel: anyway, since it's doing what it's supposed to, not a blocker - carry on!08:32
xnoxinfinity, Laney - i am staying at home today, probably like until 2pm at least, because deliveries =(08:36
juliankugh deliveries08:37
* juliank has one tomorrow, already sad08:37
sil2100xnox: aww08:43
LocutusOfBorgjuliank, what if I say "it doesn't fail on my machine?"08:50
xnoxinfinity, https://code.launchpad.net/~xnox/ubuntu-cdimage/suru-fold-fix-offset-horizon/+merge/366092 better cdimage horizon (from the web team email)08:50
juliankLocutusOfBorg: I don't see how that's relevant. There is an issue mapping the python .so file in the test case; that causes the apport hook to be loaded and fail, but it's not the apport failure causing the failure08:51
LocutusOfBorgI think I got the issue08:51
LocutusOfBorginfinity, ^^ looks like do ko updated the wrong apparmor profile in his patch08:54
-queuebot:#ubuntu-release- Unapproved: kopanocore (disco-proposed/universe) [8.7.0-2ubuntu1 => 8.7.0-2ubuntu2] (no packageset)08:54
* Laney pats xnox 08:57
juliankLocutusOfBorg: hmm, does the profile not include <abstractions/python>08:58
juliankI mean, that's why it exists08:58
juliankit does contain08:58
juliank  /usr/lib{,32,64}/python3.[0-9]/lib-dynload/*.so            mr,08:58
LocutusOfBorgit does include yes08:58
juliankbut then it should just work08:59
LocutusOfBorgyou right09:00
LocutusOfBorgI got it09:00
juliankshould I rerun that and ssh into it afterwards to see the dmesg?09:00
LocutusOfBorgapparmor issue09:00
LocutusOfBorgmmm no09:00
-queuebot:#ubuntu-release- Unapproved: rejected mariadb-10.1 [source] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]09:01
infinityLocutusOfBorg: On my local machine, I got an entirely different failure when running it.  Something to do with python3-magic. :P09:06
infinityLocutusOfBorg: Are you testing any of these uploads, or just stabbing wildly in the dark?09:08
LocutusOfBorgon my ppa09:09
LocutusOfBorgbut I'm having troubles running tests...09:09
LocutusOfBorgfor some reasons this link doesn't work https://autopkgtest.ubuntu.com/request.cgi?release=disco&arch=amd64&package=kopanocore&ppa=costamagnagianfranco/locutusofborg-ppa&trigger=kopanocore/8.7.0-2ubuntu409:09
LocutusOfBorgis autopkgtestsuite having a sad day?09:10
LocutusOfBorgif I put a wrong ubuntu3 version on the above link it answers "that version is not published in your ppa"09:11
LocutusOfBorgand meh, my link should be good09:11
juliankAgain, if needed I can retrigger the autopkgtest and then ssh into it to debug why it failed09:14
LocutusOfBorgyes please :)09:14
juliankbecause so far, the fix attempts do not seem to make much sense09:14
LocutusOfBorgnone of them, even the ubuntu1 version...09:15
infinityIndeed, I think doko's "fix" was misguided, but yours have been following down the same path so far. :)09:16
infinityCan you not reproduce locally and iterate?09:16
LaneyLocutusOfBorg: should be fixed09:16
LocutusOfBorgI'm not able to...09:16
Laneyplease try, I didn't want to click your link for you09:17
LocutusOfBorgit worked09:17
infinity^-- He means request.cgi09:17
juliankI'm running the test manually now with --shell-fail09:17
LocutusOfBorgthanks Laney I updated #launchpad to tell that :)09:17
LaneyDunno why, but rabbitmq had fallen over with no apparent output09:18
juliankI don't feel like it does anything, but I might be wrong09:20
LocutusOfBorgis "sudo autopkgtest-build-lxc ubuntu disco" still the correct command to run?09:20
juliankdon't you want to use lxd?09:21
juliankor a VM?09:21
LocutusOfBorg"autopkgtest-build-lxd images:ubuntu/disco/amd64"09:21
LocutusOfBorgis this still the correct command to run?09:21
LocutusOfBorgjuliank, if you have a link to the docs I'm happy to follow them, the commands I used in the past (artful) don't work anymore09:22
juliankI think ubuntu-daily:disco is nicer?09:22
juliankBut the infra certainly uses the VMs09:22
juliankthat is, autopkgtest-buildvm-ubuntu-cloud09:22
-queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (bionic-proposed) [237-3ubuntu10.21]09:23
LocutusOfBorgjuliank, so just a "sudo autopkgtest-buildvm-ubuntu-cloud"?09:23
LocutusOfBorgand then, how I run a local test on that package?09:23
juliank-r disco, probably09:24
juliankit generates an .img file09:24
rbalintLocutusOfBorg, -- qemu ~/.img/autopkgtest-disco-amd64.img09:24
juliankyou then do autopkgtest <dsc/package name> -- qemu <img file>09:24
* Laney is a bit concerned that LocutusOfBorg is only right now learning this09:25
LocutusOfBorgLaney, it didn't work and I started using the Ubuntu infra for this, and usually an sbuild/pbuilder chroot works just nicely, with manual test triggering09:25
rbalintLaney, our infra works so well you don't need to know how to run tests locally ;-)09:25
LocutusOfBorgI usually look at the debian/tests content, and run it manually09:25
LaneyYou could say that for test builds too09:25
Laneybut I assume it's considered best practice for people to do those...09:26
LocutusOfBorgbtw usually failures are not on amd64, so I have to know anyway how to run them on the infrastructure09:26
LocutusOfBorgLaney, trust me, I failed to find documentation for that... I'm sure there is, but I can't find it09:26
LocutusOfBorgthis is the best page I found so far, based on what you told me before09:26
julianktest is running now09:28
juliankand it worked fine09:28
juliankLocutusOfBorg: Looking at the test, this was from over a month ago, and all tests since then have passed09:28
rbalintLocutusOfBorg, http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test is a good place to start imo09:28
LocutusOfBorgrbalint, sad that google doesn't return that page...09:29
LocutusOfBorgI googled "ubuntu autopkgtest wiki" and the results don't help09:29
juliankhmm, got kopano 8.7.0-109:29
LocutusOfBorgthis is what is returned09:30
* juliank used wrong commandline09:30
julianklet's try again09:31
juliankfrom this https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/k/kopanocore/20190304_165158_f8fa9@/log.gz09:31
rbalintLocutusOfBorg, google knows me :-) i also looked for "autopkgtest local reproduce"09:32
-queuebot:#ubuntu-release- Unapproved: accepted openldap [source] (cosmic-proposed) [2.4.46+dfsg-5ubuntu1.2]09:37
julianktest's about to run09:37
juliankAttributeError: /usr/bin/python3: undefined symbol: magic_open09:38
juliankis the error now09:38
juliankalso seeing a09:38
juliank[   42.630778] audit: type=1400 audit(1555407497.911:45): apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search" name="/usr/sbin/ldconfig" pid=2746 comm="kopano-search" requested_mask="x" denied_mask="x" fsuid=0 ouid=009:38
juliankand [   42.629021] audit: type=1400 audit(1555407497.911:42): apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search" name="/usr/bin/x86_64-linux-gnu-ld.bfd" pid=2745 comm="kopano-search" requested_mask="x" denied_mask="x" fsuid=0 ouid=009:39
julianksetting the profile to complain makes it work09:40
infinityjuliank: Yeah, the magic_open failure is what I got locally too.09:40
juliankSo I guess it needs09:41
juliank/usr/sbin/ldconfig x,09:41
juliank/usr/bin/x86_64-linux-gnu-ld.bfd x,09:41
juliankwith some proper flags09:41
juliankbut not entirely sure why09:41
infinityWhy is it running ldconfig?  And why on earth is it running ld?09:42
juliank[   42.579760] audit: type=1400 audit(1555407497.859:38): apparmor="DENIED" operation="open" profile="/usr/sbin/kopano-search" name="/usr/sbin/" pid=2743 comm="kopano-search" requested_mask="r" denied_mask="r" fsuid=0 ouid=009:42
juliankinfinity: that's a good question09:42
infinity[119697.987051] audit: type=1400 audit(1555405334.972:218): apparmor="DENIED" operation="mkdir" profile="/usr/sbin/kopano-search" name="/usr/lib/python3/dist-packages/magic/__pycache__/" pid=15645 comm="kopano-search" requested_mask="c" denied_mask="c" fsuid=1000 ouid=100009:42
infinityOh python, you special.09:42
infinityI also see it attempting to run GCC in my ringbuffer.09:43
juliankI did not see that09:43
infinity[119698.000187] audit: type=1400 audit(1555405334.985:222): apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search" name="/usr/bin/x86_64-linux-gnu-gcc-8" pid=15647 comm="kopano-search" requested_mask="x" denied_mask="x" fsuid=1000 ouid=009:43
julianksome ctypes module?09:44
juliankor something like that09:44
juliankidk how that works09:44
infinityNot sure I see the value in attempting to make this migrate.09:46
infinityAlso puzzled that -1 still works and -2 is a miserable failure.09:47
juliankBut yes, "python -c "import magic"" definitely executes ldconfig09:47
juliank[pid 27144] execve("/sbin/ldconfig", ["/sbin/ldconfig", "-p"], 0x7f107a741ab0 /* 2 vars */) = 009:47
juliankIf I make ldconfig fail, it fails09:48
juliankit then falls back to gcc and ld09:48
juliankso all we need in the profile is to allow ldconfig, really09:48
LocutusOfBorgwhy on earth is -1 happy?09:48
LocutusOfBorgoh got it09:49
juliankprofile broken -> ignored09:49
ubot5`Ubuntu bug 1824103 in linux (Ubuntu) "aplay record file failed always." [Critical,Incomplete]09:50
willcookeinfinity, ^09:50
juliankLocutusOfBorg: should try reproducing this in Debian with AppArmor and then checking that it fails there and report an important (RC?) bug09:50
juliankinfinity: So the profile in -1 is not applied due to missing comma, and it thus works; and now the profile is applied, and it fails to execute ldconfig09:51
juliankwhich means that -1 is less safe than -2 :D09:51
juliankI wonder if adding ldconfig Ix would be OK09:52
juliankI tried adding it, but I had no job control, and then pressed Ctrl+C, and it ended my shell...09:52
infinityjuliank: Ahh.  So updating -2 to warn would not be a regression over -1. :P09:53
juliankThe fix is to set it to complain, run kopano-search --help09:55
juliankthen run aa-logprof to update the profile09:55
juliankand then cleanup formatting again :D09:55
juliank  /sbin/ldconfig Pix,09:56
juliankis what doko added to the profile09:56
juliankah and that fails because usr is merged?09:57
juliankit needs to be {,/usr}/sbin/ldconfig09:57
juliankor maybe it was there before09:58
juliankanyhow, needs to account for /usr09:58
-queuebot:#ubuntu-release- Unapproved: util-linux (xenial-proposed/main) [2.27.1-6ubuntu3.6 => 2.27.1-6ubuntu3.7] (core)09:59
xnoxjuliank, yes.10:01
juliankSo, I built a package with that change10:02
juliankI'll run autopkgtest on it, and upload it if it works fine10:02
juliankif only apparmor would follow (some) symlinks when loading the profile10:03
xnoxlooks good10:04
LocutusOfBorgjuliank, please also drop the patch10:05
LocutusOfBorgfrom doko10:05
-queuebot:#ubuntu-release- Unapproved: ruby-concurrent (disco-proposed/universe) [1.0.5-2ubuntu1 => 1.0.5-3] (no packageset) (sync)10:07
-queuebot:#ubuntu-release- Unapproved: ruby-oauth2 (disco-proposed/universe) [1.4.1-1ubuntu1 => 1.4.1-2] (no packageset) (sync)10:08
juliankLocutusOfBorg: I will, after verifying the change10:08
juliankx86_64-linux-gnu-g++: fatal error: Killed signal terminated program cc1plus10:17
juliankwell, that's not what I expected10:17
juliankbut let's give it 8 gigs of ram instead of 110:18
juliankI gave it 4 cores to compile with10:18
juliankso it ran out of memory I guess10:18
juliank1 GB RAM for your autopkgtest vm is not a sensible default10:19
juliank1 GB * CPU core might be10:19
juliankwell, if it has to build the package10:19
* juliank does have 24 gig of ram, so I don't really care about giving 8 of that to the VM10:19
-queuebot:#ubuntu-release- Unapproved: accepted ruby-concurrent [sync] (disco-proposed) [1.0.5-3]10:20
-queuebot:#ubuntu-release- Unapproved: accepted ruby-oauth2 [sync] (disco-proposed) [1.4.1-2]10:20
-queuebot:#ubuntu-release- Unapproved: rejected kopanocore [source] (disco-proposed) [8.7.0-2ubuntu2]10:21
juliank4 cores, 8 threads; 24 gigs of ram10:21
infinityjuliank: 2G/thread is my usual go-to for C++.10:21
infinityBut 1G/thread is closer to what we do in the DC, I believe.10:21
infinityNot positive now.10:21
juliankif you told me in like 2010 that I'd have that in my laptop in 2019 (or 2018 when I got it), I'd have been totally amazed10:22
rbalintjuliank, i'm most impressed my nvme's speed10:23
juliankthat's nice too10:23
infinityjuliank: My modest desktop has 64G of RAM, and my brother reminded me that the "killer dual socket PPro workstation" we built in 1996 had 64MB.10:23
juliankI don't think I could deal well with multiple machines10:24
juliankhence I'm on a laptop all the time10:24
infinityI live most of my life on laptops, but the desktop is much more comfortable for gaming.10:24
juliankI don't want to know what my first desktop had10:25
infinityAnd desktop parts are cheap enough that it's not really a big deal building one that's pupose-built just for fun.10:25
juliankI only remember was an athlon10:25
infinityWow, you're young.10:25
infinityI got my first Athlon 750 free at an AMD preview event in 1999.  It was the best thing EVER.10:26
infinityAnd I was 22.10:26
juliankI think I got it like 2001/2002 with XP10:27
juliankprior to that we only had one family computer10:27
juliankit came with Windows 98 SE10:28
infinityThat was also in the dark period when Intel and AMB both briefly thought that cartdiges were a good form-factor for CPUs.10:28
infinityAlso, cartridges.  Typing is hard.10:28
juliankMy dad also had a laptop with Windows ME if I'm not mistaken10:28
juliankOh, before that we had some other thing10:28
rbalintLaney, does autopkgtest not pick up unattended-upgrades ubuntu5 or i'm not patient enough?10:29
LaneyI just had to make do with a copy of Turing's thesis.10:29
Laneyrbalint: check https://people.canonical.com/~ubuntu-archive/proposed-migration/log/ ?10:29
juliankI don't know if it was an Atari or an Amiga10:29
juliankor something like that10:29
juliankand there was another DOS/Windows < 3.1 machine10:30
juliankI fried that one by turning the switch to 110V on our 230V system10:31
-queuebot:#ubuntu-release- Unapproved: redmine (disco-proposed/universe) [4.0.1-1 => 4.0.1-2] (no packageset) (sync)10:31
julianktar: ./debian/build/ECtools/archiver/helpers/.libs/StoreHelper.o: Wrote only 8192 of 10240 bytes10:31
juliankhmm, I don't have any lucj10:31
juliankjust running out of space trying to build kopanocore10:32
juliankand the other qemu seems stuck too10:32
juliank   dh_dwz -O--builddirectory=debian/build10:33
juliankand nothing after that10:33
-queuebot:#ubuntu-release- Unapproved: gitaly (disco-proposed/universe) [0.129.0+debian-3 => 1.20.0+debian-1] (no packageset) (sync)10:34
-queuebot:#ubuntu-release- Unapproved: golang-gitaly-proto (disco-proposed/universe) [0.123.0+dfsg-2 => 1.14.0+dfsg-2] (no packageset) (sync)10:35
-queuebot:#ubuntu-release- Unapproved: golang-google-cloud (disco-proposed/universe) [0.9.0-9 => 0.9.0-10] (ubuntu-mate) (sync)10:37
LocutusOfBorgthis should fix some golang packages migration ^^10:37
LocutusOfBorgdamn ubuntu-mate why did you seed it10:37
rbalintLaney, thanks, it says pending - there is a lot pending :-(10:38
LaneyMaybe they got fubared when rabbitmq died earlier10:38
Laneylemme see10:38
juliankBuilding in https://launchpad.net/~juliank/+archive/ubuntu/kopanocore now10:41
juliankI do remember this joystick: https://www.c64-wiki.de/images/a/aa/Competition_pro_blau.jpg10:47
juliankbut that does not help figuring out which machine it was back then10:48
juliankmust have been mid 90s, and like 5-10 years old10:49
juliank(the machine that is)10:49
rbalintLaney, thanks!10:53
Laneythere you go10:55
LaneyI skill shared the process to infinity :>10:55
juliankLaney: It worked!11:23
juliankLocutusOfBorg: It worked!11:23
-queuebot:#ubuntu-release- Unapproved: spirv-llvm-translator (disco-proposed/universe) [8.0.0+git20190314-0ubuntu1 => 8.0.0+git20190314-0ubuntu2] (no packageset)11:24
-queuebot:#ubuntu-release- Unapproved: kopanocore (disco-proposed/universe) [8.7.0-2ubuntu1 => 8.7.0-2ubuntu2] (no packageset)11:25
juliankLocutusOfBorg: Uploaded and forwarded to Debian11:27
juliankfwded to debian bug 92721511:29
ubot5`Debian bug 927215 in kopanocore "kopano-search: AppArmor profile does not account for usrmerge" [Serious,Open] http://bugs.debian.org/92721511:29
=== s8321414_ is now known as s8321414
-queuebot:#ubuntu-release- Unapproved: ukui-control-center (disco-proposed/universe) [1.1.7-0ubuntu1 =>] (ubuntukylin)11:39
=== RAOF is now known as Guest94052
-queuebot:#ubuntu-release- Unapproved: accepted kopanocore [source] (disco-proposed) [8.7.0-2ubuntu2]11:58
-queuebot:#ubuntu-release- Unapproved: accepted spirv-llvm-translator [source] (disco-proposed) [8.0.0+git20190314-0ubuntu2]11:58
infinityhandsome_feng: Your ukui-control-center breaks the indentation of the g_timeout_add() call.  Did you want to undo that so it's still readable?12:01
-queuebot:#ubuntu-release- Unapproved: accepted gitaly [sync] (disco-proposed) [1.20.0+debian-1]12:01
-queuebot:#ubuntu-release- Unapproved: accepted golang-google-cloud [sync] (disco-proposed) [0.9.0-10]12:01
-queuebot:#ubuntu-release- Unapproved: accepted golang-gitaly-proto [sync] (disco-proposed) [1.14.0+dfsg-2]12:01
-queuebot:#ubuntu-release- Unapproved: accepted redmine [sync] (disco-proposed) [4.0.1-2]12:01
xnoxinfinity, may i upload casper?12:03
infinityxnox: Depends why.12:03
xnoxinfinity, systemd-sysusers fails to start on overlayfs /, because it doesn't like .pwd.lock file resulting in non-quiet & degraded live-session boot12:04
xnoxwith ugly messages on boot, on e.g. subiquity-live server image12:04
infinityxnox: What's the proposed fix for this?12:04
xnoxrm /root/.pwd.lock; touch /root/.pwd.lock; touch /root/etc/passwd; touch /root/etc/passwd-12:05
xnoxinfinity, i.e. ensure all three are "on the upper layer"12:05
xnoxaka safe fs, cause systemd cares12:05
handsome_fenginfinity: oh, Sorry, I didn't notice that, can you reject that and I will adjust the format12:06
infinityxnox: Does this start before we create the ubuntu user (cause that should pull passwd up to the top layer)12:06
infinityhandsome_feng: Done.12:06
handsome_fenginfinity, Thanks!12:06
xnoxwe do: chroot /root /usr/lib/user-setup/user-setup-apply > /dev/null12:06
xnoxso yeah, the passwd files should be in the upper layer already. let me double check things again, by rebooting with break-bottom again.12:07
-queuebot:#ubuntu-release- Unapproved: rejected ukui-control-center [source] (disco-proposed) []12:07
xnoxsystemd-sysusers sees i/o error and ???? in ls -a /etc/.pwd.lock file12:07
infinityxnox: I don't see why it would be seeing I/O errors there...12:08
xnoxthere are other errors too12:08
xnoxinfinity, http://people.canonical.com/~xnox/casper-bottom.png12:10
xnoxcause like subiquity has no display-manager, and like probably not enough of polkit-1 stuff12:10
xnoxcause enodesktop12:10
mwhudsonthose squashfs errors are faaaiiirly new12:11
infinitySo some of that stuff needs [ -d ] and [ -f ] guards?12:11
mwhudsoneep need to be asleep12:11
xnoxmwhudson, yes, came with like v5 kernel. i do want kernel people to look at it... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182440712:12
ubot5`Ubuntu bug 1824407 in linux (Ubuntu) " why does booting any livefs squashfs has kernel complaining about unable to read metadata something rather" [Undecided,Incomplete]12:12
xnoxinfinity, so .pwd.lock passwd passwd- are all in upper12:12
infinityxnox: Okay, so... What are you proposing fixing? :P12:13
xnoxinfinity, rm /root/etc/.pwd.lock i think now12:14
* xnox digs systemd code12:14
infinity.pwd.lock is supposed to be there...12:15
xnoxinfinity, http://people.canonical.com/~xnox/pwd-lock-fail.png12:18
xnoxthat's how things look when booted.12:18
xnoxinfinity, i wonder if it is bad that we have .pwd.lock in filesystem.squashfs and our mount is lowerdir=installer.squashfs:filesystem.squashfs with an upper dir on top.12:20
xnoxfailing like everything.12:20
xnoxi wonder if livecd-rootfs should have cleaned up .pwd.lock in filesystem.squashfs12:21
xnoxinfinity, http://paste.ubuntu.com/p/NsMGVTr66Z/12:22
infinityI genuinely have no idea what that means.12:22
xnoxi wonder, if that's my squashfs errors too!12:22
infinityapw: ^12:22
apwinfinity, i think that error says "you tried to create a file over a directory of the same name and that won't work here"12:25
xnoxso rm /root/etc/.pwd.lock definately "fixes" systemd-sysusers. But it feels like a bug in rootfs ontop of multi-lower squashfs12:25
apwinfinity, or the other way round12:25
xnoxi wonder if it would help if the middle layer would have had a /etc directory or the lock file, or like if the lowest layer didn't have .pwd.lock in it.12:26
* xnox tries my fix by editing things from like break=top12:27
infinityxnox: I assume desktop ISOs don't see this?12:27
xnoxit maybe hidden by plymouth, let me check if they boot degraded or not12:27
xnox(possibly multilowerdir issue -> in which case desktop single-layer ubiquity should not be affected)12:28
apwxnox, yeah there is a directory on the lower layer and you are trying to copy-up-and-replace with a file12:28
apwxnox, so it is not clear it should not fail with ENOWAY anyhow12:28
xnoxtesting $ echo 'rm /root/etc/.pwd.lock' >> 25adduser => works like a charm, uploading casper.12:30
xnoxand can figure out what's wrong with our squashfs with apw whilst that is in progress.12:31
-queuebot:#ubuntu-release- Unapproved: ukui-control-center (disco-proposed/universe) [1.1.7-0ubuntu1 =>] (ubuntukylin)12:31
-queuebot:#ubuntu-release- Unapproved: accepted iproute2 [source] (xenial-proposed) [4.3.0-1ubuntu3.16.04.5]12:34
-queuebot:#ubuntu-release- Unapproved: casper (disco-proposed/main) [1.404 => 1.405] (desktop-core, ubuntu-server)12:34
Laneyxnox: tseliot was wanting to upload casper too, please to coordinate12:45
* xnox wishes we had an up todate repo for casper.12:46
* xnox nominates casper as a snap!12:46
Laney(rejected, pending such coordination)12:48
-queuebot:#ubuntu-release- Unapproved: rejected casper [source] (disco-proposed) [1.405]12:48
-queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [source] (disco-proposed) []12:53
xnoxtseliot, this is my diff http://launchpadlibrarian.net/419512765/casper_1.404_1.405.diff.gz12:57
tseliotxnox: sure, let me apply that, and re-upload13:03
xnoxinfinity, Laney - on my way to the office.13:06
tseliotLaney, xnox: uploaded13:15
-queuebot:#ubuntu-release- Unapproved: casper (disco-proposed/main) [1.404 => 1.405] (desktop-core, ubuntu-server)13:16
-queuebot:#ubuntu-release- Unapproved: curl (cosmic-proposed/main) [7.61.0-1ubuntu2.3 => 7.61.0-1ubuntu2.4] (core)13:20
-queuebot:#ubuntu-release- Unapproved: accepted casper [source] (disco-proposed) [1.405]13:25
cyphermoxLaney: tseliot: xnox: can we just all agree to use git-ubuntu's snapshot then?13:26
cyphermox(for next uploads)13:27
-queuebot:#ubuntu-release- Unapproved: pulseaudio (disco-proposed/main) [1:12.2-2ubuntu1 => 1:12.2-2ubuntu2] (desktop-core, ubuntu-server)13:35
LocutusOfBorgarchive admins, ushare has never appeared in Debian, and its in proposed-only since a while... can we kick it out completely, or is anybody having a look?13:35
LocutusOfBorg(is it still needed?)13:36
-queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (disco-proposed) [1:12.2-2ubuntu2]13:40
-queuebot:#ubuntu-release- Unapproved: mariadb-10.1 (cosmic-proposed/universe) [1:10.1.29-6ubuntu2 => 1:10.1.38-0ubuntu0.18.10.1] (no packageset)13:46
-queuebot:#ubuntu-release- Unapproved: pulseaudio (disco-proposed/main) [1:12.2-2ubuntu2 => 1:12.2-2ubuntu3] (desktop-core, ubuntu-server)13:58
-queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (disco-proposed) [1:12.2-2ubuntu3]14:00
=== Eickmeyer is now known as Eickmeyer___
tseliotcyphermox: I'm all for using git. I always use git when I make changes to packages. I wish casper were hosted somewhere, and that the CVS were mentioned in the debian/control file14:25
cyphermoxyeah, that's why I said that one; would just need to be listed in debian/control14:26
-queuebot:#ubuntu-release- Unapproved: rejected mariadb-10.1 [source] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]14:31
=== RAOF is now known as Guest32007
rbasakcyphermox, tseliot: casper is interesting for git-ubuntu, as it's never going to be in Debian and doesn't have an established VCS location14:34
rbasakYou could point Vcs-* to git-ubuntu, but then you wouldn't be able to have any pre-upload "holding area"14:34
rbasak(which could be fine)14:34
rbasakxnox also: ^14:35
rbasakOr if you want a holding area, that might have to be somewhere else eg. ~ubuntu-core-dev14:35
vorloninfinity, sil2100: anything you need from me today for release?14:35
infinityvorlon: All the testing ever, in about an hour.14:35
rbasakHowever you could keep that in sync with git-ubuntu's imports if you wished14:35
infinityGive or take.14:35
cyphermoxrbasak: tbh I was just interested in taking the import as a basis; and then keeping the code under ~ubuntu-core-dev.14:36
rbasakcyphermox: that would work14:36
cyphermoxinfinity: so, spins coming up?14:36
vorloninfinity: so new images currently awaiting respin? what's the critical path on that?14:36
rbasakcyphermox: it might be a little painful if you get a non-VCS upload though. But no more painful than the same for any other package maintained in VCS.14:37
infinityvorlon: casper and pulseaudio are the only triggers in proposed, the rest is migrated.14:37
cyphermoxrbasak: yeah, well, there's only so much we can do14:37
rbasakcyphermox: agreed, though my interest is: what can we do that will work and is better? :-)14:38
rbasak(for git-ubuntu and all packages generally I mean; not just casper)14:38
rbasakFinding best practice, etc.14:38
cyphermoxrbasak: ok14:39
tseliotrbasak: I don't remember ever using git-ubuntu, but I'll have a look at the docs.  Thanks14:39
rbasaktseliot: np. Sorry the docs are probably awful. It's still very experimental.14:40
rbasakFeel free to ask questions etc.14:40
tseliotrbasak: I found this: https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow14:40
tseliotbut sure, if I have any questions I will ask :)14:41
tobikochsil2100: platonical and I are contacts for cloud-image related stuff during and after the upcoming release.14:41
platonicallol beat me to it14:41
-queuebot:#ubuntu-release- Unapproved: golang-gopkg-sourcemap.v1 (disco-proposed/universe) [1.0.5-1 => 1.0.5-1ubuntu1] (no packageset)14:43
LocutusOfBorg^^ please accept the second version, I added in changelog the reference to the Debian RC bug I just opened14:46
-queuebot:#ubuntu-release- Unapproved: golang-gopkg-sourcemap.v1 (disco-proposed/universe) [1.0.5-1 => 1.0.5-1ubuntu1] (no packageset)14:46
vorlonkenvandine: hi, so, I just checked the latest disco desktop image build and I see that it's pulling in both core and core18 snaps; are we not fully transitioned to core18?14:48
sil2100tobikoch, platonical: thanks!14:48
kenvandinevorlon: we are not14:48
vorlonwell, that certainly won't help the bandwidth question any14:49
kenvandinevorlon: well all of our seeded snaps are core18 now14:49
vorlonkenvandine: what was left untransitioned?14:49
platonicalsil2100, is there an ISO respin happening now, and do you know what triggered it?14:49
kenvandinebut we didn't want to drop the core snap late in the cycle14:49
kenvandinewhich would require snapd + core18 snaps14:50
kenvandinethat hadn't been tested yet14:50
vorlonkenvandine: what is pulling in core snap?14:50
kenvandineso we're still use snapd from the core snap14:50
kenvandinecore is seeded to get snapd14:50
vorlonkenvandine: we HAVE landed changes in livecd-rootfs to pull in core18 and snapd snaps14:50
vorlonunseed that14:51
kenvandinewell maybe we aren't then :)14:51
kenvandineit was livecd-rootfs :)14:51
kenvandinegreat then14:51
vorlonright, we fixed that but something else is still pulling core in as a dep14:51
-queuebot:#ubuntu-release- Unapproved: mariadb-10.1 (cosmic-proposed/universe) [1:10.1.29-6ubuntu2 => 1:10.1.38-0ubuntu0.18.10.1] (no packageset)14:51
kenvandinecool, so that should be working then14:51
vorlonyeah, I pushed on the team to get all of that sorted out in livecd-rootfs for 19.0414:51
vorlon /so that/ we wouldn't pull in two core snaps14:52
vorlonbut the log shows we're still pulling in core, which means it's a dep of something14:52
kenvandinevorlon, willcooke: do we want to try to get gnome-3-28-1804 refreshed with the security fix for libxslt before you spin images?14:52
vorloninfinity: ^^14:52
vorlonkenvandine: (I'm not in London, I was just proxying based on earlier discussion here in channel)14:52
kenvandinemaybe gtk-common-themes?14:52
kenvandinethat doesn't have base: core1814:53
vorlonkenvandine: yes, likely14:53
kenvandineit doesn't stage packages and is arch all14:53
vorlonis that all data?14:53
vorloncould we make it base: none?14:53
kenvandinei can do a quick test of that14:53
sil2100base: none would still make it pull in core I guess14:54
vorlonsil2100: why?  does livecd-rootfs treat none specially?14:54
vorlonI thought base: none really means none :)14:54
sil2100Ah, wait, maybe not, I know that snap-tool treats the lack of base: as core, but maybe base: none will do the trick?14:54
sil2100nvm me then ;)14:54
vorlonright, or maybe it'll break the build because snap-tool /doesn't/ know how to handle base: none ;)14:55
* sil2100 tries to check that quickly14:55
sil2100I guess snap-tool will be fine14:56
vorlonsil2100, kenvandine: ok I just checked snap-tool in livecd-rootfs, and I don't see that it knows how to handle base: none14:56
vorlonit will look for it as the name of a snap to preseed14:56
vorlonwhich AIUI is incorrect14:56
sil2100Can't we switch it to base: core18 in this case? Since we anyway pull in core18 now from other snaps14:56
vorlonthat would probably be better yeah14:57
sil2100I wonder if that would be acceptable for the snap though14:57
vorlonand then we can make livecd-rootfs know about base: none at leisure14:57
kenvandinemy only concern is other snaps that aren't using core18 but are using gtk-common-themes will now suddenly pull in core1814:57
kenvandinebut that number should be low14:57
willcookekenvandine, do we have any data on that?14:58
sil2100I can quickly prepare a fix for snap-tool, but I think it's a bit lateish for fast-tracking a livecd-rootfs14:58
kenvandinei can look at stats on gtk-common-themes to see which distros have installed devices14:58
kenvandineanything bionic and newer will have core18 already installed14:59
vorlonsil2100: I'm available to review (or maybe tobikoch is better)14:59
vorlonI think we should at least start down that path even if we can't get all the way for 19.0414:59
-queuebot:#ubuntu-release- Unapproved: libxslt (disco-proposed/main) [1.1.32-2 => 1.1.32-2ubuntu0.1] (desktop-core, ubuntu-server) (sync)15:00
willcookekenvandine, ^ libxslt15:01
willcookeso I think that yes, we should try and get the platform snap updated too.  Is it a big job?15:02
willcookekenvandine, i_nfinity said that time is short for the platform snap15:04
kenvandinevorlon: the numbers are low for other distros, won't be a big impact15:06
kenvandinei can kick off a build adding core1815:06
-queuebot:#ubuntu-release- Unapproved: accepted libxslt [sync] (disco-proposed) [1.1.32-2ubuntu0.1]15:06
sil2100kenvandine, vorlon: do we have some snap in the snapstore that has base: none already?15:10
tobikochsil2100, vorlon: instead of hacking snap-tool, I would suggest special-casing "none" in _snap_preseed (live-build/functions l. 494).15:10
sil2100tobikoch: well, depending if this is a 'hack' or 'per-design'15:10
sil2100tobikoch: https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/36612415:11
sil2100tobikoch: but yeah...15:11
sil2100vorlon: is base: none a formal thing? I tried finding it somewhere in the docs, but couldn't15:11
tobikochsil2100: i'd say it is probably not15:12
tobikochsil2100: I think the change in that MP is not what we want. If base is reported as "" by snap-tool then livecd-rootfs assumes base core and pulls in core.15:13
tobikochSo we really want the hack in livecd-rootfs and maybe get this formally specified later.15:14
sil2100tobikoch: oh, ok, since I thought that the way it's done is that when base is None (so not defined), then *snap-tool*  defaults to core15:15
sil2100And that livecd-rootfs doesn't have to do anythiing when seeing base: "", because if base is "" it should not pull in anything (as that means the snap is a base snap)15:15
tobikochsil2100: that logic isn't in snap-tool. snap-tool is only used to ask the API for info about the snap including its base. The API will report "" for snaps that have base core. So livecd-rootfs treates that as having to pull in core. If you modify the snap that causes core to be pulled in to explicitly specify its base as "none", then that needs to be treated in _snap_preseed.15:16
sil2100tobikoch: wait, what about snap-tool line 207 then?15:17
sil2100tobikoch: that line basically does self.is_core_snap() and sets base to "", core snaps have no base at all through the API from what I see?15:18
willcookekenvandine, re: snap(s) needing the new xslt - what can I do to help test?15:18
sil2100tobikoch: and the next line sets "core" as the base of snaps that do not provide base at all15:19
tobikochsil2100: slow down a sec15:19
kenvandinewillcooke: refresh gnome-3-28-1804 from candidate and run the seeded snaps15:19
kenvandinemake sure they behave15:19
kenvandinei'm testing on bionic now15:19
kenvandinegtk-common-themes with base:core18 is building and should be in candidate soon15:20
kenvandinewe can verify that's sane soon15:20
kenvandinevorlon ^^15:21
tobikochsil2100: take a snap that has base "core" and ask the API which base it has, then you will get back *no result* for that attribute. So snap_data["snap"]["base"] would not be set and snap_data["snap"].get("base") would return the special None object not the string "None". So all this line does is to populate that attribute with an empty string.15:21
tobikochsil2100: but if gtk-common-themes now has core18 and that works as expected, I'd shelve the hack until this can be discussed with the snap people later. My two cents.15:22
cjwatsonsil2100: https://bugs.launchpad.net/launchpad/+bug/1819196 has links15:25
ubot5`Ubuntu bug 1819196 in Launchpad itself "support for base: none and build-base" [High,Triaged]15:25
cjwatsonmay not completely help but ...15:25
tobikochcjwatson: how is "none" reported by the API?15:26
cjwatsonWhat API?15:26
tobikochcjwatson: /v2/snaps/refresh when I ask for the "base" field to be included.15:27
cjwatsonI would assume it passes it through literally because why would we change it ...15:27
willcookekenvandine, calc chars system monitor and snap store snap all tested, seems fine to me15:28
vorloncjwatson: ah, that blog of sergiusens's discusses it being supported in "upcoming releases" of snapcraft/snapd, do you know if that's landed?15:30
cjwatsonvorlon: Don't know, sorry15:30
kenvandinewillcooke: great, all good on bionic too15:30
willcookekenvandine, oh, that was Bionic too15:30
vorlon(no harm in livecd-rootfs implementing that preemptively anyway)15:30
willcookestand by15:30
kenvandinewillcooke: oh, you tested both?15:30
cjwatsontobikoch: Right, as far as I can tell the store just passes that straight through unmodified15:31
cjwatson"none" as a string, not "None" or None15:31
cjwatson(or null)15:31
tobikochcjwatson: actually, I get Python None, not "none" (e.g. snapd see https://pastebin.canonical.com/p/9K8jnKP27v/), but I also get that for snaps that have implicit base "core" (e.g. lpshipit see https://pastebin.canonical.com/p/CKnTZFCTVJ/).15:31
cjwatsoncore isn't a real base and should result in null15:31
cjwatsondo not confuse the implicit core base with base: none15:32
cjwatsonsnapd does not have base: none15:32
cjwatsonit has no base15:33
cjwatsonnot the same thing15:33
cjwatson(I didn't come up with this, just the messenger)15:33
tobikochcjwatson: hehe, ok15:33
tobikochcjwatson: know of a snap using "none" explicitly?15:34
cjwatsonI'm not sure there are any yet15:34
willcookekenvandine, same tests run on B & D.  All fine15:34
cjwatsonlet me run a quick query15:34
cjwatsonsnaprevs_production_standby=> SELECT DISTINCT snap_id FROM snaprevision WHERE base = 'none';15:35
cjwatson snap_id15:35
cjwatson(0 rows)15:35
kenvandinewillcooke: ok, now do the same thing with gtk-common-themes from candidate :)15:35
tobikochcjwatson: thanks :)15:35
cjwatsonnp.  it's still in development I think so not too surprised15:35
cjwatsonnone on staging either15:36
infinityOr is it None on staging?15:36
* infinity ducks.15:36
sil2100"none", none or None?15:37
tobikochvorlon, sil2100: ^ so if a snap had base set to "none" explicitly, snap-tool should print base: none and we should special case livecd-rootfs to not do anything when it sees "none". So livecd-rootfs/live-build/functions line 494. Printing the empty string instead will make livecd-rootfs assume implicit "core".15:38
tobikochsil2100: 'none' see cjwatson's sql above.15:39
willcookekenvandine, tested - all good15:43
kenvandinewillcooke: thanks15:44
kenvandineall good for me too15:44
willcookekenvandine, so will you promote to stable?  Should we ping snap store first?15:45
kenvandinewillcooke: i've been talking to snapstore folks15:45
kenvandineroadmr just finished generating deltas15:45
willcookekenvandine, super thanks!15:45
kenvandinealmost ready to promote it15:46
sil2100tobikoch: no, so I disagree here - an empty string will not make livecd-rootfs assume implicit core from what I see, the empty string will only cause the check in _snap_post_process() to happen but it will result as a no-op as the snap name is not core or core1815:47
kenvandinevorlon: does livecd-rootfs only seed snapd if the core snap isn't seeded?15:47
sil2100tobikoch: but anyway, since this is not on fire right now, let's take this discussion to the MP15:47
vorlonkenvandine: yes15:47
kenvandinevorlon: i have gtk-common-themes ready with core1815:47
kenvandineshall i promote it and see what the isos look like?15:48
tobikochsil2100: yeah, you're right! I'm getting it all mixed up myself. The empty string would also do the right thing.15:48
sil2100tobikoch: I'm not saying I'm against moving the change from snap-tool to livecd-rootfs functions, I just feel it's more of a preference thing - anyway, let's discuss it further there ;)15:48
sil2100tobikoch: we can bikeshed a bit more there about it15:48
tobikochok, I'll add a comment15:48
sil2100kenvandine: yes please o/ (hoping that won't break everything)15:49
vorlonkenvandine: if you're satisfied that this doesn't have adverse impact on snaps outside of the desktop that depend on gtk-common-themes15:49
kenvandinesil2100, vorlon: done15:49
kenvandineWimpress: ^^ gtk-common-themes is now core18, should make you happy too :)15:50
sil2100kenvandine: thanks!16:02
kenvandinesil2100: np, i'm anxiously awaiting isos to test :)16:04
Laneydon't hold your breath :P16:05
infinityGo on.  Hold your breath.  I dare you.16:06
-queuebot:#ubuntu-release- Unapproved: gedit (disco-proposed/main) [3.32.0-2 => 3.32.0-3] (ubuntu-desktop)16:28
sil2100kenvandine: hey, ummm16:32
sil2100kenvandine: so16:32
sil2100kenvandine: is it possible that you could revert your gtk-common-themes change ;p ?16:33
sil2100kenvandine: we just learned from the snapd team that we *need* to have core right now *anyway*16:33
sil2100kenvandine: since even if none of the snaps use core as its base, we've been told we *anyway* need the core snap because of some bugs in the snapd snap16:34
sil2100willcooke: ^16:34
sil2100infinity: ^16:34
willcookedo we need to revert though? Can we seed it?16:35
sil2100willcooke: we could seed it, but vorlon said he'd prefer to revert the change instead16:36
infinityWhy do we need core?16:37
infinityYo dawg, we heard you like root filesystems.16:37
sil2100infinity: yeah, we need to have 2 base systems shipped on disco now, yay16:37
infinityI kinda feel like if we need core anyway, we shouldn't have anything using 18 yet. :/16:37
infinityOh well.16:37
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.18.0-1016.16~18.04.1] (kernel)16:37
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (cosmic-proposed/main) [4.18.0-1016.16] (kernel)16:37
sil2100infinity: yeah, it seems to have been a miscommunication somewhere16:38
sil2100A big one16:38
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.18.0-1016.16~18.04.1]16:38
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1016.16]16:38
vorloninfinity, willcooke: yes, it seems that there are bugs that prevent snapd+core18 from being sufficient on a classic desktop system, so we still have to pull in core for now. I think reverting gtk-common-themes is the best option for now16:44
infinityvorlon: Right, and I think that also means we don't want the snapd snap yet.16:45
vorlonand core 19.04 the snapd team is supposed to remove the need for core snap16:45
infinitySince we'll have snapd from core.16:45
sil2100vorlon: per infinity's question here, I guess it'd be good to actually remove the logic that pulls in snapd16:45
vorloninfinity: right, and I believe tobikoch's code is smart enough to figure this out16:45
infinityIs it?  Kay.16:45
infinityIf core is there, it won't snapd?16:45
vorlonthe log shows snapd snap being seeded to go along with core18, but it later un-seeds it again once core is pulled in16:45
-queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (disco-proposed/main) [3.32.1-1ubuntu2 => 3.32.1-1ubuntu3] (ubuntu-desktop, ubuntugnome)16:45
sil2100Ah, good!16:45
vorlonyou should check the iso contents to confirm16:46
willcookekenvandine will be back in about 20 mins.16:47
-queuebot:#ubuntu-release- Unapproved: accepted gnome-initial-setup [source] (disco-proposed) [3.32.1-1ubuntu3]16:49
platonicalvorlon, sil2100, I'm about to respin Disco bc I need to pull in a lxd fix. Is there anything else I should be waiting for?16:59
sil2100platonical: so there's still a few packages that we're waiting to migrate before re-spinning17:01
platonicalsil2100, ok, do you know how long you expect that to take?17:01
vorlonsil2100: which packages? casper should be migrated; do cloud images care about pulseaudio?17:03
vorlonseeded-in-ubuntu says no17:04
vorlonlibpulse0 is in ubuntu-server daily17:04
vorlon.. which should only be the apt repo, not the server seed17:04
vorlonso that's ok17:04
vorlonbut libxslt is a security fix and is on the server live seed17:06
sil2100vorlon: we also have libxslt which is seeded in server, but on the other hand I indeed don't know what's up17:07
vorlonplatonical: ^^ sounds like that's the blocker17:07
sil2100*what's up with that17:07
vorlonis someone poking at asterisk/i386 autopkgtest failure?17:07
platonicalvorlon, sil2100, ok thanks. ETA on that?17:07
sil2100platonical: the tests are running, I'd suppose they won't take much longer, most are finished17:08
vorlonplatonical: once the autopkgtest results have finished and are all green on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libxslt , plus ~20minutes17:08
vorlon(sorry, I don't have a good way to estimate completion of autopkgtests at a glance)17:08
platonicalok thanks17:08
vorlonuh libreoffice is in there17:09
vorlonwe should probably skip waiting for libreoffice test results :P17:09
vorlonor else make the call to have this as a zero-day security update17:11
sil2100vorlon: ok, so infinity will skip some tests for it to migrate soonish17:16
sil2100vorlon: and I just confirmed that on the last image (which had both core18 and core) no snapd snap has been preseeded, so it's working as expected indeed17:22
infinityvorlon: Yeah, I skipped the rest of libxslt tests, it's tested enough.17:23
kenvandinesil2100: done17:27
infinityAnd I'm going to build images as soon as kenvandine gets his thingee reverted.17:27
infinitysil2100: Oh, was that "done" for the revert?17:28
infinitySo, I guess I'm waiting on britney, not Ken. :P17:28
kenvandineyup :)17:32
* infinity waits impatiently for gnome-initial-setup to publish.18:34
infinityGuess I can start on base and server.18:34
-queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Disco Final] has been updated (20190416.1)18:50
-queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Disco Final] has been updated (20190416.1)19:09
-queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Disco Final] has been updated (20190416.1)19:09
-queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Disco Final] has been updated (20190416.1)19:09
-queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Disco Final] has been updated (20190416.1)19:09
-queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Disco Final] has been updated (20190416)19:15
-queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Disco Final] has been updated (20190416)19:17
-queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Disco Final] has been updated (20190416)19:18
-queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Disco Final] has been updated (20190416)19:20
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Disco Final] has been updated (20190416)19:20
bdmurrayfossfreedom: Having a link to the errors bucket in bug 1824229 would be helpful so that SRU team members can know what you are talking about.19:21
ubot5`bug 1824229 in budgie-desktop (Ubuntu Cosmic) "[SRU] Cherrypick bug-fixes and usability issues for budgie-desktop" [Medium,In progress] https://launchpad.net/bugs/182422919:21
fossfreedombdmurray, ok19:21
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Disco Final] has been updated (20190416)19:22
-queuebot:#ubuntu-release- Unapproved: libsodium (xenial-updates/universe) [1.0.8-5 => 1.0.8-5] (kubuntu) (sync)19:22
-queuebot:#ubuntu-release- Unapproved: accepted libsodium [sync] (xenial-updates) [1.0.8-5]19:24
-queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Disco Final] has been updated (20190416)19:26
-queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Disco Final] has been updated (20190416)19:41
-queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi3 [Disco Final] has been updated (20190416)19:43
-queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Disco Final] has been updated (20190416)19:43
-queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi3 [Disco Final] has been updated (20190416)19:43
Eickmeyerinfinity: I'm assuming we'll be seeing a new RC email soon?19:48
* valorie is waiting to link to it19:49
cyphermoxrcj: any idea about maas streamed images, if they're RC?19:55
bdmurrayfossfreedom: given that there already is a bug for "Issue 1" in bug 1824229 why didn't you just use that? As an SRU team member its complicated for me to track multiple issues in one bug report.20:06
ubot5`bug 1824229 in budgie-desktop (Ubuntu Cosmic) "[SRU] Cherrypick bug-fixes and usability issues for budgie-desktop" [Medium,In progress] https://launchpad.net/bugs/182422920:06
bdmurrayfossfreedom: for me to verify that the sru verification was done properly I'm going to have to look through the bug with a mental checklist of all 4 issues and look for verification of each part which is a pain20:07
rcjcyphermox: I'll defer to platonical as he's tracking release20:09
vorlonEickmeyer, valorie: I don't assume that a respin of RC images results in a new email20:09
platonicalrcj, cyphermox, what's RC?20:09
EickmeyerRC = Release Candidate20:10
Eickmeyervorlon: Thanks20:10
cyphermoxplatonical: yeah, I mean, if I deploy disco on a machine from MAAS, am I testing anything useful?20:13
cyphermoxin case I can check off some test on the drive-by20:13
platonicalcyphermox, there's currently a 20190416.1 disco build in progress, that will probably be better to test than 20190416, as we've pulled in some essential fixes20:15
-queuebot:#ubuntu-release- Unapproved: rejected containerd [source] (cosmic-proposed) [1.2.6-0ubuntu1~18.10.1]20:15
-queuebot:#ubuntu-release- Unapproved: rejected containerd [source] (bionic-proposed) [1.2.6-0ubuntu1~18.04.1]20:16
rcjcyphermox: missing from 20190416 is an apparmor fix needed for lxd20:17
cyphermoxwhat I have here appears to be snapshot-20190416-193741 right nw20:18
cyphermoxthat's probably 16, not 16.120:18
cyphermoxI guess I answered my own question, this is the right ballpark timestamp to be testing very recent images20:19
platonicalcyphermox, I don't follow the snapshot syntax, where are you getting that from?20:21
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Disco Final] has been updated (20190416.2)20:24
cyphermoxplatonical: straight from the filesystem on a MAAS rack server; in /var/lib/maas/boot-resources20:39
platonicalcyphermox: ah. well I can let you know when 20190416.1 is finished building if you like20:41
cyphermoxnah, it's fine, I'll watch what's on disk and in the logs20:41
cyphermoxit seems to be updating quickly enough20:41
fossfreedombdmurray, hmm - ok.  I can divide each issue into separate issue reports if that helps.20:51
bdmurrayfossfreedom: I think it really would but I'm just one member of the team. Its possible somebody could disagree with me but I'd be surprised. :-)20:53
fossfreedombdmurray, don't really mind.  Can you please reject the bionic and cosmic uploads so that I can reupload with the new issue numbers?20:54
bdmurrayfossfreedom: thanks, that'll help and sure I'll do the reject.20:58
-queuebot:#ubuntu-release- Unapproved: rejected budgie-desktop [source] (cosmic-proposed) [10.4+git20180830.02.f2dbc215fdb-2ubuntu0.2]21:03
-queuebot:#ubuntu-release- Unapproved: rejected budgie-desktop [source] (bionic-proposed) [10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2]21:04
-queuebot:#ubuntu-release- Unapproved: budgie-desktop (bionic-proposed/universe) [10.4+git20171031.10.g9f71bb8-1.2ubuntu1.1 => 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2] (personal-fossfreedom, ubuntu-budgie)22:04
-queuebot:#ubuntu-release- Unapproved: budgie-desktop (cosmic-proposed/universe) [10.4+git20180830.02.f2dbc215fdb-2ubuntu0.1 => 10.4+git20180830.02.f2dbc215fdb-2ubuntu0.2] (personal-fossfreedom, ubuntu-budgie)22:05
-queuebot:#ubuntu-release- Unapproved: tzdata (bionic-proposed/main) [2018i-0ubuntu0.18.04 => 2019a-0ubuntu0.18.04] (core)22:12
-queuebot:#ubuntu-release- Unapproved: tzdata (cosmic-proposed/main) [2018i-0ubuntu0.18.10 => 2019a-0ubuntu0.18.10] (core)22:13
-queuebot:#ubuntu-release- Unapproved: tzdata (xenial-proposed/main) [2018i-0ubuntu0.16.04 => 2019a-0ubuntu0.16.04] (core)22:19
-queuebot:#ubuntu-release- Unapproved: tzdata (trusty-proposed/main) [2018i-0ubuntu0.14.04 => 2019a-0ubuntu0.14.04] (core)22:24
=== Guest32007 is now known as RAOF
-queuebot:#ubuntu-release- Unapproved: gnome-software (disco-proposed/main) [3.30.6-2ubuntu3 => 3.30.6-2ubuntu4] (ubuntu-desktop)23:19
-queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Disco Final] has been marked as ready23:57

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