[01:14] <imbrandon> bddebian, where on launchpad do i go to file a uvf exception
[01:15] <bddebian> imbrandon: Just file a bug and call it: UVF Exception: kbfx and give the details
[01:15] <imbrandon> ahh ok, thought i was going insane ;)
[01:15] <bddebian> imbrandon: https://wiki.ubuntu.com/MOTU/UVFStatus
[01:17] <antinobody> Hmm, is there anything anyone wants someone with minimal knowledge to do at the moment?
[01:17] <\sh__> fix bug #1?
[01:17] <Ubugtu> Malone bug 1 in Ubuntu Dapper "Microsoft has a majority market share" [Critical,Confirmed]  http://launchpad.net/bugs/1
[01:17] <bddebian> antinobody: Define minimal.  Couldn't be much less than mine
[01:17] <bddebian> \sh__: ;-P
[01:17] <antinobody> Oh, call it "learning stage"
[01:17] <imbrandon> ok how can i generate those files ( the diffstat ? )
[01:18] <imbrandon> is that what i've been sending you?
[01:18] <antinobody> I've learned how to package, to a point, and I sent a patch to someone for one of the dh_iconcache updates
[01:18] <antinobody> I've seen bug #1
[01:19] <Ubugtu> Malone bug 1 in Ubuntu Dapper "Microsoft has a majority market share" [Critical,Confirmed]  http://launchpad.net/bugs/1
[01:19] <bddebian> imbrandon: diffstat foo.orig.tar.gz  foo_new.orig.tar.gz
[01:20] <bddebian> antinobody: You can certainly triage bugs then.  See if you can reproduce them, etc
[01:20] <imbrandon> k
[01:20] <antinobody> Ok then, anywhere you want me to start, or just go down the list by severity, reproducing what I can?
[01:21] <antinobody> That was addressed to bddebian, I'm just not used to IRC chatting yet
[01:23] <bddebian> antinobody: You can either pick a package you know or run down the list, whatever you are comfortable with.
[01:24] <imbrandon> bddebian, this dont look normal ........
[01:24] <imbrandon> root@delean:/devel/kbfx# diffstat kbfx_0.4.8+cvs20060413.orig.tar.gz kbfx_0.4.9.1ubuntu1.tar.gz
[01:24] <imbrandon>  ERROR, |   22 ---
[01:24] <imbrandon>  used,  |  391 ++---------------------------------------!!!!!!!!!!!!!!!!!!!!!!!
[01:24] <antinobody> bddebian:  All right, will do.
[01:24] <imbrandon>  2 files changed, 14 insertions(+), 260 deletions(-), 139 modifications(!)
[01:25] <imbrandon> no output or anything ( guessing becouse of the errors 22 )
[01:27] <bddebian> imbrandon: Yeah that is a strange one
[01:27] <bddebian> Sorry gang, have to head out again for a bit, bbiaw
[01:27] <imbrandon> kk l8tr
[01:42] <\sh> bddebian: https://launchpad.net/bugs/41537 are there no python2.4 packages which you can use as replacement deps?
[01:42] <Ubugtu> Malone bug 41537 in python2.3-psycopg "[UNMETDEPS]  xsim has unmet dependencies" [Normal,Needs info] 
[01:43] <\sh> or change them directly to python2.4 conform packages :)
[01:45] <whiprush> good evening everyone
[01:45] <\sh> hey whiprush
[01:45] <antinobody> hello
[01:47] <Kyral> hmm, this is random...
[01:47] <Kyral> but does anyone know why most configuration files on Unix are called *rc?
[01:48] <Kyral> like .bashrc, .vimrc, .conkyrc?
[01:49] <\sh> why not ;)
[01:49] <Kyral> I dunno...it just occurred to me that its a common denomenator and it got me wondering what does "rc" stand for
[01:50] <crimsun> mm hackety hack.
[01:50] <crimsun> for i in *; do dpatch patch-template -p "$(echo $i)" "$(grep ^Subject $i|awk -F "Subject: \[PATCH\]  \[UBUNTU alsa-lib\]  " '{ print $2 }')" <$(echo $i)>"$(echo $i).dpatch"; done
[01:51] <\sh> rc could be ressource configuration ?
[01:51] <Kyral> That could be it, would also explain the acronym for BSD-style init
[01:53] <Kyral> Why I think of these things I will never know
[01:55] <\sh> lol
[01:56] <Kyral> Well, lets just decide that we think it stands for "Resource Configuration" and until someone else who was actually around when the acronym first appeared shows up and proves us wrong, then its right :P
[01:57] <\sh> RC is normally Release Candidate...but .bashrc named as .bash release candidate...no :)
[01:57] <\sh> runtime configuration could also be possible
[01:58] <LaserJock> I think it is Random Configuration ;-)
[01:58] <Kyral> That also sounds better
[01:58] <Kyral> runtime config
[01:59] <Kyral> grr, my server is acting up
[01:59] <Kyral> Domain 0 will randomly lose internet access
[01:59] <Kyral> but the rest of them will function fine
[02:00] <Kyral> which is REALLY wierd since Domain 0 acts as the NAT router for the others
[02:00] <LaserJock> Kyral: still running that Xen stuff?
[02:00] <Kyral> yah
[02:01] <Kyral> but it doesn't have any sign of being compromised
[02:01] <Kyral> was any kind of update in Breezy recently that would have restored /lib/tls?
[02:02] <LaserJock> I got a beta of Parallels Workstation which is a virtualizatoin for x86 macs
[02:02] <LaserJock> seems to work nice
[02:04] <Kyral> I have half a mind to switch the hypervisor over to ArchLinux when I upgrade to Xen 3
[02:07] <whiprush> so hey I've been relearning packinging this weekend.
[02:07] <whiprush> do you guys do anything special as far as figuring out build deps?
[02:08] <whiprush> or do you just note them as you build the package?
[02:08] <whiprush> btw, the new ubuntu packaging guide is awesome.
[02:08] <Kyral> whiprush: run it in pbuilder without anything listed then see what configure bitches about?
[02:08] <whiprush> yeah that's what I've been doing.
[02:08] <whiprush> wondering if that's the smartest way
[02:08] <crimsun> most upstream tarballs come with an INSTALL and/or README that list build dependencies
[02:09] <whiprush> ok so there's no automated way, you just need to read the upstream docs and see what pbuilder complains about?
[02:09] <crimsun> as you work through packaging, you'll get to known which -dev packages correspond to which names
[02:10] <whiprush> I found some script in the debian new maintainers guide, but it was ... uh ... not optimal.
[02:10] <Kyral> I was planning on redoing Domain 0 anyway....
[02:10] <crimsun> I've never used an automated means, but that certainly doesn't preclude its existence
[02:10] <Kyral> I think the Domains would prefer having physical partitions backing them :P
[02:11] <whiprush> crimsun: yeah I'm sure just experience with certain packages is the key.
[02:12] <whiprush> I just chuckle because it takes me a good afternoon to do a simple package.
[02:12] <whiprush> and the desktop team can crank out the entire desktop in a few hours, heh.
[02:12] <LaserJock> whiprush: if you have any problems or comments about the Packaging Guide please send a note to me or the docteam ML
[02:13] <whiprush> LaserJock: I found it to be very well done. Are you guys planning on publishing it for dapper?
[02:13] <whiprush> I noticed it was a draft still
[02:14] <LaserJock> whiprush: it is already shipped in the ubuntu-docs package so it is in the Gnome help
[02:15] <whiprush> cool
[02:15] <LaserJock> whiprush: it is also on doc.ubuntu.com (which will go to help.ubuntu.com when dapper is releasd)
[02:15] <whiprush> yeah I found it on doc.u.c
[02:15] <LaserJock> whiprush: and in a little bit you will be able to get print copy lulu.com
[02:15] <whiprush> metal.
[02:16] <LaserJock> I'm actually looking at the first test copy right now
[02:16] <LaserJock> it should be < $10USD because we are waiving royalties (and lulu waives there charges) so it is just the cost of printing and shipping
[02:17] <whiprush> that price sounds reasonable
[02:17] <LaserJock> ack stupid homonyms s/there/their/
[02:17] <LaserJock> whiprush: all shipped Ubuntu (and Kubuntu) documentation will be available
[02:18] <LaserJock> we just started the project a week or two ago
[02:18] <whiprush> that's sweet dude
[02:18] <LaserJock> I think so.
[02:18] <LaserJock> I like having print copies around
[02:20] <LaserJock> and the packaging guide wouldn't sell enough copies (I don't think) for a normal publisher to be interested
[02:30] <crimsun> jmg: give me a chance to finalise alsa-lib_1.0.10-2ubuntu2 first, please
[02:36] <jmg> crimsun: cool
[02:43] <jmg> how much of debian policy applies to universe?
[02:43] <jmg> all of it?
[02:44] <crimsun> what's in question?
[02:44] <jmg> upstream changelog:   * Remove libxen packages (no stable API/ABI)
[02:45] <jmg> They've marked the library packages (previously nicely seperated) as "conflicts"
[02:45] <jmg> Seems pretty hackish.
[02:45] <jmg> (by julien)
[02:45] <crimsun> well, we use DP as a fairly strict guideline, but that doesn't mean there're no exceptions.
[02:46] <jmg> it kind of makes sense as they are tied together in xen-utils
[02:46] <crimsun> frankly if you're willing to lead the maintenance work, you can deviate, but well, for your sanity you may not wish to
[02:46] <jmg> just now we have xen-utils installing into python, which i dont like
[03:12] <jmg> *sigh*
[03:13] <jmg> pkg-xen torpedoed all the libxen stuff and rolled everything into xen-utils
[03:13] <bddebian> Should python deps be version dependent?
[03:14] <jmg> yeah
[03:14] <bddebian> I.E. urlgrabber has Deps: python2.3-dev python   Isn't that wrong?  Or does it just need a rebuild?
[03:14] <jmg> bddebian: it should support python2.? in building
[03:14] <bddebian> jmg: ?
[03:14] <jmg> bddebian: and hopefully yes
[03:15] <jmg> (it just needs a rebuild)
[03:15] <bddebian> But "python" is going to grab 2.4 in Ubuntu isn't it?  So I would get python 2.4 with python2.3-dev wouldn't I?
[03:15] <jmg> nah it would get python2.3-dev
[03:16] <jmg> it needs to depend python2.?-dev
[03:16] <jmg> iirc
[03:16] <bddebian> Gah
[03:17] <crimsun> bddebian: eh? we're still there in -devel
[03:17] <bddebian> I know python2.3-dev is going to get python2.3-dev.  But python is going to try to pull python2.4 isn't it?
[03:17] <bddebian> crimsun: You are but none of the people that typically ignore me are :-)
[03:17] <jmg> yeah it will
[03:18] <bddebian> So then, that is broken isn't it?
[03:18] <jmg> yes but it presumably just needs a rebuild
[03:18] <bddebian> jmg: Aw, shit, I'm talking about build-deps not deps, sorry
[03:18] <crimsun> does it b-d explicitly on python2.3-dev?
[03:19] <bddebian> crimsun: Yes build-dep: python python2.3-dev
[03:19] <crimsun> you can get away with making the latter python2.4-dev
[03:20] <bddebian> I know but what is the most correct?
[03:20] <bddebian> Regardless of what Kamion says, I do want to try to do "the right thing"
[03:20] <crimsun> python and python-dev will work
[03:21] <crimsun> it will pull python2.3 and python2.3-dev in Debian and python2.4 and python2.4-dev in Dapper
[03:21] <crimsun> but--
[03:21] <bddebian> Does it work with both? ;-P
[03:21] <crimsun> s/but--//g
[03:21] <crimsun> I can't test currently
[03:22] <crimsun> if you're unsure, test it with 2.4
[03:31] <bddebian> Hmm, seems to work
[03:35] <bddebian> Hmm, do I dare upload
[03:44] <bmonty> bddebian: if it makes you feel any better I've taken the python2.3 binaries out of a couple packages already when build-deps aren't available
[03:45] <bddebian> bmonty: It's not that man, I'm just pissed off I guess
[03:46] <bmonty> bddebian: why, what happened?
[03:47] <zul_> what happened?
[03:47] <bddebian> bmonty: I had probably better not talk about it or I will offend some
[04:02] <zul_> blah...
[05:29] <sn9> quick question: is there a channel for requesting a backport (of a non-universe pkg)?
[05:29] <robitaille> there is a backport mailing list....not sure about an IRC channel
[05:30] <robitaille> https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[05:30] <Lathiat> is approval require to bring in a brand new package?
[05:31] <sn9> i've been told the version of dbus in breezy in fundamentally incompatible with the version of hal in breezy
[05:31] <Lathiat> thats ridiculous :)
[05:31] <Lathiat> because hal is isntalled and works by default :)
[05:31] <sn9> doesn't work for me
[05:33] <sn9> dbus, that is. hal is ok
[05:33] <sn9> i think
[05:38] <ajmitch> something as central as dbus to the desktop would not be backported
[05:40] <sn9> so there's no way to get gnome-vfs working without going to dapper completely?
[05:41] <ajmitch> gnome-vfs should work just fine in breezy, and does so for many people
[05:42] <sn9> and it used to work for me, but it was very flaky and finally broke altogether
[05:43] <sn9> now, nautilus can't recognize when removable media is mounted
[05:54] <sn9> nobody seems to know anything about this problem is #ubuntu, so i went to #gnome on GIMPNet, and that's where i was told that hal 0.5 requires dbus 0.50 or later
[06:00] <robitaille> sn9 maybe it's time you try Dapper?  The release is getting quite closer.  It's most probably a simpler route than trying to backport or convince someelse to backport dbus
[06:01] <sn9> i'm already using the kernel and udev from dapper
[06:02] <sn9> installed breezy in july
[06:21] <sn9> a day or two prior to the breezy release, a ton of packages got pushed to the repos, and a few dependencies broke that were never fixed
[07:45] <zakame> hi all
[07:45] <LaserJock> hi zakame
[07:45] <zakame> hello LaserJock
[07:56] <zakame> ooh gnome-ppp doesn't work again
[07:57] <zakame> bug 42055
[07:57] <Ubugtu> Malone bug 42055 in gnome-ppp "Latest update breaks functionality" [Normal,Confirmed]  http://launchpad.net/bugs/42055
[07:58] <zakame> considering this is O in debian, I guess I ought to pick it up =)
[08:21] <zakame> hi Hobbsee
[08:22] <Hobbsee> hey zakame
[08:23] <zakame> ooh Ubuntu French Kiss, eh?
[08:25] <Hobbsee> zakame: er, what?
[08:26] <zakame> Hobbsee: reading from sounder
[08:26] <Hobbsee> oh ok
[08:26] <zakame> then again, we do have an fkiss package
[08:27] <Hobbsee> we have many interestingly named packages...
[08:27] <zakame> lol
[09:28] <Tonio_> hi
[01:09] <tiCo89> hello
[01:09] <tiCo89> somebody time to sponsor packages?
[01:12] <Hobbsee> tiCo89: StevenK might
[01:17] <StevenK> I might now.
[01:21] <StevenK> tiCo89: Please don't /query me. You can just ask here.
[01:22] <tiCo89> kk
[01:22] <tiCo89> also...
[01:22] <StevenK> That not so much a sponsor, but a sync request.
[01:22] <StevenK> It may also require a UVF exception.
[01:23] <tiCo89> can you copy libezV24 from debian and then add cobex to ubuntu? : http://www.marioiseli.com/~mario/dpkgs/UploadQueue/
[01:25] <StevenK> This late in the release, I doubt it.
[01:25] <StevenK> libezV24 might get sync'd, but I doubt very strongly new packages will find their way in.
[01:28] <\sh> moins
[02:32] <\sh> guys, where is the unmet deps list? give me some packages to work on :)
[02:37] <StevenK> \sh: In the topic.
[02:40] <blaamann> I tried to update and the complete universe three is emty for no.archive.ubuntu.com e.g look in http://no.archive.ubuntu.com/ubuntu/dists/breezy-updates/universe/source/
[02:41] <blaamann> Seems like it has been empty for a day or two
[02:41] <blaamann> And I can see that the other threes are empty as well
[02:42] <blaamann> E.g http://no.archive.ubuntu.com/ubuntu/dists/breezy-updates/main/binary-i386/Packages.gz is not there
[02:44] <\sh> blaamann: please ask the sysadmins of this mirror or elmo/znarl on #ubuntu-devel
[02:45] <blaamann> \sh: Didn't know who to ask, I will try #ubuntu-devel
[02:45] <\sh> blaamann: elmo and znwal are the sysadmins and can tell you more about it...
[02:45] <\sh> hey barry
[02:46] <blaamann>  \sh: Thanks
[02:46] <bddebian> Heya gang
[02:46] <bddebian> Hi Stephan
[02:46] <StevenK> blaamann: I'd mail the sysadmins of the no.a.u.c mirror
[02:46] <\sh> bddebian: please give me some packages (for later) to work on unmet deps...
[02:47] <\sh> bddebian: I saw that you are world champion for those packages :)
[02:47] <bddebian> Well not if you ask Kamion :-)
[02:47] <StevenK> \sh: That's what the topic is for: http://tinyurl.com/rjcqu (UNMETDEPS)
[02:47] <\sh> StevenK: yes :) I found the list :)
[02:48] <\sh> StevenK: but I don't want to take packages where bddebian is already working on :)
[02:49] <\sh> fai is not solvable, until fai-kernels are entering the archives.....whereas, this kernel package has nothing to do with standard boot kernels, because they are only used for booting fai install clients...
[02:49] <StevenK> I've taken two, but I've at least commented on them.
[02:51] <\sh> the only good solution for fai would be to recommend fai-kernels and remove the dependency on it
[02:56] <bddebian> \sh: Take anything that you want on that list
[02:56] <bddebian> :-)
[02:56] <bddebian> Except maybe matplotlib.  I have a solution, I just need some answers :-)
[02:57] <bddebian> \sh: Take a look at swingwt, I think it should be fixable
[02:58] <zul> for the icon cache stuff, you just add dh_iconcache to the debian/rules file
[02:58] <\sh> bddebian: just have a look on yum (actually I need it for my project as well :))
[02:58] <bddebian> \sh: I just uploaded what should be a depends for yum last night so it might be fixable.  Give it a shot :-)
[02:59] <zul> \sh: swingt looks like its stuck in the builds
[02:59] <\sh> python-urlgrabber (source urlgrabber) is somehow not available, or do I miss something there?
[02:59] <bddebian> OK, so I was playing with mozilla-locales-ru last night and now I can't get rid of the damn thing and it's hosing any of my other installs :-(
[03:00] <bddebian> \sh: I just uploaded a new urlgrabber last night??  Hmm, maybe it failed?
[03:00] <bddebian> zul: Yes, just add dh_iconcache to debian/rules
[03:00] <zul> okie dokie...ill guess ill work my way from the bottom and work my way up
[03:00] <\sh> bddebian: no..just had to update my packages.gz :)
[03:03] <\sh> bddebian: problems with the libswt3.1 libs
[03:05] <bddebian> Ayew
[03:05] <bddebian> There is a newer version in the archive
[03:15] <bddebian> Any ideas how I can remove the mozilla-locales-ru?
[03:18] <zul> purge?
[03:19] <bddebian> Tried that
[03:20] <kelmo_lap> what error do you get
[03:24] <bddebian> Look at this crap:
[03:24] <bddebian> http://paste.ubuntu-nl.org/13143
[03:24] <bddebian> kelmo_lap: ^
[03:26] <bddebian> \sh: Oh yeah, you can have ANY of the *-locales-* crap on Unmet Deps :-)
[03:26] <kelmo_lap> well. i coud inly suggest crude hacks for that, not knowing the software at all
[03:26] <\sh> bddebian: lol
[03:26] <kelmo_lap> only*
[03:37] <ivoks> \sh: hello :)
[03:37] <ivoks> \sh: how are you?
[03:38] <\sh> ivoks: fine :)
[05:25] <zakame> bug 42055, I do need a MOTU UVF exception to update to 0.3.23, right?
[05:25] <Ubugtu> Malone bug 42055 in gnome-ppp "Latest update breaks functionality" [Normal,In progress]  http://launchpad.net/bugs/42055
[05:25] <zakame> do note gnome-ppp is orphaned in debian
[05:31] <\sh> zakame: did you take it over from the old maintainer? :)
[05:31] <zakame> \sh: I've yet to post an RFA in wnpp, but I'm working on packaging the new upstream now
[06:56] <bmonty> bddebian: ping
[07:39] <paniq> hey, where can i get libneon 0.25.5 from?
[07:41] <bddebian> paniq: Debian has it
[07:41] <bddebian> In unstable
[07:42] <paniq> thanks
[07:42] <paniq> now if i only know how to get it ;)
[07:42] <paniq> -o+e
[07:42] <crimsun> you'll want to compile it in a Ubuntu pbuilder
[07:42] <slomo_> paniq: why do you want it? gst-plugins-bad? ;) you could file a uvf exception and hope to get it into dapper
[07:42] <paniq> bmpx
[07:42] <crimsun> there is a uvfe req for libneon already
[07:42] <paniq> i actually only want it to satisfy bmpx :>
[07:43] <crimsun> paniq: it's not a hard dependency; I spoke with deadchip about this weeks ago
[07:43] <paniq> yes, but it has support for icecast and so on... i would want to use that.
[07:44] <paniq> i suppose if i obtain the .deb and install that one it will do for now
[07:46] <bddebian> paniq: Just pull the .dsc, orig.tar.gz and diff.tar.gz from packages.debian.org
[07:46] <bddebian> Then dpkg-source -x foo.dsc
[07:46] <bddebian> Then build it :-)
[07:47] <bddebian> OK, off to honey-dos, later folks
[08:26] <siretart> could someone please try to install python-urlgrabber in dapper?
[08:26] <siretart> does that work for you?
[08:27] <\sh> yepp
[08:27] <siretart> oh, hey \sh! :)
[08:27] <\sh> siretart: apt-get update :) didn't find it this morning :) but I think barry uploaded a new one last night
[08:27] <siretart> hm. I keep on getting 'no candidate for 'python-urlgrabber'
[08:28] <\sh> Need to get 61.5kB of archives.
[08:28] <\sh> After unpacking 270kB of additional disk space will be used.
[08:28] <\sh> Get: 1 http://archive.ubuntu.com dapper/universe python-urlgrabber 2.9.7-2ubuntu1 [61.5kB] 
[08:28] <\sh> Fetched 61.5kB in 0s (118kB/s)
[08:28] <\sh> Selecting previously deselected package python-urlgrabber.
[08:28] <\sh> (Reading database ... 105953 files and directories currently installed.)
[08:28] <siretart> hmm
[08:28] <siretart> verry strange
[08:30] <siretart> let's try another mirror. perhaps de.archive.ubuntu.com has problems (again)
[08:30] <\sh> I'm just using archive.ubuntu.com without the local mirrors...
[08:32] <siretart> interesting. de.archive.ubuntu.com seems to lag a bit
[08:35] <siretart> ok. was a local mirror problem
[08:56] <bmonty> anyone done a dist-upgrade to dapper from a breezy server install?  if so, how did it go?
[09:29] <alexr> Hi there
[09:30] <alexr> Can anybody help us place the newly release gramps2.0.11 into the universe, in time for Dapper?
[09:30] <dallingham> alexr and I would like to know if it is too late to get gramps updated for dapper.
[09:38] <carsten> And I would like to support dallingham and alexr
[09:38] <carsten> :)
[09:38] <LaserJock> well, Dapper is pretty much frozen
[09:39] <carsten> well, .11 fixes about 20 bugs compared to .9 without introducing new things :-) /me hides
[09:40] <LaserJock> carsten: oh, that is nice
[09:41] <dallingham> LaserJock: GRAMPS 2.0.11 is essentially a bug fix release.
[09:41] <dallingham> As was 2.0.10
[09:41] <dallingham> We are feature frozen as well, with all of our new development going into a 2.2 branch.
[09:41] <LaserJock> ok, so you need to do a Upstream Version Freeze (UVF) excemption request
[09:42] <carsten> dallingham: if you don#t have a launchpad-account: I have
[09:42] <dallingham> carsten: I don't have a launchpad-account.
[09:42] <carsten> want me to do it?
[09:42] <dallingham> If you would, I would appreciate it.
[09:43] <carsten> good
[09:43] <dallingham> Thanks.
[09:44] <LaserJock> sorry guys but I've got to go, but maybe another MOTU can help you out.
[09:44] <carsten> sure
[09:46] <LaserJock> but if you file a bug with a changelog, etc. and assign it to the motu-uvf launchpad team
[09:46] <LaserJock> that will get you started
[09:46] <LaserJock> check out https://launchpad.net/people/motu-uvf/+assignedbugs for examples
[10:04] <carsten> Perhaps I am blind, but I don't see how I can assing a bug to the motu-uvf team. This is my report: https://launchpad.net/distros/ubuntu/+source/gramps/+bug/42270
[10:04] <Ubugtu> Malone bug 42270 in gramps "Upstream Version Freeze exception for 2.0.11" [Normal,Unconfirmed] 
[10:13] <vud1> hi.. i am doing a package.. but i have a problem
[10:14] <vud1> it is like... the old version files doesnt are removed and changed by the new
[10:14] <vud1> i dont understand :(
[10:14] <vud1> i am using dh_clean in the rules files.. but it doesnt seem be enought
[10:21] <Gloubiboulga> vud1, which files are modified?
[10:22] <dolson> uh, I guess there's some kind of problem with xchat-gnome because this is the second time that it's disconnected me without me noticing
[10:22] <dolson> not even disconnected, it just quit
[10:23] <vud1> Gloubiboulga: python files.. code files
[10:23] <vud1> it is strange.. becouse in de package-version dir, the changes are ok
[10:23] <vud1> but in the package-version/debian/package dir.. are the old files
[10:23] <vud1> :?
[10:24] <Gloubiboulga> I don't really understand what happens, could you upload the source package somewhere?
[10:25] <vud1> yes.. 1 minute, i upload it to my server
[10:25] <Gloubiboulga> ok
[10:27] <alexr> vud1: are you talking about gramps?
[10:28] <alexr> vud1: if so, 2.0.11 has a change compared to 2.0.9: the man files moved from doc to doc/man
[10:28] <vud1> Gloubiboulga: wget http://www.e-oss.net/pytrainer-deb.tar.gz
[10:30] <vud1> Gloubiboulga: look at the main.py file
[10:30] <Gloubiboulga> ok, looking
[10:30] <Gloubiboulga> it's modified during the build?
[10:31] <vud1> the package-version/pytrainer/main.py and package-version/debian/pytrainer/pytrainer-0.9.3/debian/pytrainer/usr/lib/python2.3/site-packages/pytrainer/main.py are differents :(
[10:31] <vud1> modified not.. is like.. the debian/... version is the old one
[10:32] <vud1> mmm
[10:32] <vud1> perhaps is the setup.py?
[10:32] <vud1> i dont know
[10:33] <Gloubiboulga> I've broken dpkg...
[10:33] <vud1> broken?
[10:34] <Gloubiboulga> yep, I tried to install xvfb and there's a conflict with kaudiocreator
[10:34] <vud1> orf
[10:35] <vud1> mmm
[10:35] <vud1> :(
[10:36] <vud1> well i am going to continue looking for the problem
[10:36] <vud1> thanks a lot :)
[10:37] <Gloubiboulga> I'll have a look as soon as I have fixed my problem...
[10:39] <Gloubiboulga> vud1, your main.py file seems installed in a strange directory btw
[10:39] <Gloubiboulga> you have 2 debian/ subfolders
[10:39] <vud1> mmm
[10:39] <vud1> i am going to see that
[10:41] <vud1> mm
[10:41] <vud1> what are the 2 subfolders?
[10:41] <Gloubiboulga> you've wrote: package-version/debian/pytrainer/pytrainer-0.9.3/debian/pytrainer/usr/lib/python2.3/site-packages/pytrainer/main.py
[10:41] <vud1> ah yeah
[10:41] <vud1> was a paste mistake
[10:41] <vud1> sorry
[10:41] <vud1> :D
[10:41] <Gloubiboulga> ok :)
[10:41] <vud1> the correct paste is..
[10:42] <vud1> debian/pytrainer/usr/lib/python2.3/site-packages/pytrainer/main.py
[10:47] <Gloubiboulga> vud1, I'm sorry, I can't test the build, my system is too broken :/
[10:47] <vud1> :(
[10:47] <vud1> thans anyway..
[10:47] <vud1> only one question
[10:48] <vud1> the lintian command said me this:
[10:48] <vud1> pytrainer source: changelog-should-mention-nmu
[10:48] <vud1> N:
[10:48] <vud1> No1Viking:   When you NMU a package, that fact should be mentioned on the first
[10:48] <vud1> No1Viking:   line in the changelog entry.
[10:48] <vud1> ..
[10:48] <sivang> guys, is here anything that can be done to get some of you to praise me on universe upload right application? I've seen some mergers going etc?
[10:48] <vud1> what is NMU?
[10:49] <Gloubiboulga> vud1, Non Maintainer Upload, it's not a problem in ubuntu
[10:49] <\sh> non maintainer upload
[10:49] <No1Viking> vud1, What?
[10:49] <Gloubiboulga> it's debian specific
[10:50] <phanatic> hi people
[10:50] <Gloubiboulga> hey phanatic
[10:51] <vud1> aaah ok
[10:51] <phanatic> hey Gloubiboulga
[10:51] <phanatic> Gloubiboulga: are you comin to paris?
[10:51] <Gloubiboulga> phanatic, I think so
[10:52] <phanatic> would be great to meet there in personal :)
[10:53] <Gloubiboulga> phanatic, indeed, will you come?
[10:53] <phanatic> Gloubiboulga: i hope to get some sponsorship. i'd like to go...
[10:54] <Gloubiboulga> phanatic, that'd be really great
[10:55] <phanatic> sivang: are they that criminal? :)
[10:55] <sivang> phanatic: well, they commit crimes only against bugs :-)
[10:56] <sivang> phanatic: the leaders are seb128, dhloback and vntz
[10:56] <sivang> vunts, event
[10:57] <phanatic> sivang: i see... but bugfixing isn't a crime :)
[10:57] <sivang> phanatic: well, it's a good crime :)
[10:57] <phanatic> sivang: i agree :)
[11:03] <ispiked> does Jonas Smedegaard come on irc?
[11:04] <azeem> ispiked: why?
[11:04] <ispiked> azeem: I just wanted to ask him something.
[11:04] <azeem> didn't know he was doing Ubuntu
[11:04] <ispiked> azeem: well, he was listed as a package maintainer for python-id3lib.
[11:05] <azeem> yes, he is the Debian maintainer
[11:05] <ispiked> azeem: oh, ok.
[11:05] <azeem> Ubuntu MOTU is the point of contact for Ubuntu issues, though
[11:06] <ispiked> anyway, you might be able to answer my question. that python module is written in c#. how is it compiled and run on ubuntu sysems when they don't ship mono.
[11:06] <ispiked> packages are compiled on the system they're made on, right?
[11:10] <azeem> ispiked: are you sure it is written in c#?
[11:10] <ispiked> azeem: yes. I'm looking at the source code.
[11:10] <azeem> ispiked: packages are compiled on the Ubuntu build machines
[11:11] <ispiked> azeem: how could the module run without .net dependencies?
[11:11] <azeem> ispiked: it looks like c++ to me
[11:12] <ispiked> yeah, I think you're right. :P
[11:12] <ispiked> having it named with .cc threw me off.
[11:12] <azeem> c# sources have .cs as extension I think
[11:13] <ispiked> yeah, good point.
[11:13] <ispiked> ok, well that answers my question.
[12:01] <vud1> there are any web to see the packages avaliable in ubuntu?
[12:02] <ispiked> vud1: packages.ubuntu.com maybe.
[12:02] <vud1> thanks :)