[02:24] ajmitch: Thank you for your comments. [05:24] wgrant: ubuntuwire FTBFS page hasn't updated in 4 hours === bulldog98_ is now known as bulldog98 [07:02] good morning [07:03] good morning === dholbach_ is now known as dholbach [09:19] huhm. debuild -S -sa does run lintian too … And when uploading to PPA I do want to avoid that for every. single. release. [09:19] dpkg-source -b on the other hand doesn't generate me a .changes file … [09:20] Also, when doing source packages for different releases, is there a way that it doesn't extract the orig.tar.bz2 every single time and clean it up afterwards? With wesnoth this is cumbersome i/o wise. %-/ [09:20] ah, --no-lintian for the first question === chrisccoulson_ is now known as chrisccoulson [09:34] *sigh* [09:34] $ debuild -S -sa --no-lintian [09:34] debuild: unknown dpkg-buildpackage/debuild option: --no-lintian [09:34] dpkg-buildpackage -rfakeroot -d -us -uc -S -sa --no-lintian [09:34] dpkg-buildpackage: unbekannte Option oder Argument --no-lintian [09:34] Why does man debuild document --no-lintian if that doesn't work?? [09:38] Rhonda: Does it need to be stated before dpkg-bp options? [09:45] arand: doesn't state so in the manpage, but I'll try [09:45] Rhonda: Hmm, didn't seem to work for me that or the initial way either... [09:45] it says debuild [debuild options] [dpkg-buildpackage options] [09:45] ahyes. accepted, but dput giving error [09:48] Hmm, rather, that flag didn't work with git-buildpackage, does with debuild though, as noted. [09:51] Rhonda: re cleaning: does -nc do what you want? [09:53] No. [09:54] A source build extracts the upstream source into a temporary directory, and afterwards deletes that again [09:54] -nc is about calling debian/rules clean, not about the temporary orig source extraction directory [09:56] ah for the creation of the diff.gz (or debian.tar.gz) probably [09:57] you could try to edit the release name in the .diff.gz (or debian.tar.gz) too and run only dpkg-genchanges -S afterwards [09:57] then I suppose the question is asking whether you can keep one unpacked copy of the orig.tar.whatever between source package builds [10:00] Laney: Exactly that, yes. [10:01] Uploading wesnoth-1.9_1.9.9-1~ppa1_source.changes: 550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['General error', 'General error', 'General error'] : Permission denied. [10:01] Is such an error message common these days? [10:01] I receive a mail that it was accepted nevertheless [10:01] Rhonda: yes [10:01] it tries to verify at dput time [10:01] but fails to do so [10:02] I see questions about this now and then, I assumed it got fixed by now but apparently not [10:05] It's not universal but not unheard of; somebody did explain to me what the problem was but it leaked out of my ears. Maybe a bug in the LP keyserver? [10:06] I remember something about communication issues between the ftp server (process) and the keyserver [10:06] does it only happen for ftp uploads? [10:06] I use SFTP which may explain why I've never seen it [10:07] I don't know if the sftp server does also this check or only the ftp one [10:12] uh, muscle memory [10:12] so used to bcc-ing control@bdo that I typed it instead of the mailing list I wanted to reply to (even after I said in the body that I was redirecting to said list) [10:23] I don't see the overhead need in sftp when the authorization and integrity is checked through the gpg signature. :) [10:25] Pending (2505) - is the 2505 the score or the queue place? === yofel_ is now known as yofel [10:32] the score [10:34] Is there a way to see the queue? :) [10:34] Or does the score raise over time? [10:38] https://help.launchpad.net/Packaging/BuildScores https://launchpad.net/builders [10:38] I don't know if you can see the details of the queue though [10:40] I don't know of a way to see the queue either (only to see which packages needs building but not the order) [10:41] * Rhonda is looking at https://launchpad.net/~rhonda/+archive/wesnoth-devel/+builds [10:50] I believe one of the points of sftp was that it let Launchpad know whom to spam with reject mail even if there's no GPG signature [10:50] and that it can be easier to get through firewalls [10:50] or NAT anyway [10:51] hrm [10:52] can I make debuild/dpkg-buildpackage use a separate build area like git-bp can do? [10:52] … and that ftp has to die. :) === Quintasan_ is now known as Quintasan === dholbach_ is now known as dholbach [12:05] hmm. I wonder how long a score of 2505 can take to do its job … === almaisan-away is now known as al-maisan [12:17] Rhonda: that sounds like a fairly neutral score for a package [12:18] there's a description of the scoring algorithm somewhere on help.launchpad.net I think [12:21] Laney handed me a link [13:05] ScottSanbar: was your query solved? Or do you need any assistance with recipes? === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan [14:25] duh [14:27] Seems like the i386 ppa buildds are more overworked than the amd64 ones [14:40] People, please don't upload to PPAs for a while, I want to have wesnoth-1.9 compiled on i386. Thanks for your cooperation! :) [14:44] heh === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === med_out is now known as medberry [19:10] uh oh [19:10] 1.9 GiB (96.66%) of 2.0 GiB [19:10] and all this because of a PPA of wesnoth-1.9 [19:10] Whom to talk to to potentially get some expansion? :) [19:11] #launchpad I guess [19:12] Rhonda: file a request on answers.launchpad.net/launchpad [19:13] hmm, 2 gig per PPA [19:13] So maybe I should just split it, but that wouldn't make sense for wesnoth-devel [19:14] … or drop some release [19:16] Rhonda: reasonable requests for more space are generally granted === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === medberry is now known as med_out === kentb is now known as kentb-out === Marce_ is now known as Marce