[08:54] <evaluate> Hello.
[08:54] <evaluate> If a new release of a program is made, that only includes bugfixes, does it have any chance of making it in for oneiric?
[09:55] <alkisg> I have a package which installs a program that runs on user logon. So when a user installs the package, he needs to logoff/logon for my invisible (no gui) user-session-based "service" to run from /etc/xdg/autostart.
[09:55] <alkisg> Does the packaging policy allow me to run it from postinst as the SUDO_USER, if I detect that that env var exists, and X is running?
[10:22] <tumbleweed> alkisg: I don't think that would be desireable
[10:45] <alkisg> Thank you tumbleweed, I'll put a note for the users to the docs that they need manually start it or logoff+logon
[13:01] <bdrung> tumbleweed: housten, we've had a problem: https://launchpadlibrarian.net/82843129/buildlog.txt.gz
[13:02] <nigelb> *Houston ;)
[13:06] <tumbleweed> bdrung: yeah, noticed that
[13:13] <bdrung> tumbleweed: the typo or the build failure? ;)
[13:20] <tumbleweed> bdrung: the build failure, hadn't got as far as the typo
[13:23] <bdrung> tumbleweed: any idea how to solve this build failure?
[13:26] <tumbleweed> not immediately obvious, and I can't look right now
[14:12] <tumbleweed> bdrung: ah, that was easy. The new binary packages are in NEW
[14:14] <bdrung> :)
[14:30] <ari-tczew> wgrant: could you upgrade this page http://qa.ubuntuwire.org/multidistrotools/all.html to precise?
[14:32] <CarlFK> http://packages.ubuntu.com/search?suite=default&section=all&arch=any&searchon=names&keywords=sphinx2-bin
[14:32] <CarlFK> sphinx2-bin isn't in Oneiric. what' the process for getting it in?  (I am assuming I can port the natty version forward)
[14:54] <tumbleweed> CarlFK: https://launchpad.net/ubuntu/+source/sphinx2/+publishinghistory
[14:57] <CarlFK> tumbleweed: thanks.  how do I find out why Status=deleted ?
[14:57] <tumbleweed> click on the arrow and you can see :)
[14:58] <CarlFK> low popcon ?
[14:59] <CarlFK> any idea where I can see Debian bug #624817 (no the lp bug that it links to)
[14:59] <CarlFK> thank you happy robot
[14:59] <tumbleweed> thanks ubottu
[15:01] <CarlFK> grumble.  but thanks.
[15:01] <tumbleweed> CarlFK: you can take over maintainance of it in debian
[15:04] <CarlFK> joy
[18:45] <c_korn> hello, the compilation of pragha fails because of "libtool: link: cannot find the library `/usr/lib/libcurl.la' or unhandled argument `/usr/lib/libcurl.la'" as I see it is in the /usr/lib/x86_64-linux-gnu/ directory on oneiric. how can I fix this?
[18:49] <sladen> c_korn: could you file it in the bug tracker so that it doesn't get lost?
[18:50] <c_korn> uhm, of course. against which package?
[18:50] <c_korn> so the problem is on the Ubuntu side?
[18:50] <sladen> c_korn: but most likely you're probably missing   sudo apt-get install libcurl-dev
[18:50] <sladen> c_korn: there isn't enough information to tell you what/where/how/who the issue is
[18:51] <sladen> c_korn: I don't even eg. know what software you're trying to compile
[18:51] <c_korn> I have libcurl4-openssl-dev installed
[18:51] <tumbleweed> err, no it sounds like it's bearking because curl was multiarched
[18:51] <c_korn> the music player "pragha" http://code.google.com/p/dissonance/
[18:52] <c_korn> (pragha is not in the Ubuntu repositories)
[18:52] <tumbleweed> c_korn: it may be being directed to libcurl.la by another .la file, see if you can see where that came from
[18:53] <c_korn> uff, should I look for some symbolic link now?
[18:53] <tumbleweed> no, other la files probably
[18:55] <c_korn> find /usr/lib -name *.la ?
[18:55]  * tumbleweed tries to build it
[18:55] <jtaylor> it should not need to know the path at all
[18:56] <c_korn> those are my build depends http://pastebin.com/MP5WAdLS
[18:57] <c_korn> I built the libclastfm0-dev library before. but it should be optional.
[18:58] <jtaylor> autsch
[18:58] <jtaylor> it uses LDFLAGS for libraries
[18:58] <jtaylor> that will bite you with as-needed
[19:01] <tumbleweed> erm c_korn, it built for me (make all)
[19:03] <tumbleweed> (i was building 0.99)
[19:03] <c_korn> hum, maybe it is related to my libclastfm library then
[19:03] <tumbleweed> also, I was on amd64
[19:04] <tumbleweed> yeah it might only need curl for lastfm
[19:05] <c_korn> hm, yeah. it also compiles here without my libclastfm library
[19:13] <c_korn> ok, I have rebuilt clastfm and now also pragha compiles with lastfm support. thanks.
[19:33] <c_korn> well, I think this lintian error explains my problems. http://pastebin.com/DJAMXs7H
[19:36] <tumbleweed> :)
[19:45] <c_korn> hm, shouldn't gensymbols automatically been run with compat 8 ?
[19:48] <tumbleweed> before that, even
[19:53] <c_korn> hum, but I had to generate the symbols for myself
[19:53] <tumbleweed> well, the initial symbols list has to be created by hand. After that it'll be verified at build time
[19:54] <c_korn> ah, ok
[19:54] <c_korn> so I delete one line and see what happens ;)
[19:54] <tumbleweed> remember, it'll differ between architectures
[19:54] <tumbleweed> (err, s/will/may/, e.g. if C++)
[19:55] <c_korn> ok, works ;) dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
[19:55] <c_korn> yeah, I already got into that situation once
[19:55] <c_korn> luckily there is the lib.symbols.arch naming rule of the file.
[20:04] <c_korn> what happened to xulrunner in oneiric?
[20:05] <jtaylor> firefox-dev replaces at least parts of it I think
[20:05] <chrisccoulson> we got rid of it
[20:06] <chrisccoulson> firefox-dev exists purely to provide npapi headers. please don't build anything else against it
[20:10] <c_korn> hum, but there is no xulrunner executable any longer?
[20:14] <c_korn> there is the application http://getbuzzbird.com/bb/ which I started with "xulrunner ./application.ini". how should I do that now?
[20:20] <chrisccoulson> c_korn, you can't. we don't support that anymore
[20:20] <chrisccoulson> you could always grab the upstream xulrunner binary though
[20:21] <c_korn> hum, ok
[21:37] <jbicha> what's the easy/correct way to backport from precise to oneiric-proposed?
[21:38] <tumbleweed> easiest is to just upload to oneiric-proposed, and copy-up to precise
[21:38] <jbicha> ok, what if I already uploaded to precise? since the SRU page said bugs should be fixed in the current development release first
[21:38] <tumbleweed> yeah that's not strictly necessary in the first week or so
[21:39] <tumbleweed> I'd just do exactly the same upload, with an SRUish version, to oneiric-propesed
[21:39] <arand> jbicha: There is a good wiki page on SRU:ing, you've read?
[21:41] <jbicha> arand: yes, but I don't always read every word...
[21:41] <jbicha> I'll need to do a -0ubuntu1.1 then?
[21:42] <tumbleweed> jbicha: what package?
[21:43] <jbicha> totem 3.0.1-0ubuntu8
[21:44] <tumbleweed> jbicha: totem already has an upload in -proposed waiting for verification
[21:45] <jbicha> tumbleweed: right, this upload improves the -proposed fix and fixes a second bug while I'm at it
[21:45] <jbicha> basically, how do I fix this? and how do I do this correctly next time?
[21:46] <tumbleweed> ok, I'd have said use 3.0.1-0ubuntu5.1 if 3.0.1-0ubuntu7 wasn't already there. Because of 3.0.1-0ubuntu7 you'll have to use 3.0.1-0ubuntu7.1 (which is a little misleading, in that it looks like the first SRU)
[21:47] <tumbleweed> you just note on the bug that you're about to replace the proposed versoin with another one, so don't verify it yet
[21:47] <jbicha> so 7.1 or 8.1 then?
[21:48] <tumbleweed> jbicha: it needs to be lower than the version in later releases, so 7.1
[21:48] <jbicha> I was thinking I'd just sync from precise but it looks like that doesn't really work the same way syncing from Debian does
[21:48] <jbicha> ok, and how does copying up work?
[21:50] <tumbleweed> jbicha: if oneiric and precise currently have the same versions, you can upload to -proposed, and ask for the upload to be copied to precise when it's accepted. (as if you'd uploaded it before precise opened) But this should only be done in the first week or so