/srv/irclogs.ubuntu.com/2009/05/09/#ubuntu-motu.txt

* Laney battles lplib00:03
NCommanderdirecthex, yay, welcome to the MOTU club!00:11
directhexNCommander, do i get to ride around on some kind of sabretoothed tiger and chop up bad guys?00:12
NCommanderdirecthex, nope00:12
directhexaw man, wrong MOTU :(00:12
Laneyyou get to learn the secret handshake and have plumbers do work for you in half the time00:12
Laneysee: the stonecutters00:13
directhexi can't join a secret society which is against the metric system00:13
Laneyoh, you can now get a free LWN subscription00:14
directhexhow about a hat? something dapper?00:15
directhexat a jaunty angle00:15
directhexman, ubuntu releases could totally be about hats instead of animals00:16
Laneyredhat have the hat thing going on already :(00:16
binarymutant^ too much like fedora00:17
persiajames_w, The reason for sponsor membership is historical and related to bugmail.  Feel free to raise for discussion.01:09
persiadirecthex, I'lll add you to the team.  Welcome!01:09
directhexpersia, hello01:09
james_wpersia: I'll bring it up sometime, thanks01:10
directhexpersia, it was suggested by Laney that karma demands i do some sponsoring given how much sponsoring i've expected in the past01:10
james_wheh01:10
* james_w notes that the sponsorship queue is quickly ballooning01:11
persiaOoh.  Someone else already added you.  Nifty.01:11
directhexi think it was TheMuso01:11
persiaYeah.  I just received the membership addition mail between saying I'd add you, and the error.  No idea why it was delayed.01:12
directhexclearly you ran out of internet, so it was held up01:14
=== funkyHat is now known as fun
=== fun is now known as funkyHat
binarymutantIf anyone has the time to review my package for lxsplit, I would greatly be appreciate it. It can be found here http://revu.ubuntuwire.com/p/lxsplit thank you for the time  :)01:39
binarymutantdid I miss revu day :(02:17
=== jcastro_ is now known as jcastro
brywilharrisSo who wants to REVU a package?03:29
brywilharrisSo who wants to REVU a package?03:31
brywilharrisAnybody want to review a new package?03:34
hyperairjust post the link03:34
hyperairwhoever's dropping by will look at it03:34
brywilharrisGreat, thanks03:35
brywilharrisI was beginning to think my client was borked.03:35
hyperairheh03:35
* hyperair still doesn't see a link03:35
brywilharrisGimme a minute03:36
_stochastic_http://revu.ubuntuwire.com/p/a2jmidid03:36
brywilharrishttp://revu.ubuntuwire.com/p/veusz03:36
hyperairnow then.. let's apt-get source both of them..03:37
* hyperair will look at a2jmidid first (it's simpler)03:38
brywilharrisOK03:38
* _stochastic_ is happy!03:38
hyperairdisclaimer: i'm not a MOTU, i'm just helping out because i'm bored.03:39
hyperairand i've got one hell of a block trying to figure out how to write my nautilus-share patch03:39
brywilharrisThanks anyway03:39
hyperairnp03:39
hyperairhmm waf eh..03:39
brywilharriswhat's the problem you're working on?03:39
hyperairbrywilharris: segfault.03:39
hyperairbug #25857003:40
ubottuLaunchpad bug 258570 in nautilus-share "nautilus crashed with SIGSEGV in strlen()" [Medium,In progress] https://launchpad.net/bugs/25857003:40
hyperair_stochastic_: alright, first step.. bump up your Standards-Version03:42
hyperairW: a2jmidid source: out-of-date-standards-version 3.8.0 (current is 3.8.1)03:42
_stochastic_when did that happen?03:42
_stochastic_3.8.0 was the standards version when I uploaded it03:43
hyperairdebian sid.03:43
hyperairi mean 3.8.1 is the new Standards-Version in debian sid, and karmic.03:43
_stochastic_okay03:43
brywilharrishell 3.7.3 was the standards version when I uploaded...03:44
hyperairheheh03:45
hyperairthat's not even jaunty. that's intrepid i believe.03:45
brywilharrisIt was03:46
brywilharrisat the time03:46
* hyperair facepalms.03:47
hyperairwaf.03:47
hyperairgood god03:47
hyperairwhat's with the huge amount of obfuscated code there?03:47
hyperairor is that base64'd stuff?03:48
brywilharrisin a2jmidid?03:48
hyperairyes.03:48
hyperairi've personally never used waf before so i can't comment on whether those strange looking symbols are suupposed to be there or not03:49
brywilharriswtf is waf?03:49
lifelessits a build tool03:50
hyperairanother ridiculous python-based build system03:50
lifelesssimilar in many ways to scons03:50
hyperairindeed03:50
brywilharrisAh03:50
hyperairit was inspired by scons, which in my opinion, is THE most ridiculous build system i've seen.03:50
lifelessthe base64 code is equivalent to configure - it allows a waf project to be fully selfcontained03:51
* hyperair needs to take note not to make statements like this after becoming UCD.03:51
brywilharrisso where are you seeing base 64?03:51
lifelesshyperair: scons has some issues, its true.03:51
hyperairbrywilharris: look at the bottom of the waf file03:51
hyperairlifeless: what exactly is in this base64'd code?03:51
lifelesswafs library03:52
hyperair_stochastic_: ping.03:52
lifelesscompressed03:52
hyperairlifeless: good god. how ridiculous.03:53
lifelesswhich is morally equivalent to configure03:53
lifelesswhich is the autoconf library compiled for a specific project03:53
lifelessits no better or worse03:53
hyperairi don't remember seeing base64 code in autofoo03:53
lifelessthe base64ness is irrelevant03:53
hyperairit is.03:53
lifelessconfigure isn't the preferred form of modification03:53
hyperairthat's true.03:54
hyperairbut it looks goddamn obfuscated.03:54
lifelessconfigure is the output of a compiler; so is that code blob03:54
lifelesshave you read a configure recently?03:54
hyperairsure i have.03:54
lifelessnot exactly the shining light of small and simple sh code03:54
hyperairin fact, i've patched it03:54
lifeless*not* a configure.ac.03:54
hyperair...yes sir, i know the difference between configure and configure.ac03:54
lifelessgood, just checking.03:55
lifelessanyhow, I'm not here to defend waf per se; but I think the self-hostingness (which is optional btw) is fairly well done03:55
brywilharrisSo what's the difference03:55
hyperairand i think it's ridiculous.03:55
brywilharrisI mostly write python code now03:55
hyperairso let's leave it as that.03:55
hyperaireither way, i'm supposed to be reviewing a package, not commenting on the idiocy of upstream's build system of choice.03:56
hyperair_stochastic_: you there?03:56
brywilharrisWhen I was writing code you still had a separate build and link step...03:56
hyperairmeh he disappeared.03:56
hyperairi think make's awesome enough not to require crazy python hacks.03:57
_stochastic_hyperair, sorry I ran away for a second04:00
hyperairah he's back!04:01
hyperairso anyway04:01
hyperairwhere was i04:01
brywilharriswaf?04:01
hyperairnevermind waf.04:01
hyperairright. debian/rules.04:01
hyperairi'm not very familiar with the old debian/rules way04:01
hyperairit's too easy to accidentally leave something out04:01
hyperairi'd instead suggest the minimal dh7 rules way =D04:02
_stochastic_care to show a template/example/spec?04:03
hyperairhmm04:03
hyperairwhere can i find an example..04:03
lifeless/usr/share/doc/debhelper/examples/simple04:03
lifelessor something like that04:03
hyperair_stochastic_: you can take a look at geanygdb in revu04:03
lifeless/usr/share/doc/debhelper/examples/rules.tiny | rules.simple04:04
hyperair"man dh" for more information04:04
hyperairit's awesome stuff.04:04
hyperairyou could also use cdbs, but many people say it's black magic.04:05
brywilharrisYo got that right04:05
hyperairmostly because it's that much harder to trace through a million and one .mk includes04:05
_stochastic_is there anything wrong with the way its packaged?04:05
lifelessas opposed to a mass of perl that calls a long arbitrary list of programs and hides errors?04:05
lifeless:)04:05
hyperair_stochastic_: you might like to ask upstream to include the GPL license.04:05
hyperair_stochastic_: seems they forgot.04:05
_stochastic_it is included04:05
hyperair_stochastic_: i don't see a LICENSE or COPYING file anywhere04:05
_stochastic_look again, it's titled gpl.txt04:06
hyperairooh it is04:06
hyperairgpl2.txt04:06
_stochastic_yes04:06
hyperairalright then04:06
_stochastic_that's a new warning in REVU, it wasn't there a couple days ago04:06
hyperair_stochastic_: your debian/watch isn't working.04:06
_stochastic_oh? okay, I'll look into that04:07
hyperairUnknown verb pattern '' in regex; marked by <-- HERE in m/^(?:(?:http://download.gna.org)?\/a2jmidid\/)?a2jmidid-(*) <-- HERE .tar.bz2$/ at /usr/bin/uscan line 897, <WATCH> line 2.04:07
hyperairvery strange.04:07
hyperairah04:07
hyperairright04:07
hyperair.*, not *04:07
_stochastic_ah04:07
hyperairhttp://download.gna.org/a2jmidid/a2jmidid-(*).tar.bz204:07
hyperairsee the * there04:07
_stochastic_yes04:08
hyperairthey don't release .tar.gz's do they?04:09
_stochastic_nope04:09
hyperairhmm i see.04:09
_stochastic_are you sure it should be .* the filename looks like a2jmidid-4.tar.bz204:09
hyperairyes i'm sure04:10
hyperairthis is regex.04:10
hyperairman 7 regex for more information04:10
hyperairtest it with uscan04:10
_stochastic_okay04:10
_stochastic_done.04:10
brywilharrisuscan --verbose04:11
hyperairalright, onto your copyright file04:11
brywilharrissorry go ahead04:11
hyperairhaha no problem04:11
hyperairyou're missing a few copyrights04:11
_stochastic_? which files?04:12
cody-somervilleNCommander, I noticed that grendal has been maintaining the debian packaging in the pike CVS04:12
cody-somervilleNCommander, so I'm attempting to rebase all the changes in Debian onto the debian packaging in the CVS04:13
hyperaireh um nevermind04:13
hyperairwhoops04:13
brywilharrishttp://revu.ubuntuwire.com/report.py/legal?upid=564404:13
hyperair./.waf-1.4.3-4cc0bec64a165ffe5dd3eed60cd2e01b/wafadmin/pproc.py <-- this04:13
hyperairheheh04:13
hyperairbut i suppose this is one of the autogenerated files04:13
* cody-somerville hopes what he is doing is sane. :)04:13
hyperairso nevermind04:13
cody-somervillehyperair, In that case, the clean rule should delete that04:14
hyperaircody-somerville: no i was messing around with waf earlier.04:14
hyperaircody-somerville: i'll unpack it again to check later04:14
cody-somervilleok04:15
hyperairi remember hearing some mention about needing to use the copyright symbol instead of (C)/(c)04:15
hyperair©04:16
hyperairthis one04:16
_stochastic_previous REVU uploads I've had accepted just used (c)04:16
hyperair_stochastic_: i think you can actually merge all the Nedko Arnaudov entries. i noticed you have three of those.04:16
hyperair_stochastic_: it's a very recent change.04:16
brywilharrisalias ©='echo GPLv3'04:17
hyperair._.04:17
hyperair_stochastic_: also, i'd actually suggest that you document which copyrights go to which files04:18
_stochastic_hyperair, which of Nedko's entries? where?04:18
hyperairin debian/copyright04:18
hyperair    Copyright (c) 2008 Nedko Arnaudov <nedko@arnaudov.name>04:18
hyperair    Copyright (c) 2008 Nedko Arnaudov <nedko@arnaudov.name>04:18
hyperair    Copyright (c) 2007,2008 Nedko Arnaudov <nedko@arnaudov.name>04:18
hyperairthree.04:18
_stochastic_ahh04:18
hyperairwell actually two, but you repeated one of them04:19
hyperairof course, if it's not too much trouble, you should actually document which copyrights go to which files04:19
_stochastic_in the machine-readable format? or is there another way?04:19
hyperairwell you don't necessarily have to use machine readable format, but if you were to use it, there's http://wiki.debian.org/Proposals/CopyrightFormat04:20
_stochastic_so can  Copyright (c) 2007,2008 Nedko Arnaudov <nedko@arnaudov.name> be used for all of Nedko's or does another need to explicitly list 2008 only?04:21
hyperairi'd actually merge the files that belong to Nedko04:22
hyperairin one single listing04:22
_stochastic_okay04:23
hyperairyou're also missing one of the brackets in Copyright C) 2009, Eric Hedekar <afterthebeep@gmail.com>04:25
hyperairand now the customary test-build.04:25
brywilharrisfor foo in `grep -ir '(c)' .|cut -d ':' -f 1|uniq`; do sed  -e 's/(c)/©/' $foo >temp; mv temp $foo; done04:27
brywilharrisjust make sure you don't have any variables named 'C'...04:28
hyperairi think you meant sed -i -e $foo04:30
hyperair-i means edit in place04:31
brywilharristhat would work too04:31
brywilharrishowever, this breaks python files as I just discovered...04:31
hyperairalso, the © was supposed to be in the debian/copyright file i think04:31
hyperairor something like that04:31
brywilharrispython complains about the character encoding04:32
hyperairi think it's permitted to be (c) in tbe actual sources04:32
brywilharrisIt has to be04:32
hyperairyeah04:32
hyperairhaha04:32
_stochastic_hyperair, any other issues you can spot?04:36
hyperair_stochastic_: gimme a moment to build04:37
hyperairi was updating my karmic pbuilder earlier04:37
hyperairmeanwhile, i'll take a look at veusz i guess.04:41
brywilharriskk04:42
hyperairbrywilharris: regarding your rules file... why don't you use a .install file instead of manually running install -d -m644 bla04:43
brywilharrisOK04:43
hyperairW: a2jmidid: binary-without-manpage usr/bin/a2j_control04:47
hyperairW: a2jmidid: binary-without-manpage usr/bin/a2jmidi_bridge04:47
hyperairW: a2jmidid: binary-without-manpage usr/bin/a2jmidid04:47
hyperairW: a2jmidid: binary-without-manpage usr/bin/j2amidi_bridge04:47
hyperair_stochastic_: ^04:47
hyperairyou're gonna have to write manpages for all of those =)04:47
hyperairand then add them to debian/manpages04:47
hyperairman dh_installmanpages for more information04:47
brywilharrisI gotta go to bed05:08
brywilharrishyperair: Thanks for the help05:08
binarymutantIf someone has the time to review my package http://revu.ubuntuwire.com/p/lxsplit I would greatly appreciate it :)05:30
abuDawudcan someone explain the basic process of repackaging an unstable debian package to the latest and greatest Ubuntu distro?05:30
lifelessabuDawud: generally its just a sync05:31
lifelesshttps://wiki.ubuntu.com/MOTU has docs05:31
binarymutantabuDawud, you pretty much just change the changelog and control file05:31
lifelessbinarymutant: unless it needs patching you should sync it not change changelog05:32
abuDawuddoes it involve the apt pinning process if I wanted to use apt source for requisitioning the files?05:32
abuDawudor is that over complicating things?05:32
binarymutantlifeless, I understand :)05:33
abuDawudessentially I am looking for an easy intro project into packaging after reviewing all of the documentation. I figured that would be pretty simple05:34
binarymutantabuDawud, a sync is pretty much just a bug report05:34
abuDawudbinarymutant, I will look at the link lifeless posted and read up about it.05:34
abuDawudis there somewhere simpler to start?05:34
lifelessshould we archive blankon-extra-backgrounds in revu, 6 months and the poster hasn't updated05:35
lifelessabuDawud: the simplest place to start is to fix a bug in a package that is in Ubuntu05:35
lifelessabuDawud: that way you're working with existing code and package, only making a small change, and don't need to know all the ins and outs05:36
abuDawudlifeless, I have been trying to find one that is not patched using harvest and looking through launchpad and I can't seem to find one05:36
lifelessabuDawud: what do you mean?05:37
abuDawudwell I can't seem to find where to watch for simple bugs that just need repackaging etc05:37
abuDawudall of the bugs I find seem to either be complicated code issues or they are fixed05:38
lifelessabcmidi is an example of package which has been synced, rather than patched by ubuntu05:39
lifelessabuDawud: are you interested/experienced with any particular programming languages/environments?05:39
abuDawudlifeless, a bit of perl but its all intro stuff05:39
abuDawudlifeless, I was trying to find a way to help out with my limited code knowledge05:40
abuDawudlifeless, packaging seemed to be the way to go05:40
lifelesspackaging is useful, but to package code properly you need to understand that particular language05:41
lifelesswhen packaging you will run into compile problems/link errors/dependencies/language issues05:41
lifelessthe more you understand the particular language[s] the thing you are packaging is written in, the easier it is for you05:42
binarymutantabuDawud, if you use the advanced search in launchpad you can find new bugs that need to be triaged or for packaging you can look through this listhttp://www.debian.org/devel/wnpp/orphaned05:43
abuDawudbinarymutant, thanks, I think I have some more reading to do :)05:44
lifelesswhats with licencing pacaking data (often under the (C) threshold anyway) as GPL05:54
lifelesssurely same-licence-as-package would be better05:54
binarymutantI <3 gpl05:55
lifelessso do I05:56
lifelessfor software05:56
binarymutanthow about for a Makefile? It scare me to see the nvidia license in a Makefile05:57
fabrice_spHi. Anyone with access to a powerpc computer? I'd like to know what is the return value of dpkg --print-installation-architecture06:28
blacknred0how come after making a package from a single script and then installing it the script will not go to /usr/sbin? what could of cause this?06:32
fabrice_spblacknred0, inside your deb package, is it in /usr/sbin?06:36
blacknred0fabrice_sp, no06:38
blacknred0so i figure that it will never execute06:38
blacknred0how i could make the package and placing my script on /usr/sbin whenever any user executes the command?06:39
fabrice_spblacknred0, during the building of your package, you need to 'move' the files in the correct temporary directory?06:39
fabrice_spthis temporary directory is debian/<package name>/usr/bin06:39
binarymutantIf someone has the time to review my package http://revu.ubuntuwire.com/p/lxsplit I would greatly appreciate it :)06:40
blacknred0fabrice_sp, nope... currently is mypackage/tmp not mypackage/debian/...06:40
blacknred0thnx... facbrice_sp.... i would do that then...06:41
fabrice_sp;-)06:41
blacknred0fabrice_sp, so one last question.... so should i call form rules that package? or should i have a tmp for that same script?06:43
fabrice_spblacknred0, just put your script in the right place, in the install target in debian/rules, and it should be ok06:45
blacknred0ok, thnx :P06:45
fabrice_spbinarymutant, I'm trying to build your package in amd64, but it's not possible06:45
fabrice_spis it normal?06:45
fabrice_spI'm getting: lxsplit_0.2.4-0ubuntu1.dsc: amd64 not in arch list: i386 -- skipping06:46
binarymutantfabrice_sp, arch i38606:46
fabrice_spbinarymutant, why? It's not compatible with amd64?06:47
binarymutantfabrice_sp, the site didn't say it wasn't, I should change to arch all06:49
fabrice_spbinarymutant, yes06:49
fabrice_spas amd64 is a growing arch, it would be a pity not to have it :-D (and I won't review the package :-) )06:50
binarymutantfabrice_sp, should be able to build on your architecture now, srry :)06:54
fabrice_spbinarymutant, uploaded to revu?06:55
binarymutantyes06:55
fabrice_spok (trying to build again)06:56
fabrice_spbinarymutant, all no. It's for arch independant packages. This one in compiled, so it should be any06:58
binarymutantfabrice_sp, oh okay, thank you, I get those two mixed up sometimes06:59
fabrice_spso do I :-) But when building, and you see a *_all.deb, it clarify things :-)06:59
binarymutantis there anything else that is noticeable to you fabrice_sp, it's my first C package so I'm very concerned about it07:00
fabrice_spbinarymutant, I'll have a look at the packaging now (as arch is not correct, I'm getting errors in lintian)07:01
fabrice_spyou miss ${shlibs:Depends} in depends for the binary package07:02
fabrice_spyou should drop the A in the description (the short description extend the phrase this package is a ...)07:03
fabrice_spfor the long description, don't repeat the short description07:03
fabrice_spfor man page installation: I generally prefer to have it in a manpages file, but the way you do it is correct07:06
fabrice_spthe same for docs07:07
fabrice_spotherwise, looks good (and simple ;-) )07:07
binarymutantthank you for your time I'll correct these :)07:08
fabrice_spyou're welcome. Did you uploaded a 'any' package?07:09
fabrice_sp(just to check the resulting package)07:09
binarymutantthe last two issues about the manpage and the docs, could you elaborate?07:09
fabrice_spyes :-)07:09
fabrice_spinstead of putting the name of the file you will install (for doc or for manpage) in the debian/rules file, you can put that in dedicated files in debian directory07:10
fabrice_spmanpages for man file07:10
fabrice_spdocs for doc files07:10
fabrice_spthis way, you could even have a more simple rules file, using cdbs :-)07:10
fabrice_sp(a 2 lines rules file :-) )07:10
binarymutantoh instead of using dh_ I get you07:11
fabrice_spyou still nee the dh_ stuff, but this way, it's easier to add a file07:11
fabrice_sps/nee/need/07:11
binarymutantsince its my first C package I wanted to try it with debhelper instead, it feels more in depth to me. But i've done a cdbs package and it definitely was simpler07:12
fabrice_spI mean, you will have dh_installman instead of dh_installman debian/lxsplit.107:12
fabrice_spit's a good approach to learn ;-)07:12
binarymutantif you still have any time to spare the updated package been cached into revu07:15
fabrice_spok. I'll download it again07:16
binarymutantty :)07:16
artfwoHello! I am having a hard time resolving FTBFS of my REVU upload (on karmic). Does anyone have a little time to help?07:34
hyperairartfwo: what's wrong?07:34
artfwowell, here's the upload in question http://revu.ubuntuwire.com/p/scantailor07:35
artfwoand it fails to build in the PPA07:35
artfwohttps://edge.launchpad.net/~artfwo/+archive/ppa/+build/98761607:35
artfwothere're lots of cryptic preprocess messages in the build logs, which have led me to debian bug 50510907:36
ubottuDebian bug 505109 in boost1.35 "FTBFS with GCC 4.4 and breaks other apps" [Important,Closed] http://bugs.debian.org/50510907:36
artfwoit's fixed in the latest debian, yep07:36
artfwoso07:37
artfwoI have merged boost1.35 from debian and also uploaded it to the PPA07:37
hyperairhave you tried building with a sid pbuilder?07:37
artfwonope, didn't think of it07:37
artfwobut anyways07:37
hyperairi'm giong to try building07:37
artfwoboost1.35 also fails to build in the PPA/Karmic after the merge07:38
artfwodue to the following error:07:38
artfwo../boost/test/impl/debug.ipp:280: error: 'sscanf' is not a member of 'std'07:38
artfwowhich again led me to upstream07:38
artfwohttps://svn.boost.org/trac/boost/ticket/154207:38
artfwo(comment:1)07:38
artfwoit does not seem to be fixed upstream, but I wonder if I can replace <stdio.h> with <cstdio> in my merge to fix it07:39
hyperairah!07:40
hyperairright!07:40
hyperairi had an issue with that as well07:40
hyperaircstdlib07:40
hyperairyou need to include cstdlib to each and every one of those files using sscanf07:40
hyperairit's not included by default any more07:40
artfwozomg07:40
hyperairhahah07:40
fabrice_spartfwo, why using an old boost version?07:41
artfwofabrice_sp: mainly chose it because it's in main07:41
fabrice_spthere isn't a boost1.37?07:41
fabrice_spin main also :-)07:42
artfwothere is, but boost1.35 is in main, so it's better supported and all, right?07:42
artfwohuh?07:42
fabrice_spmy bad: 1.37 is in universe07:42
fabrice_spbut I remember ScottK trying to get rid of boost1.3507:43
fabrice_spso try with 1.3707:43
ScottKActually it was boost, which is 1.3407:43
ScottKWe need to pick a target boost for Karmic.07:43
artfworight you are, 1.37 is in main as well: http://packages.ubuntu.com/source/karmic/boost1.3707:43
ScottK1.37 or 8 not sure.07:43
artfwo1.38 is universe07:43
fabrice_spohh: i'm bad at numbers :-)07:44
ScottKDoesn't mean it will stay that way.07:44
artfwodamn, I have already opened a merge bug for 1.3507:44
fabrice_spanyway, a new package should use the latest version of a lib, right?07:44
ScottK1.38 is the version Debian is aiming to use for Squeeze, so the faster we can line up on that the better.  Might be Karmic + 1 though.07:44
artfwookay, I shall try 1.37 for now07:45
fabrice_spScottK, this kind of things will be decided at UDS?07:45
ScottKI hope so.07:45
fabrice_spok07:45
artfwobut then again - is 1.35 going to sink away from karmic at all?07:46
fabrice_spartfwo, until UDS, we don't know. But it could be07:50
artfwookay07:50
savvasso the new boost is built?07:52
savvasI'll have to proceed with cgal then :)07:53
savvasgood morning btw :P07:59
artfwowell, it fails to build with boost 1.37 as well, but I think it's a matter of another bug - debian bug 52575208:00
ubottuDebian bug 525752 in kmldonkey "FTBFS with GCC 4.4: missing #include" [Unknown,Open] http://bugs.debian.org/52575208:00
_stochastic_Do any MOTUs want to take a look at this upgrade request that's ready for upload Bug #36773508:00
ubottuLaunchpad bug 367735 in calf "upgrade to newer upstream version" [Wishlist,In progress] https://launchpad.net/bugs/36773508:00
artfwoeverything has worked so nice on jaunty :(08:02
fabrice_spartfwo, we are so early in the cycle, that it's normal to have this kind of things08:05
artfwoyep, but this GCC cleanups in Karmic have just uncovered an upstream bug, which I've got to fix and forward to the author08:06
artfwothe only thing that frustrates me, is that I don't currently have enough bandwidth for pbuilder08:07
savvas_stochastic_: 1) you need to follow sponsorship process: https://wiki.ubuntu.com/SponsorshipProcess 2) did you test-build your new package?08:10
_stochastic_savvas, yes I've tested it and the upstream version fixes some bugs08:12
_stochastic_the bug is already attached to the universe sponsors, should I just sit and wait?08:12
savvasoh ok, I think what's left now is to subscribe ubuntu-universe-sponsors08:13
_stochastic_they're already subscribed08:14
savvashm..08:15
savvasit's in the activity log but not in the subscribers list08:15
savvasweird08:15
savvas_stochastic_: oh by the way, you changed the status of the bug after subscribing the sponsors, please set it back to confirmed :)08:16
_stochastic_savvas, is there anywhere that the status policy is outlined?  I constantly am adjusting things to what I think should be the right status, but then am told to change it etc.. (it was set to triaged not confirmed)08:18
savvasit shouldn't matter what the status is, but I think "in progress" means you would take care of the sponsorship yourself08:19
_stochastic_should it go back to triaged or be switched to confirmed?08:19
_stochastic_to me, in progress was referring to the fact that progress has been made on the bug08:19
savvasif you have bug control permissions, make it triaged, if not then confirmed :)08:20
_stochastic_savvas, that sponsorship link you sent me claims that all bugs ready for sponsorship shouldn't be assigned to anyone, should I remove myself from that position now?08:21
savvasI didn't see any outline or policy about the status, but that's what I was advised to follow hehe. you shouldn't change the status after subscribing the bug to the sponsors08:21
savvasyes, that's true forgot that :)08:22
savvas_stochastic_: do you see ubuntu-universe-sponsors on the right subscribers list?08:26
_stochastic_savvas, yes I do.  don't you?  refresh?08:26
savvasI have :\08:26
savvaslet me check with the normal launchpad server08:27
_stochastic_I also see it here: https://bugs.launchpad.net/~ubuntu-universe-sponsors08:27
savvaswell launchpad bug I guess :)08:27
savvasconfig.sub config.guess08:30
savvasthese are files right?08:30
savvasnot that important but if you require to make any new changes to the debian package, instead of "rm -f config.sub config.guess" use "dh_clean config.sub config.guess08:31
savvasI mean something like this: http://paste.ubuntu.com/167576/08:33
savvasany motu to review http://revu.ubuntuwire.com/p/gnote ?08:38
LucidFoxsavvas> I'm hesitant to take responsibility for uploading it :/08:39
savvasabout tarball-in-tarball? :)08:41
lifelesssavvas: tarball-in-tarball is when I stopped reviewing08:43
savvaslifeless: tarball-in-tarball in general or just the fact that the maintainer used tar.bz2?08:47
binarymutantIf someone has the time to review and possibly advocate my package http://revu.ubuntuwire.com/p/lxsplit I would greatly appreciate it08:49
lifelesstar-in-tar08:50
lidaobingsavvas, if the upstream use tar.bz2, you can repack it with "uscan --repack"08:50
lifelessI would have said 'bz2' if I mean that08:50
fabrice_spbinarymutant, you didn't fixed the depend line08:53
fabrice_spW: lxsplit: missing-depends-line08:54
binarymutantfabrice_sp, is Depends: ${shlibs:Depends}, not correct?08:55
fabrice_spthis is what lintian tell me when I run it against deb file08:57
fabrice_spW: lxsplit: missing-depends-line08:57
fabrice_spif it's normal (no dependency), you should override this lintian warning08:57
savvaswell I see that's in generally not recommended on the Debian side, so I'll talk to nyu about extracting it. thank you all!08:59
binarymutantfabrice_sp, there are no dependencies09:00
fabrice_spno even on c libs?09:01
fabrice_spcould be09:02
fabrice_spdpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}09:06
fabrice_spduring build. This would explain why no dependency09:06
binarymutantI'm not sure I understand, what options are you using with lintian?09:08
binarymutantI've grepped through the includes on the files, http://paste.ubuntu.com/167625/09:10
=== paul_ is now known as Elbrus
binarymutant#include "stuff" is that for including files from the same directory? or is that from /usr/include too?09:14
savvasdoes that need dh_makeshlibs and dh_shlibdeps in binary-arch rule?09:16
binarymutantah right, that might be it09:16
binarymutantthanks :)09:16
savvasI'm really not sure, but try it :)09:17
binarymutantwhat lintian options should I be using? I had been using -ivv09:18
tuantubi have the same warning : "warning: unknown substitution variable ${shlibs:Depends}" while building a package, what can i do to correct this ?09:19
fabrice_spdh_makeshlibs09:20
savvasdpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}09:22
savvasdpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}09:22
savvasstill there :P09:22
savvasI tried this:09:22
savvasdh_makeshlibs09:22
savvasdh_installdeb09:22
savvasdh_shlibdeps09:22
lifelesstuantub: it means the package doesn't have a library in it09:22
lifelessthat particular binary09:22
tuantublifeless: more detailed ? :-/09:23
tuantublifeless: is that important or i can simply ignore it while building packages ? :-/09:24
binarymutantI can't get the lintian error :(09:26
fabrice_spdid you run it on the deb?09:26
fabrice_spbinarymutant, ^09:27
binarymutantfabrice_sp, on the *.changes09:27
fabrice_spbuild the package and run lintian on the deb09:27
savvas$ lintian -i lxsplit_0.2.4-0ubuntu1_amd64.changesW: lxsplit: missing-depends-line09:28
binarymutantah!09:28
savvasbinarymutant: not *_source.changes :)09:28
binarymutantthank you thank you09:30
kostmoI'm packaging an upstream source with a daemon that needs a configuration file to run.  This configuration file is stored in a subdirectory of the main source directory.  Can I use debian/conffiles to specify this file somehow?10:09
kostmoThe file needs to end up in /etc/ when installed.10:11
binarymutant"dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}" I'm getting this when I run pbuilder on my package, what does this mean? I'm using debhelper10:21
lidaobinghello, how clearsign a file with two gnupg key? (I am processing my new pubkey with this document: http://www.debian-administration.org/users/dkg/weblog/48)10:34
geserbinarymutant: it doesn't know what it should replace this variable with. this warning is common as not every package using it in Depends, specifies a value which should get put in (so doesn't really need it in Depends)10:57
geserlidaobing: gpg -u keyid1 -u keyid2 --clearsign filename11:05
=== jussi01 is now known as Tuhina
=== Tuhina is now known as jussi01
=== paul_ is now known as Elbrus
lidaobinggeser, thanks11:08
binarymutantgeser, thank you for the info. Do I need to keep it so that I don't get lintian errors though since I'm using debhelper?11:10
geserI assume you shouldn't get any lintian errors if you remove it11:11
=== bastiao__ is now known as k0p
binarymutantcool, thanks geser :)11:14
binarymutantIf someone has the time to review and possibly advocate my package http://revu.ubuntuwire.com/p/lxsplit I would greatly appreciate it :)11:21
=== ember_ is now known as ember
trip0anyone recommend repository creation/managment software?12:56
binarymutanttrip0, like a version control system?12:58
trip0sorry, debian repository12:59
=== kev__ is now known as triple0
=== triple0 is now known as tripzero0
=== nhandler changed the topic of #ubuntu-motu to: Jaunty is released | Time for SRUs: http://qa.ubuntuwire.com/sru/ | Development of Karmic Koala has started -> https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTU? https://wiki.ubuntu.com/MOTU/Contributing | http://qa.ubuntuwire.com/ftbfs/
LucidFoxLaney> Thumbs up for your work on f-spot in Debian!14:07
LaneyLucidFox: \o/ let's hope it can stay in sync14:11
* LucidFox nods14:11
sebnerLaney: though you should have left it to "New" since u-m-s will set it to Confirmed :P14:11
Laneysebner: I *just* changed that14:12
Laneyit was only set that way because requestsync messed up14:12
sebnerLaney: kk14:12
sebnerLaney: btw, can we sync gnome-do-plugins from Debian. What's with the use_csc patch in ubuntu?14:13
Laneyno, I'm afraid not14:14
LaneyI did the dfsging differently in Debian14:14
Laneyunless you can convince meebey to upload the same thing as +dfsg114:14
sebnerLaney: what's the differenz?14:16
LaneyUbuntu has the gdata lib in BundledLibraries/14:16
LucidFoxLaney> Have you talked to meebey yourself about it?14:18
LaneyLucidFox: no, because I don't think it's worthwile14:18
LaneyI don't mind just waiting for a new upstream14:18
sebnerLaney: override override override14:19
sebner:P14:19
LucidFoxHe seems quite cooperative about Ubuntu compatibility, judging by my experience with f-spot.14:19
Laneyyeah he's fine, I just think it'd be a waste of time14:19
LucidFoxI wonder if it would make sense for me to rejoin u-u-s if I don't actively sponsor, but occasionally stumble upon a patch or sync/merge request subscribed by u-u-s that I want to work on.14:25
james_wLucidFox: you *could* actively sponsor :-)14:29
james_wlidaobing: this ibus upload doesn't require rebuilding the other ibus packages or anything does it?14:30
Laneysponsor-5-a-day?14:30
=== asac_ is now known as asac
lidaobingjames_w, do not14:35
james_wlidaobing: great, thanks14:35
lidaobingjames_w, ibus 1.1.0.* does not remove any API14:35
james_wlidaobing: I'll review and upload now14:35
lidaobingjames_w, there is a symbol file record this14:35
james_wah, nice14:35
lidaobingjacob, in debian/libibus0.symbols14:35
LucidFoxjames_w> qutecom built in karmic pbuilder fine for me14:36
lidaobingjames_w, thanks14:36
LucidFox-6, that is14:36
james_wLucidFox: yeah, sorry about that14:36
james_wLucidFox: please go ahead and ack it14:36
james_wI'll unsub the sponsors if you like14:36
LucidFoxok14:36
AdamDHcan any one recommend any packages that go off and downloads binary sources?14:46
AmpelbeinAdamDH: what do you mean?14:53
kklimondaAdamDH: flashplugin-nonfree14:54
AdamDHah thanks flash-plugin is a good example, how when the package is installed it will download binarys so they are not part of the package14:57
AdamDHafter Januty what is the next version called?14:58
NafalloKarmic14:59
ghostcubewhen will the anjuta bug be fixed in jaunty15:00
ghostcubestill no dist-upgrade possible15:00
ghostcube2 weeks now15:00
kklimondawhat bug?15:01
ghostcubeinstall overwritr libgbf-1-215:01
ghostcubeits even not possible to get it manually15:02
ghostcubehttps://bugs.launchpad.net/ubuntu/+source/anjuta/+bug/33846415:03
ubottuUbuntu bug 338464 in anjuta "[Jaunty] anjuta >2.25 needs Conflicts: libgbf-1-2" [Undecided,Triaged]15:03
ghostcubestill no fix15:03
AdamDHneed to get my packages into revu for Karmic, try and get them included15:03
kklimondaghostcube: you could uninstall libgbf-1-215:04
ghostcubenope15:04
kklimondasure, it's just a suggestion ;)15:05
ghostcubedoesnt work15:05
kklimondahmm.. i can't reproduce it on my system..15:05
ghostcubei can give you a pastebin15:05
ghostcubeit happens at upadte15:05
ghostcubefrom intrepid15:05
kklimondacan you paste a result of dpkg -L libgbf-1-2 ?15:06
kklimondabut that's weird - anjuta should remove libgbf-1-2..15:07
ghostcubehttp://pastie.org/47301515:08
kklimondait replaces libgbf-1-common so it should just remove it and libgbf-1-215:08
ghostcubeitzs not removable15:08
ghostcubethis is an manual purge15:08
ghostcubei posted you15:08
ghostcubei can try to force dpkg15:08
kklimondawhy can't you remove it?15:09
ghostcubesee the post of pastie says cant remove15:09
kklimondait does? :)15:09
ghostcubeah sorry german lol15:10
kklimondayeah..15:10
kklimondatry LC_ALL=C <command>15:10
geserghostcube: try "sudo apt-get remove libgbf-1-2" and check what else it wants to remove before proceeding15:10
ghostcubei can show you15:10
ghostcubei did that15:11
ghostcubelibgbf-1-2* libgbf-1-common* libgladeui-1-7*15:11
* sebner waves at geser \o/15:11
ghostcubepkg: Fehler beim Bearbeiten von /var/cache/apt/archives/anjuta_2%3a2.26.0.0-0ubuntu1_amd64.deb (--unpack):15:11
ghostcube Versuche, »/usr/bin/gbf-am-parse« zu überschreiben, welches auch in Paket libgbf-1-2 ist15:11
ghostcubeFehler =Error15:11
geserbut it wanted to upgrade anjuta before it removed libgbf-1-215:11
kklimondaghostcube: it happens when you try to remove libgbf-1-2 ?15:11
ghostcubeyes15:12
ghostcubeand if i do dist-upgrade15:12
geserso you need to "help" it a little bit to force the correct order15:12
ghostcubealways the same15:12
ghostcubegeser: i tried to remove it before install no way15:12
geserwhich error?15:12
ghostcubethe one i postet already15:12
ghostcubethis is manual15:12
ghostcubeit doesnt remove the package it installs first15:13
ghostcubedont ask me why it does this15:13
ghostcubenever had this before15:13
geserah, so this is from "apt-get remove libgbf-1-2" and not "apt-get install anjuta"?15:13
gesertry removing anjuta too (temporarily) and install it again when libgbf-1-2 got removed15:14
ghostcubeah ok15:14
ghostcubeworked15:16
ghostcubethx15:16
ghostcubebut this is bad trouble as it seems15:17
ghostcubeinside some packages15:17
kklimondait shouldn't happen as anjuta conflicts with libgbf-1-2..15:18
ghostcubeyeah its a bit weird15:18
ghostcube:)15:18
kklimondai don't have a II system anymore to test upgrade..15:18
ghostcubebut thx anjuta removal temp fixed it15:18
LucidFoxdirecthex, get aggregated on Planet Ubuntu already! :)16:03
james_wdh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)!16:07
james_wdirecthex: xsp ^16:07
hyperairxsp?16:08
hyperairalso, dh_clideps has a bug that results in a false positive until very recently.16:09
Laneysome genius fixed it16:09
* hyperair whistles16:11
hyperairthat reminds me of something i should add to my UC application16:11
LucidFox^_^16:15
sebnerhyperair for UC \o/16:16
LucidFoxsebner> https://wiki.ubuntu.com/hyperair/UniverseContributorApplication16:16
sebnerLucidFox: nahah, can't comment because I worked too little with him (I know that he is a cool/clever guy though)16:17
* hyperair feels flattered16:18
* a|wen wonders why regina-normal seems to be acting out at each merge16:18
LucidFoxregina-normal?16:19
a|wenthe configure script refuses to find libboost-python whatever i do :/16:19
hyperairpython?16:21
LucidFoxHa ha16:22
hyperairshouldnt it be setup.py then?16:22
a|wenwell, python is just one of the 3 or 4 frontends built by the package16:22
a|wen(and yeah, it has multiple backends as well)16:23
geserfor which boost version does it look?16:23
a|wenwe try to make it find 1.3516:24
geserhave you a log from configure you could paste?16:24
hyperairpastebin the configure.ac or configure.in file. that could probably yield something about how it's looking for libboost-python16:25
hyperairassuming it's an autotools script16:25
directhexjames_w, it's a false message, i'd ignore it if i were you16:26
james_wfair enough16:26
james_wI did, I was just passing it along instead of filing a bug as would take just a few seconds to commit it directly if needed16:27
a|wenthe configure run http://pastebin.ca/S:141740916:27
a|wenand configure.ac http://paste.ubuntu.com/167900/16:27
james_wdear libplasma-dev, why are you out of date? no love, James16:28
gesera|wen: does a configure.log also exist?16:30
a|wengeser: no ... neither before or after a configure run16:31
geserhmm, or was the file named config.status?16:32
geserusually there is a file which is more verbose then the configure output16:32
a|wenthere is a config.status ... just need to get it out of the chroot16:33
james_wconfig.log16:33
james_wit's not always in the root16:33
a|wenwhat is it that i need to install to have the cli pastebin thingy?16:34
james_wa|wen: pastebinit?16:34
a|wen:)16:35
a|wenconfig.status http://pastebin.com/f13848d0016:35
a|wenconfig.log http://pastebin.com/f43e6ccb116:37
geserthe second pastebin doesn't want to load here16:40
geseryou broke pastebin.com: Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 1095524 bytes) in /home/pastebin/lib/geshi/geshi.php on line 247416:40
a|wenoh, ups16:41
Ampelbeinjames_w: hi. regarding sync of mldonkey: the problem is with the Replaces: in dh-ocaml, http://paste.ubuntu.com/167905/ . It replaces ocaml-nox (<= 3.10.2-3) but as we have 3.10.2-3ubuntu1 in the repositories, the replaces doesn't work right. should i change dh-ocaml to represent the ubuntu-version?16:41
lidaobingAmpelbein,  change to: "<= 3.10.2-3.1~"?16:43
james_wit sounds like the Ubuntu version of ocaml-nox might be wrong16:43
geserI've filed a bug to get dh_ocaml moved to main to ocaml can build which should "fix" this too16:44
james_wwe have 3.11.0-516:45
a|wengeser: there is something in there that doesn't look good ... http://paste.ubuntu.com/167909/16:45
directhexwhich chickens do i sacrifice to advocate a package in REVU?16:45
gesera|wen: that's the reason why it couldn't find boost-python. Now you "just" need to find out why this happens :)16:47
geserjames_w: only in source, binary are in depwait in dh-ocaml16:47
Ampelbeinthere is two issues here, i think. first is that our version of ocaml-nox is still with the dh-stuff included, second is the wrong replaces in dh-ocaml which should refer to the ubuntu-version16:48
a|wengeser: to me it mostly looks like some syntax error ... and it being in a boost file16:50
james_wAmpelbein: yeah16:51
=== jussi01 is now known as tuhina
fransmanHow do I get a new package in Ubuntu, what's already in Debian?17:06
fransmantalking about openerp-client-web17:08
fransmanhttp://git.debian.net/?p=debian/openerp-client-web.git17:08
a|wenfransman: it's in unstable?17:09
fransmana|wen: I am not sure17:09
a|wenfransman: it doesn't look to be in debian officially yet ...17:12
=== DktrKranz2 is now known as DktrKranz
fransmana|wen: Okay, but do we need to open a ticket yet?17:17
a|wenfransman: if it get's into debian before the the feature freeze is there, you just need to test that it builds and runs on ubuntu and file a sync request (and possibly a sponsor) ... that is indeed the easiest way17:18
james_wanyone have an opinion on this patch? http://launchpadlibrarian.net/26477752/splashy_0.3.13-3ubuntu2.debdiff17:27
=== azeem_ is now known as azeem
directhexhm. lsb-release isn't in a base ubuntu image?17:27
james_wI can't remember whether that it encouraged, or discouraged, or neither17:27
james_wdirecthex: how base?17:27
directhexjames_w, pbuilder build17:27
james_wdirecthex: lsb-release probably isn't, but lsb_release might be17:28
directhexlsb-release is the package17:28
directhexmake: lsb_release: Command not found17:28
james_wah17:28
directhexcausing me strife. i'll add a build-dep17:28
james_wTask: minimal, mythbuntu-backend-master, mythbuntu-backend-slave, mythbuntu-desktop, mythbuntu-frontend17:29
a|wenjames_w: i would say that it makes sense with that patch ... but i don't know how our policy is17:29
james_wso it should be in any minimal install17:29
directhexsometimes life doesn't work out that way :(17:30
bizkutroot@wrt:~# cat /etc/issue.net17:33
bizkutUbuntu karmic (development branch)17:33
bizkutroot@wrt:~# uname -a17:33
bizkutLinux wrt 2.4.37 #3431 Thu May 7 07:36:38 CEST 2009 mips GNU/Linux17:33
directhex@_@17:33
directhexbizkut, you have an ARM box?17:33
bizkutdirecthex, i got a nlsu217:34
bizkutbut that's my wrt router17:34
directhexi meant MIPS17:34
directhexbut i'm dim, and mildly drunk17:34
bizkutyeah wrt350n17:34
bizkutlol17:34
bizkutbut still stick with 2.4 kernel for networking thing17:35
bizkutso lame17:35
* hyperair mutters darkly about how intensely stupid the intel gpu driver is.17:46
doctormoOK, I'm going to try this again now that I'm not sick and tired17:47
doctormoI'17:47
doctormoI'm not that good at packaging, I'm much more familar with python packages, which are dead easy.17:48
doctormoBut this package I have is more troublesome, it's not python, it's a binary package containing user space modules for epson scanners.17:48
doctormoIt requires postinst and prerm scripts to be run, but my attempts at including these scripts have so far failed.17:49
directhexdoctormo, what have you tried to do?17:49
a|wenwhat is the news with libboost1.37 ... can we use it?17:49
* hyperair thinks python packages are a pain.17:50
hyperairautotools packages are dead easy.17:50
doctormoWell, I have the rules file and I created debian/postinst and debian/prerm files, didn't work.17:50
directhexhyperair, port them to ipy!17:50
hyperairdirecthex: nothanks.17:50
directhexdoctormo, how is your rules file written? cdbs, dh7, dh6 (lots of dh_foo commands), something else?17:50
doctormodh6, I gather, I'll pastebin it17:51
* a|wen mutters something about autotools and python combined17:51
doctormohttp://pastebin.com/m55dfa40a17:51
directhexa|wen, autofoo generally.17:51
james_wdoctormo: how many binary packages does the source package build?17:52
doctormojames_w: one, but it may or may not be good to have one per driver.17:52
a|wenwell, just not very easy to figure out what goes wrong17:52
directhexdoctormo, okay, for the sake of argument, can we try porting to dh7?17:53
directhexdoctormo, in case it's a missing dh_ stanza?17:53
doctormodirecthex: sure thing, your the bos17:53
james_wdirecthex: nope17:53
james_wdh_installdeb is there17:53
directhexjames_w, oh. hrm...17:54
james_wdoctormo: your sh_shlibdeps shouldn't be after dh_builddeb, but that's irrelevant17:54
directhexdoctormo, is it that preinst et al are not being executed, or are not being packaged? try running "dpkg -I /path/to/output.deb preinst" to make it show you the contents of the preinst17:54
james_wthere's no point in trying to calculate that stuff to put in the debs if they have already been built17:54
doctormodirecthex: They're not being packaged, the control.tar.gz doesn't contain them as it should.17:55
james_wdoctormo: also, presumably these modules aren't arch independent, so you should be doing the work in binary-arch, not binary-indep17:57
james_wdoctormo: you can turn on DH_VERBOSE and get some visibility in to what is going on18:00
james_wmaybe not enough, but it might work18:00
doctormojames_w: Thanks, these are things I don't know.18:01
doctormohttp://divajutta.com/doctormo/iscan-plugins-all.tar.bz2 <- these are the relivent files18:02
doctormojames_w: I have 2 parts, one is a 64 bit version and the other is a 32 bit version, I must admit to attempting packaging beyond my station. I'm such there is a lot at fault with it.18:03
james_w# Automatically added by dh_makeshlibs18:04
james_wif [ "$1" = "configure" ]; then18:04
james_wldconfig18:04
james_wfi18:04
james_w# End automatically added section18:04
james_wthat's a bit worrying18:04
james_wis this file (postinst) just taken from epson?18:05
doctormojames_w: yep, made sure there was distributing rights first though.18:06
james_wwell those file will want some fixing18:06
james_wbut that's not the immediate problem18:06
james_wsed s/#DEBHELPER#// < debian/postinst > debian/iscan-plugins/DEBIAN/postinst18:08
james_wso it's doing the right thing18:08
james_w     998 bytes,    28 lines * postinst             #!/bin/sh18:08
james_w     132 bytes,     7 lines * postrm               #!/bin/sh18:08
james_w     900 bytes,    22 lines * prerm                #!/bin/sh18:08
james_wI don't see the same problem as you18:09
doctormojames_w: let me try again, `debuild` right?18:10
james_wthat was just "fakeroot debian/rules binary"18:10
james_wdebuild should work though18:10
doctormohmm18:11
james_wyou're not building the -64 package are you?18:12
doctormojames_w: no, is there a way to organise these two packages together?18:13
james_wprobably18:13
doctormohuh, well it all seems to work, I guess I was just too tired and sick to test it right last week18:16
a|wenjames_w: can you look at this ... doesn't this look like boost borked-ness? http://paste.ubuntu.com/167909/ (this is 1.35)18:24
james_wyeah, might be18:28
a|wenjames_w: it looks to be the compiler going angry at the syntax ... anyone we want to report it too?18:29
james_wwell, I'd confirm it was a problem in boost first18:30
james_wa minimal test case would be useful if it is18:30
a|wenokay ... i'll just make a new fresh karmic chroot and see if i can make a small test case18:35
gilirjames_w: thanks for the ACKs :)18:36
james_wgilir: np18:36
james_wgetting quite tiring now though, when are you going to stop for the day :-)18:36
giliralso need to do something else for today :)18:38
james_wI can't test xapian-omega as xapian-core FTBFS on i38618:42
a|wenjames_w: i have a "hello world" script to show the problem ... but apparently it is already known to broken18:52
james_w1.35?18:53
a|wenjup18:53
a|wenjames_w: for reference ... this fails http://pastebin.com/f44e8048818:55
tgm4883is there an easy way to test postinst without having to build the package each time?19:03
bddebianCould someone possibly upload gnote for me from REVU?  I seem to have issues logging into REVU these days.19:13
Laneyif you upload it I can archive19:15
bddebianI'm not sure I can upload to Ubuntu atm :(19:16
bizkuthttp://osgeeks.blogspot.com/2009/05/compiling-ubuntu-karmic-koala-mipsel.html19:18
dtchenbddebian: you can.19:23
dtchenBarry deFreese    2005-09-06 21:09:02 UTC  2005-09-06    2010-04-06 00:00:00 UTC  2010-04-06   Approved19:23
=== tuhina is now known as jussi01
gesera|wen: compiling your paste with "g++ -I /usr/include/python2.6/ -l boost_python-py26 -lpython2.6 foo.c -o foo" works here (a karmic pbuilder)19:25
=== ripps_ is now known as ripps
a|wengeser: wich version of libboost?19:26
geserlibboost-python-dev               1.34.1-15ubuntu319:26
a|wenwell... i'm claiming that 1.35 is broken19:27
bddebiandtchen: I mean I don't have an Ubuntu box atm and I don't think I have dput set up for Ubuntu on sid but forget it19:27
Laneydebsign the packages for me and I'll dput19:28
Laneythat works, right?19:29
a|wengeser: 1.37 works fine as well, and i suppose 1.34 also does, though i haven't tested that19:32
geserthe package for libboost-python-1.37-dev looks broken for me: /build/buildd/boost1.37-1.37.0/debian/libboost-python1.37-dev/usr/share/python-support/pyste/Pyste19:33
geseris one of the dirs in the deb19:34
a|wenhe, that does not look good ... but at least it let's some things compile19:35
gesera|wen: https://svn.boost.org/trac/boost/ticket/206919:54
a|wengeser: that does indeed look like it19:57
gesertry applying the mpl.patch from this ticket19:57
a|wengeser: i'll try that a little later (rebuilding my karmic pbuilder af debootstrapping works) ... my real problem was solved by just switching to 1.37 (though someone needs to fix that packaging)20:00
gesera|wen: after applying mpl.patch, your paste builds with boost1.3520:03
a|wengeser: okay ... it sounding like swithching to 1.37 was encouraged over 1.35 so might just stick with that; but i'll apply and test just so we can get it fixed20:04
bizkuthow to automate "apt-get -b source" the Unmet build dependencies when "apt-get -b source"?20:08
RoAkSoAxhey guys, how can I figure out why it FTBFS ? or how do I know which dependencies have failed to install?20:09
macoRoAkSoAx: read through the log it emails you?20:09
hyperairjpds: having done considerable work on tomboy-latex's packaging, may i add my name to debian/copyright?20:11
RoAkSoAxmaco, k thanks20:13
Laneyfun fix for anyone wanting to work on ubuntu-dev-tools: find all mentioned Ubuntu codenames and convert them to be pulled from LP using the API20:14
LaneyI made ubuntuDevelopmentSeries() but you could use the API to get all current series20:14
jmarsdenLaney: Wouldn't that make using the tools when one lacks an Internet connection impossible?  Or are you arranging for the tools to cache the set of names?20:20
nhandlerLaney: That would be a little annoying to do for the non-python scripts20:20
nhandlerjmarsden: Some of the tools do require an internet connection to work20:21
LaneyMost of them, I'd imagine20:21
Laneynhandler: Yes. One could code up a wrapper to output them.20:21
kklimondahey, when i compile source I get an error "error: ignoring return value of ‘write’, declared with attribute warn_unused_result", is there any way to explicitly ignore value returned?20:22
nhandlerLaney: And there would be a small performance hit for the extra api call20:23
Laneythat's right20:23
nhandlerI think updating them every release might be more work, but it definitely makes the scripts more efficient20:23
Laneyyou could be clever and arrange for a cache to be generated in the postinst or similar20:23
tgm4883Is there someone who can take a look at this debconf config file I made  http://mythbuntu.pastebin.com/m135d7b0b  I was following http://www.fifi.org/doc/debconf-doc/tutorial.html#AEN113  but when I answer yes I get "[: 92: =: unexpected operator" and it doesn't ask me the nested questions20:24
tgm4883basically the problem is that debconf never asks the questions inside the if statement20:24
tgm4883but I can't see a problem with it20:24
jmarsdentgm4883: Can $RET be empty?  If so try testing more like if [ x"$RET" = x"true" ] ?20:26
geserLaney: I'm looking at your u-d-t commit. Are you aware of bug 358332? I don't know what the fix will look like but you should perhaps check that _ubuntuSeries() still works as expected after that fix20:30
ubottuLaunchpad bug 358332 in launchpad-registry "[API] OOPS when distribution.getSeries() is called with an invalid name or version" [High,Fix committed] https://launchpad.net/bugs/35833220:30
Laneygeser: Right, we'll have to change which exception is caught20:31
* Laney subscribes20:31
james_wwhy do we even allowing specifying a release?20:35
james_wis it just because we don't record the current development release anywhere?20:36
LaneyI thought that, but that's a potential fight that I didn't want to have20:36
james_wI like the change you made20:36
Laneythe requestsync code needs a good old cleanup20:37
james_wme = findall('~(\S+)', '%s' % launchpad.me)[0]20:37
james_wurgh20:37
james_wme = launchpad.me.name20:38
Laneywasn't me guv'nor20:38
james_wyeah20:39
james_wbut still20:39
Laney:)20:39
james_wteam = "motu"20:40
james_wis that still used for anything?20:40
Laneyyeah, for upload privs now20:41
LaneyI think?20:41
james_wyou changed team = "ubuntu-dev" to that, but I'm not sure why requestsync would need to know anything about motu anymore20:41
RoAkSoAxis there any documentation in the Ubuntu Wiki that shows how to work with FTBFS20:41
RoAkSoAx?20:41
Laneyjames_w: only to say which team you're not a member of for the error20:42
james_wah20:42
Laneys/error/message/20:42
james_w"don't have upload rights for this package" might be better?20:42
Laneyyeah, could be. That isPerPackageUploader check is probably redundant too now.20:43
nhandlerjames_w: ubuntu-dev is used for Per Package Uploaders and motus and core-dev. MOTU is for normal MOTUS20:43
james_wyeah20:44
* Nafallo stealth hugs james_w 20:45
Laneyoh, no - it's used later on20:45
james_w canUploadPackage doesn't check per-package uploaders?20:45
james_w_findMember should check is_valid as well I guess20:45
LaneyPPUs have a bit of extra text put on their sync requests20:46
Laneywhat does that do?20:47
james_wnot sure20:47
james_wit's for deactivated teams or something I guess20:47
james_wprobably won't be an issue, but for correctness I guess it should be checked20:48
* Nafallo got ignored20:48
james_whey Nafallo :-)20:48
Nafallojames_w: :-)20:49
james_w388 20:54
james_w    if lp_functions.isLPTeamMember('ubuntu-bugs'):20:54
james_w389 20:54
james_w        task.transitionToImportance(importance='Wishlist')20:54
james_wthat's not right is it?20:54
james_wubuntu-bugcontrol is the team that controls that isn't it?20:54
stgraberindeed20:55
jmarsdenRoAkSoAx: I don't see anything in the wiki about FTBFS specifically... but in the general case, you "just" add patches so that the package does BFS... right?  How much is there that could usefully be written about this?20:57
geserRoAkSoAx: have you a specific FTBFS you try to solve?20:59
RoAkSoAxgeser, yes21:00
Nafallojames_w: jpds says he didn't do that ;-)21:01
geserRoAkSoAx: which one?21:02
RoAkSoAxgeser, : https://launchpad.net/~andreserl/+archive/ppa/+build/99451521:03
geserRoAkSoAx: that one is easy21:04
RoAkSoAxgeser, how can I solve it?21:04
RoAkSoAxgeser, or better yet, how is a regular process to solve a FTBFS21:04
geser/bin/sh is dash and it doesn't support {} expanding21:04
geserRoAkSoAx: the first part is to understand why it failed. but as there are many different reasons it's hard to document21:05
geserRoAkSoAx: in this case you need to expand the {} by hand21:05
geserRoAkSoAx: rm $(CURDIR)/usr/lib/keysafe/libkeysafe/cryptobotan.a21:06
geserRoAkSoAx: rm $(CURDIR)/usr/lib/keysafe/libkeysafe/cryptobotan.la21:06
geserand so on for the other21:06
geseror list all files on one line (which ever you prefer)21:07
RoAkSoAxgeser, oh I see... and should I document that on the changelog?21:07
geserRoAkSoAx: yes, as you need to write one for the new version it would be best to fill it with something useful :)21:08
geserI usually write something like "Removed bashism in debian/rules" in such cases21:09
RoAkSoAxgeser, ok awesome!! thanks :)21:09
RoAkSoAxgeser, and should this change be sent to debian or is it just an ubuntu change?21:10
RoAkSoAxgeser, and would it be better to do: Remove bashism in debian/rules that cause FTBFS?21:11
RoAkSoAxgeser, btw.. should it be: rm $(KEYSAFE_LIB_DIR)/cryotobotan.a or rm $(CURDIR)/usr/lib/keysafe/libkeysafe/cryptobotan.a ?21:15
geserRoAkSoAx: I didn't look at the rules files itself, just guessed from the log: so rm $(KEYSAFE_LIB_DIR)/cryotobotan.a would be better21:17
geserRoAkSoAx: and forward it to Debian too, as they try too to get everything build with dash (IIRC it was even a lenny release goal)21:18
RoAkSoAxgeser, it fails to build after doing the changes21:19
geserRoAkSoAx: what exactly you put into the changelog entry is up to you21:19
geserhmm21:19
RoAkSoAxgeser, http://pastebin.ubuntu.com/168127/21:20
geserah, that error, let me find the bug number21:21
geserRoAkSoAx: see bug 37321421:22
ubottuLaunchpad bug 373214 in linux "/usr/include/asm/* is not present in linux-libc-dev" [Critical,Fix released] https://launchpad.net/bugs/37321421:22
RoAkSoAxgeser, so should I just update my pbuilder and it will be fixed?21:26
geseryes21:26
RoAkSoAxgeser, k thanks :)21:26
nhandlerRoAkSoAx: If you do not have a download limit per month for your internet, you might consider installing the pbuilder hook that causes it to update itself before building21:28
RoAkSoAxnhandler, k thanks :)21:33
RoAkSoAxbtw.. in the changelog, for example in last ubuntu version they created a patch, in the newer debian version that patch has been merged, but there's nothing on the changelog about it. In the ubuntu version i'm merging should I include something in the changelog that says: drop xxx.patch ?21:34
james_wyep21:36
RoAkSoAxjames_w, so It would be something like: Drop debian/patches/xx.patch. Included upstream?21:38
james_wyeah21:38
nhandlerRoAkSoAx: Keep in mind, there really aren't strict requirements for debian/changelog. You just want to explain the changes you make and why you are making them.21:38
RoAkSoAxok awesome. Thanks guys :)21:39
=== ghostcube_ is now known as ghostcube
=== RoAk is now known as RoAkSoAx
Laneyhttp://www.ouaza.com/wp/2009/05/09/quilt-patch-management-with-debhelper-7/21:55
Laneyphwoar21:55
sebnerLaney: lol, just a minute ago I read this blog entry and now you post the link ^^21:56
Laney\o/21:56
nhandlersebner: I read the blog entry on the planet too21:58
sebnerLaney: we have to tell meebey!21:58
sebnernhandler: ^^21:58
nyuwhoops, debhelper is becoming cdbs22:00
sebnernyu: but much saner ;)22:00
directhexand overridable, rather than shake-your-fist-at-itable22:00
nyuI was never really fond of the implementation in cdbs (even if I wrote part of it myself).  it's the concept that makes it so useful22:03
nyuwhich has been implemented a few times already.  if debhelper will finally "get it right", I'm happy with that22:03
binarymutantif anyone would care to review and possibly advocate my package, http://revu.ubuntuwire.com/p/lxsplit, I would be very appreciative22:05
neversfeldehi, how do I test a get-orig-source rule in debian/rules?22:19
sebnerneversfelde: chmod +x rules then ./debian/rules get-orig-source22:20
Laneyor make -f22:23
neversfeldeit is up do date, so I think it works, thank you22:24
neversfeldedo I have to create a foo_version.orig.tar.gz of the svn dir by myself, or is that wrong?22:31
a|wenneversfelde: you create an orig.tar.gz from an svn export22:32
Laneyneversfelde: if you are packaging a snapshot you should write a get-orig-source rule which generates the orig22:32
Laneyit will probably use svn export, yes22:33
neversfeldemhh, I should have another look at the documentation, ty22:40
james_wJontheEchidna: hey, do you really need a transitional package for windowslist if it was only in karmic?22:44
JontheEchidnaoh, for some reason I thought it was in jaunty22:45
JontheEchidnait was in jaunty ;-)22:45
james_wreally?22:45
james_wnot according to LP22:45
JontheEchidnabrb22:46
james_woh, it's a source package rename as well?22:46
james_wwhich was apparently renamed from something previous to that22:47
james_wcan't you make your minds up? :-)22:47
a|wennot when upstream can't ;)22:48
JontheEchidnasorry, phone22:48
james_wnp22:48
JontheEchidnaplasmoid -> plasma-widget was a rename for all plasma widgets22:50
JontheEchidnaDebian decided on a different name than we had...22:50
JontheEchidnaso we got to rename all of the plasmoids22:50
JontheEchidnabut windowslist -> windowlist was an upstream change22:51
=== vorian is now known as heHATEme
neversfeldegnah, I always gets an23:16
neversfeldesvn: Syntax error in revision argument 'svn://anonsvn.kde.org/home/kde/trunk/extragear/network/choqok'23:16
neversfeldesvn: Syntax error in revision argument 'svn://anonsvn.kde.org/home/kde/trunk/extragear/network/choqok'23:16
neversfeldesorry23:16
neversfeldeand  I followed our MOTU docs23:17
neversfeldethe line in rules is23:17
neversfelde        svn export -r $(SVN_REVISION) svn://anonsvn.kde.org/home/kde/trunk/extragear/network/choqok choqok \23:17
neversfeldeand I changed changelog before23:17
neversfeldeany suggestions?23:18
james_w$(SVN_REVISION) is not set23:18
james_wit's complaining that the url is a bad revision ('-r') argument23:18
neversfeldeI thought it is enough to do this in changelog?23:18
james_wnope23:18
neversfeldeso where do I have to mention it?23:20
JontheEchidnain debian/rules23:23
JontheEchidnalemme paste an example23:24
JontheEchidnahttp://paste.ubuntu.com/168179/ (This is from the old lancelot package23:24
=== kklimonda_ is now known as kklimonda
neversfeldemhh, thanks so far, it does not work at the moment, I will have another look tomorrow23:31
neversfeldeoh, I think I got it, was a simple typo23:33

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