[00:16] <xteejx> Hi all
[00:27] <crimsun> Laney: is #227505 reproducible for you in a current daily live of 10.04?
[00:43] <xteejx> I found a script to tell me the depends and build-depends from the source... but I lost it, anyone know where to find it? I've googled for ages!
[01:07] <zooko> Greetings, people of #ubuntu-motu!
[01:16] <zooko> What does this mean? http://thread.gmane.org/gmane.linux.ubuntu.motu/6441
[01:16] <zooko> (Seen on lwn.net's Distribution page this week.)
[01:16] <zooko> Oh I guess I should read the referenced articles about ongoing discussion...
[01:19] <zooko> Huh. Interesting
[03:00] <dhillon-v10> hi all, while doing a merge, I find this one file present in Ubuntu but not in the Debian package, the changelog for debian doesn't mention about this file, so what's the best course of action here, keep that file or remove it
[03:21] <persia> dhillon-v10: The best course of action is always to understand what things do, and make your best determination as to whether it should keep being done.  What is the file in this case?
[03:28] <dhillon-v10> persia: thanks for the reply, the file is called: libecryptfs0.shlibs and it contains: libecryptfs 0 libecryptfs0 (>= 77)
[03:28] <dhillon-v10> persia: that's it
[03:28] <dhillon-v10> persia: bzr gives me this: Contents conflict in debian/libecryptfs0.shlibs
[03:29] <dhillon-v10> persia: but there's no marker in that file to cause a conflict
[03:29] <persia> Right.  Read the dh_makeshlibs manpage
[03:29] <dhillon-v10> persia: okay, just a minute
[03:31] <dhillon-v10> persia: so basically look for: dh_makeshlibs in the rules and if its there then i keep that file, because it basically contains the shlibs, and if its not there (which is the case) I can remove that file right?
[03:31] <persia> No.
[03:32] <persia> So, if dh_makeshlibs isn't there, then that's its own problem, because you're dealiing with a library.  Note that dh_makeshlibs is implied by dh(1) or cdbs.
[03:33] <persia> If it is there, then you might want to check the common ancestor to see if it was there before, or whether it's really an Ubuntu addition (you may also be able to check this from patches.ubuntu.com, depending).
[03:33] <dhillon-v10> persia: alright, I'll check patches.ubuntu.com
[03:33] <persia> Also, you might try building the package, and see if the binary shlibs files differ with and without that file, and also inspect the binary packages produced by recent uploads.
[03:34] <persia> (because dh_makeshlibs can generate one from scratch under some conditions).
[03:35] <persia> Your target goal should be to make sure that the binary packages (especially the -dev package) are constructed in such a way that other packages build-depending on the library on which you are working get the correct run-time dependencies from ${shlibs:Depends}
[03:35] <persia> You may or may not need to preserve (or modify) that file in order to reach this goal.
[03:35] <dhillon-v10> persia: yeah you are right, the file is indeed an ubuntu specific change, so I'll have  to keep it :)
[03:36] <dhillon-v10> persia: the patch says that
[03:37] <persia> dhillon-v10: Note that you may have to modify it, if the ABI has changed.
[03:38] <dhillon-v10> persia: so is that the cause of the contents-conflict bzr is giving, an outdated file
[03:38] <persia> I've no idea about that.  I can only tell you about the contents of the packages.
[03:48] <wrapster> i was trying to build libtspi and i get this error... http://pastie.org/799908
[03:48] <dhillon-v10> persia: another question: the po stuff that shows up in the diff should be removed right, the patch right now looks really long, because a major change was the formatting of changelog and control files
[03:48] <wrapster> what does this even mean?
[03:48] <persia> dhillon-v10: Best to ask questions generally.  Someone else may have a faster or better answer.
[03:49] <dhillon-v10> another question: the po stuff that shows up in the diff should be removed right, the patch right now looks really long, because a major change was the formatting of changelog and control files
[03:49] <persia> That said, Debian translations are preferred except in special cases (which would be noted in the changelog).  In cases where there are translations changes, it is important to migrate only the translations that are intentionally changed, and otherwise keep the Debian translations.
[03:50] <persia> wrapster: Check your build-depends.  If that doesn't work, try regenerating the autoconf stuff (but I think that's happening at build-time, from your log).
[03:57] <segler> hi, i am searchin' for advocates for my rhythmbox plugin, please help me. http://revu.ubuntuwire.com/p/rhythmbox-radio-browser
[03:59] <wrapster> persia: there were no buid-depends issues.
[04:00] <wrapster> yet i still get the same error
[04:00] <persia> wrapster: You're sure the desired version of all the libtool related stuff is being installed during the build?
[04:00] <persia> If so, you may have to relibtoolise (which is something I've not yet mastered), or it may be something else.
[04:03] <wrapster> persia: i just saw and one of the chid pkgs, has a dependency on libssl-dev.
[04:03] <wrapster> and thats not installed
[04:04] <persia> I doubt that's the cause of issues with LIBTOOL definition.
[04:04] <persia> That might be another issue though :)
[04:04] <wrapster> yeah.. its not.. it was my mistake.. thats already installed. :)
[04:09] <wrapster> persia: well this is what i want... Im trying to build the 64bit version of libtspi.so
[04:14] <wrapster> persia: reading across google seems to tell me i might need to have automake >=1.9 and i do have it.
[04:15] <wrapster> yet i dont really understand about this issue.. could you please help me/
[04:17] <persia> wrapster: I don't know anything beyond that included in your paste.  It appears AC_PROG_LIBTOOL isn't defined.  All I can suggest is investigating other build logs (especially ./configure output from a successful build of libtspi), and either following the advice from the error messages or something else.
[04:17] <persia> It may be that aclocal and autoconf aren't being run for some reason (if AC_PROG_RANLIB and AC_PROG_LIBTOOL are defined), or it may be something entirely different.
[04:18] <persia> I know lots about packaging and debugging crashes, but I only have a passing knowledge of autotools, and that mostly by running stuff and seeing the effects, rather than from any comprehensive source.
[04:19] <persia> (and asking please doesn't make me any more able to help you :) )
[04:41] <wrapster> persia: yeah i know.. but thats just courtesy.
[04:41] <wrapster> ;)
[04:43] <MTecknology> makefiles are ugly..
[04:43] <persia> Why?
[04:44] <MTecknology> persia: I can't get my head around this thing at all
[04:44] <persia> This is because of an aesthetic concern, or something else? :)
[04:44] <MTecknology> partly that possibly - I'm trying to fix up an itty bitty make file; it doesn't like me
[04:45] <persia> How are you trying to fix it?
[04:45] <MTecknology> lemme pull up the vm
[04:46] <MTecknology> I decided to do any development in a vm only
[04:46] <MTecknology> http://paste.ubuntu.com/364991/
[04:47] <MTecknology> I know there should be an uninstall: - I don't think it needs a clean: but should probably have one
[04:47] <persia> OK.  Which bit hates you?
[04:47] <MTecknology> beyond that - I'm clueless
[04:47] <MTecknology> I'm beed reading this - http://www.gnu.org/software/make/manual/make.html - and just getting confused
[04:47] <persia> make is an immensely powerful tool, and so confusing :)
[04:48] <MTecknology> The install: isn't right - I know that
[04:49] <persia> It's mostly right.  Use `install -m 644 -D` instead of cp for the manpage, and `install -m 755 -D` instead of cp for the binary.
[04:49] <MTecknology> If anything the man should be gzipped and sent to /usr/share/man/man1/lal.1.gz
[04:49] <persia> Also, you probably want to install to ${DESTDIR}/bin or ${INSTALLDIR}/bin or something, rather than /usr/bin
[04:49] <persia> Same for the manpage.
[04:50] <persia> Or, if you just want the makefile to play nice with a standard debian/rules, install to ${DESTDIR}/usr/bin and ${DESTDIR}/usr/share/man/man1
[04:52] <persia> If you want to be fancy, you could use ${DESTDIR}/${PREFIX}/bin and ${DESTDIR}/${PREFIX}/share/man/man1 and add a PREFIX ?= usr/local somewhere earlier (which you'd then override in debian/rules with PREFIX := usr)
[04:53] <MTecknology> any reason I'd do that over the other option?
[04:53] <persia> Your all: rule definitely isn't right.  all: should generally not have any specific activities, but rather just depend on other rules.  You might add a lal: rule, and have all: depend on lal:
[04:54] <persia> The fancy way I described installs into /usr/local/* (unless overridden) for a local make; make install, and installs to ${DESTDIR}/usr/* if PREFIX is overridden in debian/rules, thereby building the package you want.
[04:55] <MTecknology> how do I override that?
[04:55] <persia> Other tricks that might be useful would be things like CFLAGS ?= $(shell pkg-config x11 xft --libs --cflags), and then using ${CFLAGS} in your calls.
[04:55] <persia> If you want to be fancy, you could use ${DESTDIR}/${PREFIX}/bin and ${DESTDIR}/${PREFIX}/share/man/man1 and add a PREFIX ?= usr/local somewhere earlier (which you'd then override in debian/rules with PREFIX := usr)
[04:55] <MTecknology> sorry
[04:56] <persia> No problem: it's just easier for me to quote myself than retype :)
[04:57] <persia> actually, for CFLAGS, you'd probably want += rather then ?=.  That way you can take advantage of any extra cflags that get defined somewhere else.
[04:57] <MTecknology> so in rules:   %:    PREFIX ?= usr/local    dh  $@
[04:57] <persia> No.
[04:57] <persia> Put your variable defintion above your rules.
[04:58] <MTecknology> oh - you said put that part in the makefile - override in rules
[05:00] <rhpot1991> hmmm no RAOF tonight
[05:00] <MTecknology> so in deb/rules I have PREFIX = usr/bin  ?
[05:00] <rhpot1991> persia: (or anyone else), mind taking a quick peak at this: http://mythbuntu.pastebin.com/d306a3b3d
[05:00] <persia> rhpot1991: It's best to just ask a question.  Whoever happens to be around will probably answer.
[05:01] <rhpot1991> oh wait, I think I see my issue
[05:01] <rhpot1991> persia: ignore me till I fix a path issue
[05:01] <persia> rhpot1991: I don't see the point of a manual postinst: read the dh_makeshlibs manpage
[05:01] <persia> Also, install the file to libfoo.so.n and the link to libfoo.so
[05:02] <persia> MTecknology: I'd probably use "export PREFIX := usr", but it might work without all the syntactic sugar.
[05:03] <persia> You don't want usr/bin, because you're using ${DESTDIR}/${PREFIX}/bin/ so you already have the "bin".
[05:04] <MTecknology> so export pre.... goes after %: in deb/rules ?
[05:04] <persia> Before.
[05:04] <persia> Actually, if you use "export PREFIX := usr", it doesn't matter, but the convention is to define the variables before the rules.
[05:05] <MTecknology> ok
[05:05] <MTecknology> so how do I require something else?
[05:05] <MTecknology> in the makefile
[05:06] <persia> How do you mean "require"?
[05:06] <MTecknology> inside all: require lal:
[05:07] <persia> "all: lal"
[05:07] <persia> That means the all: rule depends on either the lal: rule or the lal file.
[05:08] <persia> (typically rules are named after the files they generate.  For other types of rules, there'S the special .PHONY: rule which one uses to indicate make shouldn't check files.  For more information, read about .PHONY in the make manual)
[05:08] <MTecknology> and lal: is where I build thing?
[05:08] <persia> The lal: rule should create the lal: binary.
[05:09] <MTecknology> and and for lal.1? the man page
[05:09] <MTecknology> since it will need to be gzipped
[05:10] <persia> You could create a lal.1.gz: rule for that.
[05:10] <persia> If you did, you probably want your install: rule to depend on lal and lal.1.gz
[05:11] <rhpot1991> persia: let me run this by you then, upstream wasn't including any soname data at all, I'll be submitting a patch for this.  In their build process they reference libhdhomerun.so directly.  Can I handle the symlinking myself in the packaging, or does this need to be done at the build phase?
[05:12] <persia> rhpot1991: You can handle it in the packaging if you like.  If upstream isn't including SONAME data, I strongly encourage you to create a symbols file to track ABI shifts.
[05:12] <persia> dh_link is probably interesting.  dh_install can't rename files, so you'd have to do that in debian/rules directly.
[05:13] <wrapster> what does Provides: mean in the control file?
[05:13] <MTecknology> persia: so if you run 'make' will that do what's in all: ?
[05:13] <persia> Yes.
[05:14] <MTecknology> and in the install command, how do I specify the source I'm moving?
[05:14] <rhpot1991> persia: happen to have a link or anything a symbols file?
[05:15] <MTecknology> install -m 755 -D ${DESTDIR}/${PREFIX}/bin/ lal
[05:15] <persia> !symbols
[05:15] <persia> Hrm.
[05:15] <persia> https://wiki.ubuntu.com/stefanlsd/dpkg-gensymbols
[05:15] <persia> MTecknology: man install :)  I'll give you make syntax, because programming language manuals are tricky, but simple commands are easy :)
[05:16] <MTecknology> I wasn't aware of an install command :P
[05:17] <MTecknology> Looks like I want this -   install -m 755 -D ${DESTDIR}/${PREFIX}/bin/ lal lal
[05:18] <MTecknology> I know one way to know for sure :)
[05:19] <persia> heh :)
[05:21] <MTecknology> yup - that was wrong
[05:21] <persia> Maybe drop one of the spaces?
[05:22] <rhpot1991> persia: whats the proper way to handle this whole issue, currently their makefile just inserts empty soname data, I have modified this to insert some real data but now my link are backwards, should the makefile handle the linking or should everything build off the full soname file version?
[05:23] <MTecknology> persia: I thought I was supposed to have a space after the -D /dir/ because it said that sets up everything except the last piece in man install
[05:24] <persia> rhpot1991: In an ideal world, the upstream makefile will build shared library into a versioned binary.  My personal preference when this doesn't happen is to wangle this in debian/rules and add a symbols file, but patching the upstream makefile is arguably more correct because it produces a patch one can send upstream.
[05:25] <persia> MTecknology: install [OPTION]... [-T] SOURCE DEST
[05:26] <MTecknology> persia: install -m 755 lal ${DESTDIR}/${PREFIX}/bin/lal worked
[05:26] <MTecknology> I'm lost with the -D
[05:27] <MTecknology> google isn't nice in finding examples :P
[05:27] <MTecknology> something about a command being called install
[05:27] <persia> -D creates any directories that didn't exist.  Like mkdir -o
[05:27] <persia> Err, mkdir -p
[05:27] <persia> It's a *good* name.  The command installs stuff.
[05:27] <MTecknology> oh
[05:28] <MTecknology> .... that makes much more sense when I read it now
[05:28] <MTecknology> I didn't say it's a bad command - but it's a hard one to search for
[05:29] <MTecknology> so   install -m 755 -D ${DESTDIR}/${PREFIX}/bin/ ./lal ${DESTDIR}/${PREFIX}/bin/lal
[05:29] <MTecknology> or w/o the ./ probably
[05:32] <MTecknology> I try that and I get install: target `/usr/bin/lal' is not a directory
[05:33] <persia> MTecknology: Are you root?
[05:33] <MTecknology> ya
[05:33] <persia> And you had the -D?
[05:33] <persia> Oh, I see the issue.
[05:34] <persia> read the very first line of the summary in the manpage again.
[05:34] <MTecknology> DOH!
[05:34] <MTecknology> OK!
[05:34] <MTecknology> -D takes no arguments
[05:34]  * MTecknology facepalm at man page
[05:35] <MTecknology> sorry for missing that
[05:37] <MTecknology> alrighty - I'm guessing I should be able to start a new terminal session - make; sudo make install
[05:37] <MTecknology> nope
[05:38] <MTecknology> I thought lal and lal.1.gz after all had their own lines - I guess not
[05:38] <persia> paste your Makefile again?
[05:39] <MTecknology> http://paste.ubuntu.com/365006/
[05:39] <MTecknology> little different now
[05:39] <persia> Right.  all: typically wouldn't depend on lal.1.gz
[05:39] <persia> install: needs to depend on the stuff it's copying.
[05:40] <persia> Drop the export line from install, you want just "PREFIX ?= usr/local" at the top (above all:)
[05:40] <MTecknology> oh.. does the user still needto do make before make install?
[05:40] <persia> Right now, yes, but if you follow my advice above, no.
[05:41] <MTecknology> ok; I always that that was the norm :P
[05:41] <persia> It is, but that's for entirely different reasons.
[05:41] <MTecknology> ok, should I just have all:    lal
[05:42] <MTecknology> then install:   lal   lal.1.gz ?
[05:42] <persia> You can leave all: alone or not, as you like, but if you don't specify the dependencies in install, you are prone to errors.
[05:42] <MTecknology> ok
[05:43] <persia> Also, you're installing by default to /usr/local/usr/bin : is that what you want?
[05:43] <MTecknology> I dropped /usr from that
[05:44] <persia> I can only critique what I see :)
[05:44] <MTecknology> http://paste.ubuntu.com/365009/
[05:44] <MTecknology> I meant because you said it - just letting yoy know I listened
[05:46] <MTecknology> heh - 'make' doesn't want to do anything now
[05:46] <MTecknology> and I see why :P
[05:46] <persia> That's why you want a clean: rule :)
[05:47] <MTecknology> just an rm command?
[05:48] <MTecknology> and depend on clean?
[05:49] <persia> No.
[05:49] <persia> A clean: rule.  clean: rules typically contain lots of "-rm " lines.
[05:50] <MTecknology> -rm ?
[05:50] <MTecknology> I know "rm" but "-rm"..
[05:50] <MTecknology> I just tossed this together now - http://paste.ubuntu.com/365013/
[05:50] <MTecknology> apparently wrong :P
[05:52] <MTecknology> persia: sorry for trying to jump into this with apparently very little knowledge - I thought I knew enough to be able to do better than this
[05:52] <MTecknology> nice big learning curve that I'm hoping to overcome someday
[05:52] <MTecknology> RAOF: hi - somebody was looking for you
[05:52] <MTecknology> 23:00 < rhpot1991> hmmm no RAOF tonight
[05:53] <persia> Two recommendations.  1) prefix any line you don't care about succeeding with '-'.  This is useful in case you want to, for example, run `make clean; make clean`.  2) don7t bother with all the ./ entries.  make knows where it is.
[05:53] <rhpot1991> I hit up persia all good :)
[05:53] <MTecknology> ok
[05:53] <RAOF> rhpot1991: Hah.
[05:53] <persia> But I'll leave the rest of it to either the make manual or someone else :)
[05:54] <MTecknology> persia: thanks - I'll try out this sexxy beast now
[05:54] <persia> Oh, one last bit: install depending on clean: means that the stuff will always be deleted before being installed.
[05:54] <MTecknology> I'll not do that if that's bad
[05:55] <RAOF> Well, generally you need to not delete the things that you're about to try to install :)
[05:55] <MTecknology> err - I was thinking depend on uninstall
[05:55] <MTecknology> which I guess isn't needed
[05:56] <MTecknology> I thought -D created a directory if not exists
[05:57] <MTecknology> It doesn't want to isntall lal.1.gz
[05:58] <MTecknology> Is that something that shouldn't have ${PREFIX} in it?
[05:58] <MTecknology> just ${DESTDIR}/usr/share/man/man1/lal.1.gz
[06:00] <MTecknology> -D  create all leading components of DEST except the last, then  copy
[06:00] <MTecknology> It should make that part - not complain
[06:02] <MTecknology> persia: thats for putting up with me again - I have the ITP filed too - so it's probably figure out a few tiny things on my own - then take the peoples suggestions - then actually submit to debian and file RFS :D
[06:02] <MTecknology> persia: I appreciate all the help and holding my hand
[06:02] <MTecknology> RAOF: thanks for your help too :)
[07:46] <alkisg> How can I allow 2 individuals full read/access to my bzr branch? (https://code.launchpad.net/sch-scripts)
[08:02] <dholbach> good morning
[08:22] <iulian> G'morning Daniel.
[08:28] <dholbach> hiya iulian
[08:30] <dupondje> this feels stupid :)
[08:30] <dupondje> https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/513802
[08:30] <dupondje> and 1 hour after it, the FTBFS got fixed :)
[08:47] <Laney> crimsun: (re #227505) No, I don't see that any more, but (on a dist-upgraded system, not a live cd) I'm having to toggle mute to get any sound output
[10:10] <om26er> I am having a problem with finding the copyrights of a tarrball I downloaded
[10:11] <slytherin> om26er: isn't there any COPYING or LICENSE file?
[10:11] <directhex> om26er, that's usually not a great sign. have you tried contacting the upstream developer?
[10:12] <om26er> slytherin, yes copying file is there
[10:12] <slytherin> om26er: then what is the issue?
[10:13] <om26er> slytherin, what should I look for in there? copyrights change with time
[10:13] <slytherin> om26er: Wait a minute, are you looking for license or copyright owners?
[10:14] <slytherin> I mean copyright holders for the code.
[10:14] <om26er> slytherin, copyright ownsers
[10:14] <om26er> ya
[10:14] <slytherin> is there AUTHORS file?
[10:15] <om26er> slytherin, yess
[10:15] <om26er> am looking
[10:15] <slytherin> om26er: doesn't it list copyright holders?
[10:16] <om26er> slytherin, no it dont
[10:17] <slytherin> om26er: Another option. a bit manual and lengthy. Check headers of source files. grep for word Copyright in the source files.
[10:38] <om26er> I got this error http://pastebin.org/83882 while building
[11:18] <om26er> please help I am getting the error when building  dpkg-buildpackage: error: debian/rules build gave error exit status 2
[11:32] <maxb> om26er: That is merely the consequence of an earlier error
[11:33] <om26er> maxb, did I do something wrong?
[11:40] <maxb> You'd need to pastebin more of your build log for people to help
[11:46] <om26er> maxb, terminal log?
[11:46] <maxb> yes
[11:57] <xteejx> If a source comes in several different packages, i.e. 1..the source for a program, 2..the data, 3.....the sounds ... can these be packaged separately and depend on each other without any problems?
[11:57] <om26er> here is the terminal log http://pastebin.org/83897
[11:58] <xteejx> Hi om26er :) Congrats on your Bug Control application
[11:58] <om26er> xteejx, thanx :)
[12:09] <slytherin> xteejx: Sure why not. In fact the new source format 3.0 allows different upstream tar balls to be combined together.
[12:09] <xteejx> Oh wow ok :)
[12:10] <slytherin> xteejx: If you want to package it old way you will have to create 3 different source packages. Otherwise use 3.0 format - http://wiki.debian.org/Projects/DebSrc3.0
[12:10] <xteejx> Cool, thanks slytherin
[12:43]  * directhex wonders if he owes bddebian cake
[15:04] <xteejx> FTBFS: https://launchpad.net/ubuntu/+source/ogre-contrib/1.6.4-1/+build/1350584  - builds fine locally on i386
[15:10] <xteejx> The error seems to be the autobuilder did not install nvidia-cg-toolkit, whereas locally it was fine.
[15:10] <xteejx> dholbach: ^
[15:10] <dholbach> I have no idea
[15:10] <dholbach> xteejx: but maybe somebody else can - I need to sort out a few other things
[15:10] <xteejx> No probs Daniel
[15:11] <xteejx> Anyway, I checked the control file and everything seems fine there, may have just been a quirk
[15:12] <statik> hi! is there a standard way to rename a file in a debian/patches patch? If I use cdbs-edit-patch, then rename the file directly, the resulting patch I get shows a complete removal and add of a new file, which is way more noisy than I want
[15:39] <dholbach> final day of https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in 22 minutes in #ubuntu-classroom on irc.freenode.net (first up: "Writing Beautiful Code")
[16:20] <RoAkSoAx> james_w, Heya. Hey one quick question. While doing 'bzr builddeb' i get an error 'bzr: ERROR: [Errno 2] No such file or directory:' on a patch I deleted. How to override or what i can be doing wrong?
[16:23] <geser> RoAkSoAx: did you tell bzr that the patch got removed? (bzr remove)
[16:24] <RoAkSoAx> geser, nope, but indeed that was the problem :) thanks  :)
[16:35] <highvoltage> hi, I'm reviewing zope.annotation (http://revu.ubuntuwire.com/p/zope.annotation) it says priority: extra
[16:35] <highvoltage> it should be 'optional', right?
[16:44] <randomaction> highvoltage: unless in conflicts with something or depends on "extra" package
[17:01]  * jdong unamusingly glares at VMWare
[17:01] <jdong> which just told me that a snapshot's size ranges anywhere from 768MB (RAM size) to 10.5GB (disk+RAM size)
[17:39] <tim> hi, i am trying to build a deb of gcc-4.4.3 for karmic. the folder created by apt-get source does't contain the source directly, but a tarball ... when trying to build the package, dpkg-source complains, that the binary file content changed ... any idea, what i am doing wrong?
[17:42] <daurnimator> hey all
[17:43] <daurnimator> so this probbaly isn't the correct channel
[17:43] <daurnimator> but I'm coding a daemon
[17:43] <fabrice_sp> tim, how are you trying to build it?
[17:43] <daurnimator> but I have no idea how to package/run/instlal/debainise it
[17:44] <tim> fabrice_sp, with git buildpackage
[17:44] <daurnimator> (eg, where to install, init.d scripts, how to make a pkg for it, etc)
[17:44] <fabrice_sp> !packaging | daurnimator
[17:44] <fabrice_sp> tim, if you have the source locally, you should use debuild -b
[17:45] <tim> fabrice_sp, i will give it a try
[17:58] <segler> hi, i am searchin' for advocates for my rhythmbox plugin, please help me. http://revu.ubuntuwire.com/p/rhythmbox-radio-browser
[18:01] <fabrice_sp> segler, version should be -0ubuntu1
[18:02] <fabrice_sp> also, why do you need a dir file?
[18:03] <fabrice_sp> otherwise, looks good. I'll have a deeper look later
[18:12] <crimsun> Laney: which mixer element(s) do you need to unmute?
[19:09] <ari-tczew> how can I close a few bugs in debian/changelog?
[19:09] <ari-tczew> (LP: #bug, #bug2) ?
[19:10] <Quintasan> ari-tczew: If one change closes multipe bugs shouldn't they be marked as duplicates?
[19:11] <Quintasan> ari-tczew: if the bugs are related but not the same and are closed by the same fix I belive you can do as you said - (LP: #bug1, #bug2)
[19:11] <ari-tczew> like so, but I want to know
[19:12] <Quintasan> ari-tczew: if the bugs in question have exacly same problems I would mark one of them as duplicate and close only one
[19:12] <directhex> sebner, how close to done is longomatch? all its build-deps are transitioned, so sponsorship is running at full speed again
[19:13] <ari-tczew> quintasan, statistic mate ;)
[19:13] <sebner> directhex: hmm, I wanted to wait for new upstream version but if you give me some minutes it's ready for now too
[19:14] <directhex> sebner, well, it's RC you see... and stuff is being pulled into lucid by an eager seb128 too. we're almost done \o/
[19:15] <sebner> directhex: heh, ok. then give me some minutes. I'll make it ready then
[19:15] <ari-tczew> Quintasan, btw. would you like to take sponsor now?
[19:15] <directhex> sebner, it seems to work fine against db4o 7.4, thankfully
[19:16] <Quintasan> ari-tczew: uh sure, where I can get the diff?
[19:16] <sebner> directhex: haven't tested that yet. Yesterday db4o was still untransitioned so I didn't bother doing testing
[19:17] <ari-tczew> Quintasan, bug 255360
[19:17] <directhex> sebner, a sexy ftpmaster (i guess bddebian) has been clearing things though NEW, which was running reasonably quickly anyway
[19:17] <sebner> directhex: heh, yeah he's great :)
[19:22] <Quintasan> ari-tczew: well, builds fine, let me check debian/ then :P
[19:22] <ari-tczew> sure
[19:24] <sebner> directhex: I'll give it a testbuild now, I'll tell you when ready for sponsoring
[19:26] <Quintasan> ari-tczew: I like it, builds fine and I didn't find any problems :)
[19:27] <ari-tczew> Quintasan, cool, would you like take sponsor on other bugs?
[19:27] <ari-tczew> with debdiff now
[19:28] <Quintasan> well I have time so no problem
[19:28] <Quintasan> it would be good if someone else could review it too
[19:31] <ari-tczew> Quintasan, go ahead bug 514453
[19:33] <Quintasan> ari-tczew: this one is fine with me too
[19:33] <highvoltage> if anyone's around for reviewing some zope packages so that we can get schooltool back in ubuntu, there's just two left that needs reviewing:
[19:33] <highvoltage> http://revu.ubuntuwire.com/p/zope.server
[19:33] <highvoltage> http://revu.ubuntuwire.com/p/zope.size
[19:47] <kamalmostafa> ScottK: hi Scott -- reminder: we've been sitting on libtifiles/libticalcs for a couple weeks now.  :-)
[19:47] <ScottK> kamalmostafa: It's pretty near the top of my Ubuntu TODO at this point.
[19:49] <kamalmostafa> ScottK: sounds good.
[19:57] <_stink_> anyone know of a way to have dpkg (or some other debian packaging magic thing) (1) check whether a .deb's dependencies are already installed, and (2) return an error to the shell if not?
[19:57] <_stink_> --no-act doesn't seem to care about whether depends are installed.
[20:04] <hakaishi> Hi everyone! Anyone up to advocate/review qt-shutdown-p? - I corrected the desktop file, the copyright file and the docs file as jcfp asked. http://revu.ubuntuwire.com/p/qt-shutdown-p
[20:05] <ScottK> hakaishi: I know you've been asking a long time.  You might consider asking the Debian qt-kde team if they are interested and if they are, get it into Ubuntu via Debian.  See #debian-qt-kde on OFTC.
[20:06] <geser> _stink_: you could use "gdebi --quiet --aptline $package.deb" and check if it lists something or not
[20:08] <_stink_> geser: omg.  that is awesome.
[20:08] <_stink_> i owe you a beverage should we cross paths.
[20:09] <Quintasan> hakaishi: it's good, I think if you go to Debian they should be fine with it
[20:09] <_stink_> crap, i didn't even know about gdebi.
[20:10] <hakaishi> ScottK: I thought, I get advocations only if there are no issues with the package. And since there no longer are, I thought I'll ask for it now^^
[20:10] <ScottK> hakaishi: I haven't been following the details of your package, I've just been noticing you've been asking for a while.
[20:12] <hakaishi> ScottK: Everything should be okay with the new upload. The others weren't okay because of copyright and the rules file or such
[20:12] <Quintasan> hakaishi: AFAIK it would be better to get it to debian, if you want to change it just get a newer version to Debian and request a sync, both projects will gain something :)
[20:14] <hakaishi> On which server does #debian-qt-kde run? - I mean the exact address
[20:14] <Quintasan> hakaishi: irc.oftc.net I belive
[20:15] <hakaishi> okay, thanks
[20:17] <hakaishi> Is there a website for debian-qt-kde like revu.ubuntuwire.com?
[20:18] <Quintasan> hakaishi: hmm I think you can upload to mentors.debian.org
[20:24] <hakaishi> Thank you, maybe I will try to get it into debian, maybe not. I'll see tomorrow. Bye bye
[20:34] <wind-rider> hi
[20:35] <geser> Hi
[20:35] <wind-rider> on my kubuntu lucid installation the package soprano-daemon is installed
[20:36] <wind-rider> it is made dependent on virtuoso-server today / yesterday to fix https://bugs.launchpad.net/bugs/505653
[20:37] <wind-rider> kpackagekit shows that soprano-daemon is dependent on it, but still virtuoso-server is not installed automatically
[20:37] <wind-rider> is that a bug?
[20:38] <geser> Depends or Recommends like the changelog says?
[20:39] <geser> Recommends: virtuoso-server (>= 5.0.12-0ubuntu3), ...
[20:39] <wind-rider> geser: oh, then that's the problem
[20:39] <wind-rider> geser: but that's wrong
[20:40] <ScottK> wind-rider: Probably better to ask in #kubuntu-devel.
[20:40] <wind-rider> ScottK: ok, I'll do that
[20:40] <wind-rider> virtuoso should be installed by default and not as an option
[20:40] <geser> usually Recommends are auto-installed like Depends
[20:41] <geser> but I don't know how kpackagekit behaves at it
[20:42] <ari-tczew> fabrice_sp: ping
[20:51] <sebner> directhex: ready for sponsoring :)
[21:03] <wind-rider> geser: thx, i discussed it at #kubuntu-devel
[21:04] <wind-rider> and added a comment to the bug report
[21:12] <MohammadRRR> Hi , How Gnome-do can shutdown without requesting passwird
[21:12] <MohammadRRR> *password
[21:14] <directhex> sebner, ta, i'll take a peek & upload once dinner is eaten
[21:15] <sebner> directhex: great, thx. Just ask if you have any questions
[21:20] <randomaction> fabrice_sp: could you check if zshdb builds for you? It FTBFS on buildd but builds fine in pbuilder. (bug 514359)
[21:20] <fabrice_sp> randomaction, sure
[21:21] <randomaction> maybe it only manifests in sbuild
[21:22] <ScottL_> would someone mind looking at zynjacku package in REVU ( http://revu.ubuntuwire.com/p/zynjacku ) ?
[21:23] <fabrice_sp> randomaction, I also installed some 'checking' packages (don't remember the name), that are responsable of some FTBFS in hte buildd
[21:23] <fabrice_sp> so let see what happens
[21:24] <fabrice_sp> ScottK, you should update the Maintainer field
[21:24] <randomaction> wrong nickname
[21:26] <fabrice_sp_> ScottL, also some comments in copyright (# Please also look if there are files or directories which have a
[21:26] <fabrice_sp_> # different copyright/license attached and list them here.
[21:26] <fabrice_sp_> )
[21:26] <fabrice_sp_> argh. got idsconnected
[21:27] <directhex> sebner, seems to build fine
[21:27] <sebner> directhex: sure, I (at least) fiXX0red the build :P
[21:27] <fabrice_sp_> randomaction, FTBFS
[21:28] <directhex> sebner, well, gotta check these things!
[21:28] <fabrice_sp_> FAIL: test-tbreak
[21:28] <dupondje> who can accept packages that are in queue ? :)
[21:28] <fabrice_sp_> dupondje, do you mean NEW?
[21:28] <directhex> source format 3.0? sod it, i'll upload anyway
[21:28] <dupondje> https://launchpad.net/ubuntu/lucid/+queue here ...
[21:28] <ScottL_> fabrice_sp_:  you said that ScottK should update the Maintainer field...did you mean ScottL (me) ?
[21:29] <fabrice_sp_> yes. Sorry
[21:29] <fabrice_sp_> your nicks are very close :-)
[21:29] <fabrice_sp_> dupondje, archive admins
[21:29] <ScottL_> yeah, it's been problematic sometimes
[21:30] <fabrice_sp_> :-D
[21:30] <randomaction> fabrice_sp_: ok, so reproducible in sbuild
[21:30] <randomaction> fabrice_sp_: thank you
[21:31] <fabrice_sp_> ScottL, you should also reviewyour copyright: you have sources with LGPL and different people
[21:31] <fabrice_sp_> randomaction, yw ;-) Do you want me to do more tests?
[21:34] <sebner> directhex: Yeah, I asked you 3 weeks ago (if you remember) and you didn't say to have a problem with it, else I just have to find someone else
[21:36] <fabrice_sp_> Quintasan, did you check rdepends for liblo?
[21:38] <fabrice_sp_> (just to see if we have a transition to do for the 26 rdepends)
[21:38] <ari-tczew> fabrice_sp_: I think tht nobody have time for testing all rdepends
[21:39] <fabrice_sp_> ari-tczew, so you prefer to have 26 packages that FTBFS?!
[21:40] <ari-tczew> ahh, you mean check building?
[21:40] <fabrice_sp_> yes. and test some of them.
[21:40] <Quintasan> fabrice_sp_: urgh my fault, I only checked libol to build in lucid
[21:40] <fabrice_sp_> this is a huge change (from liblo0 to liblo7), so I expect some ABI changes
[21:40] <ScottL_> fabrice_sp_:  thank you for looking at zynjacku in REVU, i'm at work so I'll look at the maintainer field and copyright at home tonight :)
[21:41] <fabrice_sp_> Quintasan, no problem ;-)
[21:41] <fabrice_sp_> ScottL, I'm putting my comments in revu (discovered more stuff :-) )
[21:41] <ScottL_> oh, excellent, thanks again :)
[21:42] <fabrice_sp_> Quintasan, ari-tczew This is only that if there is a transition to do, it's easy to create a bug report and request some help (26 packages is not that huge). Just my 2 cents
[21:42] <fabrice_sp_> ScottL, yw ;-)
[21:42] <ScottL_> the whole REVU process is teaching me gobs of stuff :)
[21:43] <fabrice_sp_> :-D
[21:44] <fabrice_sp_> last time (less that one moth ago) I requested a package review I discovered a lot of thing I forget to check in my own package;-)
[21:44] <Quintasan> fabrice_sp_: I wonder if I can somehow list all rdepends without searching on packages.ubuntu.org
[21:44] <fabrice_sp_> apt-cache rdepends liblo0 ?
[21:45] <directhex> sebner, you've closed yourself off from backports.org tho
[21:45] <Quintasan> liblo0
[21:45] <Quintasan> :/
[21:45] <fabrice_sp_> Quintasan, it's not liblo0?
[21:45] <Quintasan> I belive no, hmm'
[21:45]  * fabrice_sp_ is beginning to be tierd :-D
[21:45] <ari-tczew> fabrice_sp_: now please just tell me, do we need check only FBTFS or FTBFS + general work all rdepends?
[21:46] <sebner> directhex: that's calculated because 1) there is not really a reason for backporting any app I maintain 2) git revert. no problem at all
[21:46] <Quintasan> fabrice_sp_: it would be liblo0ldbl rather
[21:46] <fabrice_sp_> Quintasan, right
[21:46] <fabrice_sp_> ari-tczew, I would build and test some of them
[21:47] <Quintasan> fabrice_sp_: and I'm supposed to grab sources of those from debian and thest them against lucid pbuilder as well?
[21:47] <fabrice_sp_> Quintasan, I would build the lucid actual source
[21:47] <fabrice_sp_> anyway, because the lib name change, we have to rebuild all of them
[21:48] <randomaction> fabrice_sp_: I guess I'll just give a hint to DM of zshdb and leave it to the interested parties :)
[21:48] <fabrice_sp_> as the lib is in Experimental, I expect some problems
[21:48] <fabrice_sp_> randomaction, :-D
[21:48] <Quintasan> so I need to setup a custom pool for pbuilder?
[21:48] <fabrice_sp_> randomaction, when test fails, it's generally hard
[21:49] <fabrice_sp_> Quintasan, or use a chroot for that, and manually install liblo or use a ppa :-)
[21:49] <randomaction> fabrice_sp_: it fails because the script which contains the test cannot be found
[21:50] <fabrice_sp_> Quintasan, I've done that with a ppa before
[21:50] <fabrice_sp_> randomaction, oh. perhaps the script is not installed?
[21:50] <Quintasan> oh well, night it long so I might build them all as well
[21:50] <Quintasan> :P
[21:50] <Quintasan> is*
[21:51] <fabrice_sp_> lol
[21:51] <ari-tczew> Quintasan, regards!
[21:51] <randomaction> fabrice_sp_: maybe, but in this case it must be a really weird situation, as everything runs fine in pbuilder
[21:51] <fabrice_sp_> I tried that with maven, some time ago, and uploaded more than 40 packages! :-)
[21:52] <ari-tczew> btw. please mate upload pyalsaaudio :>
[21:52] <Quintasan> ari-tczew: you're going to build some too, aren't you? :>
[21:52] <fabrice_sp_> randomaction, right. I may check my build log
[21:52] <ari-tczew> fabrice_sp_: I remember maven action :>
[21:52] <fabrice_sp_> :-D
[21:53] <fabrice_sp_> dooooomi, about bug your comment in bug 514491
[21:54] <ari-tczew> Quintasan, no tonight :( ... tomorrow I'm going on celebrations about my city Tczew (750 years)
[21:54] <fabrice_sp_> dooooomi, the problem is that old lib becomes NBS, and that we should get rid of it as soon as the new one is uploaded
[21:55] <fabrice_sp_> that's where transitions comes from
[21:56] <ari-tczew> so if I right understand, sponsors have to upload debdiffs in versions e.g. 1build1 for rdepends?
[21:57] <fabrice_sp_> randomaction, in which step does the script processor.sh built in pbuilder?
[21:57] <fabrice_sp_> ari-tczew, yes
[21:57] <fabrice_sp_> randomaction, I can't find any reference to it in my log
[21:58] <randomaction> it gets installed late in the process, no evidence of running
[21:59] <randomaction> fabrice_sp_: http://paste.ubuntu.com/365429/
[22:01] <fabrice_sp_> very strange
[22:01] <randomaction> probably tests run it and expect it to be there
[22:01] <randomaction> they are silent it all is ok
[22:01] <randomaction> s/it all/if all/
[22:02] <dooooomi> fabrice_sp_: ok. anyway, the point is that most likely all rdepends can be rebuilt using the new version of the library with no problems. though i'm not quite sure what exactly would need to be done to achieve that
[22:02] <fabrice_sp_> randomaction, but in your case, the tests are ok, so it seems it can actually  find it
[22:02] <randomaction> yep
[22:03] <fabrice_sp_> dooooomi, upload a new revision for each rdepends (as build1 if the package comes from Debian)
[22:03] <fabrice_sp_> randomaction, weird
[22:03] <fabrice_sp_> :-D
[22:03] <fabrice_sp_> can you enter in your pbuilder (with login), and actually build the package? I'm getting curious when this file comes from :-D
[22:05] <fabrice_sp_> dooooomi, anyway: this is good news that actually we won't have any FTBFS because of that ;-)
[22:07] <dooooomi> fabrice_sp_: i'm at least 99.9% sure about that ;)
[22:07] <fabrice_sp__> grrrr: got disconnected again :-/
[22:07] <fabrice_sp__> dooooomi, cool! :-) That will be an easy transition the n;-)
[22:08] <randomaction> fabrice_sp__: you grew an additional underscore :)
[22:08] <fabrice_sp__> lol
[22:09] <fabrice_sp__> I only can have 2 ;-)
[22:12] <fabrice_sp_> randomaction, in a new chroot, the package builds fine
[22:15] <fabrice_sp_> it may be because of .sh not being directly runnable
[22:15] <fabrice_sp_> have to go now. Will check tomorrow. Bye
[22:16] <randomaction> fabrice_sp_: bye
[22:53] <Quintasan> randomaction: got a second?
[22:53] <randomaction> Quintasan: yes
[22:54] <Quintasan> randomaction: well, I want to sponsor ari-tczew package, I grab the debdiff from him, apply and testbuild and if everything is allight I can upload?
[22:54] <Quintasan> allright even.
[22:54] <randomaction> yes. If you use debuild, signing is done with -kKEYID
[22:55] <Quintasan> randomaction: hmm I wonder now because the changelog will mention his name, won't debuild look for his key?
[22:55] <randomaction> so you use -k with your keyid
[22:56] <randomaction> and it uses it to sign
[22:56] <crimsun> cat ~/.devscripts
[22:56] <crimsun> DEBSIGN_KEYID=foo
[22:57] <randomaction> crimsun: thanks, that's handy :)
[23:00] <Quintasan> randomaction, crimsun: thanks
[23:04] <ari-tczew> what about latest MOTU Council Meeting?
[23:04] <ari-tczew> who has been joined to MOTU?
[23:05] <randomaction> ari-tczew: no quorum: http://irclogs.ubuntu.com/2010/01/28/%23ubuntu-meeting.html