[17:03] <HighNo> jpatrick: hehe, gotcha! I was just wondering if the main channel for backporters would be #ubuntu-backports - if so backporters are IRC lazy :-)
[17:03] <jpatrick> HighNo: no, it's here
[17:03] <persia> No, it's #ubuntu-backports, and the backporters are IRC lazy.
[17:04] <persia> (although most of them idle here even when absent there)
[17:04] <jpatrick>  /cs info #ubuntu-backporters -> not registered
[17:04]  * persia notes that MOTU cannot upload to -backports as justification for the above remark
[17:04] <persia> jpatrick: #ubuntu-backports not #ubuntu-backporters
[17:04] <jpatrick> persia: opps
[17:05] <sistpoty|work> pochu, jdong: /me is confused about amule... is this actually a release (as the topmost changelog entry seems to indicate this)?
[17:05] <HighNo> :-) I was just trying to make sure I have someone to ask if anything will go wrong. But this time I will start by completely reading the wiki, trying hard, failing hard and then keep asking dumb questions :-)
[17:05] <pochu> sistpoty|work: no, not yet
[17:06] <pochu> sistpoty|work: it's a tarball generated from a svn snapshot
[17:06] <sistpoty|work> pochu: so this is a prerelease, and they're working towards a release? (as in have entered bug fixing mode)? Or are they planning to first add many new features?
[17:07] <pochu> sistpoty|work: I don't expect new features from now on (and from some time)
[17:07] <pochu> sistpoty|work: from this thread, you can see they were preparing the release a long time ago... http://forum.amule.org/index.php?topic=13194.0
[17:11] <DktrKranz> RainCT: did you receive any feedback about bug 187743?
[17:11] <ubotu> Launchpad bug 187743 in youtube-dl "[SRU] youtube-dl doesn't work anymore" [Medium,In progress] https://launchpad.net/bugs/187743
[17:12] <RainCT> DktrKranz: I have preparing a candidate revision on my TODO list for today :)
[17:13] <DktrKranz> \o/
[17:17] <pochu> nxvl_work, Ng: will any of you write a freeze exception request for terminator 0.8? I'd love to get it in the archive
[17:17] <pochu> Otherwise you can package it in your team's ppa :)
[17:18] <nxvl_work> pochu: yep, i have already talk yo pitti, i think it will be included
[17:18]  * DktrKranz is curious if there is a list of unapproved packages available to the masses.
[17:18] <pochu> nxvl_work: cool, keep me posted :)
[17:18] <nxvl_work> pochu: i'm just waiting for 0.8.1 (0.8 comes with some bugs) to upload it to debian and then sync it
[17:18] <pochu> nxvl_work: oh, I didn't know it was buggy
[17:19] <pochu> DktrKranz: what do you mean with unapproved?
[17:19] <persia> Otherwise we'd already have it :)  There was a definite plan for 8.0 to be pre-FF.
[17:19] <DktrKranz> pochu: packages waiting to be approved by archive-admins, such as SRUs
[17:19] <nxvl_work> pochu: some little bugs, and also en empty changelog :D
[17:20] <DktrKranz> we have NEW queue, unapproved queue for hardy, but I'm unable to find it for stable releases too.
[17:20] <persia> DktrKranz: There's the pending SRU page
[17:21] <DktrKranz> persia: that page is for approved SRU waiting for verification, I mean packages uploaded to -proposed still waiting to be approved by archive-admins.
[17:21] <persia> DktrKranz: Wouldn't that be in the NEW queue for -proposed?
[17:22] <nxvl_work> pochu: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=terminator
[17:22] <DktrKranz> persia: I thought so, but I was wrong. Anyway, they aren't NEW, just "unapproved"
[17:23] <persia> DktrKranz: That's just an annoying LP bug (I forget the number) that https://launchpad.net/ubuntu/gutsy/+queue?queue_state=1&queue_text= doesn't work.
[17:23] <jeromeg> DktrKranz: speaking of SRU, I tested klavaro from gutsy-proposed, runs fine for me
[17:24] <DktrKranz> jeromeg: good. I'm in sru-verification now, so I can check if package runs fine, but feedbacks from users are welcome :)
[17:24] <DktrKranz> persia: I'll dig into soyuz bug then
[17:24] <jeromeg> DktrKranz: i just want to check one last thing and will add a comment to the bug report
[17:25] <Ng> pochu: I'm gonna do my best to get 0.8.1 out tonight. I kinda screwed up making 0.8 :/
[17:26] <jeromeg> DktrKranz: ok, everything is fine
[17:27] <DktrKranz> RainCT: did you reupload aumix to -proposed? If so, I can check if I see it listed somewhere, but I think it won't.
[17:32] <RainCT> DktrKranz: yes
[17:32] <DktrKranz> bug 152884
[17:32] <ubotu> Launchpad bug 152884 in soyuz "If you accept packages from the UNAPPROVED queue, it says they're accepted, and takes you back to the NEW queue." [Undecided,New] https://launchpad.net/bugs/152884
[17:33] <jpatrick> HighNo: best place to stalk backporters is probably here
[17:33] <RainCT> anyone here familiar with python-soya?
[17:34] <persia> RAOF: How familiar do you need?
[17:34] <jeromeg> RainCT: i had to work a bit on it during feisty -> gutsy development cycle
[17:34] <jeromeg> it's really a pian !
[17:34] <jeromeg> *pain
[17:34] <RainCT> jeromeg: Do you remember how to set the icon for a window?
[17:35] <jeromeg> RainCT: no idea :)
[17:35] <jeromeg> RainCT: and it's not really documented :)
[17:36] <andy2> Can someone point me in the right direction, I am trying to make a metapackage and I can't seem to figure out how to create the source packages.  All the docs seem to start with an upstream tarball.
[17:38] <persia> andy2: For a metapackage, just create a directory of the right name, and then populate debian/changelog, debian/control, debian/copyright, and debian/rules.  You may find it easier to use something like germinate and seeds to manage the metapackage, depending on the size and complexity.
[17:39] <andy2> It would be very simple.  But I would like to upload it to my PPA.  I can't do that unless I create a .dsc and a tar.gz, correct?
[17:39] <persia> For a traditional metapackage, there is no tar.gz, and nothing but the debian/ directory.  For a germinate-based metapackage, there is content in the package, so you could choose native or non-native as you like (there are derivatives using both models in the repositories)
[17:40] <persia> andy2: Right.  Once you have created the four files I mentioned, running `debuild -S` in the directory containing debian/ would build you the .dsc and .tar.gz
[17:43] <bddebian> Heya gang
[17:43] <andy2> I guess it's my debian/rules that is giving me a problem.
[17:46] <persia> andy2: For a traditional meta-package arrangement, take a look at the meta-gnome2 package.  For a germinate-based meta-package arrangement, ubuntu-meta is the best model.
[17:49] <RainCT> jeromeg: I agree with you :P
[17:49] <jeromeg> RainCT: :)
[17:49] <jeromeg> got to go
[17:49] <jeromeg> bye
[17:49] <andy2> persia:  Thanks, that's very helpful!
[17:49] <RainCT> cya
[17:50] <persia> andy2: That's the point of free software: use the best out there.  Note that you'll need to follow the licensing for those packages if you base yours from them.
[17:53] <andy2> persia | andy2: For a metapackage, just create a directory of the right name, and then     . _MMA_
[17:53] <andy2>                           populate debian/changelog, debian/control, debian/copyright, and debian/rules.    . _ruben
[17:53] <andy2>                           You may find it easier to use something like germinate and seeds to manage the    . _stink_
[17:53] <andy2>                           metapackage, depending on the size and complexity.                                . a7p
[17:53] <andy2> [12:39:59]        andy2 | It would be very simple.  But I would like to upload it to my PPA.  I can't do    . Adri2000
[17:53] <persia> Err.  Pastebin might be easier to read, if that wasn't a mistake.
[17:54] <slomo_> superm1: i'll look at gmyth later (totem plugin i mean) and sponsoring gmyth to debian if youdidn't find someone yet
[17:54] <slomo_> superm1: bbl now though ;)
[17:55] <mario_limonciell> slomo_, yeah I do need someone to help get into debian.  I'll touch bases with you later.  thanks :)
[17:56] <ScottK> sistpoty|work: I suggest we discuss amongst ourselves via email.
[17:57] <sistpoty|work> ScottK: ok, sounds sensible
[17:57] <ScottK> sistpoty|work: It's been two acks in the past.
[17:57]  * persia likes 2 ACKs as it reduces the chance that any one person making a mistake causes an issue
[17:59] <jdong> ok, now, to scrape hardy-changes
[18:00] <persia> jdong: Why scrape?  Download the mbox tar, and once you have something working, subscribe your bot.
[18:00] <persia> That gives you headers, etc. and further doesn't break the GPG signatures.
[18:01] <HighNo> wow, we even have debian sponsors here? coolest channel on earth...
[18:03] <jdong> persia: mbox would be more reliable, but I just want something to pipe to less to see the X recent uploads
[18:05] <persia> jdong: Ah.  I think you can get just the current month as mbox, but in that case, yes scraping might be easier :(
[18:05] <jdong> persia: yeah scraping is indeed ugly, but it lets me get away with a 10-line script that does the job
[18:08] <persia> jdong: curl $(mbox.url) -o changes.mbox && mailx -H -f changes.mbox | head -10
[18:08] <persia> Your 10 lines likely use less bandwidth than my one line, and mine might benefit from the applicaiton of sed.
[18:15] <tuxmaniac> Hi folks. Is there a good guide on splitting up packages?
[18:16] <tuxmaniac> I am now stuck with a comment "Consider splitting the package" because of arch-dep-package-has-big-usr-share 14965kB 46%
[18:16] <jdong> persia: ooh interesting
[18:17] <DaveMorris> tuxmaniac: basically stick the arch dependent stuff in 1 package, and the non arch depend stuff in the other
[18:17] <DaveMorris> and have the arch depend stuff depend on the other package
[18:17] <jdong> persia: I guess the downside of my method would be the terrible hammering of the server with 10 separate HTTP connections
[18:17] <ScottK2> jdong: I'll sponsor the FF3 backport and upload it if you get an ack from asac that you've implemented his intent.
[18:17] <jdong> ScottK2: ok, cool :)
[18:17] <persia> tuxmaniac: There's some documentation on wiki.debian.org, but I find it easiest to just add the necessary bits to control, create the debian/package.install files, and pass --list-missing to dh_install until I've gotten the mix right.
[18:18] <tuxmaniac> hmm I will look into it
[18:18] <ScottK2> sistpoty|work: It might be nice to add a notice to REVU's front page indicating that no more new packages are being accepted for Hardy.   I see some uploads stil going on.
[18:18] <sistpoty|work> ScottK2: will do
[18:19] <rexbron> Ok, I just pushed a branch of ubuntu-dev-tools that separates ppaput into a module and a the script and updated the packaging. Anyone want to take a look? https://code.edge.launchpad.net/~rexbron/ubuntu-dev-tools/python-ppaput
[18:19] <persia> jdong: The downside of mine is that the download gets big at the end of the month :)
[18:20] <rexbron> s/the//
[18:20] <persia> rexbron: Do you have a bug open for discussion and possible merge? (note that you can associate a branch and a bug)
[18:20] <rexbron> persia, I have filed a bug and mentioned it in the changelog but have not proposed a merge yet
[18:21]  * RainCT looks
[18:22] <rexbron> Ok, filed a merge report
[18:23] <persia> rexbron: Ah.  I usually encourage linking the branch to the bug, so that the bug becomes a place to exchange comments on the branch until it can be merged.
[18:23] <jdong> asac: seems like xulrunner-1.9 already has USE_SYSTEM_* checks; are these valid/reliable to detect Gutsy properly or should I hardcode them to 0?
[18:23] <rexbron> persia, I also just linked the bug to the branch
[18:23] <rexbron> :)
[18:23]  * sistpoty|work heads home
[18:23] <sistpoty|work> cya
[18:23] <asac> jdong: right if the version is two low it should auto disable it
[18:24] <jdong> asac: alright, let me try in a gutsy pbuilder to make sure it detects this properly :)
[18:24] <rexbron> Opps, forgot to put a license header on the top of the new script
[18:24] <rexbron> fixing
[18:25] <ScottK2> Arghhh! - So the day AFTER feature freeze I get a bug against python-clamav and the solution to the bug is a new package (python-clamd).
[18:25] <persia> ScottK: That's why we have an exception process :)
[18:26] <ScottK2> Yeah.  Well.   Urgh.
[18:26] <jdong> :)
[18:27] <pochu> How many ACKs do we need from motu-release? 2?
[18:27] <zul> ScottK2: its called irony
[18:28] <jdong> asac: unrelated question, do you think Mozilla's gonna switch to something other than CVS anytime soon?
[18:29] <RainCT> rexbron: I think I'd be better have a "python-ubuntutools" like dholbach proposed (if possible with a better name :P) instead of python-ppapu, so that more stuff can be added to it later
[18:29] <ScottK2> pochu: Historically it's been two.  We are still nattering amongst ourselves for this release.
[18:29] <asac> jdong: http://hg.mozilla.org (-> for mozilla 2.0)
[18:29] <rexbron> RainCT, sure, not a problem
[18:29] <ScottK2> RainCT: Why put the word python in the package name?  It's not a Python module is it?
[18:30] <RainCT> ScottK2: it is now
[18:30] <jdong> asac: sweet!
[18:30] <ScottK2> It's a module?
[18:30] <rexbron> ScottK2, I factored out the backend code from ppaput
[18:30] <ScottK2> OK.  So I import ppaput and use that in my application?
[18:31] <rexbron> That is why I did it :)
[18:31] <ScottK2> OK.
[18:31] <RainCT> rexbron: also, I haven't looked at ppaput.py yet but if it does what you wrote on debian/control perhaps just "ppa" would be a better name (import ppa)
[18:31] <ScottK2> Fair enough then.
[18:31] <RainCT> or, forget my last sentence
[18:32] <RainCT> s/or/ok
[18:32] <ScottK2> Personally, I think MOTUs should have better things to do with their time than encourage 3rd party repositories, but whatever you feel is important ...
[18:33] <pochu> ScottK2: you can use ppas to call for testing :)
[18:33] <ScottK2> \sh: Dunno if you saw, but I had pdns-recursor sync'ed from Debian (with your patch plus some other stuff).
[18:33] <pochu> ScottK2: look at asac's ppa
[18:33] <RainCT> rexbron: but what would be nice are docstrings, if you have time to add some
[18:33] <\sh> ScottK2: yepp...
[18:33] <ScottK2> pochu: Sure, but developers don't need ppaput and such.
[18:33] <\sh> ScottK2: debian maintainer was fast with the upload...good :)
[18:34] <ScottK2> \sh: I think he was only fast because pkern threatened an NMU.
[18:34] <rexbron> RainCT, I am not sure what that would entail, but I will look into it
[18:34] <\sh> ScottK2: I love pkern ;) we owe him at least a beer :)
[18:40] <ScottK2> Julian owes him a beer and is much better placed than me to deliver.
[18:40] <hellboy195> \sh: ping
[18:42] <\sh> ScottK2: so it's up to me to serve him a cold one ;)
[18:42] <\sh> hellboy195: hi :)
[18:42] <ScottK2> Unless you can talk him into going to UDS and I get sponsored ...
[18:43] <hellboy195> \sh: hoi :) Have you already heard about the seg faults of wine 0.9.55 (including me) ?
[18:43] <\sh> hellboy195: yepp
[18:43] <\sh> hellboy195: my inbox is full of crashing wine spam
[18:44] <\sh> hellboy195: and I'm on it
[18:44] <hellboy195> \sh: ah k ,sry :)
[18:44] <\sh> hellboy195: my problem is that my time is limited at this time, because of new job etc...have a lot to do
[18:45] <hellboy195> \sh: no stress ;)
[18:56]  * RainCT gives up trying to give the balazar window an icon and decides that soya is crap :P
[18:57] <persia> RainCT: Well, mostly, but balazar can be confusing as well
[18:57] <ScottK2> RainCT: Feel like doing a quick Python package instead?
[18:57] <RainCT> ScottK2: for what?
[18:58] <ScottK2> RainCT: http://xael.org/norman/python/pyclamd/
[18:58] <RainCT> ScottK2: ok, but let me finish a youtube-dl SRU first
[18:58] <ScottK2> RainCT: Thanks.  It's the only solution I see to Bug #192130
[18:58] <ubotu> Launchpad bug 192130 in python-clamav "update to 0.4.0-1build1~dapper1 breaks programs" [Undecided,Confirmed] https://launchpad.net/bugs/192130
[19:05] <ScottK2> RainCT: I'll file the needs-packaging bug for it.
[19:07] <RainCT> great, even soya's author doesn't know if it is possible to give windows an icon lol
[19:08]  * festor is away: Estoy ocupado
[19:09] <vemon> how can i really remove a package from a launchpad ppa?
[19:10] <persia> vemon: Ask in #launchpad
[19:10] <pochu> vemon: there's a button for it in the UI
[19:10] <vemon> pochu, doesn't go all the way with the button
[19:10] <pochu> vemon: it takes a while
[19:10] <vemon> pochu, i'm still not able to re-upload with a same name+version
[19:10] <festor> RainCT, what is the problem?
[19:10] <vemon> ah ok..
[19:15] <RainCT> DktrKranz: uhm.. is youtube-dl failing for you?
[19:16] <ScottK2> RainCT: Bug #192205 is you get to it.  If not, I'll do it later tonight.
[19:16] <ubotu> Launchpad bug 192205 in ubuntu "pyClamd : Clamav with python needed to replace functions removed from python-clamav" [Undecided,New] https://launchpad.net/bugs/192205
[19:16] <ScottK2> is/if
[19:17] <DktrKranz> RainCT, do you refer to the patch I suggested?
[19:18] <RainCT> DktrKranz: if it fails before applying the patch.. I can't reproduce it anymore with the unpatched source :S
[19:18] <DktrKranz> d'oh
[19:19] <ScottK2> So I just now noticed that my Dapper desktop that I've been using since before Dapper was actually released (about Dapper Beta) is running the server kernel.  Odd.
[19:19] <frafu> Hello, the mousetweaks module in the launchpad buildd system says "pending (355)" for two days. Is the 355 its position in the build queue and should it not get smaller over the time?
[19:20] <RainCT> DktrKranz: oh, never mind
[19:20] <RainCT> DktrKranz: I don't know how but I got the Hardy sources :P
[19:20] <ScottK2> frafu: I lot of stuff got shoved on the buildd's in the last couple of days.  Universe is prioritized lower than Main, so it may be a while, but it'll get there.
[19:21] <DktrKranz> RainCT, heh :P
[19:22] <RainCT> SRU version for a -1 is -1ubuntu0.1, or?
[19:23] <ScottK2> RainCT: I'd suggest -1ubuntu0.1, but there's no hard and fast rule.  They main thing is to be sure you won't collide with the version number in another release.
[19:24] <persia> frafu: 355 is the priority, rather than the position in the queue.  It doesn't typically decrease in any understandable way, but rather based on age and buildd admin attitude.  Generally it's best to just wait for a while, and it gets built.
[19:26] <ScottK2> slangasek: I've got something I'm going to request a freeze exception on, but since it requires additional New processing, I thought I'd run it by you (in addition to getting another motu-release ack).  If you have a moment, please look at Bug #192205.
[19:26] <ubotu> Launchpad bug 192205 in ubuntu "pyClamd : Clamav with python needed to replace functions removed from python-clamav" [Undecided,In progress] https://launchpad.net/bugs/192205
[19:27] <ScottK2> slangasek: It's a very simple one file python module, so I don't think it will be hard to New, but thought I should check.
[19:28] <slangasek> ScottK2: yeah, that looks reasonable to me
[19:28] <RainCT> should the maintainer field be updated for SRU's?
[19:28] <frafu> ScottK2: thanks for the reply; now I know that it is not because I have missed to do something (for example asking for its reintegration because I previously got a buildfailure due to a missing dependency that was not yet available for the corresponding architecture)
[19:28] <frafu> persia: thanks for the explanation about the meaning of the number 355
[19:28] <slangasek> RainCT: you mean for an SRU of a package that was previously synced?
[19:29] <RainCT> slangasek: yes
[19:29] <ScottK2> slangasek: Thanks.
[19:29] <slangasek> RainCT: yes, it should
[19:29] <RainCT> slangasek: thanks
[19:32] <jpatrick> how do I use diffstat? manpage isn't very good, do I compare dirs or what?
[19:32] <slangasek> jpatrick: you feed it a diff on stdin, typically
[19:33] <jpatrick> slangasek: that only gives me changes in debian/
[19:34] <slangasek> jpatrick: "feed it a diff" - meaning, whatever you want to see the diffstat of, you generate the diff in the appropriate manner and feed it to diffstat
[19:34] <jpatrick> slangasek: ok, ah, now I see
[19:35] <slangasek> so that could be zcat $package_$version.diff.gz, or it could be debdiff $package_*.dsc, or diff -uNr $package_$upstream1/ $package_$upstream2/, etc
[19:35] <txwikinger> what the matter with http://qa.ubuntuwire.com?
[19:36] <jpatrick> slangasek: now, I've got it
[19:37] <ScottK2> txwikinger: Server's down.  Not sure until when.
[19:37] <txwikinger> Ah... I hoped it was not me :)
[19:38] <RainCT> txwikinger: that's evil :D
[19:38] <ScottK2> It's not you.
[19:38] <txwikinger> RainCT: I need to become more evil ;)
[19:43] <RainCT> DktrKranz: ah, candidate uploaded :)
[19:43] <DktrKranz> great, thanks
[19:45] <hellboy195>  Are monodevelop (1.0 release soon) or/and mono 1.9 release (also in a few days/weeks) important enough for a FF exception?
[19:45] <promag> I have a php project which is a website. whats the best approach to package it? how can I add the virtual host?
[19:45]  * RainCT just realized he has patched a .desktop file that is inside debian/ (with a patch system) and runs with the head against the wall :P
[19:45] <pochu> hellboy195: ask slomo_ :)
[19:45] <pochu> RainCT: lol
[19:45] <hellboy195> slomo_: ping. question above ^^
[19:45] <hellboy195> pochu: thx :)
[19:46] <\sh> I hate patches from upstream which are not clean
[19:46] <persia> \sh: That is why distributions have maintainers...
[19:47] <\sh> promag: include a file in /etc/apache2/sites-available/<websitename> with the correct configuration
[19:47] <LaserJock> RainCT: lol
[19:48] <\sh> promag: but I wouldn't install it like this...because the configuration of the website in general is the job ob the sysadmin...and not of the package and not of a website designer ;)
[19:48] <\sh> promag: the configuration should be held in svn or bzr or whatever vcs but not in a package
[19:49] <RainCT> btw, Debian is going to remove ttf-bitstream-vera. Is the same planned for Hardy?
[19:49] <ScottK2> RainCT: Why?
[19:49] <LaserJock> in favor of dejavu perhaps?
[19:50] <RainCT> yep
[19:50] <persia> I'd suggest wating for the Debian removal to be complete, and then looking at a removal.  It may be worth spending some time testing the results of adjusting dependencies to make that possible in the meantime.
[19:50] <LaserJock> I was looking at fonts the other day and it seemed like they were all the same
[19:51] <pochu> hellboy195: or bigon
[19:51] <ScottK2> At this point I'd suggest unless there's a strong reason to remove it, we should let it be.
[19:51] <pochu> later folks
[19:52] <hellboy195> pochu: k, next try ^^
[19:52] <\sh> oh well....
[19:52] <persia> pochu: If you have some time this weekend, please ping me re: gstreamer-midi.  I need help :)
[19:53] <\sh> wine will bang..I mean it's already banging like hell...but after that ;)
[19:53] <hellboy195> bigon: ping
[19:53] <LaserJock> Fujitsu: I emailed debian about python-scipy and it looks like we should have a version built on gfortran shortly
[19:53] <hellboy195> \sh: whats going on with wine? :)
[19:56] <\sh> hellboy195: there are some reports on winehq which tells me, that dejavu is still missing some important parts regarding other glyphs then latin1 etc. so all kyrillic and japanese stuff will break, that's why they are not sure to bundle dejavu with wine in this very moment..
[19:56] <ScottK2> LaserJock: I was looking into pulling their changes from svn and making an update to our package, but it can wait if you think we should.
[19:57] <\sh> hellboy195: and after looking into the crashing of wine, I'm not sure if it's wine or some other lib which is giving this result
[19:58] <hellboy195> \sh: k. thx for the info :)
[19:59] <\sh> hellboy195: and wine is really hard to debug, in the normal sense of debugging ;) gdb just failes
[19:59] <hellboy195> \sh: yeah. interesting piece of software :)
[20:03] <\sh> bah...what was the gcc switch to disable the stack-protector?
[20:03] <ScottK2> bddebian: Are you going to fix the testresources FTBFS?
[20:04] <\sh> -no-fstack-protector   that was it
[20:04] <\sh> just trying to rebuild it
[20:05] <ScottK2> \sh: Once you get WINE fixed up, how about we do a backport of it?  It's easier to find a core-dev interested in backports these days.
[20:06] <\sh> ScottK2: well, first of all it needs to be fixed...and really, I'm not sure if it's wine or something else (glibc or whatever)
[20:06] <\sh> but as there was no glibc update after last wine upload..
[20:09] <ScottK2> Let's discuss it when you think it's ready.
[20:11]  * \sh fixes cacti in the meantime
[20:13] <\sh> hmmm...is it still valuable to make updates for edgy?
[20:13] <ScottK2> \sh: My Hardy box still has the previous WINE version on it if there's any testing I could do that would help.
[20:14] <ScottK2> \sh: I'd be inclined to call it a very low priority.  It goes out of support in ~2 months.
[20:15] <DktrKranz> \sh, if you have fixes for other supported releases, you could consider one for edgy too, otherwise, keep it low prio.
[20:17] <ScottK2> Odds of getting it tested and into -updates before the release expires are probably low.
[20:20] <hellboy195> DktrKranz: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465986
[20:20] <ubotu> Debian bug 465986 in wmxres "wmxres: missing build-dependency: libxext-dev" [Normal,Open]
[20:21] <DktrKranz> hellboy195, \o/
[20:21] <hellboy195> DktrKranz: ?
[20:21] <DktrKranz> it worked :)
[20:22] <hellboy195> DktrKranz: look at it and tell me if the whole bug report is ok ;)
[20:23] <DRebellion> FF is over, but i heard that new packages can still be added to 'hardy+1' or backports or something. Could someone please explain this?
[20:23] <DktrKranz> hellboy195, it seems, even if Debian does not need our DebianMaintainerField change, but our change is reported.
[20:23] <HighNo> DRebellion: Hardy+1 is the next release
[20:24] <hellboy195> DktrKranz: k
[20:24] <HighNo> DRebellion: if it is added there it might be ported to the older versions via the backports team
[20:24] <DRebellion> HighNo, ah i see. I have a new (not in debian/ubuntu) package to contribute to ubuntu. So could I upload it for hardy+1 now?
[20:24] <slangasek> DRebellion: it's not possible to add packages to 'hardy+1' until a) it has a proper name, b) hardy itself is released.
[20:25] <HighNo> DRebellion: I am new too :-) I came "just in time"
[20:25] <DRebellion> :(
[20:25] <jpatrick> DRebellion: no, hardy+1 is not open for a long time
[20:26] <slangasek> DRebellion: on the other hand, if it's a completely new package it will have to go through a review process by the MOTU anyway, so you needn't wait idly in the meantime :)
[20:26] <HighNo> slangasek: I didn't know that. is that because the name would be needed for the package's control file (among other reasons...)?
[20:26] <ScottK2> OTOH, bug fixing and testing are very good ways to learn packaging, so you've shown up at a perfect time to learn.
[20:26] <slangasek> HighNo: well, until hardy+1 has a name, it doesn't exist in the launchpad config, so there's no archive to upload it to
[20:27] <ScottK2> It's actually possible that if you put yourself to work, learn fast, and do well, you may be MOTU when there is a Hardy +1 and you upload it yourself.
[20:27] <HighNo> slangasek: OK, but I guess uploading to REVU would still be possible?
[20:27] <slangasek> HighNo: correct
[20:27] <ScottK2> HighNo: Possible, but pointless.
[20:27] <HighNo> :-)
[20:27] <slangasek> ScottK2: well, it gets feedback, no?
[20:27] <slangasek> or maybe not :)
[20:28] <DRebellion> Well, I guess I'll just hold onto the packge until 8.04 comes by :|
[20:29] <jpatrick> HighNo: you could try getting it into Debian and syncing it across later
[20:29] <kdub> how do you upload to revu?
[20:30] <jpatrick> kdub: https://wiki.kubuntu.org/MOTU/Packages/REVU
[20:30] <HighNo> DRebellion: start studying the package guides... I took the fast (but hard) lane but doing as ScottK suggested will definetly help you. Start by fixing bugs in packages - you have plenty of time to try :-)
[20:31] <HighNo> jpatrick: right - that would be another way though I haven't heard of a 'fast debian package integration' before - so I think it is unlikely to get it into debian before hardy+1 accepts packages
[20:31] <kdub> jpatrick: all you upload is the .changes file?
[20:32] <DRebellion> kdub, you specify the .changes file to dput and it will upload the nessecary files.
[20:32] <jpatrick> kdub: yes, and it pulls everything else with it
[20:32] <kdub> ah, alright
[20:32] <jpatrick> HighNo: http://mentors.debian.net will help you and #debian-mentros @ OTFC
[20:33] <RainCT> ScottK2: what do you prefer for pyclamd: native, lp branch...?
[20:33] <\sh> kdub: important you give dput the *_source.changes file and not the *_<arch>.changes file
[20:33] <jpatrick> #debian-mentors*
[20:33] <HighNo> ScottK: btw, bugfixing... I tried to do it with the cherrypy bug you mentioned like earlier this week. I could only do it for feisty so far - what is the next thing? can anyone have a lok at that debdiff file to check if I did things correct?
[20:34] <HighNo> jpatrick: I'll try later. I think I delegated the debian packaging to the 'debian packaging bug' creator
[20:34] <kdub> \sh: i will keep that in mind
[20:36] <RainCT> HighNo: You'll definitely get it into Debian before Hardy+1 if you want, it isn't that difficult :)
[20:37] <HighNo> jpatrick: hm, is that channel on freenode? because there are 5 people in there, 1 is a bot, 1 is me... See what I mean - 3 vs. 223 ppl ? I like Ubuntu :-)
[20:37] <ScottK2> RainCT: Debian source package
[20:37] <HighNo> RainCT: Actually that's just what I heard but you know rumors...
[20:37] <ScottK2> HighNo: It's on OFTC
[20:38] <ScottK2> HighNo: Yes.  Ask attach the debdiff to the bug and then subscribe ubuntu-universe-sponsors to get it reviewed
[20:38] <RainCT> ScottK2: ?
[20:39] <jpatrick> HighNo: /connect irc.oftc.net
[20:39] <RainCT> ScottK2: native? or what do you mean?
[20:39] <HighNo> jpatrick: got it now :-)
[20:39] <ScottK2> RainCT: You asked me what format I wanted for pyclamd.  What I want is a regular (non-native) debian source package (.dsc, diff.gz, and orig.tar.gz)
[20:39] <sistpoty> anyone who minds some downtime of REVU right now?
[20:39]  * ScottK2 would prefer it actually.
[20:40] <ScottK2> sistpoty: While you're here, would you please ack Bug #192205
[20:40] <ubotu> Launchpad bug 192205 in ubuntu "pyClamd : Clamav with python needed to replace functions removed from python-clamav" [Undecided,In progress] https://launchpad.net/bugs/192205
[20:40] <RainCT> ScottK2: upstream releases just a single .py. repackaging then?
[20:40] <slangasek> jpatrick: aka 'irc.debian.org' for those purposes
[20:40] <ScottK2> RainCT: Yes
[20:40] <jpatrick> slangasek: same thing in the end
[20:40] <ScottK2> RainCT: Then you can include the license file and the changelog with it.
[20:40] <HighNo> /connect irc.debian.org
[20:41] <HighNo> hehe
[20:41] <HighNo> ooops
[20:41] <ScottK2> RainCT: Then the instructions for use on the web site would make good content for a man page.
[20:41] <HighNo> gaim seems somewhat limited ...
[20:42] <sistpoty> ScottK2, RainCT: acked
[20:42] <ScottK2> RainCT: If you run out of time, let me know.
[20:42] <ScottK2> sistpoty: Thanks.
[20:42] <sistpoty> ScottK2: anything else I need to do (bug status or s.th.)?
[20:43] <RainCT> ScottK2: what should the version number be? YYYYMMDD-ds1-<...>? (just seen that ds in another package, is that right?)
[20:43] <ScottK2> sistpoty: No.  Normally you set them to confirmed, but since RainCT already has it in progress, no point in it.
[20:43] <sistpoty> ok
[20:43] <ScottK2> RainCT: 0.1.1 from his changelog: http://xael.org/norman/python/pyclamd/CHANGELOG
[20:44] <RainCT> ScottK2: ah, ok. but with -ds or what else?
[20:45] <ScottK2> RainCT: Why -ds?
[20:46] <RainCT> ScottK2: don't I need to add anything if I repack?
[20:47] <ScottK2> Since this is packing, not repacking, I think not.  What you need to do is document how you constructed the tarball in debian/copyright.
[20:47] <ScottK2> RainCT: ^^
[20:47] <RainCT> heh
[20:47] <RainCT> ok, thx
[20:51] <\sh> oh heaven
[20:51] <sistpoty> \sh: what's up?
[20:51] <\sh> sistpoty: well, wine is hurting me a lot
[20:51] <sistpoty> oh
[20:51] <\sh> sistpoty: actually it's not wine, but something which is triggering wine crashes
[20:52] <Yasumoto> Heya guys, I'm following along with the Packaging Guide, and when I run "sudo pbuilder build ../*.dsc" I get this error:
[20:52] <Yasumoto> gzip: debian/tmp/usr/share/man: No such file or directory
[21:06] <sistpoty> persia: just saw your upload of nvidia-settings... did you also add conflicts?
[21:07] <sistpoty> (wanted to do this yesterday, but -ENOTIME :(=
[21:10] <HighNo> ScottK - did you get my lines on Bug #191198 ?
[21:10] <ubotu> Launchpad bug 191198 in python-cherrypy "[python-cherrypy] [CVE-2008-0252] missing input sanitising, remote vulnerability" [Undecided,Confirmed] https://launchpad.net/bugs/191198
[21:12] <RainCT> how can I delete (within a script) everything from the start of a file until it reaches a certain line (checking by content, not line number)
[21:13] <RainCT> ?
[21:14] <LaserJock> ScottK: sorry, was afk, were you talking about scipy?
[21:15] <ScottK2> LaserJock: Just that I'd been looking at the changes in the Debian svn and considering updating our package.
[21:15] <ScottK2> HighNo: Did you add your debdiff to the bug and subscribe UUS?
[21:15] <HighNo> ScottK: I think yes
[21:15] <LaserJock> ScottK2: well, i don't think it matters if we wait for Debian, I just think we should do it before release :-)
[21:15] <ScottK2> LaserJock: OK.
[21:16] <HighNo> ScottK: but as I mentioned, I have done that for feisty only - though the fix should work with all versions...
[21:16] <ScottK2> HighNo: Then please make debdiffs for the other versions too.  You can at least make them and test build them using pbuilder.
[21:17] <RainCT> ScottK2: did you indeed mean manpage or rather a file in /usr/share/doc/python-pyclamd/?
[21:17] <ScottK2> RainCT: Yes.  I think a man page is the preferred method.
[21:17] <ScottK2> RainCT: I'm willing to discuss it.
[21:18] <RainCT> ScottK2: do you have some example manpage (to see how it looks, not the code)?
[21:18] <sladen> RainCT: they'll be a better way, but    grep -A999999 foobar file
[21:21] <ScottK2> RainCT: How about pyspf source package?
[21:22] <RainCT> sladen: great, thanks :)
[21:24]  * LaserJock attempts a bzr branch of Debian's scipy
[21:24] <RainCT> ScottK2: (I'm away for 20 minutes)
[21:24] <ScottK2> K
[21:25] <ScottK2> LaserJock: From svn or the package?
[21:25] <LaserJock> svn
[21:25] <ScottK2> OK.
[21:25] <LaserJock> neato, it worked
[21:25] <ScottK2> Cool
[21:30] <LaserJock> my gosh the python-modules svn has a lot of packages
[21:31] <ScottK2> Yes.  It's a pretty big repo (last I counted it was over 200)
[21:32] <LaserJock> how many DD sponsor it?
[21:32] <sistpoty> persia: I'm still unsure about the "virtual package support" thingy... imo it might work for the l-r-m upgrade path, but most probably it would lead to problems on fresh installed (which could then be worked around...)
[21:32]  * \sh goes off
[21:32] <\sh> good night
[21:33] <hellboy195> \sh_away: hf
[21:33] <sistpoty> persia: since there are file conflicts, I'm adding the (very defensive) conflicts now to nvidia-settings, and also add an alternate recommends, together with correct version numbers...
[21:34] <sistpoty> persia: hopefully nvidia-glx won't be virtual package, otherwise I don't have a clue about fixing the upgrade path... maybe you do?
[21:35] <ScottK2> LaserJock: two regularly and a few others from time to time.
[21:35] <ScottK2> LaserJock: It's generally very easy to get sponsored
[21:35] <LaserJock> ScottK: wow, that's not very many though
[21:36] <ScottK2> LaserJock: There is also Debina Python Applications Team for Python apps.
[21:36] <LaserJock> I suppose now having DMs helps
[21:36] <ScottK2> Yes.
[21:36] <ScottK2> They're pretty efficient and expend a fair amount of time on it.
[21:36] <ScottK2> RainCT and pochu can vouch for it.
[21:38] <LaserJock> ScottK2: is there a core python team that looks after python itself
[21:38] <LaserJock> ?
[21:39]  * RainCT is back
[21:39] <ScottK2> LaserJock: Yes, but I'm not familiar the details of it.
[21:40]  * RainCT agrees that the python-apps/python-modules team is great
[21:46] <RainCT> ScottK2: hm.. I'm being unsure if it's even necessary to include the documentation separatly.. exactly the same is available as docstrings
[21:47] <RainCT> ScottK2: so python -c "import pyclamd; help(pyclamd)" shows it all :)
[21:52] <ScottK2> RainCT: OK.  Fair enough.
[22:02] <ScottK2> RainCT: The reporter of the bug I'm trying to resolve with this new package says you need to change the socket location for clamd in python-clamd for Ubuntu.  FYI.
[22:22] <Fujitsu> LaserJock: Very good. Thanks.
[22:22] <sistpoty> any gnome user with a nvidia card around, who'd like to test a debdiff for sensors-applet?
[22:23] <NorthernLights> Hello all
[22:24] <NorthernLights> I've uploaded a package (gtkvncviewer 0.2) half an hour ago, and it doesn't show up on revu. Should i upload it again ?
[22:24] <sistpoty> NorthernLights: let me check (revu was down due to a dist-upgrade)
[22:25] <NorthernLights> yes i saw that right after my upload the web site was down
[22:25] <sistpoty> NorthernLights: nothing in any queue... so if it's not there, you'll need to upload again
[22:26] <NorthernLights> ok, i'm uploading again then, thank you
[22:26] <sistpoty> NorthernLights: however we're in feature freeze now, so don't expect it to get much attention (and you'll need to file a feature freeze exception)
[22:27] <NorthernLights> yeah... i noticed that when entering the channel
[22:30] <NorthernLights> i'm leaving, thanks again
[22:30] <ScottK2> RainCT: Starting in ~15 minutes I'll be AFK for some time.  Any questions before I go?  If you get the package done, link me a .dsc for it and I'll have a look later.
[22:35] <RainCT> why doesn't this work ${VERSION##*-}? :'(
[22:35] <RainCT> (in debian/rules)
[22:36] <slangasek> because debian/rules is make, and that's shell syntax?
[22:37] <RainCT> slangasek: any idea how I could do that then?
[22:37] <sistpoty> $(shell thatthingwithdollaresacped)?
[22:37] <RainCT> then I don't have $VERSION there
[22:37] <slangasek> RainCT: not without more context
[22:38] <sistpoty> RainCT: you have $VERSION there... (which gets replaced by make before getting passed to the shell)
[22:38] <sistpoty> or rather $(VERSION=
[22:38] <sistpoty> hrmpf... $(VERSION)
[22:40] <sistpoty> but that thing looks pretty much like a bashism to me anyway, right?
[22:40] <RainCT> uhm.. and now why am I trying ${VERSION##*-} if what I want is exactly everything except that? what a day.. lol
[22:40] <RainCT> slangasek: how can I get the upstream version number from the changelog?
[22:41] <RainCT> sistpoty: it's POSIX
[22:41] <sistpoty> RainCT: d'oh
[22:42] <sistpoty> RainCT: SOMEVAR=$(eval head debian/changelog -1 | cut -d '(' -f 2 | cut -d ')' -f 1)
[22:42] <sistpoty> RainCT: maybe? (didn't try it though)
[22:42] <slangasek> eew cut
[22:42] <slangasek> :)
[22:42] <RainCT> I have VERSION=$(shell dpkg-parsechangelog | grep --max-count=1 -F "Version:" | cut -d" " -f2)
[22:42] <RainCT> but I don't know how to get only upstream version number
[22:43] <sistpoty> RainCT: err.. replace the eval with shell... /me is also mixing shell and make again
[22:43] <RainCT> as it might have more than one -
[22:45] <sistpoty> RainCT: add a | cut -d'-' -f -1 (or s.th.)?
[22:45] <slangasek> dpkg-parsechangelog | sed -n -e'/^ / { s/.*(\(.*\)).*/\1/; s/-[^-]*$//; p; q }'
[22:46] <sistpoty> wow
[22:46] <RainCT> o_O
[22:46] <slangasek> well, you can use head and cut if you prefer, but why fork if you don't have to :-)
[22:46] <RainCT> slangasek: have you patented this? :P
[22:47] <slangasek> uh? :)
[22:47] <slangasek> it's just a bit of sed
[22:47] <slangasek> if you know you always have a debian revision for the package in question, you can reduce the two s// to one
[22:49] <RainCT> uhm... but it doesn't work here VERSION=$(shell dpkg-parsechangelog | sed -n -e'/^ / { s/.*(\(.*\)).*/\1/; s/-[^-]*$//; p; q }')
[22:50] <sistpoty> RainCT: why do you want to find out the upstream version anyways? maybe just for an get-orig-source rule?
[22:50] <RainCT> sistpoty: yes
[22:50] <slangasek> RainCT: you have to double the $ within a makefile
[22:51] <sistpoty> RainCT: oh, I made one once for trigger (depending on a watch file)... which should always give you the latest version.. must be somewhere (either in the archive or on LP)
[22:51] <RainCT> slangasek: oh, works now. thanks!
[22:51] <dcordero> hi
[22:52] <sistpoty> RainCT: I guess "uscan --dehs" might be useful, too ;)
[22:53] <RainCT> sistpoty: it has no watch file
[22:53] <RainCT> (upstream just releases a .py)
[22:54] <sistpoty> oh, heh
[23:01]  * LaserJock starts a server install, how exciting ;)
[23:10] <ScottK2> Shouldn't take long.
[23:14]  * sistpoty is off to bed... gn8
[23:16] <LaserJock> anybody have any good recommendations for a FS for a 500GB backup drive?
[23:16] <LaserJock> should plain-old ext3 work fine?
[23:17] <jdong> LaserJock: my general policy is unless you have a REALLY REALLY good reason to choose another FS, go with ext3
[23:17] <jdong> LaserJock: it's not the fastest or most advanced, but it definitely has the most followers and most people to bail you out should you get into FS-hell
[23:18] <LaserJock> hmm, so no reiserfs? ;-)
[23:18] <jdong> LaserJock: well he has bail problems himself ;-)
[23:18] <RainCT> ScottK2: is python-clamav still useful or does this replace it?
[23:19] <RainCT> well, good night
[23:44] <LaserJock> hmmpf
[23:44] <LaserJock> anybody know how to bail out of the text installer?
[23:44] <selckin> :q!
[23:45] <LaserJock> I thought it'd be C-x C-c
[23:45] <selckin> i have no idea :)
[23:53] <Fujitsu> LaserJock: Reset button? Why would an OS installer have a cancel button?
[23:53] <Yasumoto> Heya guys, I'm following along with the Packaging Guide, and when I run "sudo pbuilder build ../*.dsc" I get this error:
[23:53] <Yasumoto> gzip: debian/tmp/usr/share/man: No such file or directory
[23:54] <LaserJock> Fujitsu: I just want to "go back"
[23:54] <LaserJock> Fujitsu: I selected the wrong network device and now the installer is "stuck" on setting up the mirrors
[23:55] <LaserJock> I was hoping to avoid having to reinstall
[23:58] <Fujitsu> Ah, it should give up after a few minutes.
[23:58] <Fujitsu> I've struck that a few times when the .au mirror has been down during installation.
[23:59] <Fujitsu> If not, killing a couple of apt-gets might fix it.