[00:00] <dhillon-v10> crimsun: yah I found it thanks though
[00:01] <geser> dhillon-v10: https://wiki.ubuntu.com/DistributedDevelopment/Documentation/Merging describes bzr merges
[00:02] <dhillon-v10> geser: I remember you telling me that, I just forgot about it :)
[00:10] <dhillon-v10> geser: can you have a look at this: http://paste.ubuntu.com/349722/ and tell me if it looks right, its for this bug: https://bugs.edge.launchpad.net/ubuntu/+source/goldendict/+bug/499335
[00:13] <geser> dhillon-v10: as you merged our changes on the current version from testing the version should be: 0.9.1~git20091117-1ubuntu1 and target lucid (not karmic)
[00:15] <geser> and as the merges change removes the file, telling "Adding a .desktop file" is wrong
[00:16] <dhillon-v10> geser: alright thanks a bunch, I'll fix those
[00:17] <dhillon-v10> geser: one question, how do you guys figure out what's wrong so quickly
[00:18] <geser> experience :)
[00:19] <geser> mostly it was looking at the changelog entry (check the version and target) and compare if the mentioned changes match the changes in the debdiff
[00:19] <dhillon-v10> geser: ahh, that's why, just wait like 2 years and I might catch up to you
[00:19] <geser> and also looking at the current changes if nothing was missed
[00:19] <dhillon-v10> *might*
[05:00] <propagandist> Happy New Year
[05:55] <crimsun> ugh, nasty hacks.
[06:09] <cornucopic> Hey all. I have a pure Python module which I want to package for Ubuntu, Where do I start? I am a total n00b in packaging
[06:11] <bjsnider> cornucopic, there's a youtube video series by daniel holbach that you can find if you search for "ubuntu motu packaging"
[06:12] <bjsnider> that will tell you what you'll need as far as the build system and commands like dh_make that you'll be using
[06:12] <crimsun> see http://wiki.debian.org/Teams/PythonModulesTeam
[06:12] <cornucopic>  hm. cool. thanks!1
[06:14] <cornucopic> How good or bad is 'stdeb'? http://pypi.python.org/pypi/stdeb/
[06:17] <cornucopic> ah that page also hints at making packages w/o stdeb and i think that is the way I would go..let
[06:17] <cornucopic> let's see
[06:25] <ScottK> cornucopic: You can also ask questions about packaging Python stuff in #debian-python on OFTC.
[06:31] <cornucopic> ScottK, thanks. OFTC is a new IRC network?
[06:37] <ScottK> cornucopic: Not new, but different.  irc.oftc.org
[06:38] <ScottK> It's where all the Debian channels are.
[06:38] <cornucopic> ScottK, oh..didn't know..
[07:17] <cornucopic> what should be in my .changes file?
[07:17] <cornucopic> I am creating a new PPA
[07:20] <fabrice_sp> cornucopic, your changes file is automatically generated by debuild -sa -S
[07:24] <cornucopic> looks like py2dsc doesn't do it..
[07:24] <cornucopic> py2dsc is part of http://pypi.python.org/pypi/stdeb/
[07:30] <cornucopic> Is there anyway I could 'write' the .changes file myself?
[07:33] <fabrice_sp> debuild is part of the tools used to package an app
[07:33] <fabrice_sp> you shouldn't need to write it by yourself
[07:33] <fabrice_sp> !packagingguide
[07:34] <fabrice_sp> cornucopic, ^
[07:35] <ScottK> cornucopic: stdeb isn't a tool that's generally used here, so you're unlikely to get a lot of help with things specific to it.
[07:49] <crimsun> why is xca calling gcc instead of g++ ?!
[07:49] <crimsun> no wonder this linker junk is failing
[08:04] <cornucopic> ScottK, Ok. so no shortcuts in sight :( I need a point to start off, I want to distribute DEBs for a pure Python module
[08:08] <cornucopic> I am starting off with https://wiki.ubuntu.com/PackagingGuide/Python and adapt it my Python module.
[08:26] <marcham89> Hello
[08:41] <cornucopic> just built my first debian package! yay.
[08:41] <fabrice_sp> congrats :-)
[08:42] <cornucopic> fabrice_sp, thank you :-)
[08:43] <cornucopic> what's the diff between using pycentral and python-support?
[08:46] <cornucopic> the python module I am creating a package for uses PSF, dh_make apparently doesn't support it. Should I choose GPL instead? (since PSF is GPL compatible?)
[08:48] <fabrice_sp> tbh, ni idea
[09:00] <cornucopic> in the debian/copyright file, only the package maintainer's name should be mentioned right?
[09:02] <RAOF> cornucopic: No; that should list all the various copyright holders & the relevent licenses.
[09:02] <RAOF> cornucopic: I quite like DEP-5 http://tinyurl.com/ktmyfb - it makes for a nice structure to build a correct file.
[09:04] <cornucopic> RAOF, that looks great. thanks.
[09:31] <cornucopic> I am getting a "secret key not available" while doing dpkg-buildpackage
[09:32] <cornucopic> i have got my GPGKEY set properly..
[09:33] <fabrice_sp> cornucopic, be sure that the name in debian/changelog match the name is your key
[09:33] <fabrice_sp> s/is/in
[09:34] <cornucopic> name is same
[09:34] <etali> cornucopic: In particular, check your key for the comment part - I have my user name in the comment part, but didn't put it in the changelog and had that problem.
[09:34] <cornucopic> etali, ah yes. i have a different name there
[09:34] <cornucopic> so what should I do ?
[09:35] <cornucopic> the comment part is different than the changelog
[09:35] <etali> cornucopic: I had my key formated as "Lesley Harrison (Etali)" so just started using the whole thing in the changelog and it worked for me.
[09:35] <cornucopic> let me try that.
[09:38] <cornucopic> I get this: "can't connect to `/tmp/gpg-SJuSrC/S.gpg-agent': No such file or directory
[09:38] <cornucopic> gpg: can't connect to `/tmp/gpg-SJuSrC/S.gpg-agent': connect failed
[09:38] <cornucopic> ", though the package building seems to have passed fine
[09:40] <cornucopic> yeah, its uploading to my PPA. which means the signature verification passed!
[09:42] <etali> great :)
[09:42] <cornucopic> Thanks all :)
[09:42] <cornucopic> how long does it take for the package to "show up" in my PPA on Launchpad
[09:49] <cornucopic> this was my changelog:
[09:49] <cornucopic> pyevolve (0.6-0ubuntu1) koala; urgency=low
[09:49] <cornucopic>   * Initial release (Closes: #00)
[09:49] <cornucopic> which was rejected: "Unable to find distroseries: koala"
[09:49] <cornucopic> what should be there?
[09:50] <fabrice_sp> karmic
[09:50] <fabrice_sp> or lucid
[09:50] <cornucopic> how does this matter?
[09:50] <cornucopic> what does it mean, rather?
[09:51] <fabrice_sp> this is the exact name of the serie
[09:51] <fabrice_sp> karmic is actual one, and lucid, next development version
[09:51] <micahg> the adjective is the series, the animal is not
[09:51] <cornucopic> so is it, the series on which I have built this package on?
[09:52] <fabrice_sp> on which you will build the binaries, yes
[09:52] <cornucopic> fabrice_sp, thanks.
[09:52] <fabrice_sp> yw :-)
[09:57] <slytherin> cornucopic: it is the target release for your package.
[09:57] <cornucopic> slytherin, oh cool. thanks!
[10:01] <cornucopic> so i get: "Upload rejected because it contains binary packages."
[10:01] <cornucopic> I am following this:https://wiki.ubuntu.com/PackagingGuide/Python
[10:01] <slytherin> cornucopic: what was the command you used for upload?
[10:01] <cornucopic> dput ppa:amitksaha/pyevolve <source.changes>
[10:02] <slytherin> cornucopic: what is the name of the .changes file?
[10:02] <cornucopic> pyevolve_0.6-0ubuntu1_i386.changes
[10:03] <slytherin> cornucopic: you need to upload source package only. So there must be a corresponding source.changes file in same directory.
[10:03] <cornucopic> slytherin, right. let me try
[10:31] <cornucopic> slytherin, i don't see any source.changes file. What am I doing wrong?
[10:32] <fabrice_sp> Anyone willing to have a look at fceux (http://revu.ubuntuwire.com/p/fceux). It's a NES emulator
[10:32] <fabrice_sp> cornucopic, do you run debuild -sa -S ?
[10:33] <fabrice_sp> I'd like to have another review before uploading it
[10:33] <cornucopic> I am using dpkg-buildpackage
[10:34] <fabrice_sp> use debuild -sa -S better: it will also check your package with lintian
[10:40] <cornucopic> ah good..uploading to PPA
[10:40] <cornucopic> let's see
[11:08] <cornucopic> accepted.  Thanks a lot folks :)
[11:09] <slytherin> cornucopic: by default dpkg-buildpackage only builds binary package. You need -S -sa options to build source package.
[11:09] <cornucopic> slytherin, hmm..will note it for the future.
[13:40] <cornucopic> do I have to do anything for my package in PPA to build?
[13:55] <geser> wait
[13:55] <geser> there was a problem with the buildds that being fixed now and the buildds are now building all queued jobs
[14:07] <cornucopic> geser, ok!
[14:21] <ejat> is there any package for sun-java6 update 17 ?
[14:21] <surfzoid> directhex: Hi, have you got few minutes to give me your point of view ?
[14:24] <surfzoid> directhex: my i386 build ok but i have the same error on x86_64 machine and 2 other on 32 and 64 bit of debian : https://build.opensuse.org/package/show?package=Mono&project=home%3Asurfzoid%3ADebianUbuntu%3AMono
[14:26] <cornucopic> I uploaded a new package version to my PPA and I get "File pyevolve_0.6-0ubuntu1.diff.gz already exists in pyevolve, but uploaded version has different contents."
[14:26] <cornucopic> Should I bother?
[14:27] <surfzoid> delete it before upload ?
[14:27] <cornucopic> No..should I?
[14:28] <bjsnider> cornucopic, how are you naming the packages in the changelog?
[14:28] <cornucopic> bjsnider, didn't change that either..
[14:29] <geser> cornucopic: are you trying to upload the same version a second time?
[14:29] <cornucopic> geser, yes
[14:29] <bjsnider> can't do that
[14:29] <cornucopic> i had to fix a build dependency
[14:29] <cornucopic> so, I delete the earlier on?
[14:29] <cornucopic> *one?
[14:29] <geser> that won't work, every version can only be uploaded once (if you get an accepted email)
[14:29] <bjsnider> cornucopic, you should set up a pbuilder environment and take care of that stuff before you send it in to the ppa
[14:30] <cornucopic> bjsnider, hmm..this is my first time.. :(. So what can I do now?
[14:30] <directhex> surfzoid, dunno, looks weird. try it on a PPA, see if it's an opensuse build system issue?
[14:30] <geser> cornucopic: bump the version and upload then (e.g. to 0.6-0ubuntu2)
[14:30] <surfzoid> add an +1 in the rev, with an entry log like "fix dep.............
[14:30] <cornucopic> and I can delete the earlier one?
[14:30] <surfzoid> directhex: i tryed ppa but must admit it was dark for me
[14:30] <bjsnider> cornucopic, is this your package, that you created out of your software?
[14:31] <surfzoid> directhex: could you simply try my gz and dsc file on your ppa ?
[14:31] <cornucopic> bjsnider, not my software, but one I contribute to. And yeah, I am creating the package
[14:31] <cornucopic> bjsnider, I will be the maintainer..
[14:31] <bjsnider> cornucopic, and there isn't a debian package of this yet?
[14:31] <cornucopic> bjsnider, no
[14:31] <bjsnider> and there isn't an ubuntu package...
[14:31] <geser> cornucopic: you can delete your previous upload but this won't help you as LP remembers the version you last uploaded
[14:32] <cornucopic> bjsnider, no
[14:32] <cornucopic> geser, hmm.
[14:32] <bjsnider> so i would take the "ubuntux" string off the name and replace it with ~ppax
[14:32] <bjsnider> where x is a number
[14:33] <surfzoid> cornucopic: increase your number version with an entry log like "fix dep........ ?
[14:33] <cornucopic> my ppa is named as pyevolve. so I can use that I would guess.
[14:34] <bjsnider> i would name the package pyevolve-0.6-0~ppa1
[14:36] <bjsnider> cornucopic, but it would be better to use pbuilder to resolve dependency issues and build issues. there's an ubuntu wiki page that explains how to set it up and use it. after it builds in pbuilder send it in to the ppa
[14:37] <cornucopic> bjsnider, cool. I will take care of if this time on. Thanks a bunch
[14:41] <cornucopic> bjsnider, This should be the one I need to look at: https://wiki.ubuntu.com/PbuilderHowto ?
[14:42] <bjsnider> affirmative
[14:45] <bjsnider> also, make sure you've got the source code minus the debian directory as pyevolve_0.6-0.orig.tar.gz before you run debuild -S -sa
[14:45] <ari-tczew> hello
[14:46] <cornucopic> bjsnider, oh? It wasn't mentioned anywhere till now. what does it do/not do?
[14:47] <ari-tczew> is someone alive? :-D
[14:47] <ari-tczew> btw. happy new year 2o1o
[14:48] <bjsnider> cornucopic, it builds the dpkg source based on the orig tarball, so that when you upload the changes file to the ppa, that tarball goes with it. then, if you have to make minor revisions or improvements, you can run debuild -S -sd and it will upload only the changes you've made, not the whole source code.
[14:50] <cornucopic> hmm..looks like i did the correct thing unknowingly:)
[14:50] <cornucopic> thanks.
[14:51] <ari-tczew> needs to open task on hardy by someone from MOTU; bug 481631
[14:53] <DktrKranz> ari-tczew: only hardy?
[14:55] <cornucopic> ok, so I have done 'sudo pbuilder create --debootstrapopts --variant=buildd
[14:55] <cornucopic> '
[14:55] <cornucopic> and its completed
[14:55] <cornucopic> now, how I can a test the build of my package?
[14:56] <bjsnider> sudo pbuilder build <filename>.dsc
[14:58] <cornucopic> naice!
[14:58] <cornucopic> learnt so many things in a day!
[14:58] <cornucopic> not a bad start to the new year:)
[14:58] <bjsnider> but that knowledge has pushed out things you already knew...
[14:58] <bjsnider> such as how to eat and walk
[14:58] <cornucopic> i walked a bit, didn't eat much:)
[15:01] <ari-tczew> DktrKranz, yes only hardy
[15:02] <DktrKranz> ari-tczew: done
[15:03] <ari-tczew> thanks
[15:18] <cornucopic> Bye all for now thanks a ton to all of ya!
[16:12] <RainCT> Can somebody tell me what's the "incoming =" line in dput.cf for PPAs?
[16:16] <micahg> RainCT: it's what PPA you're uploading to
[16:16] <micahg> https://help.launchpad.net/Packaging/PPA/Uploading
[16:16] <porthose> RainCT, ~<your account>/ppa/ubuntu
[16:17] <RainCT> nah, was looking for "~%(ppa)s/ubuntu", but thanks :)
[16:17] <RainCT> but it seems like Debian doesn't support this.. :/
[17:40] <surfzoid> directhex: i m back home, so can yu please try my files in your ppa area ?
[17:40] <directhex> surfzoid, built fine on my amd64 sid ppa
[17:40] <directhex> um, pbuilder
[17:41] <surfzoid> so we can conclude, OBS have a very large problem ?
[17:42] <surfzoid> directhex: you have an idea, why debian don't find the linked file ?
[17:42] <directhex> surfzoid, well, it works for me in a debian test build, so...
[17:43] <surfzoid> localy ?
[17:43] <directhex> yeah
[17:44] <surfzoid> so i guess the conf file of OBS miss an essencial pkg wich contain this file
[17:50] <surfzoid> directhex: is there a possible switch after -S to add the missing buildrequiere pkg in the dsc file ?
[17:51] <directhex> surfzoid, there is nothing missing that i can see. it works in a fresh sid pbuilder.
[17:53] <surfzoid> directhex: ho yeah, i don't see that, the problem is not anymore the missing file but a libtool and permission problem
[17:54] <directhex> surfzoid, possibly OBS has an out-of-date sid repo, there were libtool problems recently
[19:04] <diwic> crimsun: is it on purpose that current Lucid pulseaudio does not release unused ALSA devices the way Karmic does?
[19:08] <crimsun> diwic: eh? Sure it does.
[19:09] <diwic> crimsun: I'm in Karmic now, but when I tested Lucid earlier today, I saw it (with fuser -v) having control over my HDMI output, AFAIK without using it.
[19:10] <crimsun> control as in /dev/snd/controlC* ?
[19:10] <diwic> as in /dev/snd/pcm*
[19:10] <crimsun> it will only hold on to it if some stream is active through it
[19:11] <crimsun> was g-v-c or pavucontrol doing something with the device?
[19:12] <crimsun> hmm
[19:12] <diwic> crimsun: I'll do some additional research and file a bug if necessary the next time I'm in Lucid. I just needed to know if it wasn't on purpose
[19:12] <crimsun> see changeset ef18beded8ddbaafdf4914bab209f77e60ae3a18 in sound-2.6, too
[19:12] <crimsun> 'ALSA: hda - HDMI sticky stream tag support'
[19:13] <diwic> with the talk of mic spying I was afraid it was a feature
[19:13] <crimsun> don't ascribe to maliciousness what is simple incompetence
[19:22] <diwic> crimsun: thanks for being around :-)
[20:00] <surfzoid> directhex: a guy of OBS team answer me "it's not OBS's libtool. It's the libtool that mono ships that gets used." i m loose !
[20:00] <directhex> well, relibtoolize.
[20:01] <surfzoid> how ?
[20:02] <surfzoid> directhex: i don't how thats work to relibtoolize
[20:04] <directhex> autoreconf -f -i -s ?
[20:06] <directhex> dunno. it's DEFINITELY building in a sid pbuilder.
[20:09] <surfzoid> directhex: that s an infinite loop, the guy say same thing, add autoreconf -f -i, i saw yu already do that and i added it again after the dh_clean section
[20:13] <directhex> surfzoid, well, there's nothing more for me to say. it builds in a debian pbuilder. there's something "bad" about the "doltlibtool" command being executed
[20:16] <surfzoid> directhex: jut for info about the wall am i now, the answer of the OBS guy : "it's not OBS's libtool. It's the libtool that mono ships that gets used."
[20:16] <surfzoid> :-)
[20:16] <directhex> surfzoid, so? how many bloody times do i need to say it builds on debian? :/
[20:16] <surfzoid> from #opensuse-buildservice
[20:17] <surfzoid> directhex: hey, i say "for info", thousand thanks for your help
[20:17] <surfzoid> i understand and i am agree with you
[20:17] <ScottK> surfzoid: OBS is more than a little off topic here in any case.
[20:17] <surfzoid> but that s a common situation where both....
[20:17] <surfzoid> yes
[20:19] <directhex> ScottK, however, unlike ppa's, it supports building for non-ubuntu distros. which is potentially useful
[20:19] <ScottK> directhex: True, but still OT.
[23:44] <crimsun> the progress of this build, thanks to colored CMake output, is really depressing
[23:53] <RAOF> Why are discs so SLOWWWWW‽  Or: why must pbuilder suck.
[23:53] <crimsun> I need a build farm.
[23:54] <jmarsden> RAOF: Creating your pbuilder in a ramdisk helps with the speed issue :)
[23:54] <RAOF> Yeah; I should be doing this on my laptop with just such a setup.
[23:54] <crimsun> see, using tmpfs for it would only help a negligible amount
[23:55] <crimsun> setup and teardown is dwarfed by the compilation. e.g., VTK has wrappers for everything
[23:55] <wgrant> RAOF: Why not use sbuild with LVM snapshots?
[23:57] <RAOF> wgrant: I probably should set that up on this lappy.  On the other one, it's a fight between building-on-ramdisk for pbuilder and faster setup/teardown for sbuild.