/srv/irclogs.ubuntu.com/2008/05/07/#ubuntu-motu.txt

johHow would you typically invoke get-orig-source? Directly with debian/rules?00:08
johIs ${DEB_SOURCE_PACKAGE} set anywhere?00:10
cheatrCould someone explain the difference between  Build-Depends and Build-Depends-Indep?00:19
pochujoh: I think './debian/rules get-orig-source' is ok00:39
pochucheatr: -Indep are only used for building arch:all packages (they are only built once, usually on i386 for Ubuntu, whereas arch:any packages are built once for each architecture)00:39
mok0cheatr: -indep are also used to run the clean target00:40
johpochu: Ok00:40
pochumok0: I thought packages used in clean should be in Build-Depends and not -Indep00:41
pochumok0: as you want to clean it in every architecture ;)00:41
johpochu: You always want to be able to clean the package though, arch dependent or not :-)00:42
mok0pochu: you may be right00:42
johs/package/source tree/00:43
mok0you have to be very careful with debian/rules to design it so it can build arch and indep targets independently of each other00:43
mok0for example, if the indep package is doxygen generated documentation, you can put doxygen in Build-Depends-Indep00:44
mok0pochu: I think the clean target is only called when you build the source package00:46
pochumok0: right, but if you build some arch:any packages in say hppa you will call the clean target, so you need things called in clean to be installed00:51
pochuso they need to be in Build-Depends and not in -Indep00:51
* jdong thinks the new update-manager security update notification icon is evil and nice :)00:51
jdongthat bold red exclamation mark really gets the point across00:52
jdongonly thing that'd do it better is if in 7 days it turns into a glowing pair of red eyes...00:52
mok0pochu: afaik the indep targets are only built on the i386 platform, all others are binary package only00:52
pochumok0: yes, but they will call clean anyway00:53
pochuthat's http://lintian.debian.org/reports/tags/clean-should-be-satisfied-by-build-depends.html00:53
pochu"The specified package is required to run the clean target of debian/rules and therefore must be listed in Build-Depends, not Build-Depends-Indep, even if no architecture-dependent packages are built. "00:53
mok0pochu: I stand corrected00:54
pochuI should be misunderstanding you then00:54
pochu01:40 <      mok0> cheatr: -indep are also used to run the clean target00:54
mok0Of course the easiest is to avoid using Build-Depends-Indep altogether :-P00:55
superm1jdavies, got a few min?00:55
superm1oops00:55
superm1jdong,00:55
superm1that is00:55
emgentthere is a big problem in pulseaudio00:56
emgentnow my laptop sound dont work00:56
jdongsuperm1: reviewing for a test, but shoot if it's fast00:56
emgentlast ubuntu updates?00:57
pochugood night00:57
superm1jdong, no i am just trying to get you for more than 3 min to discuss this handbrake build system00:57
superm1to see where you got on things00:57
jdongsuperm1: I havent' given it much of a look00:57
superm1o00:58
jdongsuperm1: if the archive admins are okay with it carrying embedded versions of the libs it wants, I think we should just prefetch the versions it wants for it, then build statically against it00:58
jdongsuperm1: i.e. do the fetching step while building the src pkg00:58
superm1jdong, could you shoot an e-mail to ubuntu-devel about it ?00:58
jdongsuperm1: I think this is not a bad idea either because we are talking about encoding against iPods and other sensitive-to-format devices and upstream often has good reason for picking said versions00:58
superm1well not often, sometimes it 's just for convenience00:59
superm1eg look at the date that they picked the version and the latest version available on that date00:59
jdongsuperm1: I recall there being a big differential the last time I looked01:00
jdongsuperm1: esp. for things like ffmpeg that change on a daily basis, it felt to me like they made particular choices01:00
superm1jdong, well if ubuntu-devel says no, then i say we go to devs01:00
superm1and talk to them about the choices they made01:01
superm1and how hard coded they are on those versions01:01
jdongsuperm1: agreed01:03
jdongbut we do have precedence for bundling encoders with volatile APIs01:03
jdongVLC, mplayer (at some points), gstreamer, etc01:03
* superm1 shoves mythtv aside01:03
=== fta_ is now known as fta
=== effie is now known as effie_jayx
=== evalles_ is now known as keffie_jayx
bddebianHeya02:21
sommerScottK: uploaded an adjusted php5-clamav package to the ppa02:32
ScottKsommer: Cool.  How did it go?02:32
sommerScottK: built and tested fine on my machine... basically the same issue as python-clamav02:33
ScottKCool.02:33
sommerthe url in the debian/copyright file is no longer active however02:34
ScottKsommer: I'm asking the Debian clamav maintainer how he'd like to proceed now.02:35
sommerScottK: cool, which channel?  (I need to get more involved with debian :)02:36
ScottKIt's a PM at the moment.02:36
sommerah02:37
sommerI also took a look at dansguardian, and there's a new up up stream release that covers 0.9302:37
sommeris it better to backport or do an NMU, and sync?02:37
ScottKI'll ask.02:37
sommerScottK: cool thanks02:38
ScottKAccording to him dansguardian was just uploaded.  Would you check if it needs a merge or is we can just wait for it to sync.02:39
sommerScottK: sure, where do you chack for merges? :)02:40
ScottKsommer: Look in Launchpad and see if there's an Ubuntu diff.02:41
sommerScottK: nm, reading https://wiki.ubuntu.com/UbuntuDevelopment/Merging02:41
ScottKK02:41
sommerScottK: ah thanks, I'll do that too02:42
sommerScottK: from what I can tell after reading the merge page and the package page: http://packages.ubuntu.com/intrepid/dansguardian... a sync will be fine02:57
sommerScottK: is the package page the one you meant when refering to LP?02:57
ScottKThat's the one.03:01
sommergreat, I'll move on down the list03:02
ScottKsommer: I tend to look on LP becuase it's more up to date.  We have it already: https://launchpad.net/ubuntu/intrepid/+source/dansguardian/2.9.9.4-103:04
sommerah, I always forget the /ubuntu/codename part of the url03:05
sommerScottK: that's the latest version on the dansguardian website, so we should be good03:06
ScottKWould you please upload that to the PPA.03:06
sommersure03:06
ScottKWith an appropriate version number.03:06
=== boomer` is now known as boomer
RoAkSoAxno0tic, have you created a pbuilder already=03:58
RoAkSoAx?03:58
no0ticnot for intrepid03:58
RoAkSoAxno0tic, im building it without problems03:58
no0ticI'm waiting the new disc! :)03:58
RoAkSoAxi thought you already got it03:59
RoAkSoAxno0tic, anyways, i guess they fixed libc6 issue, but i did this and it is going good so far: sudo pbuilder create --distribution intrepid --othermirror "deb http://it.archive.ubuntu.com/ubuntu intrepid universe multiverse"04:01
CTho!seen mario_limonciell04:03
ubottuCTho: Error: I am only a bot, please don't think I'm intelligent :)04:03
=== Igorot_ is now known as Igorot
sommerScottK: dansguarding == success, uploading to the ppa04:11
ScottKsommer: Great.04:11
bddebianAnyone very familiar with doxygen?04:12
ScottKsommer: Would you please file a bug against php-clamavlib with a debdiff for your change and I'll upload it to Intrepid and then send it to Debian.04:12
sommersure will do04:12
sommerScottK: Bug #227588, in case it doesn't email you :)04:20
ubottuLaunchpad bug 227588 in php-clamavlib "Patch for clamav-0.93" [Undecided,New] https://launchpad.net/bugs/22758804:20
ScottKsommer: Thanks04:20
sommernp, think I'm going to call it a night... I'll update the wiki tomorrow04:20
ethana2anderson58ken: hi05:49
ethana2hey, could we get tesseract into repositories?05:49
ethana2or is there some other OCR software already there?05:49
RoAkSoAxethana2, tesseract-ocr05:50
ethana2oh05:50
ethana2is there any way to make add/remove show things without gui frontends?05:51
ethana2anderson58ken: sudo apt-get install tesseract-ocr05:51
RoAkSoAxethana2, you mean in the comand line?05:52
anderson58keny05:52
ethana2nevermind ;)05:52
ethana2back in 1005:52
=== Scientus_ is now known as Scientus
ethana2anderson58ken: you got it installed?06:27
dholbachgood morning06:28
RoAkSoAxanyone here that can help me?06:47
ethana2possibly06:47
RoAkSoAxethana2, packaging stuff ?06:47
ethana2involving a package needing modification in or addition to ubuntu repos?06:47
ethana2oh06:47
ethana2yeah, this is the place06:47
ethana2...i think06:47
ethana2(I'm not talking about /me/ though)06:47
RoAkSoAxethana2, yeah i know, but i ment you lol...06:48
ethana2sorry ;(06:48
RoAkSoAxok np ;)06:48
RoAkSoAxseems everyone is sleeping06:48
RAOF!ask | RoAkSoAx06:50
ubottuRoAkSoAx: Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-)06:50
RoAkSoAxRAOF  i know that.. but at this time of the day everyone is sleeping so i was just wondering is someone was alive that could helo me06:51
RoAkSoAxRAOF, you expert in packaging?06:51
RAOFRoAkSoAx: I'm a MOTU.  I can _probably_ help.06:52
RAOFRoAkSoAx: The nice thing about worldwide collaboration is that someone's _always_ awake.  It's mid afternoon here :)06:52
ethana2late evening here :)06:53
RoAkSoAxRAOF, here is almost 1 hour after midnight xD06:53
ethana2I mean, it's 9:53, but since we're so far north, still very bright out06:53
RoAkSoAxRAOF, ok 'll explaing my prob... i did a merge and after doing the necessary changes i tried to build the binary and i got this error: http://pastebin.ubuntu.com/10679/06:53
RoAkSoAxRAOF, since it shows problem with patch 99_... i supposed i had to drop the patch and i did it... so after dropping, i built another source package and then tried to build the binary again and i got this error: http://pastebin.ubuntu.com/10680/06:54
warp10Good morning06:55
RoAkSoAxany ideas what could be wrong?06:55
RoAkSoAxgood morning warp1006:55
warp10hi RoAkSoAx06:55
RAOFRoAkSoAx: Right; so, this is one of autotools less endearing features.06:56
RoAkSoAxRAOF, so what should i do?06:57
RAOFWhat's happened is that someone has made some changes to the build system, presumably to make it look for mozilla-xpcom in teh right place or something.06:57
RAOFChanging the build system requires re-running autoconf, which shouldn't be done at package build time because it makes things non-deterministic (or less obviously deterministic).06:58
RAOFSo, you re-run autoconf and then work out the diff between the new buildsystem files and the old files; this is what 99_... was.06:58
RoAkSoAxok, the Build-Depends in debian/control are: http://pastebin.ubuntu.com/10681/ and i think mozilla-com is this package: xulrunner-1.9-dev (something to note, MoM only showed me that there were conflics on the Build-Depends)06:59
RAOFThis indicates that the packaging is non-trivial; you'll need to understand what's being patched and why before you can actually perform the merge.07:00
=== doko_ is now known as doko
RAOF(Moreso than usual; you should have at least a basic understanding of the packaging for any merge, and checking for that is part of the sponsorship duties)07:01
RoAkSoAxRAOF, that patch was for:   * rerun autotools07:01
RoAkSoAx    - debian/patches/99_autotools_rerun.patch07:01
RAOFRoAkSoAx: Yeah; I know.  What you need to work out is what part of the buildsystem was patched, why it was patched, and probably end up re-running autotools and creating a new 99_autotools_rerun.patch.07:02
RAOFOne of the previous patches probably touches a Makefile.am or configure.ac; that's the buildsystem change you're interested in.07:02
RoAkSoAxRAOF, do you have any documentation that i can see to do it (i'm just learning packaging =)07:04
RAOFRoAkSoAx: I'd suggest trying a different merge if you're just learning; build system changes are always ugly and autotools is the work of Satan.07:08
RoAkSoAxRAOF, what if i've already reported it and suscribed to u-u-s ? https://bugs.launchpad.net/ubuntu/+source/blam/+bug/22667007:09
ubottuLaunchpad bug 226670 in blam "[wishlist]Please merge blam 1.8.5-1 from Debian unstable (main)" [Undecided,Confirmed]07:09
RAOFRoAkSoAx: You shouldn't have subscribed u-u-s until you'd finished the merge.  u-u-s subscription should be once you've finished and have uploaded the debdiff.07:10
RAOFRoAkSoAx: I'm a member of u-u-s, so I can unsubscribe; you'll want to unassign yourself from the bug with a comment that it's free.07:11
ethana2DANGIT07:12
ethana2Satan on irc.freenode.net is already registered07:12
RoAkSoAxRAOF, yep now i know i shouldn't have, but i did what i was told there... and i just realized of this problem when redoing the merge (because i wanted to redoit to get more familiarized)07:12
RAOFRoAkSoAx: Did you upload that debdiff without testing that it built?07:12
ethana2I was going to have him show up and denounce it ;)07:12
RAOFHeh.07:12
* RAOF stops trying to chase the null pointer through nv40 gallium.07:13
ethana2oh?07:13
ethana2RAOF: is it close to being usable?07:13
ethana2RAOF: the FOSS nVidia drivers?07:14
RAOFethana2: Depends on what you mean by "usable".  ~07:14
RAOFYes, the foss nvidia drivers.07:14
ethana2Human Being playing tremulous07:14
ethana2...usable?07:14
RAOFDunno.  Never tried tremulous.07:15
ethana2nexuiz?07:15
ethana2any 3d thing07:15
RAOFIt works for neverput & neverball.07:15
RAOFAnd PPracer07:15
ethana2sweeeet!07:15
ethana2compiz?07:15
RAOFAnd OpenArena07:15
ethana2does OpenArena work well with it?07:15
RAOFNo, not compiz.  It doesn't yet support a bunch of necessary hooks.07:15
RAOFYes.07:15
ethana2but it probably will soon, right?07:15
RoAkSoAxRAOF, in my learning process i didn't realized that it haven't built the first time... and as i said... i just realized that it didn't when redoing it :(07:16
ethana2within 6 months?07:16
RAOFethana2: Dunno.  If Canonical hired a full time dev, my answer would be 'almost certainly, and we'd be shipping nouveau by default for nv40'.07:16
ethana2ok then07:17
ethana2my Ubuntu dell will be an nVidia card07:17
RAOFBut it depends.07:17
ethana2is nv40 what's in the 8400gs?07:17
RAOFNoooooo.07:17
ethana2oh07:17
ethana2what's the 8400gs?07:17
RAOFnv4x == 6xxx/7xxx, nv5x = 8xxx/9xxx07:17
ethana2ah07:18
ethana2are there any exceptions to that?07:18
RAOFnv5x is currently undersupported.  I'm not sure if there's _any_ 3d for it yet, and 2d is very much unfinished.07:18
RAOFethana2: No, I don't think so.  Not like that stupid Geforce 4 MX business.07:18
ethana2I think I heard about that card today....07:18
ethana2when i mentioned my radeon 9200se07:19
ethana2something about sucking horribly, i may be mistaken07:19
RAOFYeah; the GF4MX was _actually_ a GF2 chip.07:19
RoAkSoAxRAOF, so... you going to unsuscribe it from u-u-s and i should do that too and add a comment that it is free to be merged??07:19
RAOFRoAkSoAx: Yes.07:19
RAOFRoAkSoAx: Unsubscribed.07:19
ethana2RAOF: well it sounds like you wouldn't consider nv5x support to be a /problem/ in the future07:20
ethana2just the present07:20
ethana2that's good enough for me to buy one I guess07:20
RAOFThat's true; I'd be buying ATI at this point though.07:20
ethana2my other option on the Dell Inspiron is the X310007:20
ethana21/2.8x the power of the 8400gs07:20
RoAkSoAxRAOF, ok thanks, and sorry for the inconvenience... but i would still like to have documentation to work on it and just learn by myself... got any?07:21
ethana2and I'm going to be watchin peach and playing apricot, so I need all the power I can get ;)07:21
RAOFYeah.  If it wasn't blown out of the water by ATI or nvidia cards, I'd be totally there.07:21
* ethana2 goes to leave you fine gentlemen alone now07:21
RAOFRoAkSoAx: I'm not sure if I've seen any 'patch the buildsystem' documentation.  I certainly can't remember any.07:21
ethana2thanks for all the info, RAOF07:21
RoAkSoAxRAOF, ok thanks, and sorry for the inconvenience  =(07:22
RAOFNo inconvenience at all!07:22
RAOFFeel free to ask as many questions as you like; much easier to learn from other peoples experience than from your own mistakes :)07:23
RoAkSoAxyeah thanks very much for your help RAOF :D07:24
=== tb1 is now known as tbf
=== ogra_ is now known as ogra
CrippledCanarycould someone pleas look at possibly sponsor Bug #22424109:50
ubottuLaunchpad bug 224241 in smstools "smstools stop working after upgrade" [Undecided,Confirmed] https://launchpad.net/bugs/22424109:50
slytherinwhere can I see how many packages are there in u-u-s queue? Just curious.09:58
Hobbseebugs.lp.net/~ubuntu-universe-sponsors09:58
slytherinHobbsee: guess what, your link does not go to launchpad. :-P10:01
=== asac_ is now known as asac
Hobbseeslytherin: expand it :)10:01
* Hobbsee typed it from memory, rather than visiting10:02
slytherinHobbsee: still you should check it. There is actually a site called lp.net. :-)10:02
* Hobbsee thought you would be skilled enough to automatically expand it.10:02
Hobbseeapologies for not typing every single character.10:03
=== luisbg_ is now known as luisbg
slytherinHobbsee: are you being serious? It is not your fault. I overlooked it. No offense meant.10:04
Hobbseeslytherin: oh ;)10:05
Hobbseeslytherin: sorry, i'm still kinda stunned at the stuff that has come out in -meeting today.10:05
Hobbseeso i'm trying to be careful, and not break rules that i don't know about10:06
\shHobbsee, one solution: just swear at me..I'm used to it ;)10:08
* norsetto swears at \sh10:08
Hobbsee\sh: i can't.  even if i apologise to you, i'm still a leader in stuff related to ubuntu, and so it gets held against me forever.10:08
Hobbsee\sh: i'm unsure if it makes a difference if the apology is publically logged or not, but i do hope not to need to try it.10:09
* \sh doesn't file complains for every little crap said in any channel here10:09
Hobbseeyes, you don't.  but others might, on behalf of you, and it still gets me lynched.10:09
Hobbseesee the -meeting earlier :)10:09
Hobbsee(this is the kind of stuff as to why i'm still stunned)10:10
\shHobbsee, oh hell yes...the moses problem and the hundreds of thousands laws around them10:10
\shno crime without a law10:11
* slytherin searches meeting log10:39
lagaslomo__: URL? ;)10:39
lagaerr, slytherin. sorry.10:39
slytherinlaga: I am not sure I have found the right one, I just started reading it. - http://irclogs.ubuntu.com/2008/05/06/%23ubuntu-meeting.txt10:41
lagaugh. interesting drama.10:46
i4xgood morning!!10:47
i4xhugs for everybody!..10:48
Hobbseelaga: unfortunately, yes ;)11:02
ajmitchdid I miss something interesting?11:08
\shajmitch, you miss all the funny things ;) /me too ;)11:11
norsettoall bow to huats (so that he will give you an ubuntu t-shirt)11:40
mok0Please remind me: how can I list all packages that provide a certain meta-package?12:10
pochumok0: do you mean that provide a virtual package?12:12
mok0pochu: yes, I need to know what packages provide libgl-dev12:12
pochuIf so, 'aptitude show $package' will do the trick12:13
mok0pochu: THANKS!12:14
mok0pochu: AFAIK some of the proprietary Nvidia packages also include a version of GL12:14
mok0pochu: I hope they provide that virtual package as well...12:15
wgrantmok0: IIRC they divert something.12:17
mok0wgrant: ok, great12:17
wgrantSo they probably won't provide them.12:17
pochuwhat's the right place to explain the renaming of a source package? debian/README.Debian-source?12:19
pochuhmm, README.source12:19
wgrantIsn't it README.source?12:20
* wgrant checks.12:20
wgrantThere's a standard now.12:20
mok0pochu: copyright I think12:20
wgrantmok0: No.12:20
mok0README.source has been discussed on the DD list12:20
mok0As I understand it, it's for explaining how to build a source package that can not be done using the standard tools12:21
pochuhttp://lists.debian.org/debian-devel-announce/2008/04/msg00016.html12:21
pochubut I'm not sure this can be included here12:21
pochu"a12:21
pochupackage where one one cannot unpack the source package with dpkg-source -x12:21
pochuand immediately get the source that would be built"12:22
mok0pochu: right12:22
wgrantpochu: Are you renaming binaries as well?12:22
pochuhere if you can do 'dpkg-source -x' I assume you already have it packaged, so the renaming of the upstream tarball has already been done...12:22
gnomefreakanyone with a intrepid system/chroot can you please try gpg --edit-key adduid <keyID> or <email for key>? im trying to add an address to my key and its not working12:23
mok0pochu: in what way are you renaming a source package?12:23
pochuwgrant: this is because there's too 'alarm-clock' packages been packaged, one in Debian and one in REVU, so I'm suggesting the REVU packager to rename it (or to talk to the Debian owner of the ITP)12:23
gnomefreakand it prints gpg info (version, ect...) than back to command propmt12:23
wgrantpochu: Is it already in Ubuntu?12:24
johpochu: Hi, could you please see my comment on revu regarding alarm-clock?12:24
pochuso he has proposed to rename it to alarm-clock-applet, but that would need to be done to the source package too, which should then be documented12:24
pochuoh joh, you're here :)12:24
pochuwgrant: nope12:24
slytheringnomefreak: shouldn't keyid be immediately after --edit-key?12:24
johHah, you're talking about my app :P12:24
wgrantpochu: Why would you document it, then?12:24
gnomefreakslytherin: i thought adduid was but maybe that is after getting into gpg :) thanks ill try12:24
mok0pochu: I would think changelog, then, that's what I am doing with mesa-glw12:25
wgrantpochu: No point documenting it if it's only on REVU.12:25
johpochu: Why would the source package need to be renamed btw? The binary itself is named 'alarm-clock-applet' for what it's worth...12:25
gnomefreakslytherin: thanks that was it12:26
pochujoh: because (I think) there can't be two source packages with the same name12:26
pochuwgrant: well, it will some day hit the archive and if I go and update it I would like to know what changes have been done to it12:26
johpochu: Ah you meant that source package. I thought you were talking about the original tarballs. Sure :-)12:26
pochuwgrant: although I think i see your point, that it's obvious to what it has been renamed looking at the actual name12:26
mok0What's the difference between the two alarm clocks?12:27
wgrantpochu: It hasn't been renamed if it was only known by the old name on REVU.12:27
johmok0: the one in debian is a stand-alone python app, mine's a gnome applet.12:27
pochuwgrant: ah, sorry, with renaming I mean renaming from the upstream tarball, not from an old package12:27
wgrantpochu: No need for a comment.12:28
pochuI mean, this is not a transition12:28
mok0joh: then I think the package should be called alarm-clock-gnome-applet12:28
johmok0: Really? Cause other gnome-applets have names ending only in -applet, like sensors-applet.12:28
mok0pochu: I would think it is sufficient to document in the changelog12:28
wgrantalarm-clock-applet12:28
wgrantIt's not a change!12:28
mok0ah well12:28
johwgrant: *nod*12:28
wgrantit doesn't need documentation.12:28
pochuok12:29
mok0As someone running kubuntu, it is nice to be able to see from the package name that the applet is for gnome12:29
mok0But that's only my 2 cents12:30
wgrantmok0: Other GNOME applets are -applet.12:30
wgrantAren't KDE applets plasmoids?12:30
mok0wgrant: yeah12:30
mok0wgrant: plasmoids? :-)12:30
wgrantIt does seem odd to just call them -applet, but it's also odd to not follow convention.12:31
pochuwell, the description is "Description: Alarm Clock applet for the GNOME panel"12:31
mok0wgrant: it's probably wise to follow convention12:31
wgrantmok0: Plasma has plasmoids.12:31
norsettowhats wrong with gnome-alarmclock-applet?12:31
mok0I like the sound of that12:31
johSo what changes are needed to change the name? Other than editing control and changelog?12:32
mok0joh: that's it12:32
johnorsetto: Well, it's not officially part of gnome so I'm a bit reluctant about branding it that way...12:32
johmok0: Nothing in rules needed?12:32
mok0joh: is the applet already in hh?12:32
johmok0: hh?12:33
mok0hardy heron12:33
johmok0: no12:33
norsettojoh: it doesn't need to be officially in gnome for that12:33
pochujoh: that's for the binary package. for the source package, rename the orig.tar.gz and move the alarm-clock-*/ directory to the new name12:33
norsettojoh: see gnome-mplayer as an example12:33
johpochu: ok, thanks.12:33
\shgrmpf12:34
johnorsetto: That's true.12:34
\shdamnit12:34
norsettojoh: btw, it fails compilation in intrepid, did you check if it compiles with gcc-4.3?12:34
\shwho the hell packaged this tool12:34
johnorsetto: Haven't tested against intrepid yet now...12:34
johnorsetto: *no12:34
\shfireflier-client-kde doesn't depend on fireflier-server neither recommends it12:34
norsettojoh: I'm getting few warnings (unused variables, implicit declarations) and a couple of fatal errors12:35
wgrant\sh: Why should a client need a server?12:35
norsettojoh: alarm.c:1858: error: expected ')' before ';' token12:35
johnorsetto: I'll look into it. Probably a missing header.12:36
\shwgrant, it should recommend it actually :)12:36
\shor suggests12:36
johnorsetto: Could you pastebin the whole output please?12:36
norsettojoh: yes12:36
\shwgrant, I just thought it's a stupid frontend for iptables ;)12:36
wgrant\sh: If it is client-server one might conceivably want the client without the server.12:37
norsettojoh: for the fatal error is just that and alarm.c:1858: error: too few arguments to function 'g_timeout_add_seconds'12:37
\shwgrant, yes..but it should actually point someone to "hey, there is actually a server, and this tool does not use iptables only" ;)12:37
wgrant\sh: .*client.* matches.12:38
johnorsetto: That's wierd, which version of glib?12:38
johAlright, alarm-clock-applet source package uploaded to revu12:40
norsettojoh: the one currently in intrepid, in my build log is libglib2.0-0 2.16.3-112:41
johnorsetto: They wouldn't change API from 2.14 to 2.16 though. How can I test this out myself without upgrading my entire system? pbuilder?12:42
\shah damnit..I'll hack manually my iptables...so I know it works out of the box ;)12:42
norsettojoh: yes12:42
joh\sh: If you're looking for a frontend to iptables, shorewall is pretty nice.12:43
* norsetto -> lunch12:44
jdaviesnorsetto: bon appetit12:44
brooniestgraber: Is there any great reason why pastebinit isn't in Debian?12:45
stgraberbroonie: the debian packager not having uploaded it yet :)12:47
stgraberbroonie: David Paleino is supposed to do it (last I spoke with him)12:48
brooniestgraber: Ah. I've got someone else (Rolf Leggewie) wanting me to sponsor an upload of it just now.12:48
stgraberhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=42522612:48
ubottuDebian bug 425226 in wnpp "ITP: pastebinit -- command-line pastebin client" [Wishlist,Open]12:48
stgraberthat bug is almost one year old :)12:49
broonieAnd no activity.12:49
brooniePlus the initial ITP is malformed.12:50
broonieOK, thanks.12:50
stgrabernp12:51
johHow exactly do I create an intrepid chroot with pbuilder? I tried upgrading my hardy build with DIST=intrepid sudo pbuilder update --override-config --othermirror "deb http://no.archive.ubuntu.com/ubuntu/ intrepid main" but there are package conflicts...12:52
stgraberjoh: sudo pbuilder --distribution intrepid create12:53
johstgraber: Ok, thanks12:53
johsudo pbuilder --create --distribution intrepid: E: No such script: /usr/share/debootstrap/scripts/intrepid12:54
jw2328_joh: do you have hardy-backports enabled>13:02
johjw2328_: no?13:03
=== jw2328_ is now known as james_w
james_wyou need it so that the updated debootstrap that knows how to create intrepid can be installed.13:04
johOk, I'll try that then13:05
slytherinjoh: upgrade is not working due to a bug. And create is not working due to another bug. :-P13:10
johslytherin: Seems to be working now though :P13:11
johOr not...13:11
slytherinjoh: What is working? create or upgrade?13:11
jcfpuntil libc6 fails to install...13:11
johslytherin: create, but: W: http://archive.ubuntu.com/ubuntu/dists/intrepid/main/binary-amd64/Packages.bz2 was corrupt13:12
johW: Failure trying to run: chroot /var/cache/pbuilder/build/13869/. mount -t proc proc /proc13:13
slytherinjoh: please tell me once you are finished with the create process. Last time Itried it didn't work.13:13
johslytherin: It didn't work here either. pbuilder: debootstrap failed13:13
mok0ls13:14
mok0focus error, sorry13:14
johCould someone please review http://revu.ubuntuwire.com/details.py?package=alarm-clock-applet ?13:14
mok0joh: collapse your changelog entry into just one13:17
johmok0: Ok13:18
mok0joh: in rules, remove the sample comment at the top13:19
johmok0: The entire comment?13:20
mok0joh: and remove the debhelper calls that have been commented out and that you're not using13:20
mok0joh: yes13:20
mok0joh: that's the custom13:20
mok0joh: get rid of all not needed fluff13:20
mok0:)13:21
johDone :-)13:21
mok0joh: also, the #ifeq ... stuff, it seems you always want to compile w/o optimization13:22
johmok0: Yeah, for debugging purposes actually...13:22
johmok0: Is that a bad idea?13:23
mok0joh: if someone else is ever to take a look at the package, s/he will not know why that is still there, if it is commented out for debugging, or what. So it's best to remove it13:23
johmok0: I meant -O0 was for debugging purposes, not the commented out block :-)13:24
mok0joh: in fact, it's just boilerplate left over from the template13:24
joh*nod*13:24
mok0joh: ah!13:24
mok0joh: well, then activate it :-)13:24
joh-O0 makes gdb backtraces more sensible though - better bug reports :P13:25
mok0joh: in .pod file, spelling mistake: "appelt"13:26
johWhups :P13:26
mok0joh: also, avoid "speech" style: It's -> It is13:27
johAlright13:27
slytherinDo you have any policy about 'machine interpretable copyright'?13:27
mok0joh: same in control13:27
johmok0: Ok, fixed13:28
mok0joh: that's all at the moment... nice work!13:28
johmok0: Great, thanks for your help!13:29
mok0joh: sorry, I don't have time to build and test the application, I need to go soon13:29
johmok0: No problem, when/if you have time let me know if it works or not ;-)13:29
johChanges uploaded.13:29
johToo bad I'm unable to test it in intrepid though.13:30
mok0joh: yeah ii is not really ready yet13:30
johmok0: Yeah, but norsetto reported he had trouble building it in ii...13:31
mok0It's in a state of flux at the moment... I am sure it will stabilize in a few weeks13:31
johAlright :-)13:32
mok0New packages from Debian unstable are streaming in13:32
emgentheya13:34
mok0norsetto: ping13:35
mok0wgrant: ping13:36
wgrantmok0: Morning.13:36
mok0wgrant: I need a pair of eyes to look at my split-out package for the GLw libraries13:37
wgrantOh dear.13:37
mok0wgrant: are you available?13:37
wgrantI guess so, though my library packaging knowledge isn't great.13:37
mok0wgrant: I will post a debdiff to Debian's mesa package, hang on13:38
wgrantmok0: You need to split the source...13:38
Hobbseeoh no, jono's here.13:39
Hobbseeeveryone behave.13:39
mok0wgrant: I did13:39
mok0wgrant: but I need to know if I did it correctly :-)13:39
jonohey13:40
mok0wgrant: Bug #22771213:41
ubottuLaunchpad bug 227712 in ubuntu "[needs-packaging] GLw libraries from Mesa" [Wishlist,In progress] https://launchpad.net/bugs/22771213:41
mok0wgrant: It is only modifications to the packaging, not the building of the libraries13:48
* mok0 thinks there should be a XS-Original-Source: field to tell the merging system that this is a source package splitoff13:50
norsettomok0: pong14:45
johnorsetto: The reason alarm-clock-applet didn't compile was actually a bug in the source. Fixed now :-)14:46
norsettojoh: cool14:46
ramviI've made a deb using checkinstall. It works great, but when I add it to my repository apt-get returns: E: Problem parsing dependency Depends \ E: Error occurred while processing eeepc-wlan (NewVersion1) \ E: Problem with MergeList /var/lib/apt/lists/... / E: The package lists or status file could not be parsed or opened.14:55
ramviWhat am I doing wrong?14:55
* Hobbsee shrugs14:55
Hobbseecheckinstall isn't supported here, sorry.14:55
Hobbseecheckinstall often doesn't work, and is known to produce strange output.14:55
ramviOk, thanks14:56
wgrantAnd is completely offtopic for here.14:56
joaopintoand you should learn regular packaging instead14:57
ramviThe thing is: I've read the packaging guide about 10 times now. Using debhelper, I don't understand why I don't get a deb after running sudo pbuilder build ../*.dsc15:00
ramviI get changes, diff.gz, dsc, build, but no deb15:00
Hobbseeramvi: probably because you're not looking in /var/cache/pbuilder/result, or wherever you've specified it to be?15:00
ramviHaha, that should be in the docs some where15:01
ramviThanks! Plenty of debs :p15:01
Hobbsee....15:02
Hobbseeramvi: try man pbuilder15:02
Hobbseeramvi: scroll down to the section where it says '--buildresult'15:02
Hobbseeramvi: see the sections in bold, in those couple of paragraphs.15:02
Hobbsee!pbuilder15:02
ubottupbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto15:02
ramvithanks15:03
ramviSoon I'm a motu15:03
joaopintojust make sure you read the mans first :P15:04
johnorsetto: Let me know if you get the time to try building alarm-clock-applet btw.15:08
ramviI'm building a kernel module for the Eeepc, but sudo pbuilder build ../*.dsc returns Makefile.inc:66: *** /lib/modules/2.6.24-16-generic/build is missing, please set KERNELPATH.  Stop.15:08
jdaviesramvi: have you st KERNELPATH?15:10
ramviThe default seems good: /lib/modules/$(shell uname -r)/build15:11
ramviBut I guess it isn't as I get that message15:11
bddebianHeya gang15:12
IulianHi bddebian15:12
bddebianHello Iulian15:12
wgrantramvi: You are actually build-depending on the requisite packages, right...?15:15
ramviwgrant: didn't think there were any dependencies. Other then the kernel maybe.. Should I depent on linux*-generic?15:18
wgrantramvi: If you need a part of it to build, you probably do want it installed, yes.15:23
ramviwgrant: linux-source. That's it?15:23
wgrantramvi: Check what other kernel module packages do.15:24
ramviThanks! I'm trying with this now:15:26
ramviBuild-Depends: debhelper (>= 5), bzip2, linux-source, linux-generic, linux-headers-generic, linux-image-generic, linux-restricted-modules-generic, linux-restricted-modules-common15:26
wgrantramvi: Please look at other kernel module packages so you can do it properly.15:27
ramviOK, please tell me one to check out15:28
wgrantI'm not quite sure. virtualbox-ose-modules, perhaps.15:28
ramviThanks15:28
=== neversfelde_ is now known as neversfelde
ramviOh my, this is too hard. Can someone five minutes out of their day and make a deb of http://snapshots.madwifi.org/special/madwifi-nr-r3366+ar5007.tar.gz for all the Asus Eee users out there? Please pretty please15:42
johramvi: Did you read the packaging howto on the wiki?15:43
ramviYes. Several times15:43
gnomefreakdid you try the debian dir from the stable one in the repos?15:43
gnomefreakand adapt it that way might give you a good starting point atleast15:44
ramvignomefreak: What do you mean?15:44
* gnomefreak not saying its the best way to do it but see if it works15:44
gnomefreakramvi: we have madwifi in archives afaik grab the source and use it to help with building it15:45
wgrantgnomefreak: Not in any separate source...15:46
ramvignomefreak: It's part of linux-restricted-modules15:46
gnomefreakcant copy the top level dir over to new source and fix as needed15:47
gnomefreakoh15:47
gnomefreakthats gonna be a beast to do if you havent done much packaging from new package15:47
ramvior you could help me? ;)15:48
gnomefreakare repos dead?15:48
gnomefreakramvi: not with that i cant thats above my head, as in ive never done anything kernel related15:49
gnomefreakmaybe its just smart that died while fetching15:49
ramvioh, ok :)15:50
broonieramvi: https://help.ubuntu.com/community/EeePC FWIW15:50
jdongramvi: I had such a .deb that compiles-on-boot the madwifi module; currently I only have the packaging for the regular madwifing-trunk but it would work with a svn URL to the ar5007 branch too15:51
ramvibroonie: Most of that is from my wiki :) ubuntu-eee.tuxfamily.org15:51
* jdong looks at where he put it15:51
ramvijdong: what does that mean? Sound good15:51
jdongramvi: install the deb, it compiles the module. Every boot, it checks via a bootscript if the module is loadable. If not, it rebuilds it.15:52
ramviWow, great!15:52
jdongramvi: source package tarballed here http://jdong.mit.edu/~jdong/macbook/crackwifi.tar.gz15:54
jdongramvi: running debuild checks it out from svn15:54
ramvijdong: love you15:55
jdongramvi: see debian/rules to customize the rule that grabs madwifi... the package collects ./madwifi so you can get it from a tarball too15:55
jdongramvi: a bit rough around the edges but should be a very good starting position.15:55
jdongas a bonus, it depends on the kernel headers so you never end up in a case where after an upgrade you can't build the module15:55
jdong(all MOTU REVUers should probably look far away from that package....)15:56
ramvihehe, thanks!15:56
persiajdong: You didn't put it in REVU did you?15:56
jdongor use it as an example for how NOT to do an Ubuntu package ;-)15:56
jdongpersia: no :)15:56
jdongpersia: I wouldn't torment you guys THAT much when it's not april 1st15:56
Hobbseejdong: and somehow, you got upload rights...15:56
* persia breathes again. The automatix upload was enough for at least two releases...15:56
jdongHobbsee: it was a personal package, never meant to see the light of day ;-)15:56
ramviJust did though15:57
bobboIs anyone around to sponsor a debdiff for me?16:04
cbx33hey guys16:10
cbx33https://bugs.edge.launchpad.net/ubuntu/+source/kdenlive/+bug/22326016:10
ubottuLaunchpad bug 223260 in kdenlive "Kdenlive crashes loading saved .kdenlive files" [Undecided,New]16:10
cbx33do those backtraces make sence to any one??16:11
taishi28012quit17:06
ScottKjdong: I'm thinking we need to add a rule in backports about transitional packages.  We're dropping a bunch of them Hardy -> Intrepid and to backport across that boundary would really suck on upgrades.17:39
jdongScottK: (brain offline) you mean to {reject, prefer source-change to hardy-like convention} backports that involve a package transition?18:06
persiajdong: did you mean "intrepid-like" convention?18:10
* persia excitedly points at https://lists.ubuntu.com/archives/ubuntu-motu/2008-May/003776.html and encourages people to brainstorm18:15
persiaDoes anyone know the status of the various "click-to-install" solutions?  Either third-party or core repository?18:16
lagaapt-url can point to packages available from sources.list AFAIK18:17
laga"is there some way we can help you with your own deb, stuff that makes18:17
lagathings easier for you?18:17
laga"18:17
lagafor the love of god - open source the damn thing or make it suck less.18:18
persiaCan Adobe craft a special link on their page that points at our flashplugin-nonfree?18:18
lagapersia: yes18:18
lagapersia: http://www.mythbuntu.org/existing-ubuntu18:18
persialaga: If you understand how, would you mind explaining it to Sebastian?18:18
lagawe do that for mythbuntu18:18
lagapersia: i'm not subscribed to ubuntu-motu, sorry.18:19
lagaapt:mythbuntu-desktop?section=universe <- but it looks straight forward18:19
persialaga: Well, you could send a reply there, and it would likely get approved in the moderation queue...18:20
lagaalright.18:21
persialaga: Thanks.  I thought it was possible, but really don't understand the mechanics.  As much as I'm not a fan of non-free, it might help resolve part of the whole "Cannot install flash" mess for quite a few people.18:22
lagainteresting. it doesn't work in kubuntu in firefox for me. might just be a fluke, though18:22
lagadone18:40
persialaga: Thanks a lot.18:48
xander21cHello :D18:57
xander21ci traying to do a merge i got all the tools but how do i choose a package?18:59
persiaxander21c: You're typically encouraged to merge packages for which you've previously applied the patch, and so are responsible for the deviation.19:01
persiaIf you have listed with your name on merges.ubuntu.com, you can look at others.19:01
persiaFirst, check to make sure there's no comment about it on dad.dunnewind.net, and no merge bug in launchpad.19:02
persiaThose conditions satisfied, it's considered nice to highlight the last uploader and tell them you are planning a merge, to avoid duplicated work.19:02
persiaMany people are busy with one thing or another, and would be happy to have your assistance with their merges.19:02
xander21cpersia for example  pidgin-libnotify has no comment in DaD so i email to the last uploader before merge19:18
persiaxander21c: Right.  This might take a bit.  Would you like something else to work on whilst you wait?19:19
xander21cactually yes, i am really newbie on this, so i hope my questions are not annoying19:21
persiaNot annoying at all.  Thanks for being intersted in helping.  It's merge season, so there's lots of talk about merges, but there's always plenty else to do as well.19:23
ScottKjdong: I mean if there are transitional packages that were dropped in Hardy, don't backport past Hardy our you end up with a mess.19:23
persiaxander21c: Two classes of stuff that might be good for someone starting would be package updates, or bugfixes.  For updates see https://wiki.ubuntu.com/PackagingGuide/Howtos/PackageUpdate and http://qa.ubuntuwire.com/uehs/19:25
persiaxander21c: For bugfixes see https://bugs.launchpad.net/ubuntu/+bugs and https;//wiki.ubuntu.com/MOTU/Contributing19:25
mok0__I need a fresh pair of eyes to take a look at my mesa package split, bug 22771219:27
ubottuLaunchpad bug 227712 in ubuntu "[needs-packaging] GLw libraries from Mesa" [Wishlist,In progress] https://launchpad.net/bugs/22771219:27
xander21cok :D19:30
xander21cpersia: will be back after careful reading19:31
mok0_i'm on the train... just went under a tunnel and lost connection :-)19:35
norsettomok0: about bug 227712, I'm not very clear of what you want to do. Are you using the mesa tarball to create a new source package and two new binary packages?19:57
ubottuLaunchpad bug 227712 in ubuntu "[needs-packaging] GLw libraries from Mesa" [Wishlist,In progress] https://launchpad.net/bugs/22771219:57
RoAkSoAxhi all.. i need some help here.. why a package... when trying to build the source will show this:20:19
RoAkSoAx fakeroot debian/rules clean20:19
RoAkSoAxdebian/rules:10: *** target file `clean' has both : and :: entries.  Stop.20:19
RoAkSoAxdpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit status 220:19
pochuRoAkSoAx: how's the line containing 'clean'?20:34
RoAkSoAxpochu, i figured out... the package in new debian version changed to CDBS so i removed the hole debian/rules and just left include /usr/share/cdbs/1/rules/debhelper.mk20:35
RoAkSoAxinclude /usr/share/cdbs/1/class/autotools.mk20:35
RoAkSoAx and the source build without any problems20:35
pochualright20:36
RoAkSoAxpochu, but now i got an error when building the binary20:37
pochupastebin it :)20:38
RoAkSoAxpochu, ok but first, i'm working with "atanks" (trying to merge it)20:39
RoAkSoAxMoM showed me conflicts in:20:39
RoAkSoAx  C* debian/atanks.desktop20:39
RoAkSoAx  C  debian/atanks.install20:39
RoAkSoAx  C  debian/rules20:39
RoAkSoAxatanks.desktop easy to fix aswell as atanks.install... but before checking out debian/rules i checked the changelod20:39
=== apachelogger is now known as radiologger
RoAkSoAxpochu, so changelog is this one: http://pastebin.ubuntu.com/10790/20:41
devfil_RoAkSoAx: http://bugs.edge.launchpad.net/ubuntu/+source/atanks/+bug/22741620:42
ubottuLaunchpad bug 227416 in atanks "Please sync atanks 2.9-1 (universe) from Debian unstable (main)." [Wishlist,Confirmed]20:42
RoAkSoAxi can see that now... well that bug already answered my question cuz i was thinking it was a sync.. that bug wasn't there yesterday... thanks devfil_20:43
devfil_RoAkSoAx: I did it yesterday, I didn't know that you wanted to work at the package... sorry20:44
pochuhey devfil_!20:44
RoAkSoAxdevfil_, nah it is ok, i'm just learning =)20:45
devfil_hi pochu :)20:45
devfil_RoAkSoAx: I'm learning  too20:45
RoAkSoAxdevfil_, and there are lots of packages to work with =)20:45
devfil_pochu: how are you?20:48
Arbyworking on a merge and the newer Debian version has older Build-Depends versions than the current ubuntu version, which should I use?20:52
Arbythis is the diff http://paste.ubuntu.com/10793/20:52
vorianthe new version20:53
RoAkSoAxArby, and change standards-version to the newer one20:53
Arbyvorian: the newer package or the newer build-depends20:54
vorianthe newer standards version20:55
vorianand versions in general in this kde package20:56
Arbystandards version I knew about, it was the build depends that had me confused20:56
geserArby: is it documented why the versioned Build-Depends are higher?20:56
geserin debian/changelog20:57
Arbynot that I've found yet20:57
Arbylooking back20:57
Arbyno, nothing in debian changelog20:58
ArbyI'll try the newer build depends and see if it builds20:58
wasabiAny policy information common for packages that provide software that should run as a particular user?21:01
wasabiAs in, how should you prompt the user for the account to use? Debconf?21:02
wasabiShould you offer to create a new system user if one does not exist? Etc.21:02
RoAkSoAxwhen doing a merge, whne we have this fields Vcs-Svn: and Vcs-Browser:, in debian/control, should we keep them in ubuntu?21:02
geserRoAkSoAx: yes, no need to remove them (and adding some extra diff for nothing)21:04
james_wgeser: I disagree21:04
RoAkSoAxgeser, what about the uploaders field?21:04
geserRoAkSoAx: the same, keep it21:04
RoAkSoAxok21:04
geserjames_w: why?21:04
RoAkSoAxthnks21:04
james_wif it's a merge then the repositories they point to won't contain the code in the distro, and so could cause confusion.21:04
james_wif a branch of the vcs is not used for Ubuntu then I would advocate deleting the headers.21:05
RoAkSoAxby the way, i'm trying to merge alsa-tools, noone working with that?21:05
RoAkSoAxjames_w, so these are the ones i was asking about:21:06
RoAkSoAxVcs-Svn: svn://svn.debian.org/pkg-alsa/trunk/alsa-tools21:06
RoAkSoAxVcs-Browser: http://svn.debian.org/wsvn/pkg-alsa/trunk/alsa-tools/21:06
ScottKjames_w: OTOH, if you're trying to feed fixes back to Debian, it's a useful bit of info.21:06
RoAkSoAxand: Uploaders: Jordi Mallach <jordi@debian.org>, Mikael Magnusson <mikma@users.sourceforge.net>, Elimar Riesebieter <riesebie@lxtec.de>21:06
ScottKjames_w: We aim for a minimal diff with Debian, so there's no need to remove either.21:06
james_wScottK: true, but an "Original-" prefix would allow that without causing the problems wouldn't it?21:06
ScottKjames_w: OK, but then what about the packages we don't touch?21:07
ScottKThe decision to modify maintainer we made after a poll of Debian Developers and required some time to get proper tool support for.21:07
ScottKI don't see those fields adding any actual harm.21:08
james_wScottK: for the packages that we don't touch the fields point to the source that we have in Ubuntu, so I don't see a problem there.21:08
ScottKjames_w: I'd see it as more needless diff.  Also more chance of a merge conflict needing more manual intervention with attended risk of messed up merges.21:08
ScottKUp until we need to do a security update and then they don't.21:09
ScottKAt that point we really need to do the minimal change.21:09
james_wthese headers aren't great anyway, so I doubt anyone really relies on them, but I don't think we should have bad information there.21:09
ScottKjames_w: It's not bad information.  It's a pointer to some revision history.21:10
ScottKThe canonical source for the package is still the source package.21:10
james_wyes, but not the revision history that Ubuntu has.21:10
ScottKI'd describe it as a portion of the revision history that Ubuntu has.21:11
james_wI'm not disagreeing with your other arguments, and I don't think this is the best place to discuss it.21:11
ScottKFor a package that's basically forked, I can see removing them.  For a temporary divergence, I don't see the need.21:11
ScottKOK.21:12
james_wIf I want to do something about it I will bring it up in a better forum.21:12
ScottKOK.  In the meantime, there's no policy to remove it, so people just learning shouldn't be told to remove it.21:12
ScottKjames_w: What would be a better forum?21:12
james_wScottK: the mailing list, or a MOTU meeting perhaps.21:12
ScottKMOTU meeting for a decision on a policy change, certainly.21:13
james_wsomewhere where we can get the input of other people, rather than just those that happen to be reading IRC now.21:13
RoAkSoAxok so should i remove those fileds or not?21:13
james_wRoAkSoAx: no, keep them, as that is the current status-quo.21:14
RoAkSoAxjames_w, ok thanks =)21:14
jimcooncathi, motu! I want to start a new project (small and simple at first). Is there anyplace I need to register the product's name with ubuntu or debian to reserve it?21:15
james_wjimcooncat: I don't think that's possible.21:17
jimcooncatOr do people just name their projects by checking google to see if anyone else has named theirs the same?21:17
james_wregistering the project on launchpad, sourceforge or similar places would perhaps discourage people from picking the same name.21:18
ScottKjimcooncat: Filing a Debian ITP bug and an Ubuntu needs-packaging bug would let people know about it, but there is no actual reservation system.21:18
jimcooncatthanks folks. you see any problem with a project called "loda"?21:18
jdaviesjimcooncat: google doesn't bring much up21:20
=== Czessi_ is now known as Czessi
pochudevfil_: I'm generally fine, thanks :) starting with sync and merges for Intrepid, and busy with uni. what about you?21:28
sebnerpochu: damn you :P21:28
devfil_pochu: I'm fine too, I know you are also helping emesene project, this is good21:29
slytherinjames_w: Vcs-Svn etc specify the VCS for packaging, right?21:32
RoAkSoAxhey guys... what about this warnings when building the source of alsa-tools: http://pastebin.ubuntu.com/10805/21:32
james_wslytherin: yes.21:33
james_wRoAkSoAx: ah yeah, crimsun is probably the most likely to want to merge alsa related stuff, so asking him whether he is working on it would be best.21:33
RoAkSoAxok thanks james_w =)21:34
slytherinjames_w: so those are going to be refered only be developers then why remove them?21:34
james_wbecause developers are people too?21:34
james_wRoAkSoAx: those warnings are probably ok.21:34
RoAkSoAxjames_w, ok so i'll build the binary, create the debdiff and talk to crimsun =)21:36
james_wRoAkSoAx: great.21:36
RoAkSoAxwhois ebner21:41
sebnerRoAkSoAx: hmm?21:41
RoAkSoAxsebner, :) you the llast one who merged athcool... can i give it a try or you working on it?21:42
sebnerRoAkSoAx: hmm. You could but I didn't touch it yet since a dependency isn't ready in intrepid yet. IIRC it's a sync though21:43
cbx33hey guys21:47
cbx33if I got this cc -shared -o ../libmltavformat.so factory.o producer_avformat.o consumer_avformat.o filter_avcolour_space.o filter_avresample.o filter_avdeinterlace.o -L/lib -lavformat -lavcodec -ltheora -lavutil -logg   -L../../framework -lavformat -lavcodec -lavutil -lavdevice  -lmlt -lswscale21:48
cbx33/usr/bin/ld: cannot find -lavdevice21:48
cbx33what would be the probable cause21:48
cbx33??21:48
wasabiUm. How do I exclude a file from conf file management? I'd like it to never replace with the built in version.21:48
RoAkSoAxsebner, so it would be better yo wait until the pciutils(>= 1:2.2.10) package is in the repos to sync?21:48
sebnerRoAkSoAx: totally right :)21:49
RoAkSoAxinstead of doing a merge21:49
sebnerRoAkSoAx: we *want* to reduce the delta/merges and increase the syncs ;)21:49
RoAkSoAxsebner, ok cool then... thanks for help =)21:50
sebnerRoAkSoAx: but if you want you can claim it in case you will process the sync request then21:50
james_wcbx33: hi. You need to Build-Depend on libavdevice-dev21:51
cbx33james_w: there is a script I'm using to build kdenlive21:52
james_whowever it appears that package is built by ffmpeg-free, which is not in Ubuntu yet.21:52
cbx33and it pulls in libavcodec fine21:52
cbx33and libavdevice is built21:52
cbx33but it's not pulling it in21:52
sebnerjames_w: though it seems that it will be there in a few days21:52
cbx33I'm just trying to get a usable kdenlive21:52
james_wcbx33: you're building libavdevice at the moment?21:52
james_wsorry, at the same time?21:53
cbx33no that's built21:53
cbx33yes21:53
cbx33the script builds that first21:53
james_wis it installed first?21:53
cbx33and that's all done21:53
cbx33yes21:53
cbx33now it's trying to build mlt21:53
james_wso you have /usr/lib/libavdevice.so?21:53
cbx33no it's in a seperate build dir21:53
cbx33and the script is set to use that21:54
cbx33apparently21:54
cbx33so if I add21:54
james_w../../framework/ ?21:54
cbx33no21:54
cbx33DEST_DIR/lib/21:54
cbx33so it's looking in the wrong place21:55
james_wah, there is "-L/lib"21:55
cbx33yes21:55
cbx33but it's still failing21:55
james_wwhich is odd, and seems to indicate that it is trying to do it, but $DEST_DIR is empty when this is expanded21:55
cbx33ahh ok21:55
cbx33hmmm21:56
cbx33maybe it's just not putting it in anywhere21:56
james_wcan you pastebin the script/makefile whatever that does this so I can see it?21:56
james_wor a pointer to where you got it from?21:56
cbx33http://pastebin.ca/101107521:56
cbx33i added  -I$DEST_DIR/include/  to line 28721:57
james_wcd ../mlt++; ./configure --prefix=$DEST_DIR --enable-debug21:59
cbx33and that fixed one bug21:59
james_wlines 323/32421:59
cbx33ignore mlt++21:59
cbx33we're still stuck at the one before21:59
cbx33:)21:59
james_wah, ok.21:59
cbx33hehe21:59
cbx33sorry21:59
cbx33see....where does it tell it to use DEST_DIR22:00
cbx33for the -L22:00
cbx33it doesn't22:00
cbx33does it22:00
Arbyon trying to build a binary I get this error, what does it mean?22:00
ArbyTrying patch debian/patches/kubuntu_01_fix_missing_output.diff at level 1 ... 0 ... 2 ... failure.22:00
Arbymake: *** [debian/stamp-patched] Error 122:00
james_wcbx33: --prefix=$DEST_DIR is probably supposed to do it.22:00
Arbyapart from obviously the patch has failed22:00
Arbywhat might cause it?22:00
cbx33yeh22:00
cbx33james_w: ecept it isn't22:00
cbx33:p22:00
james_wArby: it conflicts somehow with the new upstream code.22:01
james_wArby: do you know what patch system is in use?22:01
Arbylet me check22:01
Arbyjames_w: whatever cdbs uses (simple-patchsys?)22:02
Arbydebian/rules has include /usr/share/cdbs/1/rules/simple-patchsys.mk22:02
james_wArby: cool, in the unpacked sources try22:03
james_wcdbs-edit-patch kubuntu_01_fix_missing_output.diff22:03
james_wcbx33: I'm trying to find the upstream code.22:03
cbx33james_w: ok22:03
cbx33there is a downloader in there22:03
james_wcbx33: I've found it from that22:04
james_wthe mlt configure script is handwritten, it's not autotools22:04
cbx33ouch really22:04
cbx33that explains it then22:04
=== radiologger is now known as apachelogger
cbx33james_w: it's really annoying me22:06
cbx33if only the ubuntu pckages had been tested22:06
cbx33:p22:06
cbx33:(22:06
Arbyjames_w: output of cdbs-edit-patch http://paste.ubuntu.com/10811/22:06
Arbylooks like a problem with build-deps22:07
james_wcbx33: what subdir is it in when it fails.22:07
Arbyshould I follow through and try to answer the questions or is that likely to cause more problems22:08
james_wcbx33: also, can you pastebin your config.mak from the root of the mlt tree please?22:08
james_wArby: it seems as if the patch has been applied upstream.22:08
ScottKsommer: php-clamavlib uploaded to Intrepid.  Thank you for your contribution to Ubuntu.22:08
cbx33james_w: it ends up in ~/source/kdenlive322:08
james_wwhat you can do is answer "n"22:08
cbx33as that is what i put in for the source dir22:08
sommerScottK: party! thank you22:09
Arbyjames_w: what is it that tells you that22:09
Arbyoh I see it22:09
Arbynevermind22:09
cbx33james_w: http://pastebin.ca/101109422:09
james_wArby: and then if it asks to continue say yes, you can then check the .rej files to ensure that the code is applied, then "exit 1", and delete the patch22:09
cbx33james_w: brb22:10
james_wcbx33: there are several subdirs of mlt, in which is "factory.o producer_avformat.o consumer_avformat.o filter_avcolour_space.o filter_avresample.o filter_avdeinterlace.o" ?22:10
Arbyjames_w: output after continuing http://paste.ubuntu.com/10814/22:13
Arbywhere do .rej files live?22:13
ajmitchcbx33: hey22:15
Arbyjames_w: nevermind I think I figured it out22:16
* Arby writes down 'read the changelog better'22:16
james_wArby: heh, you on top of it now?22:18
=== Allan_ is now known as Hit3k
ArbyI think so, it had been applied upstream. just with a different name22:19
ArbyI'll remove the kubuntu patch and try to rebuild22:19
Arbythis may take some time22:19
james_wgood plan22:19
james_wcbx33: http://mlt.svn.sourceforge.net/viewvc/mlt/trunk/mlt/src/modules/avformat/Makefile?view=markup is probably where the problem is.22:21
cbx33hey ajmitch22:23
james_wcbx33: or http://mlt.svn.sourceforge.net/viewvc/mlt/trunk/mlt/src/modules/avformat/configure?view=markup22:23
cbx33can we hack a fix?22:23
james_wprobably, I can't see exactly what the problem is though.22:25
Arbyprogress, if a different error counts as progress22:25
Arby /tmp/buildd/kdevelop-3.5.1/./configure: line 38683: syntax error: unexpected end of file22:25
Arbybut the end of the configure file looks fine22:26
james_wArby: has one of the patches got "autotools" or similar in the name?22:26
cbx33james_w: what about changing -L22:26
james_wit's probably a quote missing somewhere, or something like that.22:26
cbx33yeh22:26
james_wcbx33: that would be the best way.22:26
Arbyjames_w: the complete set of pathces is http://paste.ubuntu.com/10816/22:27
Arby*patches even22:27
ArbyI did have to fix a conflict in the configure file, I really hope I didn't delete the wrong thing22:28
james_wArby: 03_libtool_update.diff and 04_am_maintainer_mode.diff look a little suspect22:28
james_wArby: that may well be it.22:28
RoAkSoAxwhat is the difference between debian/control and debian/control.stub ?22:28
james_walso, what is the update.sh file?22:28
Arbychecking22:29
james_wRoAkSoAx: debian/control will normally be generated from the latter in that case.22:29
RoAkSoAxjames_w, so should i drop .stub ?22:29
Arbyjames_w: it mentions autotools http://paste.ubuntu.com/10818/22:30
james_wRoAkSoAx: no, that's probably what you should be editing.22:30
james_wRoAkSoAx: check debian/rules, and look for mention of debian/control22:30
RoAkSoAxjames_w, ok thanks22:31
james_wArby: you could try running it, I'm not exactly sure what the purpose is.22:31
RoAkSoAxjames_w, it only has: #!/usr/bin/make -f22:31
RoAkSoAxinclude /usr/share/cdd-dev/rules22:31
james_wArby: I would also check that conflict you had in configure again.22:32
* Arby crosses everything and hopes22:32
RoAkSoAxand debian/control is much more elaborated than debian/control.stub22:32
Arbyok22:32
james_wRoAkSoAx: yep, if you are changing the maintainer, or Build-Depends you should edit debian/control.stub for cdd packages.22:32
james_wRoAkSoAx: which package is it out of interest?22:32
RoAkSoAxok thanks james_w22:32
RoAkSoAx=)22:32
RoAkSoAxfinally alsa-tools finished building the binary...  but it showed many warnings..22:35
james_wRoAkSoAx: is it debian-edu you are working on?22:36
RoAkSoAxjames_w, yes22:36
james_w(apart from alsa, obviously)22:36
RoAkSoAxjames_w, yes that's the one22:36
james_wRoAkSoAx: it doesn't need merging22:37
RoAkSoAxjames_w, so should i just report a sync bug?22:37
james_wit wasn't on my list of packages, as dholbach was the last uploader because I made a mistake.22:37
james_wRoAkSoAx: yes please.22:38
james_wthe changelog says that the changes can be dropped, all the other changes were just necessary things for the upload.22:38
RoAkSoAxjames_w, yeah i haven't got to that part yet, but thanks for the tip xD =)22:39
RoAkSoAxjames_w, so like this: requestsync -s debian-edu intrepid 0.83122:39
james_w0.82422:40
james_wyou specify the base version, not the current Debian version.22:40
RoAkSoAxjames_w, ok thanks, and what do i put in the Explanation of the sync, just that it needs to be synced?22:42
james_wyou can say that the change was made to build against an updated cdd-dev. There is a separate sync bug for cdd-dev, and syncing will still ensure that a new enough version of cdd-dev will be used.22:44
jcfpReviewers, please have a look at http://revu.tauware.de/details.py?package=sabnzbdplus22:45
RoAkSoAxjames_w, ook so i'll put there: "the change was made to build against an updated cdd-dev. There is a separate sync bug for cdd-dev, and syncing will still ensure that a new enough version of cdd-dev will be used."22:45
james_wRoAkSoAx: that should be sufficient.22:45
RoAkSoAxthanks very much james_w22:45
james_wno problem, thanks for taking care of it.22:46
tjaaltona package in hardy universe is currently uninstallable (vdr-plugin-burn, a missing package and falsely named dependancies). AIUI it would need two SRU's to fix the situation; first get the missing package in, and then fix the broken package dependancies. is this doable? the current situation is not a regression because v-p-b was introduced in hardy, but annoys me like hell22:48
tjaaltonmotu-sru members ^^22:49
RoAkSoAxjames_w, going back to alsa-tools... it showed lots of warnings while building the binaries.. but it build them successfully... any suggestion?22:50
james_wRoAkSoAx: what were the warnings?22:50
james_wRoAkSoAx: two suggestions. Firstly, look at the build logs for the current hardy package, you can see if there are warnings there.22:51
james_wSecondly, if you are building in Intrepid there are a bunch of new default CFLAGS that may be causing the issue.22:51
RoAkSoAxsome where about some char variable that was deprecated22:53
RoAkSoAxother was related to ${misc:Depends}. where can i find the whole log?22:54
james_whttp://launchpadlibrarian.net/12740476/buildlog_ubuntu-hardy-i386.alsa-tools_1.0.15-2ubuntu4_FULLYBUILT.txt.gz22:54
james_wthat's the hardy i386 one22:55
RoAkSoAxi had these same warning: ../pixmaps/alsalogo.xpm:451: warning: deprecated conversion from string constant to 'char*'22:55
the_belgainhi there - is there any chance anyone can review a package which I uploaded to REVU a few months back but didn't make it in for hardy?  It's fuppes, at: http://revu.tauware.de/details.py?package=fuppes22:56
cbx33james_w: do I hard code the -L you think?22:59
james_wcbx33: that will probably work for you22:59
james_wbut others may be interested in having it work properly22:59
cbx33yeh23:00
cbx33seems to have worked23:01
RoAkSoAxjames_w, where can i find the buildlogs in my own pc?23:01
james_wRoAkSoAx: they're probably not stored23:02
RoAkSoAxjames_w, oks so then how to compare?? i've seen some similar warnings in the i386 (but im using amd64)23:03
james_wRoAkSoAx: you can build again and redirect the build output to a file.23:04
james_wRoAkSoAx: you can grab an amd64 build log23:04
RoAkSoAxoh right lol haven't thought about it23:04
RoAkSoAxjames_w, before re building it i have to delete the binaries created in /var/cache/pbuilder/result right?23:05
RoAkSoAxor they will be overwritten ?23:06
james_wRoAkSoAx: nope, they'll just be overwritten.23:06
RoAkSoAxok so building againg23:09
RoAkSoAxjames_w, ok so after comparing the buildlogs... if there are the same warnings it will be ok??? but if there are new warnings.. what should be done?23:10
copprookay, I am going to try this question again?23:10
james_wRoAkSoAx: you should work out if they are serious.23:10
copproIf the upstream distribution doesn't include a SONAME, do I need to add one myself?23:10
RoAkSoAxjames_w, so if needed, make patches and stuff like that?23:11
james_wRoAkSoAx: in one sense if it builds and runs then it is "ok". However, warnings are there for a reason, and can often point to real problems that will bite users later.23:11
james_wcoppro: you mean Debian, or the upstream code released by the particular project?23:11
copprojames_w: I mean the upstream code. The default build for the library has no SONAME23:12
RoAkSoAxjames_w, ok cool... and seems there is no build log for alsa-tools amd6423:12
the_belgaindon't mean to pester, but just wanted to check whether this is the right place to ask to get a package reviewed for multiverse?23:12
the_belgaini've tried a few times but haven't had much luck...23:13
copprothis library has no Debian package23:13
james_wRoAkSoAx: on the left of https://edge.launchpad.net/ubuntu/hardy/+source/alsa-tools/1.0.15-2ubuntu423:14
james_wcoppro: ok, in most cases you want one, otherwise it is a headache23:14
RoAkSoAxthanks james_w =)23:14
james_whowever if upstream doesn't use one, then it would often indicate they weren't going to care about their ABI, and so using a soname would also be a headache. Do you think that applies in this case?23:15
copproI think so. They have a version number in the library anyway (kinda like libc6)23:15
james_wthe_belgain: yes, it would be. However, asking for a review doesn't mean you are always going to get one, so don't take silence the wrong way.23:15
james_wcoppro: why aren't they using a SONAME for that?23:16
coppropossibly because they are primarily Windows developers and don't know better?23:16
copproI could always use that number as the SONAME23:16
RoAkSoAxjames_w, as far as i can tell... there are the same warnings...23:17
james_wcoppro: but will they change that number in the way that is required for a SONAME?23:17
copproI believe so. I can ask23:18
james_wRoAkSoAx: it's probably ok. Just test the binaries well.23:18
the_belgainok.  i appreciate that time is limited, it's just that it seems like there's a few packages like this one which a lot of people are asking about installing in the forums etc. and i'd like to get packages for but it seems like actually getting things reviewed and committed seems pretty hard to actually manage23:18
copproor they may not :/23:18
james_wcoppro: it's probably worth asking, at the very least you will get to gauge their understanding of the issues.23:18
copproyeah23:19
copproin the meanwhile, is there a great guide for packaging libraries? I'm trying to find as many places as I can, as everyone says library packaging is difficult.23:19
james_wthe_belgain: yeah, it's unfortunate. Reviewing new packages is very time consuming, so it can be a slow process for contributors.23:19
james_wthe_belgain: also, intrepid is only just open, and most people can't even set up a development environment for it yet. In a couple of weeks I hope things will start to flow a little more smoothly.23:20
james_wcoppro: it's not necessarily difficult, but you have to be aware of the issues, and on top of the changes in the upstream code that could break the packaging.23:21
Arbyjames_w: you were right, there is some libtool strangeness occurring.23:21
james_wcoppro: have you seen the Debian libarary packaging guide?23:21
copprono, which is that?23:21
Arbythe readme for the update.sh script says http://paste.ubuntu.com/10825/23:21
the_belgaindo packages in REVU get updated for intrepid automatically (i.e. the distribution in the debian/control file etc) or does it need to be reuploaded?23:21
Arbyso I've run the script, which didn't throw any errors23:22
james_wcoppro: there's also https://wiki.ubuntu.com/MOTU/School/LibraryPackaging which is a fantastic introduction to the issues.23:22
Arbythen attemted to rebuild23:22
copproyeah, that's the one I was going to use23:22
Arbywhich fails with unexpected end of file immediately after configure: creating libtool23:23
james_wcoppro: I'm trying to turn that in to real documentation at https://wiki.ubuntu.com/PackagingGuide/SharedLibraries , but I haven't had the time recently.23:23
james_wcoppro: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html23:23
the_belgainand is there anything to do process-wise to get an uploaded package reviewed (eg. does the [needs-packaging] launchpad bug need to be assigned the MOTU team, or do MOTUs check through packages in REVU periodically)?23:23
james_wthe_belgain: it would need to be updated manuall.23:24
james_wthe_belgain: I believe it is just done through REVU23:24
the_belgainok, thanks23:24
=== coppro_ is now known as coppro
copprosorry, my computer just decided to randomly suspend itself23:26
james_wcoppro: did you get my links23:29
copproyeah23:29
copprothanks23:29
RoAkSoAxjames_w, is it ok to use a PPA to test the packages i build when merging??23:31
james_wRoAkSoAx: sure23:33
RoAkSoAxjames_w, and to test it, should i create a VM, install hardy, upgrade to intrepid and test it?23:38
james_wmmm, do you have a VM solution that provides a sound card?23:39
RoAkSoAxjames_w, i just have vmware installed23:39
james_wcan that do that?23:39
RoAkSoAxi don't know, but i'll try23:40

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