[06:30] <dholbach> good morning
[08:31] <seb128> mpt: hey
[08:32] <seb128> mpt: https://wiki.ubuntu.com/DesktopTeam/Experiences/PlayingCds is confusing
[08:33] <seb128> mpt: you wrote "Tested with Ubuntu Hardy beta by MatthewPaulThomas. " but hardy uses brasero and not serpentine and rhythmbox should open the CD and start playing it when inserted
[08:33] <seb128> mpt: are you sure you tried the right ubuntu version?
[08:33] <seb128> mpt: that's rather confusing
[08:58] <slomo__> vuntz: ping? :)
[09:02] <vuntz> slomo__: pong
[09:03] <slomo__> vuntz: hi, just wanted to ask you if i need to do anything else except the mail to desktop-devel for bumping the liboil minimal required version :)
[09:04] <vuntz> slomo__: no, that's all you need to do
[09:04] <slomo__> ok, good
[09:04] <slomo__> thanks
[09:05] <vuntz> (you can of course bribe some release team people)
[09:30] <mpt> seb128, I wrote only the "Heuristic evaluation" section. The rest of the page is probably out of date.
[09:31] <seb128> mpt: ah ok
[09:31] <seb128> mpt: what version of rhythmbox did you have?
[09:31] <seb128> mpt: when inserting a CD rhythmbox is supposed to switch to the CD and start playing
[09:32] <mpt> seb128, whichever was in Hardy beta -- finding the version myself would require restarting into Hardy
[09:33] <mpt> (which I can do if you like)
[09:34] <mvo> asac: have you seen my question about apturl and ff3? (bug #203538)
[09:34] <ubotu> Launchpad bug 203538 in apturl "Don't work with Firefox3 beta4" [Medium,In progress] https://launchpad.net/bugs/203538
[09:35] <huats> morning everyone
[09:35] <huats> hey seb128 mvo and crevette
[09:35] <mvo> hey huats
[09:35] <seb128> mpt: no hurry, I'll have a look first and might ping you back about the "don't start playing the cd" issue
[09:36] <seb128> mpt: did you use an audio only disc or one with a data track too?
[09:36] <seb128> lut huats
[09:39] <mpt> seb128, audio-only
[09:39] <mvo> Amaranth: hey! I'm updating compiz today and I was wondering if there is a reason for our compiz-dev to depend on compiz-core. do we really need that (if so, I assume because of core.xml?)
[09:39] <Amaranth> I don't think I ever did that
[09:39] <seb128> mpt: ok
[09:39] <pclynch> im having problems with the "switch users" function and need help. everytime its run it goes to a blank white screen. whats wrong?
[09:40] <Amaranth> pclynch: Firebomb nVidia HQ
[09:40] <pclynch> Amaranth : come again?
[09:40] <Amaranth> pclynch: nvidia driver bug
[09:41] <mvo> Amaranth: ok, thanks. I remove it and see what happens
[09:41] <pclynch> Amaranth : oh i see, is there anyway to fix this?
[09:41] <Amaranth> pclynch: the only 'fix' is to disable compiz
[09:42] <pclynch> Amaranth : oh... :
[09:42] <pclynch> Amaranth : might it be resolved in hardy?
[09:42] <Amaranth> nope
[09:43] <pclynch> Amaranth : alright well thanks, atleast i know whats wrong now
[09:45] <mpt> If that's a common problem, I hope it's explained on help.ubuntu.com somewhere
[09:48] <kwwii> seb128: it seems that #210538 is not related to the gdm theme itself, or?
[10:00] <seb128> bug #210538
[10:00] <ubotu> Launchpad bug 210538 in ubuntu-gdm-themes "gdm hangs after theme upgrade and reboot" [High,Confirmed] https://launchpad.net/bugs/210538
[10:00] <seb128> kwwii: no, doesn't seem to be the theme
[10:24] <Amaranth> mvo: btw, bugs marked In Progress on compiz should be fixed if you're syncing to latest upstream code
[10:24] <seb128> kwwii: ok, so this gdm human list theme issue
[10:24] <seb128> kwwii: that seems to be the gtk bug I though about
[10:25] <mvo> Amaranth: aha, thats great. I will have a look at the list soonish, I'm preparing the upgrade in a PPA and will ask for testing later and apply for a freeze exception
[10:25] <mvo> Amaranth: I understand the new 0.7.4 release is pretty close too, right?
[10:25] <seb128> kwwii: commenting the gtk_color_scheme = in the HumanList gtkrc seems to workaround the issue and that doesn't seem to impact on the colors
[10:25] <Amaranth> as i understand it the 0.7.4 release was supposed to be out for use in the spring release of distros
[10:26] <mvo> yep
[10:26] <Amaranth> so it should actually have been around right about now
[10:26] <seb128> kwwii: do you know why Human and HumanList have different gtkrc variants and if that line is required?
[10:26] <Amaranth> otherwise it'll be too late for ubuntu and fedora, at least
[10:26] <Amaranth> i'll see if ixce and/or onestone can give an update
[10:26] <mvo> its just a matter of days I think (maybe even hours) - but I should ask in #compiz-fusion-dev
[10:32] <kwwii> seb128: nope, I left the old version of gtkrc in the human theme because you cannot select the colors anyway for gdm
[10:32] <kwwii> seb128: I guess that bersace put in a new version of the gtrc
[10:33] <seb128> kwwii: ok, so have you a pending upload?
[10:34] <kwwii> seb128: yeah, I am working on it now
[10:34] <seb128> kwwii: otherwise if one of you artwork guys could confirm I can comment the gtk_color_scheme there that would be nice
[10:34] <kwwii> seb128: I also have a ubuntulooks update to fix the preview issue
[10:34] <tjaalton> where does the "about me" -dialog write?
[10:34] <seb128> kwwii: I doubt the gtk bug will be fixed for hardy
[10:34] <seb128> tjaalton: there is a rewrite?
[10:34] <kwwii> seb128: yeah, the important thing here is that the bug is gone (or the humanlist theme, one or the other)
[10:35] <seb128> kwwii: ok, so please comment the line in bzr so it's in the next upload
[10:35] <tjaalton> seb128: no I mean where does it read/write it's information
[10:35] <seb128> kwwii: let me know when you need sponsoring for the gdm theme or ubuntulooks
[10:35] <seb128> tjaalton: evolution-data-server
[10:35] <Amaranth> tjaalton: afaik that gets stuffed into evolution-data-server
[10:35] <tjaalton> yuck
[10:35] <tjaalton> nevermind then :)
[10:36] <kwwii> seb128: will do, I also have an update for human icon theme
[10:36] <seb128> ok
[10:36] <seb128> artwork on fire this week ;-)
[10:37] <kwwii> this is what happens when I start doing packaging :p
[10:37] <kwwii> between leading the community, making mark happy, doing the artwork itself, and packaging my job is getting complicated ;-)
[10:42] <Amaranth> kwwii: You should help with compiz bugs too, it's just a little step from there :)
[10:43] <Amaranth> You make pretty things, we make pretty things, etc ;)
[10:45] <kwwii> Amaranth: lol, no doubt
[10:50] <mvo> *sigh* new compiz segfaults for me, how strange
[10:50]  * mvo pokes around a bit more
[10:59] <kwwii> hrm, bug #161746 seems to be a problem with the screensaver stuff in human-theme
[10:59] <ubotu> Launchpad bug 161746 in human-theme "on dist-upgrade error on substituting human-theme" [Undecided,New] https://launchpad.net/bugs/161746
[10:59] <asac> mvo: sorry, does the preference show up in about:config ?
[10:59] <mvo> asac: no
[10:59] <asac> ah
[11:00] <asac> mvo: ok. one part of the problem is that  then obviously ;)
[11:01] <mvo> indeed
[11:01] <asac> mvo: another question is if it works with those preferences at all?
[11:01] <asac> have you tried to set them manually?
[11:01] <mvo> not yet, I was wondering if I have the wrong config dir, but then there is a firefox.js in the same dir that seems to work. I will look closer when I finished with my compiz stuff here
[11:02] <asac> mvo: i think we accidentially dropped the syspref patch during the cycle
[11:02] <mvo> aha
[11:02] <asac> it has been readded for netxt upload
[11:02] <asac> so for me the config is at least read now.
[11:04] <asac> mvo: what was the meaning of apt+http ?
[11:04] <asac> (vs. just apt://)?
[11:04] <mvo> asac: deprecated, not used anymore
[11:05] <mvo> it was meant to add repositories to the sources.list but we dropped it for security concerns
[11:05] <asac> k
[11:06] <mvo> but generally its the right dir (the same as firefox.js) - so after the next upload it should work (assuming the pref names are correct etc)
[11:06] <asac> mvo: yes ... but it would be firefox only. i think we should have something similar for /etc/xulrunner-1.9/
[11:08] <mvo> right
[11:10] <asac> mvo: i will let you know in case we introduce this now. i have to discuss this with Mozillateaam
[11:10] <asac> mvo: for now the location is right
[11:10] <asac> everything else is a bug on our side
[11:13] <tjaalton> umm, gnome-power-manager needs to be running in order for the logout-button to work?
[11:16] <tjaalton> because it starts g-p-m if it's not running already
[11:18] <Amaranth> tjaalton: that's dbus autostarting the service because the logout dialog tried to ask gpm if it could sleep/hibernate
[11:18] <tjaalton> Amaranth: urgh
[11:21] <tjaalton> that's a bug imho.. it should first check gconf if gpm is allowed to do that, and only then check the daemon
[11:22] <mvo> Amaranth: hrm, 013-add-cursor-theme-support breaks with the latest compiz. do you remember why this is not upstream?
[11:23] <Amaranth> mvo: Because I never got around to reviewing it
[11:23] <Amaranth> I don't even know where it came from
[11:23] <mvo> maybe gandalfn remembers (or even wrote it :) ?
[11:38] <seb128> mvo: you might want have a look to bug #40379 before hardy
[11:38] <ubotu> Launchpad bug 40379 in notification-daemon "Notification window too small to fit text." [Medium,Triaged] https://launchpad.net/bugs/40379
[11:38] <seb128> mvo: there is a patch, not sure if it's correct but would be nice to get the issue fixed if that's correct
[11:40] <mvo> thanks seb128
[11:40] <seb128> mvo: you are welcome :-)
[13:33] <_MMA_> Hi seb128. kwwii mentioned he talked to you about this odd GDM bug. He said it might have come down to the new color-picker gtkrc used in the theme. Ubuntu Studio's theme had hard-coded values and this bug just bit me. I'm trying to pin it down now.
[13:41] <seb128> re
[13:41] <seb128> _MMA_: I know what the issue is, did you read my comments on the other bug?
[13:42] <_MMA_> I didnt see the current one sorry.
[13:42] <mvo> Amaranth: I uploaded new snapshots to  https://edge.launchpad.net/~mvo/+archive - testing much appreciated (once its build)
[13:42] <seb128> _MMA_: bug #210538
[13:42] <ubotu> Launchpad bug 210538 in ubuntu-gdm-themes "gdm hangs after theme upgrade and reboot" [High,Confirmed] https://launchpad.net/bugs/210538
[13:42] <_MMA_> seb128: Thanx
[13:43] <seb128> you are welcome
[13:50] <_MMA_> seb128: So which comment is it? The "Commenting the gtkrc gtk_color_scheme =" part?
[13:52] <seb128> _MMA_: well, I pointed the GTK bug which is the issue in one comment and that is my suggested workaround
[13:52] <_MMA_> seb128: That's what I was saying. The Ubuntu Studio theme doesn't have that as the values are hard-coded.
[13:53] <seb128> _MMA_: maybe you have a different bug then
[13:54] <_MMA_> I get to the desktop by removing GDM. Once I reinstall it and the system tries to start it it crashes instantly. Ill let it report the crash.
[13:56] <gandalfn> mvo: yep it's me i made 013-add-cursor-theme-support, it's a back hack which pool gconf cursor theme key, it's never merged in compiz git because the last time i see the  code ;), it's plan to support a native cursor theme.
[15:03] <kwwii> mvo, pitti, seb128: just for information I have several updated packages to be uploaded (human-icon-theme, ubuntu-gdm-themes, human-theme, and ubuntulooks)
[15:03] <kwwii> who wants to take a whack at them?
[15:04] <seb128> can do that
[15:04] <seb128> urls?
[15:04] <pitti> just distribute them evenly amongst us :)
[15:04] <seb128> just the dsc are enough
[15:04] <kwwii> ok, let me post the links....one second
[15:18] <kwwii> http://sinecera.de/human-icon-theme_0.28.dsc
[15:18] <kwwii> http://sinecera.de/ubuntu-gdm-themes_0.29.dsc
[15:18] <kwwii> http://sinecera.de/human-theme_0.15.dsc
[15:18] <kwwii> http://sinecera.de/ubuntulooks_0.9.12-10.dsc
[15:18] <seb128> looking to ubuntulooks
[15:21] <seb128> ah, this one is easy
[15:22] <seb128> kwwii: so that was a theme bug!
[15:26] <_MMA_> seb128: Well I dont know, because the Ubuntu Studio theme now works. No no new updates.
[15:26]  * _MMA_ is totally stumped.
[15:26] <seb128> _MMA_: weird
[15:28] <seb128> kwwii: the change seems weird though, using selected_bg_color for bg[SELECTED] seemed logical
[15:29] <seb128> looking to ubuntu-gdm-themes
[15:30] <_MMA_> seb128: At one point, I deleted our GDMs gtkrc. After that, things worked! :) But, just to see, I added it back and it still worked.
[15:30]  * _MMA_ scratches head.
[15:31] <seb128> _MMA_: are you sure you didn't have a version use themeable colors?
[15:31] <_MMA_> Restarted GDM. Rebooted a bunch. All still works.
[15:31] <_MMA_> seb128: Positive.
[15:31] <seb128> weird then
[15:32] <_MMA_> I should try to put one in and see.
[15:33] <_MMA_> But removing it all together just uses the default system theme so I'm just gonna yank the one from our GDM.
[15:35] <kwwii> _MMA_: seb was talking about the preview of the theme in the theme selector
[15:35] <kwwii> it uses the selected_bg_color as the window decoration color in the previewer for some reason
[15:36] <kwwii> so we added an extra definition so it displays correctly in the theme chosser
[15:36] <kwwii> chooser
[15:36] <kwwii> anyway, /me tests gdm now
[15:38] <_MMA_> kwwii: He and I *were* talking about GDM earlier. That's what I was talking about just now. (thought I can see that would get confusing) But I don't see that issue personally in the preview for the system theme.
[15:40] <kwwii> ahhh, ok
[15:40] <kwwii> _MMA_: well, after replacing the gtkrc to one with hard-coded colors it works for me
[15:41] <_MMA_> So weird. I should replace mine with one and test.
[15:41] <kwwii> seb128: yeah, the previewer seems to look through the file to find the right definition of bg color to use for the window decoration so even though the theme worked the previewer didn't
[15:41] <kwwii> seb128: btw, I found I had to remove the thumbnails when I was testing it for it to appear correctly
[15:42] <seb128> kwwii: right for the thumbnail
[15:42] <_MMA_> kwwii: How? :P
[15:42] <kwwii> seb128: not sure if the version number bump will fix that or not
[15:42] <seb128> kwwii: but I'm not sure to understand the fix, are you sure it's correct?
[15:42] <kwwii> seb128: yes, it works fine now on several machines
[15:44]  * kwwii actually tested this stuff before submitting the changes this time :p
[15:45] <seb128> kwwii: right, I don't question the fact that it works, I fixed the workspace switcher color being too light too
[15:45] <seb128> kwwii: I'm rather wondering why it's work, it's it correct or if that's a workaround ;-)
[15:48] <seb128> kwwii: human-icon-theme seems to be buggy
[15:48] <seb128> hum, no
[15:49] <kwwii> seb128: after looking at other themes this seems to be the correct way
[15:49] <seb128> ok
[15:49] <kwwii> seb128: last night I had it differently (which was just a hack that happened to work)
[15:49] <kwwii> so this is the right way
[15:50] <seb128> kwwii: ok, that was the previous version which was buggy
[15:50] <seb128> you had the configure, etc in the source when usually there are not
[15:51] <kwwii> ouch...I probably built the package in the source before doing the debuild
[15:51] <seb128> that means the clean target is buggy
[15:51] <kwwii> should I reapply my changes and rebuild the sources?
[15:51] <kwwii> from a fresh source, I mean
[15:52] <seb128> no, today's version is correct
[15:52] <kwwii> whew :-)
[15:52] <seb128> that's the current hardy one which has the bug
[15:52] <kwwii> cool, a problem which I didn't create! that is something different :p
[15:53]  * kwwii feels bad for anyone having to deal with an art-hacker
[15:54] <seb128> scp is buggy nowadays
[15:54] <seb128> the speed estimation on upload are all wrong
[15:55] <seb128> it goes to 100% too quickly and then stands there while the copy is happening
[15:57] <seb128> kwwii: hum, you added a depends on gtk2-engines-murrine again?
[15:58] <kwwii> seb128: yes, after talking to mvo we decided it had to be that way if we supply the gtkrc
[15:58] <kwwii> or there would be a theme without the appropriate engine
[15:58] <seb128> the package is small enough I guess that's no issue
[15:58] <seb128> yeah
[15:58] <kwwii> yeah, it is like 800kb or so
[15:58] <seb128> that's because mvo didn't get apt installing recommends in hardy!
[15:59] <seb128> slacker!
[15:59]  * seb128 hugs mvo ;-)
[15:59]  * mvo runs from seb128
[15:59]  * kwwii hugs everyone - group hug!
[16:00] <seb128> yeah, group hug ;-)
[16:00] <seb128> kwwii: btw 800k is a lot for a theme, the deb seems to be rather 38k ;-)
[16:00] <kwwii> better still
[16:00] <kwwii> erm, even better
[16:03] <seb128> kwwii: ok, all your updates are uploaded ;-)
[16:03] <kwwii> w00t
[16:04] <kwwii> thanks man, I appreciate you taking care of it so quickly
[16:04] <seb128> I confirmed that the humanlist theme and the human preview issue are fixed on my box too
[16:04] <seb128> you are welcome
[16:04] <kwwii> excellent
[16:19] <pochu> seb128: there's a new upstream libarchive packaged in Debian, which enables the testsuite in build... have you seen it?
[16:20] <seb128> pochu: no$
[16:21] <pochu> seb128: do you want me to look into it, or is it late for this change?
[16:21] <seb128> pochu: is that a different version? maybe ask to pitti
[16:21] <pochu> err, we have 2.2.4 and that's 2.4.17...
[16:21] <pitti> yes, AFAIR it is
[16:22] <pochu> I guess that's a no-go...
[16:22] <pitti> I forwarded the patch upstream, had a quick discussion, and he adopted it
[16:22] <pitti> so we can sync in intrepid
[16:22] <pochu> ok
[16:22] <seb128> kwwii: hum, changelog autoclosing didn't work because you didn't use the right syntax, you might want to close the ubuntu-gdm-themes bugs by hand now
[16:23] <seb128> pitti: well, nothing else in main uses it so it could be a good idea to use a recent version?
[16:23] <pitti> I don't know what they changed
[16:23] <pitti> there are just two or three reverse build-deps in universe
[16:24] <seb128> does it matter what they changed if it's not used out of the gvfs anyway?
[16:24] <pitti> well, we shuoldn't break the other rdepends :)
[16:24] <pitti> but if it doesn't change ABI etc., we can consider it, sure
[16:24] <seb128> well, if pochu checks those
[16:24] <seb128> I don't really care either way
[16:25] <seb128> it just seems easier to maintain security wise if we don't have an outdated codebase
[16:25] <pitti> yeah
[16:27] <pochu> it would be cool if apt-get source libarchive/hardy worked, as apt-get install libarchive/hardy does...
[16:31] <kwwii> seb128: right, will do
[16:31] <kwwii> but first I will figure out what I did wrong :p
[16:32] <seb128> kwwii: you forgot the ":" in the syntax
[16:32] <kwwii> duh
[16:37] <seb128> tedg: do you need g-s-s sponsoring?
[16:41] <pochu> +Aug 05, 2007: New configure option --disable-bsdtar, thanks to Joerg
[16:41] <pochu> +	Sonnenberger.
[16:41] <pochu> perhaps we wnat to use that?
[16:41] <pochu> want*
[16:41] <pochu> that was one of the concerns of the security team, wasn't it?
[16:42] <pochu> (maintaining bsdtar for no reason...)
[16:42] <seb128> well, the binary is in universe
[16:42] <seb128> so I don't know if that's really an issue
[16:42] <pochu> ah, right
[16:43] <pochu> the new package from Debian also packages bsdcpio, but that's also a different binary which could be demoted
[16:46] <tedg> seb128: Let me check to ensure it built, but probably.
[16:47] <tedg> seb128: Yes, looks good, if you could sponsor it that'd be great.
[16:47] <seb128> tedg: ok, will do
[16:48] <tedg> I'm not sure how many people are running NIS on Hardy, but we should push the update anyway :)
[16:48] <tedg> seb128: Thanks.
[16:48] <seb128> you are welcome
[17:00] <pitti> seb128: what's your feeling on bug 211358?
[17:00] <ubotu> Launchpad bug 211358 in gnome-volume-manager "Disable auto-popup of xsane" [Medium,In progress] https://launchpad.net/bugs/211358
[17:03] <seb128> pitti: never got the issue so far so I've no real opinion about that, in which case do you get the popup?
[17:04] <pitti> seb128: as soon as you plug in a scanner
[17:04] <seb128> well, usually those are plugged on the computer and stay there
[17:04] <seb128> no?
[17:04] <pitti> well, at least I don't keep them switched on all the time
[17:05] <pitti> and I know many people who do the same
[17:05] <seb128> ah, you have a switch to turn yours off and on, ok
[17:05] <pitti> especially with scanner/printer combos
[17:05] <seb128> right
[17:05] <seb128> I don't think anybody relies on this notification to use the device anyway
[17:05] <seb128> I think disabling it is alright
[17:06] <pitti> ok, thanks
[17:16] <pochu> oh nice, the bsdtar testsuite fails
[17:20] <pochu> it's failed in Debian too, in all archs but mipsel
[17:24] <lapo> hi
[20:35] <crevette> hello
[20:41] <crevette> pitti: around ?
[21:26] <walrren> Keybuk: are you guys actively moving to upstart-style scripts?  and what's the status of debian on changing scripts?
[23:14] <seb128> fta_: do you want to do the libcairo update?
[23:19] <fta> seb128, sure, but tomorrow.
[23:19] <seb128> fta: ok, thanks
[23:44] <pochu> why is ~ubuntu-desktop subscribed to all these bugs? bugmail from that team ends in<EMAIL_ADDRESS>https://bugs.edge.launchpad.net/~ubuntu-desktop
[23:45] <seb128> pochu: "these bugs" being?
[23:45] <seb128> ah
[23:46] <seb128> some people confusing ubuntu-desktop and desktop-bugs when subscribing or assigning
[23:46] <pochu> yes
[23:47] <pochu> it's not very annoying as it's very few bugmail
[23:48] <seb128> well, they don't go on the list since launchpad is not subscribed
[23:51] <pochu> well, in fact they do: https://lists.ubuntu.com/archives/ubuntu-desktop/2008-April/001537.html
[23:51] <pochu> s/in fact/actually/
[23:52] <seb128> pochu: this guy is subscribed to the list that's why
[23:52] <pochu> that doesn't make sense to me...
[23:52] <pochu> I'm subscribed to the list too and my bug mail doesn't end in the list :)
[23:53] <pochu> seb128: I think that's because https://edge.launchpad.net/~ubuntu-desktop has<EMAIL_ADDRESS>as the contact address
[23:54] <seb128> pochu: right, that's on purpose to not flood members
[23:54] <seb128> pochu: though it might be fixed now in launchpad since team can use launchpad lists
[23:55] <pochu> I see
[23:55] <pochu> as I said that's not a big deal as I haven't seen many bug mail in ubuntu-desktop@, I just wanted to report it to you so that we know what's happening in case that grows :)


[01:09] -queuebot:#ubuntu-release- Unapproved: webkit2gtk (zesty-proposed/main) [2.15.92-1 => 2.16.0-1] (kubuntu, ubuntu-desktop) (sync)
[01:14] <jbicha> https://launchpadlibrarian.net/312058096/webkit2gtk_2.15.92-1_2.16.0-1~ubuntu17.04.1.diff.gz
[01:45] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (zesty-proposed/main) [3.22.11-0ubuntu1 => 3.22.11-0ubuntu2] (ubuntu-desktop)
[03:03] -queuebot:#ubuntu-release- Unapproved: accepted activity-log-manager [source] (zesty-proposed) [0.9.7-0ubuntu25]
[03:04] -queuebot:#ubuntu-release- Unapproved: accepted webkit2gtk [sync] (zesty-proposed) [2.16.0-1]
[03:05] -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (zesty-proposed) [3.22.11-0ubuntu2]
[03:11] -queuebot:#ubuntu-release- Unapproved: snapd-glib (zesty-proposed/main) [1.7-0ubuntu1 => 1.9-0ubuntu1] (ubuntu-desktop)
[03:50] -queuebot:#ubuntu-release- Unapproved: unity-settings-daemon (zesty-proposed/main) [15.04.1+17.04.20170322-0ubuntu1 => 15.04.1+17.04.20170322-0ubuntu1.1] (ubuntu-desktop)
[03:52] <robert_ancell> unity-settings-daemon 15.04.1+17.04.20170322-0ubuntu1.1 fixes bug 1675612 which appeared in the previous release
[03:53] -queuebot:#ubuntu-release- Unapproved: snapcraft (zesty-proposed/universe) [2.27.1+17.04 => 2.28+17.04] (no packageset)
[03:54] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (zesty-proposed) [2.28+17.04]
[05:11] -queuebot:#ubuntu-release- Unapproved: gwc (zesty-proposed/universe) [0.21.19~dfsg0-7 => 0.21.19~dfsg0-7ubuntu1] (no packageset)
[05:12] -queuebot:#ubuntu-release- Unapproved: accepted gwc [source] (zesty-proposed) [0.21.19~dfsg0-7ubuntu1]
[05:35] -queuebot:#ubuntu-release- Unapproved: apparmor (zesty-proposed/main) [2.11.0-2ubuntu2 => 2.11.0-2ubuntu3] (core)
[06:05] -queuebot:#ubuntu-release- Unapproved: rejected system-config-printer [source] (zesty-proposed) [1.5.7+20160812-0ubuntu7]
[06:05] -queuebot:#ubuntu-release- Unapproved: accepted system-config-printer [source] (zesty-proposed) [1.5.7+20160812-0ubuntu8]
[06:09] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.9]
[06:09] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (xenial-proposed) [1.66.9]
[06:10] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (zesty-proposed) [2.11.0-2ubuntu3]
[06:11] -queuebot:#ubuntu-release- Unapproved: makedev (trusty-proposed/main) [2.3.1-93ubuntu1 => 2.3.1-93ubuntu2~ubuntu14.04.1] (core)
[06:12] -queuebot:#ubuntu-release- Unapproved: makedev (xenial-proposed/main) [2.3.1-93ubuntu1 => 2.3.1-93ubuntu2~ubuntu16.04.1] (core)
[06:12] -queuebot:#ubuntu-release- Unapproved: makedev (yakkety-proposed/universe) [2.3.1-93ubuntu1 => 2.3.1-93ubuntu2~ubuntu16.10.1] (core, lubuntu)
[06:12] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.8.0-44.47~16.04.1]
[06:12] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-70.91]
[06:14] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (xenial-proposed) [0.9+1474479173.6c180c6-1ubuntu1]
[06:14] -queuebot:#ubuntu-release- Unapproved: makedev (precise-proposed/main) [2.3.1-89ubuntu2 => 2.3.1-89ubuntu3] (core)
[06:14] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (yakkety-proposed) [4.8.0-44.47]
[06:18] -queuebot:#ubuntu-release- Unapproved: rejected snapd-glib [source] (zesty-proposed) [1.8-0ubuntu1]
[06:20] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.8 => 2.02~beta2-36ubuntu3.9] (core)
[06:20] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (xenial-proposed) [1.27~16.04.1]
[06:20] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.19~16.04.1 => 1.27~16.04.1] (core)
[06:24] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (xenial-proposed) [1.27~16.04.1]
[06:24] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.19~16.04.1 => 1.27~16.04.1] (core)
[06:31] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (xenial-proposed) [1.27~16.04.1]
[06:39] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.19~16.04.1 => 1.27~16.04.1] (core)
[06:40] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.9 => 2.02~beta2-36ubuntu3.9] (core)
[06:41] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (xenial-proposed) [1.27~16.04.1]
[06:42] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (yakkety-proposed) [2.02~beta2-36ubuntu11.2]
[06:43] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (xenial-proposed) [2.02~beta2-36ubuntu3.9]
[06:43] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (xenial-proposed) [2.02~beta2-36ubuntu3.9]
[06:43] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (yakkety-proposed) [1.74.2]
[06:47] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (yakkety-proposed) [0.9+1474479173.6c180c6-1ubuntu1]
[06:49] -queuebot:#ubuntu-release- Unapproved: accepted unity-settings-daemon [source] (zesty-proposed) [15.04.1+17.04.20170322-0ubuntu1.1]
[06:50] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (yakkety-proposed) [1.27~16.10.1]
[06:52] -queuebot:#ubuntu-release- Unapproved: shim-signed (yakkety-proposed/main) [1.21.3 => 1.27~16.10.1] (core)
[06:53] -queuebot:#ubuntu-release- Unapproved: grub2 (yakkety-proposed/main) [2.02~beta2-36ubuntu11 => 2.02~beta2-36ubuntu11.2] (core)
[06:55] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (yakkety-proposed) [2.02~beta2-36ubuntu11.2]
[06:57] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (yakkety-proposed) [1.27~16.10.1]
[07:01] <ginggs> any ~ubuntu-archive members around to remove some universe packages please?
[07:18] <apw> ginggs, you should just ask for what you want done, not if people are here
[07:19] -queuebot:#ubuntu-release- Unapproved: grub2 (yakkety-proposed/main) [2.02~beta2-36ubuntu11.2 => 2.02~beta2-36ubuntu11.2] (core)
[07:20] <ginggs> apw: i have a list of several bugs, i didn't want to spam the channel :)
[07:21] <ginggs> LP: #167419 LP: #1671423 LP: #1671429
[07:22] <ginggs> sorry first one was a typo, should be LP: #1671419
[07:23] <ginggs> LP: #1671431 LP: #1671451 LP: #1671452
[07:27] <ginggs> and i'd appreciate if someone would look at an FFe LP: #1672412 - should be straightforward
[07:39] <apw> ginggs, on that FFe i think the question about where does the current stable go if this is done is valid
[07:43] <ginggs> apw, jbicha: the only reason debian are stuck with wine 1.8.7 instead of 2.0 is because of their freeze, i see no reason why we couldn't have wine-development 2.4+ and wine 2.0 in ubuntu
[07:44] <apw> ginggs, and perhaps indeed that is also reasonable, but right now we have two stable releases (with daft names) and your ffe would mean we lose the newer of those
[07:46] <ginggs> apw: i don't think we should be encouraging users who want the stable version to switch to wine-development
[07:46] <apw> ginggs, no this is all a bit of a mess
[07:47] <apw> because they almost cirtianly will, i am sure the first hit on google for "wine not working" will be to update to that, bound to be
[08:00] -queuebot:#ubuntu-release- Unapproved: socklog (zesty-proposed/universe) [2.1.0-8 => 2.1.0-8.1] (no packageset) (sync)
[08:00] -queuebot:#ubuntu-release- Unapproved: twoftpd (zesty-proposed/universe) [1.42-1 => 1.42-1.1] (no packageset) (sync)
[08:01] -queuebot:#ubuntu-release- Unapproved: accepted socklog [sync] (zesty-proposed) [2.1.0-8.1]
[08:02] -queuebot:#ubuntu-release- Unapproved: accepted twoftpd [sync] (zesty-proposed) [1.42-1.1]
[08:02] -queuebot:#ubuntu-release- Unapproved: uucpsend (zesty-proposed/universe) [1.1-4 => 1.1-4.1] (no packageset) (sync)
[08:02] -queuebot:#ubuntu-release- Unapproved: accepted uucpsend [sync] (zesty-proposed) [1.1-4.1]
[08:35] -queuebot:#ubuntu-release- Unapproved: gitlab (zesty-proposed/universe) [8.13.11+dfsg-7 => 8.13.11+dfsg-8] (no packageset) (sync)
[08:36] -queuebot:#ubuntu-release- Unapproved: accepted gitlab [sync] (zesty-proposed) [8.13.11+dfsg-8]
[08:42] <tjaalton> Laney: re https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 please have a look, it'll take a while to get these sorted through -proposed
[08:52] <acheronuk> apw or anyone else: could you badtest/skiptest etc the test on liqapt against polkit-kde-agent-1? https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#polkit-kde-agent-1
[08:52] <acheronuk> that acc fail there is just it needing -fno-keep-inline-functions passed to GCC (change in gcc since last upload) rather than any actual fail to be concerned on
[08:54] <acheronuk> something to tweak to fix next time a upload is needed for another reason, but probably not now with all re-tests against it's r-deps that brings
[08:54] <flexiondotorg> Please unblock ubuntu-mate-artwork/17.04.8
[09:05] <apw> flexiondotorg, ? that is in zesty-release ?
[09:16] <Laney> right, there's no freeze @ proposed-migration
[09:26] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.27.1 => 2.28] (no packageset)
[09:29] -queuebot:#ubuntu-release- Unapproved: snapcraft (yakkety-proposed/universe) [2.27.1+16.10 => 2.28+16.10] (no packageset)
[09:39] <Laney> wtf
[09:39] <Laney> why are there now *three* kwin/ppc64el tests running?
[09:39] -queuebot:#ubuntu-release- Unapproved: rickshaw (zesty-proposed/universe) [1.5.1.dfsg-1 => 1.5.1.dfsg-2] (no packageset) (sync)
[09:39] -queuebot:#ubuntu-release- Unapproved: accepted rickshaw [sync] (zesty-proposed) [1.5.1.dfsg-2]
[09:39] <Laney> acheronuk: I'm killing yours
[09:40] <flexiondotorg> apw Yes, it is. I wasn't seeing it in updates to the test machine. It has arrived now. Thanks.
[09:42] <acheronuk> Laney: whoops. sorry
[09:44] <acheronuk> Laney: could you also see my earlier request to skip the libqapt test for now? thx
[09:44] <acheronuk> if you have time to look
[09:45] <Laney> Not right now
[09:45] <LocutusOfBorg> Laney, my bad sorry
[09:46] <LocutusOfBorg> I didn't mean to run against proposed, so I triggered again without
[09:46] <acheronuk> Laney: np. not urgent
[09:47] <LocutusOfBorg> (I can't see the third one BTW)
[09:47] <acheronuk> LocutusOfBorg: I guess already killed
[09:48] <LocutusOfBorg> maybe, not sure how I could have triggered it
[09:49] <acheronuk> LocutusOfBorg: you didn't. that was me :P
[09:49] <acheronuk> should have check what was running 1st :/
[09:49] <LocutusOfBorg> oh wondeerful! sometimes with my little android screen I misclick them :)
[09:50]  * acheronuk shudders at the thought of the excuses page on android!
[09:52] <LocutusOfBorg><EMAIL_ADDRESS>[09:52] <LocutusOfBorg> Laney, ^^ wheel/armhf stuck again
[09:52] <Laney> retry it
[09:52] <Laney> that bug isn't going to get magically fixed
[09:52]  * LocutusOfBorg finds difficult to generate a retry link when it is "running" :p
[09:53] <Laney> retry-autopkgtest-regressions --state RUNNING
[09:53] <LocutusOfBorg> lovely
[09:54] <LocutusOfBorg> I waste a lot of time manually creating such links :)
[09:54] <Laney> heh
[09:56] <LocutusOfBorg> it is too silent, it exits without printing stuff
[09:56]  * LocutusOfBorg looks at the code
[09:58] <Laney> https://paste.ubuntu.com/24240035/
[09:59] <LocutusOfBorg> ok missing cookie and running uppercase :)
[10:00] <LocutusOfBorg> thanks
[10:00] <Laney> you only need the cookie for passing the URLs into wget or whatever
[10:00] <Laney> not if you just want to click them
[10:01]  * LocutusOfBorg deletes the cookie
[10:01] <LocutusOfBorg> I prefer to for i in `cat output` open them :p
[10:12] -queuebot:#ubuntu-release- Unapproved: putty (zesty-proposed/universe) [0.67-2 => 0.67-3] (no packageset) (sync)
[10:14] -queuebot:#ubuntu-release- Unapproved: accepted putty [sync] (zesty-proposed) [0.67-3]
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (yakkety-proposed) [2.28+16.10]
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.28]
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted cups [source] (zesty-proposed) [2.2.2-1ubuntu1]
[11:08] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (yakkety-proposed) [16.03-0ubuntu<IP_ADDRESS>]
[11:09] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (xenial-proposed) [16.03-0ubuntu<IP_ADDRESS>]
[12:02] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (yakkety-proposed) [2.02~beta2-36ubuntu11.2]
[12:32] <jbicha> ginggs: why don't you see if you can convert 'wine' to 2.0 *before* updating wine-development then?
[12:51] <ginggs> jbicha: for simplicity, i would prefer to stick as close as possible to debian, i.e. wine 1.8.7-2 and wine-development 2.4-1 - but I don't see any reason why you should not convert wine-development 2.0 into wine 2.0, if you wanted to do that
[12:52] <jbicha> ginggs: well you could ask jre to push wine 2.0 to wine/exp
[12:53] <jbicha> I like staying close to Debian too; that's how we ended up wine 1.7 and wine-development 2.0 because that made the most sense there I think
[12:54] <ginggs> jbicha: good idea :) i will ask jre - but i believe he is waiting on an unblock for wine 1.8.7-2
[12:55] <ginggs> jbicha: for reference, debian bug #858371
[12:56] <jbicha> since wine/exp is in use, maybe it could still be pushed to a Debian git branch?
[13:20] -queuebot:#ubuntu-release- Unapproved: gst-libav1.0 (zesty-proposed/universe) [1.10.3-1 => 1.10.4-1] (kubuntu) (sync)
[13:20] -queuebot:#ubuntu-release- Unapproved: gstreamer1.0 (zesty-proposed/main) [1.10.3-1 => 1.10.4-1] (desktop-core) (sync)
[13:21] -queuebot:#ubuntu-release- Unapproved: gst-plugins-bad1.0 (zesty-proposed/universe) [1.10.3-1ubuntu4 => 1.10.4-1ubuntu1] (ubuntustudio)
[13:22] -queuebot:#ubuntu-release- Unapproved: gst-plugins-base1.0 (zesty-proposed/main) [1.10.3-1ubuntu1 => 1.10.4-1ubuntu1] (kubuntu, ubuntu-desktop)
[13:22] -queuebot:#ubuntu-release- Unapproved: gst-plugins-ugly1.0 (zesty-proposed/universe) [1.10.3-1ubuntu1 => 1.10.4-1ubuntu1] (kubuntu)
[13:22] -queuebot:#ubuntu-release- Unapproved: gst-plugins-good1.0 (zesty-proposed/main) [1.10.3-1ubuntu1 => 1.10.4-1ubuntu1] (kubuntu, ubuntu-desktop)
[13:25] -queuebot:#ubuntu-release- Unapproved: gst-python1.0 (zesty-proposed/universe) [1.10.3-1 => 1.10.4-1] (ubuntustudio) (sync)
[13:26] -queuebot:#ubuntu-release- Unapproved: gst-rtsp-server1.0 (zesty-proposed/universe) [1.10.3-1 => 1.10.4-1] (no packageset) (sync)
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted gst-rtsp-server1.0 [sync] (zesty-proposed) [1.10.4-1]
[13:26] -queuebot:#ubuntu-release- Unapproved: gstreamer-vaapi (zesty-proposed/universe) [1.10.2-1build1 => 1.10.4-1] (no packageset) (sync)
[13:26] -queuebot:#ubuntu-release- Unapproved: gstreamer-editing-services1.0 (zesty-proposed/universe) [1.10.3-1 => 1.10.4-1] (ubuntustudio) (sync)
[13:27] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer-vaapi [sync] (zesty-proposed) [1.10.4-1]
[13:35] <Laney> who synced vaapi?
[13:36] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/gstreamer-vaapi/+publishinghistory
[13:36] <LocutusOfBorg> :)
[13:37] -queuebot:#ubuntu-release- Unapproved: libqapt (zesty-proposed/universe) [3.0.2-0ubuntu4 => 3.0.2-0ubuntu5] (kubuntu)
[13:37] <Laney> Waste of a build, and I had deliberately not synced it.
[13:37] <Laney> It needs to be built after -bad.
[13:38] <LocutusOfBorg> jbicha, ^^
[13:46] -queuebot:#ubuntu-release- Unapproved: mir (zesty-proposed/main) [0.26.1+17.04.20170209.1-0ubuntu1 => 0.26.2+17.04.20170322.1-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[13:46] -queuebot:#ubuntu-release- Unapproved: signon-ui (zesty-proposed/main) [0.17+17.04.20161109-0ubuntu1 => 0.17+17.04.20170320-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[14:36] <apw> Laney, it would be so nice if there was a block for those at the queue level, but expressed like the britney ones
[14:38] <Laney> for what?
[14:38] <apw> "i know this won't build don't let anyone sync it till that is fixed"
[14:39] <Laney> meh, maybe, I could have put something into queuebot
[14:40] <Laney> or people could not get involved in something that somebody else is clearly actively working on without consulting with that person
[14:40] <apw> or that
[14:46] <jbicha> yes, I'll try to ask first next time
[14:48] <Laney> thx
[14:57] <salem_> Hello. We are about to land a silo that will include a new package to the archive. Can anybody tell me what's the correct procedure to get someone to review the package for us? This is the branch: http://bazaar.launchpad.net/~phablet-team/mfw-plugin-irc/dummy-branch/files/head:/debian/
[14:59] <apw> salem_, normally you tell us the silo i think
[14:59] <salem_> apw, thanks! it's https://bileto.ubuntu.com/#/ticket/2629
[15:01] <apw> salem_, any idea which of the packages are new ?
[15:04] <salem_> apw, mfw-plugin-irc is the new one. But messaging-framework is now generating a new binary as well: mfw-plugin-dummy. Not sure if new binaries also require review.
[15:07] <apw> salem_, they do
[15:38] <Laney> hmm
[15:38] <Laney> if a silo can clear a depwait of a package in the main archive on one arch, can I copy that source + binaries into the silo?
[15:39] <Laney> that is, will it work to copy that package same back into zesty-proposed?
[15:43] <Laney> s/package same/same package/ ...
[15:48] <Laney> I guess I can just try it
[15:57] <apw> Laney, as in will you be able to retry the broken one and copy it back ... i think i have done htat kind of thing in error and it tends to work, but i am no lp-db expert
[15:57] <Laney> apw: Yeah, can you just copy some binaries back?
[15:57] <Laney> but I figure that even if that doesn't work, the thing which clears the depwait will be copied and the build will happen again anyway
[15:57] <apw> i think i removed it and copied it in again, but hmmmm
[15:58] <apw> right, that would be more normal i guess, copy the bits to teh PPA, prove it fixes things, copy the fixed other package out, depwait clears in -proposed and that build builds
[15:59] <Laney> well it'll be educational anyway :P
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted variety [source] (xenial-proposed) [0.6.0-1ubuntu1]
[15:59] <apw> :)
[15:59] <apw> my most educational experiences have been through accidents :)
[16:00] -queuebot:#ubuntu-release- Unapproved: webbrowser-app (zesty-proposed/main) [0.23+17.04.20170310-0ubuntu1 => 0.23+17.04.20170321-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[16:22] <infinity> Laney: It can be done, yes.  Or you could just wait until the silo thing is copied to the archive and the arch builds there.  Unless it's blocking silo promotion, and you're trying to hack around that.
[16:27] <Laney> infinity: Yeah, the silo's britney is crying
[16:28] <slangasek> I feel like I should have an animated gif at the ready to go with that comment
[16:29] <apw> i am sure there is an appropriate utube vidio
[16:29] <infinity> Laney: It's going to be less about what the archive allows and more about what the silo machinery lets you do, but I guess you'll find out. :P
[16:30] <infinity> (As in, I suspect silos won't allow you to "release" a package to the archive that has the same version as the archive)
[16:31] <Laney> It thinks that the package is in the release pocket
[16:31] <infinity> So it'll probably need an override on the silo side regardless of how you choose to solve it.
[16:31] <Laney> so I guess that it won't copy it
[16:32] <infinity> Laney: But the answer to the larger LP question is that, yes, you can copy things around willy-nilly and back again, as long as you make sure the binaries always follow you.  Once you end up with two binary builds for the same arch, it'll tell you to get stuffed.
[16:45] -queuebot:#ubuntu-release- Unapproved: qtbase-opensource-src (xenial-proposed/main) [5.5.1+dfsg-16ubuntu7.2 => 5.5.1+dfsg-16ubuntu7.4] (kubuntu, qt5, ubuntu-desktop) (sync)
[16:47] <camako> Hi Mir 0.26.2 (bug-fix release, ticket #2600) is in the 'UNAPPROVED' queue. What do I do to get it approved?
[16:47] <Laney> camako: The queue is regularly reviewed, so it'll be considered soon
[16:48] <camako> Laney, thanks
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-libav1.0 [sync] (zesty-proposed) [1.10.4-1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-base1.0 [source] (zesty-proposed) [1.10.4-1ubuntu1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-ugly1.0 [source] (zesty-proposed) [1.10.4-1ubuntu1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer-editing-services1.0 [sync] (zesty-proposed) [1.10.4-1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-bad1.0 [source] (zesty-proposed) [1.10.4-1ubuntu1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-python1.0 [sync] (zesty-proposed) [1.10.4-1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gst-plugins-good1.0 [source] (zesty-proposed) [1.10.4-1ubuntu1]
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer1.0 [sync] (zesty-proposed) [1.10.4-1]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted libqapt [source] (zesty-proposed) [3.0.2-0ubuntu5]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted signon-ui [sync] (zesty-proposed) [0.17+17.04.20170320-0ubuntu1]
[16:56] -queuebot:#ubuntu-release- Unapproved: accepted mir [sync] (zesty-proposed) [0.26.2+17.04.20170322.1-0ubuntu1]
[16:56] -queuebot:#ubuntu-release- Unapproved: accepted webbrowser-app [sync] (zesty-proposed) [0.23+17.04.20170321-0ubuntu1]
[17:00] <infinity> robru: Yo, you around?
[17:00] <robru> infinity: hey
[17:00] <infinity> robru: WTF is "Blocking because linux from the same PPA ~canonical-kernel-team/+archive/ubuntu/ppa is invalid" and how do I read that?
[17:01] <apw> that is "not-english"
[17:02] <robru> infinity: that means it's being grouped with other packages copied from that PPA.
[17:02] <apw> robru, which ones
[17:03] <infinity> robru: So, that has two problems: (1) assuming anything outside silo land is a one-ppa-per-landing scenario is wrong.
[17:03] <infinity> robru: (2) the message tells me it's blocking on something that is a valid candidate (so, the message is probably wrong).
[17:03] <robru> apw: you have to ctrl+f for that ppa to find them all
[17:03] <infinity> robru: Yeah.  VERY VERY WRONG assumption.
[17:03] <Laney> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#linux
[17:03] <Laney> linux is blocking itself...
[17:04] <infinity> robru: They stage all their kernels in a PPA.  Requiring linux-raspi2 to be ready before linux promotes is not sane.
[17:04] <infinity> (Which is probably what's happening here, despite the error message being a lie)
[17:04] <infinity> Who thought this was a good idea?
[17:05] <infinity> Not all PPAs are disposable silos.
[17:05] <infinity> And the kernel and security team were using theirs for landing long before silos came along. :P
[17:05] <robru> infinity: well we worked this out with Steve as it was a big problem with bileto having tickets half migrate and half get stuck
[17:06] <apw> robru, does that not all say they are only unhappy because 'self'
[17:06] <infinity> robru: Sure, so only check bileto PPAs.
[17:06] <infinity> (And also fix the error message, but that's less of a concern)
[17:06] <robru> apw: yes, there's a bug in how it records the message so all the packages look to be blocked by themselves
[17:07] <apw> robru, regardless of that and it not being appropriate for out PPA, all of those looks to be ok
[17:07] <apw> oh no, i recind that, there is a block bug for raspi2
[17:07] <infinity> All of what looks to be okay? :P
[17:08] <infinity> apw: Exactly.  raspi2 is blocking master, which is why I'm currently yelling on IRC.
[17:08] <apw> yeah for a moment i didn't notice that (cough) i have blocked it raspi2 too :)
[17:09] <robru> infinity: of you're in a hurry, push a commit that stops Britney from loading sourceppapolicy, otherwise I'll push a real fix later
[17:10] <infinity> robru: What will the fix look like?  A whitelist of LP users whose PPAs will be considered by the code (I think that would probably be sanest), or...?
[17:10] <robru> infinity: yeah
[17:10] <infinity> Kay.  If "later" can be today, I'm happy to wait on it, so the kernel PPA is an obvious production test case.
[17:11] <infinity> It's not urgent that it release this hour, but releasing it before the weekend would be a Good Thing.
[17:11] <robru> infinity: ok I'm just having breakfast, will start on that soon
[17:11] <infinity> \o/
[17:20] -queuebot:#ubuntu-release- Unapproved: cargo (zesty-proposed/universe) [0.16.0-0ubuntu1 => 0.17.0-0ubuntu1] (no packageset)
[17:20] -queuebot:#ubuntu-release- Unapproved: pcre3 (zesty-proposed/main) [2:8.39-2 => 2:8.39-3] (core) (sync)
[17:21] -queuebot:#ubuntu-release- Unapproved: accepted cargo [source] (zesty-proposed) [0.17.0-0ubuntu1]
[17:23] -queuebot:#ubuntu-release- Unapproved: thunderbird (zesty-proposed/main) [1:45.7.0+build1-0ubuntu1 => 1:45.8.0+build1-0ubuntu1] (mozilla, ubuntu-desktop)
[17:24] <apw> robru, is there hint language to override that block, does an explict unblock fix it ?
[17:25] <robru> apw: no, it's processed after hint policy
[17:25] <apw> that is rather unfortunate
[17:26] <apw> thoough an explicit unblock of which ever one of those is broke, would that make the set copestetic ?
[17:41] -queuebot:#ubuntu-release- Unapproved: rejected landscape-client [source] (trusty-proposed) [14.12-0ubuntu4.14.04]
[18:04] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (trusty-proposed) [14.12-0ubuntu5.14.04]
[18:23] <robru> infinity: https://code.launchpad.net/~robru/britney/+git/britney2-ubuntu/+merge/320976 here's a fix confirmed with tests, please merge
[18:28] <jbicha> infinity: could you re-enable zesty daily iso builds?
[18:28] <infinity> jbicha: Yep, getting there shortly.
[18:30] <infinity> robru: An inverse test that tests, say, ~canonical-kernel-team/ or ~ubuntu-security-proposed/ to make sure no one derps up and blocks all PPAs again would be nice (at least, it looks like the tests only test the ci-train case, and maybe the empty/primary case?)
[18:30] <infinity> robru: Otherwise, lgtm.
[18:47] <robru> infinity: ok, added a test for ignoring other PPAs. please merge
[18:48] <salem_> apw, if you need any other information regarding reviewing the new packages on silo 2629 please let me know.
[18:49] <apw> salem_, sorry got called away, won't be able to sort that today
[18:53] -queuebot:#ubuntu-release- Unapproved: screen (zesty-proposed/main) [4.5.0-3 => 4.5.0-3ubuntu1] (ubuntu-desktop, ubuntu-server)
[18:54] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (zesty-proposed/universe) [17.04.8 => 17.04.9] (ubuntu-mate)
[18:55] -queuebot:#ubuntu-release- Unapproved: mate-dock-applet (zesty-proposed/universe) [0.76-0ubuntu1 => 0.77-0ubuntu1] (ubuntu-mate)
[18:56] <salem_> apw, ok, do you know if there is any other admin who could do it for us? it's a very simple package.
[19:09] -queuebot:#ubuntu-release- Unapproved: accepted tftp-hpa [source] (yakkety-proposed) [5.2+20150808-1ubuntu<IP_ADDRESS>]
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted mate-dock-applet [source] (zesty-proposed) [0.77-0ubuntu1]
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-welcome [source] (zesty-proposed) [17.04.9]
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted screen [source] (zesty-proposed) [4.5.0-3ubuntu1]
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted pcre3 [sync] (zesty-proposed) [2:8.39-3]
[19:17] -queuebot:#ubuntu-release- Unapproved: accepted tftp-hpa [source] (xenial-proposed) [5.2+20150808-1ubuntu<IP_ADDRESS>]
[19:19] -queuebot:#ubuntu-release- Unapproved: accepted tftp-hpa [source] (trusty-proposed) [5.2-7ubuntu3.1]
[19:40] -queuebot:#ubuntu-release- Unapproved: gnome-dictionary (zesty-proposed/universe) [3.20.0-3 => 3.24.0-0ubuntu1] (desktop-extra)
[20:37] <slangasek> cyphermox, jbicha: seems that shim-signed is now correctly erroring out if it needs to set up mok and has no input, but at least one ubuntu-gnome user is getting no debconf prompting when installing a driver? https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1675870
[20:38] <cyphermox> fun
[20:42] <jbicha> the iso he installed was dated March 21 but the shim-signed fix is from March 22, could he still have been running the old code?
[20:43] <cyphermox> no, it shows it's 1.27
[20:44] <cyphermox> here for some reason this is running in a non-interactive frontend
[20:46] <cyphermox> my guess is it's additional drivers, and the way that's done doesn't get you a frontend because libgtk2-perl isn't installed and it's not falling back to Dialog because the terminal "window" isn't open when this installs.
[20:48] <jbicha> that's during the Install itself isn't it? in the apt history log: Requested by ubuntu-gnome (999)
[20:51] <cyphermox> it looks like it's in live but not done through the installer
[20:51] <cyphermox> Commandline: aptdaemon role='role-commit-packages' sender=':1.452'
[20:55] -queuebot:#ubuntu-release- Unapproved: cloud-init (zesty-proposed/main) [0.7.9-68-gef18b8ac-0ubuntu1 => 0.7.9-77-g4a2b2f87-0ubuntu1] (edubuntu, ubuntu-cloud, ubuntu-server)
[20:55] <jbicha> oh ok, so shim-signed was updated from the live iso but then he installed nvidia afterwards
[21:36] -queuebot:#ubuntu-release- Unapproved: xfdashboard (zesty-proposed/universe) [0.6.0-0ubuntu2 => 0.6.1-0ubuntu1] (xubuntu)
[21:43] -queuebot:#ubuntu-release- Unapproved: indicator-transfer-buteo (zesty-release/universe) [0.1+15.10.20151006-0ubuntu1 => 0.1+15.10.20151006-0ubuntu1] (no packageset) (sync)
[21:43] -queuebot:#ubuntu-release- Unapproved: accepted indicator-transfer-buteo [sync] (zesty-release) [0.1+15.10.20151006-0ubuntu1]
[21:49] <Ukikie> xfdashboard is an unseeded bugfix: https://mail.xfce.org/pipermail/xfce/2016-December/035391.html "Fixed a typo in default application array which prevented the correct default applications to be set up when xfdashboard was started the very first time." (Xfce 12842)
[22:06] -queuebot:#ubuntu-release- Unapproved: mir (zesty-proposed/main) [0.26.2+17.04.20170322.1-0ubuntu1 => 0.26.2+17.04.20170322.1-0ubuntu2] (kubuntu, ubuntu-desktop)
[22:27] -queuebot:#ubuntu-release- Unapproved: gstreamer-vaapi (zesty-proposed/universe) [1.10.4-1 => 1.10.4-1build1] (no packageset)
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted gstreamer-vaapi [source] (zesty-proposed) [1.10.4-1build1]
[22:58] -queuebot:#ubuntu-release- Unapproved: mate-panel (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[23:42] -queuebot:#ubuntu-release- Unapproved: gnome-sound-recorder (zesty-proposed/universe) [3.21.92-2 => <IP_ADDRESS>-0ubuntu1] (no packageset)
[23:43] -queuebot:#ubuntu-release- Unapproved: accepted gnome-sound-recorder [source] (zesty-proposed) [<IP_ADDRESS>-0ubuntu1]
[23:59] -queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (zesty-proposed/main) [3.24.0-0ubuntu1 => 3.24.0-0ubuntu2] (ubuntu-desktop)


[17:36]  * mhayden tips his hat to JayF
[17:55]  * gholms waves at mhayden
[17:56] <JayF> Hey smoser, mhayden is another long-time racker
[17:56] <harlowja> mhayden hey, for https://code.launchpad.net/~rackerhacker/cloud-init/add-ipv6-static-address-support a coworker at y! is also working on this, https://bugs.launchpad.net/cloud-init/+bug/1391695 ; she should have that up for review today, hopefully we can look at both and merge them or something
[17:56] <JayF> he's going to be tossing a patch your way for IPv6 static support
[17:57] <harlowja> JayF i saw that :-P
[17:57] <mhayden> harlowja: good timing ;)
[17:57] <harlowja> ;)
[17:57] <mhayden> harlowja: should i add a mention of my branch in that ticket?
[17:57] <harlowja> sure, although both of u guys i think started a solution at the same time, ha
[17:57] <harlowja> concidence :-P
[17:57] <mhayden> i'm curious to see the other solution as this is my first time working with cloud-init ;)
[17:58] <mhayden> well, working with the code itself i mean
[17:58] <harlowja> agreed
[17:58] <harlowja> she'll be in shortly i think
[18:00] <harlowja> mhayden another intersting question is whether ipv6 works for the other distros also
[18:00] <harlowja> that network conversion (from ubuntu -> internal format) is also used in freebsd for example
[18:00] <mhayden> my changes only add in some new dict keys
[18:00] <mhayden> so it shouldn't affect them unless they blindly write whatever is in the dict
[18:01] <mhayden> i didn't check around for that
[18:01] <harlowja> ya i don't think they do, but my guess is they are also not ipv6 compat
[18:01] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/distros/sles.py#L56
[18:01] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/distros/arch.py#L63
[18:01] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/distros/freebsd.py#L273
[18:01] <mhayden> ah so yeah, the sles one would just write IPv4 config only
[18:02] <harlowja> ya
[18:02] <mhayden> would it make sense in the future to put all the network config into json and avoid parsing the debian-style network config?
[18:02] <JayF> mhayden: That's what I'm doing :)
[18:02] <harlowja> +1
[18:02] <harlowja> ;)
[18:02] <mhayden> then i owe you tacos, JayF
[18:02] <JayF> mhayden: https://github.com/racker/cloud-init/pull/1 is the downstream patch we use for OnMetal now (I think it's enabled on the whole cloud at this point, perhaps?)
[18:03] <JayF> mhayden: we put some info in vendor_data that's based on a spec upstream for openstack to put in json network data, and read that today
[18:03] <harlowja> https://review.openstack.org/#/c/85673/16/specs/kilo/approved/metadata-service-network-info.rst right?
[18:03] <JayF> mhayden: when openstack's upstream one comes, we'll migrate off our vendored one and go to the upstream one
[18:03] <JayF> aye, capn
[18:03] <JayF> although tbh I'm not working on it actively right now
[18:04] <harlowja> whose 'Claxton Correya' i don't think thats an alias for u
[18:04] <harlowja> lol
[18:04] <harlowja> maybe it is though
[18:04] <mhayden> it's his pen name
[18:04] <harlowja> cools
[18:04] <mhayden> i'm kidding ;)
[18:04] <harlowja> me too
[18:04] <harlowja> :)
[18:17] <smoser> hey all. i'm sorry for not being present.
[18:18] <smoser> been traveling / working last three weeks and not much else.
[18:23] <harlowja> spandhe mhayden welcome, both fixing ipv6
[18:23] <harlowja> :-P
[18:23] <mhayden> yay
[18:24] <spandhe> haha
[18:43] <harlowja> mhayden spandhe  i think uploaded https://code.launchpad.net/~shraddha-pandhe/cloud-init/cloud-init-ipv6-support if u want to check thato ut
[18:44] <mhayden> taking a look
[18:46] <mhayden> looks reasonable except i might toss in a "IPV6_AUTOCONF=no" into cloudinit/distros/rhel.py
[18:46] <mhayden> just for completeness
[18:46] <mhayden> since there's going to be a static assignment
[18:46] <mhayden> but i like that spandhe remembered NETWORKING_IPV6 in /etc/sysconfig/network -- i forgot
[18:47] <spandhe> mhayden: I thought BOOTPROTO=static will take care of it..
[18:47] <spandhe> Ill look up more about autoconf
[18:47] <JayF> spandhe: not always ime
[18:47] <JayF> spandhe: IPV6_AUTOCONF=no basically maps directly to the sysctl iirc
[18:48] <spandhe> mhayden: I also put the routing info and ifconfig support..
[18:48] <mhayden> good stuff, spandhe
[18:49] <mhayden> i'm not sure about the issues caused by leaving out IPV6_AUTOCONF... but i haven't seen any providers that due IPv6 via SLAAC yet
[18:49] <mhayden> it would hopefully protect the VM against router advertisement attacks though
[18:50] <spandhe> thanks mhayden ! will add unittests soon too.. also, for now, makes sense to keep autoconf = no.. nova currently doesnt provide any information about it.. so safe it keep it no..
[18:50] <mhayden> cool
[18:50] <mhayden> i still haven't wrapped my head around writing tests in python :)
[18:52] <spandhe> mhayden: cool :) need to addcsupport for IPV6ADDR_SECONDARIES later..
[18:52] <mhayden> that will be fun
[18:52] <mhayden> do you have a use case for it? i don't
[18:52] <mhayden> we assign a single IPv6 address per instance for now
[18:52] <mhayden> anything other than that would be a floating/shared IP
[18:55] <spandhe> right.. not for now.. but when we have multiple later with global scope, etc, we can add it..
[18:56] <mhayden> makes sense
[18:56] <mhayden> harlowja: i'm a launchpad dunce -- how do i kick out my branch proposal?
[18:58] <harlowja> i believe there is a delete branch that i think u can access on https://code.launchpad.net/~rackerhacker/cloud-init/add-ipv6-static-address-support if thats what u want to do
[18:59] <JayF> mhayden: ++ absolutely hardening against RA attacks is perfect
[18:59] <mhayden> harlowja: yeah, i'll yield to spandhe's work there
[19:00] <mhayden> done
[19:00] <mhayden> JayF: yay
[19:00] <harlowja> kk
[20:23] <harlowja> smoser alright got http://cloudinit.readthedocs.org/en/latest/topics/modules.html to generate more goodness
[20:23] <harlowja> example @ http://cloudinit.readthedocs.org/en/latest/topics/modules.html#debug
[20:23] <harlowja> woot
[20:24] <harlowja> looks good this time
[20:24] <harlowja> http://cloudinit.readthedocs.org/en/latest/topics/modules.html#ubuntu-init-switch also


[00:54] <Megaladon> hey, I'm running ubuntu studio 18.10 and my volume keys aren't working
[00:55] <Eickmeyer> Megaladon: known problem. Let me see if I can find the bug report.
[00:55] <Megaladon> thanks
[00:56] <Eickmeyer> Megaladon: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1291855
[00:56] <Eickmeyer> Megaladon: Read my comment #7, that should be your workaround.
[00:56] <Eickmeyer> Permanent workaround coming to 19.10.
[00:56] <Eickmeyer> Unfortunately, development has stopped on xfce4-volumed.
[00:57] <Megaladon> is it this one? killall xfce4-volumed
[00:57] <Megaladon> xfce4-volumed
[00:57] <Eickmeyer> Yes. That needs to be entered in a terminal, one line at a time, or with && between them.
[00:59] <Megaladon> bash: syntax error near unexpected token '&&'
[00:59] <Megaladon> ?
[00:59] <Eickmeyer> No, if you want to put them all in one line, you'd but && in the middle.
[00:59] <Eickmeyer> "killall xfce4-volumed && xfce4-volumed"
[01:00] <Megaladon> ah
[01:00] <Megaladon> works now
[01:00] <Megaladon> thank you!!
[01:00] <Eickmeyer> Good. Unfortunately, you'll have to do that any time you switch between Jack and PulseAudio. In other words, when PulseAudio restarts.
[01:01] <Megaladon> What's the difference between Jack and PulseAudio?
[01:01] <Megaladon> I frequently use Ardour is that goig to mess with anything I just did?
[01:08] <Megaladon> nvmd, I just looked it up.
[01:08] <Megaladon> thanks for the volume fix
[01:16] <Eickmeyer> Megaladon: You're welcome. I finally pulled the trigger and put it in the release notes.
[01:16] <Eickmeyer> It has only become a problem recently, which is why it went undetected.
[01:22] <Megaladon> I'm way stoked on ubuntu studio and recording with ardour
[01:22] <Megaladon> what would cause PulseAudio to restart
[01:22] <Eickmeyer> Megaladon: It's fun. I used to do a lot more recording, but I also have used it for live effects processing.
[01:23] <Megaladon> cool
[01:23] <Megaladon> like adjusting the output sound of a pedal while playing live?
[01:38] <Eickmeyer> Megaladon: I'm an audio engineer, so we're talking vocal effects or taking an instrument and adding a stereo-pseudo-surround effect to it using phase and delay manipulation.
[01:41] <Megaladon> sounds like an advanced form of reverb
[01:46] <Eickmeyer> Not exactly. The guitarist would send all of that to the amp, then I'd have the amp mic'd to the mixer. From there I'd send the audio from the mixer to my computer via USB where it would split the signal into two,
[01:46] <Eickmeyer> change the phase on one, then add a slight (10-20ms) delay on that channel with a slight EQ to make it sound like the amp was a stero amp.
[01:46] <Eickmeyer> Megaladon: ^
[01:47] <Eickmeyer> EQ boost around 3k of about 2-3dB.
[01:47] <Eickmeyer> Then I'd send that back to the mixer in the form of a stereo return to a spare channel.
[01:48] <Eickmeyer> The effects I'd do would be controlled via a Behringer X-Touch Mini MIDI controller.
[01:53] <Megaladon> gotchya
[01:58] <Megaladon> thanks again for the help, I'll catchya later
[03:32] <studio-user268> Can I run Ubuntu Studio on a PC with 2 GB ram and 2,2 Ghz single core processor? Also, will it work to run the latest version alongside win 7?
[18:35] <Thr0r> I'm looking into Ubuntu studio to create a lib of all my old music CD's and playlists and all but when copying from CD I only get Track 1, Track 2,.. Not the song title.... Is It possible to retrieve that from the CD? I'm using Parole 1.0.2 now.
[18:50] <M_aD> install asunder to rip CD's
[18:53] <Thr0r> ok - thanks - I will check that
[18:57] <M_aD> works great, been using it for a few years now myself on various distro'
[19:09] <Thr0r> M_aD:  I installed Asunder but it will not start. Nothing happens when I click on it..
[19:10] <M_aD> weird
[19:10] <Thr0r> yes..
[19:10] <M_aD> i'm no expert on when stuff goes wrong or doesn't work
[19:10] <M_aD> doe you have Jack running? If so stop it and try again
[19:10] <M_aD> doe/do
[19:11] <Thr0r> Ok, It seems to happen from time to time on Linux...
[19:11] <Thr0r> ok - I will try
[19:13] <M_aD> never had that issue so it doesn't happen from time to time, at least not at my end
[19:15] <M_aD> Thr0r: by the way, which version of ubuntu studio are you using?
[19:18] <Thr0r> The latest 19.04
[19:27] <M_aD> Had Ubuntu Studio 19.04 running myself without any issues using asunder, same on xubuntu 19.04 that i use on this machine at the moment
[19:32] <Thr0r> I have tried to stop Jack, did not help, I have tried to uncheck "Auto Start Jack at session start" and reboot - did not help. Now I also tried to install Asunder on my xubuntu laptop with no Jack installed - And it still will not start. Nothing happens..
[19:32] <M_aD> hard to believe since it works at my end
[19:33] <M_aD> is it a VM or bare metal install
[19:35] <M_aD> if it's installed on your computer what are the specs
[19:35] <Thr0r> Studio install i dualboot with win7 using Grub. xubuntu is "bare metal" - Only xubuntu install on that
[19:38] <Thr0r> What is the command in Linux to get the specs of my computer?
[19:39] <M_aD> inxi -Fxz
[19:40] <M_aD> use pastebin to share the info
[19:40] <M_aD> https://paste.ubuntu.com/
[19:50] <Thr0r> ok -I used pastebin now
[19:50] <Thr0r> that is info of my xubuntu laptop
[19:51] <M_aD> where's the link?
[19:51] <Thr0r> oh....   https://paste.ubuntu.com/p/BdfJzRjzzF/
[19:52] <M_aD> that's not the complete output of inxi -Fxz
[19:52] <M_aD> how much ram does it have?
[19:53] <Thr0r> But when it does not work on any of my laptops it must be something wrong with the insall
[19:53] <Thr0r> 2GB
[19:54] <M_aD> is that xubuntu or ubuntu studio...
[19:55] <Thr0r> that is info of my xubuntu laptop.  The Ubuntu studio has 6GB RAM
[19:56] <M_aD> oh, i thought xubuntu also was 19.04 but it's 18.04.2
[19:57] <M_aD> maybe something is wonky hardwarewise, hard drive issues maybe that's causing stuff to get corrupted and act weird
[19:58] <Thr0r> Yes - I don't think the is any xubuntu 19.04?
[19:59] <M_aD> what do you mean?
[19:59] <M_aD> that there's no xubuntu 19.04? sorry not getting the last phrase
[20:02] <M_aD> anyway, no matter what, i can't help you further with the issues you have
[20:02] <Thr0r> When I was downloading I just saw studio in 19.04 and xubuntu in 18.04 - but I don't know. Doesn't mater really. Asund does not work and I am getting nowhere. I would like to have some way of copying my CD's with Album and Song titles. But I will have to look somewhere for that
[20:03] <M_aD> there is a xubuntu 19.04..... as with Ubuntu releases all flavours are released at the same time
[20:04] <M_aD> try restarting and see if asunder starts then
[20:04] <M_aD> if not check if your hard drives are still ok
[20:05] <Thr0r> ok. I have tried restart. But anyway - thanks for the help.
[20:05] <M_aD> you're welcome
[21:51] <Thr0r> M_aD: Still there? I must apologize to you for the Asunder issue - not starting etc. I went into Software shop and search for Asunder and installed the first one there. The description matched what I wanted but as you know it did not start. Turns out I installed Asunder-casept (don't know what that is but has the same description as Asunder CD-ripper). So now I installed Asunder CD-ripper and it starts and works like a charm, seems
[21:51] <Thr0r>  really, really good! Sorry for taking up your time but the Software shop descriptions tricked me...
[22:42] <M_aD> Thr0r: no problem :)


[03:53] <xu-irc55w> hello
[03:53] <xu-irc55w> hello
[03:54] <xu-irc55w> how to sharing printer in xubuntu 14,04 ? thank you
[05:19] <kurly> 14.04? lol
[06:15] <PC1> Ciao.
[12:03] <rrr> I have been having some difficulty with bridge networking, where the network doesn't connect right away. I think I have netplan configured uneccessarily. Can someone tell me how to safely remove or disable this feature?
[12:10] <kryten> rrr: Since Netplan is slightly out of context for Xubuntu, you might want to ask on the main #ubuntu channel instead.
[12:12] <rrr> ok
[12:13] <rrr> I configured netplan in hopes of using a bridge with kvm, but managed to use nmcli to achive the correct outcome, can someone direct me to disable netplan?
[12:14] <rrr> oops
[12:14] <rrr> wrong chan.


[00:01] <bryce> seb128: hrm, from what I can tell I did not get a response from any gnomecc developers :-/
[00:02] <seb128> bryce: be patient, that's not even a day
[00:13] <bryce> ok
[09:03] <tjaalton> mvo_: regarding the problems with nvidia/fglrx postrm & diversions, there's a proposed patch in bug 130208
[09:03] <tjaalton> mvo_: http://launchpadlibrarian.net/9881445/linux-restricted-modules-2.6.22_<IP_ADDRESS>-13.6ubuntu1.debdiff
[09:03] <ubotu> Launchpad bug 130208 in linux-restricted-modules-2.6.24 "package nvidia-glx None failed to install/upgrade: subprocess post-removal script returned error exit status 2" [Medium,Confirmed] https://launchpad.net/bugs/130208
[09:04] <tjaalton> mvo_: if you have time to check if the mechanism looks good..
[09:05] <tjaalton> tseliot proposed another patch (bug 36625), but this looks better to my eyes
[09:05] <ubotu> Launchpad bug 36625 in linux-restricted-modules-2.6.24 "can't remove nvidia-glx" [Medium,Confirmed] https://launchpad.net/bugs/36625
[09:12] <mvo_> tjaalton: the logic looks ok, also "==" is a bashism, it should be "=" instead
[09:13] <mvo_> and I would use $() instead of ` `
[09:14] <tjaalton> mvo_: cool, thanks! I guess I'll add that for -8
[09:14] <tjaalton> there are a lot of dupes about that, but I kept them separate since some had these suggestions about how to fix it
[09:14] <mvo_> nice, my only concern left would be that the output of dpkg-divert might change depending on the locale, but quickly looking over the dpkg-divert code, this seems to be not the case
[09:15] <mvo_> tjaalton: yeah, its cool that this is attacked now :)
[09:15] <tjaalton> I'm trying to keep the l-r-m-2.6.24 bug list sane :)
[09:16] <tjaalton> .22 has 220 open bugs
[09:16] <tjaalton> .24 "only" 52 at the moment
[09:18] <bryce> yay
[09:56] <ubotu> New bug: #191779 in xorg (main) "No nvidia driver after februar, 13th update" [Undecided,New] https://launchpad.net/bugs/191779
[11:27] <ubotu> New bug: #112514 in linux-restricted-modules-2.6.24 (restricted) "Firefox Menu Font Size Is To Large" [Low,New] https://launchpad.net/bugs/112514
[12:51] <ubotu> New bug: #191783 in compiz (main) "window title changes cause window decorator to render poorly (dup-of: 186382)" [Undecided,Incomplete] https://launchpad.net/bugs/191783
[21:16] <ubotu> New bug: #190166 in xserver-xorg-input-synaptics "scrollpad doesn't work on 8.04" [Undecided,Incomplete] https://launchpad.net/bugs/190166
[21:52] <ubotu> New bug: #42459 in linux-restricted-modules-2.6.15 (restricted) "driver not working in dapper drake" [Medium,Fix released] https://launchpad.net/bugs/42459
[21:56] <tjaalton> yay, soon below 1400 open team bugs
[21:56] <tjaalton> over 400 less than what it was two months ago
[22:10] <bryce> :-)
[22:11] <bryce> I got bored breaking my displays and sorting out crtc issues so am reviewing bugs
[22:11] <seb128> good work guys ;-)
[22:11] <bryce> thanks seb128
[22:12] <bryce> tjaalton: btw, did we get to a decision on XAA vs. EXA on 965?  I'm debating about uploading my patch for bug 175774
[22:12] <ubotu> Launchpad bug 175774 in xserver-xorg-video-intel "[hardy] Enabling "Normal" effects produces badly drawn window shadows." [Critical,In progress] https://launchpad.net/bugs/175774
[22:13] <mvo> if you do exa, we could keep compiz enabled there ...
[22:14] <tjaalton> well, if it can be patched to keep exa & greedy for 965..
[22:14] <tjaalton> bryce: didn't upstream say that patch would break stuff?
[22:15] <bryce> tjaalton: I never really got a response from upstream on it
[22:15] <bryce> but I've been running it on one of my 965 machines I use a lot, with no issues  evident
[22:16] <tjaalton> ok.. anyway, exa without any tricks is unusable on 965
[22:16] <tjaalton> and the rest could use xaa
[22:16] <tjaalton> and with tricks the shadow looks fine, since it bypasses most acceleration paths
[22:19] <tjaalton> seb128: do you personally know any hal experts? I'm waiting a reply from upstream about a problem I have with hal-set-property. it would be vital for input-hotplug
[22:19] <tjaalton> h-s-p works when run by hand but not from a hal script
[22:19] <tjaalton> which would suggest that there's some priviledge issues
[22:20] <seb128> tjaalton: not really, ask pitti rather when he's around tomorrow
[22:22] <tjaalton> seb128: ok cool, I will
[23:01] <ubotu> New bug: #190729 in compiz (main) "the composite extension it's not available after instal ati restricted driver (dup-of: 173663)" [Medium,New] https://launchpad.net/bugs/190729
[23:25] <ubotu> New bug: #190799 in xorg (main) ""additional startup programs" crash xserver" [Medium,New] https://launchpad.net/bugs/190799
[23:46] <ubotu> New bug: #191989 in xorg (main) "Losing access to system option in low screen resolution" [Undecided,New] https://launchpad.net/bugs/191989


 "Ironic really, here I am testing..." <- Maybe something keeps reporting a state. I have no idea what I'm talking about but I would like to hear what it was
[00:38] <karmavil[m]> And if it's summer for you, please 🙏 enjoy your weekend 😊


[00:22] <ubptgbot> tiedtoastar was added by: tiedtoastar
[00:40] <ubptgbot> mohammed_garmiany was added by: mohammed_garmiany
 marius stream did good, now i know bit more what qtubuntu-camera is
 [Edit] marius stream did me good, now i know bit more what qtubuntu-camera is
[03:49] <ubptgbot> <Krish g> I might make my self unpopular right but but I kinda Wana know why ubports needs a phone restart to update when Linux computers do not?
[05:15] <yjftsjthsd> ubports updates by switching to a new read-only filesystem image, doesn't it?
[05:15] <yjftsjthsd> same deal as chromebooks
[05:15] <yjftsjthsd> or fedora silverblue, if you're into that
[05:16] <yjftsjthsd> Normal systems update by writing updates into their read+write root filesystem; ubports isn't designed to allow such a thing
[05:57] <ubptgbot> Kevin Webbie was added by: Kevin Webbie
[06:41] <ubptgbot> hilledkinged was added by: hilledkinged
 Hi
[07:04] <ubptgbot> <X YZ> @hilledkinged [Hi], Hi and welcome to UBports. 😃
 @X YZ [Hi and welcome to UBports. 😃], Thx
[08:20] <ubptgbot> <E S> @YougoChats [<reply to media>], Hi Hugo, how do you like the new phone? Are you running Manjaro or UT? I am wondering what browser it has? Enjoy that beautiful piece of equipement
 @E S [Hi Hugo, how do you like the new phone? Are you running Manjaro or UT? I am wond …], It runs Postmarket OS internally, but currently UT from SD card. The browser on PMOS is firefox, but i dont know if it's the full firefox or limited somehow. The browser in UT is Morph ofcourse
 The phone itself feels solid. Phosh (PMOS's not-gnome shell) feels really awkward for me. Too many taps everywhere to get anywhere. But both PMOS and UT behave consistently well (quirks due to being unfinished notwithstanding)
[08:50] <ubptgbot> <E S> nice, how long was the shipping?
 I ordered it in juli expecting a long wait. Kept an eye on the forums about shipping announcements. About september 5 ish, news came that pinephones destined for europe were next up, and from 14. September mailings could go out. Sure enough, 14th i got a mail and 16th i got my phone. Travelled from china to poland to amsterdam to my pl
[08:55] <ubptgbot> ace in amazingly short time
 hm can I somehow launch jwm in a libertine container
[10:16] <ubptgbot> <Charlie Malkowski> Fwd from DavidMittag: Danke
 I answered my own question
 (Photo, 1080x1920) https://irc.ubports.com/r2OIgIIn.png
 now to figure out how to move files from ut to libertine
 got it
 Home directories are mounted in libertine as far as I know - Documents, Downloads, Music, etc
[11:41] <ubptgbot> Zoee 🦋 was added by: Zoee 🦋
 Does anyone know what happened to UBsync (formerly Owncloudsync)? It disappeared from the Openstore and the app stopped working, but it is extremely important for Nextcloud users.
 @ruedigerkupper [Does anyone know what happened to UBsync (formerly Owncloudsync)? It disappeared …], it's still in the store. but it's only built for armhf it looks like, so maybe ask the developer to also publish arm64 and amd64 builds
 Ah, yes, that will be it, I'm on the Xperia 64-bit channel.
 @ruedigerkupper [Does anyone know what happened to UBsync (formerly Owncloudsync)? It disappeared …], Does not ghostcloud give you what you need?
 No, Ghostcloud is good for on demand access, but UBsync does background synchronization with Nextcloud. The kind you have on apple products: sync your photos folder automatically, your documents, etc. Without you triggering it manually.
 Half of my daily and business routine depends on it ;-).
 @ruedigerkupper [Ah, yes, that will be it, I'm on the Xperia 64-bit channel.], https://t.me/UbuntuAppDevEN/43688
 Thanks a lot! But installation fails with "make sure this is a valid click package".
[17:56] <ubptgbot> elchalten was added by: elchalten
[18:29] <ubptgbot> Pedro Vicente was added by: Pedro Vicente
[18:29] <ubptgbot> originale404 was added by: originale404
[18:50] <ubptgbot> <X YZ> @ruedigerkupper [No, Ghostcloud is good for on demand access, but UBsync does background synchron …], Syncthing can do that, been running it for the last months on my Ubuntu PC and various Android mobiles. Seen it in the UT-store, too and will install and test it on my UT-phone in the next days, as so far I am very happy with it. Maybe you g
[18:50] <ubptgbot> ive it a try, too. 👍
 Is there GSI is available for OnePlus 7 pro
 [Edit] Is there GSI is available for OnePlus 7 pro??
 (Voice, 1s) https://irc.ubports.com/3eeFqR2P.oga
 Hi! Sorry to go back in time.  Is there an older version that is compatible with windows phone Lumia 950?  i want to bring my phone back to life with linux.  thank you in advance
 @LAURNITA [Hi! Sorry to go back in time.  Is there an older version that is compatible with …], Not rn
 (Photo, 1280x244) https://irc.ubports.com/XdgRrAAW.png I wanted to preorder the PinePhone Manjaro Edition, does someone also have problems with the shipping informatino (destination European Union) ?
 (Photo, 1280x244) https://irc.ubports.com/g0c7ySXh.png I wanted to preorder the PinePhone Manjaro Edition, does someone also have problems with the shipping information (destination European Union) ?
 (Sticker, 512x512) https://irc.ubports.com/oLwyxUN1.webp
[20:13] <ubptgbot> <Joan Singla> @a1300_developer [<reply to media>], I bought one to send to spain 2 days ago and I did not have any problem
[20:51] <ubptgbot> Wessel was added by: Wessel
[23:01] <ubptgbot> <Laurel Hescams> Hey folks! When I try to traceroute from the libertine container with root I get "lacking privilege for raw socket".. I don't even know how to begin to ask.


[15:48] <rbasak> Who can push to a git repo? The team owner, or the "repository reviewer", or both?
[15:48] <rbasak> Or something else?
[15:59] <cjwatson> rbasak: Just the owner of the repository, or anyone in that team if the repository owner is a team.  (Also currently Launchpad admins, but that's a bug.)
[15:59] <rbasak> That's useful. Works well for us. Thanks!
[16:00] <cjwatson> rbasak: Planned future change: the default repository for a source package in a distribution (i.e. lp:ubuntu/+source/PACKAGE) should be pushable-to by anyone who can upload to the corresponding source package; but that's not done yet.
[16:01] <rbasak> We don't want that - unless we can further filter that by ref wildcard.
[16:01] <rbasak> IOW, we want an uploader of a package to be able to push refs/tags/upload/*, but nothing else.
[16:01] <rbasak> And only the importer should be able to push refs/*
[16:02] <rbasak> Otherwise an uploader could cause the git repository to mismatch the archive's single source of truth
[16:02] <cjwatson> Ref-wildcard ACLs have long been planned though are also not yet implemented.
[16:03] <rbasak> Do you have a plan for us to be able to combine those two things though?
[16:03] <cjwatson> In general it sounds like we need a bit of an uplift in policy capabilities to match those requirements.
[16:03] <cjwatson> They aren't planned in a lot of detail.
[16:03] <rbasak> Understood, thanks
[16:04] <cjwatson> (If you need it any time soon you probably need to go through my management chain so I get some time ...)
[16:36] <nacc> cjwatson: did you have any further thoughts on where I could debug the JSONDecodeError I was hitting yesterday? I'm getting it pretty consistently now (and if i ignore it, the review does get requested correctly)
[16:42] <cjwatson> nacc: if it's returning an empty byte-string then that sounds like an LP bug; it might be worth seeing if you can construct a matching situation in the LP test suite
[16:42] <cjwatson> I don't see anything obviously wrong with that method
[16:43] <nacc> cjwatson: will do, thanks!
[16:44] <cjwatson> (sorry, I realise that's quite a big next step, but ...)
[16:44] <nacc> cjwatson: not a problem! I know you've got a lot on your plate -- I think for now I can handle that exception in our script and i'll note it down as a bug to follow-up on my end


[14:46] <FernandoMiguel> good afternoon
[15:51] <joelesko> micahg: chrisccoulson: Any progress on the seamonkey 2.5 code merge and release?
[16:27] <micahg> joelesko: sorry, the latest it should happen is monday when I'm piloting
[16:39] <joelesko> micahg: thanks


[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [amd64] (cosmic-proposed) [2.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [armhf] (cosmic-proposed) [2.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [ppc64el] (cosmic-proposed) [2.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [arm64] (cosmic-proposed) [2.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [s390x] (cosmic-proposed) [2.0.0-1]
[00:20] -queuebot:#ubuntu-release- New: accepted libcdio [i386] (cosmic-proposed) [2.0.0-1]
[04:58] -queuebot:#ubuntu-release- Unapproved: accepted pollinate [source] (artful-proposed) [4.33-0ubuntu1~17.10.1]
[04:59] -queuebot:#ubuntu-release- Unapproved: accepted pollinate [source] (xenial-proposed) [4.33-0ubuntu1~16.04.1]
[05:17] -queuebot:#ubuntu-release- Unapproved: accepted pollinate [source] (trusty-proposed) [4.33-0ubuntu1~14.04.1]
[06:43] <xnox> infinity, recall during sprint i said debootstrap/rsyslog is busted.
[06:43] <xnox> infinity, well, i believe it really is... in -proposed, hence debootstrap was failing to migrate as the default-bootstraps as called by livecd-rootfs autopkgtests is busted there.
[06:44] <xnox> infinity, would you be able to dig into that? or should I be spending time to investigate that?
[06:44] <xnox> looks like a regression since 1.0.95
[07:10] <cpaelzer> sil2100: I get the feeling that https://bileto.ubuntu.com/#/ticket/3293 is not running tests
[07:10] <cpaelzer> sil2100: anything we can do to investigate?
[07:35] <sil2100> cpaelzer: let me take a look
[07:36] <sil2100> ARGH
[07:36] <sil2100> Yeah, the usual unauthorized thing, let me take care of it
[07:37] <sil2100> cpaelzer: I poked webops to restart it, as that's the easiest way to get it fixed
[07:37] <sil2100> Need to investigate why it started turning into such a big problem recently, I don't remember it happening before
[07:39] <sil2100> cpaelzer: ok, let's see if the next run will be better
[07:43] <cpaelzer> sil2100: do I need to toggle the lander signoff
[07:43] <cpaelzer> off/on to retrigger?
[07:44] <sil2100> cpaelzer: no, it shouldn't be necessary
[07:44] <cpaelzer> sil2100: ok giving it an hour to recheck then
[07:45] <cpaelzer> queues on http://autopkgtest.ubuntu.com/running are empty
[07:45] <cpaelzer> would I see it there sil2100?
[07:45] <cpaelzer> under the ppa category
[07:46] <sil2100> Yes, but only after britney is done triggering the tests
[07:46] <cpaelzer> ok
[07:46] <sil2100> And the queues in the webview aren't updated automatically, there's always a delay
[07:46] <cpaelzer> good to know
[07:51] <sil2100> cpaelzer: done, tests actually already ran and passed
[07:51] <sil2100> cpaelzer: since the issue that bileto had was actually uploading the results to swift to display them
[07:54] <cpaelzer> oh I see
[07:55] <cpaelzer> so the perm issue is on the swift upload
[07:55] <cpaelzer> thank you sil2100!
[08:13] <sil2100> cpaelzer: yw! If I have some free time I'll try to think of a way of making sure the tokens don't get desync so often
[08:14] <sil2100> We don't do any work on Bileto now so it might get delayed
[08:17] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (bionic-proposed) [3.0.1-0ubuntu1~18.04.1]
[08:20] <cpaelzer> sil2100: low investement high gain, just bluntly restart it all 6 hours or sometihng like that
[08:43] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-24.26] (core, kernel)
[08:45] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-24.26] (core, kernel)
[08:46] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-24.26]
[08:46] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-24.26]
[08:50] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (bionic-proposed) [3.0.1-0ubuntu1~18.04.1]
[09:01] <tjaalton> how to trigger tests on the latest version of the package, instead of the version that had failed?
[09:01] <tjaalton> like this http://autopkgtest.ubuntu.com/packages/v/vtk7/cosmic/amd64
[09:02] <tjaalton> re-running tests for libglvnd runs it on the old vtk7
[09:08] <xnox> tjaalton, and one more package to triggered by with a newer version number, from e.g. proposed.
[09:08] <xnox> tjaalton, hack the retry url
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (bionic-proposed) [3.0.1-0ubuntu1~18.04.1]
[09:09] <xnox> note there are two vtk7 at the moment, one in proposed, another one in release pocket.
[09:09] <xnox> what you are saying is that libglvnd is broken against vtk7 in release pocket, but work against new one?
[09:09] <xnox> maybe libglvnd needs Depends: libvtk7 (>= new version) ? no?
[09:10] <xnox> tjaalton, cause you don't want libglvnd to migrate without libvtk7 into release pocket, and then regress in the release pocket, no?
[09:13] -queuebot:#ubuntu-release- Unapproved: rejected python-pylxd [source] (bionic-proposed) [2.2.6-0ubuntu1.1]
[09:15] <tjaalton> xnox: no, it's just vtk7 which is buggy
[09:15] <xnox> ah
[09:15] -queuebot:#ubuntu-release- Unapproved: accepted python-pylxd [source] (bionic-proposed) [2.2.6-0ubuntu1.1]
[09:15] <xnox> tjaalton, hack the url to include &package=vtk7/correctversion for the retry url of the libglvnd
[09:15] <tjaalton> looks like it needs some hand-holding to get through, depends on other packages
[09:15] <tjaalton> right, how to add '+' there?
[09:16] <xnox> urlencode
[09:16] -queuebot:#ubuntu-release- Unapproved: rejected swauth [source] (bionic-proposed) [1.3.0-1ubuntu1]
[09:18] <tjaalton> https://autopkgtest.ubuntu.com/request.cgi/?release=cosmic&arch=amd64&package=vtk7%2F7.1.1%2Bdfsg1-4build2&trigger=libglvnd%2F1.0.0%2Bgit20180308-3ubuntu1
[09:18] <tjaalton> doesn't seem to work
[09:18] <tjaalton> or I'm missing something
[09:19] <xnox> hu
[09:19] <xnox> tjaalton, package=thing to test & trigger=who & trigger=other
[09:20] <xnox> tjaalton, i think you want to run the test of libglvnd? no? then you should have package=libglvnd/version&trigger=libglvnd/version&trigger=vtk7/version
[09:20] <tjaalton> no
[09:20] <tjaalton> libglvnd doesn't have any tests
[09:20] <xnox> such that you run libglvnd, but triggered by two things - new libglvnd and new vtk7
[09:20] <xnox> oh
[09:21] <xnox> package vtk7/newversion & trigger=vtrk7/newversion & trigger=libglvnd/newversion ?
[09:21] <xnox> run vtk7 tests, whilst new vtk7 is installed and a new libglvnd installed
[09:21] <tjaalton> ok
[09:22] <tjaalton> nope, still the same
[09:22] <xnox> so what you pasted is good, but needs a second trigger for the right vtk7 as well as the package= stanza, so repeat that bit
[09:23] <xnox> package is without version number
[09:23] -queuebot:#ubuntu-release- Unapproved: accepted swauth [source] (bionic-proposed) [1.3.0-1ubuntu1]
[09:23] <tjaalton> it works without, not with
[09:23] <tjaalton> oh well, see how it goes
[09:24] <xnox> looks ok
[09:24] <xnox> http://autopkgtest.ubuntu.com/running#pkg-vtk7
[09:24] <xnox> Release:	cosmic
[09:24] <xnox> Architecture:	amd64
[09:24] <xnox> Triggers:	['vtk7/7.1.1+dfsg1-4build2', 'libglvnd/1.0.0+git20180308-3ubuntu1']
[09:24] <xnox> Requester:	tjaalton
[09:24] <xnox> Running for:	0h 0m 30s
[09:25] <tjaalton> alright, hope it passes this time
[09:25] <tjaalton> thanks
[09:26] -queuebot:#ubuntu-release- New binary: swauth [amd64] (bionic-proposed/universe) [1.3.0-1ubuntu1] (no packageset)
[09:29] -queuebot:#ubuntu-release- Unapproved: accepted fonts-guru-extra [source] (bionic-proposed) [2.0-4ubuntu0.1]
[09:31] -queuebot:#ubuntu-release- Unapproved: accepted swauth [source] (artful-proposed) [1.2.0-3ubuntu1]
[09:32] -queuebot:#ubuntu-release- Unapproved: rejected python-pylxd [source] (artful-proposed) [2.2.6-0ubuntu<IP_ADDRESS>]
[09:34] -queuebot:#ubuntu-release- New binary: swauth [amd64] (artful-proposed/universe) [1.2.0-3ubuntu1] (no packageset)
[11:58] -queuebot:#ubuntu-release- New source: libocxl (bionic-proposed/primary) [1.0.0-1~ubuntu18.04.0]
[13:41] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-ati-hwe-16.04 (xenial-proposed/main) [1:7.10.0-1~16.04.1 => 1:18.0.1-1~16.04.1] (no packageset)
[13:42] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-amdgpu-hwe-16.04 (xenial-proposed/main) [1.4.0-1~16.04.1 => 18.0.1-1~16.04.1] (no packageset)
[13:43] <tjaalton> sil2100: ^ some uploads for 16.04.5, and there's also libclc on the queue
[13:43] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-intel-hwe-16.04 (xenial-proposed/main) [2:2.99.917+git20170309-0ubuntu1~16.04.1 => 2:2.99.917+git20171229-1~16.04.1] (no packageset)
[13:56] <sil2100> tjaalton: thanks! On it
[14:00] -queuebot:#ubuntu-release- Unapproved: accepted libclc [source] (xenial-proposed) [0.2.0+git20180312-1~16.04.1]
[14:15] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-ati-hwe-16.04 [source] (xenial-proposed) [1:18.0.1-1~16.04.1]
[14:15] <sil2100> tjaalton: love those version leaps 1.4.0 -> 18.0.1
[14:19] <tjaalton> sil2100: they went for year.N
[14:20] <tjaalton> like mesa
[14:22] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-amdgpu-hwe-16.04 [source] (xenial-proposed) [18.0.1-1~16.04.1]
[14:27] -queuebot:#ubuntu-release- Unapproved: openipmi (bionic-proposed/main) [2.0.22-1.1ubuntu2 => 2.0.22-1.1ubuntu2.1] (ubuntu-server)
[14:33] -queuebot:#ubuntu-release- Unapproved: openipmi (artful-proposed/main) [2.0.22-1.1ubuntu1 => 2.0.22-1.1ubuntu1.1] (ubuntu-server)
[14:37] -queuebot:#ubuntu-release- Unapproved: openipmi (xenial-proposed/main) [2.0.18-0ubuntu11.1 => 2.0.18-0ubuntu11.2] (ubuntu-server)
[14:39] -queuebot:#ubuntu-release- Unapproved: cockpit (xenial-backports/universe) [169-1~ubuntu16.04.1 => 170-1~ubuntu16.04.1] (no packageset)
[14:40] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (xenial-backports) [170-1~ubuntu16.04.1]
[14:51] <ahasenack> hi all, I added dep8 tests to autofs package in my 5.1.2-3ubuntu2 upload
[14:51] <ahasenack> there were none before
[14:51] <ahasenack> they are all marked as "always failed" in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html, is that just a safe default for when tests are added?
[14:52] <ginggs> ahasenack: yes
[14:53] <ahasenack> can that please be changed to not ignore failures?
[14:53] <ahasenack> http://autopkgtest.ubuntu.com/packages/autofs
[15:01] <ginggs> ahasenack: after the tests have passed the first time, they have to keep passing
[15:01] <ahasenack> ginggs: ah, good, thanks
[15:12] <sil2100> tjaalton: I see the xserver-xorg-video-intel-hwe-16.04 package has dropped dri3info after the sync to Debian - won't that cause any problems, since it was an existing Ubuntu delta?
[15:13] <sil2100> s/sync to/sync from/
[15:26] <tjaalton> sil2100: I doubt it, it just says if dri3 is enabled
[15:27] <tjaalton> which should be, by default
[15:28] <sil2100> tjaalton: if that's the case then I guess I'll approve, but please have your eyes open for people whining for it being gone
[15:28] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-intel-hwe-16.04 [source] (xenial-proposed) [2:2.99.917+git20171229-1~16.04.1]
[15:28] <tjaalton> sure
[16:12] -queuebot:#ubuntu-release- Unapproved: xorg-server-hwe-16.04 (xenial-proposed/main) [2:1.19.5-0ubuntu2~16.04.1 => 2:1.19.6-1ubuntu4~16.04.1] (no packageset)
[16:13] <tjaalton> sil2100: the server, tested on nvidia by tseliot so that it doesn't regress, had to revert some things from it but it's fine
[16:13] <tjaalton> sil2100: ^
[16:14] <tjaalton> it's only mesa missing now
[16:14] <bdmurray> sil2100: How go the SRU reviews?
[16:16] -queuebot:#ubuntu-release- Unapproved: mesa (xenial-proposed/main) [17.2.8-0ubuntu0~16.04.1 => 18.0.5-0ubuntu0~16.04.1] (core, xorg)
[16:17] <tjaalton> sil2100: aand there's mesa
[16:53] <sil2100> bdmurray: I'm done for today, I'll just take care of the HWE things in xenial, e.g. mesa and xorg-server
[16:53] <sil2100> bdmurray: but all the others are yours o/
[16:54] <sil2100> tjaalton: thanks! On it, just need to grab a quick bite
[16:56] <bdmurray> sil2100: ack
[17:06] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server-hwe-16.04 [source] (xenial-proposed) [2:1.19.6-1ubuntu4~16.04.1]
[17:22] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (xenial-proposed) [18.0.5-0ubuntu0~16.04.1]
[17:25] <tjaalton> sil2100: \o/
[17:32] -queuebot:#ubuntu-release- New source: python-qinlingclient (cosmic-proposed/primary) [1.0.0-0ubuntu1]
[18:11] -queuebot:#ubuntu-release- New binary: python-vitrageclient [amd64] (cosmic-proposed/universe) [2.1.0-0ubuntu1] (no packageset)
[18:13] <bdmurray> sil2100: Could you review my upload of lsvpd for bionic?
[18:22] <sil2100> bdmurray: sure
[18:32] -queuebot:#ubuntu-release- Unapproved: accepted lsvpd [source] (bionic-proposed) [1.7.8-2ubuntu1.1]
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted gnome-online-accounts [source] (bionic-proposed) [3.28.0-0ubuntu2.1]
[20:43] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [<IP_ADDRESS>]
[20:46] -queuebot:#ubuntu-release- Unapproved: accepted im-config [source] (bionic-proposed) [0.34-1ubuntu1.2]
[21:41] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (bionic-proposed) [0.7.5-1ubuntu16.2]
[21:46] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (artful-proposed) [<IP_ADDRESS>-1ubuntu3.6]
[21:47] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (xenial-proposed) [<IP_ADDRESS>-0ubuntu23]
[21:58] -queuebot:#ubuntu-release- Unapproved: accepted gnocchi [source] (bionic-proposed) [4.2.4-0ubuntu1.1]
[22:02] -queuebot:#ubuntu-release- Unapproved: accepted heat [source] (bionic-proposed) [1:10.0.1-0ubuntu2]
[22:03] -queuebot:#ubuntu-release- Unapproved: accepted heat [source] (artful-proposed) [1:9.0.4-0ubuntu2]
[22:04] -queuebot:#ubuntu-release- Unapproved: accepted heat [source] (xenial-proposed) [1:6.1.2-0ubuntu1.1]
[22:57] -queuebot:#ubuntu-release- Unapproved: rejected debhelper [source] (artful-proposed) [10.7.2ubuntu3]
[22:57] -queuebot:#ubuntu-release- Unapproved: rejected debhelper [source] (bionic-proposed) [11.1.6ubuntu3]
[22:57] -queuebot:#ubuntu-release- Unapproved: rejected debhelper [source] (xenial-proposed) [9.20160115ubuntu4]
[23:00] -queuebot:#ubuntu-release- Unapproved: accepted iperf [source] (bionic-proposed) [2.0.10+dfsg1-1ubuntu<IP_ADDRESS>]
[23:02] -queuebot:#ubuntu-release- Unapproved: accepted iperf [source] (artful-proposed) [2.0.10+dfsg1-1ubuntu<IP_ADDRESS>]
[23:04] -queuebot:#ubuntu-release- Unapproved: accepted iperf [source] (xenial-proposed) [2.0.5+dfsg1-2ubuntu0.1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [<IP_ADDRESS>]
[23:11] -queuebot:#ubuntu-release- Unapproved: accepted fwts [source] (bionic-proposed) [18.03.00-0ubuntu2]
[23:18] -queuebot:#ubuntu-release- Unapproved: rejected ebtables [source] (bionic-proposed) [<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>]
[23:19] -queuebot:#ubuntu-release- Unapproved: rejected ebtables [source] (artful-proposed) [<IP_ADDRESS>-3.5ubuntu<IP_ADDRESS>]
[23:20] -queuebot:#ubuntu-release- Unapproved: rejected ebtables [source] (trusty-proposed) [<IP_ADDRESS>-3ubuntu<IP_ADDRESS>]
[23:20] -queuebot:#ubuntu-release- Unapproved: rejected ebtables [source] (xenial-proposed) [<IP_ADDRESS>-3.4ubuntu<IP_ADDRESS>]
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-default-settings [source] (bionic-proposed) [<IP_ADDRESS>]
[23:51] <rbasak> bdmurray: +1 on the queue rejects.
[23:52] <rbasak> I was leaving them there but really that just means every pass takes longer. And I'd seen them multiple times already.
[23:53] <bdmurray> rbasak: Yeah and it wasn't a good use of my time.
[23:54] -queuebot:#ubuntu-release- Unapproved: accepted skytools3 [source] (artful-proposed) [3.2.6-5ubuntu0.1]
[23:54] <rbasak> I was getting more reject happy nearer the end of my shift yesterday, but had already gone past those ones. Too much stuff languishing/blocked in the queues at the moment :-/
[23:55] -queuebot:#ubuntu-release- Unapproved: accepted skytools3 [source] (xenial-proposed) [3.2.6-4ubuntu0.1]