[00:30] <emgent> heya
[01:55] <skipper> Hi, I have created a package for pwdhash and uploaded it to REVU: http://revu.ubuntuwire.com/details.py?package=pwdhash It's now almost a month ago. No one is interesting in reviewing or have I to do something?
[01:59] <Laney> skipper: I think we just have to wait. I have one on there too :)
[02:00] <Laney> Sometimes the MOTUs have REVU days where everyone focuses on reviewing packages on there, maybe there will be one soon
[02:02] <skipper> then I will wait
[02:03] <wgrant> So now we have a proposal for -proposed-proposed. Great.
[02:08] <ScottK> wgrant: May as well get -proposed-proposed-proposed while we're at it, just to be safe.
[02:08] <ScottK> No one seems to be jumping on my "Just don't leave proposed on all the time" solution.
[02:08] <skipper> sounds a litte bit like m*cr*s*ft. they create patches for patches for patches. ;)
[02:15] <wgrant> ScottK: I leave -proposed on all the time, but that's because I can't upgrade to Intrepid like I usually do.
[02:16] <ScottK> Right, but wouldn't you agree that's not the general/supported case for it?
[02:22] <bddebian> Heya gang
[02:34] <ScottK> Heya bddebian.
[02:35] <bddebian> Hi ScottK
[02:51] <RAOF> Hey bddebian, ScottK
[02:51] <bddebian> Heya RAOF
[04:09] <fale> hello
[04:10] <fale> how can I put a package on PPA that requires cmake?
[04:13] <persia> fale: Take a look at some of the packages returned by `grep-dctrl -FBuild-Depends cmake -sPackage /var/lib/apt/lists/*hardy_universe_source_Sources` for examples using cmake
[04:14] <fale> persia: my question is: PPA can compile my package if my package to be compiled required cmake?
[04:15] <persia> fale: If the package is constructed correctly to call cmake properly, yes
[04:17] <fale> persia: :)
[04:18] <fale> persia: I'll try
[04:18] <fale> persia: I have to upload the cmake folder?
[04:18]  * TheMuso glances over the email about debian policy 3.8.0.0
[04:18] <ScottK> README.Source seems to be the one that will most commonly affect packages
[04:18] <persia> fale: I'm not sure.  The command I provided before will give examples of packages using cmake
[04:19] <fale> persia: ok, I'll check iy :)
[04:19] <TheMuso> ScottK: Yeah.
[04:19] <persia> I like the addition of "how to patch this for compilation" to README.Source
[04:20]  * ScottK prepares a macro for "Read man dpatch-edit-patch" and "Read man cdbs-edit-patch."
[04:22] <persia> heh
[04:23] <ScottK> I think it's useful for obscure systems but overkill for the common cases.
[04:24] <ajmitch> "Take this double-ROT13-encoded patch, run it through this hideous perl filter, reindent it all to apply, and then reboot"
[04:25] <persia> double-ROT13-encoding?  How does that work for punctuation?
[04:26] <ajmitch> who needs punctuation?
[04:26] <persia> Ah.  Right.  I hadn't sufficiently considered the perl filter
[04:26] <ajmitch> it's as obsolete as correct grammar these days
[04:36] <TheMuso> Nothing like policy changes to keep you on your toes.
[04:36] <ajmitch> it makes life exciting
[04:36] <ajmitch> of course I'll still trying to keep up with changes from 2+ years ago
[05:00] <moquist> if somebody could take a look at http://revu.ubuntuwire.com/details.py?package=vpnywhere I'd appreciate it.
[07:31] <theseinfeld> hi all
[07:31] <theseinfeld> is there a way to install autobuilder for Ubuntu?
[07:32] <theseinfeld> Do I follow the Debian steps or is there something more Ubuntu like?
[07:38] <RAOF> theseinfeld: Why are you asking this in #ubuntu-motu? :)
[07:39] <theseinfeld> because you are the masterst of the universe :)
[07:39] <theseinfeld> ?
[07:40] <RAOF> I don't know what autobuilder is, but this doesn't sound like a question about the development of Ubuntu; you may have more luck in #ubuntu or #ubuntu+1 (if you're using Intrepid)
[07:41] <theseinfeld> well, it is about building packages, but not on ppa/revu
[07:41] <theseinfeld> :D
[07:41] <theseinfeld> I will try with #ubuntu channel. Thanks
[07:42] <dholbach> good morning
[07:42] <Hobbsee_> morning!
[07:42] <theseinfeld> morning
[07:42] <RAOF> 'lo, dholbach.
[07:43] <Hobbsee_> theseinfeld: you likely do follow debian's instructions, but this is really not a support channel.
[07:43] <dholbach> hi RAOF, hobbsee, theseinfeld :)
[07:43] <theseinfeld> thanks Hobbsee
[07:43] <theseinfeld> then, anybody up for the http://revu.tauware.de/details.py?package=libdc1394-22
[07:43] <theseinfeld> It has been there since February?
[07:43] <theseinfeld> :D
[07:47] <theseinfeld> even lool is active this morning :)
[09:10] <huats> morning everyone
[09:46] <Laney> Howdy all
[09:46] <Laney> Anyone got a merge free for the taking?
[09:47] <Laney> \sh: Mind if I do paprefs?
[09:47] <persia> Laney: Not Debian merges, but there's heaps of upstream merges outstanding, if you like.
[09:47] <persia> Take a look at http://qa.ubuntuwire.com/uehs
[09:48] <persia> Err http://qa.ubuntuwire.com/uehs/no_updated.html
[09:53] <Laney> persia: I've not done one of these before, do I have to ping anyone beforehand?
[09:54] <persia> Laney: It's about the same as a merge.  You don't have to do anything, but people get annoyed when you don't collaborate.  Best to check with the last uploader, and specific maintainer, and look for bugs on LP.
[09:54] <persia> s/and spe/or spe/
[09:56] <persia> The key difference between a upstream merge and a debian merge is that the thing to attach to your bug is the new diff.gz, rather than the debdiff against Debian.
[10:11] <sistpoty|work> hi folks
[11:05] <DktrKranz> pitti, doko: regarding bug 237083, is there any available test case to check if proposed update is good?
[11:05] <DktrKranz> mh... wrong chan...
[11:11] <doko> DktrKranz: just one? glassfish should be checked with the new build to test the keystore problems, netbeans started to see the fontconfig problem. you can check in intrepid as well. same package
[11:38] <ruiboon> hi. is there any macro that automatically fills in the build-depends field in debian/control ?
[11:42] <persia> ruiboon: No, and you wouldn't want one, as sometimes you want to compile with, or not compile with some library supported by the application.
[11:42] <ruiboon> persia: thanks. i guess i have to fill it in myself
[11:44] <persia> ruiboon: Typically the README or INSTALL file in the source ought tell you which libraries you need, which ought get you 80% of the way there.
[11:47] <ruiboon> persia: ah.. that helps. thanks
[13:54] <norsetto> heya
[13:54] <sebner> huhu norsetto
[13:54] <norsetto> huhu sebner
[13:56] <lukehasnoname> good morning all
[13:56] <norsetto> morning lukehasnoname
[13:57] <sistpoty|work> hi norsetto
[13:57] <norsetto> sistpoty|work: heya master
[14:01] <huats> norsetto:  hello my friend
[14:01] <norsetto> huats: THE huats!
[14:02] <huats> norsetto: THE norsetto
[14:02] <huats> ;)
[14:11] <effie_jayx> dholbach, i was working on the package. I must change conflict/replace to make sure all packages get updated
[14:12] <dholbach> effie_jayx: that sounds about right
[14:17] <effie_jayx> I initially thought of libbakery-common but all three packages have to replace ubuntu old ubuntu versions
[14:18] <superm1> where's that nifty webpage i saw posted here at some point that lists SRU's and all of their statuses?
[14:18] <dholbach> effie_jayx: really?
[14:19] <effie_jayx> Since all previous versions in debian replace 2.3, i was just wondering
[14:21] <dholbach> effie_jayx: http://www.debian.org/doc/debian-policy/ch-relationships.html - you need conflicts/replaces if files move from one package to another
[14:21] <dholbach> effie_jayx: I thought it was only libbakery2.4-common and libbakery-common that had files moving around
[14:22] <effie_jayx> Doesn't the package leave the old 0ubuntu1 around?
[14:23] <dholbach> effie_jayx: if you add a conflicts, it should get removed in the upgrade process
[14:25] <effie_jayx> Ok. I'll try it and see
[14:30] <wgrant> superm1: Try http://qa.ubuntuwire.com/sru/. The ubuntu-archive one is linked from there, if that's what you want.
[14:31] <superm1> yes that's exactly what i was looking for
[14:31] <superm1> thanks wgrant
[14:31] <wgrant> np
[14:34] <Neurostu> can someone shed some light on what:
[14:34] <Neurostu> dpkg-genchanges: error: badly formed line in files list file, line 1
[14:34] <Neurostu> dpkg-buildpackage: failure: dpkg-genchanges gave error exit status 9
[14:34] <Neurostu> means
[14:42] <cyberix> Tool called linda does not exist in 8.04?
[14:43] <lucas> cyberix: it was removed from debian. use lintian.
[14:43] <cyberix> k
[15:02] <Neurostu> anybody?
[15:04] <slytherin> Neurostu: what are you trying to do exactly?
[15:05] <Neurostu> trying to figure out what the error msgs I'm getting mean
[15:06] <Neurostu> I posted them here about 40 minutes ago
[15:06] <cyberix> I did not have to use -f in order to update my package at REVU. I wonder, if I broke up something
[15:07] <Neurostu> slytherin: here is a pastebin of the errors: http://mwl.pastebin.com/m11739416
[15:08] <amikrop> Can I rename my package (it is uploaded but not examined) from ueagle-setup to ueagle?
[15:08] <slytherin> cyberix: did you change version?
[15:09] <amikrop> I thought it would be OK ro rename it to ueagle, because there is no other Ubuntu package with "ueagle" in its name, so it could not be confused.
[15:09] <slytherin> Neurostu: I saw the error message, but tell me what are you trying to do? Make a package?
[15:09] <cyberix> slytherin: yes
[15:09] <amikrop> Also, there is not much point in appending "-setup" to a package, because what all packages do, is setting up.
[15:10] <slytherin> cyberix: why? you are not supposed to.
[15:10] <amikrop> When I say uploaded, I mean uploaded to REVU.
[15:10] <cyberix> slytherin: New upstream release
[15:10] <amikrop> So? Could there be a problem?
[15:10] <slytherin> amikrop: You can sure change package name. That way it will have another entry in revu. Make sure you comment on old entry asking to discard it.
[15:11] <slytherin> cyberix: Are you trying to get review on new package or just new version of existing package?
[15:11] <amikrop> slytherin: alright ^^
[15:14] <Neurostu> slythering: yes, that is the output when I run dpkg-buildpackage
[15:14] <Neurostu> I'm trying to build a .deb
[15:15] <cyberix> slytherin: a new package
[15:16] <cyberix> slytherin: Review brought up a bug which was then fixed upstream
[15:16] <slytherin> cyberix: Then it is fine. Shouldn't be a problem.
[15:19] <cyberix> slytherin: Ok. Great.
[16:49] <bddebian> Heya gang
[16:50] <schmiedc> hoi
[16:50] <geser> Hi bddebian
[16:51] <bddebian> Hello schmiedc, geser
[16:51] <sistpoty|work> hi bddebian
[16:52] <bddebian> Heya sistpoty|work
[17:06] <dholbach> YokoZar: do you think you could follow up on the wine post on planet ubuntu?
[17:06] <YokoZar> dholbach: For some reason the posts I make don't seem to get syndicated to planet ubuntu
[17:08] <YokoZar> dholbach: Anyway I'm not sure what you want me to do, the patch Brandon links to is likely to cause regressions
[17:09] <dholbach> YokoZar: and it doesn't look like a good advice to most wine users :-/
[17:10] <YokoZar> Well, it makes his program work, and I think it's pretty clear from the post that this shouldn't be done unless you're running it and it bothers you enough
[17:12] <dholbach> also a PPA might work better than the sudo apt-get remove --purge wine; sudo make uninstall; sudo make install business
[17:13] <YokoZar> or just forking package and building locally
[17:14] <dholbach> oh well - I just thought you might be in the best position to answer this
[17:14] <dholbach> and definitely weird your blog does not turn up on planet ubuntu
[17:14] <dholbach> it looks like it's fine in the config
[17:15] <dholbach> I call it a day - see you tomorrow
[17:45]  * sistpoty|work heads home... cya
[18:27] <Neurobuntu> When I run: debuild my package compiles and build successfully into a deb, however it says that my file debian/files has a badly formed line... this is weird because I didn't create this file, what is supposed to be in this file
[18:28] <Neurobuntu> does debuild try to put the .deb into the repository pocket?
[18:29] <persia> Neurobuntu: debian/files contains a list of files to go in the deb.  You shouldn't have created it.  debuild doesn't care about pockets.
[18:30] <Neurobuntu> persia: if debuild is creating the file for me why is it giving me the badly formed line error
[18:31] <persia> Neurobuntu: I'm not sure.  It's something odd happening as a result of your debian/rules call.  You might try looking at the file, and compariing with the same file from another package that doesn't have that error.
[18:33] <Neurobuntu> persia, ok thanks
[18:35] <Neurobuntu> persia, is the files list necessary, i mean will a deb install correctly without it?
[18:35] <Neurobuntu> or if it isn't correct
[18:36] <persia> Neurobuntu: Check your created .deb with dpkg --contents.  I suspect it's missing something.
[18:42] <Iulian> Hi
[18:44] <Neurobuntu> persia: I don't think so, it looks like everything is in there
[18:45] <persia> Neurobuntu: Hmm.  I don't know.  You might ask someone to review the package in detail, but it might just work.
[18:47] <Neurobuntu> ok well I'll figure this out eventually, ty
[20:21] <SniperBeamer> hi, is it possible to tell cdbs not to create usr/share/doc/... but instead link to a common doc dir?
[20:22] <persia> SniperBeamer: It does that by default.
[20:22] <persia> In /usr/share/doc/...
[20:22] <persia> Just put the same files in all the subpackages.
[20:22] <persia> (or maybe I'm mistaken, but I think that's right - someone please correct me otherwise)
[20:23] <RoAkSoAx> hi guys, does anyone knows why i get this warnings when trying to create a new pbuilder ? The following packages have unmet dependencies:
[20:23] <RoAkSoAx>   aptitude: Depends: libapt-pkg-libc6.7-6-4.6 but it is not installable
[20:23] <RoAkSoAx>   libept0: Depends: libapt-pkg-libc6.7-6-4.6 but it is not installable
[20:23] <RoAkSoAx> and how can i fix it?
[20:23] <geser> RoAkSoAx: interpid?
[20:23] <RoAkSoAx> geser, yep
[20:24] <geser> looks like aptitude and libept0 need a rebuild with the recent apt
[20:25] <SniperBeamer> persia: it only symlinks files (except copyright)
[20:25] <RoAkSoAx> geser, how to do that ;)
[20:26] <geser> RoAkSoAx: you would need a interpid pbuilder for that
[20:26] <SniperBeamer> and lintian complains with debian-changelog-file-is-a-symlink
[20:26] <Pennycook_> Hi guys, I was directed over here by #kubuntu.  I have a question about using prevu; I've updated to Qt4.4 using backports and need to backport Intrepid's version of lyx.  Given lyx exists in Intrepid, is running "prevu lyx" enough, or do I need to provide a URL, maybe something else?
[20:26] <RoAkSoAx> geser, so should i create a hardy pbuilder and upgrade too intrepid??
[20:27] <RoAkSoAx> geser, libapt-pkg-libc is a package right?? cause i can't find it in the repos
[20:28] <persia> SniperBeamer: You can ignore the lintian error, and symlinks don't take that much space.
[20:28] <geser> RoAkSoAx: yes, that would too
[20:28] <geser> RoAkSoAx: libapt-pkg-libc is provided by apt
[20:29] <RoAkSoAx> geser, ok thanks, so i'll create a hardy pbuilder and upgrade it too intrepid
[20:29] <SniperBeamer> persia: sure, I just think symlinking the whole dir is a cleaner solution
[20:29] <persia> SniperBeamer: Maybe.  Investigate dh_link.
[20:30] <SniperBeamer> dh_link says that the usr/share/doc/... dir already exists
[20:31] <SniperBeamer> I didn't find an option that stops cdbs from calling dh_installdocs
[20:31] <Jazzva> Just to make sure... Changes to .po files should be removed from the final debdiff in a merge?
[20:33] <geser> Jazzva: yes, unless they were made on purpose which should be documented in the changelog
[20:34] <persia> Jazzva: Typically.  Check the Ubuntu changelog.  Except in rare cases, we prefer Debian .po files.  In those rare cases, you need to merge manually, but should be sure to push the change to Debian.
[20:34] <Jazzva> persia, geser: Thanks.
[20:34] <Jazzva> persia: What would be those rare cases?
[20:35] <persia> Jazzva: When there was an error of some sort that was fixed.  Maybe a typo, etc.
[20:35] <Jazzva> persia: I see... thanks :)
[21:02] <emgent> Security Meeting now on #ubuntu-meeting
[21:06] <whyking_> hi
[21:06] <whyking_> is this the right place for me to ask about an ubunut-package provided by MOTU (namely scipy) ?
[21:07] <RoAkSoAx> geser, any ideas why i get this?? http://pastebin.ubuntu.com/17309/
[21:08] <persia> whyking_: You can ask, although we may not know.  If it's about a bug, you may have better luck in #ubuntu-bugs.  If it's about support, you may have better luck in #ubuntu.
[21:09] <geser> RoAkSoAx: that's kind of "normal", yes, it's a bug
[21:09] <geser> RoAkSoAx: check if you have already upgraded libc6 and coreutils before proceeding
[21:10] <whyking_> I was wondering, there are some special functions in scipy.sandbox, those are present in the scipy-0.6 source tarball, but not in the i386 compiled version.. why would that be the case? and, any plans on changing that?
[21:10]  * persia points at http://women.debian.org/wiki/English/MaintainerScripts as a source of information about debugging maintainer script issues
[21:10] <geser> RoAkSoAx: s/coreutils/findutils/
[21:11] <geser> RoAkSoAx: bug #234345
[21:11] <RoAkSoAx> let's see
[21:14] <RoAkSoAx> i don't have those packages in the update-manager for upgrade.. but i'll upgrade my system and i'll tr again
[21:14] <RoAkSoAx> thanks geser ;)
[21:46] <norsetto> whyking_: could very well be a packaging bug, would you mind issuing a bug report about it in Launchpad?
[22:04] <norsetto> whyking_: well, seems like upstream has disabled the building of sandbox modules
[22:04] <whyking_> norsetto, what do you mean with upstream?
[22:05] <whyking_> norsetto, it is also not present in the debian package
[22:05] <whyking_> norsetto, is that what oyu mean?
[22:05] <sebner> whyking_: upstream is the programmer
[22:06] <whyking_> hm.. I do not think so.. it is present when I build the from the source
[22:08] <norsetto> whyking_: well, all subpackages are commented out in setup.py
[22:09] <whyking_> norsetto, oh, you are right
[22:09] <whyking_> unfortunate
[22:10] <sebner> norsetto is the rainman =)
[22:12] <whyking_> norsetto, well, thanks for looking into that
[22:12] <norsetto> whyking_: np
[22:14] <schmiedc> cya
[22:14] <norsetto> sebner: how far are you from the lake?
[22:16] <sebner> norsetto: the lake (which one) or a lake?
[22:16] <norsetto> sebner: isn't there a lake in your village?
[22:16] <sebner> norsetto: ~5-10km away
[22:17] <RoAkSoAx> sebner, you gonna take a bath in the lake?? :P xD
[22:17] <sebner> RoAkSoAx: noooo!?
[22:17] <wasabi> Packaging question: I have a command I want a daemon to run after the daemon is upgraded, to restart the daemon. but it also has to run AFTER some packages which depend on the daemon: and are thus after the daemon
[22:17] <wasabi> Basically the daemon has plugins.
[22:17] <RoAkSoAx> sebner, lol i was just joking :P
[22:18] <wasabi> After any plugins are updated, the daemon should restart. Should I implement this in each plugin's postinst?
[22:18] <sebner> RoAkSoAx: /me is too tired to discover jokes ^^
[22:18] <RAOF> wasabi: That sounds like the way to go.
[22:19] <wasabi> Hmm.
[22:19] <RAOF> wasabi: Because, looking at it another way, from the plugin package's perspective it's not properly installed until the daemon has restarted; thus, it should restart the daemon.
[22:20] <RAOF> For bonus points you could try dpkg triggers to have this happen exactly once per package-management-session, but I'm not familiar with them.
[22:49] <crimsun> hmm, so I need to revert these sysv-rc changes.  Sigh.
[22:50] <ajmitch> caused some breakage?
[22:50] <sebner> gn8 folks
[22:51] <crimsun> ajmitch: no, just the intrepid merge deprecates multiuser semantics.
[22:51] <crimsun> or at least I'm led to believe so from the changelog.
[22:52] <RAOF> And the mail on ubuntu-devel, presumably.
[22:59]  * ajmitch is still trying to catch up on -devel mail
[22:59] <ajmitch> just got to that one now :)