[01:25] Anyone willing to sponsor an upload? bug #339449 [01:25] Launchpad bug 339449 in mit-scheme "FeatureFreezeException: Merge mit-scheme with Debian" [High,Confirmed] https://launchpad.net/bugs/339449 === bluesmoke is now known as Amaranth === fabrice_sp__ is now known as fabrice_sp [04:53] jcastro: happy bday ( its midnight mytime, not sure about yours ) [04:53] :) === bluesmoke is now known as Amaranth [05:23] in debian/copyright, I have the standard gpl v2 blurb, but I have some files that are strictly v2, can I freely remove the part that says "or (at your option) any later version. " [05:23] the standard blurb i'm talking about is similar to http://bazaar.launchpad.net/~mythbuntu/mythexport/intrepid/annotate/head%3A/debian//copyright [05:24] tgm4883, If you have sources with two different licenses (and GPLv2 is different than GPLv2+), then it's best practice to identify them, and have two paragraphs. [05:25] If all your source is the same, just use the same text as in the source files. [05:25] persia, right, and I am separating them. I just need to know if I can just remove that part for the files that are strictly v2, or if there is a different blurb I should be using [05:25] You should *always* use the blurb in the source files. [05:25] Don't use "standard" blurbs, except when upstream did. [05:27] I'm trying to write a script that puts the operations dch, debuild, and dput into single command. How can I pull the latest version from debian/changelog, without a bunch of other stuff? [05:27] Note that when dealing with licenses with addresses, and you *know* the address is no longer current, updating that is fine, but otherwise, stick with upstream. [05:28] ripps, I don't think you want to do it that way, but dpkg-parsechangelog is probably what you want. [05:28] persia, ok, in the files, the only thing they say is "# Released under the terms of the GNU GPL v2" [05:28] which I was under the impression that I had to add the short license to debian/copyright [05:29] OK. You've found an exceptional case. [05:29] well I am exceptional ;) [05:29] I recommend bugging upstream, because they are *supposed* to put in the blurb. Bugging by way of a patch attached to an enhancement request is best practice. [05:30] ok, and the short term? [05:30] That said, yes, drop the "or (at your option) any later version." text. [05:30] ok [05:30] What's the easiest way of managing multiple packages with multiple backports? [05:30] I can't promise the archive-admins won't complain, but it's the closest you'll get to being right for now. [05:30] heh, well, they are complaining with how it is right now ;) [05:31] thats what i'm trying to fix [05:31] The source files are *not* properly licensed, in my opinion. I recommend checking with the archive admin to make sure you're meeting their requirements before pushing it again. [05:32] ok, will do [05:32] thanks persia [05:33] tgm4883, Also, it's worth remembering that regardless of the contents of debian/copyright, the orig.tar.gz must be suitable for redistribution on it's own. === asac_ is now known as asac === fabrice_sp__ is now known as fabrice_sp [06:45] Does anyone know why I'm getting: 'Could not find compatible GRE between version 1.9.0.1 and 1.9.0.*.' when I run firefox? [06:47] Doh [06:47] * iulian hasn't finished upgrading. [06:50] good morning [06:55] * wgrant notes that we are ~ half way through the obvious part of the universe Python 2.6 transition. [07:15] G'morning dholbach! [07:15] hiya iulian [07:17] How is it going? [07:18] very good - how are you doing? [07:18] I know I can't make the alpha release, but can someone upload bug #339449 so it's in the queue? [07:18] Launchpad bug 339449 in mit-scheme "FeatureFreezeException: Merge mit-scheme with Debian" [High,Confirmed] https://launchpad.net/bugs/339449 [07:20] dholbach: I'm doing my calculus homework right now and looking at my irssi window. :-) [07:21] good luck with that :) [07:22] Dude - IM + homework !!= productivity [07:22] Hehe [07:22] Seriously - it just doesn't work. Context switches are expensive [07:58] fabrice_sp__: looks like im-sdk is still FTBFSing (it built fine for me in pbuilder though :-/) [07:58] I'll be back in a bit, just letting you know [08:34] hi! any one willing to review my package here? http://revu.ubuntuwire.com/details.py?package=mbpurple === azeem_ is now known as azeem [08:57] good morning everybody === oojah_ is now known as oojah [10:10] If a motu has some time to review my package at http://revu.ubuntuwire.com/details.py?package=sqliteman ... [10:41] hello, I want to open a bug about moving scilab to univesre because it is now free. is there a wiki or something about how to request? [10:43] c_korn: have you solved the FTBFS problem? [10:43] slytherin: yes, it is already in jaunty. but in multiverse [10:44] c_korn: just file a bug report, explaining what changed and that you want to move it to universe and subscribe ubuntu-universe-sponsors - somebody will review, ACK and subscribe ubuntu-archive later [10:45] c_korn: I asked you if you solved the FTBFS problem. [10:46] slytherin: it only failed to build because there were empty translation files in the package. I removed them in clean target. [10:47] seems like it FTBFS in a couple of other places still: https://launchpad.net/ubuntu/jaunty/+source/scilab/5.1-0ubuntu2 [10:48] oh, that you mean :P I filed a bug in the scilab bug tracker. sylvestre wants to look at it. [10:48] at least powerpc and ia64 should build then [10:48] the other archs fail for some other reasons [10:48] missing dependencies [10:49] ah ok [10:49] openjdk-6-jdk: Depends: openjdk-6-jre (>= 6b14-1.4.1-0ubuntu2) but it is not going to be installed [10:49] java shonk [10:49] on SOME arches anyway [10:50] checking to see if we can link a JNI application... no [10:50] configure: error: could not link file that includes jni.h [10:50] on others [10:50] generally, java suckitude's to blame one way or another [10:52] is this sufficient? https://bugs.launchpad.net/baltix/+bug/340413 [10:52] Ubuntu bug 340413 in baltix "move scilab-5.1 from multiverse to universe" [Undecided,New] [10:53] c_korn: why did you file it in baltix? [10:53] slytherin: was a mistake [10:53] https://bugs.launchpad.net/scilab/+bug/340413 [10:53] Ubuntu bug 340413 in baltix "move scilab-5.1 from multiverse to universe" [Undecided,New] [10:54] should I mark the baltix one as invalid? [10:55] should I list all packages that have to be moved? [10:58] c_korn: have you checked if all build-dependencies and runtime-dependencies for all binary packages are in main/universe? [10:59] and the bug should be better against the scilab package in ubuntu and not the scilab project [11:08] * Change pastebinit's default behavior to reading from stdin (Thanks fta) [11:08] * pochu hugs stgraber :-) [11:08] * pochu hugs fta too ;) [11:11] geser: https://bugs.launchpad.net/scilab/+bug/340413/comments/1 I checked all dependencies [11:11] Ubuntu bug 340413 in baltix "move scilab-5.1 from multiverse to universe" [Undecided,New] [11:11] they are fine [11:17] pochu: works ? [11:18] pochu: that should be a "no new feature but everything's fixed" release, a bit last minute for Jaunty but we couldn't keep the one we had in so ... [11:19] stgraber: didn't update yet... shouldn't it? [11:19] stgraber: you're a good upstream for that! :) [11:24] even the translations seem to work (except one string as it's been added yesterday and isn't translated on LP yet) [11:41] jcfp: I need your python 2.5 wizardry. How did you manage to get rid of the << 2.6 dep on sab? I've a similar problem with another package... [11:42] Laney: it had to do with trying to provide a public module without supporting the default python version [11:43] which apparently isn't allowed unless the package name is something like pythonX.Y-modulename [11:43] guh [11:44] In case of sab, solution was to make the module private [11:45] might work, thanks [12:04] siretart: thanks! [12:16] hi folks [12:29] Hi sistpoty|work. [12:29] hi ScottK [13:00] savvas: hy! [13:00] savvas: so what should i do in order to help out with the python packages update to 2.6 (i think) [13:08] cristi: you mean the python 2.6 transition? [13:08] geser: yes [13:09] cristi: have you read the mail on ubuntu-devel what needs to be changed in the packaging of a package? [13:09] geser: i am just getting started, i am still reading articles on the wiki. however i was told that it's not that hard to contribute to the python 2.6 transition [13:10] geser: so the answer is no [13:10] cristi: it's really easy [13:10] (in most cases) [13:10] what is really easy lol [13:11] the python transcription i guess, ok can you help me out so i can start doing something [13:11] cristi: https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027528.html [13:12] the next step is then picking a package which needs a transition [13:13] btw: have you already a jaunty pbuilder? [13:14] geser: yes, i got it last night and took a look at introductive stuff [13:14] good as it makes the test building easier [13:20] ffmpeg did a release?! :O [13:21] what what? [13:21] ffmpeg, the "change everything every week" app? [13:21] http://svn.ffmpeg.org/ffmpeg/branches/0.5/RELEASE?revision=17805 [13:21] crazy [13:28] And the world didn't end!? [13:29] The release name is all kinds of ironic [13:33] what kind of policy is this "we have made a release but we only accept bugs against svn trunk"? [13:33] slytherin, it's more liberal than their usual policy of "trunk or gtfo" [13:34] * slytherin will be back in 10-15 minutes. [13:35] directhex, i like the trunk or gtfo [13:35] it works therefor its good [14:00] Heya gang [14:00] Hi bddebian [14:00] Hi geser [14:05] <__iron> hi [14:13] <__iron> isnt a new pidgin-version avaible in 8.10 ? [14:14] __iron: afaik it's being worked on [14:15] <__iron> k thx geser [14:21] would any motu kindly review my package? Thanks in advance! http://revu.ubuntuwire.com/p/lmalinux [14:25] hi guys [14:30] Laney: and guess what, that release is already in debian unstable since *last week* [14:33] uhm i had the hardy version of pbuilder (or at least i think), and i run sudo pbuilder update --distribution interpid --override-config. however, after trying to build a package i am getting this (error i think?) http://pastebin.com/m30804dd7 [14:33] can anyone tell me what should i do? this is my first package [14:34] cristi, not enough output to be helpful [14:34] cristi: can you paste complete error? The part you pasted is not much usefull [14:34] yes, one moment [14:34] i see now that the problem is a bit deeper [14:35] http://pastebin.com/m13e8dfee [14:36] cristi: sudo [14:37] no wait, there's more [14:37] no no, i think i overpasted [14:37] i used sudo [14:37] 2nd time [14:37] cristi: have you enabled universe section in your config? because libstatgrab-dev is in universe [14:38] blah i guess not, can you tell me how to do that, or give me a link..? [14:39] --components [14:39] cristi: are you using a ~/.pbuilderrc? If not, it is better to copy /etc/pbuilderrc to ~/.pbuilderrc and modify that file. [14:40] cristi: sudo pbuilder update --override-config --components "main universe" [14:41] hyperair: i am getting hardy release packages :-s [14:41] oh [14:41] --distribution intrepid then [14:42] i guess i should give an output [14:43] * hyperair nods [14:44] http://pastebin.com/m53074083 [14:44] intrepid not interpid [14:45] lol omg [14:45] lol [14:45] i didn't want to say anything... :/ [14:46] lol [14:46] >_< [14:47] what the hell -> Someone else has lock over /var/cache/pbuilder/base.tgz.tmp, waiting [14:47] cristi: this is the reason I asked you to use separate pbuilderrc [14:48] slytherin: i did separate [14:48] copied to ~/ [14:48] ok, so now what should i do [14:49] cristi: did you name the file .pbuilderrc? [14:49] yes [14:49] however, it's all i did [14:49] just copied it [14:49] cristi: did you change the distribution and components in that file? [14:50] no [14:50] after that you need to do pbuilder --update --override-config [14:51] #COMPONENTS="main restricted universe multiverse" // i should just uncomment the line ? [14:54] cristi: it depends on what all components you want. If you want all of them then uncomment it. [14:54] i am still getting -> Someone else has lock over /var/cache/pbuilder/base.tgz.tmp, waiting [14:56] slytherin: so, now what should i do? [14:57] slytherin: does it matter, if you're on a single-user system? [14:57] cristi: break the lock. don't ask me where it is though [14:59] hello, is this move request sufficient? or do I miss something? https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/340413 [14:59] Ubuntu bug 340413 in baltix "move scilab-5.1 from multiverse to universe" [Undecided,Invalid] [15:00] hyperair: does what matter? [15:00] hyperair: this is not really working [15:01] i don't know what is causing the lock. [15:02] slytherin: having a separate .pbuilderrc. personally i have a bunch of scripts which maintain different pbuilder base.tgz, each of different releases. i've never touched a pbuilderrc before [15:02] cristi: maybe another pbuilder is running? [15:02] or maybe the previous run of pbuilder didn't close cleanly [15:02] hyperair: i have only one terminal session open [15:02] hm [15:03] hyperair: i can start over reinstalling pbuilder i guess ? [15:03] no. [15:03] no need. [15:03] ok [15:03] i mean it won't do anything [15:03] hmmm [15:03] just delete /var/cache/pbuilder [15:03] hyperair: I have punch of pbuilderrc each corresponding to a different pbuilder chroot. :-) [15:04] slytherin: command line options ftw =p [15:04] cristi: don't delete /var/cache/pbuilder. It will also delete your base.tgz. [15:04] slytherin: that's the point. it can be regenerated [15:04] slytherin: ok, i didn't delete it [15:05] slytherin: was really close to though xD [15:05] i don't know, when things get messy like this, sometimes it would be faster to just start over, don't you think? [15:05] cristi: delete that .tmp file instead. [15:06] hyperair: provided you have fast internet connection. [15:06] ok [15:06] now? [15:06] slytherin: debootstrap takes at most 15 minutes on my desktop, and that's with 512kbps [15:06] hyperair: 512 is fast. [15:06] slytherin: you sure? [15:06] it maxes out at 50 kB/s [15:07] hyperair: yes. In the places I live, you either get fast speed or unlimited data transfer. Not both. [15:07] slytherin: ouch. [15:07] slytherin: i've got 512kbps, unlimited data transfer [15:08] slytherin: which part of the world are you from anyway [15:08] hyperair: India [15:08] i see. [15:08] your ISP sucks =( [15:09] and i thought malaysian ISPs were bad [15:09] slytherin: uh i deleted the .tmp file, now i just run again sudo pbuilder --update --override-config ? [15:09] cristi: yeah [15:10] slytherin: ok, finally done [15:11] slytherin: thank's a lot! :D [15:11] cristi: welcome [15:58] anyone willing to answer a migration to python 2.6 question?? any takers? :) [15:59] ara: just ask, and if someone knows the answer he'll tell you :) [15:59] although I guess you already know this [15:59] :D [16:00] well, the thing is that if in jaunty now you do 'apt-get source ldtp' and try to build it, it will fail [16:00] the problem is that it does not use distutils [16:00] What's the error? [16:00] so I don't know how to fix it [16:01] dh_install -i --sourcedir=debian/tmp [16:01] dh_install: python-ldtp missing files (usr/lib/python2.5/site-packages/*.py), aborting [16:01] it does not find it, because it places them under /tmp instead [16:01] (debian/tmp) [16:03] ara: what are the contents of your .install file? [16:04] usr/lib/python2.5/site-packages/*.py [16:04] usr/lib/python2.5/site-packages/ldtplib/*.py [16:04] You'll have to change it to python2.6/dist-packages*. [16:05] ara: Change it to usr/lib/python*/*-packages/*.py [16:05] I already tried that [16:05] you guys are fast [16:05] I already tried that :) [16:05] ara: Tried which? [16:05] hi all [16:05] I changed it to usr/lib/python*/dist-packages/*.py [16:05] it didn't work [16:05] ara: can you do `ls debian/tmp/usr/lib/` when the build fails? [16:05] hi rainct, persia, thekorn. pedro_ [16:06] ara: That's not what I suggested. [16:06] and Laney [16:06] :) [16:06] ScottK, yes I am going to try it now [16:06] anakron: you're on a waving spree! [16:06] :-) [16:06] Also if the issue is related to overall path, like /tmp/debian versus /tmp, that's unrelated to the new Python. [16:07] ScottK: i tried your suggestion and it didn't work either [16:07] OK. What error then? [16:08] ScottK: smae [16:08] ScottK: same [16:09] ara: Can you pastbin the actual build failure message and your debian/rules? [16:09] ScottK, pochu: these are the contents of debian/tmp after the failure: http://paste.ubuntu.com/129373/ [16:10] ScottK: it is the current package, without changes: if you do "apt-get source ldtp" you will have it all [16:10] OK === bdrung_ is now known as bdrung [16:11] ara: it's installing things in /ldtplib rather than /usr/lib/python*/*packages :) [16:11] pochu: not really [16:12] pochu: it used to install things under /usr/lib/python*/*packages/ldtplib and /usr/lib/python*/*packages, and now it has lost that structure [16:12] pochu: again, I didn't change anything on the packaging [16:12] pochu: so I thought it might be something related to the python migratoin [16:13] ara: sure. I mean, right now it tried to install things in / ;) [16:13] or at least that's what your pastebin shows [16:14] * ScottK is going to try building it and see. [16:14] pochu: but I already saw that :) [16:15] pochu: thanks anyway, I will keep trying [16:31] geser: thanks for sponsoring it! :) and sorry for the typo ("LP" instead of "LP:") [16:36] hm.. that's nice, debian bugs are now successfully tracked through launchpad :) [16:45] ara: Change python-ldtp.install to *.py [16:46] It at least builds. [16:46] You'd have to see if the binary has all the right files in it. [16:49] ScottK: it is an upstream bug. i am talking with upstream now, thanks! [16:50] ara: Excellent. [17:00] Is there a command that outputs "i386" or "amd64" depending on the architecture? [17:02] arch isn't available unfortunately [17:04] savvas: uname, but it returns other values than just i386/amd64 [17:04] uname -m ? I'll see what I can do with it, thanks :) [17:04] and I'm not sure if it shows the architecture you are running one or that one for the kernel.. :P [17:04] oh :p [17:05] cristi: you asked to help for python transition? [17:05] savvas: yes, but geser helped me a lot [17:05] savvas: I'm using it in pbuilder-dist, os.uname()[4].replace('x86_64', 'amd64').replace('i586', 'i386').replace('i686', 'i386') [17:06] for bash, uname -m | should do the same [17:06] dpkg-architecture -qDEB_HOST_ARCH [17:06] cristi: ah ok:) Since you also mentioned you're a beginner, I would suggest to start looking for bugs with "bitesize" tags: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bitesize [17:07] pochu: now that's more like it :P thanks! :) [17:07] pochu: uhmm nice [17:07] pochu: does it return i386 for i686 kernels as well? [17:08] Also, dpkg --print-architecture [17:08] savvas: they seem a bit difficult, i don't know. I tried to repair the xsensors package but i couldn't figure it out >_<. uhm and most bugs are taken for the ubuntu version [17:08] savvas: no idea, see dpkg-architecture(1) :) [17:08] hm, cool [17:09] dpkg --print-architecture definitely returns the string you expect to find in .deb file names. [17:09] savvas: and no, because I have a 686 kernel and it return 386 :) [17:09] Which is probably the same as DEB_HOST_ARCH [17:09] s/386/i386/ [17:10] does someone know how often popcon.ubuntu.com is updated (the data, not the website :))? [17:10] savvas: can i have your opinion apout a pbuild build error? [17:12] cristi: sure, but don't forget that I'm a beginner as well, not a motu :) === x-spec-t is now known as Spec [17:13] savvas: lol i thought you were a motu. however you surely know more about packaging than me so http://pastebin.com/m376c52b9 [17:13] pochu, maxb: just what I needed, awesome!! thanks :) [17:14] cristi: I think --install-layout is for python 2.6 [17:14] error: option --install-layout not recognized [17:14] savvas: is there really a problem with debian/rules ? [17:14] savvas: oh [17:15] cristi: try to substitute "for py in python2.4 python2.5" with "for py in python2.6 python2.5" [17:16] I think jaunty's python2.5 might well accept --install-layout as a no-op [17:16] cristi: is your pbuilder for jaunty release? [17:16] savvas: yes [17:17] savvas: i don't know where to substitute that [17:17] savvas: "for py in python2.4 python2.5" with "for py in python2.6 python2.5" [17:17] cristi: cool then :) - it's in the file debian/rules :) [17:17] savvas: >_< [17:18] cristi: found it? [17:18] savvas: one moment [17:18] maxb: right, I forgot :P [17:18] savvas: i can't find that phrase [17:20] i have a --install-layout=deb , it's what i added to rules [17:20] brb [17:22] cristi: can you paste the debian/rules file on pastebin? [17:22] savvas: sure [17:22] savvas: http://pastebin.com/m19039cb8 [17:23] cristi: can you paste debian/control as well? :) [17:24] cristi: and debian/pyversions as well, I forgot :) [17:24] savvas: http://pastebin.com/m630c5e16 [17:25] savvas: no pyversions [17:25] savvas: only pycompat [17:25] ah true [17:25] ok [17:26] so the log says "for py in python2.4 python2.5" [17:26] in debian/rules you have something similar: for py in $(PYVERS) [17:26] savvas: That's the expansion of what's in rules [17:26] PYVERS is a variable in that file [17:27] savvas: ok, so what should i do? [17:27] cristi: if you look at the top of the rules file it says: PYVERS:=$(shell pyversions -r) [17:27] also in the log it says: # [17:27] pyversions: missing XS-Python-Version in control file, fall back to debian/pyversions [17:27] pyversions: missing debian/pyversions file, fall back to supported versions [17:27] # [17:28] Which should work OK even if it's not preferred. [17:28] savvas: ah so i should change PYVERS to what? [17:28] ScottK: so XS-Python-Version isn't necessary at all? [17:28] note that i don't have intrepid, but 8.04 [17:29] cristi: if pbuilder is jaunty, it's fine :) [17:29] It's supposed to be there, but the fallback should work. [17:29] savvas: it is [17:29] ScottK: so why doesn't it? [17:29] Good questions. [17:29] ok cristi in debian/control under "Standards-Version: 3.7.2" try putting in a new line: XS-Python-Version: all [17:30] savvas: aha, ok [17:31] cristi: by the way, when did you last update pbuilder? [17:31] should i add these changes when running dch -i? [17:31] cristi and savvas: From the build log you're building against Intrepid, not Jaunty [17:31] savvas: i installed it today [17:31] That's the problem. [17:32] ScottK: uhm, so i should have a Jaunty pbuilder? [17:32] ah, I missed that :P [17:32] Look at the version of python2.5 that's installed and then rmadison python2.5 [17:32] ScottK: i have no idea how to do that [17:33] savvas: Would you please help cristi get her pbuilder to be Jaunty. [17:33] ScottK: his! xD omg [17:33] cristi: to remove the pbuilder you already have try this: sudo rm /var/cache/pbuilder/base.tgz [17:33] savvas: can't i just upgrade? [17:34] heya there. I'm looking for a way to build a pxe-bootable image with xserver, gtk etc... I don't know where to start so I thought it'd be best to ask the masters of the universe ;) [17:34] cristi: it's easier to start clean :) [17:34] cristi: You can, but you'll end up with a slightly different configuration and it will take as long if not longer. [17:35] sudo pbuilder --create --debootstrapopts --distribution jaunty --components "main restricted universe multiverse" [17:35] cristi: Every day isn't like this. The first day is the hardest. [17:35] savvas ScottK: ok, so i'll start over deleting === jorge__ is now known as jcastro [17:35] ScottK: hope so [17:35] cristi: this is the command to create a new pbuilder ^ [17:35] savvas: done [17:36] savvas: You might also consider recommending pbuilder-dist for new people. It's generally simpler. [17:36] savvas: oh w8 ok [17:36] ScottK: never heard about it :) I'll try it :P [17:36] savvas: It's in ubuntu-dev-tools [17:36] The equivalent is pbuilder-dist jaunty create [17:37] savvas: damn, i get an error [17:37] Or you can symlink pbuilder-jaunty to it and do pbuilder-jaunty create. [17:37] cristi: what does it say? [17:37] savvas: http://pastebin.com/m54799feb [17:39] cristi: let's try with pbuilder-dist, install this: sudo apt-get install ubuntu-dev-tools [17:39] savvas: i have them [17:39] great! execute: sudo pbuilder-dist jaunty create [17:40] still not [17:40] savvas: http://pastebin.com/m2e854888 [17:41] give me a sec [17:42] pochu, you're welcome (pastebinit stdin) [17:42] * fta hugs pochu back [17:43] cristi try: sudo pbuilder-dist jaunty create --mirror "http://archive.ubuntu.com" [17:44] savvas: it;s basically the same error [17:44] argh [17:44] give me a sec [17:44] savvas: [: 195: /home/cristi/pbuilder/jaunty-amd64_result: unexpected operator [17:44]