[10:08] <ouned> if i install ubuntu-gnome 16.10 nightly now, will it automatically the stable version after its release?
[10:16] <jbicha> ouned: yes
[10:22] <ouned> cool, thanks :)
[11:02] <darkxst> jbicha, hey, how is everything going?
[11:02] <jbicha> darkxst: winter fun over?
[11:02] <darkxst> no, lifts are closed, but I am still working up here
[11:03] <darkxst> and its dumping snow again
[11:05] <darkxst> first weekend off all winter ;) should atleast have some time now to do GNOME stuff again
[11:05] <jbicha> oh you got faster internet this weekend?
[11:06] <darkxst> lol if you call 3Mbps fast
[11:07] <msev--> https://imgur.com/dV3cHmC
[11:07] <msev--> Ubuntu gnome boot problem
[11:08] <mgedmin> 8 is ENOEXEC Exec format error
[11:08] <darkxst> msev--, Ubuntu boot problem, we share the same kernel
[11:09] <mgedmin> "runaway loop modprobe binfmt-464c"
[11:09] <mgedmin> did you self-compile this kernel?
[11:09] <msev--> How do i fix this
[11:10] <jbicha> darkxst: :( the Ubuntu isos grew a bit this cycle
[11:10] <darkxst> jbicha, I noticed, 1.4GB took a long time to download
[11:11] <mgedmin> msev--: https://help.ubuntu.com/community/Boot-Repair is perhaps worth a try
[11:13] <darkxst> jbicha, I'm in the office full time now, so should be able to download stuff there
[11:14] <darkxst>  going forward
[11:15] <jbicha> our iso is still smaller than Ubuntu (Unity)'s and they still intend to add Unity8 at the last minute to their iso
[11:16] <jbicha> did you see my mention in the release notes that we might end up shipping Qt again (maybe for 17.04)?
[11:16] <jbicha> https://wiki.ubuntu.com/YakketyYak/Beta2/UbuntuGNOME
[11:19] <msev--> i will try to run fix boot
[11:20] <mgedmin> google also suggets that binfmt-464c problem may be trying to boot a 32-bit kernel with a 64-bit userspace
[11:21] <msev--> Weird i think i installed the 64biy variant
[11:21] <mgedmin> did it boot before?
[11:21] <mgedmin> when did your troubles start?
[11:24] <darkxst> jbicha, the whole qt thing was more about accessibility than themes
[11:25] <darkxst> but really wtf? someone ported Adwaita to QT?
[11:25] <jbicha> Fedora ships it by default
[11:26] <jbicha> so I guess it doesn't matter that Ubuntu GNOME shipped Qt since Fedora (GNOME) does too now
[11:31] <darkxst> yeh ok, size doesnt matter too much!
[11:33] <darkxst> says me who has been stuck on shit internet all winter
[11:34] <msev--> Mgedmjn no it didnt boot before
[11:35] <msev--> Cool i did the boot repair and now it does
[11:36] <mgedmin> are you saying the ubuntu installer left you with a non-booting system?
[11:37] <msev--> Yes
[11:37] <msev--> Ubuntu gnome 16.04
[11:37] <mgedmin> very strange
[11:37] <msev--> I had to boot with a usb key and run there the boot repair
[11:38] <msev--> Now it seems to work
[11:53] <darkxst> jbicha, copped a kernel panick after install of yak daily
[11:53] <darkxst> but was ok on reboot
[11:55] <jbicha> I don't know anything about kernel/boot issues
[12:25] <darkxst> jbicha, I assume it happened on reboot after install but didnt really pay attention
[15:01] <gebruiker> how much memory is requried to run GNOME?
[16:10] <msev--> if i'm using a bouncer how do i set up the password for it in polari?
[16:16] <jbicha> msev--: do you mean just identify to NickServ?
[16:18] <msev--> no
[16:19] <jbicha> Polari is a fairly minimal irc client so I'm guessing it doesn't actually do that
[16:20] <jbicha> you can try asking in #polari on irc.gnome.org though
[16:21] <msev--> i'm doing that just now :)
[22:29] <jbicha> ricotz: it looks like the LO updates have been accepted into yakkety now
[23:06] <ricotz> jbicha, oh, thanks for the info


[13:06] <jdstrand> fta2: thanks, it looks like something in gnome libraries changed
[13:07] <jdstrand> fta2: I say it with some other gnome apps as well
[13:45] <fta2> jdstrand, what is status "m"?
[13:45] <jdstrand> allow PROT_EXEC with mmap(2) calls
[13:45] <fta2> oh, ok
[13:45] <jdstrand> it is the multiarch stuff added to eglibc
[13:45] <jdstrand> I am working on it now (new in ubuntu6)
[16:15] <micahg> chrisccoulson, with multiarch landing, can we build plugin-container as a separate i386 package?
[16:15] <chrisccoulson> micahg - i think it's probably more complicated than that
[16:22] <micahg> chrisccoulson, after the comments in -devel, I don't see it happening this cycle, but maybe next time :)
[16:49] <fta> dpm, uhuh, 16144 strings from lp landed upstream
[16:49] <fta> dpm, for 26 langs: http://paste.ubuntu.com/581679/
[16:50] <dpm> 16K ??? we should blog about it!!
[16:50] <dpm> that's excellent!
[16:51] <fta> i will write something, hoping to boost the other 30 langs ;)
[16:53] <dpm> brilliant
[16:53] <dpm> I'll see if I do a quick one as well
[16:54] <fta> i will also explain how other dists could enable those
[16:54] <fta> as it's only a subset of the strings lp collected
[17:03] <micahg> chrisccoulson, bug 736847, seems like the dir path for xulrunner isn't following the 1.x.x pattern
[17:03] <ubot2> Launchpad bug 736847 in couchdb "/usr/bin/couchjs crashes with /usr/lib/xulrunner-2.0/ libmozjs.so dir" [Undecided,New] https://launchpad.net/bugs/736847
[17:04] <chrisccoulson> oops
[17:04] <chrisccoulson> heh
[17:04] <chrisccoulson> there will be a few more like that
[17:11] <m_conley> chrisccoulson: ping
[17:11] <chrisccoulson> hi m_conley
[17:11] <chrisccoulson> i'm doing it now ;)
[17:12] <m_conley> chrisccoulson: took the words right out of my mouth.  :)
[17:12] <m_conley> chrisccoulson: thanks!
[17:12] <chrisccoulson> heh
[17:12] <chrisccoulson> m_conley, do you know if thunderbird is going to be adopting a release process similar to firefox? ;)
[17:13] <m_conley> chrisccoulson: hm - not sure if we're doing the short release cycle.  I know we're going to have to modify the way we do builds to work off the right mozilla-central branches though.
[17:13] <m_conley> chrisccoulson: all arcane build stuff that's probably driving our build engineers a little batty.  :)
[17:13] <chrisccoulson> yeah, i was trying to think how it would work
[17:14] <fta> chrisccoulson, what will be the default emailer in natty? evo or tb?
[17:15] <chrisccoulson> fta - oh, for natty, it's still evo. it's far too late in the cycle to change the default mail client ;)
[17:15] <fta> ok
[17:16] <fta> i don't mind either way. but i use evo, and i find its support in ubuntu is close to zero, and upstream is, well, not very receptive
[17:16] <chrisccoulson> yeah, i find that too
[17:59] <m_conley> fta: I'm working hard at making TB work nicely with Ubuntu.  Not in time for Natty, unfortunately, but soon!
[19:48] <fta> micahg, jdstrand:  linux/stable (10.0.648.134 -> 10.0.648.151)
[20:22] <fta> jdstrand, how come i need to build with -fPIC on maverick but not on natty when i use PIE?
[20:34] <jdstrand> fta: not sure. you might ask kees-- he is way more familiar with this than I
[20:36] <fta> ok, i will, next occasion. enough crashes & ftbfs for today for me
[20:37] <fta> jcastro, btw, i have the bug <soreau> talked about (empty wallpaper with just a cursor)
[20:38] <jcastro> fta: any idea where it is in launchpad?
[20:39] <fta> jcastro, i mentioned it in u-d a few hours ago, i've been ignored. i mentioned it weeks ago to didrocks, he said it's known but noone is able to reproduce it, pitti confirmed
[20:39] <fta> it happens to me very often
[20:39] <fta> each reboot, and most re-login
[20:39] <fta> but each time, the crash file is almost empty
[20:40] <micahg> fta, ACK
[20:41] <fta> micahg, seems to be just about blacklisted https certs
[20:41] <micahg> fta, yeah, I'm not sure if we want to do an upload just for that, but I'll check with jdstrand
[20:42] <fta> micahg, i need to ship the arm fix for the SIGILL on some board
[20:42] <fta> +s
[20:43] <micahg> fta, ah, hmm, ok, still don't know if that's worth pushing an upgrade to everyone
[20:43]  * micahg -> brb 15 min
[20:51] <fta> jcastro, if you find a bug # for this particular issue, please Cc me to it. it's really annoying
[20:51] <fta> i just see a sig 11, but no crash file or log of any kind :(
[20:52] <jcastro> If I see it
[20:52] <jcastro> I don't get crashers, I only get the occasional invisible box of death
[20:54] <fta> i get it on my 2 main desktops
[20:54] <fta> 32 and 64
[21:12] <micahg> fta, so, the chromium update doesn't look like something we'd want to push through -security, you're free to push through -proposed, -updates if you like (target {lucid,maverick}-proposed),  otherwise, you can just upload to natty, or skip it
[21:13] <fta> well, skipping is fine for me, it's just feeding the chrome is more up-to-date trolls
[21:14] <micahg> yeah, well, we can't push through every feel good release through -security, we don't do it for firefox/thunderbird either (case in point TB 3.1.9 wasn't pushed)
[21:15] <fta> the stable ppa will have it anyway, and at each release, it's getting more subscribers; those who can't wait the few days of the QA checks
[21:15] <micahg> fta, thanks for the heads up though!
[21:15]  * micahg needs to push thunderbird to thunderbird-stable....
[23:16] <loltoad> Hi!, when i dump the cookies.sqlite, i don't get all of the cookies i can see in the browser's cookie manager. I belive these are session cookies... how do i extract all of them?


[00:01] <gojko> and keep it running that way?
[00:01] <diogenes_> nope, first try and see if there's sound with the live session
[00:02] <gojko> but if there isn't
[00:03] <diogenes_> if there isn't then yous hould take the spets on troubleshooting it
[00:03] <diogenes_> steps*
[00:05] <gojko> also pulse audio keeps change my port from headphones to line out
[00:05] <gojko> manjaro shows that they are unplugged
[00:06] <diogenes_> try 16.04 in live and we'll see
[00:07] <gojko> I can't remember but i think I tried that I now i tried ubuntu 16.04 and it didn't work
[00:08] <diogenes_> there are stages, 16.04.1 16.04.2 and so on
[00:09] <diogenes_> thye all come with improvements
[00:09] <diogenes_> so try the latest in live
[00:10] <gojko> all of my distros were downloaded in last couple of days
[00:10] <gojko> so they are fresh as can be
[00:11] <diogenes_> well if you want to troubleshoot then install the latest 16.04, update to the latest packages afterwards we could try to troubleshoot it, but tomorrow
[00:14] <gojko> yes of course man thanks a lot, thanks for the effort, :)
[00:14] <diogenes_> np
[00:14] <gojko> and keep up the good work :)
[00:14] <diogenes_> hehe ok
[01:32] <uribecesar> ok
[13:26] <rootme> how to install google chrome
[13:27] <rootme> please help me
[13:27] <diogenes_> where is hi?>
[13:27] <rootme> hi
[13:27] <diogenes_> hi
[13:27] <diogenes_> can I help you?
[13:27] <rootme> hi man please help to install google chrome
[13:28] <rootme> in ubuntu mate
[13:28] <diogenes_> click here
[13:28] <diogenes_> https://www.google.com/chrome/browser/desktop/index.html
[13:29] <rootme> okay thank you man
[13:29] <diogenes_> you're welcome Mr. Gentleman
[13:30] <rootme> my browser is cracking please help me
[13:30] <diogenes_> is it the second question? is there a commenction between the two?
[13:30] <diogenes_> connection*
[13:31] <rootme> yeah
[13:31] <diogenes_> I've got an idea
[13:31] <diogenes_> let's deal with one at a time
[13:31] <rootme> tell me
[13:31] <rootme> what to do
[13:32] <diogenes_> what you want to do
[13:32] <rootme> please
[13:32] <diogenes_> first you have to determine what you want to do
[13:33] <rootme> "my firefox browaers
[13:33] <diogenes_> your firefox browsers? you have several?
[13:33] <rootme> it is crashing
[13:34] <diogenes_> ok, one more time, try to figure out what is your real problem and try to explain it in the most eloquent way possible
[16:21] <raspi_> bonjour a tous je vient de m'acquerir le raspi pi3 avec ecran 3.5 pouce mais je n'arrive pas a avoir le tactile je ne connait en rien les programmes unpeu d'aide svp
[19:18] <angel_> hola
[19:33] <angel_> :
[19:33] <angel_> :)
[19:39] <alkisg> halo :)
[19:39] <TaZeR> greetings my beautiful ubuntu mate angels
[19:58] <angel_> deseo hacer una pregunta como instalo aplicaciones de windows en linux
[19:58] <angel_> ya que solo necesito el office, desafortunadamente
[19:59] <diogenes_> angel_, in terminalo: sudo apt install wine
[19:59] <angel_> se que WINE o PlayOneLinux
[20:00] <angel_> ok pero wine hasta que office me soporta
[20:00] <angel_> el 2013 o el 2010
[20:00] <diogenes_> 2010
[20:01] <angel_> ok
[20:01] <angel_> muchas gracias
[20:01] <angel_> otra consulta
[20:02] <diogenes_> ok
[20:02] <angel_> al instalar wine, solo es  dar doble clic en el ejecutable
[20:02] <diogenes_> si
[20:02] <angel_> nada mas? o debo instalar algo desde consola ?
[20:03] <diogenes_> angel_, https://superuser.com/questions/866833/microsoft-office-2010-along-with-a-language-pack-using-wine
[20:04] <angel_> agradesco mucha su colaboracion
[20:04] <diogenes_> ok


[12:57] <mparillo> Looks like they re-spun the II isos: http://iso.qa.ubuntu.com/qatracker/milestones/428/builds/238229/testcases
[19:22] <RikMills> can anyone do release notes based on the beat ones? I am a bit stuck for time
[19:22] <RikMills> *beta
[23:21] <mparillo> Beta cloned to https://wiki.ubuntu.com/ImpishIndri/ReleaseNotes/Kubuntu
[23:21] <mparillo> I will start editing.


[02:15] -queuebot:#ubuntu-release- New binary: linux [armhf] (bionic-proposed/main) [4.15.0-9.10] (core, kernel)
[05:13] -queuebot:#ubuntu-release- New binary: golang-gopkg-juju-environschema.v1 [amd64] (bionic-proposed/universe) [0.0~git20151104.7359fc7-4] (no packageset)
[07:10] -queuebot:#ubuntu-release- New: accepted golang-gopkg-juju-environschema.v1 [amd64] (bionic-proposed) [0.0~git20151104.7359fc7-4]
[07:11] -queuebot:#ubuntu-release- New: accepted golang-github-k0kubun-pp [amd64] (bionic-proposed) [2.3.0-2]
[07:24] -queuebot:#ubuntu-release- New: accepted golang-github-gobuffalo-envy [amd64] (bionic-proposed) [1.3.0+git20180205.bac51f7-1]
[07:27] -queuebot:#ubuntu-release- New: accepted golang-github-valyala-fasttemplate [amd64] (bionic-proposed) [0.0~git20170224.0.dcecefd+dfsg-2]
[07:27] -queuebot:#ubuntu-release- New: accepted siridb-connector [amd64] (bionic-proposed) [2.0.5-1]
[07:27] -queuebot:#ubuntu-release- New: accepted mallard-ducktype [amd64] (bionic-proposed) [0.3-1]
[07:28] -queuebot:#ubuntu-release- New: accepted libweb-api-perl [amd64] (bionic-proposed) [2.2.3-1]
[08:27] -queuebot:#ubuntu-release- New binary: golang-gopkg-macaroon-bakery.v2 [amd64] (bionic-proposed/universe) [0.0~git20171221.21d9e9a-4] (no packageset)
[09:28] -queuebot:#ubuntu-release- New binary: libmail-chimp3-perl [amd64] (bionic-proposed/universe) [0.04-1] (no packageset)
[09:36] -queuebot:#ubuntu-release- New: accepted golang-gopkg-macaroon-bakery.v2 [amd64] (bionic-proposed) [0.0~git20171221.21d9e9a-4]
[09:36] -queuebot:#ubuntu-release- New: accepted libmail-chimp3-perl [amd64] (bionic-proposed) [0.04-1]
[11:31] <xnox> uploading gridsite, to hopefully get gdbm to migrate.....
[11:33] <ginggs> fingers crossed
[11:33] -queuebot:#ubuntu-release- New binary: gridsite [s390x] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:34] -queuebot:#ubuntu-release- New binary: gridsite [ppc64el] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New binary: gridsite [arm64] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: gridsite [armhf] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: gridsite [amd64] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: gridsite [i386] (bionic-proposed/universe) [3.0.0~20170225gitd51b2fd-2ubuntu1] (no packageset)
[11:58] <xnox> apw, slangasek, infinity  ^ should unblock gdbm transition
[12:02] <oSoMoN> sil2100, hey, would you have some time to look at the libreoffice 1:5.4.4-0ubuntu<IP_ADDRESS> SRU in the artful queue?
[12:04] <sil2100> oSoMoN: hey! I'll try, my SRU shift yesterday was a bit busy so I didn't manage to get to it
[12:04] <sil2100> If not I'll take care of it on my Monday shift for sure
[12:08] <oSoMoN> sil2100, great, thanks! Monday is fine
[12:23] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-113.136~14.04.1] (kernel)
[12:38] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-113.136~14.04.1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [amd64] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [armhf] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [ppc64el] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [arm64] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [s390x] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[12:42] -queuebot:#ubuntu-release- New: accepted gridsite [i386] (bionic-proposed) [3.0.0~20170225gitd51b2fd-2ubuntu1]
[13:02] -queuebot:#ubuntu-release- New source: gcc-8-cross-ports (bionic-proposed/primary) [1ubuntu1]
[13:02] -queuebot:#ubuntu-release- New: accepted gcc-8-cross-ports [source] (bionic-proposed) [1ubuntu1]
[13:03] -queuebot:#ubuntu-release- New: accepted linux [amd64] (bionic-proposed) [4.15.0-9.10]
[13:03] -queuebot:#ubuntu-release- New: accepted linux [armhf] (bionic-proposed) [4.15.0-9.10]
[13:03] -queuebot:#ubuntu-release- New: accepted linux [arm64] (bionic-proposed) [4.15.0-9.10]
[13:03] -queuebot:#ubuntu-release- New: accepted linux [i386] (bionic-proposed) [4.15.0-9.10]
[13:45] -queuebot:#ubuntu-release- New binary: gcc-8-cross-ports [ppc64el] (bionic-proposed/universe) [1ubuntu1] (no packageset)
[14:49] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-9.10] (core, kernel)
[15:18] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-9.10]
[15:30] <xnox> slangasek, i fixed gridsite that used to be flagged up by your hint to migrate gdbm. now iI am failing to undersntand the output form britney. It has "recur:" line.
[15:30] <xnox> more things to hint together?
[15:31] <xnox> e.g. gridsite does depend on apache2 canl-c gsoap -> so maybe these need to be added into the fix?
[15:31] <xnox> e.g. gridsite does depend on apache2 canl-c gsoap -> so maybe these need to be added into the mix?
[16:35] -queuebot:#ubuntu-release- Unapproved: bamf (xenial-proposed/main) [0.5.3~bzr0+16.04.20180207-0ubuntu1 => 0.5.3~bzr0+16.04.20180209-0ubuntu1] (ubuntu-desktop) (sync)
[16:35] -queuebot:#ubuntu-release- Unapproved: libunity (xenial-proposed/main) [7.1.4+16.04.20180207-0ubuntu1 => 7.1.4+16.04.20180209.1-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[16:35] -queuebot:#ubuntu-release- New: rejected gcc-8-cross-ports [ppc64el] (bionic-proposed) [1ubuntu1]
[16:37] <Trevinho> sil2100: hey... You might sync again https://bileto.ubuntu.com/#/ticket/3133 (only libunity is needed in fact, I wrongly rebuilt both), as I introduced a typo which I fixed.
[17:07] -queuebot:#ubuntu-release- Unapproved: accepted juju-core [source] (xenial-proposed) [2.3.2-0ubuntu<IP_ADDRESS>]
[17:14] -queuebot:#ubuntu-release- New binary: ignition-transport [ppc64el] (bionic-proposed/universe) [4.0.0+dfsg-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: pinentry [s390x] (bionic-proposed/main) [1.1.0-1] (core)
[17:14] -queuebot:#ubuntu-release- New binary: ignition-transport [s390x] (bionic-proposed/universe) [4.0.0+dfsg-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: e2fsprogs [s390x] (bionic-proposed/main) [1.43.9-1] (core)
[17:15] -queuebot:#ubuntu-release- New binary: e2fsprogs [ppc64el] (bionic-proposed/main) [1.43.9-1] (core)
[17:15] -queuebot:#ubuntu-release- New binary: sac2mseed [s390x] (bionic-proposed/none) [1.12+ds1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: mseed2sac [s390x] (bionic-proposed/none) [2.2+ds1-1] (no packageset)
[17:16] <sil2100> Trevinho: ok, I'll accept both since otherwise Bileto might be confused + there will be an archive!=bzr mismatch
[17:16] <Trevinho> sil2100: yeah, I was thinking the same...
[17:17] <Trevinho> sil2100: if you can get back the previous deb to ppa is fine, otherwsie do it for both
[17:17] <sil2100> Trevinho: (no haste, but I guess it would be nice if you did the same for artful bamf - if the same typo was there as well)
[17:17] -queuebot:#ubuntu-release- New binary: e2fsprogs [i386] (bionic-proposed/main) [1.43.9-1] (core)
[17:17] -queuebot:#ubuntu-release- New binary: pinentry [ppc64el] (bionic-proposed/main) [1.1.0-1] (core)
[17:17] -queuebot:#ubuntu-release- New binary: pinentry [amd64] (bionic-proposed/main) [1.1.0-1] (core)
[17:17] <Trevinho> sil2100: no it was in libunity
[17:17] -queuebot:#ubuntu-release- New binary: pinentry [armhf] (bionic-proposed/main) [1.1.0-1] (core)
[17:18] -queuebot:#ubuntu-release- New binary: pinentry [i386] (bionic-proposed/main) [1.1.0-1] (core)
[17:18] <sil2100> Trevinho: ah, indeed, we didn't do libunity for artful
[17:18] <sil2100> All good then
[17:19] -queuebot:#ubuntu-release- New binary: pinentry [arm64] (bionic-proposed/main) [1.1.0-1] (core)
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted bamf [sync] (xenial-proposed) [0.5.3~bzr0+16.04.20180209-0ubuntu1]
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted libunity [sync] (xenial-proposed) [7.1.4+16.04.20180209.1-0ubuntu1]
[17:20] <sil2100> Trevinho: done
[17:21] <slangasek> xnox: my hint going invalid should hopefully not prevent britney from dtrt, the hint was more for me to get a closer look at the nature of any blockers
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [amd64] (bionic-proposed) [1.1.0-1]
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [armhf] (bionic-proposed) [1.1.0-1]
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [ppc64el] (bionic-proposed) [1.1.0-1]
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [arm64] (bionic-proposed) [1.1.0-1]
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [s390x] (bionic-proposed) [1.1.0-1]
[17:21] -queuebot:#ubuntu-release- New: accepted pinentry [i386] (bionic-proposed) [1.1.0-1]
[17:24] -queuebot:#ubuntu-release- New binary: e2fsprogs [amd64] (bionic-proposed/main) [1.43.9-1] (core)
[17:24] -queuebot:#ubuntu-release- New binary: e2fsprogs [armhf] (bionic-proposed/main) [1.43.9-1] (core)
[17:24] -queuebot:#ubuntu-release- New binary: e2fsprogs [arm64] (bionic-proposed/main) [1.43.9-1] (core)
[17:24] -queuebot:#ubuntu-release- Unapproved: lttng-modules (artful-proposed/universe) [2.9.0-1ubuntu3 => 2.9.0-1ubuntu3.1] (no packageset)
[17:25] -queuebot:#ubuntu-release- Unapproved: lttng-modules (xenial-proposed/universe) [2.8.0-1ubuntu1~16.04.3 => 2.8.0-1ubuntu1~16.04.4] (no packageset)
[17:28] <tsimonq2> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668722
[17:29] <tsimonq2> This is currently breaking Lubuntu Next
[17:29] <tsimonq2> We can work around it by manually hacking $XDG_CONFIG_DIRS
[17:29] <tsimonq2> But I'm not sure how to raise attention to it otherwise
[17:30] <tsimonq2> I mean, I could *try* to muck around with it, but I don't knoe the X stack well
[17:30] <tsimonq2> infinity: ^
[17:31] <tsimonq2> s/knoe/know/
[17:37] -queuebot:#ubuntu-release- New binary: ignition-transport [armhf] (bionic-proposed/universe) [4.0.0+dfsg-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: ignition-transport [arm64] (bionic-proposed/universe) [4.0.0+dfsg-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: mseed2sac [ppc64el] (bionic-proposed/universe) [2.2+ds1-1] (no packageset)
[17:45] -queuebot:#ubuntu-release- New binary: sac2mseed [ppc64el] (bionic-proposed/universe) [1.12+ds1-1] (no packageset)
[17:48] <slangasek> http://autopkgtest.ubuntu.com/packages/b/botch/bionic/amd64 lolwut
[17:49] <slangasek> so which of dpkg, glibc, or python3-stdlib-extensions/3.6.4-3 broke botch's dot output
[17:52] <slangasek> ah, there's a graphviz update hidden in there, lovely
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [amd64] (bionic-proposed) [1.43.9-1]
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [armhf] (bionic-proposed) [1.43.9-1]
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [ppc64el] (bionic-proposed) [1.43.9-1]
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [arm64] (bionic-proposed) [1.43.9-1]
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [s390x] (bionic-proposed) [1.43.9-1]
[17:53] -queuebot:#ubuntu-release- New: accepted e2fsprogs [i386] (bionic-proposed) [1.43.9-1]
[17:54] -queuebot:#ubuntu-release- New binary: ignition-transport [amd64] (bionic-proposed/universe) [4.0.0+dfsg-1] (no packageset)
[17:55] -queuebot:#ubuntu-release- New binary: lava-dispatcher [amd64] (bionic-proposed/universe) [2018.2-1] (no packageset)
[17:56] -queuebot:#ubuntu-release- New: accepted ignition-transport [amd64] (bionic-proposed) [4.0.0+dfsg-1]
[17:56] -queuebot:#ubuntu-release- New: accepted ignition-transport [armhf] (bionic-proposed) [4.0.0+dfsg-1]
[17:56] -queuebot:#ubuntu-release- New: accepted ignition-transport [s390x] (bionic-proposed) [4.0.0+dfsg-1]
[17:56] -queuebot:#ubuntu-release- New: accepted ignition-transport [arm64] (bionic-proposed) [4.0.0+dfsg-1]
[17:56] -queuebot:#ubuntu-release- New: accepted lava-dispatcher [amd64] (bionic-proposed) [2018.2-1]
[17:56] -queuebot:#ubuntu-release- New: accepted ignition-transport [ppc64el] (bionic-proposed) [4.0.0+dfsg-1]
[17:57] -queuebot:#ubuntu-release- New binary: mseed2sac [arm64] (bionic-proposed/universe) [2.2+ds1-1] (no packageset)
[17:59] <slangasek> xnox: hmm, so gridsite doesn't appear anywhere in the output of my gdbm hint? https://paste.ubuntu.com/26547247/
[17:59] -queuebot:#ubuntu-release- New binary: mseed2sac [armhf] (bionic-proposed/universe) [2.2+ds1-1] (no packageset)
[18:00] -queuebot:#ubuntu-release- New binary: sac2mseed [armhf] (bionic-proposed/universe) [1.12+ds1-1] (no packageset)
[18:00] <slangasek> xnox: ah, and what in gdbm breaks virtualbox?  virtualbox says it only needs an updated gsoap, not gdbm, so can we untangle those?
[18:01] -queuebot:#ubuntu-release- New binary: sac2mseed [arm64] (bionic-proposed/universe) [1.12+ds1-1] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: mseed2sac [amd64] (bionic-proposed/universe) [2.2+ds1-1] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: ddupdate [amd64] (bionic-proposed/universe) [0.5.3-1] (no packageset)
[18:05] -queuebot:#ubuntu-release- New binary: sac2mseed [i386] (bionic-proposed/universe) [1.12+ds1-1] (no packageset)
[18:06] -queuebot:#ubuntu-release- New binary: mseed2sac [i386] (bionic-proposed/universe) [2.2+ds1-1] (no packageset)
[18:06] -queuebot:#ubuntu-release- New binary: sac2mseed [amd64] (bionic-proposed/universe) [1.12+ds1-1] (no packageset)
[18:06] <slangasek> xnox: aha, I think I need to add python3-defaults to the hint
[18:07] <slangasek> xnox: (update_output shows a bunch of a bunch of unrelated packages being pulled in while considering the hint, because they don't *increase* the uninstallable count; and then python3-defaults is considered, which does decrease the uninstallable count but not by as much as it would have if virtualbox hadn't been pulled in first)
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [amd64] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [armhf] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [ppc64el] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [amd64] (bionic-proposed) [1.12+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [armhf] (bionic-proposed) [1.12+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [ppc64el] (bionic-proposed) [1.12+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [arm64] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [s390x] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [i386] (bionic-proposed) [1.12+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted mseed2sac [i386] (bionic-proposed) [2.2+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [s390x] (bionic-proposed) [1.12+ds1-1]
[18:17] -queuebot:#ubuntu-release- New: accepted sac2mseed [arm64] (bionic-proposed) [1.12+ds1-1]
[18:18] -queuebot:#ubuntu-release- New: accepted ddupdate [amd64] (bionic-proposed) [0.5.3-1]
[18:30] <doko> slangasek: python3-defaults, python3.6 and python3-stdlib-extensions need to go in together, which are tied to gdbm
[19:17] -queuebot:#ubuntu-release- Unapproved: grub2 (artful-proposed/main) [2.02~beta3-4ubuntu7.1 => 2.02~beta3-4ubuntu7.2] (core)
[19:24] -queuebot:#ubuntu-release- Unapproved: grub2-signed (artful-proposed/main) [1.85.1 => 1.85.2] (core)
[19:27] <slangasek> doko: indeed, and my hint would've taken effect now except that there are new versions of ifmail and pike7.8 that were just accepted (no thanks to the previous versions having ~build1 version numbers to allow them to be autosynced over)
[19:52] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.17 => 2.02~beta2-36ubuntu3.18] (core)
[19:54] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.17 => 1.66.18] (core)
[20:00] <juliank> The util-linux SRU for xenial (bug 1722313) is looking good. The autopkgtest regressions all come from s390x suddenly having machine-level isolation. There are some more regressions on artful, but they might have been caused by it too.
[20:02] <juliank> I have another SRU for xenial pending in the unapproved queue for bug 1732865, so I'd appreciate if we could get that one released and mine in :-)
[20:03] <slangasek> juliank: do you want to throw me an MP for lp:~ubuntu-sru/britney/hints-ubuntu-xenial to document the s390x regressions with rationale?
[20:04] <slangasek> juliank: and it's friday, so no SRU release until Monday; but I'm happy to help get it ready-for-release
[20:04] <juliank> ugh, friday
[20:04] <juliank> I forgot :)
[20:06] <juliank> slangasek: So force-badtest <foo>/s390x/all?
[20:06]  * juliank no friend of britney
[20:07] <slangasek> juliank: preferably a version encoded instead of 'all', though for stable releases it normally won't make a big difference
[20:07] <juliank> because there are linux-raspi2/armhf/all, so that seems like it could work :)
[20:08]  * juliank tries
[20:09] <slangasek> juliank: also, knowing if the packages in question already have matching badtest hints in lp:~ubuntu-release/britney/hints-ubuntu/ is likely interesting
[20:09] <juliank> I'm not sure they fail in bionic
[20:09] <juliank> It seems unlikely, given that util-linux from yesterday migrated.
[20:10] <slangasek> but it may have migrated in bionic /because/ the matching packages already have hints
[20:10] <juliank> oh
[20:10] <juliank> yeah
[20:13] <juliank> slangasek: So, network-manager and lxcfs are force-badtest, but ori and nfs-utils are fixed
[20:13] <slangasek> ok
[20:13] <slangasek> still reasonable and appropriate to badtest hint all of these, if the tests regressed due to the infra change
[20:14] <juliank> ori is a simple case: the test suite path was just wrong, so it only ever succeeded on s390x because it was not run at all :D
[20:15] <juliank> nfs-utils did not run any tests before either, but the failures are more involved.
[20:16] <slangasek> doko: fwiw it's your upload of a new upstream release of graphviz, not in Debian, that regressed the botch autopkgtests
[20:22] <juliank> slangasek: https://code.launchpad.net/~juliank/britney/hints-ubuntu-xenial--util-linux-revdeps/+merge/337479
[20:22] <juliank> does the order between / not matter at all?
[20:23] <juliank> some entries are pkg/ver/arch, others are pkg/arch/ver
[20:24] <slangasek> juliank: perversely, yes, both forms are accepted
[20:31] -queuebot:#ubuntu-release- New binary: libsmbios [amd64] (bionic-proposed/main) [2.4.0-1] (core)
[20:34] -queuebot:#ubuntu-release- New binary: libsmbios [i386] (bionic-proposed/main) [2.4.0-1] (core)
[20:45] <juliank> slangasek: for the more complex failures in artful with util-linux util-linux/2.30.1-0ubuntu4.1, I'm contemplating running them against util-linux/2.30.1-0ubuntu4 again and see if they break that way as well. if they do, we know it's not the 4.1 upload and can just badtest them too. makes sense?
[20:45] <juliank> I certainly could create a such request just a few minutes ago, so it seems possible at least :)
[20:46] <juliank> that's, I don't know 3 tests, or something
[20:48] <slangasek> why, I do believe gdbm just managed to migrate
[21:00] <juliank> Hmm, it seems the re-running against the version outside proposed does not work
[21:00] <juliank> It installed 4.1 anyway
[21:00] <juliank> :/
[21:00] <slangasek> juliank: yes, you can't run an autopkgtest against !proposed for a package that has a version in proposed, unfortunately
[21:01] <slangasek> certainly a bug in autopkgtest-cloud; not sure how tractable it would be to fix
[21:01] <juliank> slangasek: Can I trigger it against something unrelated to workaround that?
[21:01] <slangasek> juliank: yes, you could do that
[21:03] <juliank> So if we see tests triggered by hello now, it's the workaround
[21:03] <slangasek> juliank: I upgraded the network-manager badtest to all versions fwiw, based on the comment already in the trunk
[21:04] <juliank> oh, ok
[21:07] <juliank> slangasek: I'll give you some hints for artful on Monday I think, (jbml is) still figuring that out
[21:07] <juliank> *jmbl
[21:07] <slangasek> ok
[21:14] <xnox> slangasek, gridsite was there, until my upload unbroke ftbfs; the new gridsite in proposed doesn't depend on gdbm, but old gridsite in release depends on the old gdbm. So my thinking it new gridsite need to manage to migrate. Or e.g. can you remove it from release, to "ease" things?
[21:15] <slangasek> xnox: per above, this was britney being naive; once I hinted python all the way in, gridsite untangled itself from gdbm and gdbm migrated.  gridsite is still tied with gsoap, which I'm looking at now (seems there are some missing rebuilds for the transition)
[21:16] <slangasek> srm-ifce, at least
[21:16] <xnox> oh good, well, i guess update_excuses.html is still old then, as it still lists gdbm =)
[21:16] <xnox> time to build php7.2 against ssl1.1 then?
[21:16] <slangasek> yes, there hasn't been another run yet to overwrite since the migration completed
[21:17] <slangasek> xnox: I don't see why not
[21:17] <xnox> autopkgtests queue is empty, so good time to do that.
[21:18] <slangasek> empty-ish :)
[21:19] <slangasek> mpfr4 is still the big one
[21:24] <slangasek> tsimonq2: Debian has dropped all builds of consolekit on Linux archs; lxsession still depends on consolekit in preference to libpam-systemd.  Do y'all want to fix that, so that we can drop consolekit in bionic and Lubuntu users get the correct upgrade behavior?
[21:24] <slangasek> ("correct" meaning "consolekit removed in favor of libpam-systemd")
[21:26] <slangasek> and lxdm needs rebuilt to drop libck-connector0 dep
[21:32] <tsimonq2> slangasek: create a bug and assign me (for future ref) and I'll be happy to do it
[21:32] <slangasek> tsimonq2: assigned
[21:33] <tsimonq2> slangasek: ack
[21:41] <slangasek> condor ftbfs with new gsoap
[21:43] <tsimonq2> slangasek: https://launchpad.net/ubuntu/+source/lxsession/0.5.3-2ubuntu1
[21:43]  * tsimonq2 just got home, timing was good
[21:49] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu6 => 2.02-2ubuntu7] (core)
[21:54] <xnox> ok systemd & php7.2 uploaded, hopefully both will build and test all the things over the weekend.
[21:54]  * xnox EOW
[21:54] <tsimonq2> o/ xnox
[21:59] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu7 => 2.02-2ubuntu7] (core)
[23:16] -queuebot:#ubuntu-release- New binary: aseba [s390x] (bionic-proposed/universe) [1.6.0-1] (no packageset)
[23:27] <doko> slangasek: I know, but having both python3 and php7 support
[23:33] -queuebot:#ubuntu-release- New binary: aseba [arm64] (bionic-proposed/universe) [1.6.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: node-md5-o-matic [amd64] (bionic-proposed/universe) [0.1.1-2] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: xymonq [amd64] (bionic-proposed/universe) [0.7-1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New binary: aseba [i386] (bionic-proposed/universe) [1.6.0-1] (no packageset)
[23:46] -queuebot:#ubuntu-release- New: accepted node-md5-o-matic [amd64] (bionic-proposed) [0.1.1-2]
[23:46] -queuebot:#ubuntu-release- New: accepted xymonq [amd64] (bionic-proposed) [0.7-1]
[23:46] -queuebot:#ubuntu-release- New: accepted libsmbios [amd64] (bionic-proposed) [2.4.0-1]
[23:46] -queuebot:#ubuntu-release- New: accepted libsmbios [i386] (bionic-proposed) [2.4.0-1]
[23:50] -queuebot:#ubuntu-release- New binary: aseba [amd64] (bionic-proposed/universe) [1.6.0-1] (no packageset)
[23:52] -queuebot:#ubuntu-release- New: accepted aseba [amd64] (bionic-proposed) [1.6.0-1]
[23:52] -queuebot:#ubuntu-release- New: accepted aseba [i386] (bionic-proposed) [1.6.0-1]
[23:52] -queuebot:#ubuntu-release- New: accepted aseba [arm64] (bionic-proposed) [1.6.0-1]
[23:52] -queuebot:#ubuntu-release- New: accepted aseba [s390x] (bionic-proposed) [1.6.0-1]
[23:56] -queuebot:#ubuntu-release- New binary: aseba [ppc64el] (bionic-proposed/universe) [1.6.0-1] (no packageset)
[23:57] -queuebot:#ubuntu-release- New: accepted aseba [ppc64el] (bionic-proposed) [1.6.0-1]


 @mitya57 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934450
 I think it was an intended change in Qt 5.12. … I wonder if maybe LocutusOfBorg somehow had qmake 5.11 installed with Qt 5.12?
[07:44] <Locutusofborg> mitya57 nack :D
[07:45] <Locutusofborg> https://launchpad.net/ubuntu/+source/ros-rviz/1.13.1+dfsg-2
 Ok. I will look in more details tomorrow (I'm still on vacation now).
[07:45] <Locutusofborg> unless you want to see that the archive in Ubuntu is broken :D
[07:45] <Locutusofborg> I didn't try debian experimental TBH
 Thanks for that link!
[07:46] <Locutusofborg> oh and btw in Ubuntu, I tried to just remove the .prl files from the chroot, and ros-rviz built successfully
[07:46] <Locutusofborg> this is what SIP does, to create the Makefile
[07:46] <Locutusofborg> ./siputils.py:        libs = self._extract_value(prl_name, "QMAKE_PRL_LIBS").split()
[07:46] <Locutusofborg> so, yes, looks like people are expecting such files to have variables defined at least
 Ah, maybe updating sip will help.
[07:47] <Locutusofborg> I don't think exporting QT_INSTALL_LIBS inside reverse-dependencies is sane, but I'm not a qt guy :)
 But I will look later, right now I have to go away from WiFi :)
[07:47] <Locutusofborg> not sure, enjoy your vac!
[07:47] <Locutusofborg> we can continue tomorrow or whenever you want
[07:47]  * Locutusofborg goes back to tv series :D


[03:34] <AskUbuntu> Setting up Juju on Ubuntu Cloud | http://askubuntu.com/q/309508
[09:19] <pavel> guys
[09:20] <pavel> does anybody have working lucid servers with juju?
[12:54] <jcastro> marcoceppi: did you have a branch for old docs to unscrew up that getting started page from yesterday? Or do you want me to bust it out?
[12:54] <jcastro> I can do it, just making sure you hadn't done it already
[12:55] <marcoceppi> I don't get around to hacking on it yet, it's all yours
[12:56]  * jcastro nods and gets to work
[12:56] <jcastro> man, new-docs can't get here fast enough
[12:57] <pavel> hi there
[12:58] <pavel> I'm really stuck with JuJu on Lucid. Is it supported at the moment?
[12:58] <jcastro> I don't think we've backported all the way to lucid
[12:58] <jcastro> Juju first appeared in oneiric!
[12:59] <pavel> Though there is a build for lucid in official PPA
[13:00] <jcastro> marcoceppi: nuts, I forgot old docs was RST, I see what you did there.
[13:00] <marcoceppi> :D
[13:00] <jcastro> pavel: huh really? I didn't know that.
[13:00] <jcastro> what version of juju is it?
[13:00] <pavel> The latest I think :D
[13:00] <marcoceppi> pavel: run juju --version
[13:00] <pavel> let me check
[13:00] <marcoceppi> jcastro: I think this is pyjuju
[13:00] <jcastro> oh ok
[13:01] <pavel> I don't think I would be able to do this, as far as it crashes on the start
[13:02] <marcoceppi> pavel: you can run `dpkg -l juju` to get the package version
[13:03] <pavel> one sec, booting vagrant
[13:03] <pavel> oh, it's 0.5.99+bzr604-0juju1~lucid1
[13:03] <pavel> so I don't have to suppose it would ever work on Lucid?
[13:04] <marcoceppi> pavel: yeah, the latest version is 0.7 for the 0.x series, the most recent version of juju is up to 1.11 but that hasn't been backported to lucid (or precise) yet
[13:04] <pavel> yeah, yeah
[13:04] <pavel> I just forget to look for the version
[13:04] <jcastro> marcoceppi: pushed, a onceover of my diff would be <3
[13:04] <koolhead17> jcastro, marcoceppi hello guys
[13:05] <jcastro> hazmat: do we have plans to bring .7 back to lucid in the PPA?
[13:05] <marcoceppi> pavel: yeah, so the juju package in the ppa hasn't been built for lucid in quite a while
[13:06] <pavel> marcoceppi, yep, now it's clear
[13:07] <marcoceppi> jcastro: we should be able to update the ppa to use the 0.7 build recipe
[13:07] <marcoceppi> unless there's a dep issue
[13:07] <jcastro> maybe it's an easy fix
[13:07] <jcastro> let's see what kapilt has to say
[13:07]  * marcoceppi nods
[13:09] <pavel> it would be great if you update lucid version
[13:09] <pavel> I have software which is really hard to install on something other then lucid
[13:09] <jcastro> sure, we can investigate
[13:10] <pavel> thanks a lot
[13:11] <hazmat> jcastro, lucid really?
[13:12] <hazmat> jcastro, i don't know that we done any testing on lucid, in a long time.. i think dpb1 tried it out last (within the past few months)
[13:13] <jcastro> ok
[13:13] <jcastro> dpb1: did it even build?
[13:51] <dpb1> jcastro: so, there was a change to the packaging to get around a missing dependency or something, and I think that broke lucid.  Here is the last build log I found for it: https://launchpadlibrarian.net/139956755/buildlog.txt.gz  -- it needs someone with python deb knowledge to look and fix it.  At that time, that was the only blocker to getting lucid going
[14:17] <noodles775> wedgwood_away, adam_g_ Do you know if there's anything else needing to be done on this MP for it to be approved/landed in charmhelpers? https://code.launchpad.net/~michael.nelson/charm-helpers/add-declarative-support/+merge/168961
[15:47] <marcoceppi> hazmat: in deployer can you specify relations via service:relation-name?
[15:47] <hazmat> marcoceppi, yes
[15:47] <marcoceppi> hazmat: thanks


[06:40] <flocculant> ochosi: are you sure *we* should be seeing a blue outline on password boxes ? looks a bit odd with greybird imo
[07:05] <flocculant> ochosi: rather in yakkety the blue outline is a lot bigger than it is in xenial
[07:53] <flocculant> if anyone is running yakkety - don't update ...
[07:54] <flocculant> updated my yak install - get no desktop - not a thing ... no alt+f2 to try and get things running
[07:54] <flocculant> thought it was just *that* install
[07:54] <flocculant> did a clean install of yak from an oldish iso, updated and boom - same thing
[07:56] <flocculant> http://paste.ubuntu.com/23072451/ doesn't appear to be anything of ours which has caused it
[10:43] <flocculant> bluesabre: dailies are a bit meh atm - and ubuntu isn't :(
[10:44] <flocculant> trying to live desktop - just blank - nothing there
[10:44] <flocculant> wonder if that could be tied up with my earlier update at yak leaving me with wallpaper only
[10:45] <flocculant> just trying an install
[10:51] <bluesabre> flocculant: that sounds terribly exciting
[10:51] <sakrecoer> flocculant: oddly enough i can't find the bug i filed, i remember it be set to "private".. but i had problems installing yakkety daily on 2016-08-06.. same bug as this one: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1610377
[10:51] <sakrecoer> after failing with the US one, i tried the xubuntu iso, and it had the same problem...
[10:51] <sakrecoer> some oddness with the DE..
[10:52] <flocculant> bluesabre: hugely ...
[10:52] <flocculant> sakrecoer: mmm
[10:55] <sakrecoer> i mean, might not be related at all... but i thought i'd mention it...
[10:58] <flocculant> sakrecoer: yea - thanks :)
[10:59] <flocculant> bluesabre: so it appears that what we show at the try/install dialogue and for ubiquity when going straight to install is ok, installs apparently, reboots to login (eventually) then zilch, nada :(
[11:00] <bluesabre> sounds like something somebody else broke
[11:00] <flocculant> yea
[11:00] <flocculant> like I said earlier - can't see anything in the list of updates I got which would be us
[11:01] <bluesabre> suppose this means you get to relax this weekend and not work :D
[11:01] <flocculant> might try enabling proposed on one of the 2 broken installs ...
[11:02] <flocculant> bluesabre: hah - I been working - built some flapjacks and some lardy cake \o/
[11:02] <flocculant> feasting on sugar today lol
[11:02] <bluesabre> don't know what lardy cake is, but I know what lard is
[11:02] <bluesabre> D:
[11:03] <flocculant> http://plum-kitchen.blogspot.co.uk/2010/07/lardy-cakeno-im-not-kidding.html
[11:03] <flocculant> basically bread - with fruit and lard and sugar in it - then when it's cooked, pour the escaped lard over the top and put a bit more sugar on it :D
[11:04] <bluesabre> ewwwwwwwwwwwwwwq
[11:05] <flocculant> :p
[11:20] <flocculant> bluesabre: so that's a no for proposed, but not unexpected
[11:20] <flocculant> weekend off then as you said \o/
[11:21] <bluesabre> flocculant: when was the last good image?
[11:21] <flocculant> couple of days ago - there's been non-existent network for a day or two
[11:22] <flocculant> I know that wed build was good - I installed from it - then made the mistake of upgrading it :p
[11:22] <flocculant> I'm not going to rebuild ubuntu (though I could) so will see if that crashes in flames tomorrow - which would at least help us ;)
[11:23] <bluesabre> flocculant: thanks, heading out for now, bbabl
[11:23] <flocculant> bluesabre: have a good day :)
[11:23] <bluesabre> you too
[12:21] <flocculant> bluesabre: Mate has same issue - no desktop after install and login - suspect all will once built
[12:22] <flocculant> flexiondotorg: fyi ^^
[17:59] <Unit193> bluesabre: whisker 1.6.0 look important enough?
[17:59] <Unit193> https://mail.xfce.org/pipermail/xfce/2016-August/035152.html
[18:00] <bluesabre> Unit193: the changelog sounds good at least
[18:00] <flocculant> evening
[18:01] <bluesabre> hey flocculant
[18:01] <flocculant> bluesabre: just finished checking most of the iso's - seems like only us and mate with an issue
[18:01] <bluesabre> :\
[18:01] <flocculant> yup
[18:02] <flocculant> that said - ubuntu will be rebuilt overnight and I'll check that tomorrow
[18:02] <bluesabre> k
[18:02] <flocculant> my installs are still dead though
[18:02] <Unit193> I thought US had a problem too?
[18:02] <flocculant> and guest login
[18:02] <Unit193> flocculant: Also thanks for the warning, though I have a feeling it's too late.  I just won't reboot now. :3
[18:03] <flocculant> Unit193: probably - I rarely bother with that as it's loads big and if we're dead they usually are :)
[18:03] <flocculant> Unit193: good luck then :p
[18:03] <bluesabre> Unit193: time for max uptime
[18:04] <flocculant> I'm just glad I'd actually got around to sorting a xenial install out ...
[18:05] <flocculant> bluesabre: even if ubuntu is ok - if we (and mate) are still broke monday - martin w is more likely to be around in -release :p
[18:05] <bluesabre> flocculant: indeed
[18:05] <flocculant> during uk day ofc
[18:05] <Unit193> Making a loooot of noise. :P
[18:05] <bluesabre> which is handy dandy
[18:05] <flocculant> :)
[18:05] <bluesabre> since I can't complain while UK folks are at work
[18:06] <flocculant> anyway - I'll obviously check again tomorrow morning and keep you updated on where we stand there
[18:06] <bluesabre> goodie
[18:06] <Unit193> flocculant: Going to poke at it in VM.
[18:06] <flocculant> I'm not even sure what package to report bug against :(
[18:06] <bluesabre> go for broke
[18:06] <flocculant> if I knew that I could start failing tracker
[18:06] <bluesabre> "linux"
[18:07] <flocculant> I guess so :D
[18:07] <Unit193> 'ubuntu' :P
[18:07] <flocculant> ha ha ha
[18:08] <Unit193> Meh, I suppose I should get the GTK3 whisker too.
[18:08] <flocculant> tracker tells people to report against syslinux if dead when booting live
[18:08] <flocculant> Unit193: I saw that pop up :)
[18:09] <Unit193> Mir and lightdm updates, what could go wrong?
[18:09] <Unit193> Oh, kernel and systemd too..
[18:09] <bluesabre> all of the above
[18:10] <flocculant> "<pitti> Laney: ooh -- you mean THINGS really, like half of -proposed" "pitti> Friday evening is the BEST time to break yakkety"
[18:10] <Unit193> fwupd, gcc, binutils...  Yeah didn't hit those last night, I might be safe.
[18:11] <flocculant> Unit193: those were definitely in the updates that killed mine off
[18:11] <flocculant> unless you actually read the pastebin and know that :D
[18:11] <Unit193> Yeah it could be any number of things. :D
[18:11] <flocculant> :)
[18:11] <Unit193> flocculant: I looked at it, but I didn't study it.
[18:12] <flocculant> I'll hold of on reporting it against some vague package till tomorrow - but if it's still the same I suppose anything is better than nothing
[18:13] <flocculant> bbl
[18:14] <Unit193> I'm a bit wondering if it is a lightdm/lightdm-gtk-greeter mismatch.
[18:15] <flocculant> Unit193: is it only us and mate use those?
[18:16] <Unit193> flocculant: Well, Xu, US, Myth, MATE.  I'm not sure if Lu does this cycle.
[18:17] <flocculant> Myth is finished with iso's afaik
[18:17] <flocculant> Lu worked - so perhaps not :)
[18:18] <flocculant> seems they do according to buildlog
[18:20] <flocculant> and there both same versions for us and them - so wasn't some update during day
[18:21] <Unit193> Still waiting on the VM, but glad it wasn't that.  Got the switch to a TTY or whatnot on upgrade, same as I had in Debian a couple days ago.
[18:22] <flocculant> anyway - bbl to see what you find
[20:16] <flocculant> Unit193: see anything of note in vm?
[20:17] <Unit193> flocculant: Yeah, that systemd doesn't tell you much, I really miss upstart's logging to ~/.cache/upstart/.  I just bailed and went with my custom .xinitrc and startx. :P
[20:17] <flocculant> :)
[20:18] <flocculant> I'll have another go tomorrow
[20:18] <flocculant> for now - goodnight all


[13:04] <zequence> I'm sure someone may have mentioned this before, but I just saw someone mention it today. The Ubuntu Studio group at soundcloud https://soundcloud.com/groups/ubuntu-studio
[13:04] <cfhowlett> I never knew about before today
[13:04] <cfhowlett> and it should be prominently mentioned in the US social media
[17:45] <sakrecoer> there is this too: https://wiki.ubuntu.com/UbuntuFreeCultureShowcase :)
[19:07] <sakrecoer> i'm on it tomorrow: kdenlive MTC, soundcloudgroup promo, and freeculture showcase. g'night y'all!


[00:07] <phillw> hi, is there a guru about?
[00:09] <phillw> the new kernel for non-pae is finishing off building... That means I have .deb I need a bit of help to get it into ppa
[00:13] <phillw> I also need a bit of help to name the kernel, as the source code is 3.13.0 and I pull in 3.13.0-18 from  /boot/config-3.13  on my VM that hosts the latest desktop
[00:15] <infinity> phillw: I'd imagine renaming it the same as apw's kernel in https://launchpad.net/~apw/+archive/nonpae/+packages would make sense.
[00:15] <infinity> (Or, just basing on his packaging)
[00:17] <Sarvatt> apw: nice, thanks for doing that ppa
[00:21] <phillw> infinity: rather than duplicate things, is apw happy to keep the 3.13 kernel updated for non-pae? I understand that 3.13 is not a lts kernel from linux kernel https://kernel.org/category/releases.html
[00:22] <phillw> infinity: I'm in my usual confused state :)
[00:25] <Sarvatt> phillw: 3.13 is a lts kernel, ubuntu kernel team is maintaining the stable releases of it but due to drama they wont list it on that site :P
[00:25] <infinity> phillw: 3.13 is going to be a Canonical-maintained LTS kernel for 14.04
[00:26] <phillw> infinity:  The VM is building .deb files which I'm used to. did you use ' debuild -S -sa' to get your build into your ppa?
[00:26] <infinity> (But I have no idea if Andy intends to keep rebasing that kernel, or if it was just a proof of concept, you'd have to ask him about it)
[00:26] <Sarvatt> yup
[00:27] <Sarvatt> just have to make sure to fakeroot debian/rules clean before updating the changelog and using debuild -S -sa to make it work in the ppa
[00:27] <Sarvatt> the kernel build system is weird
[00:29] <phillw> Sarvatt: it is a minor rebuild... https://wiki.ubuntu.com/phillw/non-pae Needless to say, I've had a heck of a lot help on this. the next step is to have it in ppa so any flavours that base off *buntu can get updates.
[00:29] <phillw> the actual .deb files are already generated
[00:35] <phillw> Sarvatt: why does http://packages.ubuntu.com/trusty/linux-source-3.13.0 have .13 release when the system is .18 ?
[01:00] <phillw> Hi, anyone used to building kernels on their local machines?
[01:01] <phillw> infinity: sorry to ping, but are you still about?
[06:30] <ppisati> yo
[06:52] <miseria> "blanca es mi piel, negro es mi cabello, llevo en mi carazon toda la generacion y un rechazo a la discriminacion" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival*
[07:20] <UserError> ppisati , thank you for accepting the arm bloat issues as legitimate
[07:20] <ppisati> UserError: ???
[07:21] <UserError> on launchpad, in the x86 kernel
[07:21] <ppisati> UserError: lp bug?
[07:21] <UserError> yes
[07:21] <ppisati> UserError: which one?
[07:21] <UserError> all of them
[07:22] <ppisati> sorry, i don't get it
[07:23] <UserError> For example the exynos drivers, i.MX Freescale AHCI, etc (to be removed)
[08:09] <cristian_c> Hi
[08:09] <cristian_c> I've opened this bug report much time ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972604
[08:09] <ubot2> Launchpad bug 972604 in linux (Ubuntu) "168c:001c [HP Compaq Presario C700 Notebook PC] Wireless led button doesn't switch colors" [Low,Triaged]
[08:10] <cristian_c> I've to open an upstream bug report. There is this wiki page: https://wiki.ubuntu.com/Bugs/Upstream/kernel
[08:10] <cristian_c> I've read it, but I've got some doubts:
[08:10] <cristian_c> for example: While booted into the newest mainline kernel only describe how the bug is reproducible in the latest mainline kernel only. If this is a regression, please note the specific commit.
[08:10] <cristian_c> Any ideas?
[08:14] <tseliot> apw: Aaron replied in the bug report
[08:16] <tseliot> cristian_c: that's for when you need to file a bug report against the upstream kernel
[08:17] <tseliot> in that case, upstream developers will only be interested in the upstream kernel, not in the ubuntu specific release (where we apply our own patches)
[08:43] <cristian_c> tseliot, ok, but what commit have I to specify?
[08:46] <tseliot> cristian_c: maybe check the "COMMIT" file for your kernel? For example here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc7-trusty/
[08:48] <cristian_c> tseliot, ok, is it right?
[08:49] <tseliot> cristian_c: it depends on the kernel you downloaded for testing
[08:52] <cristian_c> tseliot, summarizing: I try the 3.14-rc7 kernel and I specify the v3.14-rc7 and I note the v3.14-rc7 commit in the upstream bug report. Is it right?
[08:53] <tseliot> cristian_c: yes, that would be the tag. That's correct
[08:53] <cristian_c> tseliot, ok
[08:53] <cristian_c> thanks :)
[08:53] <tseliot> np
[08:54] <cristian_c> then, I use the content of the COMMIT file in the directory of the upstream kernel I try
[08:54] <cristian_c> ok
[08:54]  * tseliot nods
[08:54] <cristian_c> :-)
[12:36] <speakman> Hi folks. have you experienced any problems with netconsole? I'm running it as a module atm, but although all parameters are setup correctly there is nothing being sent from the host.
[12:37] <speakman> It's actually Debian kernel 3.2.0-4-amd64 but I guess you've probably heard if there is any problems with netconsole.
[12:38] <Whoopie> Hi, you enable CONFIG_ARPD for saucy kernels. Any chance to get also enabled in raring kernels? It was mentioned here (https://lists.ubuntu.com/archives/kernel-team/2013-August/032046.html) that it could be considered.
[12:40] <apw> Whoopie, rtg's response there implied that if noone whined about it we could consider it, as saucy went out with it enabled i assume it might be possible.  that said raring is likely going off support already isn't it?
[12:41] <Whoopie> apw: even for the backported kernels to precise?
[12:45] <Whoopie> rtg: I just asked the following question: Hi, you enable CONFIG_ARPD for saucy kernels. Any chance to get also enabled in raring kernels? It was mentioned here (https://lists.ubuntu.com/archives/kernel-team/2013-August/032046.html) that it could be considered.
[12:46] <rtg> Whoopie, Thiswill only have an impact on Raring LTS kernels in Precise. Is that what you are using ?
[12:46] <Whoopie> rtg: yes
[12:47] <rtg> Whoopie, do you have a bug started ?
[12:47] <Whoopie> rtg: no
[12:48] <Whoopie> rtg: should I open one?
[12:48] <rtg> yup
[12:48] <Whoopie> all right
[12:49] <apw> there are something like 3-4m life in that kernel
[12:51] <rtg> apw, the Raring LTS is supported until the end of Precise, isn't it ?
[12:51] <apw> rtg, until 14.04 is backported then the other lts kernels end
[12:52] <apw> at around 14.04.1 timeframe was my understanding
[12:52] <Whoopie> apw: 3-4m is a lot, and some may stay with that kernel and won't upgrade.
[12:53] <apw> 3-4 is a fair time, though people who need the feature presumably arn't using that kernel for the other 10m or so it has existed
[12:54] <Whoopie> nevertheless, opened a bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295666
[12:54] <ubot2> Launchpad bug 1295666 in linux (Ubuntu) "Please enable CONFIG_ARPD in Raring LTS kernels for Precise" [Undecided,New]
[12:59] <apw> rtg, btw i have been running -19 on my kit here ok so far
[13:00] <rtg> apw, I'm gonna start testing on a few platforms this morning. if it  looks good I'll upload in a few hours. Does that work for you ?
[13:03] <apw> rtg, ack, am spreading the love round here right now
[13:06] <rtg> dannf, install your x-gene with http://kernel.ubuntu.com/~rtg/3.13.0-19.39/. There is still time to fix issues before I upload.
[13:54] <apw> rtg, both xen and kvm seem to work on this kernel too ...
[13:54] <apw> smb, regraded to your -release versons of xen and things are basically working modulo the known issues
[13:54] <smb> apw, ack, I am right now starting to look into those
[13:55] <rtg> apw, cool. I checked out the KVM patches myself as well.
[13:56] <rtg> apw, perhaps I should just upload and be done with it. it appears to be working on all of my kit.
[13:58] <apw> rtg, i well it doesnt seem to regress at least
[13:59] <rtg> apw, We can always pickup any x-gene patches from dannf in the next upload, which will likely be Mon/Tues.
[13:59] <apw> yeah
[14:08] <apw> rtg, the next stable is going to be a heap and no mistake
[14:08] <rtg> apw, how many ?
[14:17] <apw> rtg, 149 so far
[14:18] <rtg> egads
[14:42] <dannf> rtg: installing..
[14:50] <dannf> rtg: so far so good
[14:50] <rtg> dannf, thats good news 'cause I've already uploaded :)
[14:51] <rtg> though we'll have at least 2 more before freeze
[14:51] <dannf> ack
[14:51] <dannf> thx!
[15:37] <dannf> rtg: one small typo - ./modules/sata-modules:ahxi_xgene ? (x/ahxi/ahci/)
[15:37] <dannf> rtg: want me to submit a patch, or is that good 'nuff?
[15:38] <rtg> dannf, dang. I can fix it.
[15:41] <rtg> dannf, patch pushed
[15:41] <dannf> ta
[15:54] <unicodestring111> I updated my kernel as instructed by the update manager , now some websites are not opening , IT IS NOT MY ISP FAULT - THE SAME ISP 'S SAME CONNECTION ON WINDOWS RUNS THE WEBSITE FINE - TE WEB PAGES WERE OPENING BEFORE AS WELL
[16:02] <apw> unicodestring111, reboot into an older kernl and see if it goes away
[16:22] <apw> unicodestring111, if it goes away then it was the kernel update, if not it is something else, say something else that came in the same batch of updates
[16:51] <dannf> rtg: and i see you were just copying what i typed, sorry -  my bad.
[16:51] <rtg> dannf, np
[21:19] <ParkerR> If I am wanting to backup the boot parttiion of my nexus 7 (/dev/mmcblk0p2) can I just dd it to a file? From everything I have seen it should be 8MB but when I dd it to a file it's 8.4MB. I am wanting a backup that I am able to flash with fastboot
[21:21] <ParkerR> Ok nvm. Just tested flashing it with flashboot and it worked. I figured if anything messed up I could just redo it. Glad that I didnt have to :D
[23:41] <miseria> "blanca es mi piel, negro es mi cabello, llevo en mi carazon toda la generacion y un rechazo a la discriminacion" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival*


[03:21] <dupingping> Hi, everyone.
[07:03] <dholbach> good morning
[08:52] <dupingping> dholbach, morning.
[09:07] <dholbach> hi dupingping
[09:07] <dupingping> hi
[09:08] <dupingping> dholbach, are you a moderator?
[09:21] <dholbach> moderator in which sense?
[09:23] <dupingping> I means that Ubuntu Software Center's moderator.
[09:27] <dholbach> ah, no - sorry
[09:28] <dholbach> which package are you looking for help with?
[09:28] <dupingping> My software is in pending review stats in Ubuntu Software Center for 4+ days.
[09:29] <dholbach> which package is it?
[09:29] <dupingping> it's ubuntu-sticky.
[09:29] <dholbach> do you have a link to it?
[09:30] <dupingping> it's not published yet. please look the status, at following url.
[09:30] <dupingping> https://developer.ubuntu.com/en/publish/application-states/
[09:31] <dupingping> Review pending is second step.
[09:31] <dholbach> no... the link you mention is about the software store for the phone
[09:31] <dholbach> not for the desktop
[09:31] <dholbach> unfortunately it takes a lot longer to get software in through this process for the desktop right now as it requires manual review