2009/12/19/#ubuntu-motu.txt

[00:00] <persia> Aha.
[00:01] <persia> So, there's no graceful way to do that, unfortunately.
[00:01] <persia> The ungraceful way to do it is to fiddle around with maintainer scripts.
[00:01] <persia> The maintainer scripts are informed about versions, so as an example, when upgrading the maintainer scripts can know the prior version and the version being installed.
[00:02] <persia> For arbitrary standard stuff (bin, lib, share, etc.) you can just put it in the right place in the new package.
[00:02] <quentusrex> that's basically what is happening...
[00:02] <persia> In cases where migration might break something, it might be nice to try to provide some migration tools.
[00:02] <persia> For configuration, it's a bit trickier.
[00:02] <quentusrex> there are lots of files in the same directory, when they should have been in /etc and /var
[00:03] <persia> You can make some changes, but you can't make other changes (by policy)
[00:03] <quentusrex> ok
[00:03] <persia> For example, you're not supposed to overwrite or change conffiles.
[00:03] <quentusrex> that's fine...
[00:03] <persia> I find http://women.debian.org/wiki/English/MaintainerScripts to be the best available resource on how maintainer scripts work.
[00:04] <persia> Best of luck!
[00:04] <quentusrex> thanks
[00:04] <quentusrex> I'll need it
=== lfaraone_ is now known as lfaraone
[00:59] <dktrkranz> persia: FYI, a good techincal reference for maintainer script is here: http://people.debian.org/~srivasta/MaintainerScripts.html
=== asac__ is now known as asac
[01:40] <EzraR> im trying to package an app that has a debian dir in the source tarball, in the packaging wiki it says to ask the author to delete the debian dir and supply a diff.gz
[01:40] <EzraR> what is the point of the diff?
[01:41] <EzraR> also the author wants to keep the debian dir in the source
[01:41] <EzraR> any advice?
[01:44] <EzraR> they had not deleted the .ex files so I did and got lintan warnings about it, will that be a problem in revu?
[01:47] <quentusrex> How do I do an if statement in debian rules file?
[01:57] <EzraR> quentusrex: just like you would in a shell script i believe
[01:57] <EzraR> quentusrex: it might want a \ after each line
[01:57] <EzraR> something like     if [ $month -eq 13 ]; then
[01:57] <EzraR> 	month=1
[01:57] <EzraR> 	let year=year+1
[01:58] <EzraR> sorry thats not what was suposed to paste
[02:04] <maxb> quentusrex: It rather depends what the circumstances are - sometimes you do it as shell, sometimes you do it using makefile syntax
[02:06] <maxb> EzraR: I _think_ that if there's a debian dir in the upstream source, you have the choice of either trying to work with it (such that the diff.gz adjusts upstreams into yours) or often just giving in and repacking the tarball without it.
[02:06] <maxb> Long term, it sounds like the right thing to do is to engage upstream in a discussion on why they want to have a debian packaging in-tree
[02:08] <wgrant> maxb: Or use 3.0 (quilt).
[02:09] <maxb> I'll learn that once Ubuntu supports it :-) .... (soon, I know)
[02:09] <wgrant> It's been supported for nearly 24 hours.
[02:09] <maxb> heh
[02:18] <wgrant> And it looks like an autosync run happened a few hours ago, and worked.
[02:18] <wgrant> Excellent.
[02:19] <JontheEchidna> sweet
=== asac_ is now known as asac
[03:04] <andrewLuvsUbuntu> Hi All
[03:04] <gaurav> hi tu u
[03:04] <gaurav> too
[03:05] <gaurav> hey can nyone help me
[03:05] <gaurav> ???
[03:09] <ScottK> gaurav: The odds of you getting your question answered go up if you actually ask it.
[03:11] <andrewLuvsUbuntu> Just reading the subject ... I am wanting to see if I can contribute. Although I have only worked with Ubuntu for a short time I have 12 years of professional exp. I will have a look at the site above but any other tips or starting points so I can be useful quickly?
[03:12] <ScottK> andrewLuvsUbuntu: Figure out what you want to work and and be pasionate about making it better.
[03:15] <andrewLuvsUbuntu> Thanks ScottK, is there area's/lists of what Ubuntu covers IE most apps etc are not just Ubuntu
[03:16] <ScottK> andrewLuvsUbuntu: That's true, but everything that is in Ubuntu can be part of helping out.
[03:16] <ScottK> Since you're a volunteer here, figuring out what you want to do is more productive that figuring out what the project needs.
[03:16] <ScottK> (it's needs are broad ranging and approximately infinite)
[03:17] <andrewLuvsUbuntu> Cheers, I will do some reading and come back. But would like to thank you all 9.10 is the best OS I have ever used!
=== Whoopie_ is now known as Whoopie
[04:25] <EzraR> ScottK: I finished that package (mangler) but the debian dir that came with it from upstream had all the .ex files in it still
[04:26] <EzraR> i deleted them but when It builds it leaves them in because of the .orig.tar.gz
[04:27] <EzraR> I cant send it through with those in it, so my only other option is change the orig.tar.gz
[04:28] <EzraR> unless you have a better idea
[04:28] <EzraR> the author wants to keep the debian dir in the source
[04:35] <dhillon-v10> hi all, I noticed that there are a lot of bugs in launchpad that have the tag [needs-packaging] so if I do about 20 of those right am I eligible to apply for MOTU
[05:07] <ScottK> EzraR: Then he should make it a better debian dir.
[05:11] <EzraR> true, i can help him with that
=== mac_v_ is now known as mac_vish
=== mac_vish is now known as mac_v
=== freeflyi1g is now known as freeflying
[12:58] <gaurav2> hey I am new to the concept of MOTU but very excited and want to know how can I start to help
[12:59] <gaurav2> :-D
[12:59] <directhex> ehm... let's see if this works
[12:59] <directhex> !contributing
[12:59] <directhex> bah
[12:59] <directhex> !motu
[12:59] <ubottu> motu is short for Masters of the Universe. The brave souls who maintain the packages in the Universe section of Ubuntu. See  http://wiki.ubuntu.com/MOTU
[13:00] <directhex> urgh, i have no idea which factoids are appropriate here
[13:00] <directhex> generally though, pick what you want to do, and do it - you formally become a MOTU when others have noticed how awesome you are and say "you should become a MOTU"
[13:00] <gaurav2> okkk
[13:00] <gaurav2> would you please guide me
[13:01] <gaurav2> about how should i go about it
[13:01] <james_w> gaurav2: are there any bugs that you reported?
[13:01] <gaurav2> naah
[13:01] <directhex> bug triage & bug fixing is a high priority one
[13:01] <gaurav2> okk
[13:01] <directhex> updating existing packages
[13:01] <gaurav2> hmmm
[13:01] <james_w> is there any software you use that isn't packaged?
[13:01] <directhex> i'd say the least important job is new packages
[13:01] <gaurav2> yeah
[13:02] <gaurav2> I mean it doesn't come in .deb format
[13:02] <gaurav2> then should it be packaged
[13:02] <directhex> if you like. starting with a new package is a kinda trial-by-fire way to learn this stuff, but by all means
[13:03] <gaurav2> hmmm
[13:04] <gaurav2> and how do u fix bugs it must be a really difficult task
[13:04] <directhex> depends on the bug, really
[13:04] <gaurav2> hmmm
[13:05] <directhex> sometimes a bug can be something as simple as "typo in the package description"
[13:05] <gaurav2> okkk
[13:05] <directhex> sometimes it can involve hacking on a package's source
[13:05] <gaurav2> ok
[13:05] <directhex> it's a big wide world out there
[13:05] <gaurav2> true
[13:05] <gaurav2> u r very helpful
[13:06] <gaurav2> and which programming language r most of the packages written in
[13:07] <gaurav2> C++ or Python
[13:07] <gaurav2> :-D
[13:08] <directhex> i think the most popular language in the archive is C
[13:08] <directhex> for some reason
[13:09] <directhex> C++ is popular mostly by way of KDE; Python is popular for more recent high-level app design
[13:09] <directhex> there are loads of languages in the archive though. my personal area of control is C#
=== menesis1 is now known as menesis
=== lukjad007 is now known as lukjad007_
=== lukjad007_ is now known as lukjad007
=== lukjad007 is now known as m0hi
=== m0hi is now known as lukjad007
[13:53] <persia> dktrkranz: Thanks for that.  It's more updated than the one I was using, and at least as complex (although I may need to use a custom CSS to read it often)
=== Amaranth_ is now known as Amaranth
=== slacker_1l is now known as slacker_nl
[17:32] <bdrung> Whoopie: what's your real name? i want to mention it in the debian/changelog for vlc instead of just using "Whoopie"
[18:10] <bjsnider> siretart`, ping
=== Guest40441 is now known as BlackZ
=== yofel_ is now known as yofel
=== yofel is now known as yofel_
=== yofel_ is now known as yofel
[19:17] <matti> ;]
[20:05] <joaopinto> hum, our virtualbox-ose lags behind debian
[20:06] <crimsun> joaopinto: you're free to do the merge
[20:07] <joaopinto> well, the modules fail to build with the current kernel
[20:07] <joaopinto> there is a fix on the gentoo bug tracker, but I am not sure it makes sense to apply it to the current version which is behind debian's
[20:08] <joaopinto> crimsun, I don't like doing merges when I am not familiar whith the problems that required introcuding ubuntu changes
[20:08] <crimsun> 3.1.2 fails to build in lucid?
[20:08] <joaopinto> and certainly not for a a package which includes DKMS, I don't have any experience :)
[20:08] <crimsun> that's somewhat surprising, since 3.1.0 builds fine in lucid
[20:09] <joaopinto> 3.0.8-dfsg-1ubuntu1 is what I get from my archive
[20:09] <joaopinto> lucid
=== korn_ is now known as c_korn
[20:10] <joaopinto> crimsun, I mean, the current version on lucid fails to install, not the debian version on Lucid
[20:11] <crimsun> joaopinto: right, well, it doesn't make much sense to try and fix lucid's existing one because there's already a newer one in Debian sid
[20:11] <joaopinto> I was going to use virtualbox to check test some packages on Debian VM :P
[20:11] <joaopinto> crimsun, right, but someone will need to merge it :)
[20:11]  * ScottK hands joaopinto a mirror
[20:13] <joaopinto> hum, my bug was se to duplicated of bug 474625
[20:13] <ubottu> Launchpad bug 474625 in virtualbox-ose "[lucid] VirtualBox kernel module fails to build against Linux >= 2.6.32" [Undecided,Confirmed] https://launchpad.net/bugs/474625
[20:15] <joaopinto> http://bugs.gentoo.org/290296 is supposed to fix the building failure
[20:17] <joaopinto> well, it's being worked, i just need to fix mine :P
[20:27] <ari-tczew> is possible way to get package's source from Debian on Ubuntu like "apt-get source" ?
[20:28] <ScottK> pull-lp-source in ubuntu-dev-tools.
[20:28] <ScottK> err, pull-debian-source
[20:31] <ari-tczew> this is what I looked for! thanks ScottK
[20:44] <ari-tczew> pbuilder build is for .dsc file but if I have unpacked .dsc and patched (debdiff applied), how can I run pbuilder in directory?
[20:46] <ScottK> You can't.
[20:46] <ScottK> Use pbuilder login to log into the pbuilder chroot and then do it there (then debuild -us -uc)
[20:46] <Laney> pdebuild?
[20:47] <ari-tczew> so how sponsors tests debdiff for merges?
[20:47] <Laney> build a source package and then pbuilder it
[20:53] <crimsun> I use piuparts as well.
=== lfaraone is now known as jwhales
=== jwhales is now known as lfaraone
[21:03] <crimsun> ScottK: do you have time to approve #498354 so I can fulfill the prereqs for #496274?
[21:03]  * ScottK looks
[21:04] <ari-tczew> huh, alsa 1.0.22 is out
[21:05] <crimsun> ari-tczew: yes, I know.
[21:05] <ari-tczew> :)
[21:05] <crimsun> I have utils, tools, and driver done already. I'll svn ci later this weekend to pkg-alsa
[21:05] <crimsun> however, it's not pressing
[21:06] <crimsun> I already backported all the important bits into Lucid's source packages days ago
[21:06] <ari-tczew> crimsun: do you will first update alsa first in debian?
[21:06] <crimsun> ari-tczew: yes
[21:07] <bjsnider> are diffs between one package version and another saved somewhere?
[21:07] <ScottK> crimsun: Very odd it didn't get autmoatically sync'ed.
[21:09] <ScottK> OK, I see it's Unstable.
[21:10] <crimsun> right, and testing's is older
[21:10] <ScottK> crimsun: I can't do the actual sync's needs an archive admin with shell access.
[21:10] <crimsun> ScottK: ah, ok. Sorry about that.
[21:20] <randomaction> bjsnider: if you mean versions in official repos, then yes, they can be viewed in LP branches
[21:21] <bjsnider> in other words, a diff between package-0ubuntu1 and 0ubuntu2
[21:22] <randomaction> you can usually find these in LP, eg https://launchpad.net/ubuntu/+source/gnome-commander/1.2.8.3-0ubuntu1 ("available diffs")
[21:23] <ari-tczew> or put: debdiff *ubuntu1 ubuntu2 > 1_to_2.debdiff
[21:23] <ari-tczew> err, ubuntu1.dsc ubuntu2.dsc
=== Rh0nda is now known as Rhonda
[21:25] <randomaction> sure, debdiff will serve you well if you have the packages downloaded :)
[21:25] <bjsnider> thanks, found it
[21:35] <cratylus> can i choose which repository apt-get source fetches a source package from without apt pinning ?
[21:38] <christoph_debian> cratylus: apt-get source will only work withe the corresponding deb-src line and then understands -t $distribution
[21:39] <cratylus> christoph_debian, so as long as i have the deb-src line in my sources.list somwhaere i can use -t. hmm gonna try this now
[21:41] <persia> Just take care, as this will randomly grab the newest available source when used without -t, which is highly unlikely to match either distribution entirely if used for multiple packages.
[21:41] <persia> There's also pull-debian-source in ubuntu-dev-tools
[21:42] <cratylus> hmm, so far no dice either way, it still prefers karmic to the lucid version that i want
[21:43] <cratylus> persia, will try your method as well
[21:45] <persia> You'll want to run apt-get update to properly test christoph_debian's solution.
[21:45] <randomaction> cratylus: you can use apt-get source PACKAGE=VERSION if you know the exact version to fetch
[21:45] <persia> Alternately, it is potentially possible that the karmic and lucid versions are the same.
[21:45] <persia> randomaction: Only in the case where that version is available in the local apt cache.
[21:46] <cratylus> persia, yeah i made sure to put an entry in /etc/apt/sources.list.d/lucid mirroring the karmic entries but replacing the word karmic with lucid
[21:46] <cratylus> and then updating
[21:46] <randomaction> i agree, apt-get update is good
[21:53] <cratylus> persia, to answer your earlier question, yeah i made sure they're different versions in the release. the package in question is rkhunter and it was converted from dpatch source format to the new "3.0 (quilt)" format. wanted to study existing examples
[22:02] <siretart> bjsnider: whats uo?
[22:05] <bjsnider> siretart, oh good, you're there
[22:06] <bjsnider> you know that problem with karmic's mplayer build where fontconfig was only enabled on i386?
[22:10] <siretart> uh?
[22:10] <siretart> i thought ive fixed that
[22:10] <bjsnider> i just wondered first of all if you remembered it
[22:11] <bjsnider> i guess you do
[22:11] <bjsnider> for some reason
[22:11] <siretart> the rules were/are pretty broken and fail to apply patches on !i386
[22:11] <bjsnider> the one i build on the ppa build system does not apply fontconfi at the very least to amd64
[22:11] <bjsnider> and i'm using your fixed rules file
[22:13] <bjsnider> if i call mplayer by itself with no options, it yaps about missing fonts. if i add -fontconfig to the line, everything's fine
[22:13] <bjsnider> i've got the patch, and the rules file, but it still fails
[22:14] <siretart> is it *really* applied?
[22:14] <bjsnider> if it didn't apply the patch, the build would fail
[22:14] <bjsnider> didn't you submit it upstream?
=== nhandler_ is now known as nhandler
[22:19] <bjsnider> yeah, it's definitely applied. i just looked at the raw file to be patched and it is exactly what the patch expects
[22:20] <Whoopie> bdrung: that's fine as you committed it, thanks a lot!!
[22:21] <bdrung> Whoopie: you're welcome
[22:22] <Whoopie> bdrung: are you also from the sru team?
[22:22] <bdrung> Whoopie: no, i am a normal MOTU
[22:22] <Whoopie> ok
[22:29] <bjsnider> siretart, ok, i was totally wrong. that patch didn't apply on i386 or amd64. i'm looking at the build logs
[22:32] <bjsnider> oh, how stupid of me. i took that patch out of the series file for some reason...
[22:32] <bjsnider> i should have checked that earlier
[22:32] <bjsnider> whoops
[22:48] <quentusrex> Where do I get info on the proper file locations?
[22:48] <quentusrex> where to put documentation? binaries? log files? etc?
[22:52] <crimsun> Debian Policy is a starting point
[23:04] <ScottK> FHS tool
[23:04] <ScottK> too.
[23:04] <xnox> Hello. Does dh 7 style packaging manages DEB_BUILD_OPTIONS in particular parallel building with autoconf project
[23:05] <xnox> s/manages/looks at and uses/
=== jldugger is now known as pwnguin