=== stokachu_ is now known as stokachu === cp16net_ is now known as cp16net [12:24] There's a package in a PPA called my-weather-indicator that was built as a native package; shouldn't it be non-native? === bigjools_ is now known as bigjools [12:36] probably, but that's up to the packager [15:09] hi folks [15:10] I have an issue where upstream changed a release tarball (because of a release error) [15:10] except that I already pushed the initial faulty tarball to my ppa [15:10] now I can't upload the "correct" one [15:10] would I need to do a repack reversioned tarball? [15:10] deleted the "wrong" packages doesn't seem to allow the new tarball [15:10] deleting* [15:15] pmjdebru1jn: afaik you have to upload the new one with a different version, since lp doesn't accept two source package with the same version (even if you delete one first, lp remember everything ;P) [15:18] mapreri: sure, typically that makes sense [15:18] I'm dealing with a misbehaving upstream :( [15:18] so 0.19 is the current version, so I'd have do so 0.19repack1 or something like that [15:19] do so/to do [15:19] * pmjdebru1jn wonders if there's an official procedure for this [15:19] +repack seems common [15:20] pmjdebru1jn: eheh, not all upstream are developer-friendly ;) I suggest you to upload an 0.19-1 or something like your idea [15:20] yeah. even +repack is ok, but I don't like to see it (personally opinion, of course). You are dealing with a ppa, so you can call your software version as you prefer [15:21] I don't like it either :) [15:21] this isn't about liking anything :) [15:21] but [15:21] my debian version is already higher [15:21] and it won't accept [15:21] so I guess the upstream tarball needs renaming [15:21] well reversioning [15:21] at least +repack0 seems common-ish [15:22] so would be something like 0.19repack0-0ubuntu1pmjdebruijn1~precise :D [15:23] omg -.- the lp versiong is horrible sometimes [15:23] versioning* [15:23] well partially it's forced [15:24] so... :( [15:24] you right... [15:24] I always add teh pmjdebruijn tag to make it easy to identify my packages [15:24] so that's just a practical thing too [15:25] and ~precise is required to have the same package for several dists [15:25] anyhow, it's workable nontheless [15:25] it's least there's some logic to it [15:26] anyhow, thanks [15:27] there is some logic, but the logic is for machines, not for humans ;) === tgm4883_ is now known as tgm4883 === milleja46_ is now known as milleja46 [21:46] mapreri: eh, this isn't lp versioning, it's self-inflicted :P