[07:39] <AnAnt> Hello, where can I read about the discussion regarding Thunderbird (might) be the default mail client, and the "specific tasks" upon which this will be decided ?
[07:43] <RAOF> AnAnt: You can find the etherpad document linked from the schedule on uds.ubuntu.com (I think the session was on Thursday?), but the specific tasks weren't actually decided there, just the “themes”.
[07:49] <dholbach> good morning
[07:53] <AnAnt> dholbach: Hello
[07:54] <dholbach> hey AnAnt
[07:54] <AnAnt> dholbach: thanks for the ACKs
[07:54] <dholbach> no worries :)
[09:12] <flower> could it be true that if you backport from meerkat to lucid and let meerkat stand in you changelog file, the system asks for a partial distro upgrade?
[09:52] <flower> # DIST=lucid ARCH=i386 pbuilder create
[09:52] <flower> W: /root/.pbuilderrc does not exist
[09:52] <flower> I: Distribution is sid.
[09:52] <flower> I: Building the build environment
[09:52] <flower> :/
[09:53] <flower> on debian that is
[09:53] <flower> http://fpaste.org/vNpg/ .pbuilderrc
[09:54] <flower> I: Distribution is sid. sould be I: Distribution is lucid. right?
[09:54] <jtaylor> set HOME
[09:54] <jtaylor> sudo -H
[09:55] <jtaylor> newer sudo does nto preserve HOME env variable, this was reverted in natty
[09:55] <jtaylor> but debian did not
[09:55] <flower> is it possible to do it with su on debian?
[09:56] <jtaylor> if you copy the pbuilderrc I don't see why not
[09:56] <flower> what's the command then, I don't suppose it's just # -H
[09:57] <jtaylor> cp /your/user/home/.pbuilderrc /root/
[09:58] <flower> I: Distribution is sid.
[09:58] <flower> still
[10:00] <flower> something wrong with the .pbuilderrc?
[10:01] <flower> http://fpaste.org/vNpg/
[10:02] <jtaylor> all the debia/ubuntu magic is commented
[10:02] <jtaylor> so probably no
[10:02] <jtaylor> s/no/its wrong/
[10:03] <flower> hmm
[10:04] <jtaylor> you also need to install the ubuntu keyring
[10:04] <flower> I am on sid
[10:05] <jtaylor> if you want to build for lucid
[10:06] <flower> is that keyring in debian?
[10:06] <jtaylor> no
[10:10] <flower> anyway it doesn't work
[10:11] <jtaylor> try --distribution lucid
[10:13] <flower> E: Failed getting release file http://ftp.nl.debian.org/debian/dists/lucid/Release
[10:15] <jtaylor> set the correct mirror, ftp.ubuntu.com
[10:15] <flower> # Mirrors to use. Update these to your preferred mirror.
[10:15] <flower> DEBIAN_MIRROR="ftp.nl.debian.org"
[10:15] <flower> UBUNTU_MIRROR="ftp.ubuntu.com"
[10:15] <jtaylor> pbuilder uses MIRRORSITE
[10:16] <jtaylor> it can't work if you comment out all the changes needed to use it in ubuntu ...
[10:16] <flower> hmm I find that doc about pbuilder and ubuntu rather unclear then
[10:17] <flower> very unclear to see what you have to comment out and what not
[10:17] <flower> grr
[10:17] <flower> https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders
[10:18] <jtaylor> its a bit unclear, it does not mean comment out everything after optionally, bu only the following line
[10:19] <flower> that's very confusing imho
[10:27] <flower> pbuilder-dist lucid i386 create
[10:28] <flower> ok
[10:46] <stlsaint> does bzr-builddeb have a option to sign the package at build?
[10:48] <jtaylor> bzr-buildpackage for sure has
[11:01] <stlsaint> jtaylor: aye, thakns
[11:01] <stlsaint> thanks even
[11:35] <wejaeger> Hey, anyone up for reviewing http://revu.ubuntuwire.com/p/l2tp-ipsec-vpn
[13:20] <stlsaint> im having a issue with signing my package
[13:20] <stlsaint> gpg --list-keys shows that i have keys there but when i try and sign i get error:
[13:20] <stlsaint> gpg: /tmp/debsign.X8IR3dyh/lxdm_0.3.0-0ubuntu5.1.dsc: clearsign failed: secret key not available
[13:20] <stlsaint> debsign: gpg error occurred!  Aborting....
[13:21] <jtaylor> stlsaint: are you passing the correct keyid?
[13:24] <stlsaint> jtaylor: hrm i thought so i will double check again
[13:25] <stlsaint> jtaylor: is the syntax: debuild -S -k <id> -sa
[13:26] <jtaylor> -k<id> no space (but not sure if that is required
[13:26] <StevenK> I think either work
[13:28] <stlsaint> StevenK: nope, cannot be a space
[13:28] <stlsaint> jtaylor: as always thank you
[14:05] <stlsaint> HA! Built a package and now i have no idea where pbuilder placed the .deb
[14:06] <directhex> ..
[14:06] <stlsaint> directhex: its not .../result
[14:07] <stlsaint> directhex: i used a different pbuilder and forgot to use the --buildresult option
[14:12] <arand> stlsaint: /var/cache/pbuilder/result/ ?
[14:13] <arand> stlsaint: That's the default locatin.
[14:15] <stlsaint> arand: yea but me fiddling around with my pbuidlerrc trying to configure multiple pbuilders has my stuff rearranged
[14:15] <stlsaint> ima fix it all in a min
[14:15] <arand> Ah, :)
[14:21] <stlsaint> would anyone mind taking a look at my pbuilder to see if something is wrong
[14:21] <stlsaint> i have it moved to /root/.pbuilderrc due to errors before and now it seems like its not doing what i want it to
[16:01] <l3on> Hello.. I'm going to upgrade natty at oneiric, but something is wrong with apt:
[16:01] <l3on> The following packages will be REMOVED:
[16:01] <l3on>   eclipse eclipse-cdt eclipse-jdt eclipse-pde eclipse-platform eclipse-plugin-cvs evolution evolution-exchange evolution-plugins-experimental libgvfscommon0 libperl5.10
[16:01] <l3on>   libpurple0 pidgin-skype telepathy-haze
[16:02] <l3on> what the hell? why eclipse / evolution / pidgin_skype and others will be removed?
[16:02] <jtaylor> l3on: please read this: http://ubuntuforums.org/showthread.php?t=1751299
[16:03] <Laney> !ubuntu+1
[16:03] <Laney> err
[16:03] <broder> haha
[16:03] <arand> l3on: Repository turbulence, likely.
[16:03] <l3on> thanks jtaylor
[16:04] <l3on> arand: turbulence during from few weeks :P
[16:06] <l3on> I remember that 2 days after natty release I changed repository to oenric, but I was unable to upgrade due to eclipse error :/
[16:13] <arand> l3on: Hmm, it may be eclipse having inmproper dependency specifications...
[16:16] <Laney> churn in the development release is expected
[16:16] <Laney> and such questions are better placed in #ubuntu+1
[16:55] <RainCT> nhandler: Hey. I can sponsor if needed (keyring package).
[17:21]  * micahg is going bonkers from doing build tests before requesting a sync and then getting build failures when the sync happens...
[18:27] <doctormo> Hey guys, I have a python package which I'm packaging up for debian/ubuntu
[18:28] <doctormo> It provides a number of plugins for different image programs, so I'm using a seperate deb for each plugin and a central library deb for the main python library
[18:28] <doctormo> The problem is I don't know how to correctly set up the distutils and the debian packaging to do this.
[18:29] <wejaeger> Hey, anyone up for reviewing http://revu.ubuntuwire.com/p/l2tp-ipsec-vpn
[18:32] <tumbleweed> doctormo: which package is it, and what excatly are you having trouble with?
[18:34] <doctormo> tumbleweed: lp:dastash basically the trouble I think is between the release name 'dastash' and the deb package name 'python-dastash'
[18:35] <tumbleweed> yes, if it should be called python-dastash
[18:35] <tumbleweed> are you working on the packaging in that branch?
[18:36] <doctormo> tumbleweed: I am yes, I just pushed what I have so far.
[18:43] <tumbleweed> doctormo: firstly; to be able to import dastash, you need to build-depend on everything it needs to be importable
[18:43] <tumbleweed> (an easy workaround there is to read the .py file and look for '__version__ = ' instead of importing it.
[18:43] <doctormo> I see
[18:44] <tumbleweed> also, you need to import setup from distutils.core (or setuptools if you need it)
[18:45] <doctormo> tumbleweed: Yes I fix that in rev 8, pushed rev 9 now.
[18:48] <tumbleweed> doctormo: next issue, your setup.py doesn't actually install anything, that's why you are having trouble with the other packages
[18:49] <doctormo> tumbleweed: It should be at least installing the one script and one module shown.
[18:49] <doctormo> But it doesn't even do that.
[18:50] <tumbleweed> it installs one script, by the look of it
[18:51] <doctormo> tumbleweed: Nothing appears in any of the deb files
[18:52] <tumbleweed> doctormo: worry about that later. Start by looking at what gets installed into build
[18:52] <doctormo> hmm, so far, just the script
[18:53] <tumbleweed> btw, you really shouldn't be using Provides: ${python:Provides}. That's for special, very rare, situations. And you probably should be using dh_python2 for a new package, instead of python-support. But let's get it working first...
[18:54] <doctormo> tumbleweed: The provides/deps were removed, pull a fresh version.
[19:01] <tumbleweed> doctormo: hint: it's not called "modules"
[19:02] <doctormo> Do I presume I put all the other files into setup.py too as data?
[19:02] <doctormo> (I had thought the install scripts would cover those, but aprrently not)
[19:04] <tumbleweed> you can install them with setup.py or dh_install. But if you install them with setup.py you'll need dh_install them into the correct packages anyway, so there's really no point in doing it with setup.py unless you want to make life easier for people installing on other distributions
[19:11] <doctormo> tumbleweed: I figured that was the case, but it doesn't want to work and I can't see the issue.
[19:13] <tumbleweed> doctormo: dh_install: gimp-plugin-dastash missing files (gimp/*.py), aborting
[19:13] <tumbleweed> ^ that's really very simple. There is no such file (gimp is empty)
[19:17] <doctormo> tumbleweed: I'd made some dumy files which is why I never saw that error, I've commited them now.
[19:17] <doctormo> The problem is, I think dh_install can't find my files to package them
[19:18] <doctormo> And I don't think the python debhelpers can package it correctly because my package is called python-sdstash.
[19:19] <doctormo> Ah wait, the inkscape plugin is the one missing files.
[19:58] <doctormo> OK so I have everything but the python module, it doesn't want to be installed by dh_install, but it won't be installed via anything else either.
[19:58] <doctormo> It's like it's a bunch of floating files in build which won't be nailed down to the package in debian/control
[20:03] <persia> Is the set of files deterministic?
[20:12] <keffie_jayx> Been trying to create a debootstrap for Onieric in a Lucid machine using pbuilder. But it complains about not having the Onieric script. this means that some of the tools have not been ported to lucid?
[20:13] <jtaylor> just copy any other script to the name of oneiric
[20:13] <jtaylor> there all the same
[20:15] <jtaylor> (their all symlinks to gutsy)
[20:18] <arand> doctormo: Are you still having issues with the inkscape-plugins one?
[20:19] <doctormo> arand: I think the inkscape plugin is going in the right place, but the python module isn't.
[20:21] <keffie_jayx> jtaylor: thanks :)
[20:28] <arand> doctormo: Hmm, seems I was wrong in my hunch why it wasn't working, sorry...
[20:28] <doctormo> arand: Thanks for having a look anyway
[20:28] <doctormo> I still have no clue how setup.py links to debian/control
[20:30] <persia> doctormo, It doesn't.  setup.py is executed with appropriate arguments to drop stuff in a to-be-packaged staging area.  If there is one binary package, this entire staging area is stuffed into a package.  If there are multiple binary packages, dh_install extracts bits from the shared staging area into staging areas for each binary package.
[20:31] <maco> foo.install files can be used to tell which binary package each file goes in
[20:31] <doctormo> so I need to make a dh_install thing for the python lib somehow? are there any examples?
[20:32] <persia> just create a debian/python-whatever.install file that lists all the files you want to end up in the package by relative path (e.g. usr/bin/wrapper).  Wildcards are accepted.
[20:33] <doctormo> persia: It's not the user/bin that worries me, it's the /usr/share/pyshared/ -> /usr/lib/python2.6/blah links and so on.
[20:33] <ScottK> You should let your python helper handle those bits.
[20:35] <doctormo> ScottK: How?
[20:35] <ScottK> If you've got a proper setup.py then it should be roughly automagical.
[20:36] <ScottK> dh $@ --with python2 may be sufficient.
[20:36] <ScottK> (if you're using dh_python2, which I do recommend)
[20:37] <ScottK> That's for a package with one binary.
[20:37] <ScottK> For a package with multiple binaries it's slightly more tricky.
[20:37] <ScottK> You can use pyspf as an example for that.
[20:40] <doctormo> Thanks for the example
[20:45] <doctormo> OK I think just stuffing the module into pyshared is sufficient according to the example and my testing.
[20:45] <doctormo> Sometimes automagic is as alchemy.
[20:49] <doctormo> Thanks for your help persia, ScottK and maco
[20:49] <ScottK> You're welcome.
[20:49] <ScottK> BTW, that probably won't work for Maverick, but should be fine for Natty.
[20:54] <arand> doctormo: Bit late but http://paste.debian.net/117419/ seems to get things working via a .install file
[20:54] <arand> Well provided that is where the files should end up..
[20:55] <doctormo> arand: The second line is correct, but if you put the python module directly into python2.6 it'll cause issues. Maybe.
[20:56]  * arand looks innocent, knowing barely a word of python
[21:09] <ScottK> Yeah.   Don't do that.
[21:09] <ScottK> python2.7 is the default in Natty, so it wouldn't work for that.
[21:10] <paultag> ScottK: how dare you do that. Don't you know Debian still has 2.6?
[21:10] <paultag> ;)
[21:10] <ScottK> Sigh.
[21:11] <Rhonda> Ubuntu is always the python (and gcc toolchain) testbed for Debian, did noone tell you yet?
[21:11] <paultag> it'd funnier if someone had actually not said that
[21:11] <paultag> Rhonda: :)
[21:12] <ajmitch> Rhonda: causing trouble again?
[21:13] <Rhonda> Me? Never!
[21:18] <Rhonda> ajmitch: Actually I'm a bit puzzled by that question, to be honest.
[21:26] <ajmitch> Rhonda: hm?
[21:26] <Rhonda> Either I read it wrong, or I don't understand what you try to imply.
[21:26] <ajmitch> Rhonda: that what you wrote could be jokingly trolling :)
[21:27]  * persia suspects morning sarcasm to be colliding with late-night worries
[21:27]  * ajmitch is still waking up & drinking caffeine
[21:27] <Rhonda> ajmitch: So then what about the "again" part?
[21:27] <ajmitch> I was joking
[21:28] <Rhonda> More seriously, there's nothing bed with Ubuntu switching some things earlier than Debian. In some sense this is one of the ereas where Ubuntu is giving back a lot to Debian in the sense of sent patches for future troubles.
[21:28] <Rhonda> s/bed/bad/
[21:28] <Rhonda> It's _me_ who should in bed, I guess.
[21:28] <ajmitch> heh
[21:32] <Rhonda> See, it's only trolling if you want to take it as such. But as one person who has received a few of these forwarded bugs for toolchain changes, I'm very grateful about that Ubuntu takes the lead in this area. :)
[21:39] <ScottK> This got started by a certain DD complaining yesterday that Ubuntu trying to help fix RC bugs in Debian so that the Python transitions can get done faster in Debian is Ubuntu telling Debian what to do.
[21:39]  * ajmitch shall just be quiet & do work instead :)
[21:39] <ScottK> (and no, I don't understand it either)
[21:39]  * ajmitch was in that channel at the time
[21:40] <Laney> evening all
[21:40] <ajmitch> hi Laney
[21:41] <Rhonda> ScottK: Oh, then my tongue-in-cheek comment (even if the background from my side is an appretiation of the effort) was with a bad timing. Sorry for that then.
[21:41] <ScottK> No problem.
[22:19] <rockclimb123> I uploaded a new version of a package to Debian unstable yesterday. Any idea how often the sync to Ubuntu takes place?
[22:21] <arand> rockclimb123: Pretty often I think (suncing of my AC upload was within a day or two)
[22:21] <rockclimb123> OK, thanks
[22:21] <broder> rockclimb123: syncs are run by hand by an ubuntu archive admin, usually once a day during this stage of the ubuntu cycle
[22:23] <rockclimb123> Excellent, I was hoping it would be daily. The version in Ubuntu won't build right now because of a missing dependency.
[22:24] <ajmitch> is it unmodified in ubuntu?
[22:24] <rockclimb123> Yes. The dependency got renamed in Debian, but the binary packages are still hanging around in unstable so I didn't pick it up.
[22:26] <rockclimb123> Actually I think some changes are probably needed to the dependency too to make upgrades work properly - I'll figure that out next.
[23:44] <jtaylor> is bug 782414 ready to request a SRU?
[23:52] <ScottK> jtaylor: Do you need to build-dep on python-setuptools or just python-pkg-resources?
[23:54] <jtaylor> ScottK: setuptools, the setup.py tries to import it and only then sets the requires
[23:54] <ScottK> OK.
[23:54] <ScottK> Then yes.  I'd say so.
[23:55] <ScottK> I accepted the nomination for Natty.