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