[00:23] <MTecknology> Who maintains the drupal package for the ubuntu repos?
[00:23] <MTecknology> !info drupal6 jaunty
[00:24] <MTecknology> The current version is 6.12
[00:24] <cody-somerville> !info drupal6 karmic
[00:24] <cody-somerville> fancy that
[00:26] <MTecknology> cody-somerville: ... drupal will only be updated with ubuntu releases?
[00:26] <cody-somerville> !backports
[00:27] <MTecknology> cody-somerville: I understand that much, but the drupal updates usually include security patches too
[00:29] <cody-somerville> MTecknology, I can imagine
[00:31] <MTecknology> cody-somerville: I suppose for my case then it might be a better idea to keep drupal in /var/www/ :P
[00:31] <cody-somerville> Personally, I never use web based apps from the repo
[00:32] <MTecknology> I was trying to move to doing it
[00:32] <MTecknology> but ya, probably a good decision to keep w/ what I was doing then :P
[00:32] <MTecknology> anyway - It's bed time - I get up to go to work 0100, makes for a fun night
[00:32] <MTecknology> ttyl
[00:32] <cody-somerville> bye
[01:11] <SirDerigo> un derigo para encontrarlos a todos, un derigo para engañarlos, un derigo para atraerlos a todos y atarlos al S.L
[04:38] <kklimonda> when I work with package (i.e. making changes and using UNRELEASED pocket) what should I do with package version? Bump debian revision or use the same?
[04:52] <xnox`> my package is in the debian import queu / accepted
[04:53] <xnox`> do new pacakges from debian get synced into ubuntu? or do I need to file a sync bug in launchpad?
[04:58] <jmarsden> xnox`: They get synced.  sword just got synced into Karmic :)
[04:59] <jmarsden> SWORD was manual, but a new package that has no package-w.x-yubuntuz already in Karmic is supposed to autosync,
[05:19] <xnox`> jmarsden: ok =D
[05:20] <jmarsden> Is xiphos ready to get into Debian unstable?
[05:20] <xnox`> hmmm it's already in the queue/accepted
[05:21] <xnox`> http://incoming.debian.org/
[05:21] <jmarsden> Cool!
[05:22] <xnox`> after it will all both bibletime & xiphos land in karmic & get compiled we can start filling out requests for backporting ;-)
[05:23] <xnox`> did we tell sword people that we have sliced and diced their tarball?
[05:25] <jmarsden> Well, we told the ones in the pkg-crosswire list at least :)
[05:27] <xnox`> yeah there are about 15 people signed up to the list is it all the upstream bibletime / xiphos / sword lurking?
[06:38] <Fenix|home> Greetings
[06:38] <Fenix|home> TheMuso: Are you available?
[06:47] <artfwo> Hi! Has there been any progress with bug 372243?
[08:16] <kklimonda> what is current debian policy about asking questions during package upgrades? is there any?
[09:17] <maxb> I don't know of anything official, but I imagine it's something like "Only do it if you really really need to "
[09:40] <gaspa> can someone please give-back alt-ergo and pxp ? (they build fine in my ppa, so at least amd64,i386 and lpia)
[09:42] <geser> gaspa: done
[09:43] <gaspa> geser: :)
[10:47] <hyperair> when a bug is marked for expiration, should i change its status to invalid?
[10:47] <hyperair> or should i just leave it as incomplete?
[10:48] <aboSamoor> Hi, this is my first time to think about packaging, usually everything is available in repositories with updated versions. Now, I found that bpython is not in jaunty and I want to package it and add it to my own repository, is there any specific tutorial for python packaging ?
[10:58] <loic-m> !packaging
[10:58] <loic-m> aboSamoor: bpython |    0.9.2-1 |      unstable | source, all
[10:58] <loic-m> aboSamoor: so it's in debian
[10:59] <loic-m> aboSamoor: and karmic, see: bpython |    0.9.1-1 | karmic/universe | source, all
[11:00] <aboSamoor> loic-m: I tried the debian package and it is installed without problems but it crashs before starting, so I thought I may have to package it against ubuntu
[11:01] <loic-m> aboSamoor: just get the source package first, and build it for Jaunty or use a pp
[11:01] <loic-m> s/pp/ppa
[11:02] <loic-m> or use prevu bpython for a quick look at karmic's 0.9.1
[12:01] <bencrisford> I have been working on a bug, I fixed it so I made a debdiff
[12:01] <bencrisford> but all that appeared in the debdiff was the changelog entry
[12:01] <bencrisford> none of the important stuff that actually needed to be changed
[12:01] <bencrisford> i have tried again and again...  help :'(
[12:12] <loic-m> bencrisford: what was the fix?
[12:12] <randomaction> are you taking debdiff of .dsc files?
[12:13] <bencrisford> loic-m: It was really simple, it was a matter of adding a dependency
[12:16] <loic-m> bencrisford: so the control file was changed
[12:16] <bencrisford> loic-m: Yes
[12:16] <bencrisford> but the debdiff didnt show it
[12:16] <bencrisford> loic-m: http://launchpadlibrarian.net/27556542/pellusus_2.26.0-0ubuntu2.debdiff
[12:17] <loic-m> bencrisford: are you sure the debian/control was change when making the diff.gz?
[12:18] <loic-m> bencrisford:did you manually check the diff.gz before doing the debdiff?
[12:18] <bencrisford> loic-m: Well I edited the control,  did a dch -i then debuild -S, then from the new package i made the debdiff
[12:19] <loic-m> bencrisford: check the resulting diff.gz
[12:19] <bencrisford> ok
[12:20] <bencrisford> loic-m: Its not in the diff.gz either, but if i was to add my change to the diff.gz and did my debdiff again..
[12:21] <bencrisford> would that work?
[12:22] <loic-m> bencrisford: dunno. Is saving 2 seconds worth the trouble?
[12:22] <loic-m> bencrisford: I think there's a way to do it, or you can resign afterwards, but does the debuild take _that_ long?
[12:22] <bencrisford> loic-m: ?  I don't understand..
[12:22] <bencrisford> how can i fix this?
[12:24] <loic-m> bencrisford: just make sure debian/control has the dependency, then run debuild again
[12:24] <bencrisford> i have done that several times now loic-m
[12:24] <loic-m> bencrisford: for the other solution, I've never used it, so I can't explain ;)
[12:25] <loic-m> bencrisford: if you debian/control has the dependency, it should show up in the diff.gz
[12:25] <bencrisford> loic-m: Hmm, ok, ill try, ty for your help btw ;) :)
[12:25] <loic-m> bencrisford: unless you didn't save, use the wrong directory, or there's something I can't imagine
[12:26] <loic-m> bencrisford: hope it works
[12:28] <bencrisford> loic-m: I'll be back in a bit
[12:29] <loic-m> no pb
[12:41] <thekorn> hi,
[12:41] <thekorn> I'm packaging a python application, using cdbs
[12:41] <thekorn> and I would like to add a .desktop file
[12:42] <thekorn> waht's needed to get this .desktop file registered?
[12:43] <thekorn> appart from installing this file into /usr/share/applications
[12:43] <loic-m> thekorn: put the file package.desktop in debian folder (package=name of pkg)
[12:44] <loic-m> thekorn: oh, so it's should be enough if you lready install it
[12:44] <loic-m> thekorn: just check you're also installing an icon
[12:44] <loic-m> in /usr/share/pixmaps
[12:44] <loic-m> and check your .desktop file with desktop-file-validate
[12:45] <thekorn> loic-m, yes, ok, so there is no need to add gnome.mk to debian/rules?
[12:45] <thekorn> or run dh_desktop?
[12:46] <thekorn> that's what the packaging guide says, but if I add this, the builder complains about missing ./configure
[12:47] <loic-m> dh_desktop too
[12:47] <pochu> hi thekorn :)
[12:47] <loic-m> if I read the man page correctly
[12:47] <thekorn> hi pochu
[12:48] <thekorn> oh man, packaging is so easy, but obviously way too hard for me ;)
[12:48] <pochu> thekorn: gnome.mk is not needed
[12:48] <thekorn> hmm, ok, let me try whithout it
[12:49] <pochu> dh_desktop is not needed anymore since jaunty
[12:49] <pochu> but it will do no harm
[12:49] <loic-m> pochu: I didn't know that, thanks
[12:50] <thekorn> super, thanks pochu and loic-m, it worked
[12:50] <thekorn> pochu, can we fix it in https://wiki.ubuntu.com/PackagingGuide/Complete#.desktop%20Files ?
[12:51] <pochu> thekorn: yeah, can you do it?
[12:51] <thekorn> pochu, sure
[12:52] <pochu> dh_desktop is not needed anymore since Jaunty because desktop-file-utils 0.15-2 register /usr/share/applications/ as a trigger
[12:52] <pochu> so whenever you install a file there, update-desktop-database will be called
[12:52] <pochu> so you don't need to manually call it
[12:52] <pochu> (which is what dh_desktop does)
[12:53] <alex-weej> anyone know how i can programmatically enable the universe repo? or am i going to have to butcher sources.list "manually"?
[12:55] <thekorn> pochu, ah ok, thanks for the explaination, I quoted you in the comment of my edit
[12:55] <pochu> :)
[12:58] <thekorn> else, nobody would trust a packaging n00b like me ;)
[13:09] <bencrisford> loic-m: No matter how many times I try, or what I try, nothing seems to be working :'(
[13:22] <AnAnt> Hello, can someone sponsor those:  LP #359436 , LP #359444 , LP #359446 ?
[13:45] <bencrisford> loic-m: What im doing is simple as this:
[13:45] <bencrisford> vi debian/control
[13:45] <bencrisford> dch -i
[13:45] <bencrisford> debuild -S
[13:45] <bencrisford> cd ..
[13:45] <bencrisford> debdiff  file.dsc file-new.dsc > file-new.debdiff
[14:21] <gaspa> can someone please give-back galax?
[14:26] <jpds> gaspa: By your command: http://paste.ubuntu.com/189600/
[14:28] <gaspa> jpds: thanls
[14:28] <gaspa> thanks
[14:34] <binarymutant> if someone has the time to do a revu on this package http://revu.ubuntuwire.com/p/pidgin-mbpurple I would be very appreciative :)
[14:50] <pi-meson2> A colleague and I are trying to package the latest HDF5 libraries and pytables to a PPA. Both build fine locally, and pytables (which depends on hdf5) builds the deb, but the deb doesn't install, claiming that "Package libhdf5-serial" is not installed. Is there any way to get additional debugging information from dpkg -i to help us figure out where we're going wrong?
[14:51] <StevenK> dpkg won't install dependancies for you
[14:51] <StevenK> apt will, however
[14:51] <pi-meson2> right, I know that
[14:51] <pi-meson2> we built (and installed) the dependency ourselves
[14:52] <pi-meson2> that is, we built the deb that provides the dep ourselves (that's one of the things we're trying to package)
[14:52] <StevenK> So it seems you need to install libhdf5-serial first
[14:52] <pi-meson2> right, we did! or thought we did
[14:53] <pi-meson2> http://paste2.org/p/250097 claims it's "installed"
[14:54] <StevenK> That's your problem
[14:54] <StevenK> libhdf5-serial-1.8.3-0 != libhdf5-serial
[14:55] <pi-meson2> so our libhdf5 deb should also list "libhdf5-serial" under its "provides"?
[14:56] <StevenK> That would solve that particular issue, yes
[15:00] <penguin42> Does anyone here understand the origin and versioning of cryptsetup? The changelog in the source ends in 2007
[15:04] <pi-meson2> StevenK: okay, that ended up working, thank you very much for the help
[15:29] <penguin42> anyone know about the _( and N_( macros - what's the difference?
[18:33] <nixternal> wgrant: when are you going to put the synaptics package into karmic? need my tapping back :p  in the mean time I will test out your PPA one
[18:41] <nixternal> wgrant: vote of confindence from me, that gives me my tapping back :)
[19:08] <loic-m> slangasek, ping
[19:11] <slangasek> loic-m: hi
[19:11] <loic-m> slangasek, hi
[19:12] <loic-m> slangasek: about http://dep.debian.net/deps/dep5/ I've got a few questions
[19:12] <loic-m> slangasek: don't know if you'ge got the time though
[19:13] <loic-m> slangasek: mainly for the Files: section, this bit "indicating files that have the same licence and share copyright holders."
[19:14] <loic-m> slangasek: it gets overly messy on big src/ with each files having diferent mix of authors
[19:15] <loic-m> slangasek: wouldn't it just be better to just group the files with the same License, and group the copyrights even if they're not all the same on each file?
[19:15] <slangasek> loic-m: the format doesn't dictate how you group authors; if you have twenty authors across 60 files and you want to list a single Files section for them, the format allows you to do that
[19:15] <slangasek> this should probably be clarified in the draft
[19:15] <loic-m> slangasek; Thanks. That's not clear from the description (see the citation)
[19:16] <loic-m> slangasek: that would be great
[19:17] <loic-m> slangasek: I think the other question I had was about multiple year copyright, since all the example are one year only (not so clear then)
[19:18] <loic-m> slangasek: I remember reading (don't know if it was FSF or Debian) that we should detail each year, like 2001, 2002, 2003, 2004
[19:18] <loic-m> slangasek: and not 2001-2004
[19:18] <slangasek> loic-m: correct representation of multiple-year copyrights is dictated by law, I don't think we should make any claims about this one way or the other in the spec :)
[19:18] <loic-m> What's the specification take on that?
[19:19] <loic-m> slangasek: ok. Maybe state what the law is then for more clarity (or add multiple years example)
[19:19] <slangasek> we might refer people to the law, or to a faq someone else has already written
[19:19] <slangasek> stating what the law is would be out of scope for this
[19:22] <loic-m> slangasek: last question -  when there's many files in a folder, and only a few have a different License
[19:23] <loic-m> since the format should also be human-readable
[19:23] <loic-m> Isn't there a way to cover all files minus a few files other than glob, which isn't really human-readable?
[19:24] <slangasek> I'm not sure why you say globs aren't human readable; they're more readable than anything else I can think of for doing this
[19:24] <slangasek> and they're also machine-readable
[19:25] <loic-m> I'll try to point you to an example in a minute
[19:25] <jmarsden> loic-m: Remember you can do a straight somedir/* glob and then later Files: sections take care of the exceptions.
[19:26] <jmarsden> So there is little need for a complex glob...
[19:31] <jmarsden> Incidentally, there is a typo in the dep5 spec: "If multiple Files declaratioun match the same file, then only the last match counts."
[19:32] <jmarsden> declaratioun should be declarations, I think :)
[19:34] <loic-m> jmarsden: here's what mess I'm thinking about http://paste.ubuntu.com/189767/
[19:34] <loic-m> oversimplified of course ;)
[19:35] <loic-m> "Remember you can do a straight somedir/* glob and then later Files: sections take care of the exceptions." that sounds exactly like what I'd like - src/* then list the files in src/ that aren't included
[19:35] <loic-m> unless of course we use the ""If multiple Files declaratioun match the same file, then only the last match counts."
[19:36] <jmarsden> Which is exactly what you should do.  So you can simplify the first Files to Files: src/* -- which is human readable.
[19:37] <loic-m> Ok, thanks. I wasn't sure about it.
[19:37] <jmarsden> I'm no expert, but that's how i read the spec, anyway :)
[19:37] <loic-m> jmarsden: can anybody edit the DPE-5 page?
[19:38] <jmarsden> I'm not sure.  Anyone could, when it was a wiki, but now it is a DEP... try it, I guess :)
[19:40] <loic-m> I don't think I'd dare though ;)
[19:41] <loic-m> It's probably editable on the VCS
[19:41] <loic-m> I'd just like to see that you group files with the same licenses, not the same exact copyrights
[19:47] <slangasek> you can create a bzr branch of it and push changes
[19:47] <slangasek> but it's deliberately not a wiki at this point, because that resulted in lots of drive-by edits without any discussion among the larger Debian community
[19:48] <slangasek> by "push changes", I mean "email the DEP drivers and ask them to merge"; but there are some internal administrativa to sort out yet before we're actually ready to do that, fwiw
[19:51] <loic-m> slangasek: i may just edit a patch and send them to somebody that can edit the page, or just send the questions needing to be clarified and a few modified paragraph proposing a way to clear them
[19:51] <bencrisford> loic-m: Just fyi, i managed to fix that problem from earlier with LaserJock's help :), i just needed to edit the .in rather than
[19:51] <stefanlsd> Something i've done in dep5 recently. I feel its quite readable and also helped me to get the licensing more correct - http://bazaar.launchpad.net/~stefanlsd/+junk/gears/revision/18
[19:51] <bencrisford> than just the control*
[19:52] <slangasek> loic-m: honestly, I would recommend waiting until the discussion process starts on debian-project
[19:52] <slangasek> right now there's far *too much* private discussion going on of the DEP, which I'm trying (weakly) to wrap up
[19:53] <loic-m> bencrisford: good to know
[19:53] <loic-m> bencrisford: Althoug I don't know what's the .in ;)
[19:54] <bencrisford> loic-m: I think its what debuild reads
[19:54] <bencrisford> it doesnt read the control, but the control.in
[19:54] <bencrisford> apparently anyway
[19:54] <loic-m> stefanlsd: thanks, it looks good!
[19:55] <loic-m> slangasek: ok, it's just that some of us are trying to use it esp. for new packages
[19:56] <loic-m> well, thanks a lot slangasek, stefanlsd and jmarsden
[19:58] <nhandler> If I run piuparts with the -p flag (to have it use pbuilder), shouldn't it parse my ~/.pbuilderrc file to determine the location of the tarball?
[20:06] <loic-m> bbl
[20:15] <kklimonda> nhandler: well, it would be nice. unfortunately it has /var/cache/pbuilder/... hardcoded
[20:33] <warp10> Is there someone with an amd64 machine with debian sid installed available?  You should install python-vtk, launch python and type "import vtk"
[20:40] <jmarsden> OK...
[20:40] <warp10> jmarsden: regarding to your question: I could, but my connection is really slow this evening, so I was looking for a faster solution.
[20:44] <jmarsden> Hmmm.  I'm updating it now... pbuilder-sid login got me everything up to "entering the shell" ... and then something that sucked up input but never displayed a shell prompt!
[20:44] <warp10> jmarsden: oh, weird
[20:48] <jmarsden> Definitely... and it still does it after an update.  I'll try creating a new one (I have FIOS 10mbps download speed here, so it shouldn't take *that* long...)
[20:49] <ajmitch> sorry, I only have i386 sid at the moment
[20:49]  * warp10 really, really envys jmarsden's connection
[20:49] <ajmitch> so do I :)
[20:50] <jmarsden> :)  if I paid a little more I could get 20mbps up and down... I have not succumbed to that temptation yet 10 down and 2 up is plenty for now :)
[20:51] <warp10> jmarsden: ok, I'm starting to hate you :D
[20:57] <jmarsden> It's done with the download part of the pbuilder create already ...
[20:58] <warp10> jmarsden: If I had created the chroot, it would still downloading the package list right now. Don't know why, it is incredibly slow and lagged here. Network issues, probably
[20:58] <RoAkSoAx> heya guys how can I update the headers of a patch?
[20:59] <jmarsden> sounds like it.  There it's done, 547 seconds start to finish.
[20:59] <jmarsden> RoAkSoAx: If it uses quilt, use quilt refresh ?
[20:59] <RoAkSoAx> jmarsden, ok thanks:)
[21:00] <jmarsden> warp10: Hmmm, I'm guessing I have something bad in my .pbuilderrc .. the new one has the same behaviour the old one did regarding pbuilder-sid login
[21:01] <warp10> jmarsden: oh, too bad. Can't understand what's the problem could be
[21:02] <jmarsden> I'll get there... but this "quick test" isn't turning out as quick as you hoped... sorry about that :)
[21:03] <warp10> jmarsden: no problem, rather thank you for your helpfulness
[21:03] <jmarsden> Ah... it *is* a shell... just no prompt... echo $SHELL typed into the void gets me /bin/bash... now I need to figure out where the shell prompt went...
[21:04] <ajmitch> warp10: what was the vtk problem you were having anyway?
[21:04] <warp10> ajmitch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529961
[21:04] <warp10> ajmitch: I have found that bug is still present on i386
[21:05] <ajmitch> ok
[21:05] <warp10> and I would like to know if the amd64 is really fixed. I would like to see it actually fixed ASAP, I can't merge mayavi2 without a working vtk
[21:05]  * ajmitch would check it out, but has to run out now for a bit :)
[21:06]  * jmarsden is trying to do the test in his somewhat impaired chroot shell... :)
[21:06] <jmarsden> at-get import python-vtk is bring in 47 other packages with it...
[21:06] <jmarsden> s/bring/bringing/
[21:07] <warp10> jmarsden: probably the whole python stuff and something more
[21:07] <jmarsden> Yes, lots of fonts and X libraries and so forth.  It's done now :)
[21:08] <jmarsden> warp10: test gets me a tracebackm last line of which is ImportError: No module named libvtkCommonPython
[21:09] <warp10> jmarsden: and now I'm wondering why the debian maintainer thinks his latest upload fixed this issue
[21:09] <warp10> jmarsden: thanks a lot for your time & bandwith, your help has been remarkable
[21:09] <jmarsden> Sorry, I can't help you with that question :)
[21:09] <jmarsden> No problem.
[21:10] <ajmitch> warp10: I can confirm it broken on i386 also
[21:11] <warp10> ajmitch: indeed. looks like there is a missing link
[21:31] <contrast> Greets, everyone...
[21:32] <contrast> Would someone here be so kind as to re-package GJay ( http://launchpadlibrarian.net/3400922/gjay_<IP_ADDRESS>-5_amd64.deb ) for Jaunty? The name of a library the package depends on has changed, and this is one of my favorite apps. :)
[21:39] <RoAkSoAx> jmarsden, when updating a patch header, should I specify it in the changelog??
[21:40] <jmarsden> I'm not a MOTU... I'd say yes, just to be safe -- but if you update 20 of them don't add 20 lines to the changelog :)
[21:41] <RoAkSoAx> jmarsden, haha k thanks :)
[21:41] <contrast> Sorry if this is the wrong place for making that kind of request, but could someone point me in the right direction?
[21:41] <jmarsden> contrast: The better way to request that would be to file a needs-packaging bug in launchpad, I think.
[21:42] <contrast> jmarsden: That's normally what I'd do, but this package was deleted from the repositories since it's no longer maintained (following Debian's lead).
[21:44] <vorian> contrast: it will still need a needs-packaging bug
[21:44] <contrast> jmarsden: It's a tiny change that needs to be made to the last version that was package - s/libgsl0/libgsl0ldbl/ in the control file - but I'm not sure how to do this while still maintaining the integrity of the package.
[21:44] <contrast> vorian: got cha. thanks for the heads up.
[21:44] <contrast> packaged*
[21:44] <jmarsden> contrast: Hmmm, then you need to find it a new maintainer, not just a one time update of an existing package... I'm not sure how best to proceed in that case... I'd be tempted to file the needs packaging bug anyway and indicate why you feel this is a useful package to have in Debian/Ubuntu
[21:45] <contrast> point taken... so would anyone here be interested in maintaining the package for the most amazing playlist creator ever? :P
[21:45] <contrast> j/k - i'm filing the report now.
[21:46] <RoAkSoAx> vorian, heya!! gotta question... if I updated the patch headers (quilt refresh patch.diff).. should I put that in the changelog
[21:47] <vorian> yes, put every-little-thing you change in the changelog (even if it's 20 patches)
[21:47] <vorian> but you could do it like
[21:47] <vorian> * frefresh patches:
[21:47] <vorian> - patch.1
[21:48] <vorian> - patch.2
[21:48] <vorian> so on, and so forth
[21:48] <RoAkSoAx> contrast, I think that package is not longer on debian either.. and it has been deprecated because it depends on xmms...
[21:48] <RoAkSoAx> vorian, ok cool thanks
[21:49] <jmarsden> vorian: Why not do:   * debian/patches/*: Refreshed all 20 patches      instead?
[21:49] <contrast> RoAkSoAx: yeah, that's kind of what i was thinking... this probably means it's not going to make it back into the official repos, right?
[21:49] <RoAkSoAx> contrast, right
[21:50] <vorian> depends
[21:50] <contrast> so umm... what now? :)
[21:52] <jmarsden> contrast: Looks like you'll need to find someone to package it and put it in a PPA for you, or learn packaging yourself so you can repackage it... see https://wiki.ubuntu.com/PackagingGuide/Complete
[21:53] <contrast> cool. thanks
[21:54] <jmarsden> No problem.
[21:55] <RoAkSoAx> contrast, or just download the source package, change add a jaunty entry on the changelog, and put it in a PPA
[21:56] <contrast> RoAkSoAx: tried that, couldn't get it to build after installing all dependencies
[21:56] <RoAkSoAx> contrast, why it would not build?? because of xmms i would guess...
[21:57] <contrast> nope, i installed xmms via a ppa. one sec, i'll try again and pastebin the output
[22:01] <RoAkSoAx> ok
[22:03] <contrast> http://pastebin.ca/1450088
[22:04] <contrast> i should note this is after applying the diff found here - https://launchpad.net/ubuntu/hardy/+source/gjay/<IP_ADDRESS>-5build1 - by running the command "patch -p1<../gjay_<IP_ADDRESS>-5build1.diff" in the orig directory.
[22:08] <RoAkSoAx> contrast, you would have to take a look in prefs.c line 338 and see why it's failing to build
[22:09] <contrast> yeah, tried that... given i'm not a programmer, it didn't help much. :P
[22:10] <RoAkSoAx> contrast, well what I  would try to do is download xmms and gjay from dapper, add a changelog entry from jaunty on each, and then try to build them
[22:11] <contrast> will do. thanks for the info.


[12:17] <marseillai> siretart: after an hour of test it's really a wpa bug! it turns in a infiny loop when i try in console.
[01:04] <kpdawg> #nicksetup kp.dawg
[01:16] <andrewski> i'm just starting to delve launchpad for all its coolness.  i registered my project on it and i'd love to make use of its bugtracker for it.  but before it goes live, i'd like to make sure: since i'm listed as the owner/maintainer of the project, will i be notified when bugs are reported?
[01:30] <mpt> andrewski, no, for that you need to register yourself as the "bug contact"
[01:30] <mpt> Doing that is under the "Bugs" menu for your product.
[01:31] <mpt> And welcome to Launchpad, btw.
[01:32] <andrewski> mpt: thanks for the help and for the welcome. :)  cheers.
[01:33] <andrewski> would it be bugworthy to file something that sets up the bug contact when registering a new project, or at least gives the option?  that seems like a sane default, at least to me.
[01:35] <mpt> Maybe, but maybe not
[01:36] <mpt> Depends on the proportion of products that are registering to use Malone
[01:36] <mpt> as opposed to registering to use Rosetta or the Bazaar or the other apps
[02:47] <lifeless> mpt: perhaps havie tool-specifici product registration forms ?
[02:48] <lifeless> mpt: i.e. in $sourcepackage/+bugs 'there is no upstream for this product' -> when you create one from there you get a bugs specific workflow
[03:47] <|evi> :D
[04:48] <|evi> anybody ?
[09:16] <lifeless> is staging meant to be down ?
[10:30] <sivang> morning all sundayers
[10:32] <fireglow> hi sivang :)
[10:41] <sivang> hey fireglow , how's it going?
[11:03] <fireglow> just fine :) nice weather around here. how are you doing?
[11:12] <fireglow> gtg, bb
[03:54] <andrewski> is there any way to search for a specific product with a distro?  e.g. https://launchpad.net/distros/ubuntu/+bugs-advanced-search, where i decide i'd like to search for all bugs in product "foo".
[03:57] <mdke> andrewski, as far as I've understood it, products don't occur in distros. If you're looking for all the bugs on a specific package, it's very easy. Click "Source Packages" in the top left
[03:57] <ddaa> Mh... I do not think such a search exist, and it would be tricky in the general case, since distro think in terms of packages, and there are not exactly products, but there is a relation
[03:58] <ddaa> mdke: oh thanks, how unobvious :)
[03:58] <andrewski> well, what i really mean is that if i search for, say, "rhythmbox" in ubuntu, i'll get all bugs that even mention rhythmbox, whereas i'd like to drill down and just see bugs that are assigned to rhythmbox.  mdke, i don't see how to do this even if i click on "source packages".  (forgive me if i'm getting the terminology mixed up a bit.)
[03:59] <mdke> andrewski, click "Source packages" then enter "Rhythmbox", then click "Bugs"
[03:59] <ddaa> generally, looking for distro bugs by product would be unreliable because the linkage between packages and products is not always present or up to date. But that might be a worthwile feature.
[03:59] <ddaa> andrewski: what mdke says
[04:00] <ddaa> at least search for bugs for a given source package should be easier
[04:00] <andrewski> ah, ok... that takes a lot of unobvious (for me) clicks.
[04:00] <ddaa> andrewski: file a bug!
[04:00] <andrewski> i was thinking about it, but wanted to come discuss it here first. :)
[04:00] <ddaa> on launchpad product, I agree the UI is confuddling
[04:01] <andrewski> you gotta check myself before i wreck myself: i want to say "searching for source packages in a specific distro", yes?
[04:02] <ddaa> something like "unobvious how to search bugs for a specific package in a distro"
[04:02] <mdke> andrewski, the "Source package" thing is being worked on, I believe.
[04:02] <andrewski> mdke: well, obviously i'll search before filing. ;)
[04:02] <mdke> there was an email about simplifying things last week to ubuntu-devel
[04:03] <dilys> Merge to devel/launchpad/: [trivial]  Fix crasher in specworkload table, and add a test -- my fault, but where was the test for it? (r3437: kiko)
[04:10] <andrewski> does malone take HTML (specifically "<a>") tags?
[04:14] <ddaa> andrewski: I'd expect it to quote it
[04:15] <ddaa> if you paste a URL, it should linkify it automatically
[04:15] <Kamping_Kaiser> can i close someone's support requests without being administrator of a group? it's been open for a while, and it's no longer relevent
[04:16] <mdke> andrewski, it will also linkify "bug #1234" for you
[04:30] <andrewski> ddaa, mdke: in case you're interested, that ended up as "bug #38881" in malone.
[04:30] <Ubugtu> Malone bug 38881 in malone "Searching for bugs in a specific package in a distro is unobvious" [Normal,Unconfirmed]  http://launchpad.net/bugs/38881
[04:30] <andrewski> thanks for the help.
[04:30] <mdke> cool
[04:53] <andrewski> another thought: there doesn't seem to be enough product/package info sent with bug notifications.  such info would be nice, as i would like to handle bugs filed against my registered product separately from the ubuntu bug notifications i receive.  i could use my email filter, but there doesn't seem to be any criteria....
[04:57] <mpt> andrewski, have you seen the X-Launchpad-Bug: header?
[04:57] <andrewski> [hangs head in shame]  no...
[04:57] <andrewski> /me goes and looks.
[04:58] <andrewski> oh gosh, it's right there.  well, that'll do then.  kudos to launchpad people for keeping the bug notifications trim but supplying all the useful information!
[04:58] <andrewski> thanks mpt
[07:17] <copernic> hello, does anyone know if KDE translations sync with their svn repository after being translated via rosetta?
[07:18] <mdke> copernic, you mean ubuntu->upstream? No, they don't
[07:19] <copernic> mdke: so these translations are lost?
[07:22] <mdke> copernic, they go into Ubuntu. If the translators wish to submit their work upstream, they can do so. It's like all linux development, really
[07:23] <copernic> oh I see now, that makes sence
[07:23] <copernic> po files are always there anyway
[07:23] <mdke> sure, sure
[07:23] <mdke> maybe one day if kde uses rosetta for translation, pooling translations through rosetta will be simpler
[07:24] <mdke> but for now, it's up to the individual translating teams to give back upstream
[07:34] <uws> mdke: I'm sorry to say this, but rosetta really upsets me
[07:34] <uws> I'm an upstream GNOME-NL (Dutch) translator
[07:34] <mdke> uws, that's ok. I don't make it
[07:34] <uws> really bad translations enter ubuntu
[07:34] <uws> we (gnome-nl) get the flames
[07:35] <mdke> uws, that's nothing to do with rosetta. It is the Ubuntu Dutch Translating team
[07:35] <mdke> talk to them
[07:35] <mdke> ask them to be more careful about who is in their team
[07:35] <uws> Well, the sync looks like something not directly related to ubuntu-nl
[07:35] <uws> it's really bad policy to keep all translations downstream
[07:35] <mdke> translations can only come from upstream or the ubuntu translation team
[07:35] <uws> not notifying upstream
[07:35] <mdke> uws, again, that is up to the ubuntu-nl team, in my opinion
[07:36] <uws> We try our best to get high quality trnslations, but the crappy ubuntu-nl transltations end up in ubuntu
[07:36] <uws> ignoring our hard work
[07:36] <mdke> i help in the italian team, we are quite careful about maintaining good members on the team. We enforce the gnome translation guidelines
[07:36] <uws> the official upstream gnome translations are pretty good
[07:36] <mdke> and where there are upstream translations already, we don't overwrite them
[07:36] <uws> but ubuntu ships translations that don't even get  "file->save" right
[07:37] <mdke> uws, the only thing I can suggest is to talk to ubuntu-nl, and ask them to get their act together
[07:37] <uws> Another thing
[07:37] <uws> I found a Dutch translation for Serpentine
[07:38] <uws> a gnome application for burning cd's
[07:38] <uws> it's not in gnome -cvs
[07:38] <uws> so it's officialy not our job
[07:38] <uws> it featured a nl.po WITHOUT ANY last-translator fields
[07:38] <uws> nor a name in the comments
[07:38] <uws> only a X-Rosetta.... header
[07:38] <uws> so I assume it comes from ubuntu
[07:38] <uws> it was really, really bad.
[07:38] <mdke> could be
[07:39] <uws> It really sucks I can't even figure out who is responsible for it.
[07:39] <uws> I'm done halfway fixing it. I changed about 90% of the strings.
[07:39] <uws> While Rosetta is a great way to get people involved, at the moment it's REALLY UNFRIENDLY for upstream
[07:39] <mdke> hang on
[07:39] <uws> ok
[07:40] <mdke> do you have this problem with other distributions?
[07:40] <uws> don't get me wrong. I love to see people involved
[07:40] <uws> but I really hate it to not be able to find out who did things
[07:40] <uws> mdke: No, just Ubuntu.
[07:40] <mdke> right
[07:40] <uws> mdke: The other distributions track upstream
[07:40] <mdke> no...
[07:40] <mdke> ubuntu tracks upstream too
[07:40] <uws> redhat, novell, debian, all get our translations right in some way
[07:40] <uws> ubuntu doesn't
[07:40] <mdke> hang on a sec
[07:40] <uws> k
[07:41] <mdke> ubuntu imports upstream translations. What you are complaining about is the ubuntu dutch translating team overwriting your translations with bad ones. That is something you really have to speak to that team about
[07:42] <mdke> any translation system is useless if the team management isn't working
[07:42] <uws> Yeah I figure
[07:42] <mdke> its like giving cvs access in gnome to bad translations, right?
[07:42] <mdke> s/translations/translators
[07:42] <uws> No, the bad translations don't enter gnome cvs
[07:42] <mdke> exactly, because you have good team management
[07:42] <uws> and so do other gnome-nl people
[07:43] <mdke> if you gave cvs access to a bad translator, it would be a problem, wouldn't it?
[07:43] <uws> I would strongly oppose against anyone from ubuntu-nl committing upstream po files :)
[07:43] <mdke> quite. have you talked to ubuntu-nl about this problem? it's a problem I see in other teams too (ubuntu-fr has like 200 members)
[07:44] <uws> mdke: Well, we don't hand cvs access, that's a gnome-wide decision. But we (as GNOME-NL) would instantly ask for account suspension if someone started committing nl.po files
[07:44] <uws> 200 is WAY too much
[07:44] <mdke> i agree. in ubuntu-it we are much more careful
[07:44] <mdke> it's a balance between encouraging collaboration, and making sure the OS doesn't get translations which are against upstream translation guides
[07:45] <uws> every assh*le with a computer can submit crappy stuff. While I'm glad they use gnome (or ubuntu, whatever), I don't want them participating in things they don't do right
[07:45] <mdke> uws, I agree. But the only solution is to talk to ubuntu-nl, I think
[07:45] <mdke> well, not the only one, but a good start
[07:45] <uws> And as an upstream translator, I think I can claim "some" authority over it..
[07:47] <uws> mdke: I'll talk to them.
[07:47] <uws> mdke: any pointers where I can find contact details?
[07:47] <uws> I'm not into ubuntu management stuff
[07:47] <mdke> sure
[07:47] <JanC> mdke: how do we know which translators do good translations and which do bad translations?
[07:47] <mdke> https://launchpad.net/people/ubuntu-l10n-nl
[07:48] <mdke> JanC, you read their translations
[07:48] <uws> No
[07:48] <uws> we don't
[07:48] <uws> because I don't run ubuntu
[07:48] <uws> I run upstream gnome
[07:48] <JanC> launchpad doesn't tell us who did the translation...
[07:48] <uws> Indeed
[07:48] <mdke> yes, it does
[07:48] <uws> and that's a LARGE part of the problem
[07:48] <mdke> hang on, I'll give you an example, if you'll calm down a bit
[07:48] <uws> the po files don't get a last-translator update
[07:48] <uws> mdke: I still love you :)
[07:49] <JanC> no, it doesn't tell who did what
[07:49] <mdke> i'll be happy to show you what we do in ubuntu-it
[07:50] <mdke> ok. Here's the group. https://launchpad.net/people/ubuntu-l10n-it/+members.
[07:50] <mdke> click on the first guy in the list of "Proposed Members"
[07:51] <mdke> click on Translations
[07:51] <mdke> click on one of his translations, say "gnomebaker"
[07:51] <mdke> oh crap
[07:51] <JanC> which tells me there are about 20 people who worked on it  ;-)
[07:51] <mdke> this won't work, you can't access the translations for italian
[07:52] <mdke> anyway, you click "translate" then you'll see all the suggestions that guy has made
[07:52] <JanC> eh, you have to be admin for that or what?
[07:53] <mdke> you need to be in the translation team for that language
[07:53] <mdke> JanC, you're in ubuntu-nl, right?
[07:53] <uws> the systen is broken by design
[07:53] <uws> I'm really sorry
[07:53] <mdke> uws, feel free to report any problems you see. But I can tell you, the system works, if you have good teams
[07:54] <JanC> yes, but I can't review translations ?
[07:54] <uws> As an upstream author I can't see who broke what
[07:54] <uws> let alone review
[07:54] <mdke> gah
[07:54] <mdke> JanC, if you are in the translator team for a particular language, you can review the translations
[07:54] <JanC> is this only for proposed members?
[07:55] <mdke> if someone wants to join the team, you ask them to contribute some suggestions, and then see whether he follows the TP guidelines, or whatever guidelines you use
[07:55] <mdke> JanC, is what only for proposed members?
[07:55] <JanC> that one can review what someone translated...
[07:56] <mdke> you can see all translations and suggestions
[07:56] <mdke> JanC, aren't you in ubuntu-nl?
[07:57] <JanC> I am in ubuntu-nl & ubuntu-l10n-nl but I can't see that...
[07:57] <mdke> because its ITALIAN
[07:58] <JanC> I can only see a list of packages that people "helped" translate
[07:58] <JanC> or "helped" destroy, as uws would think ;-)
[07:58] <mdke> yeah, you guys should talk to the gnome team, and work out what is going wrong
[07:59] <JanC> I have been talking with them before, but we can't do anything as long as we can't do QA...
[07:59] <copernic> uws: do you know Vncent Van Adrighem?
[08:00] <mdke> ok, I'm telling you now, the italian team is doing it, and so can you
[08:00] <JanC> copernic: yes, we know him
[08:00] <JanC> mdke: if you tell me how I can see who did what...   :)
[08:01] <mdke> underneath each string to be translated, it says the name of a person who made a suggestion, with the suggestion that they made
[08:01] <mdke> with all due respect, anyone who is in a translation team that works via rosetta should really know that
[08:01] <copernic> JanC: I haven't seem him for a while.. did he give up translating?
[08:02] <JanC> but that only works for translations that haven't been applied...
[08:02] <copernic> JanC: we had some great conversations and bugfixes some years ago
[08:02] <JanC> copernic: he's on #gnome-nl regularly
[08:02] <uws> JanC: Nah, not "helped destory"
[08:02] <mdke> JanC, yes. You'd hardly ask a proposed member to translate strings which are already translated
[08:02] <JanC> *sigh*
[08:02] <uws> copernic: Of course I know Vincent van Adrighem
[08:03] <uws> copernic: he's our gnome-nl translator and I meet with him add odd times to discuss gnome-nl issues
[08:03] <uws> s/add/at/ (slip of my muscle memory)
[08:03] <copernic> ok, seems like my absence on irc is paying off :)
[08:04] <uws> copernic: Vincent has been pretty busy lately
[08:04] <uws> copernic: But last week he graduated
[08:04] <copernic> #gnome-nl on Gimpnet?
[08:04] <uws> yeah.
[08:04] <uws> nickname  adrighem
[08:04] <JanC> mdke: how do you know someone keeps translating correctly and how do you know who made some common gramatic error so that you can correct him, etc.?
[08:04] <uws> but he's not here atm, copernic
[08:04] <copernic> uws: yeah, school sucks, I really gave up translation due to classes :(
[08:04] <mdke> JanC, generally, it is sufficient QA to ensure that someone knows how to do that _before_ entering the team
[08:05] <copernic> uws: np, will catch him later
[08:05] <JanC> mdke: nobody is a perfect translator...
[08:05] <JanC> so we must kick everybody and not translate anything anymore?
[08:06] <mdke> JanC, no, I didn't say anything approaching that
[08:06] <JanC> it's not like there are a million people waiting to do the work...
[08:07] <mdke> ok, but it sounds like you have a bit of a quality problem there. So ensuring people know what they are doing before they enter the team sounds like a good start
[08:08] <JanC> that won't work without kicking everyone out first  ;-)
[08:08] <uws> The problem is
[08:08] <uws> translating is too easy with rosetta
[08:08] <uws> the result is low quality
[08:09] <mdke> that is only if entering the right group is too easy
[08:09] <JanC> uws: we could kick everyone out of the team and just appoint some people to apply proposed translations...
[08:09] <uws> Okay, once again.
[08:09] <mdke> if the teams are right, the interface makes translation easier without reducing the quality
[08:09] <uws> I'm NOT involved in Ubuntu. NOT involved. NOT.
[08:10] <uws> I don't care about their management troubles
[08:10] <mdke> uws, you evidently use it
[08:10] <mdke> no?
[08:10] <JanC> mdke: he doesn't AFAIK
[08:10] <uws> mdke: I don't use Ubuntu
[08:10] <mdke> ah
[08:10] <mdke> so it's the flaming from ubuntu users you object to?
[08:10] <uws> I recommended it to lots of people
[08:10] <uws> But I don't use it myself
[08:10] <uws> since I run gnome from cvs anyway
[08:11] <uws> mdke: No, I object to bad translations being shipped with Ubuntu, ignoring our hard (upstream) work to get reasonable quality
[08:11] <mdke> right
[08:11] <JanC> mdke: what rosetta needs is a way to appoint translators to maintain the translation of certain packages...
[08:11] <uws> That's the only thing
[08:11] <mdke> by making these ubuntu-l10n teams, what Ubuntu has done is trusted these groups to take a lot of the responsibility for localising the operating system
[08:11] <uws> What Ubuntu does is great
[08:12] <mdke> now you either (a) object to that decision, or (b) take it up with the local group, afaics
[08:12] <uws> mdke: Yeah, but that obviously introduces a quality assurance hell
[08:12] <mdke> uws, all I can say is, it works ok for me, with an italian desktop
[08:12] <uws> mdke: "Ubuntu" (the entity as a whole) has no way to objectively judge over i18n quality
[08:12] <mdke> uws, how is gnome cvs access given out?
[08:12] <mdke> (for translators)
[08:13] <JanC> mdke: everybody has his/her own packages....
[08:13] <uws> JanC: nope
[08:13] <uws> JanC: 1mmnt
[08:13] <mdke> that's not what I mean
[08:13] <mdke> what I mean is, for someone to get cvs access to gnome as a translator, they go through some quality assurance. All that needs to be done is to do the same for Ubuntu
[08:14] <mdke> because getting access to rosetta is like getting access to gnome cvs
[08:14] <mdke> it shouldn't be given too lightly
[08:14] <uws> mdke: let me explain
[08:14] <uws> gnome-nl has about 6 regular translator
[08:14] <uws> we have 1 coordinator (adrighem)
[08:14] <uws> he's the one who commits the translations
[08:15] <mdke> right, that's exactly how italian works
[08:15] <uws> All translators send po files to him
[08:15] <uws> HOWEVER
[08:15] <uws> some people in gnome-nl have 'elevated' privileges
[08:15] <uws> they can commit stuff without coordinator approval
[08:15] <uws> one of those is me, for instance.
[08:15] <mdke> ok
[08:15] <mdke> that sounds fine
[08:16] <uws> Right now adrighem just commits whatever we send to him :)
[08:16] <uws> without any QA :)
[08:16] <uws> however, most contributors have a pretty good reputation
[08:16] <mdke> all I am saying is that you have quality assurance to get trusted status in the team, and ubuntu-nl should do that too
[08:16] <uws> and if errors are spotted and they come from one specific person, well, that person is simply ignored ;)
[08:16] <JanC> mdke: is there a way to approve all translations from 1 candidate to 1 package at once?
[08:16] <uws> mdke: We have.
[08:16] <mdke> JanC, no.
[08:17] <JanC> you mean, we would have to commit proposals string by string with 2 or 3 people ?
[08:17] <uws> Heh
[08:17] <uws> that bascially means translating again
[08:17] <mdke> you can use as many people as you like
[08:17] <JanC> indeed
[08:18] <JanC> mdke, but we don't have so many people who can do this...
[08:18] <mdke> ok
[08:18] <mdke> that's the point of encouraging new members, by checking their proposals, and then adding them to the team, when you know that they are following the right guidelines
[08:20] <JanC> but it means we can't do translations ourselves for months, coaching some people, and copying *all* their proposed translations 1 by 1 with a very small number of people
[08:21] <JanC> anyway, I'll talk a bit with Seveas about this too
[08:21] <uws> JanC: Yeah, we'd love to get this "fixed"
[08:21] <Seveas> JanC, ?
[08:21] <uws> I think a high quality Dutch translation is a shared goal
[08:21] <mdke> JanC, I'm sure the problem isn't that serious. But if you are asking me "is it better to have 3 high quality translators or 300 bad ones?" My answer would be the former
[08:21] <mdke> the reality is somewhere in between, no doubt
[08:22] <JanC> mdke: but better a not-so-good translation than no translation
[08:23] <JanC> e.g. for packages in universe
[08:23] <uws> Yeah
[08:23] <uws> JanC: Ehm, sorry
[08:23] <uws> no
[08:23] <mdke> I'm not so sure
[08:23] <mdke> it looks pretty unprofessional
[08:23] <uws> No translation is better than some crap I've seen
[08:23] <uws> mdke: indeed.
[08:23] <JanC> that's why I would prefer if it would be possible to assign people to packages to translate
[08:24] <mdke> JanC, you can do that, informally
[08:24] <mdke> draw up a list of high priority packages and assign people
[08:24] <mdke> it's a good idea
[08:26] <JanC> I'd rather have people translate at home and send po-files, it would be easier than using rosetta...
[08:26] <uws> bye
[08:26] <JanC> but that's my opinion of course...
[08:27] <mdke> you can do that with rosetta too
[08:28] <mdke> just use it like cvs, and upload po files
[08:28] <mdke> final thought: I do think that launchpad can do more to assist QA for a team, such as displaying all a person's translations in one place
[08:28] <mdke> and probably lots more
[08:28] <mdke> but there is no substitute for careful team management
[08:30] <JanC> the problem is, if we have to move all but a small number of translators outside of the core team, how many will keep doing translations?
[08:31] <mdke> i agree, there is an interesting social balance between encouraging people, and making sure the QA is good
[08:31] <mdke> the italian team has been grappling with that recently, it can be done, with good documentation, and communication
[08:31] <JanC> I guess the italian team is a bit larger than the dutch team too  ;-)
[08:32] <mdke> well... there are a few old members who are inactive
[08:32] <mdke> but it's quite big yeah
[08:32] <JanC> but I guess I'll have to talk to seveas, as he's the team owner...
[08:33] <mdke> good plan
[08:33] <mdke> it might be worth a discussion on the rosetta-users lists too, given that it is not the only team
[08:33] <mdke> i might write a mail this evening
[08:34] <JanC> one propblem is e.g. that the people I trust the most on doing translations aren't even ubuntu users   :)
[08:34] <mdke> they should definitely use the software they are translating. that's pretty basic stuff
[08:35] <JanC> mdke: they are e.g. gnome-nl translators
[08:38] <mdke> well, Ubuntu has some customisations, and uses a lot of non-gnome software
[08:39] <JanC> yeah, I guess those people are mainly interested in gnome packages...
[08:40] <JanC> but they are the most experienced translators...
[09:52] <dsas> Hi, I'm just wondering how one becomes a 'creator' of a translation file?
[09:53] <dsas> I seem to be for https://launchpad.net/distros/ubuntu/dapper/+source/ubuntu-docs/+pots/desktopguide/en_GB/+translate but have no idea how I got there, I've contributed to the docs a little, but I'm not  a member of en_GB or anything.
[09:58] <mdke> dsas, you need to be in ubuntu-l10n-gb, I guess
[09:59] <dsas> If you go to https://launchpad.net/distros/ubuntu/dapper/+source/ubuntu-docs/+pots/desktopguide/en_GB/+translate I _already_ am listed as translation file creator
[10:00] <dsas> (whatever one of those is)
[10:08] <mdke> dsas, are you listed in Ubuntu English (United Kingdom) Translators
[10:08] <mdke> ?
[10:09] <mdke> oh, sorry I've misunderstood the question
[10:09] <mdke> god knows
[10:09] <mdke> maybe you were the first to visit that url or something ;)
[10:11] <dsas> heh, it seem I created all of the en_GB doc team translations.
[10:13] <dsas> I have rights to translate desktopguide into en_GB despite not being in the ubuntu-l10n-gb team, however I don't have writes to translate about-ubuntu, only suggest.
[10:13] <dsas> yet I'm the creator of that too.
[10:15] <dsas> s/writes/rights
[10:19] <dsas> I did some translation on the quicktour for breezy, I've no idea if they got approved though. I'm also listed as creator of that (https://launchpad.net/products/ubuntu-doc/+series/main/+pots/quicktour/en_GB/+translate)
[10:20] <dsas> Does anyone from the rosetta team know what's going on?
[10:26] <dsas> Is this a bug or a feature? If i export a PO then go back to the translation page for that program, I now have rights to edit it as I see fit.
[10:29] <mdke> dsas, if you can submit translations for an ubuntu file even though you aren't in the right group, it's certainly a bug
[10:48] <dsas> reported as #38928
[10:48] <mdke> bug #38928
[10:50] <dsas> i made the bug private, just in case.
[10:50] <dsas> although I'm always up for a bit of bot kicking.
[10:51] <mdke> ok
[10:53] <dsas> perhaps not entirely neccessary as I think it's related to me being the 'creator', so probably not easily copied by many people.
[10:53] <dsas> I just tried doing it on the chinese translation and it didn't work.
[11:52] <Bunty> hiz
[11:53] <Bunty> i wana know where i can get free cds to pakistan ?
[11:53] <mdke_> Bunty, of Ubuntu?
[11:53] <mdke_> http://shipit.ubuntu.com
[11:53] <Bunty> but they are not offering cds anymore
[11:54] <Bunty> any other ?
[11:54] <mdke_> you can request cds there
[11:55] <Bunty> ok right
[11:55] <Bunty> guys tell me is this site good one so i can present it to the company tomorrow or do i need to make some changes
[11:55] <Bunty> coz i have never worked for some chemical industry
[11:55] <Bunty> www.rjahmad.com/mnc2
[11:55] <Bunty> check it tell me
[12:01] <Bunty> hay listen
[12:01] <Bunty> what are in the cds that are offered by shipit website ?