[08:42] <lool> seb128: Yeah, it could be the wm, but I have no idea yet
[08:42] <seb128> lool: what wm do you use?
[08:43] <lool> maximus I think
[08:43] <lool> err no matchbox
[08:43] <lool> maximus is on the other image
[08:44] <seb128> lool: since nobody reported a such bug on ubuntu I would tend to blame your wm there
[08:45] <seb128> lool: gnome-keyring set the correct hint for the dialog
[08:52] <lool> Makes sense
[08:54] <lool> reassigned
[08:55] <seb128> thanks
[09:23] <didrocks> morning :)
[09:27] <seb128> lut didrocks
[09:27] <seb128> didrocks: tu sais où est huats?
[09:28] <didrocks> seb128: non, il a terminé tard hier, il lui arrive parfois d'être au boulot à 10h40
[09:28] <seb128> ok
[09:28] <didrocks> seb128: si c'est vraiment important, je peux lui tél
[09:28] <seb128> non, j'vais corrigé l'erreur dans sa mise à jour moi même et uploader
[09:29] <didrocks> oki
[09:40] <seb128> huats: lut
[09:40] <huats> hello seb128 :)
[09:41] <huats> thanks for the various sponsoring
[09:41] <huats> :)
[09:41] <seb128> huats: you're welcome, I'm just fixing your yelp update because you were not around and that needs to be updated today
[09:42] <seb128> huats: you updated lot of translations directly in the source too
[09:42] <seb128> huats: is that wanted?
[09:43] <huats> seb128: not simply in the patch ?
[09:43] <huats> because if not, that was a mistake :(
[09:43] <huats> and I am sorry about that ...
[09:43] <huats> :(
[09:43] <seb128> huats: that's alright
[09:44] <seb128> huats: debdiff between the current dsc and your update lists a bunch of files changes and not only the debian directory
[09:44] <huats> pfff :(
[09:44] <huats> I shold have triple checked that...
[09:44] <huats> s/shold/should/
[09:44] <seb128> huats: debdiff | diffstat is useful ;-)
[09:45] <huats> I will remember that, I was checking by hand...
[09:45] <seb128> huats: btw not sure if that's you I told the other day but better to attach a debdiff for new revisions than diff.gz and dsc
[09:45] <davmor2> seb128: whose the best person to talk to about tracking down a regression in bluetooth-applet?
[09:45] <huats> seb128: that me
[09:45] <huats> that was me, but it was after that I think :)
[09:45] <seb128> davmor2: whoever worked on the bluez transition
[09:46] <seb128> huats: ok
[09:46] <crevette> davmor2, superm1 for instance
[09:47] <crevette> he is on #ubuntu-mobile
[09:48] <davmor2> thanks :)
[13:16] <Laney> mvo: What is the fate of gnome-terminal?
[13:18] <ember> oblivion!
[13:26] <Laney> :(
[13:30] <lool> seb128: How is it going with release stuff?
[13:31] <seb128> lool: you want to tackle some bug? ;-) it's going mostly ok, nothing critical but some annoying bugs still
[13:34] <lool> seb128: Nah, just a quick health check
[13:34] <seb128> lool: no serious issue
[13:34] <lool> Great
[13:36] <ember> seb128: are you able to sync keys with seahorse?
[13:37] <seb128> no clue
[13:37] <seb128> I never tried to sync key
[13:37] <ember> can you test it out?
[13:38] <seb128> not sure what the key syncing thing is doing but that looks something I don't especiall want to try no
[13:38] <seb128> I don't want random key changes
[13:39] <seb128> there is likely some other users here who are wanting to try that though
[13:39] <ember> never been able to use that thou, it keeps crashing since 2.23.x
[13:43] <Laney> ember: How do I get the option to not be disabled?
[13:44] <Laney> Oh, I got it
[13:44] <Laney> yes, crashed
[17:38] <glatzor> evening mvo
[17:39] <glatzor> mvo, have you already booked a flight?
[17:39] <glatzor> mvo, matt from the booking office suggested me to contact you
[17:40] <glatzor> mvo, I would takt the flight from london heathrow to sf at thursday 10:25 with united airlines
[19:39] <mvo> no mpt?
[19:39] <mvo> hmm
[20:01]  * lool waves 'WE
[20:07] <mvo> bye lool
[21:15] <mvo> Laney: hello! are you around?


[03:40] <guiverc> I've confirmed @Leokolb's issue with https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975393 ... How up-to-date is our calamares?   Isn't what we have ~up-to-date thus I can go straight upstream with this issue?  (I mean github/calamares not debian-unstable)
[03:44] <guiverc> teward  [you're a DM :) so picking on you if you have time]  How can I really know what 'upstream relase/update standards 4.6.1' relates to?   ie. https://metadata.ftp-master.debian.org/changelogs//main/c/calamares/calamares_3.2.58-1_changelog   is there somewhere I can look
[03:45] <teward> "Update standards version to 4.6.1" <-- version of the Debain Packaging Policy
[03:45] <teward> https://www.debian.org/doc/debian-policy/
[03:45] <teward> s/Packaging Policy/Policy/
[03:45] <teward> https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-6-1
[03:45] <guiverc> :) on packaging policy; thanks alas maybe should have remembered that :(
[03:46] <teward> guiverc: basically, the core Debian Policy gets revised here and there
[03:46] <teward> so "update standards" in a package means updating the packaging standards to the Debian Policy for packaging of that standards version
[03:46] <guiverc> yeah I see emails on that b/c of #ubuntu-publicity ML etc I'm on
[03:46] <guiverc> s/#ubuntu/#debian  ^
[03:48] <teward> guiverc: yep, welcome to my world of packaging policy :P
[03:53]  * guiverc noted a 'temporary/acting' has been added to one of your hats...  elections such fun (not!)    .. boards, policies - I'm glad I don't have to reside in that world..
 guiverc I think there might be a very recent hot fix point release upstream that addresses the issue.
[11:28] <guiverc> yep you were right @kc2bez
[11:28]  * guiverc looked and didn't find it


[12:41] <troy_s> What now.
[12:41] <Schalken> where is all the feisty artwork in the wiki?
[12:41] <troy_s> It isn't.
[12:42] <Schalken> is it anywhere?
[12:43] <troy_s> No.
[12:43] <Schalken> humph :\
[12:43] <troy_s> Well aside from running a chroot, vmware-player, or like ap.
[12:43] <troy_s> Why do you want it?
[12:44] <Schalken> just wanted to see how it was going
[12:44] <Schalken> if at all
[12:44] <troy_s> It is pretty much done, with some small movements along the way I am sure.
[12:45] <Schalken> is there a place i can see? (other than by upgrading)
[12:45] <troy_s> Probably not.
[12:45] <troy_s> Use vmwareplayer
[12:45] <troy_s> It is relatively painless...
[12:46] <troy_s> Seeing it isn't a huge deal though.
[12:46] <troy_s> As (thankfully) the opinions won't matter.
[12:46] <troy_s> Otherwise it just opens up a silly bikeshed of silly opinions.
[12:47] <Schalken> well im actually in opensuse atm
[12:47] <troy_s> Great.  Then don't worry about it.
[12:47] <Schalken> lol
[01:32] <kwwii> troy_s: hey man, fell asleep, sorry
[01:32] <kwwii> I guess it is high time for me to send an email to the list ;-)
[01:33] <kwwii> woke up after having bad dreams..my mind knows when "I've got mail" it seems
[01:35] <kwwii> troy_s: I'm putting an email together for the art list - will send it tomorrow morning
[01:43] <troy_s> kwwii sure...
[01:43] <troy_s> it doesn't really matter
[01:43] <troy_s> it's not like it is up for discussion etc...
[01:44] <kwwii> actually, i want it to be
[01:44] <kwwii> it is up for discussion within bounds
[01:44] <kwwii> that would help us prove how usefull we can be
[01:52] <kwwii> anyway, going on 2am here
[01:53] <kwwii> time for sleep (again)
[01:55] <troy_s> kwwii I see your point.
[01:56] <troy_s> Problem is, it can open up a can of bikeshed that is really worthless, unless you lay in some serious
[01:56] <troy_s> and I mean _serious_ ground rules.
[01:56] <kwwii> well, that is why I want to start writing an email today and send it tomorrow :p
[01:56] <kwwii> (and ask the opinions of you and other in the know first)
[01:56] <troy_s> Did you make a decision on palette concepts yet?
[01:57] <troy_s> I think we could do a 'hunt and gather' the stinky colours in the icons presently, which is far from ideal but...
[01:57] <kwwii> I've been playing around with them...not sure exactly in which direction to go yet
[01:57] <troy_s> Yeah ok...
[01:57] <troy_s> If you make a decision, it might be nice to actually bring the icons into line...
[01:57] <kwwii> definitely
[01:58] <troy_s> (assuming you keep the tan as the root, i am pretty sure we could find a tone that works that is close to the existing colours...)
[01:58] <troy_s> a very easy project really, assuming you can figure out a palette base you like.
[01:58] <kwwii> yeah, I think the tan is pretty much default now
[01:58] <troy_s> Well yah... I am not suggesting dumping the tan
[01:58] <troy_s> But as you could see, you have quite a few options
[01:58] <kwwii> well, part of this was a discussion that I started with Jane about how much we can change the official logo colors for use on screen
[01:59] <troy_s> even within locking the tan as say, a 60% 'feel' color
[01:59] <kwwii> trying to cover my ass before I leap
[01:59] <troy_s> Jane is rather useless
[01:59] <troy_s> considering that it is sab's call.
[01:59] <troy_s> (i know your contract probably says jane though)
[01:59] <kwwii> actually I was told to do it through her (and I have some experience working with her)
[01:59] <kwwii> so I need to get her to nod her head once
[01:59] <troy_s> _and_ considering that the other 'heads of state' all sit idly by whilst the design issues amass more and more problems.
[01:59] <troy_s> absolutely.
[02:00] <kwwii> the more I do the more I see how much they are leaving this stuff to me
[02:00] <troy_s> It just seems that inevitably, sab will pull the pin.
[02:00] <kwwii> probably so that if I make the mistakes it comes back on me
[02:00] <kwwii> which is fine by me ;-)
[02:00] <troy_s> Well mistakes are... relative.
[02:00] <troy_s> And, in an ideal world, expected.
[02:00] <kwwii> yepp, it is the whole picture that is more important this time around
[02:00] <troy_s> As one could argue that all of the bloody buntu's are a mistake as of now.
[02:00] <troy_s> lol
[02:01] <troy_s> They certainly all suffer from the same issues fundamentally.
[02:01] <kwwii> the best/worst part of this cycle is that I have a long way to go and a short time to get there, so nobody can expect the world
[02:01] <troy_s> I think part of that is rooted in the stinking GNOME/KDE politics.
[02:01] <kwwii> that is true, although I call it religion, not politics
[02:01] <kwwii> ;-)
[02:01] <troy_s> Well... yes it is worse than politics.
[02:02] <kwwii> it is not founded on any real intelligent reasoning
[02:02] <troy_s> In politics at least you can assassinate people and have it die.
[02:02] <kwwii> as we are a distro we can go around that though
[02:02] <troy_s> Nope.
[02:02] <troy_s> Sort of...
[02:02] <troy_s> I was speaking with an unnamed person today
[02:02] <troy_s> and I can tell you, it roots deep.
[02:02] <troy_s> Everyone is quite gutless
[02:03] <troy_s> No one wants to make a decision and simply turns things into an 'upstream' issue.
[02:03] <kwwii> dude, the upstream themeing discussion is a no-go
[02:03] <troy_s> ???
[02:03] <kwwii> there is little chance that gnome and kde are going to ever want to be the same
[02:03] <troy_s> No when speaking of the 'larger' design issues.
[02:03] <troy_s> God no
[02:03] <troy_s> That's the point
[02:04] <troy_s> But reality, the end user (lets assume say, someone in the 18-36 region with no FOSS experience) gives a shit about the politics -- they just get a desktop and they either think it stinks or doesn't.
[02:04] <troy_s> It has very little to do with politics.
[02:04] <kwwii> if you look at what we have done with the oxygen icons you will see that we have put thought into working well with gnome (tango)
[02:04] <troy_s> for better or worse
[02:04] <kwwii> sure, for the end user the whole thing is turned completely around
[02:05] <troy_s> I find it difficult to reconcile anything universal with my background.
[02:05] <troy_s> The terms simply doesn't exist, so designing for that myth is absolutely folly.
[02:05] <troy_s> It inherently will involve aesthetics.
[02:05] <troy_s> And that means a very distinct 'twist' on a concept.
[02:06] <kwwii> yeah
[02:07] <kwwii> on another topic, do you know how to install feisty in vmware?
[02:07] <troy_s> yes
[02:07] <troy_s> very simple
[02:07] <troy_s> first
[02:07] <troy_s> sudo aptitude install vmware-player
[02:07] <troy_s> 2nd make a vmx set
[02:08] <troy_s> www.easyvmx.com i think
[02:08] <kwwii> I have a vmware server running
[02:08] <troy_s> will work for you
[02:08] <troy_s> third, download install iso and install it.
[02:08] <kwwii> ahh, cool, that is what I was looking for
[02:08] <troy_s> ;)
[02:08] <kwwii> well, the installer borks everytime I get past the keyboard stuff
[02:08] <kwwii> it just sits there
[02:08] <kwwii> on the console there is some complaint about the hard drive
[02:09] <kwwii> hehe, since I updated my kernel it now seems to work ::-)
[02:09] <kwwii> sorry for the bother
[02:11] <kwwii> time for bed now though
[02:16] <kwwii> see you tomorrow
[02:44] <coz_> evening all
[02:44] <the_fool> hello
[02:44] <coz_> hey guy:)
[02:45] <the_fool> :)
[02:45] <coz_> I don't know eeryon who comes here but ar eyou new?
[02:45] <the_fool> yep
[02:45] <coz_> well then welcome :)
[02:45] <the_fool> thnaks
[02:45] <the_fool> brb
[02:46] <coz_> so have you come to discuss , or show work, or just hang out /
[06:56] <darkmatter> hiya klepas
[07:13] <klepas> hey darkmatter
[07:13] <klepas> how's the cold?
[07:15] <darkmatter> getting better
[07:15] <darkmatter> now I can work on glory more and catch up on bashing out the toolkit foundations fore my soon-to-start code project
[07:36] <klepas> :-)
[06:19] <troy_s> kwwii
[07:03] <kwwii> re
[07:04] <troy_s> kwwii are you still interested in that GDM?
[07:04] <kwwii> troy_s: definitely
[07:04] <troy_s> it seems like your balls are pinched for time, so I figured I would ask about it before i pushed a branch.
[07:04] <kwwii> lol
[07:05] <kwwii> please do, I'll work on gdm this week, so I can start from your branch
[07:05] <troy_s> there are actually a few 'bugs' in the code too.
[07:05] <troy_s> as in finite set sizes for the entry box
[07:05] <troy_s> etc
[07:05] <troy_s> hard coded messes
[07:05] <kwwii> nasty
[07:05] <troy_s> ideally, those would be 100% scalable
[07:05] <troy_s> they are easy to fix, but the 'fix' might pop up some new features ;)
[07:05] <kwwii> I looked into it a bit and wondered exactly which values are really used and which are ignored
[07:05] <troy_s> i was looking into the german word wrap issue
[07:06] <troy_s> but i can't seem to see a way to adjust for wrappage
[07:06] <troy_s> i can clip
[07:06] <troy_s> but no wrap
[07:06] <troy_s> well there are two portions of stanza that are completely there just to take up space
[07:06] <kwwii> yeah, there is no intelligent text engine for that
[07:06] <troy_s> i'll try to get the fixes in and push a branch.
[07:06] <kwwii> excellent, thanks
[07:06] <troy_s> kwwii: it is an upstream issue
[07:06] <troy_s> and wrapping
[07:06] <troy_s> would adjust the 'box' vars which adjusts composition etc.
[07:07] <troy_s> kwwii: Have you heard of UIML?
[07:07] <kwwii> I'll start filing bugs against gdm with my kde.org account :p
[07:07] <kwwii> nope, never heard of it
[07:07] <troy_s> Look into it... it is quite interesting in terms of designing towards the future.
[07:07] <troy_s> it is a universal interface markup language
[07:07] <kwwii> wow, cool
[07:07] <troy_s> that makes no assumptions about how something is to be displayed
[07:07] <kwwii> sounds interesting
[07:08] <troy_s> it is rather interesting because it tackles all of the accessibility issues/power user issues/etc
[07:08] <troy_s> with one broad stroke -- preventing app designers from 'locking' their interfaces into a particular layout
[07:08] <troy_s> and it provides XML for a specialized interface designer to tweak
[07:08] <troy_s> rather interesting on a side note...
[07:08] <troy_s> just reminded me from dicking with GDM
[07:09] <kwwii> killer
[07:10] <troy_s> have a peek at it... it has some good ideas in it.
[07:10] <kwwii> I will
[07:10] <troy_s> so
[07:11] <troy_s> what i was going to say
[07:11] <troy_s> is push your last branch into gdm with your changes
[07:11] <troy_s> and let me pull fresh off of it
[07:11] <troy_s> so that we don't get too worried about merges
[07:11] <kwwii> until now I have no changes ;-)
[07:11] <troy_s> (simple incremental makes it easier as you can imagine)
[07:11] <troy_s> okie
[07:11] <troy_s> i thought you pushed new art for the gdm
[07:11] <kwwii> going to add a new logo when I work on the version from the usplash
[07:11] <troy_s> logo wise etc.
[07:11] <troy_s> ahh.
[07:11] <kwwii> etienne had some great comments
[07:11] <troy_s> ok no guarantees, but I will try to clean it up now or so
[07:12] <kwwii> great
[07:12] <troy_s> echoed the nerf the white
[07:12] <troy_s> et is a very clever guy
[07:12] <troy_s> who_'s original CoF has some very fresh 'fruity' colours in the grads which really work.
[07:12] <troy_s> if you could somehow recapture that, i think it would solve the white pink issues.
[07:13] <kwwii> yeah, the pink seems a bit much to me
[07:15] <troy_s> it is obviously unintentional
[07:15] <troy_s> just a byproduct of the classic white gloss
[07:15] <kwwii> yeah, it comes from the palette
[07:15] <kwwii> I had an idea about the bg though
[07:16] <kwwii> making a pic with a gradient as it is now, but not scale the pic and put it on a solid color bg (with the same color as the outside of the gradient
[07:16] <troy_s> perhaps cheating the hue on the gloss might work -- instead of value only (ie adding white translucency)
[07:16] <kwwii> that way people with large screens would not notice that the pic does not fit
[07:16] <troy_s> interesting idea
[07:16] <troy_s> if it is svg though, zoom will take care of that without breaking it down
[07:17] <kwwii> true
[07:17] <troy_s> funny you should mention that, the current WIP i have now
[07:17] <kwwii> not sure about using an svg though
[07:17] <troy_s> for a side project
[07:17] <troy_s> is 17% opaque
[07:17] <kwwii> lol
[07:17] <troy_s> and relies on a vertical background grad
[07:17] <kwwii> ouch, I wonder why
[07:17] <troy_s> well it is by design
[07:17] <troy_s> in gnome, the background grad will show through if your png/svg is translucent
[07:18] <troy_s> which can make for some interesting mixes.
[07:18] <troy_s> It allows for a user to tweak a colour base without needinga full blown new wallpaper
[07:18] <troy_s> (within some obvious limitations that aren't worth mentioning ;) )
[07:19] <troy_s> did you try one with the centre punch moved over?
[07:19] <kwwii> seems like it would be better to just use a pic like you want
[07:19] <kwwii> it certainly would save a bit of time loading
[07:19] <troy_s> it saves a bit, but is a bit more flexible.
[07:19] <kwwii> yeah, I am in the process of doing just that
[07:20] <troy_s> for people who want the 'design' but
[07:20] <troy_s> don't want a given colour set
[07:20] <kwwii> gotcha
[07:20] <troy_s> (dynamic hooks into the SVG is an ideal scenario)
[07:20] <troy_s> darkmatter and I were working on something akin to that
[07:20] <troy_s> for themes
[07:20] <troy_s> setup a few icons with some established escape sequences and let the user tweak the colours through python
[07:20] <kwwii> interesting
[07:20] <troy_s> into Tropic nightmares of their own love.
[07:21] <troy_s> Python is the best thing to happen to computing since sliced bread.
[07:22] <kwwii> lol
[07:22] <troy_s> speak of the sick devil
[07:23] <troy_s> how's the flu dark?
[07:23] <troy_s> kwwii: By the way, you never answered on a question I asked ages ago
[07:23] <troy_s> Why did the default folder icon change?  I know it is a work in progress, but the earlier versions I saw seemed more elegant.
[07:24] <darkmatter> troy_s, hiya
[07:24] <troy_s> or is that nino(sp?)
[07:24] <darkmatter> its better now... kinda... just gotback from the hospital...
[07:24] <troy_s> sheesh
[07:24] <darkmatter> I hate my lungs
[07:25] <troy_s> darkmatter: Have you had any time for the middle grey project?
[07:25] <troy_s> darkmatter: I have some time to try plugging away at the python elements.
[07:26] <darkmatter> haha... yeah... was feeling well enough to work on it last night.. then 15 minutes after I started gimping my lungs threw a hissy fit
[07:27] <darkmatter> but I think I'll be able to do more today
[07:27] <kwwii> troy_s: it was one of those group decisions that I didn't win, basically
[07:28] <troy_s> lol
[07:28] <troy_s> kwwii Fall down go boom
[07:28] <darkmatter> haha
[07:28] <kwwii> exactly :-)
[07:28] <troy_s> kwwii Well that's too bad.  How many folks contribute to oxygen beyond yourself?
[07:28] <troy_s> nuino and ?
[07:28] <kwwii> nuno and david
[07:28] <troy_s> ah.
[07:29] <troy_s> wow... that's a pro wrestling 2:1
[07:29] <kwwii> and nuno does pretty much whatever david wants
[07:29] <kwwii> yeah
[07:29] <troy_s> Sounds like fun.
[07:29] <troy_s> Patsies.
[07:29] <troy_s> ;)
[07:29] <kwwii> oh yeah, you gotta love a good democracy
[07:29] <troy_s> You got to love em.
[07:29] <darkmatter> this is one of those "sabdfl flexes his deep pockets n says "I'm da daddy.... we use these folders.. NOW!!!!" moments?
[07:29] <darkmatter> ;)
[07:30] <troy_s> Yep.  Isn't that the addage that a giraffe is what you get when you try to create a horse through democracy?
[07:30] <kwwii> lol, yeah
[07:30] <troy_s> although i have some fundamental disagreements with it -- most of the best work i have ever seen is through tight collaboration.
[07:30] <troy_s> ultimately, it is the individuals involved.
[07:33] <troy_s> kwwii do you do the 'hardware' icons?
[07:33] <kwwii> oh believe me when I say that the teamwork on oxygen is sooo much better than it was on crystal
[07:33] <kwwii> troy_s: well, I have done quite a few of them
[07:33] <kwwii> I am the best illustrator in the group
[07:33] <kwwii> and those icons are very realistic
[07:36] <darkmatter> brb
[07:38] <kwwii> this weekend went by way too fast
[07:47] <PingunZ> kwwii, mind sharing the link ? :)
[07:47] <PingunZ> of your flickr
[07:49] <kwwii> PingunZ: www.flickr.com/people/kwwii/
[07:49] <PingunZ> k, thx :)
[07:50] <kwwii> not too much there yet
[07:50] <kwwii> but you can see the lasagne I made today
[07:50] <PingunZ> hehe
[07:50] <PingunZ> nice
[07:50] <PingunZ> :)
[07:50] <PingunZ> a lil' too long in the oven imo
[07:51] <kwwii> lol
[07:53] <PingunZ> I think google should make a flickr like thing
[07:53] <troy_s> isn't that where picassa is heading?
[07:54] <PingunZ> troy_s, didn't know about that, but you're right :)
[07:55] <PingunZ> 250mb, not bad


 (Photo, 1080x1920) https://irc.ubports.com/Ww40txpr.png
 @TotalSonic [<reply to media>], My background is of me and my friend :)
 @PhoenixLandPirate [My background is of me and my friend :)], You are inspiring me to start on Duolingo with that :)
 @TotalSonic [You are inspiring me to start on Duolingo with that :)], I recommend it, but I will say, I'm not very good at it, hard to keep up with it honestly, but now I'm back at work, I've got more motivation to start doing it again!
 Seems like I need to keep my PinePhone on the stable update channel, otherwise it stops turning on.
 Release candidate helped it feel faster, but it wouldn't turn on again after the battery died so flashing it again.
 @Braillynn [Release candidate helped it feel faster, but it wouldn't turn on again after the …], I had that issue at some point, but on kernelupgrade, my battery died, and now I can charge it and it'll boot fine, though when I've been using older kernels, it's been a bit hit and miss, because a lot of my chargers are /fast/ char
[02:11] <ubptgbot> gers, and on older kernels the hardware doesnt do power management via charging well, so if you try to charge using a fast charger, then your battery dies from the screen being on. … But yeah its hit or miss for what works with different peoples set ups.
 @PhoenixLandPirate [I had that issue at some point, but on kernelupgrade, my battery died, and now I …], What do you keep it on? Or do you still use Ubuntu Touch?
[02:13] <ubptgbot> <Ganvix Gust> If anyone has the Redmi s2 (ysl) and is interested in testing, I will be working on a halium 9 and hopefully halium 10 from for it, again. GSI is the first to get working before system image.
[02:13] <ubptgbot> <Ganvix Gust> I get there is a few different boot images, it's fun for some people to do it themselves
 @Braillynn [What do you keep it on? Or do you still use Ubuntu Touch?], Yeah its just ubuntu touch
 @PhoenixLandPirate [Yeah its just ubuntu touch], I meant what update channel. Or do you also keep in on stable?
 @Braillynn [I meant what update channel. Or do you also keep in on stable?], Kernelupgrade atm. but its usually either Devel or Kernel.
[02:36] <ubptgbot> Rock N Roll was added by: Rock N Roll
 (Photo, 960x1280) https://irc.ubports.com/xIDUX7Lf.png
 Had to set it up again, but it looks so good imo :)
 It seems to shut off though while it's charging and the screen goes blank.
 @TotalSonic [<reply to media>], this looks amazing on an OLED screen
 Is it compatible for galaxy A20s
 ?
 someone would have to port UT to it
 Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is really slow, keyboard is a bit slow.. Etc.
 @marc_petschke [Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is reall …], Use a different hardware :)
 :-) ... but I was looking for a tablet ... and Nexus and bq are actually the only working I could find. … Just hoped i could tweak something.
 (Document) https://irc.ubports.com/UxF5E6D1.mp4
 @Hidden19 [<reply to media>], spam?
 actuualy it seems to be not a bot ig
 ah it is bot
 a lotof groupes
 @Hidden19 [<reply to media>], @Flohack if you're still around ;)
 hello all
 how are you today?
[09:22] <ubptgbot> Castilian_inaccessibility was added by: Castilian_inaccessibility
 EIIon Ⓜusk Give-awwayyy cryptoooo!!! https://cutt.ly/azJi6XW 🚀🚀
 i was going to /report, then i remembered...
 @Castilian_inaccessibility [EIIon Ⓜusk Give-awwayyy cryptoooo!!! https://cutt.ly/azJi6XW 🚀🚀], somebody spent effort in stealing css
 not hard
 multiple templates exist
 @marc_petschke [Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is reall …], which Nexus? Nexus 5 is already quite fast compared to other devices
[12:01] <ubptgbot> <Ted Rendol> @marc_petschke [Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is reall …], some Large pdf documents are also a problem for stronger hardware than the nexus 4 or 5
[12:37] <ubptgbot> C0n57an71n was added by: C0n57an71n
[13:21] <ubptgbot> vinay13091993 was added by: vinay13091993
[14:57] <suspen> Hi, Is here someone coming from SailfishOS?
 what do you want to know?
[15:16] <suspen> What was the user experience between them? Nothing specific
 sometimes it is about compromises
[15:25] <suspen> Only app is really important to me is an accurate online navigation with house numbersű
 Does anyone in the chat have any experience flashing UT onto an Xperia X (F5121)?
 I've read the instructions on the device page and it seems a bit involved. Just wondering how difficult it is.
 it does have a few extra steps but they're mostly typical with other devices anyway. … unlock bootloader, update to stock Android that's compatible with UT, install via ubports installer
 the tricky part is the unlocking of bootloader. there's a possibility that your device cannot be unlocked ever. And you also have to follow Sony's official procedure on how to do it
 Thank you. I'm currently looking at a used one that seller says is unlocked. I'm assuming that's just for carrier though.
 @TotalSonic [<reply to media>], Looking good 😁
 @Javacookies [the tricky part is the unlocking of bootloader. there's a possibility that your …], Kugi, could you elaborate on why the device may not be possible to unlock? I'm not really well versed in the phone space and my Nexus 5 was very easy to get up and running on UT so I'm not familiar with many of these extra steps.
 there are units that are not possible to unlock … I forgot what was the indication but I think some text in the about page can be used as indications. You may check Son'y page about unlocking bootloader
 @Javacookies [there are units that are not possible to unlock … I forgot what was the indication …], Thank you again. Sony's page is a bit vague about it. Essentially gives you the procedure and then device may or may not be unlockable but nothing to indicate why.
 I'll try to remember or look for it … I wasn't actually aware of this when I bought mine. Luckily mine was unlockable :)
 ah it's not something you can see easily. You have to ask the seller a few steps. In this page, there's a code to dial which will show if the device can be unlocked … https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader#unlock-code
 @Javacookies [ah it's not something you can see easily. You have to ask the seller a few steps …], Nice, thank you for that. It also seems that models starting with a 1302 SKU seem to be unlockable more often than not according to what I've read so far. The one I'm looking at indeed has a 1302 at the start.
 good luck
 Xperia X is a nice phone and I heard there are improvements coming with OTA-16
 @Javacookies [good luck], Thank you Kugi and thank you for they help, much appreciated 👍
 Certainly seems nice. I love my Nexus 5 but it's been having the power button issue for a a couple years now and goes into bootloop at times.
 Any update for oneplus 5?
[18:27] <ubptgbot> <Steve Kueffer> @RealDanct12 [to everyone on xiaomi redmi note 7, we've fixed the fingerprint sensor pressing …], I'm considering to order a Redmi Note 7 to succeed to my Nexus 5. (better specs) According to Ubports website it seems well matured on UT. Is anyone able to recommend it? Thank you!
[18:27] <ubptgbot> <Steve Kueffer> @RealDanct12 [to everyone on xiaomi redmi note 7, we've fixed the fingerprint sensor pressing …], [Edit] I'm considering to order a Redmi Note 7 to succeed to my Nexus 5. (better specs) According to Ubports website it seems well matured on UT. https://devices.ubuntu-touch.io/device/lavender/ …  Is anyone able to recommend it? Thank
[18:27] <ubptgbot> you!
 afaih there's an echo in audio calls
 @marc_petschke [Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is reall …], what do you mean keyboard is slow? i've seen a couple of people say that but i don't experience that myself
 @marc_petschke [Hi. Is there a way to speed up utouch? I use nexus device.  pdf reading is reall …], [Edit] what do you mean keyboard is slow? i've seen a couple of people say that but i don't experience that myself even on the 1GB E5
[18:46] <ubptgbot> <Steve Kueffer> @Fuseteam [afaih there's an echo in audio calls], Ok thank you. But this might be resolved in a future update (?)
 @Steve Kueffer [Ok thank you. But this might be resolved in a future update (?)], yes, no idea when however
 @suspen [Only app is really important to me is an accurate online navigation with house n …], Between uNav, Pure Maps, OSM Scout Server, Here maps webapp, and LatLong Data (to locate coordinates for places missed by uNav's search) - AND with choosing a device that has decently responsive gps (Volla and Meizu Pro 5 in my experience) it
[18:47] <ubptgbot> is possible to get workable turn by turn navigation with UT now. But it is definitely not as good as what you get from a  hundreds of billions of dollars valued surveillance corporation.
 @TotalSonic [Between uNav, Pure Maps, OSM Scout Server, Here maps webapp, and LatLong Data (t …], irc; they might not get your reply
[18:58] <ubptgbot> <Steve Kueffer> @Fuseteam [yes, no idea when however], It seems that a solution has been very recently found: https://github.com/ubports/ubuntu-touch/issues/1662 … Hope it will be further tested and integrated to the device image.
 @Steve Kueffer [It seems that a solution has been very recently found: https://github.com/ubport …], oh cool
 @Javacookies [which Nexus? Nexus 5 is already quite fast compared to other devices], Nexus 7 2013 WLAN
 @Fuseteam [what do you mean keyboard is slow? i've seen a couple of people say that but i d …], Sometimes it takes longer between pressing and seeing the letter
 hmm weird haven't seen that behavior even on the bq e5 with 1gig of ram
[19:21] <ubptgbot> ptp31 was added by: ptp31
 Hey there
 Hey Jack!
 @marc_petschke [Nexus 7 2013 WLAN], I have a Nexus 7 LTE (deb) as well and it is just a mediocre at best performer with UT.  Frankly given its age, and that it has so many device specific bugs (no camera, no bluetooth, no side stage) I think it is better just to move on from it.  There is a possibility of support for the Lenovo M10 tab
[21:17] <ubptgbot> let coming up with a port just started for it, that I think holds some promise as an affordable tablet option for UT.
 Oh that would be cool!
 @marc_petschke [Oh that would be cool!], Some of us have already bought the device... maybe jumping the gun a little here. Just a little.
 Can we add the Pixel 3a XL to the list of supported devices?
 @Braillynn [Can we add the Pixel 3a XL to the list of supported devices?], Not until we have screen scaling set differently to the non-XL variant. That's the only missing piece, everything else can be done using an alias from "bonito" to "sargo" in the installer. But have you tried installing it manually already?
 @fredldotme [Not until we have screen scaling set differently to the non-XL variant. That's t …], I have not, I am debating on trying it though as I'm tired of android.
 I need the install image too.
 I couldn't flash Sailfish OS without a crap ton of trial and error, took all day honestly. So makes me worries UBT would be the same.
 This should get you started: https://forums.ubports.com/topic/5840/differences-in-support-compatability-between-pixel-3a-and-pixel-3a-xl/3?_=1615763861948
 The only requirement is that you downgrade to the latest Android 9.0 from Google first.
 @Braillynn [I couldn't flash Sailfish OS without a crap ton of trial and error, took all day …], Here's the prerequisite: https://developers.google.com/android/images#bonito
 I wanna use UT, but my cell provider is CDMA, and even if I get past that hurdle, I still need VoLTE otherwise I cant really do anything


[00:24] <teward> did the perl 5.22 transition finish already?
[00:25] <Unit193> teward: https://launchpad.net/ubuntu/+source/perl
[00:25] <Bluefoxicy> Transition to what?  An expanded list providing duplicate keys in a hash?
[00:26] <teward> that answers the question xD
[00:26] <teward> Unit193: thanks  (the transition tracker shows one thing still failing, hence the question)
[00:27] <Bluefoxicy> no docker 1.9 in next LTS?
[00:27] <Bluefoxicy> the new docker-compose allows setting ulimits in the compose file, which is a pretty major feature
[00:30] <Unit193> Just means I can do my perl5.22 rebuilds now too.
[00:35] <cjwatson> teward: the tracker is only a guide, and in this case that's only failing because I hadn't yet done NBS removals following the transition (doing now)
[00:36] <teward> cjwatson: ah, OK, i should've known when nginx 1.9.6-2ubuntu2 landed that the perl migration finished :P
[00:37] <teward> thanks though
[00:37] <Bluefoxicy> nginx 1.9!
[00:37] <Bluefoxicy> Ubuntu 16.04 LTS will have http2 capability
[00:37] <teward> um
[00:37] <teward> maybe at some point
[00:37] <teward> but not right now
[00:37] <Bluefoxicy> ... as if that matters.  Running nginx out of a docker container is easy.
[00:37] <teward> (talk to the Security Team)
[00:37] <cjwatson> ECHAN?
[00:37] <Bluefoxicy> teward:  http2 is part of nginx 1.9
[00:38] <teward> Bluefoxicy: optional module, has to explicitly be enabled
[00:38] <Bluefoxicy> ah
[00:38] <teward> you may be interested to read the merge bug
[00:38] <cjwatson> oh right
[00:38] <Bluefoxicy> so it's in the docker container for official, but not enabled in nginx on Ubuntu ok
[00:38] <teward> https://launchpad.net/bugs/1510096
[00:38] <teward> Bluefoxicy: the PPA has it though
[00:38] <teward> also managed by yours truly :)
[00:39] <teward> cjwatson: ?
[00:39] <Bluefoxicy> that's ... odd.
[00:39] <Bluefoxicy> does http2 add anything to the execution path if you don't explicitly set listen ssl http2?
[00:39] <teward> Bluefoxicy: as I said, talk to the sec team
[00:39] <jrwren> "security team"
[00:40] <teward> ^ they overrule things :P
[00:40] <Bluefoxicy> I mean I understand the point; I'm just curious if the code is even executed (thus, capable of bringing security problems) if the user doesn't use it explicitly
[00:40]  * teward shrugs
[00:40] <teward> whether I believe it's stable or not, not my call
[00:40] <Bluefoxicy> (I'm also annoyed nginx doesn't package modules as DSO, but that's a long-standing conversation between nginx developers and entire world)
[00:41] <teward> Bluefoxicy: for those of us on the tail end of a long day beating an ancient Dovecot into submission to migrate it to a newer dovecot, mind expanding DSO to full words?
[00:41] <teward> please :)
[00:41] <Bluefoxicy> teward:  Dynamic Shared Object
[00:41] <teward> Bluefoxicy: i think they just want the HTTP/2 protocol to have more exposure in the real world :)
[00:41] <teward> ahhh, yeah, i think dynamic modules are planned
[00:42] <teward> where'd I see that email...
[00:42]  * teward digs up the message from rbasak he saw recently...
[00:42] <Bluefoxicy> there was experimental dynamic loading support 10 years ago :P
[00:43] <teward> https://lists.ubuntu.com/archives/ubuntu-release/2016-January/003499.html is relevant
[00:43] <teward> (for the HTTP2 in Xenial thing)
[00:44] <Bluefoxicy> ah
[00:45] <cjwatson> teward: never mind
[00:45] <teward> cjwatson: ok :)
[00:45] <teward> wheee, ftbfs in sbuild schroots >.>
[01:16]  * psusi remembers when dynamic loading was the fancy new thing both to the kernel and user space... circa 1997 or so...
[01:17] <psusi> had a lot of fun playing with the new shared objects and dynamically loading them in eggdrop 1.3.x irc bot
[01:18] <psusi> can't believe it's 2016 already
[01:25] <teward> psusi: heheh
[01:40] <sarnold> pitti: could you please give some feedback on 1503762? It feels to me like Felipe's suggestion for an apparmor systemd service file is just about right but it'd be nice to have your opinion before we get too far ahead of ourselves :) thanks
[06:17] <Mirv> is it known Ubuntu Installer e-mail notes lag by up to a month? every now and then I still keep getting notices from my December's Qt landing. yesterday I got a notice for this https://launchpad.net/ubuntu/+source/gammaray/2.3.0-3build1 that landed to release pocket 2015-12-10
[06:19] <Mirv> and I had e-mail about this https://launchpad.net/ubuntu/+source/gcin/2.8.4+dfsg1-1ubuntu1 on 2015-12-28..
[06:20] <infinity> Mirv: Sounds more like a mail server hitching up somewhere.
[06:21] <infinity> Mirv: LP just spits the mail out to an MTA managed by IS, after that it's a blackhole to us.
[06:23] <infinity> Mirv: Oh.  Or no.
[06:23] <infinity> Mirv: It's s390x catching up, probably.
[06:24] <infinity> https://launchpad.net/ubuntu/+source/gammaray/2.3.0-3build1/+build/8387977
[06:24] <infinity> https://launchpad.net/ubuntu/+source/gcin/2.8.4+dfsg1-1ubuntu1/+build/8387979
[06:24] <infinity> Note those builds happened fairly recently.
[06:24] <infinity> And when proposed-migration decides they're good to copy, it recopies the source+binaries, since that's easier than figuring out how to just copy a binary. :P
[06:25] <infinity> That should probably happen silently for those cases, but it doesn't currently.
[06:27] <infinity> cjwatson: In the step where britney generates the list of archive actions required, does it know at that point (I imagine it does) if a copy is binary-only?
[06:27] <infinity> cjwatson: If so, it might be nice to flag those as silent, so people don't get a confusing second mail when an arch is catching up.
[06:27] <infinity> cjwatson: Though, a bit late now that s390x is mostly done. :P
[06:30] <Mirv> infinity: ah, a logical explanation! thanks!
[07:17] <pitti> Good morning
[08:20] <dholbach> good morning
[08:23] <sladen> Morgen
[09:16] <Odd_Bloke> I'm seeing a "The following packages have unmet dependencies:\n perl-base : Breaks: perl-modules (< 5.22.1~)\n perl-modules-5.22 : Breaks: perl-modules" error when trying to build a xenial livefs; I saw some discussion yesterday about a Perl migration, but don't know how to work out when I can expect my builds to return to a working state.
[09:17] <pitti> Odd_Bloke: it actually should work, the perl transition is complete
[09:17] <Odd_Bloke> Ah, OK.
[09:17] <Odd_Bloke> Well, it isn't: https://launchpadlibrarian.net/233282042/buildlog_ubuntu_xenial_amd64_cpc_BUILDING.txt.gz ^_^
[09:18] <pitti> Odd_Bloke: so of course you need the current perl-base with the current perl-modules
[09:18] <pitti> hm, I built containers this morning
[09:19] <Odd_Bloke> The "Get"s are perl-modules-5.22 all 5.22.1-3, perl amd64 5.22.1-3, and perl-base amd64 5.22.1-3.
[09:19] <pitti> the gets look alright to me
[09:20] <pitti> just not sure why dist-upgrade croaks about the breaks:
[09:21] <Odd_Bloke> "dpkg: perl-modules: dependency problems, but removing anyway as you requested: perl depends on perl-modules (>= 5.20.2-6)."
[09:22] <Odd_Bloke> Wait, maybe that's in the host rather than the chroot.
[09:22] <pitti> perl-modules should be removed, that's right (replaced by p-m-5.22)
[09:31] <infinity> Odd_Bloke: Fixing.
[09:32] <Odd_Bloke> infinity: <3
[09:32] <infinity> pitti: It's because perl-modules is NBS and still present in seeds as a result of still being in the archive, so his attempt to install a task that includes it will explode.
[09:32]  * infinity removes it.
[09:32] <pitti> infinity: why on earth do we seed perl-modules?
[09:32] <infinity> pitti: We don't, but things depend on it.
[09:33] <infinity> pitti: Which lands it in tasks.
[09:33] <pitti> ah
[09:33] <infinity> Oh.  And also explicitly seeded in samba-server.
[09:34] <infinity> Which is obsolete not.
[09:34] <infinity> s/not/now/
[09:35] <infinity> There, fixed even harder.
[09:35] <infinity> Odd_Bloke: Should be slightly less sad in an hour or so.
[09:37] <Odd_Bloke> infinity: Great, thanks!  Will I be able to tell that it's good once perl-modules disappears from http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.xenial/cloud-image?
[09:41] <infinity> Odd_Bloke: That would be a reasonable indicator, yeah.
[09:48] <LocutusOfBorg1> hi folks, stupid question: what does "unapproved" means? (wrt queue)
[09:50] <LocutusOfBorg1> I'm a recent MOTU, I uploaded an SRU for wily, and a backport for precise,trusty,utopic, wily and all of them ended in unapproved queue
[09:50] <pitti> LocutusOfBorg1: that's the queue for pockets that require archive admins or the release team to review and approve uploads
[09:50] <LocutusOfBorg1> oh I found it
[09:50] <LocutusOfBorg1> https://wiki.ubuntu.com/ArchiveAdministration#Diffs_for_unapproved_uploads
[09:50] <pitti> LocutusOfBorg1: i. e. all stable releases, and the devel series when it's "frozen"
[09:50] <LocutusOfBorg1> google was pointing to the queues not to the means
[09:51] <LocutusOfBorg1> yes sure, thanks
[09:51] <LocutusOfBorg1> for debian backports needs approval the first time (because they are new), not anymore after that I think
[09:51] <LocutusOfBorg1> so even after the first backport there is still need to go in the queue, fine :)
[09:52] <LocutusOfBorg1> thanks
[10:08] <LocutusOfBorg1> "virtual memory exhausted: Cannot allocate memory"
[10:08] <LocutusOfBorg1> this happens on arm64, how can I fix it?
[10:08] <LocutusOfBorg1> maybe I can upload and force -j1
[10:10] <infinity> LocutusOfBorg1: Which build?
[10:13] <LocutusOfBorg1> arrayfire/arm64
[10:13] <LocutusOfBorg1> I tried to give it back twice
[10:13] <LocutusOfBorg1> no help
[10:13] <LocutusOfBorg1> I'm going to upload an ubuntu1 without --parallel build
[10:13] <infinity> LocutusOfBorg1: Sec.
[10:13] <infinity> LocutusOfBorg1: Please don't.
[10:13] <LocutusOfBorg1> ack
[10:14] <LocutusOfBorg1> no problem
[10:15] <infinity> LocutusOfBorg1: I'm going to retry it on a machine that (probably) sucks less.
[10:15] <LocutusOfBorg1> thanks :)
[10:15] <seb128> there seems to be a blueman/bluez issue on xenial, looking at e.u.c ... Noskcaj_ could you check if that's due to your blueman update?
[10:17] <infinity> LocutusOfBorg1: Okay, if the current build on auburn fails in the same way, feel free to experiment.
[10:17] <infinity> LocutusOfBorg1: If it doesn't, it probably just means we need to fix our VM configs a bit for the bos* nodes.
[10:18] <LocutusOfBorg1> infinity, BTW assuming it will build there, it won't migrate because of missing powerpc build, I asked to remove it on Debian, should I file a bug in Ubuntu too?
[10:18] <LocutusOfBorg1> infinity, I have no problems in disabling parallel builds in Debian, maybe -j4 is too much for arm64?
[10:18] <LocutusOfBorg1> I don't want to have the same issues on the next debian upload, even if now it is fixed :)
[10:18] <infinity> LocutusOfBorg1: We select the -j, not you. :P
[10:19] <infinity> LocutusOfBorg1: And if we're selecting too high, we need to fix our setup.
[10:19] <LocutusOfBorg1> infinity, exactly I know, but I can disable it at all, or even force it :)
[10:19] <infinity> (or, rather, if we're memory starving ourselves)
[10:19] <infinity> LocutusOfBorg1: We'll see how it goes first.
[10:20] <LocutusOfBorg1> debian defaults arm64 with -j8, right?
[10:20] <infinity> LocutusOfBorg1: Well, it's -j8 on the builder I just put you on too.
[10:20] <infinity> LocutusOfBorg1: Generally, people do -j$(nproc)
[10:21] <infinity> And nproc on a Mustang is 8.
[10:21] <infinity> One our VMs, it's 4.
[10:21] <LocutusOfBorg1> ok so it wasn't a real hw
[10:22] <infinity> LocutusOfBorg1: Also, uhm, please don't remove on an arch for one failing test.  Fix the bug instead?
[10:23] <infinity> LocutusOfBorg1: It's obviously an endian bug.  Same failure on all big-endian arches.
[10:23] <seb128> pitti, did you see https://errors.ubuntu.com/problem/03377c894de2d08604cdabf066893d99c348d84f ?
[10:23] <seb128> "udev.prerm called with unknown argument 'deconfigure' dpkg ( error processing archive /var/cache/apt/archives/ifupdown_0.8.5ubuntu1_amd64.deb (--unpack))"
[10:24] <pitti> seb128: actually I did, it's debian bug 809744 and debian bug 809743
[10:25] <seb128> pitti, danke
[10:25] <seb128> pitti, I'm just looking at the e.u.c xenial top reports and it's in it
[10:25] <seb128> good to see it's handled
[10:25] <pitti> seb128: unfortunately a broken prerm can't be retroactively fixed, so we'll work around it in ifupdown
[10:25]  * seb128 clicks bug opening and add the debian watch
[10:25] <LocutusOfBorg1> infinity, I agree, but the package is rather complicate, my endianness knowledge is stuck in the "headache" step, it isn't a package I personally maintain / care about
[10:25] <pitti> I can't reproduce it in my dist-upgrades though, but apparently some people do
[10:25] <seb128> hum
[10:25] <seb128> e.u.c "create" fails
[10:26] <LocutusOfBorg1> but maybe knowing it is a big-little endian issue will make me try to patch
[10:27] <infinity> LocutusOfBorg1: Given all the BE arches failing on buildd.debian.org, it's pretty clearly that.
[10:29] <LocutusOfBorg1> infinity, I'm not too much a porter guy to remember just by looking at architectures list which are big and which are little :) sorry
[10:30] <infinity> LocutusOfBorg1: Anyhow, it's also a leaf package, so I won't whine too hard about removing the PPC binaries.  Tomorrow, after we've figured our arm64.
[10:30] <infinity> LocutusOfBorg1: Bug fixing the endian bug would be lovely too. :P
[10:31] <LocutusOfBorg1> I'm already trying that :)
[10:31] <LocutusOfBorg1> you gave me the best hint I could get
[10:32] <LocutusOfBorg1> unfortunately upstream doesn't care too much about the porting, so maintaining the code aligned for other archs might be difficult for the Debian Maintainer
[10:33] <LocutusOfBorg1> and I don't think science packages are used too much on arm* or powerpc
[10:34] <pitti> seb128: I'll merge it ASAP
[10:34] <seb128> pitti, danke
[10:40] <pitti> seb128: it's bug 1531685
[10:40] <seb128> k
[10:43] <infinity> LocutusOfBorg1: I suppose that depends on how sciency they are.
[10:43] <infinity> LocutusOfBorg1: Some very large machines run ppc64 and sparc64 and then, well, there's s390x.
[11:02] <LocutusOfBorg1> infinity, the build seems to have passed the problematic build step
[11:05] <infinity> LocutusOfBorg1: Yeahp, when it completes successfully, I'll remove the powerpc binaries for you.
[11:05] <infinity> LocutusOfBorg1: And if someone wants to fix the BE bug later, yay.
[11:06] <LocutusOfBorg1> infinity, upstream fixed i386 in this upload, so I'm going to point them to the "BE issue" thanks
[11:06] <Odd_Bloke> infinity: No sign of an update to the germinate output yet (I was even a good boy and waited 90 minutes to nag you ^_^).
[11:10] <infinity> Odd_Bloke: Give the build a whirl anyway, that germinate output on people isn't updated often.
[11:10] <Odd_Bloke> Whirling now.
[11:15] <infinity> LocutusOfBorg1: Okay, arm64 uploading, PPC binaries scheduled for deletion.
[11:16] <Odd_Bloke> infinity: Aha, the new builds look like they're succeeding; thanks!
[11:16] <infinity> Odd_Bloke: You might want to diff manifests between yesterday and today to make sure the seed/perl changes didn't do something nasty, but it should be fine.
[11:20] <LocutusOfBorg1> infinity, upstream is now aware of the BE issue :)
[11:21] <LocutusOfBorg1> BTW I don't think it will migrate because of an armhf regression
[11:21] <LocutusOfBorg1> but I'll see
[11:25] <infinity> LocutusOfBorg1: Given the stellar history on http://autopkgtest.ubuntu.com/packages/a/arrayfire/xenial/armhf/ it seems like a fluke that it ever passed.
[11:26] <infinity> LocutusOfBorg1: But I'll retry it.
[11:36] <rbasak> mvo_: around? do you know if there is any way I can get apt to keep around the file after a Hash Sum mismatch? Got some odd behaviour behind a (mandatory) proxy with a mismatch on some debs. Which, AFAICT, are being served accurately and match the Packages file, so I need to dig deeper somehow.
[11:46] <rbasak> Confusingly my failure happens reproducibly with sbuild (a handful of mismatches on debs, but not all) but then if I don't purge the session then I can install using apt-get manually without a problem.
[11:47] <rbasak> Whatever sbuild does to invoke apt doesn't seem to end up in /var/log/apt/history.log :-/
[12:29] <cjwatson> infinity: I think it possibly could, but it doesn't pass it through at the moment, and it's a bit buried :-/
[12:31] <cjwatson> infinity: (arch-specific copies)
[12:38] <doko> apw, please could you have a look at merging schroot?
[12:43] <infinity> Odd_Bloke: Bootloader->kernel bits work on the latest powerpc test image.
[12:43] <infinity> Someother bits seem broken, but progress. :)
[13:00] <sil2100> Hey! Does anyone know if there are plans of merging the new ppp from Debian to Ubuntu? If yes, is there anyone working on that?
[13:02] <LocutusOfBorg1> the last uploader was ScottK ^^^
[13:14]  * ScottK is not.
[13:15] <LocutusOfBorg1> I'm working on it
[13:15] <sil2100> LocutusOfBorg1: on ppp?
[13:16] <sil2100> LocutusOfBorg1: I'm working on some network-manager merges right now and I can only merge the new -pptp if we merge ppp, which is a bit of a bigger story
[13:16] <LocutusOfBorg1> yes, http://paste.ubuntu.com/14429758/
[13:16] <LocutusOfBorg1> feel free to test and upload
[13:16] <LocutusOfBorg1> I can't :)
[13:20] <sil2100> LocutusOfBorg1: ok, will check, I'm actually building a quick test build of a ppp merge already, but you probably put more attention when prepping this than I did ;)
[13:20] <sil2100> (since I just did minimal changes)
[13:23] <sil2100> LocutusOfBorg1: thanks!
[13:24] <LocutusOfBorg1> yw!
[13:48] <Odd_Bloke> infinity: http://paste.ubuntu.com/14429904/ is the package diff between pre- and post-seed change; that looks like a lot of removed Perl packages to me, but I don't know if that's what is expected.
[13:48] <Odd_Bloke> (For all I know, the whole point of the migration was to not pull in all of these unnecessary packages :p)
[13:52] <cjwatson> That's a familiar-looking set of removals.
[13:53] <cjwatson> I haven't tracked down why, but wouldn't get too sad about it.
[13:54] <cjwatson> Might be things moving into core or something.
[13:56] <Odd_Bloke> OK, cool.
[14:14] <pitti> sarnold: I replied to the bug, and subscribed (so I'll see responses timely)
[14:16] <seb128> pitti, did you see that the ifupdown update hit a regression on i386 autopkg
[14:16] <pitti> seb128: ah, upstart's tests have been flaky for a while; I'll retry, and ignore it if it keeps  failing
[14:17] <seb128> k
[14:23] <mvo_> rbasak: sorry for the delay, the files should be in /var/cache/apt/archives/partial, if you have more info please let me know I can also try to reproduce. this sounds worth digging into
[14:36] <rbasak> xnox: I'm working with kickinz1 on a freeipmi merge. We're looking at 1.1.5-3ubuntu3 that you uploaded with "Fix dso linking on the convenience library." Your patch was http://paste.ubuntu.com/14430242/
[14:36] <rbasak> xnox: was this for an --as-needed type thing or some other FTBFS or something else?
[14:37] <rbasak> xnox: we're not sure if this is still needed. It doesn't appear needed, but I don't understand why you needed it.
[14:37] <Odd_Bloke> infinity: cjwatson: I'm seeing a lot of "Unknown symbol mcount (err 0)" in the powerpc boot log, which looks like it's always the last message for a module (where ppc64el has many more for each module/driver, and actually boots).  Any ideas?
[14:40] <Odd_Bloke> http://paste.ubuntu.com/14430284/ is the full log.
[14:40] <Odd_Bloke> Googling around, this normally shows up when a DKMS module hasn't been compiled against the current kernel.
[14:40] <Odd_Bloke> But that seems... unlikely.
[14:43] <rbasak> mvo_: hmm. They're all truncated at exactly 2986 bytes.
[14:43] <rbasak> 2896 bytes sorry.
[14:45] <xnox> rbasak, it's been more than two years for that one... i have no idea =) if not needed, and it builds everywhere drop it, i guess...
[14:48] <cjwatson> Odd_Bloke: no idea, sorry!
[14:48] <arges> pitti: for bug 1531768, are you running arm64 instances on top of amd64? (emulated)
[14:48] <pitti> arges: no, the host should be proper arm64
[14:48] <pitti> arges: the bug report isn't that useful yet, it's mostly for collecting data
[14:49] <arges> pitti: ok, and in a single CPU variation you don't experience all the stalls?
[14:49] <pitti> arges: so it seems the more CPUs the instance gets, the faster it falls into that trap (whatever it is)
[14:49] <pitti> arges: I can't even boot an 8-CPU machine half of the time, and with 4 it at least survives a bbit
[14:49] <arges> pitti: which hardware is it exactly?
[14:50] <pitti> arges: I haven't tested single-CPU yet (it would be completely useless to me, but it'd be interesting for this bug report indeed) -- still on my list
[14:50] <pitti> arges: good question, whatever we have in Scalingstack; but I don't know about the hosts there
[14:50] <arges> ok
[14:53] <arges> pitti: i'll put the questions in the bug.
[14:54] <apw> doko, schroot ack, will put it on the list
[14:57] <rbasak> xnox: OK, thanks. I think it was needed to fix an FTBFS, and we seem to build OK without it now, so we'll drop the patch. For next time, could you try to document the reason for an upload in the changelog, please?
[16:44] <gpiccoli> nacc: ping
[16:47] <nacc> gpiccoli: pong
[16:47] <gpiccoli> Hello nacc, how are you doing?
[16:47] <gpiccoli> Sorry to bother you, can I pm?
[16:48] <nacc> gpiccoli: doing well, thanks! and yes, sure
[16:48] <gpiccoli> nice, ty
[16:56] <juliank> APT will soon start depending on liblz4, that needs to be promoted from universe to main (mvo_ et al)
[16:57] <juliank> Unless it is already
[16:57] <juliank> No it is not
[16:59] <juliank> I'll do an MIR now
[17:03] <juliank> Filed as bug #1531923
[17:05] <juliank> Someone needs to figure out who's going to be responsible for it.
[17:06] <juliank> Feel free to update the bug accordingly
[17:07] <juliank> The package is tiny though, and has always been synced.
[18:05] <bdmurray> xnox: How would you expect an updated app-install-data-partner package to change software-center? I don't see anything when I filter by "Canonical Partners".
[18:07] <xnox> bdmurray, horum.
[18:08] <hallyn> xnox: hey, you still have some upstart insight, right?

[18:08] <xnox> hallyn, i guess so...
[18:09] <hallyn> we have this really really weird bug going on involving upstart killing tasks in a container when uevents happen
[18:09] <hallyn> (i thought it was a fuse related bug, sforshee made the connection to uevents)
[18:09] <hallyn> (trying to find the bug#, one sec)
[18:10] <hallyn> bug 1530617
[18:10] <hallyn> it's quite fascinating
[18:10] <xnox> bdmurray, well, i guess we simply need to rebuild the package. And if i remember correctly, iff one has partner enabled, and the app-install-data-partner is up to date, and one doesn't have e.g. skype installed, the icon and channel discription should still be visible in the software centre and/or some such.
[18:12] <xnox> hallyn, i don't think we actually support upstart in 15.10... do we?
[18:13] <xnox> hallyn, this is crazy =)
[18:13] <hallyn> wait, we don't?
[18:14] <xnox> hallyn, not without systemd as pid 1 removed....
[18:14] <hallyn> it's not the default but i thought we supported it at least though 16.04
[18:14] <hallyn> ^ without systemd as pid 1 removed - not quite parsing,
[18:14] <xnox> hallyn, we support it as running as part of the upgrade.
[18:14] <xnox> not as anything else.
[18:15] <xnox> hallyn, e.g. if one is running 14.04, one can upgrade to 16.04 and still be running upstart until reboot.
[18:15] <hallyn> i thought bc of phone users that wasn't an option
[18:16] <xnox> hallyn, but e.g. 15.10 cannot be doing that.... as the only upgrade path to 15.10 is from 15.04 which is running systemd by default.
[18:16] <xnox> none the less. container should not be able to see udev events. and there shouldn't be udev running in the container.
[18:16] <xnox> if that is the case, it's a resource leak no? and e.g. container can affect the host....
[18:19] <hallyn> that's a huge discussion upstream, and no right now uevents cannot be filtered to not go to containres
[18:20] <hallyn> it's wise not to run udev in container, but the solution is just to prevent udev in container from writing to sys
[18:22] <hallyn> mind you containers used to not run udev, not quite sur when that changed.
[18:22] <hallyn> (for upstart)
[18:24] <hallyn> still curious what is sending SIGKILL though.
[18:27] <bdmurray> mvo_: I've updated the app-install-data-partner info for xenial but still don't see anything in software-center. Any ideas?
[19:37] <mvo_> bdmurray: hm, you updated and installed it and nothing is in there. nothing at all? or nothing from the new set?
[19:45] <mterry> Laney, hey...  so I'm reminded of some patches I put into accountsservice to enable libpam-pin years ago.  At the time, I thought we might use them for Touch, but we went a different way.  The upstream bug hasn't seen any movement, so they don't seem likely to be integrated upstream.  No one seems to use the module.  It might be good to drop the patch now, before 16.04?
[19:45] <mterry> Just checking on thoughts / confirmation no one uses it before dropping it
[19:50] <barry> mterry: LP: #1531033 is fix committed, but it's still in universe and we're depwaiting on it.  do i need to do something to actually get the package in main?
[19:50] <mterry> barry, not typically, but you can poke an archive admin to speed things up
[19:50] <barry> mterry: ack, thx
[20:06] <TJ-> bdmurray_: re app-install-data-partner - I have no idea what its supposed to point to - I only found it in a roundabout way due to reading the man-page of apturl and investigating the repo path examples it gives
[20:29] <bdmurray_> TJ-: alright
[22:42] <sarnold> pitti: thanks so much for your feedback on 1503762! :)
[22:53] <Laney> mterry: No objections from me, feel free to upload it and make it be removed on upgrade
[22:56] <mterry> Laney, cool
[23:55] <hallyn> xnox: hm, so if we're going to say upstart is not supported, should it be dropped from main?  (I'm looking for some authorotative statement about it not being supported;  that woudl qualify)
[23:59] <rbasak> hallyn: AIUI, upstart is still supported when used for user sessions on the phone, so it must remain in main.


[12:47] <snap-l> morn'
[12:49] <brousch> nog
[15:10] <rick_h__> ugh
[15:11] <rick_h__> though first day of t-ball, so good excuse to get my first baseball glove in for ever
[20:08] <snap-l> nice. :)
[22:03] <rick_h__> welp, cleaned out my rv camping amazon wishlist. 29 items in one order. I think that's a new record.
[22:44] <brousch> you ordered 29 things?
[23:30] <rick_h__> brousch: yea, big list of stuff for the camper
[23:31] <rick_h__> never seen the shopping card paginate before, went into 3 pages


[02:24] <thedoctor> hi
[15:00] <dholbach> Hello hello hello!
[15:00]  * belkinsa is here for the meeting
[15:00] <dholbach> Do we have anyone here to talk about the LoCo team portal?
[15:00] <dholbach> let's see if the bot is back ;-)
[15:00] <dholbach> #startmeeting
[15:00] <costales> Hi dholbach :)
[15:00] <PabloRubianes> hi
[15:00] <dholbach> looks like it's not there :)
[15:01] <coolbhavi> hey guys
[15:01] <coolbhavi> :)
[15:01] <belkinsa> o/
[15:01] <balloons> o/
[15:02]  * coolbhavi  is on the run on mobile
[15:02] <dholbach> brilliant
[15:02] <dholbach> I just pinged a few other folks and it looks like we're ready to go
[15:03] <dholbach> so at the last UOS we talked about LoCo teams and how it's sometimes hard to share information, like news, like pictures, like stuff about events, etc.
[15:03] <mhall119> is daker coming?
[15:03] <dholbach> I pinged him and he said he would be around
[15:03] <dholbach> a lot of teams have their own discussion forums, blogs and websites
[15:03] <dholbach> but it'd actually be nicer, if they could get the information out there to a lot more folks around the world
[15:04] <dholbach> like, if my team does an event and has lots of pictures and a nice writeup, it'd be great if they could show off their work easily and thus inspire others around the world :)
[15:04] <dholbach> during the session somebody brought up the picture feeds on loco.ubuntu.com
[15:04] <dholbach> let me see if I can find an example link
[15:05] <dholbach> http://loco.ubuntu.com/teams/ubuntu-mm/ for example
[15:05] <coolbhavi> dholbach, how about having a syndication like planet ubuntu?
[15:05] <dholbach> at the bottom you can see pictures from the Myanmar team
[15:05] <dholbach> coolbhavi, exactly... that was the idea which was brought up during the session too
[15:06] <dholbach> and because we felt that the discussion would probably take a bit longer, we decided to have a separate discussion about this
[15:06] <coolbhavi> hmmm and we already have a on air session with locos running on in parallel
[15:07] <dholbach> the last I remember from the session was that it'd be nice to offer some functionality in loco.u.c to allow teams to add pictures, or news stories or writeups or anything else
[15:07] <dholbach> this would be great on its own already
[15:07] <dholbach> but then it could probably be shared on Planet Ubuntu as well
[15:07] <dholbach> (and maybe syndicated elsewhere?)
[15:07] <coolbhavi> yep like a traceback
[15:08] <dholbach> Do you have any additional ideas or thoughts or concerns about this?
[15:08] <belkinsa> Yeah, since some of the active members of the LoCo's are not Ubuntu Members.  But if they had a way to post on the Portal, it would be nice, and have that synced with Planet.
[15:08] <daker> hi
[15:08] <mhall119> dholbach: coolbhavi: LTP already has the ability to aggregate rss feeds
[15:08] <belkinsa> Ubuntu Planet is what I meant/
[15:09] <dholbach> hey daker
[15:09] <balloons> +1 the feed into planet idea.. not everyone has to be a member of ubuntu; if you are a part of the loco, and they release an official writeup, I'd love to see it in my feed ;-)
[15:09] <mhall119> daker: does LTP currently export an RSS feed of news?
[15:09] <belkinsa> I guess the lack of having active LoCo's is the main problem.
[15:09] <dholbach> daker, here's some backlog: http://paste.ubuntu.com/7675086/
[15:09] <belkinsa> But that's a different issue.
[15:10] <daker> mhall119: no but we can add that
[15:10] <mhall119> if we do that, I think we can add it ot the planet ubuntu syndication list
[15:10] <dholbach> belkinsa, what we talked about at UOS was that there are probably many teams who have meetups and do stuff regularly, but nobody writes about it - or they don't share info and pics
[15:10] <belkinsa> Oh duh, I forgot.
[15:10] <dholbach> belkinsa, the idea was that if we make it easier, more would talk about it and come up with new ideas together :)
[15:11] <belkinsa> Right.
[15:11] <costales> I think is a good idea :) I'm thinking that will be necesary to force the sign of the Conduct Code for those teams too
[15:11] <belkinsa> Ubuntu Ohio is already doing this.
[15:11] <costales> It'd be better for split my personal thoughts/posts from my team posts ;)
[15:11] <belkinsa> And I think that should be true for all teams.
[15:11] <mhall119> the homepage feed on LTP uses only hand-picked blogs, so we can export that to planet ubuntu and that should be enough oversight to keep inappropriate things out
[15:12] <dholbach> yeah... I think we could test the new news feed for some time before adding it to the planet
[15:12] <dholbach> just so we know it's not too much content, or too much spam, etc
[15:12] <mhall119> IIRC, we have the loco-council access to manage those feeds
[15:12] <mhall119> /have/gave/
[15:12] <dholbach> maybe we could do a monthly digest too ... or something
[15:12] <belkinsa> +1 on the handpicked blogs
[15:12] <coolbhavi> mhall119, how about team owners moderating the content?
[15:12] <costales> Just an idea: Split the planet in 2 tabs: Members | Teams. It could be interesting for split the contents (maybe :)
[15:13] <coolbhavi> and posting across
[15:13] <belkinsa> costales, I like that idea.
[15:13] <mhall119> coolbhavi: team admins can manage their team's aggregation, but the homepage uses a separate selection
[15:13] <belkinsa> But you need two RSS feeds for that.
[15:13] <mhall119> coolbhavi: basically teams can add any feed they want to their team, but then the LC can tag a feed to appear on the homepage as well
[15:13] <coolbhavi> ok got it mow seems good
[15:14] <dholbach> Or team members could write up something and team contacts/admins could approve this as content which goes out to everyone?
[15:14] <coolbhavi> dholbach, +1
[15:14] <mhall119> dholbach: that would be harder to manage
[15:14] <belkinsa> dholbach, +1, but as mhall119, I agree.
[15:14] <mhall119> doing it per-feed is easy, doing it per-post would require more work in LTP
[15:15] <dholbach> mhall119, it could just be a tag of the post?
[15:15] <mhall119> dholbach: I don't think the aggregator library we're using gives us that easily
[15:15] <dholbach> ah ok... I wasn't aware of the technical limitations, sorry
[15:16] <daker> mhall119: no teams can't add their RSS feeds rightnow, only LC can
[15:16] <dholbach> but would some copying between feeds work?
[15:16] <mhall119> daker: ok, but the data structure would allow that right? We just need to expose it by adding a couple of new pages
[15:16] <daker> mhall119: yes
[15:17] <dholbach> so all we have right now is an aggregator library? is there any blogging library installed as well? or would we expect users to blog elsewhere and we just syndicate?
[15:17] <mhall119> dholbach: for the first-round can we just use feed where the source blog uses a specific category or tag to limit it to content they want to appear on LTP?
[15:18] <mhall119> dholbach: they would blog elsewhere
[15:18] <dholbach> I'm just trying to understand where we are right now and what would easily be possible :)
[15:19] <dholbach> mhall119, daker: how would you imagine the new "share story" process to work? what would be the easiest thing we could add?
[15:20] <mhall119> dholbach: we could probably fake a feed in the aggregation data tables and have code that copies content from a source feed into that fake one
[15:21] <costales> dholbach: What about to create 1 special user for the Planet with an URL > that URL will be a RSS Feed. You will not need to change anything now (?)
[15:21] <coolbhavi> costales, like a permalink :)
[15:21] <dholbach> hum... so step 1) team adds team blog feed to LTP, 2) team member blogs on blog feed, uses special tag or category, 3) blog entry ends up in LTP aggregation feed, 4) by extension goes to planet ubuntu as well - is this right?
[15:21] <balloons> so everything would post as "Loco Teams" or something.. all feeds would show up as the same person?
[15:23] <belkinsa> dholbach, that might work but again management could be an issue.
[15:23] <mhall119> balloons: depends on how planet planet works, if it uses the author tag of the feed, we can give it the original blog's author
[15:23] <dholbach> costales, yes, that's right - the question is just "who gets to post to the blog you add to Planet?"
[15:24] <dholbach> mhall119, daker: are the steps I mentioned above how you roughly imagine it'd work?
[15:25] <mhall119> dholbach: roughly yes, doing it per-feed to start would be easiest and we can add per-post moderation from there
[15:25] <coolbhavi> dholbach, how about giving the user permissions to add other users based on request?
[15:26] <dholbach> coolbhavi, I would assume that's possible - it'd just be a question how much we open the gates to spamming or general (on-topic) flooding of Planet Ubuntu :)
[15:26] <costales> coolbhavi: Maybe a Launchpad Team with another repository feed?
[15:27] <dholbach> mhall119, earlier you mentioned some copying that takes place as part of aggregation - I assume that'd be a point where we could make changes to the posts? I was thinking of doing things like adding jump marks (read more →here←) or doing things like digests (weekly LoCo roundup or something)
[15:27] <coolbhavi> hmm thats a concern :)
[15:28] <daker> dholbach: yes
[15:28] <dholbach> brilliant
[15:28] <mhall119> dholbach: that might take a bit more work, but it's possible yes
[15:28] <dholbach> I don't think we would need this in a first iteration - I was just asking out of interest
[15:29] <mhall119> dholbach: simple aggregation and re-feeding to planet wouldn't involve copying or editing though
[15:29] <dholbach> that's right
[15:29] <dholbach> that sounds like a good first start already and I'm quite happy with what we could do in future iterations :)
[15:30] <dholbach> any more thoughts, ideas, questions, or anything else we didn't talk about yet?
[15:30] <mhall119> daker: my other thought was to generate an RSS feed for events and meetings, that would automatically be published to planet
[15:31] <belkinsa> +1
[15:31] <belkinsa> Along with blog posts.
[15:31] <dholbach> nice one
[15:31] <mhall119> so, the feed shows any events or meetings that have already happened or are happing that day (but not future ones)
[15:31] <mhall119> like an automated announcement
[15:32] <costales> +1 nice idea! mhall119
[15:32] <belkinsa> Yeah, but maybe have some time before the furture one
[15:32] <mhall119> that might encourage more teams to use LTP for those, so they get that reposted to planet
[15:32] <belkinsa> Maybe a month?
[15:32] <dholbach> why not future events/meetings?
[15:32] <mhall119> belkinsa: not too much, maybe 24 hours
[15:32] <dholbach> ah ok
[15:32] <mhall119> dholbach: what's the point in advertising your Ubuntu Hour for December in June?
[15:32] <costales> mhall119: maybe the mettings for the next 2/3 days, because the posts are in the planet 2/3 days
[15:32] <dholbach> no, not like that
[15:33] <mhall119> the feed would show "the current loco activity"
[15:33] <dholbach> you said "not future ones"
[15:33] <belkinsa> mhall119, assuming they will post a blog post about that event/meeting?
[15:33] <dholbach> that's why I thought "well, some advance notice would probably help getting others there" :-)
[15:33] <dholbach> so yeah, 24h or whatever timing we finetune it to later on
[15:33] <belkinsa> Same here.
[15:34] <mhall119> ok, fine-tuning that is easy enough
[15:34] <dholbach> yeah, sorry - that's what I meant
[15:34] <mhall119> dholbach: are you taking notes on this somewhere that we can turn into work items or bug reports?
[15:34] <ishwon> Aaah! I was having dinner & I guess I missed a lot.
[15:34] <dholbach> I took an action at UOS to turn this into a mini-spec
[15:34] <ishwon> Hi folks!
[15:34] <dholbach> I'll save the irc logs and write something up next week.
[15:35] <dholbach> Would anyone want to help turn this into a mini-spec?
[15:35] <daker> mhall119: yes we can do that
[15:35] <dholbach> Once it's done, I'd bring up the discussion on loco-contacts@ and<EMAIL_ADDRESS>[15:35] <costales> Hi ishwon o/
[15:36] <mhall119> dholbach: daker: how about having a hackday on IRC where we try and get new contributors setup with an LTP development environment?  currently it's only daker working on it and he's also working on about a dozen other Ubuntu projects
[15:36] <dholbach> sure sure
[15:36] <dholbach> that was the idea behind the spec
[15:36] <dholbach> if we put it out there and blog about it, it'll be more likely that others help out
[15:36] <coolbhavi> dholbach, great thanks :) I would be glad to help for a mini spec here btw
[15:36] <dholbach> having a hackday accompanying that sounds great
[15:36] <daker> mhall119: hm this reminds me that i didn't get a reponse about RT ticket from IS
[15:36] <dholbach> thanks coolbhavi
[15:37] <ishwon> Scrolling through the chat log ( :
[15:37] <mhall119> daker: RT for what?
[15:38] <daker> mhall119: i released a new LTP version with some fixes last Saturday
[15:38] <mhall119> ah, ok
[15:39] <mhall119> daker: they had a DC outage over the weekend, so it may have been lost or forgotten in the mayhem
[15:39] <PabloRubianes> daker: I made a bug on the LTP and a possible fix but maybe got unnoticed
[15:39] <daker> mhall119: i'll ask later
[15:39] <dholbach> does anyone else have any more ideas/questions/concerns/anything else on the topic? if not Bhavani and I (anyone else?) will digest the irc logs and massage them into a mini-spec and bring it up for discussion on the lists again.
[15:40] <dholbach> ... and we can discuss it some more at that time. :)
[15:40] <coolbhavi> good with it here
[15:40] <coolbhavi> :)
[15:40] <mhall119> dholbach: do you think we need to ask permission before adding the LTP feeds to the planet aggregation?
[15:40] <mhall119> or, since we're Ubuntu Members, can we JFDI?
[15:41] <dholbach> mhall119, I think we should discuss it with the Community Council and maybe have a brief history of content to look back to.
[15:41] <mhall119> ok
[15:41] <dholbach> I could imagine that it'd be a very short discussion as it's going to very much on-topic. :)
[15:41] <mhall119> ok
[15:42] <dholbach> Brilliant! Thanks a lot everyone! I'm very much looking forward to reading more from teams around the world! :-D
[15:42] <belkinsa> Thanks for the meeting, dholbach!
[15:42] <coolbhavi> dholbach, ll bring up a small wiki page reg ideas and get in touch with you on weekend :)
[15:42] <coolbhavi> thanks btw
[15:42] <dholbach> coolbhavi, brilliant
[15:42] <mhall119> thanks daker for your continued work on LTP
[15:42] <dholbach> yeah, daker - you're a hero!
[15:42] <daker> mhall119: dholbach yw :)
[15:43] <dholbach> thanks a lot to all the other heroines and heroes in here as well :)
[15:43] <belkinsa> \o/
[15:43] <coolbhavi> :)
[15:43] <daker> PabloRubianes: i saw it, i'll review it during the w-e
[15:43] <PabloRubianes> daker: thanks
[15:44] <costales> Thank you! \o/
[15:44] <costales> It was a pleasure
[15:44]  * coolbhavi goes and grabs some dinner


 Goodbye.
[09:39] <jo-erlend> hey. What's the status of https://launchpad.net/couchdb-glib?
[10:10] <rye> morning
[11:24]  * webm0nk3y pokes his head in
[12:56] <Chipaca> jo-erlend: ask rodrigo?
[14:07] <webm0nk3y> good morning Ubuntu One world
[14:55]  * webm0nk3y looks at joshuahoover
[14:55] <joshuahoover> webm0nk3y: yes?
[14:55] <webm0nk3y> just lookin


[03:43] <coolstar-pc> How do I prevent Unity from trying to put my app's menu at the top of the screen, as it fails, and my app is almost useless without that menu.
[05:22] <jo-erlend> coolstar-pc, why does it fail?
[05:23] <jo-erlend> but you can provide an environment variable when launching the application in order to deactivate global menu. I don't remember exactly what it's called, though.
[05:27] <jo-erlend> coolstar-pc, UBUNTU_MENUPROXY=0 command. For instance, "UBUNTU_MENUPROXY=0 gcalctool" will run the calculator without integrating its menu with the top panel.
[05:46] <coolstar-pc> jo-erlend: Is there a way to have it in the python code?
[05:46] <jo-erlend> you could set that variable from your main method, for instance.
[05:46] <jo-erlend> or, at least I think so. I'm not entirely sure, actually.
[05:51] <jo-erlend> it probably only affects subprocesses, so it's possible that your main code would have to set the environment variable using something like os.putenv("UBUNTU_MENUPROXY", "0"), then run your application as a subprocess and exit.
[05:52] <coolstar-pc> ok. I'll try that
[05:54] <jo-erlend> but if there's a problem with how the menubar works with your application, then I would recommend that you investigate what's causing it. Perhaps you're doing something wrong in your app, or that there's a bug in the menubar implementation? In both cases, you should try to fix the problem instead of avoiding it.
[05:55] <coolstar-pc> jo-erlend: It might be because i'm putting the menubar in an icon at the right of the toolbar (like chrome), and Unity is trying to put it at the top
[06:02] <jo-erlend> ok... Then my suggestion would be that if UBUNTU_MENUPROXY is "0" or not set, then you show that icon. Otherwise, you let Ubuntu use its global menu. It is a bad idea to design your application to break with its environment.
[06:04] <coolstar-pc> jo-erlend: I developed my App in Ubuntu 10.10, and I saw that when running in Unity, the app doesn't show the menu icon, but in KDE or XFCE it shows.
[06:04] <coolstar-pc> It works fine in Ubuntu 10.10
[06:04] <jo-erlend> the _icon_ is hidden?
[06:04] <coolstar-pc> Unity tries to move the icon to the top apparently, and fails
[06:04] <jo-erlend> uh..
[06:05] <jo-erlend> it sounds to me like you're doing something wrong.
[07:25] <umpirsky> Hi developers. I have problem adding appindicator to my PyGTK app. When I place this https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#Python_version into my __init__.py, before gtk.main(), it works, but when I put it in my main window finish_initializing() method, it does not get showed.
[07:26] <umpirsky> If you look at http://bazaar.launchpad.net/~quickly-committers/quickly/trunk/view/head:/data/templates/ubuntu-application/project_root/python_lib/Window.py#L72 they suggest to put it in indicator.py
[07:26] <umpirsky> I don't have idea how that file should look like.
[07:27] <umpirsky> And why it works only in __init__.py
[09:29] <umpirsky> Hi. Can someone point me to some website/blog/wiki where I can read what are the best practices for creating theme dependent appindicator icons? I found nothing on https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators and https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines.
[09:30] <umpirsky> Basicly I'm lost. I' not sure what icons I can rely on, and if I create my own, how should they look and how to determine active theme e.t.c.
[09:32] <umpirsky> It says "
[09:33] <umpirsky> It says "Themable panel icons – you can set a specific icon to be a panel icon for an indicator: this should make it easier for creating single colour panel icons for light and dark themes." but it does not say how to do it?


[00:05] <Scary_Guy> Fun on Mint and I've been doing this for a while.  I delete the Documents/Downloads folders in ~/ and just make links to similarly named directories on a larger drive.  Works fine.
[00:06] <Scary_Guy> Well, LMDE4, but I'm sure it'd work on Ubuntu as well.
[22:13] <jrwren> everytime I see impish, I'm like... WTF is impish... thinking it is old from 26yrs ago. lul.
[22:59] <cmaloney> Heh


[15:06] <sur5r> hi everyone. can anyone tell me how to proceed when i consistently get oopses when trying to log in to launchpad? ubuntuone login itself is working...
[15:57] <cjwatson> sur5r: Can you give us the OOPS ID?
[16:03] <cjwatson> sur5r: (we can fix it for you if you do)
[16:04] <sur5r> let me generate a new one *g*
[16:05] <sur5r>  OOPS-276c9cbd23332010a7cfaefde7ab8da2
[16:06] <sur5r> cjwatson: there you go
[16:07] <cjwatson> thanks.  oh for goodness's sake, oops.c.c is lagging again.  this may take a while - how about I email you when it's done?
[16:08] <sur5r> no hurry
[16:08] <sur5r> i fighting this for months now
[16:08] <sur5r> *i'm
[16:09] <cjwatson> OK, we should really fix this damn bug - https://bugs.launchpad.net/launchpad/+bug/1607242
[16:09] <cjwatson> which is almost certainly what you're running into
[16:09] <sur5r> i suspected sth. like that
[16:09] <sur5r> because my mail address is known to launchpad because of debian packages i maintain
[16:09] <cjwatson> right, a typical case
[16:09] <cjwatson> anyway, we have a strategy to fix it, I'll do it once the oops analysis system catches up
[16:10] <sur5r> thanks a lot
[16:11] <sur5r> btw<EMAIL_ADDRESS>seems to be aliased to /dev/null
[16:12] <sur5r> or isd-support@ whatever
[16:13] <cjwatson> I don't know about that part of it I'm afraid
[16:13] <sur5r> i thought as much
[16:14] <sur5r> it's just that those addresses are where you end up when trying to use mail to solve the problem
[16:14] <sur5r> should've come here right away *g*
[16:15] <cjwatson> trying to find out where it currently goes
[16:23] <cjwatson> apparently it goes to an RT queue that I've been meaning to get access to for ages and have never got round to it, so I'll chase that up
[16:28] <sur5r> *G*


[03:03] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Impish Beta] has been updated (20210923)
[06:30] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Impish Beta] has been updated (20210923)
[06:37] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Impish Beta] has been updated (20210923)
[07:59] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Impish Beta] has been marked as ready
[11:38] -queuebot:#ubuntu-quality- Builds: Xubuntu Desktop amd64 [Impish Beta] has been marked as ready
[11:40] -queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Impish Beta] has been marked as ready
[14:23] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Impish Beta] has been marked as ready
[14:36] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Impish Beta] has been marked as ready
[15:32] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Impish Beta] has been updated (20210923)
[17:36] <franksmcb> Bridge test IRC side
[17:45] <RikMills> Aug 13 02:46:42 * ubuntubridgebot_ has quit (Ping timeout: 240 seconds)
[17:45] <RikMills> last time seen
[19:01] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Impish Beta] has been updated (20210923)
[19:42] <bdmurray> Has anybody seen the disc check message when doing installations?
[20:39] <fossfreedom> No. Good spot
[20:51] <RikMills> wasn't that changed to run in the background?
[20:53] <RikMills> https://launchpad.net/ubuntu/+source/casper/1.457
[20:53] <RikMills> i.e. not show during boot
[20:57] <RikMills> if that is what you meant, anyway
[21:05] <bdmurray> RikMills: that's what I meant thanks!
[22:09] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Impish Beta] has been marked as ready
[22:52] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop amd64 [Impish Beta] has been marked as ready
[22:52] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop arm64+raspi [Impish Beta] has been marked as ready
[22:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Impish Beta] has been marked as ready
[22:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity ppc64el [Impish Beta] has been marked as ready
[22:55] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity arm64 [Impish Beta] has been marked as ready
[22:55] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity s390x [Impish Beta] has been marked as ready
[23:24] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server arm64+raspi [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unleashed [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unmatched [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Impish Beta] has been marked as ready
[23:54] -queuebot:#ubuntu-quality- Builds: Ubuntu Server armhf+raspi [Impish Beta] has been marked as ready