[12:57] <docdrum> Hi!  I'm using a BSD-licensed library in my own project.  Is it allowed to use launchpad to host a fork of the lib and the .deb packages if I'm not the 'owner' of the library?
[13:33] <diwic> docdrum, since the library is BSD licensed the owner has granted you that right, as well as many other rights.
[13:34] <diwic> (with the usual I am not a lawyer disclaimer)
[13:40] <docdrum> diwic: OK, thanks!  I was unsure b/c the launchpad-docs only talks about 'your project'.
[13:42] <docdrum> I'm (quite, ianal2) sure about the licensing terms, just wondering if launchpad allowed this usage
[16:08] <veloutin> is there pricing information for private ppas somewhere?
[16:57] <poolie> veloutin: i _think_ it's included in commercial subscriptions which are a flat price
[16:58] <poolie> suggest you mail commercial@launchpad.net
[16:58] <veloutin> yeah, It's what I just read from a few questions
[16:59] <veloutin> thanks, though :)
[16:59] <poolie> you're welcome
[18:29] <tgm4883> What is the process for getting bug comments deleted?
[18:29] <tgm4883> Specifically https://bugs.launchpad.net/ubuntu/+source/mythbuntu-control-centre/+bug/214074/comments/15
[18:30] <nigelb> ask a question against launchpad
[18:31] <tgm4883> nigelb, will do. Thanks
[18:34] <maxb> tgm4883: I have hidden the spam comment
[18:47] <bdrung> comment 5 in https://bugs.launchpad.net/ubuntu/+source/mythplugins/+bug/3041 is spam
[22:31] <gustonegro> hi, I'm getting an regject email when I try to upload a source
[22:31] <gustonegro> the email points to here: https://help.launchpad.net/Packaging/UploadErrors
[22:32] <gustonegro> the reason is because:  File <UPLOADED_FILE> already exists in <LOCATION>
[22:32] <gustonegro> however....I deleted that package already.  I don't have any packages in my PPA
[22:33] <gustonegro> are they not really deleted?
[22:58] <maxb> gustonegro: You can never replace a file in a PPA with one with different contents, even after deleting it
[22:59] <gustonegro> maxb: why is that?
[23:02] <lifeless> because its part of a federated database
[23:02] <lifeless> every user of the ppa makes the assumption that per-package files never change contents
[23:03] <gustonegro> hmm...so what can I do?
[23:03] <gustonegro> there are no users of the ppa yet.  I just want to delete the old one and make a new one.
[23:03] <lifeless> the old what?
[23:04] <gustonegro> the old package
[23:06] <gustonegro> here it says I have no published packages: https://launchpad.net/~august-alien/+archive/ppa
[23:06] <lifeless> you need to use a new version number for the upstream
[23:07] <lifeless> e.g. add +test1 to it
[23:07] <gustonegro> add +test1 to the package name?
[23:07] <gustonegro> can I do that with dput ?
[23:18] <gustonegro> could someone explain what this all means or point me to some docs on the matter?
[23:19] <lifeless> debian/control defines your version
[23:19] <lifeless> every upload must be unique.
[23:19] <lifeless> -> you must change it every time
[23:19] <lifeless> the upstream part defines the tarball that is looked for
[23:19] <lifeless> to change that you change the upstream part and the tarball name.
[23:20] <gustonegro> what is an upstream?  I've read all the docs and see it all the time, but never is it defined.
[23:21] <gustonegro> sorry for the naive question.....maybe there is a better forum for that.
[23:22] <gustonegro> so if I make a mistake in a upload, I always have to go back and rebuild the package....even if it was just a packaging mistaeke?
[23:23] <lifeless> yes
[23:23] <lifeless> after you dput you can never reuse the version number
[23:23] <gustonegro> wow
[23:24] <gustonegro> so , I have to set a version number by changing the package name?
[23:25] <lifeless> what you normally do is leave the tarball unchanged
[23:25] <lifeless> and change the packaging only resulting in a new *diff* reusing the same tarball
[23:25] <lifeless> but because you are trying to upload a changed tarball, thats why the problem is happening
[23:25] <lifeless> so in this special case (because you are learning)
[23:26] <lifeless> you need to change the tarball version [and package version] to be able to upload
[23:26] <gustonegro> for that I just rename the tarball and change the "Source" section of the control file?
[23:28] <maxb> Why would you change the package name? You want to change the package version
[23:29] <gustonegro> maxb: where is the package version set? I don't see it any where except in how I named the .orig.tar.gz tarball?
[23:30] <lifeless> maxb: he doesn't have the old tarball anymore... contents conflict
[23:34] <maxb> Sure... but that's still only cause to change the version, not the name
[23:34] <lifeless> right
[23:34] <lifeless> but the 'name' of a tarball includes the version
[23:34] <maxb> gustonegro: the version is set from the top entry in debian/changelog
[23:34] <lifeless> maxb: you're binding the terms differently
[23:35] <maxb> So, yes, the file may need to be renamed, but nothing in debian/control needs to change
[23:35] <lifeless> right
[23:35] <lifeless> gustonegro: ^ whats your current tarball name
[23:35] <lifeless> gustonegro: and whats the first line in your debian/changelog