/srv/irclogs.ubuntu.com/2013/10/01/#launchpad.txt

pkgmanwgrant: I have an odd source package rejection problem. Can you help?00:22
wgrantpkgman: Have you tried using debsign directly, or passing additional signing options to debuild?00:23
pkgmanI take it you read my e-mail then? I couldn't find any examples for using a passphrase file and suppressing gpg-agent via either of those.00:24
wgrantYou can't just use an alternate GNUPGHOME?00:25
pkgmanWould that allow passing through a passphrase file?00:26
wgrantOr use a gpg wrapper script and use debuild -p<wrapper>00:28
pkgmanI can't find a -p option in the manpage for debuild. What does it do?00:29
pkgmanOr is that the debsign option? That looks plausible.00:30
pkgmanI'll try that tomorrow. But I'm still curious as to what a dpkg-source return value of 9 means and why the package gets rejected.00:31
pkgmanI followed the documented behavior of debsign, or so I thought, and a diff of the dsc and changes files showed no differences aside from checksums and signatures.00:32
wgrantpkgman: debuild passes most of its options down to dpkg-buildpackage.00:33
wgrantWhich in turn inherits a number of options from debsign, though they're explicitly documented in dpkg-buildpackage's manpage.00:33
cjwatsonpkgman: Launchpad just runs "dpkg-source -sn -x foo.dsc" (on a lucid system, currently); nothing particularly exotic00:41
pkgmanSo, if dpkg-source is running, the changes file has already been validated?00:42
cjwatsonYes00:42
cjwatsonPut the uploaded source somewhere and perhaps we can look at it00:43
pkgmanCan you access a rejected dput upload from today?00:43
wgrantNo, they're deleted.00:44
pkgmanOkay. I'll put the stuff on 4shared right now.00:44
cjwatsonWe can see the logs, but they're (curiously) unhelpful.00:44
cjwatson(FWIW, I would have answered you earlier if you'd stuck around; I was taking the kids to the park when you first asked.)00:48
pkgmancjwatson: No worries. I work odd hours anyway.00:59
pkgmanI'm back.01:34
pkgmanwgrant: Do you have time to look at my source bundle, or should I wait for cjwatson?01:41
_bjfStevenK, about? if i wanted to create and run my own version of qastaging is it possible? are the instructions at https://dev.launchpad.net/Running enough or is there more to it?01:56
=== _bjf is now known as bjf
StevenKbjf: Why do you want to do that?02:07
bjfStevenK, i hate life and want to abuse myself02:07
StevenKHaha02:07
bjfwell, i have a love/hate relationship with qastaging02:08
bjfi love it when it's there and bitch when it goes down02:08
StevenKbjf: I would suggest you use lpsetup instead -- that means you can confine LP to its own LXC container02:09
bjfStevenK, interesting ... will look at that. can i populate it with a reasonable amount of the data (teams/projects/etc.)?02:10
bjfStevenK, meaining, real teams/projects/etc. from LP data02:10
StevenKbjf: That's a much harder question.02:11
StevenKbjf: qastaging tends to mostly hang around, staging will disappear over the weekend as it restores its database02:13
bjfStevenK, ack, i use it regularly. however, there have been a time or 3 that it's been borked for a week or more02:13
bjfStevenK, it's also slooooww02:14
bjf(or seems that way to me)02:14
StevenKbjf: Yeah, it will be slow :-)02:15
StevenKbjf: However, it shouldn't be dead for a week or more, we tend to use it for QA and notice when it's dead/misbehaving02:16
bjfStevenK, yeah, i know, but there really were a time or two ... anyway i had to ask. sounds like it's a pita to populate my own02:18
bjfStevenK, i have a  good sized system in the Boston DC that i was thinking of using for this02:18
StevenKbjf: LP is fairly heavyweight -- our prod DB servers have 128GiB of RAM02:23
bjfStevenK, http://kernel.ubuntu.com/testing/test-results/statler.html02:24
bjfStevenK, i'm assuming qastaging is a lesser system02:25
StevenKbjf: qas is spread amogst four machines02:26
bjfStevenK, ah, thought that might be the case02:26
bjfStevenK, somewhat related question, has anyone run qas or something similar on an openstack cluster ?02:27
wgrantbjf: qastaging and staging should rarely be down for more than 24 hours, and never both for more than an hour. We had some unfortunate incidents last week where staging was down for 3 days, but that's the first time in a long while, and qastaging was fine during that.02:33
wgrantNeither has been down for more than 3 days in several years.02:33
bjfwgrant, can you refresh my memory. i forgot all about staging. what's the basic diff. between the two? if you were me doing LP dev (creating/modifying) bugs which would you use?02:35
wgrantbjf: They're pretty similar from an end-user PoV. staging's DB tends to be reset more frequently (every Saturday, unless something goes wrong), but qastaging is moving to a similar schedule.02:37
=== zenitraM^away is now known as zenitraM
=== zenitraM is now known as zenitraM^away
=== zenitraM^away is now known as zenitraM
=== zenitraM is now known as zenitraM^away
=== zenitraM^away is now known as zenitraM
=== zenitraM is now known as zenitraM^away
hlamerHi. Maybe somebody is able to explain, what is the problem with this build: https://launchpadlibrarian.net/152013500/buildlog_ubuntu-raring-i386.python-qutepart_1.1.0-1~raring1_FAILEDTOBUILD.txt.gz ?09:30
cjwatsonhlamer: The builder is broken.  Could you provide the https://launchpad.net/.../+build/... link rather than the buildlog?09:31
cjwatsonActually maybe I can find it ...09:32
cjwatsonYeah, chindi0409:32
cjwatsonhlamer: I'll deal with it, thanks09:32
hlamercjwatson: https://launchpad.net/~hlamer/+archive/enki/+build/506488609:33
cjwatsonRetried, should be happier on the next builder.  chindi04 is disabled and will be rebuilt09:34
cjwatsonI'll retry the other failures too09:34
hlamerOk, thanks!09:34
cjwatson(done)09:38
czajkowskicjwatson: we'd be lost without you09:47
=== zenitraM^away is now known as zenitraM
=== matsubara is now known as matsubara-lunch
scranenHi, I got a bit stuck trying to upload stuff to a ppa. We uploaded a new version (let's say from v1 to v2) some time ago, found out there were some horrible mistakes in the packaging procedure and deleted the packages. In the meantime the packaging has been fixed, and we'd like to again submit a new version, going from v1 to v2. Now I'm getting upload errors because product_v2.orig.tar.gz already exists. This is not a file I had15:21
scranenAdvice?15:21
=== matsubara-lunch is now known as matsubara
=== zenitraM is now known as zenitraM^away
=== zenitraMz is now known as zenitraM
=== jml- is now known as jml
=== revilo-freenode is now known as DangerDevil
=== rpadovani is now known as WebbyIT
=== Kyle_ is now known as Kyle
=== tsimpson_ is now known as tsimpson
=== jml__ is now known as jml
=== elmo__ is now known as elmo
=== davmor2_ is now known as davmor2
Waka_Flockawhy is my branch empty? lp:~wakaflocka/midori/enhancements21:06
dobeyWaka_Flocka: you haven't pushed anything to it?21:09
Waka_Flockahow do i push?21:10
dobeyand it's not empty21:10
Waka_Flockaah never mind21:10
Waka_Flockait says "Working tree "/home/jacolby/midori/" has uncommitted changes (See bzr status). Uncommitted changes will not be pushed.21:11
Waka_Flocka"21:11
dobeywell yes, you can't push changes that haven't been committed21:11
Waka_Flockaoh how can i commit, i am a complete starter at this21:11
dobeyyou should probably read the bzr tutorials/documentation then21:12
dobeyit doesn't really have anything to do with launchpad directly, aside from the fact that you're hosting code on it21:13
=== Corey_ is now known as Corey
=== Nigel_ is now known as G

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