[00:02] <imbrandon> heya persia
[00:02] <somerville32> heya imbrandon and persia
[00:02] <imbrandon> ello somerville32
[00:02] <persia> Hey imbrandon
[00:02] <persia> hi somerville32
[00:08] <zul> hey imbrandon you still havent open up that bug yet
[00:10] <imbrandon> hrm i thought i had, maybe my net flaked
[00:10] <imbrandon> if not i will right now
[00:11] <imbrandon> zul: do you need a patch attached or "just a bug" ?
[00:11] <zul> imbrandon: nope i already ported the fatx stuff to 2.6.24
[00:12] <norsetto> g'night all
[00:12] <imbrandon> killer, ok filing now
[00:14] <imbrandon> zul: against l-u-m correct >?
[00:14] <zul> zul: yeppers
[00:15] <zul> just so I dont get my head chopped off
[00:16] <imbrandon> np, would be faster but lp is being a pita right now ( slow )
[00:16] <zul> well it is christmas maybe the hamsters had too much eggnog
[00:16] <imbrandon> :)
[00:16] <imbrandon> i actualy have two timeouts
[00:16] <imbrandon> so far
[00:16] <imbrandon> grrr
[00:16]  * zul cant type tonight
[00:18] <imbrandon> wow really slow, 50% done
[00:22] <Larose> Is there exist a "simple" example of a - good - kernel module package ?
[00:22] <imbrandon> zul: bug number 178809
[00:22] <zul> thanks..
[00:26] <persia> awen_: If you prepare a fix that also fixes a linked Debian bug, it's good practice to add a comment to the Debian bug that indicates how it was fixed.  A patch tested on Debian is typically even more welcome.
[00:28] <awen_> persia: i'll note that... which package are you at atm?
[00:28] <persia> awen_: I just did bug #145551
[00:28] <ubotu> Launchpad bug 145551 in libapache-mod-random "[UNMETDEPS] libapache-mod-random has unmet dependencies" [Medium,Fix committed] https://launchpad.net/bugs/145551
[00:29] <persia> I won't have time now for some of the others, but even if the solution isn't uploaded yet, it can be useful for Debian.
[00:30] <awen_> persia: so i should just put a note on the debian bug, that it's fixed by pulling a new upstream version?
[00:31] <persia> awen_: Yes.  Reporting that upstream 2.1 is compatible with apache2.2 would be helpful, as it would tell the maintainer that an update would be good, rather than the package requiring removal.
[00:31] <awen_> persia: i'll go through the packages i've uploaded a new version for tomorrow
[00:32] <persia> awen_: Thank you.
[00:33] <awen_> persia: another thing... i've looked at another libapache-mod-tsunami, same problem as all the others; but the only avaible apache 2.2 compatible version was branched at version 2.0 of the package and is still at a version below 3.0 which we have now
[00:33] <awen_> what do you normally do then?
[00:34] <persia> awen_: Three choices, 1) try to merge the patch into the newest upstream,  2) coordinate with the Debian maintainer to discuss adding an epoch and using the apache2 branch, or 3) add a new source package for the apache2 branch.
[00:36] <nxvl_work> persia: hi!
[00:36] <persia> nxvl_work: Hello.
[00:36] <awen_> persia: okay, thanks... i can see a coordination with the debian maintainer is needed, i should start with that
[00:37] <nxvl_work> persia: did you a know a good way to split dpatch files?
[00:37] <persia> awen_: That's often easiest.  I suggest coordinating through mail to the BTS report, as that way other people subscribed to the package or bug will also see the information, and may have useful input.
[00:37] <nxvl_work> persia: i found what was happening with dillo
[00:37] <nxvl_work> persia: it is a 1.9M long patch
[00:37] <awen_> persia: good idea
[00:37] <nxvl_work> persia: editing 181 files
[00:38] <nxvl_work> evil DDs
[00:38] <persia> nxvl_work: splitdiff.  I haven't tried it on the internationalisation patch for dillo, but given that that specific patch is maintained by an upstream patch author, I'm not sure splitting it is correct.
[00:38] <mruiz> Hi all. I'm fixing a bug related to a missing menu entry. Desktop file (foo.desktop) is done but I have to configure the package to put this file in /usr/share/applications. How can I do it with CDBS ?
[00:38] <persia> nxvl_work: Check the URL given in the dpatch to see if the patch upstream (not dillo upstream) has released a new patch, and be sure to report the bug to them as well.
[00:39] <nxvl_work> persia: i tried splitdiff, but it doesn't split it on dpatch format, it split it on diff format, which is not the same
[00:39] <persia> mruiz: CDBS automatically calls dh_install, so just put it in debian/<package>.install
[00:39] <nxvl_work> persia: i have reported it to the one who apears on the changelog as the one who make the patch, but he hasn't write me back
[00:40] <persia> nxvl_work: They are basically the same.  You might have to temporarily delete the dpatch header from the dpatch to get the diff -u
[00:40]  * persia still doesn't think splitting the diff is the right solution
[00:41] <nxvl_work> persia: i don't want to solve it spliting and packing, it's only to check which of the 181 files is the problematic one to backup it
[00:42] <persia> nxvl_work: And manually calling the unpatch rule doesn't leave useful .rej files for inspection?
[00:42] <nxvl_work> it leaves a LOT of .rej files
[00:42] <nxvl_work> not all usefull
[00:42] <persia> nxvl_work: All of those are the problem.
[00:42] <mruiz> hi persia . The content of gnome-chess.install appears in http://pastebin.ubuntu.com/3027/. How should I add the desktop file information ?
[00:43] <nxvl_work> persia: so, there is only .rej files for the ones which are having trouble not for any of the rest?
[00:43] <persia> mruiz: $relative_path_to_desktop_file /usr/share/applications/
[00:43] <persia> nxvl_work: Right.  The .rej files are the patches that were rejected.  The rest applied cleanly.
[00:44] <nxvl_work> mmm
[00:44] <nxvl_work> i will take a look
[00:46] <mruiz> thanks persia . I'm building the package...
[00:46] <nxvl_work> 15 files
[00:47] <nxvl_work> no, 102
[00:50] <nxvl_work> oh, god, this is a crapy patch
[00:50] <nxvl_work> it's all wrong
[00:51] <awen_> night everyone
[00:57] <mruiz> I have an Ubuntu package with the following version "0.3.3-6.1build1". I tried to modify the Maintainer field with update-maintainer and I got  "Not an Ubuntu package or already maintained by the Ubuntu team". Where is the problem?
[00:58] <Amaranth> mruiz: Just what it says, there is no Ubuntu specific version so it's a Debian package
[00:58] <Amaranth> build1 means, iirc, that it's an automatic rebuild
[00:58] <Amaranth> for some dependency change, I guess
[00:59] <imbrandon> s/automatic//
[00:59] <Amaranth> imbrandon: I thought build1 was used when you asked an archive admin to do a rebuild
[00:59] <imbrandon> build1 means rebuld with no changes
[00:59] <Amaranth> Oh, then not everyone follows that rule
[01:00] <Amaranth> Lots of people just use ubuntu1
[01:00] <imbrandon> so i can reupload manualy too a build1 but the same rules apply
[01:00] <imbrandon> no thats totaly diffrent
[01:00] <imbrandon> it will mess up the merges
[01:00] <Amaranth> Right, I know it's different
[01:00] <Amaranth> But I see it done
[01:00] <imbrandon> e.g. a build1 will automaticly sync on next merge cycle, a ubuntu1 wont
[01:00] <imbrandon> thus build1 can be manualy uploaded also but it needs to have -0- changes, only a rebuild
[01:01] <mruiz> then, should I change the version to X.Y-ZubuntuW ?
[01:01] <imbrandon> mruiz: what is the version you started with ?
[01:02] <imbrandon> if you made changes yes it needs to be ubuntuX
[01:02] <imbrandon> Amaranth: give-backs normaly dont have a new version number appened iirc
[01:03] <mruiz> imbrandon, changelog entries http://pastebin.ubuntu.com/3028/
[01:04] <imbrandon> mruiz: the last entrie needs to be "-6.1ubuntu1"
[01:04] <imbrandon> entry*
[01:04] <mruiz> thanks imbrandon
[01:04]  * mruiz changing the version
[01:08]  * mruiz building the package :-)
[01:21] <mruiz> strange... After a successful build I got the following information: mruiz@hardy:~/pbuilder/result$ dpkg --contents gnome-chess_0.3.3-6.1ubuntu1_i386.deb |grep .desktop
[01:21] <mruiz> -rw-r--r-- root/root       981 2007-12-26 22:17 ./usr/share/applications/gnome-chess.desktop
[01:21] <mruiz> -rw-r--r-- root/root       981 2007-12-26 22:18 ./usr/share/gnome/apps/Games/gnome-chess.desktop
[01:21] <mruiz> two places with the same Menu file...
[01:25] <tritium> Shouldn't various doc like maint-guide, packaging-guide, etc. show up in yelp after installation?  I've even run updated the scrollkeper DB...
[01:28]  * tritium installs dhelp *shrug*
[01:38] <imbrandon> ...
[01:39] <mruiz> imbrandon, how can I delete the Menu file under /usr/share/gnome/apps/Games/ ? Makefile.{am,in} install it there...
[01:48] <imbrandon> just dont install it, if thats what your asking, or user rm in the rules
[01:48] <imbrandon> s/user/use
[01:49] <imbrandon> rm debian/gnome-chess/usr/share/......
[02:09] <mruiz> imbrandon, my debian/rules files is too short (just 6 lines) http://pastebin.ubuntu.com/3029/ . Where should I put the line "./usr/share/gnome/apps/Games/gnome-chess.desktop" ?
[02:10] <imbrandon> you need to overide on of the targets like your doing with clean
[02:10] <imbrandon> if you arent familiar with debhelper its not easy to use cdbs to start with
[02:13] <mruiz> imbrandon, yes...I have to learn more about debhelper
[02:34] <imbrandon> :)
[02:36] <mruiz> imbrandon, it's a challenge for me... :-)
[02:41] <mruiz> bye all...
[02:48]  * Hobbsee waves
[02:53] <mruiz> cya!
[02:58] <x-ip> hi, i installed gdesklets at kubuntu feisty and there is a problem starting or trying to start the  daemon
[02:58] <x-ip> ./gdesklets-daemon
[02:58] <x-ip> The following error occurred: IOError(2, 'No such file or directory')
[02:59] <x-ip> thats at /usr/lib/gdesklets
[03:09]  * TheMuso has 1337 unread emails.
[03:11] <ScottK2> TheMuso could probably do with unsubscribing from some mailing lists.
[03:12] <TheMuso> ScottK2: Its called away for 4 and a half days.
[03:13]  * StevenK wishes he was away. 
[03:13] <StevenK> Cooking and entertaining for ten people on Christmas day is still hurting
[03:16] <StevenK> TheMuso: How was your trip?
[03:19] <TheMuso> StevenK: Very nice thanks. I always enjoy getting with family.
[03:21]  * StevenK is all familied out until New Year
[03:31]  * imbrandon is also
[03:32] <StevenK> imbrandon: Good, then you can fix apt-mirror
[03:32] <imbrandon> okies
[03:32] <imbrandon> i've just been enjoying my new keyboard tongiht,far less typos
[03:32] <imbrandon> its one of those brushed metal ones that come with the new metal iMacs
[03:32]  * StevenK is plotting a wireless keyboard and mouse for his machine
[03:33] <imbrandon> very nice to use, not all the MM keys work but i have a feeling if i installed the MBP keymap they would
[03:33] <imbrandon> StevenK: they have a wireless verion of the one i just got
[03:33] <imbrandon> too
[03:34] <StevenK> I'm still pondering.
[03:35] <imbrandon> although the wireless version dosent have the numpad
[03:35] <StevenK> Also curious if I have the transmitter/reciever on the desk, will they work since the keyboard drawer is below the dek
[03:35] <imbrandon> http://www.apple.com/keyboard/
[03:35] <imbrandon> i have the wired one
[03:35] <imbrandon> StevenK: should , i had a wireless one at one time and they worked uotp 10 feet away
[03:35] <StevenK> Ah. I'm not buying Apple hardware
[03:35] <imbrandon> through stuff etc
[03:36] <imbrandon> upto*
[03:36] <imbrandon> the one i had was logitec (sp?)
[03:36] <imbrandon> it was nice, but i'm hooked on apple keyboards the last few years
[03:37] <imbrandon> even on non-apple computers ( like mine )
[03:37]  * StevenK slaps a fan-boy sticker on imbrandon's head
[03:37] <imbrandon> heh nah, they are quite diffrent , plus the extra fN keys ( f13 - f19 ) are nice to be mapped to other things
[03:38] <imbrandon> hum my irssi seems to be cutting off the last few chars of each line
[03:38] <imbrandon> :(
[03:38]  * StevenK makes a note to add 50 spaces to every line he tells imbrandon
[03:39] <imbrandon> heh well it something about the nicklist i have in irssi, it runs in another "screen" and does some funky stuff, seems i have to restart irssi every few days because of it
[03:39] <imbrandon> i might turn it off
[03:39]  * imbrandon takes a screenie
[03:39]  * StevenK has no nicklist
[03:41] <TheMuso> imbrandon: What? You too lazy to do a /n when you need a list of nicks?
[03:42] <imbrandon> :)
[03:42] <StevenK> I don't usually use /names. I will try and tab complete the nick I'm after
[03:42] <TheMuso> StevenK: Yeah, but /n is handy.
[03:42] <imbrandon> StevenK / TheMuso : http://people.ubuntuwire.com/~imbrandon/irssi-nicklist.png
[03:43] <StevenK> That's a little frightening
[03:44] <imbrandon> heh why ?
[03:45] <StevenK> imbrandon: You can't scroll the list, it's just there.
[03:47] <imbrandon> yea you can
[03:47] <imbrandon> i have it mapped to shift+pgup/pgdn
[03:48] <imbrandon> one quark about it though ( it is a official script on the irssi page ) is it only refreshes everytime i type a line or someone else types a line
[03:49] <imbrandon> so the list can be stale a bit in a quiet room
[06:33] <tritium> imbrandon: is there no hardy package for debootstrap?  I'm trying to setup schroot...
[06:34] <tritium> https://wiki.ubuntu.com/DebootstrapChroot is a little unclear...
[06:34] <imbrandon> tritium: there is, its probably just not linked to that page
[06:35] <tritium> I've not seen one.  Onyl 1.0.7_all
[06:35] <tritium> only, even
[06:35] <imbrandon> 1.0.7 is the latest iirc
[06:35] <tritium> So, no dist name associated with it anymore?
[06:36] <imbrandon> huh ?
[06:36] <imbrandon> dist names are only needed for backports
[06:36] <imbrandon> ignore those
[06:36] <LucidFox> jdong, what's the status of mpeg4ip?
[06:37] <tritium> ah, then that wiki page is even _more_ unclear.  Thanks.
[06:38] <tritium> The wiki page explicitly tells you to use those ~dist1_all.deb packages
[06:41] <imbrandon> yes then it is mistaken, you should just grab the latest available
[06:41] <tritium> Thanks, imbrandon.
[06:41] <imbrandon> basicly if your on gutsy and have backports enabled, your golden, just install them as normal
[06:42] <imbrandon> and other packages it mentions
[06:42] <tritium> I'm trying to setup a hardy chroot.  Which are you suggesting I install as normal?
[06:42] <imbrandon> chroot or pbuilder?
[06:43] <tritium> chroot.  I already have a pbuilder setup.
[06:43] <tritium> Don't want to clutter my main install with dev packages I won't otherwise need.
[06:43] <imbrandon> if you have a hardy pbuilder setup already then you have the required packages already installed, ignore if it tells you to install anything and just follow the indtructions
[06:43] <Yurivilca> http://digg.com/2008_us_elections/Mike_Huckabee_If_you_vote_for_me_you_live_if_you_don_t
[06:43] <Yurivilca> Check out Mike Huckabee's latest psychotic utterance!
[06:46] <imbrandon> tritium: also note too you can `pbuilder-hardy login` and use it as a chroot too :)
[06:47] <tritium> imbrandon: I'm not following what you're saying.  I'm following https://wiki.ubuntu.com/PackagingGuide/Basic, where advice on installing schroot comes *after* advice to install pbuilder.
[06:47] <imbrandon> s/pbuilder-hardy/how_you_call_pbuilder/
[06:47] <tritium> yes, but don't you clean your pbuilder for each build?  Seems like a chroot for things like devscripts, debhelper, dh-make, etc. would be nice.
[06:48] <imbrandon> ahh ok, then yes you probably want another chroot, its pretty simple , just debootstrap hardy into a new dir, then you can just `chroot /where/you/bootstraped/`
[06:49] <tritium> Okay, thanks.
[06:49] <imbrandon> past that its all customizations, basicly i was telling you earlier that if you followed the tutoral on setting up pbuilder that it installe dall the required packages to make a "normal" chroot
[06:50] <tritium> I appreciate it.
[06:50] <imbrandon> e.g. if you have a hardy pbuilder it used debootstrap to make the hardy pbulder, so you have the required version of debootstrap to make a hardy chroot
[06:50] <imbrandon> nayhow yw
[06:50] <imbrandon> any*
[06:51] <tritium> Ah, right...
[06:53] <tritium> Hi jsgotangco!
[06:54] <jsgotangco> g'day tritium :)
[06:54] <tritium> It has been a while...
[08:13] <warp10> Hi all!
[08:18] <SWAT> hmm, I've manually added a dependency to the control file ('Depends: package (=version-0ubuntu1)'). But when I build and install the package, it does not complain about missing the Depends package. Any tips?
[08:48] <gpocentek> SWAT: is there a control.in file too?
[08:49] <SWAT> gpocentek, no, just a normal control file (added by myself with dh_make)
[08:50] <gpocentek> SWAT: could you pastebin your debian/control?
[08:51] <SWAT> gpocentek, http://paste.ubuntu-nl.org/49666/
[08:51] <SWAT> note, it depends on another package I built (the test package)
[08:53] <gpocentek> hum, this is odd, I see nothing wrong
[08:53] <SWAT> me neither. Yet when I install, it does not complain about missing the 'test' package (at all)
[08:53] <gpocentek> there's usually a space between '=' and the version but I don't think it's a problem
[08:53] <SWAT> perhaps I need to add something to my preinst/prerm scripts?
[08:54] <gpocentek> SWAT: soory to ask but... are you really sure that 'test' is not installed?
[08:54] <gpocentek> I can do things like that, that's why I ask :)
[08:54] <SWAT> yeah. Hold on a minute
[08:55] <SWAT> ah, well, it does complain (it just took a long time before I saw the message), so it leaves the package as 'iU'
[08:55] <SWAT> do I need to add something so it just doesn't install from the start?
[08:56] <SWAT> "dependency problems - leaving unconfigured"
[08:56] <gpocentek> hum
[08:56] <gpocentek> if I'm not wrong apt wouldn't install it at all but dpkg tries anyway
[08:57] <gpocentek> i don't think that there's a packaging trick to avoid that
[08:57] <SWAT> ok, I admit I tried it with 'sudo dpkg -i'. So it's normal?
[08:57] <gpocentek> I guess
[08:57] <SWAT> thanks for the time/effort/info
[08:57] <gpocentek> no problem
[08:57] <SWAT> if I'm doing something, I want to do it right
[08:58] <gpocentek> SWAT: I don't know your package, but usually -data packages don't depend onthe 'main' package
[08:59] <SWAT> ok, that's because I actually really want to. Thanks a lot and enjoy the rest of the day :)
[08:59] <gpocentek> just a warning to avoid circular dependencies
[08:59] <gpocentek> ok
[08:59] <gpocentek> thanks :)
[10:06] <LucidFox> persia> Perhaps instead of a debdiff, I could prepare an interdiff from 2.4~preview3 to 2.4.0
[10:06] <LucidFox> (regarding avidemux)
[10:08] <persia> LucidFox: I don't really know anything about avidemux, or what it does, but such an update may make sense.  It really depends on how closely we plan to coordinate with debian-multimedia.  If we're looking for a future sync, it may make more sense to get an update there and merge.  If we're taking a separate path, the interdiff for the new upstream makes more sense.
[10:09] <LucidFox> Then I'll ask Marillat to prepare a new release, and then merge it
[10:09] <LucidFox> (and I'll point him to the Ubuntu changes I made)
[10:10] <persia> LucidFox: If you're in coordination, that sounds best.  Do you want the bug unsubscribed in the meantime, or does the current merge still make sense while waiting for the coordination?
[10:12] <LucidFox> I'd say it still makes sense, because it closes an x264 rebuild bug that wasn't possible with Avidemux 2.3
[10:13] <persia> LucidFox: OK.  I'll take a look at the changes, and if there's nothing particularly insane, push the merge while waiting for the coordination.  Further, I'll un-dup the 2.4 upgrade, and assign to you.
[10:19] <persia> ember_: somerville32: mruiz: You have updated packages on REVU.  Please submit bugs with interdiffs for processing.
[10:20] <persia> (or if there is already a bug, ask someone to archive the REVU entry)
[10:22] <persia> LucidFox: Is MMX processing broken in some way?
[10:24] <LucidFox> Apparently. I couldn't get ffv1rec to build.
[10:25] <LucidFox> This probably needs an upstream bug report.
[10:25] <persia> LucidFox: For both i386 and amd64?  Odd.  I agree it's upstream.
[10:26] <persia> LucidFox: As a general note, I don't like build-depending on imagemagick: I think it's better to create the files at packaging time, just in case someone wants to tweak them a little to look better.  It's not enough to block me, but just a personal preference.
[10:28] <LucidFox> It's used to create downsized icons.
[10:28] <LucidFox> I'll talk to upstream about that - perhaps they could provide all sizes themselves.
[10:29] <persia> LucidFox: Right, but the resizing algorithms may result in blurry images.  y converting at build-time, there is no way to fix this easily.  I personally prefer a larger diff.gz with the possibility to later fix this than a smaller diff.gz with no possibility to fix it.  On the other hand, there are also arguments for doing it the other way.
[10:30] <LucidFox> Ah, so create a separate XPM for every size?
[10:30] <LucidFox> But those would still need to be converted to PNG at build time...
[10:31] <persia> LucidFox: Rather, create a separate .png for each size, and uuencode them.  uudecode at build time.  Better still if upstream ships all the different icon sizes, hand tuned for best appearance at each resolution.
[10:32] <LucidFox> Ahh.
[10:37] <SWAT> the more people who know how to package the better or not? Would a 'quick packaging howto' be a good thing or not? The number of people who package would probably increase, but the quality could/would be questionable.
[10:38] <persia> SWAT: A quick packaging HOWTO would be great, as long as it is 1) correct, 2) has pointers to relevant external docs & policies, and 3) Doesn't indicate there is one true way to do things.
[10:40] <persia> LucidFox: You've changed a build-depends from libfaad-dev to libfaad2-dev, but the package doesn't seem to build in hardy unless it is changed back to libfaad-dev.  What am I missing?
[10:41] <jpatrick> SWAT: I had a go at it here: http://people.ubuntuwire.com/~jpatrick/tutorials/
[10:42] <persia> jpatrick: Would you like a critique?
[10:42] <LucidFox> Hmm. Now looking at it, hardy renamed the package - it was libfaad2-dev in gutsy, but libfaad-dev in hardy
[10:42] <LucidFox> http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=faad&searchon=names&subword=1&version=all&release=all
[10:42] <SWAT> jpatrick, I'll have a look at it when I have the time (it's very limited atm)
[10:43] <jpatrick> persia: well, not, I have to get used to it
[10:43] <persia> LucidFox: What do you want me to do?
[10:43] <jpatrick> s/well/why/
[10:43] <slytherin> libfaad-dev is correct for hardy
[10:43] <SWAT> persia, maybe I'll have a go at it (depends on my available time)
[10:43] <persia> jpatrick: OK.  I'll dig through.
[10:44] <persia> SWAT: Good luck.  Note that in most cases, work to improve the current WIP packaging guide would be helpful, but there are usually a couple people around willing to review a draft if you want to do something separate, and maybe integrate later.
[10:46] <LucidFox> persia> reuploaded the debdiff
[10:47] <persia> LucidFox: OK.  I'll grab the new debdiff, and try another build.  Thanks.
[10:47] <slytherin> LucidFox: Which bug is this by the way?
[10:48] <persia> bug #163287
[10:48] <ubotu> Launchpad bug 163287 in avidemux "Please merge avidemux 2.4~preview3-0.0 from debian-multimedia.org experimental" [Wishlist,In progress] https://launchpad.net/bugs/163287
[10:52] <slytherin> LucidFox: I think you do need need those many changes to changelog, you can pickup changelog from debian and add hardy entry. But I am not a MOTU, so you can wait for official comments from persia
[10:52] <persia> slytherin: Just for context, this package isn't actually in Debian.
[10:53] <New> :)
[10:53] <slytherin> Oh.
[10:53] <persia> New: You'll get slammed with highlights with that nick: consider changing it.
[10:54] <New> what does mean?
[10:55] <New_cat> ok?
[10:55] <New_cat> :P
[10:55] <persia> New_cat: : We talk about NEW packages and the NEW queue frequently, and it may be difficult to distinguish when people are speaking to you.  Your new nick is more likely to be accurate.
[10:56] <sandyang> ok?
[10:56] <persia> sandyang: Either sandyang or New_cat works well :)
[10:57] <slytherin> anything other than new, build, ftbfs, sync, merge should work. :-P
[10:58] <persia> package and spec are dangerous as well.
[10:58] <geser> bug too
[11:00] <jpatrick> poor Spec
[11:00] <geser> oO(someone with a nick name "bug" would have fun in #ubuntu-bugs)
[11:01] <persia> jpatrick: Yep.  Tends to use slight variations of the nick around here (currently x-*-ting)
[11:01] <jpatrick> haha
[11:02] <SWAT> persia, don't remind me, everytime the SWAT (samba) package is mentioned...
[11:03] <persia> SWAT: How about our universe security team :)
[11:03] <persia> jpatrick: http://paste.ubuntu.com/3039/
[11:04] <jpatrick> persia: the talk was mine
[11:04] <jpatrick> but good point
[11:04] <SWAT> persia, yeah, I noticed that after I became an official member (the bad thing: I have this nick for more than a decade now)
[11:04] <persia> SWAT: I understand.  I don't tend to spend much time in channels dedicated to classical antiquities :)
[11:09] <frenchy> Hi all, do MOTUs action sync requests?  If so, is there anything that I have to do get a sync request actioned?  Re: https://bugs.edge.launchpad.net/ubuntu/+source/me-tv/+bug/178519.
[11:09] <ubotu> Launchpad bug 178519 in me-tv "Please sync me-tv 0.4.19-1 from Debian unstable" [Wishlist,New]
[11:10] <jpatrick> frenchy: we are in Debian Import Freeze
[11:11] <geser> frenchy: any good reason why we should use the sid package and not the current one in hardy?
[11:11] <frenchy> jpatrick: I thought that "Debian Import Freeze" meant that nothing further was imported from Debian without a request.
[11:12] <frenchy> jpatrick: Huh, there's one in Hardy?
[11:12] <geser> frenchy: yes, but we also shouldn't request syncs because we can?
[11:12] <jpatrick> !info me-tv hardy
[11:12] <geser> frenchy: it's still in REVU?
[11:12] <ubotu> Package me-tv does not exist in hardy
[11:13] <geser> I assumed it already passed revu but didn't check
[11:13] <frenchy> geser: It got archived because it made it into sid.
[11:13] <persia> It didn't pass REVU.
[11:13] <persia> Specifically, the reviewer with the right equipment to test encouraged a push to sid, which has been done.
[11:14] <persia> frenchy: Isn't there already an approved sync request for me-tv submitted to the archive-admins?
[11:15] <frenchy> persia: Sorry, don't know.  Is that in BTS?
[11:15] <persia> frenchy: Sync requests are handled in LP.
[11:15]  * persia thinks bug #178519 will be processed next week when the archive-admins return from the holiday break.
[11:15] <ubotu> Launchpad bug 178519 in me-tv "Please sync me-tv 0.4.19-1 from Debian unstable" [Wishlist,New] https://launchpad.net/bugs/178519
[11:15] <frenchy> persia: Yes, https://bugs.edge.launchpad.net/ubuntu/+source/me-tv/+bug/178519.
[11:17] <frenchy> persia: Thank you, that's exactly what I wanted to know.  Did know if it was automatic though.
[11:17] <frenchy> s/Did/Didn't
[11:18] <persia> frenchy: Not automatic after DIF.  Requires the approval of a member of ~ubuntu-dev (in this case, the bug submitter)
[11:18] <frenchy> Shouldn't IRC and watch 'Family Guy' at the same time.
[11:21] <persia> LucidFox: Build failures coming your way :)
[11:22] <frenchy> Sorry, still not quite clear, Philipp is not a member of ~ubuntu-dev, but it looks like someone as definitely linked it into Ubuntu.
[11:23]  * persia points at https://launchpad.net/~pkern/+participation
[11:26] <frenchy> persia: Ohhh ... via MOTU, Ta.
[11:28] <Essope> hi
[11:30] <sandyang> hi
[11:30] <sandyang> so quietly~~~
[11:34] <frenchy> So if it does get sync'd ... is that it?  What happens with bug fixes from there?
[11:36] <geser> frenchy: if you get important bug fixes uploaded to Debian you can ask for a sync again (till FF) or ask for an upload to Ubuntu directly
[11:38] <sandyang> If the human came be here, I ll start to tell the story, some people want listen?
[11:39] <frenchy> geser: Thanks, FF isn't till 14 Feb, right?  I'm sure that there'll be a lot of improvements up until that time.  But I'm hoping to make one last sync request ... would that be frowned upon?
[11:40] <frenchy> Sorry, this is my first introduction to MOTU.
[11:42] <persia> frenchy: No need to apologize.  Everyone needs to learn once.  It's safe to sync up to FF as long as there is a good reason for the sync (more than just an updated release).  After FF, bugfix uploads are still welcome (and may be in the form of syncs), but no new features are allowed, and string changes are not preferred.
[11:43] <frenchy> persia: Thank you.
[12:09] <DarkSun88> Hi all.
[12:18] <liri> The PackagingGuide on the wiki deals with compiled packages and I was wondering if there's a Guide or general information on packaging a web application (scripts).
[12:19] <mruiz> hi all
[12:20] <slytherin> liri: is there anything specific you want to package?
[12:21] <persia> liri: http://webapps-common.alioth.debian.org/draft/html/ may be of interest
[12:23]  * persia wonders if dbconfig-common might also be interesting for non-web applications that have a database dependency
[12:25] <persia> pochu: did you ever get feedback from Festor about the aMule import?
[12:31] <\sh> moins
[12:31] <\sh> guys, does anyone has problem creating or updating a debootstrap chroot/or pbuider chroot ?
[12:32] <dfiloni> pochu: the 2.8.6.1 version of wxwidgets2.8 fixs amule bugs?
[12:32] <persia> \sh: A couple people have reported issues in the last 24 hours.  I don't remember seeing a posted solution.
[12:33] <persia> dfiloni: Quite likely.  aMule tends to track upstream WX fairly closely, and doesn't seem to try to work around the weaknesses of WX.
[12:35] <dfiloni> persia: ok thanks for the reply. Did you have a merry christmas?
[12:36] <liri> persia: yeah, I'd like to package my project. I actually already started doing it a while ago and stopped for lack of time (I can provide you with the url where you can find the directory structure of my packages if you'd like to review it and comment on it which I will welcome gladly)
[12:37] <liri> persia: I'm going over that link, seems quite important, thanks.
[12:37] <\sh> persia, looks like during update that /dev is not bind mounted properly and during creating something is wrong with the /var partition
[12:40] <persia> dfiloni: Yes.  Thank you.  You?
[12:40] <persia> liri: If you'd like to submit your package for review, best to prepare a candidate for REVU.
[12:41] <persia> \sh: Hmm...  I don't know much about chroot creation, but that sounds like some sort of skew.  Has there been a debootstrap update since the default kernel switch?  Might that make a difference?
[12:41] <dfiloni> persia: I had a good christmas too
[12:42] <\sh> persia, didn't see any...but I'll do a reinstall of this system here and do another upgrade to hardy...so I'll can check again.
[12:42]  * \sh needs to use some LVM based install now...
[12:43] <liri> persia: that link on webapps is great as policy and general guide, though I was hoping for a more practical guide on creating the package
[12:44] <persia> \sh: LVM is nice :)  I can't seem to even create a chroot now (as I've my play area mounted with nodev).  Maybe there's some new security checks in place?
[12:45] <\sh> persia, do you get any "/var blabla mounted with noexec, nodev" message?
[12:45] <persia> liri: I don't think that exists.  You'd do best to follow the guide for normal applications, skip the part that compiles stuff, and then follow the draft webapp policy.
[12:46] <persia> \sh: Yes.  precisely.  it is mounted nodev, so this is (somewhat) expected behaviour.  It's also new behaviour, as I've created chroots on this mount point previously.
[12:47] <\sh> persia, and now try to update your hardy chroot or what ever pbuilder chroot you have...it gives you another (different) error message after trying to install libc5
[12:47] <\sh> aeh libc6
[12:47] <liri> persia: alright, I'll work the basic package and ask around when I get to the part of how to organize the webapp files for distribution later
[12:47] <persia> \sh: I don't use pbuilder.  I've not had any issues updating my LVM scratch partitions that I snapshot for sbuild.
[12:47]  * persia updates again, just in case...
[12:48] <liri> persia: the login to the revu system is only for motus and alike?
[12:49] <persia> liri: Login is only available for those who have submitted packages.  In order to submit packages, you must 1) have a signed CoC, 2) have uploaded your GPG key to launchpad, and 3) have joined the Contributors of packages for ubuntu universe group.
[12:49] <persia> !revu | liri
[12:49] <ubotu> liri: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[12:50] <persia> \sh: I can't reproduce the update issue.  It either doesn't affect amd64, is pbuilder specific, or is the result of something special for your chroot.
[12:50] <\sh> persia, it affects actually amd64 and i386...(/me has a x86_64 install here and use i386 and amd64 chroots)
[12:51] <mruiz> hi all. How is the procedure to fill a unmet dep bug? I solved one :-)
[12:51] <persia> \sh: Then I suspect it's either pbuilder or your mirror.  Having both chroots be odd makes it look non-local.
[12:51] <\sh> report the bug, add the debdiff and subscribe uus
[12:52] <\sh> persia, well, mirror is the archive.ubuntu.com ,-) and it's there since yesterday when I tried to update...well
[12:52] <persia> mruiz: Adjust control (or whatever), update the changelog, test build, verify the solution, attach a debdiff, subscribe the sponsors.
[12:53] <persia> \sh: I update my minimal partitions (sid/gutsy/hardy) two or three times a day, and haven't encountered that, with the same mirror.  Odd.
[12:53] <liri> persia: I've joined the launchpad group of contributes but I don't remember about the others so I'll check it out
[12:54] <persia> liri: "liran"?
[12:54] <liri> persia: yeap
[12:55] <persia> Yep.  Submit a signed CoC and your GPG key, and ask someone here to update the REVU keyring, and you'll be able to upload.  You might want to add your IRC nick to your LP page as well, just to make it easier for people to identify you.
[12:56] <liri> persia: I'm updating the gpg as we speak, thanks. I'm not seeing anything about a CoC on the REVU page, what's that about?
[12:57] <persia> liri: It's the Ubuntu Code of Conduct.  Says you'll be nice and good to others while working on Ubuntu.  Further information should be available from your LP page.
[12:59] <liri> persia: ahh alright
[12:59] <liri> persia: I promise to be nice :-)
[13:11] <\sh> persia, hmm...well, I see after reinstalling this server...
[13:23] <liri> persia: alright I'm all set up with the requirements
[13:24]  * persia syncs the keyring
[13:26] <liri> thanks.
[13:26] <liri> I'll upload the package later for you guys to review and comment on
[13:26] <persia> liri: You'll want to wait at least 30-45 minutes for the keyring to sync (I'll let you know when it's done)
[13:28] <imbrandon> moins all
[13:28] <imbrandon> heya persia , looks like Mako will be in your neck of the woods the next few weeks ( via planet.debian.org )
[13:29] <mruiz> hahaha
[13:29] <imbrandon> or i guess planet.ubuntu.com too :)
[13:29] <mruiz> good morning imbrandon
[13:29] <imbrandon> heya mruiz
[13:29] <persia> imbrandon: Yep.  Looking forward to an activity.  Don't know if the visit will last to the 12th for TLUG though.
[13:30] <imbrandon> cool-i-o , dunno if you have met him before or not, he is a really cool person, you'll enjoy meeting him i'm sure ( if you get the chance )
[13:31] <imbrandon> i caught up with him 2 or 3 times, been really fun
[13:32] <imbrandon> plus now a member of the FSF board :) lol
[13:34] <persia> Actually, it's a current topic of interest here.  New government support and grants has changed things a bit: there's worry that FOSS acceptance in Taipei may make Akihabara less of a special place.  RMS did a speaking tour recently (October) with four events in Tokyo.  Now if only the remaining ubuntu-ja patches didn't break things for everyone else...
[13:34] <StevenK> imbrandon: So, have you fixed all of my problems with apt-mirror? :-)
[13:35] <imbrandon> StevenK: yup actualy i have, i got them in my bzr branch but not in main svn yet, going to commit them today and prob make a release sometime today
[13:35] <StevenK> Woot!
[13:35] <imbrandon> http://people.ubuntuwire.com/~imbrandon/bzr/apt-mirror/trunk
[13:35] <imbrandon> bzr branch that if you want it early
[13:35] <imbrandon> i tested it quite thourghly last night
[13:36] <imbrandon> it has the pacaking and all in that bzr if you wanna just debuild it
[13:36] <imbrandon> or you can wait and i'll try and get white to upload a new release today sometime ( once i make a new release tarbal etc )
[13:36] <StevenK> Why is it in bzr and svn?
[13:37] <imbrandon> i use bzr localy and such, then bzr-svn to merge it back to the main branch when i'm happy with it
[13:37] <imbrandon> demitry only knows and cares to know sf.net svn, and bzr-svn allows me to use both
[13:38] <imbrandon> with the same co
[13:40] <imbrandon> i got to thinking
[13:41] <imbrandon> StevenK: would it not be trivial to make the postmirror_script support any scripting lang supported by the host if i just make the requirement that its executable ?
[13:41] <imbrandon> like perl or shell or batch ( windows )
[13:42] <imbrandon> bu system() on the script directly instead of system("/bin/sh $script") ??
[13:42] <imbrandon> s/bu/by/
[13:43] <StevenK> As long as there is a useful error message if it isn't executable
[13:43] <imbrandon> k, personaly i think that would be more usefull , so people can use anything they want, yea good call, lemme look into that
[13:43] <imbrandon> buth the /bin/sh way is currently "in it"
[13:47] <imbrandon> btw is there a big diffrence between exec() and system()  ? i read the docs but it dident seem to matteer much
[13:47] <StevenK> system() does a fork() and then a exec()
[13:48] <StevenK> exec() takes over your current process
[13:48] <StevenK> (system() also has the parent wait())
[13:48]  * StevenK waits for imbrandon to say "what?"
[13:48] <StevenK> :-P
[13:48] <imbrandon> heh no i got all that
[13:49] <imbrandon> in otherwords i probably wanna stuck with the system() for the script call, but adding a wait probably would be a good idea to trap error codes
[13:49] <StevenK> You don't need to wait(), Perl will do it for you.
[13:49] <Essope> yay, less bugs.
[13:49] <imbrandon> k
[13:53] <StevenK> imbrandon: Better, if it's executable, execute it, but if it's not, assume /bin/sh
[13:53] <imbrandon> ahh good idea
[13:54]  * Essope hits a few more with the invalid stick
[13:54] <cbx33> hey hey peeps
[13:54] <persia> liri: Sync complete.
[14:01] <imbrandon> heya cbx33
[14:02] <cbx33> hi imbrandon
[14:02] <cbx33> doh this is driving me nuts
[14:02] <cbx33> abcde won't work after I change my cd drive from PS to SS
[14:03] <cbx33> well i have to specify the device
[14:04] <imbrandon> PS / SS ?
[14:04] <imbrandon> ohhh nevermind
[14:04]  * imbrandon is dumb
[14:06] <cbx33> primary slave
[14:06] <cbx33> secondary slave
[14:18] <StevenK> Oh, that's so useful.
[14:18] <StevenK> g++ ... -g -Wall ... >/dev/null 2>&1
[14:18] <imbrandon> hahah
[14:18] <imbrandon> looks like a cmake call :) j/k
[14:18] <persia> It's the new trick for avoiding compiler warnings
[14:19] <StevenK> "If I don't see them, they don't exist"
[14:19] <imbrandon> head in sand trick
[14:19] <Essope> burying your head in the sand is *always* effective, yes.
[14:19] <persia> Precisely.  Only warnings printed to the console count (M-x ostrich)
[14:20] <imbrandon> StevenK: http://paste.ubuntu.com/3044/
[14:21] <Essope> perhaps that could become an official MC proceedure.
[14:21] <imbrandon> StevenK: that pretty much what you ment ?
[14:25] <StevenK> imbrandon: Works for me.
[14:25] <StevenK> imbrandon: I think it should go after the cleaning code.
[14:26] <imbrandon> yea it its, its the very last thing
[14:27] <imbrandon> s/its/is
[14:28] <StevenK> imbrandon: You'll upload a 0.4.6 targetted at Dapper in your PPA?
[14:29] <imbrandon> StevenK: yup, here in about ~15 minutes or so
[14:29] <StevenK> Then I'll see it in the morning
[14:29] <imbrandon> k
[14:29] <imbrandon> i;m just ruuning it once or twice more to "make sure" then i'll commit to PPA and main svn and make a release
[14:29] <imbrandon> i have enough changes for a point release
[14:30] <StevenK> You can remove the note from the POD docs, too
[14:30] <dfiloni> any news about the new pidgin version?
[14:30] <imbrandon> yup yup, i just noticed that
[14:30] <StevenK> I only just remembered :-)
[14:32] <imbrandon> i only did about 10 minutes ago heh
[14:33]  * imbrandon looks how to spell StevenK's last name for the changelog
[14:37] <StevenK> I'd prefer to be attributed like my IRC real name
[14:37] <mruiz> I filled the bug 178869, related to unmet deps. Hobbsee marked it as duplicate of a pbuilder bug... I replied her, but I want to know if I'm correct :-)  Comments?
[14:37] <ubotu> Launchpad bug 178869 in pbuilder "[UNMETDEPS] gnome-voice-control has unmet dependencies (dup-of: 125107)" [Undecided,New] https://launchpad.net/bugs/178869
[14:37] <ubotu> Launchpad bug 125107 in pbuilder "[gutsy] pbuilder-satisfydepends-gdebi can't resolve pure virtual build-depends" [Undecided,New] https://launchpad.net/bugs/125107
[14:38] <StevenK> Like all Steven's, I'm doomed to trying to crowbar the 'n' off my name.
[14:38] <persia> StevenK: Then why is it part of your IRC nick?
[14:38] <StevenK> Because ... shut up.
[14:38] <StevenK> :-P
[14:38] <imbrandon> StevenK: heh would you rather Steve Kowalik in the CHNAGELOG ? hehe
[14:39] <StevenK> imbrandon: Right
[14:39] <imbrandon> k
[14:39]  * StevenK runs off to bed, it being 1:40am
[14:39] <imbrandon> gnight :)
[14:39] <imbrandon> thanks for the help
[14:42] <persia> mruiz: How were you testing the installation?  I can install gnome-voice-control in hardy just fine from a minimal snapshot chroot.  I suspect I can build it from sbuild as well: you may just have encountered the pbuilder bug and had it affect the package build.
[14:42] <mruiz> persia, I built the package with pbuilder
[14:43] <mruiz> after some modifications in control file, I got a successful build
[14:44] <persia> mruiz: That's not a very good unmetdeps test.  pbuilder helps test package building, but neither matches the buildds nor a target installation.  It's a dup.  There might be a FTBFS bug: checking now...
[14:45] <persia> mruiz: Yep.  I can reproduce the FTBFS in sbuild.  undup & retitle if you like.
[14:45] <mruiz> persia, then is a FTBFS bug ?
[14:45] <persia> mruiz: Not building is FTBFS.  Not installing is unmetdeps
[14:47] <persia> mruiz: You can check the current build status from https://launchpad.net/ubuntu/hardy/+source/gnome-voice-control/0.2-0ubuntu4, which seems to indicate a problem, as the last update was 8th October, and it's still not built.  Your debdiff may help.
[14:48]  * persia notes that as it also FTBFS in gutsy, this may be SRU worthy, but confirmation would be required from the SRU team.
[14:48] <mruiz> persia, it is possible to reuse the bug report or do I have to open a new one?
[14:50] <persia> mruiz: Definitely possible to reuse.  unmark the dup, set the pbuilder task invalid, retitle as FTBFS, update the description, etc.
[14:59] <imbrandon> StevenK: ( i know your afk but this is for backlog ) uploaded 0.4.6-0~dapper1 to my dapper PPA, should be built by the time you wake/get to it
[15:01]  * GoldenPony thought StevenK was known not to read backlog
[15:01] <imbrandon> no idea, he'll probably just check the PPA tomarrow without reading it
[15:02] <persia> GoldenPony: sometimes he catches it.  I suspect it depends on traffic.  If we all post a lot, we can likely overrun his check buffer :)
[15:03] <GoldenPony> persia: fair enough
[15:03]  * GoldenPony ponders bed...and not waking up again
[15:03]  * persia suspects that is difficult without careful planning
[15:03] <GoldenPony> seeing as laserjock refuses to do his duty, etc...
[15:04] <GoldenPony> shame on him.
[15:06]  * GoldenPony throws a rubber chicken at imbrandon, persia, and StevenK 
[15:06] <imbrandon> heh
[15:06]  * persia chews the rubber chicken happily
[15:06] <GoldenPony> oookay!
[15:07] <GoldenPony> strange persia.
[15:08] <mruiz> persia, FTBFS bug is updated :-)
[15:09] <LucidFox> Why are builds so slow today?
[15:09] <LucidFox> both in PPA and in Ubuntu itself...
[15:10] <persia> LucidFox: slow?  Not broken?
[15:10] <LucidFox> Not broken... just idle :)
[15:10] <LucidFox> I have three PPA builds queued three hours ago, and they're still "pending"
[15:11] <Essope> ppa is broken.  see /topic
[15:12] <GoldenPony> there's a dead parrot sketch reference in that, i'm sure.
[15:13] <persia> LucidFox: Consider that a good thing.  If they are idle, they won't have to be given back :)
[15:18] <superm1> morning folks. i've got a revu if anyone is interested: http://revu.tauware.de/details.py?package=mythbuntu-common
[15:19] <mruiz> how is the procedure to request an SRU for a FTBFS fix?
[15:19] <Essope> mruiz: dance frienziedly, in a circle, pleading for the gods of SRU to help you
[15:19] <Essope> and to appease all your desires
[15:19] <mruiz> Essope, hahaha
[15:21] <imbrandon> !SRU | mruiz
[15:21] <ubotu> mruiz: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[15:32] <persia> superm1: Looks clean, except for the changelog.  See the comment, and be sure to archive if you are uploading.
[15:32] <superm1> persia, ah okay thanks.  yeah i missed that.
[15:33]  * persia advocates linda
[15:35] <superm1> I must have to backport another linda from hardy, my linda didn't catch it :)
[15:37] <persia> superm1: You aren't feeding her properly.  linda likes "-v -f long -t E,I,W,X": it makes her voluble and freindly.
[15:37]  * superm1 makes an alias in his bashrc
[15:38] <persia> superm1: If you're doing that, consider always passing "-iIv" to lintian as well.
[15:38] <superm1> yeah i usually run both with -i, but never used other switches
[15:40] <persia> superm1: For lintian, the "I" is the important one.  For linda, it's the "-t E,I,W,X".  The rest is just to get them to explain what they mean.
[15:43] <soc> hi
[15:44] <soc> has someone been able to compile kde4 (from subversion) with ubuntu's soprano (1.99~rc2 afaik)?
[15:44] <soc> it fails since a week with errors in libdolphinprivate ...
[15:45] <soc> i would hate it if i had to start compling things from kdesupport again :-(
[15:45] <imbrandon> soc: your likely to get far more help with kde4 stuff in #kubuntu-devel
[15:45] <imbrandon> likely something just needs to be updated
[15:47] <soc> imbrandon: it's clearly a soprano error
[15:48] <soc> soprano 1.99 is required to build kdebase
[15:48] <soc> soprano 1.99~rc2 is in ubuntu
[15:49] <soc> and now the question is if i'm the only one experiencing that error or if thats a problem with the ubuntu package ...
[15:49] <soc> because i'd expect that 1.99 and 1.99~rc2 are compatible else it wouldn't make sense to put sorpano in there, if nothing compiles with it anymore ...
[15:53] <soc> btw, why are the builds failing? :-)
[15:53] <jpatrick> soc: bad update thing
[15:54] <soc> gcc?
[15:55] <jpatrick> something with libstdc++6 i think
[16:01] <LucidFox> Does Hardy already use PulseAudio by default?
[16:02] <soc> ah ok
[16:22] <bluefoxicy> I still cannot find any easy way to identify why a package was removed
[16:22] <bluefoxicy> been googling for ubuntu libsafe {dfsg,feisty,remove} etc...
[16:23] <bluefoxicy> meh I'm getting nowhere
[16:27] <geser> bluefoxicy: http://people.ubuntu.com/~ubuntu-archive/removals.txt
[16:27] <geser> (From Debian) long-standing RC bugs, gives a false sense of security
[16:39] <DarkSun88> Hi all
[17:28] <warp10> If someone is willing to review a package, I jave just uploaded tennix (a simple 2D tennix game) on REVU. Thanks in advance! http://revu.ubuntuwire.com/details.py?package=tennix
[19:18] <awen_> what's with the build system?
[19:19] <cheguevara_> glibc is b0rked
[19:20] <awen_> that's kind of a problem
[19:46] <cyberix> So 24.12. was a REVU day and 31.12. will be the next one?
[19:48] <geser> cyberix: sort of, if you find a reviewer here that day
[19:51] <ion_> Hi
[19:54] <ion_> Please review http://revu.tauware.de/details.py?package=hardware-connected and http://revu.tauware.de/details.py?package=apt-mark-sync
[20:41] <imbrandon> hum the automount(gnome) stuff is mostly hal? i have a strange problem
[20:43] <imbrandon> i have a 2gb sd card that if i leave it in the camera , and hookup via usb cable , it mounts and works fine, if i take it  out and put it in my card reader it says invalid partition table
[20:43] <imbrandon> but both ways work in windows :(
[20:44] <imbrandon> oh well, onto something more productive
[20:53]  * TheMuso sees a few hardy-changes mails, and wonders whether its worth uploading at this point, if builds are failing, as you have to get them given back later.
[20:56] <imbrandon> heya TheMuso , well if they are given back via a mass giveback then they will be at the front of the queue :)
[20:56] <TheMuso> imbrandon: Yeah I know, but still.
[20:57] <imbrandon> yea kinda sucks they are still broke, couldent have happened at a worse time
[20:57] <TheMuso> What causes them to break?
[20:58] <imbrandon> a libstc++6 from debian iirc
[20:58] <imbrandon> broke the chroots
[20:58] <TheMuso> Lovely.
[20:58] <imbrandon> not 100% sure but thats what i gathered from -devel last night
[20:59] <TheMuso> Right.
[20:59] <imbrandon> lamot breifly looked at it and said he couldent fix it, would likely have to be infinity
[20:59] <imbrandon> iirc
[20:59] <imbrandon> lamont*
[20:59] <TheMuso> right
[21:00] <imbrandon> ohhh btw between me and StevenK we got the bug fixes and features you need for apt-mirror
[21:01] <imbrandon> ( and even a migration path so you dont have to redownload *everything* )
[21:02] <imbrandon> its in svn at sf.net right now ( commited it all a few hours ago ) and i built a package to use on dapper in my PPA ( not sure if it built yet )
[21:02] <TheMuso> imbrandon: You rock. I'm off for breakfast now, but I'll talk to you about it after.
[21:02] <imbrandon> kk
[21:10] <TheMuso> imbrandon: Whats the address to fetch it?
[21:11] <imbrandon> svn https://apt-mirror.svn.sourceforge.net/svnroot/apt-mirror/trunk
[21:11] <TheMuso> Thanks. I thought sourceforge only offered cvs.
[21:12] <imbrandon> nope svn too
[21:12] <TheMuso> wow
[21:12] <TheMuso> Is there a delay like there is for CVS?
[21:12] <imbrandon> not that i know of, seems to commit right away
[21:13] <imbrandon> i dident know there was a cvs delay
[21:13] <jonnymind> Hello everyone,.
[21:13] <imbrandon> i even use bzr-svn with it 99% of the time
[21:13] <Amaranth> imbrandon: pub cvs is delayed a couple hours
[21:14] <Amaranth> They do a batch copy or something to save resources
[21:14] <imbrandon> Amaranth: ahh, no then there is no delay
[21:14] <Amaranth> instead of moving each commit over
[21:14] <imbrandon> well with svn there is no pub and priv, its both the same url
[21:15] <imbrandon> just one is authenticated :)
[21:15] <imbrandon> so i guess thats why no delay
[21:16] <TheMuso> imbrandon: What do I need to know re the migration path?
[21:16] <imbrandon> TheMuso: your using debmirror right ?
[21:16] <imbrandon> ( msotly )
[21:17] <TheMuso> Yes
[21:17] <emgent> heya imbrandon :P
[21:18] <imbrandon> mv /location/of/current/{dists,pool} to /var/spool/apt-mirror/mirror/ftp.host.from.mirrorlist.com/
[21:18] <imbrandon> then it should pick it up
[21:18] <TheMuso> imbrandon: Right
[21:18] <imbrandon> if you have the installer components rsynced , be sure to use the "skip-clean" lines in the mirror.list
[21:18] <imbrandon> so clean.sh dosent want to delete them as "old packages"
[21:19] <imbrandon> heya emgent
[21:19] <TheMuso> imbrandon: SO to mirror i18n, indices etc, I jst ensure they don't get cleaned?
[21:20] <imbrandon> correct, and rsync them via the new postmirror_script
[21:20] <imbrandon> ( its in the mirror.list config )
[21:20] <TheMuso> Where is the postmirror script?
[21:20] <TheMuso> ok
[21:20] <imbrandon> default its in /var/spool/apt-mirror/var/postmirror.sh
[21:20] <imbrandon> but you can set it to anywhere in the mirror.list
[21:21] <TheMuso> imbrandon: Right, but does it come with a script to do that? Or do I have to write that myself?
[21:21] <imbrandon> and it can be anything ( e.g. perl , python, shell, etc ) as long as its executable, if its not execurtable it will try to run it with /bin/sh
[21:21] <imbrandon> no i dident make a sample script yet
[21:21] <TheMuso> imbrandon: Right, what variables does one use to address the correct dirs?
[21:22] <imbrandon> huh?
[21:22] <imbrandon> oh hum, never thought about that
[21:22] <imbrandon> the script should get those vars passed to it huh ? heh
[21:23]  * imbrandon thinks
[21:24] <imbrandon> for the moment i guess you will have to just know what the paths are in mirror.list that you set
[21:24] <imbrandon> but i can work out a way to pass the vars soonish
[21:25] <imbrandon> default everything is below /var/spool/apt-mirror/
[21:26] <TheMuso> imbrandon: Yeah I know, I'm going to change that. Where else can you have a mirror.list? In your home dir?
[21:26] <TheMuso> I'd rather not run it system wide.
[21:36] <imbrandon> sure
[21:36] <imbrandon> you can put it anywhere
[21:36] <imbrandon> just call apt-mirror with the mirror.list as the only argument if its not in /etc/apt/mirror.list
[21:37] <imbrandon> apt-mirror /home/themuso/etc/mirror.list , or whatever
[21:38] <imbrandon> ok afk ~1 hour, or so, bbiab
[21:40] <TheMuso> Ok thanks imbrandon.
[22:04] <nxvl> how is with the new debian changes? i have a change which solves an ubuntu bug, should i merge or just apply the patch?
[22:21] <norsetto> nxvl: if its for hardy I would say merge, what is it?
[22:22] <jonnymind> Hello ppl; I have a couple of questions.
[22:23] <jonnymind> Justasec
[22:23] <jonnymind> I am releasing a new official version of the package at bug 174470
[22:23] <ubotu> Launchpad bug 174470 in ubuntu "Package for the Falcon Programming Language" [Wishlist,In progress] https://launchpad.net/bugs/174470
[22:24] <jonnymind> Is it against the policy to allow direct download of the package I am offering here before it is approved?
[22:24] <jonnymind> s/offering/submiting/
[22:27] <nxvl> norsetto: Bug #178046
[22:27] <ubotu> Launchpad bug 178046 in dillo "dillo failed to unpatch" [Undecided,Confirmed] https://launchpad.net/bugs/178046
[22:28] <norsetto> jonnymind: IMO, its your package, you are free to do what you want with it as long as you don't release it under the ubuntu umbrella (for instance with an ubuntu version).
[22:30] <jonnymind> I see.
[22:32] <jonnymind> Ok, I will release it as generic "debian" package.
[22:32] <jonnymind> Btw, what's the current debian version tag?
[22:32] <jonnymind> The thing that must be put in the changelog?
[22:32] <jonnymind> sid; ?
[22:34] <norsetto> jonnymind: for debian you mean?
[22:34] <jonnymind> Yes. I'd like to provide at least a .deb package.
[22:35] <norsetto> nxvl: I don't see why we should wait for a merge, unless they are telling you that its coming in the next couple of weeks or so
[22:36] <norsetto> jonnymind: what I mean is that this is distribution dependant; I guess you mean the distribution in package_name (version) distribution, urgency ?
[22:37] <jonnymind> yes
[22:37] <norsetto> jonnymind: thats unstable for debian sid and hardy for ubuntu development
[22:37] <jonnymind> I want to provide a deb package (which is reasonabily ok, I think already 99% or 100% policy compliant), but I wouldn't want to offedn anyone.
[22:38] <jonnymind> I see, thanks
[22:39] <psusi> I'm updating a package and in the process, switched to a new upstream release... when I debuild -S -us -uc, it finds the new .orig.tar.gz, but decides not to upload it thinking this is not the first release from upstream... how can I make it consider the .orig new?
[22:39] <norsetto> jonnymind: its archive dependant so you may as well use your own so that you surely won't "offend" anyone
[22:40] <jonnymind> My own?
[22:40] <psusi> and am I using the correct new version string?  I went with -14-0ubuntu1 since we have diverged from debian
[22:40] <psusi> which is still on -13
[22:41] <jonnymind> Like not unstable nor ubuntu, anything will do, right?
[22:41] <norsetto> jonnymind: yes, you said you were going to distribute it, so I guess you will set up a local archive, or will you just give a link to the .deb?
[22:41] <jonnymind> atm, just link to the deb.
[22:41] <jonnymind> I may provide an archive in future, though.
[22:42] <jonnymind> But I'd rather prefer to support distros than creating an archive.
[22:42] <norsetto> jonnymind: use jonnymind then ;-)
[22:43] <jonnymind> Fine, I got the point. Thanks.
[22:47] <DarkSun88> Hi
[22:48] <nxvl> norsetto: so, my debdiff is fine?
[22:48] <norsetto> nxvl: I don't know
[22:49] <nxvl> norsetto: what i was asking is, in that case did we need to merge or just apply the patch, and upload?
[22:49] <nxvl> norsetto: whish is the best practice
[22:49] <nxvl> which*
[22:49] <norsetto> nxvl: to merge we need a package to merge from, there isn't any at the moment, right?
[22:49] <nxvl> norsetto: i mean fine as a debdiff is what i should do
[22:49] <nxvl> norsetto: right
[22:50] <nxvl> norsetto: the patch was posted some hours ago
[22:50] <nxvl> so i don't thing there is a new release yet
[22:51] <norsetto> nxvl: so, unless your contacts in debian are telling you that they plan to release a new package soon just seek sponsoring for your debdiff
[22:51] <norsetto> nxvl: they might, so, ask them and decide on the base of what they tell you
[22:52] <nxvl> norsetto: ok, that is what i was asking, so if they release it before someone sponsors my diff i merge it
[22:52] <nxvl> ok, i will checkl
[22:52] <nxvl> :D
[22:52] <nxvl> thnx
[22:52] <nxvl> bbl
[22:52] <norsetto> nxvl: np
[22:54] <jonnymind> norsetto: can I dput in the revu the new version (with a changed version number) of a package without further notice?
[22:55] <norsetto> jonnymind: sure, its a new version because its a new upstream revision I guess?
[22:56] <jonnymind> yes
[22:56] <jonnymind> crystalized 0.8.5 into even number 0.8.6 for official release.
[22:58] <psusi> I'm updating a package and in the process, switched to a new upstream release... when I debuild -S -us -uc, it finds the new .orig.tar.gz, but decides not to upload it thinking this is not the first release from upstream... how can I make it consider the .orig new?
[22:58] <psusi> and am I using the correct new version string?  I went with -14-0ubuntu1 since we have diverged from debian which is still on -13
[22:59] <TheMuso> imbrandon: Does apt-mirror support ftp downloading?
[23:03] <imbrandon> TheMuso: yea, it supports whatever wget supports , so yes
[23:03] <TheMuso> imbrandon: Great, thanks.
[23:03]  * TheMuso will migrate over to it very shortly then.
[23:03] <imbrandon> :)
[23:04] <imbrandon> lemme know of any issues and i'll try to get them fixed asap
[23:04] <imbrandon> before i make an "official"  0.4.6 tarbal
[23:04] <TheMuso> Ok.
[23:13] <jonnymind> Thanks ppl and good night!
[23:20] <norsetto> g'night all