[10:41] <johnl> hello. I'm getting chroot problem errors when trying to build packages on launchpad: https://code.launchpad.net/~ceph/+recipe/ceph-rc-builds
[10:42] <wgrant> johnl: Hi. That's a known issue that I landed a fix for a few hours ago.
[10:43] <johnl> ok great. I assume it's not deployed yet? (just got a fail a few minutes ago)
[10:44] <wgrant> johnl: It will hopefully be rolled out in the next day or two. For now you should be able to work around it by building the recipe into a PPA that had packages in it before the 9th of December.
[10:44] <wgrant> You can then copy it to the new PPA.
[10:46] <johnl> ok, super, thanks.
[10:47] <wgrant> The deployment is blocked on a few un-QA'd revisions before this fix, but it's nearly there.
[10:55] <lifeless> wgrant: has flacostes rolled back rollout been done now?
[10:55] <wgrant> lifeless: Yes.
[10:55] <wgrant> An hour or so ago.
[10:56] <wgrant> 12093
[10:56] <wgrant> Scripts are even working this time!
[10:56] <lifeless> o/
[13:15]  * lamont looks around for a backport of python-launchpadlib from lucid to hardy
[13:28] <MTecknology> From<EMAIL_ADDRESS><EMAIL_ADDRESS>[13:28] <MTecknology> weirdest spam I've ever seen....
[13:29] <MTecknology> it's like someone is grabbing every user from ~ubuntu-members
[13:59] <MTecknology> allenap: how dare you change the topic!
[13:59] <MTecknology> btw- howdy helper :)
[14:23]  * CardinalFang hugs Launchpad.
[14:50] <allenap> MTecknology: Hi there :)
[14:50] <MTecknology> howdy
[14:52] <MTecknology> allenap: you good with design and planetplanet?>
[14:52] <allenap> MTecknology: Neither! What's up?
[14:53] <MTecknology> allenap: This is all I can come up with with my poor design skills (http://planet.nginx.org/) and I'm trying to make it actually look pretty
[14:58] <allenap> MTecknology: Ouch, that's ugly :) Personally, I would try switching to a sans-serif typeface and making the text bigger, then see how it looks. But, as I say, visual design is not really my domain.
[14:59] <MTecknology> allenap: :'(   I wrote that all from scratch
[14:59] <allenap> MTecknology: Sorry, I didn't mean to offend :)
[15:01] <MTecknology> allenap: you didn't, i know I'm not good with designing things. I can half way get there if I can picture it in my head, but that's what i can't do
[16:22] <zyga> hi, I seem to have damaged my branch
[16:22] <zyga> I had a branch, with debian packaging, stacked on top of the project trunk (technically, there was no actually common parts between the two)
[16:22] <zyga> I then changed the owner of both branches
[16:23] <zyga> and now it seems that the packaging branch is broken, I cannot bzr get it, I cannot bzr push to it
[16:23] <zyga> the branch is: lp:~linaro-infrastructure/django-render/packaging
[16:23] <zyga> it used to be ~zkrynicki
[16:23] <zyga> pushing to it causes: bzr: ERROR: Server sent an unexpected error: ('error', "Cannot lock LockDir(lp-57682896:///~linaro-infrastructure/django-render/packaging/.bzr/branchlock): File exists: u'/srv/bazaar.launchpad.net/mirrors/00/06/4e/64/.bzr/branch/lock': [Errno 17] File exists: '/srv/bazaar.launchpad.net/mirrors/00/06/4e/64/.bzr/branch/lock'")
[16:23] <zyga> getting says: bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~zkrynicki/django-render/upstream/".
[16:24] <zyga> note - the getting error message still refers to the _old_ trunk (called upstream here) that was owned by my launchpad user
[16:24] <zyga> what can I do to recover?
[16:54] <berco> Hi, can a LOSA make PUBLIC our PPA "TI OMAP trunk PPA" https://launchpad.net/~tiomap-dev/+archive/trunk? It has been created as private by mistake, we (TI) already have a trunk PPA marked private called "TI OMAP private trunk PPA". Thanks.
[16:56] <allenap> zyga: I'll find someone who can help you.
[16:56] <allenap> abentley: Would you be able to help zyga out with a branch issue?
[16:57] <abentley> allenap, I believe the user should be able to change a private branch to public.
[16:58] <allenap> zyga: See abentley's reply. Does that make sense?
[16:59] <zyga> abentley, that was not a private branch
[16:59] <zyga> allenap, abentley: I resolved the issue by deleting the packaging branch and uploading it again to ~linaro-infrastructure team
[17:00] <zyga> but I suspect it's a lp bug
[17:00] <zyga> I got bit by this once before
[17:02] <Chex> berco: sure, give me a  couple
[17:03] <abentley> zyga, sorry.  I'm only used to being asked about branches.
[17:03] <berco> Chex: thanks a lot
[17:13] <Chex> berco: ok, all set, the PPA is public now.
[17:15] <berco> Chex: thanks
[17:31] <berco> Chex: I still see "TI OMAP trunk PPA" in private. Does it need some time to update?
[17:37] <Chex> berco: hrrm , looking
[17:38] <Chex> berco: oh, sorry, am getting this error, which is a bit odd ' This archive already has published sources. It is not possible to switch the privacy. '
[17:39] <Chex> berco: makes sense when going public to private, but not the way your going..
[17:51] <berco> Chex: Does it mean we cannot switch from private to public? just wanna make sure I understood
[17:56] <Chex> berco: I am trying to figure that out, let me get back to you
[17:57] <berco> Chex: okay, thanks. I'll need to leave the office but keep me posted here.
[18:14] <evaluate> hello
[18:17] <evaluate> I have a PPA and I would want to make the package available for both maverick and natty, but if I upload it with the same version number it doesn't work. Do I need to make sepparate PPAs for different distros or is there another trick?
[18:26] <maxb> evaluate: You should not make separate PPAs, rather, you should upload with different version numbers. You should take care that the version numbers sort correctly maverick < natty, such that someone upgrading from maverick to natty also sees the upgrade of your package
[18:27] <evaluate> maxb, ok, so for example for maverick I name it -1ubuntu1 and for natty -1ubuntu2?
[18:27] <maxb> evaluate: please don't :-)
[18:27] <maxb> As a good rule of thumb, never construct your PPA version numbers to look like they are official archive packages
[18:28] <evaluate> umm
[18:28] <maxb> It's good to not be misleading
[18:28] <evaluate> ok :p
[18:28] <evaluate> so then -1 and -2?
[18:29] <maxb> Then they look like official Debian version numbers :-)
[18:29] <maxb> Generally, I use something like -0ppa1maverick1
[18:29] <evaluate> ugh, is there a common convention then? :-)
[18:30] <evaluate> ohh, right, using the distro names, caus they are also alphabeticall. Didn't think about that one :-)
[18:30] <evaluate> maxb, thank you!
[18:30] <maxb> in which the zero says it's not based on a specific Debian packaging, the first 1 suggests the version of the base packaging, and the final 1 is what I would increment if fixing a problem in a single series build
[18:31] <evaluate> maxb, is there a way to delete a package that I already uploaded?
[18:31] <evaluate> caus it already contains -1 :-)
[18:32] <maxb> You can delete packages in the web ui, but making version numbers go downwards is usually not a good thing
[18:32] <maxb> is it a package which is *actually* in debian?
[18:32] <maxb> If not, I'd just keep the 1 until the next upstream version happens, and drop it to a 0 at that point
[18:32] <evaluate> I just uploaded it 5 minutes ago, it didn't even build yet. Could you please tell me where exactly I could delete it? I can't seem to find that feature...
[18:33] <evaluate> maxb, it's waiting in the NEW queue currently. They are pretty busy with the release apparently... :p
[18:34] <maxb> Oh, well, if your ppa packaging is actually based on a real debian upload, then yes, I'd base the version number on that version
[18:35] <maxb> Chex, berco: There's no detail in it whatsoever, but bug 376072 exists :-/
[18:35] <evaluate> ok then, -1 it is.
[18:35] <evaluate> thanks again maxb
[18:39] <Derixx> I have rm some packages in a ppa a few days ago. Now I want to copy packages with the same name to that ppa, but it says that there is already such packages :/
[18:39] <Derixx> it isn t
[18:39] <Derixx> it's removed!
[18:39] <maxb> same name *and* same version?
[18:42] <Derixx> right
[18:42] <maxb> A package name&version may be deleted, and is removed from disk and from the repository indexes, but a name&version can never be reused, even when deleted
[18:43] <Derixx> bug
[18:43] <maxb> This is to ensure the horrifically confusing situation of a single version referring to two different builds of a package, never arises
[18:43] <Derixx> arghhh
[18:43] <maxb> No, feature.
[18:43] <maxb> It's quite deliberate, I assure you
[18:44] <Derixx> it sounds like a 'hack' instead of a feature
[18:45] <Derixx> anyway, this isn't experienced as nice behavior by me... but alas, it is as it as atm...
[18:45] <maxb> Well... a version number is supposed to uniquely identify a version - pretty much by definition
[18:45] <maxb> It's not really a hack to strongly enforce that
[19:01] <evaluate> maxb, do you have the ability to delete a package forcefully?
[19:01] <evaluate> The package I deleted still appears in the build queue...
[19:06] <maxb> evaluate: That's fine, the build will be cancelled automatically when it reaches the head of the queue
[19:06] <evaluate> maxb, ok then.
[20:59] <bdmurray> bdrung: I'm not finding the lp-set-dupe bug in ubuntu-dev-tools easily
[21:00] <bdrung> bdmurray: it was closed
[21:01] <bdrung> bdmurray: it was bug #576477
[21:02] <bdmurray> bdrung: okay, some of the code in there is is unnecessary now as launchpad handles marking a bug w/ duplicates as a duplicate of another now
[21:12] <mgariepy> hello, i'm having a weird bug with a ppa
[21:12] <mgariepy> the package is published on lp but when i do apt-get update, apt-cache search i can't find the package
[21:13] <mgariepy> deb http://ppa.launchpad.net/revolution-linux/ppa/ubuntu hardy main
[21:13] <mgariepy> and the package is bzr-inotify
[21:13] <mgariepy> https://launchpad.net/~revolution-linux/+archive/ppa
[21:17] <thumper> mgariepy: that ppa doesn't appear to have bzr-inotify in it
[21:19] <mgariepy> thumper, the package is present on https://launchpad.net/~revolution-linux/+archive/ppa?field.series_filter=hardy


[12:29] <Milos_SD> Hello... Does anyone have an idea how can I purge xorg-edgers packages a revert to default on ubuntu 12.04 64bit?
[12:29] <Milos_SD> :)
[12:29] <mlankhorst> Milos_SD: ppa-purge ppa:xorg-edgers/ppa or something
[12:30] <Milos_SD> mlankhorst, that doesn't work on 64bit :(
[12:31] <Milos_SD> ppa-purge or aptitute doesn't work with multiarch...
[13:05] <tjaalton> no reason why they shouldn't
[16:37] <tjaalton> meh, installing the powervr blob on the panda made it more sluggish
[17:03] <mlankhorst> uploaded the new stack to my ppa, with armhf so I'm going to test on my panda :p
[17:03] <mlankhorst> tjaalton: you need to have the ti-omap ppa
[17:05] <mlankhorst> Currently 12 packages building and 26 packages waiting to build.. poor pandaboard ppa builders
[17:28] <tjaalton> mlankhorst: ah, ok
[17:28] <tjaalton> still on precise
[17:41] <mlankhorst> yeah but you need to remove the mem=... args from /boot/boot.script else the ti kernel will go lockup
[17:41] <mlankhorst> and install ubuntu-omap4-extras
[17:42] <tjaalton> ok
[17:43] <mlankhorst> if you use unity3d, you need to add option 'hwcursor' 'false' to /usr/share/X11/xorg.conf.d/99-*omap*.conf to prevent massive glitches
[17:44] <mlankhorst> and I think there was some bug with smp in the 1486 kernel so you might need nosmp too, I'm using that for now.
[17:44] <tjaalton> what a mess :)
[17:45] <mlankhorst> well robclark helped me a little with sorting those quirks out
[17:46] <mlankhorst> wow no launchpad queue, all my non-arm uploads finished \o/
[20:26] <Sarvatt> tjaalton: ha, go figure i finally hit that black screen bug right after you uploaded the fix and i hadn't rebooted into it yet
[20:27] <mlankhorst> :-)
[20:39] <tjaalton> Sarvatt: hehe
[21:09] <ehoover> Hello, sorry to be a bother - but who would I contact to get an XCB upstream patch applied to the current ubuntu package?  The patch fixes a pretty significant problem for Wine and I'd like to get it fixed before 12.04.2/12.11.
[21:12] <tjaalton> which bug?
[21:14] <ehoover> https://bugs.freedesktop.org/show_bug.cgi?id=54671
[21:15] <tjaalton> no I mean on launchpad
[21:17] <ehoover> I haven't created a bug for it on launchpad, I was working directly with upstream.  Would it help for me to do that?
[21:17] <tjaalton> for SRU's it's mandatory
[21:19] <ehoover> I'm sorry, I'm not familiar with your procedures (I've never had to do this before).  Could you point me to what I need to read so that I'm not bothering you unnecessarily?
[21:20] <Sarvatt> yeah it would help a lot, we're frozen for 12.10 so it has to reference a launchpad bug to upload the fix (and a 12.04 stable release update would absolutely need a launchpad bug), ubuntu-bug xorg will fill out most of the info for you
[21:20] <tjaalton> just file a bug against libxcb
[21:20] <tjaalton> or that
[21:20] <Sarvatt> couldn't figure out the ubuntu-bug invocation for libxcb from a quick try :P
[21:21] <Sarvatt> oh ubuntu-bug libxcb1
[21:22] <tjaalton> or the source package
[21:22] <tjaalton> but lp will map it there if it's filed against the binary package
[21:22] <Sarvatt> ubuntu-bug libxcb doesn't work
[21:24] <tjaalton> ḧuh
[21:24] <tjaalton> ok
[21:24] <tjaalton> right, it's apport..
[21:29] <ehoover> ok, i've filed bug https://bugs.launchpad.net/libxcb/+bug/1059276 and linked it to the upstream bug.  Should I copy the details of the issue to the launchpad bug or is that unnecessary?
[21:57] <Sarvatt> hmm, i can't nominate for series on that bug
[22:00] <Sarvatt> ehoover: so what app is hitting that for you? can't say i've noticed the problem ever with wine, going to need some kind of test case for a precise fix to happen
[22:03] <ehoover> Sarvatt: I've seen it with Borderlands and Silverlight.  Others have reported issues with Skyrim and a few other apps.  Would you like me to link in the Wine bug?
[22:43] <bryceh> RAOF, when you get in:  I've uploaded new jockey and nvidia-common for bug #1047681.  Mind reviewing/accepting them?
[23:05] <mlankhorst> oh
[23:07] <mlankhorst> well testing on my panda, seems i need some explicit depends on libgl1-mesa-glx-lts-quantal to upgrade things correctly, need to figure out a correct fix for that
[23:39] <mlankhorst> other than that it works it seems


[00:27] <syntroPi> Why is synaptic always freezing after some uptime while fighting over the cpu ressources with dbus and gnomeshell? any known bugs?
[00:28] <syntroPi> it takes orders of magnitude more time to load up and unfreeze
[00:29] <syntroPi> any known bugs in dbus which may be related to this?
[00:42] <darkxst> syntroPi, Bug 1328586
[00:46] <darkxst> syntroPi, although that should be fixed in utopic and gnome3-staging
[02:08] <syntroPi> darkxst, thanks thats exactly the issue i have here on x64trusty with gnome 3 staging ppa
[02:08] <syntroPi> gnome-shell, dbus-daemon and synaptic are fighting over cpu ressources while it loads
[02:09] <darkxst> syntroPi, it should have been fixed with gnome-shell - 3.12.2-0ubuntu0~trusty2 , unless you use the magnifier
[02:11] <syntroPi> whut? the magnifier? i use https://github.com/tobiasquinn/gnome-shell-mousewheel-zoom on gnome-shell 3.12.2-0ubuntu0~trusty2
[02:14] <syntroPi> sometimes it loads with normal speed right after booting (2s or such) but once it got in that weird state only reboot resolves it. whole gnome-shell is sluggish while it does its crazy loading freeze
[02:14] <darkxst> that would be using the magnifier
[02:15] <syntroPi> yup how come?
[02:18] <darkxst> syntroPi, to zoom!
[02:19] <syntroPi> yes ofc just wondering how the gnome-shell zoom is related to that issue
[02:19] <darkxst> https://wiki.gnome.org/ThreePointNine/Features/FocusCaretTracking
[02:19] <darkxst> zoom uses a11y features
[02:23] <syntroPi> thanks i will disable the zoom and read into those bugs to understand more of this
[02:29] <darkxst> syntroPi, you can run synaptic with "NO_AT_BRIDGE=1" as a work-around
[02:34] <syntroPi> WOW thank you that works
[09:53] <melodie> hi
[09:53] <melodie> does update-notifier work for you in 14.04?
[09:55] <darkxst> hey melodie!
[09:55] <darkxst> I'm on utopic now, but recall update-notifier crashing a lot in 14.04
[09:57] <melodie> hi darkxst! ok, but I meet with this issue in a fresh install of Bento Precise on a eeepc 1101HA and a guy on #ubuntu-fr looked for himself and noticed 130 packages to be updated in his GUbuntu 14.04, this is why I am coming here to ask. Would you know how I can debug? what command lines and or log files I should look at?
[09:58] <darkxst> melodie, backtrace?
[09:58] <melodie> of course the guy using Ubuntu Gnome Trusty has update-notifier that should have notified and which didn't
[09:58] <melodie> how do I use backtrace?
[09:58] <darkxst> if it crashed, there should be a crash file in /var/crash
[09:58] <melodie> I have no idea about that : just "backtrace update-notifier" ?
[09:59] <melodie> ok I look /var/crash
[09:59] <darkxst> ubuntu-bug <that crash file>
[09:59] <melodie> ok
[09:59] <darkxst> melodie, and I don't think its anything specific to ubuntu GNOME
[10:01] <melodie> the /var/crash directory is empty
[10:01] <melodie> is "backtrace" a tool?
[10:02] <darkxst> melodie, no, a backtrace is trace of the crash
[10:02] <darkxst> https://wiki.ubuntu.com/DebuggingProgramCrash
[10:03] <melodie> thank you
[10:03] <darkxst> if there is nothing in /var/crash it probably didnt crash and just isnt working
[10:04] <melodie> darkxst in case of crash break the window! XD (I have done a desktop file containing a command line for direct update and upgrade)
[10:05] <melodie> but for now I removed it all and reinstalled it all. I had apt configured without the recommend depends and I have re-configured with the recommend depends, before reinstalling. I'll see how it behaves now
[10:05] <melodie> hummm
[10:05] <melodie> still no notification after reboot, so far
[10:06] <darkxst> melodie, file a bug, although I think the notifaction goes off at a set time
[10:06] <darkxst> each day
[10:11] <ricotz> darkxst, hi, are you sure there is no abi break in gjs?
[10:12] <darkxst> ricotz, its like 2 patches, and no abi break
[10:13] <darkxst> or 3:
[10:13] <darkxst> 6 days	cairo: enable multithreading for cairo-xlib	Giovanni Campagna	3	-2/+16
[10:13] <darkxst> 2014-06-15	mainloop: restore priority arguments to *_add() calls	Giovanni Campagna	1	-9/+15
[10:13] <darkxst> 2014-05-02	Fix building Regress-1.0.gir with cairo disabled
[10:13] <ricotz> i am pretty sure there are like https://git.gnome.org/browse/gjs/commit/?id=675ce6243cc5ac1925cf937dcd49f26f36ef9da2
[10:13] <ricotz> i am speaking of the 1.41.3 upload
[10:14] <ricotz> ah the 1.40.1 tag is missing
[10:14] <darkxst> ricotz, yes, most of that is in 1.40.1
[10:15] <ricotz> any way i wouldn't count on it to remain stable
[10:15] <ricotz> like mutter does
[10:16] <darkxst> ricotz, right, I will probably break it with js31!
[10:17] <ricotz> i would have bumped it as precaution
[10:18] <ricotz> yeah the js31 rebuild is another things and get caught already due shlib-deps generation
[10:18] <darkxst> ricotz, I will bump it when required, 1.41.3 could well have been 1.40.2
[10:19]  * ricotz just noticed the update while it creates conflicts here ;)
[10:19] <ricotz> ok
[10:20] <darkxst> conflicts?
[10:20] <ricotz> i mean i bumped the library in my ppa, so apt isn't so happy about it ;)
[10:21] <darkxst> oh I see
[10:22] <darkxst> I would suggest holding off on that until js31, but guess that is too late!
[10:25] <darkxst> ricotz, gjs is pretty stable, most api changes come as a result of spidermonkey upgraddes
[10:25] <ricotz> darkxst, don't worry i will just a push new version
[10:26] <ricotz> darkxst, hmm, i would call it stable while seeing the mentioned api cleanup commit
 melodie, file a bug, although I think the notifaction goes off at a set time  || do you know someone who could say more about that?
[10:27] <melodie> I think it used to be displayed each time we would boot, when configured to be launched each day
[10:27] <melodie> going now
[10:29] <darkxst> ricotz, we have been running current gjs with old GNOME for a few cycles, and really the biggest issue was E4x removal
[10:30] <darkxst> (and of course I removed that as part of js24
[10:31] <darkxst> melodie, not to sure, I think it fires at a set time each day, I am constantly upgrading my system so often miss notifications
[10:33] <ricotz> darkxst, ok, there are other consumers as well, but there is actually just gnome-shell really using it
[10:33] <ricotz> (libpeas support isnt built on ubuntu)
[10:34] <darkxst> ricotz, shell and gnome apps
[10:34] <ricotz> it is the same with mutter, they are removing api which wasnt used in gnome-shell, and therefore not breaking things in this regard
[10:34] <darkxst> polkit has a gjs backend also, but not built on ubuntu
[10:34] <ricotz> but it is still an abi break
[10:36] <darkxst> mutter is pretty much volatile!
[10:37] <ricotz> same developers with no commitment to abi/api stability ;)
[10:37] <ricotz> .. for those library
[10:37] <ricotz> ies
[10:45] <melodie> darkxst then I'll have to find out more about update-notifier
[10:45] <darkxst> mutter is a moving target, gjs not so much
[10:47] <darkxst> melodie, just dig in, its just a python scripts I think
[10:50] <darkxst> melodie, or chat with the -desktop team, they would know more
[10:50] <ricotz> if it is python using python-gi, and you are using the gnome3-staging ppa, annotation changes in gtk+3.0 could result in problems, i guess
[10:51] <darkxst> ricotz, melodie doesnt even use GNOME
[10:52] <darkxst> she is making an openbox remix
[10:56] <ricotz> alright, i assumed an ubuntuGNOME problems here ;P
[10:58] <darkxst> ricotz, its spillover from phillw's world!
[11:05] <darkxst> ricotz, not too sure how she ended up in this channel, maybe I am being stalked!
[11:06] <ricotz> darkxst, heh, i see, and you waited until she left
[11:07] <ricotz> ubot5 knows everything
[11:09] <darkxst> ricotz, ubot5 doesnt seem to know much!
[11:59] <ceed^> After todays upgrades in staging PPA I can't open gnome-control-center or any settings. I get error while loading shared libraries: libgtop-2.0.so.7: cannot open shared object file: No such file or directory
[12:04] <ricotz> ceed^, sorry, please downgrade the libgtop packages
[12:06] <ceed^> ricotz, I'm not sure I know how to only downgrade a couple of packages.
[12:07] <ceed^> looking it up now... :)
[12:09] <ceed^> Can do it with Synaptic it seems..
[12:10] <ricotz> sudo apt-get install libgtop2-7=2.28.5-2 libgtop2-common=2.28.5-2 libgtop2-dev=2.28.5-2 gir1.2-gtop-2.0=2.28.5-2
[12:10] <ricotz> ceed^, this should do the trick
[12:11] <ceed^> thanks!
[12:13] <ceed^> ricotz, settings are back, thanks. Do I have to be careful with updates now so I do not get the broken packages back?
[12:16] <ricotz> ceed^, no, the packages should stick and won't get updated again until the next proper update
[12:19] <ceed^> Thank you so much! :)
[16:08] <john8681> hi
[16:11] <john8681> i would like to install ubuntu onto a windows 8 computer that in virus ridden. Please let me know if I can just go ahead and install ubunto or do I need to reformat windows 8
[21:01] <Noskcaj> darkxst, Should we be packaging gnome-sound-recorder? It was new in 3.12
[22:18] <darkxst> Noskcaj, yes
[22:18] <Noskcaj> i'll get that done some time today then