=== spm` is now known as spm === cinerama_ is now known as cinerama === lifeless_ is now known as lifeless === medberry is now known as med_out === jtv is now known as jtv-eat === jtv-eat is now known as jtv === lag` is now known as lag [12:57] 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] docdrum, since the library is BSD licensed the owner has granted you that right, as well as many other rights. [13:34] (with the usual I am not a lawyer disclaimer) === braiam is now known as Exi-o- === Exi-o- is now known as Braiam === gary_poster changed the topic of #launchpad to: https://launchpad.net/ | Help contact: gary_poster | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ [13:40] diwic: OK, thanks! I was unsure b/c the launchpad-docs only talks about 'your project'. [13:42] I'm (quite, ianal2) sure about the licensing terms, just wondering if launchpad allowed this usage === mbarnett` is now known as mbarnett === med_out is now known as med === med is now known as medberry [16:08] is there pricing information for private ppas somewhere? [16:57] veloutin: i _think_ it's included in commercial subscriptions which are a flat price [16:58] suggest you mail commercial@launchpad.net [16:58] yeah, It's what I just read from a few questions [16:59] thanks, though :) [16:59] you're welcome === matsubara is now known as matsubara-lunch === jcsackett is now known as jcsackett|lunch [18:29] What is the process for getting bug comments deleted? [18:29] Specifically https://bugs.launchpad.net/ubuntu/+source/mythbuntu-control-centre/+bug/214074/comments/15 [18:30] Ubuntu bug 214074 in mythbuntu-control-centre (Ubuntu) "cannot install packages using MCC in diskless chroot" [Medium,Won't fix] [18:30] ask a question against launchpad [18:31] nigelb, will do. Thanks [18:34] tgm4883: I have hidden the spam comment [18:47] comment 5 in https://bugs.launchpad.net/ubuntu/+source/mythplugins/+bug/3041 is spam [18:47] Ubuntu bug 3041 in mythplugins (Ubuntu) "mtd built without transcode support" [Medium,Fix released] === matsubara-lunch is now known as matsubara === jcsackett|lunch is now known as jcsackett === Quintasan_ is now known as Quintasan === yofel_ is now known as yofel [22:31] hi, I'm getting an regject email when I try to upload a source [22:31] the email points to here: https://help.launchpad.net/Packaging/UploadErrors [22:32] the reason is because: File already exists in [22:32] however....I deleted that package already. I don't have any packages in my PPA [22:33] are they not really deleted? === matsubara is now known as matsubara-afk [22:58] gustonegro: You can never replace a file in a PPA with one with different contents, even after deleting it [22:59] maxb: why is that? [23:02] because its part of a federated database [23:02] every user of the ppa makes the assumption that per-package files never change contents [23:03] hmm...so what can I do? [23:03] there are no users of the ppa yet. I just want to delete the old one and make a new one. [23:03] the old what? [23:04] the old package [23:06] here it says I have no published packages: https://launchpad.net/~august-alien/+archive/ppa [23:06] you need to use a new version number for the upstream [23:07] e.g. add +test1 to it [23:07] add +test1 to the package name? [23:07] can I do that with dput ? [23:18] could someone explain what this all means or point me to some docs on the matter? [23:19] debian/control defines your version [23:19] every upload must be unique. [23:19] -> you must change it every time [23:19] the upstream part defines the tarball that is looked for [23:19] to change that you change the upstream part and the tarball name. [23:20] what is an upstream? I've read all the docs and see it all the time, but never is it defined. [23:21] sorry for the naive question.....maybe there is a better forum for that. [23:22] 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] yes [23:23] after you dput you can never reuse the version number [23:23] wow [23:24] so , I have to set a version number by changing the package name? [23:25] what you normally do is leave the tarball unchanged [23:25] and change the packaging only resulting in a new *diff* reusing the same tarball [23:25] but because you are trying to upload a changed tarball, thats why the problem is happening [23:25] so in this special case (because you are learning) [23:26] you need to change the tarball version [and package version] to be able to upload [23:26] for that I just rename the tarball and change the "Source" section of the control file? [23:28] Why would you change the package name? You want to change the package version [23:29] 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] maxb: he doesn't have the old tarball anymore... contents conflict [23:34] Sure... but that's still only cause to change the version, not the name [23:34] right [23:34] but the 'name' of a tarball includes the version [23:34] gustonegro: the version is set from the top entry in debian/changelog [23:34] maxb: you're binding the terms differently [23:35] So, yes, the file may need to be renamed, but nothing in debian/control needs to change [23:35] right [23:35] gustonegro: ^ whats your current tarball name [23:35] gustonegro: and whats the first line in your debian/changelog