[00:01] <cody-somerville> ScottK, ah, appears to be a bug in the configure script or something
[00:02]  * cody-somerville has to run for the moment.
[00:08] <loic-m> when i run sudo make install it works (binaries are put in /usr/bin) but when I pbuild the package it fails during the make install step with "install: cannot create regular file `/usr/bin/ecm': Permission denied"
[00:22] <ScottK> loic-m: I'd guess you want usr/bin/ecm in your debian/rules, not /usr/bin/ecm.
[00:23] <loic-m> Well, atm I'm using $(MAKE) install in debian/rules and it doesn't work
[00:24] <loic-m> makefile has 	install -m 755 -t /usr/bin ecm unecm and it works when sudo make install
[00:24] <ScottK> loic-m: That's because for make install you want an absolute path.  For the package you want relative.
[00:25] <loic-m> so I can't use $(MAKE) install in debian/rules?
[00:32] <loic-m> when I use 	install -m 755 ecm usr/bin in debian/rules the package builds, but there's no binaries in it (there should be the ecm binary)
[00:35] <crimsun> loic-m: you need to place ecm in the correct relative destination
[00:36] <crimsun> loic-m: normally that's $(CURDIR)/debian/tmp/usr/bin or $(CURDIR)/debian/packagename/usr/bin
[00:37] <crimsun> remember, it's relative to the extraction path, which is the toplevel containing debian/
[00:37] <loic-m> the problem is, even the Complete packaging guide doesn't explain the install: part of the debian/rules file
[00:39] <loic-m> my makefile just creates the binaries in the directory it's started (where the source are). There's an install section, but since it doesn't work with pbuilder I don't use make install in debian/rules
[00:47] <loic-m> crimsun, I've got no binaries in the package if in debian/rules I use 	install -m 755 -t $(CURDIR)/debian/packagename/usr/bin ecm
[00:48] <crimsun> loic-m: hopefully you actually used the real packagename instead of "packagename"
[00:49] <loic-m> yes, I used ecm, sorry
[00:49] <loic-m> and I've got package = ecm in both makefile and debian/rules (just to be sure)
[00:52] <crimsun> can you pastebin your top-level Makefile and debian/* somewhere?
[00:52] <loic-m> Is there a forum for MOTU or packaging?
[00:52] <jmarsden> loic-m: I'm no expert, but you might consider patching the Makefile so that make install supports the use of $DESTDIR, at which point you avoid all this need for manually moving files around and getting confused?
[00:53] <crimsun> loic-m: (you're in the "forum")
[00:53] <loic-m> I can create a thread in ubuntu's forum and post the files there
[00:54] <loic-m> but I'd also really like an explanation on how the process work with pbuilder (the man page only details the options)
[00:54] <crimsun> loic-m: any pastebin will suffice, no need to create a new thread on the forums [unless you're dead set on it]
[00:54] <jmarsden> loic-m: As crimsum said, you are in the right place.  If someone working with you wants to see files they will ask you to pastbin them.
[00:57] <jmarsden> loic-m: pbuilder is just a chrooted development environment, there is no difference in how things work in there vs in your normal workstation, just that it doesn't have lots of packages already installed so building in a pbuilder makes sure you have your dependencies correct.
[01:02] <loic-m> http://pastebin.com/m510990f3 for the makefile, http://pastebin.com/m2fa45b16 for debian/rules
[01:12] <crimsun> eek
[01:12] <crimsun> loic-m: how thorough a review do you want?
[01:13]  * ScottK steps away from the pastebin.
[01:13] <crimsun> i.e., you define $CC but don't actually use it, preferring instead to use cc, and your install target has the wrong dependencies
[01:14] <loic-m> I'll have a look
[01:15] <crimsun> your install rules uses debian/tmp instead of debian/ecm; is that intentional?
[01:16] <crimsun> (that most recent was for debian/rules; the others are for the Makefile)
[01:16] <loic-m> No, i got it from another debian/rules (I used lha package) or from the Complete packaging guide
[01:18] <loic-m> Makefile: I edited it. Sorry for the dependencies, I should have seen that (even though it works)
[01:18] <crimsun> you might want install -p -m 755 debian/ecm/usr/bin ecm
[01:18] <crimsun> (debian/rules)
[01:19] <crimsun> i presume you have not created a debian/{,ecm.}install ?
[01:19] <crimsun> RAOF: sorry, was too tired to review last night
[01:24] <loic-m> with your install line, I get : install: cannot stat `debian/ecm/usr/bin': No such file or directory
[01:25] <crimsun> sorry, i reversed the arguments
[01:25] <crimsun> (been a long day)
[01:26] <loic-m> why do I need the -p option (--preserve-timestamps)?
[01:29] <crimsun> err, that should have been -D
[01:30] <crimsun> interesting, my pastes are completely out of order
[01:30] <crimsun> that explains why nothing makes sense =)
[01:31] <crimsun> i.e., install -D -m 755 ecm debian/ecm/usr/bin/ecm
[01:38] <RAOF> crimsun: That's fine!
[01:42] <loic-m> crimsun: Thanks a lot. It works perfect, and the package is ok
[01:43] <loic-m> Does -D work because it creates the directories before installing? I though /usr/bin would be already in the chroot
[01:45] <crimsun> loic-m: that's correct, it does create the dirs
[01:47] <loic-m> Do all submitted packages need a man page?
[01:48] <crimsun> it's a really, really good idea if the executables have man pages
[01:50] <nellery> is it permitted for packages in main to suggest packages outside of main?
[01:50] <crimsun> absolutely.
[01:51] <nellery> thanks crimsun
[04:25] <CarlFK> if Makefile has "all:       scons" is it proper to put scones in control: Build-Depends:?
[04:28] <RAOF> CarlFK: Does the package build without it?  If not, yes.
[04:30] <CarlFK> thanks
[04:36] <CarlFK> I built ffmpeg2theora_0.21-0.1build1.1_i386.deb but dpkg -i didn't seem to install the main binary anywhere.  how can I probe it to see what it will install where?
[04:36] <nhandler> CarlFK: dpkg --contents
[04:36] <RAOF> dpkg --contents
[04:37] <CarlFK> thanks.  I think that showed me the problem even
[06:35] <CarlFK> it seems "make install" isn't installing... does pbuilder or something have a way to tell me what make install is doing?
[06:36] <RAOF> The log will contain that.
[06:37] <RAOF> Presuming that make outputs to stdout or stderr, which it does.
[06:37] <CarlFK> where's the log?
[06:39] <RAOF> Either on your console, or somewhere else.  pbuilder-dist has a withlog option, which'll put it in ~/pbuilder/.lastlog
[06:39] <RAOF> (This is one of the things I like about sbuild; it emails me the buildlogs!)
[06:41] <StevenK> I have yet to get sbuild to mail me, but the build logs being handy is great
[06:50] <CarlFK>  I normally use dpkg-buildpackage, I have never used pbuilder.  I have followed the top of https://wiki.ubuntu.com/PbuilderHowto
[06:50] <CarlFK> did sudo pbuilder create.  not sure what to do next
[06:51] <CarlFK> sudo pbuilder build *.dsc?  (why sudo?)
[06:52] <RAOF> CarlFK: Check the backscroll in the terminal.  That's at least one copy of the log.
[06:52] <CarlFK> heh
[06:52] <RAOF> Also, sudo because pbuilder chroots, and you need to be root to do that.
[06:53] <CarlFK> ok, that makes sense
[06:59] <CarlFK> RAOF: I skimmed the last 24 hours and looked at all the lines with pbuilder... didn't find any clue what I should do
[07:00] <RAOF> CarlFK: You mean the last 24 hours of #ubuntu-motu?  I meant the terminal you ran pbuilder in!
[07:01]  * RAOF wishes he had a 24/7 internet box to keep backscroll in :(
[07:01] <StevenK> RAOF: That can be fixed
[07:02] <RAOF> StevenK: Yeah, by the purchase of a 24/7 internet box.  Or where you thinking of something else?
[07:02] <CarlFK> pbuilder-dist jaunty withlog build = "File /home/juser/pbuilder/jaunty-i386-base.tgz does not exist"
[07:03] <StevenK> RAOF: I was thinking of a VPS, actually
[07:03] <CarlFK> lol
[07:03] <RAOF> StevenK: So, a timeshare on an internet connected box.  I'm considering it.
[07:04] <StevenK> RAOF: How is that a time share?
[07:05] <RAOF> I share the CPU with the other virtualised systems on the box?  Or am I confusing VPS with something different?
[07:06] <RAOF> So, the slices are so tiny that it appears instantaneous, but it's still a time-share :)
[07:06] <StevenK> RAOF: Sure, but I don't notice
[07:06] <StevenK> I don't think I share the machine with a Gentoo user
[07:06] <RAOF> Hopefully you couldn't tell.
[07:08] <CarlFK> I need to do "pbuilder-dist jaunty create" ?
[07:09] <RAOF> CarlFK: Yes
[07:09] <dholbach> good morning
[07:10] <iulian> G'morning.
[07:23] <dholbach> who of you would like to give a hands-on session at the next Ubuntu Developer Week? :)
[07:23] <mgdm> you mean an IRC one?#
[07:23] <Hobbsee> when is it/
[07:24] <CarlFK> this look reasonable?  "ffmpeg2theora-trunk$ sudo pbuilder-dist jaunty withlog build ../ffmpeg2theora_0.21-0.1build1.dsc
[07:25] <RAOF> CarlFK: Yes.
[07:28] <dholbach> Hobbsee: Jan 19th-23rd
[07:29] <Hobbsee> dholbach: and what time of day?
[07:29] <dholbach> the same as last time: 16UTC-20UTC - so might be bad for you
[07:29] <CarlFK> well, now I get build errors that I didn't with dpkg-buildpackage
[07:31] <iulian> I'd be interested.
[07:31] <Hobbsee> oh, meh.
[07:31] <dholbach> iulian: woohoo
[07:31] <dholbach> iulian: what kind of session?
[07:31] <iulian> dholbach: Good question.
[07:31] <iulian> I don't know yet.
[07:31] <mgdm> I have had a talk of sorts in my mind on open source photography tools, which I could do, but I suspect there are others orund here better qualified
[07:32] <dholbach> the preliminary schedule is up here: https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep
[07:32]  * iulian looks
[07:32] <dholbach> whatever topic you pick, it'd be nice if it was a hands-on session
[07:32] <dholbach> so people could actually play with a few tools and find out more about how we do things
[07:32] <iulian> Yea, indeed.
[07:33] <dholbach> I'll ask mvo to give a session about python-apt and somebody else about i18n-ising code
[07:33] <dholbach> and pester the kernel folks, bzr, etc :)
[07:34] <iulian> And git.
[07:34] <dholbach> but a few packaging/bugfixing/testing sessions would be nice to have as well
[07:34] <dholbach> if you want to talk about it, sure why not - maybe you can do it together with the kernel folks? :)
[07:35] <iulian> What about a "packaging with git" session?
[07:35] <iulian> Sure.
[07:35]  * dholbach has no clue about git at all.
[07:37]  * dholbach hugs iulian
[07:37]  * iulian hugs dholbach back.
[07:37]  * iulian -> breakfast.
[07:37] <dholbach> enjoy
[07:37] <iulian> Thanks.
[07:39] <CarlFK> does  "sudo pbuilder-dist jaunty withlog build ../ffmpeg2theora_0.21-0.1build1.dsc" use the "Build-Depends" from the .dsc or debian/control?
[07:40] <RAOF> They _should_ be the same, right?  debian/control is where the B-D in the dsc is generated from.
[07:41] <CarlFK> yeah, one has more spaces, so the line wrapped more, so it looked like one had more
[07:41] <didrocks> morning o/
[07:50] <CarlFK> pbuilder-dist logs shows  "patches: debian/patches/01-fix_includes.patch"  but I deleted that patch.  where did it find it?
[07:54] <CarlFK> this happned: dpkg-source: info: unpacking ffmpeg2theora_0.21.orig.tar.gz
[07:55] <CarlFK> how do I tell pbuilder-dist to use the dir I am in?
[07:57] <CarlFK> ok, plan B: make install without sudo.  so I see it trying to install the binary: Install file: "ffmpeg2theora" as "/usr/local/bin/ffmpeg2theora";
[07:57] <CarlFK> scons: *** [/usr/local/bin/ffmpeg2theora] /usr/local/bin/ffmpeg2theora: Permission denied
[07:57] <CarlFK> so that is working.
[07:58] <CarlFK> why isn't dpkg-buildpackage doing that?
[08:05] <dholbach> CarlFK: is the patch mentioned in debian/patches/00list? did you rebuild the source package with     debuild -S   or similar?
[08:06] <CarlFK> dholbach: I didn't rebuild the source package - Im still trying to debug why the binary? package doesn't install right.  so I need to build the source package, then run pbuilder-dist?
[08:07] <dholbach> CarlFK: pbuilder* uses the source package, so if you make changes to the source package, you need to rebuild it after doing whatever changes using  debuild -S
[08:09] <CarlFK> well, only reason I was using pbuilder was to make sure 'make install' was trying to install to /usr/local/bin, which is is.
[08:09] <CarlFK> so now I am trying to figure out why that isn't happening when I do dpkg-buildpackage
[08:09] <dholbach> why to /usr/local/bin?
[08:11] <CarlFK> well, don't really care where - as long as it goes somewhere.  problem is it isn't going anywhere
[08:12] <RAOF> CarlFK: Pastebining the buildlog (with dpkg-buildpackage if you like - you don't have to use pbuilder if you don't want to) would be useful.  As, probably, would debian/rules
[08:12] <CarlFK> I am trying to upgrade ffmpeg2theora,
[08:12] <CarlFK> coming up
[08:14] <CarlFK> http://dpaste.com/101518/ debian/rules.
[08:18] <CarlFK> http://dpaste.com/101519/ dpkg-buildpackage -rfakeroot -uc -b
[08:21] <CarlFK> http://dpaste.com/101521/ dpkg -c ../ffmpeg2theora_0.21-0.1build1.1_i386.deb
[08:24] <dholbach> CarlFK: why is the autotools.mk in debian/rules commented? it doesn't seem to be in the intrepid version
[08:25] <CarlFK> dholbach: from http://v2v.cc/~j/ffmpeg2theora/index.html "remove autotools build system, only scons build is supported now."
[08:26] <RAOF> CarlFK: makefile.mk requires you to set the "make install" target.  Since you haven't, it doesn't get run, and so nothing gets installed.
[08:27] <CarlFK> ah, I guess that's something autotools.mk does?
[08:27] <RAOF> "DEB_MAKE_INSTALL_TARGET unset, skipping default makefile.mk common-install target
[08:27] <RAOF> "
[09:41] <CarlFK> If Makefile has just "install:         scons install"  (so no passing on prefix=foo) whats the make file syntax for $1?
[10:10] <paulproteus> Is there an Ubuntu way to "sync" a package from Debian experimental, rather than Debian unstable?
[10:10] <directhex> yeah
[10:10] <paulproteus> Awesome.
[10:10] <directhex> use requestsync's  "-d experimental" flag, iirc
[10:11] <directhex> no auto syncing from experimental though
[10:11] <paulproteus> Poifect.
[10:11] <directhex> i.e. gotta ask manually
[10:11] <paulproteus> That's no big deal, I can handle that.
[10:22] <RAOF> CarlFK: I'm insufficiently familiar with scons do answer that question.  You'll need to work out how the buildsystem works a bit before you can answer that, though.
[14:07] <bddebian> Heya gang
[14:14] <Laney> howdy
[14:17] <nhandler> dholbach: ping
[14:17] <dholbach> nhandler: pong
[14:18] <nhandler> dholbach: I have a very minor suggestion for the sponsoring page on your site. Could you add an anchor tag for the universe queue? That way, when I refresh the page, I don't need to scroll down.
[14:19] <dholbach> nhandler: added a note to do that - good point
[14:19] <nhandler> Thanks a lot dholbach
[14:21] <bddebian> I have no Ubuntu box or Jaunty pbuilder at the moment.  Is there any chance someone could test build LordsAWar 0.1.4 from Debian unstable for me?
[14:21] <nhandler> bddebian: Test build it in jaunty?
[14:22] <bddebian> Aye
[14:22] <nhandler> bddebian: Sure thing, give me a second.
[14:22] <bddebian> I want to sync it but I want to make sure it builds first :)
[14:22] <handschuh> If someone has free time, i would be glad to get a short review on http://revu.ubuntuwire.com/details.py?package=h2database .  thanks!
[14:23] <nhandler> bddebian: It is downloading now
[14:25] <bddebian> nhandler: Great, thanks!
[14:26] <Laney> hooray for pull-debian-source!
[14:26] <nhandler> Laney: That is what I'm using ;)
[14:26] <nhandler> I also used it a lot yesterday when looking over some merges
[14:26] <Laney> I knew something that did that would be useful
[14:26] <Laney> thanks for whipping it up
[14:27] <nhandler> You're welcome Laney
[14:27] <bddebian> What's wrong with dget? :)
[14:27] <nhandler> I personally think we need to mention some of the more useful tools in u-d-t on some of the MOTU wiki pages. That way, new contributors will know they exist
[14:27] <nhandler> bddebian: This script uses dget. However, it eliminates the need to hunt down the dsc url
[14:27] <bddebian> Ahh, nice
[14:29] <\sh> hey bddebian
[14:31] <bddebian> Heya \sh, how ya been?
[14:32] <\sh> bddebian: busy busy :) and I think you are busy with debian stuff, right? :) how's family? :)
[14:33] <bddebian> \sh: Yeah, trying to work for Ubuntu via Debian ;-)  Family is good thanks!
[14:33] <ScottK> bddebian: You wouldn't by chance be in the Debian Python Modules Team?
[14:34] <bddebian> ScottK: No sorry.  I thought about it at one point but I'm not too swift with Python (or anything else for that matter)
[14:34] <ScottK> OK.  I know one guy who's looking to get something sponsored there.
[14:34] <ScottK> Thanks.
[14:37] <loic-m> When creating man pages for a package that don't have any, does the Debian policy advise a special place to put them?
[14:37] <bddebian> Put them in the debian/ dir
[14:38] <loic-m> not debian/man?
[14:38] <bddebian> You can but I usually just stick them right in debian/
[14:40] <Laney> Can someone merge my LP branch of ubuntu-dev-tools into trunk (bzr merge lp:~laney/ubuntu-dev-tools/dev)? It just adds experimental to pbuilder-dist.new's list of Debian releases so that pbuilder-experimental can be used.
[14:40] <ScottK> Unless there are a lot of them, just debian is fine.
[14:43] <loic-m> thanks bddebian an ScottK
[14:44] <bddebian> NP
[14:54]  * ScottK notes 71 packages not yet merged this cycle and 3 days until the nominal deadline: http://merges.ubuntu.com/universe.html
[14:54] <nhandler> ScottK: Can we 0-day the merges?
[14:54] <ScottK> nhandler: After DIF.
[14:55]  * Laney requested a merge on LP of u-d-t
[14:55] <bddebian> ScottK: Know if any of them are QA or orphaned packages?
[14:55] <Laney> Those packages come up on UEHS, right?
[14:56] <nhandler> ScottK: I'll probably go through DaD after DIF and handle a lot of the untouched merges
[14:56] <ScottK> bddebian: No idea.  A fair number of them have an NMU as their last upload.
[14:56] <ScottK> nhandler: Great.
[14:56]  * Laney will too
[14:56] <bddebian> Where's the list these days? :)
[14:56] <nhandler> What list bddebian ?
[14:56] <ScottK> bddebian: ^^^ has the link.
[14:57] <pochu> nhandler, Laney: feel free to take my eclipse merge ;)
[14:57] <nhandler> pochu: If it is as ugly as it has been in the past, you can keep it ;)
[14:58] <bddebian> nhandler: MoM/DaD whatever folks are using this days :)
[14:58] <nhandler> bddebian: DaD: http://dad.dunnewind.net/universe.php
[14:58] <nhandler> That is for universe
[14:58] <nhandler> bddebian: MoM: http://merges.ubuntu.com/
[15:00] <bddebian> nhandler: Right, thanks
[15:00] <nhandler> You're welcome bddebian
[15:02] <Laney> pochu: Is the guy on bug 308302 doing the merge or just supplying the FTBFS fix?
[15:04] <nhandler> bddebian: The package built fine. Do you want a copy of the build log?
[15:05] <bddebian> Hmm, none of them jump out at me immediately
[15:05] <bddebian> nhandler: Is that needed for syncs now?
[15:06] <nhandler> bddebian: It isn't required. I just normally attach it to show that it built for me
[15:09] <pochu> Laney: the latter
[15:10] <nhandler> bddebian: Here is the build log if you want it: http://paste.ubuntu.com/90852/
[15:10] <bddebian> nhandler: Thanks!
[15:11] <loic-m> Shoudl I use debhelper (>= 7) in Build-depends or debhelper (>= 5) (or lower)? 7 is dh_make choice, but I remember a discussion where 7 is too much and not recommended
[15:11] <nhandler> np bddebian
[15:11] <Laney> Use 7 if you need 7
[15:12] <DRebellion> loic-m, look at the debhelper manpage
[15:12] <DRebellion> loic-m, start at 5, and work up from there if you need any mentioned features
[15:15] <loic-m> DRebellion: thanks
[15:16] <loic-m> before uploading a new package to REVU, should I replace my name/address with MOTU in Maintainer field (debian/control)?
[15:17] <nhandler> Yes loic-m
[15:17] <nhandler> You can set yourself as the XSBC-Original-Maintainer
[15:18] <loic-m> thanks nhandler
[15:24] <Laney> right, let's check out eclipse
[15:24] <ScottK> Laney: It needs more than 1GB RAM to build, FYI.
[15:24] <pochu> unless you have a PPA :P
[15:25] <Laney> ...
[15:25] <Laney> I'm stuck developing in a VM until I get back home after the holidays
[15:25] <Laney> maybe I'll give it a miss
[15:25] <pochu> I used to build wxwidgets and eclipse locally, until PPAs started to be fast
[15:26] <Laney> Might be worth checking with Debian if they plan to push 3.4 out soonish anyway
[15:27] <Laney> There's a WIP in SVN
[15:27] <ScottK-desktop> There's been a lot of clamoring for it.
[15:27] <DRebellion> If anybody's got some free time, I would much appreciate a second advocation for cifer ( http://revu.ubuntuwire.com/details.py?package=cifer ). Thanks in advance.
[15:36] <dholbach> nhandler: http://people.ubuntu.com/~dholbach/sponsoring/#universe
[15:37] <nhandler> Awesome dholbach. You rock!
[15:37] <dholbach> no worries :)
[15:37] <Laney> grargh
[15:42] <loic-m> when running debuild, lintian gives this error: bad-ubuntu-distribution-in-changes-file jaunty
[15:42] <loic-m> Is it normal?
[15:42] <ScottK> You can ignore that.
[15:43] <loic-m> Thanks
[15:43] <azeem> loic-m: is that on hardy or intrepid?
[15:44] <ScottK> azeem: It's either.
[15:44] <azeem> k
[15:44] <ScottK> The lintian that knows about Jaunty is just in Jaunty right now.  I've asked for a backport.
[15:44] <azeem> just wondering, cause by the time intrepid released, the jaunty name was already known
[15:44] <azeem> AFAIK
[15:45] <ScottK> It was, but no one bothered to patch lintian before the release.
[15:47] <loic-m> azeem: Intrepid
[15:48] <loic-m> To clean up my debian/ruls, can I just export DH_VERBOSE=1 then remove all the lines executed that don't produce anything?
[15:49] <loic-m> s/ruls/rules
[16:08] <loic-m> Before i upload the package, could someone review my makefile at http://pastebin.com/m6c04de62 and debian/rules at http://pastebin.com/mbbf948b ?
[16:11] <stdin> why not use $(DESTDIR) in your Makefile?
[16:12] <loic-m> Because I don't know the recommended method for $(DESTDIR)
[16:12] <stdin> eg: http://pastebin.com/d15f1de93 and http://pastebin.com/d312b1212
[16:13] <stdin> when it's not set it evaluates to nothing, so nothing changes. but when set it will use $(DESTDIR) as the root to install to
[16:13] <loic-m> Thanks a lot
[16:13] <loic-m> Now I understand better
[16:14] <loic-m> I'll change it
[16:14] <stdin> oh, but you'll probably want to do "install -d $(DESTDIR)/usr/bin" in the Makefile too
[16:14] <stdin> to create the dirs
[16:14] <loic-m> install -D or install -d?
[16:15] <stdin> i'd use -d
[16:16] <loic-m> I thought that it would also treat ecm and unecm as directory names
[16:16] <stdin> you could use -D to copy it, but it's clearer with -d
[16:16] <stdin> not with "install -d $(DESTDIR)/usr/bin"
[16:16] <stdin> that just creates the dir if it's not there
[16:17] <loic-m> "treat all arguments as directory names;" and ecm unecm are after the option (or should I put them before -d $(DESTDIR)/usr/bin" ?
[16:18] <stdin> put "install -d $(DESTDIR)/usr/bin" before the other install commands
[16:18] <loic-m> like in http://pastebin.com/m175b5842 ?
[16:19] <stdin> like http://pastebin.com/d699522fd
[16:20] <loic-m> Thanks
[16:21] <stdin> if you use DESTDIR then it's easier to expand the project later, without having to go over old install code
[16:21] <DRebellion> loic-m, you should use multiple targets for ecm and unecm
[16:21] <nhandler> Does anyone know of any debian packages that use an epoch in their version number?
[16:21] <stdin> nhandler: just about all the KDE packages
[16:23] <nhandler> stdin: Thanks
[16:23] <AnAnt> Hello, can someone review http://revu.ubuntuwire.com/details.py?package=thwab for me ? it's my first  package for python software, so more importantly I need comments that are python specific
[16:23] <DRebellion> loic-m, http://pastebin.com/f75073197
[16:23] <loic-m> DRebellion like http://pastebin.com/m68b4233e or should I also use multiple targets for install?
[16:23] <DRebellion> loic-m, see the link above
[16:23] <DRebellion> loic-m, the .PHONY says that install and clean don't create files named install and clean
[16:24] <DRebellion> loic-m, $< is the name of the first prerequisite, $@ is the name of the target
[16:24] <loic-m> Thanks
[16:24] <loic-m> Thanks a lot
[16:24] <DRebellion> loic-m, the all target is a gnu convention
[16:24] <DRebellion> loic-m, no problem ; )
[16:25] <DRebellion> loic-m, you probably want to put a GPL license at the top or something as well
[16:25] <loic-m> Ok. I'll try to modify rules myself to see if i've understood ;)
[16:26] <DRebellion> loic-m, you also probably want to use rm -f instead of just rm, so you don't get errors if they don't exist.
[16:26] <DRebellion> (in the clean target)
[16:27] <leonel> hello :  what's the last date to  merge a universe package  from  debian to jaunty ??  acording to https://wiki.ubuntu.com/JauntyReleaseSchedule   is it   march 19 ??
[16:28] <loic-m> DRebellion: Thanks. For the Top, like Licensed under the GPL ?
[16:29] <DRebellion> loic-m, read the end section of /usr/share/common-licenses/GPL-3 for info on licensing your code.
[16:29] <pochu> leonel: Feature Freeze, but there can be exceptions
[16:29] <DRebellion> "How to Apply These Terms to Your New Programs"
[16:29] <leonel> pochu: thanks
[16:30] <leonel> so Feb 19  last date  thanks   pochu
[16:31] <persia> leonel, Rather, target is to have everything merged by 25th December.  Any merges after that need a reason, and need to respect any active freezes.  There's a few of us who do a run of merges on the last couple days before release for very important bugfixes.
[16:32] <leonel> persia: ok thanks
[16:33] <Laney> persia: I thought it was any merges after FF that need a reason, not DIF?
[16:33] <pochu> me too
[16:33] <persia> Laney, No, merges after DIF need a reason, but that reason can be "because I really wanted to"
[16:33] <persia> And FF is irrelevant to merges, entirely.
[16:34] <persia> If a given merge would include a feature that breaks FF, it needs an exception.  If it doesn't, it doesn't.
[16:34] <nhandler> I thought the big thing about DIF was that automatic syncs stopped.
[16:34] <persia> nhandler, Yep.
[16:35] <persia> Ideally, at that point (Thursday), we'll be switching mode from pulling all the fancy new stuff we can find, and looking to get everything integrated and working well.
[16:37] <nhandler> Is there any reason that we do not talk about many of the tools in ubuntu-developer-tools in the wiki guides?
[16:38] <loic-m> DRebellion: Ive modified it http://pastebin.com/m6c04de62
[16:39] <Laney> nhandler: The reason is probably that nobody did it yet
[16:39] <leonel> persia:  I'd like  to have  The latest cherokee   ( www.cherokee-project.org ) in jaunty and debian has  the latest version 0.11.5 and   packages.ubuntu.com shows 0.11.3  I'm keeping the latest in PPA    but there's no 0.11.5 on  merges.ubuntu.com ..
[16:39] <DRebellion> loic-m, erm... you sure you got the right link there?
[16:40] <nhandler> Laney: Ok. I think I might go through a few of the guides and try to add in information about some of the tools. If people don't know they exist, they won't use them
[16:40] <loic-m> DRebellion: sorry, I forgot to press the send button...
[16:40] <DRebellion> loic-m, hehe
[16:41] <DRebellion> nhandler, what package are the "ubuntu-developer-tools" in?
[16:41] <persia> leonel, Have you checked the rmadison output?
[16:41] <Laney> leonel: 0.11.5 was only uploaded today - p.u.c needs time to catch up
[16:41] <jpds> DRebellion: ubuntu-dev-tools.
[16:41] <Laney> check rmadison or LP and you'll see that it's there already
[16:41] <DRebellion> jpds, thanks
[16:42] <leonel> Laney: great !!!
[16:42] <DRebellion> hmm... i've got it installed, but i don't think i've ever used any of those udts...
[16:43] <leonel> persia: rmadison says  0.11.3   ...
[16:43] <nhandler> DRebellion: Many of the tools are very useful. That is why I think we should talk about them on the wiki
[16:43] <Laney> pbuilder-dist(.new) and pull-*-source are the ones I use most
[16:43] <CarlFK> is there a var that has the /usr in it so I don't need usr in debian/rules DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(DEB_DESTDIR)/usr
[16:43] <Laney> Oh, and submittodebian
[16:43] <Laney> Oh, and update-maintainer
[16:43] <DRebellion> nhandler, I look forward to reading about them then ; )
[16:43]  * Laney thought some of these were in devscripts :(
[16:43] <jpds> Oh, and everythign else?
[16:44] <Laney> I think that's it!
[16:44] <jpds> buildd is cool.
[16:44] <persia> leonel, Give it a couple days.  If it's not pulled by the time the autosync shuts down (probably Thursday or maybe Friday given the date), you can request a sync.
[16:44] <Laney> ...nope, what-patch I use a lot too
[16:44] <nhandler> DRebellion: I need to finish reading about some of the scripts, then I will add them to the wiki
[16:44]  * Laney runs
[16:44] <DRebellion> jpds, that IS cool :D
[16:44] <leonel> persia:  Great  Thank you !
[16:45] <ScottK> Sync just got run today for the first time in a while, so stuff may be catching up now.
[16:45] <persia> leonel, DIF only means "Don't do it without thinking".  If you *want* the newer cherokee, and you have a reason to want it, that's enough of a reason to do it post DIF.
[16:45] <Laney> nhandler: Can you merge my u-d-t branch pretty please?
[16:46] <DRebellion> Is there anyway to get `buildd' to fetch ppa info?
[16:46] <leonel> persia: Ok
[16:46]  * ScottK read submittodebian as submittobddebian for a moment.
[16:46] <cprov> DRebellion: what kind of info ?
[16:46] <nhandler> Laney: I'll take a look at it
[16:47] <nhandler> Link?
[16:47] <DRebellion> cprov, as in, the same info it gets from the main builders...
[16:47] <DRebellion> like
[16:47] <Laney> Erm, I put it into lp
[16:47] <DRebellion> The source version for 'posterazor' in Intrepid (universe) is at 1.5.1-0ubuntu1.
[16:47] <DRebellion> Current build status for this package is as follows:
[16:47] <DRebellion> sparc: Successfully built.
[16:47] <DRebellion> and so on
[16:47] <jpds> DRebellion: I looked into it once, but couldn't find a global build page for all the builders.
[16:47] <Laney> bzr merge lp:~laney/ubuntu-dev-tools/dev
[16:47] <Laney> The change is really very minor
[16:47] <DRebellion> jpds, https://launchpad.net/+builds ?
[16:48] <jpds> DRebellion: No, like https://edge.launchpad.net/ubuntu/+source/pidgin-facebookchat/1.44-1 for example.
[16:49] <cprov> DRebellion: sorry, but your request doesn't make much sense. You mean "showing that information in the PPA UI as you show for ubuntu packages" ?
[16:49] <nhandler> Laney: You might want to set your information using 'bzr whomai'
[16:50] <Laney> nhandler: I did that now
[16:50] <Laney> Too late for the past though
[16:50] <DRebellion> cprov, I mean that currently you can pull build info for packages that are in the ubuntu repos, but not for packages that are only in ppas.
[16:50] <Laney> (I'm not working on my PC as I've gone to the parents for christmas, so nothing is set up)
[16:50] <cprov> DRebellion: what about the information in the PPA page itself ?
[16:51] <ScottK> cprov: Did you get a chance to look into where the hppa builds of kde4bindings went any more (I can dig up the bug number if you need it)?
[16:51] <persia> DRebellion, You seek to enable https://launchpad.net/+me/+source/pidgin-facebookchat to pull off a PPA?
[16:51] <cprov> ScottK: no, not yet, sorry
[16:52] <cprov> ScottK, it's in my list for this week.
[16:52] <DRebellion> persia, erm.. no
[16:52] <ScottK> cprov: Great.  We've about got armel nailed and hppa should work now.  Unfortunately without that package the entire KDE stack is broken.
[16:53] <ScottK> cprov: If you find a way to resurrect the current build when you look at it, it should work.
[16:53] <DRebellion> I was basically asking if there was a script like buildd that would get build statuses for packages in ppas, not just those in the ubuntu repos.
[16:54] <persia> https://launchpad.net/+me/+builds?
[16:54] <cprov> ScottK: okay, if you are in a hurry, resurrecting the build is easy I can do that right now, but I'd like to find out why it's not being created by normal means
[16:54] <loic-m> About debian/rules there"s something I don't understand in https://wiki.ubuntu.com/PackagingGuide/Complete#rules
[16:54] <persia> loic-m, What?
[16:54] <loic-m> it says "The next rule is clean, which runs make -i distclean and removes the files that are made during the package building. "
[16:54] <jpds> DRebellion: Well, buildd grabs the info off pages like the example I gave. So you'll need something like it for PPAs.
[16:55] <cprov> DRebellion: oh, the 'buildd' screen-scraping script.
[16:55] <nhandler> Laney: Pushed to trunk
[16:55] <loic-m> but when I run pbuilder clean is done before make
[16:55] <DRebellion> cprov, yep
[16:55] <azeem> loic-m: next rule in the file, not next rule in terms of running order I guess
[16:55] <persia> loic-m, debian/rules clean is run several times during the process, just to make sure it's really clean.  It cleans up before, just in case you ran a test build or something.
[16:55] <loic-m> ok thanks
[16:56] <cprov> DRebellion: there is nothing for PPAs yet, but soon there will be extensions for launchpadlib for that.
[16:56] <loic-m> That's why I should use rm -f instead of rm?
[16:56] <DRebellion> cprov, cool
[16:56] <cprov> DRebellion: you can already check the source publishing history, stay tuned.
[16:57] <Laney> nhandler: cheers
[16:57] <nhandler> Laney: Any time. Could you also try out my pull-debian-source script? I pushed a new version to make it work for versions with an epoch in them, but I would like to get some more testing done
[17:00] <oliver_g_> hello
[17:00] <Laney> nhandler: I'll make sure to use whenever I need to grab something, and will report/fix any bugs that I find
[17:00] <loic-m> DRebellion: I'm using 	$(MAKE) all in rules as in http://pastebin.com/m1e71ab7 to go with the makefile you suggested ( http://pastebin.com/m1c41a761 ) is it ok or should I make ecm and unecm separately?
[17:01] <oliver_g_> I have a question about managing source trees when working with packages...
[17:01] <DRebellion> loic-m, yes, $(MAKE) all is the way to go
[17:01] <loic-m> Thanks. If it's ok, I'll upload the package to revu
[17:02] <DRebellion> loic-m, in the Makefile, you should probably make the install target have the prerequisite as all instead of ecm and unecm
[17:02] <oliver_g_> btw. is there maybe a description of the whole workflow when adding patches to a package? Like, how to juggle work between bzr checkouts and source packages and patch systems...
[17:03] <nhandler> Thanks a lot Laney
[17:03] <DRebellion> loic-m, you should also support $(CFLAGS)
[17:03] <DRebellion> loic-m, like this http://pastebin.com/m1a33262e
[17:04] <DRebellion> loic-m, so, if you wanted, you could build like: `make CFLAGS=-Wall all' or something
[17:04] <loic-m> DRebellion http://pastebin.com/m29152b12 for the all (I also used it for clean
[17:05] <DRebellion> loic-m, you can't do `rm -f all', because all isn't a variable, just the name of a target
[17:05] <ScottK> cprov: I don't think we're going to have another kde4bindings upload soon, so if you could resurrect it, that'd be great (at least we'll know if it works and it'll clear several NBS).
[17:06] <loic-m> DRebellion ok, so same for install -m 755 -t $(DESTDIR)/usr/bin all. Should i leave the $(CFLAGS) = like that?
[17:06] <DRebellion> loic-m, yes and yes
[17:06] <DRebellion> loic-m, you might wish to make CFLAGS = -Wall -pedantic to spot any possible build problems, but that's up to you
[17:07] <cprov> ScottK: okay, let me run the magic
[17:07] <DRebellion> loic-m, perhaps you should declare something like   allfiles = ecm unecm
[17:07] <DRebellion> and then do install....... $(allfiles) and rm -f $(allfiles)
[17:08] <ScottK> cprov: Thanks.
[17:08] <akb41> Hi all... I have a slightly complex situation with a new package I'd like included in the next ubuntu rev version. That freezes on thursday, yes?
[17:09] <loic-m> DRebellion: I'll try
[17:10] <DRebellion> loic-m, the idea is to give a central place where you can easily make changes to these things without having to comb through the whole file.
[17:11] <loic-m> DRebellion: So : is for setting prerequisite and = for variables?
[17:11] <DRebellion> loic-m, yes
[17:13] <DRebellion> loic-m, you might also want an uninstall target, for the sake of completeness
[17:15] <loic-m> The uninstall target only removes the ecm and unecm binaries in $(DESTDIR)/usr/bin if I understand
[17:17] <loic-m> DRebellion: is there a way to specify the variable allfiles to rm -f $(DESTDIR)/usr/bin/ or shoud I just cd $(DESTDIR)/usr/bin/ then rm -f allfiles?
[17:18] <DRebellion> loic-m, i would use a for loop
[17:18] <ScottK> leonel: Dunno if you noticed, but cherokee got updated on the last sync run.  It's building now..
[17:19] <DRebellion> loic-m, for f in $(allfiles); do rm -f $$f; done
[17:20] <DRebellion> loic-m, oops
[17:20] <DRebellion> loic-m, for f in $(allfiles); do rm -f $(DESTDIR)/usr/bin/$$f; done
[17:23] <loic-m> DRebellion: Thanks. I tried the makefile and it works!
[17:25] <DRebellion> loic-m, great : )
[17:25] <loic-m> http://pastebin.com/m20b54941
[17:25] <DRebellion> loic-m, why does the uninstall target depend on all?
[17:26] <DRebellion> loic-m, also (very minor) you should move `allfiles = ecm unecm' to above `all : ecm unecm' so that all your variables are declared before you start your targets.
[17:29] <loic-m> DRebellion: ok, thanks. I though since uninstall was working on all (rm the files) I had to put them as prerequisites
[17:29] <DRebellion> loic-m, no, because uninstall doesn't require the presence of the files `ecm' and `unecm' in the current directory, its just removing them (if they exist) from their installed directories.
[17:30] <akb41> (Plunging bravely ahead). The problem is this: I have a program I'd like in Ubuntu. It is in debian Sid, but the debian maintainer made a mistake and categorized it as "non-free", even though it is in fact free (at least by debian guidelines). He tried to redo the upload, but due to a bug in dak, that bounced; the fix could be a little gross, a debian sub-version number may or may not work. Meanwhile, ya'll are heading for free
[17:30] <loic-m> DRebellion: Done, http://pastebin.com/m7dfb3dac
[17:32] <DRebellion> loic-m, looks god, great job ; )
[17:32] <DRebellion> s/god/good
[17:32] <loic-m> DRebellion: most of it isn't my job ;)
[17:33] <DRebellion> loic-m, but you still learnt a lot about Makefiles, no?
[17:33] <DRebellion> loic-m, ooh
[17:33] <loic-m> DRebellion: yes, that's what I was going to write. I really learnt a lot, and about rules too
[17:33] <DRebellion> loic-m, one more thing: (almost forgot) you need to add a shebang at the top.
[17:34] <leonel> scottK yes I see that on  packages.ubuntu.com    where can I see that  scottK ?
[17:34] <loic-m> DRebellion: Thanks, I'll do that
[17:34] <DRebellion> loic-m, like htis http://pastebin.com/m49e0d34c
[17:35] <Laney> Does anyone have a copy of bryce's merge_changelog script?
[17:35] <loic-m> DRebellion: thanks, I was going to put #! /bin/sh ;)
[17:37] <loic-m> DRebellion: in debian/rules, do I need to define MAKE (used in $(MAKE) f.e.)?
[17:40] <DRebellion> loic-m, no, MAKE is defined for you
[17:42] <loic-m> DRebellion: thanks, I'll upload the package to revu
[17:54] <loic-m> lintian complains out-of-date-standards-version 3.7.3 (current is 3.8.0), I thought it was better to leave the standards as they were, should I change it to 3.8.0?
[17:55] <ScottK> leonel: https://launchpad.net/ubuntu/jaunty/+source/cherokee/0.11.5-1
[17:55] <jpds> loic-m: In a merge, or new package?
[17:55] <ScottK> loic-m: If it's a package from Debian, leave it be.  If it's not in Debian, then update it.
[17:55] <loic-m> jpds: a new package
[17:55] <jpds> loic-m: Update.
[17:56] <loic-m> ScottK: ok, my mistake then. I'll update it
[17:56] <jpds> loic-m: If it's from Debian, we leave it be to reduce the delta.
[18:01] <loic-m> http://revu.ubuntuwire.com/report.py/legal?upid=4326 revu complains the code contains incorrect FSF address - should I modify the address in the source file?
[18:02] <loic-m> s/source file/source, not the orig archive ;)
[18:03] <slytherin> loic-m: don't bother. but if you do, modify with a patch system.
[18:05] <iulian> loic-m: Better talk to upstream.
[18:12] <loic-m> patch system is next on my list of things to learn, so for the moment I'll leave it as is ;)
[18:16] <loic-m> ok, package is at http://revu.ubuntuwire.com/details.py?package=ecm
[19:02] <didrocks> just a silly question, why do we have to use both "conflicts/replaces" when a package can't be installed with another one, and don't use only "replaces" field?
[19:04] <didrocks> I just assume it is if A replaces B, installing A will remove B, but then, if we try to install B, it will do it, is it right?
[19:04] <didrocks> (that is to say, that the conflicts marker remains in cache, and it will not be possible to install B afterwards as long as A is installed)
[19:07] <Laney> didrocks: I believe that replaces won't cause the old package to be removed unless you replace all its files
[19:09] <didrocks> Laney: oki, that makes sense. I didn't find the debian policy very clear about it :)
[19:09] <didrocks> tanks!
[19:09] <didrocks> thanks*
[19:10] <Laney> replaces means "it's ok that this package installs the same files as the other one"
[19:10] <Laney> and conflicts means "this package cannot be installed at the same time as the other"
[19:11] <Laney> but conflicts on its own won't cause the other one to be removed, merely cause dpkg to error out - so you need conflicts and replaces!
[19:11] <Laney> This is my understanding of it anyway
[19:17] <slytherin> Laney: didrocks: I believe conflicts alone is sufficient.
[19:18] <Laney> slytherin: "If one package is to be installed, the other must be removed first - if the package being installed is marked as replacing (see Overwriting files and replacing packages - Replaces, Section 7.6) the one on the system, or the one on the system is marked as deselected, or both packages are marked Essential, then dpkg will automatically remove the package which is causing the conflict, otherwise it will halt the installation of the new ...
[19:18] <Laney> ... package with an error."
[19:18] <didrocks> smagoun: really?
[19:18] <didrocks> slytherin: (sorry smagoun )
[19:19] <Laney> so replaces is needed too
[19:19] <didrocks> ok Laney, I thing you're right :)
[19:19] <didrocks> think
[19:19] <slytherin> didrocks: Which package are you dealing with in this case?
[19:20] <didrocks> slytherin: it was more a general question… I have just use conflicts/replaces without asking myself previously :)
[19:21] <slytherin> didrocks: I believe that both are not always necessary. If I remember correctly totem-xine used to have conflict with totem-gstreamer. But there was no replaces.
[19:22] <Laney> Right. You use a conflict/replace if one package supersedes another, and a conflict alone if they just can't be installed together for some other reason.
[19:23] <Laney> And replaces alone if a package takes over ownership of a file
[19:25] <didrocks> ok, I will look at some packages to have this very clear in my mming
[19:25] <didrocks> mind*
[19:26] <didrocks> thanks a lot Laney & slytherin :)
[19:26] <Laney> np
[19:27] <slytherin> didrocks: you are welcome
[19:44] <ramses-sv> j #ubuntu-meeting
[19:45] <CarlFK> what does it take to get a package ( http://packages.ubuntu.com/jaunty/i386/ffmpeg2theora) listed on  http://qa.ubuntuwire.com/uehs ?
[19:48] <Laney> A working watchfile, to not be in Debian (or be orphaned)
[20:15] <DRebellion> How can I get debuild to build a source package without signing it?
[20:15] <loic-m> debuild -S -uc -us
[20:16] <DRebellion> loic-m, thanks
[20:16] <loic-m> loic-m: for once I can help ;)
[20:16] <DRebellion> hehe
[20:17] <loic-m> s/loic-m: /DRebellion :/ need to go to sleep
[20:18] <DRebellion> loic-m, just buildtesting ecm ;)
[20:21] <nhandler> DRebellion: Just out of curiosity, why don't you want to sign it?
[20:23] <DRebellion> nhandler, because my name isn't in the changelog, so it attempts to sign with loic-m's credentials, which obviously don't exist.
[20:23] <nhandler> DRebellion: You do know that you can tell debuild to sign it with your key by doing -k followed by either your gpg key or your email address
[20:24] <DRebellion> nhandler, yes, but this build isn't going anywhere out of my computer. Also, I was just curious about the syntax if i DID want to not sign a package.
[20:24] <serialorder> can anyone explain to me when to use iceape-dev vs seamonkey-dev vs libxul-dev vs xulrunner-1.9-dev
[20:28] <serialorder> second question: if a merge or upgrade fixes a bug reported in a previous version of ubuntu lets say hardy, should that bug # be included the changelog to autoclose even though the fix is going into jaunty and not hardy?
[20:33] <loic-m> DRebellion: sorry I was away. Does it build fine?
[20:34] <DRebellion> loic-m, yep. I've made some comments on the revu page.
[20:35] <loic-m> I use debuild -S -uc -us a lot because each time I use debuild -S -sa it asks for my password two times. And I chose a long password :(
[20:36] <DRebellion> loic-m, well, sounds like nobody's going to bruteforce yours anytime soon. Anyway, I must go. Good luck with ecm.
[20:37] <loic-m> DRebellion: thanks alot for the comments on REVU
[20:43] <loic-m> DRebellion: if you're still there, when removing configure: rules, I assume I also habe to remove configure-stamp:
[20:53] <anmar> RainCT, pochu: hey guys I am here...
[20:53] <anmar> RainCT, pochu: I will touch base with you tomorrow. cheers!
[21:01] <Laney> What does svn-buildpackage mean by this? http://paste.ubuntu.com/91099/
[21:03] <bbs> Template #1 in /var/lib/dpkg/tmp.ci/templates has a duplicate field "template" with new value "Dexrex/ToS-accepted". Probably two templates are not properly separated by a lone newline.
[21:03] <bbs> wtf does that mean oO
[21:03] <bbs> my template was based on how paralells did theirs
[21:20] <pochu> Laney: try with --svn-ignore-new
[21:21] <pochu> Laney: it may be due to the missing file
[21:21] <Laney> Yeah, I think I have to use svn rm instead of rm
[21:21] <pochu> (adonthell.desktop)
[21:21] <pochu> yeah :)
[21:22] <Laney> ah, there we go
[21:22] <Laney> thanks
[21:45] <rrittenhouse> I'm trying my hand at packaging. I packaged the hello program in the PackagingGuide but i'm looking for suggestions on a second package that might teach me a few new things but without being too overwhelming.
[21:46] <CarlFK> rrittenhouse: well, you could help me with my 'small' but real project that has one little anoying thing I would like cleaned up
[21:47] <CarlFK> http://dpaste.com/101650/  rules and Makefile
[21:48] <CarlFK> I had to add $(PREFIX) to the make file.  that bothers me
[21:49] <CarlFK> I think rules should just run "scons install $(PREFIX)" without bouncing though make/Makefile
[22:01] <rrittenhouse> CarlFK, I'll be back in a couple of hours. Will you be around?
[22:04] <CarlFK> rrittenhouse: probably
[22:30] <bbs> Template #1 in /var/lib/dpkg/tmp.ci/templates has a duplicate field "template" with newvalue "dexrex/ToS-accepted". Probably two templates are not properly separated by a lone newline.
[22:30] <bbs> i don't get this
[22:31] <bbs> i have 3 templates in one file
[23:36] <loic-m> Is there a tool to download all relevant files from a package in REVU instead of manually clicking on each uploaded file?
[23:37] <nhandler> loic-m: Use get on the .dsc file
[23:37] <nhandler> s/get/dget/
[23:37] <nhandler> There is also a REVU source repository that you can use
[23:37] <loic-m> Thanks nhandler
[23:38] <nhandler> You're welcome loic-m
[23:42] <serialorder> there have been a number of merges I have seen with po files strings being split up differently, is that something I should worry about
[23:42] <serialorder> example: http://paste.ubuntu.com/91212/
[23:47] <loic-m> nhandler: I can't get the address of the REVU source repository... do you know where I can find it, or other keywords than "REVU source repository ubuntu"?
[23:49] <nhandler> loic-m: https://edge.launchpad.net/revu/+announcement/1224
[23:51] <loic-m> nhandler: Thanks a lot
[23:52] <nhandler> :)
[23:57] <loic-m> nhandler: it only downloads the first upload for the package though (one year old for the package i'm looking at). Is there a way to change that behavior?
[23:57] <nhandler> What method are you using?
[23:57] <loic-m> apt-get source
[23:58] <nhandler> I'm not sure. I would suggest just using dget
[23:58] <nhandler> You could try asking RainCT about the repo
[23:58] <nhandler> loic-m: ^^^