=== azeem_ is now known as azeem [04:17] hey [04:20] how's [04:20] ** everyone doing? [05:37] hi, do i have to take any action to get my bzr sru approved from https://launchpad.net/ubuntu/maverick/+queue?queue_state=1&queue_text=bzr ? [05:39] thats in main - #ubuntu-devel is a better channel [05:39] (sorry to make you follow pointers) [05:44] ah thanks, i had the idea newbie developer questions would be more appropriate here [05:44] newbies are normally motus fodder yes [05:44] but the subject matter is the filter [05:48] poolie: I goofed on that one a while back myself :), in fact IIRC, it was misguiding you into this channel :) [05:51] np thanks :) [08:17] good morning [08:54] Hello MOTU, I've just become the maintainer for an upstream project (glipper) which is in Universe. Currently glipper is an applet, but the new version 2.0 uses app indicators (and drops applet support). I want to know how you normally deal with a new version that has a major change in functionality. ie. Should the new version use /usr/share/glipper2 to allow it to not conflict with glipper 1.0, or should the old package be renamed glipper-applet, so [08:54] that users who upgrade can will automatically have the app indicator version installed? [08:55] I am assuming that we don't want to drop the old glipper 1.0 package, because there are still people using gnome panel who might rely on it [09:02] morning [09:04] laszlok: That depends a bit on upstream (which you are :)). If you want to maintain gnome-panel support, then we can do whatever. If you're going to drop it and just support appindicators, that's also cool. We can handle either. [09:04] I'm using git-buildpackage making svn-tracking PPA packages, and I'd want to use the version "1.01+svn2530~ppa1". However, this makes git-buildpackage not create an orig tarball, (from my svn branch), is there a way around this or will I need to stick to "1.01+svn2530-ppa1" which does work.. [09:06] arand: git-buildpackage is correct, there. A non-native package version consists of $STUFF-$DEBIAN_REVISION. Since 1.01+svn2530~ppa1 does not contain ‘-’, it's a native version. [09:06] arand: Versioning it as 1.01+svn2530-0~ppa1 would work. [09:06] RAOF: I have removed applet support, and I am no longer going to update the 1.0 branch, so essentially there is no support for the applet version. I guess that means it should just be dropped eh? [09:07] laszlok: Yup, pretty much. [09:07] RAOF: ok thanks, I'll be back when I have 2.0 ready to go in my PPA === kklimonda is now known as Guest46494 === Guest46494 is now known as kklimonda [10:35] does anybody know how to fix this FTBFS? https://launchpad.net/ubuntu/+source/clementine/0.7.1-0ubuntu1/+buildjob/2431201/+files/buildlog_ubuntu-natty-i386.clementine_0.7.1-0ubuntu1_FAILEDTOBUILD.txt.gz [10:37] FYI it was built fine on PPA and pbuilder. [10:38] because you did not have pkgmangler there [10:39] and build failed cause translation pkgmangler complains [10:40] hrw: ok how to fix it? [10:41] ari-tczew: I would just remove all empty *.po files but no idea is it proper fix [10:42] hrw: do you use sbuild? [10:42] no. I use pbuilder but have all pkgmanglers installed [10:43] hrw: it doesn't matter if you have it installed, pbuilder will build package fine anyway [10:45] ari-tczew: but this build error for me looks like related to pkg-manglers only [10:45] hrw: is it a bug in launchpad builders? [10:46] ari-tczew: I think that message about empty PO files is self documenting === yofel_ is now known as yofel === ApOgEE is now known as ApOgEE_away === ApOgEE_away is now known as ApOgEE_afk [14:25] ari-tczew: you can also have those pkgmanglers which are run on the buildds in your pbuilder (I've them in my pbuilder to catch exactly such errors) [14:25] geser: how to set up them?> [14:25] and I "fix" such errors in the past by removing those mentioned (empty) .po files [14:26] ari-tczew: login into your pbuilder (and use --save-after-login to keep those changes) and install pkgbinarymangler (and pkg-dbgsym-create if you want .ddebs too) [14:27] you might check the configuration files in /etc/pkgbinarymangler/ if the tools you want are "enabled" [14:27] geser: what are .ddebs for? [14:27] used for*? [14:28] .ddebs contain the extracted debug symbols from the binaries (those -dbgsym packages are used to generate the backtraces you can see in bugs) [14:30] (I hope I got the package names right as I'm not my Ubuntu to check) [14:30] ari-tczew: .ddeb is ubuntu way of providing debug informations for all packages. kind of automatically generated -dbg packages [14:30] geser: proper names you used === Pici is now known as Guest95063 === Pici` is now known as Pici === ximion1 is now known as ximion [16:51] mav+4.6.2 - is there a known issue with shutting down? when I shut down it goes to TTY, so I have to log in and do shutdown -h now === makl is now known as ximion === ximion is now known as makl === Quintasan_ is now known as Quintasan [19:31] hrw, geser: I have installed pkgbinarymangler in my pbuilder and clementine still builds fine :/ [19:35] ari-tczew: check /etc/pkgbinarymangler/striptranslations.conf (inside your pbuilder) if it's enabled ("enable: true") as I don't remember the defaults [19:44] geser: http://paste.ubuntu.com/591411/ [19:44] failed [19:46] you sure you used "login --save-after-login" when installing "pkgbinarymangler" *inside* your pbuilder? [20:05] geser: yes [20:05] I can try it again [20:29] geser: http://paste.ubuntu.com/591420/ [20:29] is it OK? [20:30] yes [20:31] geser: now just 'exit' ? [20:31] yes, but you might want to check if everything is enabled [20:32] # pkgstriptranslations will do nothing unless enable is set to "true" [20:32] enable: false [20:32] ! [20:33] geser: how to change it? there is no vim, mcedit, nano [20:34] either install an editor (and remove it later if you don't want to have it permanently in the pbuilder) or edit the file from outside (edit /var/cache/pbuilder/build/*/etc/pkgbinarymangler/striptranslations.conf) [20:37] geser: yeah, install an editor... I'm silly [20:53] sed? [20:53] sed s/enable: false/enable: true/ [21:05] geser: It works! [21:05] so, the result is FTBFS :p [21:07] geser: do you know where are these files? http://paste.ubuntu.com/591441/ [21:08] there are not in source directory [21:27] ari-tczew: looks like those files are generated during build but I don't understand enough about translations (and cmake) to tell you how to fix it [23:56] any ideas why there is a sensible-browser and chromium-browser in /usr/bin? [23:57] seidos: sensible-browser is a generic one linking to whichever browser meets its conditions which idr at the moment [23:59] it will try to launch the appropriate browser (or $BROWSER)