/srv/irclogs.ubuntu.com/2011/06/21/#ubuntu-motu.txt

=== medberry is now known as med_ou
=== med_ou is now known as med_out
=== slicer_ is now known as slicer
=== FlannelKing is now known as Flannel
=== zopa is now known as azop
=== astralja1a is now known as astraljava
dholbachgood morning08:00
ajmitchmorning dholbach08:29
dholbachhey ajmitch08:29
nigelbhello ajmitch08:31
ajmitchhi nigelb08:31
nigelbajmitch: You haven't been around for some time or is it just my feeling? :-)08:32
ajmitchI've been around, but mostly lurking08:34
nigelbAh, that explains that.08:34
ajmitchwhat have you been up to?08:36
nigelboh this and that :)08:38
ajmitchin other words, plenty of secret stuff? :)08:43
nigelbajmitch: Not entirely, working on the web projects last cycle, picking up ftbfs this cycle.08:45
* ajmitch ought to find one thing to try & do & stick with :)08:47
=== ximion2 is now known as ximion
=== ximion2 is now known as ximion
DorianJaminaisHello11:45
DorianJaminaisI am trying to package NetGameTrack11:45
DorianJaminaisbut I have an error using pbuilder11:45
DorianJaminaisthe makefile try to create a new folder : /usr/local/include/NetGameTrack11:46
DorianJaminaisbut I get an error message saying that it doesn't have the permission11:47
Laneyajmitch: do get libappindicator into debian :) :) :) :)11:47
DorianJaminaisWhat is the correct way to do this ?11:47
Laneythe makefile shouldn't be doing that11:47
DorianJaminaisarf fail11:48
DorianJaminaisso it is impossible to create new folder in /usr/local/include ?11:48
DorianJaminaisor it has to be done an other way ?11:48
tumbleweedDorianJaminais: first of all, packages shouldn't put anything into /usr/local11:48
DorianJaminaisso in /usr/include ?11:49
tumbleweedsecond, during the build, you mustn't install to the system, but to the build directory, your Makefil should understand DESTDIR (which is probably going to be ./debian/$packagename ) and install there11:50
DorianJaminaisin my makefile, I got a variable PREFIX, if I change it's value to DESTDIR, should it be okay ?11:51
tumbleweedthat may work as a hack, but PREFIX is something different11:51
tumbleweedPREFIX is something that could ended up in built files (i.e. if PREFIX was /usr, it should look in /usr for data). DESTDIR tells the build system to install to a staging directory rather than the host11:52
DorianJaminaisalright11:52
DorianJaminaisso I will rather try to replace PREFIX by DESTIR in the install target11:53
nigelbtumbleweed: were you able to put my list to good use?11:53
nigelbtumbleweed: I wonder if we should now announce a hackathon-type event for ftbfs now that we have a list.11:53
tumbleweednigelb: nope, I'm just graphing all FTBFSs11:53
tumbleweednigelb: so, I can easily annonate your list by finding all the ftbfs bugs filed against those packages (more than 50% have bugs), but haven't done anything else with it11:56
tumbleweedyes, announcing the hackathon is good11:56
nigelbcool, pick a date when most people can devote a few hours to it, and I can announce11:57
tumbleweedany time works for me11:57
nigelbtumbleweed: next wednesday? That way we have time to get the word out.11:59
tumbleweedsounds good to me. Anyone else?12:00
nigelbLaney, dholbach: thoughts ^12:01
dholbachnigelb, next wednesday = tomorrow?12:01
nigelbdholbach: no the week after12:02
dholbachok, super12:02
nigelb28th12:02
dholbachbecause barry wanted to run a dh_python2 porting jam on this thursday (23rd)12:02
nigelbYeah, I remember that :-)12:02
nigelbwhen is the platform rally?12:02
cjwatsonnext week12:03
nigelbWould it affect negatively if we ran it the week of the rally?12:03
Laneywhat's the proposal?12:03
nigelbLaney: A hackathon like event to fix the ftbfs.12:04
tumbleweedmostly linker-related issues12:04
nigelbAh, that too. FTBFS caused by linker issues.12:04
Laneysounds good if you can find people to do the work12:04
cjwatsonI don't think there'd be a particular problem having that in parallel with the rally12:05
nigelbI intend to do the work. about finding others, well, I gotta try.12:05
* tumbleweed has some local mentorees that I'll try and throw at it12:05
cjwatsonunless you think there might be a problem with Canonical people mostly on the same timezone so there being less coverage to help people in different timezones12:05
cjwatsonbut I shouldn't think that would be a big problem12:05
nigelbIn which case, I'll start blogging and writing to the mailing lists.12:06
Laneyis there a status page or similar?12:06
* tumbleweed can set one up12:06
LaneyI wonder if an IRC bot which you can ask for a new task would be fun12:07
nigelbI thought of a wiki or etherpad. bUt a bot sounds fun too :-)12:07
tumbleweedharvestbot :)12:07
LaneyChallengeBot: !next12:07
nigelbas long as folks don't think we're spamming the channel ;)12:08
tumbleweedetherpad sounds good for something like that12:08
Laney<ChallengeBot> Laney: Fix "FTBFS: blah blah" http://some.site12:08
Laneywell, could be done in PM or another channel or whateer12:08
LaneyI just thought it might be a fun way to organise it12:08
Laneyleague table for completing challenges and so on12:09
Laneyoff-the-cuff thoughts :-)12:09
cjwatsonwhen I joined the Debian release team, ajt set the prospective RAs a bunch of challenges, which were basically of the form "get these release-critical bugs fixed or the packages removed or whatever's appropriate, using your best judgement"12:10
cjwatsonnaturally we tended to get the intractable ones that had been sitting around for ages with people too scared to touch them12:10
cjwatsonit was rather fun12:10
Laneyhaving a list that you're emptying is quite motivating I think, indeed12:11
nigelbI suspect we can have an etherpad list with hints on how to fix, claiming and marking as fixed.12:11
nigelbI would use the wiki, but its been fairly unusable after the upgrade12:12
LaneyLP bugs would be the best way to claim probably12:13
Laneyjust need a way to link them into the status page (harvest or whatever it is)12:13
nigelbI could hack something up tonight. Let me see.12:13
tumbleweedwell that's easy, we have a list of bugs to poll, and can re-generate a status page12:14
nigelbyup12:14
nigelbtumbleweed: if you can get me bugs for each package, I can get a status page up tonight.12:14
lifelesstags?12:14
Laneyquite12:15
tumbleweednigelb: http://pastebin.com/9mGhvSBx12:15
Laneyjust use the API to grab bugs with a tag and make some kind of table12:15
* tumbleweed prefers the tag approach, yes12:15
nigelbRight, so we needed to file bugs for all the packages first.12:15
nigelb(If they don't exist already)12:16
tumbleweedpoke doko for his ftbfs-filing script, or write one12:16
nigelbah, ok12:16
Laneyare you going to use the normal sponsoring process for this or something else?12:18
nigelbnormal sponsoring process12:19
nigelbIs there something else?12:19
tumbleweedi think it would be preferable to try and review those faster, though12:19
tumbleweedit's lots of similar bugs, so you want feedback before people make the same mistakes12:19
LaneyI just thought that some pre-vetting / mentoring / whatever might be good12:19
nigelbOh, that way. I hope there are mentors around who can sponsor stuff.12:19
Laneyotherwise low quality fixes might make it through12:20
nigelbYes, indeed, it would be.12:20
=== ximion1 is now known as ximion
=== ximion2 is now known as ximion
=== highvolt1ge is now known as highvoltage
DorianJaminaisSorry to disturb you again :D14:25
DorianJaminaisWhat is the proper way in the makefile to install a file to /etc/init.d ?14:25
DorianJaminaisI tried with install -m 744 root -o root file /etc/init.d14:27
geseruse "dh_installinit" in the binary target in your debian/rules14:27
DorianJaminaisbut i get an error saying that I don't have the permission14:27
DorianJaminais@geser : thanks, I will look at it14:27
geserDorianJaminais: the whole packaging building happens in a "staging" directory, you have to install everything relativ to it14:28
geserthe contents of that staging directory end in the build deb (and the deb gets unpacked to / during package installation)14:29
DorianJaminaisactually at first I though doing : install -m 744 root -o root file ${DESTDIR}/../etc/init.d14:29
cjwatsonif your DESTDIR requires .. after it, then you have DESTDIR set unconventionally14:30
cjwatsonbut aside from that, that is a perfectly normal way to write makefiles14:31
cjwatsoninstallation locations should generally have $(DESTDIR) in front of them14:31
DorianJaminaisokay so I will try with the ${DESTDIR}14:32
DorianJaminaisthanks14:32
=== med_out is now known as med
=== med is now known as medberry
nigelbWhat's the old-fashioned way of getting the source if I'm not running oneiric?16:20
nigelbI remember it had something to do wwith the dsc file. Otherwise my memory is drawing a blank16:20
micahgnigelb: pull-lp-source in ubuntu-dev-tools works16:20
nigelbmicahg: ah. Thanks.16:21
Ampelbeinnigelb: or 'dget <URL_TO_DSC>16:22
nigelbdget!16:22
nigelbAmpelbein: definitely the one my memory drew a blank on :-)16:22
tumbleweedpull-lp-source saves you finding <URL_TO_DSC> :)16:23
Ampelbeinnigelb: I know the problem. garlic helps ;-)16:23
nigelbtumbleweed: I did find pull-lp-source, but I had to refresh my memory on what I used to do.16:25
nigelbIn a Makefile, is there a global significance for the P in $(P)INSTALL16:29
nigelbOkay, for linking changes, is there a hint on how to find where in the Makefile(s) the linking is happening?16:52
nigelbI can't find a line yet16:52
tumbleweedwith a fair number of packages, the makefile is auto-generated, so you want to make sure the right makefile is generated16:53
nigelbI think this one isn't autogenerated16:54
nigelband wherever  look, I see $(LIBS) at the eend16:54
tumbleweednigelb: which package are you looking at?16:55
Ampelbeinnigelb: the problem with link failures often is that libraries are added to $(LDFLAGS), which is wrong.16:55
nigelbtumbleweed: scratchbox216:55
nigelbAmpelbein: Right. True here.16:56
tumbleweedthis package also helpfully hides its gcc arguments :/16:56
nigelbI have a talent to pick the hard ones ;)16:57
nigelbI guess adding the libraries to CFLAGS is wrong too?16:57
Ampelbeinnigelb: even more so, yes ;-)16:58
Ampelbeinnigelb: libraries should go to LIBS16:58
nigelbAmpelbein: Isn't line 4 here doing that? http://paste.ubuntu.com/630444/16:59
nigelb(the wrong thing I mean)16:59
Ampelbeinyes, that's wrong and is likely the cause of --as-needed issues17:00
nigelbThis is going to be painful.17:01
nigelbSince they're doign the Wrong THing(TM)17:01
tumbleweedyes17:02
tumbleweedbut we fixed a fair bunch of packages in the last cycle, and a few more already this cycle17:02
nigelbI'm up for fixing. Just my lack of knowledge/experience playing against me.17:03
tumbleweedYeah, some are really easy, some nasty :)17:03
nigelbtumbleweed: suggestions on fixing this one?17:04
nigelbCan I do a LIBS declration just like the CFLAGS and then change the entry to put LIBS at the end?17:05
dholbachwho would like to help me with Ubuntu Developer Week? we still have some open slots available: https://wiki.ubuntu.com/UbuntuDeveloperWeek17:06
dholbachanything you'd like to talk about or would like somebody to talk about?17:07
Laney"Who are MOTU and what do they do?" [not volunteering ;)]17:09
nigelbThere's also volun-TOLD. ;)17:09
nigelbIs http://paste.ubuntu.com/630451/ the right way to modify http://paste.ubuntu.com/630444 so that the linking problems are solved?17:18
nigelbAlso, if there isn't a patch system in the package, what's the suggested course of action?17:20
dholbachLaney, yeah, it'd be nice to have a session like that17:20
tumbleweednigelb: err yes a LIBS sounds good (sorry I've got to run). Suggested course of action is a patch applied directly, and possibly stored in debian/applied-patches too17:20
nigelbtumbleweed: thanks :-)17:22
=== Quintasan_ is now known as Quintasan
=== Guest5054 is now known as JackyAlcine
macodholbach: so nigelb is looking at scratchbox217:46
macowhen you dget it, there's scratchbox2_2.2.2-2.dsc and scratchbox2_2.2.2-2.tar.gz17:47
macobut there's no orig17:47
macofrom the changelog, it looks like it started out native (no debian revision in the version string) but then transitioned to non-native and the tarball was changed to match the non-native version number17:48
macowhich leaves me wondering if the maintainer has been using a flag to make debuild shut up about the lack of orig17:49
Laneyit's usually mostly warnings which are rather easy to ignore17:50
Laney(by mistake)17:50
micahgwell, the maintainer is treating it as native when it should be non-native since everything is being kept upstream17:52
dholbachmaco, it looks like there's no tarball releases, but only stuff tagged in git (I didn't look for very long I must admit)17:52
frafu_Hi, I will package a python application (named Onboard) with distutils-extra. The package requires version 2.10 of dist-utils-extra. However, version 2.27 of distutils-extra has a bug that breaks the package building of Onboard. That bug has been fixed in version 2.28 of distutils-extra. My question: should I keep 2.10 as the required version of distutils-extra for the package, or raise it to 2.28? Thanks in advance for any advic17:53
macodholbach: is that the usual thing to do for "stuff tagged in git"? i wouldve done a pristine-tar on it...17:54
maco(relevant to me as spim upstream has stopped releasing tarballs, just has svn, and i need to package a new tag)17:54
dholbachmaco, no, I probably would do it differently17:54
dholbachif you need to make changes in Ubuntu for it now, I'd be pragmatic and just change whatever fixes the problem you're after :)17:55
Laneythere's nothing really wrong with it, but arguably he should use non-native version numbers17:55
micahgLaney: there is something wrong with it, it's not a Debian native project17:56
highvoltage2/win 617:56
Laneywhy must it be to be a native package?17:56
cjwatsonmaco: it sometimes happens by mistake when maintainers move their source trees around or whatever and forget to ensure that the .orig.tar.gz is in the parent directory17:57
cjwatsonif it's in Debian, I'd suggest poking the Debian maintainere17:57
cjwatsonthey probably didn't mean to do it that way17:57
LaneyI almost uploaded tomboy as a native package just now, because I forgot to convert to 3.0 (quilt) when switching to bz2 origs :-)17:57
maconigelb: you're the one fixing the ftbfs... you do the poking :P17:57
Laneythe warnings are all too easy to miss17:57
cjwatsononce you're in 3.0 format, dpkg-source stops you getting it wrong - that's one of the reasons 3.0 (native) and 3.0 (quilt) exist as explicitly separate formats17:58
Laneyindeed17:58
nigelbmaco: heh17:59
macodholbach: well, when i make changes to spim, itll be in debian and ubuntu, as i'm one of the maintainers for it in debian, and it now ftbfs17:59
LaneyBut personally I'd be happy with 1.0 erroring out based on the version17:59
dholbachmaco, hm?17:59
cjwatsonLaney: there are too many cases of people doing it deliberately for that, I think18:00
macodholbach: the "if you need to make changes in ubuntu for it now, just change whatever fixes the problem" bit... we're nowhere near feature freeze. i'll be mking the changes in debian and requesting a sync18:00
Laneycjwatson: Sure, as a preference or something.18:00
Laneydefaults are hard to change18:01
cjwatsonI suspect buxy feels that doing much further work on 1.0 is a waste of time at this point ...18:01
Laneyoh yes, I don't expect it to happen …18:01
micahgLaney: ugh, I thought there was a policy, but can't find it, so I guess I was wrong, apparently there was a heated discussion about this 2 years ago: debian 54498118:03
ubottuDebian bug 544981 in developers-reference "Discourage native packages that are not tightly specific to Debian" [Wishlist,Open] http://bugs.debian.org/54498118:03
Laneymicahg: Right, I think it's another one of Those Things really.18:05
Laneyi.e. a best practice issue that you're encouraged to consider, but can go against if you decide it's right18:05
micahgyep, as confusing as it may be for everyone else :-/18:06
Laney'mr' is a recent one I've come across18:06
Laneybut I guess you could consider releasing to Debian as making a new upstream release and debian/changelog as your changelog ...18:07
cjwatsonthat's a bit different from the case where the project *does* have a separate upstream existence but is released in native format anyway18:08
* maco looks at planet and snorts at "an automated version of cking"18:10
LaneyI don't know anything about this particular package, but I do note a debian/ directory in git18:10
Laneyanyway I'd moved to speaking more generally, and see that all the arguments have been had in that bug already so there's no need to go over them again :-)18:11
nigelbI think i hit bigger bugs in this package with my changes18:12
nigelbNow I get http://paste.ubuntu.com/630480/ while building scractchbox2, and the file doesn't eexit. It seems to be autogenerated.18:19
frafu__Sorry, I had a crash. So I am repositing my question again: I will package a python application (named Onboard) with distutils-extra. The package requires version 2.10 of dist-utils-extra. However, version 2.27 of distutils-extra has a bug that breaks the package building of Onboard. That bug has been fixed in version 2.28 of distutils-extra. My question: should I keep 2.10 as the required version of distutils-extra for the pack18:19
=== ogra_ is now known as IIll
=== IIll is now known as ogra_
=== Guest7372 is now known as JackyAlcine
tumbleweednigelb: still stuck? If so, can I see your current debdiff20:01
pcprattshi! is there a standard way to support both a gui and command line installer?  I need to collect some settings from the user20:11
directhexpcpratts, at package install time?20:19
pcprattsdirecthex: yes20:19
pcprattsdirecthex: I could make two build scripts and make 2 different deps, but I don't know if that is generally desired20:20
directhexpcpratts, yes, this is how debconf works - it supports multiple "frontends", and uses the configured one by default (which is the gnome one on ubuntu, the kde one on kde, the text one in a console)20:20
pcprattsdirecthex: deps = debs20:20
pcprattsokay20:20
pcprattsdirecthex: are there any debconf bindings for java that you know of?20:21
directhexer, no. you'd write a bash script for your package's post-install, which invokes debconf at the correct places. you can make it so the result of that is to run something with given parameters, though20:21
directhexyou wouldn't query the debconf database from inside your app, but you'd use it to craft a config file20:22
directhexhttp://www.fifi.org/doc/debconf-doc/tutorial.html20:22
pcprattsdirecthex: okay.  thanks so much.  I can see how I can put something together.  thanks also for the tutorial link20:22
=== webjadmin is now known as JackyAlcine
directhexpcpratts, i wouldn't say it's particularly intuitive, but it's powerful and does exactly what it needs to20:25
pcprattsdirecthex: haha, just like most of the things you need to do to make a deb20:26
pcprattsdirecthex: I'm not bashing, debian and ubuntu rules.  but I never cared for make or shell scripts20:26
directhexdebhelper is pretty easy, for many build systems20:27
directhexsome build systems it's more difficult20:27
pcprattsdirecthex: yeah, all my code is in Java, so debhelper is kinda weird to use with anty20:27
pcprattsant*20:27
directhexi don't doubt it20:27
macopcpratts: i think you want to talk to jamespage20:28
macohe's apparently pretty masterful with java/ant stuff20:28
pcprattsmaco: I've got most everything working except now someone wants a console installer20:28
pcprattsmarco: we'll just have to see if my package gets accepted though20:29
=== Quintasan_ is now known as Quintasan
=== yofel_ is now known as yofel
=== medberry is now known as med_out
blackmoon-105hi, i'm try to package bt drivers with dkms, but i receive an error: http://pastebin.com/Yq7gDpUP my dkms.conf is here: http://pastebin.com/99Wp7ukb21:33
=== jdstrand_ is now known as jdstrand
pcprattsI am trying to use debconf.  I am doing most of the packaging by hand because I use java alot.  my config file is not getting put into the .deb.  any suggestions?21:55
pcprattsI don't see any relevant debhelper commands21:56
=== med_out is now known as med
=== med is now known as medberry
pcprattsI think I found it: dh_installdebconf22:08
=== apachelogger is now known as rohansgoogle
=== rohansgoogle is now known as apachelogger

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