[11:05] <BluesKaj> Hi all
[11:43] <Maddeth> Morning/afternoon/evening all, I am looking for a comparison of packages between 10.04 LTS and 12.04 LTS to what will be 14.04 LTS, any idea's, should I just roam launchpad?
[14:42] <dakotawulfy> hi
[15:04] <dakotawulfy> hi
[15:05] <dakotawulfy>  hey  will you be able to update from alpha to beta with out a new install ?
[15:06] <DJones> dakotawulfy: Yes, should be, as long as you keep updating, you'll just stay with the latest version
[15:06] <dakotawulfy> ok cool thanks
[15:06] <DJones> !final | dakotawulfy (This is a bit premature talking about going from beta to final, but its the same principal),
[15:07] <dakotawulfy> ok
[15:08] <dakotawulfy> has any one had any problems with zenity ??
[16:17] <AA___> Hello everyone, i am trying to install th cherokee webserver on ubuntu 14.04. As far as i can tell, the cherokee package in is not in 14.04 yet and at the same time, the cherokee project does not seem to have a ppa for trusty tahr....Can anyone provide some help about getting the cherokee webserver for the saucy release installed on trusty tahr?
[16:18] <mamarley> You could try using the PPA for Saucy.  It would probably work.
[16:19] <AA___> Thanks mamarley, does this mean any special parameters to add-apt-repository?
[16:19] <mamarley> You could add it normally and then change "trusty" to "saucy" after adding.  I don't use apt-add-repository, so I don't know for sure.
[16:20] <AA___> I did that and it did not work..I edited the entry from update-manager
[17:27] <HALanon9000> ubuntu 14.04 has been pretty stable until now. i restarted my computer because i couldn't connect to my wifi, but when i logged in Unity was broke. i can right click on the desktop and create new folders and change the desktop background, but no launcher or status bar. i can use ctr alt t to get to terminal and start various applications, but when i when i tried starting unity, it said it wasn't installed. so i installed usin
[17:27] <HALanon9000> g apt-get and started it, my windows flashed a couple of times but still no luck. any ideas on how to fix this
[17:45] <HALanon9000> is anyone active? ^^
[23:41] <Anonymouse_> is there a 14.04 for Ubuntu Studio?
[23:57] <Anonymouse_> http://cdimage.ubuntu.com/xubuntu/daily-live/20140121.1/trusty-desktop-amd64.iso is 404!  @_@


[19:11] <jo-erlend> should I be able to install Ubuntu MID on my Nokia N900?
[19:24] <GrueMaster> ogra what's with the team meeting reminder?  We only have the meeting once a day and it is far earlier than what you have announcing.
[19:25] <GrueMaster> Er, once a week I mean.
[19:25] <GrueMaster> Oh, nevermind.  No scrollback in this channel.  Odd.


[18:05] <longsleep> Is docker supposted to work? I am getting BUG: scheduling while atomic: docker.armhf/5023/0x00000002 when trying to start a container - see http://paste.ubuntu.com/11709495/ for full log.
[20:44] <ToyKeeper> Dammit, scp doesn't have an option to copy symlinks as symlinks instead of following them.
[20:45]  * ToyKeeper adds another request for rsync in the default image
[20:51] <ToyKeeper> Would be nice to have strace too.
[21:01]  * ToyKeeper tries to figure out how to get /dev/i2c entries in order to use all the lovely I/O this thing has.
[21:02] <ToyKeeper> BTW, it'd be nice to have lspci too.
[21:02] <ToyKeeper> And lsusb.
[21:03] <ToyKeeper> 'modprobe -v i2c-bcm2708 i2c-dev' didn't seem to help.  :(
[21:04] <ToyKeeper> So far it looks like no HDMI and no i2c, which reduces my project ideas to zero.
[21:06] <ToyKeeper> I could use it as a SSO token generator, but I've already got a container doing that on my lxc server.
[21:14] <ToyKeeper> With udev and systemd and such, I'm guessing I can't just mknod the device entries.
[21:16] <ToyKeeper> I wonder if audio works, and if I can get NFS tools installed plus some codecs.
[21:16] <ToyKeeper> It could function as a music player pulling songs from a NAS...
[21:17] <ToyKeeper> I'm looking for use cases which I can't just spin up another LXC client for.


[03:05] <MTecknology> newz2000: hi
[17:19] <thorwil> newz2000: so i'm back online sooner than expected :)
[17:19] <newz2000> hey thorwil
[17:21] <thorwil> newz2000: the images from my mail are in place?
[17:22] <newz2000> thorwil: are they different than the ones in your bzr branch?
[17:22] <newz2000> I can't remember what I did now
[17:22] <thorwil> newz2000: they are until the revision 20 that i just pushed
[17:23] <newz2000> how can I tell if I put the right ones in or not?
[17:23] <thorwil> in other words, the tarball attached and the rev 20 are identical
[17:23] <thorwil> newz2000: look at the images for 23 and 22 days to go
[17:24] <newz2000> http://www.ubuntu.com/files/countdown/910/countdown-9.10-1/23.png
[17:24] <thorwil> newz2000: if you see the number placement change, it's the old set
[17:24] <newz2000> oh, ok, I have the old ones
[17:24] <newz2000> I'll get the ones in from your download
[17:25] <thorwil> good
[17:25] <thorwil> what happened to the slideshow?
[17:25] <newz2000> I'm not sure, activity kind of tapered off after the first round
[17:25] <thorwil> rime, knome: i lost internet connection for a while ...
[17:26] <thorwil> newz2000: i thought it was ready to be used!?
[17:27] <newz2000> there were some improvements yesterday, I think the last thing that needs done is to start the text out visible and then fade out. The speed looks good though.
[17:27] <newz2000> I've been a little caught up in beta and other projects though so somene needs to tell me it's done and ready
[17:27] <thorwil> ah, ok
[17:28] <jpds> newz2000: http://www.ubuntu.com/testing/karmic/beta#Upstart - that cdimage link is gone.
[17:28] <Ng> jpds: ta :)
[17:29] <jpds> Ng: That page right there, not your racks.
[17:29] <Ng> jpds: definitely not my racks
[17:29] <jpds> Hehe.
[17:29] <newz2000> Ng: do we need to change the link or put the image back in place?
[17:29] <Ng> newz2000: not my call :)
[17:30] <Ng> I'd be surprised if the alphas are coming back though ;)
[17:30] <newz2000> ok, let me find Steve Langasek
[17:36] <newz2000> ok, all done, thanks jpds
[20:25] <Turl> canonical's repo servers are extremely slow today :(
[20:25] <Turl> no more than 15kB/s
[20:39] <jpds> Turl: Yes.
[20:39] <jpds> Turl: Tell that to every single person hammering the servers getting the beta when they should be using torrents/local mirrors.
[20:44] <Turl> any main server not being hammered?
[20:45] <jpds> Turl: Pick a mirror from https://launchpad.net/ubuntu/+archivemirrors
[20:48] <Turl> my country mirror is one week behind, not much help
[20:49] <jpds> Turl: You could always use one like br.archive.ubuntu.com, rather than the one in London ?
[20:50] <Turl> true
[20:50] <Turl> I guess it'll have better speed
[20:50] <Turl> I'm using ar.archive.ubuntu.com - the speed is sloooooow
[20:50] <jpds> That's because ar.archive is pointing at London.
[20:51] <Turl> oh
[20:51] <Turl> why is there an ar.archive then?
[20:51] <Turl> it's confusing for ppl
[20:51] <jpds> Because noone's applied to be an official country mirror for Argentina?
[20:52] <Turl> yeah, but why not just remove ar. and create it when there's an official mirror?
[20:53] <jpds> Because that would break people's current setups?
[20:54] <Turl> yeah, but I mean, why was it created initially? I don't see why that exists
[20:56] <knome> thorwil, newz2000: i think rime has been busy.
[20:56] <knome> thorwil, newz2000: what was left to tweak?
[20:57] <newz2000> knome: the last thing I know that was mentioned was starting the text out as shown
[20:57] <newz2000> instead of fading it in at the beginning
[20:57] <newz2000> but I've been a bit caught up in other things so I wasn't able to follow the conversations too closely
[20:58] <thorwil> knome: i missed  a bit more than 1 day
[20:58] <knome> okay, let me find the link
[20:58] <knome> http://markus.alshain.fi/markus/deve/slider/slider04.html
[20:58] <knome> that's the current
[20:59] <knome> i don't think all the frames are correctly aligned
[20:59] <knome> but how does that look otherwise?
[21:00] <Turl> knome: isn't it too quick? :/
[21:00] <knome> newz2000 thought it was too slow before.
[21:00]  * newz2000 checks
[21:00] <newz2000> no, it's not too quick. Looks good.
[21:00] <thorwil> yes, out of center
[21:01] <knome> i suppose that's relatively easy to fix.
[21:01] <knome> is there anything else to fix?
[21:01] <knome> other than that and it being clickable, naturally
[21:01] <Turl> it looks like you are running on a fast car
[21:01] <Turl> :P
[21:04] <thorwil> knome: no fade in for first text, centering, clickable. should be fine then
[21:04] <knome> Turl, hmm. does driving a car fast bring you negative feelings? ;)
[21:04] <knome> no fade at all?
[21:05] <Turl> knome: nope, but impedes me from reading :P I might be thinking it's too fast because mine moves almost continously but slower
[21:05] <Turl> http://labs.turl.com.ar/animcount/slide.html
[21:05] <knome> yeah.
[21:05] <newz2000> ah, that's nice too. Too slow but the effect looks good.
[21:06] <thorwil> knome: hmm ... seems there are 2 fade-ins, for pulse and text on first frame. ideally it would be one quick fade-in for both. but having no fade-in for the text cam from newz2000
[21:07] <thorwil> Turl: very nice. i especially like the start
[21:07] <knome> thorwil, there is no fadein for the pulse
[21:08] <thorwil> knome: then my tired brain mis-interpreted the jump from flat fill to graphic as very fast fade :)
[21:08] <Turl> thorwil: thanks :)
[21:09] <newz2000> I'm going to leave the animation in your hands guys. Make it look good and snappy. I'll publish it on Monday.
[21:09] <thorwil> Turl: the opening-up step before the countdown should run through and not have a stop/slow-down
[21:10] <Turl> thorwil: yep :)
[21:10] <thorwil> Turl: on the first run, i saw a grey area instead of the countdown image for a short bit
[21:11] <thorwil> guess that means images aren't but should be preloaded
[21:12] <Turl> yep
[21:13] <knome> http://emonk.fi/open/ubuntu/Karmic%20Countdown%20Banner/slider04.html
[21:13] <Turl> I did it quickly the other day but never finished it :P
[21:13] <knome> does that look better?
[21:13] <Turl> knome: what did you change? I think it's the same as before
[21:13] <knome> oops, broke it
[21:14] <knome> Turl, text doesn't fade in the first time and the frames are aligned
[21:14] <knome> now it's also clickable
[21:14] <knome> for now it reloads the current page
[21:15] <Turl> it creates a horrible blue like :/
[21:15] <Turl> and red
[21:15] <Turl> when you click on it
[21:16] <knome> just a minute
[21:16] <knome> i see if i can affect that
[21:17] <knome> ok, no more blue+red
[21:18] <knome> thorwil, ?
[21:19] <Turl> works fine now knome :)
[21:19] <knome> yay
[21:20] <thorwil> either i have a bad screenshot-timing, or at least some of the graphics are still off-center
[21:20] <knome> thorwil, can you give me some exact data if you did screenshooting, i can fix it then
[21:21] <knome> hmm
[21:22] <thorwil> knome: looks like the laptop is 5 px to far to the left
[21:23] <knome> for some reason, the text on laptop fades out almostimmediately
[21:24] <knome> right, i fixed it
[21:24] <knome> thorwil, any other misaligned?
[21:24] <knome> (hoe's the lappy now)
[21:24] <knome> *how
[21:25] <thorwil> cloud is shifted to the right
[21:25] <knome> how much?
[21:27] <knome> brb
[21:27] <thorwil> knome: 3 pixels
[21:28] <thorwil> knome: something wrong with the border. i only see a black border on top, not any other side
[21:31] <knome> hmm
[21:31] <knome> weird
[21:32] <knome> oh, not really.
[21:32] <thorwil> too tired, good night! :}
[21:32] <knome> it's now red for debugging
[21:32] <knome> okay, night thorwil
[21:33] <Turl> knome: #ubuntu910-rotator { border: 0; }
[21:33] <Turl> that should remove it
[21:33] <knome> no, we should *have* a black border...
[21:34] <Turl> why?
[21:35] <knome> thorwil says so
[21:35] <Turl> knome: you might remove it from the ul and add it to #ubuntu910-wrap
[21:35] <Turl> :)
[21:36] <knome> no, then it's 182x152, which is too much, i hear
[21:37] <knome> ah, fixed anyway
[21:37] <knome> kind of followed your idea, but made the wrap itself 2px smaller;)
[21:38] <Turl> I was going to recommend you that heh :P


[04:49] -queuebot:#ubuntu-release- Unapproved: accepted maas [source] (bionic-proposed) [2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1]
[05:13] -queuebot:#ubuntu-release- New binary: tabbar-el [amd64] (cosmic-proposed/none) [2.2-1] (no packageset)
[05:44] -queuebot:#ubuntu-release- New: accepted tabbar-el [amd64] (cosmic-proposed) [2.2-1]
[06:25] -queuebot:#ubuntu-release- Unapproved: rejected ostree [source] (bionic-proposed) [2018.6-0ubuntu0.1]
[06:28] -queuebot:#ubuntu-release- Unapproved: accepted apache2 [source] (bionic-proposed) [2.4.29-1ubuntu4.3]
[06:32] -queuebot:#ubuntu-release- Unapproved: accepted tomcat8 [source] (bionic-proposed) [8.5.30-1ubuntu1.3]
[07:05] <ginggs> would someone please kick the can along 'force-badtest python-xarray/0.10.8-1/arm64' in stefanor's hints
[07:06]  * tumbleweed can
[07:06] <tumbleweed> ginggs: when does this can hit the wall?
[07:06] <tumbleweed> also, we miss you at debconf :(
[07:09] <ginggs> tumbleweed: i believe it's this https://github.com/numpy/numpy/issues/8325 (so not in xarray itself)
[07:09] <gitlab-bot> numpy issue 8325 in numpy "np.nan incorrectly casted into datetime on powerpc, leading to failing tests of pandas" (comments: 28) [Open]
[07:10] <ginggs> tumbleweed: i miss y'all too!
[07:13] <ginggs> tumbleweed: and please 'force-badtest cmake-extras/1.3+17.04.20170310-1ubuntu4/ppc64el' - i believe the latest test shows it has regressed in release http://autopkgtest.ubuntu.com/packages/c/cmake-extras/cosmic/ppc64el
[07:14] <tumbleweed> ginggs: xarray only on arm64?
[07:15] <ginggs> tumbleweed: yes, the i386 was floating point precision, and seems fixed now
[07:33] <rbalint> slangasek, the rax-nova-agent changes to systemd unit dependencies are due to upstream changes which made part of our patches obsolete and the agent seem to be working well in their cloud, matching their claims
[07:35] <rbalint> slangasek, if needed i can add more explanation to the bug as well and the SRE is there for the package, indeed, but IMO it would be reasonable to approve one
[08:10] <tumbleweed> ginggs: sorry, was doing some video stuff, but committed the bump now
[08:11] <ginggs> tumbleweed: np, thanks!
[08:11] <tumbleweed> do we know what's up with cmake-extras?
[08:11] <tumbleweed> what regressed it?
[08:19] <ginggs> tumbleweed: no ideas what caused it, but it wasn't googletest
[08:22] <tumbleweed> ginggs: ok, committing a badtest
[08:41] <ginggs> tumbleweed: thanks again!  we can probably blame doko for cmake-extras :p
[08:41] <tumbleweed> he's here if you'd like me to apply the blame in person
[11:02] -queuebot:#ubuntu-release- Unapproved: linux-base (trusty-proposed/main) [3.5ubuntu4 => 4.5ubuntu1~14.04.1] (core) (sync)
[11:12] -queuebot:#ubuntu-release- New binary: golang-github-gdamore-encoding [amd64] (cosmic-proposed/none) [0.0~git20151215.b23993c-1] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: php-composer-xdebug-handler [amd64] (cosmic-proposed/none) [1.1.0-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: gmbal-commons [amd64] (cosmic-proposed/universe) [3.2.1-b003-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: mimepull [amd64] (cosmic-proposed/universe) [1.9.7-1] (no packageset)
[12:23] -queuebot:#ubuntu-release- New: accepted gmbal-commons [amd64] (cosmic-proposed) [3.2.1-b003-1]
[12:23] -queuebot:#ubuntu-release- New: accepted mimepull [amd64] (cosmic-proposed) [1.9.7-1]
[12:23] -queuebot:#ubuntu-release- New: accepted golang-github-gdamore-encoding [amd64] (cosmic-proposed) [0.0~git20151215.b23993c-1]
[12:23] -queuebot:#ubuntu-release- New: accepted php-composer-xdebug-handler [amd64] (cosmic-proposed) [1.1.0-1]
[14:42] -queuebot:#ubuntu-release- New binary: gmbal [amd64] (cosmic-proposed/universe) [4.0.0-b002-1] (no packageset)
[15:39] -queuebot:#ubuntu-release- New: accepted gmbal [amd64] (cosmic-proposed) [4.0.0-b002-1]
[17:13] -queuebot:#ubuntu-release- New binary: bar-cursor-el [amd64] (cosmic-proposed/universe) [2.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: golang-github-git-lfs-gitobj [amd64] (cosmic-proposed/universe) [0.0~git20180705.5aa0c18-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: gnome-subtitles [s390x] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[17:14] -queuebot:#ubuntu-release- New binary: initsplit-el [amd64] (cosmic-proposed/universe) [1.8+3+gc941d43-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: eproject-el [amd64] (cosmic-proposed/universe) [1.5+git20180312.068218d-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: gnome-subtitles [ppc64el] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[17:15] -queuebot:#ubuntu-release- New binary: limesuite [s390x] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: gnome-subtitles [i386] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[17:15] -queuebot:#ubuntu-release- New binary: limesuite [amd64] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: limesuite [ppc64el] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: gnome-subtitles [amd64] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[17:17] -queuebot:#ubuntu-release- New binary: limesuite [i386] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: limesuite [armhf] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: limesuite [arm64] (cosmic-proposed/universe) [18.06.0+dfsg-1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: gnome-subtitles [arm64] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[17:24] -queuebot:#ubuntu-release- New binary: gnome-subtitles [armhf] (cosmic-proposed/universe) [1.4-1] (cli-mono)
[22:21] -queuebot:#ubuntu-release- New: accepted bar-cursor-el [amd64] (cosmic-proposed) [2.0-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [amd64] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [armhf] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [ppc64el] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted golang-github-git-lfs-gitobj [amd64] (cosmic-proposed) [0.0~git20180705.5aa0c18-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [amd64] (cosmic-proposed) [18.06.0+dfsg-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [armhf] (cosmic-proposed) [18.06.0+dfsg-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [ppc64el] (cosmic-proposed) [18.06.0+dfsg-1]
[22:21] -queuebot:#ubuntu-release- New: accepted eproject-el [amd64] (cosmic-proposed) [1.5+git20180312.068218d-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [i386] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted initsplit-el [amd64] (cosmic-proposed) [1.8+3+gc941d43-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [i386] (cosmic-proposed) [18.06.0+dfsg-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [arm64] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [arm64] (cosmic-proposed) [18.06.0+dfsg-1]
[22:21] -queuebot:#ubuntu-release- New: accepted gnome-subtitles [s390x] (cosmic-proposed) [1.4-1]
[22:21] -queuebot:#ubuntu-release- New: accepted limesuite [s390x] (cosmic-proposed) [18.06.0+dfsg-1]
[23:14] -queuebot:#ubuntu-release- New binary: libtickit-perl [s390x] (cosmic-proposed/universe) [0.65-2] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: libcircle-be-perl [amd64] (cosmic-proposed/universe) [0.173320-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: libtickit-perl [i386] (cosmic-proposed/universe) [0.65-2] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: libtickit-perl [amd64] (cosmic-proposed/universe) [0.65-2] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: libtickit-perl [ppc64el] (cosmic-proposed/universe) [0.65-2] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: libtickit-perl [arm64] (cosmic-proposed/universe) [0.65-2] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: libtickit-perl [armhf] (cosmic-proposed/universe) [0.65-2] (no packageset)


[01:43] <Noskcaj-school> I've reverted the upstream clutter commit which made gdk the default backend, which fixes parole. Should i put this in the staging ppa?
[01:52] <Noskcaj-school> And do we wait for an upstream responce or should we ask the desktop team if we can revert the change in ubuntu
[02:03] <Noskcaj-school> Or should we just not use clutter until it's fixed?
[02:37] <bluesabre> Noskcaj-school: we should either communicate with upstream about it or at least get it in ubuntu (since it also affects totem)
[02:37] <bluesabre> and I'll change our default to xv in the next default-settings upload
[02:38] <Noskcaj-school> bluesabre: Couldn't we just remove the --enable-clutter from parole to fix our default?
[02:38] <Noskcaj-school> And i'll ask in -desktop now
[02:47] <bluesabre> Noskcaj-school: we actually have the default config set to clutter... normally its set to XV
[02:47] <Noskcaj-school> ok
[02:47] <bluesabre> we chose clutter since it could do software acceleration and work in vbox and elsewhere
[02:47] <bluesabre> until now, when it doesn't work at all that is ;)
[09:06] <ochosi> bluesabre: just so you know, Greybird is 1.6-ready, just for
[09:07] <ochosi> got to tag yesterday and now i'm on my way, hope i'll get to it tonight
[09:07] <ochosi> bbl
[09:56] <bluesabre> ochosi: excellent
[12:13] <ochosi> bluesabre: ok, beat myself to it: https://github.com/shimmerproject/Greybird/releases/latest
[14:45] <Guest40123> Hi
[14:46] <Guest40123> Hello
[17:21] <pleia2> http://news.softpedia.com/news/xubuntu-linux-is-being-used-to-teach-students-at-colegio-hispano-americano-in-puerto-rico-487132.shtml
[17:32] <knome> :)
[17:32] <knome> "new series"
[21:35] <bluesabre> "In the latest interview article" at least they do pay some attention though
[21:35] <bluesabre> :D
[21:35] <bluesabre> cool to see the article get picked up
[21:35] <bluesabre> great job again pleia2 :D
[21:38] <knome> yep, ++
[21:43] <Unit193> knome: I've been ACK'ing all the BTS stuff as that's the email set for the package(s).
[21:50] <knome> mmkay.


[07:36] <mup> PR snapcraft#868 closed: Parametrize call args for pluginhandler <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/868>
[13:23] <zyga> Son_Goku: hey
[13:23] <zyga> Son_Goku: greetings from bucharest
[13:23] <zyga> Son_Goku: how's stuff?
[13:23] <Son_Goku> you're alive!
[13:23] <Son_Goku> *\o/*
[13:23] <zyga> gee, dude, shave ;-)
[13:24] <zyga> this is the last week of my journes
[13:24] <zyga> I saw some warnings that snap-confine doesn't build in master
[13:25] <zyga> Son_Goku: how are you doing?
[13:26] <Son_Goku> I'm alright
[13:26] <Son_Goku> I've been getting pings about snapd for Fedora though
[13:26] <Son_Goku> and you missed me getting the policy working
[13:27] <zyga> Son_Goku: \o/
[13:27] <zyga> Son_Goku: wooot, what's next?
[13:27]  * zyga hugs Son_Goku :)
[13:27] <Son_Goku> https://github.com/zyga/snapcore-fedora/pull/10
[13:27] <mup> PR zyga/snapcore-fedora#10: Refresh patches for snapd spec <Created by Conan-Kudo> <https://github.com/zyga/snapcore-fedora/pull/10>
[13:27] <Son_Goku> first, merge that
[13:27] <zyga> Son_Goku: I was broken during wekeend and partially last week, trying to get some health back
[13:28] <zyga> checking that out now :)
[13:28] <Son_Goku> then update https://bugzilla.redhat.com/show_bug.cgi?id=1367825 with a new spec
[13:28] <Son_Goku> and SRPM
[13:28] <zyga> yep, with pleasure!
[13:29] <Son_Goku> and since the service files have changed a bit, check to be sure if additional services need to be requested for the preset: https://bugzilla.redhat.com/show_bug.cgi?id=1367932
[13:29] <zyga> Son_Goku: yeah, I was just thinking about that
[13:29] <Son_Goku> I think snapd.autoimport.service needs to be enabled as well
[13:29] <zyga> Son_Goku: no, not really, it's just for core AFAIK
[13:29] <zyga> Son_Goku: I need to check with mvo when he's here today but I don't think we need it
[13:29] <zyga> well. think :)
[13:30] <zyga> Did you get it to work all the way?
[13:30] <zyga> with snaps installing and stuff?
[13:30] <zyga> `+2.8.4 (Apple Git-73)
[13:30] <Son_Goku> well, I need to retest on a fresh VM to be certain, but yes
[13:30] <zyga> was that you or me? :)
[13:30] <Son_Goku> https://github.com/snapcore/snapd/blob/master/debian/rules#L66
[13:30] <zyga> that's amazing :)
[13:31] <Son_Goku> that's where I checked to see the services that should be enabled
[13:31] <zyga> yeah, I know we run them everywhere
[13:31] <zyga> but I think this was just us hurrying with image readiness
[13:31] <zyga> I'll double check with mvo
[13:31] <Son_Goku> ah
[13:31] <zyga> I'd rather not enable that service unless we have to
[13:31] <Son_Goku> right
[13:31] <Son_Goku> if it's not necessary, then leave it be
[13:32] <Son_Goku> I've already updated the patches to have new versions of the services :)
[13:34] <Son_Goku> O.o
[13:34] <Son_Goku> ffs
[13:34] <Son_Goku> the store doesn't work now!
[13:34] <Son_Goku> because it uses port 53
[13:34] <Son_Goku> nowhere was that documented :(
[13:34] <zyga> Son_Goku: what's the .foo syntax in %patchN
[13:35] <zyga> what?!?
[13:35] <Son_Goku> zyga, if the patch fails, the buildroot maintains a backup copy of the original with that prefix
[13:35] <zyga> port 53?
[13:35] <zyga> ah, nice
[13:35] <Son_Goku> makes it easier for rediffing
[13:35] <Son_Goku> wtf is it using port 53 for?!
[13:36] <zyga> Son_Goku: DNS?
[13:36] <zyga> Son_Goku: can you point me to some code that does this?
[13:36] <Son_Goku> I just tried to do "sudo snap install hello"
[13:36] <Son_Goku> try it in a Fedora VM with the package and latest stuff
[13:36] <Son_Goku> ah, I think it is DNS lookup
[13:37] <Son_Goku> why is snapd doing its own DNS lookup?
[13:37] <zyga> Son_Goku: probably because it's golang but I'm checking
[13:39] <zyga> Son_Goku: yes, internal DNS
[13:39] <zyga> Son_Goku: does that need selinxu tweaks?
[13:39] <Son_Goku> yes
[13:39] <Son_Goku> are there any other TCP/UDP things that I need to do as well?
[13:41] <zyga> I don't know of any
[13:41] <zyga> just https and DNS
[13:42] <zyga> Son_Goku: as a side comment, working on confinement of any kind makes you re-learn how the stack _really_ works
[13:42] <zyga> Son_Goku: I find that refreshing
[13:46] <zyga> Son_Goku: merged
[13:46] <Son_Goku> I'm working on adding rules for dns and http cache ports
[13:46] <Son_Goku> I have a feeling it'd be a good idea to add cache ports too
[13:47] <zyga> Son_Goku: http cache?
[13:47]  * zyga is starving, had u-breakfast only
[13:47] <Son_Goku> ports like 8080, etc.
[13:48] <Son_Goku> often used by proxies and stuff
[13:48] <zyga> ah, I understand
[13:48] <zyga> sure
[13:51] <zyga> Son_Goku: ok, we don't want autoimport
[13:51] <zyga> Son_Goku: I'll ript it out (both the service and udev)
[13:51] <Son_Goku> okay
[13:51] <zyga> Son_Goku: this means the approvals are okay now
[13:51] <Son_Goku> just don't install the files, but leave the patches alone
[13:51] <zyga> Son_Goku: I'll do this and redo the SRPM :)
[13:51] <zyga> OK
[13:51] <Son_Goku> what are they used for, btw?
[13:52] <zyga> they are used to claim a headless device
[13:52] <zyga> plug a drive with stuff you made elsewhere
[13:52] <Son_Goku> ah
[13:52] <Son_Goku> useless then
[13:52] <zyga> it sucks assertions
[13:52] <zyga> yes
[13:52] <zyga> and "acks" them
[13:52] <Son_Goku> but yeah, leave the patch alone
[13:52] <zyga> (imports and checks signatures and cross-signatures and stuff)
[13:52] <Son_Goku> as it can eventually be applied to snapd once the debian packaging is gutted from the package
[13:53] <Son_Goku> technically, it could be applied now, as it doesn't conflict
[13:53] <Son_Goku> but... meh
[13:57] <zyga> Son_Goku: pushed a small patch, please look at it
[13:59] <zyga> Son_Goku: this week I'll try to merge snap-confine into snapd and we _may_ finally get dist tarballs
[14:00] <Son_Goku> neh
[14:00] <Son_Goku> not particularly enthused about that *shrugs*
[14:00] <zyga> well, it will simplify a lot though
[14:00] <zyga> one package
[14:01] <Son_Goku> at least from my point of view, not really
[14:01] <Son_Goku> if we really wanted to build everything as one thing, we could have, since rpmspec supports multiple sources
[14:02] <Son_Goku> technically, so does dsc built debian packages
[14:02] <zyga> Son_Goku: yeah, that's true, this is more of an upstream change though, it will make changes easier
[14:02] <zyga> close coupling between the two packages
[14:08] <Son_Goku> zyga, you know, I'm surprised you guys don't just use systemd presets in the packaging of snapd for Debian/Ubuntu
[14:08] <Son_Goku> it makes things a lot simpler
[14:08] <Son_Goku> then you don't even *need* dh-systemd to do much
[14:09] <zyga> Son_Goku: I suspect because those are not used in debian but I don't know
[14:10] <zyga> Son_Goku: the first time I even realized this feature existed was when I started working with fedora
[14:11] <zyga> Son_Goku: I'm building everything locally for testing
[14:11] <zyga> Son_Goku: I'll do a small release of snap-confine to fix some issues and integrate patches with packaging, probably <IP_ADDRESS>
[14:11] <zyga> Son_Goku: but only after this works :)
[14:11] <zyga> Son_Goku: I think we should do f24+ only for now
[14:11] <zyga> Son_Goku: until 23 is resolved
[14:12] <zyga> Son_Goku: right now I think I broke 23 because of older libc (trivial patch already merged into master)
[14:13] <zyga> Son_Goku: and we need to update something (still unsure what) to get store interaction to work
[14:13] <Son_Goku> well, Fedora 23 is EOL in December
[14:13] <zyga> Son_Goku: but again, I'll focus on 23 when 24+ is done
[14:13] <zyga> Son_Goku: are there any stats available to know how many users moved to 24 already?
[14:13]  * Son_Goku shrugs
[14:13] <zyga> OK
[14:14] <zyga> well, I think 23 shoudl be easy-ish
[14:14] <zyga> fingers crossed :)
[14:16] <zyga> Son_Goku: what should I say for bodhi type= when there's just a new upstream release?
[14:16] <Son_Goku> use bugfix as the type unless it's an enhancement
[14:16] <zyga> Son_Goku: I want to update snap-confine in f24 with the new patches and snap runtime layout
[14:16] <Son_Goku> or a security fix
[14:16] <Son_Goku> bugfix
[14:16] <Son_Goku> use bugfix
[14:16] <zyga> Son_Goku: is there a bug? I think we can only refer to snapd tracking bug itself (/snap change)
[14:17] <Son_Goku> bugfix doesn't require a bug
[14:17] <zyga> Son_Goku: do I need a bug number or will it ignore it?
[14:17] <zyga> ah, OK
[14:17] <Son_Goku> it'll ignore it if no bugs are listed
[14:17] <zyga> Son_Goku: any karma tweaks I should apply?
[14:17] <Son_Goku> change the positive karma version from 3 to 1
[14:18] <zyga> thanks, done
[14:18] <Son_Goku> though I hadn't been pushing snap-confine updates through bodhi because I figured we'd want to ship snap-confine and snapd in the same update
[14:18] <zyga>   https://bodhi.fedoraproject.org/updates/FEDORA-2016-c579dae0b4
[14:19] <zyga> well, not today :)
[14:19] <zyga> today I just want both out
[14:20] <Son_Goku> well, fortunately, we can edit an existing update :)
[14:21] <zyga> and this is 25
[14:21] <zyga>   https://bodhi.fedoraproject.org/updates/FEDORA-2016-f3b947ec5d
[14:21]  * zyga reboots with enforcing policy :)
[14:21] <zyga> "make selinux enforcing again"
[14:24] <zyga> I'll bump snap-confine dependeny to .44
[14:25] <zyga> Son_Goku: more selinxu denials
[14:26] <zyga> paź 30 15:25:38 fedora24 setroubleshoot[3400]: SELinux is preventing snapd from read access on the directory /etc/systemd/system. For complete SELinux messages. run sealert -l 3dc56126-a462-4305-8495-d9bb54be3740
[14:26] <zyga> Son_Goku: can you please include that in the policy?
[14:26] <Son_Goku> why does it need to read /etc/systemd/system?
[14:26] <zyga> Son_Goku: you made it :)
[14:26] <zyga> ah
[14:26] <zyga> well, sorry
[14:26] <zyga> my bad :)
[14:26] <zyga> it needs to because it looks there for systemd units
[14:27] <zyga> and knows which one to make and which to remove
[14:27] <zyga> (snap specific untis)
[14:27] <Son_Goku> so it needs read/write access to /etc/systemd/system
[14:27] <zyga> Son_Goku: correct
[14:27] <zyga> Son_Goku: one more denial
[14:27] <zyga> paź 30 15:25:29 fedora24 setroubleshoot[3400]: SELinux is preventing snapd from node_bind access on the tcp_socket port None. For complete SELinux messages. run sealert -l 73e31352-953f-4156-8ab0-7b67ce1db019
[14:28] <zyga> paź 30 15:25:29 fedora24 python3[3400]: SELinux is preventing snapd from node_bind access on the tcp_socket port None.
[14:28] <zyga> that's internal golang thing that probes for ipv6
[14:35] <zyga> Son_Goku: does this look ok? http://paste.ubuntu.com/23402604/
[14:35] <Son_Goku> that's fine
[14:35] <zyga> (I switched to ubuntu pastebin as the one on fedora didn't work for some reason)
[14:36] <zyga> Son_Goku: pushed
[14:36] <zyga> Son_Goku: if you fix the policy I think we can get this in now :)
[14:36] <zyga> Son_Goku: can I help you in any way?
[14:39] <Son_Goku> hmm
[14:39] <Son_Goku> this is annoying
[14:39] <Son_Goku> I may have to grant access to unlabeled files because snaps don't have the label applied to them :(
[14:40] <zyga> Son_Goku: can you be more specifc?
[14:40] <zyga> Son_Goku: snapd doesn't touch (I think) snap files, just systemd units it creates, udev rules it creates and a few other similar things (dbus xml stuff)
[14:40] <zyga> Son_Goku: can those inherit the label from snapd somehow?
[14:41] <Son_Goku> not sure
[14:41] <Son_Goku> I wonder if systemd mounts can be set up to mount with a label?
[14:41] <zyga> Son_Goku: maybe, let me look
[14:42] <zyga> Son_Goku: nothing in systemd.mount
[14:42] <zyga> er, systemd.unit
[14:47] <zyga> morphis: hey
[14:47] <zyga> morphis: are you working today?
[14:50]  * zyga inspects failures on f26 and ppc64
[14:51] <zyga> DEBUG util.py:421:  Error: nothing provides kernel-headers >= 2.2.1 needed by glibc-headers-2.24.90-13.fc26.ppc64.
[14:51] <zyga> DEBUG util.py:421:  nothing provides kernel-headers >= 2.2.1 needed by glibc-headers-2.24.90-13.fc26.ppc64
[14:51] <zyga> looks like something that's more general
[14:53] <zyga> Son_Goku: I'll step outside to have a snack
[16:01] <Son_Goku> urgh
[16:01] <Son_Goku> Ubuntu Core does way too much
[17:13] <linuxhiker> I am trying to figure out how to get the following to happen: ./configure; make world
[17:14] <linuxhiker> I have configure working just fine
[17:14] <linuxhiker> and make without world just fine
[17:14] <linuxhiker> I figured out that if I use the make plugin, I can use a parent make file that can call world
[17:14] <linuxhiker> but that is outside of the source tree as it is part of the snapcraft build system, not the software I am actually trying to build
[17:47] <qengho> linuxhiker: Is that "configure" autoconf?
[17:49] <qengho> linuxhiker: That "world" bit seems weird. Does it have a "install" target?
[17:53] <linuxhiker> qengho: yes the configure is autoconf (that part works) and in fact the basic build works fine
[17:54] <linuxhiker> qengho: but "world" is needed to build a secondary part of the source tree that only builds with either "world" or something like make -C contrib/Makefile
[19:24] <zyga> Son_Goku: hey
[19:24] <zyga> Son_Goku: so what did you manage to do with the policy?
[19:24] <Son_Goku> I hate Ubuntu Core
[19:25] <Son_Goku> I got enough for snapd, but apparently ubuntu-core wants to stick its fingers everywhere
[19:26] <zyga> Son_Goku: can you be more specific and less dramatic
[19:26] <Son_Goku> also, is ~/snap a directory created by snapd?
[19:26] <zyga> indirectly, through snap run or snap-confine
[19:26] <Son_Goku> zyga, ubuntu-core installs udev rules, etc.
[19:26] <zyga> (currently both do)
[19:26] <Son_Goku> okay, so I need to define a snap_home_t
[19:26] <zyga> Son_Goku: yes, it manages the system
[19:27]  * zyga pats Son_Goku on the back
[19:27] <zyga> you can do it :)
[19:27]  * Son_Goku sighs
[19:27] <Son_Goku> also, apparently something wants to talk to NetworkManager
[19:28]  * Son_Goku is tired
[19:29] <Son_Goku> I'm taking a break from playing whack-a-mole
[19:29] <Son_Goku> zyga, are there any specific directories I need to know about for the home directory?
[19:32] <zyga> Son_Goku: no, just ~/snap


[02:27] <bigbash> nice, got myself a touchpad for $99
[02:44] <Cheesehead> bigbash: Well?  Details, man. I don't have all night.
[02:50] <bigbash> oh sorry
[02:51] <bigbash> Cheesehead, they are liquidating their stock
[02:51] <bigbash> if you have an app or academic account with hp you can get them for $99
[02:51] <Cheesehead> So you bought a touchpad that has been through a blender? Liquified?
[02:51] <bigbash> *epp
[02:51] <bigbash> haha no
[02:52] <Cheesehead> Though I turn up my nose at HP on general principles (mostly related to gouging on ink & toner)
[02:53] <bigbash> yea but can't really beat $99 plus at $15 coupon so it is $89.24 with shipping and tax
[02:53] <Cheesehead> Indeed.
[02:53] <Cheesehead> Congratulations on the shiny new toy!
[02:53] <bigbash> thanks, I picked up one for my nephew too
[02:53] <bigbash> he can watch his kid shows on it now
[03:03] <ripps> bigbash: hey, I'm back. So your talking about a series of old kernel patches... that's a bit tricky. Do you know if they still even work with a modern linux kernel? First I try to apply the patches to kernel and see if it even builds, there are tons of guides online on how to build a custom kernel. If the patches do work, you might want to contact the ubuntu-kernel team on #ubuntu-kernel on how to move this to a package.
[03:07] <bigbash> ripps, I tried to apply the kernel patches and it said it was successful but when i do /usr/src/linux and do make menuconfig the sna stuff the should be in Networking Options doesn't appear to be there
[03:09] <ripps> bigbash: kernel stuff is bit out of my reach, If the source code was supposed to just add a kernel module, I could help you setup an automatic dkms build package, but this looks like it modifies the actual kernel source, which is pretty complicated. You'd best consult someone who actually works with the kernel.
[03:10] <bigbash> ripps, ok I'll see I I can get someone from kernel to help.  Seems the guy doesn't want to be be reached either. locked twitter, locked fb, etc.
[03:11] <bigbash> it is like from 2000 so
[03:12] <ripps> the source code to the linux kernel has changed a great deal in the last decade, I don't know that the patches would even work with it. They might patch without issue, but that doesn't mean the kernel will even use the code when compiled.
[03:16] <bigbash> hmm it requires kernel 2.4 or over
[13:20] <lostson> good morning all
[15:42] <Cheesehead> Brainstorm Triage Jam announcement: http://loco.ubuntu.com/events/ubuntu-us-wisconsin/1177/detail/
[15:47] <Cheesehead> bigbash: Wisconsin Bug Jam announcement: http://loco.ubuntu.com/events/ubuntu-us-wisconsin/1178/detail/
[17:57]  * Cheesehead looks at the clock and realizes the Madison Ubuntu Hour starts in three minutes


[03:07] <lotuspsychje> good morning
[04:36] <sem> Good night
[04:37] <sem> Insomnia
[04:40] <lotuspsychje> hey sem
[04:48] <sem> Do you think LXQt will be the 3rd desktop environment to be usable in Wayland on Ubuntu?
[04:49] <sem> I assume kde and gnome are already usable
[06:55] <guiverc> plus will it be called lxqt though??? or lwqt  (as an earlier version was referenced..)
[08:03] <PeGaSuS> UWN is not very readable on mobile devices
[08:03] <PeGaSuS> unless "reader mode" is enabled
[12:24] <mandem0110> Morning... :)
[12:53] <ogra_> PeGaSuS, there is a parallel discourse post usually, on discourse.ubuntu.com ... thats very mobile firendly ...
[12:55] <ogra_> (and the email version should be fine too, depending on your mobile mail app)
[13:41] <sem> LXQt vs LWQt would be a great way to differentiate between them
[18:13] <lotuspsychje> for those who want, tnx to JimBuntu we managed to rip a latest canonical status rss in #techrss
[18:18] <oerheks> JimBuntu 4 president!
[18:26] <JimBuntu> lolz
[23:41] <oerheks> ♥


[01:35] <nano4ever> Can anyone look at a debdiff I made for the upgrade Bug #206862 ??
[01:35] <ubot4> Launchpad bug 206862 in xsensors "New upstream version (0.60) available" [Wishlist,New] https://launchpad.net/bugs/206862
[01:38] <hggdh> nano4ever: it is a patch, not a debdiff
[01:39] <dtchen> nano4ever: is there any other possible value for num?
[01:40] <dtchen> using a switch/case there seems odd if it can only be useful for 1
[01:40] <dtchen> and, it's missing all the Debian infrastructure
[01:40] <nano4ever> oh sorry i'll upload it now
[01:40] <dtchen> (as hggdh alluded to)
[01:42] <hggdh> yeah, an if would be enough. And I, particularly, don't like a return in the middle of a switch
[01:42] <nano4ever> hggdh: alright it's uploaded
[01:47] <hggdh> nano4ever: why are you patching the autoconf files?
[01:48] <hggdh> in other words, is 0.61 the new upstream release?
[01:51] <hggdh> ooooh, we are still at 0.50 in Lucid
[01:51] <nano4ever> well the patch is from here https://lists.ubuntu.com/archives/ubuntu-motu/2008-September/004711.html
[01:51] <nano4ever> the author posted the patch but with no official change in version number
[01:52] <hggdh> thank you
[01:52] <nano4ever> I contacted him and he said that he would post some updates to xsensors but he hasn't done it yet...
[01:53] <hggdh> it would probably be a better idea to propose a new source upstream version, instead of patch 0.50 to 0.60 to 0.61
[01:53] <hggdh> the debdiff is rather big as a result
[01:53] <nano4ever> ah ok
[01:54] <nano4ever> so what's the process for making such a proposal?
[01:54] <hggdh> and -- usually -- running autoconf on package build is not viewed as a good option (I do not really know if it is run, or if the patches for the autoconf are just for completeness)
[01:55] <hggdh> nano4ever: you could download the new upstream and add your patches there
[01:55] <hggdh> this would make the debdiff much smaller, and there is no sense in carrying such a large patch if the new upstream code has it all there (except for your patch)
[01:56] <nano4ever> i just followed the directions here for the update .. https://wiki.ubuntu.com/PackagingGuide/Complete#Updating an Ubuntu Package
[01:56] <nano4ever> so are you saying that I should make a new package from upstream, then apply the author's patch as an update?
[01:57] <hggdh> yes
[01:57] <hggdh> you would have to download the source from upstream (hopefully they have a distribution tarball)
[01:58] <hggdh> because this would make life much more simpler
[01:58] <hggdh> this is, in fact, what the instructions you pointed try to say
[01:58] <hggdh> "Get the new source. Usually you would look up where the old version was downloaded from (check debian/copyright) and use that source. But again, since this is a prepared example:
[01:59] <hggdh> so we would upgrade from version 0.50 to 0.6x (whatever it is), plus the additional patch(es)
[01:59] <hggdh> but the *base* version would be 0.6x
[02:00] <hggdh> nano4ever: BTW -- thank you for working on this. I understand you may be a bit frustrated now, though
[02:00] <hggdh> nano4ever: did I explain it OK?
[02:01] <nano4ever> i'm just a bit confused. I did start on the link i gave then I skipped to "Creating a debdiff"
[02:01] <nano4ever> I dled the the newsource
[02:02] <hggdh> you were on the right track, up to diff-ing from 0.50 to 0.60 to 0.61 to you patch
[02:02] <hggdh> this is where you took a, er, misguided turn
[02:03] <nano4ever> so if I just follow the "Updating an Ubuntu Package" section and upload the dsc file, that should be enough?
[02:03] <hggdh> basically, we are -- right now -- at 0.50 (perhaps plus some patches). The new upstream is at 0.6x. So -- we upgrade the *whole* package to 0.6x
[02:03] <hggdh> which is to say, we download 0.6x, and base a new package version on it
[02:04] <hggdh> you would need the dsc plus (most probably) a diff
[02:04] <hggdh> because you will (at least) have to update the ./debian/* files
[02:05] <nano4ever> would the diff be from 0.50 to 0.60?
[02:05] <hggdh> no. The diff would be from the *current* released upstream
[02:05] <hggdh> plustd whatever patches necessary
[02:05] <hggdh> 0.50 is dead
[02:06] <nano4ever> ok, so what I'm thinking is copy over the .50 debian directory to .60, update those files, then make a .dsc and diff from the new .60 and .60.orig , is that about right?
[02:07] <nano4ever> and then after .60 is approved, patch to 0.60-0ubuntu2 with the coretemp patch..
[02:07] <hggdh> in this case, it is pretty much a *new* version, so there is no debdiff -- you will be uploading a new .orig, plus the debian packaging pieces
[02:08] <nigel_nb> hggdh: I'm going to get that ppa wiki done today :)
[02:09] <hggdh> for the last question: this, I am not sure. I personally would try to put it all together in one go, but MOTU may want different
[02:10] <hggdh> nano4ever: also, the best channel for packaging Universe is the #ubuntu-motu one
[02:10] <hggdh> nigel_nb: cool, thanks
[02:11] <hggdh> nano4ever: also, please remember the package should be built for Lucid, not Karmic
[02:11] <nano4ever> hggdh: alright thanks for the tips! also, I tried #ubuntu-motu,but got no response..
[02:12] <hggdh> nano4ever: heh. Ask, and fill yourself of patience ;-)
[02:12] <hggdh> they may delay to answer, but usually they do. Also, this is Friday night/Saturday morning on most places
[02:13] <nano4ever> ah makes sense
[02:13] <hggdh> nano4ever: again, thank you for your work on this. We *do* appreciate
[02:15] <nano4ever> thanks for the thanks :P
[02:15] <nano4ever> just trying to give back
[02:15] <hggdh> nano4ever: just one more point: we usually try very hard to use the upstream distro tarball without changes *in* it, and addtional patches separate in ./debian/patches
[02:15] <hggdh> any patches we carry create a 'delta' from upstream (i.e., a local difference). We try to maintain this delta to a minimum
[02:16] <nano4ever> gotcha, i'll keep it that in mind
[02:16] <hggdh> nano4ever: this is how I started in Ubuntu ;-) giving back what I was taking
[02:21] <hggdh> dtchen: welcome back as an official developer :-)
[02:29] <nigel_nb> hggdh: how do I know if a bug is part of publically announced testing initiative of an ubuntu team?
[02:31] <hggdh> well, if it was publicly announced...
[02:31] <hggdh> bug #?
[02:35] <nigel_nb> hggdh: making the wiki edits
[02:35] <nigel_nb> or creation
[02:35] <hggdh> oh, OK
[02:37] <hggdh> then -- we (as triagers) would have to receive a notice. This is actually a good question... perhaps we need a common place for all officially endorsed test packages as noted in
[02:37] <nigel_nb> yea a wiki
[02:38] <nigel_nb> I can offer to main a static list, if I'm able to get the announcements
[02:41] <hggdh> this is something to be formalised, I agree
[02:42] <nigel_nb> part of the agenda for the next meeting then
[02:43] <hggdh> yes -- and it will have to be discussed with the other groups
[02:43] <hggdh> meanwhile, we might go on, and assume it will be there
[02:44] <nigel_nb> yep, including the devs and motu is my best guess
[02:45] <hggdh> yes
[02:45] <nigel_nb> are there any such programs now?
[02:45] <nigel_nb> that have called for testing?
[02:52] <nigel_nb> hggdh: wifi manager in gnome is which package? gnome-net-tools?
[02:53] <nigel_nb> gnome-nettools (spelled wrong earlier)
[02:55] <hggdh> I do not know (yet). What is the name of the file?
[02:55] <nigel_nb> file?
[02:56] <nigel_nb> the entire bug report consists of "The network manager is unable to connect to hidden wireless network."
[02:56] <nigel_nb> I need to change the package and ask for more info
[02:56] <hggdh> oh
[02:56] <hggdh> network-manager
[02:57] <hggdh> and network-manager-gnome
[02:58] <hggdh> but it is probably network-manager that cannot find the AP
[02:59] <nigel_nb> okay, thank you :)
[16:05] <nperry> !info pidgin
[16:05] <ubot4> nperry: pidgin (source: pidgin): graphical multi-protocol instant messaging client for X. In component main, is optional. Version 1:2.6.2-1ubuntu7 (karmic), package size 562 kB, installed size 1784 kB
[16:05] <nperry> packages.ubuntu.com is down hrrrm
[16:19] <hggdh> sometimes it happens. It is, IIRC, a volunteer service
[18:55] <Yos> I just started having this problem for the first time: My computer is booting up into low graphics mode and I cannot change visual effects to normal or extra
[18:55] <Yos> Is this a bug?  If so, how to report it properly
[18:57] <etali> Yos, this channel is for people who are triaging bugs, rather than for support.  You'd probably get a quicker response regarding solving your problem in the #ubuntu channel
[18:58] <etali> If you want to report it as a bug, you can find help at https://help.ubuntu.com/community/ReportingBugs
[18:58] <Yos> Ok, thanks
[18:59] <etali> I hope you manage to get it sorted!
[19:53] <awardle> Can bugs in evolution be upstreamed?
[19:54] <nigel_nb> awardle: yes, it has to be upstreamed *if* it is upstream
[19:54] <awardle> where to
[19:54] <hggdh> and, for Evolution, they should
[19:54] <hggdh> http://bugzilla.gnome.org
[19:55] <nigel_nb> hggdh: upstream gnome down for you?
[19:55] <nigel_nb> I've been trying for some time
[19:55] <hggdh> will check
[19:55] <hggdh> hum
[19:55] <hggdh> not looking good
[19:56] <awardle> bugzilla.gnome.org seems to be down
[19:56] <nigel_nb> unfortunately, true :(
[19:57] <hggdh> yes. I just asked about it on their bug channel
[19:57] <hggdh> now we wait, Saturday and all of that
[19:57] <nigel_nb> yea, plus holiday season
[19:58] <awardle> Could someone set bug 495936 to low
[19:58] <ubot4> Launchpad bug 495936 in evolution "Feature request: better indication of signed and/or encrypted email" [Undecided,Confirmed] https://launchpad.net/bugs/495936
[19:58] <nperry> Right my first request for this evening, time to eat my tea
[20:00] <hggdh> awardle: I actually marked it WishList. Thank you
[20:01] <hggdh> nperry: you *eat* tea?
[20:01] <nigel_nb> nperry: was about to ask, but hggdh already asked
[20:02] <hggdh> just curious. Different people, different mores, etc
[20:02] <nigel_nb> probably eating the tea cup too?
[20:04] <awardle> tea in England can also mean dinner
[20:04] <nigel_nb> awardle: dinner or supper?
[20:04] <hggdh> ah
[20:04] <nperry> hggdh: tea aka dinner
[20:05] <nigel_nb> early dinner then
[20:05] <nperry> its 8pm
[20:05] <hggdh> well, my grandmother-in-law used to ask us if we wanted a lemonade of coke, or orange, or whatever
[20:05] <nperry> so late really
[20:06] <hggdh> indeed. teatime is gone
[20:06] <hggdh> brb. Lunch time at my TZ.
[20:17] <nperry> Wow that was nice back to my learning to triage :)
[20:39] <hggdh> nperry: just ask on any doubt, and we will try to answer
[20:41] <hggdh> OK. bugzilla.gnome.org is down for the weekend (I *should* have read the annoucement...)
[20:46] <hggdh> for all, courtesy of the extremely nice bugmeister for gnme: http://permalink.gmane.org/gmane.comp.gnome.devel.announce/67
[20:47] <nigel_nb> oh great, I was hoping to work on the git.gnome this weekend, so thats gone now
[20:47] <hggdh> :-)
[21:01] <nperry> hggdh: This evening theres alot of bugs from email, for packages syncs for example 495994 - the right people have been subscribed, do we need to confirm or marked as triaged?
[21:01] <nperry> bug 495994 **
[21:01] <ubot4> Launchpad bug 495994 in libhamcrest-java "Sync libhamcrest-java 1.1-4 (main) from Debian testing (main)" [Wishlist,New] https://launchpad.net/bugs/495994
[21:02] <hggdh> looking. But usually, workflow request (sync/merge, and others) are outside triaging scope
[21:03] <hggdh> in this case, even more due to the OR -- he knows what has to be done
[21:03] <hggdh> so, no, do not touch them
[21:03] <nperry> Ok, just had to double check if New was the right status
[21:04] <nperry> Thanks :)
[21:04] <hggdh> welcome
[21:05] <nigel_nb> hggdh: frustrating to triage today with no upstream :(
[21:06] <hggdh> I know. But we can hope it will back earlier (this is their intention)
[21:08] <nigel_nb> yea
[21:09] <nigel_nb> I'm not triaging today, cant leave tasks undone, I'd rather skip 2 days and go all out from monday
[21:10] <nperry> Hummm debian bug tracker playing up
[21:11] <nperry> Ah working now :)
[21:18] <nperry> hggdh: fsys state-tarfile returned error exit 2 -- Could this be a bad download?
[21:18] <hggdh> nperry: could, but give me a pastebin
[21:19] <nperry> bug 495992
[21:19] <ubot4> Launchpad bug 495992 in kdebase-runtime "package kde-icons-oxygen 4:4.2.2-0ubuntu1 failed to install/upgrade: subprocess dpkg-deb - fsys state-tarfile returned error exit 2" [Undecided,New] https://launchpad.net/bugs/495992
[21:19] <nperry> Terminallog - Never seen the error before, but just to be sure before i convert to question and solve issue
[21:21] <yofel> hm, what was 'broken pipe' again?
[21:21] <hggdh> nperry: does not sound like bad download
[21:22] <hggdh> yofel: a subprocess had a pipe to another subprocess, and this pipe vanished (one of the subp died, in this case)
[21:22] <yofel> hggdh: ah yes, thx
[21:26] <hggdh> nperry: you can check, nevertheless, by downloading the package to a temp dir, then manually running 'dpkg-deb --fsys-tarfile|tar -tv'
[21:26] <hggdh> er
[21:26] <hggdh> dpkg-deb --fsys-tarfile <package> | tar -tv
[21:27] <nperry> meh packages.ubuntu.com is down :/
[21:28] <hggdh> nperry: you can drill down to the specific package from here: https://bugs.edge.launchpad.net/ubuntu/+source/kdebase-runtime
[21:29] <hggdh> select the Overview link at the headers, and then go to the correct distro version
[21:30] <hggdh> for example, I ended up here: https://edge.launchpad.net/~ubuntu-security/+archive/ppa/+build/1388105
[21:31] <hggdh> oops. Wrong drill down, the OR package is at 0ubuntu1, the one I am showing is at 0ubuntu1-1
[21:33] <nperry> Thats odd, why isnt downloading OR 1-1
[21:35] <hggdh> no, it is, the bug title is wrong
[21:36] <hggdh> look at the description, and at the end of the log (I also based myself on the title)
[21:37] <hggdh> dpkg: erro processando /var/cache/apt/archives/kde-icons-oxygen_4%3a4.2.2-0ubuntu1.1_all.deb (--unpack):
[21:37] <hggdh> hum. pt_BR, BTW
[21:39] <nperry> Indeed updated that, else i'll forget :)
[21:40] <nperry> Right the .deb seems ok
[21:52] <Laibsch> Hi
[21:52] <Laibsch> How do I search for bugs that are marked as fixed in the current development release but nominated for hardy or karmic?
[21:53] <hggdh> Laibsch: good question, let me try to find out
[21:55] <Laibsch> https://bugs.launchpad.net/ubuntu/hardy/+nominations
[21:55] <hggdh> heh, there you go
[21:55] <Laibsch> completely non-obivous, but google helps
[21:56] <Laibsch> and unfortunately, that includes yet to be fixed bugs
[21:57] <nperry> hggdh: I believe bug 495724 is ready to be set as triaged with importance medium
[21:57] <ubot4> Launchpad bug 495724 in b43-fwcutter "Broadcom 4306( b43-fwcutter) Wireless can't connect to Access Points WEP/WPA/Unsecure." [Undecided,Incomplete] https://launchpad.net/bugs/495724
[21:57] <nperry> nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed - handsake doesn't seem to be happening
[21:58] <nperry> So I think its a network card/driver related problem - as ndiswrapper driver fixes issue
[21:59] <hggdh> Laibsch: trying "advanced search" under +nominations should get there -- then select fix released/committed
[21:59] <Laibsch> Just did that
[21:59] <Laibsch> Got a timeout error a couple of times
[21:59] <Laibsch> but it seems to be working now

[21:59] <hggdh> ah, OK
[22:01] <Laibsch> who can change the status for nominations?
[22:02] <Laibsch> I think bug 129407 can be rejected as invalid for example
[22:02] <ubot4> Launchpad bug 129407 in linux-ubuntu-modules-2.6.22 "r818x.ko missing in linux-ubuntu-modules-2.6.22-8-generic" [Medium,Fix released] https://launchpad.net/bugs/129407
[22:02] <hggdh> Laibsch: for nominations, only the maintainers can refuse it
[22:02] <Laibsch> I see
[22:03] <Laibsch> but wait
[22:03] <Laibsch> Ubuntu has no Maintainer per se
[22:03] <hggdh> nperry: it would be good to also have the dmesg, and a 'lspci' output
[22:03] <Laibsch> It's a team effort
[22:03] <hggdh> Laibsch: getting there
[22:04] <hggdh> linux *does* have maintainers
[22:04] <hggdh> (I mean the package)
[22:05] <hggdh> the kernel team, specifically
[22:06] <nperry> hggdh: Full dmesg?
[22:07] <hggdh> nperry: yes, better more than less data
[22:15] <Laibsch> who would be capable of closing the hardy task for bug 178289?
[22:15] <ubot4> Launchpad bug 178289 in ubuntu "Absolutely no keyboard input on fresh hardy alpha 2 installation." [Undecided,Fix released] https://launchpad.net/bugs/178289
[22:15] <Laibsch> I'm a member of "Ubuntu bugs", yet I don't seem to have the power to do it
[22:18] <nigel_nb> Laibsch: I believe only Ubuntu Drivers can close that task
[22:18] <nperry> hggdh: Is there an upstream for b43-fwcutter
[22:18] <hggdh> Laibsch: first of all, most of the times we see a bug against Ubuntu, this is because the OR did not know which package to set it against
[22:19] <Laibsch> ?
[22:19] <Laibsch> hggdh: Were you really talking to me?
[22:19] <hggdh> also, bugsquad/bug-control does not have authority to close nominations
[22:19] <nigel_nb> hggdh: I think pedro someone from QA team can.....
[22:20] <nigel_nb> pedro, or someone else from the QA team
[22:20] <hggdh> Laibsch: yes -- that bug was set to Ubuntu because the OR did not know where to put it (neither do I, for taht matter)
[22:20] <hggdh> also, I reset it to INVALID, since there is no "fix" (apart from a probable bad hardware)
[22:21] <hggdh> nigel_nb: probably
[22:21] <nigel_nb> anyway, invalid is fine ;)
[22:21] <nperry> If it was just in livecd it would be in ubiquity but if it was there when booted it would be xorg - right?
[22:22] <hggdh> Laibsch: nevertheless, you are pointing to a nice issue -- the forgotten nominations. Something should, clearly, be done there
[22:22] <hggdh> nperry: it *might* be X, but the OR stated the keyboard was non-functional also during boot
[22:23] <hggdh> so this would -- being software -- be more related to the kernel
[22:23] <Laibsch> hggdh: I thought you were talking about a logical OR (such as the one used in google searches).  My abbreviation for your OR is OP. ;-)
[22:23]  * Laibsch has been using Usenet a lot at dial-up times
[22:24] <hggdh> Laibsch: sorry. To be clear -- OR == Original Reporter; for me, OP == Original Poster (which, perhaps wrongly, I tend to use only on mailists)
[22:24] <Laibsch> yeah, I understood that now
[22:25] <hggdh> Laibsch: my fault, nevertheless. I should have been less lazy
[22:25] <Laibsch> nah, don't worry
[22:26] <Laibsch> I guess it would make sense to have a "Hardy driver", "$release driver" for past releases
[22:26] <Laibsch> I'm interested in fixing problems in karmic and hardy
[22:26] <Laibsch> Where should I raise this suggestion?
[22:26] <hggdh> something like that, yes. I am going to raise this on next bugsquad/control meeting
[22:27] <hggdh> Laibsch: a good place would be the devel-discuss and bugcontrol mailing lists
[22:27] <dtchen> bdmurray: 464612 was a grub bug anyhow.
[22:27] <Laibsch> hggdh: I don't like to subscribe to yet another mailing list
[22:27] <hggdh> :-)
[22:27] <Laibsch> when is that meeting going to be held?
[22:27] <Laibsch> I suppose it's being done in IRC?
[22:27] <hggdh> first tuesday of every month, here
[22:28] <hggdh> time... I *think* it is 1600Z
[22:29] <hggdh> Laibsch: https://wiki.ubuntu.com/BugSquad/Meeting
[22:29] <hggdh> so, yes, 1600Z
[22:29] <hggdh> 16:00 UTC, actually
[22:29] <Laibsch> that's quite some time out
[22:30] <hggdh> yes, this is why I suggested the MLs
[22:30] <Laibsch> And I'll likely be without internet for the next one
[22:30] <Laibsch> 12th, not the 5th?
[22:30] <Laibsch> that's probably doable for me
[22:30] <hggdh> send it to the bugsquad ML (or bugcontrol, or devel-discuss)
[22:31] <hggdh> oh, I was wrong, it is the second Tuesday, not the first
[22:34] <Laibsch> please finishi editing that page ;-)
[22:34] <hggdh> anyway, I just added an additional topic for next meeting
[22:34] <hggdh> just did
[22:34] <hggdh> :-)
[22:35] <Laibsch> I would not call it pollution
[22:35] <Laibsch> the nominations are a great way to alert the right people that something needs fixing in an older release
[22:35] <Laibsch> ... if used properly
[22:35] <hggdh> I went for the kill, Laibsch. Nominations are good, but if they are not acted on, they just pollute
[22:36] <hggdh> I all in favour of them but -- like your bug example -- they must either be accepted or rejected
[22:38] <Laibsch> what's the alternative?
[22:38] <Laibsch> bugs are marked as fixed when the fix is in release+1
[22:38] <Laibsch> and I think that makes sense
[22:39] <Laibsch> As I said, I'd be willing to comb through bugs for hardy and karmic
[22:39] <Laibsch> and there aren't that many to be overwhelming
[22:41] <hggdh> for those fixed, yes
[22:53] <nperry>   hggdh Could i add to the agenda the ammount of Incomplete bugs which havent had a reply for a good couple of months/years - I know they don't count towards any stats but there is alot of them :)
[22:55] <yofel> nperry: this is a good start for a statistic: https://bugs.edge.launchpad.net/ubuntu/+expirable-bugs
[22:58] <nperry> Is there a magical time for it to be set as invaild? Or has it got to be done manually?
[22:58] <hggdh> nperry: you can, but we already discussed it
[22:58] <hggdh> currently dropping for expiry has been disabled for Ubuntu bugs
[22:58] <hggdh> it would be -- by default -- 60 days
[22:59] <nperry> If its already been discussed I wont do :)
[22:59] <hggdh> genrically, anyone can add a topic for the meeting (but should also be present to explain)
[22:59] <yofel> nperry: the list I gave you are the bugs that would already be invalid if the feature was turned on
[23:00] <hggdh> it was discussed on UDS, IIRC
[23:01] <nperry> Is there any remote log of this?
[23:02] <hggdh> of waht was noted down, yes, the blueprints
[23:02] <hggdh> I do not remember if the session was videotaped, though
[23:03]  * nperry going to look in gobby :)
[23:07] <nperry> hggdh: bug 495724 files have now been attached by OR
[23:07] <ubot4> Launchpad bug 495724 in b43-fwcutter "Broadcom 4306( b43-fwcutter) Wireless can't connect to Access Points WEP/WPA/Unsecure." [Undecided,Incomplete] https://launchpad.net/bugs/495724
[23:10] <nperry> direct probes are failing.. now thats threw me
[23:11] <hggdh> I have been off the BCM world for a while, so I am not sure how things are not. I will mark it triaged
[23:15] <hggdh> done
[23:16] <nperry> Thankyou hggdh :)
[23:39] <Laibsch> hggdh: I just received a comment from Steve Langasek that indeed the feature is not used because signal-to-noise is too low.  To improve that I think that making nominations for a release possibly only after a ticket has been closed as fix released would be a good idea.
[23:39] <Laibsch> what do you think about this suggestion?
[23:40] <micahg> Laibsch: that's the only time it's possible for anything to be done about it anyways
[23:40] <Laibsch> exactly
[23:40] <Laibsch> and it would decrease the noise considerably, I think
[23:46] <micahg> bdmurray: can you bump the ff version in the                 firefox-lp-improvements package to 3.6.*?
[23:54] <hggdh> Laibsch: good idea, but willrequire lp changes
[23:55] <micahg> hggdh: you think it should be discussed at the meeting before filing a bug?
[23:55] <hggdh> I think it should be discussed by all, yes -- bug-control/squad and devel
[23:56] <hggdh> since I myself do not approve/reject, I am unsure of all possible impacts


[06:40] <prexium01> Hey all.
[17:23] <tyche> I've got a question about a page on the edubuntu wiki.  Is someone available who could help me?
[17:25] <tyche> highvoltage: PING
[17:32] <tyche> ogra: PING
[20:07] <foka> tyche, Hi
[20:09] <foka> tyche, I don't know if I can help you or not, but feel free to post your question here
[20:34] <highvoltage> tyche: PONG
[21:00] <tyche> highvoltage: I also sent you an email.  Basically, my question is "what is an Arizona Team page doing on your wiki?":  https://wiki.edubuntu.org/ArizonaTeam/Meetings/08August03
[21:29] <highvoltage> tyche: ah, the edubuntu wiki and the ubuntu wiki is the same thing
[21:30] <highvoltage> tyche: wiki.edubuntu.org is just wiki.ubuntu.com with another theme
[21:30] <highvoltage> tyche: you'll notice the same for the kubuntu wiki :)
[23:25] <tyche> highvoltage: Interesting.  Thankyou for the information.