[00:55] <pochu> tacone: best is to ask questions here or in the mailing list... but if you want a mentor, ask for one in ubuntu-motu-mentors@l.u.c
[00:55] <pochu> tacone: to get started look at https://wiki.ubuntu.com/MOTU/GettingStarted
[00:56] <tacone> ok, pochu, thank you
[00:57] <pochu> no problem, and welcome :-)
[00:58] <tacone> pochu: one thing not so clear to me, is how to really start
[00:58] <tacone> I mean, reading the wiki, you are supposed to already have contributed something.
[00:58] <tacone> am I wrong ?
[00:59] <crimsun> to ask for a mentor?  You do not have to have contributed, no.
[00:59] <tacone> nice, I'll try to get one then :)
[01:14] <jdong> ScottK: what'd you say was up with clamav 0.93? is that the release we are handling as a pre-backport?
[01:54] <bddebian> Heya gang
[02:03] <crimsun> bddebian: 'lo.
[02:03] <crimsun> bddebian: thanks for the trang fix-build, BTW.
[02:03] <bddebian> Heya crimsun
[02:03] <bddebian> Ah, NP
[03:58] <emgent> morning
[04:15] <CyberMatt> middle of the night for me
[04:20] <jdong> superm1: <humor> what do you think about ipod-touch-convenience using -o Ciphers=arcfour?</humor>
[04:22] <superm1> jdong, could you even come up with a justifiable argument for that :)
[04:23] <jdong> superm1: 2.2x transfer throughput for syncing?
[04:23] <superm1> lol
[04:23] <superm1> i think you hit limitations on wireless BW...
[04:23] <jdong> which is a big deal loading up a 8GiB video collection
[04:24] <jdong> superm1: actually no the ARM core in these things is disappointingly short when it comes to SSH :(
[04:24] <jdong> top shows sshd pegging
[04:24] <jdong> maybe that means I need to go dropbear instead of openssh
[04:24] <superm1> what we really need is samba or nfs ported to it
[04:24] <superm1> although maybe a ftp daemon would suffice too
[04:25] <jdong> superm1: well surely arcfour is still more secure than FTP ;-)
[04:25] <jdong> what we *really* need is to rev engineer the USB protocol.
[04:26]  * superm1 doesn't want to know about the government secrets that jdong passes over ssh to his ipod touch
[04:26] <superm1> if I even knew where to start on reverse engineering a protocol, i'd be all game for that
[04:26] <jdong> superm1: I think transmitting songs in cleartext fits some RIAA "making available" argument? :D
[04:26] <superm1> haha
[04:26] <jdong> and considering how anally supportive MIT is of the RIAA I don't take any chances.
[04:26] <jdong> :(
[04:27] <superm1> i'd anticipate the easiest way to capture the packets is via vmware or a similar VM
[04:28] <superm1> and a packet capture layer on linux
[04:28] <jdong> superm1: meh Windows makes it even easier, there's a nice stack of USB snooping tools for Windows that hooks into the kernel layer already
[04:28] <jdong> superm1: and iTunes has a Windows port :)
[04:28] <jdong> or we could use DTrace on OS X oh wait that's locked down....
[04:28] <jdong> :P
[04:28] <superm1> well then why hasn't anyone done this?
[04:29] <jdong> superm1: I'm not sure if anyone has. Certainly I don't think jailbreaking is an appropriate solution to syncing the Touches with Linux
[04:29] <superm1> well in fairness, everyone i know that has one has only purchased it for the purpose to jailbreak it...
[04:30] <jdong> superm1: well I didn't originally but I eventually had to.
[04:30] <superm1> "had to"?
[04:30] <jdong> superm1: I was fine living with what Apple gave me until the $20 apps update nonsense, and syncing it with Ubuntu
[04:31] <superm1> really?  i couldn't use this w/o the last.fm client on there
[04:31] <jdong> superm1: and then I got into a brief period of trying to hack around the insides of the iPod Touch only to figure out that this game's no fun with Apple's antagonism
[04:31] <jdong> superm1: I use my iTouch primarily as a video watching platform. The thing is amazing -- it decodes desktop-resolution hi-res H.264 without skipping a beat
[04:32] <superm1> use handbrake for the transcoding normally?
[04:34] <jdong> actually I use an uncastrated ffmpeg mostly
[04:34] <superm1> woah.  crazy talk
[04:34] <jdong> because I was unhappy with handbrake's lack of input options.
[04:34] <jdong> but for DVDs yes I'll use handbrake
[04:35] <superm1> someone on my team put together a nice transcoding post recording job for myth to bring stuff to h264, but i haven't started to use it because i think i'd prefer to watch it on my LCD tv
[04:35] <jdong> I'm working on converting my ffmpeg scripts to a mencoder+faac+x264-bin backend
[04:35] <jdong> that way it can be usable with multiverse out of the box
[04:35] <jdong> because it seems like ffmpeg is headed in the opposite direction here in Ubuntu
[04:36] <superm1> yeah so i've noticed
[04:37] <jdong> it's a shame because my preliminary research shows I'll be off into about 6 commands and fifos everywhere
[04:37] <jdong> mostly this comes from reverse-engineering handbrake's backend.
[04:38] <jdong> kinda silly they don't directly use mencoder/mplayer as the frontend too
[04:38] <emgent> heya people
[04:38] <jdong> since they already utilize it in the backend (or have the bindings to do so)
[04:38] <superm1> why don't you just clean up handbrake and add functionality there?
[04:48] <superm1> jdong, have you done some driver development in the past trying to get this reverse engineered, or just playing messenger?
[04:49] <jdong> superm1: I've not worked with the iPod Touch but I have had experience reveng'ing other USB peripherals on Windows
[04:49] <jdong> superm1: unfrotuantely my TODO list is very huge
[04:49] <superm1> jdong, you might have tickled my fancy for something to work on during the plane ride to UDS...
[04:49] <jdong> superm1: and for the above question, the handbrake input-frontend is quite silly, complex, and MPEG2-specific and I didn't find it very worthwhile to use it as a base :(
[04:49] <superm1> jdong, care to point me at some starting points?
[04:50] <jdong> superm1: sorry need to head out at the moment
[04:50] <StevenK> I think the first item is 'learn to spell unfortunately'
[04:50] <StevenK> jdong: ^
[04:50] <jdong> there's something called usbsnoop or something liek that for Windows
[04:50] <jdong> StevenK: making fun of my typing skills? :P
[04:50] <ajmitch> StevenK: harsh
[04:50] <superm1> i'll start out reading the USB specs I suppose :)
[04:50] <StevenK> jdong: And your spelling skills
[04:50] <jdong> StevenK: lol I'm using a laptop keyboard ;-)
[04:51] <jdong> AND gnome-terminal *STILL* doesn't have spellcheck
[04:51] <jdong> despite my NUMEROUS whiny e-mails to ubuntu-devel-discuss about my KEYBOARD.
[04:51] <StevenK> It would have been ironic if I'd mispelled it.
[04:51] <jdong> </bad impression>
 ?
[05:28] <asomething> Hey! I've got a question. What is the process for trying to get an exception package in main at this point? Seahorse Bug #215729 has a patch attached that resolves a fairly important bug. I've tested and confirm that it work as well as created a debdiff for it.
[05:28] <ubotu> Launchpad bug 215729 in seahorse "Seahorse fails to import keys" [Medium,In progress] https://launchpad.net/bugs/215729
[05:29] <asomething> I've only seen info on getting exceptions for universe packages
[05:30] <Hobbsee> asomething: slangasek was looking into that, as was LaserJock
[05:32] <asomething> ok, glad to know it's being looked at. I've attached a debdiff to the report and which I've built in pbuilder and installed with no issue :)
[05:39] <LaserJock> asomething: I already uploaded it once :-)
[05:41] <LaserJock> I'm trying to make sure slangasek will approve it this time ;-)
[05:41] <asomething> ﻿LaserJock: thanks for working on it! I wasn't sure if it was on any ones radar as the bug report didn't have any thing but the patch attempts in its comments
[05:42] <LaserJock> yeah
[06:04] <Hobbsee> slangasek: how does the patch get fixed, so it does get approved?
[06:06] <slangasek> Hobbsee: per the discussion on #ubuntu-devel, the question right now is whether someone is sure that there are no memory leaks in the new code
[06:07] <Hobbsee> slangasek: hm, sorry, missed the other discussion
[06:07] <Hobbsee> slangasek: do we have good C people here who know how to check?
[06:07] <slangasek> well, I know how to check
[06:07] <slangasek> so if it comes down to me, then the ETA is probably 2h :)
[06:11] <asomething> ﻿slangasek: i'm currently running the patched version, if there is any way i can help, let me know
[06:14] <slangasek> asomething: sorry, at this stage of the freeze I'm really after making sure that it's reviewed by someone who's a) core-dev, b) able to confirm that there aren't any memory leaks
[06:15] <asomething> ﻿slangasek: np, definitely understand
[06:25] <RAOF> asomething: I'm not terribly familiar with glib's types, but that patch declares a (gchar *) and then mallocs enough space for 11 char (not gchar) and assingnes with a (char *) cast.  Either it doesn't matter, and it's just stylistically ugly, or it does matter and it'll (hopefully) segfault on some strange arch.
[06:28] <RAOF> ...Except the existing code does something similar, so maybe that's standard glib practice that I just find strange :)
[07:18] <elemjay> Latest Google Tech Talk on the future of Linux: http://www.youtube.com/watch?v=4A6ImflixL8
[07:31] <awmcclain> If I'm packaging a perl module, all the dependencies would be most appropriately listed under build-depends-indep, since the perl module has not architecture-specific binaries, correct?
[07:31] <awmcclain> s/not/no
[07:32] <RAOF> awmcclain: It's actually a little bit more subtle than that.
[07:34] <awmcclain> RAOF: Howso?
[07:35] <RAOF> awmcclain: I should dig up the policy document.  Basically, b-d-i are guaranteed to be installed for binary-indep:, b-d are guaranteed for clean: etc.
[07:36] <awmcclain> RAOF:  http://www.debian.org/doc/debian-policy/ch-relationships.html bottom of page
[07:38] <awmcclain> RAOF: I'm confused because for the deb files created by dh-make-perl, the build-arch, build-indep and build install targets are all conflated.
[07:39] <awmcclain> So I don't have a clear example of what the differences are.
[07:41] <RAOF> Right.  So basically, everything should be in b-d-i *except* for stuff required to run clean (that would be debhelper, dpatch, etc).
[07:42] <awmcclain> Thank you RAOF
[07:42] <awmcclain> My attempt to patch one package has ballooned into 6 custom dependency packages, so I'm trying to wrap my head around a lot of concepts.
[07:43] <RAOF> Heh.
[07:57] <protonchris> TheMuso: I noticed that you changed Bug 216308 from Fix commited back to confirmed?  Did you run into issues with the updated package?
[07:57] <ubotu> Launchpad bug 216308 in glom "Glom crashes when adding record" [Undecided,Confirmed] https://launchpad.net/bugs/216308
[08:21] <LaserJock> oh fortran how I hate you, let me count the ways
[08:21] <LaserJock> do i=1, infinity
[08:22] <LaserJock> write (*,*) 'I hate you'
[08:22] <LaserJock> done
[08:22] <LaserJock> s/done/enddo
[08:52] <dholbach> good morning
[09:28] <geser> good morning
[09:34] <harrisony> j #ubuntu-devel
[09:40] <emgent> morning
[10:04] <elmargol> is there a lecture or somoething how to use bazaar to manage a debian package?
[10:04] <elmargol> https://wiki.ubuntu.com/BzrMaintainerHowto is not very detailed
[10:09] <Iulian> Hello
[10:33] <StevenK> Could I convince someone from motu-release to look at bug 181150
[10:33] <ubotu> Launchpad bug 181150 in moko "[FFe] moko contains a shared library with no soname/dev package handling" [Critical,Confirmed] https://launchpad.net/bugs/181150
[10:33] <AnAnt> Hello, what should I put in Vcs-Bzr ? the whole path for the package or just the branch path ?
[10:34] <AnAnt> the bzr branch has several pacakges
[10:36] <AnAnt> the bzr branch is http://bazaar.launchpad.net/~ubuntume.team/ubuntume-artwork/hardy
[10:36] <AnAnt> the bzr branch is http://bazaar.launchpad.net/~ubuntume.team/ubuntume-artwork/trunk
[10:36] <AnAnt> there are several folders in this branch, each branch is for a package
[10:36] <AnAnt> there are several folders in this branch, each folder is for a package
[11:07] <jscinoz> ok...
[11:07] <jscinoz> PPA is being screwy again..
[11:07] <jscinoz> package failing to build, but the logs are indicating it completed successfully.
[11:08] <cprov> jscinoz: buildlog url ?
[11:08] <jscinoz> http://launchpadlibrarian.net/13461391/buildlog_ubuntu-hardy-i386.urbanterror-data_4.1-0ubuntu3_BUILDING.txt.gz
[12:26] <doko> is revu.tauware.de down?
[12:28] <james_w> doko: https://lists.ubuntu.com/archives/ubuntu-motu/2008-April/003599.html
[12:29] <doko> nice, so no glassfish for hardy
[12:30] <james_w> doko: sistpoty may be able to extract the package for you, I'm not sure.
[13:02] <james_w> Laney: hi, are you around?
[13:32] <Laney> james_w: Am now, what's up?
[14:00] <protonchris> TheMuso: Nevermind.  It looks like it just went through thanks.
[14:03] <soren>  a
[14:03] <soren> whoops
[14:34] <sistpoty|work> hi folks
[14:34] <emgent> hi sistpoty|work :)
[14:34] <sistpoty|work> hi emgent
[15:05] <elmargol> I'm searching users who can provide some feedback on some packages I created for feisty. https://launchpad.net/~teamgnunet/+archive  (gnunet is an anonymous filesharing network)
[15:05] <elmargol> -feisty +hardy
[15:09] <Hobbsee> anyone interested in dealing with rsync?
[15:09] <StevenK> "dealing with" ?
[15:10] <Hobbsee> new upstream release, outstanding cves, it looks like
[15:11]  * persia grumbles about upstream failing to modify copyright attribution or include licensing information in files when they have changed >90% of the content
[15:12] <\sh> Hobbsee, rsync is main?
[15:12] <\sh> -?+!
[15:12] <Hobbsee> \sh: oh, so it is
[15:22] <Hobbsee> \sh: you could deal with it anyway
[15:23] <\sh> Hobbsee, grmpf ;) well, actually I need a stable hardy...so I'll check when I'm home...
[15:23] <Hobbsee> \sh:
[15:23] <Hobbsee> thankyou.
[15:24] <\sh> Hobbsee, team to subscribe for main? ubuntu-release?
[15:24] <Hobbsee> yes
[16:44] <Nafallo> ah.
[16:45] <Nafallo> I thought I saw a topic change somewhere :-)
[17:16]  * sistpoty|work heads home... cya
[18:34] <\sh> re
[18:34] <emgent> heya \sh :)
[18:35] <\sh> hey emgent
[19:05] <promag> hello guys
[19:05] <promag> $ apt-get install dpxis-app-base
[19:05] <promag> The following packages have unmet dependencies:
[19:05] <promag>   dpxis-app-base: Depends: dpxis-plugins-base but it is not going to be installed
[19:06] <promag> how can I FORCE dpxis-plugins-base installation automatically?
[19:11] <pochu> promag: that package doesn't exist (anymore)
[19:12] <pochu> well, it has never been in Ubuntu according to packages.ubuntu.com so wrong channel
[19:39] <emgent> DktrKranz: heya :D
[19:40] <DktrKranz> hey emgent
[19:40] <emgent> thanks for cacti
[19:40] <DktrKranz> you're welcome :)
[19:41] <DktrKranz> I didn't want to have a SRU around ;)
[19:43] <emgent> :)
[19:50] <sebner> DktrKranz: heya :)
[19:50] <DktrKranz> aloha sebner
[19:51] <sebner> ^^
[20:14] <cbx33> hey all
[20:14] <cbx33> howz it going
[20:14] <cbx33> long time :p
[20:59] <kees> can a motu-release person look at bug 216132?  I'd like to get a refpolicy bug-fix upload exception.
[20:59] <ubotu> Launchpad bug 216132 in refpolicy "SELinux breaks CUPS" [Undecided,New] https://launchpad.net/bugs/216132
[21:04] <stani> pochu, ScottK: I've attached a debdiff to fix Bug #215714. Could one of you take care it gets uploaded?
[21:04] <ubotu> Launchpad bug 215714 in phatch "The path for python extensions should reflect the 2.0 api" [Medium,Confirmed] https://launchpad.net/bugs/215714
[21:05] <stani> POX_: Do not apply this patch to Debian. I will prepare phatch-0.1.4 which handles this issue in a better way.
[21:10] <norsetto> kees: its acked
[21:17]  * proppy hugs norsetto
[21:17] <norsetto> proppy: heya!
[21:17] <proppy> norsetto: howdy ?
[21:17] <norsetto> proppy: goodie goodie, and you?
[21:18] <kees> norsetto: okay, thanks.
[21:18] <proppy> norsetto: nice nice, gnometheming :)
[21:19] <norsetto> proppy: booh :-) time to convert to the Dark (read Blue) Side ;-)
[21:19] <proppy> ? :)
[21:20] <proppy> not sure I'm getting it
[21:20] <proppy> norsetto: aaah understood
[21:20] <proppy> blue means kde :) ?
[21:20] <pochu> stani: I'm on it, thanks for the patch :)
[21:20] <norsetto> proppy: indeed
[21:20] <proppy> this one was hard
[21:21] <proppy> norsetto: you're like yoda to me
[21:21] <norsetto> proppy: may the farce be with you ;-)
[21:22] <stani> pochu: thanks
[21:22] <proppy> haha, you're such a frenchmen
[21:23] <norsetto> proppy: what can I do .. I spent the last 5 days in France ....
[21:23] <proppy> sad that we never met there !
[21:23] <proppy> nancy is too far
[21:23] <norsetto> proppy: was in Nice this time
[21:25] <proppy> :)
[21:26] <sebner> norsetto: we have to convert you back to the brown folks ^^
[21:26] <norsetto> sebner: vade retro satana!
[21:27] <sebner> norsetto: latin?
[21:27] <RainCT> asac: hey, anything new about the adblock-plus bug?
[21:27] <norsetto> sebner: yes
[21:28] <sebner> norsetto: Please translate ^
[21:28]  * proppy wonders if xfce is the "mouse" force
[21:28] <norsetto> sebner: go away satan! (or whatever the devil is called nowadays)
[21:29] <pochu> ScottK: ACK to upload phatch, bug 215714? sistpoty approved it but I don't think the phatch task was there at that moment, so he approved nautilus-python... but after that we need to upload phatch too
[21:29] <sebner> norsetto: gnome rulez :P
[21:29] <ubotu> Launchpad bug 215714 in phatch "The path for python extensions should reflect the 2.0 api" [Medium,Confirmed] https://launchpad.net/bugs/215714
[21:29] <RainCT> asac: uhm.. reading bugmail right now. so taht was a problem in xulrunner?
[21:30] <RainCT> omg, we are losing norsetto, bring him back! :)
[21:30] <asac> RainCT: yeah ;)
[21:31] <asac> the upstream bug is linked in the bug report
[21:31] <RainCT> asac: ok, cool :)
[21:31] <asac> RainCT: but that problem was rather old afaict
[21:31] <norsetto> rainCT: a BIG loss (I'm above the 100 kg now :-()
[21:31] <asac> we just didn't notice because we didn't ship that extension i guess
[21:31] <asac> and ignored bugs about it
[21:31] <asac> so another good thing to get these things in packages
[21:32] <pochu> ScottK: it's broken right now due to the change in nautilus-python and I've verified Stani's debdiff is correct (and it's really small, a one line fix to change the path)
[21:34] <crimsun> anyone from MOTU-R willing to approve https://bugs.edge.launchpad.net/ubuntu/+source/trang/+bug/141447/comments/14 ?
[21:34] <ubotu> Launchpad bug 141447 in trang "trang segfaults on gutsy (x86 and AMD64)" [Medium,Fix committed]
[21:38] <bersace> Hi
[21:38] <bersace> why isn't  gnome-scan updated to 0.6 ? :/
[21:38] <bersace> release march the 10th !
[21:39] <bersace> see you later
[21:47] <stani> pochu: Is ScottK around?
[21:48] <pochu> stani: doesn't look like :) but he will answer when he's back, don't worry
[21:48] <pochu> stani: I'll ask in the bug report too, just in case
[21:48] <pochu> as there are 4 more members in that team :)
[21:48] <pochu> err
[21:49] <pochu> actually I think norsetto is one... norsetto ^
[21:49] <pochu> 22:32 <     pochu> ScottK: it's broken right now due to the change in nautilus-python and I've verified Stani's debdiff is correct (and it's really small, a one line fix to change the path)
[21:49] <norsetto> hmmm?
[21:49] <pochu> bug 215714
[21:49] <ubotu> Launchpad bug 215714 in phatch "The path for python extensions should reflect the 2.0 api" [Medium,Confirmed] https://launchpad.net/bugs/215714
[21:50] <pochu> norsetto: we need a motu-release ACK for phatch too
[21:50] <stani> pochu: yes I saw, maybe it is good to tell him that this bug has been reported in the first place because of Phatch
[21:50] <pochu> sistpoty approved nautilus-python and now the phatch extension won't work unless we apply stani's fix
[21:50] <norsetto> pochu: ok, I'll check it asap
[21:50] <pochu> thanks
[21:50] <pochu> I'm waiting to press enter :)
[21:50] <pochu> emilio@saturno:~/tmp$ dput phatch_0.1.3-1ubuntu2_source.changes
[21:51] <stani> pochu: haha, I wish I could press it for you
[21:51] <pochu> hmm, actually that wouldn't have worked... ubuntu  isn't my default in /etc/dput.cf :)
[21:52] <stani> pochu: can you help me to fix this issue better for PAPT with build-depends and pkg-config?
[21:53] <pochu> stani: well, actually I could upload it and wait for an ack since the queue is set to manual and thus uploads need to be manually accepted, but I'll wait and get an ACK first :)
[21:53] <stani> pochu: so I can make POX_ happy too
[21:53] <stani> pochu: I mean for debian not for ubuntu
[21:53] <pochu> stani: sure. "pkg-config --variable=pythondir nautilus-python" is the command you need
[21:53] <norsetto> pochu: bug number?
[21:54] <pochu> norsetto: bug 215714
[21:54] <ubotu> Launchpad bug 215714 in phatch "The path for python extensions should reflect the 2.0 api" [Medium,Confirmed] https://launchpad.net/bugs/215714
[21:54] <pochu> the diff is a one liner
[21:54] <norsetto> pochu: kind of difficult for motu-release to ack if you don't subscribe ....
[21:55] <pochu> ah, sorry
[21:55] <pochu> norsetto: ScottK knows the package so I was expecting him to ACK it, but he isn't around so... :)
[22:00] <norsetto> pochu: you tested this?
[22:00] <pochu> norsetto: yes
[22:01] <norsetto> pochu: yes, with success I guess ...
[22:01] <pochu> I've verified that a) the nautilus-python update broke it, and b) that this debdiff fixed it
[22:01] <pochu> of course
[22:01] <norsetto> pochu, stani: ok, looks good to me, go ahead
[22:02] <stani> norsetto: thanks
[22:02] <norsetto> pochu: de nada
[22:02] <pochu> thank you norsetto
[22:03] <stani> norsetto: obrigado
[22:03] <norsetto> stani: maag niet uit ...
[22:06] <pochu> stani: Successfully uploaded packages.
[22:06] <pochu> bbl
[22:06] <stani> norsetto: haha, quite good
[22:06] <stani> norsetto: ﻿but should be "maak niet uit" (maag = stomach)
[22:07] <stani> pochu: thanks!
[22:07] <norsetto> stani: yes, but its funnier this way ;-)
[22:07] <stani> norsetto: that is for sure!
[22:11] <stani> pochu: I don't understand why the package is called python-nautilus but pkg-config uses nautilus-python
[22:12] <stani> pochu: also the changelog mentions nautilus-python
[22:12] <stani> pochu: so what is the difference between python-nautilus and nautilus-python?
[22:14] <norsetto> crimsun: I have no idea what -findirect-dispatch does, but I guess you tested this with success?
[22:15] <crimsun> norsetto: yes.  It's taken from the Debian change by Barry.
[22:15] <norsetto> crimsun: I see, perhaps you should mention it in the changelog? Do we also need the -O2 -g in there?
[22:15] <stani> pochu: other question do I have to add pkg-config to build-depends as well?
[22:16] <crimsun> norsetto: yes, because I didn't wish to patch Makefile, which is more cumbersome, as well.
[22:17] <norsetto> crimsun: ok, but perhaps we should then do something similar to what we do for the CFLAGS
[22:18] <norsetto> crimsun: for the optimisation flag I mean
[22:18] <crimsun> sure, I'll rediff.
[22:26] <crimsun> norsetto: updated debdiff attached, thanks.
[22:30] <sebner> gn8 folks :)
[22:31] <eddyMul> I'm trying to patch git-core-1.5.4.3-1ubuntu2 in hardy with 1.5.4.3-1ubuntu2~ppa1 from my PPA. somehow, synaptic doesn't see the ~ppa1 as an upgrade. What can I do other than "force version"?
[22:32] <crimsun> that's because 2~ is lower than 2
[22:33] <eddyMul> crimsun: ah. I will bump the version, then. thanx!
[22:34] <crimsun> cf. http://www.debian.org/doc/debian-policy/footnotes.html#f33
[22:36] <eddyMul> crimsun: so, will 1.5.4.3-1ubuntu3~ppa1 be ok?
[22:37] <crimsun> that sorts higher than 1.5.4.3-1ubuntu2.anything, however.
[22:38] <crimsun> try 1.5.4.3-1ubuntu2+ppa1 or something
[22:38] <eddyMul> crimsun: there have been a "back and forth" wiki changes in the PPAQuickStart page
[22:38] <eddyMul> about what should be used for appending, '~' or '+'....
[22:38] <eddyMul> currently, it says '~'....
[22:39] <eddyMul> https://help.launchpad.net/PPAQuickStart
[22:39] <crimsun> in this case I presume you prefer whatever's in your ppa
[22:39] <eddyMul> crimsun: your assumption is correct.
[22:39] <eddyMul> crimsun: so I should use +ppa instead of ~ppa, then?
[22:40] <crimsun> so your target needs to be versioned higher than what's currently in hardy and simultaneously lower than an SRU/security update.
[22:41] <eddyMul> crimsun: yes.
[22:41] <crimsun> for /this/ instance, I would use '+' instead of '~'.
[22:55] <norsetto> crimsun: have you built this in a ppa? Trying to build it locally just trashes my hd to death
[22:57] <eddyMul> crimsun: I got it. Just /this/ instance.   :)
[22:59] <crimsun> norsetto: I've tried twice to build it locally.  I gave up after, each time, it ate through all RAM and swap.  I finally got work permission to build it on a machine there.  It eats about 6 GB.
[23:01] <norsetto> crimsun: right, god bless java ....
[23:03] <norsetto> crimsun: ok, go on with that bloated thing
[23:06] <crimsun> norsetto: to be clear, is that an "ok to upload" for #141447?
[23:06] <norsetto> crimsun: roger
[23:06] <crimsun> thanks
[23:36] <pochu> stani: nautilus-python is the source package (and upstream name), so that's why the changelog (which uses the package name) and pkgconfig (which is from upstream) have nautilus-python
[23:37] <pochu> stani: the Debian/Ubuntu binary package is called python-nautilus though, as the Python Policy says Python modules should be prefixed with python-
[23:37] <stani> pochu: ok, so it is changed because of debian policy?
[23:37] <pochu> yep
[23:37] <stani> pochu: ok
[23:37] <pochu> stani: for pkg-config, yes, add it if you are going to use it
[23:38] <stani> I've added: pkg-config and python-nautilus to build-depends without minimum version requirements as I would now know which ones
[23:39] <pochu> no need for a minimun version yet
[23:39] <stani> would not know
[23:39] <stani> ok
[23:40] <stani> so I have phatch 0.1.4 ready for debian ;-)
[23:40] <pochu> :-)
[23:40] <stani> I've sent an email to POX_ cc to you as well about it
[23:41] <pochu> great. maybe in 2 years I'm able to sponsor it ;-)
[23:45] <pochu> stani: you missed commas in your change to debian/control
[23:46] <stani> pochu: thanks for reviewing, I'll add them now
[23:47] <stani> pochu: done
[23:51] <pochu> stani: thanks. btw you should document every change in debian/changelog
[23:52] <stani> pochu: ok, I will later, I really have to go now