[13:33] <JanC> serfus: Colin (the installer developer) already answered on the bug  ☺
[13:34] <serfus> right, i just spoke with him before he did
[13:35]  * serfus is trying to rush this bug away
[13:35] <serfus> :P
[13:38] <JanC> ☺
[16:12] <paultag> mhall119: boom, roasted :)
[16:12] <paultag> mhall119: don't sass me with that KDE stuff, that was close to my heart :)
[16:13]  * mhall119 kicks paultag
[16:13] <paultag> neener neener :)
[16:16] <mhall119> checking up on my wiki paultag >:(
[16:17] <paultag> mhall119: damn straight. I fact check for work now
[16:17] <paultag> mhall119: I never really used KDE2, so I was shocked you would have, since I knew you went all linuxey after me, for some reason
[16:18] <mhall119> then you should know that wiki's aren't an acceptable source of authority
[16:18] <paultag> sure they are :)
[16:18] <mhall119> paultag: hell, I even used CDE
[16:18] <mhall119> for limited definitions of 'used'
[16:18] <paultag> dude, twm
[16:19] <paultag> that was my steeze before the flavor of GNOME at the time
[16:19] <paultag> then KDE when I went all Gentoo-ey, and while I was in Mandrake land from 2001->200something or other
[16:20] <mhall119> geek
[16:20] <paultag> nerd *
[16:21] <mhall119> said with love
[16:21] <paultag> yeahyeah :)
[16:48] <mhall119> why didn't someone tell me it was Sunday?
[17:27] <paultag> http://i.qkme.me/35ixqe.jpg


[00:14] <JanC> dannf: I doubt those are *signed* with the *public* key  ;)
[00:15] <JanC> but you probably want the 'ubuntu-cloud-keyring' package
[00:20] <JanC> undersun: get your mailserver offline, learn how to be a better sysadmin, re-install your VPS from scratch and configure it properly
[01:46] <dannf> JanC: i checked u-c-k, didn't see that *private* key in the keyring
[05:25] <n0ts>  hi
[10:11] <bubu\a> j #puppet-razor
[12:42] <radish> hi there, is there an easy way to use local storage for volumes in openstack folsom? local as in the compute node uese its own HDDs
[12:43] <vhdirk> hi all
[12:45] <vhdirk> I just installed ubuntu server 12.10 on our new server, but while I can clearly see that my network devices are detected (em1, em2, p2p1, p2p2), /et/udev/rules.d/70-persistent-net.rule is just plain empty
[12:45] <vhdirk> meaning that, if I run ifconfig, it only returns the loopback device
[13:32] <hallyn> stgraber: say, does this ring any bells for you?        lxc-start<PHONE_NUMBER>.339 ERROR    lxc_conf - Device or resource busy - error unlinking /usr/lib/x86_64-linux-gnu/lxc/dev/console
[13:32] <hallyn> i seem to rcall someone mentioning that in the last few days...
[13:32] <hallyn> utlemming: still no /dev in precise ubuntu-cloud
[13:33] <stgraber> hallyn: I saw the bug, my guess was that it was related to devtmpfs and /dev/console being open on the host
[13:33] <stgraber> but I only saw it quickly in bugmail and didn't investigate, so jsut a guess really
[13:39] <hallyn> stgraber: d'oh, right, thanks
[13:44] <cdoughty> Hi, I'm installing Ubuntu 12.04 server via cobbler 2.2.3 using a seed file and I'm noticing, when trying to use a static IP, that it always uses DHCP unless I put "netcfg/disable_autoconfig=true" in kopts.  My confusion is that Ubuntu just flat out ignores the "netcfg/disable_autoconfig boolean true" in the seed file.
[13:51] <shadeslayer> Hi
[13:52] <shadeslayer> I'm trying to configure 2 static ethernet interfaces, but when I run sudo /etc/init.d/networking restart it gives me : RTNETLINK : File exists
[13:52] <shadeslayer> and fails to bring up either eth0 or eth1
[13:52] <shadeslayer> s/either/both/
[13:52] <shadeslayer> *and fails to bring up both eth0 and eth1
[13:53] <shadeslayer> I googled it a bit and there's no definitive answer
[13:53] <lordievader> shadeslayer: I had the same problem on a couple of vm's, what fixed it for me was removing /etc/udev/rules/70-persistent-net.rules
[13:54] <shadeslayer> aha
[13:54] <lordievader> shadeslayer: And then a reboot..
[13:54] <shadeslayer> alright
[13:55] <shadeslayer> if this works I'll be jumping like a maniac
[13:58] <lordievader> shadeslayer: Hehehe :)
[14:11] <shadeslayer> lordievader: doesn't work
[14:13] <lordievader> shadeslayer: That is too bad.
[14:14]  * shadeslayer tries something
[14:17] <cdoughty> so has anyone here installed ubuntu 12.04 server with a seed file from cobbler before and gotten static IPs configured?
[14:28] <shadeslayer> lordievader: any other ideas?
[14:33]  * shadeslayer is utterly lost with this error
[14:33] <lordievader> shadeslayer: Not really, it worked for me, so didn't bother looking for more.
[14:33] <lordievader> shadeslayer: Sorry.
[14:33] <shadeslayer> no need to be :)
[14:54] <xorred> just starting up with a ubuntu 12 vps, used for a webserver...  portscanning it reveals port 53 open, should I close it via iptables? it's not needed externally, right?
[15:02] <shadeslayer> lordievader: fixed it
[15:02] <shadeslayer> stupid virtual networks were causing issues
[15:03] <shadeslayer> probably misconfigured
[15:09] <xorred> does anyone know why my ubuntu server says that iptables -t nat -F says "can't initialize table 'nat'"
[15:09] <xorred> ?
[15:15] <rbasak> xorred: are you running a custom kernel or something like that? Check /var/log/kern.log
[15:21] <xorred> rbasak: it's empty
[15:21] <xorred> I just got this vps from my vps provider, guess the distro is custom since it had apache preinstalled
[15:22] <xorred> lol, lsmod returns 0
[15:22] <xorred> is that bad
[15:27] <shadeslayer> okay, so, my server has 2 ethernet interfaces, I can ping google from one, but not the other
[15:27] <shadeslayer> I get a Destination not reachable
[15:27] <shadeslayer> *destination host unreachable
[15:29] <rbasak> xorred: sounds like your host is providing the kernel and not supplying logs either, and hasn't built the nat module. Is this virtuozzo by any chance?
[15:30] <rbasak> xorred: I think the short answer is to ask your host :/
[15:34] <xorred> rbasak: I just installed another kernel - 3.5 lowlatency
[15:34] <rbasak> xorred: just make sure that you can actually run the kernel you have installed. Depending on the hosting environment you may not have control over it.
[15:35] <xorred> well so far it's strange. openvz, and rebooting it - halts it
[15:35] <xorred> weird
[15:35] <xorred> have to boot up from the control panel manually every time
[15:37] <xorred> lol wth, uname -a shows 2.6, initrd and vmlinuz point to 3.5! /boot contains only 3.5
[15:37] <xorred> what the....
[16:06] <xorred> strange, why is add-apt-repository not present in ubuntu 12.10?
[16:07] <andol> xorred: Because you don't have the software-properties-common package installed?
[16:19] <ppetraki> I've got an upstart task that simply won't start. http://pastebin.ubuntu.com/1307508/
[16:19] <ppetraki> hallyn, ^ ?
[16:21] <hallyn> ppetraki: anything in /var/log/upstart/ ?
[16:22] <ppetraki> umm.. yeah, but it doesn't add up as to why it works from shell, and not from upstart
[16:22] <hallyn> i'm wondering whether the job started, and the script simply had a failure
[16:23] <ppetraki> hallyn, http://pastebin.ubuntu.com/1307519/
[16:23] <hallyn> ppetraki: you're aware that upstart scripts run in dash?
[16:24] <ppetraki> hallyn, no
[16:24] <hallyn> so what you're sourcing probably isn't proper dash
[16:24] <ppetraki> hallyn, so how do I source bash?
[16:24] <hallyn> you don't - can you toss a full script in /bin for it to run?
[16:25] <hallyn> or convert /var/lib/juju/units/opengrok-2/charm/inc/common to dash
[16:26] <ppetraki> grr, that just makes more work, the whole idea was to have entry points callable as functions
[16:26] <ppetraki> I guess I could do the same symlink business with inc/common as is done with the rest of hooks
[16:29] <hallyn> ppetraki: you could just switch the /bin/sh symlink
[16:30] <hallyn> no big deal for your juju charm imo
[16:30] <ppetraki> hallyn, sounds like alternatives magic, got an incantation to do that programatically?
[16:33] <hallyn> ppetraki: i don't.  and i don't see any /etc/alternatives/sh
[16:33] <ppetraki> hallyn, I'm just going to create some tiny driver scripts, atleast I understand the problem now
[16:33] <hallyn> i think a simple 'rm -f /bin/sh; ln -s /bin/bash /bin/sh' in hooks/install is the way to go
[16:34] <hallyn> ok
[16:34] <ppetraki> hallyn, that was sneaky http://pastebin.ubuntu.com/1307536/
[17:15] <demersus> Anyone have time and expertise to help me figure out why my NFS4 mounts don't share the same usernames?
[17:15] <demersus> I tried following the documentation, but it seems like the id mapping is not mapping correctly
[17:27] <RoyK> demersus: using kerberos?
[17:28] <RoyK> demersus: and same UIDs and GIDs on both systems?
[17:28] <demersus> RoyK,  no I am just using the simple quickstart nfs4 config.  No kerberos, /etc/passwd on both machines
[17:29] <demersus> No the UIDs, and GIDs are different.  Isn't imapd supposed to support different UIDs?
[17:29] <RoyK> imapd? or idmapd?
[17:29] <demersus> RoyK: sorry typo.  idmapd
[17:30] <RoyK> I'd recommend something of a shared user database
[17:30] <RoyK> ldap usually works
[17:30] <RoyK> nis too, although a bit old-style
[17:31] <RoyK> unix systems generally work *far* better with the same UID/GID on users
[17:31] <demersus> This is just temporary so I can migrate websites to another server while DNS updates.  I don't want to go through all the trouble of syninc UIDs
[17:31] <demersus> Maybe I don't understand the use of idmapd.  I thought it was supposed to sync user names instead of UIDs
[17:32] <RoyK> if it's just moving the data, you could transfer them and run something like "find /path -user <uid> -exec chown <newid> {} \;"
[17:32] <RoyK> I've only used idmapd for connecting windows/unix
[17:32] <demersus> Ok.
[17:33] <demersus> Thanks for your suggestions.  I appreciate the help.
[17:33] <RoyK> or - change the uid/gid on the new server to the old uid/gid
[17:33] <RoyK> probably the easiest
[17:34] <demersus> True.  I was just hoping NFS + idmap would be quicker and easier for the time being. (Lots of vhosts & users)
[17:34] <demersus> I should have copied the UIDS in the first place.
[17:35] <RoyK> well, just change them
[17:35] <RoyK> and chown /home/someuser to that uid
[17:36] <RoyK> chowning a bunch of files takes far longer
[17:36] <demersus> Okay.
[17:36] <RoyK> make that chown -R ...
[17:37] <demersus> I figured that is what you meant
[17:37] <demersus> Thanks
[18:16] <shadeslayer> hi, I was wondering if someone could help me a wee bit in setting up a VM on my server
[18:17] <shadeslayer> I can't quite figure out how to get my VM a public IP
[18:17] <shadeslayer> The host has 2 static IP's and I'd like to assign one of them to the VM
[18:27] <RoyK> shadeslayer: no sure, but I'd use a bridge
[18:27] <shadeslayer> that's what I'm using :)
[18:27] <shadeslayer> but for some reason the VM doesn't pick the ip
[18:27] <RoyK> shadeslayer: that is, configure the primary as a bridge and don't assign that IP to the host
[18:27] <shadeslayer> oh
[18:27] <shadeslayer> I'm not sure I want to do that
[18:28] <shadeslayer> because the primary IP is already for something else
[18:28] <RoyK> well
[18:28] <RoyK> what I do on my server is: I have eth0 without an IP address
[18:28] <RoyK> I have br0 with the host's IP
[18:29] <RoyK> and then the guests bridge on that with different IP addresses
[18:29] <RoyK> I think this is the "preferred" setup
[18:30] <shadeslayer> RoyK: I have this : http://paste.kde.org/582494/
[18:30] <shadeslayer> where br0 is supposed to be the bridge
[18:31] <RoyK> you shouldn't set an IP address on the bridge interface
[18:32] <RoyK> at least not on the same network as the guests
[18:32] <shadeslayer> so drop 18-22?
[18:33] <shadeslayer> ( As you can tell, I'm doing this for the first time and I simply followed the KVM networking guide )
[18:33] <RoyK> set the ip address on br0, not on eth1
[18:33] <shadeslayer> https://help.ubuntu.com/community/KVM/Networking
[18:33] <shadeslayer> RoyK: but don't I have to set the static IP on eth1?
[18:34] <RoyK> you don't need/want an IP address on eth1
[18:34] <RoyK> it'll be bridged to br0
[18:34] <shadeslayer> okay
[18:34] <shadeslayer> and bleh, how do I get rid of this : RTNETLINK answers: File exists
[18:34] <shadeslayer> Failed to bring up br0.
[18:35] <RoyK> eth1 is just a bridge point
[18:35] <RoyK> br0 is using that
[18:35] <shadeslayer> ( happens once I run :  invoke-rc.d networking restart )
[18:35] <shadeslayer> okay
[18:35] <shadeslayer> got it
[18:35] <RoyK> restart networking or reboot
[18:36] <RoyK> and if you're using RFC1918 addresses for the guests, keep in mind that they won't be accessible from the internet unless you do some NAT magick
[18:36] <shadeslayer> uh oh
[18:37] <shadeslayer> RoyK: okay, what if I want a publically accessibly IP for the VM
[18:37] <shadeslayer> absolutely no NAT'ing
[18:39] <RoyK> just don't set any IP address other than the primary on br0
[18:39] <RoyK> and none on eth1
[18:39] <RoyK> then tell the vm to use br0 and set the official IP on its interface (eth0)
[18:39] <RoyK> it'll be bridged through br0 and sent out
[18:40] <shadeslayer> alrighty
[18:40] <RoyK> http://paste.ubuntu.com/1307846/
[18:40] <RoyK> this is the configuration of one of my servers - it runs a few VMs with official IP addresses
[18:41] <shadeslayer> RoyK: http://paste.kde.org/582512/
[18:41] <shadeslayer> does that look sane?
[18:43] <RoyK> no use for netmask or gateway
[18:43] <RoyK> well
[18:44] <RoyK> netmask, yes, if it has an ip address, but no gateway
[18:44] <RoyK> a system has one gateway
[18:44] <shadeslayer> okay
[18:44] <RoyK> regardless of interfaces
[18:44] <RoyK> if you have more gateways, you need OSPF or BGP or something
[18:45] <RoyK> (or RIP if you're from the ninetees)
[18:45] <shadeslayer> hah :D
[18:45] <shadeslayer> no idea what those are but reading up on them :)
[18:46] <RoyK> you don't need to
[18:46] <RoyK> both OSPF and BGP will require routing deals with the ISP, so you don't need that
[18:47] <RoyK> BGP is used between ISPs
[18:47] <shadeslayer> heh, I'm reading to satisfy my curosity as to what this is :P
[18:47] <RoyK> :
[18:47] <RoyK> :)
[18:47] <RoyK> that's good
[18:47] <shadeslayer> *curiosity
[18:47] <RoyK> curiousity is always good
[18:48]  * shadeslayer notes that he should probably sleep within 30 minutes to catch his flight for UDS
[18:48] <RoyK> UDS?
[18:48] <shadeslayer> Ubuntu Developer Summit
[18:48] <shadeslayer> starts next week
[18:48] <RoyK> where's that?
[18:49] <shadeslayer> Copenhagen
[18:49] <RoyK> too bad my employer sticks to redhat...
[18:49] <shadeslayer> :D
[18:50] <shadeslayer> hmph
[18:50] <shadeslayer> I keep getting this interface called vnet0
[18:50] <RoyK> that's usual
[18:51] <RoyK> virtual interface created to interface with vr0
[18:51] <RoyK> br0
[18:51] <RoyK> one per vm
[18:51] <shadeslayer> http://paste.kde.org/582518/
[18:51] <RoyK> configure the vm to use the IP you want to use
[18:51] <shadeslayer> okay
[18:53] <RoyK> and btw, posting official ip addresses isn't dangerous unless you haven't secured the server, but then, if you haven't secured the server, it's out bad anyway
[18:54] <shadeslayer> :)
[18:55] <shadeslayer> ok, still doesn't connect to the internet
[18:56] <shadeslayer> can't ping the vm, can't ping from the vm
[18:56] <RoyK> pastebin the config from both host and guest
[18:56] <RoyK> ifconfig from both should do
[18:57] <shadeslayer> hmm .. VM doesn't have pastebinit/internet
[18:57] <shadeslayer> will take a screenshot :)
[18:57] <RoyK> ok
[18:57] <shadeslayer> RoyK: VM : http://i.imgur.com/moyEN.png
[18:57] <RoyK> I guess the host setup is prominent
[18:58] <shadeslayer> vm http://paste.ubuntu.com/1307888/
[18:58] <shadeslayer> erm
[18:58] <shadeslayer> host ^
[18:58] <RoyK> same IP on host br0 and guest
[18:59] <RoyK> guess the host will reply, then
[18:59] <RoyK> try to remove the ip address on br0
[18:59] <shadeslayer> okay
[19:00] <shadeslayer> Missing required variable: address
[19:00] <shadeslayer> Missing required configuration variables for interface br0/inet.
[19:00] <RoyK> sec
[19:00] <shadeslayer> sure
[19:01] <RoyK> iface eth1 inet manual
[19:01] <RoyK> make that br0
[19:02]  * shadeslayer tries
[19:04] <shadeslayer> mmm ... rebooting VM
[19:04] <shadeslayer> nop
[19:41] <moonpup> anyone know if it's possible to disable scp within ssh?
[19:41] <moonpup> i know how to disable sftp, but would like to nix scp as well
[20:50] <Carleeno> Hi, all! I run a small biz and wanting to set up a ubuntu server to handle webhosting, SOGo (and it's dependencies), ftp, samba (for active dir and file sharing), and quickbooks db. any problems with running all of those services from one machine? Or will I need to split any of them up?
[21:08] <Carleeno> I know it's not exactly a tech question, but does anybody see any issues with running the following services all from one machine? SOGo, postgreSQL, OpenLDAP, postfix, Cyrus IMAP, as well as Samba (for Active Dir and file sharing), web hosting and ftp hosting, and Quickbooks DB? I vaguely recall that there might be a problem with using samba for AD along with sogo and openLDAP on the same box. I'm asking because I'm about to b
[21:09] <patdk-lap> you can run as much stuff on one box as you want
[21:09] <patdk-lap> the only issue you will have is if things require certain ports
[21:10] <patdk-lap> but normally, you should split them up for security, flexability, or just general update/upgrade mainance ease
[21:14] <Carleeno> Thanks patdk-lap, I'll keep that in mind
[21:14] <wash> Hello - it was suggested to me at Linuxcon by an Ubuntu developer that ubuntu has a system called juju that might fit my needs for cluster provisioning. Are there any juju developers/users around? I wasn't able to find the sort of details that I was looking for on the juju website
[21:17] <wash> I'm looking specifically to deploy minimal Debian or Ubuntu system images to an HPC cluster that I run at my university. The cluster has 7 different classes of compute nodes, and I need to be able to manage 4 different system images.
[21:18] <wash> I need something that supports PXE booting, but must be able to install the system image to a hard drive as I cannot have the OS image living in memory.
[21:18] <redamber> When installing Server 12.10 I get an error after detecting the cd-rom, this is the error "ERROR MOUNTING CD-Rom"
[21:28] <trisec> nabbend
[21:37] <cromag> evening
[21:39] <cromag> is ubuntu server release upgraded the same way as the desktop version ?
[21:39] <RoyK> it is
[21:39] <cromag> clear and nice.
[21:39] <cromag> thanks :)
[21:39] <RoyK> but most of us that run server releases stick to LTS
[21:40] <resno> LTS!
[21:40] <RoyK> !lts
[21:40] <cromag> i see.
[21:41] <cromag> i'll stick around for at bit.


[05:37] <BenC> is there a reason that libc6-dev includes scsi/* stuff?
[05:40] <doko> BenC: no clue, but jbailey currently is not online
[05:58] <BenC> the three scsi/*.h headers are the only thing in libc6-dev that conflict with linux-kernel-heades
[06:02] <BenC> that's very interesting, it actually has these files in the glibc source tree
[06:02] <BenC> so I guess that trumps me including them in lkh...time for another kernel upload :/
[07:04] <jbailey> doko: thanks. =)
[07:04] <jbailey> BenC: The opinion that I've always heard was the the Linux SCSI headers were out of date.
[07:05] <BenC> the ones in glibc's source?
[07:05] <jbailey> I'd like to start a discussion on the libc list about just using kernel headers now that upstream has decided that they'll actually export usable headers to userspace.
[07:05] <jbailey> No, the ones in the kernel source for some reason.
[07:05] <jbailey> So the glibc ones were preferred.
[07:05] <BenC> makes sense to me
[07:05] <BenC> ah, ok
[07:05] <jbailey> I came up against this over the weekend when I was helping out with the NPTL port.
[07:05] <BenC> well, I reverted lkh exporting scsi/* for now
[07:05] <jbailey> for hppa, that is.
[07:05] <jbailey> thanks.
[07:05] <jbailey> Have you uploaded yet?
[07:06] <BenC> about 2 minutes ago
[07:06] <BenC> so it will work its way in
[07:06] <jbailey> Cool.
[07:24] <jbailey> oooo..  new lrm.
[07:24] <jbailey> I wonder if my wireless will work with the edgy kernel./
[07:29] <BenC> theory is that it will :)
[07:35] <jbailey> I'll give it a try.  The folks here seem surprised that I was concerned my airplane isn't on the departurs board.
[07:35] <jbailey> There is, after all, 40 minutes until it leaves.
[07:35] <jbailey> *sigh*
[07:35] <jbailey> But I'm guessing that I don't need to rush. =)


[17:57] <teward> is there a way to configure netplan so that it can handle two gateways, but only use the second if the first fails to reply/respond?
[17:57] <teward> not sure if there's this type of failover-setup for default gateway routes


[00:00] <bryce> would have been trivial to do if I'd known about it last week
[00:01] <Q-FUNK> I mentioned it even before that, back when Hardy was frozen, this spring.  there's just always too many things to watch for and it probably got lost in the shuffle.
[00:02] <bryce> yeah could be
[00:03] <Q-FUNK> and during UDS, there were far too many issues to tackle too
[00:05] <Q-FUNK> in fairness, I lost far too much time hunting down debian-specific changes in X that affect driver behavior in ways that other distros with fewer diffs don't get.
[00:07] <Q-FUNK> backporting all geode-related changes in 1.5 that work for other distros, only to find that it only solves half the issues on debian/ubuntu, wasn't exactly a pleasant suprise.
[00:07]  * bryce nods
[23:35] <tormod> bryce, upload sponsor day today? thanks :)
[23:36] <bryce> :-)
[23:36] <bryce> yup taking a break from spec writing to catch up on my sponsoring queue


[00:42] <infinity> xnox: Well, linux-image isn't noawait, but it also almost certainly shouldn't be.  There's also no way for it to be in a loop with things like bamfdaemon and desktop-file-utils, though.
[00:43] <infinity> xnox: ca-certificates might be a candidate.
[07:40] -queuebot:#ubuntu-release- Unapproved: networking-ovn (disco-proposed/universe) [6.0.0~rc1-0ubuntu1 => 6.0.0-0ubuntu1] (no packageset)
[07:43] <jamespage> morning ubuntu-release - sorry missed the upload for ^^ networking-ovn last friday...
[07:43] -queuebot:#ubuntu-release- Unapproved: nova (disco-proposed/main) [2:19.0.0-0ubuntu1 => 2:19.0.0-0ubuntu2] (openstack, ubuntu-server)
[07:44] <jamespage> and ^^ nova upload resolves an issue with the automated backport to 18.04 as openssl 1.1.1 is now in bionic-proposed
[07:44] <jamespage> if they could be reviewed and accepted much appreciated!
[07:44] <jamespage> thanks!
[07:57] <seb128> confirmed bug #1824672, unsure if you consider that as an issue to fix or just cosmetic though?
[07:57] <ubot5`> bug 1824672 in syslinux (Ubuntu) "Disco "check disc for defects" appears not to function" [Undecided,New] https://launchpad.net/bugs/1824672
[08:20] -queuebot:#ubuntu-release- Unapproved: sip4 (disco-proposed/universe) [4.19.15+dfsg-1 => 4.19.15+dfsg-1ubuntu1] (kubuntu)
[08:23] -queuebot:#ubuntu-release- Unapproved: pi-bluetooth (disco-proposed/universe) [0.1.10ubuntu3 => 0.1.10ubuntu5] (no packageset)
[08:23] -queuebot:#ubuntu-release- Unapproved: rejected pi-bluetooth [source] (disco-proposed) [0.1.10ubuntu5]
[08:23] -queuebot:#ubuntu-release- Unapproved: pi-bluetooth (disco-proposed/universe) [0.1.10ubuntu3 => 0.1.10ubuntu5] (no packageset)
[08:27] -queuebot:#ubuntu-release- Unapproved: accepted pi-bluetooth [source] (disco-proposed) [0.1.10ubuntu5]
[08:45] <seb128> gstreamer upload to disco to fix the current autopkgtest issue with parlatype which blocked the update in disco-proposed in the queue
[08:47] -queuebot:#ubuntu-release- Unapproved: gfxboot-theme-ubuntu (disco-proposed/main) [0.21.0 => 0.21.1] (core)
[08:52] -queuebot:#ubuntu-release- Unapproved: gstreamer1.0 (disco-proposed/main) [1.15.90-1~sync1 => 1.15.90-1ubuntu1] (desktop-core, ubuntu-server)
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted networking-ovn [source] (disco-proposed) [6.0.0-0ubuntu1]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted sip4 [source] (disco-proposed) [4.19.15+dfsg-1ubuntu1]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (disco-proposed) [2:19.0.0-0ubuntu2]
[09:05] -queuebot:#ubuntu-release- Unapproved: accepted gfxboot-theme-ubuntu [source] (disco-proposed) [0.21.1]
[09:05] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer1.0 [source] (disco-proposed) [1.15.90-1ubuntu1]
[09:08] <Laney> Looking into that syslinux thing a bit
[09:08] <mvo> sil2100: hey, can we release the "shadow" SRUs? I looked at the autopkgtest issues listed and one lxd failure is a "test timeout" and the other lxd one I have no clue but I can't see anything useradd/userdel related in there. and mariadb always fails it seems. I can dig into the second lxd test some more if you want though
[09:09] <seb128> Laney, thx
[09:12] -queuebot:#ubuntu-release- Unapproved: rejected blis [sync] (disco-proposed) [0.5.2-6]
[09:13] -queuebot:#ubuntu-release- Unapproved: accepted latte-dock [source] (disco-proposed) [0.8.8-0ubuntu1]
[09:14] -queuebot:#ubuntu-release- Unapproved: accepted python-django-mptt [sync] (disco-proposed) [0.8.7-1]
[09:17] <Laney> going to have to learn how it works first though /o\
[09:19] <infinity> seb128: Huzzah for the gstreamer 32-bit fix.
[09:19] <seb128> :-)
[09:19] <sil2100> mvo: hey! I can take a lookie now
[09:19] <infinity> seb128: Did you want to replace the gst-* ~sync1 uploads with real syncs while you're at it?
[09:20] <mvo> sil2100: thank you!
[09:20] <seb128> infinity, I can do if you prefer, it's mostly cosmetic
[09:21] <infinity> seb128: Yeah, not super picky, just makes me feel icky. :)
[09:21] <seb128> if you are fine waiting for another round of rebuilds/autopkgtest for that stack to migrate
[09:21] <seb128> k, let me sync then
[09:21] <infinity> seb128: Figured maybe you'd want to since this is about to retrigger testing $world anyway.
[09:23] <ginggs> i have received the reject mail for blis 0.5.2-6 yet, so don't i know the reason.  can i sync 0.5.2-7 ?
[09:23] <ginggs> s/have/have not/
[09:23] -queuebot:#ubuntu-release- Unapproved: gstreamer-vaapi (disco-proposed/universe) [1.15.90-1~sync1 => 1.15.90-1] (no packageset) (sync)
[09:24] -queuebot:#ubuntu-release- Unapproved: gstreamer-editing-services1.0 (disco-proposed/universe) [1.15.90-1~sync1 => 1.15.90-1] (ubuntustudio) (sync)
[09:25] -queuebot:#ubuntu-release- Unapproved: gst-plugins-base1.0 (disco-proposed/main) [1.15.90-1~sync1 => 1.15.90-1] (desktop-core, ubuntu-server) (sync)
[09:25] -queuebot:#ubuntu-release- Unapproved: gst-rtsp-server1.0 (disco-proposed/universe) [1.15.90-1~sync1 => 1.15.90-1] (no packageset) (sync)
[09:25] -queuebot:#ubuntu-release- Unapproved: gst-plugins-ugly1.0 (disco-proposed/universe) [1.15.90-1~sync1 => 1.15.90-1] (kubuntu) (sync)
[09:25] -queuebot:#ubuntu-release- Unapproved: gst-python1.0 (disco-proposed/universe) [1.15.90-1~sync1 => 1.15.90-1] (ubuntustudio) (sync)
[09:26] <seb128> infinity, done ^
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-base1.0 [sync] (disco-proposed) [1.15.90-1]
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gst-python1.0 [sync] (disco-proposed) [1.15.90-1]
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer-editing-services1.0 [sync] (disco-proposed) [1.15.90-1]
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-ugly1.0 [sync] (disco-proposed) [1.15.90-1]
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer-vaapi [sync] (disco-proposed) [1.15.90-1]
[09:32] -queuebot:#ubuntu-release- Unapproved: accepted gst-rtsp-server1.0 [sync] (disco-proposed) [1.15.90-1]
[09:38] <sil2100> mvo: ok, looking at the shadow SRU - I guess the main reason it wasn't released by anyone before is because it seems like the SRUs had some additional LP bugs attached that haven't been verified yet
[09:38] <sil2100> Can you take a look at those and see if maybe you could verify them? Or, well, if maybe they're not really relevant
[09:38] <sil2100> mvo: for instance:
[09:39] <sil2100> mvo: xenial and bionic have LP: #984390 and xenial LP: #1495580
[09:39] <ubot5`> Launchpad bug 984390 in shadow (Ubuntu Bionic) "$PATH is taken from login.defs not /etc/environment" [Medium,Fix committed] https://launchpad.net/bugs/984390
[09:39] <ubot5`> Launchpad bug 1495580 in shadow (Ubuntu Xenial) "chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set" [Medium,Fix committed] https://launchpad.net/bugs/1495580
[09:39] <sil2100> Very old bugs
[09:40] <sil2100> Guess maybe it's just some leftover in the changelog
[09:44] -queuebot:#ubuntu-release- Unapproved: python-h5netcdf (disco-proposed/universe) [0.5.0-1 => 0.7.1-1] (no packageset) (sync)
[09:49] <LocutusOfBorg> can we please kick llvm-toolchain-snapshot out from disco?
[09:50] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-snapshot (disco-proposed/universe) [1:9~svn354105-1~exp1 => 1:9~svn358327-1~exp1] (no packageset) (sync)
[09:50] <infinity> LocutusOfBorg: It's not in disco.
[09:50] <infinity> LocutusOfBorg: So... Done?
[09:51] <LocutusOfBorg> https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1824784
[09:51] <ubot5`> Ubuntu bug 1824784 in llvm-toolchain-snapshot (Ubuntu) "kick out from disco" [Undecided,New]
[09:51] <LocutusOfBorg> infinity, disco-proposed with block-proposed tag
[09:52] <infinity> LocutusOfBorg: Yes, it's in disco-proposed.  Not in disco.
[09:52] <infinity> LocutusOfBorg: So... What's the problem?
[09:52] <LocutusOfBorg> that its now an experimental only package
[09:52] <infinity> It'll move from disco-proposed to ee-proposed.
[09:52] <LocutusOfBorg> no, not autosyncd anymore
[09:52] <infinity> Oh, if you mean remove it entirely, sure.  But then why did you just request a sync?
[09:52] <infinity> Like, 3 minutes ago
[09:53] <LocutusOfBorg> infinity, because in case you nack the removal, I'm planning to keep it up-to-date manually
[09:53] -queuebot:#ubuntu-release- Unapproved: blis (disco-proposed/universe) [0.5.1-11 => 0.5.2-6] (no packageset) (sync)
[09:53] <infinity> LocutusOfBorg: Honestly, I suspect there's value in having it in proposed and manually refreshes occasionally, to see that it continues to build/work/etc.
[09:53] <ginggs> i think a dingo ate my blis reject mail
[09:54] <infinity> LocutusOfBorg: But your call, if you're the one maintaining it.
[09:54] <LocutusOfBorg> in case you want to keep it around a little bit more, I want my changes in the packaging to go in the archive, so I can see if the testsuite is fixed
[09:54] <LocutusOfBorg> as you can see I committed fixes from the 8 branch in the snapshot one
[09:54] <LocutusOfBorg> infinity, I'm not in a position to have a decision, you are archive admin, I prefer you to decide on it
[09:55] <LocutusOfBorg> we moved to experimental, because the binary packages moving to snapshot to "stable+1" version, were always missing breaks+replaces
[09:55] <infinity> LocutusOfBorg: If you're going to keep it updated, I'll keep it.  If you're not, I'll remove it.  Up to you.
[09:55] <infinity> :P
[09:55] <LocutusOfBorg> so people had pain in upgrading
[09:55] <sil2100> valorie, acheronuk: hey! So I see someone reported LP: #1824669 for kubuntu, did you see something like that by any chance?
[09:55] <ubot5`> Launchpad bug 1824669 in syslinux (Ubuntu) "Live boot fails legacy boot Kubuntu 19.04" [Undecided,New] https://launchpad.net/bugs/1824669
[09:55] <LocutusOfBorg> I just want people to stop having upgrades issues, the same we faced in debian
[09:55] <infinity> ginggs: The reject message was something like "an experimental package that is changing literally daily isn't an ideal candidate for a pre-release stable sync".
[09:56] <LocutusOfBorg> also "please remove this binary from foo" often resulted in ftpmasters removing the binaries from other llvm-toolchain-N packages
[09:56] <LocutusOfBorg> so, I would prefer to stop having it around but really, if you think it is worth the effort, I can still sync it and check if it works or not
[09:57] <ginggs> infinity: ack, debian maintainer told me yesterday 0.5.2-6 is the one we want, so i tested autopkgtests in my PPA an syc'd
[09:57] <infinity> LocutusOfBorg: If you prefer to remove it, I'll remove it.   :P
[09:57] <LocutusOfBorg> I would like to drop it, if possible, I think also it would be easier for archive admins
[09:57] <infinity> LocutusOfBorg: Kay.  Removing then.
[09:58] <ginggs> infinity: but now he uploaded 0.5.2-7 this morning, so up to you if you want to let 0.5.2-6 through now
[09:58] <LocutusOfBorg> because the new binaries often builds only in a subset of archs, and meh if I sync manually your automatic minions don't work
[09:58] <LocutusOfBorg> I hope to don't make you angry if in the future we change idea!
[09:59] <infinity> LocutusOfBorg: I'm always angry. :)
[09:59] <infinity> LocutusOfBorg: (removed)
[09:59] <LocutusOfBorg> <3 lovely thanks
[10:00] <ginggs> infinity: it should migrate, and then i'll check with him again before release and do another sync if needed
[10:00] <sil2100> valorie, acheronuk: oh, ok, I guess LP: #1824670 is related and duflu did take a look at it
[10:00] <ubot5`> Launchpad bug 1824670 in nvidia-graphics-drivers-340 (Ubuntu) "Boot to black screen after Kubuntu 19.04 install" [Undecided,New] https://launchpad.net/bugs/1824670
[10:01] <infinity> ginggs: If the Debian maintainer has higher confidence in experimental than in what we're currently shipping, that's probably a good enough argument, though we should likely take -7
[10:01] <infinity> Since it looks like it has obvious bugfixes over -6
[10:01] <ginggs> infinity: ack, please reject -6 (again) and i'll sync -7 when launchpad picks it up
[10:02] -queuebot:#ubuntu-release- Unapproved: rejected blis [sync] (disco-proposed) [0.5.2-6]
[10:03] -queuebot:#ubuntu-release- Unapproved: rejected llvm-toolchain-snapshot [sync] (disco-proposed) [1:9~svn358327-1~exp1]
[10:04] -queuebot:#ubuntu-release- Unapproved: accepted python-h5netcdf [sync] (disco-proposed) [0.7.1-1]
[10:04] -queuebot:#ubuntu-release- Unapproved: puma (disco-proposed/universe) [3.12.0-2 => 3.12.0-2ubuntu1] (no packageset)
[10:05] <LocutusOfBorg> infinity, ^^ I really want it to move forward, I don't know which network configuration your infrastructure has, but local tests pass, as well as in Debian, and DebOMatic... I hope we can wait for some new release, and in the meanwhile let me ask upstream (the test is ignored already on windows and somewhere else, like appveyor CI)
[10:06] <mvo> sil2100: thanks, let me double check this (and sorry for the slow reply, was in a meeting)
[10:08] <LocutusOfBorg> also, there is a new puma 3.12.1 that has changes in that exact particular test... interesting
[10:09] <sil2100> mvo: infinity had a point with one thing - at least one of those bugs could be very suspicious if it's really fixed, so yeah, would be good to check that
[10:09] <sil2100> Wonder why it was included in the .changes file
[10:11] <sil2100> Oh, infinity is right, the six-digit one is *actually* explicitly in the changelog ;p (/me didn't look at that yet)
[10:14]  * cjwatson eyes https://bugs.debian.org/926735 and wonders if we want that in disco
[10:14] <ubot5`> Debian bug 926735 in libparted2 "Include upstream patch for extended partition size" [Serious,Open]
[10:14] <cjwatson> Trying to construct a test case now ...
[10:18]  * infinity eyes cjwatson and wonders if we want him on distro.
[10:18] <cjwatson> :P
[10:18] <infinity> We have a pretty solid testcase.
[10:18] <LocutusOfBorg> "I want cjwatson on disco" so I can pull-lp-source him! :D
[10:18] <LocutusOfBorg> everybody should have a local cjwatson instance :)
[10:20] <cjwatson> I mean it'd be handy to be cloned
[10:21] <cjwatson> Don't want my clones to have more fun than I do though
[10:22] <LocutusOfBorg> you can pthread_join your forks eventually...
[10:22] <cjwatson> All gets a bit Greg Egan
[10:22] <LocutusOfBorg> but OTOH I don't want zombie cjwatson around... :D
[10:36] <acheronuk> sil2100: I tried a 'legacy' live usb boot on a Dell Inspiron 15 5578 laptop last night to check, and all was fine. That laptop is wuite new, and  Darin's (bug reporter) are about 2009 with Nvidia (I have Intel) so maybe not a fair comparison
[10:37] <acheronuk> sil2100: oh, I see your later comment. right
[11:01] -queuebot:#ubuntu-release- Unapproved: multipath-tools (disco-proposed/main) [0.7.4-2ubuntu7 => 0.7.4-2ubuntu8] (core)
[11:01] <xnox> infinity, https://launchpad.net/ubuntu/disco/+queue?queue_state=1&queue_text=multipath-tools http://launchpadlibrarian.net/419367051/multipath-tools_0.7.4-2ubuntu7_0.7.4-2ubuntu8.diff.gz
[11:06] -queuebot:#ubuntu-release- Unapproved: accepted puma [source] (disco-proposed) [3.12.0-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (disco-proposed) [0.7.4-2ubuntu8]
[11:10] <sil2100> mvo: how does the ddtp-ubuntu stuff work? I mean, I guess we'd normally like that updated, I see you did an import from Debian into ddtp-pot-disco but the translations in launchpad don't seem to exist for disco?
[11:10] <sil2100> mvo: anyway, it's probably not a priority to get that updated
[11:10] <sil2100> mvo: was just wondering if that's anything that you're working on already?
[11:11] <sil2100> For cosmic I guess we skipped the update?
[11:12] <sil2100> acheronuk: yeah, in that case I guess this should also be an issue for Ubuntu, right?
[11:13] <mvo> sil2100: I updated it for disco but its stuck apparently in LP approval of the templates
[11:13] <mvo> sil2100: https://translations.launchpad.net/ddtp-ubuntu/disco/+imports
[11:13] <mvo> sil2100: I'm not sure why this no longer gets approved, either in the "old" days people looked at this and don't anymore or a script has changed
[11:13] <mvo> sil2100: with that approved I think I could upload new translations for disco
[11:14] <infinity> tjaalton: Have you had more time to think about the nouveau modeset madness?
[11:14] <sil2100> mvo: hm, I wonder what happened then, I guess I don't have the powers to approve that - but probably Gunnar has, let me reach out to him
[11:14] <sil2100> mvo: anyway, not a top priority, but certainly would be nice if your work wouldn't go to waste just because of that
[11:14] <infinity> tjaalton: It occurred to me just now that this means all nvidia systems will also be running the installer at 640x480, which is really suboptimal.
[11:15] <mvo> sil2100: let me know if there is a way to automate this
[11:15] <mvo> sil2100: please ping me once this is unblocked, the amount of work to upload the update is tiny
[11:17] <acheronuk> sil2100: you would think so, be Darin said the Ubuntu iso booted ok. I'm afraid I don't have hardware I can reproduce this on, and not much time anyway today
[11:17] <acheronuk> *but Darin
[11:18] <sil2100> mvo: thank you!
[11:22]  * acheronuk deliberately NEVER EVER buys laptops with Nvidia ;)
[11:23] <tjaalton> infinity: on uefi systems it'll use efifb with the native resolution..
[11:23] <infinity> tjaalton: EFI systems are still relatively newish.
[11:24] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (disco-proposed/main) [20190124+dfsg1-0ubuntu1 => 20190315-0ubuntu1] (core, ubuntu-cloud)
[11:26] <tjaalton> sure
[11:27] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules (disco-proposed/restricted) [5.0.0-10.11 => 5.0.0-11.12] (kernel)
[11:30] <tjaalton> infinity: a more refined patch would take more time, so if you prefer to revert for disco and rethink it for EE then that's fine
[11:32] <sil2100> acheronuk: ok, that's a bit weird then!
[11:32] <sil2100> ;)
[11:32] <sil2100> But yeah, if only his laptop is affected (and only for Kubuntu), I'd say the importance of the bug has lowered a bit
[11:33] <sil2100> I was worried it's an indication of something bigger
[11:33] <sil2100> Wonder what's going on there
[11:33] -queuebot:#ubuntu-release- Unapproved: rejected linux-restricted-modules [source] (disco-proposed) [5.0.0-11.12]
[11:33] <infinity> tjaalton: Has the nouveau/firmware situation gotten significantly worse since cocmis?
[11:33] <infinity> tjaalton: cosmic, even.
[11:33] <infinity> tjaalton: Cause I'd prefer not to regress in the name of progression.
[11:41] <tjaalton> infinity: i'm not sure, upstream said it's not the first tume
[12:04] <infinity> tjaalton: I guess what I'm driving at is that if cosmic and bionic(+hwe) have the same issues you were trying to work around in disco, you're causing a regression to fix something that isn't.
[12:15] -queuebot:#ubuntu-release- Unapproved: blis (disco-proposed/universe) [0.5.1-11 => 0.5.2-7] (no packageset) (sync)
[12:17] -queuebot:#ubuntu-release- Unapproved: accepted blis [sync] (disco-proposed) [0.5.2-7]
[13:07] <LocutusOfBorg> rails migrated!
[13:09] <LocutusOfBorg> I think we now need a rails that disables bootsnap only on armhf instead of everywhere...
[13:17] -queuebot:#ubuntu-release- Unapproved: ruby-mixlib-install (disco-proposed/universe) [3.11.7-1 => 3.11.7-1ubuntu1] (no packageset)
[13:24] -queuebot:#ubuntu-release- Unapproved: mozjs60 (disco-proposed/main) [60.2.3-2build1 => 60.2.3-3] (desktop-core) (sync)
[13:25] -queuebot:#ubuntu-release- Unapproved: accepted mozjs60 [sync] (disco-proposed) [60.2.3-3]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted ruby-mixlib-install [source] (disco-proposed) [3.11.7-1ubuntu1]
[13:34] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules (disco-proposed/restricted) [5.0.0-10.11 => 5.0.0-11.12] (kernel)
[13:45] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (cosmic-proposed) [2:13.0.2-0ubuntu3.1]
[13:46] -queuebot:#ubuntu-release- Unapproved: diaspora (disco-proposed/universe) [<IP_ADDRESS>+dfsg-4 => <IP_ADDRESS>+dfsg-4ubuntu1] (no packageset)
[13:49] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.20 => 237-3ubuntu10.21] (core)
[13:50] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.8 => 4.0.0-1ubuntu8.9] (ubuntu-server, virt)
[13:51] -queuebot:#ubuntu-release- Unapproved: accepted linux-restricted-modules [source] (disco-proposed) [5.0.0-11.12]
[13:51] <infinity> LocutusOfBorg: That diaspora change looks wrong to me.
[13:52] <infinity> LocutusOfBorg: ruby-handlebars-assets has an epoch in both Ubuntu and Debian, why would you remove it in the version check?
[13:53] <infinity> LocutusOfBorg: The problem you're seeing in britney isn't the version, it's a component mismatch.
[13:53] <infinity> ruby-handlebars-assets moved from contrib to main in Debian and we didn't follow suit (yet).
[13:54] -queuebot:#ubuntu-release- New binary: linux-restricted-modules [amd64] (disco-proposed/restricted) [5.0.0-11.12] (kernel)
[13:54] -queuebot:#ubuntu-release- Unapproved: rejected diaspora [source] (disco-proposed) [<IP_ADDRESS>+dfsg-4ubuntu1]
[13:56] <infinity> LocutusOfBorg: Fixing.
[13:57] -queuebot:#ubuntu-release- Unapproved: ruby-oauth2 (disco-proposed/universe) [1.4.1-1 => 1.4.1-1ubuntu1] (no packageset)
[13:58] <LocutusOfBorg> sorry infinity I obviously made a mistake
[13:58] <LocutusOfBorg> because I saw "hey diaspora is not main, how can be a mismatch"
[13:58] <LocutusOfBorg> I didn't think about multiverse, you are right
[13:58] <LocutusOfBorg> sorry
[13:58] <LocutusOfBorg> ruby-oauth2 looks more legit
[13:58] <infinity> LocutusOfBorg: All good.  Should be fixed in the next publisher run.
[13:58] <LocutusOfBorg> lovely! I don't think it will migrate TBH
[13:59] <LocutusOfBorg> but I want autopkgtestsuite results...
[14:02] -queuebot:#ubuntu-release- Unapproved: accepted ruby-oauth2 [source] (disco-proposed) [1.4.1-1ubuntu1]
[14:38] -queuebot:#ubuntu-release- New: accepted linux-restricted-modules [amd64] (disco-proposed) [5.0.0-11.12]
[14:52] -queuebot:#ubuntu-release- Packageset: 44 entries have been added or removed
[15:02] -queuebot:#ubuntu-release- Unapproved: ddtp-translations (disco-proposed/universe) [20180103.1 => 20190415.1] (no packageset)
[15:51] -queuebot:#ubuntu-release- Unapproved: ruby-concurrent (disco-proposed/universe) [1.0.5-2 => 1.0.5-2ubuntu1] (no packageset)
[15:51] <LocutusOfBorg> ^^ that one is finally fixed yay
[15:55] -queuebot:#ubuntu-release- Unapproved: pi-bluetooth (disco-proposed/multiverse) [0.1.10ubuntu5 => 0.1.10ubuntu6] (no packageset)
[15:59] <ginggs> LocutusOfBorg: good work! please send that fix to debian bug #926782
[15:59] <ubot5`> Debian bug 926782 in src:ruby-concurrent "ruby-concurrent: autopkgtest needs update" [Normal,Open] http://bugs.debian.org/926782
[16:00] -queuebot:#ubuntu-release- Unapproved: accepted pi-bluetooth [source] (disco-proposed) [0.1.10ubuntu6]
[16:00] -queuebot:#ubuntu-release- Unapproved: accepted ruby-concurrent [source] (disco-proposed) [1.0.5-2ubuntu1]
[16:03] <LocutusOfBorg> ginggs, already fixed an uploaded in debian too
[16:12] -queuebot:#ubuntu-release- Unapproved: accepted ddtp-translations [source] (disco-proposed) [20190415.1]
[16:19] -queuebot:#ubuntu-release- Unapproved: update-notifier (trusty-proposed/main) [0.154.1ubuntu4 => 0.154.1ubuntu5] (kubuntu, ubuntu-desktop, ubuntu-server)
[16:29] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-meta (disco-proposed/universe) [0.35 => 0.36] (ubuntukylin)
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-meta [source] (disco-proposed) [0.36]
[17:04] -queuebot:#ubuntu-release- Unapproved: libpng1.6 (disco-proposed/main) [1.6.36-6 => 1.6.37-1~exp2] (core) (sync)
[17:22] <LocutusOfBorg> infinity, missing build on ppc64el: os-autoinst (from 4.5.1527308405.8b586d5-2)
[17:22] <LocutusOfBorg> missing build on s390x: os-autoinst (from 4.5.1527308405.8b586d5-2)
[17:22] <LocutusOfBorg> please can you do it? removed on debian, decruft NBS proposed
[17:24] <vorlon> infinity, LocutusOfBorg: looking
[17:25] <vorlon> infinity, LocutusOfBorg: done
[17:26] <LocutusOfBorg> <3
[17:31] <bdmurray> vorlon: I've verified bug 1822886 if you also feel it is worth releasing early.
[17:31] <ubot5`> bug 1822886 in ubuntu-release-upgrader (Ubuntu Cosmic) "universe missing after bionic->cosmic do-release-upgrade" [Critical,Fix committed] https://launchpad.net/bugs/1822886
[17:43] <LocutusOfBorg> last fix from my side for today
[17:44] <LocutusOfBorg> vala-panel is ok
[17:45] -queuebot:#ubuntu-release- Unapproved: vala-panel (disco-proposed/universe) [0.4.87+dfsg1-1 => 0.4.87+dfsg1-1ubuntu1] (ubuntu-mate)
[18:03] <infinity> LocutusOfBorg: That patch could use a link to the upstream commit yuo took "part" of...
[18:04] <infinity> LocutusOfBorg: And why on earth are you trying to sync libpng from experimental?
[18:05] -queuebot:#ubuntu-release- Unapproved: rejected libpng1.6 [sync] (disco-proposed) [1.6.37-1~exp2]
[18:36] <vorlon> bdmurray: released, thanks
[19:09] <infinity> vorlon: What exactly did you do above to os-autoinst?
[19:09] <infinity> (he asked, after removing the NBS binaries that weren't removed)
[19:10] <LocutusOfBorg> infinity, because of arm* fixes
[19:10] <infinity> Argh, and why did the VPN section of my panel disappear again?
[19:10] <LocutusOfBorg> infinity, I'm the debian libpng maintainer...
[19:10] <LocutusOfBorg> and I uploaded to experimental because of freeze, not because of instability
[19:11] <infinity> LocutusOfBorg: That's nice.  We're in a hard freeze, and libpng is on every image.
[19:11] <LocutusOfBorg> actually mostly all of the arm improvements are already in the current 1.6.36-6 version, but I would like to avoid having to maintain all the patches there, the new release included them all with some additional fixes
[19:12] <LocutusOfBorg> but of course I see your point
[19:12] <LocutusOfBorg> and you are RT, so I'll be happy whatever decision you make :)
[19:12] <infinity> I already made it. :)
[19:17] <LocutusOfBorg> :)
[19:17] <LocutusOfBorg> btw I vala-panel is now updated, we should probably drop the file at all, but I prefer to keep changes minimal
[19:18] -queuebot:#ubuntu-release- Unapproved: vala-panel (disco-proposed/universe) [0.4.87+dfsg1-1 => 0.4.87+dfsg1-1ubuntu1] (ubuntu-mate)
[19:19] <vorlon> infinity: apparently what I did was typo '-a s390x' as '-b s390x' <shrug>
[19:20] <infinity> Neat.
[19:21] <LocutusOfBorg> pick the one you prefer infinity :) the last upload might even be better
[19:22] -queuebot:#ubuntu-release- Unapproved: vala-panel (disco-proposed/universe) [0.4.87+dfsg1-1 => 0.4.87+dfsg1-1ubuntu1] (ubuntu-mate)
[19:25] <infinity> LocutusOfBorg: Why not the whole commit, that actually deletes the file?
[19:27] <infinity> I mean, in spirit, as it may not apply cleanly.  But you can do the 1-liner to CMakeLists, rm the file, then dpkg-source --commit.
[19:50] <LocutusOfBorg> infinity, that is the second upload
[19:50] <LocutusOfBorg> the reason for not deleting the file is that dpkg-source didn't pick deleted files...
[19:51] <LocutusOfBorg> in any case this is already a commit part of 0.4.88 released version, so it will go away on next sync
[19:57] <LocutusOfBorg> infinity, ^^ now you have the three flavours, the one with the function removed, the one with the cmake one-line and the one with also the file removed
[19:58] -queuebot:#ubuntu-release- Unapproved: vala-panel (disco-proposed/universe) [0.4.87+dfsg1-1 => 0.4.87+dfsg1-1ubuntu1] (ubuntu-mate)
[19:59] <LocutusOfBorg> next time I'll leave ricotz and seb128 the fixup of the sync from debian experimental :)
[20:00] -queuebot:#ubuntu-release- Unapproved: mokutil (disco-proposed/main) [0.3.0+1538710437.fb6250f-0ubuntu2 => 0.3.0+1538710437.fb6250f-1] (core) (sync)
[20:04] <vorlon> LocutusOfBorg: ^^ seriously?
[20:05] <vorlon> we're in final freeze. *critical fixes only*, not "sync new upstream versions to be in sync"
[20:05] -queuebot:#ubuntu-release- Unapproved: rejected mokutil [sync] (disco-proposed) [0.3.0+1538710437.fb6250f-1]
[20:06] <vorlon> not even new upstream version; but regardless, no
[20:19] <cyphermox> I may have a fix for casper in a minute; provided I manage to master this test iso properly
[20:19] <cyphermox> (integrity check)
[20:22] <tsimonq2> infinity, vorlon: How badly would the Release Team hate me if I wanted to upload a new Calamares module, assuming I take full responsibility for testing it?
[20:30] <xnox> slitghtly concerts that lxqt-globalkeys took out 6 builders for 1h+ now, when normally the build takes just 2minutes.
[20:30] <xnox> *concerned
[20:30] <xnox> either the cloud is dead, or the lxqt-globalkeys is blocking 12 buildings in a hung state.
[20:30] <xnox> *builders
[20:33] <xnox> no, not 12 builders, 24 builders.
[20:33] <xnox> tsimonq2, what's up with lxqt-globalkeys? do you have access to lubuntu ci? maybe we should cancel the builds, and retry them?
[20:33] <xnox> https://launchpad.net/builders -> ctrl+f for lxqt-globalkeys
[20:34] <xnox> i have rights to cancel these too.... it seems odd how they are hung.
[20:36] <tsimonq2> O_o
[20:43] <xnox> hm cancelling them doesn't help, as they get stuck in "cancelling" state then.
[20:43] <xnox> launchpad is probably broken.
[20:44] <tsimonq2> Yeah, it's that.
[21:03] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Disco Final] has been marked as ready
[21:04] <Eickmeyer> BOOM!
[21:04] <Eickmeyer> No blockers. :)
[21:19] -queuebot:#ubuntu-release- Unapproved: apparmor (disco-proposed/main) [2.13.2-9ubuntu5 => 2.13.2-9ubuntu6] (core)
[21:20] <fossfreedom> Eickmeyer, bit early? thought there is at least one more spin coming
[21:20] <tsimonq2> There's Always one more spin coming.
[21:21] <tsimonq2> Eickmeyer: I don't think infinity has updated base-files yet.
[21:21] <tsimonq2> (At minimum.)
[21:21] <Eickmeyer> Ohhhh.... :/
[21:21] <Eickmeyer> *unmarks*
[21:22] <tsimonq2> Eickmeyer: No need.
[21:22] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Disco Final] has been updated (20190413.1)
[21:22] <Eickmeyer> ¯\_(ツ)_/¯
[21:27] -queuebot:#ubuntu-release- Unapproved: rejected vala-panel [source] (disco-proposed) [0.4.87+dfsg1-1ubuntu1]
[21:27] -queuebot:#ubuntu-release- Unapproved: rejected vala-panel [source] (disco-proposed) [0.4.87+dfsg1-1ubuntu1]
[21:27] -queuebot:#ubuntu-release- Unapproved: rejected vala-panel [source] (disco-proposed) [0.4.87+dfsg1-1ubuntu1]
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted vala-panel [source] (disco-proposed) [0.4.87+dfsg1-1ubuntu1]
[21:30] -queuebot:#ubuntu-release- Unapproved: rejected apparmor [source] (disco-proposed) [2.13.2-9ubuntu6]
[21:31] <infinity> Well, that apparmor didn't last long in the queue...
[21:31] <infinity> Didn't even get to review it.
[21:31] <jdstrand> sorry
[21:31] -queuebot:#ubuntu-release- Unapproved: apparmor (disco-proposed/main) [2.13.2-9ubuntu5 => 2.13.2-9ubuntu6] (core)
[21:31] <jdstrand> I wanted a quick patch comment. the new one is there
[21:32] <infinity> Does this fix the issue you were discussing earlier?
[21:32] <jdstrand> this isn't install critical, so sru is fine, but if you want to take it, it is super small
[21:33] <jdstrand> it fixes part of it. I say part because this seems like twp parts
[21:33] <jdstrand> there is a shiftfs interaction with apparmor that jjohansen needs to look at
[21:34] <jdstrand> I fixed the easy part :)
[21:34] <jdstrand> the details are in the bug
[21:34] <jdstrand> if lxd didn't use shftfs or shiftfs was backed out, this would be good enough
[21:35] <jdstrand> I'm not advocating for that per se, but mention it since that might be something you want to consider
[21:37] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (disco-proposed) [2.13.2-9ubuntu6]
[21:38] <jdstrand> thanks
[22:04] <tsimonq2> xnox: (Technically, you also have access to the Lubuntu CI, being an Ubuntu Core Developer that is indirectly a Lubuntu Developer: https://ci.lubuntu.me/ )
[22:17] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (disco-proposed/main) [1.10ubuntu3 => 1.10ubuntu4] (core)
[22:18] <rbalint> infinity, bdmurray just marked one of the bugs rls-dd-incoming, and those issues are seen frequently on errors.ubuntu.com
[22:20] <rbalint> full autopkgtest is still running locally, the changes are on review at https://github.com/mvo5/unattended-upgrades/pulls
[22:22] <rbalint> u-u should run fine on default configs, thus it may be enough to release it as a 0-day sru, but wanted to show the most important patches
[22:26] <infinity> rbalint: Conceptually, I don't have issues with a u-u upload right now while I'm working on migrating a kernel anyway.
[22:26] <infinity> vorlon: I'm perhaps a bit too sleepy to give a good review to that u-u, could you give it some love?
[22:27] <vorlon> ok
[22:28] <rbalint> infinity, i'm too sleepy as well, thus i would not mind waiting till tomorrow or at least a review
[22:29] <rbalint> infinity, but i can fix anything tomorrow that were not caught by the review
[22:29] -queuebot:#ubuntu-release- Unapproved: linux (disco-proposed/main) [5.0.0-11.12 => 5.0.0-13.14] (core, kernel) (sync)
[22:29] -queuebot:#ubuntu-release- Unapproved: linux-signed (disco-proposed/main) [5.0.0-11.12 => 5.0.0-13.14] (core, kernel) (sync)
[22:37] -queuebot:#ubuntu-release- Unapproved: parted (disco-proposed/main) [3.2-24build1 => 3.2-25] (core) (sync)
[22:46] <rbalint>  infinity, vorlon u-u autopkgtest passed locally in disco
[22:46] <rbalint> running another in bionic
[22:47] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (disco-proposed) [1.10ubuntu4]
[22:48] <vorlon> infinity, rbalint: accepted ^^
[22:49] -queuebot:#ubuntu-release- Unapproved: linux-meta (disco-proposed/main) [<IP_ADDRESS>.12 => <IP_ADDRESS>.14] (core, kernel) (sync)
[22:50] <rbalint> vorlon, thanks! i'll keep the remaining patches needed in stable releases for the 0-day sru
[22:53] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (disco-proposed) [<IP_ADDRESS>.14]
[22:53] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (disco-proposed) [5.0.0-13.14]
[22:53] -queuebot:#ubuntu-release- Unapproved: accepted parted [sync] (disco-proposed) [3.2-25]
[23:07] -queuebot:#ubuntu-release- Unapproved: casper (disco-proposed/main) [1.403 => 1.404] (desktop-core, ubuntu-server)
[23:08] <vorlon> LocutusOfBorg: so you're disabling tests in puma when you cannot account for what the failure means?
[23:09] -queuebot:#ubuntu-release- Unapproved: accepted casper [source] (disco-proposed) [1.404]
[23:13] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (disco-proposed) [5.0.0-13.14]
[23:20] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-13.14] (core, kernel)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-aws (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-gcp (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-meta-aws (disco-proposed/main) [<IP_ADDRESS>3.3 => <IP_ADDRESS>4.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-meta-gcp (disco-proposed/main) [<IP_ADDRESS>3.3 => <IP_ADDRESS>4.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-restricted-modules (disco-proposed/restricted) [5.0.0-11.12 => 5.0.0-13.14] (kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-azure (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-meta-azure (disco-proposed/main) [<IP_ADDRESS>3.3 => <IP_ADDRESS>4.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-kvm (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- Unapproved: linux-meta-kvm (disco-proposed/main) [<IP_ADDRESS>3.3 => <IP_ADDRESS>4.4] (core, kernel) (sync)
[23:24] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-13.14] (core, kernel)
[23:25] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-13.14] (core, kernel)
[23:26] -queuebot:#ubuntu-release- Unapproved: accepted linux-restricted-modules [sync] (disco-proposed) [5.0.0-13.14]
[23:27] -queuebot:#ubuntu-release- Unapproved: linux-signed-azure (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:27] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:27] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-13.14]
[23:27] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-13.14]
[23:27] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-13.14]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-aws [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-gcp [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-aws [sync] (disco-proposed) [<IP_ADDRESS>4.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-gcp [sync] (disco-proposed) [<IP_ADDRESS>4.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-azure [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-azure [sync] (disco-proposed) [<IP_ADDRESS>4.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-kvm [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-kvm [sync] (disco-proposed) [<IP_ADDRESS>4.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: rejected linux-signed-azure [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: linux-signed-azure (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:32] -queuebot:#ubuntu-release- Unapproved: rejected linux-signed-gcp [sync] (disco-proposed) [5.0.0-1004.4]
[23:32] -queuebot:#ubuntu-release- Unapproved: linux-signed-gcp (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-azure [sync] (disco-proposed) [5.0.0-1004.4]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed-gcp [sync] (disco-proposed) [5.0.0-1004.4]
[23:38] -queuebot:#ubuntu-release- Unapproved: linux-gcp (disco-proposed/main) [5.0.0-1003.3 => 5.0.0-1004.4] (core, kernel) (sync)
[23:42] -queuebot:#ubuntu-release- Unapproved: tomcat9 (cosmic-proposed/universe) [9.0.16-3~18.04 => 9.0.16-3~18.10] (no packageset) (sync)
[23:42] <tdaitx> sbeattie: vorlon: ^ tomcat9 build is finished now, I requested the binary copy
[23:46] <sbeattie> thanks
[23:48] <vorlon> tdaitx: accepted
[23:48] -queuebot:#ubuntu-release- Unapproved: accepted tomcat9 [sync] (cosmic-proposed) [9.0.16-3~18.10]