=== RAOF_ is now known as RAOF === thumper_laptop is now known as thumper === jelmer is now known as Guest4379 === Guest4379 is now known as jelmer [10:10] I have a strange PPA build FTBFS issue. Uploaded a version of audacity with libsoundtouch enabled. to enable that to work, I also built a new soundtouch package from upstream 1.3.1 (to satisfy the audacity depends). soundtouch built successfully. audacity builds successfully for lpia and amd64 but fails for i386. In a local pbuilder the i386 succeeds. [10:11] The failure is with a #include of one of the soundtouch include headers in /usr/include/soundtouch - but all three arch's have it installed [10:16] URL of the build log? [10:17] http://launchpadlibrarian.net/18012508/buildlog_ubuntu-hardy-i386.audacity_1.3.4-1.1ubuntu2~ppa1h_FAILEDTOBUILD.txt.gz [10:17] and the amd64 for comparison: [10:17] http://launchpadlibrarian.net/18012525/buildlog_ubuntu-hardy-lpia.audacity_1.3.4-1.1ubuntu2~ppa1h_FULLYBUILT.txt.gz [10:17] soory, lpia! [10:18] I checked the log to be sure the soundtouch 1.3.1 dev package was installed, and that the audacity configure script detects the system libraries as it should [10:24] IntuitiveNipple: compare also the contents of libsoundtouch1-dev on amd64 and i386 [10:24] geser: of the .debs you mean? [10:25] IntuitiveNipple: yes, the amd64 one has usr/include/soundtouch/st_assert.h, the i386 hasn't that file (I didn't check lpia yet) [10:26] geser: really!? I checked them locally and they were okay, which would explain why it builds locally. How the heck did it manage to miss that I wonder? [10:28] IntuitiveNipple: http://launchpadlibrarian.net/18010432/buildlog_ubuntu-hardy-i386.soundtouch_1.3.1-0ubuntu1~ppa1h_FULLYBUILT.txt.gz and see the package contents at the end of the log [10:28] geser: yeah I noticed that... now to work out *how* that happened! [10:29] somehow a patch must have failed, just i386 [10:37] well this has me truly flummoxed! [10:59] Hi, where to request for a certain Series to be deleted, if it was accidentally created? [11:22] pro-rsoft|idle: open a question against the launchpad project, specifying the project/series you wish removed. [11:23] okay [11:43] Hi [11:44] Does/Will launchpadlib allow to download PO files from rosetta? === pro-rsoft|idle is now known as pro-rsoft|lunch === nebi is now known as nebi|away === nebi|away is now known as nebi === nebi is now known as nebi|away === nebi|away is now known as nebi [16:57] Hello guys! I am still unable to build packages in PPA. There is an error (new one) in the log file. Please, can anyone help? Thanks! Log is located here - http://launchpadlibrarian.net/17982008/buildlog_ubuntu-intrepid-i386.thinkingrock_2.0.1-0ubuntu5_FAILEDTOBUILD.txt.gz [17:03] salutis: don't use the build target (which is run as non-root) to install files, a better place is the binary target [17:04] geser: aha [17:05] geser: I will try! [17:05] salutis: can you point me to your PPA? so I can look at the package [17:06] geser: deb http://ppa.launchpad.net/salutis/ubuntu hardy main [17:06] deb-src http://ppa.launchpad.net/salutis/ubuntu hardy main [17:12] salutis: after checking your debian/rules, it would be a good idea if you looked again at the packaging guide (https://wiki.ubuntu.com/PackagingGuide/Complete) escpecially the section about debian/rules (and the example there) [17:13] it might save you several upload iterations before it finally builds [17:15] geser: you're right. because there's no compilation I changed 'build' to 'binary' [17:15] geser: I will try and check [17:18] salutis: if you don't have a build, you can have a empty build target, but everything which needs "root" like installing files, changing ownership, etc. needs to be run from the binary target [17:23] geser: thank you for your help! it saved me lot of time. I am trying to fix my packages right now [17:27] I got error by e-mail from no_reply@lanuchpad.net: 'Rejected: Unhandled exception processing upload: 'ascii' codec can't encode character u'\u010d' in position 75: ordinal not in range(128)' :( [17:29] does it also give a traceback? [17:31] LarstiQ: no, I received only e-mail [17:32] LarstiQ: I don't know about trackback [17:32] salutis, what were you trying to upload? [17:32] Ursinha: salutis-connect (1.2.5) [17:33] oh, your package [17:33] let me see if there is an already reported bug [17:33] Ursinha: yes [17:35] Ursinha: FYI - the package is lintian checked, without errors or warnings [17:36] salutis, i guess the error you got is unrelated to package problems [17:37] u'\u010d' is č [17:38] salutis: which I guess may be in your name? [17:38] salutis: do you have the .dsc file available somewhere? [17:42] LarstiQ: here - http://www.salutis.sk/salutis-connect_1.2.5.dsc [17:45] salutis: okay, no problem there. [17:45] salutis: could there be any other place in the package that uses a č, the changelog maybe? [17:46] salutis: I see your user page features it [17:48] salutis: did the reject email mention anything else? [17:48] LarstiQ: grep -R 'č' * gives me only 'salutis-connect.sh: _AUTHOR_NAME_="Rudolf Adamkovič - Salutis"'. so, it's only in main script [17:49] salutis: then I think it's a launchpad bug [17:49] LarstiQ: in the e-mail, there are is only 1 line with mentioned error and then some generic information like 'format', 'date', 'source', 'binary', 'architecture' etc... [17:49] LarstiQ, it is indeed [17:50] :( [17:50] Ursinha: without the code or such, I suspect it's trying to use salutis' display name somewhere and not taking into account some unicode issues? [17:51] LarstiQ, launchpad has known issues with some unicode chars [17:51] LarstiQ, all on queue to be fixed [17:51] Ursinha: cool [17:51] at least all we know :) [17:52] so, I can remove 'č' from my profile name and it should work? I want upload packages ASAP :-/ [17:52] :) [17:52] salutis: that would be my recommended try at a workaround, yes [17:52] salutis, you can try that [17:52] perfect guys, I am very happy from your help! and sorry for my buggy english :) [17:54] salutis: thinkingrock looks interesting, just this week I've been reading David Allen's book, so I'll surely check it out [17:56] salutis, no problem :) you can come here every time you need [17:57] salutis, can you just tell me if changing the char on the script will be enough to workaround it? [17:57] Ursinha: yes, of course. wait a second [17:57] salutis, thanks >:) [17:57] oops [17:58] s/>// [18:00] Ursinha: it's working, package is accepted [18:02] salutis, thanks for checking it for me [18:02] and for reporting it [18:03] thanks guys! [18:04] salutis: pleased to help :) [18:05] salutis, no worries :) [18:08] salutis, one more thing if possible :) can you send me one PM or email with the error mail you've received? [18:12] Ursinha: yes, of course. I will [18:12] salutis, thanks! if you prefer email, you can send it to ursinha@canonical.com [18:15] Ursinha: It's in PM here at ICQ. it is O.K.? [18:16] it's ok, i'm receiving it [18:16] ICQ? how come? [18:17] Ursinha: no, no - I mean IRC, of course :) [18:17] oh :D [18:19] salutis, may i attach that info to the bug i'm filing? [18:21] Ursinha: of course [18:22] salutis, thanks [18:27] guys, how long it take to delete packages from PPA? I deleted my packages 5 mins ago and I still can't upload new ones (Rejected: File <...> already exists in PPA for Rudolf Adamkovic, but uploaded version has different contents) [20:12] This morning I had a package build on PPA for gutsy, hardy, and intrepid (i386, amd64, lpia). The hardy i386 package somehow missed out installed *one* (development header) file into the -dev package. The i386 builds for gutsy and intrepid included the file, as did local pbuilder hardy i386 test builds. I've just bumped the changelog version and re-uploaded the package and now the file is included. Because I can't explain the issue based o [20:12] n the packaging itself I'm wondering if it *might* be some kind of random glitch on the buildds. I thought it might be a good idea to at least put the issue on the radar in case similar things happen again for others. [20:13] The package in my PPA is soundtouch (1.3.1-0ubuntu1~ppa1h) hardy - note, it successfully built but another package that Build-Depends on it FTBFS the i386 hardy version only [20:15] (the file is "usr/include/soundtouch/st_assert.h" and it is created by debian/patches/00_assert.patch) [20:23] how long it takes to delete packages from PPA? I deleted my packages aprox. 1 hour ago and I still can't upload new ones (Rejected: File <...> already exists in PPA for Rudolf Adamkovic, but uploaded version has different contents). please help! [20:28] sorry, there was a network error. if there was any answers to my question, please post it again. thanks! === mwhudson_ is now known as mwhudson [21:50] is it possible to add a new bug tracker for a project when it's not in the registered tracker list? [21:50] fta, I think you have to request for it to get added [21:51] beuno, how? a bug? [21:51] you can file a question in https://answers.launchpad.net/launchpad [21:51] ok, thanks [22:56] hello [22:56] how can i create a new release to add files to? launchpad is so confusing :( [22:56] Stavros, you have to create a release from a series [22:56] (it is confusing, we're working on it) [22:56] so, go to a series (or create a new one) [22:57] and you can create a release from it [22:57] ah, "register a release"? thanks [22:57] that's it! [22:57] np [22:57] how long until the non-confusing version arrives? :/ [22:57] I wish I knew. But it's on the top of the list, so it can't be too long [22:57] ah, great [22:59] i hate how i try to find something and keep going round and round in cycles [22:59] yeah, we all do [23:00] we're working on making the UI much easier to use [23:00] that's great, because now the functions are all over the place [23:00] for example, i wanted to add a new download, there should be an "add file" in the downloads page [23:00] so you will see many improvements land [23:00] where i can select from the series or add a new one [23:00] i hope so, because i love the service [23:00] it's really useful (when i can use it) :P [23:00] Stavros, when you find something confusing, please, file a bug for it, or add a comment to an existing one [23:01] it helps a lot to know what we should be focusing on [23:01] ah, great, i'll do that now [23:01] anyway, I'm off to do sunday stuff [23:02] oh, it's sunday [23:02] okay, thanks again