[01:40] <studio-user099> hi
[01:40] <studio-user099> spanish?
[14:00] <Nexus3> Hello there
[18:17] <sirriffsalot> Whenever I try to completely remove, reinstall or remove "libc6" which is causing broken packages, it wants to remove a HUGE amount of other essentials, like alsa, ardour3 and all kinds of things which are out of the question. What's this all about?
[18:17] <sirriffsalot> libc6 is currently at 2.17, when it should be at 2.15, but if I try to force the version down it tries to shred my system all the same
[18:17] <sirriffsalot> What the hell...
[18:26] <zequence> sirriffsalot: Why should it be 2.15?
[18:26] <zequence> Make sure you have the exact version for the package you want to install and do: sudo apt-get install lib6=<version>
[18:27] <zequence> Probably you added a PPA which updated it, and a bunch of other stuff
[18:28] <sirriffsalot> 2.17 is for ubuntu 14.04, I have 12.04
[18:29] <sirriffsalot> sirriffsalothp@HP:~$ sudo apt-get install libc6=2.15
[18:29] <sirriffsalot> Reading package lists... Done
[18:29] <sirriffsalot> Building dependency tree
[18:29] <sirriffsalot> Reading state information... Done
[18:29] <sirriffsalot> E: Version '2.15' for 'libc6' was not found
[18:29] <sirriffsalot> sirriffsalothp@HP:~$ sudo apt-get install libc6=2.17
[18:29] <sirriffsalot> Reading package lists... Done
[18:29] <sirriffsalot> Building dependency tree
[18:29] <sirriffsalot> Reading state information... Done
[18:29] <sirriffsalot> E: Version '2.17' for 'libc6' was not found
[18:29] <sirriffsalot> Long time no see zequence :)
[18:35] <zequence> sirriffsalot: I don't think those were the exact versions
[18:36] <zequence> sirriffsalot: http://packages.ubuntu.com/precise/libc6
[18:36] <zequence> seems to be 2.15-0ubuntu10.6
[18:36] <zequence> so: sudo apt-get install libc6=2.15-0ubuntu10.6
[18:36] <zequence> but, there will probably other packages that are the wrong version, dependencies, etc
[18:38] <sirriffsalot> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
[18:38] <sirriffsalot> And sudo apt-get -f install gets me back where we were already
[18:38] <sirriffsalot> Namely, E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
[18:38] <sirriffsalot> E: Unable to correct dependencies
[18:39] <zequence> What can I say.  It can sometimes make a difference
[18:40] <zequence> sudo aptitude install -f
[18:43] <sirriffsalot> Hmm
[18:44] <sirriffsalot> Running a .deb file should not screw my system up, that's all I did since this happened, and this is from winehq
[18:44] <sirriffsalot> I don't have aptitude, and can't install it, lol :)
[18:57] <sirriffsalot> Guess I'll ask in ubuntuforums, hopefully they can dig deeper
[19:08] <jarnos> I connected my Android device via USB using PTP connection in 13.10. File manager becomes very slow when using that folder. Is that something that is fixed in 14.04.1 and what might be the cause for the slowness? I couldn't make MTP connection work. I see the file listings in file manager, but no permissions for me.
[20:11] <holstein> jarnos: i thought that was discontinued by android?
[20:11] <holstein> jarnos: regardless, there is nothing ubuntu/linux/ubuntustudio is doing that will effect the connectivity or speed of an android device
[20:12] <holstein> there is little we are doing downstream that will have anything to do with it.. i would go back up to either #xubuntu or #ubuntu channels or mailing lists and see what issues others are having with android devices
[20:12] <jarnos> holstein, you thought what was discontinued?
[20:12] <holstein> i know, i just stopped connecting my android like that, and use the network to move files
[20:13] <holstein> jarnos: i thought "MTP connection" was discontinuted
[20:13] <holstein> jarnos: regardless, you can try 14.04 live and see.. but, there is nothing in our linux kernel that is making android slow, or not connect
[20:14] <jarnos> holstein, no, my brand new Samsung S5 mini offers MTP and PTP connections.
[20:14] <holstein> jarnos: sure
[20:14] <holstein> jarnos: then, i would take that up with samsung, if you cant get it working
[20:14] <holstein> jarnos: otherwise, try plugging the device into other machines, and other USB ports, and other operating systems.. if you think its 14.04 vs 13.10, try 14.04 live and see
[20:15] <jarnos> holstein, yeah, I am going to install 14.04.1 when I have time.
[20:15] <holstein> jarnos: why?
[20:16] <holstein> jarnos: why not just try it live, as i suggested, and make sure that it is the issue?
[20:16] <holstein> jarnos: i *always* try the live CD's anyways.. and suggest them, even if the user insists on upgrading rather than a fresh install..
[20:16] <holstein> its nice to see the *actual* kernel running on the actual hardware.. to make sure the hardware supports the linux kernel that is going to be used
[20:21] <jarnos> holstein, oh yes, I could try running live session by USB pendrive once I manage to make one. (The ISO is too big to fit in a CD.) I tried Startup Disk Creator in Ubuntu Studio 13.10 to make one of 14.04.1, but it asked my password to get permissions to install Grub, which I found odd and cancelled the operation.
[20:22] <holstein> jarnos: sure, when i, or anyone else refers to "live CD" thats just the live iso downloaded and running on what you like
[20:22] <holstein> jarnos: i didnt mean to say an actual CD
[20:22] <holstein> jarnos: though, many other ubuntu flavors *do* fit on a CD
[20:24] <holstein> jarnos: you will need "sudo" or "root" access from many operating systems to do what is being done
[20:24] <holstein> jarnos: i use "unetbootin"
[20:24] <holstein> !info unetbootin
[20:24] <holstein> but, the ubuntu iso's are "dd copy-able".. meaning, you can just dd copy them directly to the usb stick
[20:25] <jarnos> holstein, but why do I need them? I am creating a live USB and not touching the system I am running.
[20:25] <holstein> jarnos: why do you need them? what them?
[20:25] <holstein> jarnos: why do you need what?
[20:25] <jarnos> holstein, I referred to "sudo"
[20:26] <jarnos> holstein, or superuser password.
[20:26] <holstein> jarnos: as i said, you need sudo or root access to have that level of control on the USB stick
[20:26] <holstein> jarnos: if you dont want to do it that way, i would run a live CD, anc unplug my current hard drive.. then, i would *know* nothing is happening
[20:27] <holstein> otherwise, read up on what is actually happening, and dont take my word (or anyone else's) on the matter
[20:27] <holstein> what do i do? i use sudo to either dd copy the iso, or i use unetbootin, which asks for a sudo password
[20:27] <holstein> i then, carefully refer to the proper drive.. and double check, or, i do it on a machine that only has the source and target drives
[20:31] <jarnos> holstein, Thanks for your advise.


[00:15] <hexsprite> hi bzr people ;) i have been using git-svn and wonder if bzr-svn has the same limitations.  particularly i want to be able to share bzr repositories between my laptop and my desktop and be able to merge between them using bzr and then commit via svn from either of them... possible?
[00:15] <lifeless> totally possible
[00:15] <hexsprite> great!
[01:40] <ianm_> how do you force unlock a directory?
[01:40] <lifeless> bzr break-lock
[01:42] <ianm_> thanks
[01:54] <cerw> hi there
[01:54] <lifeless> hi
[01:54] <cerw> i have question our repos is getting too big, we are using for archive mainly, can i somehow remove some old revision, without demiging the repo ?
[01:55] <lifeless> not trivially no
[01:56] <lifeless> you need to do a rebase operation skipping the bits you don't want
[01:56] <lifeless> how big is too big?
[01:56] <cerw> it's about 70G
[01:56] <cerw> but the think is we dont need to keep all the repos
[01:57] <cerw> we are using it for deploying
[01:57] <cerw> everyday new version of release and taging them, that works great
[01:57] <cerw> but we need to keep only maybe 20days old tags, the oder onnes we can trash..
[01:59] <cerw> waht is rebase about?
[02:00] <lifeless> rebase rewrites history; what you want to do can be described as rewriting history
[02:00] <lifeless> there is also stacked branches which may help you and still keep history
[02:00] <lifeless> are you deploying binary files?
[02:00] <cerw> yeap it's final product, so some binary some scripts
[02:01] <cerw> anad lots of data
[02:05] <cerw> so i can remove revisions using rebase?
[02:07] <lifeless> with some effort yes
[02:07] <lifeless> its not exactly polished at the moment
[02:08] <lifeless> someone posted a recipe to the list I think
[02:15] <cerw> i am just playing with it now and it looks it it rewrutes each revision again
[02:15] <cerw> not sure if i want that
[02:15] <cerw> can i start branch and tell it to start it from some revision?
[02:16] <cerw> then i can split it ..
[02:21] <cerw> ok so is there way i can copy branch startinfr from some Revision?
[03:47] <NfNitLoop> So, out of curiosity, I tried to reproduce this bug w/ 1.9rc1 & 0.4.14:  https://bugs.launchpad.net/bzr-svn/+bug/248289
[03:47] <NfNitLoop> but I apparently can't commit to a bound svn branch.
[03:48] <NfNitLoop> I get the error:  ValueError: invalid property value 'branch-nick' for None
[03:48] <NfNitLoop> I'm not sure if that's a bzr error or bzr-svn.
[03:51] <poolie> NfNitLoop: can you put the traceback from ~/.bzr.log into a new bug please?
[03:51] <NfNitLoop> ok.   for bzr alone?
[04:05] <poolie> for the command that gave you the error
[04:05] <NfNitLoop> er, well, it was just 'bzr', but I'm not sure if it's the interaction with svn that cause it.
[04:05] <NfNitLoop> in any event, the bug is here:  https://bugs.launchpad.net/bzr/+bug/293440
[04:49] <NfNitLoop> Wow.
[04:49] <NfNitLoop> I just learned about stacked branches.
[04:49] <NfNitLoop> That's nice!
[04:49] <NfNitLoop> I should keep a closer eye on bzr-land. :)
[04:59] <NfNitLoop> Is there a way, once I've got a stacked branch...
[04:59] <NfNitLoop> to unstack it?
[05:00] <NfNitLoop> sortof like unbind?
[05:01] <lifeless> not really; just branch from it locally without the stacked parameter and it will copy everything
[05:01] <lifeless> there is an internal api
[05:01] <NfNitLoop> Yeah, I just tried that...
[05:01] <lifeless> bt, its internal:P
[05:01] <NfNitLoop> and it didn't go very well. :p
[05:01] <lifeless> oh? it should work, what went wrong
[05:01] <NfNitLoop> NotImplementedError: <bound method VirtualInventoryTexts.iter_lines_added_or_present_in_keys of <bzrlib.plugins.svn.versionedfiles.VirtualInventoryTexts object at 0x13d48f0>>
[05:02] <lifeless> file a bzr-svn bug for that
[05:04] <NfNitLoop> it *did* warn me that stacking was experimental in bzr-svn. :p
[05:18] <cerw> hi there
[05:19] <cerw> can i make a copy (branch) from current repository, but stariung by soe REVISION? i dont want to keep the whole repo..
[05:34] <jkakar> I'm trying to merge a branch and getting this error: http://paste.ubuntu.com/67126/
[05:34] <jkakar> Any suggestions on how to proceed?
[05:34] <mkanat> Is there an "up and revert in one command" command?
[05:50] <poolie> mkanat: no
[05:51] <poolie> jkakar: :/ sorry for the bad message
[05:51] <poolie> one of them is a rich-root repository probably
[05:51] <poolie> bzr info will tell you
[05:51] <poolie> upgrade the other one to 1.9-rich-root
[05:52] <spiv> And "bzr info -v" will tell you if "bzr info" just says "unnamed".
[05:58] <poolie> that is getting to the top of my shit list
[07:00] <vila> hi all
[07:06] <spiv> vila: hi
[09:20] <SuperMMX> hi, guys, is it possible to add hooks only for a specific branch ?
[09:36] <matkor> Hi ! What would be better (faster over slow network) for distributing mostly RO version of given branch ? checkout ? --lightweight checkout ? else ?
[09:38] <AfC> Well, a lightweight checkout will only work if you have real time access (over your network) to the actual branch, wherever it is.
[09:44] <matkor> AfC: I have branches spread over vpn ... but find doing bzr update (over plain checkout) long process, I wonder if there is way to speed it up ...
[09:44] <matkor> I am using sftp://
[09:44] <Peng_> Using bzr+ssh would be faster.
[09:44] <Peng_> You should make sure you're using the latest version of bzr you can, and that your branches aren't in the old knit format.
[09:45] <Peng_> Other than that, there's not much you can do.
[09:45] <AfC> Yeah, I wouldn't particularly expect sftp:// to be fast for much of anything.
[09:46] <matkor> Peng_: I will switch to bzr+ssh than .. I think I follow all upgrade suggestions seen in bzr CLI , so I suspect I am up to date in terms of branches format ...
[09:46] <AfC> I mean, sure, if your VPN never breaks and has really low latency and is really fat, then sure, run lightweight. But it sounds like you have the opposite than, that which is *just* the situation where you want to have full (distributed version control) branch information locally. So, {shrug}
[10:14] <matkor> AfC: Mostly what I do is bzr update (downloading newer version) over VPN, really really rarely  I need history or make comit ...
[10:15] <AfC> matkor: do you do `bzr status` and `bzr diff`?
[10:16] <matkor> AfC: yes
[10:16] <matkor> and bzr missing <remote>
[10:17] <matkor> in --lightweight checkout it's not possible withou network connection ?
[10:17] <AfC> As I understand it, no.
[10:18] <AfC> The whole point of distributed version control is to get the data to the other side of the bottleneck.
[10:19] <AfC> and like I said, if you're complaining about your VPN's speed...
[10:19] <AfC> But more to the point, why don't you try all this yourself and see?
[10:19] <matkor> mhmm... OK so will switch to bzr+ssh and see if it helped with my feelings.  If it works acceptably for you, then fine.
[10:20] <AfC> I certainly would *NEVER* recommend this sort of thing to anyone, but I believe strongly in the premises of decentralized version control and the value of having full history somewhere locally.
[10:21] <AfC> So what you're asking about is really somewhat anathema. That Bazaar supports it all has always struck me as ... strange ... but hey.
[12:41] <jelmer> lifeless, ping?
[14:11] <Flimm> Hello, I'm using Launchpad to host my bazaar branch
[14:11] <Flimm> How can my friend download any commits I make to his computer?
[14:11] <Flimm> This is the method I'm using now:
[14:11] <Flimm> bzr branch lp:epidermis
[14:12] <Flimm> Then whenever I commit and push, my friend does
[14:12] <Flimm> bzr revert
[14:12] <Flimm> bzr pull lp:epidermis
[14:14] <beuno> Flimm, why does he revert?
[14:14] <beuno> he can emrge from your branch
[14:14] <beuno> *merge
[14:16] <Flimm> merge doesn't auto commit though
[14:16] <Flimm> and I don't want him to deal with any conflicts in case he has edited the files
[14:16] <beuno> no, you commit after you merge
[14:17] <beuno> I don't understand
[14:17] <Flimm> pull automatically commits the way I commited, which I like
[14:17] <beuno> well, he can pull to a separate branch
[14:18] <Flimm> By why should he make a separate branch every time I commit?
[14:20] <Flimm> he reverts in order to undo any changes he might have made
[14:23] <beuno> Flimm, he can keep a seperate branch with the mainline
[14:23] <beuno> and one he works on
[14:24] <beuno> why would he have to loose his changes every time you commit?
[14:24] <Flimm> He's not contributing any code at all, he's just testing the code
[14:25] <beuno> uhm
[14:25] <beuno> ok
[14:25] <beuno> so, what's the problem
[14:34] <Flimm> I just wondering if that was the recommended approach, beuno
[14:35] <beuno> Flimm, well, I suppose if someone doesn'really doesn't want to play with a branch in parallel, and really will never commit, etc etc etc, then reverting all the time sounds about right
[14:35] <beuno> you could potentially also use pull --overwrite
[14:35] <beuno> but this is a bit of an odd use case I think
[14:41] <nogden> hey people, does anyone else have a problem installing bzr-svn in kubuntu interpid?
[14:41] <nogden> using the launchpad ppa for stable releases at the moment
[14:43] <nogden> seems that bzr version installed is 1.8-1 and bzr-svn expects 1.8 any ideas of a workaround?
[14:47] <Peng_> Where are you installing bzr-svn from?
[14:48] <nogden> I'm assuming it comes from the same ppa does it not?
[14:49] <nogden> or is there a seperate one for the plugin?
[14:49] <Peng_> Oh, I didn't know it was in the PPA again.
[14:49] <Peng_> Sorry, I can't help then.
[14:49] <nogden> ah, my mistake.... it isn't
[14:49] <nogden> it's in universe/devel
[14:51] <Peng_> Oh.
[14:53] <nogden> hmmm, acording to launchpad bzr-svn 0.4.13-2 (the version in universe/devel) just required bzr >= 1.6
[14:54] <nogden> now I'm running bzr 1.8-1 from the launchpad ppa but there seems to be an issue
[14:55] <nogden> ah, apt reports that it depends on bzr < 1.8
[14:58] <nogden> hmmm, looks like a manual install... grrr
[14:59] <nogden> ah, packages available in deb http://samba.org/~jelmer/debian/ unstable/
[16:01] <abentley> jam:ping
[16:05] <asabil> could someone please update the bzr-svn in ppa ?
[16:05] <asabil> to disable the bzr (<1.8)
[16:36] <disturbedsaint> markh I've updated the wiki page about tbzr, hope it's OK
[17:18] <Kinnison> Anyone here know of an issue pushing to a knit repository over sftp with current bzr.dev ?
[17:20] <Kinnison> specifically something which looks a bit like this: http://rafb.net/p/Tbug8Y55.html
[17:39] <gour> nice, bzr-gtk-0.95 does not crash with bzr-trunk as 0.94
[18:20] <LeoNerd> Has anyone written a bzrfs fuse module yet?
[18:20] <james_w> LeoNerd: yeah, there's one around
[18:21] <james_w> don't know if it's been kept up to date
[18:22] <gour> oops, 1.10dev is crashing here - http://rafb.net/p/dm1VJO45.html
[18:28] <Peng_> gour: Eh? Was that a change you made?
[18:28] <Peng_> gour: You should use "hashlib.md5", not "hashlib.new".
[18:29] <james_w> Kinnison: I haven't, I think it's bug time for you.
[18:29] <gour> Peng_: hmm. maybe it's bette to rm search plugin, until it's ready
[18:32] <Peng_> gour: Actually, use bzrlib.osutils.md5().
[18:32] <gour> Peng_: what about this one - http://rafb.net/p/Tdc42F61.html bzr-gtk & bzr-dev ? (i fixed it by upgrade to 0.95)
[18:33] <gour> Peng_: it's better that i become more familiar with python's standard lib before 'fixing blindly'
[18:33] <Peng_> gour: That one I don't know.
[18:44] <Peng_> gour: Well, http://bzr.mattnordhoff.com/loggerhead/bzr-search/py2.6/ should fix the md5 issue, but there might be others.
[18:44] <Peng_> (I don't have Python 2.6 to test myself.)
[18:45] <Peng_> gour: (And it also ruins compatibility with older versions of bzr. :P )
[18:58] <Kinnison> james_w: *pout*
[19:01] <Kinnison> filed as https://bugs.launchpad.net/bzr/+bug/293746
[19:01] <james_w> thanks
[19:14] <gour> Peng_: yes...pkgs need to (slowly) migrate to 2.6...soon there will be even 3.0
[19:39] <mDuff> Does the 1.9rc1 standalone win32 installer include bzr-svn, or did I have an old copy of that hanging around from somewhere?
[19:50] <ja1> abentley: sorry about the delay, are you still around?
[19:50] <abentley> Yeah.
[19:51] <abentley> ja1: Are you okay with me merging the shelf ui with the changes I sent?
[19:51] <jam> yeah
[19:51] <jam> I thought that was clear enough in the last email. Plus I gave you "tweak" anyway.
[19:52] <jam> markh: I had a question about getting paramiko into the installers. Are you doing something special to have it happen?
[19:52] <abentley> jam: I still figure that "tweak" doesn't count if you don't make all the changes suggested, and I haven't changed the use of bzrtools yet.
[19:53] <jam> abentley: I said that was "weird" but that "we may not have anything better"
[19:53] <jam> I was more bringing up the discussion than asking for a change
[19:54] <abentley> jam: Okay, but I said "Is this something you want fixed before this lands?" and you didn't reply.
[19:55] <jam> I probably missed that part
[19:55] <jam> sorry
[19:55] <abentley> np
[19:55] <abentley> In terms of discussion, do you have an idea what we should do?
[19:56] <jam> luks: I had a question about qbzr, if you have time
[19:56] <luks> jam: sure
[19:56] <jam> I'm trying to make sure I bundled the right version
[19:56] <jam> but I didn't see an 0.9.5 tag in the trunk repo
[19:56] <jam> do you know if it was added?
[19:57] <luks> um, I don't know, alexander did the release, but I can check
[19:57] <luks> but it's probably always safest to grab the tarball
[19:58] <jam> luks: I just saw this:
[19:58] <jam>   521 Alexander Belchenko       2008-11-03 [merge]
[19:58] <jam>       merge 0.9.5 release
[19:58] <jam> And I'd rather not have to download tarballs for everything for every release
[19:58] <jam> it is easier to do a "bzr branch -r tag:..." when necessary
[19:58] <luks> yes, the tag seems to be in the m erged branch
[19:58] <luks> release-X.Y.Z as usual
[20:10] <abentley> thumper: How's it going?
[20:10] <thumper> morning abentley
[20:11] <thumper> still knackered
[20:11] <thumper> but not as bad as yesterday
[20:11] <abentley> thumper: Progress is progress, I guess.
[20:11] <thumper> abentley: do you know when 1.9 release is?
[20:12] <abentley> thumper: Bazaar 1.9?  No, not offhand.
[20:12] <abentley> thumper: Probably this week, though.
[20:12]  * thumper nods
[20:13] <jam> thumper: 1.9rc1 was 2008-10-31, so 1.9 would be expected on 2008-11-07
[20:13] <thumper> thanks jam
[21:02] <NfNitLoop> Hrmmm.
[21:03] <NfNitLoop> bzr-svn seems to *explode* in memory usage when I try to pull one particular revision in particular.
[21:03] <NfNitLoop> even though only a few lines were changed.
[21:03] <NfNitLoop> The only thing I can see is that the lines are really long?
[21:04] <lifeless> NfNitLoop: gigabytes long?
[21:04] <NfNitLoop> (811 characters)
[21:04] <NfNitLoop> no. :)
[21:04] <lifeless> how big are the files these lines are in?
[21:04] <NfNitLoop> hmm, not too big, I don't think, let me see...
[21:06] <NfNitLoop> heh.
[21:06] <NfNitLoop> 20k.
[21:06] <lifeless> no alarm bells so far
[21:07] <NfNitLoop> still, I can `bzr pull -r 510`, but `bzr pull -r 511`  nearly brings down my laptop.
[21:07] <NfNitLoop> Unfortunately this against our non-public repo... trying to figure out how to reproduce this.
[21:08] <NfNitLoop> Ooooh, wait.
[21:08] <ianm_> is it easy to step back in time through commits?
[21:08] <NfNitLoop> -r 511 might not necessarily be (svn)r511, eh?
[21:09] <NfNitLoop> since I'm only grabbing one of the sub-projects?
[21:09] <mDuff> ianm_, the short answer is "yes"; the long answer is "what, exactly, do you mean by that?"
[21:09] <ianm_> mDuff: I see this when I start my app: Gtk-CRITICAL **:gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
[21:10] <mDuff> ianm_, trying to figure out at what poit that issue was reproduced?
[21:10] <ianm_> mDuff: right
[21:10] <ianm_> it was recent
[21:10] <mDuff> ianm_, you might find the bzr-bisect plugin interesting.
[21:10] <NfNitLoop> aha, yes, it's a different revision in svn... which appears to be huge. :p   that makes more sense.
[21:11] <ianm_> is there anything like "bzr previous" that I can do repeatedly until the warning disappears?
[21:12] <NfNitLoop> ianm_: There's "uncommit"... but make sure you do it in a branch. :p  (it uncommits and discards your history one revision at a time)
[21:12] <NfNitLoop> ianm_: bisect may help you.
[21:12] <NfNitLoop> it does a binary search through your revisions. :)
[21:12] <NfNitLoop> maybe faster than doing it 1 at a time.
[21:13] <ianm_> it must be within the last 20 commits
[21:13] <ianm_> so I currently have a working directory where when I commit it also pushes to launchpad
[21:14] <mDuff> ianm_, bisect really is the right tool for the job; otherwise, you're just doing "bzr co -r [number]" or some variant thereof.
[21:14] <ianm_> can I "bzr branch /that/directory" then use bzr uncommit there?
[21:14] <mDuff> ianm_, checkout -r [number] is really more the right tool than branch+uncommit
[21:15] <ianm_> mDuff: hmm ok.  can I do that locally?  a launchpad checkout takes like 5 minutes
[21:15] <mDuff> ianm_, yes, that's a local operation
[21:15] <mDuff> ianm_, do it within your existing tree
[21:16] <ianm_> mDuff: all within my one working directory?
[21:16] <mDuff> ianm_, well, you can just do a lightweight checkout of a specific revision into a different directory... that'd probably be the fastest+safest approach
[21:17] <ianm_> mDuff: yeah that sounds good.  how do you do a lightweight?
[21:17] <NfNitLoop> branch --lightweight
[21:17] <NfNitLoop> uhrmm... but don't uncommit from there. :)
[21:17] <NfNitLoop> (does that work from a lightweight co, even?)
[21:19] <mDuff> ianm_, ie. bzr checkout --lightweight -r7 ~/myproject ~/myproject.r7
[21:19] <mDuff> ianm_, ...but really, bisect is The Right Tool.
[21:19] <ianm_> is bisect easy to setup?
[21:20] <mDuff> ianm_, you should be able to just check it out into your ~/.bazaar/plugins/ directory
[21:20] <NfNitLoop> lifeless: aha.  Yep, turns out that someone had checked in a 1G file.  Sooo, guess that repo's not a good use-case for bzr. :p
[21:20] <mDuff> ianm, bzr co http://bzr.licquia.org/bzr-bisect/trunk/ ~/.bazaar/plugins/bisect
[21:21] <mDuff> ianm_, then see "bzr bisect --help".
[21:23] <lifeless> NfNitLoop: we're working on that, but yeah, youll need a couple of gb to check it out today
[21:25] <NfNitLoop> I've got 2G RAM...
[21:25] <NfNitLoop> so it looks like I'll need more than a couple. :p
[21:25] <ianm_> mDuff: I found the commit, now I just have to figure out what's wrong about the glade file change, ugh ;)
[21:26] <ianm_> mDuff, NfNitLoop: thanks for your help!
[21:26] <mDuff> ianm_, cool. bisect is nifty, eh? :)
[21:27] <ianm_> I actually just did a bunch of local co -r but I imagine it is ;)
[22:10] <lifeless> spiv: so, I would guess a mis-selection on pushing (CHKRepository, RemoteRepository)
[22:11] <lifeless> spiv: which new repositories avoid because of sprout getting delegated to the FS level
[22:12] <poolie> lifeless: hi
[22:12] <poolie> my net access seems to be up but flaky
[22:12] <lifeless> poolie: cool; we did a standup
[22:12] <poolie> good for you
[22:12] <lifeless> poolie: I mailed the notes to the list
[22:13] <poolie> i would have said: i did everyone's reviews; today i'm going to fix the internet ;-) and then i think try inter-historic-tree diffs in CHK
[22:13] <poolie> also, that needs a better name
[22:13] <lifeless> true
[22:18] <jam> poolie: I built a new win32 installer today, learning from user feedback. I'm wondering if I should completely remove the old installer, or if just naming the new one "-2" is sufficient?
[22:18] <poolie> is there any benefit to keeping the old one?
[22:18] <poolie> i can't see any
[22:19] <poolie> unless someone wants to compare its bugs or something, and if we really want that you still have a copy
[22:19] <poolie> i would call the new one -2 or something though
[22:19] <poolie> to make it clear
[22:20] <poolie> how about that?
[22:21] <jam> yeah, I'm calling it -2, I just wondered about deleting the old download file
[22:21] <jam> probably best  to delete it so we don't have people wondering which one to grab
[22:22] <poolie> just delete it
[22:22] <jam> I just had LP timeout while trying to upload, which is the first time it happened for me
[22:22] <jam> but hopefully it will go through this time.
[22:22] <jam> poolie: btw, I think the reason that rebooting worked for you is because you have the regular "Subversion" binaries installed
[22:23] <jam> and it just got added to the path as part of the reboot
[22:23] <jam> can you check?
[22:30] <poolie> jam, i'm pretty sure i don't have svn on that machine
[22:31] <poolie> can check
[22:46] <poolie> jam, i don't have svn there
[22:46] <poolie> it's a nearly fresh vm
[22:51] <jam> interesting, considering I'm 90% sure that the dll isn't bundled in that installer.
[22:52] <poolie> what was the name, libsvn-1.dll
[22:52] <jam> libsvn_client-1.dll IIRC
[22:53] <poolie> maybe there is some kind of negative cache
[22:53] <poolie> if you see what i mean
[22:53] <poolie> that bzr-svn *shouldn't* work on this machine, but it's normally failing quietly
[22:53] <poolie> now i'm getting that message again
[22:54] <poolie> jam, if we're shipping the bzr-svn plugin but not the libraries it uses that seems potentially problematic
[22:55] <jam> poolie: yeah, I manually added the libs in the -2 installer
[22:55] <jam> I don't understand why they aren't coming in automatically like all the other ones
[22:55] <poolie> oh i see
[22:56] <jam> And now, I managed to install it, and I get the icon in the systray
[22:56] <jam> but when I run I get:
[22:56] <jam> "ImportError: DLL load failed with error code 193"
[22:56] <jam> not sure what that is yet
[22:56] <poolie> i would guess what we're seeing as a windows vista feature, that if loading a dll fails the user sees a dialog with no intervention from the application
[22:57] <lifeless> the windows runtime linker will show an error if a dll for an .exe can't be found
[22:57] <lifeless> dynamic loading doesn't do this
[22:57] <jam> well, running the 'bzr.exe' directly isn't complaining
[22:57] <jam> (weird network fault)
[22:58] <jam> anyway, bzr-svn seems good in the new install
[22:58] <poolie> well, that's not consistent with what we're seeing here
[22:58] <jam> I don't know why TortoiseBZR is failing to run the "settings" page
[22:58] <poolie> jam, i'll try it out
[22:58] <lifeless> jam: PATH may not match between the console and gui environments
[22:58] <lifeless> jam: try logging the user out and in?
[22:58] <jam> could be. I explicitly chose not to add 'Bazaar' to my path, because I wanted to unistall
[22:58] <poolie> jam, i could run the settings from the tray icon
[22:59] <poolie> i did add it to my path
[22:59] <jam> ok, so it might just be that
[23:02] <poolie> i'm waiting for more windows updates :/
[23:02] <poolie> after that i'll upgrade it
[23:09] <lifeless> garh, its summer
[23:09] <lifeless> I can tell because the noise pollution is insane
[23:09] <poolie> barely
[23:19] <disturbedsaint> markh, are you there?
[23:19] <markh> disturbedsaint: hi
[23:19] <disturbedsaint> hi
[23:20] <disturbedsaint> was wondering if the different menu's when clicking on the tray-icon work for you
[23:20] <disturbedsaint> seems like tbzr has to be in the global PYTHONPATH
[23:21] <markh> umm - that is possible for the tbzrcache process actually
[23:21] <markh> but just start it manually and you will be OK
[23:22] <poolie> so if you give a lp: url, it's the resolved form of that url that's remembered as the parent etc?
[23:22] <james_w> poolie: yeah
[23:22] <james_w> Aaron recently proposed to change that I believe
[23:22] <disturbedsaint> markh, when launching from the command prompt it does indeed work
[23:23] <disturbedsaint> just wanted to know if it's intentional the way it is
[23:23] <markh> it would be possible to hack the shell extnesion code to set PYTHONPATH before launching the tbzrcache process
[23:23] <markh> and its not a problem in a binary build
[23:23] <james_w> the only downside I can thing of is that you need whatever directory service plugin installed to be able to resolve the parent, but I don't think that's too onerous
[23:24] <markh> while I'm developing, I always run tbzrcache manually so I can see the output
[23:24] <james_w> poolie: I met with Mark, some of lp-code, and others last week. Something like Russell's issue came up, and Mark was talking about how we could try and improve this.
[23:25] <disturbedsaint> if it isnt a problem in the binary builds then it's fine :)
[23:25] <james_w> he suggested storing both what the user asked for, and what they got, which allows you to later make decisions about what you should do
[23:25] <poolie> james_w: the problem of people renaming branches?
[23:25] <james_w> not only when branches move, but when they diverge and the like
[23:26] <james_w> poolie: it was actually forks in development, but I think it still applies
[23:26] <james_w> the UI for presenting this to the user and finding out what action they wanted to take wasn't discussed, but it's an interesting idea
[23:26] <markh> disturbedsaint: have you ever seen a "would recurse to death" error?  If so, try updating the tbzr branch - I think I nailed that a couple of days ago.
[23:26] <james_w> and would probably help in some situations
[23:27] <markh> bb in 20
[23:27] <disturbedsaint> actually I haven't
[23:27] <disturbedsaint> though I do seem to lose the overlays on directories after a while
[23:27] <disturbedsaint> still trying to find out why that happens
[23:27] <james_w> poolie: thumper and jml were there, and they might have a different of how this was supposed to work, or what it was supposed to solve.
[23:27] <disturbedsaint> Like bug 284511 (https://bugs.launchpad.net/tortoisebzr/+bug/284511)
[23:28] <disturbedsaint> Thats the only real issue I'm having atm
[23:33] <thumper> james_w: what was the question?
[23:36] <poolie> hi thumper
[23:36] <poolie> we should talk sometime
[23:36] <thumper> hi poolie
[23:36]  * thumper needs coffee badly
[23:36] <poolie> :)
[23:36] <thumper> poolie: how about we talk this afternoon?
[23:36] <poolie> yay jetlag
[23:36] <poolie> sure
[23:36] <thumper> I'm about to go and get coffee
[23:36] <poolie> are you home now?
[23:36] <thumper> yes
[23:36] <thumper> it snowed here!
[23:42] <markh> disturbedsaint: when that happens check .bzr.log - you should find an error there - and most likely is the "would recurse to death" error.
[23:44] <disturbedsaint> markh: happened the last time 1,5hours ago
[23:45] <disturbedsaint> But I got the source (branch) about 7 hours ago, so maybe there's another reason for it happening
[23:45] <disturbedsaint> The error is "raise RuntimeError("Status of '%s' would recurse to death" % member)"
[23:49] <markh> disturbedsaint: I only pushed it minutes ago :)
[23:49] <markh> that is the error I think is now fixed
[23:50] <disturbedsaint> ah, I see :)
[23:59] <disturbedsaint> markh, I'll give it a try tomorrow


[02:13] <Admiral_Chicago_> hey there j1mc
[02:16] <j1mc> heya, Admiral_Chicago_
[02:16] <jjesse> evening
[02:16] <j1mc> hi jjesse
[02:16] <jjesse> hiya j1mc
[02:16] <j1mc> a lot of people in this channel saying hello this evening.  :)
[02:16] <jjesse> :)
[02:17] <j1mc> jjesse: fijam asked a bunch of questions on the channel earlier today... i'm not sure if he got a response.  did you see those questions, and if he got a response?
[02:19] <jjesse> hmm didn't see the questions
[02:19] <j1mc> np... i think he was going to ask on the ml
[02:20] <jjesse> are you in chicago as well j1mc?
[02:20] <jjesse> nixternal and Admiral_Chicago_ looks like i might be comming back to chicago for a week in july we sould get together again
[02:23] <Admiral_Chicago_> jjesse: definetly
[02:23] <Admiral_Chicago_> jjesse: j1mc is in chicago as well. he is sitting next to me now
[02:23] <jjesse> awesome, i'll let the two of you know when exactly so we can do another meet up again
[02:24] <Admiral_Chicago_> awesome
[02:24] <jjesse> my boss didn't even question the "company" dinner we had together :)
[02:24] <Admiral_Chicago_> we are hacking on docs: perhaps you can answer a question
[02:24] <jjesse> i can sure try
[02:24] <Admiral_Chicago_> let me pastebin it
[02:25] <Admiral_Chicago_> http://pastebin.ca/594581
[02:25] <Admiral_Chicago_> so i'm looking for the proper way to refrence the terminal in the docs
[02:25] <j1mc> jjesse: cool.  it would be good to meet you.
[02:25] <Admiral_Chicago_> wouldn't it be Applications  >> accessories >> terminal
[02:25] <jjesse> j1mc: yeah it will be nice
[02:26] <Admiral_Chicago_> it seems lke there are two ways to refence the terminal in docbook, not sure which  way to do it
[02:26] <Admiral_Chicago_> nixternal: feel free to answer that question
[02:26] <jjesse> is it referenced both ways in our documents?
[02:26] <Admiral_Chicago_> not sure, I haven't looked at all the docs
[02:26] <Admiral_Chicago_> i've seen it both ways in teh kubuntu docs
[02:28] <jjesse> hmm then we should standarize and file bugs to get it solved
[02:28] <jjesse> wow saw an article the 1st year of an iPhone will run you $1936
[02:28] <Admiral_Chicago_> dang.
[02:29] <jjesse> i think it should be Applications >> Asscesories >> Terminal
[02:29] <jjesse> that includes data and voice plans
[02:29] <Admiral_Chicago_> i seem to remember there being discussion in doc ML
[02:29] <jjesse> i thought so too, try the gmane archives?
[02:29] <Admiral_Chicago_> looking now
[02:30] <jjesse> is Rich still in class?
[02:30] <Admiral_Chicago_> https://lists.ubuntu.com/archives/ubuntu-doc/2007-May/008493.html
[02:30] <Admiral_Chicago_> not sure
[02:30] <greg_g> So, I just had to uninstall the kubuntu-desktop meta package along with everything else.  The first link from google when searching for "uninstall kubuntu-desktop" is this: http://doc.gwos.org/index.php/Uninstall_kubuntu-desktop
[02:31] <greg_g> I added my information there for Fiesty, but was wondering if you wanted to use it for the ubuntu wiki
[02:31] <jjesse> Admiral_Chicago_: i acutally prefer the 2nd choice
[02:31] <Admiral_Chicago_> as do i, makes it easier to visualize the navigation
[02:32] <jjesse> but mdke_ has the final answer because of the entity it is defined
[02:32] <jjesse> do you have an xubuntu-menus-C.ent?
[02:32] <Admiral_Chicago_> uh thats a good question
[02:32] <jjesse> or are you using the gnome-menus-C.ent
[02:32] <Admiral_Chicago_> i don't know what that is
[02:33] <jjesse> if you read: https://lists.ubuntu.com/archives/ubuntu-doc/2007-May/008501.html
[02:33] <Admiral_Chicago_> how can I check.
[02:33] <jjesse> you see that the gnome-menus-C.ent lists entities for gnome
[02:33] <Admiral_Chicago_> ah okay
[02:33] <Admiral_Chicago_> let me navigate the docs for a sec
[02:34] <jjesse> ok in /trunk/xubuntu/libs there is a xubuntu.ent, and there is also the gnome-munus-C.ent
[02:34] <jjesse> so now you can reference whatever is in any of those as long as your xml includes those files
[02:35] <jjesse> looks like in xubuntu.ent there is an entity for for terminal already
[02:35] <jjesse> <!ENTITY terminal '<menuchoice><guimenu>Applications</guimenu><guimenuitem>System</guimenuitem><guimenuitem>Terminal</guimenuitem></menuchoice>'>
[02:36] <Admiral_Chicago_> i'm in /libs but don't see the xubuntu.ent
[02:36] <Admiral_Chicago_> ah i see it
[02:36] <Admiral_Chicago_> okay col
[02:38] <greg_g> Am I in the correct channel for my inquiry?
[02:38] <greg_g> (is only trying to help, I saw a need and I am trying to fix it)
[02:39] <Admiral_Chicago_> jjesse: http://pastebin.ca/594618
[02:39] <jjesse> greg_g: sorry let me read scroll
[02:39] <Admiral_Chicago_> what do you think of those edits?
[02:40] <jjesse> if you use &terminal; it should build out all of <!ENTITY terminal '<menuchoice><guimenu>Applications</guimenu><guimenuitem>System</guimenuitem><guimenuitem>Terminal</guimenuitem></menuchoice>'> when you go to build it
[02:40] <jjesse> that's the beauty of entities
[02:41] <greg_g> I am thinking of editing this page to include removal in Fiesty: https://help.ubuntu.com/community/FromUbuntuToKubuntu
[02:42] <jjesse> sounds good to me greg_g
[02:42] <greg_g> thanks jjesse, since this is my first time contributing to the help wiki, I thought it would be best to make sure I had the right idea.
[02:43] <jjesse> greg_g: to be honest i usually do it and ask for forgiveness later :)
[02:44] <greg_g> either way I guess :)
[02:55] <Admiral_Chicago_> grr. okay doc work is frustration after all
[02:55] <jjesse> yes yes it is :)
[02:55] <jjesse> did it not work correct w/ the entitY?
[02:56] <Admiral_Chicago_> well i haven't tried that yet
[02:57] <Admiral_Chicago_> but i find section and section and section
[02:57] <Admiral_Chicago_> like i started video then there was video one, two, three...
[02:57] <Admiral_Chicago_> jjesse: would you mind looking at my diff in a second
[02:58] <jjesse> Admiral_Chicago_: sure
[02:58] <Admiral_Chicago_> email address?
[02:59] <Admiral_Chicago_> jjesse at ubuntu dot com?
[02:59] <jjesse> yes sir
[03:03] <j1mc> when i try to validate a feisty .pot file after fixing a bug, i get an error: http://pastebin.ca/594649
[03:03] <jjesse> ok heading out to walk the dog
[03:03] <jjesse> be back in a bit
[03:03] <j1mc> i didn't change that... :)  is that an error, or should i not worry?
[03:03] <j1mc> ok, jjesse
[03:04] <nixternal> what is all of this work going on for? to much work for the doc channel
[03:04] <nixternal> to much noise
[03:05] <nixternal> j1mc: you don't validate .pot files
[03:05] <nixternal> the validate script is only for .xml files
[03:05] <j1mc> yessss... ok thanks.
[03:05] <nixternal> you don't manually edit .pot files either
[03:05] <j1mc> you don't?  why not?
[03:05] <nixternal> there is a script that automatically generates them
[03:05] <nixternal> pot files are automatically generated
[03:05] <nixternal> xml2po
[03:06] <j1mc> how do i know where the error came from then?
[03:07] <nixternal> what error?
[03:07] <nixternal> the error in pastebin?
[03:07] <j1mc> https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/122713
[03:07] <ubotu> Launchpad bug 122713 in xubuntu-docs "Path in xubuntu documentation does not match true situation" [Undecided,Confirmed]
[03:07] <j1mc> !botsnack
[03:07] <ubotu> Yum! Err, I mean, APT!
[03:08] <nixternal> j1mc: you recreate all of the pot files and then create a new xubuntu docs package, get it uploaded, and rosetta will grab the new pot files
[03:09] <nixternal> j1mc: as long as you have fixed it in the .xml, mark it as fix committed once you have sent in the patch and it gets uploaded
[03:09] <nixternal> and why he is just now noticing this issue is beyond me
[03:10] <nixternal> that should have been noticed probably back in Dapper, if not Edgy or Feisty, that's how old that error probably is
[03:11] <j1mc> i don't even see it in the desktopguide.  it's only in the pot file
[03:11] <j1mc> it's not in the xml...
[03:15] <j1mc> do you think maybe the pot file wasn't regenerated for feisty?
[03:16] <Admiral_Chicago_> sent to jjesse, j1mc, and nixternal
[03:20] <j1mc> ./vilidate.sh /pathto/file.xml
[03:31] <jjesse> Admiral_Chicago_:  did you figure out the validation problem?
[03:34] <nixternal> j1mc: very well could have happened like that
[03:38] <Admiral_1hicago_> i found the problem
[03:39] <Admiral_1hicago_> well to one validation isssue
[03:39] <Admiral_1hicago_> not sure about the other one
[03:39] <Admiral_1hicago_> nixternal: can i just email you the file I have and you can give me feedback?
[03:39] <Admiral_1hicago_> its a bit hard to work in here...
[03:44] <jjesse> problems Admiral_Chicago?
[03:44] <Admiral_Chicago_> yea, they changed the key on the wireless network.
[03:44] <Admiral_Chicago_> jjesse: my documentation isn't validating....
[03:44] <Admiral_Chicago_> i can't figure out where....
[03:45] <jjesse> that's a bummer
[03:45] <jjesse> i've spent a long time trying to get mine to validate
[03:45] <jjesse> i need to work on validating my adept documentation
[03:48] <jjesse> i think validation is the hardest part of working on documentation
[03:49] <j1mc> nixternal: the problem was in the /docs-ubuntu/feisty/xubuntu/libs/xubuntu.ent file, so it took me a bit to track that down.
[03:49] <j1mc> docs-ubuntu is my own folder name... but it's in the feisty branch.  :)
[03:50] <j1mc> i've submitted a patch via the bug report, but i think they'll need to rebuild the pot file.
[03:50] <Admiral_Chicago_> bug # ?
[03:50] <j1mc> that would be the only way to correct it.
[03:51] <jjesse> nixternal: Ping
[03:51] <j1mc> https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/122713
[03:51] <ubotu> Launchpad bug 122713 in xubuntu-docs "Path in xubuntu documentation does not match true situation" [Undecided,Confirmed]
[03:51] <jjesse> nixternal: for my adept documentation when it gets built do i use the kubuntu-docs entities or how does that work?
[03:58] <nixternal> yo yo
[03:58] <nixternal> jjesse: well if it is for Kubuntu then yes, if it is the KDE ones, then using meinproc will cause it to link to the KDE entities correctly
[03:59] <jjesse> umm....
[03:59] <nixternal> Admiral_Chicago_: you sent an email, but no patch, was that meant to be?
[03:59] <jjesse> ok it is the kubuntu specific adept guide
[04:00] <jjesse> nixternal: also did you see i will probablly be in chicago in july
[04:00] <jjesse> for another week
[04:00] <nixternal> wow, this is going to be difficult...if you do one for KDE, we will then have 2 adept manuals
[04:00] <nixternal> jjesse: rock on, make sure you warn me so I am in Michigan that week instead :)
[04:00] <jjesse> nixternal: i know the problem is adept is different ify ou install on debian testing
[04:00] <jjesse> then it is on gutsy
[04:00] <nixternal> same version in Debian though?
[04:01] <nixternal> we do a custom one, that is for sure
[04:01] <Admiral_Chicago_> nixternal: oh yea...
[04:01] <nixternal> maybe we should incorporate it into the installation section of our tbh?
[04:01] <jjesse> nixternal: checking
[04:01] <jjesse> version info that is
[04:02] <nixternal> our installation section will need to get reworked now anyways. We have GDebi-KDE now
[04:02] <jjesse> why the switch from adept to gdebi-kde?
[04:04] <jjesse> afk for a bit, putting wife to bed :)
[04:05] <jjesse> ok back for abit while wife is getting ready, are we moving from adept to something new
[04:08] <nixternal> not switching from adept. gdebi now allows Kubuntu to user the ability to just click a .deb file to install now
[04:08] <jjesse> so how does that affect the way we install packages?
[04:08] <nixternal> whereas before, if they downloaded a debian file, they had to install it via the command line, now they don't
[04:09] <jjesse> so adept is still used?
[04:09] <nixternal> doesn't affect the way we install package at all, it is just an added benefit
[04:09] <nixternal> oh ya, adept is getting something close to a rewrite I believe
[04:09] <jjesse> awesome, before or after i am done documenting it? also who is doing the overhaul?
[04:09] <nixternal> the install section I created wasn't all that great in the first place, so now that I have a base, it will be easy to work with
[04:09] <jjesse> debian version of adept is 2.1 cruiser
[04:09] <nixternal> manchicken and mornfall, and probably after you are done
[04:10] <nixternal> hrmm, Gutsy version is the same
[04:11] <jjesse> intersting, can't find adept in my install of gutsy
[04:11] <Admiral_Chicago_> what about upstream?
[04:11] <nixternal> jjesse: because you did a dist-upgrade maybe? the apt and adept packages conflicted last week and if you installed apt, you removed adept
[04:11] <jjesse> resinstalling kubuntu-desktop
[04:12] <jjesse> ok afk for about 15 minutes now, so manchicken is someone i should contafct then?
[04:12] <jjesse> probablly going to do a whole rewrite of what i have then :(
[04:16] <Admiral_Chicago_> :\
[04:22] <nixternal> jjesse: not a whole rewrite, that would be nuts. But I think there are going to be some "big" internal type changes, and of course the GUI will change. I don't think it passed the KDE usability audits
[04:22] <nixternal> I think I remember seele saying it was horrible. and when she says that, it has meaning since she leads that project (KDE usability) and does that for a living :)
[04:25] <Admiral_Chicago_> be back in a bit...
[04:26] <jjesse> back
[04:26] <jjesse> nixternal: i think you are right, i know it is terrible to use and i  don't know usablity
[04:32] <nixternal> I know it is ugly
[04:33] <nixternal> heck, since dapper there has been that one button that was always grayed out, no functionality, and just now something is getting done about it
[04:33] <jjesse> ok so back to my original question, should i change it to use kubuntu's entities?
[04:34] <nixternal> if it isn't going to be packaged apart of adept, and will be maintained in our repos, I say yes
[04:34] <jjesse> ok so me think this out then, there needs to be an adept guide that ships in kde and there needs to be an adept guide that ships with kubuntu (noting changes kubuntu has made)
[04:38] <nixternal> true
[04:38] <jjesse> so how does that work :)
[04:38] <nixternal> as long as it gets into KDE, I am happy :)
[04:39] <nixternal> oh wait, I will put it in KDE :)
[04:39] <jjesse> :)
[04:39] <nixternal> you should go ahead and get you a SVN account there as well since you are planning on doing some contributing
[04:39] <nixternal> 10 more minutes of this garbage
[04:39] <nixternal> do you have asp.net experience at all? ever used it? ever seen it?
[04:39] <jjesse> ok, i need to remember my gpg to unlock my password to get access back to ubuntu-doc svn
[04:40] <jjesse> asp.net? yeah i've used it before
[04:40] <nixternal> my lord, it is the worse thing I have ever in my life messed with
[04:40] <jjesse> i think i have a asp.net book from MS Press laying around
[04:40] <nixternal> I am sitting in my ASP.NET class
[04:40] <jjesse> bummer to that, i think i'm going to play madden 07
[04:40] <nixternal> I would rather draw images of Microsoft on my thighs with a razer blade
[04:41] <jjesse> are you doing everything in mono?
[04:41] <nixternal> some stuff I have been
[04:41] <nixternal> but so far I haven't been able to get the aspx stuff working correctly with monodevelop
[04:42] <jjesse> ah
[04:42] <nixternal> I need to give that a try again actually..it could have been because I had no clue what I was doing at first
[04:43] <nixternal> oh well, I am going to head home, see y'all later :)
[04:43] <jjesse> l8ter
[06:01] <j1mc> nixternal: i submitted a patch that will fix the bug (# 122713), but the .pot file will need to be regenerated for it to show as fixed to the translators.
[06:02] <j1mc> can i do that?
[06:02] <nixternal> yes
[06:02] <j1mc> is there an app to do it?  what's the name of it?
[06:03] <nixternal> command line :)
[06:03] <nixternal> from trunk/xubuntu
[06:03] <nixternal> which app is this by the way?
[06:03] <j1mc> it's in the feisty branch
[06:03] <nixternal> we have a script that creates them all at once
[06:03] <nixternal> actually, what I would do, is hold off on that...a .pot patch is nothing nice
[06:04] <nixternal> they are tremendous in size
[06:04] <nixternal> we have about 2 months before we create the pots anyways I believe
[06:04] <nixternal> but I don't know, seeing as rosetta is open, it might make sense to run the pots now
[06:05] <j1mc> nixternal: it's a feisty-doc bugfix, though.  the problem may also be in trunk, but this person is trying to translate feisty docs.
[06:06] <nixternal> hrmm...well it probably won't get fixed for feisty, as it isn't life threatening, and getting just that updated would be crazy to get an SRU to go through
[06:07] <j1mc> ah, ok.
[03:57] <fijam> hello
[03:57] <jjesse> hello
[06:34] <fijam> hi
[06:36] <nixternal> Kubuntu docs are switching to GPLv3! ;p
[06:36] <nixternal> hi fijam
[10:00] <ubotu> New bug: #50707 in sun-java5 (multiverse) "JDK docs not listed in yelp" [Low,Incomplete]  https://launchpad.net/bugs/50707
[10:01] <nixternal> oh wow, and that is our fault how?
[10:01] <nixternal> that is because JDK docs are to be looked at with a browser
[10:04] <nixternal> not our problem anymore..all they did was subscribe us thankfully
[11:33] <bdmurray> nixternal: that was my bad then I figured you were more knowledgable about yelp
[11:33] <nixternal> oh...hehe
[11:34] <nixternal> the JDK docs are meant to be read from a browser...I know because I use them almost daily now
[11:34] <nixternal> to get them in Yelp, the package would have to create a .desktop file and put it where ever Yelp looks..I think..I know that is how I would do it for KHelpCenter
[11:35] <bdmurray> Well, I guess I was right to a degree - you did know more than me.
[11:35] <nixternal> hehe
[11:35] <nixternal> I am sure mdke_ or LaserJock would know better though with Yelp
[11:35] <bdmurray> by the way do you know who the mythical wiki admins are?
[11:36] <nixternal> I used to, but I think they have since left the company
[11:36] <nixternal> I don't even know who the main admin is even more
[11:36] <nixternal> I used to think kiko, but I guess he is more LP than anything else
[11:37] <nixternal> that Java bug though, we need to see if we can get it fixed for Gutsy maybe...I need to yell, I mean speak at the current Java package anyways :)
[11:51] <jjesse> hello
[11:52] <jjesse> may i recomend timbuktu big block red
[11:52] <jjesse> its a great wine :)
[12:06] <nixternal> hehe
[12:06] <nixternal> isn't it to early to be drinking?
[12:06] <jjesse> nope, cooking dinner
[12:06] <jjesse> its 6pm
[12:06] <nixternal> oh ya, 6 there :)
[12:07] <nixternal> I am getting ready to head up to timbuktu
[12:07] <jjesse> yeah?
[12:07] <nixternal> well at least where my aunt lives out in the boontoolies
[12:12] <jjesse> boondocks?
[12:14] <mpt> nixternal, you're in Mali?
[12:15] <nixternal> worse, Chicago :)
[12:15] <mpt> wow, good luck with that "swim across the Atlantic Ocean" step
[12:15] <mpt> ;-)
[12:15] <nixternal> mpt: timbuktu is a word us silly americans use to reference "out in the middle of nowhere" kind of
[12:16] <nixternal> or somewhere far away that I have no clue about
[12:16] <nixternal> speaking of that "swim across the Atlantic..." I just read about a guy who has done it
[12:16] <jjesse> what?
[12:16] <nixternal> ya, let me find the link
[12:16] <mpt> nixternal, same here, but it's fun to flummox people by referring to the real one
[12:17] <nixternal> and that you did :)


[05:20] <hikiko> Hi
[06:33] <halivingston> hey folks, I just tried the "alleged" final ISO and tried running the desktop under Microsoft HyperV and it installs fine, but on login after you enter your credentials the background just stays there and nothing happens ... but my CPU usage on HyperV Manager says 10%
[06:34] <halivingston> do you know if you guys tested this scenario? It used to work in beta2.
[09:47] <seb128> good morning desktopers
[09:52] <seb128> pitti, isn't bug #1572863 a feature? what language did you pick? I though didrocks changed seeded complete support for the main locales with the goal to get ride of the "incomplete" dialog on login
[09:52] <ubot5`> bug 1572863 in language-selector (Ubuntu) "no "incomplete language support" note in offline xenial install" [Undecided,New] https://launchpad.net/bugs/1572863
[09:53] <seb128> changes*
[09:58] <pitti> seb128: no, check-language-support still gives me two metric tons of dictionaries and stuff, I only have the langpacks installed
[09:58] <willcooke> morning all
[09:58] <seb128> weird
[09:58] <seb128> hey willcooke
[09:58] <pitti> seb128: well, maybe that is by design now, but that's not what the ISO test case says
[09:59] <pitti> and I'd like to have German spell checking :)
[09:59] <seb128> pitti, hunspell-de-* are on the iso
[09:59] <seb128> as is hyphen-de
[10:02] <willcooke> desktoppers - ISO test please:  http://iso.qa.ubuntu.com/qatracker/milestones/359/builds
[10:04] <willcooke> desktoppers - for desktop a quick smoke test.  Also look at flavours which don't have as many test runs
[10:05] <davmor2> willcooke: I done broked it already :(
[10:05] <davmor2> http://people.canonical.com/~davmor2/desktop-screenshots/wifi-broken.png
[10:06] <willcooke> noooo
[10:06] <willcooke> driver issue?
[10:06] <willcooke> or more wide than that?
[10:06] <seb128> davmor2, move out of the wood back to civilization?
[10:07] <seb128> joke aside can you apport report a  bug against network-manager?
[10:07] <seb128> so we get logs&co
[10:10] <seb128> davmor2, is that reproducible? when did that start?
[10:11] <davmor2> seb128: yeap I'm just looking into causes as it works in the oem installer part
[10:11] <seb128> davmor2, is that an issue in the live session or installed system? does your wifi card requires a firmware?
[10:13] <davmor2> seb128: intel wifi no driver, it works in live session, it works in the oem installer part so you can download updates, but it doesn't work in the installed end user session on first boot, if you reboot it then does
[10:14] <davmor2> seb128: hence diggind into it as there are so many different bits to enable and not enable it in and it is finding out if it is every install or what
[10:14] <davmor2> it doesn't help that the connect to network page has suddenly disappeared from ubiquity either though
[10:17] <Laney> No need to go on about that bug every 2 minutes, it's known
[10:30] <seb128> darkxst, rather asking here
[10:30] <seb128> is the GNOME iso supposed to boot to a "get me started" with no installer reference?
[10:31] <darkxst> seb128, it should boot to the ubiquity greeter screen
[10:31] <seb128> I typed ubiquity but it has no result
[10:31] <seb128> the live session?
[10:31] <seb128> first item
[10:31] <seb128> I usually boot to live and run ubiquity from there
[10:31] <seb128> it feels nicer to have a session to play with while installing
[10:31] <darkxst> oh in the live session, ubuiqity is in the panel on left in overview
[10:32] <seb128> which is hidden by default
[10:32] <seb128> that's quite un-intuitive
[10:32] <seb128> but ok
[10:32] <seb128> imho you should not display the "how to get started" on the iso
[10:33] <seb128> it's more likely than people want to play with things or install
[10:33] <seb128> rather than watch introduction video and read help
[10:34] <darkxst> searching for ubiquity (or install) should also work?
[10:34] <seb128> not in the tutorial app which is maximized
[10:34] <seb128> like my default reflexe was to try to use what pop in front of my screen
[10:34] <darkxst> oh I see, right
[10:37] <darkxst> interesting the GCI kids all loved the tutorial app! it probably doesnt need to be on the live session though
[10:37] <darkxst> or maybe would be better if it wasnt maximised?
[10:39] <darkxst> I wonder if we could do a simple popup/notification "Press <super/win> key to get started"
[10:41] <seb128> darkxst, unsure, but closing/not maximizing doesn't help either since your desktop is empty
[10:41] <seb128> like there is nowhere obvious on screen that you can hit the activity corner to get the dash
[10:42] <seb128> so if you are not a GNOME user you get to sit down there watching tutorial or an empty desktop
[10:42] <seb128> oh well, I guess most of users are GNOME users and now where to go ;-)
[10:45] <darkxst> well there is a slight learning curve compared to a traditional DE
[10:48] <darkxst> and yet even windows users just go and click on "Activities" not try and press <super> which even opens the menu on windows (maybe they don't know that either though!)
[11:20] <seb128> darkxst, good work, Ubuntu GNOME looks good ;-)
[11:20] <seb128> just did an i386 installation
[11:20] <seb128> worked great
[11:21] <darkxst> seb128, thanks, should be a very solid release
[11:22] <Laney> mark them as ready!
[11:22] <darkxst> Laney, ok, I just finished smoketesting the last images, look good here also
[11:22] <Laney> :3
[12:10] <seb128> mdeslaur, lol, I didn't see that this trusty samba update was 4.1 to 4.3 serie, fun one!
[12:10] <mdeslaur> seb128: yeah, the fix was over 400 commits, no hope to backport it into 4.1
[12:10] <seb128> urg
[12:10] <mdeslaur> everyone else updates to either 4.2 or 4.3 too
[12:10] <mdeslaur> s/updates/updated/
[12:10] <seb128> that's quite annoying what happens
[12:11] <seb128> its means security update disrupt your working infra
[12:11] <seb128> but I guess no choice there...
[12:11] <mdeslaur> yeah, we didn't really have a choice
[12:12] <mdeslaur> this is the perfect example of why we usually backport fixes instead of upgrading versions
[12:13] <seb128> right
[12:14] <seb128> especially on something complex/interacting with other systems like samba
[13:07] <a1fa> whats with unity mouse acceleration? i dont know if i should open up a bug report or not
[13:08] <a1fa> but disabling mouse acceleration in the mouse setting should disable the mouse acceleration
[13:08] <a1fa> i shouldnt have to use xinput
[13:08] <a1fa> xinput --set-prop 8 "Device Accel Velocity Scaling" 1
[13:13] <a1fa> and why does launchpad no longer allow you to report a bug ;(
[13:56] <seb128> Trevinho smells
[13:56] <Trevinho> mh
[13:57] <seb128> Trevinho, sorry, I made the mistake to let my laptop unlocked
[13:58] <seb128> somebody used the opportunity
[13:58] <Trevinho> seb128: yess, yesss......
[13:58] <Trevinho> :)
[13:59] <willcooke> :D
[14:01] <seb128> cyphermox, did you look at the missing "connect to wifi" page in ubiquity?
[14:01] <cyphermox> started looking yeah
[14:01] <cyphermox> you still have nm-applet, and it's too late for fix now.
[14:01] <seb128> still looking? did you figure you somebody
[14:02] <seb128> Laney is starting as well and just said he was sure he would duplicate work with somebody
[14:02] <seb128> seems like he's right :p
[14:02] <seb128> yeah
[14:02] <seb128> just don't want to dup too much work
[14:02] <seb128> how much did you look?
[14:02] <seb128> should we stop?
[14:02] <cyphermox> no, please keep at it
[14:02] <seb128> k
[14:03] <cyphermox> I only just got up minutes ago, and jumped right in a meeting
[14:03] <seb128> k
[14:04] <cyphermox> all I did was yesterday try to add printfs and such to find out if it was being started at all, but I didn't see any hints
[14:04] <cyphermox> I don't know why it's unhappy
[14:21] <Laney> cyphermox: I found the problem
[14:21] <Laney> stand by
[14:43] <seb128> happyaron, e.u.c daily xenial view has some youker-assistant reports about import error due to missing lxml
[14:43] <seb128> is anyone looking at that?
[14:50] <Laney> pitti: do you know things about dbus-python?
[14:50] <pitti> Laney: that's a trick question :)
[14:50] <Laney> The wifi bug is because we ask for a property called 'state'
[14:50] <Laney> but it's actually called 'State'
[14:50] <Laney> apparently dbus-python handled uppercasing in trusty but not in xenial
[14:50] <Laney> ???????????????????
[14:50] <pitti> oh, did that change between 1.0 and 1.2?
[14:50] <pitti> oh, wow
[14:50] <Laney> I'm asking if it is known and/or deliberate :)
[14:51] <pitti> not to me, at least; so far whenever I used properties I just spelled them right
[14:51] <Laney> haha
[14:51] <pitti> so, single-character fix?
[14:52] <seb128> yep
[14:52] <Laney> well
[14:52] <Laney> I'm worried that it might be a problem elsewhere
[14:52]  * seb128 saw a wifi screen on Laney's screen
[14:52] <pitti> well done -- can't possibly get smaller for an SRU :)
[14:52] <cyphermox> Laney: definitely sounds like it could be a problem elsewhere
[14:52] <cyphermox> Laney: nice catch
[14:52] <Laney> this instance is obviously trivial to fix
[14:52] <Laney> but if other things expected the old behaviour...
[14:53] <Laney> I don't see any in ubiquity though
[14:53] <pitti> do we know, was this still working in wily?
[14:54] <pitti> ah, nevermind
[14:54] <pitti>  dbus-python | 1.2.0-2build2  | trusty  | source
[14:54] <pitti>  dbus-python | 1.2.0-2build2  | vivid   | source
[14:54] <pitti>  dbus-python | 1.2.0-2build3  | wily    | source
[14:54] <pitti>  dbus-python | 1.2.0-3        | xenial  | source
[14:54] <Laney> haha
[14:54] <pitti> it's not like this actually changed much
[14:54]  * Laney didn't look there
[14:54] <Laney> did we switch py2->3?
[14:54] <pitti> and http://launchpadlibrarian.net/234773210/dbus-python_1.2.0-2build4_1.2.0-3.diff.gz has no code changes at all
[14:55] <Laney> hmm, nope, I was reproducing on python3
[14:55] <Laney> umm, not reproducing
[14:55] <Laney> dbus change?
[14:56] <pitti> more probable, yes
[14:56] <seb128> nothing obvious in the commits log or bugzilla*
[14:56] <pitti> but that means it would affect dbus-glib, gdbus etc. too
[14:56] <pitti> Laney: did that affect wily already?
[14:56] <pitti> I suppose not
[14:56] <seb128> I think not
[14:56] <Laney> yes
[14:56] <pitti> then we at least don't look at the 1.6 -> 1.10 changes, only at 1.10.0 to 1.10.6
[14:56] <seb128> it does?
[14:56] <Laney> I used d-feet and it works
[14:57] <Laney> yes to my previous question
[14:57] <pitti> $ busctl introspect org.freedesktop.NetworkManager /org/freedesktop/NetworkManager | grep State
[14:58] <pitti> .State                              property  u           70                                       emits-change
[14:58] <pitti> that says it's "State", not "state" ??
[14:58] <Laney> State is the right name
[14:58] <pitti> oh, what you said, sorry
[14:58] <Laney> but on old dbus you could do Get(iface, 'state')
[14:58] <Laney> and it worked
[14:58]  * Laney goes to ask smcv
[14:58] <pitti> Laney: that should be simple enough to test with dbus-send on a trusty VM?
[14:59] <Laney> that's what I just did
[14:59] <Laney> I'll just fix ubiquity, but want to confirm that this was intentional
[15:06] <Laney> cyphermox: can haz bug number?
[15:07] <cyphermox> not sure, too many tabs
[15:07] <cyphermox> Bug 1572793
[15:07] <ubot5`> bug 1572793 in ubiquity (Ubuntu) "Ubiquity no longer prompts to join available WiFi networks" [Undecided,Confirmed] https://launchpad.net/bugs/1572793
[15:08] <Laney> ta
[15:08] <pitti> if we all think very hard, can we flip that one bit on our released image?
[15:09] <Laney> I can go and sed them
[15:09] <cyphermox> pitti: you don't want to respin? :)
[15:09] <Laney> don't worry
[15:09] <cyphermox> Laney: live binary sed at download-time, everywhere
[15:09] <cyphermox> oh, the NSA could help there.
[15:10] <pitti> cyphermox: no, just direct some strategic solar radiation on the world's mirrors :)
[15:10] <cyphermox> you mean bit-flipping using a magnifying glass?
[15:10] <pitti> whatever helps :)
[15:11] <cyphermox> I thought that's what "stategic solar radiation" meant, at least if you apply the same logic to ants.
[15:11] <pitti> strategically aimed/placed at that bit, I meant
[15:12] <pitti> anyway, 16.04.1 it is
[15:15] <cyphermox> yep
[15:18] <seb128> charles, tedg, did any of you had a chance to look at the geoclue issue?
[15:18]  * tedg has not
[15:19] <seb128> :-(
[15:22] <Laney> cyphermox: for your reviewing pleasure
[15:22] <cyphermox> SHIP IT!
[15:22] <cyphermox> :)
[15:22] <Laney> might be a good idea for someone other than me to test
[15:22] <cyphermox> yep I will in a second
[15:23] <pitti> i. e. this is boot life session, change that s to an S (or install -proposed package), run ubiquity, right?
[15:23] <Laney> sure
[15:23] <Laney> not that there is any package yet
[15:24] <pitti> right, but that change is simple to apply inline on a running system
[15:24] <Laney> yep, just saying so that you don't go looking
[15:27] <cyphermox> davmor2: ok, that other bug is as I said, in the oem-config, after we get back to a "real" session, wpasupplicant has been killed.
[15:27] <cyphermox> no supplicant = no wifi
[15:29] <davmor2> cyphermox: \o/
[15:31] <davmor2> cyphermox: so that is a fixable thing right?
[15:31] <cyphermox> davmor2: yeah, given enough eyes, all bugs are shallow
[15:31] <cyphermox> given enough hammers, anyone can fix systemd units.
[15:32] <davmor2> cyphermox: I have hammers it how I break things :)
[15:32] <pitti> (needs really big mallets, though)
[15:32] <cyphermox> but I think maybe I'd just make things reboot rather than trying to get to a session straight out of the oem wizards
[15:33] <cyphermox> perhaps all we need is for wpasupplicant to ship a unit, so that things don't get killed off if it's running already
[15:33] <cyphermox> oh, except it does
[15:34] <cyphermox> and the busname looks wrong.
[15:35] <pitti> I have fi.epitest.hostap.WPASupplicant and fi.w1.wpa_supplicant1
[15:35] <cyphermox> [Service]
[15:35] <cyphermox> Type=dbus
[15:35] <cyphermox> BusName=fi.epitest.hostap.WPASupplicant
[15:35] <cyphermox> ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
[15:36] <cyphermox> it should be fi.w1 ^
[15:36] <cyphermox> where do you have both pitti?
[15:36] <pitti> /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service and /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service
[15:36] <cyphermox> right
[15:36] <pitti> and tab-completing "busctl introspect fi.<tab>"
[15:37] <cyphermox> I'm looking at wpa_supplicant.service under /lib/systemd/system
[15:37] <pitti> right
[15:37] <pitti> that name does exist, but there's another one, not sure which is the "right" one
[15:38] <seb128> https://blog.mozilla.org/futurereleases/2016/04/21/firefox-default-browser-for-linux-users-ubuntu-new-snap-format-coming-soon/
[15:38] <cyphermox> fi.w1... seems to me like the right one. that's where we talk to wpa from NM, in any case
[15:39] <pitti> cyphermox:  nice catch; then it should (re)start on demand again
[15:39] <pitti> so is /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service entirely obsolete then?
[15:40] <cyphermox> maybe, lemme see if it's not really used only for hostap
[15:40] <pitti> oh, or maybe it actually does listen to both names
[15:40] <pitti> the old name for backwards compat reasons
[15:41] <cyphermox> yep
[15:42] <cyphermox> for some reason upstream only ships the old name as a systemd unit?!
[15:42] <tedg> seb128: So apparently we want to SRU unity8-policy-kit, which is a new package and on CI-Train. I don't know how all those work together.
[15:43] <tedg> seb128: I don't think I can make an SRU bug until the package exists, no?
[15:45] <seb128> tedg, you can open a bug against "ubuntu" and reference it to the changelog, the important bit is to have a page for the testing/tracking, no to have the right component/autoclosing on upload
[15:46] <tedg> seb128: Okay, will do
[15:46] <tedg> Thanks!
[15:46] <seb128> tedg, yw!
[15:47] <seb128> tedg, what was the review url you pinged me about the other day?
[15:47] <seb128> I can have a look now
[15:47] <tedg> seb128: Cool, it is the packaging for this package: https://code.launchpad.net/~ted/unity8-policy-kit/initial-work/+merge/291371
[15:48] <seb128> tedg, charles, any chance I can one of you to look at this geoclue issue in exchange? :p
[15:49] <tedg> seb128: Heh, probably not today as we're both doing time critical things today, but I should be free tomorrow.
[15:49] <seb128> sounds like a good friday afternoon thing ;-)
[15:49] <seb128> thanks!
[15:50] <tedg> Oh, now that we have a VPN I wonder if I can test being in the UK....
[15:50] <cyphermox> pitti: this didn't look to have worked :/
[15:50]  * tedg starts substituting all his 'z' and 's's
[15:50] <charles> seb128, as tedg said, today doesn't look good
[15:50] <seb128> charles, I think you are in Prague next week? I can nag you in person there :p
[15:51] <tedg> seb128: Heh, don't let him change his timezone without a fix!
[15:54] <seb128> tedg, right!
[15:57] <seb128> tedg, " This package provides a service for the Pay Service" ?!
[15:57] <seb128> tedg, did you copy/paste the description from the pay-service and didn't change it?
[15:57] <tedg> Oops, copy paste :-)
[15:58] <seb128> tedg, also policykit / policykit-gnome ... can you do "unity8-policykit" for consistency? (without the "-")
[15:59] <seb128> (I guess it's a bit more annoying because it would mean renaming the launchpad project)
[16:00] <tedg> Yeah, though we could make the deb and the LP project be different.
[16:00] <seb128> would be confusing as well
[16:00] <seb128> like users would try to go from the package to the launchpad page using the name and get a not found
[16:01] <tedg> Heh, I'd like to see a user figure out there's an issue with the policykit agent :-)
[16:01] <seb128> tedg, copyright should be updated to -2016 (nitpick)
[16:01] <tedg> More worried about Ubuntu Devs
[16:02] <seb128> right, those are your users as well :p
[16:06] <tedg> Heh
[16:06] <tedg> seb128: Copyright and description updated. What do you want to do with the package name?
[16:06] <tedg> We're gonna have to rebuild, so we could change the LP project as well.
[16:09] <davmor2> willcooke, pitti, cyphermox: do we know what is happening with this now?
[16:09] <seb128> tedg, if you rename can you make it policykit-unity8? consistent with -gnome/-kde/...
[16:09] <seb128> tedg, but yeah renaming is better if that's not too much work
[16:09] <willcooke> davmor2, "this"?
[16:09] <cyphermox> davmor2: what's "this" ?
[16:09] <davmor2> willcooke, cyphermox: the wifi issues
[16:10] <willcooke> davmor2, yes!
[16:10] <cyphermox> in part, yeah
[16:10] <cyphermox> my idea for wpasupplicant doesn't seem to work though
[16:10] <tedg> seb128: K, I'll just make a new LP project and kill the old one.
[16:10] <davmor2> no don't say that
[16:10] <seb128> tedg, thanks
[16:11] <seb128> tedg, the packaging/license/etc looks fine otherwise
[16:11] <tedg> seb128: Cool, thanks!
[16:11] <seb128> yw!
[16:22] <willcooke> congratulations desktoppers
[16:23] <Trevinho> Yay!
[16:24]  * Trevinho takes drinks out from the fridge
[16:25] <willcooke> \o/
[16:25] <seb128> thanks!
[16:25] <seb128> well done team!
[16:25] <seb128> and other teams as well ;-)
[16:28] <davmor2> \o/
[16:28]  * pitti goes and grabs a xerus ice cream
[16:29] <pitti> ... for purely medical reasons, of course!
[16:32] <ximion> congrats to the successful release! :)
[16:32] <ximion> and I must say, GNOME Software / Ubuntu Software is working well here :)
[16:35] <jcastro> it is quite nice
[16:49] <tedg> seb128: So we have the branch to add a libpam-cgfs dep for UAL so that it gets pulled in for unity8, but that then fails on vivid because there is no libpam-cgfs. Is there a way to write that dep so that it'll work on vivid and xenial?
[17:05] <andyrock> \o/
[17:21] <willcooke> out
[17:47] <Laney> in ou tin
[19:36] <flocculant> attente: when you're about - https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1551707/comments/3
[19:36] <ubot5`> Launchpad bug 1551707 in gnome-software (Ubuntu) "Installing local debs gives an error dialog" [High,Fix released]
[19:36] <flocculant> if it is in fact different I'll report it - unless it gets reported in the meantime
[19:44] <attente> flocculant: hey, i'm not sure what's going on there, i just tried it with some other debs, but maybe there's some deps missing that would cause the error message...
[19:45] <flocculant> attente: could be - if I try with gdebi - it wants to get 2 dependencies
[19:46] <attente> flocculant: ok, yeah. so i'm not sure what to do there. on the one hand it sounds like erroring out is the right thing to do if we can't install the deb due to missing deps, on the other, maybe we could be better about looking for those deps
[19:47] <flocculant> I'd have to assume that the second would be the way to go :)
[19:47] <flocculant> but no coder here ;)
[19:49] <flocculant> attente: mmm - so I installed the deps that gdebi needed, but it still fails with software
[19:50] <attente> flocculant: oh... really?
[19:50] <flocculant> yea
[19:51] <flocculant> just going to look in a clean install
[19:51] <attente> flocculant: ok, i'll look into it
[19:51] <attente> flocculant: not sure that will change much
[19:52] <flocculant> well - this install has been kicked about all over the place for the last 2 or 3 months - so I prefer to check :)
[19:53] <attente> flocculant: sure, be my guest :) i'm not expecting anything different though...
[20:00] <flocculant> attente: well the issue is 'slightly' different on that - doesn't install, but don't get the error popup
[20:01] <attente> flocculant: it actually doesn't install? or is it just the button that isn't updating properly?
[20:01] <attente> that second one is a known issue
[20:01] <attente> do you see the progress bar at all for installation on the button?
[20:02] <flocculant> attente: it doesn't install - I saw the progress bar - which I would think finished much too quickly to have been the install
[20:03] <attente> ok. did it pop up a dialog asking you to authenticate with user password?
[20:03] <flocculant> no
[20:03] <attente> flocculant: can you link to the deb? i want to try that specific one
[20:04] <flocculant> https://www.google.com/chrome/browser/desktop/ 64 bit
[20:05] <flocculant> locally I needed to install libappindicator1 and libindicator7 to allow gdebi to install it
[20:06] <flocculant> attente: also I'm using xubuntu - not that it should make any difference
[20:07] <attente> flocculant: yeah, i can reproduce with that deb
[20:07] <flocculant> attente: ok cheers :)
[20:07] <flocculant> attente: you need anything from me at all now?
[20:08] <attente> flocculant: nope. i see the error message too :)
[20:08] <attente> GDBus.Error:org.debian.apt.TransactionFailed: error-unreadable-package-file: [Invalid UTF-8]
[20:08] <flocculant> okey doke - I shall wander off into the void again then :)
[20:08] <flocculant> thanks for looking
[20:08] <attente> flocculant: nooo not the void! :P
[20:09] <attente> flocculant: thanks for letting me know :)
[20:09] <flocculant> welcome :)
[20:10] <flocculant> nice to actually have some idea of who to tell to be honest - this is a rather useful channel for a flavour's qa to idle in :)
[20:11] <attente> hehe, indeed!
[22:27] <TheMuso> Holy crap! Just discovered that systemctl can use policykit so you don't have to run it with sudo. Wow thats awesome! :)
[22:28] <TheMuso> Although you do have to autnehticate every time.
[22:28] <TheMuso> Still, useful to know.
[22:53]  * Laney can't remember if polkit has caching
[22:54] <Laney> but I thought that the gnome agent did
[22:54] <Laney> could be just making that up though
[22:57] <TheMuso> Seems not for systemctl at least.
[22:57] <TheMuso> The GNOME agent may, but this was under Unity.
[22:58] <Laney> that's the gnome one
[22:58] <Laney> Just checked, doesn't here
[22:58] <TheMuso> Ah ok.
[22:59] <Laney> still, cool of systemd to use that
[23:00] <TheMuso> Indeed.
[23:01] <TheMuso> I discovered it totally by accident, calling systemctl to work with a service without using sudo.