[00:19] <davidsansome> I uploaded a package to revu about 20 minutes ago but it hasn't shown up on the list yet - does it take a little while or have I probably done something stupid with gpg keys?
[00:32] <RAOF> davidsansome: There is a certain processing time (I'm not sure how long), but do you have a sponsor / FFe / etc lined up for that package?  Lucid is frozen for new packages, so it's likely to sit there until at least after the Lucid release.
[00:36] <davidsansome> RAOF: I'm in no particular hurry to get it in, I suppose it's fine if it waits until after Lucid
[03:31] <psusi> how do I take a trunk and release it as an initial ppa?
[05:05] <_Andrew> Is there anyone I can talk to about packaging up something for Lucid? I want to see this package upgraded to 1.7.0 stable ( https://launchpad.net/ubuntu/lucid/+source/ogre/1.6.4.dfsg1-1 ) however it looks like it's just imported from debian with no ubuntu maintainer?
[05:07] <_Andrew> Actually maybe ubuntu-release is a better place for this..
[05:10] <persia> _Andrew: You'd really want to see it upgraded in Debian first.
[05:13] <_Andrew> Shouldn't the libogremain packages have a virtual package for the latest version? I see two different versions available in lucid because of dependencies on them.
[05:18] <persia> That mostly just needs cleanup on the depending packages.
[07:24] <dholbach> good morning
[11:05] <Laney> wow
[11:05] <Laney> Jack sense now works on my Macbook
[11:05]  * Laney hugs crimsun 
[13:05] <shadeslayer> whats the difference between cowdancer and pbuilder?
[13:05] <hyperair> cowdancer and pbuilder are like apples and oranges
[13:05] <hyperair> you can't compare them.
[13:05] <shadeslayer> ive already read the wiki,but it doesnt cover the differnces
[13:06] <hyperair> you want to compare cowbuilder and pbuilder
[13:06] <shadeslayer> hyperair: hmmm
[13:06] <hyperair> cowdancer uses copy-on-write.
[13:06] <hyperair> and cowbuilder uses cowdancer
[13:06] <shadeslayer> hyperair: whats that?
[13:06] <hyperair> hmm how to explain..
[13:06] <shadeslayer> hyperair: in english :P
[13:06] <hyperair> okay, you know how pbuilder tarballs your chroot, then unpacks it during build?
[13:06] <ari-tczew> is it right channel for asking about SRU?
[13:06] <shadeslayer> hyperair: yeah
[13:07] <hyperair> ari-tczew: #ubuntu-devel i think
[13:07] <ari-tczew> ok
[13:07] <hyperair> shadeslayer: right, cowbuilder basically cp -l's everything so you get a hardlink of every file.
[13:07] <hyperair> shadeslayer: and cowdancer encapsulates everything (like fakeroot) to make sure that whenever you write, the file is copied away
[13:07] <hyperair> and the copy modified
[13:07] <hyperair> so your original remains intact
[13:08] <shadeslayer> hyperair: ah so it kinda makes a copy of everything and then in the end you get 2 things,the original stuff and the modified one
[13:09] <shadeslayer> hyperair: whereas pbuilder modifies the original one
[13:09] <hyperair> shadeslayer: it doesn't make a copy if you reads.
[13:09] <hyperair> i mean
[13:09] <hyperair> if you do reads alone
[13:09] <hyperair> it doesn't make a copy
[13:09] <hyperair> that's why it's called copy-on-write
[13:09] <hyperair> when you start writing, a copy is made so that the original is untouched
[13:09] <hyperair> and pbuilder's "original" is a tarball.
[13:10] <shadeslayer> ok..
[13:10] <shadeslayer> i think ive got some idea....
[13:10] <hyperair> okay, think about it this way...
[13:11] <shadeslayer> hyperair: ok well here comes the next stupid question,which is better :P
[13:11] <shadeslayer> hyperair: sure go on
[13:11] <hyperair> what pbuilder does is like.. tar -xzf sometarball.tar.gz, cd sometarball, edit edit edit, purge.
[13:11] <shadeslayer> ok..
[13:11] <hyperair> what cowbuilder does is like.. it listens to your write() calls
[13:11] <hyperair> and chmod
[13:11] <hyperair> and stuff that modifies things
[13:11] <shadeslayer> and copy edit write
[13:11] <hyperair> right
[13:12] <shadeslayer> got it!
[13:12] <shadeslayer> hyperair: ok so your right they cant be compared :P
[13:12] <hyperair> so your first write() will cause cp fileA tmp/fileA, and redirect writes to tmp/fileA. subsequent reads will read from tmp/fileA
[13:12] <shadeslayer> and it really depends on your pref. which is better
[13:12] <hyperair> well yes
[13:12] <hyperair> each comes with pros and cons
[13:13] <shadeslayer> hyperair: cowdancer probably takes more time to build a package...
[13:13] <shadeslayer> hyperair: oh btw how do i get pbuilder to keep the cache? like while creating the pbuilder tarball
[13:13] <hyperair> pbuilder: it uses tarballs, so when you're not building things, you will use very little space. if you have multiple pbuilder environments, this is wonderful.
[13:14] <hyperair> cowbuilder: it does not compress when inactive, so you get larger storage
[13:14] <shadeslayer> hmm
[13:14] <hyperair> pbuilder: it unpacks the tarball at the beginning of the build, this causes tremendous I/O, and on some filesystems, can cause your system to lock up until it's done.
[13:15] <hyperair> cowbuilder: cp -l everything. that should take a few seconds, or less for preparing. lets you get straight to the job.
[13:15] <hyperair> as for during-compilation... i don't think there is much difference.
[13:15] <hyperair> compilations generally create new files, rather than modifying existing files.
[13:16] <hyperair> copy-on-write does not apply to creation of new files, because there was nothing to copy in the first place.
[13:16] <shadeslayer> ohh... ok
[13:16] <shadeslayer> so basicaly cowbuilder makes links to these files like you said earlier
[13:16] <hyperair> cowbuilder is an alternative to sbuild that uses a pbuilder interface (so it's easier to configure, and doesn't require you to create an LVM partition per chroot)
[13:17] <hyperair> yeah. hard links.
[13:17] <hyperair> i suppose you know what hard links are, right?
[13:17] <shadeslayer> yeah of course
[13:17] <hyperair> so it makes hard links, so new files and stuff mv'd into place will not affect the original
[13:18] <hyperair> rm'd things also don't affect original
[13:18] <hyperair> but chmod/chown, and write will
[13:18] <shadeslayer> nice
[13:18] <hyperair> so it will encapsulate those and force a copy to be made
[13:18] <shadeslayer> ahh.. ok i get it :D
[13:18] <shadeslayer> hyperair: thanks for the info
[13:19] <hyperair> np =)
[13:19] <hyperair> shadeslayer: by the way, hard links are just the way cowdancer implements copy-on-write. there are copy-on-write filesystems around like btrfs. i expect that to be quite cool when it gets stable (it's cool enough already like this)
[13:20] <hyperair> and then there's also unionfs which is another implementation of copy-on-write, one which pretends to be a filesystem.
[13:20] <hyperair> i think it's now superseded by aufs2 or something
[13:20] <shadeslayer> yeah ive heard of those
[13:20] <hyperair> you could probably implement a better cowdancer using unionfs =p
[13:21] <hyperair> there are places where cowdancer complains about stuff being not implemented
[13:21] <hyperair> like flock and stuff
[13:21] <hyperair> i don't really bother -- it shouldn't matter, i think.
[13:22] <hyperair> i maintain a complete ubuntu mirror on my campus so if my chroots get messed up i can always re-create them in a matter of minutes
[13:23] <shadeslayer> nice
[13:23] <shadeslayer> takes about a hour here
[13:30] <lfaraone> How often are the debian bzr branches updated? I want to merge in some changes off a just-uploaded package from Debian.
[13:30] <Laney> lfaraone: I believe you can import-dsc to the debian branch locally
[13:30] <hyperair> shadeslayer: it takes well over an hour for debian ;-)
[13:31] <lfaraone> Laney: yes, but I read that's discouraged against since it can mess up future merges, no?
[13:31] <Laney> I dunno
[13:31] <hyperair> shadeslayer: i can also dist-upgrade to the next ubuntu version in a matter of an hour or so (more time spent on I/O than downloading)
[13:32] <hyperair> use teh git. and git import-dsc =D
[13:32] <lfaraone> Laney: "This import functionality is very convenient, but due to the nature of Bazaar it is not a good idea to do this more than once. If there are two contributors to a package, and they both do the import independently then they will find it difficult to merge between themselves, as the two branches are not related in Bazaar's eyes. "
[13:32] <lfaraone> (per http://jameswestby.net/bzr/builddeb/user_manual/normal.html)
[13:33] <james_w> lfaraone: what package?
[13:35] <shadeslayer> hyperair: nice
[13:35] <hyperair> ;-)
[13:35] <shadeslayer> hyperair: i guess it pays to have a server close by...
[13:36] <shadeslayer> ill probably setup a local ubuntu server when i start earning :D
[13:36] <shadeslayer> so itll be my personal clone of the entire ubuntu repos :D
[13:36] <hyperair> shadeslayer: well yeah. it pays to weasel your way into your university's open source society and use their resources and authority to start an ubuntu server ;-)
[13:37] <hyperair> shadeslayer: the hard disks were donated by the ubuntu-sg loco
[13:37] <shadeslayer> hyperair: i proposed setting up a server in my uni... they shot it down :D
[13:37] <shadeslayer> ubuntu server i mean
[13:37] <hyperair> shadeslayer: well, you need to be more influential than just an ordinary student ;-)
[13:37] <shadeslayer> they run a OS X and a windows server
[13:38] <shadeslayer> hyperair: hehe.. i guess so...
[13:38] <hyperair> shadeslayer: i had support from the teacher advisors of the society, as well as some laboratories which use ubuntu.
[13:38] <shadeslayer> hyperair: nice.. everything my uni uses is MS.. and more MS
[13:39] <hyperair> shadeslayer: couple that with the fact that we started underground (we got permission from one of the labs to use their port 80 and mod_proxy to reverse-proxy stuff from a certain domain name into our server)
[13:39] <shadeslayer> hyperair: heck.. they use a C++ compiler from the 90's
[13:39] <hyperair> shadeslayer: it's the same here =p
[13:39] <shadeslayer> hyperair: borland turbo C++ ?
[13:39] <hyperair> shadeslayer: some labs use ubuntu, but most labs use windows. and a lot of them use windows-only software.
[13:39] <lfaraone> james_w: autokey.
[13:40] <hyperair> shadeslayer: okay, that's sad.
[13:40] <shadeslayer> hyperair: i bet that all ports apart from 8080 are blocked
[13:40] <shadeslayer> hyperair: dont ask....
[13:40] <hyperair> shadeslayer: i requested a DMZ. port 80 was opened, and they claim it's a DMZ.
[13:40] <hyperair> just port 80
[13:40] <shadeslayer> hyperair: good thing my isp just bumped my speed to 70 KBps for free
[13:40] <hyperair> good god.
[13:41] <hyperair> ooh nice
[13:41] <shadeslayer> hyperair: yeah it actually came as a shock...
[13:41] <hyperair> shadeslayer: my ISP did that once.
[13:41] <shadeslayer> hyperair: http://www.airtel.in/wps/wcm/connect/about+bharti+airtel/Bharti+Airtel/Media+Centre/
[13:41] <hyperair> shadeslayer: then they realized their mistake after a few months and dropped the speed again =(
[13:41] <shadeslayer> hyperair: thankfully its not a mistake :D
[13:42] <shadeslayer> hyperair: oh its this one actually : http://www.airtel.in/wps/wcm/connect/About%20Bharti%20Airtel/bharti+airtel/media+centre/bharti+airtel+news/telemedia/pg-airtel-breaks-the-speed-barrier
[13:42] <hyperair> cool =\
[13:42] <hyperair> i want =(
[13:43] <shadeslayer> hyperair: i was actually thinking of switching ISP's :D
[13:43] <shadeslayer> but not after this :D
[13:43] <james_w> lfaraone: yeah, launchpad currently has to mirror the package for it to be imported to bzr
[13:43] <hyperair> shadeslayer: over here we have a few small-time ISPs which suck, and one major ISP which sucks less.
[13:44] <hyperair> shadeslayer: needless to say, they have a monopoly, and continue to suck like hell due to lack of competition =.=
[13:44] <lfaraone> james_w: okay. what's the replication lag currently?
[13:44] <shadeslayer> hyperair: hehe... looks like LP has a full work load : https://launchpad.net/builders
[13:45] <james_w> lfaraone: dunno
[13:45] <shadeslayer> wth... only 4 builders online :D
[13:45] <james_w> it's LP-internal
[13:47] <lfaraone> james_w: I take it that I was correct in my understanding that I shouldn't just import the dsc, right?
[13:48] <james_w> lfaraone: you can, but it won't reflect history quite how you would like
[13:49] <lfaraone> james_w: so you'd advise against it.
[13:50] <james_w> generally, yes
[13:50] <shadeslayer> ah nice...
[13:50] <lfaraone> (at this point I'd need to get a FFe for a NUV, not sure it that'd fly, but the changes made in the NUV have been well tested for a while now in PPA and elsewhere)
[13:50] <shadeslayer> no errors in creating the pbuilder
[14:47] <psusi> hrm... when viewing the bzr branch on lp it recognizes my name on the initial import that I did via lp and hyperlinks it to my lp home page... but the subsequent commits that I did with bzr push from my machine it does not recognize my username and hyperlink... why?
[14:48] <cody-somerville> psusi, you need to do a bzr whoami
[14:49] <psusi> cody-somerville: and?
[14:50] <cody-somerville> set your name and username.
[14:50] <persia> Isn't it bzr lp-login or something?
[14:51] <psusi> ohh... ok, so the full name and email have to match exactly?  I see...
[14:52] <psusi> you'd think it would figure it out when I push and it logs in with my ssh key
[14:55] <cody-somerville> you don't commit when you push, how could it know?
[14:55] <cody-somerville> What if you merge in someone elses branch? Should it just assume all those commits someone else made are yours too?
[14:56] <cody-somerville> persia, no, thats for pushing to launchpad and has nothing to do with commits.
[14:57] <psusi> well then bzr launchlad-login should probably figure it out ;)
[14:58] <cody-somerville> Probably not.
[14:58] <cody-somerville> lp-login only sets the username used when connecting to bazaar.launchpad.net
[14:58] <psusi> why not?  it's authenticating to lp using your ssh key, it seems a good place to check that your bzr whoami matches lp
[15:01] <cody-somerville> psusi, :) I'm sure they'd appreciate a patch then.
[15:03] <psusi> is there a bzr version of cherrypick?
[15:35] <lfaraone> persia: re bug 511502 in dvi2ps, can't we just sync over -3 from Debian? looks like it includes the patch for TexXLive2009, and it builds from source on my machine.
[15:36] <persia> lfaraone: That would be great.
[15:37] <lfaraone> persia: okay, -3 is still in Unstable, but it works fine afaict.
[15:37] <persia> lfaraone: Could you open a new bug for that, and unassign me from the transitoin bug?
[15:37] <lfaraone> persia: in progress :)
[15:37] <persia> I've those three packages locally, and fiddle with them when I have time, but I'll admit to not having as much as I'd like :)
[15:37] <persia> Thanks!
[15:38] <lfaraone> persia: bug 546113
[15:39] <persia> lfaraone: "ubuntu-sponsors" please :)  The ubuntu-*-sponsors groups are going away.
[15:39] <lfaraone> persia: so I should set the transition bug to "in progress" assigning me?
[15:39] <lfaraone> or assinging nobody?
[15:40] <lfaraone> persia: mk. tell requestsync that :P
[15:40] <persia> lfaraone: It's been done.  Which requestsync are you running?  Maybe an old one?
[15:58] <lfaraone> persia: karmic.
[15:58] <lfaraone> persia: 2.10.53ubuntu3
[15:59] <persia> lfaraone: upgrade :)
[16:00] <lfaraone> persia: backports anybody
[16:03] <persia> No point.  It's post-beta, so it's best to be testing on a live system :)
[16:29] <lfaraone> persia: can I subscribe ubuntu-release to bug 546139 even though I haven't prepared the merge yet? (I'm waiting for the release to be imported into LP bzr)
[16:30] <persia> I wouldn't subscribe them until you have something for them to review.
[16:49] <stas> hi guys, i'm trying to patch a package that had no patches before
[16:49] <stas> so I followed this page
[16:49] <stas> http://www.debian.org/doc/manuals/maint-guide/ch-dother.en.html#s-patches
[16:49] <stas> but I got some errors like this
[16:49] <stas> diff: ./alpine-1.0+dfsg/.pc/maildir.patch/imap/src/osdep/unix/maildir.c: Permission denied
[16:50] <stas> can you help me what I'm doing wrong
[16:50] <stas> the error comes after I'm trying to dpkg-buildpackage -d -S
[17:14] <stas> nvm solved
[17:14] <napster> Hi all...
[17:15] <napster> I'd like to do daily builds for VLC media player on PPA on launchpad. Can anyone help me to do this? I've the latest tarballs and build essentials with me
[17:25] <stas> napster: the easies way to do that si to `fork` someones vlc deb sources, take the `debian` dir from there and use it to build your packages
[17:26] <napster> stas, I'm a newbie. Me and most of my friend use vlc. I think it is helpful if I do this. Can you explain a little bit? How to 'fork'?
[17:27] <stas> copy and modify it in case something doesn't work
[17:32] <shadeslayer> hey whats the command to create a new debian/ folder with the new source format?
[17:33] <stas> shadeslayer: http://www.debian.org/doc/manuals/maint-guide/ch-first.en.html#s-dh_make
[17:34] <hyperair> dh_make && echo '3.0 (quilt)' > debian/source/format =p
[17:34] <shadeslayer> stas: thanks
[17:35] <napster> stas, I've 'apt-get source vlc' and copied the debian/ to the latest source tarball from vlc(git)
[17:35] <shadeslayer> hyperair: =p is a part of the command?
[17:35] <hyperair> no it's an emoticon
[17:35] <hyperair> :-P
[17:35] <shadeslayer> hyperair: ah i thought so :D
[17:35] <hyperair>  ;-)
[17:36] <napster> stas, But debuild -S returns errors. How can I fix this : http://pastebin.com/xP30KSME
[17:38] <shadeslayer> napster: you probably want #ubuntu-packaging
[17:38] <stas> napster: first you have to update the changelog
[17:38] <stas> get some docs
[17:39] <stas> it will help you a lot
[17:39] <napster> ah... ok :(
[17:39] <shadeslayer> napster: just browse manpages online : manpages.ubuntu.com
[17:40] <napster> ok
[17:42] <shadeslayer> README.debian and README.source can be deleted right?
[17:42] <shadeslayer> theyre not that imp. i mean
[17:43] <shadeslayer> theres a readme of the package in the source dir though..
[18:03] <ari-tczew> I'm working on switch package to 3.0 quilt format and I;m reading http://wiki.debian.org/Projects/DebSrc3.0#FAQ ; what's the different between quilt and native package?
[18:04] <nigelb> ari-tczew: native packages are ones that are specific to debian with no upstream, like apt
[18:05] <ari-tczew> nigelb, thanks!
[18:13] <shadeslayer> ari-tczew: quilt is a patching system
[18:13] <ari-tczew> shadeslayer: I know
[18:13] <shadeslayer> ari-tczew: ah.. then both of them are quite different :P
[18:14] <ari-tczew> ;]
[18:14] <nigelb> shadeslayer: he was just confused reading the wiki page
[18:14] <ari-tczew> right
[18:15] <shadeslayer> btw do i need to specify in the rules page that install foo.docbook or do i just leave foo.docbook in the debian/ folder and it will be automatically be picked up
[18:16] <shadeslayer> nigelb: ah ok
[18:30] <ari-tczew> what's a field in debian/control: Uploaders?
[18:38] <siretart> ari-tczew: it doesn't really have a meaning in ubuntu. in debian, comaintainers are listed there
[18:54] <EzraR> whats the proper way of dealing with translations, after I update a package the stuff I add isnt translated and gets thrown into the po files
[18:54] <EzraR> lintain says to send a request to debian translaters but that seems rude
[19:21] <shadeslayer> hi i need help with pbuilder :   pbuilder-satisfydepends-dummy
[19:21] <shadeslayer> um i meant this error : http://pastebin.ca/1851718
[19:33] <geser> shadeslayer: my guess is that you don't have universe enabled in your pbuilder
[19:33] <shadeslayer> geser: would that be about it?
[19:34] <akher0n> or karmic-backports (if you're using karmic)
[19:34] <akher0n> at least the first package that's not found is in -backports
[19:34] <shadeslayer> geser: akher0n lucid pbuilder
[19:35] <shadeslayer> ok how do i enable those repos then?
[19:35] <geser> https://wiki.ubuntu.com/PbuilderHowto#Universe%20support
[19:35] <shadeslayer> ah.. thanks
[19:36] <shadeslayer> geser: should i add this to the top or the bottom?
[19:37] <shadeslayer> nvm
[20:39] <MTecknology> Is there any easy way to package a binary only closed source application? - like truecrypt
[20:40] <geser> like any other package but you can probably skip the compilation state
[20:47] <MTecknology> geser: I'm guessing it's been done - truecrypt
[21:10] <kitta1652> Hello.
[21:11] <kitta1652> I need help with an Avaahi related networking issue. I am in a situation where I do not have a DHCP server and need to use APIPA Addressing.
[21:38] <kecsap>  hi all! I would like to push some new softwares to the multiverse repository. I am a newbie here and would like to be an Ubuntu developer. Is it the right process is the reviewing through REVU?
[21:39] <kecsap> (for the new packages)
[23:41] <cousteau> I find it very annoying the way "shared" numeric pads work on laptops, so I made a script that remaps all num pad keys to the numeric version, independently of whether the NumLock or shift are pressed or not
[23:42] <cousteau> I find that it could be useful, so I've made a .deb with it, something useful I can do with it?
[23:44] <cousteau> tried to follow the SponsorshipProcess wiki but got lost in the "report a bug" step
[23:50] <cousteau> cause I don't know which package is this "bug" related to... all the X server?