[00:00] <nxvl> LaserJock: yep
[00:00] <LaserJock> maix: dpkg --compare-versions is what you can use to check if a version is higher than another
[00:00] <LaserJock> maix: you'll want to read the dpkg man page for more information on it though, it's not exactly the most user friendly
[00:01] <maix> i searched there
 i thought: if they patch it the new version will be 6.1, if debian does it will be 6-2, if ubuntu does it will be 6-1ubuntu1; is that right?
 if it had a security fix I think it'd be 6-1ubuntu0.1
[00:01] <maix> -> are there other possibilities how it could be?
[00:02] <LaserJock> yes
[00:02] <maix> or would it be enough if i'd check them all :)
[00:02] <crimsun> I would tend to use 6-1ubuntu~foo
[00:02] <maix> hm that's weird ^^
[00:02] <LaserJock> it could be 6-1ubuntu1
[00:02] <LaserJock> or it could be 6-1ubuntu0.8.04.1
[00:02] <wgrant> crimsun: ubuntu1~patched1 shouldn't sort before ubuntu0.1, should it? That looks very wrong.
[00:03] <maix> LaserJock, 6-1ubuntu1 is in my list :)
[00:04] <LaserJock> generally the lowest you'd see would be 6-1ubuntu0.1
[00:04] <crimsun> wgrant: it doesn't, typo
[00:04] <LaserJock> unless you use something like what crimsun said
[00:04] <wgrant> crimsun: Phew.
[00:04] <maix> and 1ubuntu0.8.... would be higher than 1ubuntu0patched, wouldn't it?
[00:04] <wgrant> maix: Yep.
[00:05] <LaserJock> on the other hand
[00:05] <LaserJock> you could look at the probability of the package getting a security or other update
[00:05] <maix> LaserJock, that dpkg --compare-versions only works with whole packages not if i specify the versions just as parameter?
[00:05] <LaserJock> and decide to not worry about it
[00:06] <LaserJock> maix: not, you just put version strings
[00:06] <LaserJock> *no
[00:06] <maix> LaserJock, i think the possibility is not very high  :)
[00:06] <LaserJock> like dpkg --compare-versions 0.6-1 gt 0.6-2
[00:06] <jdong> maix: dpkg --compare-versions '1.2.3' '<' '1.2.4' && echo TRUE
[00:06] <maix> argh cause i got bash: 6-1ubuntu0.8.04.1: No such file or directory
[00:07] <maix> but that's because of the unescaped < :)
[00:07] <LaserJock> oh, I don't use <
[00:09] <maix> yes, i use lt now ;)
[00:11] <maix> ok,  6-1ubuntu0patched1 is lower than all the possibilities it could be :)
[00:12] <maix> crimsun, and 6-1ubuntu~patched to
[00:12] <maix> but the latter looks better :)
 you could look at the probability of the package getting a security or other update -> in fact yes, but i also asked because i'd like to know :)
[00:24] <LaserJock> sure
[00:25] <maix> i anyway wanted to learn about packaging and motu and that stuff :)
[00:25] <LaserJock> then you're in the right place ;-)
[00:26] <maix> and i learned that you all are very helpful (or just have too much time :P )
[00:29] <LaserJock> maix: bit of both ;-)
[00:29] <maix> *g*
[00:31] <maix> after i've read some things about packaging and am able to package one you'll hear from me on revu :)
[00:31] <maix> but at first: gn8 ^^
[00:32] <LaserJock> maix: night
[00:39] <LaserJock> does kvm work very good on non-VT procs?
[00:39] <jdong> LaserJock: no it doesn't work at all
[00:39] <jdong> kvm requires VT extensions
[00:41] <LaserJock> it says it falls back to basically qemu
[00:41] <LaserJock> in the package description anyway
[00:48] <persia> LaserJock: The fallback was removed in February.  The description may need to be updated.
[00:48] <LaserJock> k
[00:48] <LaserJock> I just installed VirtualBox anyway
[00:48] <LaserJock> not sure if it's gonna work all that well, but what the heck
[00:49] <LaserJock> I'd like to set up some virtual machines for SRU testing
[00:50] <LaserJock> I think for some of these I'm just gonna have to do the SRU myself
[00:50] <persia> VirtualBox seems to work fine, as long as you're emulating i386.
[00:52] <LaserJock> wow, I even found my dapper, feisty, and gutsy CDs
[01:07] <emgent> hello people
[03:26] <happinessturtle> hi, someone please rebuild audacious-crossfade :P
[03:29] <jdong> happinessturtle: file a SRU bug report for it please
[03:43] <persia> I thought there already was such a bug report
[04:42] <happinessturtle> jdong, i already filed a bug report and subscribed uus to it :)
[04:42] <happinessturtle> well, actually, i just hijacked one of the 30 or 40 reports filed ;)
[06:05] <LaserJock> anybody feel like working up a pretty simple SRU for kcheckgmail?
[07:21] <LaserJock> jdong: please have a look at bug #175731
[07:21] <ubotu> Launchpad bug 175731 in postfix-policyd "postfix-policyd hangs at "connecting to mysql database:"" [Undecided,New] https://launchpad.net/bugs/175731
[07:43] <CrippledCanary> could someone in motu-sru have a look at bug #221973
[07:43] <ubotu> Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,New] https://launchpad.net/bugs/221973
[08:01] <geser> CrippledCanary: I've looked at your debdiff (I'm not from motu-sru) and it looks ok but has two minor issues
[08:01] <geser> the target in debian/changelog should be "hardy-proposed" instead of "hardy"
[08:02] <geser> and the automatic bug closure in Ubuntu uses "LP: xxx" instead of "Closes: xxx"
[08:07] <CrippledCanary> ok... thanks
[08:40] <iulian> G'morning
[11:05] <guja_nebeska> Which language is gonna be more useful for future Ubuntu developer - C or Phyton?
[11:11] <persia> Well, make and shell, really.
[11:24] <AnAnt> Hello, if a package X depends on package Y, and I attempt to install X, which postinst will run first ? X's postinst or Y's ?
[11:30] <Hobbsee> AnAnt: y's, i expect
[11:31] <AnAnt> Hobbsee: thanks
[11:31] <laga> hum
[11:31] <laga> is the postinst run immediately after installation?
[11:31] <Hobbsee> i think so
[11:32] <laga> you can probably force the execution order by using the pre-depends field
[11:32] <laga> Hobbsee: if packge X depends on Y, Y is not necessarily installed before X AFAIK
[11:32] <AnAnt> laga: how's that ?
[11:32] <wgrant> Unless there is a Pre-Depends, the order cannot be guaranteed.
[11:32] <AnAnt> laga: put Y in X's Pre-Depends: field ?
[11:33] <AnAnt> I see
[11:33] <laga> AnAnt: it works like Depends:, you just say Pre-Depends:
[11:33] <AnAnt> laga: thanks
[11:33] <wgrant> Hm, actually, maybe for postinsts it is. But for preinst it definitely isn't.
[11:34] <laga> i don't know. :)
[11:53] <CrippledCanary> can someone have a look at bug #221973 again....
[11:53] <ubotu> Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,New] https://launchpad.net/bugs/221973
[11:53] <CrippledCanary> I want to sort out as much issues as possible as soon as possible
[13:35] <emgent> heya
[14:19] <PeP`> greetings
[14:20] <PeP`> I never know if I should install the suggested/recommended packages... and, most importantly; I don't know the difference between them either... can someone enlighten me?
[14:20] <PeP`> I was advised to ask in here...
[14:23] <bimberi> PeP`: http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html#s-depends
[14:24] <PeP`> thank you bimberi
[14:27] <PeP`> and if you install the recommended packages, and these recommended ones also recommend a third set of packages... I suppose installing them would benefit to the first package...
[14:32] <panda> PeP`, not necessarily
[14:35] <PeP`> ok panda, I only install the first-level recommended oned anyway...
[14:35] <PeP`> thanks
[14:52] <rc55> Hi, I'm interested in creating a package for ziproxy, am I in the right place?
[14:53] <rc55> I've tested it on hardy, and it works fine, I think other people might benefit from it
[14:55] <laga> rc55: cool
[14:55] <laga> !packaging
[14:55] <ubotu> The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[14:55] <laga> rc55: check these links ^^
[14:56] <rc55> cool, reading them now
[15:21] <bddebian> Heya gang
[16:45] <megabyte405> hey - having persistent "Chroot problem" build errors in my ppa - anybody can take a look? https://launchpad.net/~abiword-stable/+archive/+builds?build_text=&build_state=all
[16:45] <megabyte405> I know there's the issue where the first build in a new ppa will do that, but I did retry and it ddidn't work for those top two builds
[16:52] <megabyte405> nvm had to retry them twice - weird
[16:53] <jdong> /bin/sed: can't read /usr/lib/libgnutls.la: No such file or directory
[16:53] <jdong> libtool: link: `/usr/lib/libgnutls.la' is not a valid libtool archive
[16:53] <jdong> make[6]: *** [libAbiCollabXMPPUnixHandler.la] Error 1
[16:53] <jdong> some of those build errors looked legit
[17:02] <megabyte405> yeah, now I only have legit ones :D
[17:02] <megabyte405> the ppa system was being a tad finicky before, now it's ok
[17:22] <coppro> can I get help with a package I've built? I'd like someone to look it over and point out my mistakes, if you would be so kind
[17:24] <persia> coppro: Best way to get a review of a package of a new source is REVU.  I'm unsure when the next REVU day will happen, but likely in a couple weeks.  Right now, most people are either taking a break or focused on fixing critical bugs in the recent release.
[17:25] <coppro> okay
[17:25] <coppro> thanks
[18:03] <ffm> There is a package, sugar-write-activity, that cannot be installed in hardy because it depends on a nonexistent package, python-abiword. Why is it in the repos if it is unusable?
[18:14] <persia> ffm: There are actually quite a few packages like that.  Take a look at the output of `apt-cache unmet -i`.  These are bugs in need of fixing, typically, and happen when packages didn't get enough testing before release.
[18:15] <sebner> persia: can you confirm that intrepid archives open on 1th may?
[18:17] <persia> sebner: No.  I doubt anyone can.  The archives open when they can, and are typically frozen at first while the toolchain is updated.  Watch for the intrepid-changes mailing list, and wait for most of the toolchain to have been uploaded before looking to do anything.
[18:17] <persia> Personally, I'd be surprised to see much available before the 7th or 8th.
[18:18] <sebner> persia: kk. just saw the intrepid release schedule on the wiki and on the first may it's "Toolchain Uploaded". Made by Martin Pitt :)
[18:19] <persia> Ah.  That's more authoritative than my opinion then :)  Given that, I'd expect the archive to be available for general developer use on the 2nd or 3rd.
[18:20] <sebner> persia: cool. :D next question. If we still use DaD. Can I already claim some merges for me or should it open to anybody? The next few days I have stress at school but on the weekend I would be happy to start mergin *if* the archves are open
[18:22] <persia> I'm not sure of the current status of the MoM/DaD integration effort.  If DaD is up and running, you ought be able to use it.  As with either tool for any release, be sure to also check Debian to avoid merging something that will be obsolete in the next few hours.
[18:23] <ffm> persia, So, what's the solution? Remove the package or add the dependency package?
[18:23] <sebner> persia: yeah that's clear. just wast want to be sure that no one complains if I already claim merges for myself. (>10) ^^
[18:23] <sebner> ignore "wast" xD
[18:24] <ffm> persia, I don't really know if it needs that package to function, the PPA version of it (pre-hardy) installs fine without it.
[18:25] <persia> ffm: If you can find a way to make it work without affecting other packages, it would be a candidate for a stable release update.  If Abiword needs to be updated, this is less likely.
[18:26] <ffm> persia, What's the magic forumula from going from a "apt-get source" to a binary deb for my testing? (I've only worked with RPM building in the past)
[18:26] <persia> sebner: Best to start with the merges that are the result of your last work, rather than other merges.  If you are just keeping up to date with Debian, people are unlikely to complain.
[18:27] <persia> sebner: Also, during the initial merge is a good time to check to see if the merge patch would fix a bug in Debian, and be sure the appropriate Debian bug is filed.
[18:27] <persia> ffm: There are two popular ones.  sbuild and pbuilder.
[18:27] <persia> !sbuild
[18:27] <ubotu> sbuild is a system to easily build packages in a clean schroot environment.  To get started with SBuild, see https://help.ubuntu.com/community/SbuildLVMHowto
[18:27] <persia> !pbuilder
[18:27] <ubotu> pbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto
[18:28] <sebner> persia: Yeah. The problem is 1) I have not that many of my merges to do 2) not worth changes 3) bringing new upstream versions to ubuntu is nice :)
[18:28] <persia> sebner: You were doing lots of merges for hardy.  Did none of those packages get updated in Debian during the freezes?
[18:28] <ffm> persia, merci. Which one is better IYHO?
[18:29] <ffm> crimsun, hey!
[18:29] <persia> Also, I think you were working on the rcbugs list.  Most of those are likely syncs now, and should be reported as such (but need investigation).
[18:29] <sebner> persia: I said "not" many. Only 7-8 I think. And not all of them are worth a merge.
[18:29] <persia> ffm: I like sbuild, but I also like there being competition between two tools, as I believe it gives us a better way to measure packages against policy.
[18:30] <sebner> persia: yeah. of course I will check if a merge is a sync now ^^
[18:30] <persia> If we all use the same tool, we are only testing compliance with a given implementation.
[18:30] <ffm> persia, Hm.. I don't have LVM set up... (i've been meaning to, but I don't want to have to recopy all my data...)
[18:30] <persia> sebner: Ah, right, Debian is in a release freeze now, so there might not be so many merges for intrepid as we had for hardy.
[18:31] <persia> ffm: I just resized a partition to free up 20GB.  You don't have to use LVM for your entire disk.  Also, it is possible to use sbuild and schroot without VLM-snapshots, but you'll have to fiddle a bit more, and it's slower.
[18:31] <sebner> persia: well. DaD shows me a lot of new upstream versions. Just not "my" pakages. That's the reason why I asked you ^^
[18:31] <geser> sebner: you can take one of mine open merges if you need work, but tell me which ones, so I know I don't need to work on them
[18:32] <sebner> geser: I'll check that on weekend. thx.
[18:34] <sebner> geser: buh. around. 60 if I counted correctly. Great. But I'll mainly take new upstream versions. Will let you know which ones. Thanks again :D
[18:34] <slangasek> persia: Debian only just entered release freeze, so there's going to be at least one round of merges...
[18:35] <sebner> slangasek: can you give me a timeframe?
[18:35] <slangasek> timeframe for what?
[18:35] <persia> slangasek: Oh, I'm sure there will be merges, but I seem to remember the first soft freeze starting in March or so, and don't expect Maintainers to be rushing to build the volume of updated merges we saw right before FeatureFreeze for hardy.
[18:36] <sebner> slangasek: the merge round
[18:36] <persia> (as an added bonus, the rcbugs list for intrepid ought be more syncs and less merges)
[18:36] <slangasek> sebner: not before the archive opens for intrepid, and then as long as it takes? :)
[18:36] <sebner> persia: syncs are also fun. doesn't matter :)
[18:36] <sebner> slangasek: ^^
[18:36] <slangasek> (well, until the cutoff date, which should be in the IntrepidReleaseSchedule)
[18:36] <sebner> kk
[18:37] <sebner> persia: ah still a question left
[18:37] <slangasek> persia: I didn't notice any real impact from the soft freeze on the rate of package changes in Debian
[18:37] <sebner> persia: I have a lot of -0ubuntu1 packages. Should they stay in this state or do we want merges and syncs from debian in generel? I know that there are expections of course. but in generel ...
[18:38] <persia> sebner: Between Archive Open and Debian Import Freeze, we want to get as close as possible to Debian for every package also in Debian.
[18:38] <sebner> persia: great. good to know
[18:38] <Kopfgeldjaeger> hi
[18:39] <sebner> persia: btw. I don't want to annoy you ^^. Any progress for the new "hackers" team?
[18:39] <Kopfgeldjaeger> what should i do if an application does not have an icon but needs a desktop file?
[18:39] <ffm> Is the devel schedule up yet for ibex?
[18:39] <persia> Between Debian Import Freeze and Feature Freeze, it's a good idea to track Debian, and if a package can be synchronised, this is always good.
[18:39] <ffm> Kopfgeldjaeger, Make an icon.
[18:39] <persia> After FeatureFreeze, it's mostly about backported bugfixes.
[18:39] <ffm> Kopfgeldjaeger, It's bad form for it to have a .desktop with a generic icon.
[18:39] <persia> sebner: See the minutes for the last MOTU Meeting (when they come out).
[18:40] <sebner> persia: I attended the meeting ;)
[18:40] <persia> sebner: Then you saw the determination :)
[18:41] <sebner> persia: yeah. we decided the name. But when will the group be renamend and "open"
[18:41] <persia> sebner: LIkely Wednesday, if not sooner.
[18:41] <sebner> persia: great. Sounds stupid but I want to start my new development round with a @ubuntu.com mail adress ;)
[18:43] <geser> ffm: https://wiki.ubuntu.com/IntrepidReleaseSchedule
[18:45] <sebner> effie_jayx: heya. you are pretty often on the planet. good work :)
[18:46] <effie_jayx> sebner,  try to... community work / reportin / a bit of packaging... ;)
[18:46] <CrippledCanary> if we are supposed to fix SRU-worty bugs perhaps someone looks at bug #221973 soon :)
[18:46] <ubotu> Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,New] https://launchpad.net/bugs/221973
[18:46] <sebner> persia: you are member of the MC right?
[18:47] <jdong> persia is everything. at the same time :)
[18:47] <sebner> geser: uhuhuh. I'll take scite. I just it very often in past :)
[18:47] <sebner> jdong: hehe
[18:48] <sebner> persia: you have to shout with your MOTUs. Look on DaD who is the last uploader of "rosegarden" ;)
[18:49] <persia> sebner: Heh.  If you're up for it, track down the uploader by looking at the key that signed the message to hardy-changes, and complain :)
[18:50] <sebner> persia: ^^. You won't?
[18:51] <persia> sebner: I'm not likely to have the time soon :(
[18:51] <sebner> persia: No problem. I look for the villain and you complain. You have a lot of authority ^^
[18:52] <persia> sebner: For that sort of thing, no more than you.
[18:53] <sebner> persia: but people know you and have respect and will be afraid to do it once more :)
[18:55] <Kopfgeldjaeger> ffm: ok. gimped a gtk cube with a green check
[18:56] <ffm> Kopfgeldjaeger, What package is it anyway?
[18:56] <Kopfgeldjaeger> gtkhash, utility to compute hashes
[18:57] <ffm> Kopfgeldjaeger, Cool.
[19:11] <Kopfgeldjaeger> what would be the best way to include an icon+desktop file into a package with cdbs?
[19:13] <nixternal> there are a few ways actually, check out the docs in /usr/share/doc/cdbs/
[19:14] <persia> Kopfgeldjaeger: Put them in debian/ and install them with the package.install file.  Call dh_desktop and dh_icons in debian/rules.
[19:14] <nixternal> if the icon/desktop file isn't included with the application, what I generally do is add the icon and the desktop file in debian/ and install from there
[19:14] <nixternal> with a foo.install file
[19:15] <nixternal> damn you persia! let me answer a question :p
[19:15]  * persia stops answering questions
[19:15] <Kopfgeldjaeger> ok. they're already in debian :) i also just found that with dh_desktop, it's called with gnome.mk.
[19:15]  * nixternal goes back to the lug meeting
[19:15] <nixternal> haha, you can answer questions again :)
[19:23] <Kopfgeldjaeger> hmpf. dh_desktop and dh_icons are called (added gnome.mk to rules), but the desktop file and the icon arent included :/
[19:29] <awmcclain> If I'm packaging a daemon, what's the best way to test my install? I can test the basics within a pbuilder environment, but getting a daemon to run is quite difficult. Any thoughts?
[19:33] <RainCT> Kopfgeldjaeger: you have to install them with dh_install
[19:33] <RainCT> Kopfgeldjaeger: .desktop files into usr/share/applications and icons into usr/share/pixmaps
[19:34] <Kopfgeldjaeger> oh key... how should i call dh_install? just add the lines in debian/rules? a link would help
[19:35] <RainCT> Kopfgeldjaeger: is there a debian/install (or debian/<packagename>.install) file?
[19:35] <Kopfgeldjaeger> nope.
[19:36] <RainCT> Kopfgeldjaeger: well, then create one. does the package produce only one binary package or more?
[19:36] <Kopfgeldjaeger> only one
[19:37] <RainCT> Kopfgeldjaeger: then you can call the file just debian/install (without the package name prefixed), and list the file to install and the destination each on one line
[19:37] <RainCT> Kopfgeldjaeger: like:   debian/gtkhash.desktop usr/share/applications
[19:37] <Kopfgeldjaeger> thanks. thats really clear.
[19:38] <RainCT> np :)
[20:37] <Kopfgeldjaeger> haaar.... uploading package the 20th time to ppa (stupid errors... like no source, intrepid not there yet, uploaded also .deb) -.-'
[20:41] <Kopfgeldjaeger> ok. how can i build the source package (source only, .orig included)?
[20:41] <RainCT> Kopfgeldjaeger: debuild -S -sa
[20:41] <RainCT> Kopfgeldjaeger: (-sa is to include the .orig.tar.gz)
[20:42] <Kopfgeldjaeger> thanks. already tried -S and -sa. but not together. whoa!
[20:42] <RainCT> heh
[21:02] <Kopfgeldjaeger> maan :/ ppa says md5sums dont match, but they do...
[21:34] <ffm> Can someone confirm bug #219358 for me?
[21:34] <ubotu> Launchpad bug 219358 in sugar-write-activity "Package has unresolved dependancies" [Undecided,New] https://launchpad.net/bugs/219358
[21:37] <Lamego> yes
[21:37] <Lamego> ffm, Depends: python-abiword (>= 0.6) but it is not installable
[21:38] <ffm> Lamego, Thank you.
[21:38] <zorglu_> q. i got a .deb installable on ubuntu, but it is closed-source. is there a way to be included in ubuntu universe/multiverse ?
[21:38] <ffm> Lamego, Would you care to mark the bug such?
[21:40] <Lamego> done
[21:44] <pwnguin> zorglu_: well... we have progress quest, because idiots love idiotic things
[21:45] <zorglu_> pwnguin: ?
[21:45] <pwnguin> its a windows binary
[21:45] <pwnguin> in ubuntu
[21:46] <coppro> oh, thanks for remining me to start playing
[21:46]  * pwnguin stabs
[21:46] <zorglu_> pwnguin: i dont understand what you mean
[21:46] <coppro> I think he's saying yes
[21:47] <zorglu_> coppro: ok thanks :)
[21:47] <pwnguin> zorglu_: if ubuntu is allowed to redistribute the binaries, and it's not terrible, it could be considered
[21:47] <pwnguin> but expect opposition
[21:48] <zorglu_> pwnguin: how opera and co did it ?
[21:48] <pwnguin> opera's in canonical's commercial repo
[21:48] <pwnguin> i dont know if they build the package by hand or if they have access to the source, but either way it's not in uni/multiverse
[21:49] <zorglu_> pwnguin: ok what kind of opposition is there to go in uni/multiverse ?
[21:49] <pwnguin> what sort of opposition? people who don't like closed source and dealing with closed source bugs
[21:49] <zorglu_> pwnguin: the .deb is already working and comply to usual rules of .deb
[21:50] <pwnguin> is there a source package?
[21:50] <zorglu_> pwnguin: i could build one but i cant publish the source, no
[21:51] <pwnguin> zorglu_: take a look at the pq source package
[21:51] <zorglu_> pq= ?
[21:51] <pwnguin> progress quest
[21:51] <coppro> it's in the package 'pq'
[21:51] <zorglu_> ok looking
[21:51] <pwnguin> a stupid parody of PC RPG games
[21:52] <coppro> pwnguin, can you look over a package I made and give me pointers, if it's not too much of an issue?
[21:52]  * pwnguin isn't worth a damn at reviews yet
[21:53] <coppro> it's my first ever package - I'm sure you can find something wrong
[21:53] <pwnguin> im not so sure about that
[21:53] <pwnguin> what's lintian say about it
[21:53] <pwnguin> ?
[21:54] <zorglu_> about packaging, is there a way to make a 32bit package being easily installable on a 64bit ?
[21:54] <coppro> running it
[21:54] <zorglu_> like autojailling or somethign
[21:55] <coppro> it says tons since I upgraded to gutsy, apparently
[21:55] <coppro> *hardy
[21:56] <pwnguin> well fix those ;)
[21:57] <coppro> how do I tell it that a file in the source package shouldn't exist in the distribution
[21:58] <coppro> lintian complains about them
[21:58] <crimsun> ffm: hi
[21:58] <miguillo> is revu server working correctly? i uploaded a package and it doesn't show up in the new packages list
[21:59] <coppro> then I get a 'dpkg-source: warning: ignoring deletion of file Patterns/Rakes/.DS_Store'
[21:59] <ffm> crimsun, so, for packages with broken dependancies, we'll just remove the package from universe, right?
[21:59] <crimsun> ffm: not for hardy, no.
[21:59] <ffm> crimsun, not even 8.04.1?
[22:00] <crimsun> ffm: no.
[22:00] <ffm> crimsun, if we can fix the package so it doesn't require that dependency, does that qualify for a SRU?
[22:01] <crimsun> ffm: yes
[22:01] <Kopfgeldjaeger> could someone have a quick look at (there arent many changes to look at) my package for gtkhash? builds fine with hardy-ppa. i would like to see it in intrepid
[22:01] <Kopfgeldjaeger> http://nicolaispohrer.dyndns.org/packaging/
[22:04] <coppro> where can I find a guide to lintian errors?
[22:16] <coppro> why am I getting an unkown-section universe error?
[22:16] <crimsun> don't hardcode universe into debian/control:section
[22:16] <crimsun> the archive-side overrides take care of that.
[22:16] <coppro> oh
[22:16] <coppro> so what do I put there?
[22:17] <crimsun> whatever's appropriate.  Just omit universe.
[22:17] <coppro> ok
[22:17] <crimsun> (http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections)
[22:19] <Kopfgeldjaeger> n8
[22:22] <RainCT> miguillo: have you joined the ubuntu-universe-contributors team in Launchpad? (and if so, how much time ago?)
[22:22] <RainCT> Kopfgeldjaeger: please upload to REVU if you want reviews
[22:23] <miguillo> RainCT: something like 10hours ago
[22:23] <RainCT> miguillo: Your key won't be on REVU yet, then. I'll start a sync now.
[22:23] <miguillo> RainCT: thanks
[22:25] <RainCT> miguillo: ok, you should be able to upload now
[22:26] <miguillo> RainCT: my upload was accepted, do i need to do it again?
[22:26] <RainCT> miguillo: yes
[22:30] <panda> A blueprint is a possible future package ?
[22:30] <crimsun> it possibly involves packages
[22:31] <panda> thanks
[22:36] <crimsun> RAOF_: would I be incorrect in presuming that hardy lacks a gnome-do-plugin-foo for banshee?
[22:37] <crimsun> (I know it was committed some time ago, but I only recently began to look at Do)
[22:40] <miguillo> RainCT: uploaded again, and it is not showing in new list
[22:40] <soto> What is the other build system similar to pbuilder?
[22:42] <jdong> sbuild?
[22:42] <soto> jdong: No, I don't think that was it. I think it was Ubuntu specific.
[22:43] <jdong> soto: what is it used for?
[22:43] <soto> jdong: Building packages in a chroot.
[22:43] <jdong> pbuilder's really the only one. There's pbuilder-dist and prevu which are frontends to builder
[22:43] <jdong> and sbuild which is more similar to what the build servers use
[22:43] <soto> jdong: prevu.
[22:43] <jdong> ah :)
[22:43] <soto> jdong: Thanks
[22:44] <jdong> prevu is a frontend for pbuilder that makes the process of building backports simpler
[22:44]  * jdong is the author :)
[22:44] <soto> Well thanks for writing it.
[22:44] <RainCT> miguillo: what package is it? tomcat6_6.0.16-0ubuntu1_source.changes?
[22:44] <jdong> sure thing :)
[22:45] <miguillo> RainCT: it's ok now, after reload, thanks
[22:47] <soto> jdong: prevu will automatically 'install' a package in the jail so that a lter package I'm building will be able to find it right?
[23:07] <coppro> how do I use dh_installman
[23:08] <coppro> correctly, of course
[23:10] <RainCT> coppro: listing the manpages in a debian/manpages file, for example
[23:10] <jdong> soto: if you run a prevu-update after the build of the previous package, yes.
[23:10] <RainCT> coppro: (and then calling dh_installman in debian/rules)
[23:11] <RainCT> good night
[23:12] <coppro> okay, what's the syntax for manpages?
[23:12] <coppro> I need to install one file for two binaries
[23:16] <coppro> okay, why is my package no longer creating orig.gz and diff.gz files?
[23:19] <RainCT> coppro: https://wiki.ubuntu.com/PackagingGuide/Howtos/PODManpage, for example
[23:26] <coppro> that helps my man issue I think
[23:27] <coppro> not my {diff,orig}.gz problem
[23:30] <coppro> how do I figure out where dkpg-buildpackage thinks my original source archive is?
[23:35] <RainCT> coppro: what's the name of the uncompressed directory?
[23:36] <RainCT> coppro: well. if it was for example "hello-world-0.1" then the original source should be located at ../hello-world_0.1.orig.tar.gz
[23:36]  * RainCT goes to bed now
[23:36] <RainCT> good night all