[00:04]  * ScottK just edited the reportbug conffile to always go back to Debian
[00:04] <funkyHat> I'm poking around in the epiphany package, which is FTBFS, and the configure script exits with an error because it can't find an install script
[00:04] <sistpoty> funkyHat: got a link to the error? (or a failing build log?)
[00:05] <funkyHat> http://launchpadlibrarian.net/31705993/buildlog_ubuntu-karmic-i386.feisty-wallpapers_0.13_FAILEDTOBUILD.txt.gz
[00:05] <c_korn> ScottK: always go back to debian ?
[00:05] <funkyHat> Wait that's not it, sorry -.-
[00:05] <sistpoty> c_korn: to upstreams bug tracker is also a possibility
[00:05] <funkyHat> sistpoty:
[00:06] <funkyHat> http://launchpadlibrarian.net/31703294/buildlog_ubuntu-karmic-i386.epiphany_0.7.0-2_FAILEDTOBUILD.txt.gz
[00:06] <funkyHat> middle-click fail :(
[00:06] <ScottK> c_korn: reportbug in Ubuntu is set not to report to Debian by default.  You can change that in I forget which file in /etc and I've done that since I only use reportbug for reporting bugs to Debian.
[00:07] <c_korn> ScottK: ah, ok. should do that, too. thanks for the hint.
[00:12] <sistpoty> funkyHat: can you pastebin debian/rules please?
[00:12] <sistpoty> (my box is a little bit laden right now with building 3 packages)
[00:13] <funkyHat> sistpoty: http://pastebin.com/f570c7997
[00:14] <sistpoty> funkyHat: interesting, from the packages drawn in as build-depends I imagined that it would run autotools during build (which is not the case)
[00:14] <sistpoty> funkyHat: let me take a look at the source package
[00:15] <funkyHat> sistpoty: the error comes from the configure script, ~ line 1731 http://pastebin.com/m1f5d82a1
[00:26] <sistpoty> c_korn: sorry, gambas2 upload still in the queue, I rebuild *without* applying the debdiff :(
[00:27] <c_korn> sistpoty: you mean the bug has already been fixed and is in the queue ?
[00:28] <sistpoty> c_korn: nope, local rebuild
[00:29] <sistpoty> (so that I don't upload a package where I didn't apply any debdiff *g*)
[00:29] <c_korn> sistpoty: ah, ok :)
[00:29] <sistpoty> funkyHat: ah, I see it now after unpacking the source package: lrwxrwxrwx 1 stefan stefan     35 2009-09-19 01:26 install-sh -> /usr/share/automake-1.10/install-sh
[00:30] <irvingpop> Hi,  I'm looking for some help (or a good guide) packaging a program which has never been packaged before for Ubuntu/Debian
[00:30] <sistpoty> funkyHat: nowadays, we've got automake 1.11
[00:30] <funkyHat> sistpoty: oh! feel silly for not noticing that :)
[00:30] <irvingpop> It's Flashcam ( http://www.swift-tools.net/Flashcam/ )
[00:31] <irvingpop> I'm not the developer, but I need to run this in my environment and I'd like to build a PPA for it
[00:36] <funkyHat> sistpoty: I updated the symlinks, but debuild doesn't like that, I think I need to make a patch that changes them instead, but not sure how?
[00:44] <sistpoty> funkyHat: my best guess is to adjust debian/rules to call a ln -sf in the clean target
[00:44] <ScottK> dh_links won't do it?
[00:45] <sistpoty> ScottK: unless I'm mistaken, dh_link is for installing links in the package, but here the links are only needed for building
[00:45] <ScottK> Ah.  I wasnt' following completely then.  Nevermind
[00:47] <sistpoty> c_korn: sorry to bug you again, actually I did apply the debdiff in the first place, but still it doesn't work: main.cpp:935: error: invalid conversion from 'const char*' to 'char*
[00:47] <c_korn> sistpoty: huh ?
[00:47] <sistpoty> c_korn: let me check the build log
[00:48] <c_korn> sistpoty: oh, grrr. the thing is. I am still on jaunty locally. which does not have the new gcc of course :(
[00:48] <sistpoty> c_korn: that's what pbuilder is for ;)
[00:48] <c_korn> sistpoty: yes, I used the wrong chroot actually :)
[00:49] <sistpoty> heh
[00:53] <c_korn> sistpoty: where does the error occur ?
[00:54] <sistpoty> c_korn: http://paste.ubuntu.com/273849/
[00:55] <sistpoty> c_korn: so main.cpp:935
[00:55] <sistpoty> (why are FTBFS errors frequently on lines divisible by 5?)
[00:55] <sistpoty> *g*
[00:55] <c_korn> sistpoty: oh, I see. it is the same function. (only for sqlite2)
[00:56] <funkyHat> Are the bits inside the rules just sh scripts (i.e. can I use for each, or should I just do an ln -sf for each one?)?
[00:56] <sistpoty> funkyHat: actually rules is a makefile
[00:57] <sistpoty> funkyHat: so you can (to some account) use shell... but with some caution
[00:57] <sistpoty> funkyHat: each line is called in a separate subshell
[00:57] <funkyHat> sistpoty: yeah, I've never used make before, I'm just trying to work out what I can do with it (looking at the make manual at gnu.org as well)
[00:58] <sistpoty> funkyHat: so you'll need to add a \ at the end of a make line to have the following line not be executed in a different subshell
[00:58] <funkyHat> Ok. Still seems slightly better than just doing each one separately
[00:58] <sistpoty> funkyHat: likewise $ is reserved in make, so you'll need to escape it with a \ (for i in foo; do echo $$i; done)
[00:59] <sistpoty> funkyHat: escape with another $ even... (strange enough when I type in shell code as make I my fingers recall the trick)
[01:01] <funkyHat> for i in depcomp install-sh missing ; ln -sf /usr/share/automake-1.11/$$i $$i ; done
[01:02] <c_korn> funkyHat: I think there is a "do" statement missing
[01:02] <c_korn> funkyHat: after the first semicolon
[01:02] <funkyHat> oops! thanks :)
[01:03]  * sistpoty admits that he prefers to have these on extra lines... as that means less complexity but YMMV
[01:05] <funkyHat> My thinking was if automake's version changes again, that's 2 less lines to update, but I guess it only makes a half a second difference, really
[01:06] <sistpoty> yes, but changing 3 simple lines is easier than one complex line... but that's really just a matter of taste ;)
[01:13] <funkyHat> dpkg-deb: warning: 'debian/epiphany-data/DEBIAN/control' contains user-defined field 'Original-Maintainer'
[01:14] <funkyHat> Is that normal, and I've just missed it before?
[01:14] <sistpoty> funkyHat: that's normal
[01:37] <funkyHat> If I create a debian/patches dir, will it be automatically used?
[01:38] <funkyHat> But surely I shouldn't have to? I'm confused about why my debdiff doesn't say anything about my change to debian/rules
[01:39] <c_korn> funkyHat: did you run debuild -S -sa after your changes ?
[01:39] <c_korn> and did you create a new changelog entry using dch -i ?
[01:39] <funkyHat> I just did debuild -S - maybe that's the problem!
[01:42] <funkyHat> c_korn: doesn't seem to make any difference
[01:43] <c_korn> funkyHat: did you overwrite the original diff.gz by running debuild without having the changelog entry incremented (I am without haveing created a new entry) ?
[01:44] <funkyHat> c_korn: possibly :(
[01:44] <c_korn> funkyHat: so you have to redownload it.
[01:44] <c_korn> just overwrite the diff.gz and .dsc file
[01:45] <sistpoty> funkyHat: debian/patches is not automatically used if you manually added it
[01:45] <funkyHat> Can I use a script to get the urls for just those?
[01:46] <funkyHat> sistpoty: turns out I was being silly thinking I need to use it anyway, but thanks, I will remember that :)
[01:46] <sistpoty> funkyHat: but as a rule of thumb: if the package is from debian, and doesn't have a patch system, then don't add one ;)
[01:47]  * c_korn wonders about that rule. won't debian introduce a patch system then because direct code changes are ugly ?
[01:47] <sistpoty> c_korn: what makes you believe that direct code changes are ugly?
[01:48] <sistpoty> c_korn: imho (unless you've got a number of patches that you want to separate), a patch system is ugly
[01:48] <c_korn> if there is a new upstream version the diff.gz might not apply any loner
[01:48] <sistpoty> c_korn: just because a patch applies doesn't mean it's still valid
[01:50] <sistpoty> c_korn: imo no patch system makes e.g. a debdiff or the .diff.gz much more readable, and doesn't add complexity to debian/rules (or to someone needing to change a file)
[01:50] <funkyHat> Can I find the urls for thse files without apt-get source? I don't want to use that as it will overwrite my changes
[01:50] <c_korn> sistpoty: well without a patch system this problem also exists. and if patches are seperated a patch can simply be dropped (but you already mentioned that)
[01:50] <sistpoty> c_korn: the big drawback is however if there are a great number of patches, as you cannot separate these
[01:50] <c_korn> funkyHat: they are in launchpad
[01:51] <c_korn> funkyHat: or on packages.ubuntu.com
[01:51] <c_korn> latter is not updated as regularly
[01:51] <funkyHat> I was hoping for a command that would tell me them, but ok :)
[01:51] <c_korn> well, I am also lokking for such a command
[01:51] <sistpoty> funkyHat: apt-cache showsrc <packagename> gives you a directory
[01:52] <sistpoty> funkyHat: so you can construct the url by http://archive.ubuntu.com/ubuntu/<directory>/<filename>
[01:52] <sistpoty> (adjust the first part with mirror)
[01:53]  * funkyHat might make a script for that :)
[01:53] <funkyHat> If I find I want it again
[01:55] <maxb> funkyHat: Look at pull-*-source from ubuntu-dev-tools
[01:56] <c_korn> hm, that looks like apt-get source to me. would also pull the tarball
[01:56] <sistpoty> hey mterry: looks like you're tackling the tough FTBFS... thanks a lot!
[01:59] <funkyHat> c_korn: that would be fine as long as it doesn't extract it on top of my stuff
[01:59] <c_korn> funkyHat: you can tell it to download only.
[02:01] <funkyHat> Ok, I have a patch for universe for someone to sponsor :)
[02:03] <sistpoty> funkyHat: the entire universe? :P
[02:04] <sistpoty> funkyHat: otherwise debdiff's are welcome ;)
[02:05] <funkyHat> sistpoty: the debdiff is already attached to a bug and waiting for me to subscribe someone ;þ
[02:05] <sistpoty> funkyHat: bug #?
[02:06] <funkyHat> #432834
[02:06] <funkyHat> https://bugs.edge.launchpad.net/ubuntu/+source/epiphany/+bug/432834
[02:07]  * sistpoty takes a look
[02:08] <sistpoty> funkyHat: crack, you're ruining my processing of the sponsors queue. I must severly test epiphany :PO
[02:08] <funkyHat> :þ
[02:10] <sistpoty> funkyHat: test-building... if it succeeds, can you forward the patch to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543037 please?
[02:11] <sistpoty> (the debian/rules snippet should suffice)
[02:11] <funkyHat> sistpoty: I was wondering if I should forward the whole patch, or just the patch for debian/rules ?
[02:11] <funkyHat> Ah :)
[02:11] <sistpoty> heh
[02:12] <funkyHat> Or whether I should make a patch with debian-y stuff in debian/changelog as well
[02:14] <sistpoty> funkyHat: well, debian has a new version already, so you'd need to readjust that to forward it
[02:14] <sistpoty> funkyHat: usually the patch itself is enough
[02:15] <funkyHat> I was also in the middle of checking which version of automake is in debian at the moment, but forgot about it :)
[02:15] <funkyHat> And it's 1.11 anyway
[02:17] <c_korn> sistpoty: ok, now the package fails to build for me at another place: http://pastebin.com/d6818bdb
[02:19] <sistpoty> c_korn: interesting, at a glimpse, it looks like a build-dependency decided to change the api
[02:19] <c_korn> (again the line can be divided by 5 :)
[02:20] <sistpoty> hehe
[02:20] <c_korn> this is the line: 	snprintf(ctx,16*sizeof(char),"%.2g",THIS->doc->getPDFVersion());
[02:20] <sistpoty> c_korn: I'd need to take a closer look, but please give me a few minutes
[02:21] <c_korn> should I pastebin the whole file ?
[02:21] <funkyHat> sistpoty: which bit do I need precisely, the line startind with diff -u or just the line starting with --- downwards?
[02:21] <sistpoty> funkyHat: the one with ---
[02:22] <funkyHat> Ok. let me know if it's ok to send :)
[02:22] <sistpoty> funkyHat: ok to send
[02:22] <funkyHat> Cool
[02:23] <c_korn> hm, grep -R getPDFVersion . only outputs this line.
[02:24] <funkyHat> Been wanting to get involved for months now, and finally managed to get somewhere :). Thanks for your help
[02:24] <funkyHat> I will come back tomorrow and try and squish some more FTBFSs :)
[02:26] <sistpoty> funkyHat: epiphany uploaded btw. ;)
[02:27] <funkyHat> Yay :)
[02:27] <sistpoty> (and crap, I lost a live at level 1)
[02:29] <c_korn> in the PDFDoc.h file (where the class is defined) there is this now: http://pastebin.com/d2689dd6a
[02:31] <sistpoty> c_korn: looks like you're one step in advance, I just looked up that the package to search for clues if obviously libpoppler-dev
[02:32] <c_korn> yep, and here getPdfVersion() is introduced: http://www.mail-archive.com/poppler@lists.freedesktop.org/msg02946.html
[02:33] <c_korn> hm, those changes are in qt/poppler-qt.h and not PDFDoc.h
[02:34] <c_korn> puh, I am getting tired
[02:36] <c_korn> sistpoty: here, the bad commit is: http://lists.freedesktop.org/archives/poppler/2009-August/005021.html
[02:37] <c_korn> http://pastebin.com/d6dcba8ee
[02:38] <c_korn> here in git: http://cgit.freedesktop.org/poppler/poppler/diff/poppler/PDFDoc.h?id=5491d16dfbd73f0256c62e49d02622dc3185012e
[02:39] <c_korn> how should the line be changed correctly ?
[02:40] <sistpoty> hm... I'm also getting a tired
[02:41] <sistpoty> c_korn: it looks to me, as if the function puts the version into a string
[02:41] <sistpoty> c_korn: and I hope that it was a double in the form of "major.minor"
[02:42] <sistpoty> c_korn: so the fix would be snprintf(ctx,16*sizeof(char),"%d.%d",THIS->doc->getPDFMajorVersion(), THIS->doc-getPDFMinorVersion());
[02:52] <quentusrex> what's a good key word for something that downloads tons of files ???
[02:52] <quentusrex> heavy? all? complete? thick?
[02:53] <sistpoty> ban?
[02:59] <c_korn> sistpoty: done. https://bugs.launchpad.net/ubuntu/+source/gambas2/+bug/432792/comments/2
[03:00] <c_korn> should I have opened another bug about the API change ?
[03:02] <sistpoty> c_korn: I don't think so, I guess that change was blessed already
[03:02] <sistpoty> c_korn: /me looks and test-builds again
[03:04] <c_korn> ok, just leave a comment in the bug report. and if everything is fine I will forward this patch to Debian
[03:04] <c_korn> I really have to sleep now
[03:04] <c_korn> sistpoty: thank you very much for your help.
[03:04] <sistpoty> c_korn: thank you for fixing another FTBFS ;)
[03:04] <c_korn> I hope I will be able to fix those bugs on my own in the future
[03:05] <c_korn> sistpoty: heh, np. bye.
[03:05] <sistpoty> cya
[04:27]  * sistpoty goes to bed, gn8 everonye
[04:27] <sistpoty> everyone evene
[06:58] <quentusrex> Anyone know if this is a valid package name: freeswitch-sounds-music-1.0.8 ???
[07:07] <jmarsden> quentusrex: I'm not an expert, but package *names* do not usually have the -1.0.8 version number on the end.  The name (the first word of the first line of debian/changelog) would be freeswitch-sounds-music.  The 1.0.8 would inside () as part of the second word of that first line of debian/changelog ... (1.0.8-1)  or whatever is appropriate.  Packages with a number as part of the actual package name usually mean the pa
[07:07] <jmarsden> ckage is a library and the number is the SONAME version.
[07:19] <quentusrex> jmarsden: the numbers at the end are the version
[07:20] <quentusrex> but having -'s in the name is ok?
[07:33] <quentusrex> what's the best method to just copy files to a directory from within a package?
[07:33] <quentusrex> I'm aware of the *.install files
[07:34] <quentusrex> I need to copy a file that is currently in ./sounds/ into /opt/freeswitch/sounds/en/us/
[07:34] <quentusrex> is there a package automagic way to get it to use the install file to copy it there?
[08:00] <jaguar_> Hello....
[08:02] <jaguar_> Hoooi....Anybody there.....
[08:02] <fabrice_sp> Hi jaguar_
[08:02] <fabrice_sp> looking for help on packaging?
[08:02] <mrooney> If I want to make a python package PPA for Intrepid -> Karmic, do I build for intrepid and copy the package forward on LP?
[08:03] <mrooney> I assume I don't need to change the target in the changelog and upload three times?
[08:03] <fabrice_sp> mrooney, I always upload a new package, with karmic reference in changelog
[08:04] <mrooney> fabrice_sp: ah okay, you would do three different uploads, changing the reference each time?
[08:05] <fabrice_sp> mrooney, that's what I do, because I tried to copy one package some time ago, and it didn't worked. You could ask in #launchpad or try to copy it :-)
[08:07] <jaguar_> Hooooooooi...........
[08:08] <jaguar_> fabrice_sp: Hello... Fab
[08:17] <quentusrex> fabrice_sp: what do you think would be a good key word that would download all packages below it? rather than specify one of the packages that are required this virtual package would download them all: thick? fat? complete? heavy?
[08:35] <fabrice_sp> quentusrex, it's too early for me to be reative :-)
[08:36] <fabrice_sp> creative
[08:43] <quentusrex> fabrice_sp: :)
[08:44] <quentusrex> maybe you can help with this question. I have a data package... it's one job is to copy a set of files from the package to a destination directory.
[08:44] <quentusrex> what's the most proper way to do this? *.install files?
[08:44] <quentusrex> or a 'cp ./files/* /etc/freeswitch/sounds/ '
[08:44] <quentusrex> in the debian/rules ?
[08:46] <fabrice_sp> .install files
[08:46] <fabrice_sp> it's clearner
[08:46] <fabrice_sp> cleaner
[08:46] <quentusrex> do you have an example of how to set that up? I know I should put " etc/freeswitch/sounds/* " in the file
[08:47] <quentusrex> but where should I put the files?
[08:48] <fabrice_sp> you install everything in a place, and set up the .install files
[08:48] <fabrice_sp> dvdstyler, IIRC
[08:48] <quentusrex> do you have an example? everything I search for in google brings the wrong results...
[08:49] <fabrice_sp> IIRC I did it for dvdstyler
[08:49] <fabrice_sp> or you can look fter a -data package
[08:49] <fabrice_sp> in packages.ubuntu.com, for example
[08:53] <quentusrex> fabrice_sp: I must be tired... I can't find a link to the source files to see the *.install files...
[08:54] <fabrice_sp> quentusrex, https://launchpad.net/ubuntu/karmic/+source/dvdstyler/1.7.3-0ubuntu3/+files/dvdstyler_1.7.3-0ubuntu3.dsc
[08:54] <fabrice_sp> use dget with that url
[08:55] <quentusrex> and to extract it?
[08:56] <Laney> dget -x
[08:56] <Laney> or dpkg-source -x
[08:56] <fabrice_sp> dpkg-source -x or use directly apt-get source dvdstyler
[08:57] <fabrice_sp> too late :-)
[08:57]  * Laney uses pull-lp-source
[08:57] <jaguar_> fabrice_sp: Hello...
[08:57] <fabrice_sp> hello jaguar_
[08:57] <jaguar_> Can i ask you something...?
[08:58] <quentusrex> fabrice_sp: I don't see any *.install files...
[08:58] <jaguar_> fabrice_sp: I'm new to IRC...
[08:58] <fabrice_sp> !ask | jaguar_
[08:58] <fabrice_sp> :-)
[08:59] <jaguar_> ubottu: OK SIR...
[09:00] <jaguar_> I' not bad in 'C' and need to contribute to linux. How can i do that...?
[09:00] <fabrice_sp> quentusrex, you're right. quadrispor changed from .install to .files
[09:00] <fabrice_sp> you can look at 11.7.2 version that stil uses .install files
[09:01] <fabrice_sp> jaguar_, you can look at the topic
[09:01] <fabrice_sp> for example, http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909.html
[09:01] <jaguar_> fabrice_sp: yes i'm going to the page. tnx.
[09:02] <fabrice_sp> jaguar_, yw :-)
[09:02] <wgrant> (that page will mark superseded versions in a few minutes)
[09:03] <quentusrex> fabrice_sp: where are the actual files that are to be installed in usr/share/*
[09:03] <quentusrex> ?
[09:03] <fabrice_sp> thanks wgrant !
[09:03] <fabrice_sp> quentusrex, install in debian/tmp
[09:04] <quentusrex> fabrice_sp: I still don't see where to put the files that will be installed into usr/share/*
[09:06] <fabrice_sp> quentusrex, you call the 'make install'  to install everything in debian/tmp, and after, you split the files between the pacakge with .install files
[09:07] <fabrice_sp> or like quadrispro has done with dvdstyler: you install everything in the normal package directory, and exctract the /usr/share files from there with a .install file
[09:07] <quentusrex> fabrice_sp: I am still confused. this sucks... I thought there was a: you place the files here: debian/usr/share/*, then put usr/share/* in the *.install file
[09:09] <fabrice_sp> you can install debian/<package name>/usr/share, with <package name> = name of the 'principal' package
[09:10] <fabrice_sp> and then put <package name>/usr/share in .install file
[09:15] <quentusrex> so anything I put in debian/freeswitch/etc/freeswitch/sounds/* will be installed into /etc/freeswitch/sounds/* if I put: etc/freeswitch/sounds/* into freeswitch.install ?
[09:15] <quentusrex> wow... that was long...
[09:16] <jaguar_> fabrice_sp: I can see a lot of packages in that page... What should I do now...?
[09:18] <fabrice_sp> quentusrex, in that case, you don't need a .install file
[09:18] <fabrice_sp> jaguar_, look at the compilation error, and see if you can fix it
[09:18] <quentusrex> fabrice_sp: what would I need then?
[09:19] <quentusrex> I have files that just need to be copied and pasted into a folder, that's it... it's a data package.
[09:19] <jaguar_> fabrice_sp: Yes Sir.
[09:22] <wgrant> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909-karmic.html <- Styling sucks, but it now identifies superseded versions.
[09:24] <jaguar_> fabrice_sp: I'm starting with 'gamine'....tnx
[09:26] <wgrant> jaguar_: 'gamin' is a bad choice. The version for which the build failed is superseded, so it might already be fixed.
[09:26] <jaguar_> wgrant: can you suggest one....?
[09:27] <wgrant> jaguar_: I'm afraid not. I need to run to dinner.
[09:27] <jaguar_> wgrant: k
[09:36] <AnAnt> james_w: would you review devscripts ?
[09:38] <fabrice_sp> quentusrex, if you want to spli the /use/share directory to freeswitch-data, you should create a freeswitch-data.install
[09:39] <quentusrex> fabrice_sp: I don't want to split it
[09:39] <fabrice_sp> my English sucks this morning :-/
[09:39] <fabrice_sp> I thought you wanted to create a -data package
[09:39] <quentusrex> I have one package, but I'm trying to split it into application, and sound files
[09:39] <fabrice_sp> in different packages, then?
[09:39] <quentusrex> so I don't have to upload the sound files each time
[09:39] <quentusrex> yes
[09:39] <quentusrex> so the data package should just copy the files into place.
[09:40] <fabrice_sp> and this files are installed by the make install command?
[09:41] <quentusrex> they are currently
[09:41] <quentusrex> but I'm trying to pull them out to be installed and downloaded/uploaded separately.
[09:49] <fabrice_sp> quentusrex, so you just need to add a freeswitch-data.install file, with the files/directory you want to move there
[09:50] <fabrice_sp> buildd don't have access to Internet, so you won't be able to download files when building the package
[09:51] <fabrice_sp> actually, it would easier if you had some 'rules' or place to look at
[09:51]  * fabrice_sp needs more coffee this morning
[10:38] <debfx> siretart: what do you think about syncing keepassx 0.4.1 to ubuntu? does it need a FFe? bug #431798
[11:46] <directhex> has anyone who isn't me had problems connecting to msn lately? pidgin or epiphany, makes no difference
[11:46] <directhex> empathy
[11:46] <directhex> bah
[11:46] <Laney> how lately?
[11:46] <Laney> I connected about 8.30 this morning
[11:51] <pochu> I'm connected right now using emesene
[11:51] <pochu> no problems recently
[11:53] <directhex> hm. i changed my password, now it seems happier
[11:56] <Laney> gwibber pulls in gnome-mount?!
[20:29] <quentusrex> What's the difference between architecture: 'any' and 'all'
[20:32] <ScottK> quentusrex: If a package is arch all, then it can be run on all architectures.  We build these in i386, but then are used on all of our architectures.  Arch any, can be built for any architecture, but needs to be compiled for each architecture it will run on.
[20:33] <jmarsden> quentusrex: See http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
[22:14] <ripps> Does anybody here know how to change my gpg key to be passwordless so that I can automatically sign and upload packages automatically using fta's ppa-bot without having to give my gpg password everytime it runs.
[22:14] <Laney> you should use a separate key
[22:15] <ripps> Laney: what do you mean?
[22:15] <Laney> it's a bad idea to have your primary key unprotected
[22:15] <Laney> just make a new one which is solely for this ppa
[22:16] <ripps> hmmm..... I suppose that's an option. The ppa is a team ppa, is it possible to give a team a gpg key?
[22:16] <Laney> no
[22:16] <Laney> that is also a bad idea if one member gets the key compromised
[22:17] <ripps> it's kindof inconvient, because right now, I can only create, sign, and upload packages from this computer. Your saying I can't create a shared key so other people can upload to ppa besides me?
[22:21] <Laney> no, you can have a team PPA. Each member of the team has their own key.
[22:22] <ripps> Oh, I think I get it.
[22:22] <ripps> But I will have to register this new key with my account on launchpad
[22:22] <Laney> sure
[22:26] <ripps> Okay, when I goto seahorse and try to create a new pgp key, it gives me an error when I try to create a key without a password
[22:27] <ripps> How do subkeys work? is it possible to create a passwordless subkey?
[23:07] <funkyHat> On the FTBFS page, what do the slightly faded-looking colours mean?
[23:08] <funkyHat> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909.html
[23:08] <c_korn> funkyHat: what do you mean ?
[23:09] <funkyHat> c_korn: see some of the red boxes are not as red as the others?
[23:09] <c_korn> funkyHat: currently not. can you give an example ?
[23:10] <funkyHat> The top 3 (abiword, asio, beecrypt) are, the next 2 aren't, cin is, clutter isn't, etc.
[23:12] <funkyHat> Oh, superseded
[23:14] <c_korn> don't know what you mean
[23:14] <c_korn> but glad you found out :)
[23:27] <wgrant> funkyHat: You might notice the '(superseded)' after the version number. Style improvement suggestions welcome.
[23:28] <jmarsden> ripps: You should be able to use an agent to remember your GPG passphrase so you only enter it once per session.  This is way more secure than trying to create and use passphrase-less keys.  man gpg-agent for more info
[23:28] <funkyHat> wgrant: oh, yeah, I didn't notice that before :)
[23:35] <funkyHat> wgrant: I guess <span style="float: right">(superseded)</span> would make that clearer
[23:36] <funkyHat> As they'd all line up, and I'd be less likely to just skim that bit thinking it's part of the version
[23:38] <funkyHat> That might be helpful for other people. I know what it means now anyway:)
[23:42] <lifeless> james_w: how do I tell package imports that there is an original bzr branch to use for <package foo>