[01:21] <ubotu> New bug: #215448 in malone "Should strip gpg signatures for attachments" [Undecided,New] https://launchpad.net/bugs/215448
[01:21] <RAOF> Ooo, yeah.
[01:57] <mtaylor> kiko: hey... how do I keep a package in a PPA from building for lpia? 
[01:57] <mtaylor> kiko: I've got one with mono depends which don't seem to be in gutsy for lpia, and I'd love to mark it as "don't bother"
[01:58] <cprov-out> mtaylor: restrict the control file Architecture field
[01:58] <mtaylor> cprov-out: isn't that just for the binary packages? 
[01:59] <mtaylor> or the binary sections, rather? 
[02:00] <cprov-out> mtaylor: well, it controls in which architecture you want to build a given binary package, if instead of 'any' you specify 'i386 amd64' it won't build in lpia
[02:00] <mtaylor> cprov-out: right... but I'm erroring out in missing build depends... 
[02:01] <mtaylor> so I'm trying to prevent it from even loading up a vm and starting...
[02:02] <cprov-out> mtaylor: sorry, I don't understand what you mean. loading where ?
[02:02] <mtaylor> a PPA
[02:02] <mtaylor> in a PPA
[02:02] <mtaylor> cprov-out: so, I upload the source package for gutsy
[02:03] <mtaylor> and it tries to build it against i386 amd64 and lpia, but I konw that the lpia build is going to fail for gutsy - and that it's going to fail in the build-dep step
[02:03] <mtaylor> and I don't really care about that - so I'd like to just skip it
[02:03] <kiko> mtaylor, what cprov-out said -- update the control file to not build it on that arch.
[02:04] <mtaylor> do I need to do the architecture field of all of the binary sections?
[02:04] <cprov-out> mtaylor: okay, so far ... upload a new source that won't build in lpia, change the Architecture in the control file as I've suggested.
[02:04] <kiko> yes -- one for each binary, mt
[02:04] <kiko> mtaylor, 
[02:04] <mtaylor> ok
[02:05] <kiko-zzz> cprov-out, now -- to to bed. :)
[02:05]  * kiko-zzz goes too
[02:05] <cprov-out> mtaylor: s/any/i386 amd64 (leave the 'all' alone)
[02:05] <cprov-out> kiko-zzz: not yet, I have a review to reply, but g'night :)
[02:06] <mtaylor> sweet. thanks guys
[02:58] <YokoZar> My emails to ubuntu-devel are still getting put in the moderation queue despite me being in the Ubuntu Developer group.  Do I have to use a specific address, or can I use any of my confirmed launchpad emails?
[02:58] <YokoZar> Or is it because I have to sign my emails?
[03:00] <jamesh> YokoZar: ubuntu-devel is not managed by launchpad
[03:01] <jamesh> so you need to subscribe any emails you want to post as at https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[03:01] <YokoZar> jamesh: I was hoping someone would know how the scripts interact, because it somehow uses the ubuntu devel group as a validation
[03:02] <jamesh> which scripts are you referring to?
[03:02] <YokoZar> Or maybe I'm mistaken and new Ubuntu devs have to be manually added to the mailing list by the admin
[03:03] <YokoZar> I just assumed there was some sort of "ask launchpad if this email is an ubuntu dev, if not put in moderation queue" type script going on
[03:03] <jamesh> you need to subscribe to the mailing list yourself
[03:03] <jamesh> see the URL I posted above
[03:03] <YokoZar> I'm already subscribed though, since before I was a dev
[03:03] <YokoZar> I'll try removing/redoing it, maybe that'll refresh it
[03:04] <jamesh> YokoZar: we do have mailing list support in Launchpad now, but the existing Ubuntu mailing lists haven't been migrated to that infrastructure
[03:04] <jamesh> that will likely happen in the future
[03:04] <YokoZar> Thanks
[03:04] <jamesh> once that's done, you'll be able to post with any email registered to your LP account, and you'll only get first post moderation once for all lists
[03:04] <jamesh> rather than once for each list
[03:05] <jamesh> (in cases where you aren't a list member, that is)
[03:14] <YokoZar> I think I figured out the problem - I registered a long time ago with an address that now forwards to my current one; since I was sending from my new  address, it thought me not a subscriber
[03:14] <YokoZar> Thanks for your help :)
[03:19] <jamesh> YokoZar: you can subscribe multiple addresses to the list, and set them as no email if you want
[03:19] <jamesh> that way you can post from multiple addresses but receive email on only one
[04:08] <emgent> good night people
[07:19] <jtv> mdke: ping
[07:19] <mdke> jtv: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back)
[07:30] <carlos> morning
[08:00] <mpt> Gooooooooooooooooooood morning Launchpadders!
[08:04] <jml> morning. pshaw.
[08:04] <jml> mpt: changing hemispheres has you all topsy turvy!
[08:05] <jml> next thing you know, you'll be saying that the sun rises in the west and eggs should be cracked with a fork!
[08:05] <mpt> Eggs should be cracked with a frying pan.
[08:08] <mdke> morning all
[08:09]  * mdke winces at mention of eggs
[08:09] <mdke> jtv: pong; saw your email, and am pretty excited :)
[08:09] <mdke> sounds awesome
[08:12] <AnAnt> Hello
[08:12] <AnAnt> a question about SVN imports
[08:13] <AnAnt> does that mean that I should continue using the SVN or the BZR ?
[08:13] <AnAnt> because I see a status called "last sync"
[08:13] <thumper> AnAnt: it depends
[08:13] <AnAnt> thumper: depends on what ?
[08:14] <thumper> AnAnt: if you are switching to bzr then just start using bzr
[08:14] <thumper> AnAnt: if you want to keep committing to svn then don't
[08:16] <AnAnt> sorry, I was lagging
[08:17] <AnAnt> thumper: depends on what ?
[08:17] <thumper> [19:14] <thumper> AnAnt: if you are switching to bzr then just start using bzr
[08:17] <thumper> [19:14] <thumper> AnAnt: if you want to keep committing to svn then don't
[08:18] <AnAnt> thumper: ok, I see that the bzr is in ~vcs.imports/ how do I change that to be in my team dir ?
[08:18] <thumper> AnAnt: branch from it and push to LP
[08:18] <jtv> mdke: cool, just let me know what you need.
[08:19] <AnAnt> thumper: you mean: bzr branch http://<~vcs.imports URL> , then bzr push svn+ssh://<my team url> ?
[08:20] <mdke> jtv: basically I have been importing po files into the ubuntu-doc branch, and correcting some of them by amending a string and the po-revision-date. I've got a list of them in a file called broken_translations in the branch and need to upload those po files to LP at ubuntu/hardy/+source/ubuntu-docs/templates
[08:20] <thumper> AnAnt: if you are using a recent bzr (1.2 or later) then use 'bzr launchpad-login' to identify yourself
[08:21] <thumper> AnAnt: then you can go 'bzr branch lp:~vcs-imports/project/name
[08:21] <thumper> AnAnt: and 'bzr push lp:~team/project/name'
[08:21] <thumper> AnAnt: somewhat smaller
[08:21] <AnAnt> ok
[08:21] <thumper> I'm looking to change the ui shortly (RSN)
[08:23] <AnAnt> how do I tell bzr about my account ?
[08:23] <AnAnt> I get: No Launchpad user ID configured.
[08:25] <AnAnt> thumper: how do I tell bzr about my account ?
[08:26] <mdke> AnAnt: did you see the bit about "bzr launchpad-login"
[08:26] <jtv> mdke: argh, the scripts don't support sourcepackage uploads yet.  Never mind.  Have a URL to that broken_translations file for me?
[08:26] <AnAnt> ah, bzr launchpad-login <username>
[08:27]  * mpt gets enraged by "There is 1 error"
[08:27] <mpt> I fixed the error, but Launchpad keeps unfixing it
[08:28] <mdke> jtv: hang on a tic. (to be honest, I don't really know why we use LP source package translations rather than project translations, it's all a bit confused)
[08:29] <jtv> mdke: saves an import step, I guess.  Shortens your feedback cycle.
[08:30] <mdke> jtv: can LP import translations automatically from a bzr branch yet?
[08:30] <mdke> or is that not feasible?
[08:33] <jtv> mdke: that's still a long way off.
[08:33] <AnAnt> thanks fellows !
[08:34] <mdke> jtv: ah. anyway, we don't really use the automatic import stuff; since all our translations come from LP anyway
[08:35] <mdke> it's no big deal to upload pot files
[08:35] <jtv> mdke: the file you're digging up links to the updated PO files, right?
[08:35] <mdke> jtv: not really, it just lists them. what do you mean by links?
[08:36] <jtv> mdke: just so I can unambiguously find the right ones.
[08:36] <mdke> jtv: yes, that will be ok. I'm just waiting for a commit to go through
[08:36] <jtv> ok
[08:37] <mdke> jtv: but at the moment I haven't finished correcting all the translations, it would just be to show you how things are set up, for now. I expect that all the translations will be fixed by the weekend
[08:38] <jtv> mdke: okay, if you send them to me now I can start scripting.
[08:41] <jtv> mdke: the problem was that you don't have upload privileges, right?
[08:41] <jtv> mdke: going for a post-lunch walk first though.  :-)
[08:43] <mdke> jtv: yes; I had upload privileges for some languages but not others
[08:43] <mdke> damn this commit is taking a long time
[08:47] <mdke> jtv: ok, my commit hasn't finished and I need to go to work, so i'll just tell you. In the https://code.edge.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy branch, it is at ubuntu/broken_translations, and the templates referred to are all at ubuntu/$templatename
[08:47] <mdke> jtv: (except for one, serverguide, which is at generic/serverguide)
[08:48] <mdke> jtv: for the next release I've simplified the branch structure a lot so it is more straightforward
[08:48] <jtv> mdke: ok, thanks.
[08:48] <mdke> jtv: the broken translations file has some asterisks in it, which are just for my benefit so  can see which translations I fixed already; I'll take them out when everything is fixed
[08:49] <mdke> jtv: thanks to you :)
[08:50] <jtv> mdke: as I like to say, thank me when it's done. :-)
[08:50] <mdke> i will :D
[08:50] <mdke> bye
[08:50] <jtv> bye
[08:51] <ubotu> New bug: #215537 in malone "Correcting unknown package by choosing "I don't know" gives further mysterious error" [Undecided,New] https://launchpad.net/bugs/215537
[08:52] <Fujitsu> Hm, I think that's a dupe.
[08:54] <Fujitsu> Indeed, bug #189522.
[08:54] <ubotu> Launchpad bug 189522 in malone ""I don't know" refused when reporting a bug" [Undecided,Incomplete] https://launchpad.net/bugs/189522
[08:54] <Fujitsu> mpt: You even replied to that bug yourself.
[08:55] <mpt> Fujitsu, I saw that report when reporting the new one
[08:55] <Fujitsu> Is the new one different in some way?
[08:55] <mpt> 189522 doesn't have enough information for me to tell whether it's the same bug
[08:56] <mpt> but it seems unlikely that it is
[08:57] <Fujitsu> 189522's reporter complains that he can't choose "I don't know". You do too in 215537. Is it particularly likely that it's broken in two ways?
[08:57] <mpt> In David's case he (apparently) chose "I don't know" to start with, whereas I chose a package name to start with.
[08:57] <Fujitsu> Ah. So it could well be.
[08:58]  * Fujitsu returns to his cave.
[09:00] <mpt> Bug 102216 is in a similar predicament -- I can't reproduce it, it might be the same bug as the one I just reported, but it seems unlikely.
[09:00] <ubotu> Launchpad bug 102216 in ubuntu "[malone] Still finds an error when chosen dont know for package name" [Undecided,Invalid] https://launchpad.net/bugs/102216
[10:06] <ubotu> New bug: #215557 in launchpad-buildd "open-iscsi fails to install" [Undecided,Invalid] https://launchpad.net/bugs/215557
[10:16] <Kmos> https://edge.launchpad.net/ubuntu/+mirror/ftp.dei.uc.pt-archive2 -> could some LP admin remove my entry that is duplicate?
[10:17] <\sh> guys, when is the publisher for ppa running? every XX mins? 
[10:19] <Fujitsu> \sh: */20
[10:20] <\sh> Fujitsu, thx :)
[10:35] <ubotu> New bug: #215575 in launchpad "xorg-driver-fglrx cannot be selected as package to report bug about" [Undecided,New] https://launchpad.net/bugs/215575
[11:58] <muffinresearch> Quick question. Does launchpad have any kind of web service or API?
[12:21] <nouri> Hi.  Is there a way to send bug e-mails to an arbitrary e-mail address?
[12:21] <nouri> I want to send bug mails to a list.  (And I found out too late that launchpad itself has lists now.)
[12:51] <ubotu> New bug: #215628 in soyuz "Require a script to unembargo private packages" [High,In progress] https://launchpad.net/bugs/215628
[13:13] <ignas> hi
[13:47] <ubotu> New bug: #215661 in launchpad "PPA should allow multiple versions of a package to be present" [Undecided,New] https://launchpad.net/bugs/215661
[13:47] <ubotu> New bug: #215665 in malone "impossible to install hardy in LVM" [Undecided,New] https://launchpad.net/bugs/215665
[14:32] <ubotu> New bug: #137440 in launchpad-documentation "Launchpad application tours don't close the deal" [Low,Confirmed] https://launchpad.net/bugs/137440
[15:21]  * Hobbsee stabs packages that dont' built.
[15:21] <Hobbsee> er, build
[15:23] <ignas> i am having a small problem with PPA
[15:23] <ignas> i made the mistake of deleting a package from there
[15:23] <Hobbsee> shoot
[15:23] <ignas> now i have files in there that do not allow me to reupload the package
[15:23] <ignas> and i can't find a way to make it rebuild the package
[15:24] <ignas> the package was broken, but at least it was apt-get installable for some value of apt-get installable
[15:24] <Hobbsee> upload a higher version?
[15:25] <ignas> automatically generated stuff so making it create something a version higher is a bit problematic
[15:25] <Hobbsee> because the stuff all autogenerates again, each time?
[15:26] <ignas> no, because the code that would detect what "debian" versions are available is not there ;)
[15:26] <ignas> so if the package i am generating a deb from is the same - i will get the same debian package version
[15:27] <Hobbsee> sounds like the package is broken.
[15:27] <ignas> which package?
[15:28] <Hobbsee> your package
[15:28] <ignas> the idea is this - i take a python egg, run it through a script, and get all the parts needed to upload it to PPA
[15:28] <ignas> like .changes .dsc the diff and the tarball
[15:28] <ignas> automatically
[15:29] <ignas> as that is the only way i can generate the deb at the moment
[15:29] <ignas> i can't really create zope.i18n_3.4.0-2
[15:29] <ignas> and as 3.4.0-1 was uploaded to launchpad
[15:29] <ignas> and then deleted
[15:29] <ignas> i can't upload 3.4.0-1 again
[15:29] <Hobbsee> why?
[15:30] <ignas> because ppa does not allow me that
[15:30] <ignas> it deleted the deb
[15:30] <Hobbsee> if you wait for the cron job, you can actually upload it again.
[15:30] <Hobbsee> oh, so this is not true delete.
[15:30] <Hobbsee> cprov-out: might be able to help you do a true delete
[15:31] <ignas> i don't know what a true delete is ...
[15:31] <Hobbsee> stuff that deletes both binary and source
[15:31] <ignas> i see
[15:31] <ignas> only admins can do it?
[15:31] <Hobbsee> apparnetly so
[15:32]  * Hobbsee does not work on launchpad
[15:34] <Hobbsee> ignas: is it really helpful to have created a build system where you cannot do a rebuild, for any reason?
[15:34] <sayers> Launchpad is a very cool tool.
[15:34] <ignas> i can do a rebuild, problem is that if I fix a package, i can't upload the fixed package if it's already there
[15:35] <ignas> unless i do a "new release"
[15:35] <ignas> as in - debian release
[15:35] <cprov-out> ignas: the disk-remover is running each 30 minutes are you sure that the files still on disk. Point me to your PPA.
[15:36] <ignas> cprov-out: https://edge.launchpad.net/~schooltool-owners/+archive?field.name_filter=zope.i18n&field.status_filter=any
[15:36] <ignas> zope.i18n 3.4.0 is the problematic package
[15:46] <Hobbsee> fricking launchpad.
[15:46] <Hobbsee> cprov-out: please investigate OOPS-832EA102 
[15:47] <Hobbsee> and OOPS-832EA103
[15:48] <Hobbsee> come on, this was working for gutsy...
[15:49] <Hobbsee> it shouldn't die around hardy freeze time.
[15:49] <cprov-out> ignas: the files you've mentioned are not in pool since 2,5 hours ago, you should be able to re-upload the same version.
[15:50] <ignas> i see, i saw them listed when i expanded package description so i assumed they still are in there
[15:50] <ignas> got "Already uploaded to ppa.launchpad.net"
[15:50] <ignas> "Doing nothing for python-zope.i18n_3.4.0-1_source.changes"
[15:51] <Hobbsee> ignas: use dput -f
[15:51] <cprov-out> ignas: :) dput is silly 
[15:51]  * Hobbsee tries the workaround
[15:51] <ignas> cprov-out: thanks, that fixed it
[15:51]  * Hobbsee stabs.
[15:52] <Hobbsee> workaround doesn't work.
[15:52] <cprov-out> ignas: too early ... wait some minutes to thank us.
[15:52] <ignas> :)
[15:52] <Hobbsee> no way to do release management work on launchpad any more.  Not happy.  Please fix.  Thanks in advance.
[15:54] <cprov-out> Hobbsee: let's check your oops. You, impatient child :P
[15:54] <Hobbsee> cprov-out: it's 1am.  I'm not so patient when i want the stuff to build before i go to bed.
[15:55] <Hobbsee> cprov-out: and i don't think slangasek suddenly wants to do all the universe stuff, too.
[15:55] <cprov-out> Hobbsee: it was a timeout, did you try again ?
[15:55] <Hobbsee> cprov-out: 3 times on edge, 2 on normal LP.
[15:56] <Hobbsee> no dice.
[15:59] <Hobbsee> hiya mthaddon 
[15:59] <mthaddon> hey Hobbsee 
[16:03] <Hobbsee> cprov-out: can you ping me when you get it fixed please?
[16:03]  * Hobbsee heads to bed
[16:04] <cprov-out> Hobbsee: okay, good night.
[16:04] <Hobbsee> thanks
[16:06] <Hobbsee> Rejected:
[16:06] <Hobbsee> The source bip - 0.7.2-0ubuntu1 is already accepted in ubuntu/hardy and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload.
[16:06] <Hobbsee> ?
[16:06] <Hobbsee> i deleted it.
[16:07]  * Hobbsee shrugs, will test it in other ways
[16:15] <ubotu> New bug: #215738 in soyuz "The message on emails for upload rejections is misleading" [Medium,In progress] https://launchpad.net/bugs/215738
[16:18] <ignas> cprov-out: hmm, indeed - apparently no thanks ;) even though i have reuploaded the package with -f, launchpad is not trying to rebuilt it, because it is "deleted"
[16:47] <ignas> cprov-out: launchpad rejected my changes because - "the version is the same"
[16:51] <kiko> ignas, increment the version and try again.
[16:51] <ignas> kiko: i can't
[16:51] <ignas> kiko: which is why i tried to remove the old package
[16:51] <ignas> "delete" it
[16:51] <ignas> and upload it again
[16:52] <ignas> it deleted the deb
[16:52] <kiko> ignas, you can't? fingers cramped? :)
[16:52] <ignas> kiko: i can't - it would take long, and i want a working deb back
[16:52] <cprov-out> ignas: does't really matter if you've deleted the source, soyuz check if it was ever uploaded to that PPA.
[16:52] <cprov-out> ignas: so, you will never be able to reupload the same version.
[16:52] <ignas> kiko: so i was thinking maybe there is a way to at least "rebuild" the deb again
[16:53] <ignas> if i can't reupload the same version
[16:53] <kiko> hmmm
[16:53] <ignas> until i get the version part resolved
[16:53] <ignas> because at the moment i am stuck
[16:53] <ignas> old version deleted, new version - not there yet
[16:53] <cprov-out> ignas: why did you remove it ?
[16:53] <ignas> cprov-out: because i assumed that if i will remove it i will be able to upload it back
[16:53] <ignas> again
[16:53] <ignas> because well - it won't be in there
[16:55] <cprov-out> I have to go not, but I'm sure someone else will explain to you why it's we can't allow you to upload the same version of a package with a different content.
[16:55]  * cprov-out goes
[16:55] <ignas> emm, so unless i will manage to come up with a new version I will not have anything installable in PPA?
[16:56] <kiko> ignas, you can just append -rev1 to the existing version number.
[16:57] <ignas> kiko: packages are generated automatically
[16:57] <ignas> kiko: i have written only parts of that system, so i would have to find out how it works and fix it
[16:57] <ignas> kiko: which i will do, but it will take time
[16:57] <kiko> ignas, you can change them after generated, this once.
[16:57] <ignas> kiko: i have no idea how debian packages are generated at the moment
[16:58] <kiko> ignas, I'll let you read about that -- but it's not very complicated, just pick up the source package you generated and update the version
[16:58] <kiko> maybe LaserJock or Fujitsu might have a hint :)
[16:59] <ignas> kiko: so - why is the delete button in there at all?
[16:59] <ignas> kiko: if it only "hides" actually
[17:00] <ignas> and if it only "hides", why isn't there "unhide" button
[17:01] <kiko> it does delete the package.
[17:01] <kiko> it just doesn't allow you to reuse the version.
[17:02] <ignas> i see
[17:03] <ignas> ok, it makes sense, though having an undelete or "rebuild" button would be kind of nice, because - the version is locked to the particular state of the package anyway
[17:03] <ignas> if it is to "not allow 2 different packages under the same name + version in the world"
[17:03] <kiko> that I could agree with; however, if you delete and upload a new version, all bets are off.
[17:03] <ignas> thing, then it would kind of make sense to allow people to reupload the same package under the same version number
[17:04] <kiko> if you want to file a bug about undeleting deleted packages that haven't been superseded yet, we can do that
[17:04] <ignas> i mean - you can just keep md5/sha or something like that
[17:04] <ignas> kiko: if such a thing would make sense for anyone else except for me at this specific moment...
[17:22] <ignas> hmm, i have dsc file, changes file, orig.tar.gz and diff.gz, how do i get the same sandbox i would get by using "apt-get source some-package" from these?
[17:40] <rockstar_> Can someone point me to the link where I can request an svn project be converted to bzr?
[17:40] <rockstar_> ...and added to launchpad...
[17:44] <_MMA_> I don't know if this is a Launchpad or Bazaar question. Is there a way to keep specific files automatically synced between branches?
[18:07] <ubotu> New bug: #215798 in launchpad-bazaar "Register branch page should make it clear registration is not pre-requisite for working on a project" [Medium,New] https://launchpad.net/bugs/215798
[18:29] <sque> Hi! I need some help with branch merging... I am unexperienced user of bazaar. Ok I have this branch https://code.launchpad.net/~sque/liboonet/spec2-dev and I want to merge it at this https://code.launchpad.net/~sque/liboonet/trunk. I clicked on propose for merge, it changed on "work in progress" statues, I then added to the merge queue
[18:30] <sque> and now? what?
[18:30] <sque> how the REAL merging happens? I have given all the needed info
[18:32] <matsubara> sque: someone with the appropriate permission need to merge your branch into the other branch
[18:33] <sque> I am the owner of both branches
[18:33] <matsubara> and push the changes to launchpad
[18:34] <sque> matsubara the "propose for merging" and "add in merge queue" are just informational actions?
[18:34] <sque> I have to pull both branches localy, merge one to the other and push it back?
[18:34] <matsubara> sque: AFAIK, yes
[18:36] <matsubara> you just need to pull the target branch locally.
[18:36] <matsubara> brz pull target-branch
[18:36] <matsubara> cd target-branch
[18:36] <sque> I have done that...
[18:36] <sque> and then?
[18:36] <matsubara> bzr merge url-of-proposed-merge-branch
[18:36] <matsubara> bzr commit -m "description of merged changes"
[18:36] <matsubara> bzr push
[18:37] <matsubara> I think that would do it
[18:37] <sque> so this... does nothing! https://code.launchpad.net/~sque/liboonet/trunk/+merge-queue
[18:39] <matsubara> well, nothing is unfair. Imagine for instance how that merge-queue helps projects which get lots of contributions. It's a single place where you can see all the proposed patches to include in mainline.
[18:39] <matsubara> I think that at some point this might be automated though.
[18:39] <matsubara> sque: you might want to ask thumper about it when he's around.
[18:40] <matsubara> or maybe abentley
[18:40] <sque> The way it is presented seems more like a real action not just an organizational place
[18:41] <sque> and that got confused me. If I knew from the 1st place that it was just informational I wouldn't use it on a project of 1 developer :P
[18:41] <sque> I would just merge the code localy and just commit it
[18:42] <sque> anyway ty :)
[18:42] <matsubara> sque: https://blueprints.edge.launchpad.net/launchpad-bazaar
[18:43] <matsubara> sque: that's the list of specs the launchpad-bazaar team will be working on. check the branch-merge-bot one. it seems to be what you're asking for.
[18:43] <sque> it was the first in the list that I clicked ;)
[18:43] <matsubara> sque: so the merge-queue page is the first step on that direction
[18:43] <sque> yes
[18:44] <sque> and probably you will press something like "do it" and all the queue will be processed
[18:44] <sque> nice :D
[19:21] <Zelut> I just uploaded a package to my PPA which was denied.  I believe I have fixed it but the same dput command tells me 'you already uploaded that one dummy'
[19:21] <LaserJock> Zelut: yeah, either remove the .upload file or use dput -f
[19:24] <nand> hi!
[19:24] <Zelut> LaserJock: ok, that works.. now I realize I don't think I fixed the problem after all :)
[19:25] <Zelut> LaserJock: I build my package with bzr-buildpackage --native.  That created .changes, .deb, .orig & .dsc.
[19:25] <nand> some news on the LP mailing lists since #208431 got fixed?
[19:25] <nand> my application is still stuck :/
[19:25] <Zelut> LaserJock: I dput the .changes (after signing) and its rejected for 'containing a binary package'
[19:26] <LaserJock> yeah
[19:26] <LaserJock> you need a source-only upload
[19:26] <Zelut> LaserJock: ..but if I remove the .deb from the folder it complains that it can't find the .deb.
[19:26] <LaserJock> so look for a _source.changes file
[19:26] <LaserJock> rather than a _<arch>.changes
[19:27] <Zelut> ...which I don't have.
[19:27] <LaserJock> could be you need to create one
[19:28] <Zelut> can you tell I'm new at this :)
[19:32] <Zelut> ok, I think I got it.. dput the _source.changes file.. lets see how this gets accepted.
[19:33] <LaserJock> it's got a much better chance :-)
[19:33] <Zelut> I'll wrap my head around this one of these days.
[19:36] <Zelut> ok, this is probably another simple one but this time I got: Signer has no upload rights at all to this distribution.                                                                             
[19:37] <LaserJock> oops
[19:37] <LaserJock> you uploaded to Ubuntu
[19:38] <LaserJock> you were ------||----- close to being a MOTU there ;-)
[19:38] <Zelut> i thought I'd try to squeeze it in there
[19:38] <LaserJock> so you just rand dput *_source.changes?
[19:38] <LaserJock> *ran
[19:39] <Zelut> I did, and I'm using the .dput.conf as suggested here: https://help.launchpad.net/PPAQuickStart
[19:39] <LaserJock> yeah, the problem is the default is ubuntu
[19:40] <LaserJock> we've discussed a little about changing the global dput config to not default to ubuntu to avoid that kind of thing
[19:40] <Zelut> so I should simple remove the /ubuntu/ on my incoming or..?
[19:40] <LaserJock> no
[19:41] <LaserJock> your .dput.cf file is fine
[19:41] <LaserJock> you just need to do dput my-ppa *_source.changes
[19:41] <LaserJock> where "my-ppa" is the name of the PPA in the .dput.cf you want to upload to
[19:42] <LaserJock> dput has a global config file in /etc/ that has an ubuntu section for developers to upload with
[19:42] <LaserJock> but it's set as the default
[19:43] <Zelut> that makes sense
[19:43] <Zelut> i wonder if its assumed people using PPAs already know this so it isn't mentioned on the LP link.
[19:44] <Zelut> ie; if you're building your own PPA archive you *probably* already know the steps so the docs are lacking.
[19:45] <Zelut> ok, tat one was accepted
[19:45] <Zelut> thank you
[19:47] <LaserJock> well, it is in there
[19:47] <LaserJock> but probably not clear enough
[19:47] <LaserJock> Step 3: Upload signed sources only (no binaries), using
[19:47] <LaserJock> dput phototeam-ppa P_V_source.changes
[19:48] <LaserJock> so technically that has both the "You need to upload _source.changes" part and "dput <ppa> *_source.changes" part
[19:48] <LaserJock> but it's not really as clear as it probably should be
[21:20] <ubotu> New bug: #215913 in malone "filing bug report requires account" [Undecided,New] https://launchpad.net/bugs/215913
[21:56] <ubotu> New bug: #195013 in rosetta "Firefox 3 and xulrunner 1.9 needs translations" [Undecided,Confirmed] https://launchpad.net/bugs/195013
[21:58] <gilir> hi
[22:01] <gilir> I have some problems with a PPA
[22:01] <gilir> The repository itself seems to be corrupted
[22:02] <gilir> https://launchpad.net/~awn-testing/+archive
[22:03] <gilir> If somenone have a good idea, I'm interesting :)
[22:22] <Rinchen> gilir, what do you mean by "corrupted"?  I see you had some amd64 failures there
[22:22] <Rinchen> but other than that it looks ok to me
[22:23] <Rinchen> gilir, ah, I see. "Chroot problem"
[22:24] <Rinchen> kiko, do you know what causes the ppa builders to set the status as "Chroot problem"?
[22:24] <Rinchen> that's a new one for me
[22:24] <gilir> Rinchen people using the PPA have the same error when they do apt-get update
[22:25] <Rinchen> gilir, well your log states "E: Encountered a section with no Package: header"
[22:26] <Rinchen> do you have a depends in there by chance?
[22:26]  * Rinchen is not the PPA expert. :-)
[22:27] <gilir> Rinchen yes I build package with depends on packages on the PPA
[22:27] <gilir> but I can't see which package have this Section probelm
[22:29] <Rinchen> yeah the logs don't seem to indicate which dependency it might be...they just issue the error
[22:31] <Rinchen> unfortunately gilir I don't know enough to help you beyond this point. someone else here might though.  If you don't get an answer, you can file a Question on LP or email the users list
[22:31] <gilir> Rinchen Ok thanks :)