[13:19] <RRWa> What component is responsible for automatic screen locking. Does it rely on a third party application like xautolock? Or is that provided by power management?
 rrwa is on power management and also has options in xscreensaver


[15:51] <cjohnston> joey: stop that! :-P
[15:52] <joey> cjohnston: :) Stu M asked for all the really important ones to Linaro so I've just been tagging them so he can view them easier
[15:52] <cjohnston> lol
[15:54] <nigelb> joey: Good that you did that actually.
[15:54] <nigelb> I think at least 2 of them are committed already :)
[15:56] <joey> cjohnston: nigelb - there is really one big one left that's not there and I suspect it maybe be meaningful as a bug...  simplifying the system so a non-technical admin can create, delete, etc (i.e. fix permissions and not require everyone to be super users).  There are a lot of actions there because this also includes killing the perception that summit is unreliable. So I'm not going to bug that as I said it.
[15:56] <joey> oops
[15:57] <joey> s/maybe be meaningful/will NOT be meaningful/
[15:57] <joey> I think we have to attack that as individual items
[15:57] <nigelb> Yes, we do.
[15:57] <nigelb> I'm fixing the "summit is unreliable" thing mostly.
[15:57] <nigelb> so, the rescheduler and autoscheduler are now fixed.
[15:58] <nigelb> Now, I need to go through render.py and fix all its problems that make it break all of a sudden.
[15:58] <cjohnston> Yes.. That's a whole big issue.. which will require alot.. mhall119 and I began talking about the user permissions on the flight
[15:59] <nigelb> and, for the admin bit.  This calls for us to create a better admin interface than the one we have for at least part of it, like scheduling.
[15:59] <joey> Yeah sadly it's a large refactoring job mixed with some design items
[15:59] <joey>  == lots of work
[15:59] <cjohnston> uh huh
[16:00] <nigelb> Hopefully, you'll find someone to work full time on this, so we can dump all of this on him/her :D
[16:02] <joey> I think that's what Stu was asking. Maybe Canonical will contribute some dev time this cycle
[16:02] <joey> I know I will be via James W and Salgado
[16:03] <nigelb> We heard that a few ISD folks might be spending their free time on summit :)
[16:03] <mhall119> key words there being "might be" and "free time"
[16:04] <mhall119> I don't plan on spending every Sunday afternoon approving merge proposals
[16:05] <mhall119> especially if you keep breaking stuff
[16:05] <nigelb> hey, what did I break?
[16:06] <mhall119> I dunno, cjohnston said you were breaking stuff
[16:06] <mhall119> 08:37 < cjohnston> mhall119: nigelb broke it again
[16:06] <cjohnston> hehehe
[16:06] <nigelb> mhall119: You need to stop believing everything cjohnston says.
[16:07] <nigelb> mhall119: He just said that because I didn't fix his tracker ;)
[16:07] <nigelb> (which was because the tracker took overnight to get the data :/)
[16:07] <mhall119> cjohnston wouldn't lie to me
[16:07] <cjohnston> +1
[16:07] <mhall119> cjohnston: would you ever lie to me?
[16:07] <nigelb> He already has.
[16:07] <cjohnston> We keep telling our kids, delayed obedience is the same as non-obedience.. so not fixing is the same as breaking
[16:08] <mhall119> lol
[16:08] <mhall119> +1 on that
[16:08] <nigelb> haha
[16:08] <cjohnston> mhall119: never ;-) I saw nigelb drinking that 'soda'
[16:08] <mhall119> yeah, 8 glasses of it
[16:08] <nigelb> bwahaha
[16:08] <cjohnston> and I have a picture of nigelb with the 'soda'
[16:08] <nigelb> speaking of which, is zach on IRC?
[16:08] <cjohnston> zach/
[16:08] <cjohnston> ?
[16:08] <mhall119> BBQ guy
[16:09] <cjohnston> Pfeffer?
[16:09] <nigelb> mhall119: cjohnston forgets his name. Of all the people.
[16:09] <cjohnston> I know a couple zach's in the ubuntuish world
[16:09] <cjohnston> joey: ^^
[16:09] <mhall119> joey isn't a zach, he's a joey
[16:09] <nigelb> cjohnston: Of course I met Pfeffer :)
[16:09] <nigelb> lol
[16:10] <joey> yeah he's on #linaro
[16:10] <joey> pfefferz or zpfeffer
[16:10] <nigelb> mhall119: btw, I have fixed 2 things on LP that's annoying for sprints.  Once the sprint page will sort by displayname instead of name.  The blueprints page should soon do that same.
[16:10] <nigelb> s/Once/One is/g
[16:10] <mhall119> nigelb: nice
[16:10] <nigelb> and cjohnston fixed the required field to have better description
[16:11]  * nigelb ^5 cjohnston
[16:11] <cjohnston> and particiapation essential is no longer required!
[16:11] <mhall119> I gotta admit, I'm both jealous and proud seeing you guys fixing LP bugs
[16:12] <cjohnston> :-P
[16:14] <nigelb> mhall119: If its any satisfaction. It isn't easy.  Its a lot of dead code, especially blueprints.
[16:37] <nigelb> cjohnston: who's the person doing the guidebook coordination?
[16:37] <nigelb> david barth?
[16:38] <cjohnston> mandella
[16:38] <nigelb> cjohnston: the ARM person?
[16:38] <cjohnston> I believe he is canonical
[16:39] <cjohnston> You reminded me of something, so I just PMed him
[16:40] <nigelb> anyway, I'm working on that colors bug this week, so I might need your help coordinating with him
[16:40] <cjohnston> ok. how so?
[16:40] <nigelb> mhall119: If I can fix the colors bug for ical, can we do a deploy so we can figure out if the guidebook folks are happy?
[16:41] <nigelb> cjohnston: We need to give them the ical so they can update their app.
[16:41] <cjohnston> gotcha
[16:41] <cjohnston> We could apply it to this last uds and they could use that
[16:41] <cjohnston> I believe
[16:41] <nigelb> Yup, we'll need to deploy and ask them to test.
[16:55] <cjohnston> mhall119: nigelb YoBoY https://launchpad.net/community-web-projects
[16:56] <nigelb> *whee*
[16:56] <nigelb> cjohnston: add summit, hof, team-reports
[16:56]  * YoBoY hugs cjohnston
[16:56] <cjohnston> I already did nigelb
[16:56] <cjohnston> thats what im confused about
[16:58] <YoBoY> are you the owner (or admin) of the other projects ? perhaps they have to accept or something like that
[16:59] <cjohnston> Yes.. you add them from edit details on the other project, not in the new project
[16:59] <YoBoY> (stupid remark, summit is already marked as part of the group :] )
[17:00] <cjohnston> I see that.. but the community-web-projects (atleast the front page) doesnt show anything other thann LTP
[17:01] <YoBoY> yes, the code tab is ok, all the project are there
[17:01] <YoBoY> just the frontpage... strange ^^
[17:01] <nigelb> cjohnston: cache probably. Should be cleared in some time.
[17:01] <nigelb> but its worth notifying LP folks.
[17:02] <cjohnston> already did
[17:06] <YoBoY> ok it's a bug https://edge.launchpad.net/community-web-projects we can see all the projects on the edge version of LP :)
[17:13] <nigelb> YoBoY: not a bug, just cache.
[17:13] <nigelb> and edge should really be deprecated :)
[17:14] <YoBoY> ^^
[17:14] <YoBoY> i don't use it
[17:19] <YoBoY> question : should it be possible and accurate  to have a unique "community-web-team" and not a team for each project ? If I look the members of each teams, I can find the same people in every teams
[17:21] <cjohnston> YoBoY: the only thing is that they have commit access, so if we can get new developers for one team, do we want to give them commit to everything
[17:23] <YoBoY> yes, right, but if you give the membership to someone, it's because you trust this person. new devs always contribute with merge proposals
[17:33] <mhall119> just make all the project-teams members of the global team
[18:28] <nigelb> cjohnston: lol, I just realized something.
[18:28] <nigelb> I can do all my LP testing with my local launchpad!
[18:28] <nigelb> create BP, import them, and all that :D
[18:55] <mhall119> cjohnston: make a global team, make it delegated like ~ubuntu-locoteams
[18:56] <cjohnston> k
[19:39] <cjohnston> MTecknology: ping
[19:52] <mhall119> can someone post the style guide url?
[19:52] <mhall119> or even just the community-orange hex cofr
[19:52] <mhall119> code
[19:54] <YoBoY> HEX #DD4814
[19:55] <YoBoY> http://design.canonical.com/the-toolkit/guides-for-websites/
[19:55] <mhall119> thanks YoBoY
[19:55] <YoBoY> de rien :)
[20:02] <mhall119> cjohnston: nigelb: https://launchpad.net/summit check out the icon
[20:02] <cjohnston> lol
[20:03] <nigelb> mhall119: Nice :)
[20:03] <cjohnston> now make one for LTP
[20:03] <nigelb> mhall119: who did that?
[20:03] <nigelb> doctormo?
[20:03] <nigelb> cjohnston: It already does haev
[20:03] <nigelb> *have one
[20:03] <mhall119> nigelb: I did
[20:03] <cjohnston> i dont get that one tho
[20:03] <mhall119> cjohnston: LD already has an icon
[20:03] <mhall119> cjohnston: don't get which one?
[20:03] <cjohnston> ld
[20:04] <nigelb> mhall119: WOW, you're awesome :)
[20:04] <mhall119> it's a directory
[20:04] <cjohnston> but its LTP :-P
[20:04] <mhall119> so we'll change it
[20:04] <MTecknology> cjohnston: hi
[20:04] <cjohnston> lol
[20:04] <mhall119> once we rebrand
[20:05] <cjohnston> MTecknology: could you add ubuntu-drupal as a member of community-web-projects? we are trying to put all community web projects together
[20:06] <MTecknology> https://launchpad.net/~community-web-projects
[20:06] <MTecknology> 404
[20:06] <cjohnston> https://launchpad.net/community-web-projects   its a project group
[20:06] <MTecknology> you want to make an umbrella project part of an umbrella project?
[20:07] <cjohnston> hmm
[20:07] <mhall119> nesting FTW!
[20:07] <cjohnston> lol
[20:08] <MTecknology> cjohnston: not even possible
[20:08] <cjohnston> :-/
[20:09] <MTecknology> Only projects can be 'Part of' other projects; project groups are separate entities in that regard
[20:09] <MTecknology> just checked
[20:09] <cjohnston> gotcha
[20:12] <MTecknology> time for court- ttyal
[20:12] <cjohnston> o/
[20:21] <YoBoY> cjohnston: ubuntu-drupal don't have the same goals as the community-web-projects, we focus only on existing or work in progress webapps and shared ressources for them who are accessible with a *.ubuntu.com url
[20:22] <mhall119> I think that does fall under the goal of community-web-projects
[22:04] <cjohnston> Is anyone in here good with making changes to screenshots?
[22:19] <MTecknology> dpes anyone in here know anything about drupal and the inner workings of ubuntu?
[22:20] <MTecknology> the ubuntu community*
[22:21] <MTecknology> cjohnston: you have a clue, right?
[22:30] <YoBoY> cjohnston: depends, but forget, don't have time this week


[16:47] <pleia2> putting a2 announcement on fridge
[16:47] <jose> thanks, pleia2 :)
[16:47] <wxl> yes indeed
[16:47] <wxl> hopefully you saw the one on -devel-announce
[16:47] <wxl> as the one on -release has some errors in it
[16:47] <wxl> my bad
[16:47] <wxl> but it's an alpha release, so you can expect bugs, right? :)
[16:49] <pleia2> I'll use the devel-announce one, thanks :)
[16:49] <wxl> pleia2: there's also a proper one at VividVervet/Alpha2/ReleaseAnnouncement
[16:50] <pleia2> we have a script that converts mailing list posts, then we reference the mailing list announcement
[16:50] <jose> it's automagic!
[16:51] <wxl> whoa
[16:51] <wxl> mind blown
[16:52] <pleia2> that's what you get when technical people run your news team ;)
[16:52] <wxl> hehehe
[16:53] <wxl> you guys don't have a link check script do you?
[16:53] <pleia2> anyway, it's up now, will land on planet in like 2423 hours
[16:53] <pleia2> we have a few, but wiki.ubuntu.com is annoying and I think Unit193 just uses a website now to do that
[16:53] <pleia2> (the wiki times out too quickly for most link checkers)
[16:53] <wxl> huh cuz i was thinking about something that could grab all the subpages of a particular wiki and check them all
[16:54] <pleia2> unfortunately the wiki is very slow to load
[16:54] <wxl> yeah
[16:54] <wxl> Unit193: whatcha think about link checking the wiki?
[17:01] <PaulW2U> wxl: the devel-announce item was added to the prep doc *ages* ago
[17:01] <wxl> PaulW2U: just checking :)
[17:06]  * PaulW2U thinks issue #401 is going to be a big one
[20:05] <pleia2> somehow spammers are using the ubuntu/ubuntu user account (bypassing SSO?) and creating lots of spammy drafts, submitted a ticket with IS about it
[20:05] <wxl> oh great
[20:05] <wxl> just when they're backed up :(
[20:06] <pleia2> they're always backed up
[20:06] <wxl> well the holidays didn't help
[20:07] <pleia2> ah, yeah, long break for canonical folks
[20:07] <pleia2> I think I've got 3-4 tickets in flight with them now :\
[20:10] <pleia2> they must love me
[20:10] <pleia2> in the "oy, her again!" way ;)
[20:54] <Unit193> wxl: What page?
[20:59] <wxl> Unit193: in general
[20:59] <Unit193> Have fun.


[06:29] <ricotz> good morning desktopers
[06:29] <ricotz> mdeslaur, https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1796625
[06:30] <duflu> Hi ricotz
[06:47] <seb128> good morning desktopers
[06:55] <duflu> Hi seb128
[06:58] <seb128> hey duflu, how are you? had a good w.e,
[06:59] <duflu> seb128, Hi. Felt good about getting up early but now it hurts. Although that's probably all the gardening I did. How are you?
[07:00] <duflu> seb128, also do you know what package owns/creates /etc/default/grub?
[07:03] <jibel> good morning
[07:04] <jibel> duflu, grub2
[07:05] <duflu> jibel, thanks, I should have checked the source since that's the most likely answer
[07:05] <duflu> Hi ji
[07:05] <duflu> Hi jibel
[07:19] <didrocks> good morning
[07:21] <duflu> Morning didrocks
[07:21] <didrocks> hey duflu
[07:58] <willcooke> morning
[07:58] <willcooke> brrrrrr
[07:58] <willcooke> cold today :(
[07:58] <didrocks> hey brrrrrrring willcooke
[08:00] <oSoMoN> good morning desktoppers
[08:00] <duflu> Morning willcooke (now brought?), oSoMoN
[08:02] <Laney> hey ho
[08:03] <willcooke> Could someone help with a version of gdm which includes Ray's fix: https://gitlab.gnome.org/GNOME/gdm/merge_requests/37#note_340480
[08:03] <willcooke> for testing
[08:03] <gitbot> GNOME issue (Merge request) 37 in gdm "WIP! local-display-factory: defer initialization for CanGraphical=no seats" [Opened]
[08:04] <didrocks> salut oSoMoN, hey Laney!
[08:06] <didrocks> willcooke: I have another gdm fix, so if people getting that bug can confirm this fixes for them, I'm happy afterwards to see if as a side-effects, it solves my issue (I had to revert gdm to previous version, as I can't even keep my session running with that gdm issue)
[08:09] <willcooke> didrocks, ack
[08:13] <seb128> duflu, I see you got your reply for grub :)
[08:13] <seb128> hey Laney didrocks willcooke
[08:13] <seb128> how is everyone?
[08:13] <seb128> duflu, I'm ok, did end up getting the baby stomach bug though, started being sick on friday evening :/
[08:13] <seb128> I'm better today though
[08:14] <duflu> seb128, sorry to hear, and now good to hear
[08:14] <willcooke> :(
[08:14] <seb128> didrocks, you got a fix from your gdm bug? nice!
[08:15] <duflu> seb128, I would like to propose a drop in the default grub timeout since it's an easy win of up to 10 seconds faster boots. However I'm confused as to whether 1 second is really any better than 0. Both seem to be OK with quickly pressing Escape
[08:16] <duflu> so recovery still works
[08:16] <seb128> duflu, we do wait for 10s by default? that's only when other OSes are available though?
[08:17] <duflu> seb128, yes all machines. And no none of my machines have other OSes. They all start with wiped disks
[08:17] <seb128> my machines don't stuck at grub for 10s for pretty sure
[08:18] <didrocks> hey seb128! not for my bug, for will's one
[08:18] <duflu> Do they take more than 10s to boot from off to login screen? If so they might be
[08:18] <didrocks> seb128: I'll see if that fixes mine once they confirm it fixes for them (seems quite unrelated, but you never know)
[08:18] <didrocks> seb128: hope that you will stay strong vs stomach bug ;)
[08:19] <seb128> thx
[08:19] <seb128> ah, so it's not another fix
[08:19] <seb128> I parsed wrong what you wrong
[08:19] <seb128> let's see yeah
[08:23] <Laney> hey didrocks seb128 duflu willcooke
[08:23] <willcooke> hihihi all
[08:23] <duflu> Hi Laney
[08:23] <Laney> sup
[08:29] <seb128> it's cold this morning, like 3°C during the night, brrr
[08:34] <seb128> duflu, I would be pretty surprised if all Ubuntu machines were stucked by default in grub for 10s. Mine take longer than that to get to gdm but it goes to plymouth before those 10s afaik, also I've looked at bootcharts and there is no such gap ... or is that recent cosmic regression?
[08:34] <willcooke> I havent seen any 10s waits on my testing
[08:35] <duflu> willcooke, how long is your blank purple screen?
[08:35] <duflu> seb128, I have tried 3-4 laptops with cosmic and they all have the problem
[08:35] <willcooke> duflu, will test
[08:35] <duflu> and all benefit from the fix
[08:35] <seb128> that's a new issue in cosmic?
[08:35] <duflu> Also it seems someone said it is in bionic
[08:35] <duflu> haven't verified
[08:35] <seb128> that doesn't make any sense to me
[08:35] <willcooke> hm
[08:35] <duflu> Maybe so, but still true
[08:36] <seb128> on bionic I would be verify surprised
[08:36] <willcooke> now I come to look at it, there is about 13 seconds of purple
[08:36] <seb128> I didn't pay attention enough to cosmic boot, maybe it's true there
[08:36] <duflu> willcooke, and 3 seconds of kernel, remember :)
[08:37] <duflu> seb128, also note that the grub delay probably doesn't show up in the boot chart. It preceeds the kernel
[08:37] <duflu> Anyway, my laptops were around 20 seconds before and now more like 10 seconds or less
[08:37] <seb128> please open a bug and rls-cc-incoming it so foundations can have a look
[08:38] <willcooke> duflu, can I make a change to the grub config and retest easily
[08:38] <willcooke> ?
[08:38] <duflu> willcooke, /etc/default/grub GRUB_TIMEOUT = 0 and then sudo update-grub
[08:39] <duflu> it will knock your socks off
[08:39] <willcooke> duflu,  I can just put that right at the end of the cfg file right?
[08:39] <willcooke> oh
[08:39] <willcooke> wrong file
[08:39] <willcooke> ignore m,e
[08:39] <willcooke> me
[08:39] <duflu> willcooke, probably edit the line
[08:40] <willcooke> hm, I think it *is* a bit quicker
[08:40] <willcooke> not 10 seconds
[08:40] <willcooke> but maybe 3 or 4
[08:40] <duflu> willcooke, did you remember 'sudo update-grub' ?
[08:41] <willcooke> I did
[08:41] <willcooke> I'll do some better tests
[08:44]  * didrocks starts his laptop and goes to make coffee, so I didn't pay that much attention to the purple screen before plymouth starts
[08:44] <duflu> The blank purple screen mostly indicates the kernel isn't started yet, so that's a performance bug if it lingers
[08:52] <willcooke> Timeout 10: 19,18,24s.  Timeout 0: 9,10,15,9
[08:52] <willcooke> That 15 in the timeout zero was when gdm actually started
[08:52] <willcooke> so yes, it does rather look like there is a 10s wait
[08:52] <willcooke> nice find duflu
[08:53] <duflu> Woo. Although it sounds like someone already found it in bionic
[08:53] <duflu> bug 1784363
[08:53] <duflu> I've never looked at boot charts but would guess they only start when the kernel does
[08:57] <seb128> duflu, that bug claims it's a regression from https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.2 so it wouldn't have been in bionic but due to a SRU
[08:58] <duflu> seb128, maybe. That user doesn't sound completely clear so we would need to check the facts
[08:58] <duflu> Although it doesn't change whether the issue is in cosmic
[08:58] <seb128> http://launchpadlibrarian.net/378957376/grub2_2.02-2ubuntu8.1_2.02-2ubuntu8.2.diff.gz
[08:58] <seb128> -DEFAULT_HIDDEN_TIMEOUT := 0
[08:58] <seb128> that tweaks around those parameters
[08:59] <seb128> so it's possible
[08:59] <seb128> well, it's even more important if it's a SRU regression in bionic
[08:59] <duflu> It looks like there are multiple variables allowing you to change the same thing
[08:59] <seb128> anyway it's tagged, let's wait for foundations to reply
[08:59] <seb128> right
[09:00] <seb128> but if the change made it hit a timeout it wasn't hitting before, then maybe there is a bug in the new variables use
[09:00] <seb128> or a misuse
[09:00] <didrocks> do any of you have a bionic machine with GNOME Boxes installed?
[09:00] <duflu> Yeah sounds like the "timeout" was always 10 seconds. We just accidentally started using that variable recently
[09:01] <didrocks> duflu: this timeout is (IIRC) triggered if you have grub menu displayed and didn't press anything
[09:01] <didrocks> like previous boot failing
[09:01] <didrocks> (but yeah, shouldn't be used if you didn't touch anything ofc)
[09:03] <seb128> what didrocks says
[09:03] <willcooke> duflu, seb128 I've pinged Pat and Steve to see what they say
[09:03] <seb128> willcooke, thx, I was pondering emailing them, good that you beat me to it :)
[09:03] <willcooke> :)
[09:05] <willcooke> I'm an email machine this morning 💪💪
[09:07]  * didrocks boots a live on his secondary laptop to check Boxes on 18.04 thus
[09:07] <seb128> didrocks, I'm not using boxes sorry
[09:07] <didrocks> no worry
[09:07] <seb128> virtualbox here :)
[09:07] <seb128> what's the bug you are looking at?
[09:08] <didrocks> but I think Boxes changed the default for ubuntu to be 1GB
[09:08] <didrocks> the one I added to the iso tracker: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1796037
[09:09] <duflu> Laney, my gjs fix landed already B) If you were still considering an update then maybe also cherry pick?
[09:13] <Laney> duflu: did you want to propose it for cherry picking to the stable branch upstream?
[09:13] <duflu> Laney, yes I can
[09:13] <duflu> it needs to be in cosmic before we finish the gnome-shell leak fix SRU to bionic anyway
[09:25] <duflu> Laney, https://gitlab.gnome.org/GNOME/gjs/merge_requests/238
[09:25] <gitbot> GNOME issue (Merge request) 238 in gjs "context: Defer and therefore batch forced GC runs [performance]" [Opened]
[09:25] <Laney> 👍
[09:26] <didrocks> confirmed, Boxes changed between bionic and cosmic the default RAM size for ubuntu iso
[09:26] <didrocks> (from 2Gb to 1Gb)
[09:27] <Laney> 👎
[09:28] <didrocks> emoji day for Laney ;)
[09:28] <didrocks> I'm going to have a look if this is per-distro, global…
[09:33] <didrocks> ok, it's not BOXES deciding the RAM size, maybe libvirt?
[09:39] <didrocks> hum, can't revert easily libvirt…
[09:41] <seb128> didrocks, it's coming from libvirt?
[09:41] <didrocks> seb128: don't know, it's not coming from Boxes as least…
[09:42] <seb128> didrocks, https://gitlab.gnome.org/GNOME/gnome-boxes/commit/aaef956f6733df30ecf9ab860afc4bda244c4225
[09:42] <seb128> that's old though, maybe changed since
[09:43] <didrocks> seb128: I have installed bionic version on my cosmic install, and it was still 1Gb, let me see if the current code base is similar to what you saw
[09:43] <didrocks> (it might come as well from libosinfo?)
[09:43] <didrocks>     private const int64 DEFAULT_RAM = 2 * (int64) GIBIBYTES;
[09:44] <didrocks> so, something overrides that
[09:44] <seb128> ask teuf?
[09:45] <didrocks> ah, and osinfo-db as well
[09:45] <didrocks> yeah, if reverting those 2 doesn't work, that's my plan ^
[09:47] <didrocks> found!
[09:47] <didrocks> so, it's osinfo-db
[09:47] <didrocks> let's see why now…
[09:50] <didrocks> ok, the regression is in this diff: http://launchpadlibrarian.net/390925704/osinfo-db_0.20180917-1_0.20180929-1.diff.gz
[09:50] <didrocks> between the 17/09 and 29/09
[09:50] <didrocks> should be easy enough :)
[09:50] <willcooke> Nice detective skills didrocks
[09:51] <didrocks> heh, /me takes his magnifying glass to inspect the culpurit :p
[09:51] <didrocks> +        <ram>1073741824</ram>
[09:51] <didrocks> ok, they added support for 18.10 (it was fallbacking to default before I think) and mistyped the ram usage
[09:52] <didrocks> so basically, it's only if starting a cosmic image with very recent osinfo-db
[09:53] <didrocks> hum, 18.04 had the same property, let's try a 18.04 with this version (need to download an iso first)
[09:56] <didrocks> ok, GNOME Boxes on 18.04 hadn't a 18.04 definition, so fallbacked to what seb128 wrote (2Gb)
[09:56] <didrocks> but now, is has one to 1Gb as well
[09:57] <didrocks> so, I wonder, should we bump them to 2Gb? (1.5 is our official minimum, unsure it's tested with this though)
[09:57] <andyrock> anyone willing to take a look at this MR: https://code.launchpad.net/~azzar1/update-manager/lp-1787553-bionic/+merge/354455 ?
[09:57] <didrocks> as before, they were starting with 2Gb
[09:57] <didrocks> and what about 16.04, now that they have snapd, should we change them to 2Gb as well?
[09:57] <didrocks> (as the issue we are seeing in snapd spiking in CPU when going OOM)
[09:58] <didrocks> jibel: seb128: willcooke: Laney ^
[10:00] <jibel> didrocks, 2G is safer. Higher memory consumption started with preseeding of snaps, it made all our automated tests fail. I increased to 1.5 IIRC
[10:00] <willcooke> sounds like a good idea
[10:00] <didrocks> so, fixing 16.04 / 18.04 / 18.10 ?
[10:00] <jibel> yes
[10:00] <didrocks> let me PR that on upstream gitlab
[10:01] <didrocks> I will let until Wednesday and distro-patch if we don't have it merged (but we are currently in sync with debian)
[10:02] <seb128> =pç⁾$
[10:02] <seb128> sorry
[10:02] <seb128> andyrock, I can add to my backlog for a bit later/tomorrow
[10:03] <andyrock> thx!
[10:03] <andyrock> and hey!
[10:03] <seb128> didrocks, yeah, bumping seems fine to me
[10:03] <didrocks> ok, we have aggreement, let's modify our bug, and fix it upstream ;)
[10:04] <didrocks> if this is merged quickly, I'll request a new snapshot in debian + sync
[10:17] <didrocks> any idea why I can't create a MR against libosinfo/osinfo-db on gitlab? I have the list of all other fork, but not the main repo…
[10:19] <Laney> it looks like the project has turned those off (that's an option)
[10:20] <Laney> the readme says to use https://www.redhat.com/mailman/listinfo/libosinfo
[10:20] <didrocks> ah…
[10:20] <didrocks> thanks Laney!
[10:20] <Laney> retro
[10:20] <didrocks> yep
[10:20] <didrocks> I was looking for a CONTRIBUTING.md
[10:21] <didrocks> didn't think about reading the README for this :p
[10:21] <didrocks> thanks ;)
[10:54] <willcooke> tjaalton, hiya - is there any update on the virtualbox issue atm?
[10:55] <tjaalton> willcooke: nope
[10:55] <CarlenWhite> Really wished we had more laptops with extra HDD slots. Wouldn't mind dedicating one to Windows and one to Ubuntu instead of the current tight-ship setup on a 256GB SSD.
[10:55] <tjaalton> filed it upstream, the new patch has been dropped from xserver 1.20.2 queue for now until it's known where the bug is
[10:56] <willcooke> tjaalton, ack.  So we're back to where we were, needing nomodeset for vbox?
[10:56] <tjaalton> if that's the route yes
[10:57] <willcooke> tjaalton, ok.  And is "getting it fixed for release" something which you're actively working on? Like, do I need to formally ask for it to be a priority?
[10:58] <tjaalton> I'd like to know why plymouth starts "too early" now, showing ugly "server splash" instead of the proper thing on these
[10:58] <tjaalton> fixing that race would solve most of the issues
[11:00] <willcooke> tjaalton, is there a bug open for that?
[11:01] <tjaalton> no, all the bugs are for x
[11:01] <willcooke> tjaalton, would you mind opening one, and I can chase up with Foundations?
[11:01] <tjaalton> sure
[11:01] <willcooke> thank you!
[12:05] <Laney> willcooke: did you want to test https://people.canonical.com/~laney/package-junkyard/ ?
[12:21] <willcooke> Laney, word
[12:22] <Laney> brap
[12:30] <willcooke> anyone interested in sponsoring this fix for SRUing to Bionic?  https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1760621
[12:30] <willcooke> patch attached by all accounts
[12:33] <willcooke> nope, there isnt,
[12:33] <willcooke> but I could make one if anyone cares
[12:33] <willcooke> https://github.com/Guake/guake/commit/f8699b4be6c058fd58a33a1d783cd404e9076b0e
[12:34] <willcooke> Laney, hrm.  Installed those packages, but I can't even get a text tty up anymore.  Investigating
[12:53] <willcooke> Laney, Feels the same to me, still getting  a black screeen with the text cursor just as often as gdm
[12:53] <willcooke> will make logs
[12:54] <Laney> k, post them on the MR, you should at least see debugging output from the new stuff
[12:54] <willcooke> ack
[12:54] <willcooke> and yeah, sometimes I dont even get a text tty anymore (probably related)
[13:02] <willcooke> Laney, just to confirm - I only needed to install the debs and not the ddebs too?
[13:02] <Laney> right
[13:02] <willcooke> ta
[13:02] <Laney> you don't need them but if you had them already you'll probably get an error from dpkg if you don't install those too
[13:03] <Laney> I usually do dpkg -iO *deb
[13:03] <willcooke> I'll redo that, just in case
[13:04] <willcooke> I did -dpkg -i * (having only downloaded the debs, but maybe I did someting daft)
[13:35] <Laney> Oct 08 13:55:33 test-Inspiron-3137 gnome-shell[739]: Failed to create backend: Could not find a primary drm kms device
[13:45] <willcooke> Laney, looking at Ray's most recent comment (just a moment ago) - could this be related to Plymouth?  Where something goes from suitable  -> unsuitable -> suitable again?
[13:49] <Laney> willcooke: I dunno, maybe? You could remove it from the kernel cmdline if you wanted to play with that theory
[13:50] <willcooke> Laney, is it the "splash" option?
[13:50] <Laney> quiet splach
[13:51] <Laney> s
[13:51] <willcooke> ack
[13:51] <Laney> but probably get what he's asking for first
[13:51] <willcooke> roger
[13:53] <tjaalton> willcooke: on an uptodate cosmic I see that vboxvideo is loaded early enough after install, there's no race and things work fine
[13:53] <willcooke> tjaalton, oki, lemme try that again
[13:53] <tjaalton> bionic host
[13:54] <willcooke> ack
[13:56] <didrocks> jibel: willcooke: so, on libosinfo, they would like to match the recommended to what we say (4Gb). The issue is that GNOME Boxes will use this by default instead of the minimal
[13:56] <didrocks> I think it's fine, just want another opinion before changing it
[14:03] <jbicha> didrocks: osinfo-db is a bit complicated
[14:04] <didrocks> yeah, it's not only for VM I guess
[14:07] <jbicha> I'm not aware of it being used outsides vms
[14:07] <didrocks> so, I wonder, but seems like they really want the recommended to be set to our wiki page that willcooke edited https://help.ubuntu.com/community/Installation/SystemRequirements?action=diff&rev2=108&rev1=107
[14:07] <jbicha> I think generally the people who maintained Boxes and the osinfo stuff all these years don't really use Ubuntu
[14:08] <jbicha> currently, the same RAM value is used for both the server and desktop editions of Ubuntu
[14:08] <didrocks> willcooke: either we changed on the wiki the recommended Mem to be 4Gb or I change in libosinfo-db, but that means that VM will request 4Gb by default
[14:08] <didrocks> yeah
[14:08] <jbicha> I agree that 4 GB is a ridiculous default for a VM
[14:09] <didrocks> jbicha: want to chat on the ML?
[14:09] <didrocks> maybe having a second opinion will help there
[14:09] <jbicha> yeah I'll comment there
[14:10] <didrocks> thx! still waiting for willcooke/jibel though when they are aroudn
[14:10] <didrocks> around*
[14:12] <jbicha> Boxes/osinfo-db have several papercut issues for Ubuntu
[14:12] <willcooke> meeting
[14:12] <willcooke> reading
[14:13] <jbicha> I'm glad that osinfo-db is a separate package now since it makes it easier to SRU it. we should do an SRU after 18.10's release to include 18.10's info
[14:13] <willcooke> I think it's totally fine to have a difference between "What we recommend for everyone" and "What the default is for a VM"
[14:14] <willcooke> but I might be wrong
[14:14] <willcooke> 4GB for a VM feels to high to me, 2GB seems OK
[14:14] <willcooke> whereas 4GB for a hardware install as a recommendation seems OK to me
[14:15] <didrocks> willcooke: the issue right now is that Boxes is using the "recommended" field and upstream seems to think that they want to align the recommended with what we have in our wiki page
[14:15] <didrocks> willcooke: or… what we could do… Have 4Gb recommended for a daily usage
[14:15] <didrocks> and recommend 2Gb for a VM
[14:15] <willcooke> didrocks, cunning!
[14:15] <didrocks> (like with few browser activity)
[14:15] <willcooke> I like it
[14:15] <didrocks> willcooke: do you mind editing the wiki page with those info?
[14:15] <didrocks> so that it's official :)
[14:15] <willcooke> stand by
[14:16] <didrocks> and I can link by on the mailing list as a reference point :)
[14:18] <willcooke> didrocks, done
[14:19] <didrocks> willcooke: perfect! :)
[14:19] <didrocks> thx, forwarding :)
[14:20] <willcooke> thanks didrocks
[14:20] <willcooke> Laney, 10 out of 10 working boots when removing quiet splash :/
[14:22] <Laney> fun
[14:22] <Laney> that last journal has permission errors in it
[14:22] <Laney> e.g. Oct 08 14:53:19 test-Inspiron-3137 gdm-launch-environment][805]: GdmSessionWorker: could not take control of tty: Operation not permitted
[14:22]  * ricotz hopes this bug gets some real attention https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1795901
[14:22] <Laney> ricotz: #ubuntu-hardened
[14:23] <ricotz> ok
[14:26] <ricotz> Laney, I assume there was some discussion there already?
[14:26] <Laney> I don't know, sorry, I'm not in that one
[14:26] <ricotz> I see, I am making more noise then ;)
[14:37] <willcooke> Laney, pasted a new one with sudo
[14:55] <Laney> willcooke: want to come to #gdm?
[14:55] <Laney> might be faster
[15:57] <seb128> good afternoon desktopers
[15:57] <didrocks> wb seb128
[15:57] <seb128> thx
[15:57] <Laney> yo
[15:58] <Laney> good trip?
[16:00] <oSoMoN> hey seb128
[16:00] <seb128> yeah, pretty fine, a bit of traffic because we left a bit late
[16:04] <willcooke> hey seb128
[16:04] <seb128> ricotz, did you mention the webkitgtk issue on the security channel (they don't have irclogs so I can't look there)?
[16:06] <ricotz> seb128, I did and marc answered
[16:06] <seb128> good
[16:06] <seb128> thx
[16:07] <oSoMoN> anyone fancy reviewing https://code.launchpad.net/~osomon/ubiquity-slideshow-ubuntu/libreoffice-icons-update/+merge/356186 ?
[16:07] <ricotz> seb128, still a bit problematic that this went through without testing
[16:08] <ricotz> or at least insufficient testing
[16:13] <seb128> ricotz, did he comment about that? I expect they do test runtime but not rdepends builds (which they probably should)
[16:15] <didrocks> didrocks@casanier:/tmp$ mkdir foo
[16:15] <didrocks> mkdir: impossible de créer le répertoire «foo»: Le fichier existe
[16:15] <didrocks> didrocks@casanier:/tmp$ mkdir bar
[16:15] <didrocks> mkdir: impossible de créer le répertoire «bar»: Le fichier existe
[16:15] <didrocks> seriously… :p
[16:15]  * didrocks will stop using /tmp and temp names :p
[16:15] <ricotz> seb128, no, he just asked the report
[16:16] <ricotz> *ack'ed
[16:16] <seb128> didrocks, :)
[16:16] <seb128> ricotz, k
[16:16] <seb128> oSoMoN, I can have a look if noone picks it up
[16:16] <seb128> but let me deal with some other backlog first
[16:17] <didrocks> oSoMoN: merged
[16:18] <didrocks> seb128: FYI ^
[16:18] <seb128> didrocks, thx, can you handle the upload as well?
[16:18] <didrocks> seb128: not today, but tomorrow, sure
[16:18] <seb128> k, I might do it today
[16:18] <seb128> check the queue tomorrow before doing it :p
[16:18] <didrocks> hum, actually it's the only change
[16:19] <didrocks> so easy enough to upload, let me do it
[16:19] <seb128> right
[16:19] <seb128> thx!
[16:20] <didrocks> yw
[16:23] <oSoMoN> thanks didrocks
[16:24] <didrocks> (done)
[16:24] <oSoMoN> cheers
[16:24] <Laney> oSoMoN: are you handling thunderbird or just firefox atm?
[16:24] <oSoMoN> didrocks, have you tried /tmp/baz ?
[16:25] <oSoMoN> Laney, just firefox, one step at a time!
[16:25] <Laney> ok
[16:25] <Laney> in that case
[16:25] <Laney> chrisccoulson: is xnox's sync of thunderbird from bionic to cosmic something you approve of?
[16:26] <chrisccoulson> Laney, it doesn't matter, because it's about to get replaced by 60.2.1
[16:26] <Laney> presumably that's a sync with binaries, not sure I like it on those grounds anyway
[16:26] <Laney> oho
[16:26] <seb128> chrisccoulson, including cosmic? ;)
[16:26] <chrisccoulson> yeah
[16:26] <Laney> if that includes cosmic then I can just reject this one pasting that message
[16:26] <seb128> \o/
[16:27] <Laney> happy days
[16:27]  * Laney is being forcefully moved on from this room :(
[16:27] <Laney> brb :(
[16:30] <seb128> :(
[16:32] <didrocks> oSoMoN: I was mkdiring it, but ended up with ba2 :p
[16:36] <jbicha> ricotz: could you look into https://launchpad.net/ubuntu/+source/vala/0.42.2-1/+latestbuild/ppc64el ?
[16:37] <jbicha> previously, debian/rules was setting -O1 for vala so that's why this just started failing now (Ubuntu's ppc64el uses -O3 by default)
[16:43] <xnox> Laney, chrisccoulson - my copy-package request was with binaries.
[16:44] <xnox> which got rejected
[16:44] <Laney> 😈
[16:44] <xnox> interesting that i got no email about that
[16:44]  * xnox ponders if rejects of syncs go to /dev/null
[16:44] <xnox> or maybe to the actual uploader, rather than the sync requestor?
[16:45] <Laney> I remember that emailing around copies is weird in some way or other
[16:45] <Laney> probably that the copier just doesn't get them in some cases
[16:45] <Laney> like when you sync something into a queue, no email
[16:48] <ricotz> jbicha, noted
[17:11] <jbicha> seb128: there are a bunch of apps that we opted into language packs (so the translations are stripped) but aren't actually marked for translation
[17:11] <jbicha> one example is swell-foop https://translations.launchpad.net/ubuntu/cosmic/+imports?field.filter_extension=all&field.filter_status=NEEDS_REVIEW&batch=75&direction=backwards&memo=21000&start=21000
[17:11] <jbicha> https://translations.launchpad.net/ubuntu/+source/swell-foop
[17:12] <seb128> jbicha, do you have a full list? I tried to reviewed the .pot queue and accept them but it was noisy
[17:13] <jbicha> I don't have a list but I guess I could make one
[17:14] <jbicha> when are lang packs supposed to be generated this week?
[17:15] <seb128> not sure but the date on the cycle schedule is 11th
[17:16] <seb128> so I guess on friday
[17:16] <jbicha> do you know when the automatic langpack update is supposed to happen?
[17:20] <seb128> https://dev.launchpad.net/Translations/LanguagePackSchedule has been updated for cosmic
[17:20] <seb128> let me check on the machine
[17:21] <seb128> Wednesday
[17:21] <seb128> that's day 3 in cron right?
[17:23] <jbicha> yes
[17:27] <willcooke> night all
[17:33] <jbicha> seb128: ok, it's just a few: https://paste.debian.net/1046391/
[19:03] <ricotz> jbicha, could you test a patch for the -O3 failure on ppc64?
[19:08] <ricotz> jbicha, https://paste.debian.net/plain/1046407
[19:33] <jbicha> ricotz: I guess I didn't handle the bootstrap stuff right
[19:33] <jbicha> https://launchpadlibrarian.net/392324819/buildlog_ubuntu-cosmic-amd64.vala_0.42.2-1ubuntu0.1_BUILDING.txt.gz
[19:43] <ricotz> jbicha, yeah, still not that easy
[19:46] <jbicha> ricotz: why don't we just set -O2 since that's the default everywhere else? that gives you more time to work on it without the 18.10 release so soon
[19:48] <ricotz> jbicha, that would be fine
[19:49] <ricotz> I am wondering if there are ppc64 failure of rdepends caused by that already
[19:50] <jbicha> it's not built on Ubuntu's ppc64el yet so I wouldn't think so
[19:51] <ricotz> make check is what is failing, so if any vala based application is built on ppc64 it would fail if it used an specific syntax
[19:51] <seb128> jbicha, thanks, I review/approved gnome-robots, the other ones didn't build a template
[19:52] <seb128> jbicha,    dh_translations
[19:52] <seb128> dh_translations: more than one meson translation domain found (polari,help-org.gnome.Polari), don't know which one to use
[19:52] <seb128> same for gnome-recipies
[19:52] <seb128> unsure what's the issue with gnome-contacts, the log has no error/success output
[19:58] <jbicha> never mind about gnome-contacts. It was only done in Debian not Ubuntu yet because of bug 1791489
[19:59] <jbicha> I'll go ahead and fix up gnome-robots and polari packaging so we can try those again tomorrow
[19:59] <jbicha> currently, those 2 have their translations stripped so they need to be fixed one way or another
[20:11] <seb128> jbicha, gnome-recipies not gnome-robots
[20:12] <seb128> jbicha, seems like gnome-contacts got stalled missing a reply/is going to miss this cycle?
[20:14] <jbicha> Release Team wanted us to add symlinks to the faenza icon themes
[20:21] <seb128> that looked like a minor point/easy to workaround
[20:22] <seb128> that seems a weird request though
[20:24] <jbicha> that's why it's nicer to get new versions in before Feature Freeze, less paperwork and such :)
[21:35] <GunnarHj> Hey jbicha, saw your bug comment about polari. Isn't that a case where the --domain option would help?
[21:40] <jbicha> I guess so but I think upstream may take my patch
[21:41] <jbicha> GunnarHj: is this still the best way to handle things? https://salsa.debian.org/gnome-team/libgweather/blob/debian/master/debian/rules#L35-40
[21:43] <jbicha> I found another project with 2 pots today (gnome-recipes)
[21:45] <GunnarHj> jbicha: I think this makes more sense in the libgweather case:
[21:45] <GunnarHj> override_dh_translations:
[21:45] <GunnarHj> 	dh_translations --domain=libgweather-3.0
[21:45] <GunnarHj> 	ninja -C obj-$(DEB_HOST_GNU_TYPE) libgweather-locations-pot
[21:56] <GunnarHj> jbicha: That way it would deal with possible .desktop, .policy, etc. files correctly (I don't know if there are any, though).
[21:58] <jbicha> well recipes definitely has a .desktop :)
[21:58] <GunnarHj> Ok.
[22:04] <GunnarHj> jbicha: On another topic: Were you aware off this yelp translation issue?
[22:05] <GunnarHj> https://bugs.launchpad.net/ubuntu-translations/+bug/1796747/comments/1
[22:07] <jbicha> I saw it, I was hoping Seb would see it tomorrow
[22:07] <jbicha> (I'm still subscribed to yelp bugs but not ubuntu-translations bugs)
[22:08] <GunnarHj> jbicha: Ok. I suspect that he may already have edited the LP template; let's see tomorrow.
[22:12] <jbicha> kenvandine: I broke your gnome-calculator snap auto build, master wants libgtksourceview-4-dev
[22:23] <jbicha> hmm, gnome-recipes is tricky too :)
[22:36] <GunnarHj> jbicha: Looks similar to libgweather. Using --domain=gnome-recipes and a separate ninja() call for gnome-recipes-data-pot ought to work. But it's a universe package, and there are no LP templates yet..
[22:38] <jbicha> yeah, different problem
[22:42] <GunnarHj> jbicha: I think that the first step is to upload with translation stripping. Then, when the POTs are in the import queue, someone has to approve manually and with that create the templates.
[22:51] <jbicha> GunnarHj: https://paste.debian.net/1046427/
[22:52] <jbicha> src/ingredients.inc is a generated file (that's pretty unusual for translating)
[22:53] <jbicha> I tried a few different things but I think I'm just doing to turn off langpacks for gnome-recipes for cosmic
[22:56] <maddawg2> question...  i have a service that is failing to start preventing me from booting my machine... is there like a "safe mode" equivalent for ubuntu that would allow me to start without running any of the autostart services at boot and then allow me to remove the package in question
[23:11] <GunnarHj> jbicha: Yeah, that looks messy. Probably wise to wait til next cycle.
[23:14] <jbicha> I opened https://github.com/mesonbuild/meson/issues/4353
[23:14] <gitbot> mesonbuild issue 4353 in meson "pot command can't find generated file" [Open]
[23:14] <jbicha> https://l10n.gnome.org/module/recipes/ has a .pot but maybe they don't use meson to build it
[23:20] <GunnarHj> jbicha: That's a plausible assumption.
[23:22] <GunnarHj> maddawg2: Yes there is. I think it's possible to edit the grub entry, but I don't remember how. Please note that this is not a support forum; I'd recommend that you try e.g. https://askubuntu.com


[02:05] <Kalidarn> hey guys, not sure what Canonical's position or opinion is on the new US law being proposed SOPA, but i noticed that launchpad.net certificates are issued by GoDaddy, an apparent supporter of the controversial law https://pay.reddit.com/r/politics/comments/nmnie/godaddy_supports_sopa_im_transferring_51_domains/
[02:06] <Kalidarn> http://www.thedomains.com/2011/11/15/here-is-godaddys-statement-in-support-of-the-stop-online-privacy-act-house-hearing-tomorrow/
[02:12] <Peng> Oh geez
[02:16] <Kalidarn> though the domains appear to be registered with markmonitor not sure if they're a godaddy reseller though
[02:16] <Kalidarn> can't say i've done too much research
[02:19] <Kalidarn> it would appear they aren't, least from what i see so far.
[02:20] <Kalidarn> Peng: i found this rather amusing https://pay.reddit.com/r/politics/comments/nmnie/godaddy_supports_sopa_im_transferring_51_domains/c3aarjl
[02:22] <Kalidarn> apparently Bob Patterson has a trash can made out of an elephant's foot.
[02:23] <Kalidarn> http://en.wikipedia.org/wiki/Bob_Parsons#Elephant_shooting_controversy
[04:32] <cnd> I uploaded a package to a ppa with an orig tarball that was different than in the ubuntu archives
[04:32] <cnd> I rebuilt using the same orig tarball, and uploaded without the orig tarball this time
[04:32] <cnd> but I still got the same error back
[04:32] <cnd> could the orig tarball I uploaded be stuck in the ppa somehow?
[04:34] <cnd> to be specific, I'm trying to upload qt4-x11 to ppa:ubuntu-x-swat/x-staging
[04:37] <wgrant> cnd: It's not possible to upload a different file with the same name.
[04:38] <wgrant> That would be a lie, and confuse people and software alike.
[04:38] <cnd> wgrant, I'm not trying to
[04:38] <cnd> I did the first time accidentally
[04:38] <wgrant> Even if the old file is no longer used by a published package in that archive.
[04:38] <wgrant> You can't upload the same filename with different contents.
[04:38] <cnd> yes, I'm not trying to do that
[04:39] <cnd> wgrant, listen to what I'm saying
[04:39] <cnd> I accidentally uploaded a different tarball
[04:39] <cnd> now I'm trying to upload again without the tarball, and the source package was built with the correct orig tarball
[04:39] <cnd> and it's still being rejected
[04:39] <wgrant> Ah, you didn't say the initial upload of the different tarball was rejected.
[04:40] <cnd> ahh, ok
[04:40] <cnd> I just tried uploading with a bumped ubuntu version
[04:40] <cnd> ~xstaging2 instead of ~xstaging1
[04:40] <cnd> we'll see if that fixes things
[04:41] <wgrant> It won't if it is complaining about the orig.tar.gz.
[04:41] <wgrant> What is the error message?
[04:41] <cnd> still rejected
[04:41] <cnd> File qt4-x11_4.7.4.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents.
[04:41] <wgrant> Can you pastebin the dsc?
[04:42] <cnd> this was the dput output: http://paste.ubuntu.com/779451/
[04:42] <cnd> the orig tarball wasn't sent
[04:42] <wgrant> That's not really relevant.
[04:43] <cnd> this is the dsc: http://paste.ubuntu.com/779454/
[04:43] <wgrant> the dsc still has the hash of whichever tarball you built against.
[04:43] <wgrant> Uploading without it won't work.
[04:43] <cnd> how can I get the hash of the tarball in ubuntu?
[04:43] <wgrant> Obtain the Ubuntu tarball, and rebuild your source package against it.
[04:44] <wgrant> No manual dsc hacking, please :)
[04:44] <cnd> arg, I have the correct orig tarball in ../
[04:44] <cnd> but it was building against ../build-area/
[04:44] <wgrant> Hah
[04:44] <wgrant> Where did the tarball of lies come from?
[04:45] <wgrant> You should probably destroy it to prevent future mistakes.
[04:45] <cnd> uscan --download-current-version
[04:46] <wgrant> o_O
[04:46] <wgrant> That generates a different one?
[04:46] <cnd> so either upstream changed it, or ubuntu's tarball isn't really the orig upstream tarball
[04:46] <wgrant> Yay :/
[04:46] <cnd> or the watch file is broken :)
[04:53] <cnd> wgrant, it worked finally
[04:53] <cnd> thanks!
[04:53] <wgrant> Excellent.
[08:16] <czajkowski> morning
[11:12] <Quintasan> jelmer: Can one change the code import url once it has been set up?
[11:33] <jelmer> Quintasan: yes, but you have to be a code import admin
[11:33] <jelmer> Quintasan: I can change one for you if you lik
[11:33] <Quintasan> jelmer: Splendid, there is more than one, actually we move whole telepathy-kde
[11:34] <Quintasan> lp:~telepathy-kde/telepathy-kde/telepathy-kde-accounts-kcm -> git url is now 	git://anonscm.debian.org/pkg-kde/kde-extras/telepathy-kde/telepathy-kde-accounts-kcm.git
[11:34] <Quintasan> lp:~telepathy-kde/telepathy-kde/telepathy-kde-approver -> git://anonscm.debian.org/pkg-kde/kde-extras/telepathy-kde/telepathy-kde-approver.git
[11:35] <jelmer> Quintasan: probably easiest to file a questin in answers.launchpad.net/launchpad if there are many
[11:35] <jelmer> I'm about to head out
[11:35] <Quintasan> jelmer: Okay. Will do that
[19:30] <joancreus> i tried to login. i did receive a warning message (somebody might be impersonating you) but not a confirmation code
[19:30] <joancreus> ideas?
[19:31] <joancreus> thanks a lot
[19:34] <joancreus> ?
[19:35] <joancreus> i've retried but no luck
[19:35] <joancreus> the same happened
[19:55] <joancreus> now working


[04:25] <mup> Bug #1914742 changed: udev settle fail <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1914742>
[04:25] <mup> Bug #1914776 changed: maas rack controllers read call hung, failed with Expired timestamp <cdo-qa> <foundations-engine> <MAAS:Expired> <https://launchpad.net/bugs/1914776>
[04:25] <mup> Bug #1916610 changed: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered <MAAS:Expired> <linux (Ubuntu):Expired> <https://launchpad.net/bugs/1916610>
[04:31] <mup> Bug #1914742 opened: udev settle fail <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1914742>
[04:31] <mup> Bug #1914776 opened: maas rack controllers read call hung, failed with Expired timestamp <cdo-qa> <foundations-engine> <MAAS:Expired> <https://launchpad.net/bugs/1914776>
[04:31] <mup> Bug #1916610 opened: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered <MAAS:Expired> <linux (Ubuntu):Expired> <https://launchpad.net/bugs/1916610>
[04:34] <mup> Bug #1914742 changed: udev settle fail <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1914742>
[04:34] <mup> Bug #1914776 changed: maas rack controllers read call hung, failed with Expired timestamp <cdo-qa> <foundations-engine> <MAAS:Expired> <https://launchpad.net/bugs/1914776>
[04:34] <mup> Bug #1916610 changed: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered <MAAS:Expired> <linux (Ubuntu):Expired> <https://launchpad.net/bugs/1916610>
[04:37] <mup> Bug #1914742 opened: udev settle fail <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1914742>
[04:37] <mup> Bug #1914776 opened: maas rack controllers read call hung, failed with Expired timestamp <cdo-qa> <foundations-engine> <MAAS:Expired> <https://launchpad.net/bugs/1914776>
[04:37] <mup> Bug #1916610 opened: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered <MAAS:Expired> <linux (Ubuntu):Expired> <https://launchpad.net/bugs/1916610>
[04:43] <mup> Bug #1914742 changed: udev settle fail <curtin:Expired> <MAAS:Expired> <https://launchpad.net/bugs/1914742>
[04:43] <mup> Bug #1914776 changed: maas rack controllers read call hung, failed with Expired timestamp <cdo-qa> <foundations-engine> <MAAS:Expired> <https://launchpad.net/bugs/1914776>
[04:43] <mup> Bug #1916610 changed: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered <MAAS:Expired> <linux (Ubuntu):Expired> <https://launchpad.net/bugs/1916610>
[09:11] <mup> Bug #1906916 changed: maas 2.9 rc4 override failed testing  <ui> <MAAS:Fix Released> <maas-ui:Fix Released> <https://launchpad.net/bugs/1906916>
[09:11] <mup> Bug #1912697 changed: MAAS accepts user-data in different formats depending on the UI or API <MAAS:Fix Released> <https://launchpad.net/bugs/1912697>
[09:14] <mup> Bug #1933873 changed: [2.9] MAAS pods cannot create VMs because available resources is zero <MAAS:New> <https://launchpad.net/bugs/1933873>
[11:11] <mup> Bug #1898550 changed: FAIL: installing grub to target devices <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1898550>
[11:14] <mup> Bug #1898550 opened: FAIL: installing grub to target devices <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1898550>
[11:17] <mup> Bug #1898550 changed: FAIL: installing grub to target devices <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1898550>


[00:32] <BUGabundo> night guys
[01:52] <dw-> keep up the great work
[12:22] <juk> where did apps from system tray gone?
[12:25] <juk> like doking dictionaries and stuff only transmission is left, and ibus
[12:36] <juk> whole gnome got messed up
[12:43] <juk> nevermind goldendict is stopped stardict's madness
[13:57] <coz_> nvidia-current is now held back ?  oy :)
[15:15] <joaopinto> hi
[15:25] <DanaG> Okay, so I upgraded my tablet to natty, and it wiped out ALL my compiz settings AND my gnome panel!
[15:26] <DanaG> So now i get this lame unity panel thing that doesn't even have a clock!
[15:27] <DanaG> And the gnome menu opens a nautilus window to /usr/share/applications, instead of doing the cool thing it used to do...
[15:27] <DanaG> So now I have 12 nautilus windows open to the same place.
[15:40] <DanaG> And it won't even let me use the freaking cube with Unity!
[15:41] <DanaG> Why in the world does that bar absolutely, positively have to have the desktops SLIDE?
[15:41] <IdleOne> Welcome to the new way of doing stuff.
[15:41] <IdleOne> so you end up losing your windows also
[15:42]  * IdleOne closed 4 firefox windows earlier. I wasn't using any of them
[15:42] <IdleOne> and yeah that applications thing bugs me also
[15:52] <joaopinto> is there a known problem with the livecd installer from 18th ?
[15:59] <jcastro> joaopinto: I can't get mine to work either (in testdrive)
[15:59] <joaopinto> jcastro, it fails during the user creation phase right ?
[16:00] <jcastro> no, mine fails when creating the file system part
[16:00] <joaopinto> actually after 2 tries I am not sure was at the same place
[16:00] <jcastro> I was just going to wait for the next spin
[16:00] <joaopinto> I was planning to play with Unity this holidays :(
[16:01] <joaopinto> the error message presents the link to report a bug, which is hard to use because it doesn't allow to copy or open a browser from it
[16:01] <joaopinto> looking at /var/log/installer didn't show anything meaningful either :(
[16:04] <joaopinto> we need real persistent usb installs :(
[16:54] <rye_> hi people, is anybody else experiencing huge performance issues while running ubuntu vm in natty using kvm?
[18:13] <F3RR1S>  /join #ubuntu
[18:13] <F3RR1S> oops
[18:14] <F3RR1S> I need help porting my video from laptop to a tv via s-video cable
[18:14] <F3RR1S> is there an easy way to do this?
[18:21] <apadox> Hello, how can i update from Maverick to Natty from console?
[19:56] <Some_Person> It may be too early to ask this, but I'll do it anyway: will issues involving major crashes likely be fixed in natty?
[19:56] <bjsnider> no, we plan on creating as many showstoppers as possible to screw with our user base
[19:56] <Some_Person> no, seriously
[19:56] <bjsnider> our theory is they will become deeply resentful of us, but we need to actually conduct a test to prove it
[19:56] <bjsnider> we never assume anything
[19:57] <Some_Person> I want a serious answer
[19:57] <bjsnider> ask a serious question
[19:58] <Some_Person> I'm having major issues involving random system crashes in maverick. Will this likely be fixed in natty?
[19:59] <Some_Person> It's a simple "yes/no/don't know" question
[19:59] <bjsnider> have you submitted a bug?
[20:00] <charlie-tca> bjsnider: +1 lol
[20:00] <Some_Person> I'm not sure what to put in the bug report other than "it crashes and I have to reboot"
[20:00] <Some_Person> there's no obvious indication of what the problem is
[20:00] <bjsnider> now we're getting somewhere
[20:00] <bjsnider> just submit the bug and you will receive instructions
[20:01] <bjsnider> they can't fix it if they don't know it's broken
[20:43] <billybigrigger> where is the system menu in unity?
[20:50] <charlie-tca> Some days it is accessed by clicking the ubuntu logo in the left corner
[20:50] <charlie-tca> but you might have to go through nautilus, to  /usr/share/applications   and find the application to click on there
[21:16] <BUGabundo> o/
[21:17] <charlie-tca> hello, BUGabundo
[21:18] <charlie-tca> Are things any better today?
[21:19] <BUGabundo> not really
[21:20] <BUGabundo> nasty day at work
[21:20] <BUGabundo> and personally not my best days :(
[21:20] <charlie-tca> Sorry to hear that :-(
[21:20] <BUGabundo> at least I saved my docs
[21:20] <BUGabundo> re-mirroring to external server what I have
[21:20] <BUGabundo> its only 20GBs
[21:37] <billybigrigger> any way to kill unity and revert back to gnome-panel?
[21:40] <ior3k> billybigrigger: login with the Ubuntu Classic Desktop session
[21:41] <billybigrigger> roger
[21:44] <billybigrigger> ahhhh there we go :)


[11:16] <kostja_osipov> t
[12:18] <est31> hello I want to request a code import
[12:18] <est31> now my question is: what do I enter as "branch name"?
[12:18] <est31> is it the "series"?
[12:20] <est31> or is it the real branches' name, thats then also usable in a lp:branchname string for bzr-builder?
[12:22] <cjwatson> Not quite either of those exactly as you write :-)
[12:23] <cjwatson> The branch name is the end of the fully-qualified lp: URL, so for example lp:~cjwatson/man-db/master
[12:23] <est31> ah ok
[12:23] <cjwatson> But if a branch is the development focus for a project (as that example one is), then it's aliased as simply lp:man-db
[12:23] <cjwatson> For an import it's reasonably usual to make it be the same as whatever the branch name is in the remote system
[12:24] <cjwatson> So in my example, it's an import of the master branch from a git repository, so it's just "master"
[12:25] <est31> thanks
[12:26] <est31> It was about a custom git branch yes.
[12:28] <est31> any way to request older commits too? because you can enter specific revision ids, but only when the imports started, am I right?
[12:29] <est31> (I mean: the revision ids start with the first imported commit)
[12:30] <cjwatson> Um, I don't quite understand.  The importer walks the full history.
[12:30] <cjwatson> (Or at least all the history reachable from the ref name you give it.)
[12:30] <est31> you are right, sorry.
[12:30] <cjwatson> That's not an option, it's an intrinsic part of doing a version control import.
[12:31] <est31> quite cool :)
[12:45] <est31> so, I want to execute pbuilder as non-root
[12:45] <est31> any way I can accomplish this?
[12:45] <est31> pbuilder-user-mode-linux complains about some tmp file not set in my ~/
[12:45] <cjwatson> I don't use pbuilder myself; the procedure in https://wiki.ubuntu.com/SimpleSbuild should work fine though, I never run sbuild as root
[12:46] <cjwatson> pbuilder-user-mode-linux is, I suspect, a pretty experimental thing
[12:57] <aditya_dev_s> please help how can i login into launchpad if i am windows 8 user
[13:00] <adidev> hello, hi i am aditya from india.. i am new to launchpad..please help me to login to download code if i am a windows 8 user
[13:03] <est31> What are logs for the option: "Mail address where logs are sent to (mandatory, no default!)" inside ~/.sbuildrc?
[13:03] <est31> I'm just wondering whether it requires a mail server on localhost...
[13:05] <cjwatson> est31: You can use the -n option to suppress saving logs and sending log mails.  But this is really not Launchpad-specific at this point.
[13:07] <est31> thanks though cjwatson any on-topic #channel I can ask for help?
[13:07] <cjwatson> adidev: I would suggest following through the instructions at https://help.launchpad.net/Code, and then if you get stuck ask specific questions about the specific error messages you're seeing.  (I haven't used Windows seriously in 15 years, so there's no way I can give you a full walkthrough.)
[13:07] <cjwatson> est31: Perhaps #ubuntu-packaging
[13:50] <est31> is there a way to inspect the history of a recipe?
[13:50] <est31> and when I change it, will older packages still be available?
[14:00] <dobey> editing a recipe doesn't change what's already in the PPA
[14:01] <dobey> i don't know if there's a way to see a log of changes to a recipe
[14:03] <est31> thanks dobey!
[14:13] <cjwatson> Yeah, we don't keep logs of old versions of recipe text, except perhaps whatever you can divine from old build logs.
[17:04] <teward> cjwatson: ping
[17:04] <cjwatson> teward: Please tell me what you want and I'll reply when I'm around.
[17:04] <teward> heh
[17:04] <teward> autoresponder.
[18:08] <s1991> Hello, I have some doubts abt packaging system.
[18:08] <s1991> Is ubutu-packaging same as debian-packaging?
[18:09] <cjwatson> Sometimes specifics differ, but in general yes.
[18:10] <s1991> cjwatson: Is it true that for making PPA first we have to create a debian pacakge?
[18:11] <cjwatson> Yes.
[18:12] <s1991> cjwatson: I followed this tutorial https://help.launchpad.net/Packaging/PPA . It doesn't specify anything abt that
[18:16] <s1991> cjwatson: Is there any tutorial which explains creating PPA ?
[19:37] <teward> cjwatson: on the GUI frontend for git stuff - saw those screenshots, can I say that they look decent even though they're very preliminary?
[20:43] <cjwatson> teward: Cool, thanks.  There's definitely a long way to go, the second of those needs more infrastructure in place in order to be able to have more recent commits
[20:43] <cjwatson> (In advance of a proper integrated code browser, which I'd like to do but won't be for a while yet)
[20:43] <teward> cjwatson: indeed.
[20:55] <teward> cjwatson: stupid question though, why wouldn't you be able to apply the same logic as is currently used by the bzr code browser to the git side?
[20:55] <teward> (granted I have no backend knowledge, so...)
[20:55] <teward> (adapting of course for the bzr vs. git differences as you go)
[22:08] <cjwatson> teward: We don't have an integrated code browser for bzr; only loggerhead (which you see on bazaar.l.n), which is utterly bzr-specific and not integrated into the main webapp UI
[22:09] <teward> ahh ok
[22:09] <teward> cjwatson: thanks for the clarify :)
[22:09] <cjwatson> teward: We'll likely start out with a similar approach for git, probably using cgit, but it's not ideal.
[22:10] <teward> cjwatson: i think the goal should be, in my opinion, functional vs. ideal
[22:10] <teward> firstly
[22:10] <cjwatson> certainly
[22:10] <cjwatson> we're taking the quickest plausibleroute
[22:10] <teward> cjwatson: same logic applies for bzr as well - ideally you'd have a proper integrated code browser for that as well, but function over idealism
[22:11] <blr> hopefully cgit won't stick around long :)
[22:11] <teward> cjwatson: hopefully you don't mind my commenting and asking though - git functionality on LP will go a long way towards making it better for projects
[22:11] <teward> since a lot like git over bzr and such
[22:12] <teward> so thank you for you and everyone's efforts
[22:12] <teward> (on both the front and backend changes)
[22:12] <blr> teward: I don't think anyone has any illusions over the current state of dvcs and where things are going.
[22:12]  * teward shrugs
[22:13] <blr> I've only been using bzr for the last few months, but it has certainly grown on me.
[22:13] <teward> blr: i use bzr only where needed - learned git for most things
[22:13] <teward> but meh
[22:13] <teward> blr: for those who prefer git over bzr, though... :P
[22:13] <teward> (I also use bzr for my package merge debdiffs and such but that's a different matter xD)
[22:16] <teward> cjwatson: regardless please pass on my thanks to those doing the backend development and such - I really do like the whole idea of having git in addition to bzr on LP - i'm not the only one either judging on that bug requesting it :)
[22:17] <cjwatson> teward: We might be able to retrofit an integrated browser to bzr without too much work, but we'd need to see whether it's worthwhile.  And thanks, blr there has been doing a lot of the backend work as well as wgrant of course.
[22:17] <cjwatson> I use almost exclusively git for my own projects outside Ubuntu/Launchpad, so I'm keen to switch myself.
[22:18] <teward> well then thanks to blr and wgrant :)
[22:28] <blr> cjwatson: switched to get from hg several years ago as well for personal things.
[22:28] <blr> git even
[22:29] <blr> teward: we're certainly excited about it - it is certainly one of the most regularly requested new features for LP.
[22:30] <teward> blr: well, i'd be happy to help alpha/beta test if you guys need public tests eventually before throwing it onto production - i'm a strong supporter of git for LP after all
[22:30] <teward> kinda annoyed at bzr, but mostly for reasons that I won't share here 'cause Ubuntu CoC violations throughout that rant :P
[22:31] <teward> until then i'll just track the bug where most of cjwatson's branches get linked to :)


[04:49] <easter_egg> Hi, is possible to have a ubuntu/bot/nickname cloak for the brazilian bot?
[04:49] <easter_egg> the nick of the bot is ubottu-br
[05:42] <persia> easter_egg, The ubuntu/bot/nickname is fairly tightly limited to bots managed by the common bot wranglers.  This doesn't mean "no", but you may want to prepare answers to questions such as "What does that bot do differently?  Why shouldn't that bot be managed by the common wranglers?", etc.
[05:43]  * persia is non-authoritative when it comes to bot management policies
[05:44] <vish>  "bot wranglers" ! :D
[05:44] <rww> Is that the polite term for what I'm doing when I feel like strangling ubottu?
[05:45] <easter_egg> persia, the ubottu-br is like ubottu. But with the meetbot plugin too and for only brazilian channels
[05:46] <easter_egg> persia, this is for not to overload the other bots
[05:46] <persia> rww, It's the term I've always used for the folks that manage bots.
[05:47] <persia> easter_egg, I'm not someone who can receive those answers well: you need someone authoritative about those things.
[05:47] <easter_egg> persia, who is the one?
[05:49] <persia> easter_egg, I'm not sure precisely, but I believe https://launchpad.net/~ubuntu-bots/+members is the current list.
[05:49]  * persia could be mistaken: that could be the list of folks that can change the code of the bots
[05:49] <easter_egg> persia, thank you very much
[05:49] <easter_egg> i will search
[05:50] <persia> I'd recommend waiting instead.  This time of day is not one that any of them tend to be active.  You might get a real answer sometime in the next 4-10 hours.
[05:54] <easter_egg> ok =]
[05:55] <rww> I'd wait for an IRC Councilperson, since they're the ones who can actually issue bot cloaks, so one would imagine they know about who gets them :)
[05:55] <persia> Either way.  Waiting is best now :)
[10:45] <Flannel> easter_egg: You can also get the normal bot mask of unaffiliated/ownername/bot/botname (where botname is the bots nick, and ownername is the owners nick)