=== medberry is now known as med_out === kentb is now known as kentb-out [02:15] I'd like to help === ryanakca is now known as Guest66690 === almaisan-away is now known as al-maisan [06:03] oops, a better gnash snapshot was uploaded 10 days ago :(, I guess it's SRU time for it === al-maisan is now known as almaisan-away [07:04] good morning [07:05] mornin [07:09] morning [07:09] good evening ajmitch [07:12] so everything's ready for release now? :) [07:14] Debian RC bug list is huge :( [07:14] yeah, I didn't even take much of a look at it lately, I guess there could be plenty of chances for SRUs [07:15] there are probably for the previous releases as well :) [07:15] * ajmitch has to check the version tracking on that rc bugs list, first one I like at, the ubuntu version is below the found version for the debian bug [07:16] given how hacky it is, the bug list might be cut down a bit just by fixing that :) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [10:44] Hi!! :-) [10:44] I'd like to start working with the motu team [10:44] what could I do? [10:47] At this very moment, there's very little to because its release day tomorrow. [10:47] But there's a lot of stuff you could do [10:49] https://wiki.ubuntu.com/MOTU/Contributing is a good page [10:50] :-) Thank you nigelb :-) [10:51] ok [10:51] I looked at that [10:52] and I have a problem with pbuilder [10:52] Are you getting an erro fo some sort? [10:52] yes [10:53] this is the error: sudo pbuilder create --debootstrapopts --variant=buildd [10:53] sorry [10:53] this: "Someone else has lock over /var/cache/pbuilder/base.tgz.tmp, waiting" [10:53] and its loop [10:54] (sorry for my english, im italian) [10:54] I'm not an exxpert, maybe if you wait, someone will be able to help you [10:54] * nigelb pokes Laney, meanwhile [10:54] ok [10:54] thank you nigelb [10:54] np :) [10:54] :-) [11:07] someone could help me? [11:14] bah [11:19] Laney: problem? [11:19] he left [11:19] ah, the usual [11:19] * ajmitch has a different pbuilder problem with sid, is most annoying :) === almaisan-away is now known as al-maisan [11:27] right, done enough paid work for the evening, time to sleep === al-maisan is now known as almaisan-away === irssi is now known as robc === almaisan-away is now known as al-maisan === med_out is now known as medberry === al-maisan is now known as almaisan-away [16:45] Ciao [16:47] Hi!! :-) [16:47] Angelo: it helps if you stay here. Someone tried to reply to you, but you'd gone. I suggest leaving an irc client open, or using something like irccloud [16:48] Angelo: what's in your pbuilderrc ? [16:48] tumbleweed: ah... ok. Thank you [16:49] when I create the pbuilder there's a message that tells that someone else is locking the file [16:49] yes, you said. What's in your .pbuilderrc ? [16:49] I'm assuming you haven't set it up for multiple distros? [16:50] you can probably just delete /var/cache/pbuilder/base.tgz* [16:50] ah, sorry...ok [16:50] but before you create a new one, you may want to set it up, following https://wiki.ubuntu.com/PbuilderHowto [16:50] this line: COMPONENTS="main restricted universe multiverse" [16:50] (or just use pbuilder-dist) [16:51] no I didnt delete /var/cache/pbuilder/base.tgz [16:51] it's safe to [16:52] I followed that guide, but the error (sorry if I didnt tell u before) was about base.tgz.temp file [16:53] I was suggesting setting it up for multiple releases now, because otherwise you'll be creating new base images anyway, when you get there [16:53] Angelo: just try deleting that file [16:54] tumbleweed: ok. So I should delete only base.tgz.temp? [16:54] yes [16:54] (I'm just guessing, but it can't hurt to delete it) [16:54] and start again with pbuilder create? [16:55] ok! :-)) [16:55] It's what I thought, but I didnt know it [16:55] thank u!! [16:55] :-) [16:56] tumbleweed: and u speak italian right? :-)) [16:56] Angelo: very poorly, I'm afraid [16:56] tumbleweed: ahaha...ok [16:56] tumbleweed: I just saw your real name [16:57] * tumbleweed lies in ZA, never spent enough time in italy to pick up the language, but I can get around... [16:57] tumbleweed: so i'm deleting it [16:58] tumbleweed: I couldnt delete it [16:59] tumbleweed: access denied [17:00] sudo rm :) [17:01] tumbleweed: DONE! :-)) I didnt remember that. Im new with ubuntu :-) [17:01] tumbleweed: thank u :-) [17:01] np [17:02] tumbleweed: now is creating the file [17:02] tumbleweed: before I read what u write..... but I have a problem at home (maybe I will explain) and I disconnect for that reason [17:03] tumbleweed: what are u doing in ubuntu? [17:04] easy answer: my wiki page is mostly up to date https://wiki.ubuntu.com/StefanoRivera [17:05] tumbleweed: ok! [17:05] * jussi waves to tumbleweed and offers more salmiakki liquer :D [17:06] * tumbleweed guesses he'd better bring some amarula to UDS then [17:06] tumbleweed: unfortunately I wont be there... [17:06] so it goes :/ [17:06] tumbleweed: I have a good reason though :D [17:07] tumbleweed.. how does one get involved as you did? I'm also trying to get into python related [17:07] packages [17:07] pdtpatrick: you just start, and ask for help [17:08] find something that's bugging you, and fix it [17:08] "bugging me" :) [17:08] going to have to recreate my environment and keys .. upload and get started [17:08] if you just want to help out generally, each phase of the release has different areas that need attention [17:09] right now, it's probably a good idea to look for release critical bugs that were fixed in debian, but we missed the fixes for: http://qa.ubuntuwire.com/bugs/rcbugs/ [17:09] if any of those are serious enough, we can put out -updates fixes (SRUs) for them [17:09] well i'm currently a sysAdmin myself and do most things python/bash/django but wanted to help out and at the same time gain more experience with python along the way. [17:11] lots of ubuntu's infrastructure is written in python, many of the recent websites are django, so there are a few areas you could help out in [17:11] Okay .. going to read the getting started page and then proceed from there. Will ask questions here if i get lost somewhere [17:11] please do [17:12] tumbleweed: I read your page and launchpad too :-). Thank u [17:17] * tumbleweed heads off out to dinner [17:18] * Laney wibbles [17:18] tumbleweed: Hi! :-) [17:43] Hello [17:43] I noticed that there are a number of packages that fail to build on armel. [17:44] and this might be a newbie question but can you build armel packages on a i386 arch? Is there a way to do it? [17:56] I go for dinner [17:58] cdunlap: pbuilder-dist dist armel create [18:01] jtaylor: Thank You. I appreciate the information [18:11] where is the "get-build-deps" command in oneiric? [18:11] gone [18:11] sudo mk-build-deps -i -r === medberry is now known as med_out [18:14] thanks, Laney [18:35] I'm trying to hack a package together, but I'm getting this error: [18:35] dpkg-shlibdeps: [18:35] I mean, dpkg-shlibdeps: error: couldn't find library libgda-5.0.so.4 [18:35] But that library is built by the package itself. [18:35] $ find . -name "libgda-5.0.so.4" [18:35] ./debian/tmp/usr/lib/libgda-5.0.so.4 [18:35] ./libgda/.libs/libgda-5.0.so.4 [18:36] Presumably I have a typo somewhere, but I can't figure it out. [18:36] murrayc: did you check the SONAME with objdump? [18:37] also, is this more than one binary package, and if so, where is the binary that dpkg-shlibdeps complains about? [18:38] azeem: How would I use objdump to do that? [18:38] azeem: Well, here is the full error: [18:38] dpkg-shlibdeps: error: couldn't find library libgda-5.0.so.4 needed by debian/libgda-5.0-bin/usr/bin/gda-list-config-5.0 (ELF format: 'elf32-i386'; RPATH: '') [18:38] objdump -x ./debian/tmp/usr/lib/libgda-5.0.so.4 | grep SONAME [18:39] murrayc: probably debian/tmp isn't installed into any package, so it skips it [18:39] isn't there a debian/libgda-5.0/usr/lib/libgda-5.0.so.4 as well? [18:39] azeem: SONAME libgda-5.0.so.4 [18:40] ok [18:40] azeem: No [18:40] I guess there should indeed be. [18:40] murrayc: is libgda-5.0.so.4 getting shipped in any binary package then? [18:40] if not, that'd be enough reason for the error [18:40] Yes, it should be. [18:40] ok [18:41] more debian/libgda-5.0.install [18:41] usr/lib/libgda*.so.* [18:41] usr/lib/libgda*/providers/libgda-sqlite.so [18:41] usr/lib/libgda*/providers/libgda-web.so [18:41] Which I guess should take care of that. [18:41] yeah [18:41] I am just hacking the libgda-4.0 package to be a libgda-5.0 package. [18:43] murrayc: the library package is libgda-4.0-4 at least on Debian [18:43] so it should likely be libgda-5.0-4 as well [18:43] murrayc: check that debian/control actually references libgda-5.0 [18:44] (as a binary package) [18:44] Actually, there were some -1 mentions. I've removed them and I'll try again. [18:44] I assumed that I could just remove the -4. [18:44] regular library packages encode the sonmae [18:44] soname* [18:45] so libgda-5.0-4 would be correct [18:45] OK. Thanks. [18:45] it's unclear what the 5.0 is good for if binary compat hasn't changed but oh well [18:45] I'll try to add that back then. [18:45] azeem: Maybe upstream just forgot to reset the shared libary version. [18:45] the library name has changed [18:45] It's meant to be totallly parallel installable. [18:46] so you can restart the soversion [18:46] murrayc: that's what the 5.0 vs. 4.0 is good for I guess [18:46] just make sure the package name in debian/control and the debian/.* files match [18:46] for library only packages so soversion alone is enough [18:51] azeem: Thanks. Trying again after fixing that. I had no idea, as usual. [18:51] cheers [18:53] azeem: control is generated from control.in, and the -1 is only in the control. [18:53] azeem: So where does that -1 come from? [18:53] hrm [18:53] can you pastebin control.in? [18:53] azeem: In a moment, after I've checked something. [18:53] np, I'm looking at the old source package [18:53] should be enough [18:55] murrayc: debian/rules has "SONAME := 4" in the old package, did you change that? [18:55] debian/control should get generated from control.in by replacing @SONAME@ with $SONAME, i.e. 4 [18:56] azeem: Yes, I must have. [18:56] To 1 [18:57] I think it's best to change that back [18:57] OK [18:57] Trying again. It takes a while. [18:58] 4.0 is the API version? [18:59] 5.0 [18:59] Of course I'd rather that the experts packaged all the Glom dependencies, but in the meantime I'm trying to hack some packages together for the PPA. [18:59] so they broke API again? [19:00] 5.0 should be the upstream version, SOVERSION is 4 AFAICT [19:00] i.e. the number a fter the .so [19:00] Yes. 5.0 has been going for about a year now. Should hit stable in a few weeks. [19:00] so it should be libgda-5.0-5? [19:00] 20:32 < murrayc> ./libgda/.libs/libgda-5.0.so.4 [19:00] API = 5.0, major component of SONAME = 5 [19:00] but maybe they'll switch before release? [19:00] It doesn't have so many users so the break is not generally that annoying. It's just awkward to get the new packages into the distros. [19:01] so SONAME in rules should be 5 and you should rename any libgda-4.0 or libgda4 to be 5.0 or 5 [19:01] azeem: They can't reduce it because there were unstable tarball releases. [19:01] in control.in and all files in debian/, and all paths therein [19:01] right [19:01] Why should it have any relation to libgda-4.0 whatsoever? Why 5? [19:03] azeem: It builds! [19:03] azeem: Obvious stuff to you, I guess. [19:03] yay [19:04] erm, because they bumped the API version to 5.0? [19:04] and 5 is the SONAME [19:04] 20:36 < murrayc> azeem: SONAME libgda-5.0.so.4 [19:05] oh ok [19:05] 20:57 < azeem> but maybe they'll switch before release? [19:05] * Laney shrugs [19:05] carry on [19:06] Laney: Thanks anyway === chrisccoulson_ is now known as chrisccoulson === med_out is now known as medberry === yofel_ is now known as yofel [20:08] hello! === bulldog98_ is now known as bulldog98 [20:25] I have a problem with dget, someone would help me? [20:26] Angelo: no need to ask to ask a question, just ask it - state the problem [20:26] ahah.. ok [20:27] This is the error that I have had running dget: turpial_1.5.0~rc1-1~natty1.dsc: dscverify: turpial_1.5.0~rc1-1~natty1.dsc failed signature check: gpg: non sono stati trovati dati OpenPGP validi. gpg: processing message failed: eof Validation FAILED!! [20:28] you don't have the key of the developer who uploaded that package. That's normal, we don't provide a keyring of all the developers public keys [20:28] quite impossible in ubuntu as a different key could be used for each upload and discarded [20:29] (the part in italian means that the system didnt found valid OpenPGP data) [20:29] you can get the key yourself, and verify that you trust it, or download the soruce with apt-get source / pull-lp-source [20:29] ah, ok.... [20:29] (or just trust that it wasn't tampered with, that's the easy answer) [20:32] so what should i do to use dget? I never used a key for that [20:32] I registered 2 keys on launchpad [20:32] but never used [20:34] dget is verifying the signature on the source package that you are downloading. It was signed by the person who uploaded it [20:34] if you don't care about validating every signature, use the -u option to dget [20:36] ah ok..... thank you! [20:36] And then there are the packages on LP that don't have a signature at all. [20:37] and do u use verifying the signature usually? (sorry for my english :-) ) [20:48] Now I go [20:48] see u tomorrow! [20:48] tumbleweed: thank you for your help [20:49] micahg: thank u too [20:50] ajmitch: I used the option and it seems it worked. thanks [20:50] bye!! [20:50] :-) [21:34] hey how are things going? [21:34] hi highvoltage [21:34] howdy ajmitch [21:39] once you have submitted the package to REVU, does the package still needs to be marked as "In progress" ? [21:42] hi highvoltage [21:42] shayonj: https://wiki.ubuntu.com/Bugs/Status [21:45] tumbleweed, ah, missed the page.thanks :) [21:47] shayonj: we strongly recommend getting new packages into Debian if possible, and letting them flow into Ubuntu that way [21:48] tumbleweed, oh i see. So is it fine if i upload to Debian after i did to REVU ? [21:48] i mean from next time onwards i will take care of that, but what about the one i already did ? [21:50] shayonj: not many people look at REVU. You can probably get it into Debian before anyone has even commented on it on REVU [21:50] tumbleweed, sounds good. thanks :) [21:51] but it can't hurt to put a comment saying what you've done [21:53] yes, that would probably be sensible :) [21:54] hah, definitely [21:55] phew, i remembered to update [21:55] in before release rush === medberry is now known as med_out