[03:30] <qwebirc10954> Hello all is there no complete how to to installing mythbuntu
[03:31] <qwebirc10954> Unless im not looking in the right places I can't seem to find database setup info
[05:02] <Gibby> qwebirc10954: what are you looking for,? It takes care if it during install. Are you using mythbuntu control center?
[05:02] <tgm4883> Gibby, he left
[05:04] <Gibby> Ahh sorry, on my phone, still working out the tweaks on my bouncer
[11:47] <qwebirc99688> Hi, I'm wondering how to figure out if this fix is in the current 0.26 build?  http://code.mythtv.org/trac/ticket/10995
[11:48] <qwebirc99688> I'm guessing not, as I'm seeing this issue.     The build number of the binaries is v0.26.0-28-ge3087dd .... but couldn't track that to an obvious revision.
[15:04] <sabhain> Gibby: trying to decide what to do about an upgrade.  I have been on 10.10 for awhile, need to move to LTS.
[15:05] <sabhain> Gibby: it's my daily driver at work, so I don't want something too different.  Been a long time Gnome2 user .. multiple monitors on multiple sessions.
[15:05] <sabhain> Gibby: and I'm really particular on my mouse behavior (sloppy focus, raise-on-click "OFF").
[15:06] <sabhain> What I'm reading tells me I might be best moving to XFCE, but thought I'd poke around to see if anyone had experience / strong opinions


[10:31] <Dutchy45> Hey guys, I don't know if I'm in the right place but I'm looking for help with gridcoin?
[17:15] <asciiwolf> hello, I have a problem pushing my project to launchpad bzr
[17:16] <asciiwolf> When I try bzr push it just hangs and does nothing. :-( Are there currently any issues with the Launchpad Bazaar?
[17:42] <asciiwolf> my launchpad profile: https://launchpad.net/~asciiwolf
[17:45] <tsimonq2> asciiwolf: What's the exact command you're using?
[17:46] <asciiwolf> I have tried more commands:
[17:47] <asciiwolf> bzr push lp:autoremover , bzr push lp:~asciiwolf/autoremover/trunk , bzr push lp:~asciiwolf/+autoremover/trunk
[17:47] <asciiwolf> none of them worked
[17:48] <asciiwolf> It just asks to accept the key fingerprint, then hangs forever
[17:48] <tsimonq2> hm.
[17:49] <asciiwolf> I have tried it on both Ubuntu (latest bionic devel build) and Fedora, both with the latest bzr client installed
[18:16] <asciiwolf> yay, I tried to make a new ssh key and it works now
[18:16] <asciiwolf> So problem solved I guess :)


[08:38] <rpadovani> o/ I don't know if it's the right channel where report this, but... I'm trying to login to https://staging.launchpad.net/? to take a look, but the U1 login page says mail/password combination is wrong. I tried a lot of times, but I'm not able to login. Of course, I'm sure credentials are right, I'm able to login to login,ubuntu.com without problems
[08:38] <rpadovani> (and also to main lp site)
[08:39] <wgrant> rpadovani: login.staging.launchpad.net uses a separate account database.
[08:39] <wgrant> You may need to create a new account or request a password reset.
[08:39] <rpadovani> wgrant, I see, thanks
[08:40] <wgrant> (staging.launchpad.net uses login.staging.launchpad.net, while qastaging.launchpad.net uses login.launchpad.net. so you can always use qastaging if staging SSO is broken.)
[08:42] <rpadovani> wgrant, it works, thanks :-) Maybe then is better to link qastaging here? Or report this thing of the different account somewhere?
[08:42] <rpadovani> https://launchpad.net/projects/+new
[08:43] <wgrant> The different account databases are deliberate.
[13:26] <kostja_osipov> hi
[15:52] <nortoboru> hello
[16:19] <desrt> cjwatson: hey.. i was sent to ping you about https://bugs.launchpad.net/launchpad/+bug/638498 :)
[16:20] <cjwatson> desrt: well, OK, but not today :)
[16:20] <cjwatson> it's probably not too hard
[16:21] <desrt> ya.  seems more like an oversight than anything else
[16:21] <desrt> but it's putting a cramp in my style for my 'debootstrap jhbuilder chroots' project
[16:22] <desrt> it's not really blocking me per se... i can continue developing it with debian releases in the meantime
[16:23] <desrt> anyway... thanks!
[16:27] <cjwatson> desrt: It's probably as simple as http://paste.ubuntu.com/10616167/ plus tests
[16:28] <cjwatson> desrt: Firing off tests now to see what breaks
[16:30] <desrt> cjwatson: you lied.  you said 'not today' :)
[16:32] <desrt> cjwatson: it seems that ubuntu does Releases files the way that debian used to do them...
[16:32] <cjwatson> desrt: I'm not going to finish this today :)
[16:32] <desrt> ie: one file per dist
[16:33] <cjwatson> Debian still does that
[16:33] <cjwatson> Release files are a per-series object
[16:33] <desrt> they do one file per category/component/etc.
[16:33] <desrt> whatever that is called
[16:33] <desrt> like, main/contrib/non-free, each has its own
[16:34] <cjwatson> Those Release files are a slightly different type of thing, and don't contain checksums
[16:34] <cjwatson> We have them too
[16:34] <desrt> oops.  i'm sorry.  i didn't mean release.  i mean Contents
[16:34] <cjwatson> Ah, yes, we don't have per-component Contents as yet
[16:35] <desrt> probably just as well for my purposes, to be honest.... with debian, everything i want is in main but for ubuntu some of it is in universe...
[16:35] <desrt> i guess eventually i'm going to have to deal with parsing multiple contents files
[16:37] <cjwatson> That's dak b36379705f3f2a52788ad19cf1da339c4edf339d, for my reference
[23:37] <DalekSec> wgrant: Can I gently poke you about lp 907675?
[23:38] <wgrant> DalekSec: That's blocking on https://twistedmatrix.com/trac/ticket/5350
[23:39] <DalekSec> wgrant: Awesome, thanks muchly!
[23:40] <DalekSec> Sad, bit dated,


 So after deleting all windows partitions and adding news ones (/boot, swap, /, /home) it complains that no EFI partition is selected. Should I continue or am I doing it the wrong way ?
[00:34] <Enissay> Actually there was an efi partition which I deleted with the other windows partitions :D
[00:37] <Enissay> Ow, I see the menu allows me to create a new EFI partition
[00:37] <Enissay> If I do, do I still need the /boot partition as well ?
[00:40] <Enissay> okay, dumb question... nvm :D
[00:48] <leftyfb> Enissay: why are you manually partitioning the drive?
[01:41] <MrPockets> Sorry if I'm dense, but I believe the samba client on 20.04 no longer supports smbv1?
[01:42] <MrPockets> and I'm really sturgglign with trying to google how to tell it to support v1
[01:44] <leftyfb> MrPockets: why do you think you need smbv1?
[01:45] <MrPockets> Because I know this old NAS to only support v1 and since upgrading I get "Vailed to mount Windows share: Software caused connection abort" when trying to browse to it
[01:45] <MrPockets> And I get protocol error when using smbclient to mount
[01:47] <MrPockets> So while I'm not certain thats the issue, I'm not certain its not.
[01:47] <leftyfb> MrPockets: https://askubuntu.com/questions/1265923/configuring-20-04-samba-for-smbv1
[01:49] <MrPockets> mm yes i did try that
[01:49] <MrPockets> though
[01:50] <MrPockets> I read better and moved the client min ver line up under "workgroup" and now it works.  So, thanks for helping my idiocy and i appreciate your petience for dealing with people like me
[04:11] <apteryx> hi! I'm installing an application via a .deb archive, but the icon is not shown in the searching its name in the dash (I get a generic empty icon).
[04:11] <apteryx> the icons are correctly installed under /usr/share/icons/hicolor.  What could be wrong here?
[04:13] <leftyfb> apteryx: what application and what version of ubuntu are you trying to install it on?
[04:13] <apteryx> I'm installing jami-qt from a Guix-generated .deb (I'm working on the generator myself).
[04:14] <apteryx> the "integration" with the Ubuntu 20.04 host is done by placing a few files in the standard places
[04:15] <apteryx> such as /usr/bin/jami-qt, /usr/share/applications/jami-qt.desktop, /usr/share/metainfo/jami-qt.appdata.xml, /usr/share/icons/hicolor/48x48/apps/jami.png and /usr/share/icons/hicolor/scalable/apps/jami.svg.
[04:16] <apteryx> is there an icon cache to refresh after installing?  I don't see this done in the official jami-qt .deb offered for ubuntu here: https://dl.jami.net/manual-nightly/ubuntu_20.04/
[04:23] <apteryx> the icon shown instead of jami.svg or jami.png is a gear (two gears when viewed from the Ubuntu software store), which I believe is the icon shown when no icon was found.
[04:30] <soreau> if anyone wants to try wayfire, it's here https://github.com/soreau/wayfire-debs
[04:35] <apteryx> interestingly the icon in the tray is OK
[04:35] <apteryx> (system tray)
[04:38] <apteryx> uh, it seems that 'for d in /usr/share/icons/*; do sudo gtk-update-icon-cache -f $d; done' did it.
[04:39] <apteryx> would that not happen automatically when installing via apt?
[04:45] <alkisg> apteryx: as a test, try to install a program like htop, which updates the mime and icon database on its postinst. If this fixes your icon issue as well, then look into the update-mime-database and update-icon-cache commands
[04:53] <apteryx> to be clear, I installed the package using 'dpkg -i' in my last experiments.  Would that change something?
[04:53] <apteryx> alkisg: will do, thanks
[07:32] <jjakob> on 18.04 I can't edit resolv.conf, says it can't write, even though it's root rw. that's after I tried editing netplan config and netplan apply and rebooting the whole thing, it still didn't change
[07:35] <jjakob> netplan apply said the interface is still up so it's not changing it
[07:35] <jjakob> but a reboot should've changed it but didn't
[07:40] <jjakob> rm: cannot remove '/etc/resolv.conf': Operation not permitted
[07:41] <jjakob> yet I'm root: id -u 0
[07:45] <vallaseven7> Hello
[07:46] <toddc> vallaseven7: welcome
[07:46] <vallaseven7> :)
[10:27] <MrGeneral> f
[10:27] <MrGeneral> f
[10:31] <Mekaneck> MrGeneral: any Ubuntu support question?
[10:32] <MrGeneral> Sorry no
[10:32] <MrGeneral> Sorry for typing!
[12:04] <BluesKaj> Hi all
[12:18] <coz_> good morning to all
[12:31] <apteryx> alkisg_web: installing htop doesn't resolve the icons cache issue
[12:31] <apteryx> I'm starting to believe that the md5sums is necessary for the icon cache machinery
[12:32] <apteryx> my generated .deb doesn't have one (it's an optional feature)
[13:30] <apteryx> where can I find the code for the appstream generator used by Debian & Ubuntu (I think?).  It seems to be the component responsible for integrating the icons nicely with the system upon installing a .deb.
[13:35] <ogra> apteryx, probably rather a question for #ubuntu-devel or #ubuntu-desktop (i think that backend runs over the archive and snap store though ... somewhere in the infrastructure)
[13:36] <apteryx> ogra: OK, will do, thanks!
[14:03] <Ronalds_Mazitis_> node.js app seem to run only on 20.04 and not 18.04
[14:03] <Ronalds_Mazitis_> same npm version
[14:03] <Ronalds_Mazitis_> index.mjs:13
[14:03] <Ronalds_Mazitis_> import * as http from 'http';
[14:03] <Ronalds_Mazitis_> SyntaxError: Unexpected token import
[14:03] <Ronalds_Mazitis_> node-v14.17.1 on both systems
[14:32] <Ronalds_Mazitis_> hello anybody?
[14:32] <wez> hi
[14:32] <Ronalds_Mazitis_> my plan is to
[14:32] <Ronalds_Mazitis_> develop a game
[14:33] <Ronalds_Mazitis_> particularly using this  https://github.com/lv88h/Quick_3D_MMORPG
[14:33] <Ronalds_Mazitis_> for some reason I can start node server only from 20.04
[14:34] <Ronalds_Mazitis_> on virtualbox
[14:34] <Ronalds_Mazitis_> I have same npm versions
[14:34] <Ronalds_Mazitis_> also I'm really thinking time had gone backwards at some point
[14:34] <Ronalds_Mazitis_> and we need to crack this
[14:34] <Mekaneck> !patience | Ronalds_Mazitis_
[14:35] <Ronalds_Mazitis_> Mekaneck, well I can wait infinity till I get the things I want besides damn bits of data
[14:36] <Ronalds_Mazitis_> destiny made You stay in your place right
[14:36] <Mekaneck> Ronalds_Mazitis_: ask again later
[14:37] <Mekaneck> if you're that impatient, search the web
[14:44] <dongcarl> Hi I'm wondering if there's a place I can track ubuntu's glibc package in a git repo, like salsa for debian: https://salsa.debian.org/glibc-team/glibc
[14:46] <lotuspsychje> dongcarl: official packages usualy tracked/bugged on launchpad unless the snaps, its the maintainers choice
[14:47] <rbasak> dongcarl: https://git.launchpad.net/ubuntu/+source/glibc - except that this is inverted - it's a git view of what was done, rather than the place that the package is maintained.
[14:48] <rbasak> It looks like https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/glibc is where the package is actually maintained
[14:48] <rbasak> However, like Salsa in Debian, that may or may not match the actual package received by users.
[14:49] <dongcarl> rbasak: Huh! How did you find that second link?
[14:49] <rbasak> dongcarl: Vcs-Browser from https://git.launchpad.net/ubuntu/+source/glibc/tree/debian/control
[14:49] <rbasak> That's the metadata field where a packager _can_ choose to point to a VCS repository
[14:49] <rbasak> However in Ubuntu it's often unchanged from Debian
[14:50] <rbasak> (in this case it wasn't)
[14:50] <dongcarl> Ah very cool, thank you!
[14:52] <dongcarl> rbasak: How would one find the first link (for a given package, say, gcc)
[14:53] <rbasak> dongcarl: it currently only exists for most packages in the main component. It's not yet deployed archive-wide. But glibc and gcc are included.
[14:53] <rbasak> Just replace the source package name in the URL. The rest should stay the same
[14:53] <dongcarl> rbasak: Cool, many thanks!
[14:56] <deeeepsteep> hello
[14:57] <deeeepsteep> do people still use irc?
[14:57] <BrianBlaze> hi
[14:57] <matsaman> good question
[14:57] <BrianBlaze> yes you're not the only one :)
[14:57] <deeeepsteep> :)
[14:59] <Mekaneck> !ot | deeeepsteep
[14:59] <wez> Is deeeepsteep similar to dubstep?
[14:59] <Mekaneck> wez you too
[14:59] <Mekaneck> take it to offtopic please
[14:59] <deeeepsteep> no its a mr robot reverence
[14:59] <wez> Mekaneck: ?
[15:00] <Mekaneck> wez: you guys are chat about offtopic things. This Channel is for ubuntu support only
[15:00] <Mekaneck> chat/chatting
[15:00] <Mekaneck> clear enough imho
[15:01] <wez> Mekaneck: Lets get down to the Ubuntu then!
[15:01] <Mekaneck> wez just cut it
[15:02] <wez> Mekaneck: ?
[15:02] <Mekaneck> stop
[15:02] <wez> I am being ontopic nbow
[15:02] <wez> Can I use Ubuntu without needing snaps?
[15:03] <wez> I don't really like the performance drop when using them
[15:03] <wez> Is there a command to ignore packages that try to install them?
[15:03] <sixwheeledbeast> you don't have to have snaps currently, but you may loose a few default applications
[15:03] <sixwheeledbeast> unofficial advice but you could remove snapd
[15:04] <Mekaneck> wez:  remove snap from your system if you don't need or like them
[15:04] <Str1x> sixwheeledbeast: i was about to say
[15:04] <Str1x> you can remove snapd
[15:04] <sixwheeledbeast> Last time I suggested this I was told not to suggest this, but I have no problem with it.
[15:05] <wez> Mekaneck: Are there any deb packages that installs them?
[15:05] <wez> or only snapd?
[15:05] <sixwheeledbeast> some debs do but only a small amount
[15:05] <Mekaneck> snap and deb are two different things and debs don't pull 'm in afaik
[15:05] <Mekaneck> sudo apt autoremove --purge snapd
[15:05] <Mekaneck> and done
[15:05] <Str1x> wez: remove all snap packages first
[15:05] <sixwheeledbeast> apt has a placeholder package that points to snap
[15:06] <sixwheeledbeast> for some packages
[15:06] <wez> Str1x: Yeah I noticed there were a ton installed by default
[15:06] <wez> I didn't like that
[15:06] <sixwheeledbeast> if you tried to install these it would pull snap in again so you would have to pin it
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <EMOOOOOO> A
[15:07] <Mekaneck> yay... troll time
[15:07] <sixwheeledbeast> a ton seems excessive, I recall "a handful"
[15:11] <matsaman> Mekaneck: that's just spam
[15:20] <wez> Mekaneck: Lets discuss snap, why is it installed for?
[15:21] <Mekaneck> i'm not discussiing anything, please stop asking me please
[15:21] <lotuspsychje> !discuss | wez
[15:22] <lotuspsychje> we got a nice discuss channel start your topic there wez
[15:22] <wez> lotuspsychje: Thank you!
[15:23] <wez> This is a very helpful community
[15:23] <sixwheeledbeast> i see an application for it but i just don't want it as default.
[15:24] <leftyfb> !snap | wez
[15:25] <wez> leftyfb: I know what they try to achieve, but they do it inefficiently
[15:25] <wez> I want to know if there is a way to fix that
[15:25] <wez> squashfs is the worst
[15:25] <leftyfb> wez: feel free to file a bug
[15:25] <wez> leftyfb: Do you know the link?
[15:26] <leftyfb> wez: https://bugs.launchpad.net/snapd
[15:26] <wez> cheers!
[15:33] <ogra> wez, there is also the #snappy channel where the devs work ... and for discussions around the snap ecosystem you should use forum.snapcraft.io ...
[15:33] <wez> I will get on that, cheers! and thanks!
[16:39] <apb1963> Greetings #ubuntu!
[16:40] <apb1963> I noticed a variety of warnings & errors in syslog.  https://paste.ubuntu.com/p/FqpvNHwNds/
[16:45] <apb1963> Possibly the most important one is here: "Jun 29 09:03:09 yellow update-notifier.desktop[290201]: ERROR:root:free space check failed" (and more).  When in fact I have 47GB free.
[16:47] <apb1963> I'm sure I don't have to point out: "Jun 29 09:10:21 yellow gnome-shell[2902]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x62000f8
[16:47] <apb1963> Jun 29 09:10:50 yellow xdg-desktop-por[302300]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
[16:47] <apb1963> " That follows soon after.
[16:51] <apb1963> Please tag my nick when responding... I'll be in another window.  Thanks!
[17:11] <Ronalds_Mazitis_> hey
[17:11] <Ronalds_Mazitis_> so
[17:11] <Ronalds_Mazitis_> why node.js project does not work on 18.04 but on 20.04 with same npm version?
[17:12] <Ronalds_Mazitis_> Uploaded file: https://uploads.kiwiirc.com/files/4b0ac5e7e4017dbe2b99ef4c43530f23/pasted.txt
[17:23] <alkisg_web> Ronalds_Mazitis_, what's the output of `node -v` in both systems?
[18:13] <BrofessorXD> hello :) does anyone know why i'm only able to click the "library" tab on my Steam installation? Can't even find properties under >file menu
[18:17] <sixwheeledbeast> maybe remove and reinstall?  There is no "file" or "properties"  tho
[18:18] <sarnold> maybe file a bug with steam?
[18:18] <sixwheeledbeast> Steam > Settings or View > Settings maybe
[18:19] <sixwheeledbeast> if you have an current vanilla Ubuntu installation Steam support may help
[18:28] <ApostleInTriumph> Hello. I've two directories containing M and N files each. I'd like to sample m and n random files from each and copy to a new directory. where m<M, n<N. How do I go about?
[18:30] <sarnold> ApostleInTriumph: if it were me I'd probably do something like ls | shuf | head -10 ; ls | shuf | head -20   to get the files..
[19:27] <yates> i apparently have a package installed from a ppa as shown from the APT-Sources here: http://paste.ubuntu.com/p/SxtPm3Przt/
[19:27] <yates> what is the command to install that on another ubuntu system?
[19:28] <leftyfb> yates: https://launchpad.net/~matteosecli/+archive/ubuntu/latexml
[19:36] <octav1a> Usb headset worked fine yesterday, but now it won't show in sound devices. Tried a few USB ports. dmesg shows the device detected without error. What can I try to get it to show up in the list of available sound devices?
[19:37] <sarnold> octav1a: pavucontrol usually helps these sorts of things
[19:37] <octav1a> I should install that? What for?
[19:39] <sarnold> when you run it, it helps you see what devices are on beng used for which applications
[19:39] <nhasian> join #intune
[19:39] <nhasian> oops
[19:39] <octav1a> Okay I installed it but in the "output devices" and "input devices" , it's still only showing the one built-in audio and not the USB one.
[19:39] <sarnold> :(
[19:50] <nuala> I'm running some tcpdump and see a lot `ARP, Request who-has <somedevice>.local tell <ap_ip>` appear. like 50 of them, every 30 seconds. It seems these are all devices I once was in the same WiFi with? mostly asking out of curiosity…
[19:52] <sarnold> nuala: sounds reasonable enough; the kernel try to maintain their arp tables to know which machines are reachable, and how to reach them
[19:52] <sarnold> nuala: you can run 'ip n' (short for neighbor, but I'm not sure I know how to spell that) to see the kernel's current arp table
[20:00] <nuala> yes `ip n` shows what currently is connected to our WiFi.. yeah I'm sure its fine just ... hmm.. curious thing.
[21:19] <goddard> im still getting random lockups
[21:19] <goddard> when i come back to my computer after the screen turns off
[21:19] <goddard> i tested my memory and it did 2 passes in memtest with no errorrs
[21:19] <goddard> so safe to say it is probably something else
[21:20] <goddard> think it is some gnome bug?
[21:20] <matsaman> goddard: nvidia?
[21:21] <goddard> yes
[21:21] <matsaman> that'd be my first suspicion
[21:22] <matsaman> goddard: http://google.com/search?q=ubuntu+nvidia+nomodeset
[22:45] <bodhi> how do I schedule a disk check on the next reboot. I think there is some disk corruption in my vm root disk
[22:48] <sarnold> bodhi: I think kernel command line fsck.mode=force can do it<EMAIL_ADDRESS>[22:48] <bodhi> sarnold: thank you.
[22:58] <netameta> How can i add variables to destop entry ?
[22:58] <netameta> I need to run terminator --maximise --layout=4screens when the icon is clicked
[23:07] <netameta> How can i add parameter to destop entry ?
[23:24] <bodhi> sarnold: I do not have systemd-fsck
[23:25] <sarnold> argh ..
[23:25] <sarnold> bodhi: what release are you on? hmm
[23:26] <bodhi> 20.04
[23:26] <Endermen1094> how can i make my Gentoo install appear with my Xubuntu grub screen
[23:27] <sarnold> bodhi: hm, that's what I've got too, and the systemd-fsck stuff is in the main systemd package
[23:29] <shonudo> Endermen1094: it didn't add it automatically after you selected your install partition for xubuntu?
[23:29] <shonudo> i think there's a moment where you get to review what the conf will look like
[23:29] <Endermen1094> I currently have it set in the bootloader of my laptop  to boot xubuntu-> Gentoo
[23:29] <Endermen1094> It did not
[23:29] <shonudo> chainloader setup?
[23:30] <shonudo> i'm not sure what you mean by "boot xubuntu > gentoo"
[23:30] <shonudo> and odd that it did not
[23:31] <Endermen1094> first my device tries to boot  xubuntu and when i press e and then Esc it brings up my gentoo grub screen
[23:33] <Endermen1094> os-prober detects my gentoo install
[23:33] <oerheks> so gentoo-grub is primairy
[23:34] <oerheks> probably chainloading too?
[23:35] <Endermen1094> let me connect to here from my phone so i can continue  talking here
[23:36] <Endermen10941> Ok this is me from my phone
[23:37] <shonudo> oerheks: yeah, i thought it might be a chainloader setup too
[23:39] <Endermen10941> https://photos.app.goo.gl/bey64f3nThM1aCRx9 this is the bootloader from bios
[23:45] <Endermen10941> Windoes Boot Manager is a relic of its pre installed os


[00:10] <Wimpress> Found a release critical issue in Ubuntu MATE 19.10.
[00:11] <Wimpress> I have a suitable workaround, which is to seed cryptsetup to prevent Ubiquity automatically removing.
[00:11] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (eoan-proposed/universe) [1.252 => 1.253] (ubuntu-mate)
[00:11] <Wimpress> Could someone plase let that one ^ in please? I need to respin the Ubuntu MATE iso.
[00:12] <Wimpress> If you could also let ubuntu-mate-artwork 19.10.9 through too, that would be great. New wallpaper in that, so would be good to have on the beta.
[00:55] <infinity> Wimpress: That bug's been there since cosmic or disco...
[00:55] <infinity> Wimpress: I'm going to find a proper solution to it, but I don't consider it beta critical.
[00:56] <infinity> Wimpress: Also, I'm respinning later for an efivars bug, so no need to do it yourself.
[01:07] <Wimpress> infinity: Thanks for taking a look.
[01:07] <Wimpress> It has been fixed in the past.
[01:07] <Wimpress> Ubuntu MATE is the only flavour exhibiting the issue.
[01:08] <Wimpress> Any chance you can let that update meta package in for the time being.
[01:08] <infinity> Wimpress: Uhh.  MATE is very much not the only flavour with the cryptsetup issue.
[01:08] <Wimpress> The issue is a post-install `apt autoremove` will remove cryptsetup and then the system won't come up on reboot.
[01:08] <infinity> Wimpress: Yes.  That's not specific to MATE.
[01:09] <Wimpress> infinity: Well, we've tested several flavours this evening.
[01:09] <infinity> Not very well, then?
[01:09] <Wimpress> Well enough to demonstrate that the issue isn't present in Ubuntu, Xubuntu and Kubuntu.
[01:09] <infinity> I mean, I know for a fact it's in Ubuntu and Xubuntu.
[01:10] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1841672
[01:10] <infinity> Kubuntu has the same workaround you're about to do here.
[01:10] <Wimpress> https://bugs.launchpad.net/ubuntu/eoan/+source/ubuntu-mate-meta/+bug/1801629
[01:10] <Wimpress> Those bugs have some background.
[01:10] <Wimpress> Ahh, interesting about Kubuntu.
[01:11] <Wimpress> So, is that a no on the workaround meta package?
[01:11] <infinity> Anyhow, I'll let it in like this for now.
[01:11] <Wimpress> Cheers. Much appreciated.
[01:11] <infinity> Nah, if you want to do this for now, whatevs.  But we need to fix it in ubiquity to get it fixed properly.
[01:12] <infinity> (and in calamares, for the weirdos that use that)
[01:12] <infinity> Basically, the short answer is that "if we install on lvm, crypt, btrfs, etc, we should mark those packages manually installed".
[01:12] <Wimpress> Yeah, I realise a proper fix is required. Was just trying to find a way to prevent unexpected breakage.
[01:12] <Wimpress> infinity: Right.
[01:13] <infinity> But I will reiterate that this bug has been there for two cycles, so people just fail at testing, apparently.
[01:13] <Wimpress> https://git.launchpad.net/livecd-rootfs/commit/?id=b2db5bf3658f33dfaf3261bdc73f41be72acd374
[01:13] <Wimpress> That was an attempt to fix the issue.
[01:13] <infinity> I know.
[01:13] <Wimpress> With people claiming the issue was fixed.
[01:13] <Wimpress> And Ubuntu MATE 19.04 is fine.
[01:16] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-meta [source] (eoan-proposed) [1.253]
[01:16] -queuebot:#ubuntu-release- Unapproved: accepted xe-guest-utilities [source] (eoan-proposed) [7.10.0-0ubuntu2]
[01:16] <infinity> People claim a lot of things.  I'll be doing a deep dive on it later this week.
[01:17] <infinity> Oh, 19.04 might have been fine because we broke it differently.  Right.
[01:17] <infinity> Then we unbroke it.
[01:17] <infinity> Which returns it to broken.
[01:17] <infinity> Anyhow.  Will sort later.  Don't worry about your respins.  I'll do them before bed.
[01:20] <Wimpress> infinity: Thank you.
[01:22] <Wimpress> infinity: I confirm the Xubuntu 19.10 daily is not affected.
[01:22] <Wimpress> Just retested it.
[01:25] <infinity> How bizarre.
[01:25] <Wimpress> ikr
[01:34] <Wimpress> Ubuntu Desktop 19.10 daily is also not affected.
[02:08] -queuebot:#ubuntu-release- Unapproved: wlcs (eoan-proposed/universe) [1.1.0-0ubuntu2 => 1.1.0-0ubuntu3] (no packageset)
[02:09] -queuebot:#ubuntu-release- Unapproved: accepted wlcs [source] (eoan-proposed) [1.1.0-0ubuntu3]
[02:26] -queuebot:#ubuntu-release- Unapproved: ubuntu-budgie-meta (eoan-proposed/universe) [0.51 => 0.52] (personal-fossfreedom, ubuntu-budgie)
[02:28] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-budgie-meta [source] (eoan-proposed) [0.52]
[02:28] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-meta (eoan-proposed/universe) [0.38 => 0.39] (ubuntukylin)
[02:28] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-meta [source] (eoan-proposed) [0.39]
[02:39] -queuebot:#ubuntu-release- Unapproved: debian-keyring (eoan-proposed/universe) [2019.08.23 => 2019.09.24] (no packageset) (sync)
[02:40] -queuebot:#ubuntu-release- Unapproved: accepted debian-keyring [sync] (eoan-proposed) [2019.09.24]
[02:58] -queuebot:#ubuntu-release- Unapproved: tiff (eoan-proposed/main) [4.0.10+git190818-1 => 4.0.10+git190903-1] (core) (sync)
[05:16] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.9 => 19.10.10] (core)
[05:18] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity [source] (eoan-proposed) [19.10.10]
[05:21] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.9 => 19.10.10] (core)
[05:22] <vorlon> infinity: ^^ beta-critical; out-of-date udebs. including apt-setup, which is needed to restore i386 foreign-arch on amd64.
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Eoan Beta] has been updated (20190925)
[05:22] <vorlon> (self-reviewing and accepting)
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Eoan Beta] has been updated (20190925)
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Eoan Beta] has been updated (20190925)
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Eoan Beta] has been updated (20190925)
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Eoan Beta] has been updated (20190925)
[05:22] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Eoan Beta] has been updated (20190925)
[05:23] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (eoan-proposed) [19.10.10]
[05:28] <jibel> FYI, 2 showstoppers on ubuntu desktop right now for beta: bug 1844509 and bug 1845198
[05:29] <infinity> vorlon: If only that had happened before I pressed the mass rebuild button. :/
[05:29] <infinity> Oh well.
[05:30]  * infinity cancels them all.
[05:35] <infinity> vorlon: Aaand, broken X gives you an FTBFS.  Fixing.
[05:42] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-drivers-common [source] (bionic-proposed) [1:<IP_ADDRESS>]
[05:59] <infinity> jibel: I'll build fresh ISOs with the other bits that have landed anyway.  If either bug mysteriously goes away, you can side-eye that really hard.  Otherwise, I'll expect fixes when I wake up. :P
[07:23] -queuebot:#ubuntu-release- Unapproved: bolt (eoan-proposed/main) [0.8-3~ubuntu3 => 0.8-4] (desktop-core, ubuntu-server) (sync)
[07:27] -queuebot:#ubuntu-release- Unapproved: spirv-llvm-translator (eoan-proposed/universe) [8.0.1-1 => 9.0.0-0ubuntu1] (no packageset)
[07:28] -queuebot:#ubuntu-release- Unapproved: accepted spirv-llvm-translator [source] (eoan-proposed) [9.0.0-0ubuntu1]
[07:29] <tjaalton> infinity: broken X?
[07:31] <infinity> tjaalton: FTBFS on amd64, making it uninstallable on !amd64.
[07:31] -queuebot:#ubuntu-release- Unapproved: intel-opencl-clang (eoan-proposed/universe) [8.0.1-0ubuntu2 => 9.0.0-0ubuntu1] (no packageset)
[07:32] <tjaalton> huh
[07:32] -queuebot:#ubuntu-release- Unapproved: accepted intel-opencl-clang [source] (eoan-proposed) [9.0.0-0ubuntu1]
[07:32] -queuebot:#ubuntu-release- Unapproved: libgdata (eoan-proposed/main) [0.17.11-1 => 0.17.11-3] (ubuntu-desktop) (sync)
[07:33] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator [i386] (eoan-proposed/universe) [9.0.0-0ubuntu1] (no packageset)
[07:33] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator [ppc64el] (eoan-proposed/universe) [9.0.0-0ubuntu1] (no packageset)
[07:35] <infinity> tjaalton: To be clear, I didn't "fix" anything, I just deleted it from -proposed. :P
[07:35] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator [amd64] (eoan-proposed/universe) [9.0.0-0ubuntu1] (no packageset)
[07:35] <infinity> tjaalton: Feel free to actually upload a fix.
[07:35] <tjaalton> I don't understand what would break it
[07:37] <tjaalton> as if it didn't hit build-indep:
[07:37] <tjaalton> I only added a new patch in the new version
[07:38] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator [armhf] (eoan-proposed/universe) [9.0.0-0ubuntu1] (no packageset)
[07:39] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator [arm64] (eoan-proposed/universe) [9.0.0-0ubuntu1] (no packageset)
[07:42] <infinity> tjaalton: Could be debhelper's fault, I suppose.
[07:42] <tjaalton> yeah
[07:43] <tjaalton> the patch is semi-urgent only for a bionic sru, so I'll try to figure out what caused this
[07:44] <tjaalton> should happen on debian too
[07:49] <tjaalton> and does
[08:29] <Laney> were those cancelled livefs builds on purpose?
[08:29] <Laney> infinity:
[08:38] <cjwatson> Laney: IRC from 05:30 UTC
[08:39] <Laney> ah yes, thanks
[08:40] <Laney> something is really wrong with page up/page down in my irssi/tmux
[08:41] <Laney> it only pages up half the screen, and then when I page down it's replaced by different contents
[08:55] <apw> Laney, that almost feels familiar ... is that a ncurses based thing?  i am sure i saw something similar in mutt for a little while recently
[08:59] <Laney> yeah
[08:59] <Laney> (I think anwyay)
[08:59] <Laney> I've not tried mutt inside tmux though
[08:59] <Laney> it looks like this bug which people are reporting in WSL: https://github.com/Maximus5/ConEmu/issues/1444
[09:00] -queuebot:#ubuntu-release- Unapproved: mir (eoan-proposed/main) [1.4.0-0ubuntu2 => 1.4.0-0ubuntu3] (ubuntu-desktop)
[09:25] -queuebot:#ubuntu-release- Unapproved: thunderbird (eoan-proposed/main) [1:68.0+build6-0ubuntu1 => 1:68.1.0+build3-0ubuntu1] (mozilla, ubuntu-desktop)
[10:17] -queuebot:#ubuntu-release- Unapproved: enigmail (eoan-proposed/universe) [2:2.0.12+ds1-1 => 2:2.1.2-0ubuntu1] (mozilla)
[10:17] -queuebot:#ubuntu-release- Unapproved: mozilla-devscripts (eoan-proposed/universe) [0.53 => 0.53-0ubuntu1] (no packageset)
[10:18] -queuebot:#ubuntu-release- Unapproved: accepted mozilla-devscripts [source] (eoan-proposed) [0.53-0ubuntu1]
[10:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Eoan Beta] has been updated (20190925)
[10:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Eoan Beta] has been updated (20190925)
[10:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Eoan Beta] has been updated (20190925)
[10:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Eoan Beta] has been updated (20190925)
[10:28] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:30] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:32] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:35] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:35] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:36] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Eoan Beta] has been updated (20190925)
[10:42] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Eoan Beta] has been updated (20190925.1)
[10:44] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi3 [Eoan Beta] has been updated (20190925)
[10:44] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi3 [Eoan Beta] has been updated (20190925)
[10:44] <rbalint> infinity, Laney: could you please merge https://code.launchpad.net/~rbalint/britney/autopkgtest-eoan-hints/+merge/373126 to let systemd in? the armhf issue is not a regression from 241
[10:55] -queuebot:#ubuntu-release- Unapproved: apt (disco-proposed/main) [1.8.3 => 1.8.4] (core)
[11:01] <mdeslaur> could someone please release python-django? it's a security update and all tests are now passing
[11:14] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Eoan Beta] has been updated (20190925)
[12:11] <infinity> rbalint: We're in the middle of a freeze, systemd isn't going in anyway.
[12:12] <infinity> mdeslaur: Can it wait until Thursday?
[12:12] <mdeslaur> infinity: sure
[12:12] <mdeslaur> infinity: what's thursday?
[12:13] <infinity> mdeslaur: Beta.
[12:13] <mdeslaur> oh sure, no rush
[12:30] -queuebot:#ubuntu-release- Unapproved: libdrm (eoan-proposed/main) [2.4.99-1 => 2.4.99-1ubuntu1] (core, xorg)
[12:31] <rbalint> infinity, there is a granted FFe for 242, but i can understand if you consider it too late now (LP: #1843755)
[12:37] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (bionic-proposed/main) [1:<IP_ADDRESS> => 1:<IP_ADDRESS>] (desktop-core, ubuntu-server)
[12:42] <rbalint> infinity, so do you consider the FFe not applying anymore? then i need to switch to cherry-pick mode for eoan
[12:43] -queuebot:#ubuntu-release- Unapproved: qbittorrent (eoan-proposed/universe) [4.1.6-1 => 4.1.7-1] (no packageset) (sync)
[12:43] -queuebot:#ubuntu-release- Unapproved: accepted qbittorrent [sync] (eoan-proposed) [4.1.7-1]
[12:43] -queuebot:#ubuntu-release- Unapproved: dino-im (eoan-proposed/universe) [0.0.git20190909.9950742-1 => 0.0.git20190916.f746ce7-1] (no packageset) (sync)
[12:44] -queuebot:#ubuntu-release- Unapproved: accepted dino-im [sync] (eoan-proposed) [0.0.git20190916.f746ce7-1]
[13:00] <santa_> dear release wizards,
[13:01] <santa_> I have seen you deleteted the latest xorg-server upload (..ubuntu4) I guess because it failed to build for amd64
[13:03] <apw> santa_, "FTBFS on amd64; breaks the world"
[13:03] <santa_> the ubuntu3 version also fails, I have been investigating this issue and I plan to continue this afternoon. if you don't have any objections I plan to send a mail to ubuntu-devel explaining all the thing
[13:04] <santa_> (once I get all the data)
[13:06] <tjaalton> santa_: it's because of debhelper
[13:06] <tjaalton> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941128
[13:08] <LocutusOfBorg> please reject llvm in unapproved
[13:08] <LocutusOfBorg> a new version will be syncd later
[13:09] <santa_> tjaalton: ah, you are here, you are one of the persons I was expecting to talk to. I know it's debhelper. I also bisected the thing and found the offending commit
[13:09] <tjaalton> cool
[13:09] <tjaalton> which one?
[13:09] <santa_> let me see...
[13:10] <santa_> 2fd94649173464628cd732ee20834bb634fc62a2 "Rewrite sequence handling..."
[13:11] <tjaalton> as I feared
[13:11] <santa_> I found also another possible issue, this one with xorg-server itself
[13:12] <tjaalton> ok?
[13:13] <santa_> as you probably already know the xorg-server fails because of the source code tar.gz generation
[13:13] <tjaalton> yes
[13:13] <tjaalton> binary-indep is skipped
[13:13] <tjaalton> err, build-indep
[13:13] -queuebot:#ubuntu-release- Unapproved: psi-plus (eoan-proposed/universe) [1.4.554-3 => 1.4.554-3ubuntu1] (no packageset)
[13:13] <LocutusOfBorg> isn't this an RC bug in Debian too?
[13:13] <tjaalton> already filed
[13:14] <LocutusOfBorg> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debhelper&archive=no&pend-exc=pending-fixed&pend-exc=fixed&pend-exc=done&sev-inc=critical&sev-inc=grave&sev-inc=serious&repeatmerged=no
[13:14] <LocutusOfBorg> I can't see...
[13:14] <tjaalton> well, the severity could be bumped maybe
[13:14] -queuebot:#ubuntu-release- Unapproved: accepted psi-plus [source] (eoan-proposed) [1.4.554-3ubuntu1]
[13:14] <LocutusOfBorg> doko, ^^ another dh_dwz sadness
[13:14] <santa_> I know. I checked with "dh build --no-act". in any case that made me look why that source code generation was done in the first place, so doing some "archeology" I found the debian bug requesting to do that...
[13:15] <santa_> (lets see if I find the link haha)
[13:17] <santa_> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730552
[13:18] <tjaalton> yes, and?
[13:18] <santa_> so apparently the guy in charge of the tigervnc wanted the source code patched and autoreconfed
[13:19] <santa_> so if you open the diff he submitted you will see the source code generation happens _after_ the patching and autoreconf
[13:19] <santa_> and back then, the xorg package wasn't using dh yet
[13:20] <tjaalton> alright
[13:21] <santa_> so if you look @ a recent xorg-server build log, for example: https://launchpadlibrarian.net/440421585/buildlog_ubuntu-eoan-amd64.xorg-server_2%3A1.20.5+git20190820-0ubuntu3_BUILDING.txt.gz
[13:22] <tjaalton> yes I know
[13:22] <tjaalton> they had 3y to complain ;)
[13:22] <santa_> you will see the .tar.gz source generation happens before the patching and autoreconf
[13:22] -queuebot:#ubuntu-release- Unapproved: cinder (eoan-proposed/main) [2:15.0.0~b1~git2019080709.0a0d55d8a-0ubuntu1 => 2:15.0.0~b3~git2019092509.cea6e823c-0ubuntu1] (openstack, ubuntu-server)
[13:23] <santa_> yes they had time to complain, I just wanted this to be known
[13:24] <tjaalton> notified the person who did the conversion to dh (not me, actually)
[13:25] <santa_> also I tought you might want to fix it, which could fix the FTBFS along
[13:25] <santa_> of course if there's an underlying debhelper issue (it seems to me there is) that would be nice to get it fixed
[13:29] <santa_> tjaalton: I could try to fix the source .tar.gz generation this afternoon if you are interested
[13:30] <santa_> and test tigervnc build against it
[13:30] <tjaalton> feel free
[13:31] <santa_> ack. of course not an excuse to not fix debhelper
[13:32] -queuebot:#ubuntu-release- Unapproved: openjdk-8 (eoan-proposed/universe) [8u232-b04-0ubuntu5 => 8u232-b04-0ubuntu6] (no packageset)
[13:36] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-8 [source] (eoan-proposed) [8u232-b04-0ubuntu6]
[13:42] <seb128> can the enigmail  in the queue be approved? it's a version compatible with tb 68 (which is what we have currently in eoan-proposed)
[14:04] -queuebot:#ubuntu-release- Unapproved: grubzfs-testsuite (eoan-proposed/universe) [0.4 => 0.4.1] (no packageset)
[14:05] -queuebot:#ubuntu-release- Unapproved: accepted grubzfs-testsuite [source] (eoan-proposed) [0.4.1]
[14:11] <seb128> apw, ^ can you do enigmail? or is there anyone in that tz to ping for reviews atm?
[14:11] <apw> /
[14:11] <apw> seb128, /me has a look
[14:12] <rbalint> infinity, Laney: could you please at lease merge the systemd hints?
[14:13] <seb128> apw, thx
[14:13] <apw> seb128, a 1.5Mb diff ... lovely
[14:14] <seb128> apw, right, well what we currently have in the archive doesn't work with the new tb
[14:14] <seb128> and it's universe
[14:14] <seb128> so just trust upstream and Olivier for the packaging? ;)
[14:14] <apw> but a 1.5Mb diff
[14:14] <seb128> I know, sorry :/
[14:15] <seb128> apw, option B is to delete enigmal from eoan...
[14:15] <apw> seb128, don't tempt me :)
[14:15] <seb128> :)
[14:16] <Laney> rbalint: I'm spinning a few plates, I will look soon
[14:16] <Laney> you have other release team members in here too though
[14:16] <rbalint> Laney, thanks, and their help is also welcome
[14:20] <apw> seb128, see pm
[14:20] <seb128> apw, I didn't get any, lack of ircnick auth?
[14:20] <apw> lack of ability to use cut-n-paste it seems
[14:25] <apw> oSoMoN, engimail> hey, what changed with this .js that we can include it now?
[14:39] <oSoMoN> apw, the debian maintainer claims that embedding OpenPGP.js is not DFSG-compatible, but I don't see why, he says it's a binary blob, but it clearly isn't, and he hasn't responded to my questions thus far
[14:40] <oSoMoN> the file isn't even minified
[14:40] <apw> oSoMoN, that much is obvious from its 40K lines ...
[14:40] <oSoMoN> it might not be shipped exactly as distributed upstream, but the source is there for anyone to read and inspect, so I don't see a problem with it
[14:41] <oSoMoN> apw, my plan is to unblock the transition with this upload, and when the debian maintainer gets around to updating his package, we can sync back
[14:50] -queuebot:#ubuntu-release- Unapproved: cinder (disco-proposed/main) [2:14.0.1-0ubuntu1 => 2:14.0.1-0ubuntu3] (openstack, ubuntu-server) (sync)
[15:12] -queuebot:#ubuntu-release- Unapproved: ubuntu-wallpapers (eoan-proposed/main) [19.10.1-0ubuntu1 => 19.10.2-0ubuntu1] (desktop-core)
[15:17] -queuebot:#ubuntu-release- Unapproved: gstreamer1.0 (eoan-proposed/main) [1.16.0-3 => 1.16.1-1] (core) (sync)
[15:18] -queuebot:#ubuntu-release- Unapproved: gst-plugins-base1.0 (eoan-proposed/main) [1.16.0-4 => 1.16.1-1] (desktop-core, ubuntu-server) (sync)
[15:19] -queuebot:#ubuntu-release- Unapproved: gosa (eoan-proposed/universe) [2.7.4+reloaded3-9 => 2.7.4+reloaded3-10] (no packageset) (sync)
[15:19] -queuebot:#ubuntu-release- Unapproved: libcommons-compress-java (eoan-proposed/universe) [1.18-2 => 1.18-3] (no packageset) (sync)
[15:20] -queuebot:#ubuntu-release- Unapproved: libextractor (eoan-proposed/universe) [1:1.9-1 => 1:1.9-2] (no packageset) (sync)
[15:20] -queuebot:#ubuntu-release- Unapproved: libstb (eoan-proposed/universe) [0.0~git20190617.5.c72a95d-2 => 0.0~git20190817.1.052dce1-1] (no packageset) (sync)
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted libcommons-compress-java [sync] (eoan-proposed) [1.18-3]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted libstb [sync] (eoan-proposed) [0.0~git20190817.1.052dce1-1]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted libextractor [sync] (eoan-proposed) [1:1.9-2]
[15:21] -queuebot:#ubuntu-release- Unapproved: accepted gosa [sync] (eoan-proposed) [2.7.4+reloaded3-10]
[15:51] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.10 => 19.10.11] (core)
[15:52] <Laney> That's for one of the RC bugs for beta
[15:52] <Laney> rbalint: Now I'll look at your branch
[15:53] -queuebot:#ubuntu-release- Unapproved: grub-installer (eoan-proposed/main) [1.128ubuntu12 => 1.128ubuntu13] (core)
[15:58] <vorlon> Laney: I've just merged rbalint's branch
[15:58] <vorlon> (with a fixup)
[15:58] <vorlon> he had also pinged me directly
[15:58] <Laney> oh right
[15:59] <vorlon> rbalint: ^^ I specifically didn't drop the badtest hint for linux-oem-osp1/5.0.0-1019.21 because it's still referenced in update_excuses for migration of build-essential
[16:34] <xnox> vorlon:  can you please accept https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1838525 into eoan-proposed?
[16:34] <vorlon> xnox: looking.  does this require a d-i and a ubiquity respin?
[16:35] <vorlon> accepted
[16:36] <vorlon> probably not a d-i respin I guess, since grub-installer isn't in the initrd
[16:36] <vorlon> and this only affects the classic server ISO?
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted grub-installer [source] (eoan-proposed) [1.128ubuntu13]
[16:41] <xnox> vorlon:  reported on classic server ISO only, thus will need server iso respin.
[16:41] <xnox> vorlon:  i wouldn't expect desktop to be affected as much, as I believe we run grub-installer differently and /run should be mounted in /target
[16:41] <xnox> but not verified.
[16:42] <xnox> on desktop, we need to install/preserve cryptsetup-initramfs packages anyway..... not sure if juliank did it yet or not
[16:50] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity [source] (eoan-proposed) [19.10.11]
[16:57] <vorlon> xnox: "we run grub-installer differently" - then could this change have a side effect of *un*mounting /run from target before other things are done with it?
[16:57] <vorlon> xnox: cryptsetup-initramfs> I saw ubuntu-mate-meta got an upload yesterday by Wimpress that looked like a workaround for this issue
[16:58] -queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.10 => 19.10.11] (core)
[16:59] <Wimpress> vorlon: Yes, a workaround. Not a fix. Happy to revert it.
[17:00] <Wimpress> When the underlying issue is resolved.
[17:02] <Laney> juliank: guess you can try the ssl cert stuff now
[17:10] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-wallpapers [source] (eoan-proposed) [19.10.2-0ubuntu1]
[17:15] <Laney> if and when there's a respin, that ubiquity should get into it
[17:16] <Laney> feel free to re-upload it if you need to respin ubiquity itself, it's pushed to master
[17:16] <Laney> see you
[17:33] -queuebot:#ubuntu-release- New binary: ubuntu-wallpapers [amd64] (eoan-proposed/main) [19.10.2-0ubuntu1] (desktop-core)
[17:40] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-9 (eoan-proposed/universe) [1:9~+rc5-1~exp1 => 1:9-1] (no packageset) (sync)
[17:49] <juliank> Laney: will play tomorrow
[17:50] <juliank> xnox: we have a problem on desktop with cryptsetup being autoremoved that's being tracked and that was worked around in mata
[17:50] <juliank> * mate
[17:50] <juliank> (ubuntu-mate core, desktop started depeending on cryptsetup, ugh)
[17:58] <juliank> xnox: apparently it's infinity's turn to investigate that cryptsetup further
[18:19] <infinity> rbalint: By "we're in a freeze", I meant beta freeze.  As in, your urgency to migrate systemd won't make it migrate until after I'm done with beta anyway.
[18:29] -queuebot:#ubuntu-release- Unapproved: rejected llvm-toolchain-9 [source] (eoan-proposed) [1:9~+rc5-1~exp2~build1]
[18:31] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (eoan-proposed) [19.10.11]
[18:37] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-9 [sync] (eoan-proposed) [1:9-1]
[19:16] -queuebot:#ubuntu-release- Unapproved: python-blazarclient (eoan-proposed/main) [2.1.0-0ubuntu2 => 2.2.1-0ubuntu1] (ubuntu-server)
[19:17] -queuebot:#ubuntu-release- Unapproved: python-castellan (eoan-proposed/main) [1.3.0-0ubuntu1 => 1.3.1-0ubuntu1] (openstack, ubuntu-server)
[19:19] -queuebot:#ubuntu-release- Unapproved: python-ceilometermiddleware (eoan-proposed/universe) [1.3.0-0ubuntu2 => 1.5.0-0ubuntu1] (openstack)
[19:21] -queuebot:#ubuntu-release- Unapproved: python-cinderclient (eoan-proposed/main) [1:4.2.1-0ubuntu2 => 1:5.0.0-0ubuntu1] (openstack, ubuntu-server)
[19:22] -queuebot:#ubuntu-release- Unapproved: python-glance-store (eoan-proposed/main) [0.29.1-0ubuntu1 => 1.0.0-0ubuntu1] (openstack, ubuntu-server)
[19:23] -queuebot:#ubuntu-release- Unapproved: python-glanceclient (eoan-proposed/main) [1:2.16.0-0ubuntu2 => 1:2.17.0-0ubuntu1] (openstack, ubuntu-server)
[19:25] -queuebot:#ubuntu-release- Unapproved: python-ironic-lib (eoan-proposed/universe) [2.18.0-0ubuntu1 => 2.21.0-0ubuntu1] (no packageset)
[19:26] -queuebot:#ubuntu-release- Unapproved: accepted python-ironic-lib [source] (eoan-proposed) [2.21.0-0ubuntu1]
[19:30] <vorlon> RAOF: you appear to have promoted libxml++2.6 to main without a team subscriber
[19:30] <vorlon> cpaelzer__: ^^ you appear to have signed off on the MIR without a team subscriber
[19:39] -queuebot:#ubuntu-release- Unapproved: iptables (eoan-proposed/main) [1.8.3-2ubuntu4 => 1.8.3-2ubuntu5] (core)
[19:48] -queuebot:#ubuntu-release- Unapproved: accepted iptables [source] (eoan-proposed) [1.8.3-2ubuntu5]
[19:54] -queuebot:#ubuntu-release- Unapproved: python-keystoneauth1 (eoan-proposed/main) [3.15.0-0ubuntu1 => 3.17.1-0ubuntu1] (openstack, ubuntu-server)
[19:55] -queuebot:#ubuntu-release- Unapproved: python-keystoneclient (eoan-proposed/main) [1:3.20.0-0ubuntu2 => 1:3.21.0-0ubuntu1] (openstack, ubuntu-server)
[19:56] -queuebot:#ubuntu-release- Unapproved: python-manilaclient (eoan-proposed/main) [1.27.0-0ubuntu3 => 1.29.0-0ubuntu1] (openstack, ubuntu-server)
[19:57] -queuebot:#ubuntu-release- Unapproved: python-monascaclient (eoan-proposed/main) [1.15.0-0ubuntu1 => 1.16.0-0ubuntu1] (ubuntu-server)
[19:58] -queuebot:#ubuntu-release- Unapproved: python-neutron-lib (eoan-proposed/main) [1.29.0-0ubuntu1 => 1.29.1-0ubuntu1] (ubuntu-server)
[19:59] -queuebot:#ubuntu-release- Unapproved: python-novaclient (eoan-proposed/main) [2:14.2.0-0ubuntu1 => 2:15.1.0-0ubuntu1] (openstack, ubuntu-server)
[20:01] -queuebot:#ubuntu-release- Unapproved: python-octavia-lib (eoan-proposed/universe) [1.2.0-0ubuntu1 => 1.4.0-0ubuntu1] (no packageset)
[20:02] -queuebot:#ubuntu-release- Unapproved: accepted python-octavia-lib [source] (eoan-proposed) [1.4.0-0ubuntu1]
[20:02] -queuebot:#ubuntu-release- Unapproved: python-octaviaclient (eoan-proposed/main) [1.9.0-0ubuntu1 => 1.10.0-0ubuntu1] (ubuntu-server)
[20:07] -queuebot:#ubuntu-release- Unapproved: python-ironicclient (eoan-proposed/main) [2.8.0-0ubuntu1 => 3.0.0-0ubuntu1] (openstack, ubuntu-server)
[20:08] -queuebot:#ubuntu-release- New: accepted ubuntu-wallpapers [amd64] (eoan-proposed) [19.10.2-0ubuntu1]
[20:14] -queuebot:#ubuntu-release- Unapproved: python-os-brick (eoan-proposed/main) [2.9.1-0ubuntu3 => 2.10.0-0ubuntu1] (openstack, ubuntu-server)
[20:14] -queuebot:#ubuntu-release- Unapproved: python-os-ken (eoan-proposed/main) [0.4.0-0ubuntu1 => 0.4.1-0ubuntu1] (ubuntu-server)
[20:15] -queuebot:#ubuntu-release- Unapproved: python-os-vif (eoan-proposed/main) [1.15.1-0ubuntu2 => 1.17.0-0ubuntu1] (ubuntu-server)
[20:18] -queuebot:#ubuntu-release- Unapproved: python-os-win (eoan-proposed/main) [4.3.0-0ubuntu1 => 4.3.2-0ubuntu1] (openstack, ubuntu-server)
[20:18] -queuebot:#ubuntu-release- Unapproved: python-osc-lib (eoan-proposed/main) [1.13.0-0ubuntu1 => 1.14.1-0ubuntu1] (ubuntu-server)
[20:18] -queuebot:#ubuntu-release- Unapproved: python-oslo.cache (eoan-proposed/main) [1.36.0-0ubuntu1 => 1.37.0-0ubuntu1] (openstack, ubuntu-server)
[20:19] -queuebot:#ubuntu-release- Unapproved: python-oslo.concurrency (eoan-proposed/main) [3.29.1-0ubuntu2 => 3.30.0-0ubuntu1] (openstack, ubuntu-server)
[20:21] -queuebot:#ubuntu-release- Unapproved: python-os-api-ref (eoan-proposed/universe) [1.6.1+dfsg1-0ubuntu2 => 1.6.2+dfsg1-0ubuntu1] (no packageset)
[20:22] -queuebot:#ubuntu-release- Unapproved: accepted python-os-api-ref [source] (eoan-proposed) [1.6.2+dfsg1-0ubuntu1]
[20:22] -queuebot:#ubuntu-release- Unapproved: python-openstacksdk (eoan-proposed/main) [0.31.1-0ubuntu2 => 0.36.0-0ubuntu1] (openstack, ubuntu-server)
[20:37] -queuebot:#ubuntu-release- Unapproved: python-openstackdocstheme (eoan-proposed/universe) [1.30.0-0ubuntu3 => 1.31.1-0ubuntu1] (openstack)
[20:41] -queuebot:#ubuntu-release- Unapproved: python-zunclient (eoan-proposed/universe) [3.3.0-0ubuntu2 => 3.5.0-0ubuntu1] (no packageset)
[20:41] -queuebot:#ubuntu-release- Unapproved: accepted python-zunclient [source] (eoan-proposed) [3.5.0-0ubuntu1]
[20:42] -queuebot:#ubuntu-release- Unapproved: python-oslo.db (eoan-proposed/main) [5.0.1-0ubuntu1 => 5.0.2-0ubuntu1] (openstack, ubuntu-server)
[20:42] -queuebot:#ubuntu-release- Unapproved: python-oslo.i18n (eoan-proposed/main) [3.23.1-0ubuntu2 => 3.24.0-0ubuntu1] (openstack, ubuntu-server)
[20:45] -queuebot:#ubuntu-release- Unapproved: python-oslo.config (eoan-proposed/main) [1:6.11.0-0ubuntu1 => 1:6.11.1-0ubuntu1] (openstack, ubuntu-server)
[20:45] -queuebot:#ubuntu-release- Unapproved: python-oslo.context (eoan-proposed/main) [1:2.22.1-0ubuntu2 => 1:2.23.0-0ubuntu1] (openstack, ubuntu-server)
[20:47] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-look (eoan-proposed/universe) [0.65 => 0.66] (ubuntustudio)
[20:47] <Eickmeyer> ^ Just a wallpaper
[20:47] <Eickmeyer> infinity, vorlon: ^
[20:48] <vorlon> Eickmeyer: are you asking for a respin for beta?
[20:49] <Eickmeyer> vorlon: I wasn't, but if it's not too much trouble to get that in, that'd be nice.
[20:50] <Eickmeyer> I only got the needed .svg yesterday, sadly.
[20:50] <vorlon> ok.  the delta to debian/ubuntustudio-wallpapers-disco.install looks wrong fwiw
[20:50] <Eickmeyer> Really? That's odd.
[20:51] <Eickmeyer> I didn't even touch that file.
[20:51] <Eickmeyer> vorlon: If that's the case, is there anything I need to do?
[20:53] <vorlon> Eickmeyer: you should probably fix that and reupload
[20:53] <Eickmeyer> vorlon: ack, will do. Feel free to reject, I'll take a look at what's going on.
[20:56] -queuebot:#ubuntu-release- Unapproved: rejected ubuntustudio-look [source] (eoan-proposed) [0.66]
[20:56] -queuebot:#ubuntu-release- Unapproved: python-oslo.privsep (eoan-proposed/main) [1.33.1-0ubuntu2 => 1.33.3-0ubuntu1] (ubuntu-server)
[20:56] <vorlon> seb128: syncing a new upstream version of libarchive that drops a binary package that has reverse-build-dependencies hardly seems like a feature-freeze-appropriate change
[20:57] -queuebot:#ubuntu-release- Unapproved: python-oslo.log (eoan-proposed/main) [3.44.0-0ubuntu4 => 3.44.1-0ubuntu1] (openstack, ubuntu-server)
[20:57] <vorlon> seb128: so, can you please follow up on mtree-netbsd so that we can remove the NBS bsdtar?
[21:00] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.log [source] (eoan-proposed) [3.44.1-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- Unapproved: python-oslo.middleware (eoan-proposed/main) [3.38.0-0ubuntu3 => 3.38.1-0ubuntu1] (openstack, ubuntu-server)
[21:05] -queuebot:#ubuntu-release- Unapproved: python-openstackclient (eoan-proposed/main) [3.19.0-0ubuntu2 => 4.0.0-0ubuntu1] (openstack, ubuntu-server)
[21:06] -queuebot:#ubuntu-release- Unapproved: python-oslo.serialization (eoan-proposed/main) [2.29.1-0ubuntu3 => 2.29.2-0ubuntu1] (openstack, ubuntu-server)
[21:07] -queuebot:#ubuntu-release- Unapproved: python-oslo.rootwrap (eoan-proposed/main) [5.16.0-0ubuntu2 => 5.16.1-0ubuntu1] (openstack, ubuntu-server)
[21:08] <Eickmeyer> vorlon: found the problem, absolutely right, there should've been no diff on that file. Reuploading.
[21:09] -queuebot:#ubuntu-release- Unapproved: python-oslo.reports (eoan-proposed/main) [1.29.2-0ubuntu2 => 1.30.0-0ubuntu1] (openstack, ubuntu-server)
[21:11] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-look (eoan-proposed/universe) [0.65 => 0.66] (ubuntustudio)
[21:11] <Eickmeyer> vorlon: ^ There it is.
[21:17] <seb128> vorlon, ups, sorry about that, will fix it, thanks for pointing it out!
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-look [source] (eoan-proposed) [0.66]
[21:28] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.rootwrap [source] (eoan-proposed) [5.16.1-0ubuntu1]
[21:28] -queuebot:#ubuntu-release- Unapproved: devscripts (eoan-proposed/main) [2.19.6 => 2.19.6ubuntu1] (core)
[21:31] -queuebot:#ubuntu-release- Unapproved: mtree-netbsd (eoan-proposed/universe) [20180822-4 => 20180822-4ubuntu1] (no packageset)
[21:33] -queuebot:#ubuntu-release- Unapproved: accepted mtree-netbsd [source] (eoan-proposed) [20180822-4ubuntu1]
[21:33] <seb128> vorlon, fixed, sorry for overlooking that it had a reverse-build-depends; I'm not sure that I agree that the dropping of an old transitional binary with 1 rdepends is worth ffe paperwork though (or worth adding a delta to reverse the removal over Debian instead of just fixing the rdepends)
[21:34] <vorlon> seb128: thanks for following through!  ok, I didn't check that it was transitional - though clearly there were still references to it, so that's the important part to clean up
[21:34] <seb128> yeah, I looked at rdepends, should have checked with -b as well, my fault
[21:35] <seb128> it should be all good now so we can move on :-)
[21:47] -queuebot:#ubuntu-release- Unapproved: accepted python-caja [source] (eoan-proposed) [1.22.1-0ubuntu1]
[21:49] -queuebot:#ubuntu-release- Unapproved: backblaze-b2 (eoan-proposed/universe) [1.3.8-2 => 1.3.8-2ubuntu1] (no packageset)
[21:49] -queuebot:#ubuntu-release- Unapproved: accepted backblaze-b2 [source] (eoan-proposed) [1.3.8-2ubuntu1]
[21:58] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.10 => 20101020ubuntu543.11] (core)
[21:59] -queuebot:#ubuntu-release- New: accepted virtualbox-ext-pack [sync] (eoan-proposed) [6.0.12-2]
[22:00] -queuebot:#ubuntu-release- New binary: virtualbox-ext-pack [amd64] (eoan-proposed/none) [6.0.12-2] (no packageset)
[22:02] -queuebot:#ubuntu-release- Unapproved: accepted python-keystoneclient [source] (eoan-proposed) [1:3.21.0-0ubuntu1]
[22:04] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (disco-proposed) [6.0.6-1ubuntu<IP_ADDRESS>]
[22:07] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (bionic-proposed) [5.2.32-1~ubuntu18.04.2]
[22:08] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (xenial-proposed) [5.1.38-0ubuntu<IP_ADDRESS>]
[22:11] -queuebot:#ubuntu-release- Unapproved: buildstream (eoan-proposed/universe) [1.2.4-1 => 1.2.4-1ubuntu1] (no packageset)
[22:12] -queuebot:#ubuntu-release- Unapproved: accepted buildstream [source] (eoan-proposed) [1.2.4-1ubuntu1]
[22:13] -queuebot:#ubuntu-release- Unapproved: accepted python-castellan [source] (eoan-proposed) [1.3.1-0ubuntu1]
[22:25] -queuebot:#ubuntu-release- Unapproved: accepted python-ceilometermiddleware [source] (eoan-proposed) [1.5.0-0ubuntu1]
[22:26] -queuebot:#ubuntu-release- New: accepted virtualbox-ext-pack [amd64] (eoan-proposed) [6.0.12-2]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted python-blazarclient [source] (eoan-proposed) [2.2.1-0ubuntu1]
[22:28] -queuebot:#ubuntu-release- Unapproved: custodia (eoan-proposed/universe) [0.6.0-3 => 0.6.0-3ubuntu1] (no packageset)
[22:29] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.11]
[22:29] -queuebot:#ubuntu-release- Unapproved: duplicity (eoan-proposed/main) [0.8.04-2 => 0.8.04-2ubuntu1] (ubuntu-budgie, ubuntu-mate)
[22:29] -queuebot:#ubuntu-release- Unapproved: accepted custodia [source] (eoan-proposed) [0.6.0-3ubuntu1]
[22:30] -queuebot:#ubuntu-release- Unapproved: accepted python-cinderclient [source] (eoan-proposed) [1:5.0.0-0ubuntu1]
[22:34] -queuebot:#ubuntu-release- Unapproved: gitlint (eoan-proposed/universe) [0.9.0-2 => 0.9.0-2ubuntu1] (no packageset)
[22:35] -queuebot:#ubuntu-release- Unapproved: accepted gitlint [source] (eoan-proposed) [0.9.0-2ubuntu1]
[22:36] -queuebot:#ubuntu-release- Unapproved: gnome-keysign (eoan-proposed/universe) [1.0.1-3 => 1.0.1-3ubuntu1] (no packageset)
[22:36] -queuebot:#ubuntu-release- Unapproved: accepted gnome-keysign [source] (eoan-proposed) [1.0.1-3ubuntu1]
[22:45] -queuebot:#ubuntu-release- Unapproved: ionit (eoan-proposed/universe) [0.3.3-1 => 0.3.3-1ubuntu1] (no packageset)
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted python-glance-store [source] (eoan-proposed) [1.0.0-0ubuntu1]
[22:46] -queuebot:#ubuntu-release- Unapproved: pagemon (eoan-proposed/universe) [0.01.16-1 => 0.01.17-1] (no packageset) (sync)
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted ionit [source] (eoan-proposed) [0.3.3-1ubuntu1]
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted pagemon [sync] (eoan-proposed) [0.01.17-1]
[22:47] -queuebot:#ubuntu-release- Unapproved: accepted python-glanceclient [source] (eoan-proposed) [1:2.17.0-0ubuntu1]
[22:48] -queuebot:#ubuntu-release- Unapproved: knack (eoan-proposed/universe) [0.6.2-1 => 0.6.2-1ubuntu1] (no packageset)
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted python-keystoneauth1 [source] (eoan-proposed) [3.17.1-0ubuntu1]
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted knack [source] (eoan-proposed) [0.6.2-1ubuntu1]
[22:49] -queuebot:#ubuntu-release- Unapproved: pathspider (eoan-proposed/universe) [2.0.1-2 => 2.0.1-2ubuntu1] (no packageset)
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted python-manilaclient [source] (eoan-proposed) [1.29.0-0ubuntu1]
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted pathspider [source] (eoan-proposed) [2.0.1-2ubuntu1]
[22:50] -queuebot:#ubuntu-release- Unapproved: pylint-flask (eoan-proposed/universe) [0.5-3 => 0.5-3ubuntu1] (no packageset)
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted python-monascaclient [source] (eoan-proposed) [1.16.0-0ubuntu1]
[22:51] -queuebot:#ubuntu-release- Unapproved: accepted pylint-flask [source] (eoan-proposed) [0.5-3ubuntu1]
[23:00] -queuebot:#ubuntu-release- Unapproved: accepted python-neutron-lib [source] (eoan-proposed) [1.29.1-0ubuntu1]
[23:00] -queuebot:#ubuntu-release- Unapproved: python-stetl (eoan-proposed/universe) [2.0+ds-1 => 2.0+ds-1ubuntu1] (no packageset)
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted python-stetl [source] (eoan-proposed) [2.0+ds-1ubuntu1]
[23:04] -queuebot:#ubuntu-release- Unapproved: accepted python-novaclient [source] (eoan-proposed) [2:15.1.0-0ubuntu1]
[23:05] -queuebot:#ubuntu-release- Unapproved: python-trio (eoan-proposed/universe) [0.11.0-1 => 0.11.0-1ubuntu1] (no packageset)
[23:05] -queuebot:#ubuntu-release- Unapproved: accepted python-trio [source] (eoan-proposed) [0.11.0-1ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted python-octaviaclient [source] (eoan-proposed) [1.10.0-0ubuntu1]
[23:13] -queuebot:#ubuntu-release- Unapproved: python-ttystatus (eoan-proposed/universe) [0.38-2 => 0.38-2ubuntu1] (no packageset)
[23:14] -queuebot:#ubuntu-release- Unapproved: accepted python-ironicclient [source] (eoan-proposed) [3.0.0-0ubuntu1]
[23:14] -queuebot:#ubuntu-release- Unapproved: accepted python-ttystatus [source] (eoan-proposed) [0.38-2ubuntu1]
[23:15] -queuebot:#ubuntu-release- Unapproved: ranger (eoan-proposed/universe) [1.9.2-4 => 1.9.2-4ubuntu1] (no packageset)
[23:16] -queuebot:#ubuntu-release- Unapproved: accepted ranger [source] (eoan-proposed) [1.9.2-4ubuntu1]
[23:18] -queuebot:#ubuntu-release- Unapproved: accepted python-os-brick [source] (eoan-proposed) [2.10.0-0ubuntu1]
[23:19] -queuebot:#ubuntu-release- Unapproved: uranium (eoan-proposed/universe) [3.3.0-1 => 3.3.0-1ubuntu1] (no packageset)
[23:20] -queuebot:#ubuntu-release- Unapproved: accepted uranium [source] (eoan-proposed) [3.3.0-1ubuntu1]
[23:21] -queuebot:#ubuntu-release- Unapproved: accepted python-os-ken [source] (eoan-proposed) [0.4.1-0ubuntu1]
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted python-os-vif [source] (eoan-proposed) [1.17.0-0ubuntu1]
[23:22] -queuebot:#ubuntu-release- Unapproved: vmdb2 (eoan-proposed/universe) [0.13.2+git20190215-1 => 0.13.2+git20190215-1ubuntu1] (no packageset)
[23:23] -queuebot:#ubuntu-release- Unapproved: accepted python-os-win [source] (eoan-proposed) [4.3.2-0ubuntu1]
[23:23] -queuebot:#ubuntu-release- Unapproved: accepted vmdb2 [source] (eoan-proposed) [0.13.2+git20190215-1ubuntu1]
[23:23] -queuebot:#ubuntu-release- Unapproved: vmware-nsx (eoan-proposed/universe) [14.0.0~b1~git2019062013.30eab6bb8-0ubuntu1 => 14.0.0~b1~git2019062013.30eab6bb8-0ubuntu2] (no packageset)
[23:24] -queuebot:#ubuntu-release- Unapproved: accepted python-osc-lib [source] (eoan-proposed) [1.14.1-0ubuntu1]
[23:24] -queuebot:#ubuntu-release- Unapproved: accepted vmware-nsx [source] (eoan-proposed) [14.0.0~b1~git2019062013.30eab6bb8-0ubuntu2]
[23:26] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.cache [source] (eoan-proposed) [1.37.0-0ubuntu1]
[23:28] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.concurrency [source] (eoan-proposed) [3.30.0-0ubuntu1]
[23:30] -queuebot:#ubuntu-release- Unapproved: accepted python-openstacksdk [source] (eoan-proposed) [0.36.0-0ubuntu1]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted python-openstackdocstheme [source] (eoan-proposed) [1.31.1-0ubuntu1]
[23:43] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.db [source] (eoan-proposed) [5.0.2-0ubuntu1]
[23:53] -queuebot:#ubuntu-release- Unapproved: accepted python-oslo.i18n [source] (eoan-proposed) [3.24.0-0ubuntu1]
[23:56] -queuebot:#ubuntu-release- Unapproved: libcloudproviders (eoan-proposed/universe) [0.3.0-1 => 0.3.0-3] (no packageset) (sync)
[23:56] -queuebot:#ubuntu-release- Unapproved: accepted libcloudproviders [sync] (eoan-proposed) [0.3.0-3]