/srv/irclogs.ubuntu.com/2009/06/11/#ubuntu-motu.txt

=== asac_ is now known as asac
sharmscan anyone point me to documentation about lpia?01:34
sharmsie what flags it uses, where it sets them01:34
sharmsor is it some secret non documented process01:34
=== santiago-pgsql is now known as santiago-ve
superm1sharms, lpia is no longer a 'supported' architecture starting with karmic01:46
sharmssuperm1: yeah I just have a dell mini 9 with the default dell load, and I was trying to figure out exactly how lpia worked01:48
sharmsunfortunately they didnt document almost anything about it01:48
sharmsbut dpkg-buildpackage should tell me what I need to know, its just disappointed01:48
sharmsthis stuff should be more open01:48
superm1sharms, i believe basically gcc should be preconfigured right if you install it01:50
superm1shouldn't need to worry too much about what flags are needed and what not01:50
ajmitchsuperm1: lpia has been dropped from support?01:50
superm1ajmitch, it's just chugging along in case its needed in the future01:50
superm1but no media will be generated from it i believe01:50
superm1there was a session at UDS to discuss this01:50
ajmitchwhich are the true 'supported' architectures now ?01:51
sharmssuperm1: it is important for me to know exactly how they compile packages.  You would think somewhere on the wiki it would say 'For LPIA we use these compile flags: '01:51
ajmitchand obviously the majority of us weren't at UDS nor do we have time to dig through 100+ wiki pages01:51
superm1ajmitch, i386, arm*, and amd6401:51
superm1ppc chugs along on ports01:51
superm1i forget what the decision was about hppa and sparc though01:51
ajmitch"discussed at UDS" does irritate me at times for stuff that could be better communicated :)01:52
ausimagewhere's Ncommander? thought he worked specifically on those arches01:52
sharmsI agree, I wish the wiki was used a bit more01:52
superm1sharms, i'd apt-get source glibc and take a look at the flags that are applied in debian/rules01:52
superm1they should surely be there01:52
ajmitchsharms: this is the sort of thing that should have made it to ubuntu-devel-announce01:52
superm1or gcc - i'm not which is the main source package01:52
sharmsajmitch: it was sent to devel-announce, but had 0 details01:52
NCommanderausimage, hrm?01:53
sharmslwn.net post also didnt have details, just people asking for details01:53
sharmsand obviously no responses01:53
ausimagelpia switches01:53
NCommanderlpia builds with -Os, and a set of tune flags which I don't remember off hand01:53
ajmitchsharms: I don't see anything beyond the "community-supported ARM release" on u-d-a01:53
NCommanderhowever, lpia is completely unsupported (and has never been recommended for general usage)01:53
ajmitchand hppa eol01:53
sharmsNCommander: right but it shipped on my dell, so I have an interest in it01:53
NCommanderWe decided at UDS to leave it building, but remove all kernels and such, so its effectively EOL01:54
NCommandersharms, that's OSG ubuntu, and not consistant with the main archive01:54
NCommandersharms, distribution upgrades and the like from machines pre-installed with ubuntu are not supported.01:54
NCommander*OSG's01:54
superm1that's not correct - it depends on if there is a custom repo in place01:54
sharmsok maybe you don't understand.  I am a developer.  I write software.  I am simply looking for information on the LPIA settings01:54
superm1the dell netbooks that ship intentionally have a custom repo, and upgrades aren't supported01:55
sharmsI do not want support, just transparent development01:55
sharmsget it?01:55
superm1any other dell machines that ship with ubuntu have standard repos and can do standard upgrades and what not01:55
NCommandersuperm1, sharms, for lpia/hardy, then the only difference is we target i686 unless that was changed by OSG01:55
NCommandersuperm1, then I'm mistaken. My bad.01:55
NCommandersuperm1, but I thought dell shipped i386 on all machines that didn't have custom repos.01:55
superm1NCommander, which is true, and dist upgrades are supported just fine01:56
NCommandersuperm1, right, my mistake.01:56
NCommandersharms, what model of Dell machine do you have?01:56
sharmsDell Mini 901:56
superm1those definitely ship with lpia and custom repos01:57
NCommandersharms, right, which runs a customized version of Ubuntu from Dell01:57
sharmsagain I dont want support, I just want to know what files where changed to enforce the LPIA compile settings on the distro01:57
NCommandersharms, there is no change. Hardy i386 and lpia are identicial except the later builds against i68601:57
NCommanderand that might not even be true for OSG's archives or hardy01:57
sharmsand being that I see lpia-wrapper is in karmic, someone has to know what files those are01:57
NCommandersharms, I wrote lpia-wrapper01:57
NCommandersharms, it was an experiment in building the archive with -Os for karmic only.01:57
sharmsSo they named it lpia, but really its just Ubuntu i686?01:58
NCommandersharms, no. Originally, lpia was to be optimized for the Intel atom processor, and was bootstrapped with the gutsy cycle01:59
NCommandersharms, that never happened, so lpia and i386 are functionally equivelent01:59
NCommanderExcept for minor incompatibilities caused by the lpia architecture string.01:59
NCommander(aka, why you can't just install skype without playing on the command line)01:59
ajmitchsounds like a mess02:00
NCommanderajmitch, s/sounds like/is/g02:00
sharmsI appreciate the info, can you point me to what file stores the default DEB_BUILD_OPTIONS?02:01
NCommandersharms, its in /usr/share/ somewhere, but there is no difference for lpia vs i38602:01
sharmsha ok02:01
ajmitchso lpia was a vicious lie foisted upon us, and we can drop all those diffs that we carry for packages to make them build on lpia?02:02
NCommanderajmitch, no, we need those still02:02
NCommanderajmitch, that's the arch-string incompatibility I brought up before.02:03
StevenKThere isn't many of them left02:03
StevenKI've been killing lpia-only diffs this go round as I get time02:04
ajmitchcarrying deltas againt debian for an effectively EOL arch does cause some headaches :)02:04
NCommanderajmitch, its not officially EOL until we kill the port outright, the problem is there is a chance we might actually need the lpia port in the semi-future, hence why it didn't get the ax along with the hppa port.02:05
ajmitchthis is why I bitch about the lack of information beyond "We discussed it at UDS" :)02:05
NCommanderajmitch, where was that said?02:06
sharmsI havent heard any of this information except right here right now02:06
sharmsno mailing list communication of it, nor wiki02:06
ajmitchwhat sharms just said02:06
ajmitchboth you & superm1 replied with "We discussed" or "We decided"02:07
ajmitchnot your fault, just that it hasn't got beyond that point02:07
NCommanderajmitch, sharms, well, I won't speak for the Hardy/lpia used in the custom Dell repos. I know fairly little about it, so I'm not sure if everything I just said w.r.t. to compiler flags is revelent to it02:08
NCommanderBut with Gutsy-Jaunty, lpia was essentially i386 Ubuntu compiled targetting i68602:08
ajmitchNCommander: I'm not caring about the compiler flags, just about the arch being supported & something to care deeply about fixing breakage one02:09
NCommanderajmitch, its never been supported in the main archive.02:09
sharmsNCommander: with respect to Ubuntu, not Dell,  Matthias Klose sent a mail to Ubuntu Announce about lpia specifically saying: "uses different optimizations options in the compiler,02:09
sharmsdifferent configuration and build options for some packages."02:10
sharmsbut with absolutely no details anywhere else02:10
* ajmitch must have always got the wrong impression that it was then02:10
NCommanderajmitch, the only reason its supported for PPAs is because you can easily virtualize i386 :-)02:10
sharmswhich makes it hard to get involved with understanding it, when the wiki has no info and the mailing lists turn up no results other than people guessing what they are, and some moblin guys suggesting what might be good flags02:10
NCommandersharms, that was earlier this cycle, right?02:10
sharmsI wouldnt know because further information isnt available except here on IRC :)02:10
NCommandersharms, most people do development on i386 or amd64, so there isn't a lot of people who would be interested in the i386-lpia differences02:11
=== mathiaz_ is now known as mathiaz
NCommander(or those people could be sadistic like me, and use an ia64 desktop)02:11
sharmsright, but if I want to fix a bug, finding some kind of information would be great02:11
ajmitchNCommander: I don't envy your power bill02:11
NCommanderajmitch, the same circuit also powers three sparcs, my laptop, three ARM boards, the powermac, a powerbook, a PReP PPC, the TV, and the XBox 36002:12
NCommanderajmitch, I'm kinda wondering if the next machine will finally blow the breaker.02:12
ajmitch3-phase power? ;)02:12
sharmsNCommander: and someone had to discuss compiler flags, build options and configurations somewhere.  It just wasn't done anywhere in the open that people can reference02:12
sharmsKlose didnt just go off as a lone cowboy and set all that up I am sure02:13
NCommanderajmitch, the power bill isn't too bad. I make up for it in the heating costs of a weekend.02:13
ajmitchNCommander: if you know the right people to poke, get lpia renamed to lpia (unnofficial) on https://edge.launchpad.net/ubuntu/karmic02:13
ajmitch pages like that are what mislead me02:14
sharmsajmitch: it is only misleading because you didnt hear the uds discussion :)02:14
NCommanderajmitch, that probably should also have armel as official :-/02:14
ajmitchsharms: I obviously needed to stay up until 4AM to listen in on it :)02:14
ajmitchNCommander: if armel is official, then yes it should be :)02:15
sharmsha02:15
* NCommander isn't even sure who can flip that switch02:15
NCommanderIt requires a duck and that's all I know02:15
ajmitchsharms: UDS was about 10 or 11 hours behind my timezone, made listening in on anything a bit hard02:15
TheMusoWouldn't signalling a port as official require it to be moved to a.u.c?02:15
sharmsyeah it would be cool to see more blog entries etc about technical ideas02:16
NCommanderTheMuso, no, that's just for mirroring reasons. lpia has been marked official since hardy(?), and its on ports.u.c02:16
sharmsso I can atleast google it02:16
TheMusoNCommander: oh right.02:16
NCommandersharms, *cough* I have meant to send an email about that, but it slipped off my TODO list02:16
sharmsNCommander: well the info is much appreciated, regardless of date presented :)02:17
NCommanderI probably need a RT ticket to get the (unofficial) flag changed02:17
ajmitchdo the magic, I don't care how :)02:17
NCommanderwow, the last upload to dapper was more than two months ago02:18
ajmitchI guess the list of critical bugs to get fixed has shrunk a bit02:19
ajmitchapart from security stuff02:19
NCommanderajmitch, in dapper?02:20
ajmitchdo dapper-security uploads go through dapper-changes?02:20
ajmitchbecause I'm sure there have been things to get fixed in those 2 months02:21
jdstrandiirc, there is a bug that prevents -security uploads from going to -changes02:21
ajmitchright, so -changes is underrepresenting the number of uploads, no big problem02:21
=== Guest54546 is now known as santiago-ve
ScottKIIRC it's a misfeature, not a bug but the result is the same.03:18
Andphehello everyone, newbiew here03:56
AndpheI took a debian package and try to port it to ubuntu03:56
Andpheindeed I put it at my ppa https://launchpad.net/~andphe/+archive/ppa03:56
ScottKAndphe: What package?03:56
Andphev4l2ucp03:57
Andpheright now I'm trying to add it a menu entry and a icon03:57
AndpheI read doc about dh_installmenu, but not sure how to proceed03:57
Andphethis is the rules file03:58
Andphehttp://paste.ubuntu.com/193158/03:58
AndpheI added the cp line to copy the icon03:58
ScottKThe package is already in Ubuntu in Karmic.03:58
Andphebut not sure where to put the dh_installmenu03:58
ScottKYou might look at that version.03:58
AndpheScottK really ?03:58
Andphethat is a great and bad news03:58
ScottKv4l2ucp | 1.3-0ubuntu1 | karmic/universe | source, amd64, i38603:59
Andphebecause the package is in karmic but I wasted my time03:59
Andphewell03:59
Andphethank you03:59
ScottKNo problem.03:59
AndpheI'll take a look03:59
Andphe;(03:59
ScottKI'd guess you likely learned something in the process, so I doubt it was a waste.03:59
* Andphe going to cry to another place03:59
Andpheyep I learned something :)04:00
Andphefigthing with the menu issue04:00
Andphethanks again04:00
Andphebye04:00
ScottKBye.04:00
Andpheget back04:08
Andphethe karmic one doesn't have a menu neither04:09
Andphenor a icon04:09
ausimageAndphe: at least for gnome the menu item is .desktop file... and the format is fairly simple04:14
Andpheausimage: as I understand having a v4l2ucp.menu file the dh_installmenu helper would do the trick04:15
Andpheright ?04:15
Andphehaving this rules file http://paste.ubuntu.com/193158/04:15
Andphewhere should go the dh_installmenu line ?04:16
ausimagenot sure... but creating the a desktop file to be included is quite easy04:16
ausimageI personally just place the desktop file where it is supposed to be04:16
AndpheI see04:16
ausimagethough I am just learning all the ropes too :)04:17
Andphefinally found a example04:17
Andphehttp://www.togaware.com/linux/survivor/rules.html04:17
ausimagehttp://paste.ubuntu.com/193168/ <== my desktoop04:17
* Andphe trying04:17
AndpheThanks for share04:17
ausimage*er my desktop menu file...04:17
ausimageyw04:18
ausimageanyone know why dch is not picking up my version changes?04:42
* ausimage thinks hand edits were far simpler to manage at this rate :/04:42
lifelessausimage: dch edits the changelog, it doesn't look at diffs or anything04:43
ausimagelifeless... I thought it would advance my versions automatically...04:43
ausimageI am now stuck with a cli editor to write a new stanza... :(04:44
ausimageshould it not at least check the version info in the directory name itself?04:45
lifelessno04:46
lifelessyou tell dch what you want it to do04:46
lifelessdch --help04:46
ausimageI looked...04:47
ausimage:/04:47
ausimagecould not tell which switch advances the versioning04:47
ausimagea nice gui editor.... select copy paste click click done.... ;)04:48
bddebiandch -i, dch --nmu, dch --qa will all advance the version04:51
ausimagewhich does the app versioning?04:52
bddebian???04:52
ausimagethe way I read the switches they only affected the package versioning04:53
bddebianUnless it is a native package, of course04:53
bddebianUpstream does the app versioning04:53
ausimageI am the upstream... for the package...04:53
bddebianThen you set the version :)04:54
ausimageand when I use dch I would expect to see the version in the directory :/04:54
ausimagedirectory name04:54
bddebianNo, dch will never adjust an upsteam version04:54
bddebianNor does it change the dir name afaik04:54
ausimageit did I think once for me04:55
bddebianWell unless it is a native package I should say.04:55
bddebianWas it a native package?04:55
ausimageum that time it was I think... only cause it can't seem to realize the taz.gz is still in the parent dir :/04:56
ausimagebddebian and last few package turns I made with my package it has wanted me to -0ubuntu in addition to the orig for the tarball...04:58
ausimageI was wondering if someone could tell me why my package builds on jaunty but not karmic...06:03
ausimageit is in revu here http://revu.ubuntuwire.com/details.py?upid=602306:03
ausimageI did nothing to the package 'cept change karmic to jaunty :/06:04
ausimagefrom my ppa log of the karmic build it claims a dir path is missing :/ from soovee-common06:05
persiaausimage, Do you have a karmic buildlog?06:05
ausimagehttps://edge.launchpad.net/~ausimage/+archive/soovee/+build/1069853/+files/buildlog_ubuntu-karmic-i386.soovee_1.07.2-0ubuntu-1~jaunty~ppa1_FAILEDTOBUILD.txt.gz06:06
ausimagepersia is that ok?06:06
=== fabrice_sp_ is now known as fabrice_sp
StevenKdh_install: soovee-common missing files (debian/tmp/usr/lib/python2.6/dist-packages/soovee_app/pages/*), aborting06:07
StevenKI guess Python in Karmic is putting them somewhere else06:07
ausimageyup... but it does not complain about it with jaunty06:07
ausimageoh ahh :/06:07
StevenKHard coding python version is bad, too06:07
StevenKYou know, things are allowed to change from Jaunty to Karmic?06:07
ausimageyeah... but I was not aware of what did06:08
ausimageand I did not know how else to set the *.install lists06:08
persiaI think you'll want to play with dh_install --list-missing06:09
* ausimage has already been accused of using a bigger tool than necessary when it comes to packaging ;)06:09
StevenKBigger *hammer*06:09
ausimagewith the changelog pointing at karmic ?06:09
persiaBut you might also want to try to find someone who has experience splitting python packages: there may be an especially good way to do things in an automated fashion.06:09
ausimageoh yeah that would be nice...06:10
persiaDoesn't matter what the changelog says.  It matters what you build against.06:10
=== MooKow is now known as LordKow
persiaAlso, you ought to delete debian/souvee.install: it's a useless file.06:10
ausimagek that I can do...06:10
persiachangelog.sch.save looks like a leftover as well.06:11
ausimagecleaned that up06:12
StevenKdh 7 needs to support applying patches and then cdbs can completly die06:14
ausimagepersia it looks like dh_install needs me to build first :/06:14
persiaStevenK, dh --with-quilt06:14
ausimagecause it does not seem to find the dir eitherway...06:15
persiaausimage, Just add --list-missing in your rules file, build, and examine the build log.06:15
StevenKpersia: ARGH06:15
StevenKpersia: But Quilt BURNS06:15
ajmitchStevenK: what don't you like about it?06:15
persiaStevenK, Then write a --with addon for your favorite patch system :p06:15
StevenKajmitch: It's a sledgehammer of a patch system06:15
ausimagesame thing persia...06:15
StevenKAnd I invariably break my kneecaps while swinging it06:16
persiaausimage, Yes, the error is expected.  It's the other information in the log that will tell you what you aren't installing.06:16
StevenKHaving to quilt new ; quilt add ; edit ; quilt refresh ; quilt omg-it-hurts ...06:16
persiaYou ought only need to push -a, add, pop -a.06:17
StevenKIf I'm modifying a patch that is at the top of the stack, yes06:17
ausimagei thought install got its files after building :/06:18
StevenKIt requires too much workflow to use effectively06:18
persiaDifferent definitions of "build".  There's "build" in the sense of converting source into the target format (usually just copying stuff around for python), and "build" in the sense of creating binary packages.06:19
persiaStevenK, Then write more addons.  It oughtn't be hard to create a dpatch add-on.  simple-patchsys probably requires a bit more effort.06:19
ausimagei think it is convert source into target part....06:20
StevenKWhat?06:20
ausimagek that is wierd... i did a dpkg-build package with it set as karmic build and it built06:21
ausimagethough I know not to put weight in that06:22
ausimage:S06:22
ausimageI guess I need to ask another python packager for help on this....06:24
ausimageanyone know who qualifies?06:24
persiaStevenK, Debian bug #527255 probably contains sufficient guidance if you're actually going to do it...06:24
ubottuDebian bug 527255 in debhelper "debhelper still needs manual modification in debian/rules to involve" [Wishlist,Closed] http://bugs.debian.org/52725506:24
ausimagepersia it seems that pythoncentral might be borked :/06:27
ausimageit shows the files in lib.linux-i686-2.6lib.linux-i686-2.606:27
ausimagei meant lib.linux-i686-2.6 not python-2.606:28
* ausimage is overtired and might be reading that right :/06:30
persiaausimage, I can't tell you what is right, because I don't know.  I can only point you at tools that can help you figure out what might be right.06:31
ausimageah sorry...06:32
persiaNo need to be sorry.  I just didn't want you to think I was ignoring you :)06:33
dholbachgood morning06:34
fabrice_sphey dholbach ! Good morning06:38
dholbachhi fabrice_sp06:38
fabrice_spdholbach, did you see my answer in #384936?06:40
fabrice_spbug #38493606:40
ubottuLaunchpad bug 384936 in gmerlin "libgmerlin0 cause a coredump in new version of openmovieeditor because the lib package miss the plugins" [Undecided,Confirmed] https://launchpad.net/bugs/38493606:40
dholbachno not yet06:40
fabrice_spok06:40
dholbachfabrice_sp: I hope the Debian maintainers adopt the change06:41
dholbachnhandler: great work on getting the perl session on the schedule!06:41
fabrice_spdholbach, we can wait, as I can't get the gmerlin-avdecoder merge sponsored, so no new openmovieeditor that will make use of that lib... :-(06:44
ajmitchmorning dholbach06:44
dholbachhiya ajmitch06:47
porthosedholbach: good mourning, when you have time, can we talk about bug #385066?06:51
ubottuLaunchpad bug 385066 in icon-slicer "Sync icon-slicer 0.3-2 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/38506606:51
dholbachporthose: sure06:51
porthoseI think the change in src/main.c should have been applied with a patch sytem06:52
porthosebut it wasn06:52
porthosewasn't06:52
dholbachporthose: icon-slicer doesn't use a patch system in Ubuntu right now, so it seems that the maintainer was happy to directly patch the source06:53
* fabrice_sp remembers a similar discussion :-)06:54
porthosebut I thought all changes outside of the debian directory should be applied with a patch system?06:55
dholbachporthose: that depends on the preference of the maintainer06:55
dholbachporthose: there are lots of packages that directly apply patches (especially native packages or packages that have the full source in a version control system)06:56
porthoseok, guess I need to do some more detective work, thanks ;-)06:57
dholbachno worries06:57
dholbachfabrice_sp: I'll take a look at gmerlin-avdecoder in a bit06:57
dholbach(sorting out some other stuff right now)06:57
fabrice_spporthose, that's quite easy to detect: just have a look at debian diff file. If it contans change to the source, no patch system needed :-)06:58
porthosethat's what I am doing right now :)06:58
qiyongmay i ask an apt-mirror question?06:58
dholbachfabrice_sp, porthose: or run "what-patch" from the ubuntu-dev-tools package :)06:59
fabrice_spdholbach, thanks! :-) As it's a new package from Debian Multimedia, it's not so easy to find someone willing to look at it :-)06:59
fabrice_sp!ask | qiyong06:59
ubottuqiyong: Please don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)06:59
qiyonghow can I get apt-mirror to mirror two arch's ?07:00
StevenKList them in the config file07:00
qiyongset defaultarch i386 amd6407:00
qiyong^doesn't work07:00
qiyongset defaultarch i386, amd6407:01
qiyong^neither07:01
StevenKMy apt-mirror manual page doesn't list defaultarch at all?07:01
persiafabrice_sp, porthose: Note that debian/README.source, if present, should provide detailed advice on how a package is to be patched.  Also, be aware that in some cases there will be a mix of patch systems and non-patch systems, for annoying reasons related to how the some of the patch systems work: in these cases, use the patch system if possible.07:01
StevenKqiyong: http://ubuntuforums.org/archive/index.php/t-599479.html07:03
fabrice_sppersia, in general, I use the existing patch system (basically, if there is a patches directory in debian), otherwise, look at the diff file to see if some files has been modified07:04
qiyongStevenK: so?07:04
fabrice_spwhat is Nuku-Nuku? a bot?07:04
persiafabrice_sp, In most cases, that ought work.07:05
qiyongStevenK: i want to mirror both amd64 and i38607:05
StevenKqiyong: I refuse to spell it out for you, read the documentation.07:05
Hobbseefabrice_sp: yeah, it's a bot07:06
qiyongStevenK: i get it :)07:06
qiyongStevenK: deb-arch07:06
persiaHobbsee, I can't seem to remember the right syntax.  Can you make it go away again, unless you know it to be an approved bot?07:07
Hobbseepersia: it's lucidfox's - the best way to get it gone is to probably request it not be here.  I'm not sure why it's here to start with07:09
persiaHobbsee, Oh, suddenly I have a reasonable path to solution.  Thanks.07:10
Hobbseepersia: you're welcome07:10
persiaI can't complain about a bot, given the somewhat indirect nature of my own access, but I do intend to complain about the annoying responses I get all the time.07:10
Hobbseepersia: yeah, it certainly shouldn't be triggering on ! and should be changed.07:12
Hobbseeor at least, if it wants to stay in ubuntu land07:13
persiaRight.  non-triggering bots for various purposes (personal logging, intermediation of access, etc.) seem reasonable, so long as they are mostly indistinguishable from normal users.07:13
persiaActive bots seem to violate the "no bots" policy fairly clearly.07:14
Hobbseeindeed.  I think ! is the standard, so it's probably just an oversight.  I'll point it out, or you're welcome to - you'll probably see LucidFox first07:14
persiaPerhaps.  I'm at least motivated, as I've been becoming increasingly annoyed by that bot for the past several weeks.07:15
nixternalso what are we talking about in here that has the screen all filled up?07:17
dholbachfabrice_sp: is there a reason the debian-multimedia folks don't use those build-deps?07:18
dholbachfabrice_sp: it ftbfs for me - I just added a comment to REVU07:20
Stupendousstevedholbach: Are you around?07:22
dholbachStupendoussteve: yes07:23
fabrice_sp_dholbach, I'll check. Thanks07:24
fabrice_sp_Oh: it FTBFS because of a change in karmic. I have to check the correct changes07:25
Stupendousstevedholbach: In your comment on bug #374350 you asked why I updated config.sub to 2008. I actually don't really know. That is to say, the a previous Ubuntu delta updates config.sub to a 2007 version without it being mentioned in any changelog07:26
ubottuLaunchpad bug 374350 in ssed "Please merge ssed 3.62-6.3 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/37435007:26
dholbachStupendoussteve: some packages will automatically update config.{sub,guess} if available and that's fine07:26
dholbachStupendoussteve: I just wasn't sure if there was a reason why you mentioned it :)07:27
dholbach... if there was a specific reason07:27
StupendoussteveI see. Is it something that I shouldn't bother doing myself in a merge?07:27
dholbachStupendoussteve: if the package builds as expected without updating, I wouldn't bother07:27
persiaIt's not usually done as part of a merge, although some packages auto-update at source-build time (which I personally find to be the *most* annoying of the three possible times to update)07:28
StupendoussteveI see, I'll remove that part when I work on the other changes07:28
dholbachStupendoussteve: let me know when you updated it and I'll take a look again07:28
StupendoussteveThat package was confusing. If I used mergemaster the deb-ubuntu diff was 80KiB, but the diff from previous to new Ubuntu versions ended up being like 4KiB, something fishy07:28
iulianErm, how do I stop the update-manager from popping out?07:44
slytheriniulian: check release notes of jaunty07:46
iulianslytherin: Aha! Got it, thanks.07:48
Stupendousstevedholbach: Patch in bug #374350 looks better now08:08
ubottuLaunchpad bug 374350 in ssed "Please merge ssed 3.62-6.3 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/37435008:08
fabrice_sp_dholbach, gmerlin-avdecoder is in the NEW queue of Debian (http://ftp-master.debian.org/new/gmerlin-avdecoder_1.0.0-1.html). How long does it  take to have it accepted? automatic merge would do the trick08:11
fabrice_sp_(and by the way: debian added the same build dependency, except libmjpegtools :-) )08:12
dholbachfabrice_sp_: nice... no idea how long it will take, but I think it's fine to merge from NEW... or something08:13
dholbachStupendoussteve: good work - uploaded08:17
persiaNEW isn't public, so it's non-trivial to merge and guarantee matched orig.tar.gz08:17
persiaBetter to wait until closer to DIF.08:17
fabrice_sp_let's wait, then. It has been uploadded by the same guy as gmerlin, so I think it should go fast08:19
fabrice_sp_2 days ago08:20
fabrice_sp_another question: when dealing with bug #383825, I found a FTBFS in koffice. Is it better to open a new bug report, attach the debdiff, and subscribe main sponsors??08:22
ubottuLaunchpad bug 383825 in texlive-bin "[karmic] libpoppler4 -> libpoppler5 transition" [Undecided,Confirmed] https://launchpad.net/bugs/38382508:22
persiafabrice_sp_, If you can fix more than one thing in a single bug, that's a win.  Save the bug numbers, as there is a limited supply.08:25
fabrice_sp_persia, ok. I'll attach the debdiff to this one, then. Thanks for your answer!08:26
persiafabrice_sp_, Thanks for fixing the bug :)08:26
fabrice_sp_:-D08:26
persiaDon't forget to mention everything in the changelog entry though: the sponsors will be checking to make sure your changelog matches the changes, even if you fix a few extra bugs along the way.08:27
fabrice_sp_sure08:34
=== fabrice_sp_ is now known as fabrice_sp
=== cjwatson_ is now known as cjwatson
cjwatsonsharms: I don't know if it was explicitly stated by anyone in the discussion last night, but just to be clear, there's no "secret" buildd magic involved in lpia - it's entirely in packages, so for example you can just look at the gcc-4.3 etc. source package to see the default compiler flags. There is no default setting of DEB_BUILD_OPTIONS on lpia or any other architecture.09:29
persiaWell, there's DEB_BUILD_OPTIONS=parallel=n+1, but that's true for every architecture.09:34
persia(and only on the buildds)09:34
savvasis this line ok in debian/install with debhelper >= 7: data/etc/ ./09:40
persiasavvas, Yes, but it's awfully odd.  What is it intended to do?09:42
savvashm.. you're right09:43
savvasI guess conffiles should be better :)09:43
persiasavvas, What are you trying to accomplish?09:43
savvasI have some configuration files that need to be installed09:44
* persia glares at "amd64 not in arch list: amd64 arm armel hppa i386 powerpc sparc kfreebsd-i386 kfreebsd-amd64 ppc64 lpia -- skipping"09:44
savvashttp://paste.ubuntu.com/193311/09:44
persiasavvas, You want "data/etc/* etc/" (assuming such a glob won't have false matches)09:45
savvasthat's better, thanks!09:47
savvaser.. just for the record, debian/conffiles isn't the place for such files?09:47
persiaI generally don't put anything in debian/conffiles, and trust debhelper to just mark anything I stick in /etc as a conffile (although I forget which bit of magic does this)09:50
savvasI heard that too, thanks again :)09:51
savvasheard or saw, can't remember actually :P09:52
persiaAh, it's dh_installdeb.  "In V3 compatibility mode and higher, all files in the etc/ directory in a package will automatically be flagged as conffiles by this program, so there is no need to list them manually in package.conffiles."09:52
cjwatsondebian/conffiles never caused files to be installed anyway09:58
cjwatsonit simply flagged files that had already been installed by some other method09:58
huayrahi, does the MOTU mono team have a channel or shall I just ask here?10:07
huayraI am working with package of a mono app (iFolder)10:07
huayraand will need sponsoring from you guys10:07
huayra:)10:07
huayrato get it into Karmic10:08
james_whi huayra10:08
james_wyour best bet is #debian-mono on OFTC10:08
huayraif anyone here knows about mono apps package, please point me towards sn.exe10:08
huayraI thought debian used to hang @ freenode10:09
james_wthey used to10:09
james_wthey moved a few years ago10:09
huayrabeen hanging so long with Ubuntu that I hardly catch debian news anymore...10:09
huayrathanks james_w :-)10:09
huayraone question though.,10:09
huayraWe should try to get it into debian first?10:10
james_wyup10:10
james_wespecially for mono packages10:10
huayrawhat if we do it the other way around?10:10
huayraI don't believe we will get it into karmic if we do it through debian10:10
james_wbecause those involved with mono in Ubuntu tend to work through Debian10:10
james_wso they will just encourage you to do that anyway10:11
huayrabut, it is possible to do it the other way, isn't it?10:11
james_wwell, start with talking to them10:11
huayraI mean, theoretically?10:11
james_wyou can work on the packaging with them, get review10:11
huayrak10:11
james_wand they know how to get it quickly in to karmic if needded10:11
huayrathanks10:11
=== ApOgEE- is now known as ApOgEE
slytherinhuayra: you can talk with directhex here but I believe he is also part of Debian pkg-mono team.10:34
Laneyhuayra, james_w: It's #debian-cli @ OFTC now, fyi11:02
james_woops, thanks Laney11:03
Laneyno worries11:03
slytherinare the autosyncs stopped currently?11:25
persiaMight be off for the Alpha2 Freeze.  Ought be running again by the end of the week.11:28
persia(and it's only kinda semi-automatic anyway: there's this script the archive-admins run)11:28
=== nenolod_ is now known as nenolod
LaneyI replied to that mail, but it got held for moderation as I picked the wrong from address11:31
slytherinLaney: which mail?11:33
Laneythe one where the guy asked about autosync11:33
slytherinpersia: Can't it be added to a cron job?11:33
persiaslytherin, I suppose.  It might even be in a cron job sometimes.  I still think that if it's off now, it's because of Alpha 2.11:34
persiaOne of the reasons I believe it not to be in a cron job is that I suspect the script sometimes has errors, and it's useful to have a human check the results.11:34
slytherinRight. I thought same but considering that pycaml is in universe I was wondering why universe is frozen for alpha 211:34
=== azeem_ is now known as azeem
persiaI don't think the script differentiates.  I also prefer the freezes to be *everywhere* because there are several universe flavours.11:35
slytherinhmm11:36
ivoksmaybe a stupid question...11:56
ivoksis there a reason why one package would conflict with it self?11:56
persiaivoks, versioned conflicts maybe, as a result of some sequence of package name changes over time.11:56
ivokswithout version11:57
ivokslike this:11:57
persiaBut that would just be cruft.11:57
ivoksPackage: libopenais3-dev11:57
ivoksConflicts: libopenais3-dev11:57
ivoks:)11:57
persiaNo, that's just wrong.11:57
ivoksi thought so...11:57
ivoksthat should've been:11:57
ivoksConflicts: libopenais2-dev11:58
persiaI suspect there was once a libopenais3-n-dev that (correctly) conflicted with libopenais3-dev, and then the -n- was dropped, but the Conflicts wasn't dropped.11:58
persiaThat would make more sense.11:58
ivokshow about conflicting lib-dev and providing lib-dev?11:58
ivokswhile package is libX-dev11:58
ivoksthat would make sense if we would like to replace lib-dev with libX-dev, right?11:59
persiaivoks, That's permitted, and not uncommon when transitioning from libfoo-dev to libfooN-dev11:59
ivoksright...11:59
persiaBut "Conflicts" and "Provides" play funny.  I forget precisely how the overrides work.11:59
persia(in other words, do a test install as a dependency of something just to make sure)12:00
ivoksright...12:00
maxbA package never conflicts with itself, therefore "Provides: foo; Conflicts: foo" ensures that only one package doing that can be installed at a time12:10
ivoksyeah, that's normal12:10
ivoksthis one is conflicting it self :)12:11
ivoksanyway, i fixed it12:11
nhandlerHas anyone ever gotten "internal error: command failed with error code 123" with lintian before?12:45
joaopintohello12:52
joaopintoI am using a cdbs debian/rules, and calling dh_desktop from the install/package rule, however my postinst script is empty12:52
joaopintoany ideas ?12:52
sorenWhat did you expect to be in there?12:53
joaopintoI do have the #DEBHELPER# on debian/postinst12:53
joaopintothe script calling update-desktop-database12:53
joaopintothat was supposed to be inserted by dh_installdeb12:53
sorenWell, dh_desktop is a no-op these days.12:54
persiajoaopinto, dh_desktop was replaced by a trigger: man dh_desktop12:54
sorenWhat's the package?12:55
joaopintopersia, this is a package for jaunty, wasn't that trigger included on karmic ?12:55
joaopintosoren, not on the repositories12:55
sorenjoaopinto: That's not what I asked :)12:55
joaopintomy man dh_desktop does not metion a triger12:55
joaopintosolarion, acetoneiso12:56
joaopintoops, soren12:56
persiajoaopinto, Yes, in jaunty it still does something.12:56
joaopintothis package is for jaunty :\12:59
joaopintoI must be missing something12:59
persiaAre you defining a MIME type in your .desktop file?13:01
persiaIf not, dh_desktop doesn't do anything.13:01
joaopintoI know, I am13:02
joaopintoMimeType=application/x-iso13:02
directhexyay, /me just prepared a new package13:03
joaopintohum reading on some ML mentions that the cdbs gnome class is expected to add the call13:03
joaopintobut reading from the example file comments, it should be added by dh_installdeb13:03
persiaErm, no.13:04
persiadh_desktop is the only bit that adds stuff to the postinst.13:05
persiathe GNOME CDBS class calls dh_desktop.13:05
joaopintoI am calling it on install/package:13:05
persiaAnd in your buildlog, is that early enough?  Perhaps you could add "cat debian/foo.postinst" after your dh_desktop call in rules, and check that build log.13:06
joaopintowell, it does not change debian/postinst it is expected to change debian/package/DEBIAN/postinst , it does not13:07
persiaIt should change debian/foo.postinst, which then gets copied to DEBIAN/postinst.13:07
joaopintohum ? isn't #DEBHELPER# expected to be ketp untouched ?13:08
persiaAnyway, `cat` is a great tool to use in rules files to understand the state of the build during the build.13:08
persiajoaopinto, #DEBHELPER# is used as a placeholder for dh_foo to add stuff at build time.13:08
persia(or maybe it does happen in dh_installdeb: now I'm confused)13:09
joaopintopersia, right, but isn't that just for the final posinst ?13:09
joaopintoit does not make sense it being changed during building, since it works as a build input file13:09
joaopintoas far as i understand, the #DEBHELPER# is expected to be replaced only on debian/package/DEBIAN/postinst, not on the original postint13:10
joaopintoand it does, it is replaced by an emptry string, and nod the dh_desktop script as expected13:11
joaopintonot13:11
persiaHrm.  Well, try with DH_VERBOSE, perhaps.13:12
sorenjoaopinto: At the time dh_desktop is called, where exactly is the .desktop file?13:14
joaopintosoren, hum, good question13:15
sorenjoaopinto: It needs to be in $tmp/usr/share/applications13:15
sorenIf you're copying it in there at a later stage, that's your problem.13:15
sorenIf dh_desktop doesn't find a .desktop file in there with a MimeType key, it doesn't do anything.13:15
sorenI'm looking at acetoneiso's SVN, and I don't see a Makefile, so it's a bit for me to guess when it gets installed.13:16
joaopintook, dh_desktop is beeing called before dh_install that is probably my problem13:16
joaopintosolarion, you need to call qmake to get the Makefile13:16
joaopintoops, soren13:16
sorenI'm looking at the websvn thing, so I'm out of luck.13:17
persiaRather, if it doesn't find a .desktop file IN /usr/share/applications.  It ought be a bit more flexible, honestly, but the complaint was that it was running too often, and the corner cases where it doesn't work are often masked by it running several times during an installation run.13:17
soren..but you seem to have identified the problem now.13:17
joaopintonow I just need to find the cdbs post-install rule name :P13:17
sorenpersia: Isn't that what I said?13:17
persiaHrm.  I should read better.  There's other valid places to put .desktop files to have them show up in the menus, and those don't work correctly.13:18
* soren wouldn't know13:19
joaopintoaccording to CDBS doc,  install/package should be post-install actions, however it's called before the debhelper specific install rule13:20
joaopintoperl -pe 's~#DEBHELPER#~qx{cat debian/acetoneiso.postinst.debhelper}~eg' < debian/postinst > debian/acetoneiso/DEBIAN/postinst13:23
joaopintocan anyone translate this to english :P ?13:23
cjwatson"read debian/postinst; replace '#DEBHELPER#' string with contents of debian/acetoneiso.postinst.debhelper; write result to debian/acetoneiso/DEBIAN/postinst"13:24
joaopintonice, it worked, just had to move the dh_desktop call to binary-package/app:13:24
joaopintocjwatson, tks13:24
cjwatsonperhaps you were running dh_desktop and dh_installdeb in the wrong order13:24
joaopintosoren and persia, tks, it was the dh_desktop call place13:24
cjwatsondh_installdeb must be run after anything that produces autoscript fragments13:25
joaopintoI was, because according to the CDBS docs the install/* is a post-install rule, and it's a pre-post-install :P13:25
joaopintothe problem was with dh_install being called after dh_desktop13:26
joaopintoit's fixed now, tks :)13:26
joaopintois there a page where you can see package versions for multiple debian based distros/repositories ?13:47
Hobbseean output of rmadison?13:48
Hobbseeactually, i think there is somewhere13:48
joaopintormadison only works with a single db, right ?13:49
cjwatsondepends on what server it's talking to13:49
cjwatsonwe set it up to talk to madison-lite; you can instruct madison-lite to look at whatever archives you want13:50
cjwatsonall you need is the Packages and Sources files in the appropriate layout13:50
joaopintothe db backend is just a Packages/Sources parser, os is it a real db ?13:50
persiajoaopinto, https://launchpad.net/multidistrotools could help you construct a nice page from multiple distributions, if you like.13:52
cjwatsonjoaopinto: just a Packages/Sources parser with a bit of caching13:52
cjwatsonpersia: mdt was replaced by chdist, wasn't it?13:53
joaopintoI am developing a generic apt2sql tool, maybe it would be interesting to have cross debian-derivated distro view13:53
cjwatsonjoaopinto: http://manpages.ubuntu.com/manpages/karmic/en/man1/madison-lite.1.html13:54
persiacjwatson, Indeed it was: that explains why we lost track of upstream.  Thanks for the pointer.13:55
persiawgrant, ^^13:55
persiajoaopinto, If you're looking for tracking stuff in SQL, you may also find http://wiki.debian.org/UltimateDebianDatabase interesting13:56
wgrantpersia, cjwatson: That didn't do HTML output, last time I checked.13:57
joaopintoah, so there is such db already13:57
persiajoaopinto, I'm not sure that UDD has information on the versions for all derivatives, but at least the structure might be useful.13:57
cjwatsonwgrant: no, but it's reasonably machine-parseable so I'm sure it'd be easy to transform13:58
cjwatsonwgrant: assuming you mean madison-lite13:59
wgrantcjwatson: I meant chdist, actually.13:59
joaopintohttp://udd.debian.org/schema/udd.html#public.table.packages <- It misses XSBC-Original-Maintainer13:59
RainCTHeya13:59
cjwatsonwgrant: oh, I never used the old mdt so I don't know13:59
wgrantIt just seems to be a Perl rewrite of the core bits of mdt, minus the fairly long and messy versions2html.13:59
persiacjwatson, http://qa.ubuntuwire.com/mdt/main.html is an example of the mdt output.14:00
=== thekorn_ is now known as thekorn
joaopintoI was thinking on a generic table, allowing to associate random fields to a package, to avoid changing a detailed table when a new field is included on the format14:00
joaopintohum, is UDD expected to have public external read access ?14:02
persiajoaopinto, You can download a snapshot of the DB contents from udd.debian.org (dunno about external public access)14:05
joaopintoperl cgis, yuck :P14:06
joaopintoi'll continue the apt2sql python script14:07
=== dendrobates-afk is now known as dendrobates
ttxdholbach, ara: finished my packaging training session, posted logs. Should I clean up the "upcoming sessions" area in https://wiki.ubuntu.com/Packaging/Training as well ?14:15
arattx: I can do it, don't worry. Thanks a lot ttx!14:15
ttxara: my pleasure.14:16
dholbachthanks ttx, you're a java packaging rockstar!14:16
dholbacha general rockstar even14:16
ttxdholbach: I prefer that :)14:16
geserjpds: I'm thinking about what's the best way to add some cacheing to lp/functions.py (from udt): do it in a class (which I prefer) (and move it to an own file) or do it on module level in functions.py. What's your opinion?14:24
jpdsgeser: Class sounds go, I think Laney wanted to OOP program everything too, go for it :)14:26
jpdsgood*14:27
Laneyjpds: ref?14:27
jpdsLaney: Didn't you say you wanted to OOP bits of u-d-t?14:28
Laneyyeah, I mean what did geser propose?14:28
RainCTLaney: < geser> jpds: I'm thinking about what's the best way to add some  cacheing to lp/functions.py (from udt): do it in a class (which  I prefer) (and move it to an own file) or do it on module level  in functions.py. What's your opinion?14:28
Laneyaha14:29
geserLaney: I'm thinking about adding some cacheing to lp/functions.py to not refetch everytime objects from LP14:29
Laneyyes that's a good idea, and my thought was to encapsulate it in a class14:29
geserthat was my idea too14:30
RainCTbtw, does someone know if there are any plans to update libmotif?14:31
mterryIs there an easy way to search if any Ubuntu package puts files in a given directory?  packages.u.c only lets me search on filenames, not directory names.14:33
cjwatsonit lets you search on parts of filenames too, doesn't it?14:33
cjwatsonor you can use apt-file, or grep the Contents files in the archive directly14:33
LaneyRainCT: It looks to be QA, so that plan could come from you!14:34
Laneyalthough someone did ITA it a while ago14:34
geserRainCT: the thread about it on http://lists.debian.org/debian-devel/2009/05/msg00656.html is known to you? I've just seen on the PTS page for it that a new version is laying around on mentors.d.n (since nov 2007)14:37
directhexoh arses, i wanted to see the java session14:37
directhexcould have been educational14:38
mterrycjwatson: Yeah, parts of filenames, but that doesn't include the directory path.  I'll try your other suggestions.  Thanks!14:38
persiadirecthex, irclogs.ubuntu.com has the log, and the speaker is likely still available to answer questions in #ubuntu-java14:38
RainCTLaney, geser: thx14:39
mterrycjwatson: apt-file works like a charm14:40
persiamterry, Only trick with apt-file is that sometimes either Contents is out of sync, or it's not being generated for a given release.  Be aware of this if you're planning to rely upon it.14:44
mterrypersia: Sure14:44
directhexttx, one thing i didn't see asked: do java packages get their binary deps tracked automatically? i.e. if i have foo, which build-depends libbar-java, do i need to manually specify the binary dep on libbar-java?14:46
ttxdirecthex: it's not tracked automatically.14:47
persiaThere's some work towards doing that, but it's still in it's infancy.14:47
persia(at this point, it's lucky if a given non-libary package can set it's own classpath correctly without a wrapper script)14:48
ttxdirecthex: usually it's up to the Java program to pull the required libs14:48
ttxdirecthex: rather than up to libs to pull potentially-required runtime dependencies14:48
ttxbut I've seen both approaches in the wild :)14:48
directhexttx, and do you anticipate java 7 bringing any major changes to the field?14:49
ttxdirecthex: I'm not a Java expert, I'm a Java victim. So I don't know.14:50
directhexttx, if nothing else, that statement there earnt you a lol ;)14:50
ttxmy vague understanding was that they dropped from Java 7 all the work that was kinda going in that direction14:51
directhex...14:51
directhex*golf clapping*14:51
devfilasac: ping14:52
directhexttx, and java libs don't have anything resembling an ABI version or SONAME, which is why you unversion the package names & simply cross fingers in package deps where versions are concerned?14:53
asacdevfil: ?14:54
asac(contentless ping?)14:54
ttxdirecthex: welcome to my daily nightmare14:54
directhexttx, i don't envy you, from the picture you're painting14:55
devfilasac: I'm using swiftweasel right now to test it and it seems to be faster than Ubuntu firefox, the source code contains the patch applied to firefox to enable somethings to make it faster, why Ubuntu firefox package doesn't have these changes?14:55
ttxdirecthex: it's not as bad as it sounds. But it will become more difficult as we add more Java software to Ubuntu14:55
devfilasac: there is also http://brainstorm.ubuntu.com/idea/18058/14:56
bddebianHeya gang15:02
geserHi bddebian15:04
asacnow he is gone15:05
directhexttx, well, good luck with it15:07
devfilasac: I'm here again :)15:08
asacdevfil: good. so thats not new and we are working on PGO15:10
asacfor karmic15:10
asacbut in general swiftweasel is not really famous for making sane things ;)15:10
asacso whatever the answer is, swiftweasel is unlikely to have the answer ;)15:11
devfilasac: so in karmic we will have firefox 3.5 (as decided to UDS) + PGO... great! About swiftweasel, it is only an example for "wow, firefox in linux can be faster too :)"15:12
bddebianHeya geser15:12
asacdevfil: most likely we will get PGO with xulrunner 1.9.1 PGOed and if it really helps also ffox 3.5 PGOed (though all bin code is in xul)15:13
asacdevfil: so swiftweasel does PGOed builds?15:13
devfilasac: I don't know how PGO works, in the patch there are only somethings enabled (pipelining), however the about window reports "Swiftweasel version 3.0.10 PGO", so I think yes15:15
asacdevfil: yeah pipelining is one of the things that are not sane ;)15:16
asacbut it should really not matter that much anyway15:17
asacso i guess its really PGO15:17
asacwhich gives hope that this will give a noticable boost15:17
asacthough it might be a bit tricky because we cannot PGO firefox ... nistead xulrunner15:17
devfilasac: why can't we PGO firefox?15:18
asacbecause firefox does not have many binary bits15:18
asacits just 1MB of size (the package)15:18
asacbut technical details. i have to write a spec about it i guess15:19
devfilasac: firefox package is a metapackage, I mean the real firefox source15:22
asacdevfil: firefox-3.515:36
asacis 1mb and does not have much binaries15:36
asacanyway. no need to discuss on these details ;) we are on it.15:36
devfilasac: great, thanks :)15:37
andrew_sayersIs it considered bad manners to propose a new feature by sending an unprompted merge request?15:39
persiaandrew_sayers, Depends on the project, really.  Do you have context?15:40
andrew_sayerspersia: in this case, I proposed adding code to Ubufox that would work around Flash not setting the screensaver...15:41
persiaAh.  For that, I'd suggest filing a bug with an attached branch, rather than just a merge request, and asking about it on #ubuntu-mozillateam.15:42
superm1ooh i'm curious on this code15:43
persia(but I may be incorrect in my understanding of how the mozillateam likes stuff: I just remember hearing about multiple review cycles for some people's first patches)15:43
superm1checks when flash is active on a webpage and inhibits the screensaver?15:43
geserjpds, Laney: I've commited a singleton for LP API access to trunk: using it makes e.g. calling buildd --help from ~5sec to < 0.1 sec15:44
andrew_sayerspersia: fair enough, will do.15:44
andrew_sayerssuperm1: currently inhibits when there's Flash anywhere on any open page.15:44
superm1cool15:45
andrew_sayersCleverer solutions are worth looking at if the code's actually likely to get used :)15:45
persiaPersonally, I'd be against that.  I often have a page or two with some silly flash ad minimised (or even at the front) when I step away.15:45
persiaSomething that only inhibited for current focus, or similar would be nicer.15:46
persia(although I tend to end up with my screen locked in the process of stepping away, so perhaps I'm not the best example user for this use case)15:46
Laneygeser: cool, that's a good start. Next up is full-on sexy encapsulation15:47
andrew_sayerspersia: yeah, I wouldn't be surprised if the answer was "we'd merge that if it inhibited in X, Y and Z conditions".  I'm mostly looking to see if there's interest right now.15:47
superm1i think maybe the better solution is to offer an interface from firefox to cause an inhibit, and then flash should start using said hook15:50
superm1since likely the reason it doesnt happen now is that flash is sandboxed from calling out to apps on the system15:50
RainCTpersia: ever heard about adblock-plus? :)15:51
persiasuperm1, But *when* should flash call that hook?15:51
superm1when video playback is active15:52
andrew_sayerssuperm1: Flash could easily inhibit the screensaver if it wanted - it's just a matter of sending a DBus message.  They've had a bug report open for about 6 months now, and no sign of activity.15:52
persiaRainCT, I don't mind viewing advertisements.  At one point in the past, a significant chunk of my income came from others viewing advertisements.  Sometimes they are even useful to me (albeit rarely).15:52
superm1i suppose i dont know flash internals perfectly, but i would think that video playback is some type of standard call15:52
superm1can you send a dbus message from a firefox plugin though?15:53
andrew_sayersNo, but you can run a Python script...15:53
persiahrm.  Be nice if that was possible to differentiate.15:53
superm1again matter of being able to shell out to the system, or I suppose linking against dbus15:53
andrew_sayersIf you're really interested, the merge request is at https://code.launchpad.net/~andrew-bugs-launchpad-net/ubufox/flashsaver/+merge/676815:54
jpdsgeser: Awesome :)16:06
persiaCould a pbuilder user tell me where I would put pbuilerrc.config?16:22
* persia digs at docs more, and discovers more pitfalls to bind_mounting /home when fiddling.16:27
hyperairpersia: ~/.pbuilderrc16:27
persiahyperair, Yeah.  I discovered that one, but that's not throwaway.  I'm trying with /etc/pbuilderrc, although I'm unsure if it will work for my use case (playing with qemubuilder).16:28
hyperairaah16:28
hyperairqemubuilder eh..16:28
hyperairit's good for x86 and x86_64, but powerpc... *shudder*16:29
persiaBut in a LVM-hosted schroot, so I don't want to dirty my local area.16:29
hyperairO_o16:29
hyperairi see16:29
persiaSpeed is not the issue :)16:29
hyperairpersia: i don't really care about speed either, but setting up qemubuilder for powerpc is hell.16:31
hyperairpersia: you need the kernel, and you can't apt-get install it without a powerpc machine because you can't chroot into a powerpc installation16:31
hyperairugh16:31
persiaWell, that's just a matter of wget + dpkg -x.  More annoying is probably that one has to somehow get an Ubuntu build of openhackware (which can't build due to a quirk in Soyuz).16:32
=== dashua__ is now known as dashua
nixternalpersia: with backports, in this case amarok 2.1, it would require a new package that was separated out of the previous releases, what is the policy if there even is a policy? can you add a *new* package to backports?16:39
nixternaland who keeps moving developer documentation to help.ubuntu.com/community?16:39
nixternalJontheEchidna: ^^ do you know the process since it seems you are working on it?16:40
persianixternal, I don't know.  Ask one of the backporters.  I think it's discouraged, at least.16:41
JontheEchidnaI've not actually done one before but I have read to docs and one point last week :P16:41
JontheEchidnabasically just show that it builds/intalls/runs on the target distro, while attachign a debdiff of the changes16:42
JontheEchidnaand then one throws it at ScottK :P16:42
nixternalJontheEchidna: ya, but the qtscriptengine though, that isn't in jaunty at all16:43
JontheEchidnaright16:43
JontheEchidnaIt looks like I'll have to rewrite the totally non-backportable packaging for qtscriptgenerator (the official package in karmic)16:44
JontheEchidnav.v16:44
persiaAlso, one has to be careful about anything with rdepends.  Dunno if any of the listed ones would break.16:44
nixternalfun16:44
nixternalJontheEchidna: what about the jaunty builds of it that are in the ppa? you can just use that16:44
nixternalditch the changelog of course ;p16:44
JontheEchidnathat would be a new package (qtscriptbindings is the name in the package of the ppa)16:45
nixternalya....we might just have to stick with ppa in this case16:45
JontheEchidnabut amarok upstream really wants 2.1.0 in -backports :(16:46
JontheEchidnamaybe we could just take the packaging for qtscriptbindings and rename it qtscriptgenerator? :D16:46
nixternalpeople in hell want ice water too16:46
JontheEchidnathey are the same thing, except for the packaging differences16:46
persiaJust find a couple backporters, and offer tasty bribes.16:49
joaopintoa theorical question17:11
joaopintodeb http://pt.archive.ubuntu.com/ubuntu/ jaunty universe17:11
joaopintois there any convention for the /ubuntu/ part ? should it match the Origin value on the Release field ?17:11
persiaIt's fairly flexible, although it's nice when it carries recognisible branding of some sort.17:15
persia(e.g. ports.ubuntu.com uses /ubuntu-ports/ )17:15
=== yofel_ is now known as yofel
cjwatsonpersia: and the reason for *that* is so that a mirror can easily carry both /ubuntu/ and /ubuntu-ports/ if it wants to17:36
persiacjwatson, That makes an incredible amount of sense.  Is it normal to do things like that, or would the guideline of following Origin be better?17:38
cjwatsonpersia: I think just something identifying is fine17:38
joaopintothere is an odd thing, the ports related archictures are listed on the "ubuntu" root Release file17:39
joaopintodespite them not being available on that archive17:39
joaopintoI mean http://archive.ubuntu.com/ubuntu/dists/jaunty/Release17:40
joaopintoI guess main/binary-amd64/Packages , etc should not be listed there17:41
joaopintoopd, I mean't armel17:41
joaopintoops17:41
=== rmcbride_ is now known as rmcbride
cjwatsonjoaopinto: yes, that's because the split only happens at mirroring time and it can't edit the Release file because it's already signed17:46
cjwatsonjoaopinto: just ignore it17:46
cjwatsoni.e. the archive publication process just publishes one giant archive, part of which gets mirrored out to /ubuntu/ and part of which gets mirrored out to /ubuntu-ports/17:46
joaopintook, I am checking for the arch specific Release file availability before trying to import it17:47
fabrice_sp_Hi, Is the status of this bug report correct bug #383825 ? I always thought merge rshould be Confirmed, and not In progress..17:49
ubottuLaunchpad bug 383825 in texlive-bin "[karmic] libpoppler4 -> libpoppler5 transition" [Undecided,Confirmed] https://launchpad.net/bugs/38382517:49
fabrice_sp_not this one17:49
fabrice_sp_this one: Bug #38547617:50
ubottuLaunchpad bug 385476 in inkscape "Merge with Debian" [Wishlist,In progress] https://launchpad.net/bugs/38547617:50
directhexhm. jcastro?17:54
=== ejat is now known as e-jat
binarymutantif anyone has any free time to spare, http://revu.ubuntuwire.com/p/pidgin-mbpurple , needs advocation :P18:08
joaopintocjwatson, is the ubuntu archive managed with reprepro ?18:22
joaopintoon my repository reprepro is setting the arch's Release file "Archive:" to the codename of the base Release file, I see that -security and -updates have the "Archive:" set to the "Suite:" name18:25
persiajoaopinto, It'S not.  It's managed by Launchpad.18:34
joaopintook, so it's a reprepro issue18:34
joaopintoDebian also uses the base suite name as the archive name18:34
=== bdrung_ is now known as bdrung
Id2ndR_Hello. didrocks is here ?18:46
didrocksId2ndR_: yes, I'm here :)18:48
Id2ndR_didrocks: great ! That's difficult to be here at same time as you're18:48
Id2ndR_didrocks: I think there is something quite easy I'd be able to do with https://bugs.launchpad.net/bugs/37316718:49
ubottuLaunchpad bug 373167 in gnome-control-center "After installing Thunderbird, preferred applications shows both "Mozilla Thunderbird" and "Thunderbird"" [Low,Confirmed]18:49
didrocksId2ndR_: timezone rules ;) But I'm always on IRC, so, you can drop a message and I can read it later18:49
maxbjoaopinto: Have you found anything that actually cares about the content of those architecture Release files?18:50
Id2ndR_didrocks: that's true, but this is not very usefull to get answers18:51
joaopintomaxb, I am developing such a thing, I care18:51
maxbjoaopinto: APT doesn't seem to download them.... why does your thing care?18:51
didrocksId2ndR_: (I'm reading)18:51
joaopintomaxb, APT does also care, but it only cares about a specific view, your system architecture18:52
didrocksId2ndR_: ok, I'm not sure that it's something we will change now, as we are changing the way "default application" are setted up. So, this will have an impact on this bug18:53
maxbjoaopinto: I know APT cares about the dists/XXX/Release file - I'm not certain that APT even downloads the dists/XXX/component/binary-arch/Release files18:53
joaopintomaxb, well, they are on the archive, if they are not required they should not be there in the first place :P18:54
maxbI agree :-)18:55
joaopintoeither I rely on them, to establish a unique key, or I just ignore them and rely on the base Release file18:55
LucidFox@leave18:56
Id2ndR_didrocks: Ok so you think that it is nopt usefull to work on this, that's it ?18:56
didrocksId2ndR_: yes, as the way we handle prefered application will change in karmic release18:57
slytherinpersia: if a package fails to build with openjdk but builds fine with gcj (probably because bug in gcj), should I change build dep or fix the package? I have to yet confirm that there is a bug in GCJ.19:00
Id2ndR_didrocks: Ok. I think I haven't do anything since I'm in the programm. So what do you think I shoud work on ?19:00
persiaslytherin, Hrm?  It's a bug that the package builds?19:00
maxbjoaopinto: As I said, I'm 99% sure that APT completely ignores them, so you probably should too19:00
maxband what apt uses as "Archive" for the purpose of "release a=foo" policy definitions is the Suite field19:01
joaopintook, tks19:02
joaopintoI will just use (origin, suite, version, architecture)19:03
slytherinpersia: there is a enum declared which members having non-ascii names. I believe gcj does not yet handle enum type as defined by java 1.5 but rather handles it as defined by 1.4. So it builds with GCJ but fails to build with openjdk because of non-ascii names.19:03
persiaslytherin, Hrm.  I'm unsure whether that's a bug in gcj or in the 1.5 spec.19:04
persiaI'd "fix" the package, just to avoid the gcj dependency, but I think it's a suboptimal solution.19:04
slytherinpersia: ok. is this a unicode letter - å ?19:05
persiaslytherin, 'Q' is a unicode letter, but 'å' is not an ASCII letter.19:06
maxbThere are restrictions on characters of allowed enum values beyond those applied to java identifiers in general? Really?19:07
slytherinpersia: the naming rule for variables is this - an unlimited-length sequence of Unicode letters and digits, beginning with a letter, the dollar sign "$", or the underscore character "_". So I guess a variable starting containing å is not correct.19:07
slytherinmaxb: no separate restrictions for enum. same as variables.19:08
maxbThat rule relies on the ambiguous definition of "letter"19:08
persiaslytherin, How is "letter" defined.  I suspect that's vague.  Is 'は' a "letter"?19:08
maxbWhat's the package? I'd like to see what sun java makes of that source19:09
slytherinpersia: not sure. I am just reading this from standard java tutorial.19:09
slytherinmaxb: libjaudiotagger-java. I think sun java will also fail to build it.19:09
persiaslytherin, Right.  That's my point.  THe spec is unclear.  It ought define the set of codepoints that are acceptable as "letter"s.19:09
persiaI suspect they mean the alphabetic characters with ASCII values between 33 and 89.19:10
* maxb hunts the JLS19:10
slytherinI too think the same. But then I wonder why gcj does not fail on this.19:11
* slytherin goes to dinner19:12
maxbThe Java letters include uppercase and lowercase ASCII Latin letters A-Z (\u0041-\u005a), and a-z (\u0061-\u007a), and, for historical reasons, the ASCII underscore (_, or \u005f) and dollar sign ($, or \u0024).19:12
maxbslytherin: ^19:12
persiagcj is GNU.  GNU eats unicode for breakfast (something about people getting whiny and submitting patches)19:12
slytherinmaxb: thanks, where did you find that?19:13
persiamaxb, Ah, great.  Thanks for finding the glossary.  It is a bug in gcj then.19:13
maxbJLS3e19:13
maxbhttp://java.sun.com/docs/books/jls/third_edition/html/lexical.html#3.819:13
* slytherin goes for dinner19:14
=== fabrice_sp_ is now known as fabrice_sp
=== lakin_ is now known as lakin
slytherinmaxb: that paragraph is also confusing. There is also a statement about allowing programmers to use identifiers in native language.19:34
maxbslytherin: what is confusing?19:35
slytherinwhy does it talk about identifiers in native language when they are not allowed.19:36
maxboh, point19:39
maxbit says "include" not "is"19:39
slytherinanyway i am for now patching the package19:40
slytheringot to go. battery low, no electricity.19:41
maxbI will figure out the real answer later....19:41
persiamaxb, When you do, please file a bug against whichever of gcj or openjdk is buggy :)19:44
geserLaney: looking at the LP API doc and the canUploadPackage in functions.py (udt): do you think it's sufficient to check the archive_permissions for a person and compare the component of it with the component of a source package instead of iterate over all uploaders?19:47
Laneygeser: I don't know how that will work for per-package uploaders though19:49
Laneybut it could be good for shortcutting in the majority of cases19:49
geserand use isPackageUploader for the other cases19:51
Laneygeser: we should try to avoid leaking LP API objects out19:52
Laneyall calls should go through the wrapper19:52
geserisPerPackageUpload is from functions.py19:52
geserbut I need to rewrite both functions to use the new LpApiWrapper class19:53
Laneyhmm19:53
Laneymost of those functions should move inside the wrapper19:54
geserI've already started moving some of them to the new wrapper class and marked the old functions as deprecated19:54
geserso nothing will break till all scripts are moved to the wrapper class19:55
geser(see my latest commits to udt)19:55
=== DrKranz is now known as DktrKranz
Laneygood stuff19:57
Laneyso all I worry about is not leaking details of lplib out to clients19:57
geserI'll try to do my best to avoid it (but don't on the other hand to write a function just to access an attribute of an LP object in one script in one place)20:01
RainCTniice, VoxForge now has enough phonemes to recognize the word «computer» :P20:04
RoAkSoAxivoks, Why is openais-legacy FTBFS in the Ubuntu-HA repo?20:22
ivoksit's not anymore :)20:22
ivoksi removed it20:22
ivoksthere's no need for it in ppa20:23
ivokscause we have it in karmic repository20:23
ivoksi've sent pacemaker to ppa, so that it rebuilds with openais-legacy from repository20:23
RoAkSoAxivoks, ok cool20:24
RoAkSoAxivoks, though the one in the PPA was 2009060620:25
ivoksthat's 14 days diff20:26
ivoksfor version that's not being developed, right?20:26
RoAkSoAxivoks, yeah but i has a patch on the init script20:26
ivokswell, apply it20:27
ivoksdon't change version of package20:27
ivoksonly revision20:27
RoAkSoAxivoks, here's the changelog: http://pastebin.ubuntu.com/193688/20:27
ivokswell, ok20:28
ivoksonce that version gets into debian, we'll sync20:28
RoAkSoAxivoks, that would be better then20:28
ivoksand rebuild pacemaker20:28
RoAkSoAxok cool20:30
ivoksdon't worry20:31
RoAkSoAxivoks, I just want to be helpful :)20:32
ivoksi know ;)20:32
ivoksgrrrrrrrrrr20:33
ivoksit failed to build20:33
ivokswhy now20:33
ivoksah...20:34
ivoksgrrrr20:34
ivoksinit script20:34
RoAkSoAxivoks, ohh I remember.. that's why I uploaded the openais-legacy package from Madkiss20:35
ivoksyeah :/20:35
ivoksi give up for today20:35
RoAkSoAxivoks, you gonna fix that package or should I upload openais-legacy again or should I just apply the changes?20:35
ivoksgo ahead, upload the openais-legacy 2009060620:37
RoAkSoAxivoks, ok.20:37
ivoksi just did a 24 hours circle20:37
RoAkSoAxivoks, that's awful.. you need to get some sleep20:38
ivoksthat's true20:38
ivokstake care...20:39
RoAkSoAxu too20:39
Nafallohmmm20:39
Nafallowhat's the difference between bzr import and bzr merge-upstream ?20:40
Nafalloanyone know by any chance?20:40
savvasNafallo: try #bzr (or #bazaar - I forgot), but have you checked the help messages? bzr import --help; bzr merge-upstream --help20:52
=== pace_t_zulu_ is now known as pace_t_zulu
Nafallosavvas: yes. didn't help much.20:53
Nafallolifeless: question for you a few (read about 14, including join/parts) lines up :-)20:54
persia#bzr is the place to go then.20:54
persia(and it's likely too early for lifeless at this hour, although I could be mistaken)20:54
Nafallopersia: of course it is. thank god irc is async ;-)20:55
persiabut someone in the right channel might know now :p20:55
Nafallopersia: well. considering both those commands are in plugins... :-)20:56
Nafallo(and I don't need to know now. I'll just import as usual ;-))20:56
NafalloAAAAAAAAAAA. silly tarball!20:57
Nafalloit removed my tree and added a subdirectory with the name of the program-version.20:58
Nafallothank god I branched it before.20:58
Nafallo*FACEPALM*20:59
jpdsNafallo: Thanking yourself?20:59
Nafallohow am I supposed to use this as orig.tar.gz20:59
NafalloI need to rebuild the damn thing :-(20:59
Nafalloehrm. ignore me. I'm on crack.21:05
Nafallobut something else it broken I reckon.21:05
ausimageAre there any knowledgeable python packagers available to help with http://revu.ubuntuwire.com/details.py?upid=6023?21:09
ausimageIt is python app I am coding and attempting to package for karmic...21:10
ausimageI was also attempting to package it in pieces too21:10
ausimageand that is where I am stuck perse.... at least the karmic buildd on LP is :/21:11
ausimageIt is just not finding a file from soovee-common.21:11
fabrice_spausimage, when I have a problem with this kind of things (splitting a package in several pieces), I build the package from within a schroot, and see what files are created where21:23
fabrice_spI'm just having this issue (files in a wrong place), and I'll build the package in a chroot21:23
ausimagek... then I need to learn how to do that I guess :/21:23
fabrice_spit's easy :-)21:24
fabrice_splt me check the wiki for the page21:24
ausimagek21:24
fabrice_spyou have a pbuilder installed?21:24
ausimagefabrice_sp: that is one item on my punch list21:24
ausimageno21:24
fabrice_spoh21:24
ausimagethe other is that I am being requested to change the name of the package to add 0ubuntu as well as orig to the original tarball21:25
fabrice_spausimage, https://wiki.ubuntu.com/DebootstrapChroot for dchroot21:25
fabrice_spand you'll find all the tools info here: https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases21:26
fabrice_spto add 0ubuntu1 to the version, you just have to change the version in debian/changelog21:26
ausimagenot that... when a I got to build source in order include original I need soovee-0ubuntu.orig.tar.gz....21:27
fabrice_sp?!21:27
ausimagenot soovee.orig.tar.gz21:28
fabrice_spyou need soovee-<version>.orig.tar.gz21:28
fabrice_spyou miss the version21:28
ausimagethe version too yeah21:28
ausimagebut I have include -0ubuntu in the name too21:28
fabrice_spactually, it's sovee_<version>.orig.tar.gz21:28
fabrice_spwith a _ not a -21:28
ausimagenot here... if I have the the file as you suggest it says it is not there21:29
fabrice_spcheck your changelog: the version should be the same21:30
ausimagethe current is soovee_1.07.221:30
ausimagehttp://revu.ubuntuwire.com/details.py?upid=602321:30
ausimageis the current package21:30
ausimagefabrice_sp: I did try without... the -0ubuntu in the original and it would not locate the tarball21:31
fabrice_spthe version is wrong21:31
fabrice_sp1.07.2-0ubuntu-1 should be 1.07.2-0ubuntu121:31
fabrice_spthat's why it's requesting you to have -0ubuntu in orig21:32
fabrice_sphave to go. Sorry.21:32
ausimageduh... guess my brain is not withit to catch that :/21:32
fabrice_spbye21:32
ausimagelaterz21:32
geserdoes someone with per-package upload rights need sponsoring for sync requests? I assume no21:50
persiageser, Ideally they oughtn't, but I'm not sure the archive-admins have a view as to who can upload what.21:58
persia(might be handy to have a script that checked a sync bug to see if it was approved, if that's parsable by comments)21:59
Nafalloso... who do I need to cuddle for this SRU? ;-)22:05
joaopintocan the simple fact that the software contained  package is not working justify justify an SRU that will introduce a new upstream version ?22:06
persiajoaopinto, Only if a fix can't be backported for some reason.22:07
joaopintowhy backporting a specific fix instead of doing an upstream upgrade, based on the fact that the current version was never tested/working during the entire development cycle, what is the advantage of using a fix versus new upstream ?22:09
persiaI don't have a good answer, and have found myself in that position previously.  That's the policy though.22:10
joaopintowell, I am not going to spend time that may be wasted on a policiy block, i'll just try to get it fixed for Karmic, since it's still broken there22:13
persiaGetting it fixed in karmic first is a requirement for SRU anyway.22:15
joaopintoah :\22:17
=== cemc is now known as cemcNA
rawlerwhenever someone's got a minute or two, I've got a package needing sponsoring..22:23
rawlerjust don't really test it for too long.. it's kindof addictive.. :)22:23
rawlerhttp://revu.ubuntuwire.com/details.py?upid=602522:23
joaopintopersia, what is the recommended procedure, should I contact the debian maintainer asking for the update on Debian first ?22:34
joaopintothis is a python2.6 transition related issue, I am not sure it affects debian at the same extent22:35
persiajoaopinto, getting an update in Debian always makes it nice because we don't have to care as much.  Depending on how upstream distributes the source, it may even be essential to get it into Debian first.  If that is taking a long time, and you want to pursue the SRU, and there's no worries about the orig.tar.gz, don't let Debian delay you.22:37
bulletxthi, is someone kind enough to package and include AcetoneISO for ubuntu Karmic, it's about 2 years there's a launchpad ticket but no one ever picked it up and do the work22:38
joaopintoI already built a package for myself, if no one missed it yet on jaunty I will not care about it, I will try just emailing Debian maintainer first22:38
joaopintoit is a minor release upgrade from the debian version perspective22:39
persiajoaopinto, Right.  It sounds like it's mostly important in terms of being missed in the jaunty update.22:40
ingenthri have a question about packaging for Ubuntu I hope someone can point me in the correct direction on22:54
ingenthrit's not immediately for Universe, but may like to get it there some day so I want to do things correctly22:54
Cry__Babyhello22:55
Cry__Babywhat is Karmic Koala ?22:55
persiaingenthr, Ask away.  The faster you learn, the faster it can get in, and the more users wil be happy :)22:56
persiaCry__Baby, It is the development release of Ubuntu, scheduled to be released as Ubuntu 9.10 in october.22:56
Cry__Babycool22:56
Cry__Babywhat is the main objective of this channel, and who are the people that visit here?22:56
ingenthrpersia: thanks; i've looked at the wiki(s) and the debian policies, and what i'm not sure about is what namespace a package should live in... it looks like it should be /opt/${provider} but it could be /usr/local too22:57
persiaThe objective is suitable for debate.  On-topic discussions include packaging, coordination of packages in universe, Ubuntu development discussions, and related topics.22:57
ingenthrpersia: though it looks as if /usr/local is really for the syadmin if building from source?  the whole thing gets more confusing if looking to the LSB and the LANANA22:58
persiaingenthr, For something to be part of the distribution, it should be in neither of those places.  It belongs in /usr22:58
persiaMy personal opinion is that /opt is for non-free software, and /usr/local/ is for special bits added by the sysadmin.22:58
ingenthrpersia: where in /usr if it's a system daemon?22:59
ingenthrpersia: i work with the memcached project and some of my colleagues and I have a new project we'd like to get a number of people to be able to easily use22:59
persiaingenthr, binaries in /usr/bin, libraries in /usr/lib, resources in /usr/share/${package}, configuration in /etc, state files in /var/lib/${package}, cache in /var/cache/${package}, logs in /var/logs/${package}.23:00
joaopintoCry__Baby, reading the topic also helps :)23:00
persiaingenthr, Then get it packaged, and get it distributed :)23:00
Cry__Babyjoaopinto, true :)23:00
joaopintoingenthr, you might want to look how for a similar daemon already packaged23:01
ingenthrjoaopinto: true enough...  :)  will do... i'm a bit of a n00b here and trying to follow the docs...23:04
joaopintosomeone already submited a debdiff for the package I was talking about, bug 36885523:05
ubottuLaunchpad bug 368855 in cherrypy3 "formatwarning() definition from cherrypy3 incompatible with Python 2.6" [Undecided,Confirmed] https://launchpad.net/bugs/36885523:05
joaopintoit's one month old, let's hope it will not become one of those left behind until the release23:07
persiajoaopinto, Is the debdiff good?  Does it fix the problem?  Should I upload it?23:08
joaopintohum, I'll check23:08
joaopintoit introduces changes which are not required23:08
joaopintolike debhelper version bump23:09
joaopintooh, the debdiff is based on jaunty's version, it was before the synch23:11
=== vuilzak is now known as GrimKo
ingenthrone other question: if you want to create a binary package for different versions, should one build it on the oldest version?23:14
=== vuilzak is now known as GrimKo
joaopintodepending on library changes you may need different build rules/package versions for each ubuntu release23:15
persiaingenthr, That's often safest.  Build on the old version, and copy forward.  Distro policy forbids insertion of new packages into old releases though, so one does that starting from now.23:16
=== vuilzak is now known as GrimKo
joaopintowell, that debdiff is not fine, the fix for the python2.6 compability is a one liner, but I still think it's best to go with the new upstream version, I will wait for the debian feedback23:18
ingenthrjoapinto: my only external dependency is libevent, and i'll certainly test with newer releases23:18
joaopintoingenthr, ok :)23:18
ingenthrjoapinto: have been building on 8.0.4 to be safe23:19
persiajoaopinto, Could you comment on the bug detailing how the debdiff isn't fine, and why it's better to wait?  That ought save anyone else from having to investigate.23:19
lifelessNafallo: hi23:20
lifelessNafallo: bzr import is built into bzr23:21
lifelessbzr merge-upstream is a bzr-builddeb command and knows about packaging metadata23:21
joaopintothat debdiff makes sense if it's aiming for the SRU with a new upstream23:22
persiajoaopinto, And it has a MOTU-SRU ACK.  Does it belong in jaunty-proposed?23:25
joaopintohum, I have justed in packages.*23:26
Nafallolifeless: hmm. thanks :-).23:27
Nafallolifeless: I reckon my memory is just bad (rather than import having changed)23:27
joaopintopersia, it is not available on jaunty-proposed...23:28
ausimageK... karmic build is really wierd :S23:28
persiajoaopinto, Yes, but I can put it there.  I'm distracted by many things, and you have been investigating this, so I'll take your advice, if well argued and well-grounded.23:28
nhandlerIf a file says it is available under the BSD license, what keyword (http://wiki.debian.org/Proposals/CopyrightFormat?action=recall&rev=196#Keywords) should I use? BSD-3 ?23:28
joaopintopersia, oh wait, let me test it, I didn't test the build, was just reading the debdiff23:29
persiajoaopinto, OK.  Let me know.23:29
ausimageinstead of placing the files in debian prior to packaging... it places them in build... with a lib.linux-i686-2.6 and scripts-2.6 directories23:30
persianhandler, If a file claims to be under the "BSD" license, it isn't.  quote the license.  (all actual BSD-licensed code has the proper BSD license in the code, and is copyright The Regents of the University of California)23:30
ausimagehows it know where they end up when they are all lumped like that  :?23:31
lifelessNafallo: you may be thinking of import-dsc23:33
binarymutantif somone could review and possibly advocate http://revu.ubuntuwire.com/p/pidgin-mbpurple , I would be forever grateful :)23:34
nhandlerpersia: It is a Perl module which says "You may use this module under the terms of the Artistic, GPL, or the BSD licenses."23:35
persianhandler, Hrm.  That's tricky.  Artistic allows that usage.23:35
Nafallolifeless: doesn't look like it I'm afraid. :-)23:36
Nafallolifeless: more likely that I'm getting old ;-)23:36
joaopintopersia, it does not build, I have commented on the bug report23:39
ausimageI figured it out!!23:40
ausimagejaunty use dist-packages and karmic uses site-packages23:40
ausimage:/23:40
persiajoaopinto, Thanks.  I'll unsubscribe the sponsors.  Since it has MOTU-SRU ACK already, if you can fix it (perhaps in collaboration with the patch submitter), it can be done.23:40
ausimagein an install file can I use *-packages for that directory?23:40
ausimageor is it too big a tool again :/23:41
* ausimage picks up the tool and attempts to swing it at his package for karmic23:43
joaopintopersia, question, a debdiff is expected to be applied over an base source+base bioçd diff right ?23:45
joaopintoI believe he just dif a diff between both debian/*, so the debdiff would apply if I used a new upstream orig23:45
joaopintoI mean, the patches would apply23:46
* ausimage does jig in his small space :D23:46
persiajoaopinto, I don't usually make that much fuss about the format of the supplied debdiff, as long as I can be confident that what I'm producing matches what the submitter had locally.23:47
persiajoaopinto, You may want to track down kklimonda when next available, and chat about it to resolve any confusion.23:48
joaopintook23:48
ausimagepersia is it ok to have install file with.... somedir/*partial/* ?23:49
persiaausimage, I think there's likely a more subtle way to do it, but I'm not sure.23:50
ausimagethis issue with my karmic package is distutils I think....23:50
ausimagethey changed their destination directory subtly from *dist to *site :/23:51
lifelessNafallo: import-dsc would import a dsc and grab the orig for you, it would output the right paths23:53
=== Nicke_ is now known as Nicke

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