[07:22] <vila> hi all, happy new year !
[07:30] <lifeless> vi hila
[07:31] <vila> :)
[09:01] <AuroraBorealis> why can i not bind a colocated branch to a remote branch?
[09:01] <AuroraBorealis> it keeps binding it to itself
[09:08] <AuroraBorealis> it doesn't seem colocated branches are very stable :<
[09:58] <AuroraBorealis> anyone?
[11:42] <soren> This doesn't look right: http://paste.ubuntu.com/790403/
[11:42] <soren> Oh, this is probably a #launchpad thing. Sorry.
[13:24] <jelmer> vila: are you here today?
[13:24] <vila> jelmer: yup ;)
[13:24] <vila> jelmer: happy new year !
[13:24] <jelmer> vila: hey!
[13:25] <jelmer> vila: Thanks, happy new year to you too!
[13:25] <jelmer> vila: How were your holidays?
[13:26] <vila> pretty good, except for resting ;)
[13:26] <vila> we met a lot of friends so... lots of parties ;)
[13:29] <jelmer> :-)
[13:48] <jelmer> hmm, looks like we have some reviews to catch up to :)
[13:54] <vila> jelmer: oh, hmm, yeah
[13:54] <vila> jelmer: do you know if poolie and mgz are still in vacations ?
[13:55] <jelmer> vila: not sure about poolie, but I think the UK has a holiday because the 1st was on a sunday
[13:55] <vila> lol
[13:56] <vila> I thought only *French* were doing such things ;)
[13:57] <jelmer> hehe
[14:12] <mgz> yup, still holiday today, should have posted noting that, sorry
[14:15] <jelmer> mgz: no worries :)
[14:15] <jelmer> mgz: oh, and happy 2012
[14:15] <mgz> thanks! and to you and vila (and everyone else here) too
[14:16] <mgz> will be driving back home later today
[14:16] <jelmer> where did you spend your holidays?
[14:17] <mgz> with one sister then the other, so a lot of baby holding the last few days
[14:17] <vila> mgz: hey !
[14:17] <mgz> what did you get up to jelmer?
[14:19] <jelmer> I spent christmas at my parents and then went to Berlin for 28C3 and NYE with some friends
[14:19] <mgz> ah, various of my friends were following that online, don't think any of them actually went though
[19:50] <AuroraBorealis> continued from last night, does anyone know why i can't bind a colocated branch to a remote branch? it keeps binding 'to itself' which obviously doesnt work
[19:56] <jelmer> AuroraBorealis: hi
[19:57] <AuroraBorealis> heya
[19:58] <jelmer> AuroraBorealis: can you expand a bit on what you're trying to do exactly?
[19:59] <AuroraBorealis> i'm trying out colocated branches cause i like how things are laid out
[19:59] <AuroraBorealis> so i have a 'trunk' branch inside of it, and thats the working tree and all that
[19:59] <jelmer> ?
[19:59] <AuroraBorealis> i created a new "colocated branches workspace" in bazaar explorer
[20:00] <jelmer> AuroraBorealis: is this colocated branches in bzr 2.5, or the bzr-colo plugin?
[20:00] <AuroraBorealis> it appears to work in bzr 4.2
[20:00] <AuroraBorealis> as thats what i have
[20:00] <AuroraBorealis> err
[20:00] <jelmer> AuroraBorealis: that would be the bzr-colo plugin then
[20:00] <AuroraBorealis> 2.4.2
[20:00] <fullermd> Wow, can you send me a copy?   8-}
[20:00] <jelmer> AuroraBorealis: no idea about that, sorry
[20:01] <AuroraBorealis> so...if i upgrade to 2.5 then will it not be a plugin and work better? =/
[20:01] <fullermd> Actually, doesn't Explorer have some thing it calls 'colocated', but is actually just the only single-switched-wt thing, not actually anything strictly colo?
[20:01]  * fullermd has vague memories of reading something about that.
[20:01] <AuroraBorealis> it seems to be a light checkout
[20:01] <jelmer> AuroraBorealis: the 2.5 colo support has other issues
[20:01] <AuroraBorealis> pointing to .bzr/branches/whatever
[20:01] <jelmer> AuroraBorealis: it's not finished yet
[20:02] <jelmer> AuroraBorealis: that sounds like bzr-colo
[20:02] <AuroraBorealis> well it was in bazaar explorer so i thought it was semi official
[20:03] <jelmer> AuroraBorealis: I mean the colocated branch support in bzr 2.5 is not finished yet
[20:04] <AuroraBorealis> is that using the plugin (or code based off the plugin) or is it brand new
[20:04] <jelmer> AuroraBorealis: it's completely independent of the plugin
[20:04] <AuroraBorealis> ok.
[20:04] <AuroraBorealis> i shall wait then
[20:04] <jelmer> though I think Neil has done some work in bzr-colo to make it work with bzr 2.5's colocated branch support
[20:06] <AuroraBorealis> i just like the layout of colocated branches and wanted to try it out :<
[20:44] <Wellark> hi! I remember reading it somewhere but can't find the info on help.launchpad.net.. how can I change which branch lp:<project> actually points to?
[21:00] <jelmer> Wellark: hi
[21:01] <jelmer> Wellark: #launchpad is usually more appropriate for Launchpad-specific questions
[21:01] <jelmer> Wellark: there should be a edit button next to the branch name on your project home page
[21:04] <Wellark> jelmer: oh, sorry. but anyway, thanks! I'll follow up at #launchpad


[02:01] <xubuntu21i> hi all new to this
[02:32] <zelayamantica> Hola
[02:33] <zelayamantica> Español?
[07:59] <nova> I have an Intel NUC loaded with xubuntu eoan connected to a television.  The televisions is 4k but I have xubuntu set to 1080p.  It looks fine after booting up, but if I switch to another input on the TV for a while and go back I see my 1080p xubuntu taking up only 1/4 of the screen.  It is not a scaling issue on the TV as far as I can tell because I have other 1080p devices that display without problems.  Has anyone experienced this
[07:59] <nova> or know what the problem could be?
[08:04] <nova> Here's what it looks like: https://pasteboard.co/IZ1zDrnt.jpg
[08:05] <nova> What's also interesting is that it isn't using the correct wallpaper when this happens either.
[08:30] <nova> Another problem I am having...If i set "LightDM gtk+greeter settings" to use a solid color background, then log out and back in, I see a process called xiccd using exactly 25% of my cpu.  It seems like when I use an image for the background it doesn't do this.
[09:31] <brainwash> nova: https://bugs.launchpad.net/ubuntu/+source/xiccd/+bug/1845800
[09:32] <nova> If i add the experimental PPA and update xiccd, am I also going to update the other packages from that repo?
[09:33] <brainwash> not if you only install xiccd
[09:34] <brainwash> "apt install xiccd" will update the version if a newer one is available
[09:34] <nova> but if I already have xfce4-panel installed, and I update while using that PPA, will it not update that package as well?
[09:34] <brainwash> you disable the ppa afterwards
[09:35] <nova> so I should not use "sudo apt update && sudo apt upgrade" after adding the PPA
[09:35] <nova> but sudo apt install xiccd, then remove the ppa
[09:36] <nova> ?
[09:36] <brainwash> sudo apt update && sudo apt install xiccd
[09:36] <brainwash> disable PPA
[09:36] <nova> and the next time I update with the ppa disabled, will it downgrade the package?
[09:37] <brainwash> shouldn't
[09:37] <brainwash> it's a newer version
[09:37] <brainwash> alternatively, you could probably just remove that package
[09:37] <nova> oh?  it's not essential?
[09:37] <brainwash> or disable its autostart launcher (if it has one)
[09:38] <brainwash> it is need for color management of your monitor
[09:38] <brainwash> in case you have a custom color profile
[09:38] <nova> I see..thank you
[09:39] <brainwash> https://simon.shimmerproject.org/2019/02/19/color-profile-support-for-xfce/
[09:39] <brainwash> if you want to read about it
[09:39] <nova> How long do you think it could take for this experimental version to make its way to the main repos?
[09:40] <brainwash> sadly, no idea
[09:40] <brainwash> maybe never
[09:40] <brainwash> it is fixed in xubuntu 20.04
[09:41] <brainwash> or, it will be once it's released
[09:41] <brainwash> in april
[09:42] <nova> Oh I see
[09:44] <nova> I see it listed in the "Session and Startup/Application Autostart", I'll just uncheck it there since I don't really have any need for color profiles that I'm aware of.
[09:45] <nova> Thank you for your guidance ;)
[09:46] <brainwash> you're welcome
[15:59] <piturren51> hello i need help for unistalling xubuntu. i don't have idea how can i do that.
[16:04] <Kumool> something like dd if=/dev/sd1 of=/dev/null ?
[16:04] <GridCube> piturren51: what do you mean unistalling?
[16:04] <GridCube> what do you want to uninstall?
[16:05] <Kumool> xubuntu, you heard him
[16:05] <GridCube> that makes no sense
[16:05] <Kumool> you can also just take your hdd out, and smash it with a rock
[16:05] <GridCube> ^ that would work
[16:05] <Kumool> no no, ubuntu could still survive
[16:06] <GridCube> doubt it, but it does take 14 days for it to manifest tho
[16:06] <Kumool> piturren51: uninstalling could mean erasing the partition/drive or it could be overwriting it with another OS
[16:07] <piturren51> erase the drive and install a new os
[16:08] <GridCube> you don't need to do anything then, the other installer will ask you if you want to format
[16:08] <GridCube> specially if its another linux flavour
[16:08] <GridCube> windows wont ask and just format everything
[16:11] <piturren51> i tryed it from a bootable usb but appears a xubuntu screen at that moment before starting the installation and i can't move forward
[16:14] <GridCube> your boot manager might not be looking to boot from usb first
[16:14] <GridCube> check at the uefi options
[16:14] <GridCube> maybe theres an F key you need to press to force teh boot to chose usb first
[16:17] <Kumool> read
[16:17] <Kumool> the
[16:17] <Kumool> docs
[16:17] <Kumool> use your phone
[16:17] <Kumool> everyone has installer instructions


[13:10] <hjd> Hi, a new version of scala was recently packaged in Debian, along with related new dependencies scala-parser-combinators and scala-xml. Unfortunately these packages have circular dependencies and won't build unless they themselves are available. (search "scala" on http://qa.ubuntuwire.com/ftbfs/ for details). Is there some process or approach for boostrapping such packages?
[13:11] <hjd> bug 1126035 might be relevant
[13:32] <infinity> hjd: Is this a one-time thing, or will it be required for every major version bump or something equally awful?
[13:35] <infinity> hjd: If it's a one-time thing, I can bootstrap them sometime this weekend and fix it up.  If it's an ongoing concern, you might want to come up with a clever way to iterate bootstrap uploads in the future, since it's entirely possible that Debian will go source-only soon too.
[13:37] <hjd> infinity: I don't have full overview, but I note that scala version 2.10 and 2.11 both depended on itself.  So maybe the latter...
[13:39] <infinity> Huh.  It really does build-dep on itself.  Cute.
[13:40] <hjd> In the bug report, there's a link to an upstream ticket, so people are talking to upstream and trying to make it better (see for instance https://github.com/scala/scala-lang/issues/295)
[13:51] <infinity> hjd: Commented on the upstream ticket at https://issues.scala-lang.org/browse/SI-9299
[13:52] <infinity> hjd: I might bootstrap this current version as a show of good faith, but it's definitely not a process I want to have to repeat every 6 months.
[14:06] <hjd> infinity: Thank you :) That's perfectly understandable.
[16:53] <ScottK> tumbleweed: It might be kind of interesting to track the total number of uploaders for each release over time in http://people.ubuntuwire.org/~stefanor/ubuntu-activity/ - I assume that's each to get from the data set you're using.
[16:55] <tumbleweed> ScottK: yeah, probably is quite easy


[09:13] <moha> Hi
[09:16] <moha> Does netplan support Open vSwitch bridges? If yes, how can I define an OVS bridge in netplan config file? Here is what I have defined currently, but linux -bridge: http://ix.io/4k5T that I want convert it to OVS bridges
[09:17] <moha> sorry, this link: http://ix.io/4k5U
[09:18] <moha> looking for a syntax to convert to OVS bridges
[09:39] <moha> Oh, the Xmass vacations; Anybody online here? (:
[09:40] <lotuspsychje> moha: being 1jan and weekends, server channel might be a bit quiet
[09:41] <lotuspsychje> idle around a bit today : )
[09:41] <lotuspsychje> !netplan


[13:33] <wolfger> party?
[13:33] <rick_h__> pretty much
[13:33] <rick_h__> monday party
[13:35] <wolfger> Had to deal with issues that resulted from my Sunday work, made 500% worse by the fact that our system is just plain shitty to begin with.
[13:36] <wolfger> I can't even begin to imagine how the system was allowed to be so bad in the first place, or why nobody cares enough to fix it, but it turns every relatively minor problem into an omgwtfbbq problem
[13:36] <brousch> wolfger: job security
[13:39] <wolfger> job discouragement
[13:53]  * ColonelPanic001 watches the shuttle launch
[13:53] <ColonelPanic001> 3 minutes to go
[13:59] <rick_h__> man, snapl isn't around
[14:00] <rick_h__> man, we need to raise funds to get a twit brick: https://www.brickorder.com/twit/
[14:00] <rick_h__> come on, we want a big brick with the lococast logo on it
[14:00] <greg-g> ColonelPanic001: ditto
[14:00] <ColonelPanic001> think this is the first time I've watched one live
[14:00] <rick_h__> linky!
[14:00] <ColonelPanic001> http://www.nasa.gov/multimedia/nasatv/ustream.html
[14:01] <greg-g> ColonelPanic001: second for me, I think, but this one is a bit more special
[14:01] <greg-g> I *almost* wish it would have been delayed a few more days when I'll be down in Orlando on Wed/thurs
[14:01] <ColonelPanic001> heh
[14:02] <greg-g> hell, remove the almost, I do wish I could have seen it in person
[14:02] <ColonelPanic001> I don't know, to be honest, seeing it in person on the ground probably wouldn't be seeing much. It'd be cool to "see it with my own eyes", but a couple minutes goes and it's over pretty uick and out of sight anyway
[14:03] <greg-g> ColonelPanic001: yeah, but seeing that exhaust trail go speeding up and then curve out is just neat
[14:03] <rick_h__> yea, Jim McQ was talking about it at a CHC recently
[14:03] <rick_h__> they saw one from about 5mi away
[14:03] <ColonelPanic001> nice
[14:03] <rick_h__> sounds like the most interesting thing is seeing it, but not hearing it
[14:03] <rick_h__> for a long time
[14:03] <ColonelPanic001> don't get me wrong, if I was down there, I'd go, too
[14:04]  * greg-g nods
[14:04] <greg-g> 13,500 mph, good god
[14:05] <greg-g> going at over Mach 17
[14:05] <ColonelPanic001> yeah. It's mind-blowing how fast they go from on the ground to being what a layman like me would call "in space"
[14:05] <ColonelPanic001> just "boom" and they're there
[14:05] <wolfger> ColonelPanic001: First one you've watched live? You really know how to procrastinate, don'cha?
[14:05] <ColonelPanic001> :P
[14:06] <wolfger> greg-g: it'd be cool to "feel it". Visually, the TV/monitor is the best show, but there's no rumble.
[14:08] <rick_h__> why does it sound like I missed the launch on this?
[14:09] <wolfger> OK, what's with the TWiT Brick House?
[14:09] <rick_h__> they're building a wall by the entry way where you buy a brick as part of raising $$ for the new studio
[14:09] <rick_h__> think lococast.net with a big logo on a big brick would look good in there :)
[14:10] <wolfger> It would.
[14:10] <rick_h__> but $640 is a bit much, that's what it would cost us to get our t-shirts
[14:11] <greg-g> wolfger: yeah, and I can watch the video later :)
[14:14] <wolfger> 3D is nothing compared to VR.... movie studios need to figure out how to include physical and aromatic stimuli into their movies
[14:14] <ColonelPanic001> how sad that when I see a shuttle launch, it reminds me of the 60s and whatnot. I mean, travelling through f'ing space should not be something I think of as "back in the old days"
[14:14] <ColonelPanic001> it's f'ing SPACE
[14:15] <wolfger> Space: The BTDT Frontier
[14:15] <ColonelPanic001> VR and 3D are nothing compared to a goddamn plot. They need to learn to incorporate a goddamn plot in their movies.
[14:15] <wolfger> ColonelPanic001: that's just crazy talk
[14:15] <wolfger> next you'll be asking them not to rehash old movies
[14:15] <ColonelPanic001> I'll take a grainy black and white movie with good writing over Transformers any day
[14:16] <wolfger> I don't know... some days I just want to see Megan Fox bending over the hood of a car....
[14:16] <ColonelPanic001> that takes 10 seconds.
[14:17] <brousch> wolfger: there's a whole genre of movies for that
[14:17] <ColonelPanic001> I have the internet for porn.
[14:17] <brousch> i see ColonelPanic001 is an expert in that genre
[14:17]  * ColonelPanic001 nods
[14:20] <wolfger> how can snap-l not be here?
[14:20] <wolfger> He needs to see this: http://shirt.woot.com/shirts/gozerhead
[14:28] <wolfger> Man dies due to being stupid; police and media blame internet instead. http://www.cnn.com/2011/WORLD/asiapcf/05/15/australia.planking.death/index.html?hpt=Sbin
[14:32] <rick_h__> ok, had to look this thing up
[14:33] <rick_h__> and the 'planking' is stupid that is all
[14:33] <rick_h__> let the morons winnow themselves away I say
[14:37] <binbrain> good news is if the planking photo goes bad there will be an audience for the aftermath photo as well
[14:49] <brousch> rick_h__: i guess my online barcamp session grid viewer technically works already: http://waznex-server.appspot.com
[14:50] <brousch> it just displays the most recently uploaded photo
[14:50] <rick_h__> cool
[14:54] <brousch> now i just have to make it better
[14:54] <rick_h__> hah, that's always the fun part
[14:55] <brousch> the mobile app will take the picture and send it right to the server, so it avoids having to take a picture, visit a web page, click upload, browse your gallery for the photo, select it
[14:55] <rick_h__> and then store it locally for quick repeat access?
[14:56] <_stink_> heh, file a feature request!
[14:56] <brousch> no local storage
[14:56] <rick_h__> boooo, what about all that "lack of internet" talk :P
[14:57] <brousch> for offiline visit the physical board
[14:57] <rick_h__> bah, we want OCR and local cache with audio search ability
[14:58] <brousch> heh
[14:58] <brousch> well i'm considering slicing the photo up by column
[14:59] <rick_h__> you should test what google docs does for parsing it
[14:59] <rick_h__> be curious if it can actually make anything decent from it
[14:59] <brousch> i might learn how at tonight's grpug: SimpleCV - open source machine vision with python
[14:59] <brousch> google docs only recognizes fonts
[15:00] <brousch> i tried it a week or two ago
[15:00] <rick_h__> gotcha
[15:00] <brousch> slicing it by column would make it really useful on a tiny screen
[15:00] <rick_h__> definitely
[15:00] <brousch> column is time slot, row is room
[15:00] <greg-g> I've heard good things about SimpleCV from the Ingenuitas guys http://ingenuitas.com/
[15:01] <brousch> greg-g: that's who's presenting tonight
[15:01] <greg-g> oh, awesome!
[15:01] <brousch> i guess he's in holland for a month or so
[15:01] <wolfger> rick_h__++ (re: winnowing)
[15:01] <rick_h__> nice, GRPUG is 4th result for "simplecv python" search in google for me
[15:01] <wolfger> I find it sad that society has moved away from that concept...
[15:01] <greg-g> huh, they have a new team member, Katherine
[15:01] <brousch> rick_h__: hah, that's awesome
[15:02] <rick_h__> oh, nate is a dev on this?
[15:02] <rick_h__> interesting
[15:02] <brousch> nate oostendorp
[15:02] <brousch> you know him?
[15:02] <rick_h__> man I hate SF ui, ugh
[15:02] <greg-g> :)
[15:03] <rick_h__> so his sister is a best friend of my wife
[15:03] <rick_h__> they went to med school together where I worked
[15:03] <rick_h__> so know his sister, etc
[15:03] <rick_h__> I interviewed with him for 20min in the strangest interview I've ever had a while ago
[15:03] <greg-g> haha, awesome
[15:04] <rick_h__> yea, after I failed to get in, met him in person at this sisters house warming party...kind of strange
[15:04] <rick_h__> /this/his/g
[15:05] <greg-g> oh I bet
[15:05] <rick_h__> heh, only time I interviewed and didn't ge the job, not that I'm bitter or anything :P
[15:05] <brousch> one of the other guys is bringing people from gentex, so he might even get some business out of the presentation
[15:05] <brousch> rick_h__ wasn't awesome enough for them? now i'm scared
[15:05] <greg-g> rick_h__: :P
[15:05] <rick_h__> anyway, looks like an interesting thing
[15:06] <rick_h__> brousch: heh, well I think I'd have done fine, but yea...
[15:08] <brousch> the strangest interview i had was in the basemnt of an ann arbor apartment back in 1998 or 1999. it was a startup that scraped the USA today web site for baseball stats and packaged them for fantasy baseball. the guys are probably millionaires by now
[15:10] <wolfger> or in court
[15:11] <wolfger> although I believe the courts already ruled that stats aren't proprietary, the MLB is rather agressive in protecting anything it views as "it's property"
[15:13] <brousch> heh
[16:18] <greg-g> what is snap-l up to today?
[16:18] <greg-g> he's taking weird photos: https://identi.ca/attachment/45528874
[16:18] <rick_h__> belated anniversary celbration
[16:18] <rick_h__> up at frakenmuth for a few days
[16:18] <rick_h__> lol, that pic is a winner
[16:19] <greg-g> awesome
[16:22] <wolfger> JoDee's sense of humor FTW
[16:23] <wolfger> not a chance in hell I could get a pic of my wife wearing that hat... or live to tell the tale if I did.
[16:24] <brousch> tequila
[16:25] <rick_h__> "to enable stupid picture mode, please apply tequila"
[16:25] <rick_h__> yea, that works for most wives :P
[16:25] <brousch> hm, when did oreilly ebook start coming in APK?
[16:25] <rick_h__> apk?
[16:25] <rick_h__> I know they've had a few ebooks as apps, but meh
[16:26] <rick_h__> hah, playbook recall time
[16:27] <rick_h__> go go BB with your bad self
[16:27] <brousch> hm, not all of them are apk, only about 1/2 of mine
[16:28] <brousch> rick_h__: don't taunt. i'm sure tjagoda is already depressed enough
[16:41] <jrwren> you never owned pretty hate machine?
[16:43]  * wolfger resists (barely) the temptation to taunt tjagoda
[17:19] <rick_h__> lol, I love the web: http://thenextweb.com/apps/2011/05/11/angry-birds-for-chrome-already-hacked-unlocking-all-levels/
[17:25] <greg-g> rick_h__: yeah, saw that when I was looking for tips on getting all of the "chrome balls" this weekend
[17:25]  * greg-g isn't addicted, promise
[17:25] <rick_h__> greg-g: yea, I didn't have to complete the whole android app either :/
[17:25] <rick_h__> fortunately I think I got most of it out of my system then
[17:26] <rick_h__> just love the web side though. View source, change stuff, cheat away
[17:26] <greg-g> :)
[17:26] <greg-g> yeah, fun stuff
[18:03] <rick_h__> webdevs Blazeix, widox, n0p_ http://www.youtube.com/watch?v=N8SS-rUEZPg&feature=player_embedded
[18:03] <rick_h__> some yummy new features in there and some I didn't know they had added
[19:28] <tjagoda> brousch/rick_h/wolfger: BBerry recalled them while they were still in the distribution channel
[19:29] <tjagoda> Consumers pretty much unaffected
[19:29] <rick_h__> I think most playbooks are still in the distribution channel :)
[19:29] <tjagoda> That's just trolling right there =P
[19:29] <rick_h__> you know it
[19:30] <tjagoda> Least it's not like an iPhone, where I have to "hold it right" to get signal? =P
[19:32] <brousch> does it even get 3G signal?
[19:33] <tjagoda> Nah, those launch in a bit
[19:34] <tjagoda> (Hopefully I wont have to "hold it right" to get 3G signal, or I'll never get the end of that.(
[19:34] <tjagoda> that.) *
[19:35] <brousch> so even if you hold it right, you don't signal
[19:36] <brousch> iphone > bbpad
[19:37] <tjagoda> iAnything < *
[19:38] <tjagoda> Especially after they brutally stomped iFlow out of business
[19:43] <greg-g> horrible name, iFlow
[19:45] <brousch> better than iStoppedUp
[19:45] <tjagoda> iFlew?
[19:46] <brousch> iCantPee
[20:20] <binbrain> does anybody know how the md5sum of a package makes it into the aptitude info?
[20:22] <binbrain> at 1st I thought it went in the control file or something that builds the deb put its somewhere, but then realized that is impossible
[20:24] <jrwren> releases.gz includes it IIRC
[20:26] <jrwren> err, packages.gz
[20:27] <jrwren> releases includes md5sum of the packages so that it can't be spoofed easily.
[20:32] <binbrain> jrwren: thanks, that seems right, I guess my problem is that I need the packages.gz after a fresh instal without doing an apt-get update which I believe fetches that packages.gz info
[20:34] <jrwren> right
[20:34] <jrwren> its on the CD
[20:34] <jrwren> do you want me to look up something for you?
[20:36] <jrwren>  dists/natty/Release shows 2 Packages files on the CD
[20:38] <binbrain> I see them there, but the problem is that the info in them isn't "merged" or whatever such that if I did a show on the package info I'd get the md5sum
[20:38] <binbrain> anyhow, I have something to go on, thanks
[20:47] <jrwren> not sure what you mean.
[20:47] <jrwren> what are you trying to do?
[20:51] <binbrain> jrwren: have a fresh install, no apt-get update or anything. I need to right away look at the packages installed and see what their md5sum's are. I noticed that the md5sum: on the package info's are empty
[20:52] <jrwren> they are?
[20:53] <binbrain> jrwren: yeah, not sure why
[20:53] <jrwren> so they are. i wonder if its an apt v. dpkg thing
[21:02] <binbrain> jrwren: md5sum/SHA* info doesn't get added until the 1st apt-get update
[21:02] <binbrain> just confirmed that
[21:07] <brousch> it looks like mono will survive http://tirania.org/blog/archive/2011/May-16.html
[21:08] <jrwren> mono will survive no matter what.
[21:08] <jrwren> its open source.
[21:08] <jrwren> its like saying "what if google fired guido, what would happen to python???"


[15:00] <Laney> !dmb-ping
[15:00] <xnox> yo
[15:00] <bdmurray> hi
[15:02] <Laney> pishuilu: just checking you are here for the DMB meeting?
[15:03] <pishuilu> Laney: hi, I am here.
[15:04] <Laney> ok, we will be with you shortly
[15:04] <Laney> let's go
[15:04] <pishuilu> ok
[15:04] <Laney> #startmeeting DMB 2015-09-28
[15:04] <meetingology> Meeting started Mon Sep 28 15:04:26 2015 UTC.  The chair is Laney. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:04] <meetingology> Available commands: action commands idea info link nick
[15:04] <Laney> #topic Review of previous action items
[15:04] <Laney> #subtopic bdmurray to setup a pad for the dmb to collaborate on response for noskcaj
[15:05] <Laney> any news?
[15:05] <bdmurray> I ended up creating a bzr branch
[15:05] <Laney> I missed that
[15:05] <Laney> does it have anything useful in?
[15:06] <bdmurray> I don't think so.
[15:06] <Laney> what's next then?
[15:06] <bdmurray> Nope, nothing in it.
[15:08] <bdmurray> I think "micahg to get Noskcaj feedback"
[15:08] <Laney> bit concerned that this drags on
[15:09] <bdmurray> well we could start adding our own feedback then
[15:09] <Laney> right
[15:09] <Laney> I didn't -1 the application but those who did could start to work on it...
[15:10] <Laney> xnox: that includes you
[15:11] <Laney> #subtopic Laney to start an onboarding page for new dmb members
[15:11] <Laney> I didn't do this yet :(
[15:11] <Laney> I am kind of annoyed at myself for not getting around to it
[15:11] <Laney> and I will put it on my calendar for friday afternoon
[15:12] <Laney> done
[15:12] <Laney> #action laney stop slacking and write onboarding page
[15:12] <meetingology> ACTION: laney stop slacking and write onboarding page
[15:12] <Laney> #subtopic michag to confirm if mozc packageset change happened
[15:13] <Laney> did, yes?
[15:13] <Laney> Archive Upload Rights for ubuntu-input-methods-dev: archive 'primary', package set 'input-methods' in wily
[15:13] <Laney> #subtopic michag to follow up with Unit193 about their application and a meeting date
[15:13] <Laney> NFI
[15:13] <Laney> #action michag to follow up with Unit193 about their application and a meeting date
[15:13] <meetingology> ACTION: michag to follow up with Unit193 about their application and a meeting date
[15:14] <bdmurray> I seem to recall that happening but not the outcome.
[15:16] <Laney> can't find any mail anyway
[15:16] <Laney> #topic PPU application: ShuiLu Pi for ubuntukylin-default-settings
[15:16] <Laney> pishuilu: hey, it's now your turn
[15:16] <Laney> can you introduce yourself and your application?
[15:16] <pishuilu> ok
[15:16] <Laney> #chair bdmurray
[15:16] <meetingology> Current chairs: Laney bdmurray
[15:16] <Laney> (brb)
[15:17] <pishuilu> I am a member of Ubuntu Kylin team.
[15:17] <pishuilu> I maintain ubuntukylin-default-settings package.
[15:18] <pishuilu> This package contains a number of system configurations.
[15:19] <pishuilu> For example, firefox search engine and start page, default language for installer images, fix zip fie display of garbage characters
[15:19] <pishuilu> etc
[15:20] <cyphermox> Do you have plans to start maintaining other packages in ubuntukylin, or other packages in general?
[15:20] <xnox> pishuilu: have you come across something that you wanted to customize, but it wasn't in fact customizable at all? Ie. impossible to set some kind of a setting, cause there is no such setting. And how did you resolve such requests?
[15:21] <pishuilu> cyphermox: Now I maintain ubuntukylin-default-settings and ubiquity-slideshow-ubuntukylin package
[15:22] <pishuilu> Later will also maintain other Ubuntu Kylin packages
[15:24] <bdmurray> pishuilu: Could you answer xnox's question?
[15:24] <pishuilu> xnox: Sometimes I should create a script to execute
[15:25] <pishuilu> shell script
[15:26] <pishuilu> Like fix bug LP: #1462848 (fix zip file display of garbage characters)
[15:30] <bdmurray> pishuilu: Have you followed the work in bug 1422290 which seems like it may be a proper fix?
[15:30]  * xnox ponders if my question got through
[15:30] <xnox> pishuilu: have you come across something that you wanted to customize, but it wasn't in fact customizable at all? Ie. impossible to set some kind of a setting, cause there is no such setting. And how did you resolve such requests?
[15:30] <pishuilu> cyphermox: But I can't maintain all Ubuntu Kylin packages. some packages will be maintained by other colleagues.
[15:31] <cyphermox> of course
[15:34] <bdmurray> pishuilu: have you seen the other questions asked of you by xnox and myself?
[15:34] <pishuilu> bdmurray: I don't follow  bug 1422290. I fix some questions which is not fixed by upstream. If upstream fix this bug ,I will undo this configuration.
[15:37] <pishuilu> xnox: sorry , I miss your question.
[15:37] <xnox> pishuilu: have you come across something that you wanted to customize, but it wasn't in fact customizable at all? Ie. impossible to set some kind of a setting, cause there is no such setting. And how did you resolve such requests?
[15:38] <pishuilu> ok
[15:38]  * stgraber waves (my phone lied to me)
[15:39] <pishuilu> xnox: I think if it wasn't in fact customizable at all, so this bug is not for this package.
[15:40] <pishuilu> xnox: This package function is system configuration.
[15:40] <xnox> pishuilu: so you never modified anything in ubuntu, or request to be modified in ubuntu to customize stuff??
[15:43] <pishuilu> xnox: I mean configuration is not modifying some package source.
[15:44] <pishuilu> xnox: For exmaple, replace the specific icon
[15:45] <pishuilu> configure defaults.list of applications etc.
[15:50] <bdmurray>  pishuilu: Could you comment on happyaron's caveat regarding a need "to be more careful"?
[15:51] <pishuilu> xnox: You mean that modify some package source and submit patches to upstream?
[15:52] <pishuilu> bdmurray: ok
[15:54] <pishuilu> bdmurray: happyaron's caveat mean : when I fix a bug ,I should consider a problem more comprehensively
[15:54] <bdmurray> pishuilu: And what steps are you taking to do that?
[15:57] <pishuilu> When I fix a bug , first I should think this bug's influence of the whole system
[15:58] <pishuilu> so I can consider a problem more comprehensively
[15:59] <bdmurray> Can you give us an example of how you've done that?
[16:00] <pishuilu> Details should be considered in all kinds of unexpected circumstances
[16:01] <pishuilu> For example , fix bug 1462848
[16:03] <Laney> (I have one when you're finished)
[16:03] <Laney> (then we should wrap up as we're over time already)
[16:03] <pishuilu> I didn't consider the previous zh_CN outside
[16:05] <pishuilu> Laney: I am sorry. Spent so much time !
[16:07] <Laney> It's okay
[16:07] <Laney> bdmurray: you want to ask more?
[16:07] <pishuilu> I should consider zh_CN,zh_TW,zh_HK etc.
[16:08] <bdmurray> Laney: no, that's okay
[16:09] <Laney> ty
[16:09] <Laney> pishuilu: What testing do you do on the package before asking for it to be uploaded?
[16:09] <Laney> Do you test it on a non Chinese system for example?
[16:11] <pishuilu> Laney: I test it on Chinese system.
[16:12] <pishuilu> Because Ubuntu Kylin provide for the use of Chinese users
[16:12] <Laney> I'm worried about cases where I have normal Ubuntu and Ubuntu Kylin installed at the same time
[16:12] <Laney> like if I have a Chinese friend who uses my computer
[16:13] <Laney> I don't want the Kylin settings to break anything on my account
[16:14] <pishuilu> Laney: I see what you mean
[16:16] <pishuilu> Laney: I should make some configurations  effect only in zh_CN.
[16:17] <Laney> yes, you can also look at the $DESKTOP_SESSION environment variable
[16:17] <Laney> it's also valid to be chinese and not use kylin :)
[16:18] <pishuilu> Laney:OK, I know.
[16:18] <pishuilu> Thanks.
[16:18] <Laney> ok, thanks
[16:18] <Laney> !dmb-ping
[16:18] <Laney> anyone else?
[16:18] <Laney> or vote?
[16:19] <xnox> i lost wifi
[16:19]  * xnox is back
[16:20] <Laney> hello?
[16:20] <bdmurray> I have no more questions.
[16:23] <Laney> #vote grant ShuiLu Pi upload rights for ubuntukylin-default-settings
[16:23] <meetingology> Please vote on: grant ShuiLu Pi upload rights for ubuntukylin-default-settings
[16:23] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[16:26] <xnox> +1
[16:26] <meetingology> +1 received from xnox
[16:27] <bdmurray> +1
[16:27] <meetingology> +1 received from bdmurray
[16:28] <Laney> +1
[16:28] <meetingology> +1 received from Laney
[16:28] <stgraber> +1 [happy to see that the package is no longer overwriting paths owned by other packages but doing clean diverts now, otherwise would have -1]
[16:28] <meetingology> +1 [happy to see that the package is no longer overwriting paths owned by other packages but doing clean diverts now, otherwise would have -1] received from stgraber
[16:29] <Laney> Would like to see a bit more consideration given to co-existing with other flavours
[16:30] <pishuilu> Laney: OK
[16:30] <Laney> and probably a review procedure
[16:30] <Laney> like, don't commit any changes without another team member approving them
[16:31] <Laney> anyway...
[16:31] <Laney> #endvote
[16:31] <meetingology> Voting ended on: grant ShuiLu Pi upload rights for ubuntukylin-default-settings
[16:31] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[16:31] <meetingology> Motion carried
[16:31] <Laney> stgraber: you ok to action?
[16:31] <stgraber> sure
[16:32] <stgraber> done
[16:32] <Laney> thanks
[16:33] <Laney> pishuilu: https://wiki.ubuntu.com/MOTU/New <- good page to read
[16:33] <Laney> and please ask if you have any questions at all
[16:33] <pishuilu> OK ,I know. Thanks very much.
[16:35] <Laney> #topic AOB
[16:36] <Laney> can all of you please respond to this old thread?
[16:36] <Laney> https://lists.ubuntu.com/archives/devel-permissions/2015-August/000815.html
[16:37] <Laney> #endmeeting
[16:37] <meetingology> Meeting ended Mon Sep 28 16:37:28 2015 UTC.
[16:37] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-28-15.04.moin.txt
[16:37] <Laney> cheers
[16:39] <pishuilu> Thank you, goodbye!
[16:40] <jdstrand> hi!
[16:40] <mdeslaur> \o
[16:41] <jdstrand> #startmeeting
[16:41] <meetingology> Meeting started Mon Sep 28 16:41:07 2015 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:41] <meetingology> Available commands: action commands idea info link nick
[16:41] <jdstrand> The meeting agenda can be found at:
[16:41] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:42] <jdstrand> [TOPIC] Weekly stand-up report
[16:42] <jdstrand> I'll go first
[16:42] <jdstrand> this week I'm working on snappy documentation
[16:43] <jdstrand> when helping someone with framework policy for a snap, I discovered that snappy's dbus bus policy implementation is not sufficient (not surprising, but now we have details to move forward)
[16:43] <jdstrand> I need to file a bug with ideas on how to solve that so the snappy guys can get it fixed
[16:44] <jdstrand> I have a couple of review tools issues to fix
[16:44] <jdstrand> helping the golang, juju, and lxd MIRs along
[16:44] <jdstrand> and an embargoed issue
[16:46] <jdstrand> fyi, ty hicks is out this week sprinting
[16:46] <jdstrand> mdeslaur: you're up
[16:46] <mdeslaur> I just released nvidia drivers
[16:46] <mdeslaur> and I'm working on php5 updates
[16:46] <mdeslaur> I have a few other updates to test
[16:46] <mdeslaur> and that's probably it for this week, as I'm on vacation for the next two weeks
[16:47] <mdeslaur> that's it from me, sbeattie
[16:47] <sbeattie> mdeslaur: nice!
[16:47] <sbeattie> I'm covering community for ty hicks this week while he's sprinting
[16:47] <sarnold> mdeslaur: nice :)
[16:47] <sbeattie> I have an embargoed issue this week
[16:48] <sbeattie> I'm also working on gcc-5 pie stuff
[16:48] <sbeattie> I have some outstanding apparmor patches to review.
[16:48] <sbeattie> that's pretty much my week.
[16:49] <sbeattie> jjohansen: I think you're up?
[16:49] <jjohansen> I am working on breaking the world
[16:50] <jdstrand> sbeattie: how close are we to putting gcc-5 pie to done?
[16:50] <jjohansen> that is kernel work on stacking and its related items
[16:51] <jjohansen> I have some bug fixes to pull together too, that need to get pushed out to various kernels
[16:51] <jdstrand> jjohansen: after the meeting can we sync super quick on that?
[16:51] <jjohansen> jdstrand: sure
[16:53] <jjohansen> should I pause for sbeattie, or just poke sarnold
[16:53] <jdstrand> I think moving ahead is fine
[16:53] <sarnold> I'm on bug  triage this week and working on the lxd MIR
[16:54] <sarnold> I'll try to poke at some apparmor patches for a change of pace
[16:54] <sarnold> I think that's it for me, chrisccoulson?
[16:55] <chrisccoulson> I shall be doing a thunderbird update this week. That's the only planned update I have :)
[16:55] <chrisccoulson> So I'll be hoping to make some progress on Oxide (I investigated some memory use issues last  week, and have just finished adding support for HTML notifications)
[16:57] <chrisccoulson> I would like to start figuring out what https://blueprints.launchpad.net/oxide/+spec/site-settings is going to look like
[16:57] <chrisccoulson> I think that's me done
[16:58] <jdstrand> [TOPIC] Highlighted packages
[16:59] <jdstrand> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:59] <jdstrand> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:59] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/jabberd2.html
[16:59] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/revelation.html
[16:59] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/c-icap.html
[16:59] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/iscsitarget.html
[16:59] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/tpp.html
[17:00] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:00] <jdstrand> Does anyone have any other questions or items to discuss?
[17:03] <jdstrand> mdeslaur, sbeattie, jjohansen, sarnold and chrisccoulson: thanks!
[17:04] <jdstrand> #endmeeting
[17:04] <meetingology> Meeting ended Mon Sep 28 17:04:01 2015 UTC.
[17:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-28-16.41.moin.txt
[17:04] <sarnold> thanks jdstrand
[17:04] <jjohansen> tanks jdstrand
[17:05] <mdeslaur> thanks jdstrand!
[17:05] <sbeattie> thanks jdstrand


[07:19] <locodir-user> hi every one i am new here
[11:25] <locodir-user> hai
[11:26] <locodir-user> hello friend
[11:26] <locodir-user> is anyone there


[08:14] <dbarth> hey trainguards
[08:14] <dbarth> or qa
[08:14] <sil2100> Hey! What's up?
[08:15] <dbarth> i'm trying to push https://requests.ci-train.ubuntu.com/#/ticket/1503#audit_log but the lander signoff flag got resetted
[08:15] <dbarth> i don't know why britney is so unhappy tbh
[08:16] <dbarth> hmm, or maybe :
[08:16] <dbarth> 2016-06-20 17:06:26 +0200 (abreu-alexandre) Preparing packages.
[08:16] <sil2100> dbarth: you want it to be APproved by Lander?
[08:16] <dbarth> i will re-approve then; just reloading the packages to be double sure
[08:16] <sil2100> Ok
[08:16] <dbarth> grr :)
[08:16] <sil2100> Yeah ;)
[08:16] <robru> dbarth: it was still in state "currently building" when you set it, that's not allowed
[08:17] <robru> dbarth: efrrr
[08:17] <sil2100> robru: sightseeing, now!
[08:17] <robru> dbarth: yeah sorry it's because Alex rebuilt, I misread
[08:18] <dbarth> right probably
[08:18] <dbarth> rgrrr
[08:18] <robru> sil2100: I'm sightseeing the laundromat Right now
[08:18] <sil2100> robru: they have one in the hotel?
[08:18] <robru> sil2100: no it's some blocks away
[08:19] <robru> sil2100: in an hour I'll go for lunch
[08:24] <robru> xavigarcia: only public branches are supported
[08:26] <xavigarcia> robru: hey, thanks for pointing out! I will ask the guys who maintain that project to make it public!
[08:26] <robru> xavigarcia: you're welcome
[08:39] <sil2100> robru: just not to the restaurant upstairs ;) Hope you don't eat there no more
[08:47] <robru> sil2100: haven't been upstairs even once since The Incident
[10:24] <sil2100> robru: hey!
[10:24] <sil2100> robru: you still somewhere around?
[10:25] <robru> sil2100: what's up?
[10:25] <sil2100> robru: I noticed that commitlogs stopped working since the usual API bits for published_versions doesn't seem to get updated (at least on first look?)
[10:25] <sil2100> https://requests.ci-train.ubuntu.com/v1/comments?published_versions=:&text=Merging
[10:25] <sil2100> I use this and the last published_version mention is from the 16th
[10:26] <robru> sil2100: hmmm that's odd.
[10:26] <sil2100> All landings later than that are not registered there
[10:26] <sil2100> hmm
[10:26] <robru> sil2100: I did touch the audit logging code but it should all still be hooked up with the published versions
[10:26] <sil2100> For instance grepping for the recent ubuntu-ui-toolkit release gives me nothing
[10:27] <sil2100> e.g. we had 1.3.2009+15.04.20160615.3 released around yesterday and it's not there
[10:28] <robru> sil2100: ok I'll check what changed on the 16th
[10:30] <sil2100> robru: thanks :)
[10:31] <robru> sil2100: ok I have some leads to follow up here. but first, are you sure you can't change your commitlog script to just inspect what package versions were built in the image? I've always felt trying to inspect the train for it's publications would be error-prone, like this.
[10:32] <sil2100> robru: I do that, but I need the binding package_version->landing from somewhere
[10:32] <sil2100> I get the list of package versions from the manifests and look for the corresponding landings to those versions
[10:32] <robru> hmmm
[10:33] <sil2100> How am I supposed to know which package version was coming from which landing otherwise?
[10:33] <robru> sil2100: why does it matter which landing it came from? can't you just inspect the changelog on the released package to know everything you need to know about it?
[10:33] <sil2100> robru: no, since we want to know the landing description as well
[10:33] <robru> hmmm
[10:34] <sil2100> robru: since I print out changelog entries as well, but we need to know which packages came from which landing, as a landing can be composed from many different packages
[10:34] <sil2100> Changelogs give us info about the certain package, but we want to know if that package was part of a bigger piece or not
[10:35] <robru> sil2100: yeah but I don't really understand why you need to track this relation, can't the commitlog just say "ok, this image has a new unity8, new mir, etc"
[10:35] <sil2100> So we need: landing description and group the package releases into landings
[10:36] <sil2100> Well, one of the reasons might be reverts: when we want to revert a package, we need to know what other packages from the landing might need reverting
[10:36] <sil2100> But in overall it also gives a good understanding of what feature-sets have landed
[10:36] <sil2100> As I said, a changelog gives you info about just one component
[10:36] <sil2100> While landings are made out of multiple components that make up for a landing
[10:37] <sil2100> And that landing might have more importance when all pieces are released - without this info we waste time by trying to connect packages together
[10:38] <sil2100> Looking at the changelogs and then trying to figure out: "was this landed as a separate thing? Did this go with any other changes? Where are the other bits? Are there any other bits?"
[10:41] <robru> sil2100: ok I pushed a fix, after about an hour, if there are any tickets currently in proposed, you should see their published_versions fields being populated.
[10:41] <robru> sil2100: eg just look at https://requests.ci-train.ubuntu.com/v1/comments?published_versions=: to see the values being filled before the merge happens
[10:41] <sil2100> \o/
[10:42] <robru> sil2100:  eg https://requests.ci-train.ubuntu.com/#/tickets?status=pocket this one ticket should be the guinea pig for now
[10:42] <robru> sil2100: not a retroactive fix, of course, anything already merged is lost
[10:46] <sil2100> robru: ok, no worries, I just won't re-generate silos in that case ;)
[10:46] <sil2100> I mean, commitlogs
[10:48] <sil2100> robru: anyway, thanks!
[10:51] <robru> sil2100: you're welcome
[11:27] <rvr> mardy: ping
[11:27] <rvr> mardy: I can't authenticate in Instagram, is it known?
[11:29] <rvr> mardy: I see a json response, {"code": 403, "error_type": "OAuthForbiddenException", "error_message": "You are not a sandbox user of this client"}
[11:33] <rvr> pstolowski: ping
[12:00]  * sil2100 goes for a longer lunch
[12:06] <mardy> rvr: interesting...
[12:09] <mardy> rvr: please file a bug on the instagram scope: https://www.instagram.com/developer/sandbox/
[12:18] <pstolowski> rvr, pong
[12:18] <rvr> pstolowski: Hi
[12:19] <pstolowski> hey
[12:19] <rvr> pstolowski: I found a problem with silo 1 and Flickr
[12:19] <rvr> pstolowski: After posting a comment, the page was refreshed, but I couldn't post any other comments
[12:20] <rvr> pstolowski: Scope said "Please login to post a comment". I checked and was still authorized in Accounts.
[12:20] <rvr> pstolowski: See the screenshot in the trello card
[12:25] <pstolowski> rvr, hmm, i don't think changes in this silo could cause this, did you have time to check it without the silo?
[12:38] <pstolowski> rvr, i'm reflashing to check this
[12:39] <rvr> pstolowski: Sorry. Nope, I didn't check without the silo packages.
[13:05] <pstolowski> rvr, ok, i check with and without the silo
[13:06] <pstolowski> rvr, i cannot reproduce the problem. in both cases after hitting 'Post' i'm still able to enter a comment. however, the scope seems to be broken. in both scenarios i don't see my comments. scope-registry.log has this:2016/06/21 15:03:37 post a comment:  fail
[13:07] <rvr> pstolowski: I see
[13:07] <pstolowski> rvr, re your particular problem, i suspect a problem with online accounts; i've seen similar issues in the past, removing and re-adding the account may help
[13:08] <rvr> pstolowski: In stable it still shows the text field to enter a new comment
[13:08] <pstolowski> rvr, also, without the silo the preview gets reversed; the silo fixes it
[13:08] <rvr> pstolowski: But I see that the content sort problem is gone
[13:09] <pstolowski> rvr, do you ever see your comments really submmited after posting?
[13:09] <rvr> pstolowski: Nope
[13:10] <rvr> pstolowski: They aren't posted, I don't see them checking in the website
[13:11] <pstolowski> rvr, can you grep /home/phablet/.cache/upstart/scope-registry.log for 'post a comment' ?
[13:41] <robru> sil2100: fix confirmed: https://requests.ci-train.ubuntu.com/v1/comments?published_versions=:
[14:31] <renato___> robru, messaging app is faling to build on  arm64 for yakkety and xenial, with some strang open gl bug
[14:32] <robru> renato___: please refer to channel topic
[14:32] <renato___> robru, is this a blocker? I think this is not new, since this is not related with my changes
[14:34] <renato___> robru, sorry  I thought that you are back , enjoy your vocations
[14:34] <robru> Thanks!
[14:37] <kenvandine> robru, lol.... you need to learn how to vacation :)
[14:37] <kenvandine> no irc allowed!
[14:39] <sil2100> I told him that!
[14:39] <sil2100> But at least in case of serious forest fires we can reach out to him
[14:59] <dbarth> jibel: hey, i have silo 19 which seems not to want to go onto the QA board
[15:00] <dbarth> ie https://requests.ci-train.ubuntu.com/#/ticket/1545
[15:00] <dbarth> can you add it?
[15:00] <jibel> dbarth, yes, I'll have a look
[15:00] <dbarth> thanks
[16:32] <renato___> trainguards,  silo 46 is not pushing the packages to the ppa? Could you guys help me with that?
[16:58] <sil2100> renato___: let me take a quick look
[16:59] <sil2100> renato___: I see packages recently built, what's wrong with those?
[16:59] <sil2100> renato___: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-046/+packages
[17:00] <renato___> sil2100, I ask to update the the diff, and started to work.
[17:00] <renato___> thansk
[20:40] <kenvandine> sil2100, what does this mean?
[20:40] <kenvandine> Diff missing (qtbase-opensource-src-gles/vivid, qtbase-opensource-src/vivid, qtdeclarative-opensource-src-gles/vivid, qtdeclarative-opensource-src/vivid).


[06:56] <blahdeblah> I trust everyone heard about the Ubuntu Forum compromise by now?  Make sure you change your password (and any others that matched it), and be on the lookout for phishing scams that ask you to enter your Ubuntu forums user id.
[07:03] <bradm> honest, we're working on getting it back up! :)
[07:09] <jared> blahdeblah & bradm - do eithe rof oyu have thoughts on service slike lastpass? This breach has me considering but I'm not sure enough either way to make a decision
[07:09] <bradm> jared: I use keepassx myself for some stuff
[07:10] <jared> I'm smart enough to use 2 factor on everythingi that has it but yeah, to me if I don't use it I don't have strong passwords, if I do use it if they get in they get everything.
[07:10] <jared> So not quite sure
[07:11] <bradm> anything that lets you use different passwords everywhere would have to be an improvement
[07:11] <bradm> I can't comment specifically on lastpass, I don't use it myself
[07:12] <bradm> but there's no reason you can't store the KeePassX db on, say, UbuntuOne's filesharing..
[07:12] <jared> bradm: I'm locked down on my work laptop which I use for Uni daily
[07:12] <jared> Was considering the yubikey option with lastpass
[07:13] <bradm> thats probably not a bad way to go
[07:13] <jared> And then on the phone I just have to use their special browser for "secure" stuff and chrome for all the stuff I don't log in for
[07:14] <jared> And just make sure I set up the master password as secure as possible
[07:16] <bradm> pwgen -s with as large a size as you can remember isn't a terrible way to go..
[07:17] <jared> Nah the idea is you don't remember your master, you only use it when you change stuff
[07:17] <jared> Write it on a piece of paper and store it in a safe/drawer
[07:18] <bradm> uh, so people can access your passwords without authenticating?
[07:19] <jared> Sounds like I haven't thought this through
[07:19] <jared> Got myself a bit confused when reading up perhaps I haven't unconfused myself yet
[07:20] <bradm> with keepass it has a master password you have to enter when you open the db
[07:20] <bradm> I thought lastpass was similar
[07:20] <jared> Ah yeah, ignore me
[07:21] <jared> I was getting a few different services intermingled
[07:21] <jared> I guess 12 - 16 should be ok
[07:22] <jared> I find much over that gets difficult
[07:24] <jared> Handy that the s4 has a numbers row on the main keyboard for this sort of thing
[07:24] <bradm> yeah, that should be plenty
[07:25] <jared> Apparently lastpass had one breach 2 years ago but stated as long as the masterpass was secure (not dictionary, etc) then no issues due to the fact they don't get any unencrypted data
[07:26] <bradm> depends on how its encrypted
[07:27] <bradm> the forums didn't have passwords in plain text, but that doesn't stop people complaining :)
[07:28] <jared> I'm not overly concerned about the forum one, but it did make me rethink what the process I use for choosing password
[07:28] <bradm> I mean, there's encryption, and there's encryption.
[07:29] <bradm> rot13 could be called encryption, but I'd hardly call it secure
[07:31] <jared> I'm far from expert but the lastpass stuff is described at https://lastpass.com/whylastpass_technology.php if that helps. The problem I have is that I don't know enough to see if I'm being convinced by crappy advertising arguments
[07:33] <bradm> AES is pretty much considered secure
[07:33] <bradm> and 256 bit AES would take a long time to crack
[07:34] <bradm> thats not to say there won't be some new thing found, but you can say that of anything
[07:40] <jared> bradm: thanks for letting me pick your brain. I'm thinking a lastpass service might be worth it if it means I can ahve independent strong passwords as compared to the weak stuff I formulate if I have to remember them all
[07:40] <bradm> jared: no worries, I haven't heard anyone say bad things about lastpass really, I'm sure its a fine choice
[07:42] <jared> Sometimes as a lay user it's hard to cut through the FUD
[08:07] <blahdeblah> jared: I use Firefox's password safe with a nice long master password for most things. I use a separate browser for banking.
[08:07] <blahdeblah> I refuse to bank on any mobile device. :-)
[08:08] <jared> blahdeblah: fair call :)
[08:09] <blahdeblah> And i use jpilot's password manager (GNU Keyring integration) for generating random passwords, and keeping important stuff.  It's a dead-simple X11 app that doesn't really integrate with anything else, so it's pretty standalone.
[10:32] <jared> blahdeblah: unfortunately I need something cross platform :/ But nice to know if I ever live the dream on Linux
[10:44] <blahdeblah> jared: KeePassX is probably a good choice
[10:46] <jared> blahdeblah: I'll suss that one out, it's come up a few times
[10:47] <jared> blahdeblah: storing something like that on dropbox with 2 factor auth ruin the security of it all though?
[11:00] <blahdeblah> I'm not a big fan of dropbox personally, because they keep the private keys themselves
[11:01] <blahdeblah> But as long as the file is encrypted itself, it's "safe enough"
[11:01] <jared> I'll have a play with keepassx first and see if that works.
[11:01] <jared> If I find that doesn't work I guess I'll have a play with lasspass
[11:02] <blahdeblah> I definitely prefer a local password database to a cloud-based one
[11:03] <jared> Fair call, I can put it on an SD card for the work laptop
[11:04] <jared> http://portableapps.com/apps/utilities/keepass_portable
[12:57] <ilja> Hello, would this be a place to ask a question
[13:09] <ilja> I have got a thinkpad x230t with a wacom stylus pen.
[13:09] <ilja> ubuntu 13.04 and everything has been working really good until yesterday.after installing tuxpaint-config
[13:09] <ilja> and setting tuxpaint on fullscreen, the stylus pen is totally out of wack.It seems to have a matching point on the left hand of the screen.the further I move away from the the larger the mismatch.Calibrating does not work.
[13:09] <ilja> The interesting thing is that it works perfectly in the login screen and perfectly in other user accounts.
[13:09] <ilja> So far all my internet research led nowhere. Has anyone an Idea what I could do to correct the problem?


[07:11] <tsimonq2> https://launchpad.net/ubuntu/+source/yara/3.11.0-2/+build/17974429
[07:12] <tsimonq2> What this is implying is that a source carried over from Focal -> Groovy needs an NCR if there are failed builds.
[07:12] <tsimonq2> At least, from my interpretation.
[07:12] <tsimonq2> That seems fairly peculiar.
[07:29] <mvo> hey, the snapd ppa upload fail current (https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+build/19231876) with "INFO 	Built-Using refers to source package apparmor (= 2.10.95-0ubuntu2.11), which is not known in xenial in ~snappy-dev/ubuntu/image" - any suggestions what I can do to fix this?
[07:35] <tomwardill> mvo: see the chatter in launchpad-ops
[08:05] <mvo> thanks tomwardill
[08:06] <tomwardill> I don't entirely follow it myself, just got back from PTO, but I think it's an unintended consequence of a new feature, cjwatson will know more
[08:14] <mvo> tomwardill: if it's know I will just be patient, thanks for the update
[08:58] <cjwatson> mvo: You can also drop Built-Using for now as a workaround given that this is part of implementing the feature - it didn't do anything before.  But I expect to weaken that constraint shortly until we get more details sorted out
[09:41] <mvo> ok, thank you
[10:26] <mvo> cjwatson: is there a bug I can subscribe to about the built-using issue? I'm preparing the workaround now
[10:31] <cjwatson> mvo: sorry, no, but the temporary workaround at our end is already on master
[10:31] <mvo> cjwatson: cool, I hope it's ok if I create one, then I can reference it in my workaround and once closed I revert the workaround
[10:31] <cjwatson> Sure
[10:32] <mvo> cjwatson: is there a (rough)timeline for deployment ? no rush, just curious
[10:32] <cjwatson> mvo: today
[10:32] <mvo> cjwatson: heh, nevermind then
[10:33] <mvo> cjwatson: I will just wait a bit
[10:33] <cjwatson> I just need to get it past our slightly flaky buildbot
[10:33]  * mvo nods
[13:34] <xalqor> Hi everyone
[13:35] <xalqor> I'm trying to backport postfix 3.5.1 to ubuntu 18.04
[13:35] <xalqor> I followed directions to create the package and upload it to my ppa on launchpad
[13:35] <xalqor> I got an email that the package upload was accepted into my ppa
[13:36] <xalqor> But the package list in my ppa is empty
[13:36] <xalqor> So when I do apt-get update,  even though it lists my ppa in the sources,  it doesn't see any packages there
[13:37] <rbasak> xalqor: check "View package details" on your PPA page. The package might still be building.
[13:38] <xalqor> It says there were build failures on amd64 and i386
[13:38] <xalqor> Hmm... I thought I built that on my machine before uploading?
[13:39] <xalqor> Ok I'm looking at the log, I don't actually see the issue
[13:39] <xalqor> It seems to be complaining about some dummy package "sbuild-build-depends-core-dummy"
[13:40] <xalqor> Here is the build log: https://launchpadlibrarian.net/477446139/buildlog_ubuntu-bionic-amd64.postfix_3.5.1-1~ubuntu18.04.1~ppa1_BUILDING.txt.gz
[13:40] <cjwatson> The actual error is above
[13:40] <cjwatson>  sbuild-build-depends-postfix-dummy : Depends: debhelper-compat (= 12)
[13:40] <cjwatson> That's telling you that bionic doesn't have that version of debhelper
[13:41] <cjwatson> You can reconfigure your PPA ("Edit PPA dependencies") to use the backports pocket in the primary archive, since bionic-backports happens to have debhelper 12.  Or you can backport the package to work with debhelper 11.  Your choice.
[13:42] <cjwatson> Your local test probably wasn't in a clean enough environment
[13:43] <xalqor> Ok -- I'm a total newbie at packages -- I'm setting ubuntu dependencies to backports on my ppa
[13:44] <cjwatson> The "rmadison" tool (the name is a patchwork of multiple layers of historical reasons, don't even try ...) in the devscripts package is handy for getting a quick view of which packages exist where.  "rmadison debhelper" in this case
[13:46] <xalqor> I will check that out.
[13:47] <xalqor> debhelper | 11.1.6ubuntu1               | bionic
[13:48] <xalqor> debhelper | 12ubuntu1                   | disco
[13:48] <xalqor> debhelper | 12.1.1ubuntu1~ubuntu18.04.1 | bionic-backports
[13:49] <cjwatson> The other thing that may not be obvious is that each version of debhelper declares a Provides field expressing the compatibility levels it supports
[13:49] <cjwatson> (among other things)
[13:49] <cjwatson> So for instance in focal:
[13:49] <cjwatson> $ apt-cache show debhelper | grep ^Provides
[13:49] <cjwatson> Provides: debhelper-compat (= 9), debhelper-compat (= 10), debhelper-compat (= 11), debhelper-compat (= 12), dh-sequence-dwz, dh-sequence-elf-tools, dh-sequence-installinitramfs, dh-sequence-systemd
[13:50] <cjwatson> And in the above build log, apt is saying that it couldn't find anything that was actually a package called debhelper-compat with version 12 (which we don't expect anywhere), or a package that has Provides: debhelper-compat (= 12)
[13:52] <cjwatson> In bionic it's just "Provides: debhelper-compat (= 9), debhelper-compat (= 10), debhelper-compat (= 11)"
[13:52] <xalqor> So setting the ppa dependencies to backports means that launchpad can use debhelper 12 in bionic-backports to build it
[13:53] <cjwatson> Right.  Each build gets its own /etc/apt/sources.list dispatched to it on top of a corresponding clean base image, and will only be able to see things that are available starting from that
[13:54] <xalqor> Looks like the build worked this time, but I'm still waiting for it to upload
[13:54] <xalqor> I guess from the launchpad build server to the repository
[13:55] <xalqor> https://launchpadlibrarian.net/477499548/buildlog_ubuntu-bionic-amd64.postfix_3.5.1-1~ubuntu18.04.1~ppa1_BUILDING.txt.gz
[13:55] <cjwatson> My personal preference is normally to backport to the target series' released version of debhelper instead, but that can be a more involved process and does need more experience
[13:56] <cjwatson> The upload in question is from a temporary staging area to Launchpad's database
[13:56] <cjwatson> There's then a separate publication step
[13:56] <cjwatson> But it all looks in progress now, so cup of tea time
[13:58] <xalqor> I always forget the kitchen accessories at home
[13:59] <xalqor> Thanks for the help :)
[14:03] <xalqor> I'm still not seeing it in the package list
[14:05] <xalqor> Not sure what status I should be looking for to know that it should be there
[14:08] <xalqor> Both amd64 and i386 targets are showing up as successful builds now on launchpad
[14:10] <xalqor> Ah it's showing up now
[14:10] <seb128> hey there, question of the day
[14:10] <seb128> is that a bug or am I overlooking something?
[14:11] <seb128> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802675 has a comment from today but https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802675/+activity has the most recent even in decembre?
[14:43] <wgrant> seb128: Activity tracks bug metadata changes.
[14:55] <seb128> wgrant, oh, thanks, it's not obvious from the label
[14:56] <seb128> wgrant, do you know if there is a way from the api to query who was the last person to comment on a bug?
[14:56] <wgrant> seb128: Not without iterating through bug.messages, I don't think
[15:02] <seb128> wgrant, thanks
[15:36] <xalqor> @cjwatson thanks for the help. I also had to backport init-system-helpers and now it seems to be working
[15:50] <cjwatson> Good stuff
[16:37] <cjwatson> mvo: You should no longer get that Built-Using error now
[16:40] <mvo> cjwatson: \o/ thank you!
[18:04] <RikMills> someone trip over a lead? LP seems dead
[18:04] <ijohnson> yeah I can't get to LP either :-|
[18:05] <sarnold> ilasc, btw, no notice on https://twitter.com/launchpadstatus yet
[18:06] <sarnold> ah I hadn't noticed the times in the topic..
[18:09] <RikMills> sarnold: they should change that twitter account to say, "if you are checking this account, launchpad is probably broken"
[18:09] <sarnold> lol
[18:10] <basd82> Hello is correct that lauchpad is unreachebol
[18:11] <sarnold> basd82: correct, it's currently offline
[18:11] <basd82> maintenance ? or mallfunction
[18:11] <sarnold> I'm not sure
[18:11] <ijohnson> seems a malfunction with network issues
[18:12] <pappacena> We are checking it, but it's mallfunction.
[18:12] <Eickmeyer> Wiki is down too.
[18:12] <basd82> Oke than it is not at my side , hope it fix soon i am in the middel of deployment
[18:17] <pappacena> Not on your side, basd82. It affects a few other services too (https://status.canonical.com/), and our team is working to put everyting back online.
[18:20] <RikMills> it was debian who had half their infra die yesterday. guess it is our turn ;)
[18:22] <Odd_Bloke> Guess we should have blacklisted "network-outage" so it wouldn't autosync. :p
[18:43] <basd82> where back up
[18:46] <RikMills> looks like build farm is not happy yet, but progress :)
[18:47] <pappacena> git and bzr might not be 100% fixed yet too (although I just did a successful git pull here). But we have people working on it.


[00:47] -queuebot:#ubuntu-release- New binary: hoel [arm64] (bionic-proposed/universe) [1.3.1-1] (no packageset)
[00:47] -queuebot:#ubuntu-release- New binary: multitime [arm64] (bionic-proposed/universe) [1.3-1] (no packageset)
[00:47] -queuebot:#ubuntu-release- New binary: hoel [armhf] (bionic-proposed/universe) [1.3.1-1] (no packageset)
[00:48] -queuebot:#ubuntu-release- New binary: multitime [armhf] (bionic-proposed/universe) [1.3-1] (no packageset)
[01:03] -queuebot:#ubuntu-release- New binary: hoel [ppc64el] (bionic-proposed/universe) [1.3.1-1] (no packageset)
[01:16] -queuebot:#ubuntu-release- New binary: multitime [ppc64el] (bionic-proposed/universe) [1.3-1] (no packageset)
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [amd64] (bionic-proposed) [1.3.1-1]
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [armhf] (bionic-proposed) [1.3.1-1]
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [ppc64el] (bionic-proposed) [1.3.1-1]
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [arm64] (bionic-proposed) [1.3.1-1]
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [s390x] (bionic-proposed) [1.3.1-1]
[04:08] -queuebot:#ubuntu-release- New: accepted hoel [i386] (bionic-proposed) [1.3.1-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [amd64] (bionic-proposed) [1.3-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [armhf] (bionic-proposed) [1.3-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [ppc64el] (bionic-proposed) [1.3-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [arm64] (bionic-proposed) [1.3-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [s390x] (bionic-proposed) [1.3-1]
[04:44] -queuebot:#ubuntu-release- New: accepted multitime [i386] (bionic-proposed) [1.3-1]
[04:45] -queuebot:#ubuntu-release- New: accepted gnome-tweaks [source] (bionic-proposed) [3.27.4-1ubuntu1]
[04:47] -queuebot:#ubuntu-release- New binary: gnome-tweaks [amd64] (bionic-proposed/none) [3.27.4-1ubuntu1] (no packageset)
[04:54] -queuebot:#ubuntu-release- New: accepted gnome-tweaks [amd64] (bionic-proposed) [3.27.4-1ubuntu1]
[05:51] <cpaelzer> slangasek: yes I found that as well - since <IP_ADDRESS>-2 it is good
[05:51] <cpaelzer> I'm abandoning the MP
[06:35] <tjaalton> it's already merged
[06:36] <tjaalton> or to be exact, changed so that it only affected the bad version
[06:41] <doko> tjaalton: freepa needs a bind9 merge
[06:42] <doko> freeipa even
[07:05] <tjaalton> doko: I know, the server team is on it
[07:15] <tjaalton> merging https://code.launchpad.net/~tjaalton/britney/hints-ubuntu/+merge/336803 would unblock python-ldap and then 389-ds-base
[08:17] <apw> tjaalton, what on earth is is attempting to merge that into ?
[08:17] <tjaalton> apw: huh, something silly
[08:17] <apw> are you merging it into the code perhaps
[08:17] <tjaalton> same mistake that cpaelzer did, apparently
[08:18] <tjaalton> I pulled hints-ubuntu, modified it and then pushed it to lp:tjaalton
[08:20] <cpaelzer> thanks that I'm not alone tjaalton :-)
[08:20] <tjaalton> :)
[08:20] <cpaelzer> this is the default that is selected, which is wrong :-/
[08:20] <apw> tjaalton, can you change what it is trying to merge it into, that isn't an editable for me
[08:21] <tjaalton> I'll try
[08:21] <tjaalton> No RSA host key is known for bazaar.launchpad.net and you have requested strict checking.
[08:22] <tjaalton> huh
[08:25] <apw> tjaalton, hmmm going to be one of those days is it
[08:25] <tjaalton> looks like it
[08:26] <apw> tjaalton, anyhow the diff looks fine when its not mad, merged and pushed
[08:26] <tjaalton> cool
[08:28] <apw> tjaalton, https://code.launchpad.net/~tjaalton/britney/hints-ubuntu/+merge/336815
[08:28] <apw> ok i found a button to resubmit it against the right thing i think
[08:32] <tjaalton> good, I couldn't
[10:10] -queuebot:#ubuntu-release- New source: ipxe-qemu-256k-compat (bionic-proposed/primary) [1.0.0+git-20150424.a25a16d-0ubuntu1]
[10:15] <cpaelzer> the above is for bug 1713490
[10:15] <cpaelzer> TL;DR a copy of xenial src:ipxe stripped of most but a few roms we need as compat
[10:15] <cpaelzer> I also need a MIR on this which I think I can only open once through new (to have the src on LP)
[10:16] <cpaelzer> so if one could take a look that would be great
[10:16] <cpaelzer> let me know if there is anything I still need to do to pass the new queue on this
[10:18] -queuebot:#ubuntu-release- New binary: libvirt [s390x] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[10:20] <cpaelzer> and that is libvirt splitting a few submodules (in Debian) for storage support
[10:22] -queuebot:#ubuntu-release- New binary: libvirt [ppc64el] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[10:37] -queuebot:#ubuntu-release- New binary: libvirt [arm64] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[10:43] -queuebot:#ubuntu-release- New binary: libvirt [armhf] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[11:00] -queuebot:#ubuntu-release- New binary: libvirt [amd64] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[11:05] -queuebot:#ubuntu-release- New binary: libvirt [i386] (bionic-proposed/main) [4.0.0-1ubuntu1] (ubuntu-server, virt)
[11:09] <smb> Can someone drop the artful upload of ubuntu-fan from the sru queue, please? (would like to replace it with minor packaging changes)
[11:15] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-fan [source] (artful-proposed) [0.12.9~17.10.1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [amd64] (bionic-proposed) [4.0.0-1ubuntu1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [armhf] (bionic-proposed) [4.0.0-1ubuntu1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [ppc64el] (bionic-proposed) [4.0.0-1ubuntu1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [arm64] (bionic-proposed) [4.0.0-1ubuntu1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [s390x] (bionic-proposed) [4.0.0-1ubuntu1]
[11:37] -queuebot:#ubuntu-release- New: accepted libvirt [i386] (bionic-proposed) [4.0.0-1ubuntu1]
[11:39] <cpaelzer> thanks for those accepts
[11:39] <cpaelzer> I'd be happy about an accept or discussion on New source: ipxe-qemu-256k-compat as well
[11:52] <doko> component-mismatches are not updated ...
[11:56] <cpaelzer> If one would accept src:ipxe-qemu-256k-compat I'd know one component-mismatch more than before :-P
[12:18] -queuebot:#ubuntu-release- New binary: bind9 [s390x] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[12:26] -queuebot:#ubuntu-release- New binary: bind9 [ppc64el] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[12:29] -queuebot:#ubuntu-release- New binary: bind9 [amd64] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[12:33] <ahasenack> \o/
[12:33] <ahasenack> heads up: the bind9 upload above needs python3-ply to be pulled back into main. The source and python-ply (py2 version) are in main already
[12:44] -queuebot:#ubuntu-release- New binary: bind9 [arm64] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[12:48] -queuebot:#ubuntu-release- New binary: bind9 [armhf] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[13:00] -queuebot:#ubuntu-release- New binary: bind9 [i386] (bionic-proposed/main) [1:9.11.2.P1-1ubuntu1] (core)
[13:56] -queuebot:#ubuntu-release- Unapproved: ubuntu-fan (artful-proposed/main) [0.12.8~17.10.1 => 0.12.9~17.10.1] (no packageset)
[14:01] <smb> ^so its back and waiting to be accepted
[14:16] <cpaelzer> hehe
[14:16] <cpaelzer> one more ping on ipxe-qemu-256k-compat (source) btw
[14:16] <cpaelzer> this really is a rename+strip of src:ipxe from former releases
[14:16] <cpaelzer> and I just realized it has to pass new queue to be able to file the MIR for it
[14:17] <cpaelzer> bug 1746255
[14:28] <cpaelzer> also libvirt in proposed migration puzzles me
[14:29] <cpaelzer> maybe one can help me to track why it is complaining about unsatisfieable Depends
[14:29] <cpaelzer> glusterfs-common is universe
[14:29] <cpaelzer> libvirt (most components) are in main
[14:29] <cpaelzer> but the link to gluster is a suggests (intentionally)
[14:29] <cpaelzer> libvirt-daemon => Suggests: libvirt-daemon-driver-storage-gluster
[14:29] <cpaelzer> libvirt-daemon-driver-storage-gluster_4.0.0-1ubuntu1_amd64.deb => Depends: glusterfs-common
[14:29] <cpaelzer> Seeded is only libvirt-daemon-system/libvirt-bin
[14:29] <cpaelzer> But proposed migration complains:
[14:29] <cpaelzer> libvirt-daemon-driver-storage-gluster/amd64 unsatisfiable Depends: glusterfs-common
[14:29] <cpaelzer> maybe it is not about main/universe after all and I miss something
[14:29] <cpaelzer> but on a system with the ppa of the same source all is installable with/without gluster as I thought it should be
[14:29] <cpaelzer> any hint is welcome
[14:31] <tjaalton> I'm weeding through all the python madness in bionic-proposed, and was wondering why pyasn1/-modules still hasn't migrated and update_output.txt shows that some packages should be uninstallable. well, turns out I can install python-construct but python-dfvfs complains that -construct can't be installed..
[14:32] <tjaalton> and I have a newer version installed already?!
[14:32] <tjaalton>  python-dfvfs : Depends: python-construct (>= 2.5.2) but it is not going to be installed
[14:33] <tjaalton> ahah
[14:33] <tjaalton> there's a braks
[14:33] <tjaalton> *breaks
[14:33] <tjaalton> newer dfvfs is in -proposed
[14:34] <tjaalton> just ftbfs while fine on debian
[14:51] -queuebot:#ubuntu-release- New: accepted bind9 [amd64] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[14:51] -queuebot:#ubuntu-release- New: accepted bind9 [armhf] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[14:51] -queuebot:#ubuntu-release- New: accepted bind9 [ppc64el] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[14:51] -queuebot:#ubuntu-release- New: accepted bind9 [arm64] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[14:51] -queuebot:#ubuntu-release- New: accepted bind9 [s390x] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[14:52] -queuebot:#ubuntu-release- New: accepted bind9 [i386] (bionic-proposed) [1:9.11.2.P1-1ubuntu1]
[16:18] <rbasak> cpaelzer: libvirt-daemon-driver-storage-gluster_4.0.0-1ubuntu1_amd64.deb does depend on glusterfs-common.
[16:18] <rbasak> cpaelzer: if it doesn't in the source, perhaps the build added it?
[16:18] <cpaelzer> rbasak: it does, but that is fine
[16:18] <cpaelzer> as libvirt-daemon-driver-storage-gluster_4.0.0-1ubuntu1_amd64.deb itself is only suggested
[16:21] <cpaelzer> so it should not be a component mismatch
[16:21] <cpaelzer> and also glusterfs-common is available in general (I can install it)
[16:21] <cpaelzer> oh well
[16:21] <cpaelzer> maybe it depends on a specific new version of glusterfs-common that is itself blocked by something
[16:21] <cpaelzer> I need to look in that
[16:22] <cjwatson> component-mismatches-proposed is out of date and I suspect that once it comes up to date it'll show -gluster for demotion to universe
[16:22] <rbasak>  Depends: glusterfs-common, libc6 (>= 2.4), libvirt-daemon (= 4.0.0-1ubuntu1)
[16:22] <cjwatson> I might have managed to unstick it earlier; we'll see
[16:22] <cpaelzer> ok, I'll just let it be and consider it a false positive that will be resolved
[16:22] <cpaelzer> because atm that is how it looks to me
[16:23] <cpaelzer> libvirt-daemon-driver-storage-gluster is new and should be only in universe
[16:23] <rbasak> Oh, I see. Now I think I understand the problem. Never mind, sorry.
[16:23] <cjwatson> it probably just went into main by default due to being from a source in main
[16:23] <cjwatson> don't worry about it for now
[16:23] <cpaelzer> yeah
[16:23] <cpaelzer> thanks cjwatson
[16:23] <cpaelzer> all I wanted to hear
[17:15] <cjwatson> cpaelzer: as I thought.  demoting now
[17:46] <flocculant> cpaelzer: re mouse integration - just posted to bug, but as you're here ... success with ppa and tablet - thanks very much :)
[17:48] <flocculant> nvm ...
[18:00] <slangasek> has anyone analyzed why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html says 'freeipa-server-dns/amd64 unsatisfiable Depends: bind9-dyndb-ldap (>= 11)' when bind9-dyndb-ldap 11.1-1 is now in bionic-proposed?
[18:00] <nacc> ahasenack: --^
[18:01] <ahasenack> slangasek: bind9 9.11 can't migrate because I missed a universe dependency (lmdb)
[18:01] <ahasenack> slangasek: I have https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1746296 and a branch for it, currently building in a ppa
[18:02] <ahasenack> slangasek: the other universe dependency we need a component-mismatch for, it's python3-ply. The source package (ply) is in main, as is the python-ply (py2) package it produces
[18:02] <slangasek> ahasenack: yes, but that shouldn't translate to "unsatisfiable dependency", it should only translate to "depends on bind9", which is also listed
[18:02] <nacc> yeah that's weird
[18:02] <nacc> they are both in universe
[18:02] <ahasenack> slangasek: that I haven't analyzed, i zeroed in in the lmdb dependency I missed
[18:03] <ahasenack> slangasek: >= 11 seems wrong, shouldn't it be >= 9.11?
[18:04] <ahasenack> oh, it's from another source package
[18:04] <ahasenack> n/m
[18:06] <ahasenack> excuses says "missing build": missing build on amd64: bind9-dyndb-ldap (from 10.1-2)
[18:07] <ahasenack> but 11.1-1 built: https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.1-1/
[18:07] <nacc> ahasenack: nice catch, that's presumably why
[18:18] <ahasenack> excuses is just not seeing the builds for some reason?
[18:18] <nacc> ahasenack: it might be lagging
[18:19] <ahasenack> it's built since december
[18:19] <nacc> ahasenack: then i don't know ;)
[18:19] <ahasenack> https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.1-1/ also says "no changes file available"
[18:20] <oSoMoN> hey, can the libreoffice i386 autopkgtest failure be ignored to allow 1:5.4.4-0ubuntu2 to migrate? it's the same failure that was ignored for the past few updates, because of bug #1699772 (java/kernel stack clash)
[18:21] <oSoMoN> (the good news is that someone from the kernel team is looking into it so hopefully a future kernel update will have a fix)
[18:28] <doko> oSoMoN: lo won't mirgrate until poppler, mpclib, mpfr4, gnustep-* tinyxml2, binutils gcc-* glibc migrate ... and probably other affected transitions
[18:29] <oSoMoN> okay, I'd better be patient then…
[18:30] <doko> oSoMoN: or help identifying stuff which still needs fixing?
[18:30] <oSoMoN> doko, sure, where do I start?
[18:32] <jbicha> doko: does LO 6 need to wait for all those transitions?
[18:32] <doko> oSoMoN: update_excuses and update_output, looking for library packages which won't migrate, i.e. transitions imported from debian and not done in Ubuntu
[18:32] <doko> jbicha: it needs poppler
[18:33] <jbicha> doko: yes, I mean does oSoMoN need to wait to upload LO 6 until after the poppler transition is done?
[18:33] <doko> so fixing autopkg tests which prevent migration of poppler helps
[18:33] <doko> ahh, maybe not
[18:50] <seb128> doko, oSoMoN, it was built before poppler was uploaded so it should be able to migrate no?
[18:50] <seb128> well before poppler at least
[18:51] <doko> no
[18:59] <LocutusOfBorg> apw, merge my patch please? (hints bzr repo)
[18:59] <oSoMoN> the poppler transition happened between I test-built LO in a PPA and I uploaded it, so I had to re-upload with a patch for the new poppler
[19:08] <slangasek> ahasenack, nacc: hmm, then it should still only translate into "depends on bind-dyndb-ldap", which appears to be the source package still building that binary in both bionic and bionic-proposed.
[19:09] <ahasenack> slangasek: for a moment I thought this dyndb-ldap package came from the bind9 source, specially because of the similar version (11.1 vs 9.11) that tricked my eye
[19:09] <nacc> slangasek: yeah, i agree; it feels like 'something' is in the wrong state
[19:09] <nacc> slangasek: rmadison reports the binaries are available, e.g., but excuses doesn't see them?
[19:09]  * slangasek nods
[19:10] <slangasek> so, launchpad says it's there, let's see if it's missing from the packages files
[19:11] <slangasek> it is present in the packages files
[19:12] <slangasek> so that's going to take some rooting around in britney state, sigh
[19:26] <nacc> doko: should i change the state of the libsodium bug task so it's back on the MIR list to modify for bionic?
[19:46]  * slangasek considers manually copying bind-dyndb-ldap to the release pocket to try to unblock
[19:56] <slangasek> ahahaha can't copy bind-dyndb-ldap because it depends on new bind9 sonames <facepalm>
[20:00] <slangasek> ah, but behold, now bind-dyndb-ldap is happy :P
[20:01] <slangasek> ahasenack, nacc: what's the current thinking wrt lmdb?  Is this getting dropped or MIRed?
[20:03] <ahasenack> slangasek: I'm dropping it at the moment, it's for a new tool to convert zone files
[20:04] <slangasek> ok
[20:04] <ahasenack> slangasek: https://launchpad.net/~ahasenack/+archive/ubuntu/bind9-drop-lmdb-1746296/+packages has packages I will test tomorrow
[20:04] <slangasek> ahasenack: test tomorrow> why, vs. me uploading them today?
[20:05] <ahasenack> I just want to be sure the only thing we will not have is that tool to convert the zone files
[20:05] <ahasenack> slangasek: would you like to review my branch perhaps?
[20:06] <ahasenack> slangasek: https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+ref/bind9-drop-lmdb-1746296
[20:06] <slangasek> ahasenack: that seems like something I could manage to test with debdiff before pushing, if necessary :) but also, it seems like that shouldn't block the long and messy proposed-migration dep chain right now
[20:06] <slangasek> sure, I'll look
[20:06] <slangasek> I guess it's still the case that I don't have access to land this branch anywhere?
[20:06] <ahasenack> slangasek: ok, let me do a quick install then. I moved to another task while the packages in the ppa were building
[20:07] <ahasenack> slangasek: probably, me neither. You can take over it with a debdiff if you are happy with it, I don't mind
[20:17] <slangasek> ahasenack: wow, so for some reason, I can't do a clean checkout of this repo; all of the win32 *vcxproj*.in files in the tree show up as modified
[20:18] <slangasek> ahasenack: seems to be some line feed issue, git knows that the files in the working dir don't match but refuses to fix them :P
[20:19] <ahasenack> slangasek: I just did a quick test with a feature that the CHANGES file say would be affected by using the new lmdb library, using the packages from that ppa, seems to have worked fine: https://pastebin.ubuntu.com/26491290/
[20:19] <slangasek> also, was I wrong to expect pristine-tar data on these branches?
[20:20] <ahasenack> created this file: https://pastebin.ubuntu.com/26491297/
[20:20] <ahasenack> slangasek: reading
[20:20] <slangasek> ahasenack: uploaded, thanks
[20:21] <ahasenack> slangasek: I don't know about pristine-tar. I cloned bind (using git ubuntu clone bind9), then created a new branch from ubuntu/devel, and that's what I pushed to lp
[20:21]  * slangasek nods
[20:21] <slangasek> right, so it was more a question of whether I should expect pristine-tar on the usd branches
[20:21] <slangasek> it's possible I was told before that I shouldn't, but I still do, because I'm difficult that way
[20:21] <ahasenack> nacc: ^ :)
[20:22] <ahasenack> slangasek: there will still be one component-mismatch on python3-ply, can you fix that?
[20:22] <ahasenack> python-ply, which comes from the same source ("ply"), is in main
[20:22] <slangasek> ahasenack: already done; will be fixed in next publisher run
[20:22] <ahasenack> great
[20:29] -queuebot:#ubuntu-release- New binary: rsyslog [s390x] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:32] -queuebot:#ubuntu-release- New binary: rsyslog [ppc64el] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:36] -queuebot:#ubuntu-release- New binary: rsyslog [arm64] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:37] -queuebot:#ubuntu-release- New binary: rsyslog [armhf] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:37] -queuebot:#ubuntu-release- New binary: rsyslog [i386] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:41] -queuebot:#ubuntu-release- New binary: rsyslog [amd64] (bionic-proposed/main) [8.32.0-1ubuntu1] (core)
[20:53] <slangasek> tsimonq2: so I caught in scrollback you were discussing skipping alpha2.  I haven't seen anything to the contrary, and it's Tuesday of the milestone week, so I guess this is the plan of record?
[20:56] <nacc> ahasenack: slangasek: we have per-distro pristine-tar branches
[20:56] <nacc> slangasek: let me know if that does not answer your question
[20:56] <slangasek> nacc: so why did git-buildpackage not find them?
[20:56] <slangasek> nacc: was it because I was building from ahasenack's branch instead of from one of the usd branches?
[20:56] <nacc> slangasek: gbp ivoekd directly?
[20:56] <nacc> *invoked
[20:56] <slangasek> yeah
[20:56] <nacc> slangasek: gbp can't find them
[20:57] <nacc> gbp doesn't have any concept of multiple pristine-tar
[20:57] <nacc> we wrap all that with git-ubuntu build :)
[20:57] <nacc> it's possible that's now fixed in the latest gbp, but I think it's not still -- i'll need to look
[20:57] <nacc> basically our wrapper uses a context to checkout the "right" pristine-tar branches to 'pristine-tar' and then calls gbp
[20:58] <nacc> there is a export-orig subcommand now that makes that more accessible
[20:59] <tsimonq2> slangasek: I guess it is, yes.
[20:59] <slangasek> nacc: ah ok
[22:01] <nacc> slangasek: seeing as you did it before, would it be possible for you to promote libsodium again? LP: #1621386? it's pulled up by php7.2-cli now (which is in turn going to get promoted via the seeds)
[22:11] <slangasek> nacc: needs a new team subscriber, unity-api-team should not be considered an owner for new MIRs
[22:11] <nacc> slangasek: it does already
[22:11] <nacc> slangasek: ubuntu-server subscribed to the package
[22:12] <slangasek> nacc: <refresh> oh, so they did
[22:12] <nacc> slangasek: :)
[22:13] <nacc> i also thought i had put a comment to that effect in the MIR bug
[22:13] <slangasek> nacc: you want me to read *both* sentences of the comment?
[22:13] <nacc> slangasek: it is a lot to ask :)
[22:14] <tsimonq2> "Therefore, we will need to include it in main to support Unity 8." woah we're putting Unity 8 BACK in the archive?
[22:14]  * tsimonq2 runs
[22:16] <slangasek> it's actually just a pork barrel MIR
[22:17] <slangasek> "the Server Team will formally support unity8, in exchange for you shipping nodejs in main"
[22:17] <tsimonq2> hah :)
[22:23] <nacc> lol
[22:30] <nacc> slangasek: thanks
[23:17] <juliank> oh, rsyslog landed in NEW.
[23:17] <juliank> Kind of makes sense, I guess
[23:18] <juliank> We do have new binaries after all
[23:19] <juliank> I wonder why that did not happen when lvm2-lockd was introduced, though. that was odd.
[23:19] <juliank> or maybe it did and I did not notice
[23:20] <nacc> juliank: it did, and probably was auto-accepted
[23:20] <juliank> ah
[23:20] <juliank> well, I don't care much as long as it works :)
[23:20] <nacc> (not 100%, but just a guess)
[23:20] <nacc> auto = reviewed by an AA and accepted, i mean
[23:21] <juliank> yeah
[23:23] -queuebot:#ubuntu-release- New binary: rkt [amd64] (bionic-proposed/universe) [1.29.0+dfsg-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: otb [s390x] (bionic-proposed/universe) [6.4.0+dfsg-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- New: accepted otb [s390x] (bionic-proposed) [6.4.0+dfsg-1]
[23:37] -queuebot:#ubuntu-release- New: accepted rkt [amd64] (bionic-proposed) [1.29.0+dfsg-1]
[23:37] -queuebot:#ubuntu-release- New binary: otb [ppc64el] (bionic-proposed/universe) [6.4.0+dfsg-1] (no packageset)
[23:42] -queuebot:#ubuntu-release- New: accepted otb [ppc64el] (bionic-proposed) [6.4.0+dfsg-1]