[01:55]  * MTecknology doubts anyone will answer his RFS in debian :(
[01:55] <nigelb> MTecknology: there a few DDs around here
[01:56] <nigelb> so if you ask in a more lively time here, you might get a sponsor ;)
[01:56] <MTecknology> nigelb: I'll try that - i usually quiet myself when things are busy because i figure my issue isn't a very big deal in comparison :P
[02:22] <MTecknology> If I want my package to build two pacakges; how do I do that?
[02:23] <micahg> MTecknology: .install files
[02:23] <nigelb> packagea.install and packageb.install
[02:23] <nigelb> and have packagea and packageb inside control file
[02:24] <MTecknology> how will the rules file change for that?
[02:24] <MTecknology> or is that decided by the .install files?
[02:25] <nigelb> somewhere in debian developers guide there should be more details
[02:25] <MTecknology> alrighty, I'll run off to search
[02:25] <MTecknology> thanks
[02:26] <MTecknology> oh...
[02:27] <MTecknology> lal.install -> lal usr/bin means the package lal will install the binary lal after it's built
[02:27] <MTecknology> that makes sense
[02:27] <MTecknology> if i got it right :P
=== kamalm-away is now known as kamalm
[03:12] <duanedesign> trying to update glunarclock i am getting this when I try and build the package with the new source from Debian using the /debian from the current Ubuntu version. http://paste.ubuntu.com/399088/
[03:14] <persia> why are you using new source from Debian with /debiian from Ubuntu?
[03:14] <persia> Surely a full merge would be more useful.
[03:15] <persia> That said, that error indicates a bug either in the upstream build system or in the flags passed in debian/rules.  You can debug or ignore, as long as you're not massively changing the dependencies from the in-archive version.
[03:18] <duanedesign> persia: i think i was doing that because a build dependency was fixed in UBuntu
[03:21] <persia> duanedesign: It's always better to try a proper merge.  Debian orig.tar.gz + Ubuntu diff.gz has little value.
[03:22] <duanedesign> persia: ok so i will get the Debian source and then fix the missing build dependency on libgnomeui-dev
[03:23] <persia> duanedesign: Right.  Get the debian source.  Review the current Ubuntu patch.  Apply anything from the Ubuntu patch that is still relevant.  If any of that is relevant in Debian, make sure that bugs have been filed in Debian.
[03:24] <duanedesign> persia: ahh, ok. thank you. that makes sense
[03:24] <persia> duanedesign: No problem.  Thanks for helping to integrate more bugfixes from Debian.
[03:25] <duanedesign> persia: ii am enjoying it. this is my second one from the Debian RC list.
=== kamalm is now known as kamalm-away
=== anzenketh_ is now known as anzenketh
=== nixternal_ is now known as Guest87737
[07:44] <jdetaeye> Have a question on the MOTU process to bring new packages to ubuntu.
[07:44] <jdetaeye> I filed a package review request last august.   Nothing happened with it since them.
[07:44] <jdetaeye> A new upstream release is now released, and I uploaded an updated package. As a result my package is again at the bottom of the review queue.
[07:44] <jdetaeye> This doesn't move forward...
[07:44] <jdetaeye> Is this normal? Is there anything I can/should do to make the review progress?
[07:46] <RAOF> jdetaeye: Sadly there's much more work available than MOTU to do it.  REVU tends to get a bit neglected because of that.
[07:46] <RAOF> The *best* way to make the review progress is to try to get the package into Debian; then you get it into Ubuntu for free.
[07:48] <jdetaeye> RAOF: Doesn't going through debian and then ubuntu add yet another step to the process?   It's not really "for free", is it?
[07:48] <happyaron> hhi, does CC BY-NC-SA meet DFSG?
[07:49] <christoph_debian> happyaron: seriously?
[07:50] <happyaron> christoph_debian: I am packaging a input method, and one of the table file is licensed under CC BY-NC-SA
[07:50] <christoph_debian> happyaron: free means free for all uses
[07:50] <jdetaeye> RAOF: I also submitted a similar review request with the fedora team, also around last august.   The review has long finished, and the new upstream release is already published on fedora as well.    I am surprised that it takes sooo much longer at Ubuntu
[07:50] <christoph_debian> happyaron: NC means not for comercial use
[07:51] <RAOF> jdetaeye: You don't have to go through Ubuntu if you go through Debian; it gets pulled in for free.
[07:51] <happyaron> christoph_debian: so I need to put them to non-free or remove it to make the package suitable to DFSG?
[07:51] <persia> happyaron: Either way works.
[07:52] <happyaron> persia: thanks
[07:52] <jdetaeye> RAOF:   I'll try the debian route then.    IMHO, you should close/review the revu process itself: it's simply not working...
[07:52] <christoph_debian> happyaron: or convince the author to relicense ;)
[07:53] <RAOF> jdetaeye: That's been considered.  Some of the problem is that MOTU is in a bit of flux at the moment, with the archive reorganisation.
[07:53] <abogani> Anyone could review my merge proposal https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 ? Thanks!
[07:53] <christoph_debian> jdetaeye: I guess a pre-release freeze isn't the best time to get stuff added
[07:53] <RAOF> jdetaeye: Also, we've always preferred people to go through Debian.
[07:54] <happyaron> christoph_debian: I didn't get the author's response, so looks I have to remove that file
[07:54] <jdetaeye> RAOF: To go the debian route, do I close my revu request and/or launchpad bug?    Or leave them open?
[07:54] <persia> jdetaeye: You may as well leave them open.
[07:55] <persia> jdetaeye: The LP bug should be closed when the package enters Ubuntu.  You can add another task for the Debian ITP.
[07:55] <jdetaeye> ok, thanks all for your input.    I know what to do now...
[07:55] <persia> jdetaeye: Depending on who you work with in Debian, you may be able to have them look at the package in REVU, but they may ask you to use mentors.debian.net
[07:55] <persia> Some packages do get through REVU, but there's just never enough reviewers.
[08:22] <happyaron> persia: hi, I see when removing a file I need to change the tarball to something-versiondsfg, how should I do that? simply recompress a new tarball?
[08:22] <Rhonda> happyaron: Yes.
[08:23] <happyaron> Rhonda: thanks
=== hannesw_ is now known as hannesw
[08:23] <Rhonda> … and it's not as if persia would be the only one to answer that so I don't see much sense in hilighting him particular for such questions. :)
[08:23] <happyaron> oh, I know now
[08:24] <persia> happyaron: Especially when you can figure out the answer before I notice the highlight :p
[08:24] <happyaron> :)
[08:24] <Rhonda> happyaron: Don't forget to document which files you left out debian/README.source
[08:25] <Rhonda> And people consider it nice to provide a get-orig-source target in debian/rules to produce the stripped tarball in such cases.
[08:26] <happyaron> Rhonda: oh, what to do in get-orig-source target? is there any example that I can look in?
[08:26] <persia> There's a few in the packaging guide (and stop highlighting people for general questions)
[08:27] <Rhonda> I don't have such a package myself so I'm uncertain what to suggest. I think christoph_debian might know some?
[08:27] <Rhonda> persia: Well, that was a direct response so in this case I consider it acceptable. :)
[08:28] <Rhonda> Oh, btw.: "On saturday, 20th of March, at five to midnight, we have released our most straining and time consuming project ever. Its codename is Simon André and we are pleased that it was (more or less) a smooth release process with just a minor delay of three days - but the best don't release on time but when it's ready."
[08:29] <\sh> N
[08:29] <\sh> Rhonda, who?
[08:30] <persia> Rhonda: Congratulations!
[08:31] <\sh> Rhonda, oh...congrats :) happy sleepless nights :)
[08:31] <Rhonda> \sh: We as in me and my SO ;)
[08:33] <\sh> Rhonda, yeah got it :) as said: happy sleepless nights :) I can sing a song about that :)
[08:34] <christoph_debian> happyaron: hm where is a good one?
[08:34] <christoph_debian> happyaron: mybe the irrlicht is nice one minute
[08:35] <christoph_debian> happyaron: http://git.debian.org/?p=pkg-games/irrlicht.git;a=blob;f=debian/rules;h=2a0fc94526d5c4c5419fab481773ad9e37870bf2;hb=HEAD
[08:35] <christoph_debian> could of course be improved
[08:36] <persia>  $dir(_) !!
[08:37] <persia> christoph_debian: Also, why all in a subshell?
[08:38] <christoph_debian> persia: to have all that running in ../foo
[08:38] <happyaron> christoph_debian: thanks, I will look it
[08:40] <persia> Hrm.  I thought there was a make construct for that, but it slips my mind now.  Anyway, running in .. seems odd given the "must run in any directory" requirement, although it's *incredibly* common, as everyone always wants it in ..
[08:40] <happyaron> well, I am trying to use the rules.tiny, how can I add such stuff to it?
[08:40] <persia> happyaron: Just add get-orig-source at the bottom.
[08:40] <happyaron> oh
[08:41] <christoph_debian> persia: if you know a better one I'm happy to improve ;)
[08:41] <persia> happyaron: If you7re feeling especially cool, add a dh_uscan and have dh(1) call it from dh get-orig-source *unless* there is an override.
[08:42] <persia> christoph_debian: As soon as I catch up on my backlog, I'd be happy to fix any number of get-orig-source rules, but I know it will take me a couple hours to fix that one now, and I ought be catching up.
[08:42] <happyaron> looks to be a good idea when I wanna to be cool, :)
[08:43] <christoph_debian> persia: ya a good example will do as well :)
[08:43] <christoph_debian> going to university now anyway see you all in the evening ;)
[08:43] <persia> directhex: Didn't you have a nice get-orig-source that repacked in some package?
[08:44] <RAOF> persia: Yes.  I stole it from one of *your* packages. :)
[08:44] <persia> Oh.
[08:44] <directhex> persia, what degree of repackingness? we use it in a few places
[08:44]  * persia clearly needs more memory
[08:45] <persia> directhex: Something like http://git.debian.org/?p=pkg-games/irrlicht.git;a=blob;f=debian/rules;h=2a0fc94526d5c4c5419fab481773ad9e37870bf2;hb=HEAD
[08:47] <directhex> persia, mysql-connector-net.
[08:47] <persia> christoph_debian: When you get back: there's your example
[08:48] <Laney> there's some magic to make the tarballs be md5sum consistent too
[08:49] <Laney> yes, there
[08:50]  * Laney runs
[08:51] <hyperair> Laney: ?
[08:51] <Laney> what?
[08:51] <hyperair> md5sum consistent?
[08:52] <hyperair> i've generally used --rsyncable to get md5sum consistent tarballs
[08:53] <Laney> does that work?
[08:53] <Laney> we pass an mtime to tar and then gzip -9fn
[08:57] <hyperair> it works.
[08:58] <Laney> i don't see that guarantee in the man page
[09:00] <hyperair> Laney: it has to be the same tarball.
[09:00] <Laney> well it's not
[09:01] <Laney> we're talking about get-orig-source rules here
[09:01] <hyperair> then it won't work
[09:01] <hyperair> back in the days of debsrc 1.0, get-orig-source has to convert tar.gz into tar.bz2
[09:01] <hyperair> er sorry
[09:01] <hyperair> .tar.bz2 to .gz
[09:01] <hyperair> my way was to bunzip2 and gzip --rsyncable
[09:02] <hyperair> as long as the input is the same, gzip --rsyncable should yield an identical stream
[09:02] <hyperair> the purpose of --rsyncable was not to change blocks unnecessarily
=== traveller__ is now known as traveller
[10:04] <skwashd> hi all
[10:04] <skwashd> i'm a bit of a n00b when it comes to the ffe process
[10:05] <skwashd> based on what i now know ...  https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/518029 doesn't look to me like it is ready to go for lucid
[10:05] <ubottu> Ubuntu bug 518029 in glusterfs "glusterfs 2.0.x max's out CPU" [Medium,Fix committed]
[10:05] <persia> skwashd: Basically, file a bug describing all the ways in which the upload would break FeatureFreeze, and all the benefits of the upload, and as much detail as possible, and subscribe the release team.
[10:06] <skwashd> persia: i did all that ... but didn't sub the release team
[10:06] <skwashd> and there is nothing in the project bzr repo showing a commit
[10:06] <persia> "Fix Committed" is almost certainly the wrong status if the bug isn't mostly fixed.
[10:06] <skwashd> there are packages in the guy's ppa
[10:06] <skwashd> which i tested and seem to work
[10:07] <skwashd> but i don't want to rely on a ppa for the next 2 years or so :)
[10:07] <persia> Right.
[10:08] <skwashd> persia: should i change the status and sub the release team?
[10:08] <persia> So, update the title, etc. to make it clear it's an FFe.
[10:08] <persia> Change the status to NEW or something (needs confirmation), and subscribe the release team.
[10:08] <persia> !ffe
[10:08] <ubottu> Feature Freeze Exception. See https://wiki.ubuntu.com/FreezeExceptionProcess for the freeze exception process.
[10:08] <persia> Read the wiki for current details.
[10:08] <persia> Based on upstream's comments, I suspect there's at least an even chance.
[10:09] <skwashd> persia: ttx held my hand through another ffe which made me realise this one didn't seem right
[10:10] <persia> Yeah.  This one isn't right yet.
[10:10] <persia> Needs a hand along the way.
[10:10] <skwashd> i'm working on it now
[10:11] <skwashd> glad i caught it now ... not in 4weeks ;)
[10:16] <skwashd> persia: does it now look better?
[10:18] <persia> The release team still won't see if, because the status is wrong.
[10:19] <persia> But you really want to chat with RoAkSoAx about it.
[10:19] <skwashd> ah clicked save for the status change ,,, thought it would do that when i posted my comment'
[10:19] <skwashd> what timezone is RoAkSoAx in?
[10:20] <Rhonda> persia: Is there anything more we can/should do for bug #539061?
[10:20] <ubottu> Launchpad bug 539061 in pgadmin3 "Please sync pgadmin3 1.10.2-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/539061
[10:21]  * persia makes minor noises about highlighting for general questions
[10:22] <persia> Rhonda: Oh, not general at all.
[10:22] <persia> No, there should be nothing else required.  It just needs an archive-admin to do something.
[10:22] <persia> We were in beta-freeze through friday, so I suspect there's a backlog, and it ought get hit in the next day or two.
[10:23] <persia> Yeah, 134 outstanding sync requests to process.
[10:23]  * persia hopes native-source-sync comes for lucid+1 to avoid this sort of thing
[10:25] <Rhonda> Thanks.
[10:26] <skwashd> persia: when is RoAkSoAx likely to be around?
[10:28] <persia> skwashd: LP claims UTC-4 is the right timezone.  I'm not sure of daily schedules :)
[10:28] <persia> But it's 6:30 there now, so maybe soon, maybe in ~12 hours.
[10:28] <persia> (assuming LP has the correct timezone)
[10:29] <skwashd> ok ... and i should be waiting here for him/her?
[10:29] <persia> Or try to catch some other time.  I wouldn't recommend doing nothing but watching joins/parts waiting for a specific nick :)
[10:30] <skwashd> i will look back in here from time to time
[10:30] <persia> But as RoAkSoAx has self-assigned the bug and has upload rights to the package, I presume that's the best contact to move forward.
[10:30] <Laney> or use an asynchronous communication edium
[10:30] <skwashd> thanks for the help
[10:30] <persia> Laney: What, like email?
[10:30] <Laney> that would be an example :)
[10:31] <Laney> I need to get a better 'm' key
[10:32] <skwashd> i find irc is usually more efficient at sorting stuff out
[10:32] <skwashd> but if he isn't around by the time i'm going to bed i'll email him
[10:33] <skwashd> now i have figured out who roaksoax is too :)
[10:35]  * Laney moans about changelog verbosity (lack thereof)
[10:37] <slytherin> Laney: You can not complain about both in same sentence. :-)
[10:38] <Laney> I *want* verbosity, and I'm not getting it!
[10:39] <Rhonda> slytherin: One can, if one is meant cynical. :)
[10:40] <Rhonda> One of my alltime favorites is "New Upstream version (closes: #1, #2, #3, #4, #5)
[10:41] <slytherin> he he
[10:41] <azeem_> that was the second upload of dpkg in 93?
[10:41] <Laney> Ha, Closes: is young compared to dpkg
[10:54] <Rhonda> azeem_: I was rather refering to the fact that none of those bugs were about "there's a new upstream version".
=== ogra_ is now known as ogra
[12:06] <duanedesign> what is the 'Ubuntu delta'?
[12:21] <skwashd> persia: now i feel like a real idiot ... https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/531545
[12:21] <ubottu> Ubuntu bug 531545 in glusterfs "[FFe] Please sync glusterfs 3.0.2 from debian testing" [Wishlist,Confirmed]
=== traveller_ is now known as traveller
=== kamalm-away is now known as kamalm
=== didrocks` is now known as didrocks
[14:35] <nigelb> nixternal: thank you for the offer to help with patch review :)  I'd greatly appreciate if you hung around there and helped the new contributors deal with some of the more difficult doubts.  Currently, only persia is very active there :)
[14:40] <MTecknology> nigelb: isn't persia active everywhere somebody might need help? :P
[14:41] <nigelb> MTecknology: oh yes.  I was just looking to give him a break :)
[14:42] <persia`> skwashd: Always wise to check all bugs in a package :)
[14:50] <abogani> Anyone could review my merge proposal at https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 , thanks!
=== aburch_ is now known as aburch
=== sladen_ is now known as sladen
=== shadeslayer is now known as shadeslayer_
=== debfx_ is now known as debfx
[15:47] <lfaraone> nhandler: does http://packages.debian.org/changelogs/pool/main/p/python-debian/current/changelog#versionversion0.1.15 read as something that requires a FFe? 0.1.15 of this library is required to fix a RC bug in debtorrent (and apply a bunch of other fixes in that upload)
[15:56] <james_w> lfaraone: if that is pulled in then there will be some work required on rdeps to use the new module name
[15:56] <james_w> simple stuff though
[15:57] <james_w> plus, we should have 0.1.16 if we want to update
=== Myrtti_ is now known as Myrtti
[16:20] <lfaraone> james_w: so it's not as simple as a sync request, I take it?
=== yofel_ is now known as yofel
=== fedoralogger is now known as apachelogger
[17:02] <nigelb> nixternal: can you pop by in #ubuntu-reviews when you get the time :)
[17:11]  * DktrKranz grumbles at http://launchpadlibrarian.net/41622655/ggcov_0.8.1-1_0.8.1-1ubuntu1.diff.gz
[17:51] <james_w> nhandler: I hear rumours that groundcontrol is currently broken by LP changes, do we still want to sync it?
[17:56] <abogani> Anyone could review my merge proposal at https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 , thanks!
=== directhe` is now known as directhex
[18:04] <james_w> Laney: apparently you cannot upload haskell-zip-archive, which seems odd to me
[18:04] <Laney> say what?
[18:04] <Laney> Did I do a sync request?
[18:04] <james_w> ah, because it's NEW, my mistake
[18:04] <Laney> heh
[18:05] <Laney> actually there was a new version of that uploaded just today
[18:05] <Laney> if you haven't already done it, we should wait for that
[18:05] <Laney> james_w: ^^^^^
[18:05] <Laney> (I dunno if your archive tools can see it yet)
[18:06] <james_w> I haven't asked it to sync yet
[18:06] <Laney> let's wait
[18:06] <Laney> I'll set it to incomplete
[18:07] <hyperair> does anyone here use a usb keyboard with a notebook?
[18:07] <Laney> yes
[18:07] <hyperair> Laney: using lucid?
[18:08] <Laney> yep
[18:08] <hyperair> Laney: okay, when you plug in your notebook, is your key-repeat different from your notebook's key-repeat?
[18:08] <hyperair> the key repeat rate
[18:08] <Laney> i haven't noticed that
[18:08] <Laney> remind me tomorrow and i'll look
[18:08] <hyperair> mine is set pretty high. then when i plug in the external keyboard, the key repeat rate gets really slow
[18:08] <hyperair> i have to disable and re-enable it in the keyboard preferences
[18:09] <hyperair> (in karmic)
[18:11] <Legendario> Is the debian merge valid for universe too?
[18:13] <Legendario> there is a software in universe I would like to be updated but packages.ubuntu.com says it will be kept the same version for lucid, although debian testing brings the last version
[18:34]  * abogani waves
[18:34] <abogani> I bother you for two reasons:
[18:34] <abogani> 1) Again I have a package that is built perfectly locally but not on PPA (seems that it didn't able to find included headers). What is the best way to "replicate" buildd build process? Simple dpkg-buildpackage and pbuilder don't seems be the right tools. Do you have some suggestions?
[18:34] <abogani> 2) Anyone could review my merge proposal at https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640?
[18:34] <abogani> Thanks!
[18:35] <geser> Legendario: what package did you look at?
[18:35] <geser> abogani: have you a build log from PPA at hand?
[18:36] <Legendario> geser asunder
[18:36] <abogani> geser: Sure: http://launchpadlibrarian.net/41621441/buildlog_ubuntu-lucid-i386.simavr_1.0a1-0ubuntu1~ppa1_FAILEDTOBUILD.txt.gz
[18:38] <geser> Legendario: if you get a FeatureFreeze exception, the new version could be synced to lucid.
[18:39] <Legendario> geser, and how to do that?
[18:39] <geser> !ffe
[18:39] <ubottu> Feature Freeze Exception. See https://wiki.ubuntu.com/FreezeExceptionProcess for the freeze exception process.
[18:39] <geser> Legendario: ^^
[18:39] <abogani> geser: I really appreciated your help (this isn't first time that you help me) but Do you know if there is a way to replicate "buildd"? In this way I can investigate for my own and stop to bother you every times.
[18:39] <abogani> sbuild perhaps?
[18:39] <abogani> or what?
[18:40] <Legendario> geser, but besides that, how do things usually work? Which are the repos merged automatically from debian? Is universe included?
[18:41] <geser> abogani: sbuild or pbuilder, both should work. If only one works or fails, you seem to have found a special bug
[18:42] <abogani> geser: I tried pbuilder but it always fail because it don't able to satisfy dependencies.
[18:44] <geser> Legendario: yes, till the DebianImportFreeze all unmodified packages get synced from Debian (for Lucid this was syncing with Debian testing and the deadline was Feb 11th). After that date and till FeatureFreeze, a sync has to be requested manually. And after FeatureFreeze some more checks and if necessary exceptions are needed too.
[18:44] <geser> abogani: have you universe enabled in your pbuilder?
[18:45] <abogani> geser: Ouch. No.
[18:45] <geser> that's a common error when someone setups a pbuilder for the first time
[18:46] <Legendario> geser, so i must think this version got to debian testing after the freeze date?
[18:46] <abogani> geser: I already know to be stupid! :-) Do you have some RTFM for me?
[18:47] <geser> Legendario: yes, it got to testing on 2010-03-02 (see http://packages.qa.debian.org/a/asunder.html)
[18:48] <geser> abogani: https://wiki.ubuntu.com/PbuilderHowto#Universe%20support is one way to enable universe support
[18:48] <abogani> geser: Do you have a name? So in this way I can write a memo for offer to you a glass of chianti... :-)
[18:49] <Legendario> geser, thanks a lot. I'll take a look at the ffe wiki
[18:50] <geser> abogani: look at my LP page :) https://edge.launchpad.net/~geser
[18:50] <hyperair> james_w: thanks for syncing banshee =)
[18:51] <hyperair> 1.5.6 is out, and on its way to debian, by the way =\
[18:51] <abogani> geser: Ohh!
[18:52] <Legendario> geser, to the ffe, do I have to make the package myself or should I just point the debian package?
[18:52] <abogani> geser: Could you do something for my merge proposal https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 ?
[19:07] <paissad> guys, if you download a package from git, knowing that i would like to append the revision number to the package, how can you retreive the revision from git ?
[19:08] <paissad> for svn, i use to do "svn log -q -r HEAD $url)
[19:08] <paissad> But with git, i'm a little bit confused !
[19:09] <geser> abogani: I'm currently busy with other things, but your branch is listed on http://qa.ubuntu.com/reports/sponsoring/index.html for needed sponsoring.
[19:12] <highvoltage> How do I make plymouth run in dry mode so that I can test a theme?
[20:38] <arand> I'm trying to "apt-get source poppler-utils=0.12.4-0ubuntu1.1~ppa1" (ppa:arand/poppler), this being an older version than currently in repos. But this gives: E: Ignore unavailable version... _?_
[20:41] <james_w> do you have a deb-src line for that PPA?
[20:41] <arand> Ah, *facepalm
[20:42] <anzenketh> I am trying to use dh_installinit to package over multiple init scripts but it is only doing one.
[20:42] <arand> Annoying that add-apt-repository doesn't auto-add it..
[21:09] <nhandler> james_w: I had not heard that. Do you have a link to a bug?
[21:10] <james_w> no, 'fraid not
[21:10] <james_w> bug 527978 I guess
[21:10] <ubottu> Launchpad bug 527978 in groundcontrol "Launchpad now using openid breaks login" [Critical,Confirmed] https://launchpad.net/bugs/527978
=== rulus_ is now known as rulus
[21:29] <MTecknology> How is this for making a watch file?   http://projects.l3ib.org/lal/files/ lal-(.*)\.tar\.gz debian debian/orig-tar.sh
[21:30] <Rhonda> MTecknology: Would that actually work? debian/orig-tar.sh won't have execute permissions I would guess?
[21:33] <MTecknology> Rhonda: I don't completely understand how the watch file works, what is that part for?
[21:35] <Rhonda> It's covered in man uscan, but first two are URL and pattern, optional third is version and fourth an action to call.
[21:36] <Rhonda> Never actually used different things than debian and uupdate in there so you might just want to experiment a bit.
[21:43] <MTecknology> Rhonda: thanks, just tried it out and that's pretty cool how it checks and downloads the latest
=== hggdh_ is now known as hggdh
[22:39] <MTecknology> My make file builds and installs but I want to separate it into two packages so  %:  dh $@  probably won't work - i'm guessing. If the makefile has install targets I was told I have no reason for package.install files. How am I supposed to handle this?
[22:40] <MTecknology> I know I could easily just build two binaries and install them in one package but I'd rather do something harder and that installs less on the users system if they don't want it
[22:43] <RAOF> MTecknology: The tiny dh rules file will work just fine for multi-binary packages; you need package.install files.
[22:44] <RAOF> MTecknology: There are two reasons to have package.install files - (1) Because upstream's build system doesn't provide an appropriate install target, or (2) because you only want to take particular pieces of what upstream's install target does.  Multi-binary packages fall into the latter.
[22:45] <RAOF> (There may be more reasons for .install files that I've not thought of in that list)
[22:45] <MTecknology> ok, thanks :D
[22:45] <MTecknology> makes perfect sense why he said that then too
[22:52] <MTecknology> RAOF: so adding .install and .manpages files means that anything used in those files will be used instead of what's in the make install section?
[22:55] <RAOF> MTecknology: No.  You want to check out “man dh_install”, as dh_install is what reads the .install files.  Basically, for multi-binary packages, “make install” gets redirected to a debian/tmp directory, which you then need to use .install files to copy the relevant bits to your packages.
[22:58] <MTecknology> oh
[23:01] <MTecknology> RAOF: I love how when I started packaging things it felt like there was about a 90 deg learning curve - now that I know a tiny little bit I feel like it's only ~80deg now :)
[23:01] <RAOF> It's quite intuitive after you've spent time familiarising yourself with it :)
[23:04] <MTecknology> My problem is that I'm adding features to somebody elses code, writing make files from scratch, doing the debian/ stuff, learning about LP packaging, trying to understand the processes, and all with no background before I started :P
=== nxvl_ is now known as nxvl