[12:50] <hggdh> @login
[12:50] <hggdh> @btlogin
[13:39] <ocean> hi, from the last call of !ops (in #u) I can see that my nick is still mentioned in the factoid - obviously I'm no longer an op :)


[15:01] <dorian_> Hey there. I hit 'bzr revert' by mistake. Some file were backed up under the file.d.~#~ convention. Some were not. Do you know if I can find the missing backup files ?
[15:02] <LeoNerd> 'revert' tries to check if the outstanding edit is due to a 'merge' or similar operation
[15:02] <LeoNerd> I.e. something that didn't involve human effort to create and can be rebuilt by applying the same operation if necessary
[15:05] <dorian_> LeoNerd, like unshelve ?
[15:05] <LeoNerd> Ah.. mmmm
[15:05] <LeoNerd> Yes that tricky little cornercase ;)
[15:05] <dorian_> are the unshelved patch stored somewhere ?
[15:05] <LeoNerd> I don't know what happens to unshelve'd changes, whether that is preserved somewhere
[15:05] <LeoNerd> Last time I looked I couldn't find one
[15:06] <dorian_> where can I find help about this ? I might have lost a day worth of work
[15:06] <dorian_> I want to make sure before starting over
[15:07] <LeoNerd> Take a look under the  .bzr/checkout/shelf directory and see if there's leftover files in there
[15:09] <dorian_> nope
[15:09] <fullermd> An unshelved change should be the same as a manual one; bzr doesn't know where it came from...
[15:09] <mgz> dorian_: pastebin the log section of the failed unshelve operation?
[15:10] <mgz> everything should generate conflicts/orig files, except when shelve breaks badly
[15:10] <dorian_> mgz, the unshelve operation didn't fail. It's the revert operation which didn't make backups
[15:12] <mgz> pastebin that then? revert always makes backups of files that actually have changes in them
[15:13] <mgz> also, it's a good habit to just make checkpoint commits in a work branch, even when experimenting
[15:13] <mgz> it's pretty easy to pull them out into neater branches later
[15:15] <dorian_> there is nothing is the log of the revert operation which is out of the ordinary
[15:15] <dorian_> the return code is fine also
[15:15] <dorian_> I hope bzr doesn't actually do the revert operation if it doesn't make backup successfully :/
[15:20] <mgz> hm, did were you discarding a pending merge at the same time?
[15:21] <mgz> I mean, I'm not sure how you have a days worth of uncommitted changes and decide to type revert, but trying to understand what actually went wrong
[15:23] <dorian_> It's ok. I resigned and accepted that my work is lost. I won't stop using bzr since it's my boss choice either -__-
[15:24] <mgz> I'd like to know what you did and help it not happen again
[15:25]  * LeoNerd (also suggests commit-early commit-often, but knows that doesn't immediately help the current problem :/ )
[15:25] <mgz> but I need an actual log to have any idea
[15:26] <dorian_> I wasn't at the latest revision. I had local changes. I hit revert
[15:26] <dorian_> no backup to be found
[15:26] <dorian_> maybe it comes from that
[15:26] <LeoNerd> Ah, for that situation I always shelve / pull / unshelve
[15:27] <LeoNerd> Treat revert as "Throw away my changes". Those "backup" files are just for accident recovery
[15:27] <dorian_> thanks for you help anyway
[15:29] <mgz> hm, I still get a backup file in that case.
[23:35] <jvelasquez> how could I see a list of everything managed by bzr?
[23:37] <jvelasquez> got it.  bzr ls -V
[23:37] <fullermd> You may want -R too, depending on the meaning of "everything".
[23:38] <jvelasquez> ohh. yea! thanks.


[01:57] <natefinch> rick_h_: I don't suppose you're actually online?
[10:41] <schkovich> hi guys! where could i find more information on state-port and syslog-port? im setting firewall on juju state-server. a bit more understanding on services exposed on those two ports would be helpful.
[11:04] <schkovich> x248aGent£
[12:51] <stub> Design question. A client charm is related to the PostgreSQL charm, and needs to use a PostgreSQL extension. eg. it needs to tell the unit to install a package from a PPA.
[12:52] <stub> Should the client charm be allowed to instruct the PostgreSQL charm to add the PPA and install the package? Or do I need to also have a subordinate charm that does the package installation?
[12:53] <stub> subordinate seems messy (although trivial, as it would be a 3 line install hook and a pile of boilerplate to keep charm-proof happy)
[12:54] <stub> But allowing a client service to instruct the db to install arbitrary packages from arbitrary locations? That seems a security problem.
[12:55] <stub> Well, the third option is to have the operator specify the ppa and package to install in the PostgreSQL service's config. I'm guessing that is the best option.
[12:56] <stub> (and I can now block the client until the operator has actually done it)
[13:33] <lazyPower> cory_fu: ping
[13:33] <cory_fu> Hey
[13:33] <lazyPower> greetings, can you join me in#juju-gui for a minute? Frankban is asking about some specifics w/ SF that i'm not familiar with
[13:40] <marcoceppi> lazyPower: tell him to join us over here ;)
[15:57] <schkovich> is there a way to setup to which interface on machine n juju ssh n will be connect eg configure ssh proxy on the state server?
[16:12] <lamont> I have a subordinate-charm question, which I suppose I could just code up and see, but it's not clear from the docs..
[16:13] <lamont> if I have subordinate charms A and B, and A needs some info from B, is there a relation there?
[16:17] <marcoceppi> lamont: both are subordinates?
[16:18] <marcoceppi> presumably attached to the same primary?
[16:18] <lazyPower> lamont: you can write a relationship that will allow them to exchange data, but you cannot deploy a subordinate to a subordinate.
[16:18] <lamont> yes, same primary, both subord
[16:19] <lamont> lazyPower: so I need to create a relationship for them to share info, just like they're real charms and everything. (DOH)
[16:19] <lamont> that would go a long way to explaining WHY THE CHARM ISN'T DOING WHAT THE AUTHOR THOUGHT
[16:19] <lazyPower> lamont: correct - adding a relationship/interface to do that data-exchange should be teh asme process as any other charm :)
[16:20] <lazyPower> lamont: can i ask what you're trying to do so i have more context?
[16:20] <lamont> hp-health thinks it's getting data from nrpe-external-master
[16:20] <lamont> and it's all lies
[16:20] <lamont> (it shows up as blank hostnames in the nagios files that are exported)
[16:21] <lazyPower> thats fun
[16:21] <lamont> I can see we're going to need to work on your understanding of the definition of "fun" :p
[16:21] <lazyPower> yeah if you need to proxy information through - i ran into this w/ the docker/flannel-docker stuff
[16:21] <lazyPower> i'm using flannel-docker to proxy info directly to docker (docker manages the docker config - no exceptions) - so teh subordinate is acting as an informatoin proxy and a payload delivery mechanism
[16:22] <lazyPower> the mechanics are a bit alien at first glance
[16:23] <lazyPower> it sounds like you have some of the same requirements for behavior in this particular setup
[16:28] <lamont> hrm... and which is the primary charm there?
[16:29] <lamont> properly, the main charm could proxy the nagios hostname from n-e-m and just populate it into all the other subordinate relations
[16:29] <lamont> or n-e-m could write it to a file :D
[16:29] <lamont> even though that feels wrong
[16:30] <lamont> n-e-m needs a good rewrite from scratch
[16:30] <lazyPower> lamont: thats highly dependent on context, and which is the manager of the concerns
[16:30] <lazyPower> http://blog.dasroot.net/2015-charm-encapsulation.html
[16:35]  * lamont will do some reading
[16:43] <lamont> and, of course, lp:charms/trusty/nrpe is the perfect place to begin this quest
[16:55] <tvansteenburgh> jw4: you around?
[16:56] <jw4> tvansteenburgh: yes, but OTP for a bit
[16:56] <jw4> tvansteenburgh: feel free to ask and I'll try to multitask :)
[16:58] <tvansteenburgh> jw4: afaict, the Action.ListAll api does not return info about actions run on subordinates
[16:59] <tvansteenburgh> jw4: wanted to check with you before filing a bug
[17:02] <tvansteenburgh> jw4: subordinate actions also don't seem to send any updates to the AllWatcher
[17:07] <jw4> tvansteenburgh: hmm - I don't know of a specific concept of subordinate actions, but I assume you mean actions on subordinate units?
[17:08] <tvansteenburgh> jw4: yes
[17:08] <rick_h_> natefinch: heads up I'm around now if you still need anything
[17:08] <jw4> tvansteenburgh: actions and the actions watcher don't know about subordinates, so if you query actions on a unit it doesn't know to look for subordinates
[17:09] <jw4> tvansteenburgh: seems like a viable candidate for a bug report
[17:09] <natefinch> rick_h_: was wondering why there's no link to the juju blog on the top of jujucharms.com
[17:09] <natefinch> rick_h_: most of core didn't even know there was a blog
[17:09] <tvansteenburgh> jw4: thanks for confirmation, will file bug
[17:09] <rick_h_> natefinch: because the blog isn't updated/big enuogh to warrant a link at the top :) and the homepage/community shows recent posts
[17:09] <jw4> tvansteenburgh: cool
[17:10] <rick_h_> "Latest from the blog"
[17:10] <natefinch> rick_h_: fair enough. It looks like it's all external posts... do we have the ability to have our own posts hosted on jujucharms.com?
[17:11] <rick_h_> natefinch: so this is from the aggregator with things tagged juju I thought? /me dbl check. https://jujucharms.com/community/blog
[17:11] <rick_h_> natefinch: you'd have to check with the web team where/how the aggregation is pulled in.
[17:11] <natefinch> rick_h_: ok, thanks
[17:16] <natefinch> gah, I hate exceptions
[18:03] <lazyPower> wwitzel3: hey have you ever seen this happen before?
[18:03] <lazyPower> http://i.imgur.com/7CGtl8k.png
[18:03] <lazyPower> wwitzel3: it appears I managed to trap 2 executing hooks at the same time
[18:39] <bac> tvansteenburgh: ping
[18:41] <tvansteenburgh> bac: pong
[20:17] <lamont> what does relation-ids want for an argument?  interface name?
[20:18] <lamont> yeah.  relation-name
[20:18]  * lamont goes back to headscratching
[20:31] <tvansteenburgh> jw4: fyi https://bugs.launchpad.net/juju-core/+bug/1457205
[20:31] <mup> Bug #1457205: Subordinate charm Action data not reported by API <juju-core:New> <https://launchpad.net/bugs/1457205>
[20:31] <jw4> thanks tvansteenburgh


[16:24] <andresmujica> hi,  i'm affected by the bug 400962 and i'm wondering if it's a known problem with openjdk ?


[03:05] <nabn> i'm currently running 15.04 ubuntu-gnome. Should I be worried things will break if i do a release-upgrade?
[05:48] <chris_> Hey guys, I think I found a bug. Where can I file a report?
[12:27] <LinDol_phone> hi all
[12:28] <LinDol_phone> i am going to Suwon in korea ~.~
[12:29] <LinDol_phone> because i went my hometown for meeting my family~.~
[17:06] <tester55> hello, is there a way to remove items from Gnome's Frequent Apps list? I am using gnome shell 3.16.3.
[21:44] <darkxst> eliasps, hi
[21:48] <eliasps> Hi darkxst
[21:48] <eliasps> How are you?
[21:49] <eliasps> I'm sorry for the large e-mail traffic, still learning :P
[21:53] <darkxst> eliasps, I'm good
[21:54] <darkxst> had a big weekend snowboarding ;)
[21:55] <eliasps> That's awesome. I tried my luck with sports like that, free falling. Too exciting. :p
[22:00] <eliasps> Got the PPA version of the package with chdist. I was sure I had run an update. But it's ok now!
[22:00] <eliasps> I'm gonna try and update another package now.
[22:20] <eliasps> darkxst I'm updating gnome-online-accounts. I tag it as ~wily2, right? Cause the one in the ppa (3.17.x) was ~wily1.
[22:21] <darkxst> eliasps, no, leave that package, it will be a hard one
[22:21] <eliasps> It has no differences in dependencies. Are there extra steps for it?
[22:22] <eliasps> But ok, I'll leave it.
[22:22] <AndChat-189569> good morning :)
[22:22] <eliasps> I guess the hardest ones are the most essential. gnome-control-center and relatives,shell, gedit and stuff, right?
[22:23] <darkxst> but yes its tag would be ~wily2
[22:23] <eliasps> AndChat-189569 hi
[22:23] <darkxst> g-o-a introduced google drive integration, which needs gvfs update
[22:23] <eliasps> I see.
[22:26] <eliasps> So for that one to be built, needs extra steps before the build itself? on the source code?
[22:30] <darkxst> eliasps, it may do, haven't checked
[22:31] <eliasps> I tried to build it, status says "Attempted", so failed. I won't mess with that one.
[22:53] <eliasps> gnome-logs have some issues with a patch.
[23:01] <darkxst> eliasps, then you need to rebase them using quilt probably
[23:03] <darkxst> eliasps, but read the ubuntu changelog first ;)
[23:04] <eliasps> I'm reading the changelog. Some change I saw is that libsystemd is required. the control.in has libsystemd-dev
[23:09] <darkxst> that patch was cherry-picked from git
[23:12] <eliasps> I'm sorry, I don't know what that means.
[23:13] <darkxst> it was an upstream patch, that was needed but not included in the last release
[23:13] <darkxst> try quilt push -f
[23:14] <darkxst> and read the output
[23:14] <eliasps> I did that, it said ignored (Red font).
[23:16] <darkxst> Reversed (or previously applied) patch detected!
[23:17] <eliasps> So you don't need to apply it with quilt for the package to be built successfully?
[23:19] <darkxst> it is included in the new release, so you can just drop it
[23:20] <eliasps> darkxst Polari 3.18 seems to be built successfully, do I send you the polari_3.18.0-0ubuntu1~wily0.debdiff file only?
[23:20] <eliasps> Oh I see, thank you!
[23:20] <darkxst> eliasps, yes, just pastebin it and link here
[23:22] <eliasps> darkxst http://paste.ubuntu.com/12606483/
[23:22] <eliasps> just that?
[23:27] <eliasps> should i also build the 3.16.1 version (from debian) for the gnome3 ppa?
[23:27] <eliasps> No, it's on the main
[23:27] <eliasps> OK.
[23:41] <darkxst> eliasps, yes, uploaded, but don't use ubuntu pastebin in the future, its a pain
[23:41] <darkxst> (forces login just to get raw  text of the paste)
[23:42] <eliasps> darkxst I can upload the files as they are in http://people.ubuntu.com/~eliasps/gnome3/ if you prefer
[23:43] <darkxst> eliasps, pastes are fine, but use pastebin.com or any other paste service that does not require login
[23:46] <eliasps> Ok!


[00:26] <slangasek> doko_: I'll go ahead and upload it
[00:28] <geofft> Hi folks. Almost any use of LD_AUDIT on amd64 on Precise/Quantal causes a segfault due to a bug in libc6 that's been fixed upstream
[00:28] <geofft> The patch is fairly tiny (it just checks for null, mostly). Is it reasonable to expect an SRU for this?
[00:28] <geofft> This bug makes latrace, for instance, completely useless
[00:28] <infinity> geofft: Is there a bug filed?  With a pointer to the upstream fix?
[00:29] <infinity> geofft: Expecting an SRU for something I haven't heard of until today is probably wishful thinking.  But I can certainly include it in my next SRU round if I know about it.
[00:29] <geofft> Not yet. Just wanted to check it was worth doing so, or whether libc6 is too scary to be worth doing non-security SRUs for
[00:29] <geofft> inifinity: Yeah, I'm totally happy to file a bug then describing it. Thanks!
[00:29] <sarnold> hey geofft :)
[00:30] <geofft> Oh, bad phrasing on my part, "expect" = "expect that a bug will be useful", not "expect it'll automatically get fixed"
[00:30] <geofft> hi sarnold!
[00:30] <infinity> geofft: File a bug and point me to it.  I do SRU glibc occasionally, as you can spot from the changelog.
[00:31] <infinity> geofft: I won't SRU *just* for minor bugs like that, but if there are some easy cherrypicks I can do to make pepole happy at the same time as fixing more serious bugs, I'll do it.
[00:31] <geofft> Do you want the standard SRU format [Impact] etc.?
[00:31] <slangasek> yes :)
[00:31] <infinity> geofft: If you're willing to do the full SRU template, go nuts.  Saves me the effort.
[00:41] <slangasek> doko_: well, or I would upload it, except it doesn't pass its test suite
[00:41] <slangasek> which is puzzling, because the error is obvious, the test is looking for a file in the build dir that it needs to look for in the source dir
[00:48] <slangasek> doko_: the tests are broken with glib2.0 (>= 2.37.2), there's some goofy g_test_get_filename() function here that doesn't work.
[00:50] <slangasek> which relies on setting G_TEST_SRCDIR, which nothing does.
[01:01] <geofft> infinity: Filed LP #1243473. Let me know if you need more detail.
[01:01] <geofft> Relatedly, LD_AUDIT is the awesomest thing ever, and latrace is like ltrace that actually works. (Well, modulo that bug.)
[01:03] <em> what kernel is the latest ubuntu using?
[01:07] <sarnold> em: saucy's kernel version in the package name is 3.11.0-12.19
[01:09] <sarnold> em: "Ubuntu 13.10 includes the 3.11.0-12.19 Ubuntu Linux kernel which was based on the v3.11.3 upstream Linux kernel. " https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes
[01:10] <infinity> geofft: That should be enough, thanks.
[01:11] <sarnold> geofft: cool, thanks for the fun new tool recommendation :)
[01:14] <slangasek> doko_: ok, pango1.0 uploaded finally
[01:49] <Logan_> doko_: Are you around?
[01:50] <Logan_> Or cjwatson?
[01:50] <infinity> Logan_: Just ask your question...
[01:51] <Logan_> Bleh, okay. Thought it merited their specific attention for specific reasons. :P Is 14.04 deriving from unstable or testing? Because doko_'s email says that syncs are running from unstable.
[01:51] <Logan_> But I thought LTS releases derive from testing.
[01:52] <infinity> It's from unstable.  Now that we have proposed-migration, syncing from testing doesn't buy us much, and tends to just slow us down.
[01:52] <Logan_> Alright, cool. https://wiki.ubuntu.com/LTS should be updated, then.
[01:52] <Logan_> Why is ubuntu-dev-tools's syncpackage script defaulting to syncing from testing, then?
[01:53] <infinity> Because someone didn't get the memo, I suspect.
[01:53] <infinity> I'll fix that.
[01:55] <Logan_> It doesn't seem that it was specifically set to that for trusty. I wonder if there's a config in there for every x releases deriving from testing.
[01:55] <infinity>             if ubu_info.is_lts(ubu_info.devel()):
[01:55] <infinity>                 dist = 'testing'
[01:55] <infinity> That bit just needs to go away.
[01:55] <Logan_> Oh, yup.
[01:56] <Logan_> Want me to file a bug, or are you going to handle it?
[01:57] <infinity> I'll fix it right now.  But for now, you can just use '-d unstable'
[02:01] <infinity> Oh, xnox already fixed it.  Which is why I can't find the bits in bzr. :P
[02:02] <infinity> Logan_: It's correct in bzr, it's just not been uploaded yet.  I assume bdrung will get around to pushing it to Debian and syncing soon.
[02:03] <Logan_> Okay, awesome. Thanks for your help, Adam!
[02:03] <infinity> Or maybe I'll upload it to Debian now, so more people don't end up confused.
[02:03] <infinity> bdrung: Were you planning an ubuntu-dev-tools upload to sid?  Mind if I do one?
[02:04] <Logan_> You might cause a conflict! :P
[05:18] <Noskcaj> Is it ok to merge stuff from unstable now, due to proposed-migration?
[05:41] <sarnold> Noskcaj: yes, that was discussed a few hours ago, and syncing from unstable is now the new desired state
[05:41] <Noskcaj> sarnold: ok, thanks for the info.
[05:41] <sarnold> Noskcaj: ubuntu-dev-tools's syncpackage script has apparently been fixed in bzr already, just not re-packaged yet
[05:42] <pitti> Good morning
[05:43] <sarnold> morning pitti :)
[05:43] <ScottK> Noskcaj: Unless someone is known to be inactive, up until DIF you should check with the last person to touch a merge before doing it.
[05:43] <ScottK> pitti: Your upower patch worked great.  I look forward to testing the SRU when it's ready.
[05:43] <ScottK> Thanks.
[05:43] <pitti> ScottK: nice; I'll prepare one today then
[05:43] <sarnold> ScottK: DIF?
[05:43] <ScottK> Debian Import Freeze.
[05:44] <sarnold> thanks :)
[05:46] <pitti> doko_: there's also a bug for it, debian bug 724842
[05:46] <Noskcaj> ScottK: don't worry, i have asked myself ;)
[06:15] <Noskcaj> smb: Do you plan to upload a newer dahdi-linux any time soon?
[06:16] <Noskcaj> pitti: bug 1079605
[06:16] <pitti> doko_: fixed cracklib uploaded to Debian, will autosync
[06:16] <pitti> Noskcaj: yeah, infinity wanted to have a look at some point, but I guess he was busy
[06:18] <Noskcaj> ok, thanks for the info
[06:18] <pitti> Noskcaj: we have a quite a large delta, and some of it is hopefully not required any more, etc.
[06:18] <pitti> Noskcaj: so if you feel like looking into it and making a first assessment of our delta, please feel free :)
[06:19] <Noskcaj> pitti: I would have no idea where to start
[06:19] <pitti> Noskcaj: ah, that's fine; I thought you asked because you considered doing the merge
[06:20] <Noskcaj> Not for something that big, i was just checking that it hadn't been forgotten
[06:22] <Noskcaj> That said, if anyone has merges for me to do, i've finished with all the packages that are in my name
[06:25] <pitti> Noskcaj: if you want to steal some of mine, I'd be in your debt :) (but perhaps avoid aptdaemon)
[06:49] <pitti> ScottK: upower SRU uploaded and bug updated for SRU, FYI
[06:52] <geofft> Agh, I'm confused about multiarch. Why do libc6-i386 and libc6:i386 both exist?
[06:53] <slangasek> geofft: libc6:i386 is just the native build of libc6 for i386.  libc6-i386 is a "biarch" (or "multilib") build of libc6, packaged for amd64, because some things aren't yet solved using multiarch
[06:53] <slangasek> like, the compiler itself
[06:55] <geofft> So I legitimately need both? OK
[06:56] <slangasek> you legitimately need both if you have packages installed that depend on each :)
[07:05] <Noskcaj> My requestsync keeps breaking, so would someone mind syncing visp and osgearth?
[07:10] <bkerensa> software-properties-gtk seems to be epic broken in trusty
[07:10] <bkerensa> its crashing pretty rapidly
[07:11] <Noskcaj> bkerensa: It didn't open for me last time i tried
[07:11] <bkerensa> Noskcaj: exactly it didnt open and whoopsie dialog popped up
[07:12] <bkerensa> a quick look in syslog now shows a line a second of software-properties-gtk crashing and whoopsie sporadically trying to report it
[07:12] <bkerensa> looks like there is not software-properties-gtk candidate for trusty either
[07:12] <bkerensa> aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/trusty
[07:12] <bkerensa> thats the issue
[07:14] <Noskcaj> pitti: I've merged gpgme1.0 for you, have you got time to review the branch?
[07:14] <pitti> Noskcaj: sure
[07:15] <Noskcaj> plus you should be safe to sync visp
[07:15] <Noskcaj> https://code.launchpad.net/~noskcaj/ubuntu/trusty/gpgme1.0/1.4.3/+merge/192293
[07:15] <Noskcaj> I'll try and work on psqlodbc now
[07:18] <pitti> Noskcaj: oh, did the DD take the autopkgtest fix?
[07:19] <pitti> Noskcaj: ah no, visp needs a merge
[07:19] <Noskcaj> pitti: Looks like it from the changelog
[07:19] <pitti> Noskcaj: plus, it never built on i386 for us due to a test failure
[07:20] <cjwatson> what entry in the Debian visp changelog suggests that they took our change?
[07:20] <pitti> Noskcaj: nope, I filed debian bug 726983 much later
[07:21] <cjwatson> even a cursory debdiff makes it clear they didn't.  Please put more effort into verification or else don't request syncs
[07:21] <cjwatson> otherwise you're throwing away other developers' work
[07:21] <Noskcaj> crap, i was looking at a different package as well, i am sorry for wasting yourtime
[07:25] <pitti> Noskcaj: gpgme uploaded, thanks
[07:26] <bkerensa> Noskcaj: I found the problem its python-apt well slangasek found it :) but I am going to fix it
[07:26] <Noskcaj> thanks bkerensa
[07:26] <Noskcaj> pitti: no problem, i shouldn't have copy/pasted the chagelog though
[07:27] <pitti> Noskcaj: oh, copy&pasting them is fine in general (everyone does that anyway), it just sometimes needs some trimming for the slightly different context
[07:31] <Noskcaj> pitti: gpgme is FTNFSing, give me a minute to disable the bad (gnupg2) test
[07:31] <Noskcaj> *FTBFS
[07:48] <pitti> Laney: can you please add an autopkgtest override for bzr-builddeb? This has never worked, and is now blocking python-apt from propagating (new version fixes a lot of things due to the added trusty template)
[07:48] <pitti> bkerensa: ^ FYI
[07:49] <bkerensa> :D
[08:06] <Noskcaj> pitti: It might be better if you fix the ftbfs for gpgme1.0 since my only fix is disable dh_auto_test (which fully works)
[08:07] <Laney> pitti: okay, but "never worked"> someone should look into that, of course
[08:07] <pitti> Laney: yes, of course; but it shouldn't block the propagation
[08:07] <pitti> Laney: once the sync/build/binNEW rush settles down a bit, I'm planning to go through/fix/poke people all of the failures
[08:08] <Laney> well, it's correct that it does as that is how the integration is specified
[08:09] <Laney> https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-bzr-builddeb/
[08:09] <Laney> why can't I see the details in the jobs?
[08:09] <Laney> can in trusty
[08:11] <pitti> Laney: right, but bzr-builddeb was failing in saucy, and it's not the new python-apt which breaks bzr-builddeb
[08:12] <pitti> Laney: hm, I don't know why the later saucy builds are broken in that way
[08:18] <Noskcaj> cody-somerville: Do you plan to keep maintaining catfish in debian?
[08:18] <Noskcaj> If so, it really needs an upload. if not, please file a wnpp bug
[08:18] <didrocks> pitti: ah, bzr-builddeb was already failing?
[08:19] <didrocks> we don't have that traced, I was trying to reproduce… (but can't on my installed saucy machine)
[08:19] <didrocks> and yeah, python-apt doesn't change a thing tried
[08:20] <didrocks> Laney: pitti: I was tracking it as this is one of the last piece blocking us to resume releasing things to trusty
[08:20] <didrocks> (we can't run the tests as add-apt-repository is failing as we don't have latest python-apt)
[08:20] <bkerensa> Has trusty patch pilots officially kicked off yet?
[08:20] <pitti> didrocks: you mean bzr-builddeb or p-apt?
[08:20] <pitti> didrocks: ah, so p-a
[08:21] <didrocks> yeah, p-a
[08:22] <bdrung> infinity: i can do the upload now. do you want to add yourself and do the upload to unstable?
[08:31] <Laney> I added the force-badtest
[08:32] <Laney> but I don't think I'm a fan of "it wasn't me that broke the tests, so let's ignore them"
[08:32] <Laney> We should have noticed when they started failing in saucy and fixed it then
[08:32] <Laney> Not that I can actually reproduce the failure under run-adt-test :(
[08:53] <pitti> no? I can
[08:54] <Laney> I got it in a plain chroot
[08:54] <Laney> missing python-distro-info test-dep but then there's one more failure
[08:59] <ogra_> pitti, Laney i guess bug 1243573 is for one of you :)
[08:59] <Laney> Ubuntu Touch touchy
[08:59]  * Laney blinks
[08:59] <ogra_> haha
[09:04] <pitti> bug in our "synced" system-image writable-files mode?
[09:05] <ogra_> pitti, probably, i didnt research it, there were so many errors with that upgrade
[09:06] <ogra_> (apps all vanished, system-image-cli didnt allow me to switch channels etc)
[09:07] <pitti> ogra_: (followed up to the bug)
[09:08] <ogra_> thx
[09:08] <bdrung> where to report recipe build failures to (that are caused by the build infrastructure)?
[09:08]  * ogra_ guesses against launchpad
[09:09] <cjwatson> bdrung: launchpad-buildd
[09:09] <bdrung> thanks
[09:09] <cjwatson> bdrung: but check the existing reports, there are a few standard ones in there that are blocked on host upgrades
[09:10] <Laney> ogra_: I think the upgrade wiped out more than it should have
[09:10] <Laney> I lost my accountsservice settings too
[09:10] <ogra_> my U1 account stayed
[09:10] <Laney> e.g. greeter background and it showed me the first run tutorial
[09:10] <ogra_> and my wallpaper too
[09:11] <ogra_> same for language
[09:11] <Laney> I said greeter backgroudn on purpose
[09:11] <Laney> the unity background stayed, and that is in gsettings
[09:11] <ogra_> all apps were gone for me ...
[09:11] <Laney> also had a new SSH host key, but I can't remember if that's expected when using phablet-flash
[09:13] <popey> Laney: you lost data when going from saucy to trusty?
[09:14] <Laney> my home directory is intact
[09:14] <bdrung> cjwatson: i found the bug already reported: it is bug #1089615
[09:15] <ogra_> popey, i lost all apps here, data stayed
[09:15] <popey> hmm
[09:15] <ogra_> (i didnt have to newly log in to G+ but had to reinstall the app)
[09:37] <Laney> pitti: argh, finally got it
[09:38] <Laney> If you don't have libalgorithm-merge-perl installed then dpkg-mergechangelogs generates conflicts in some situations when it doesn't if you have it installed
[09:38] <Laney> One of which is in the bzr-builddeb testsuite
[09:39] <Laney> It's a Recommends of dpkg-dev
[09:39] <pitti> Laney: ah, so somehow libalgorithm-merge-perl made it into my VM test, but not into your's?
[09:40] <Laney> I must have had both python-distro-info and libalgorithm-merge-perl installed for the tests to succeed, but the jenkins VMs didn't
[09:41] <Laney> so there's a difference somewhere between run-adt-test and those
[09:41] <pitti> so they need to become test deps?
[09:41] <Laney> in terms of dep installation
[09:41] <Laney> and that, yes (well, I'm not sure if libalgorithm should actually be a real dep?)
[09:42] <Laney> It's an implementation detail of dpkg-dev, but bzr-builddeb relies on calling that program to merge changelogs
[09:44] <pitti> ah, so that's what one would need to uninstall to get back the old conflict markers
[09:45] <Laney> old ones?
[09:45] <pitti> I find that automatic changelog merging often sorts wrongly, and it's much less obvious what it damaged
[09:45] <Laney> you mean within one entry?
[09:46] <pitti> no, I mean it mis-sorts the older ubuntu entries in between the debian ones
[09:47] <cjwatson> I often let it merge but then use "bzr shelve --destroy" to throw away the mis-sorting / other changes
[09:47] <pitti> (often, anyway)
[09:47] <cjwatson> particularly for changelogs in very old packages that contain misformatted junk at the bottom but I don't think it makes sense to reformat that in an Ubuntu delta
[09:47] <pitti> but then again, it's been a while since I actually used bzr for merging, so maybe that got fixed
[09:49] <Laney> Oh, well the testsuite allegedly checks for that
[09:49] <Laney> Anyway, I'll just add them as test-deps I think
[09:57] <cjwatson> pitti: FYI I rejected entangle as it was mistakenly uploaded to saucy.  Not sure whether you get notified as the sponsor
[09:58] <alexbligh> Is there a way to make specific files in a .deb that are in /etc **NOT** conffiles?  I don't want to delete the directory on package removal or I'll lose the user's stuff (so I don't really want to symlink out of /etc). However, I do want the individual files the pack
[09:58] <alexbligh> age installed to be removed (because the new version tends to install other files with slightly different names). What's the best way to do this?
[09:58] <pitti> cjwatson: argh, thanks; autofingers still need readjustment..
[09:58] <pitti> cjwatson: reuploaded to trusty
[09:58] <cjwatson> alexbligh: Use dpkg-maintscript-helper's tools to manage the upgrade changes
[09:59] <cjwatson> alexbligh: And keep them as conffiles
[09:59] <pitti> cjwatson: yes, I got a rejection mail
[09:59] <alexbligh> cjwatson, are they on Lucid?
[09:59] <cjwatson> alexbligh: (note that you can use debian/foo.maintscript to make this fairly easy; see dh_installdeb(1))
[09:59] <cjwatson> alexbligh: It would be quicker for you to check than me, if you have a setup
[09:59] <alexbligh> cjwatson, thanks, will do.
[10:00] <cjwatson> alexbligh: But apparently not; on lucid the correct thing to do is to simulate the same actions by hand in maintainer scripts
[10:00] <cjwatson> (carefully)
[10:01] <alexbligh> cjwatson, complete brainfart here, target is Precise these days. Not enough tea.
[10:01] <cjwatson> precise has dpkg-maintscript-helper so it's all much easier
[10:01] <cjwatson> https://wiki.debian.org/DpkgConffileHandling if you need to backport to earlier releases
[10:03] <alexbligh> cjwatson, thanks once more
[10:06] <shadeslayer> tseliot: ping
[10:06] <mardy> didrocks: hi! Any idea why this is failing? https://code.launchpad.net/~mardy/signon/packaging/+merge/190911
[10:07] <shadeslayer> tseliot: I was looking at https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1224098 and preinst.in seems a bit weird to me, line 19-20
[10:07] <shadeslayer> -s returns true if the file exists and size is greater than zero, but then there's a ! before it ... why?
[10:09] <didrocks> mardy: reusty is not there yet, we are working on it
[10:11] <tseliot> shadeslayer: let me have a look
[10:11] <shadeslayer> ack
[10:16] <tseliot> shadeslayer: it's obvious a bug (some leftover I assume)
[10:16] <tseliot> *obviously
[10:16] <shadeslayer> ack :)
[10:16] <shadeslayer> tseliot: want to sponsor a upload ? :D
[10:17] <shadeslayer> also, shouldn't checking -s suffice?
[10:18] <tseliot> shadeslayer: I'll request an SRU for precise and saucy and upload. I'll need some help testing the fix (so that the SRU team can approve it)
[10:18] <tseliot> yep
[10:18] <tseliot> that's why I said "leftover"
[10:18] <shadeslayer> roger roger
[10:19]  * shadeslayer goes back to looking at bugs
[10:20] <infinity> pitti: I'll be doing a bi-directional merge of initramfs-tools in the next week or two.  It's high on my list.
[10:21] <pitti> infinity: ah, you can do changes in Debian, too? convenient
[10:21] <infinity> bdrung: I did a bzr snapshot upload of ubuntu-dev-tools to Ubuntu, but whenever you do the Debian upload, you can just sync over that.
[10:21] <infinity> pitti: I should hope I can, I've been upstream for it since it was written.
[10:21] <bdrung> infinity: okay, i will do the debian upload now. do you want to SRU that fix to saucy?
[10:22] <infinity> (Granted, not a very active upstream since maks took over)
[10:22] <infinity> bdrung: I'm not terribly picky about SRUing it back, since I run the devel release, but if you want to push it back to saucy and maybe precise, go nuts.
[10:28]  * pitti sets up trusty LP apport retracers
[11:05] <tseliot> shadeslayer: are you available to test a package locally?
[11:06] <shadeslayer> tseliot: not the nvidia-prime one :P
[11:06] <shadeslayer> because I don't have a nvidia card
[11:06] <shadeslayer> I just noticed the bug in another channel, and decided to investigate
[11:06] <tseliot> shadeslayer: oh, never mind then
[11:46] <mdeslaur> infinity: how did you fix mysql on arm64?
[11:46] <cjwatson> mdeslaur: was it an ICE or similar?
[11:47] <mdeslaur> cjwatson: yeah
[11:47] <cjwatson> mdeslaur: some of the builders have reliability issues; looks like he gave it back on birch, which is the best of them
[11:48] <mdeslaur> cjwatson: ah, cool. good to know, thanks
[11:48]  * mdeslaur gives birch a cookie
[11:48] <cjwatson> (birch has heat issues or something else that means we sometimes have to power it down for a bit, but it at least doesn't have random segfaults ...)
[11:49] <mdeslaur> cjwatson: what kind of hardware are they?
[11:50] <cjwatson> can't answer here just yet I'm afraid
[12:41] <cjwatson> OK, I think the remaining bits of the Perl 5.18 transition (aside from waiting for builds and a few more no-change uploads) are (a) libdr-tarantool/i386 FTBFS (b) gdal FTBFS (c) libmongodb-perl FTBFS
[12:54] <ScottK> pitti: upower SRU verified.  Thanks again for the quick turnaround.
[12:54] <pitti> ScottK: nice, thanks
[17:38] <ScottK> cjwatson: Just to double check before I accept this, you're OK with a grub2 SRU to fix the Kubuntu UEFI problem, right?  http://launchpadlibrarian.net/154805913/grub2_2.00-19ubuntu2_2.00-19ubuntu2.1.diff.gz
[17:41] <slangasek> are Kubuntu the only ones setting GRUB_DISTRIBUTOR?
[17:44] <ScottK> slangasek: I think Studio might have done so too,  but (and I didn't follow the details) there's some partial Kubuntu specific support for this already, so it's an easy fix, but for other flavors it'd be more complex.
[17:44] <slangasek> mmk
[17:45] <ScottK> I know Colin discussed it with shadeslayer  and apachelogger  before fixing in trusty, but (IIRC) he said the Kubuntu team needed to do the SRU.
[18:14] <gdos> !bug 1243839
[18:16] <gdos> !bug 1243859
[18:40] <doko> barry, any update on the component mismatches?  from my side we should make sure that both pypy and python-cffi build on arm64 before promoting it
[18:42] <barry> doko: i agree with that.  i haven't done anything on it yet.  maybe tomorrow
[20:07] <slangasek> bah, why does top in trusty clear the screen on exit?  who thought that was a good idea? :P
[20:20] <slangasek> ev: so I have a strange issue here with apport; the crash file that I've managed to generate for unity8 on goldfish is missing a 'Package' field, which means apport-retrace will refuse to process it
[20:20] <slangasek> ev: have you heard of such a bug, or do you have any idea what might cause it?
[20:22] <ev> slangasek: have you run it through apport-cli yet?
[20:22] <ev> something needs to call add_package_info or whatever the function is
[20:22] <ev> whoopsie-upload-all will do this as well
[20:23] <slangasek> hmm, is that something that needs to be run on the target system, I guess?
[20:24] <slangasek> or at least, on some system where /usr/bin/unity8 exists
[20:25] <geofft> isn't this the -R option to apport-retrace?
[20:25] <geofft> apport-retrace --gdb doesn't work for me on /var/crash files, but --gdb -R does
[20:25] <slangasek> well, since I'm cross-retracing it, I don't want it to wind up with package information from my host system
[20:26] <slangasek> (particularly since unity8 isn't installed at all)
[20:29] <slangasek> ev: so running apport-cli on it on the target system seems unlikely to finish any time soon
[20:30] <slangasek> geofft: and -R seems to be insufficient, it still complains about the missing Package field
[20:30] <ev> slangasek: yeah, you need to collect the additional data (via apport-cli or whoopsie-upload-all) on the phone itself
[20:30] <slangasek> ev: hmm, challenging. :)
[20:31] <ev> :) sorry
[20:32] <slangasek> ev: yeah, apport-cli doesn't want to finish here (dies with 'Killed'), probably running out of memory
[20:32] <ev> eep
[20:32] <slangasek> perhaps I should spin up an emulator with a touch more than 90MB of RAM
[20:32] <ev> emulator? is that actually working for touch stuff?
[20:33] <slangasek> ev: no, if it were working I would not be trying to get a backtrace from unity8 ;)
[20:33] <cjwatson> ScottK: Yes, I'm fine with it.  It'll need a grub2-signed upload afterwards.
[20:33] <slangasek> but I do have a shell on it
[20:33] <ev> :D
[20:33] <slangasek> and am trying to get us to the next step
[20:33] <ScottK> cjwatson: Thanks.
[20:43] <stgraber> slangasek: based on what I'm seeing on real devices, I gues you'd need at least 512MB to have the emulator emulate something vaguely close to reality
[20:43] <slangasek> quite possible :)
[20:43] <slangasek> in fact, maybe trying to run it in 96MB of RAM is why unity8 segfaulted ;)
[20:44] <slangasek> interesting, updating the config did not cause it to run with more RAM
[20:44] <stgraber> considering it's taking almost 200MB on a physical device, that'd be a safe bet ;)
[20:44] <slangasek> xnox: do you know how to get more than 96MB of RAM out of goldfish?
[20:48] <slangasek> ah, guess it's just -memory
[20:48] <rampageRipper> hello world,has anyone saved this page: books4electricians.blogspot.com?
[21:09] <slangasek> cjwatson: what does the click run-user hook do on startup?  I'm seeing it do a whole lot of nothing here on goldfish and blocking the session startup, and I'm wondering if that's overall emulator slowness or miscellaneous system brokenness or what
[21:12] <cjwatson> slangasek: It runs user hooks, which among other things is necessary to make .desktop files for preinstalled apps work properly
[21:12] <cjwatson> slangasek: It shouldn't be doing anything especially exotic - you can look at the hooks in /usr/share/click/hooks/ with "User-Level: yes"
[21:13] <slangasek> ok
[21:13] <cjwatson> Which should be click-desktop, content-hub, upstart-app-launch-desktop at the moment (and click-desktop basically arranges to stub itself if upstart-app-launch-desktop is present)
[21:13] <slangasek> well, now I just hung the emulator by running 'sync'
[21:13] <slangasek> so yay
[21:13] <cjwatson> I don't know what content-hub does
[21:14] <slangasek> right, it's the content-hub that was runnnig
[21:14] <slangasek> I wound up killing it to see
[21:32] <ScottK> cjwatson: Who has to take care of uploading grub2-signed?
[21:36] <cjwatson> ScottK: anyone really
[23:20] <saiarcot895> What exactly is a debdiff? Is it just the diff of the sources?
[23:36] <infinity> saiarcot895: Yeah, it's a diff between two source packages.
[23:36] <infinity> saiarcot895: Or, that's the most common use of the tool and the term.  You can also debdiff binaries, which is handy. :)


[10:27] <jinal> Hello .. Where can I get more information about the Gnome3 PPAs? Specifically, ppa:gnome3-team/gnome3 says it has Gnome 3.12 packages for Trusty , but I only see a handful of packages. Is it being worked on in the staging ppa?
[10:28] <jinal> What is the latest stable (tested) version of Gnome i can get on UbuntuGnome 14.04 LTS and using which PPA?


[00:50] <cmaloney> Can someone confirm something for me?
[00:51] <cmaloney> https://screamingatthesun.bandcamp.com/track/singularity <- This band say they're not im the episode
[00:51] <cmaloney> https://archive.org/details/OpenMetalcastEpisode114TheSpacesIn-Between <- 38:45
[01:52] <_stink_> cmaloney: if you are asking for a quite literal sanity check, then yes, it is the same track
[01:52] <_stink_> i have them playing on separate tabs staggered by about 9 seconds
[01:52] <_stink_> it's pretty freaky
[01:52] <cmaloney> _stink_: Yeah, I didn't think I was crazy
[01:53] <cmaloney> but these guys insist I don't have their track in there
[01:54] <_stink_> weird.
[12:36] <cmaloney> Good morning
[12:39] <rick_h_> ugh morning
[12:47] <cmaloney> That good eh?
[12:48] <rick_h_> sick of 1.5mb uploads
[12:48] <rick_h_> so called comcast business
[12:48] <rick_h_> so feeling queasy now
[12:50] <brousch> I love this phone
[12:50] <cmaloney> rick_h_: Worried they'll fuck everything up?
[12:51] <rick_h_> cmaloney: well just evil empire, lots of money, and last time I had comcast (when we first moved it) I tried to pay for more service but they couldn't deliver it
[12:51] <rick_h_> but if they can get me 10mb up...I'll write the check
[12:51] <brousch> They can deliver it between the hours of 2AM and 5AM.
[12:52] <rick_h_> hah
[12:52] <rick_h_> well I can schedule photo uploads then I guess
[12:52] <cmaloney> rick_h_: Yeah, that's been my beef with my parent's DSL
[12:52] <cmaloney> but for whatever reason my mom has it in her head that by changing their internet provider they'll somehow enable Obama to take their landline
[12:53] <cmaloney> (don't ask)
[12:53] <rick_h_> lol
[12:53] <rick_h_> well yea that's the nice thing at least
[12:53] <rick_h_> no phone/tv service so it's just internet
[12:53] <brousch> Dictator Obama can take it whenever he wants to.
[12:53] <cmaloney> They have two phone lines into the house
[12:53] <rick_h_> I'll keep paying netflix, amazon prime, and google voice for the rest of my stuff
[12:53] <cmaloney> DSL is on another line
[12:53] <cmaloney> and they're getting sub-ISDN speeds
[12:54] <rick_h_> ugh
[12:54] <rick_h_> yea, the uverse lady tried to talk me into getting two u-verse accounts and splitting traffic
[12:54] <rick_h_> or going the isdn/etc route
[12:54] <rick_h_> look, I'm not looking to get a partial t3 and spend $2000 a month
[12:57] <cmaloney> Yeah, UVerse is all about the up-sell
[12:57] <cmaloney> Comcast as well
[12:57] <cmaloney> they don't quite get that all we care about is a fat pipe.
[12:58] <cmaloney> or phat, depending on your inclination
[12:58] <cmaloney> "Prime Pantry Launches Over 1000 New Items and Brands"
[12:58] <cmaloney> This is not good
[13:07] <cmaloney> Apparently Mono had an update.
[13:28] <jrwren>  oh?
[13:30] <cmaloney> Likely security
[13:30] <cmaloney> Was looking at my updates this morning on my 12.04 desktop
[13:30] <cmaloney> Pretty sure I'm not getting new features. ;)
[13:35] <jrwren> cmaloney: lots of debs, or just 2 debs?
[13:40] <cmaloney> Lots
[13:59] <smoser> cmaloney, if i wanted to talk some at next mug, would there be some time ?
[14:00] <smoser>  i need / want to practice / not wait till last minute for http://sched.co/2qeT
[14:00] <cmaloney> smoser: What would you like to talk about?
[14:00] <smoser> ^
[14:00] <cmaloney> How much time are you looking for?
[14:01] <smoser> 10 , 20 , 30 minutes ? not more than 30. as that would mean i'm *too* prepared . :)
[14:03] <cmaloney> Heh
[14:03] <cmaloney> OK, we can definitely use a second act.
[14:03] <cmaloney> Just contacted our first act to see if he's able to present.
[14:04] <cmaloney> Send<EMAIL_ADDRESS>an abstract / bio and we'll work it in. :)
[14:04] <cmaloney> Thanks!
[14:05] <cmaloney> (or we can use the helpfully provided info / bio. .;) )
[14:05] <cmaloney> <- idjit.
[14:22] <cscheib> when is MUG this year?
[14:22] <cscheib> April again?
[14:22] <brousch> MUG is each month!
[14:23] <cscheib> oh crap, i haven't had my coffee yet
[14:23] <cscheib> I saw mug and thought of penguicon for some reason
[14:32] <cscheib> OK, coffee is made.  much better
[14:33] <cmaloney> heh
[14:33] <cmaloney> Penguicon is in April. Last weekend iirc.
[14:33] <cmaloney> Yep. 23-26
[14:39] <cscheib> what're next month's topics?
[15:15] <cmaloney> TBD, although one of them is Scott Moser telling us about how images are born. ;)
[19:11] <cmaloney> Apparently vim is moving to github
[19:51] <_stink_> nice!
[20:21] <greg-g> from google code?
[20:23] <cscheib> yes
[20:23] <cscheib> and switching from mercurial to git
[20:25] <cmaloney> and switching from VI bindings to emacs
[20:25] <cmaloney> C-x C-s bay-bee


[00:09] <tsimonq2> Second respin rolling. Fingers crossed, this will have the correct session for the installer prompt, and all that.
[00:09] <tsimonq2> I'm knee-deep in that blog post, but I'll have another Cala upload incoming
[01:01] <tsimonq2> New respin is out: 20231210
[01:01] <tsimonq2> Syncing to confirm on my end that the installer prompt, yk, looks right. :P
[01:04]  * guiverc notes "grub-common	2.12~rc1-12ubuntu4" so :) there
[01:05] <tsimonq2> casper/noble,now 1.487 amd64 [installed]
[01:05] <tsimonq2> Gah, needs another round.
[01:07] <tsimonq2> Second rebuild kicked off; I'll have a third before I EOD with some Cala settings goodies (hopefully), and a fourth will be done as usual in the morning, heh.
[01:08] <tsimonq2> If we happen to notice any languages that need denylisting, or that don't fully refresh with the new language once selected/confirmed, let me know.
[01:08] <tsimonq2> arraybolt3: I know you're likely on your weekly $day(z)off, but casper is good. Somehow, your idea worked. :P
[01:09] <tsimonq2> arraybolt3: I mean, I needed to tweak some stuff minorly... but good job. :)
[01:29] <arraybolt3> Woot! Glad it works!
[01:29] <arraybolt3> I worked hard on that :)
 He's alive :D
 Perfect timing!!
[02:47] <tsimonq2> I can confirm it's all working as expected, for some languages. We'll need some automated testing to see *which* languages don't work.
[02:47] <tsimonq2> Plus, we can't forget about the open WiFi networks. WEP is *probably* meh, but why not *shrug*
[02:48] <tsimonq2> All of that will have to be later this week for me :P
[02:49] <arraybolt3> Quick way to make a mess - run sbuild and submittodebian in the same directory in parallel.
[03:29] <tsimonq2> https://lubuntu.me/noble-alpha-featureset/
[03:35] <arraybolt3> woohoo!
[03:35] <arraybolt3> mind if I throw that onto r/Linux?
[03:35] <arraybolt3> tsimonq2: ^
[03:36] <tsimonq2> I have one answer to that question, and I'll answer it only once: *at your own peril.*
[03:36] <tsimonq2> If you REALLY think you can survive that, I mean, sure.
[03:36] <tsimonq2> But don't say I didn't warn you.
[03:36] <arraybolt3> :P I've participated in threads over there quite a bit, so I think I'll be OK. I defended Zorin OS the other day.
[03:37] <tsimonq2> Also: https://9to5linux.com/lubuntu-24-04-lts-to-ship-with-optional-wayland-session-improved-installer
[03:37] <arraybolt3> oh dang, I guess Wayland alpha is official then 😬
[03:37] <arraybolt3> That was on the "let's tread gently" list, but now it's on the "FULL STEAM AHEAD LET'S GOOOOOO!" list :P
[03:39] <arraybolt3> On the bright side I got a minimal labwc session to work in Noble the other day so it's definitely possible.
[03:39] <arraybolt3> The question is whether a labwc+LXQt session is workable or not.
 https://fosstodon.org/@LubuntuOfficial/111554061455353552
[04:05] <arraybolt3> nice
[04:17] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2045944 hah, I ran into that bug a couple nights ago and thought it was the fault of the new script I had just written. Glad to see it was an actual upstream bug.
[04:17] -ubottu:#lubuntu-devel- Launchpad bug 2045944 in grub2 (Ubuntu Noble) "all ubuntu-server preinstalled image builds fail with grub2 2.12~rc1-12ubuntu3" [Critical, Fix Released]
[04:17] <arraybolt3> er, upstream from me anyway
[04:20] <tsimonq2> I'm heading off for the night, let's hope I don't wake up to a fire. :P
[04:20] <arraybolt3> o/
[10:29] <mkukri> any daily grub-install installer failures on grub 12ubuntu3 should be fixed in 12ubuntu4, just saw lubuntu isos also ran into it
[10:29] <mkukri> sorry that bug was my bad
[10:46] <mkukri> good news, unfortunately these things happen when chipping away at a multi-year technical debt backlog. but at least grub-pc will now be properly re-installed on package updates (vs it used to be held back unless you explictly dpkg-reconfigured)
 Confirm 2 installs latest ISO good (re @lubuntu_bot: (matrix) <kc2bez> The latest respin seems to have it fixed.)
 Once built, please test the latest sddm merge to make sure it works ok in lubuntu
 in ppa here: https://launchpad.net/~rikmills/+archive/ubuntu/sddm-merge/+packages
 I really appreciate the heads up on this Rik, thank you! (re @RikMills: Once built, please test the latest sddm merge to make sure it works ok in lubuntu)
 We have enough problems already! :P (re @tsimonq2: I really appreciate the heads up on this Rik, thank you!)
[14:36] <tsimonq2> mkukri: Chipping away at backlog certainly is *noble* work. Just remember to knock it off after Feature Freeze. ;)
[14:37] <tsimonq2> mkukri: Thanks for your help; it happens.
[14:37]  * tsimonq2 slaps mkukri with a wet fish :D
[14:37] <tsimonq2> (classic IRC joke)
[14:39] <mkukri> most of the noble effort is focused on fixing bugs and automated testing. there are no drastic things on the roadmap.  and dont worry,  i dont have free reign anyways :)
[14:40] <tsimonq2> >:D
[14:44] <mkukri> and just fyi,  the remaining "big" grub thing in noble (and debian) is merging the final 2.12 release when it comes out.
[15:29] <tsimonq2> mkukri: Perfect, just keep us posted. :)
[15:29] <tsimonq2> So, here's another thing we haven't considered WRT installer-prompt...
[15:29] <tsimonq2> If someone selects e.g. Spanish, and then selects Try Lubuntu, they don't really have a keyboard selection option, do they?
[15:29] <tsimonq2> They actually have to install the system, I think...
[15:29] <tsimonq2> Could be wrong.
[15:32]  * lubot [matrix] <kc2bez> starts a VM
 https://matterbridge.lubuntu.me/5ff7ba77/file_10212.jpg
[15:37] <tsimonq2> If you run `lxqt-config-input -s "Keyboard Layout"` and the language is set to English, it opens right to the LXQt settings for keyboard selection. For other languages, it needs the translated name. Might want to go off an int or something.
[15:38] <tsimonq2> We could have a button within the prompt that pops that config up?
 There is a widget we can add to the tray I think
[15:38] <tsimonq2> Otherwise, when clicking Try Lubuntu, if the language is not English, we can have it pop that window up right away?
[15:38] <tsimonq2> oh?
[15:38] <tsimonq2> Spanish is obviously the guinea pig here. ;)
 @Roberalz right about now if you have thoughts, go ahead :)
 Yeah, it is the only other language I sort of know.
 https://matterbridge.lubuntu.me/227064e3/file_10213.jpg
 It is mostly just an indicator but clicking through lets you get to the config menu you found.
[15:45] <tsimonq2> ooooooooooooooooooh
[15:48] <tsimonq2> A few things here...
[15:49] <tsimonq2> Can we assume the normal user only has one keyboard layout? Should we have that as a default icon if the language is not US English/standard US keyboard?
[15:50] <tsimonq2> In terms of setting it initially in the live install, I think back to how Calamares does it: they have a specific box you can type in to verify whether the layout works as expected.
[15:52] <tsimonq2> I'm trying to think of the best UX for this... any ideas Dan?
[15:52] <tsimonq2> If they just choose Install Lubuntu, they're all set, we don't need to do anything.
[15:53] <tsimonq2> If they choose Try Lubuntu, they should have an intuitive way to configure their keyboard layout... but would we really need a pre-welcome center popup?
[15:53] <tsimonq2> hmmm
[15:55] <tsimonq2> This seems like a wxl question, tbh. XD
 Is a god option, Debian has it activated by default in lxqt (re @kc2bez: It is mostly just an indicator but clicking through lets you get to the config menu you found.)
 Perhaps after installing it could be deactivated, but to test the system it could be loaded.
[17:48] <tsimonq2> I like that as a starter idea, actually... hmmm
 Seee I knew @Roberalz had the answers XD
 Just tested latest iso - selected Icelandic (íslenska) as language - confirmed selected try and the desktop was in Icelandic !!
[18:12] <tsimonq2> 🎉🎉🎉🎉
 Well done mates! (re @lubuntu_bot: (irc) <tsimonq2> 🎉🎉🎉🎉)
[18:12] <tsimonq2> Thank you!!!! There are some languages that *don't* work, let's find them ;)
[18:13] <tsimonq2> (No rush, if we don't get manual testing done for this, I'll write an automated QA test.)
 I think there are way to many variants of English,spanish;french etc ..also as you know the keyboard was still in US English. (Live session) (re @lubuntu_bot: (irc) <tsimonq2> Thank you!!!! There are some languages that *don't* work, let's find them ;))
[18:16] <tsimonq2> I agree with that :)
[18:16] <tsimonq2> @Leokolb: Would you consider the Calamares language list to be "too much?" The reason I ask is, both use QLocale on the backend so I can probably use some of their logic.
 The list that Calamares has used until now is good in my opinion and of course is same for keyboard (I think) (re @lubuntu_bot: (irc) <tsimonq2> @Leokolb: Would you consider the Calamares language list to be "too much?" The reason I ask is, both use QLocale on the backend so I can probably use some of their logic.)
[18:42] <arraybolt3> tsimonq2: you've not already packaged picom-conf have you?
[18:42] <arraybolt3> if not I'll tackle it
 Go ahead
 Also we need a new sddm-conf, just got tagged at the request of us and OpenSUSE iirc
 May need to add to pkgset
[18:49] <arraybolt3> tsimonq2: also now that we've announced experimental Wayland support, are we so sure about making that a PPA-only thing?
 *shrug* I said "we're not exactly sure what that looks like yet" for a reason :)
 Up for discussion; what do you think?
[18:56] <arraybolt3> I think we should at *least* have the package for it in the archive to be installed by the end user, similar to what Kubuntu has done and probably still is doing.
 Let's reuse "Lubuntu Next"
[18:57] <arraybolt3> But as we've announced it to the whole world, we may have people looking for it in the session menu, and so we may even want it to be installed but not the default. Most users won't find it.
[18:57] <arraybolt3> Lubuntu Next?
 That was the codename for Lubuntu with LXQt back in the day before it was our official desktop
[18:58] <arraybolt3> oh cool
[18:58] <arraybolt3> was it like installable as a separate package, or was it a separate ISO entirely?
 We had a lubuntu-next daily and everything. Some of the old cruft is still there and there's precedent, so depending on how far we get this cycle, we could spin up Lubuntu Next images that are not being released.
 https://ubuntu-archive-team.ubuntu.com/cd-build-logs/lubuntu-next/
 But we should focus on finishing our feature set and going bug hunting when we're done....
[19:11] <arraybolt3> I like it
[19:36] <arraybolt3> ok, well I have a test machine at least, need to look into stefonarch's LXQt Wayland progress since he actually has working desktops and I have broken weirdness :P but it's doable for sure.
[21:44] <arraybolt3> tsimonq2: you said something about needing a new sddm-conf? The only new things I see in that are some new translations.
[21:45] <arraybolt3> And I do not see any new Git tag, so it's just a Git sync.
 I think there were plans for a release on Github
[21:46] <arraybolt3> ah. Well in that instance I should probably hold off until that happens.
 There was some chatter in the LXQt channel earlier
[21:46] <arraybolt3> which channel is that?
[21:46] <arraybolt3> Is it on Libera?
[21:47] <arraybolt3> I can look it up myself, just figured I'd ask
 It is bridged between OFTC, Matrix and Telegram
[21:47] <arraybolt3> I'm on OFTC, so I can join there.
 https://matrix.to/#/#lxqt:matrix.org
 Standby I can get you the OFTC info too
[21:49] <arraybolt3> just found it
[21:49] <arraybolt3> already joined
[21:49] <arraybolt3> https://lxqt-project.org/release/2023/11/10/release-lxqt-menu-data-1-4-1/ should probably package that soon-ish
 👍
[21:50] <arraybolt3> anyway, /me tackles picom-conf
 Awesome, thank you!
[21:51] <arraybolt3> Probably need to file an ITP bug in Debian and whatever we call the equivalent in LP.
[21:52] <arraybolt3> Worthy of note, there hasn't been a release of that either yet so I'm packaging a Git snapshot.
 Gotta start with something I guess.
[21:53] <arraybolt3> tsimonq2: did you already package libqtilitools for Debian and upload it? As well as sddm-conf? Or should I be going on a Debian-side packaging spree there?
[21:56] <arraybolt3> tsimonq2 did *not* do it for Debian. OK, so for now Lubuntu-only it is, I'll tackle Debian later, probably after the release of sddm-conf.
[22:04] <arraybolt3> alright, let's see if this builds :D
[22:04] <arraybolt3> I shamelessly stole Simon's entire packaging for sddm-conf and tweaked it to work for us
[22:15] <arraybolt3> Preparing to test the new package before submitting it.
 If you happen to toss it at a PPA I will test it too.
[22:17] <arraybolt3> sounds good
 Oh, thanks for the info. (re @lubuntu_bot: (irc) <arraybolt3> https://lxqt-project.org/release/2023/11/10/release-lxqt-menu-data-1-4-1/ should probably package that soon-ish)
[23:07] <arraybolt3> hahahaha I just about included the entire Git history for picom-conf in the source package
[23:08] <arraybolt3> Lintian's "very long line length" warnings let me know.
[23:21] <arraybolt3> https://git.lubuntu.me/Lubuntu/picom-conf-packaging
 https://github.com/AzumaHazuki/lxqt-themes-lubuntu-box/issues/1#issuecomment-1849072555
[23:45] -ubottu:#lubuntu-devel- Issue 1 in AzumaHazuki/lxqt-themes-lubuntu-box "Please make a tag" [Open]
 Are you sure it's MIT, not Expat? :P (re @lubuntu_bot: (irc) <arraybolt3> https://git.lubuntu.me/Lubuntu/picom-conf-packaging)
 Also idc feel free to set my licensing to whatever flavor of GPL the source uses
[23:47] <arraybolt3> tsimonq2: Well it says MIT in the source code.
 vorlon thwacked me for that on the first set
[23:47] <arraybolt3> So according to upstream, yes. (Probably *is* expat but, who am I to disagree with the mighty upstream devs?)


[08:32] <dholbach> hola dpm
[08:32] <dholbach> dpm, did you get back all right?
[08:34] <dpm> hey dholbach
[08:34] <dpm> I did, thanks :)
[08:34] <dholbach> still jetlagged I guess :)
[08:38] <dpm> a bit, but I'll survive :)
[08:44] <dholbach> ok :)
[08:57] <dholbach> brb


[02:30] <mpt_> Goooooooooooooooooooood afternoon Launchpadders!
[02:30] <Hobbsee> afternoon mpt!
[08:19] <carlos> morning
[08:41] <janimo> are PPA packages built against gutsy updates or proposed versions as well? The sugar package built in my PPA depends on a  libpango that is not in the gutsy archives enabled by default
[08:42] <janimo> needs  1.18.3-0ubuntu1 vs the current 1.18.2-0ubuntu1
[08:43] <Fujitsu> janimo: They're built only against the RELEASE pocket at this time.
[08:44] <janimo> I wonder how come sugar ends up with a depneds that's not there
[08:45] <janimo> RELEASE pocket ==  components enabled by default in a gutsy system?
[08:45] <Fujitsu> RELEASE as opposed to BACKPORTS, UPDATES, SECURITY, PROPOSED.
[08:45] <janimo> Fujitsu: aha, I did not kwno this so far, thanks
[08:45] <janimo> I'll mention this from now on when calling for testers
[08:46] <janimo> but pango 1.18.3-0ubuntu1 is not in release yet AFAIK
[08:46] <janimo> so still can't see how it ended up as a dep
[08:47] <Fujitsu> Er, once a distrorelease is released, RELEASE is never changed.
[08:48] <janimo> http://launchpadlibrarian.net/10379818/buildlog_ubuntu-gutsy-i386.sugar_0.65%2Bgit20071114-1_FULLYBUILT.txt.gz
[08:48] <janimo> this has gutsy-updates mentioned in it
[08:48] <janimo> and secutiry too
[08:49] <janimo> Get:117 http://ftpmaster.internal gutsy-updates/main libpango1.0-common 1.18.3-0ubuntu1 [63.5kB]
[08:49] <janimo> so it clearly includes UPDATES if that is a pocket, no?
[08:49] <Fujitsu> Oh, you can't be serious. This design is so broken.
[08:49] <Fujitsu> janimo: Right, PPA just doesn't make sense.
[08:50] <janimo> well, ot's ok as long as it is mentioned somewhere, I just did not expect it
[08:50] <Fujitsu> It only started building against them all recently.
[08:51] <Fujitsu> I love the listing of changes we get.
[08:56] <ubotu> New bug: #163053 in rosetta "KDE files with non gettext plural forms include plural form header" [Undecided,New] https://launchpad.net/bugs/163053
[09:13] <Hobbsee> Fujitsu: but we knew ppa was broken.  *shrug*
[09:13] <Hobbsee> Fujitsu: i'd imagine it includes updates and release.
[09:14] <Fujitsu> Hobbsee: It includes updates, release and security, but only since the last rollout.
[09:14] <Hobbsee> Fujitsu: dont expect a changelog.  next, you'll start expecing the documentation to be correct, too.
[09:14] <Hobbsee> ah, right, good.
[09:14] <Fujitsu> This wasn't documented, right.
[09:14] <Hobbsee> but appears to only sometimes use what's already in the ppa.
[09:14] <Hobbsee> presumably dependant on the moon phase.
 mdz: Isn't there? I was sure that previous versions of the policy mentioned that Soyuz would remain non-free, as it will always be a service sold to other distros.
[10:29] <mdz> Fujitsu: there are a number of services which Canonical hopes to offer through Launchpad, though as far as I know that does not imply that it will never be open source
[10:30] <Fujitsu> mdz: I am trying to dig out the version of the Launchpad FAQ to which I made reference.
[10:31] <mdz> this isn't really an area of direct responsibility for me, so I can't speak authoritatively, but there are people on this channel who can
[10:32] <Fujitsu> It mentioned that Canonical was unable to open much of it, because it was all very integrated, and components such as Malone wouldn't run without Soyuz, and Soyuz wouldn't be released because it was sold as a service for other companies producing distributions.
[10:36] <Fujitsu> I can find no full copies of it, but an excerpt is as follows:
[10:36] <Fujitsu> "Launchpad is a large, monolithic, web application. We would be happy to release ... however, that code will not run without the distribution management code, which is part of of the service that Canonical provides to other companies that make their own distributions."
[10:37] <Hobbsee> Fujitsu: i would guess that that was the case, but that it's now deemed safe - as soyuz and friends are so utterly and totally convoluted they wouldn't be much help to anyone without an awful lot of study.
[10:38] <Hobbsee> (and we know this, due to how they explode differently each time)
[10:39] <Hobbsee> mdz: do you know if the plan changed, or that FAQ was wrong?
[10:40]  * Hobbsee is well aware that it has to be big, and do lots of stuff, but still...
[10:42] <elmo> Hobbsee: dude
[10:43]  * Hobbsee waits, watches for lightning bolts
[10:43] <elmo> archive management is hard.  I know this because, I've written one.  and it's far less ambitious than soyuz (and in a lot of ways, far less featureful).  and it still explodes if people look at it the wrong way
[10:43] <elmo> I'm really not sure your negativity is helpful to anyone
[10:44] <elmo> celso and julian are working as hard as they can to improve things, constantly beating up soyuz in public is hardly going to do wonders for their morale.  especially, when it _is_ getting better all the time
[10:44] <Hobbsee> elmo: noted.  and i wasnt saying it was easy.
[10:45] <Hobbsee> for the record, i think they've done a good job.  I'd just love to see some stuff improved.
[10:45]  * Hobbsee shuts up.
[10:46] <mdz> Hobbsee: no, I'm not familiar with the document Fujitsu quoted there
[10:46] <mdz> SteveA might be in a better position to comment
[10:46] <Fujitsu> mdz: It was the Launchpad FAQ for a looong time. But I guess you wouldn't exactly have needed to read it, so...
[10:51] <mpt> I removed that stuff about Launchpad being highly integrated from the FAQ
[10:51] <Fujitsu> mpt: Aha. So there has not, in fact, been a policy change?
[10:51] <mpt> primarily because it wasn't relevant to the question, but we also aim (eventually) to make it untrue
[10:51] <Fujitsu> People were just laughing at it too much?
[10:51] <mpt> It's not a policy change
[10:52] <mpt> I don't remember anyone laughing at it
[10:52]  * Fujitsu has seen an email or two to launchpad-users laughing at it, and in other places.
[10:53] <mpt> at Launchpad being monolithic, perhaps
[10:53] <Fujitsu> Well, yes.
[10:53] <mpt> There were good reasons for that, I'm told, but that was before my time :-)
[10:53] <Fujitsu> But that paragraph was the only visible reference to it.
[10:53] <mpt> Only visible reference to what?
[10:55] <Fujitsu> It being monolithic.
[10:57] <mpt> I think it was mentioned in #launchpad once or twice
[11:38] <Hobbsee> hiya cprov
[11:39] <cprov> Hobbsee: hi there.
[11:42]  * Hobbsee belatedly apologises for ranting about the state of parts of launchpad, yet again.
[11:43]  * Hobbsee should just go and help fix it, or something.
[11:56] <Hobbsee> er, what do bugs for the activity log get filed under?
[11:56] <Hobbsee> malone?
[11:56] <Fujitsu> malone
[11:56] <Hobbsee> ok
[11:57] <Hobbsee> activity log says that a bug got marked invalid, but it doesnt say in *which* package it got marked as invalid.
[11:59] <Fujitsu> The activity log is useless. As a backup you can use bugmail archives.
[12:00] <Hobbsee> not if i'm not subscribed to the bug.
[12:00] <Hobbsee> and the activity log is *not* useless.  it just doesnt contain some required parts.
[12:00] <Hobbsee> i can see that some nutter changed the bug wrongly, but nto in which project.
[12:01] <Hobbsee> therefore, i cant see what they were thinking, but i know who it is, to hit them with the "please dont do this" stick.
[12:01] <Hobbsee> this is, of course, suboptimal for multi-project bugs :)
[12:04] <Hobbsee> pretty please launchpad.  please load the bug.
[12:26] <ubotu> New bug: #163091 in malone "+activity does not show which package was changed, only that it was (multiple packages/projects problem)" [Undecided,New] https://launchpad.net/bugs/163091
[12:52] <Ubulette> hi
[12:55] <Ubulette> there's something strange with the ppa builders. in i386, there's a lang pack flood. looking at it, it seems each pack should take 2 or 3 mins, yet, every few packs, some are taking 30+ min (on the 3 i386 builders at the time), for no apparent reason.
[12:56] <Ubulette> meaning that i386 are all blocked more than they should be
[12:57] <Ubulette> https://edge.launchpad.net/~ubuntu-langpack/+archive/+builds?build_text=&build_state=all&start=100&batch=50
[13:09] <Hobbsee> Ubulette: may be a queue botchup.
[13:10] <Hobbsee> cprov: with arch: all packages, is there any particular reason why they *have* to be built on i386?  if they're arch all, cant you just shove sections of them to amd64 / lpia too?
[13:10] <Hobbsee> would make i386 not lag so much
[13:13] <cprov> Hobbsee: we can't yet dispatch arch-all to any builder due to a sbuild bug (lack of feature, in fact)
[13:13] <Ubulette> Hobbsee, it's been like that for weeks (maybe forever) so it may be a bug or at least something that could be improved. loosing 3*30min every 3*7 packages seems a waste
[13:13] <Hobbsee> cprov: oh, so it does depend on sbuild.  right.
[13:13] <Hobbsee> Ubulette: i dont work on soyuz :)
[13:45] <lamont> cprov: could we have a timestamp in NOT-OK status?
[13:46] <cprov> lamont: not easily but yes, we could, file a bug with your use case.
[13:47] <lamont> ok
[14:55] <Diije> muhaha
[14:56] <Hobbsee> ....okay?
[15:00] <lamont> Hobbsee: remind me of that build log that you wanted to have explained?
[15:00] <Hobbsee> lamont: kdebase-workspace
[15:01] <Hobbsee> lamont: why ti didnt take the kdepimlibs5 dep, which is already in the ppa, and instead took the universe version
[15:01] <Hobbsee> (and therefore fell into DEPWAIT)
[15:02] <Hobbsee> lamont: can you email me with the answer?  i need to head to bed.
[15:02]  * Hobbsee has an exam in 7 hours.
[15:04] <lamont> Hobbsee: ok
[15:04] <Hobbsee> thanks
[15:05] <ubotu> New bug: #163118 in soyuz "upload queue fails check on partner archive" [Undecided,New] https://launchpad.net/bugs/163118
[15:15] <lamont> grumble.
[15:15] <lamont> bigjools/cprov/whoever... how do I find all the ppa's that have kdebase-workspace source in them?
[15:16] <bigjools> lamont: there's no package search facility :/  (yet)
[15:18] <lamont> bigjools: ah, so the answer to my question is "ask someone with SQL-powers"....
[15:18] <lamont> so...  could you find me which ppa hobbsee's problemchild is in?
[15:18] <bigjools> lamont: correct :)
[15:19] <lamont> otherwise I get to go find it in history from a couple days ago
[15:20] <lamont> which actually wasn't that bad. nm
[15:20] <lamont> https://edge.launchpad.net/~kubuntu-members/+archive/+build/44227\
[15:21] <lamont> feh.  and built/published...
[15:50] <ubotu> New bug: #163125 in soyuz "change-override.py crashes with 'NoneType' object has no attribute 'changeOverride'" [Undecided,Confirmed] https://launchpad.net/bugs/163125
[16:22] <ipso> I registered my project and uploaded translation files several weeks ago or maybe even a month ago, however they are still "pending review". Does it normally take this long?
[16:23] <Odd_Bloke> ipso: I believe there's a biiig backlog, but I don't know if it's that big...
[16:23] <Odd_Bloke> There's a helpful answer. :p
[16:24] <ipso> Yeah, it'll be a month in a couple days
[16:24] <ipso> What actually needs to be reviewed with new translation files?
[16:33] <PriceChild> I asked for my ppa to be cleared, and some debs were immediately removed, but the rest weren't. I was then told I had to wait till 3am for a cron to sort things out... its been two days later and still nothing :/ https://answers.edge.launchpad.net/launchpad/+question/17826
[17:50] <ubotu> New bug: #163155 in rosetta "Show external suggestions based on both singular and plural text" [Undecided,New] https://launchpad.net/bugs/163155
[18:05] <Ubulette> elmo, are you there ?
[18:05] <Ubulette> about bug 162723
[18:05] <ubotu> Launchpad bug 162723 in xulrunner-1.9 "xulrunner-1.9 build leaves orphaned find processes, hangs buildds" [High,New] https://launchpad.net/bugs/162723
[18:06] <Ubulette> it's a package i've created
[18:07] <Ubulette> elmo, i need info on what you're experiencing. tell me when you're available
[19:20] <Ubulette_> elmo, nevermind, it's fixed (#162723). next upload should no longer do that.
[19:21] <elmo> Ubulette_: super - thanks; how did you fix it?
[19:23] <Ubulette_> &> is a b/dashism. i changed it for the more standard > /dev/null 2>&1
[19:24] <elmo> ok
[19:27] <Ubulette_> those 2 find should not be there anyway. it's a workaround for a bug upstream but mozilla build system is crazy
[19:46] <bkc> does bugs/launchpad have an API that could be used to connect to mylyn/eclipse?
[19:56] <ubotu> New bug: #163180 in launchpad "LaunchpadViewForm shouldn't display (Optional) for display-only widgets" [Medium,Confirmed] https://launchpad.net/bugs/163180
[20:25] <somerville32> Someone is spamming a bug.
[20:25] <somerville32> or not
[20:25] <somerville32> weird :/
[20:25] <somerville32> Bug
[20:26]  * somerville32 goes to report it.
[21:01] <ubotu> New bug: #163196 in soyuz "partner archive lacks atomic dists/ update" [Undecided,New] https://launchpad.net/bugs/163196
[23:30] <ubotu> New bug: #163233 in rosetta "Refactor rosetta/xx-pomsgset-translate.txt pagetest and translationgroups/60-translation-suggestions.txt" [Undecided,New] https://launchpad.net/bugs/163233


[01:42] <Ohelig1> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:42] <Ohelig1> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[01:42] <Ohelig1> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[01:42] <Ohelig1> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[02:33] <Xgc12> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:33] <Xgc12> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[02:33] <Xgc12> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[02:33] <Xgc12> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[02:35] <bigpresh9> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:35] <bigpresh9> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[02:35] <bigpresh9> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[02:35] <bigpresh9> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[02:37] <kamkran> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:37] <kamkran> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[02:37] <kamkran> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[02:37] <kamkran> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[02:40] <ski_> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:40] <ski_> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[02:40] <ski_> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[02:40] <ski_> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[03:21] <caf6> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:21] <caf6> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[03:21] <caf6> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[03:21] <caf6> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[03:28] <TReK20> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:28] <TReK20> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[03:28] <TReK20> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[03:28] <TReK20> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[03:52] <Dominian1> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[03:52] <Dominian1> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[05:09] <drathir13> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[05:09] <drathir13> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[05:09] <drathir13> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[05:09] <drathir13> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[05:29] <Raziel5> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[05:29] <Raziel5> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[05:29] <Raziel5> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[05:29] <Raziel5> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[07:46] <developers> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[07:46] <developers> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[07:46] <developers> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[07:47] <developers> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[08:00] <Sigyn22> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[08:00] <Sigyn22> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[08:00] <Sigyn22> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[08:00] <Sigyn22> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[08:17] <bigpresh13> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[08:18] <bigpresh13> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[08:18] <bigpresh13> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[08:18] <bigpresh13> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[08:56] <LookingGlassSec> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[08:56] <LookingGlassSec> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[08:56] <LookingGlassSec> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[08:56] <LookingGlassSec> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[09:07] <Turandot1> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:07] <Turandot1> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[09:07] <Turandot1> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[09:07] <Turandot1> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[09:33] <woddf219> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:33] <woddf219> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[09:33] <woddf219> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[09:33] <woddf219> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[09:39] <Cisien5> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[09:39] <Cisien5> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[09:39] <Cisien5> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[09:39] <Cisien5> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[09:40] <bshah> tsimonq2: acheronuk: +r this channel?
[10:06] <cheshire_cat> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[10:06] <cheshire_cat> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[10:06] <cheshire_cat> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[10:06] <cheshire_cat> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
[10:27] <acheronuk> bshah: done. thanks


[00:35] <linux> hi
[00:35] <linux> how are you
[00:36] <linux> I have problems in sound on my linux ubuntu studio
[00:36] <linux> how can I solwe it
[00:37] <linux> I solwe it
[00:38] <linux> now is working
[07:04] <adam_> Good Evening from ModMan Entertainment Studios, Las Vegas
[07:05] <adam_> This is my first use of US
[08:02] <zequence> adam_: Hello ther :)
[15:30] <professor_> Hi eveyybody, I've just installed Ubuntu Studio  15.10 on my Easynote sj51 laptop.
[15:32] <professor_> in fact I've completely removed my Windows 7 as I found everything I need in the Ubuntu OS
[15:32] <professor_> Anybody out there trying the same experience please?
[23:40] <Akern> Hi guys, I read you need contributors, I don't know if I can help you the way you'd like, but I'd like to!


[12:31] <danilos> gary_poster, I did a test call and I am ready :)
[12:31] <danilos> hi, btw :)
[12:31] <gary_poster> danilos, cool :-)
[12:32] <gary_poster> hi
[12:32] <gary_poster> bac benji (not here IIRC) danilos gmb, call in 1
[12:32] <gmb> ack
[12:33] <benji> you recall correctly
[12:34] <bac> hi
[12:36] <gary_poster> benji, now you've done gone and confused me :-P
[12:36] <benji> heh
[12:36] <bac> skypee crashee
[12:41] <bac> +1 on RT stupidity
[12:52]  * gmb lunches
[12:53] <gary_poster> danilos, call @ 20 minutes past the hour, cool?
[12:54] <danilos> gary_poster, cool
[13:37] <gary_poster> danilos, but 20 minutes past *what* hour, yes? :-)
[13:37] <gary_poster> danilos, ready any time
[13:37] <gary_poster> gimme a call when you like
[13:37] <danilos> gary_poster, heh, yeah, there are also :30 timezones :)
[13:37] <gary_poster> :-)
[13:40] <bac> danilos: i'd like to chat when you get finish with gary_poster
[13:44] <danilos> gary_poster, https://pastebin.canonical.com/53876/
[14:33] <danilos> bac, hi
[14:33] <danilos> bac, up for a call now?
[14:34] <bac> hi danilos.  i think i figured out the proper place to make the fix.  looks like a change to the call of getSubset in _guessed_potemplate_for_pofile_from_path
[14:34] <bac> i hadn't found that bit of code yesterday
[14:34] <bac> danilos: so let's not do a call atm
[14:34] <danilos> bac, cool, sounds right
[14:57] <gary_poster> bac benji gmb, confirmed with Francis that Marianna's email was a template: we, and all LP engineers, should attend Budapest if possible (benji will not be able to go, I think).
[14:58] <gmb> Okidoke.
[14:58] <bac> gary_poster: ok
[14:58]  * gmb tries to work out a route that doesn't involve a connection at Schipol
[14:58] <bac> bring your mittens
[14:59] <gary_poster> because of security and uzis, gmb?
[14:59] <gmb> gary_poster: No; Schipol is the luggage-loss capital of Europe :)
[14:59] <gary_poster> heh ok
[15:00] <gary_poster> C! H! Arrrrrrrrrrrrrrgh!
[15:31] <bac> danilos: could you review my branch?  https://code.launchpad.net/~bac/launchpad/bug-867411/+merge/78270
[15:36] <danilos> bac, heh, sure, it's a short branch
[15:37] <bac> danilos: yep...and should be unsurprising
[15:43] <danilos> bac, transaction.commit() is needed for librarian, right?
[15:43] <danilos> bac, (in tests, that is)
[15:43] <bac> danilos: i can try to remove it and see
[15:44]  * bac < lunch
[15:44] <danilos> bac, oh, it's actually a script run, fair enough
[15:45] <danilos> bac, r=me, and I am off :)
[15:54] <gary_poster> lunch/babysitting begins now
[15:54] <gary_poster> I expect to be gone just over an hour
[16:57] <bac> gary_poster: you sure get to show off your work today:  https://qastaging.launchpad.net/
[17:16] <gary_poster> bac, heh, I didn't think about that
[17:17] <gary_poster> but yes
[18:17] <bac> gary_poster: i just noticed on my calendar a dentist appt for 8 am tomorrow.  i'll miss the standup.
[18:25] <gary_poster> ok bac.  hope it goes well
[18:35] <bac> gary_poster: i'll probably get yelled at...but i always do
[18:35] <gary_poster> heh
[18:35] <bac> i really like the floss on a stick.  hygienest does not
[18:35] <gary_poster> heh
[18:55] <bac> gary_poster: both branches sent off to ec2 land.  going back to the well.
[18:55] <gary_poster> great bac thanks
[19:11] <bac> gary_poster: do you know much about gpghandler wrt host vs public_host?
[19:11] <gary_poster> no sorry bac
[20:21] <bac> gary_poster: can you see this link https://launchpad.net/~speed-dreams/+archive/ppa/+admin
[20:22] <gary_poster> looking bac
[20:22] <gary_poster> bac Not allowed here
[20:22] <bac> ok
[20:22] <bac> wonder why i have super powers
[20:32]  * bac finishes chr, woo
[21:39] <gary_poster> bye