/srv/irclogs.ubuntu.com/2010/05/22/#ubuntu-motu.txt

=== nobawk|away is now known as nobawk
imbrandonevening all02:19
=== keffie_jayx is now known as effie_jayx
=== effie_jayx is now known as keffie_jayx
=== nigelbabu is now known as nigelb
MTecknologylfaraone: hi, how's it going?05:39
MTecknologylfaraone: I had a question about your pianobar ppa - It won't install - pianobar: Depends: libfaad0 (>= 2.6.1) which is a virtual package.05:42
jetienneq. is there a way to prevent dh_make from interative prompting ?06:42
=== CieD is now known as Ciemon
=== wgrant_ is now known as wgrant
sujihi08:29
nigelbI'm getting a build failure, can someone take a look? http://paste.ubuntu.com/437710/08:29
sujiIn ttf-indic-fonts some fonts has bugs, i cleared that, now how can update that package?08:29
fabrice_spsuji, open a bug report, generate a debdiff, attach it to the bug report and subscribe sponsors08:30
sujifabrice_sp: where to do the things?08:31
fabrice_spsuji, bug report: https://launchpad.net/ubuntu/+source/ttf-indic-fonts/+bugs08:32
nigelbsuji: is your package in debian?08:33
nigelbsuji: if so, fix it there and it will get synced08:34
sujinigelb: Already the ttf-indic-fonts debian package in ubuntu upstream, i just download the tar.gz and clear the bug in 2 fonts from that08:34
fabrice_spyou can check http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ttf-indic-fonts08:34
fabrice_spthe package has been modified in Ubuntu08:34
nigelbsuji: the bug is fixed in debian?08:35
fabrice_sp!info ttf-indic-fonts08:35
ubottuttf-indic-fonts (source: ttf-indic-fonts): Metapackage for free Indian language fonts. In component main, is optional. Version 1:0.5.8ubuntu2 (lucid), package size 8 kB, installed size 36 kB08:35
fabrice_spdebian is at 1:0.5.8, so older08:36
nigelbfabrice_sp: shouldn't we be giving the delta back to debian about now?08:37
sujihttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441901 this bug i thought to say.08:37
ubottuDebian bug 441901 in ttf-tamil-fonts "TAMu fonts use wrong encoding" [Normal,Open]08:37
nigelbsuji: so, fix in debain first I'd say08:38
nigelband you can send the ubuntu changes back, make it 1:0.5.9 and just sync it08:39
fabrice_spnigelb, yes: we should forward the patch to Debian, if it has not already been done08:39
sujibut i cleared that, i correct the encoding.08:39
nigelbsuji: where did you clear it? in ubuntu or in debian?08:39
sujijust i bring the font and map the characters to their proper unicode, now am having that fonts only, from that what i do next?08:40
fabrice_spthe diff between Ubuntu and Debian is quite huge08:40
sujii got the source tarball from ubuntu08:41
fabrice_spand it's in main, so only a core dev can sponsor it08:41
nigelbsuji: right now, I'd say, get the ubuntu specific patches that are not in debian and open a bug in debian bts and send them there08:42
nigelband if you have more fixes, open in debian bts08:42
nigelbonce it has been fixed there, you can request a sync08:42
nigelbfabrice_sp: do we have documentation for this sort of thing? If not, its high time we wrote one08:43
fabrice_spnigelb, you mean about what to do with patches?08:43
nigelbfabrice_sp: yeah, sending to debian, how, when, etc08:44
fabrice_spI remember some wiki page on how to contribute to Debian for Ubuntu dev08:44
fabrice_splet me check08:44
nigelbhttps://wiki.ubuntu.com/Debian/ForUbuntuDevelopers08:44
nigelbgot it!08:44
fabrice_spthis one, yes :-)08:45
fabrice_spin this case, the bug has been opened in 2007, and not fixed since then....08:46
fabrice_spso sending the patch to Debian may not have the effect we expect :-)08:47
nigelbim pretty sure if we give them a patch will have an effect + I know the debian maintainer08:47
fabrice_spin this case, ok :-)08:47
fabrice_spI still have some patch I forwarded some month/year ago that haven't been adopted08:48
fabrice_spso I generally report to Debian and if no news in one or 2 weeks => I upload in Ubuntu08:48
nigelbYou could mail the maintainer or take permission to do nmu08:48
nigelbfabrice_sp: around?09:08
nigelbif someone can take a look at this build failure to figure out whats going wrong, would be much appeeciated09:09
nigelbhttp://launchpadlibrarian.net/48910943/buildlog_ubuntu-lucid-amd64.cdrdao_1%3A1.2.3-0ubuntu1_FAILEDTOBUILD.txt.gz09:09
=== mcl0vin_ is now known as mcl0vin
fabrice_spnigelb, I'll check09:35
fabrice_spTocParser.cpp is generated from TocParser.g, so it's not so easy09:57
fabrice_spyou can check in the upstream cvs, if the problem is solved or not09:59
geserfabrice_sp: partly solved in #ubuntu-packaging10:07
geserupstream included a patch to TocParser.cpp yet patch managed to apply it a second time (at a wrong location) breaking TocParser.g10:08
fabrice_spok10:21
fabrice_spbyt the way geser, did you my message on vtk?10:22
fabrice_spsee10:22
geseryes, I saw it10:23
fabrice_spok. I have a working package in my ppa, if you want to test something10:23
geseris the fixed boost-defaults package independent from the vtk merge or would it also work with the current vtk (and make it installable again)?10:23
fabrice_spit would work with current one10:24
fabrice_spboost-defaults is broken in lucid also10:24
fabrice_spand I'm waiting for the upload to Maverick to follow the sru process10:24
nigelb"dh_install --fail-missing --sourcedir=debian/tmp" in rules causes the build to fail.12:19
nigelbI should be investigating it or just remove --fail-missing?12:19
carstenhnigelb: investigate of course12:23
Gnigelb: check for *.dirs files12:31
Gnigelb: you may have entries surplus to requirements12:32
nigelbG: looks like I didn't add the required entires12:32
arandWould anyone mind sponsoring hardy..lucid in Bug #581331 ?12:40
ubottuLaunchpad bug 581331 in bitlbee (Ubuntu Karmic) "error message while trying to use my MSN account in bitlbee" [High,Triaged] https://launchpad.net/bugs/58133112:41
nigelbIs there a reason why a package cannot be 'debuild -S -sa' a second time?12:48
Gnigelb: what error message do you get?12:56
nigelbG: hold on, let me debuild again12:56
nigelbhttp://paste.ubuntu.com/437747/12:57
Gnigelb: does conf/config.sub still exist?13:01
nigelbG: inside the package?13:02
Gnigelb: also, you are patching configure.ac, are you rerunning autoreconf.sh somehow?13:03
Gnigelb: inside the exploded tree, yeah13:03
nigelbI dont see a conf/config.sub anywhere13:03
nigelbG: No autoreconf.sh file anywhere either13:05
nigelbThere is a configure.ac file in the main package tree13:06
Goh sorry, autogen.sh13:07
nigelbno autogen.sh either13:07
nigelbbtw, I'm not patching configure.ac, at least not that I know13:08
GLine 2913:08
nigelboh13:09
Gnigelb: is a copy of the current source .deb/.dsc file etc available somewhere that I can maybe take a look at, I can't guarrantee anything but I might be able to work it out13:10
Gnigelb: I had similar issues13:10
nigelbI can put it up somwhere and you can take a look at the whole tree13:10
nigelbNow, it works once and built the package, but I expect debuild to work second time too13:11
Gagreed, so would I :)13:11
nigelbcopying, should get copied in a few minutes13:12
nigelbgreat, its going to take 35 minutes :/13:17
Geek13:17
nigelbpeople.ubuntu.come is slow13:17
Gnigelb: do you have a copy of the debian.tar.gz file somewhere (or diff.gz)?13:17
nigelbI wonder if I should put it up on mentors.debian.org13:18
nigelbI do, but its a new upstream version13:18
nigelbso you want the whole thing anyway13:18
GI can grab the upstream tarball myself13:18
nigelbso what do you want? the new diff.gz?13:19
Gyeah13:19
nigelbhttp://people.ubuntu.com/~nigelbabu/cdrdao_1.2.3-0ubuntu1.diff.gz13:20
nigelbG: ^13:20
Gnigelb: giving it a ago now13:27
nigelbG: debuiild works first time13:28
nigelbgive it a second go and it gives you trouble13:28
Ghmmmm that is odd13:32
GI've got a feeling I know why13:32
nigelbooh, why?13:34
Gnigelb: there is a 'make -C' statement in the clean stuff13:34
Ggoing to give something a go13:34
nigelboh13:34
nigelbah, that is changing things post build!13:35
Gand prebuild13:37
nigelbso those lines have to go right?13:38
Gnigelb: I think so, but just looking at something now13:38
Gnigelb: I've got a feeling, that you could replace the whole debian/rules with the new standard simplified version13:44
nigelbG: where do I find that?13:45
=== mcl0vin_ is now known as mcl0vin
Gnigelb: http://stats.nigelj.com/debian.rules13:49
Gcan't believe I had to shuffle the file around about 5 times because all the subdomains i use either have funky rewrite rules or I forgot to change the DNS records :S13:50
nigelbheh13:50
Gnigelb: hmmm, it doesn't fully work it seems, it may need an override :S13:51
nigelbhm :(13:51
Gnigelb: I think you could get away with removing those make rules in clean13:52
nigelbG: the ones we thought were problematic?13:53
Gyeah13:53
nigelblemme try13:53
Gyeah, seems to work for me13:54
Gnigelb: looks like you'll need to replace it with several manual rms in the clean part though13:56
Gbased on diff.gz after the second build13:56
nigelbwell, now it debuild -S -sa works twice13:57
bilalakhtarbdrung: EMERGENCY! The package gnome-media-player which you sponsored failed to build due to chroot problem in powerpc. see https://launchpad.net/ubuntu/+source/gnome-media-player/0.1.2-0ubuntu1/+build/1744204/+files/buildlog_ubuntu-maverick-powerpc.gnome-media-player_0.1.2-0ubuntu1_CHROOTWAIT.txt.gz13:58
macobilalakhtar: there should be a "try again" button if a build fails i think13:58
bilalakhtarmaco: Ohk13:58
nigelbG: several rms? how do I figure which ones?13:59
bilalakhtarBut this was my  very first package that I got into Ubuntu. A disappointment for me,though it is a problem with the buildd machines13:59
bilalakhtarmaco: Its not there13:59
Gnigelb: hold on... something is weird here13:59
Gnigelb: there is: clean: clean-patched unpatch,  cleaned-patch is: clean-patched: patch ....14:00
bilalakhtarWierd. The same package built properly on amd64, armel and i386 architectures14:00
macobilalakhtar: in maverick?14:00
bilalakhtarmaco: Yes14:00
nigelbG: that definitely wierd14:00
macothe weirder architectures sometimes do that ;-)14:00
bilalakhtarCan a MOTU get the package gnome-media-player built?14:01
bilalakhtarI mean rebuilt?14:01
bilalakhtarmaco: See this. http://launchpadlibrarian.net/48903998/buildlog_ubuntu-maverick-powerpc.gnome-media-player_0.1.2-0ubuntu1_CHROOTWAIT.txt.gz14:01
macothats what im trying14:01
Gnigelb: also, it looks like some files have been modified outside of the patch system14:01
macoive hit the try again button on packages in the kubuntu ppas. trying to find where it is in non-ppas because im pretty sure we have access to that too14:01
nigelbG: thats strange. that happens during build time?14:02
Gnigelb: remove the patch part out of clean-patched, and then examine diff.gz14:02
Gnigelb: ahhh maybe14:02
Glet me see14:02
ScottKmaco: If you can upload the package, you should have a rety button.14:02
macothere was one day when every amd64 build for like an hour just fell over with a chroot problem. that was interesting14:02
macoScottK: how do i find it in non-ppas?14:03
bilalakhtarmaco: I think 3 months ago. I faced that problem as well.14:03
macoi am getting lost in launchpad14:03
Gnigelb: oh wait, my mistake14:03
macooh im dumb14:04
macoim not logged in14:04
nigelbhah14:04
ScottKhttps://launchpad.net/ubuntu/+source/gnome-media-player/0.1.2-0ubuntu1/+build/174420414:04
nigelbG: /me bows to DMs and DDs.14:05
macoits before breakfast time! i have an excuse!14:05
bilalakhtarScottK: Yeah that ine14:05
geserbilalakhtar: it's a known bug that some powerpc builds fail with a chroot error14:05
bilalakhtar*one14:05
Gnigelb: debian/rules for me now looks like: http://stats.nigelj.com/cdrdao.rules14:05
bilalakhtarThanks! maybe maco or ScottK did it14:05
Gnigelb: I'm neither :P14:06
macoi clicked it after i logged in14:06
bilalakhtargeser: Why does Ubuntu build packages for PowerPC, anyway?14:06
bilalakhtarI think its unsupported14:06
ScottKbilalakhtar: It's community supported.14:07
ScottKIt works pretty well and has a significant user base.14:07
nigelbG: neither am I, but I understand the daunting task14:07
nigelbG: my rules file looks the same too14:07
* bilalakhtar understands why PowerPC is important14:07
xelisterhi guys, I would like to provide recent compcache for ubuntu. Anyone want to lead me?14:08
xelistercompcache (compressing swap in ram) exists in lucid, but a bit older version and without the userspace tool14:09
xelisterthe package does not yet exist in debian (but work is in progress afaik)14:09
nigelbin that case, I'd guide you to be a DM for that package14:10
xelisterok, so what to do?14:11
nigelbxelister: http://www.debian.org/doc/maint-guide/ch-first.en.html#s-choose14:12
carstenhxelister: is the name of the package compcache-tools?14:14
xelisteryes14:14
xelisterso far I build that program from source (trivial) and it works, in creates an .ko to be loaded and user space tool14:15
carstenhxelister: tomorrow the last response from daniel to this bug ( http://bugs.debian.org/495386 ) is five month ago and the bug itelf is nearly two years old ...14:18
carstenhxelister: I didn't find information about how to handle this situation, just to point to when you highjack the itp14:19
nigelbthe package compcache-tools?14:19
nigelb09:14 < xelister> yes14:19
xelisterbtw Im not any "debian developer" or something yet14:20
nigelbxelister: you can be a maintainer14:20
carstenhxelister: that a two years old itp bug is old enough to be highjacked seems to be obvious14:20
carstenhnigelb: not that fast if you think about "Debian maintainer"14:20
nigelbwell, not that fast, but you can start maintaining it and then later be a DM officially14:21
carstenhxelister: not being a DD or DM doesn'T prevent you from maintaining a package, you just need to find sponsors14:21
carstenhand if your sponsor begins to hate you you become DM14:22
nigelblol14:22
nigelbsame way you become MOTU14:22
carstenhxelister: the first step seems to search for ITP in the developers reference manual and hope that there are some rules you can point to14:23
ScottKThe usual way to take over an ITP is to email the bug and the submitter asking if it's OK and then going ahead in a week or two if you don't hear back.14:23
carstenhxelister: you should do what ScottK suggests :)14:24
xelisterhmm but that was debian's bug not ubuntu14:29
carstenhxelister: if you get the package into debian you need to maintain it there as you are responsible for it. if it is in debian it gets synced to ubuntu automatically.14:29
carstenhxelister: maintaining it in ubuntu when debian possibly has its own version doesn't sound that efficient since everything must be done twice14:30
carstenhxelister: if you don't like to get reach more people with the same amount of work you could also just prepare a new version for ubuntu and ask for a sponsor14:40
carstenhs/get //14:40
arandWould anyone mind sponsoring hardy..lucid in Bug #581331 ?14:40
ubottuLaunchpad bug 581331 in bitlbee (Ubuntu Karmic) "error message while trying to use my MSN account in bitlbee" [High,Triaged] https://launchpad.net/bugs/58133114:40
xelisterhmm actually, that ramzswap did not work perfectly14:50
xelisterperhaps this is because it is supposed to be rather used with .33 kernel14:50
xelistercan I easly upgrade Lucid to .33 kernel?14:50
xelisterand if it turns out it works with .33 kernels only, then does it make sense14:52
carstenhyou can't get a new upstream version to lucid anyway14:53
carstenhbut getting it into maverick is easy14:53
xelisteroverall.. it was not so good tu use .32 in lucid.. things like btrfs suck on .3214:54
arandxelister: You can get mainline build of the kernel for ubuntu for testing purposes: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds?action=show&redirect=KernelMainlineBuilds14:56
xelisteryeah I just ofund that... would be nice to have ppa of kernels like .33 but WITH ubutnu specyfic stuff (drivers)14:56
fabrice_spHi. A small question: where should be installed the .egg-info file in a python package? A patch I sent changed it from /usr/lib/python2.5/site-package to /usr/lib/python2.5/site-pacakge/vtk (it's for python-vtk pacakge)15:22
geserfabrice_sp: try asking the python packaging experts in #debian-python@OFTC15:27
fabrice_spok. Thanks geser15:28
=== nobawk is now known as nobawk|away
=== nobawk|away is now known as nobawk
=== nobawk is now known as nobawk|away
=== nobawk|away is now known as nobawk
ScottLit appears that i found the problem with the ardour mute buttons bug #58178619:57
ubottuLaunchpad bug 581786 in Ubuntu Studio "Mute button not enabled by default in Ardour 2.8.6 Lucid AM64" [Undecided,New] https://launchpad.net/bugs/58178619:57
ScottLsorry, wrong channel :P19:58
=== kmdm is now known as Guest54370
=== kmdm is now known as Guest62013
=== nobawk is now known as nobawk|away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!