[00:03] <kai^sds> for the record: my bug had already been reported as #548652
[00:53] <ddecator> i tried to add my bugday to the fridge calendar, but it won't let me login o.o
[00:56] <micahg> ddecator: you don't log in, and why should it go on the fridge calendar?
[00:57] <ddecator> micahg: that's what it says to do on the wiki, haha
[00:57] <micahg> ddecator: fridge calendar or fridge post?
[00:58] <ddecator> micahg: at the bottom of the page: https://wiki.ubuntu.com/UbuntuBugDay/Organizing
[01:00] <micahg> ddecator: the wiki instructions say how to add a calendar, you have to follow the link
[01:01] <ddecator> micahg: i did, then when trying to login, i can't, it just refreshes the page
[01:01] <micahg> ddecator: login where?
[01:01] <micahg> ddecator: you log into your own google account
[01:02] <ddecator> ok, i think i get what i need to do now..
[03:59] <Damascene> any one know about this?
[03:59] <Damascene> http://uppix.net/8/d/6/2fb857359fee9b0fcaf988d043f09.png
[03:59] <Damascene> text is showing as ???? for Arabic files from windows user
[03:59] <Damascene> Arabic files name
[05:23] <Damascene> every time I start my system it needs to report kernel problem
[05:23] <Damascene> any way when I try to do so it takes ages to upload the report
[08:43] <BUGabundo_remote> the tuggs say Hi
[09:17] <jibel> vish, hey,
[09:19] <jibel> vish, you've set bug 529847 as dup of 52630 but I think they are different.
[09:19] <ubot4`> Launchpad bug 529847 in synaptic (Ubuntu) (and 1 other project) "Reload Package prompt gives up when another Synaptic is running (dup-of: 52630)" [Undecided,New] https://launchpad.net/bugs/529847
[09:19] <ubot4`> Launchpad bug 52630 in synaptic (Ubuntu) (and 1 other project) "Retry option for database lock situations (affects: 1) (dups: 1) (heat: 16)" [Wishlist,Triaged] https://launchpad.net/bugs/52630
[09:34] <vish> oh , he's not here..
[09:36] <BUGabundo_remote> ZOMG SO TRUE http://xkcd.com/727/
[09:36] <BUGabundo_remote> hi vish
[09:36] <BUGabundo_remote> saw my last batch of photos
[09:36] <BUGabundo_remote> ?
[09:37] <vish> BUGabundo_remote: hey,  which ones?
[09:37] <BUGabundo_remote> from last weekend
[09:37] <BUGabundo_remote> last days of vacations
[09:40] <alvin> I want to file a bug against the upgrade to Lucid. (Lucid changes lvm fstab entries to UUID) Against what package do I file it?
[09:41] <persia> I've had boot work with UUID LVM entries, although I agree it's less intuitive.  Are you sure it's really a bug?
[09:41] <alvin> Yes, because snapshots have the same UUID as their parent. I ended up with a snapshot of /home mounted on /home
[09:42] <persia> Oh, good point.  I don't happen to snapshot any of my boot-essential drives.
[09:42] <alvin> I needed to remove all snapshots in order to boot properly.
[09:42] <persia> Or edit /etc/fstab
[09:42] <alvin> Well, a snapshot of /root could come in handy sometimes. Previously, fstab entries where changed to UUID, except for LVM. I don't know why that changed.
[09:42] <vish> jibel_: hi.. 529847 starts off and title probably needs an update but the reporter wants a retry button essentially
[09:43] <alvin> So, what package is responsible?
[09:43]  * persia is looking
[09:43] <vish> starts off differently*
[09:43] <persia> I don't think it's just lucid though.  I think that happened to me for a jaunty->karmic upgrade as well.
[09:44] <alvin> On a fresh install of karmic /dev/mapper/... is used. I'm sure about that. Let me check a Jaunty
[09:45] <alvin> Hmm, you are right. Fresh install is /dev/mapper. Upgrade (also to Jaunty) changes to UUID
[09:46] <persia> So it's just a general bug, rather than an upgrade bug.
[09:46] <alvin> Yes, then this must have been the first time I upgraded a system with existing snapshots
[09:46] <persia> Unfortunately grep -n fstab /var/lib/dpkg/info/* didn't show me anything that looked like a postinst that would be doing that.
[09:47] <persia> So I've no idea which package needs fixing.  I'd definitely like to "me too" the bug though: it's annoying to try to figure out what is where by UUID when I'm using LVM anyway.
[09:49] <alvin> There is a bit more. (in Lucid), after I changed the entry for /home to /dev/mapper. First, /home can not be mounted, so you go into a recovery shell and type # mount /home. THen you get: mount: special device /dev/mapper/vg0-home does not exist. Then I did lvremove volumegroup/snapshotofhome. Then mount /home and voila. /home is mounted by mapper.
[09:50] <alvin> So, if there is a snapshot, the parent directory is not even found by mountall. This is probably another bug, so I'll file separately.
[09:50] <persia> Try booting into the initramfs (break=preinit I think), and see if `vgchange -a y` adds the correct entries to /dev/mapper
[09:50] <alvin> ok, I'll make a snapshot and reboot
[09:50]  * persia has two lucid systems with LVM: one boots fine, the other consistently fails to set up the /dev/mapper entries
[09:51] <alvin> There's also bug 527666 and bug 557909 if you have +4 lvm volumes
[09:51] <ubot4`> Launchpad bug 527666 in mountall (Ubuntu Lucid) (and 1 other project) "Waiting for /some/partition [SM] (affects: 26) (dups: 2)" [High,Fix released] https://launchpad.net/bugs/527666
[09:51] <ubot4`> Launchpad bug 557909 in devmapper (Ubuntu) "lucid hangs on boot because of device ownership (affects: 6) (heat: 40)" [Undecided,Confirmed] https://launchpad.net/bugs/557909
[09:53] <persia> I don't have an issue with 527666, and I have 12 volumes.
[09:53] <alvin> And are the permissions on /dev/mapper/ good?
[09:55] <persia> I have a mix of root.root and root.disk for reasons I don't entirely understand.
[09:56] <persia> And some things are just confusing.  I have a volume I use as a clean chroot for lucid/amd64 which is root.disk and another which I use as a clean chroot for lucid/i386 (created within a few seconds of the other) which is root.root.
[09:56] <alvin> That's the last bug. In Karmic, the group is always disk. In Lucid, volumes with group disk do not get mounted
[09:56] <persia> My swap is root.disk and gets used (I'm not sure "mount" is the correct term)
[09:57] <persia> Actually, my / is root.disk, and that definitely gets mounted.
[09:57] <alvin> Hmm, the new snapshot has 'disk', while the original /home has root. It does get mounted. But now /opt has disk and blocks the boot
[09:57] <alvin> Oh?
[09:57] <alvin> Tricky...
[09:57] <persia> I don't think it's the permissions.  I think it's something more subtle.
[09:58] <alvin> If it's not the permissions, it's the first bug 527666, but that one should be fixed. I always have a drive that can't get mounted, but it's not always the same.
[09:58] <ubot4`> Launchpad bug 527666 in mountall (Ubuntu Lucid) (and 1 other project) "Waiting for /some/partition [SM] (affects: 26) (dups: 2)" [High,Fix released] https://launchpad.net/bugs/527666
[09:58] <alvin> Now it's /opt again
[09:59] <jibel_> vish, but the fixes are different, that's why I would keep 2 different reports.
[09:59] <alvin> ah, after a new reboot, now my snapshot of /home is again mounted on /home
[09:59] <jibel_> vish, and a reload button is not the solution for 529847. We'd better try to reuse the running instance of synaptic.
[09:59] <alvin> So, the bug is reproducible if you reboot enough
[10:00] <persia> alvin: Except, like I said, I have >10 volumes and have never encountered it.  This is on my laptop, which is probably my most frequently rebooted device (certainly more than any of my servers or my handheld)
[10:00] <alvin> Yes, we have to find out what the difference is here.
[10:02] <alvin> This reboot I have 2 volumes that don't get mounted , but this time, the right /home is mounted.
[10:02] <alvin> i'll start out by filing the UUID bug, but I'm still not sure against what package.
[10:03] <vish> jibel_: not the reload button , he mentions "retry option" to reload , this will allow him to close synaptic running already and retry the reload from the sources dialogue..
[10:04] <jibel_> vish, yep "retry"
[10:04] <alvin> Ah, more information. If I remove the snapshot, all filesystems are mounted at boot. persia, would you like to try this? Take a snapshot of one of your filesystems and reboot?
[10:04] <vish> jibel_: but I not sure what you meant though , feel free to undup it if you want to dealt separately  :)
[10:04] <vish> s/to/it
[10:04] <persia> alvin: Erm, let me get to a good point to reboot first, but sure :)
[10:05] <alvin> persia: Thanks. I'll be here all day (quasselcore)
[10:08] <jibel_> vish, that's the point: do not close the close the running synaptic but reuse it instead.
[10:08] <jibel_> vish, thanks for your help on triaging synaptic's reports ;)
[10:11] <vish> :)
[10:11] <vish> jibel_: thats a nice idea , unduping it
[15:12] <alvin> persia: You might want to wait with the reboot. Meanwhile, I did a fresh install of Lucid server (daily)
[15:13] <alvin> Everything is fine, as long as you don't create an lvm snapshot. This time I got the grub rescue shell and needed the cd to delete the snapshot in order to boot again.
[15:13] <persia> alvin: How long should I wait?  I'm down to about 4 things to clear before I can reboot, but once I get away from the reboot goal, the list grows again :)
[15:14] <alvin> while I found another bug. You know the ubuntu-server team has taken the sensible decision to make boot messages visible? Well, errors (and plymouth's suggestions) are not visible.
[15:14] <persia> You should be able to boot in rescue mode (hold down the shift key while booting), and remove the snapshot from the initramfs
[15:14] <persia> That's a bug in the plymouth theme: which theme are you using?
[15:14] <alvin> persia: No, holding shift didn't work. I got: "Grub loading, and then immediately fd0 not found, disk not found, grub rescue>
[15:15] <alvin> no team. it's ubuntu-server (see bug 548954)
[15:15] <persia> Oh, you have a snapshot of /boot?
[15:15] <ubot4`> Launchpad bug 548954 in upstart (Ubuntu Lucid) (and 7 other projects) "Ubuntu servers should display information during boot by default (affects: 22) (dups: 2) (heat: 144)" [High,Fix released] https://launchpad.net/bugs/548954
[15:15] <alvin> No, a snapshot of some empty lvm volume I created
[15:15] <persia> Ubuntu server had better have a plymouth theme installed, even if just the text theme, or boot gets annoying.
[15:16] <persia> My servers has it, but it's an upgrade, so I'm unsure how that changes things.
[15:16] <alvin> That wouldn't be nice to people with some intel cards. A lot of servers have those and they show blank screens with a framebuffer or so I'm told.
[15:17] <alvin> Unless you are willing to take the risk and make a snapshot, I would use a spare machine. You can, however, use the cd to enter the root shell and remove the snapshot without touching the rest of your system.
[15:24] <persia> You don't need to use framebuffer.  THere's a text theme that just does text.
[15:24] <persia> I'd expect it to work on a console.
[15:25] <gnomefreak> anyone having issues with 2.6.32-20-generic+nvidia+latest gdm? i see plymouth but it never makes it to GDM restarting gdm does not work
[15:26] <micahg> gnomefreak: there were some problems with the first -20
[15:26] <gnomefreak> micahg: thanks
[15:26] <micahg> gnomefreak: is it 20.29 or 20.30?
[15:26] <persia> Those were with ACPI, and mostly affected thinkpads though.
[15:26] <gnomefreak> not sure im not on it
[15:30] <ZykoticK9> vish, regarding https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/561667 Chromium is included in the default Lucid install, and adding a single sentence to a package description which improves usability seem to me (perhaps incorrectly) like a "paper cut"
[15:31] <vish> ZykoticK9: you mean in the software store?
[15:31] <maco> it is?
[15:31] <ZykoticK9> vish, sorry not "default Lucid install" but "default Lucid repository"
[15:31] <vish> err... center
[15:31] <maco> ah ok
[15:32] <alvin> persia: I can confirm that Lucid, installed from cd lists /dev/mapper in fstab for lvm volumes, as it should be. So, it's only on upgrade that this goes wrong
[15:32] <maco> i was like "huhh?? no irefox?"
[15:32] <maco> *fire
[15:32] <ZykoticK9> sorry maco - wrong wording
[15:32] <vish> ZykoticK9: ah well , that would be just a bug in the dev release of software center, we usually dont do papercut for those too
[15:32] <persia> alvin: That matches my experience.  Did you already file this bug, or are you waiting for a package hint?
[15:33] <alvin> Waiting for the package hint actually. I have no idea what's responsible for adapting existing stuff during upgrade
[15:33] <ZykoticK9> vish, i certainly bow you your expertise in these matters (but this seems like such an easy thing to solve)
[15:33] <persia> vish: Extending papercuts also to dev releases ought result in more polished stuff on release, no?
[15:34] <persia> alvin: There's a meeting on now, but may as well ask in #ubuntu-server come the turn of the hour.
[15:34] <alvin> persia: A meeting of the server team?
[15:34] <vish> ZykoticK9: persia: then every little bug became a papercut , that was why we didnt want to include dev release bugs
[15:35] <persia> vish: Fair: still good to highlight little easy-to-fix stuff.  Lots of stuff isn't easy to fix, and can wait.
[15:35] <persia> alvin: Yep.
[15:35] <gnomefreak> micahg: linux-image-2. 2.6.32-20.30
[15:36] <alvin> persia: So, I should ask afterwards? (just informing about the protocol here)
[15:36] <ZykoticK9> vish, it certainly wasn't myself who added it to papercuts and i was unaware that papercuts don't apply to Dev releases - so sorry for bothering you with this :)  Thanks everyone in bug-squad
[15:36] <micahg> gnomefreak: hmmm, weird, anyways, I didn't reboot with -20 and am waiting for --21 to push through archvie
[15:36] <persia> alvin: I usually find team members have more time after a meeting ends then when I ask for stuff when they are in a meeting :)
[15:36] <alvin> Good point
[15:37] <vish> ZykoticK9: no worries
[15:37] <vish> ZykoticK9: persia: i agree it is easy to fix , hence i mentioned "nice catch" :)
[15:37] <persia> vish: Indeed :)
[16:02] <Damascene> Hi,
[16:02] <Damascene> some one said "on aime bien avoir une selition" on a bug
[16:02] <Damascene> what does that mean?
[16:03] <Damascene> https://bugs.launchpad.net/bugs/562130
[16:03] <ubot4`> Launchpad bug 562130 in language-selector (Ubuntu) "Selecting an RTL language should install and RTL capable terminal emulator (affects: 21) (heat: 98)" [Low,Triaged]
[16:04] <jibel_> Damascene, even in french it doesn't mean anything.
[16:04] <Damascene> :D
[16:04] <Damascene> so it's spam?
[16:06] <jibel_> no, I don't think so. rather someone lost in life.
[16:23] <micahg> plars: please note in bug next time there's no private info so as not to scare the rest of us :)
[16:24] <plars> micahg: np, I probably should have noted it but I figured it was obvious since I did it *right* after opening it and I was also the submitter :)
[16:24] <micahg> plars: I saw that, but wasn't sure
[16:25] <micahg> plars: anyways, retracer is done :)
[16:25] <plars> micahg: oh it worked this time? yay!
[16:25] <plars> :)
[16:26] <plars> let's see if it actually got anything useful though
[16:26] <micahg> plars: what version of TB?
[16:26] <plars> 3.0.4+nobinonly-0ubuntu1
[16:27] <plars> nope :(
[16:27] <plars> figures
[16:27] <micahg> plars: it's already being addresses upstream: mozilla 532198
[16:27] <ubot4`> Mozilla bug 532198 in XPCOM "Fix NS_InvokeByIndex() to use BLX for method invocations when compiling for Thumb" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=532198
[16:27] <plars> micahg: cool
[16:28] <micahg> plars: we actually have a fix in Firefox already I think
[16:29] <plars> I figured it was likely to be another thumb2 porting issue
[16:29] <micahg> yep, let me see iff we can throw it on Thunderbird
[16:30] <micahg> plars: I'll try to get it added in today
[16:31] <plars> micahg: you rock, thanks!
[16:31] <micahg> plars: np
[16:38] <alvin> persia: reported as bug 563117
[16:38] <ubot4`> Launchpad bug 563117 in mountall (Ubuntu) "Release upgrade converts /dev/mapper entries in /etc/fstab to UUID (affects: 1)" [Undecided,New] https://launchpad.net/bugs/563117
[16:38] <persia> Hah.  mountall.
[16:38]  * persia "mee too"s
[16:49] <micahg> yofel: shouldn't apport have a saner message if the package is just old?
[16:50] <Damascene> any one having problem with wiki.ubuntu.com ?
[16:51] <yofel> well, might be, but the way it does the genuine package test right now it can't differentiate between "not in the archive anymore" and "was  never in the archive"
[16:52] <yofel> as apt-cache policy linux-image... will not return a valid archive link
[16:53] <micahg> yofel: can we just change the message to say no genuine or has been superseded in archive?
[16:53] <micahg> yofel: and maybe also say please try to reproduce (if possible) with latest package version in archive?
[16:54] <yofel> hm, that might be a good idea, but you should rather talk to pitti about this
[16:55] <Damascene> yofel, hi, you are the ubuntu-bug maintainer?
[16:56] <yofel> Damascene: no, if anything I know a bit more about it than others and I'm responsible for ubuntu-bugs bash completion
[16:57] <yofel> the only maintainer I know is Martin Pitt (pitti in #ubuntu-devel)
[16:57] <Damascene> oh, I thought you can change the text as mich-g asked
[17:00] <micahg> yofel: I'll talk to him later
[17:18] <Damascene> is the --(stroke)-- broken on ubuntu wiki?
[17:18] <Damascene> I don't get that effect at all
[17:18] <Damascene> I even didn't find how to sign
[18:49] <Damascene> https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/562130
[18:49] <ubot4`> Launchpad bug 562130 in language-selector (Ubuntu) "Selecting an RTL language should install and RTL capable terminal emulator (affects: 24) (heat: 106)" [Low,Triaged]
[18:49] <Damascene> what should I do now?
[19:07] <Sabre_Edge> Hi I am having this bug with playonlinux Bug #534780, what can i do to resolve this issue (using ubuntu 10.04 beta 2)?
[19:07] <ubot4`> Launchpad bug 534780 in playonlinux (Ubuntu) (and 1 other project) "app seems to crash after selection of an entry-confirmation (affects: 4) (heat: 20)" [Undecided,Fix committed] https://launchpad.net/bugs/534780
[19:12] <Sabre_Edge> anyone ?
[19:51] <JoshuaL> my system doesnt want to sleep, it goes black and the system wont respond, how can i report this bug?
[20:48] <mars> Hi everyone.  I have a bug where the Gnome Screen Unlock dialog shows for a second, then the whole monitor goes black.  I need to switch terminals to get the display to restore itself.  What package should I file the bug against?
[20:48] <yofel> does anyone know if software center hardcodes button text colors on the info pages? http://yofel.dyndns.org/pics/ext/software-center.png That black box should have a black button that says "Remove", but you can't read it
[20:49] <yofel> oddly enough the buttons in the menus aren't affected, only the description pages http://yofel.dyndns.org/pics/ext/software-center1.png
[20:50] <atrus> mars: what do you have to do to restore the display?
[20:50] <mars> atrus, Ctrl-F1, Ctrl-F7
[20:51] <atrus> mars: and after that it was okay?
[20:51] <mars> yes
[20:51] <atrus> my first guess would be to file against your video card driver
[20:51] <mars> atrus, sorry, Ctrl-Alt-F1, Ctrl-Alt-F7
[20:51] <mars> atrus, ugh, nvidia here :(
[20:52] <mars> atrus, ok, thank you for the help
[21:43] <BUGabundo> evening 'p
[21:51] <sandberg> I'm trying to debug bug #423252, but gdb chokes when the nss-ldap module is invoked. Anyone got any sugestions about alternative debuggers?
[21:51] <ubot4`> Launchpad bug 423252 in sudo (Kairos Linux) (and 10 other projects) "NSS using LDAP on Karmic breaks 'su' and 'sudo' (affects: 25) (heat: 198)" [High,Confirmed] https://launchpad.net/bugs/423252
[21:53] <sandberg> I'd really like to get a stack trace of my test application when something calls __nptl_setxid...
[22:02] <bencrisford> BUGabundo: evening
[22:03] <BUGabundo> hey ben
[22:45] <hggdh> seb128: is https://wiki.ubuntu.com/DebuggingApportRetrace good for you?
[22:48] <hggdh> argh, wiki.ubuntu.com is misbehaving today...
[22:50] <seb128> hggdh, "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."...
[22:50] <seb128> hggdh, will comment when I get it ;-)
[22:50] <yofel> actually I got one 500 and 2 503 errors in the last hour
[22:50] <hggdh> seb128: yes, I am trying to save the last update, and failing
[22:50] <hggdh> yofel: at least I only get this one
[22:57] <W3ird_N3rd> Hope I'm in the right channel. I think the netboot ISO is broken again. one or two days ago it couldn't finish because seemlingly no mirror had kernel modules, today no IP can be obtained using DHCP
[22:57] <W3ird_N3rd> I am using http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-i386/current/images/netboot/
[22:57] <W3ird_N3rd> the mini.iso
[22:59] <W3ird_N3rd> or should I ask in ubuntu-devel?
[23:18] <jibel_> Am I right if I affect bug 557023 to casper ?
[23:18] <ubot4`> Launchpad bug 557023 in initramfs-tools (Ubuntu) "update-initramfs: deferring update (trigger activated) / cp: cannot stat `/vmlinuz': No such file or directory (affects: 11) (dups: 10) (heat: 120)" [Medium,Confirmed] https://launchpad.net/bugs/557023
[23:19] <plars> micahg: thanks for getting that thunderbird fix in before freeze :) Now I just need to test again
[23:19] <micahg> plars: that would be great :)
[23:20]  * micahg really needs to clean up bugs next month
[23:20] <micahg> plars: won't build for another 10 hrs
[23:24] <hggdh> seb128: new page name: https://wiki.ubuntu.com/DebuggingWithApportRetrace
[23:27] <BUGabundo> Bug 563425
[23:27] <BUGabundo> bug #563425
[23:27] <ubot4`> BUGabundo: Bug 563425 on http://launchpad.net/bugs/563425 is private
[23:27] <ubot4`> Launchpad bug 563425 in linux (Ubuntu) "9.10 64bits shows only 3gb ram (affects: 1)" [Undecided,New] https://launchpad.net/bugs/563425
[23:28] <BUGabundo> apw: can you take a quick peak at it? trying to help an user out
[23:28] <bdmurray> micahg: can you elaborate on bug 560563?
[23:28] <ubot4`> Launchpad bug 560563 in ubuntu-qa-website "package status updates stopped on 2010-04-09 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/560563
[23:29] <micahg> bdmurray: fixed already, the counts on the left side were not being updated
[23:30] <bdmurray> micahg: okay great!
[23:57] <kklimonda> BUGabundo: lots of bios related messages - has he tried to update it?
[23:57] <BUGabundo> he says toshiba has no newer bios
[23:58] <kklimonda> heh
[23:59] <BUGabundo> can you past the link back?
[23:59] <BUGabundo> I have no log, since my disk was in RO
[23:59] <BUGabundo> had to reboot to liveusb and fsck
[23:59] <BUGabundo> :(


[09:24] <moha> Salam
[09:26] <moha> In an Ubuntu server 22.04, I have some interfaces. If I comment one of them (in order to deactivate it) and then `netplan apply`, `ip -br a`--> the one that has been commented is still up and can ping its gateway! What could be wrong? I should reboot the OS, then that interface will be in 'Down' state.
[09:27] <moha> Note: I'm using 'bridges' in the netplan config file
[09:27] <moha> Indeed it can not down/up a bridge that has been changed in the config file. Deos it need to restart any other services?
[09:28] <schopin> moha: unless you use the --state option to netplan apply, the code won't know that your old interface used to be managed by netplan, and so will simply ignore it, as we figure it's better not to break stuff we're not sure we're owning ;)
[10:40] <Eighth_Doctor> slyon: I'm trying to package 0.106 in Fedora, but the meson install step always throws this error:
[10:40] <Eighth_Doctor> ERROR: Tried to install symlink to missing file /builddir/build/BUILDROOT/netplan-0.106-1.fc39.x86_64/usr/lib/systemd/system-generators/../../../usr/libexec/netplan/generate
[10:41] <schopin> Eighth_Doctor: do you have a link to the full build?
[10:42] <Eighth_Doctor> well it's on my computer, but give me a sec and I'll give you one
[10:42] <schopin> build logs, of course :)
[10:43] <Eighth_Doctor> here's a scratch build that you can get logs from once it finishes failing: https://koji.fedoraproject.org/koji/taskinfo?taskID=97473258
[10:43] <Eighth_Doctor> also, netplan requiring meson 0.61 means I can't upgrade it for RHEL 8 anymore
[10:43] <Eighth_Doctor> they only have meson 0.58
[10:53] <schopin> Eighth_Doctor: that's weird. The install step for `generate` seems to be fine, and the target is apparently the right directory (if I count my ../ correctly ;) ). Do you have access to the build root? If so, can you try and find where the `generate` executable actually ended up?
[10:54] <Eighth_Doctor> give me a sec, I need to re-run it without cleanup :)
[10:54] <Eighth_Doctor> then I can look
[10:57] <Eighth_Doctor> schopin: the generate binary seems to be in usr/libexec/netplan
[10:58] <Eighth_Doctor> which is where it's supposed to be
[11:02] <slyon> Eighth_Doctor: thanks for working on the 0.106 RPMs!
[11:03] <Eighth_Doctor> yeah, once I have this working, I'll update the spec upstream too
[11:03] <Eighth_Doctor> I think this really is an argument for having CentOS/Fedora CI for netplan
[11:03] <slyon> We need some meson 0.61 features, so there was no way to avoid that. But you could still use the legacy "Makefile" build on RHEL8 if needed.
[11:03] <Eighth_Doctor> you deleted it, didn't you?
[11:04] <slyon> Yes, I agree. I want CentOS/Fedora and Debian CI
[11:04] <Eighth_Doctor> yeah, the Makefile only wraps Meson
[11:04] <Eighth_Doctor> so that doesn't help at all 😅
[11:04] <slyon> Eighth_Doctor: I kept it for the 0.106 release, it's still in the tarball
[11:04] <Eighth_Doctor> ah
[11:04] <slyon> I only dropped the legacy Makefile after release
[11:04] <slyon> as we don't want to support that any longer
[11:04] <Eighth_Doctor> sure
[11:05] <Eighth_Doctor> I kind of wish cmake had been chosen because of how much more stable it is, but ehh
[11:05] <Eighth_Doctor> I should at least send up the one patch I have locally
[11:05] <slyon> but meson is the new fancy! :D (and they have a 1.0 now!)
[11:06] <Eighth_Doctor> yeah, but does that mean they'll keep to some kind of stability promise?
[11:06] <Eighth_Doctor> and we don't have that in RHEL 8 or RHEL 9 :(
[11:07] <Eighth_Doctor> it was hell getting RHEL 9 upgraded to meson 0.63
[11:07] <Eighth_Doctor> https://gitlab.com/redhat/centos-stream/rpms/meson/-/merge_requests/6
[11:08] <slyon> right. We'll try to keep the requirement at 0.61 for now
[11:09] <Eighth_Doctor> I guess this will be the end of the line for RHEL 8
[11:10] <Eighth_Doctor> at least this means that compat patch you don't like doesn't have to be upstreamed :P
[11:11] <slyon> :P
[11:12] <Eighth_Doctor> I don't want this again
[11:12] <Eighth_Doctor> but I think I'm going to basically force us to have CentOS and Fedora CI now
[11:12] <slyon> wrt you symlink issue.. I think it could be related to the /usr prefix on a merged-usr vs split-usr system (not sure what RHEL8/9 are using?) https://wiki.debian.org/UsrMerge https://wiki.gentoo.org/wiki/Merge-usr
[11:12] <schopin> Eighth_Doctor: sorry, that's now officially the end of my intuitions for this issue. I'll leave it in slyon 's capable hands ;)
[11:13] <Eighth_Doctor> slyon: we're a mergedusr distro (the first even!)
[11:13] <Eighth_Doctor> https://fedoraproject.org/wiki/Features/UsrMove
[11:13] <slyon> Eighth_Doctor: OK so it should be very similar
[11:13] <Eighth_Doctor> back then it was just called UsrMove
[11:13] <slyon> right
[11:20] <slyon> "ERROR: Tried to install symlink to missing file /builddir/build/BUILDROOT/netplan-0.106-1.fc39.x86_64/usr/lib/systemd/system-generators/../../../usr/libexec/netplan/generate" -> I think this is related to the systemd_generator_dir variable in meson, which is consumed from pkgconfig 'systemdsystemgeneratordir'
[11:20] <slyon> see https://launchpadlibrarian.net/650576320/buildlog_ubuntu-lunar-amd64.netplan.io_0.106-0ubuntu1_BUILDING.txt.gz for how the layout on the Ubuntu build is looking like, e.g.:
[11:20] <slyon> lrwxrwxrwx root/root         0 2023-02-09 11:10 ./lib/systemd/system-generators/netplan -> /usr/libexec/netplan/generate
[11:20] <slyon> (instead of /usr/lib/systemd/systemd-generators)
[11:31] <Eighth_Doctor> oh, you guys haven't switched to merged /usr for systemd itself yet?
[11:39] <slyon> I'm not as involved in systemd maintenance anymore. Can't recall the details
[11:56] <Eighth_Doctor> looks like adding one more traversal made the symlink generation work properly
[13:10] <slyon> good
[13:55] <Eighth_Doctor> slyon: https://github.com/canonical/netplan/pull/323
[13:57] <slyon> Eighth_Doctor: thank you! I need to double check the systemd usrmerge situation in Debian/Ubuntu wrt to that meson.build change. Otherwise this LGTM!
[13:57] <Eighth_Doctor> 👍


[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)vkaovcovm: Researcher- superfly inetpro в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)qnijykx: K_K_N smile kmf[m] в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)cwunayag: SilverCode Cryterion tumbleweed в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)jqfkgpguc: thatgraemeguy andrewlsd Webtricity в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)wpdnt: Researcher- inetpro superfly в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[15:45] <DSG358> ГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)ymbsiuing: paddatrapper DalekSec Maaz ГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“вЂћГўвЂ“
[15:45] <DSG358> в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„ we have got more than 200% of the monthly donations today, thank you all so much!(weechat devs)dwtxtco: paddatrapper thatgraemeguy bmg505 в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„в–„
[18:32] <pavlushka> Happy new year ZA!


[12:49] <shnatsel> creepy, creepy old apps that minimize to nonexistant tray
[14:40] <astraljava> gah
[19:46] <len-nb> Hey! how come we don't have a 32 bit iso any more?
[19:47] <len-nb> Two days in a row.
[20:44] <ScottL> len-nb, good question, i checked listadmin and approved the message stuck in their from the build daemon (huh, i thought i fixed that too) but didn't see anything for 32 bit
[20:44] <ScottL> if we don't see anything tomorrow i'll poke cjwatson again about this
[20:45] <ScottL> it might be because of the linux-lowlatency-pae transition (either taking time for things to settle down or for things to actually get done and pushed)
[20:45] <ScottL> len-nb, i'm done with the menu, i'll post pictures in a bit
[20:45] <ScottL> well, in an hour or so
[20:46] <ScottL> i'm starting the tweak the ubiquity slide library in a few hours
[20:46] <ScottL> and i think i just fixed the cursor theme as well
[20:46] <ScottL> i still need to read the backscroll about alio's testing and the conversations about the kernel
[22:21] <astraljava> brb, trying to switch from irssi to weechat.
[23:26] <ScottL> astraljava, are you going to be able get the live-settings package this weekend?
[23:44] <ScottL> i'm guessing to push to -default-settings in fifteen minutes
[23:44] <ScottL> (yay!  i believe i have the menu adjusted)
[23:55] <len-nb> ScottL, sounds great. I actually got my workflow application to do something... It can actually find the icons that go with the desktop files now.
[23:56] <len-nb> With regard to the 32 bit iso, I am somewhat surprised it vanished. In the past if one iso didn't work the old version still stuck around.
[23:58] <len-nb> So there might be a new 32bit iso and an older 64 bit iso. It is almost like the package thinks the 32bit package is no longer defined.


[00:04] -queuebot:#ubuntu-release- Unapproved: update-manager (bionic-proposed/main) [1:<IP_ADDRESS> => 1:<IP_ADDRESS>] (core)
[00:07] -queuebot:#ubuntu-release- Unapproved: update-manager (cosmic-proposed/main) [1:<IP_ADDRESS> => 1:<IP_ADDRESS>] (core)
[00:31] -queuebot:#ubuntu-release- Unapproved: systemd (disco-proposed/main) [240-6ubuntu3 => 240-6ubuntu4] (core)
[00:39] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (cosmic-proposed/main) [1:<IP_ADDRESS> => 1:<IP_ADDRESS>] (core)
[02:21] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (bionic-proposed/main) [1:18.04.30 => 1:18.04.31] (core)
[05:57] -queuebot:#ubuntu-release- Unapproved: eclipse-titan (cosmic-proposed/universe) [6.3.1-1build4 => 6.3.1-1build4.1] (no packageset)
[06:01] -queuebot:#ubuntu-release- Unapproved: eclipse-titan (bionic-proposed/universe) [6.3.1-1build1.1 => 6.3.1-1build1.2] (no packageset)
[06:27] -queuebot:#ubuntu-release- Unapproved: android-platform-system-core (bionic-proposed/universe) [1:8.1.0+r23-4~18.04 => 1:8.1.0+r23-5~18.04] (no packageset) (sync)
[06:28] -queuebot:#ubuntu-release- Unapproved: android-platform-system-core (cosmic-proposed/universe) [1:8.1.0+r23-4~18.10 => 1:8.1.0+r23-5~18.10] (no packageset) (sync)
[06:28] -queuebot:#ubuntu-release- Unapproved: accepted android-platform-system-core [sync] (cosmic-proposed) [1:8.1.0+r23-5~18.10]
[06:29] -queuebot:#ubuntu-release- Unapproved: accepted android-platform-system-core [sync] (bionic-proposed) [1:8.1.0+r23-5~18.04]
[06:45] <vorlon> anyone know why update_excuses hasn't updated for 6h?
[06:50] <vorlon> possibly a hung package-subscribers process
[07:30] <handsome_feng> Hi, Any chance someone in release team have a look at LP: #1809214, It has been there for 4 months. :(
[07:30] <ubot5`> Launchpad bug 1809214 in ubuntukylin-theme (Ubuntu) "[UIFe] Please upgrade ubuntukylin-theme to <IP_ADDRESS>" [High,New] https://launchpad.net/bugs/1809214
[08:00] <mitya57> infinity: that looks like a different endianness bug. I started looking at it yesterday, will continue tomorrow.
[08:00] -queuebot:#ubuntu-release- Unapproved: maven (bionic-proposed/universe) [3.6.0-1~18.04 => 3.6.0-1~18.04.1] (no packageset) (sync)
[08:00] -queuebot:#ubuntu-release- Unapproved: maven (cosmic-proposed/universe) [3.6.0-1~18.04 => 3.6.0-1~18.04.1] (no packageset) (sync)
[08:01] <mitya57> *will continue today
[08:03] -queuebot:#ubuntu-release- Unapproved: accepted maven [sync] (cosmic-proposed) [3.6.0-1~18.04.1]
[08:05] -queuebot:#ubuntu-release- Unapproved: evolution-ews (disco-proposed/universe) [3.32.0-1 => 3.32.1-1] (no packageset) (sync)
[08:05] -queuebot:#ubuntu-release- Unapproved: evolution (disco-proposed/universe) [3.32.0-1 => 3.32.1-2] (ubuntukylin) (sync)
[08:06] -queuebot:#ubuntu-release- Unapproved: accepted maven [sync] (bionic-proposed) [3.6.0-1~18.04.1]
[08:06] -queuebot:#ubuntu-release- Unapproved: accepted evolution-ews [sync] (disco-proposed) [3.32.1-1]
[08:22] -queuebot:#ubuntu-release- Unapproved: gobject-introspection (disco-proposed/main) [1.60.0-1 => 1.60.1-1] (ubuntu-desktop) (sync)
[08:23] -queuebot:#ubuntu-release- Unapproved: libsoup2.4 (disco-proposed/main) [2.66.0-1 => 2.66.1-1] (core) (sync)
[08:24] <didrocks> sil2100: hey, mind syncing latest canary image to the usual place?
[08:30] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (disco-proposed/main) [2.575 => 2.576] (desktop-core)
[08:38] <sil2100> didrocks: hey, sure, just need a few moments o/
[08:38] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (disco-proposed) [2.576]
[08:40] -queuebot:#ubuntu-release- Unapproved: ukui-control-center (disco-proposed/universe) [1.1.6-2 => 1.1.7-0ubuntu1] (ubuntukylin)
[08:44] <didrocks> sil2100: thx ;)
[08:55] <jibel> sil2100, you can delete previous images
[08:58] -queuebot:#ubuntu-release- Unapproved: gnome-boxes (disco-proposed/universe) [3.31.90-2 => <IP_ADDRESS>-0ubuntu1] (desktop-extra)
[09:10] <sil2100> jibel: http://people.canonical.com/~platform/ubuntu-canary/20190410/
[09:11] <didrocks> sil2100: thx! Can we envision having a scp if the ubuntu-cdimage path isn't doable?
[09:11] <jibel> sil2100, thx
[09:11] <didrocks> like automated, in a single directory, erasing previous builds
[09:11] <didrocks> so that we don't bother you everyday :)
[09:11] <jibel> or every 2 days
[09:14] <sil2100> didrocks: yeah, this could be quite easily automated I suppose (although I'm doing it in a bit of a tricky way right now since I want do to the copies inside the network and somehow my key forwarding doesn't work), but let me just quickly chat with Steve today about maybe special casing this somehow in cdimage
[09:15] <didrocks> sil2100: thx, keep us posted!
[09:20] <seb128> whoever accepted evolution-ews, that needs the corresponding evolution-data-server/evolution accepted as well to build
[09:21] <sil2100> seb128: I didn't, but I can take a look at those
[09:21] <seb128> thx
[09:22] <seb128> well there is a stack of GNOME .1 updates to review
[09:22] -queuebot:#ubuntu-release- Unapproved: accepted evolution-data-server [sync] (disco-proposed) [3.32.1-1]
[09:22] -queuebot:#ubuntu-release- Unapproved: accepted evolution [sync] (disco-proposed) [3.32.1-2]
[09:22] <seb128> would be welcome as well, the sooner the better ... :)
[09:22] <seb128> (they are mostly translations update only)
[09:23] <Laney> ews was auto approved
[09:24] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (disco-proposed) [240-6ubuntu4]
[09:25] <seb128> what's the criterious for auto-approve?
[09:25] <seb128> evolution is in universe as well but was not
[09:25] <Laney> no package set
[09:25] <seb128> I guess it's being on some ISO rather than universe?
[09:25] <seb128> ah
[09:25] <seb128> thx
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted cheese [sync] (disco-proposed) [3.32.1-1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted file-roller [sync] (disco-proposed) [3.32.1-1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted gnome-logs [sync] (disco-proposed) [3.32.1-1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted materia-gtk-theme [source] (disco-proposed) [20190201-1ubuntu2]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted eog [sync] (disco-proposed) [3.32.1-1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted gnome-system-monitor [sync] (disco-proposed) [3.32.1-1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted gnome-characters [sync] (disco-proposed) [3.32.1-1]
[09:29] <seb128> woot, thx for the reviews :)
[09:30] <Laney> I can't accept the flash one, guess that needs a ~canonical-partner-dev
[09:31] <Laney> or whatever the team is
[09:35] -queuebot:#ubuntu-release- Unapproved: accepted budgie-indicator-applet [source] (disco-proposed) [0.5-0ubuntu2]
[09:35] -queuebot:#ubuntu-release- Unapproved: accepted vala [sync] (disco-proposed) [0.44.3-1]
[09:35] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (disco-proposed) [3:15.0.0~rc2-0ubuntu2]
[09:35] -queuebot:#ubuntu-release- Unapproved: accepted yelp [sync] (disco-proposed) [3.32.1-1]
[09:35] <sil2100> Oh
[09:35] <sil2100> I can do that then
[09:35] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-mate-settings [source] (disco-proposed) [19.04.2]
[09:36] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (disco-proposed) [1:20190409.1-0ubuntu1]
[09:38]  * Laney deliberately let his membership in that team expire :>
[09:39] -queuebot:#ubuntu-release- Unapproved: accepted gnome-boxes [source] (disco-proposed) [<IP_ADDRESS>-0ubuntu1]
[09:39] -queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [source] (disco-proposed) [1.1.7-0ubuntu1]
[09:41] <acheronuk> is anyone able to look at the ubuntukylin-theme UIFFe that was mentioned earlier?
[09:41] <sil2100> Laney: hah, tricky! ;)
[09:42] <sil2100> acheronuk: no, but let me look at it now
[09:42] <sil2100> eeek, that's really quite old
[09:43] <acheronuk> yeah, which is why I highlighted
[09:55] <handsome_feng> acheronuk, sil2100: Many thanks!
[10:09] <cpaelzer> jfh: hey I loose "likes" of bdmurray due to bug 1817258 - have you heard anything if IBM is even trying to verify the actual SRU
[10:09] <ubot5`> bug 1817258 in numactl (Ubuntu Cosmic) ""numastat" doesn't display correct information for the guest." [High,Fix committed] https://launchpad.net/bugs/1817258
[10:16] <doko> apw, sforshee: weekly linux/5.0.0-8.9 autopkg test fail ping
[10:16] <jfh> cpaelzer: didn't heard anything special on that - but I see that Santwana tested version 2.0.11-2.1ubuntu0.2 from the PPA (for Leonardo) on bionic - comment #18
[10:17] <sil2100> handsome_feng: approved o/
[10:17] <jfh> cpaelzer: I'll sent her a note and ask to retest from proposed ...
[10:20] -queuebot:#ubuntu-release- Unapproved: firefox (disco-proposed/main) [66.0.2+build1-0ubuntu1 => 66.0.3+build1-0ubuntu1] (mozilla, ubuntu-desktop)
[10:23] <handsome_feng> sil2100: Thanks! :D
[10:37] <acheronuk> sil2100: shall I put that in the queue then?
[10:37] -queuebot:#ubuntu-release- Unapproved: webkit2gtk (disco-proposed/main) [2.24.0-1 => 2.24.1-1] (desktop-core) (sync)
[10:41] -queuebot:#ubuntu-release- Unapproved: accepted language-selector [source] (bionic-proposed) [0.188.2]
[10:51] -queuebot:#ubuntu-release- Unapproved: accepted ureadahead [source] (bionic-proposed) [0.100.0-21]
[11:01] <handsome_feng> acheronuk, thank you, I really appreciate it if you could sponsor the package! And I thank you can do that?  sil2100 left a comment to approved that. :)
[11:06] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-appindicator (disco-proposed/main) [23.1-1 => 28-1] (ubuntu-desktop) (sync)
[11:19] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-theme (disco-proposed/universe) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntukylin)
[11:19] <acheronuk> handsome_feng: ^^
[11:20] <handsome_feng> acheronuk, Thannnnnnnnnnnks! :)
[11:34] -queuebot:#ubuntu-release- Unapproved: notary (disco-proposed/universe) [0.6.1~ds1-2 => 0.6.1~ds1-3] (no packageset) (sync)
[11:35] -queuebot:#ubuntu-release- Unapproved: accepted notary [sync] (disco-proposed) [0.6.1~ds1-3]
[11:43] -queuebot:#ubuntu-release- Unapproved: spf-engine (disco-proposed/universe) [2.9.0-2 => 2.9.0-3] (no packageset) (sync)
[11:43] -queuebot:#ubuntu-release- Unapproved: accepted spf-engine [sync] (disco-proposed) [2.9.0-3]
[11:51] -queuebot:#ubuntu-release- Unapproved: zsh (disco-proposed/main) [5.5.1-1ubuntu2 => 5.5.1-1ubuntu3] (core)
[11:53] <xnox> ^ fixes FTBFS / autopkgtest as triggered by glibc
[11:56] <rbalint> AA people, could you please publish ubuntu-meta's new ubuntu-wsl binary for all stable releases?
[12:25] <rbalint> rbasak, if you have time in your sru cycle please take a look at u-u, all bugs are verified now and the package is ready to go and the master bug is LP: #1702793
[12:25] <ubot5`> Launchpad bug 1702793 in unattended-upgrades (Ubuntu Xenial) "Full backport SRU for unattended-upgrades" [Low,Fix committed] https://launchpad.net/bugs/1702793
[12:30] <sil2100> handsome_feng: thanks for the upload, let me review it o/
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-theme [source] (disco-proposed) [<IP_ADDRESS>]
[12:35] <handsome_feng> sil2100, Thanks for your review. :)
[12:39] <handsome_feng> sil2100: BTW, It would be great if you can review another FFe bug when you are free, LP: #1818769 :P
[12:39] <ubot5`> Launchpad bug 1818769 in ubuntu-kylin-software-center (Ubuntu) "[FFe] Please upgrade ubuntu-kylin-software-center to 1.5.4" [High,New] https://launchpad.net/bugs/1818769
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted firefox [source] (disco-proposed) [66.0.3+build1-0ubuntu1]
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted zsh [source] (disco-proposed) [5.5.1-1ubuntu3]
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted webkit2gtk [sync] (disco-proposed) [2.24.1-1]
[12:47] <sil2100> handsome_feng: on it
[12:50] -queuebot:#ubuntu-release- Unapproved: unity-tweak-tool (disco-proposed/universe) [0.0.7ubuntu4 => 0.0.7+-0ubuntu5] (no packageset)
[12:51] -queuebot:#ubuntu-release- Unapproved: accepted unity-tweak-tool [source] (disco-proposed) [0.0.7+-0ubuntu5]
[12:52] <sil2100> handsome_feng: approved o/
[12:53] <handsome_feng> sil2100, Wow, It's a wonderful night, Thanks! :)
[12:56] <handsome_feng> acheronuk, So could you help to upload this too, and I promise this is the last package. :P
[12:57] -queuebot:#ubuntu-release- Unapproved: netbeans (cosmic-proposed/universe) [10.0-3~18.04.1 => 10.0-3~18.04.1ubuntu1] (no packageset) (sync)
[13:02] -queuebot:#ubuntu-release- Unapproved: linux (disco-proposed/main) [5.0.0-8.9 => 5.0.0-10.11] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-aws (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-kvm (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-meta-kvm (disco-proposed/main) [<IP_ADDRESS>1.1 => <IP_ADDRESS>2.2] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-azure (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-raspi2 (disco-proposed/universe) [5.0.0-1004.4 => 5.0.0-1005.5] (kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-meta-aws (disco-proposed/main) [<IP_ADDRESS>1.1 => <IP_ADDRESS>2.2] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-meta-raspi2 (disco-proposed/universe) [<IP_ADDRESS>4.1 => <IP_ADDRESS>5.2] (kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-signed (disco-proposed/main) [5.0.0-8.9 => 5.0.0-10.11] (core, kernel) (sync)
[13:03] -queuebot:#ubuntu-release- Unapproved: linux-signed-azure (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[13:04] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu (disco-proposed/main) [19.0.0-1 => 19.0.1-1] (desktop-core) (sync)
[13:15] <acheronuk> handsome_feng: uploading, slowly on a cr*p connection
[13:16] -queuebot:#ubuntu-release- Unapproved: netbeans (bionic-proposed/universe) [10.0-3~18.04.1 => 10.0-3~18.04.1ubuntu1] (no packageset) (sync)
[13:16] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [amd64] (cosmic-proposed) [1.425.1]
[13:16] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [arm64] (cosmic-proposed) [1.425.1]
[13:17] <handsome_feng> acheronuk, \^o^/
[13:20] <acheronuk> np
[13:21]  * acheronuk thinks a 75MB for a software centre is a big bloated, but wth
[13:25] -queuebot:#ubuntu-release- Unapproved: ubuntu-kylin-software-center (disco-proposed/universe) [1.3.14 => 1.5.4] (ubuntukylin)
[13:26] <acheronuk> handsome_feng sil2100 ^^
[13:33] <handsome_feng> acheronuk, This is fantastic!
[13:37] <sil2100> \o/
[13:37] <sil2100> acheronuk: thanks o/
[13:42] -queuebot:#ubuntu-release- Unapproved: linux-meta-azure (disco-proposed/main) [<IP_ADDRESS>1.1 => <IP_ADDRESS>2.2] (core, kernel) (sync)
[13:42] -queuebot:#ubuntu-release- Unapproved: linux-meta (disco-proposed/main) [<IP_ADDRESS>.9 => <IP_ADDRESS>.11] (core, kernel) (sync)
[14:32] <sil2100> handsome_feng, acheronuk: I don't like the debian/changelog in ubuntu-kylin-software-center since it has a few UNRELEASED entries, but I'll accept it anyway
[14:32] <sil2100> Just be sure to fix that up sometime
[14:33] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-kylin-software-center [source] (disco-proposed) [1.5.4]
[14:43] -queuebot:#ubuntu-release- Unapproved: casper (disco-proposed/main) [1.402 => 1.403] (desktop-core, ubuntu-server)
[14:46] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [amd64] (bionic-proposed) [1.417.1]
[14:46] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [arm64] (bionic-proposed) [1.417.1]
[14:54] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [amd64] (xenial-proposed) [1.361.3]
[14:54] -queuebot:#ubuntu-release- New: accepted ubuntu-meta [arm64] (xenial-proposed) [1.361.3]
[14:56] -queuebot:#ubuntu-release- Unapproved: accepted netbeans [sync] (cosmic-proposed) [10.0-3~18.04.1ubuntu1]
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted netbeans [sync] (bionic-proposed) [10.0-3~18.04.1ubuntu1]
[15:41] <bdmurray> sil2100: Could you have a look at my u-r-u & update-manager uploads for B and C? Its rather important.
[15:41] -queuebot:#ubuntu-release- Unapproved: pdl (disco-proposed/universe) [1:2.019-5 => 1:2.019-5build1] (no packageset)
[15:42] -queuebot:#ubuntu-release- Unapproved: accepted pdl [source] (disco-proposed) [1:2.019-5build1]
[15:46] -queuebot:#ubuntu-release- Unapproved: gnome-desktop3 (disco-proposed/main) [3.32.0-1ubuntu1 => 3.32.1-1ubuntu1] (ubuntu-desktop)
[15:51] <sil2100> bdmurray: hum hum, ok, will try looking at that today still
[15:52] <bdmurray> sil2100: I could ask someone else if you are short on itme
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted gnome-desktop3 [source] (disco-proposed) [3.32.1-1ubuntu1]
[15:55] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu [sync] (disco-proposed) [19.0.1-1]
[16:04] -queuebot:#ubuntu-release- Unapproved: cloud-init (disco-proposed/main) [18.5-45-g3554ffe8-0ubuntu1 => 18.5-61-gb76714c3-0ubuntu1] (core, edubuntu, ubuntu-cloud)
[16:06] <Odd_Bloke> Could someone please accept ^ in to -proposed so we can start doing the testing our FFE calls for?
[16:07] <Odd_Bloke> (I'm not sure if it would be blocked from migrating by the freeze, but I've filed https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1824185 with block-proposed just in case.)
[16:07] <ubot5`> Ubuntu bug 1824185 in cloud-init (Ubuntu) "Release a new upstream snapshot to disco" [Undecided,New]
[16:10] <Odd_Bloke> vorlon: ^, if you have a minute
[16:10] <vorlon> Odd_Bloke: on it
[16:11] <Odd_Bloke> Thanks!
[16:11] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (disco-proposed) [18.5-61-gb76714c3-0ubuntu1]
[16:11] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (cosmic-proposed/partner) [1:20190312.1-0ubuntu<IP_ADDRESS> => 1:20190409.1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:11] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20190312.1-0ubuntu<IP_ADDRESS> => 1:20190409.1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:11] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20190312.1-0ubuntu<IP_ADDRESS> => 1:20190409.1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:11] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20190312.1-0ubuntu<IP_ADDRESS> => 1:20190409.1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:24] -queuebot:#ubuntu-release- Unapproved: jhove (cosmic-proposed/multiverse) [1.20.1-5~18.04.1 => 1.20.1-5~18.10.1] (no packageset) (sync)
[16:25] -queuebot:#ubuntu-release- Unapproved: jhove (bionic-proposed/multiverse) [1.20.1-5~18.04.1 => 1.20.1-5~18.04.1ubuntu1] (no packageset) (sync)
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted jhove [sync] (cosmic-proposed) [1.20.1-5~18.10.1]
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted jhove [sync] (bionic-proposed) [1.20.1-5~18.04.1ubuntu1]
[16:39] -queuebot:#ubuntu-release- Unapproved: jetty9 (cosmic-proposed/universe) [9.4.15-1~18.04 => 9.4.15-1~18.04.1ubuntu1] (no packageset) (sync)
[16:40] -queuebot:#ubuntu-release- Unapproved: jetty9 (bionic-proposed/universe) [9.4.15-1~18.04 => 9.4.15-1~18.04.1ubuntu1] (no packageset) (sync)
[16:46] -queuebot:#ubuntu-release- Unapproved: accepted jetty9 [sync] (cosmic-proposed) [9.4.15-1~18.04.1ubuntu1]
[16:49] -queuebot:#ubuntu-release- Unapproved: accepted jetty9 [sync] (bionic-proposed) [9.4.15-1~18.04.1ubuntu1]
[16:53] -queuebot:#ubuntu-release- Unapproved: tomcat8 (bionic-proposed/universe) [8.5.39-1ubuntu1~18.04 => 8.5.39-1ubuntu1~18.04.1] (kubuntu) (sync)
[16:59] -queuebot:#ubuntu-release- Unapproved: tomcat8 (cosmic-proposed/universe) [8.5.39-1ubuntu1~18.04 => 8.5.39-1ubuntu1~18.10] (kubuntu) (sync)
[17:01] -queuebot:#ubuntu-release- Unapproved: accepted tomcat8 [sync] (cosmic-proposed) [8.5.39-1ubuntu1~18.10]
[17:04] -queuebot:#ubuntu-release- Unapproved: accepted tomcat8 [sync] (bionic-proposed) [8.5.39-1ubuntu1~18.04.1]
[17:12] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (cosmic-proposed) [1:<IP_ADDRESS>]
[17:13] -queuebot:#ubuntu-release- Unapproved: wpa (disco-proposed/main) [2:2.6-21ubuntu2 => 2:2.6-21ubuntu3] (core)
[17:15] -queuebot:#ubuntu-release- Unapproved: flashplugin-nonfree (disco-proposed/multiverse) [<IP_ADDRESS>ubuntu1 => <IP_ADDRESS>ubuntu1] (no packageset)
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted flashplugin-nonfree [source] (disco-proposed) [<IP_ADDRESS>ubuntu1]
[17:17] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (bionic-proposed) [1:<IP_ADDRESS>]
[17:21] <sil2100> bdmurray: ekhm, where is teh template on LP: #1822886 ?
[17:21] <ubot5`> Launchpad bug 1822886 in ubuntu-release-upgrader (Ubuntu Cosmic) "universe missing after bionic->cosmic do-release-upgrade" [Critical,Triaged] https://launchpad.net/bugs/1822886
[17:21]  * sil2100 stares at bdmurray in an evil way
[17:23] <bdmurray> sil2100: See this is why I needed a review!
[17:25] <sil2100> ;)
[17:25] <sil2100> bdmurray: just poke me once you update teh bug
[17:35] -queuebot:#ubuntu-release- New sync: linux-meta-snapdragon (disco-proposed/primary) [<IP_ADDRESS>9.2]
[17:35] -queuebot:#ubuntu-release- New sync: linux-snapdragon (disco-proposed/primary) [5.0.0-1009.9]
[17:36] -queuebot:#ubuntu-release- Unapproved: linux-gcp (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[17:36] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (disco-proposed/main) [5.0.0-1001.1 => 5.0.0-1002.2] (core, kernel) (sync)
[17:36] -queuebot:#ubuntu-release- Unapproved: linux-meta-gcp (disco-proposed/main) [<IP_ADDRESS>1.1 => <IP_ADDRESS>2.2] (core, kernel) (sync)
[18:05] <bdmurray> sil2100: Sorry about that I was involved in something, I may not get to it before you eod
[18:10] <sil2100> bdmurray: ok, no worries, I'll pick it up tomorrow on my SRU shift then
[18:18] -queuebot:#ubuntu-release- New source: intel-compute-runtime (disco-proposed/primary) [19.13.12717-0ubuntu1]
[18:33] <ddstreet> stgraber rbalint not sure if you noticed yet, but the lxd upload for lp #1821924 appears to have broken the docker.io autopkgtests
[18:33] <ubot5`> Launchpad bug 1821924 in lxd (Ubuntu Cosmic) "LXD Deb->snap transition fails in WSL due to snap command not working (yet)" [Low,Fix committed] https://launchpad.net/bugs/1821924
[18:36] <stgraber> ddstreet: hmm, not sure what to think of it, the exact same package in disco is all green on autopkgtest
[18:37] <stgraber> ddstreet: yeah, pretty sure that upload isn't what broke it, if you look at your own retry, it's failing despite not using the new lxd package
[18:40] <stgraber> ddstreet: there's something weird going on with snapd in this case but it doesn't look like a lxd problem
[18:40] <stgraber> you'll notice:
[18:40] <stgraber> ==> Installing the LXD snap from the latest track for ubuntu-18.10
[18:40] <stgraber> snap "lxd" is already installed, see 'snap help refresh'
[18:40] <stgraber> which shows that the lxd snap is supposedly installed, the lxd shim package (0.4 from October) sees it as all good
[18:40] <ddstreet> stgraber i think you're right, looks like snapd is failing as well, with a similarly weird error:
[18:40] <ddstreet> + /snap/bin/go get -u github.com/snapcore/spread/cmd/spread
[18:40] <ddstreet> /snap/go/3542/gowrapper: line 3: /snap/go/3542/bin/go: No such file or directory
[18:40] <stgraber> and then things blow up on /snap/bin/lxd being missing
[18:41] <ddstreet> yeah something off with snap
[18:41] <stgraber> ddstreet: yep, so there's something pretty wrong going on with snapd in there
[18:55] -queuebot:#ubuntu-release- Unapproved: ureadahead (xenial-proposed/main) [0.100.0-19 => 0.100.0-19.1] (core)
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-aws [sync] (disco-proposed) [5.0.0-1002.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-gcp [sync] (disco-proposed) [5.0.0-1002.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-aws [sync] (disco-proposed) [<IP_ADDRESS>2.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-gcp [sync] (disco-proposed) [<IP_ADDRESS>2.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-raspi2 [sync] (disco-proposed) [<IP_ADDRESS>5.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-raspi2 [sync] (disco-proposed) [5.0.0-1005.5]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-azure [sync] (disco-proposed) [5.0.0-1002.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-azure [sync] (disco-proposed) [<IP_ADDRESS>2.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (disco-proposed) [<IP_ADDRESS>.11]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-kvm [sync] (disco-proposed) [5.0.0-1002.2]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (disco-proposed) [5.0.0-10.11]
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-kvm [sync] (disco-proposed) [<IP_ADDRESS>2.2]
[19:01] -queuebot:#ubuntu-release- Unapproved: pyparted (disco-proposed/main) [3.11.2-7 => 3.11.2-7ubuntu1] (desktop-core)
[19:02] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-azure [sync] (disco-proposed) [5.0.0-1002.2]
[19:02] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (disco-proposed) [5.0.0-10.11]
[19:02] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-gcp [sync] (disco-proposed) [5.0.0-1002.2]
[19:11] -queuebot:#ubuntu-release- Unapproved: accepted pyparted [source] (disco-proposed) [3.11.2-7ubuntu1]
[19:19] -queuebot:#ubuntu-release- Unapproved: pyparted (disco-proposed/main) [3.11.2-7ubuntu1 => 3.11.2-10] (desktop-core) (sync)
[19:22] -queuebot:#ubuntu-release- Unapproved: accepted pyparted [sync] (disco-proposed) [3.11.2-10]
[19:32] -queuebot:#ubuntu-release- Unapproved: accepted intel-media-driver [source] (disco-proposed) [18.4.0+dfsg1-1ubuntu1]
[19:46] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1002.2] (core, kernel)
[19:46] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (disco-proposed/main) [5.0.0-1002.2] (core, kernel)
[19:48] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-10.11] (core, kernel)
[19:48] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1042.46~14.04.1] (kernel)
[19:48] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-10.11] (core, kernel)
[19:49] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-10.11] (core, kernel)
[19:53] -queuebot:#ubuntu-release- Unapproved: console-setup (disco-proposed/main) [1.178ubuntu11 => 1.178ubuntu12] (core)
[19:54] <vorlon> rcj: ^^
[19:55] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1002.2]
[19:55] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-10.11]
[19:55] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-10.11]
[19:55] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (disco-proposed) [5.0.0-1002.2]
[19:55] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-10.11]
[20:03] <rcj> vorlon: thank you
[20:04] -queuebot:#ubuntu-release- Unapproved: console-setup (cosmic-proposed/main) [1.178ubuntu9 => 1.178ubuntu9.1] (core)
[20:05] -queuebot:#ubuntu-release- Unapproved: rejected console-setup [source] (cosmic-proposed) [1.178ubuntu9.1]
[20:08] -queuebot:#ubuntu-release- Unapproved: rejected console-setup [source] (disco-proposed) [1.178ubuntu12]
[20:11] -queuebot:#ubuntu-release- Unapproved: console-setup (disco-proposed/main) [1.178ubuntu11 => 1.178ubuntu12] (core)
[20:13] -queuebot:#ubuntu-release- Unapproved: console-setup (cosmic-proposed/main) [1.178ubuntu9 => 1.178ubuntu9.1] (core)
[20:16] -queuebot:#ubuntu-release- Unapproved: console-setup (bionic-proposed/main) [1.178ubuntu2.7 => 1.178ubuntu2.8] (core)
[20:19] -queuebot:#ubuntu-release- Unapproved: console-setup (xenial-proposed/main) [1.108ubuntu15.4 => 1.108ubuntu15.5] (core)
[20:19] <vorlon> bdmurray: ^^ do you have time for some off-day SRU reviews?  (with xenial being the most important, as it currently blocks rcj)
[20:26] <bdmurray> vorlon: in a little bit yeah
[20:36] -queuebot:#ubuntu-release- Unapproved: cloud-init (disco-proposed/main) [18.5-61-gb76714c3-0ubuntu1 => 18.5-62-g6322c2dd-0ubuntu1] (core, edubuntu, ubuntu-cloud)
[20:37] <Odd_Bloke> vorlon: We discovered a regression, could you accept ^, please?
[20:38] -queuebot:#ubuntu-release- Unapproved: librsvg (disco-proposed/main) [2.44.10-1 => 2.44.10-1ubuntu1] (core)
[21:01] -queuebot:#ubuntu-release- Unapproved: emacs (disco-proposed/main) [1:26.1+1-3.2ubuntu1 => 1:26.1+1-3.2ubuntu2] (ubuntu-desktop)
[21:06] -queuebot:#ubuntu-release- Unapproved: software-properties (disco-proposed/main) [0.97.9 => 0.97.10] (core)
[21:06] <vorlon> Odd_Bloke: looking
[21:07] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (disco-proposed) [18.5-62-g6322c2dd-0ubuntu1]
[21:15] -queuebot:#ubuntu-release- Unapproved: accepted console-setup [source] (cosmic-proposed) [1.178ubuntu9.1]
[21:16] -queuebot:#ubuntu-release- Unapproved: accepted console-setup [source] (bionic-proposed) [1.178ubuntu2.8]
[21:17] -queuebot:#ubuntu-release- Unapproved: accepted console-setup [source] (xenial-proposed) [1.108ubuntu15.5]
[21:19] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (bionic-proposed) [0.96-0ubuntu<IP_ADDRESS>]
[21:31] <ddstreet> stgraber you were right, the core snap is broken in cosmic, i opened lp #1824237 for it
[21:31] <ubot5`> Launchpad bug 1824237 in snapd (Ubuntu Cosmic) "snap 'core' broken/missing and causing autopkgtest failures" [Undecided,New] https://launchpad.net/bugs/1824237
[21:53] -queuebot:#ubuntu-release- Unapproved: openldap (bionic-proposed/main) [2.4.45+dfsg-1ubuntu1.1 => 2.4.45+dfsg-1ubuntu1.2] (ubuntu-server)
[21:53] -queuebot:#ubuntu-release- Unapproved: openldap (cosmic-proposed/main) [2.4.46+dfsg-5ubuntu1.1 => 2.4.46+dfsg-5ubuntu1.2] (ubuntu-server)
[21:57] -queuebot:#ubuntu-release- Unapproved: openldap (xenial-proposed/main) [2.4.42+dfsg-2ubuntu3.4 => 2.4.42+dfsg-2ubuntu3.5] (ubuntu-server)
[22:06] <vorlon> ddstreet, stgraber: is this only reproducible with snapd 2.38+18.10?
[22:08] <vorlon> ddstreet: I've marked your bug regression-proposed, and marked LP: #1818648 verification-failed-cosmic, so we immediately stop the line on the SRU
[22:08] <ubot5`> Launchpad bug 1818648 in snapd (Ubuntu Cosmic) "[SRU] 2.38" [Undecided,Fix committed] https://launchpad.net/bugs/1818648
[22:22] <vorlon> the only differences between pyparted 3.11.2-7ubuntu1 and 3.11.2-10 are the changelog, the maintainer field, and debian/tests.  So why did the one build on armhf, and the other fails with a SIGBUS? >:|
[22:22] -queuebot:#ubuntu-release- Unapproved: accepted wpa [source] (disco-proposed) [2:2.6-21ubuntu3]
[22:22] -queuebot:#ubuntu-release- Unapproved: fwupd (disco-proposed/main) [1.2.5-1 => 1.2.5-1ubuntu1] (desktop-core)
[22:29] <vorlon> infinity, wgrant: ^^ is there anything that's changed recently with the launchpad buildd chroots?  because this is crazy
[22:29] <vorlon> (pyparted)
[22:36] <mwhudson> vorlon: changes in build dependencies?
[22:36] <vorlon> mwhudson: complete debdiff is http://launchpadlibrarian.net/418712335/pyparted_3.11.2-7ubuntu1_3.11.2-10.diff.gz - nada
[22:37] <mwhudson> vorlon: i mean, maybe a new binutils or something
[22:37] <vorlon> ah
[22:37] <mwhudson> changes in the archive
[22:37] <mwhudson> wtb a thing to wdiff the build environment sections of the two build logs
[22:37] <vorlon> mwhudson: the only package that's different in the log is linux-libc-dev which seems an unlikely culprit for impacting distutils
[22:37] <mwhudson> yes
[22:38] <vorlon> and the window when this broke is *narrow*, I literally uploaded 7ubuntu1, went to submittodebian, noticed the maintainer had already fixed this issue in 10, synced it
[22:40] <mwhudson> oh that is silly!
[22:41] <vorlon> disco-changes shows they were accepted 8 minutes apart
[22:41] <mwhudson> next ideas: builder specific (but i think all our builders are the same these days), it's just random?
[22:41] <vorlon> I've retried the build 2 more times
[22:42] <vorlon> the builder names are similar (bos02-arm64-06{0,8}) for all that's worth
[22:59] <infinity> vorlon: I really wanted to blame the kernel, but that seems to be unchanged. :/
[23:01] <infinity> vorlon: Do we have a process to ask for the Microsoft solution in scalingstack (reboot the base compute nodes)?
[23:01] <vorlon> uh
[23:01] <vorlon> that'd be an RT I guess
[23:01] <infinity> Cause an FPE is rather suspiciously weird.
[23:02] <vorlon> oh it was sigfpe, not sigbus?  yeah I didn't even read it right
[23:04] <xnox> vorlon, speaking of puma.... the autopkgtest is generated with autodep8, and it's just this:
[23:04] <xnox> $ autodep8
[23:04] <xnox> Test-Command: gem2deb-test-runner --autopkgtest --check-dependencies 2>&1
[23:04] <xnox> Depends: @, libssl-dev,rake,ruby-rack, gem2deb-test-runner
[23:04] <xnox> aka
[23:04] <xnox> just run the test-suite.... and it does pass for me, in disco-release
[23:05] <xnox> i'll do that again in disco-proposed now locally, if that passes too.... i wonder if we can try putting puma into "large packages" to give it more than one cpu. as it runs client and server, that supposed to talk to each other....
[23:05] <xnox> and there is already one known test skip in single-cpu case.
[23:05] <xnox> but also, puma does not look broken to me on ubuntu.
[23:11] <xnox> passes in a chroot in disco-proposed too
[23:12] <vorlon> xnox: but all of this is reactive; people are willing to spend time on picking at the specific autopkgtest failures only because attention has been drawn to them on ubuntu-devel
[23:12] <xnox> vorlon, dude i'm not pretending that i'm doing something other than exactly that.
[23:13] <xnox> =)))))))))
[23:13] <vorlon> xnox: I can't imagine why it would need a 'large' testbed, it only takes 2 minutes to fail on a small one
[23:13] <xnox> it's just if puma builds on builders, but fails to do the same thing in autopkgtest, we are at odds with like host kernel, or different size of resources.
[23:13] <xnox> well, trying to reproduce the failure, and failing at the moment =)
[23:15] <vorlon> xnox: the command run in the autopkgtest is not one that's run in the package build
[23:16] <xnox> vorlon, the command run in autopkgtest, should be the one generated by autodep8 see my message from 00:04:16 UK time.
[23:16] <vorlon> which is not the same as the command run during the build
[23:16] <xnox> vorlon, which is ~= run the test-suite, and it's trivial to run that command locally.
[23:16] <xnox> and running the autodep8 generated command locally, passes everything.
[23:17] <vorlon> TestPathHandler#test_handler_boots
[23:17] <vorlon> I see the problem
[23:17] <vorlon> this is an anagram of 'boost'
[23:17] <vorlon> all is explained
[23:26] <xnox> vorlon, i notice that there is "CI" mode in test harness that we are not using.
[23:26] <xnox> specifically it appears to enable autoretry and timeout of the tests.
[23:26] <xnox> patching things to take AUTOPKGTEST_TMP into account.
[23:48] -queuebot:#ubuntu-release- Unapproved: probert (disco-proposed/universe) [<IP_ADDRESS>build1 => 0.0.15] (no packageset)
[23:48] -queuebot:#ubuntu-release- Unapproved: accepted probert [source] (disco-proposed) [0.0.15]
[23:52] -queuebot:#ubuntu-release- Unapproved: lubuntu-default-settings (disco-proposed/universe) [19.04.1 => 19.04.2] (lubuntu)