| === Ursinha-afk is now known as Ursinha | ||
| === charles_ is now known as charles_quassel | ||
| === charles_quassel is now known as charles__ | ||
| === Ursinha is now known as Ursinha-afk | ||
| === Ursinha-afk is now known as Ursinha | ||
| === Ursinha is now known as Ursinha-afk | ||
| sergio-br2 | hey hello | 16:54 |
|---|---|---|
| sergio-br2 | i create a ppa, and use a recipe like this: # bzr-builder format 0.3 deb-version 1.8.0.1231-0ubuntu3 | 16:54 |
| sergio-br2 | but my packages are becoming vbam - 1.8.0.1231-0ubuntu3~ubuntu12.04.1 | 16:55 |
| sergio-br2 | how can i delete this ubuntu12.04.1 entry? | 16:55 |
| sergio-br2 | i searched web, and there is no info about this | 17:05 |
| sergio-br2 | seeing 2 times ubuntu in the name of package is annoying me | 17:05 |
| sergio-br2 | if someones knows why names in package changed from "trusty" to ubuntu14.04.1... | 17:23 |
| pmatulis_ | if one has an apport report transferred to a non-Ubuntu system is there any way to use it to open a bug with it or does one manually open the bug and include it as attachment? | 17:59 |
| cjwatson | sergio-br2: We changed that because it's important that versions be monotonically increasing, and we're getting near the end of the alphabet; the codename of Ubuntu 17.10 will sort earlier than that of Ubuntu 17.04. | 21:55 |
| cjwatson | So we needed to fix this far enough in advance that it won't be a problem for future backports. | 21:55 |
| sergio-br2 | cjwatson, thanks. But for example, i had a problem to update my package, i thougt it will automatically upgrade from [...]~ubuntu14.04.1 to [...]~ubuntu14.04.1 | 21:58 |
| sergio-br2 | *[...]~ubuntu14.04.1 to [...]~ubuntu14.04.2 , sorry | 21:58 |
| sergio-br2 | before, recipe was # bzr-builder format 0.3 deb-version {debupstream} | 22:00 |
| cjwatson | I'm pretty rusty on the details of recipes I'm afraid. I don't use them much. | 22:03 |
| cjwatson | I guess this is https://code.launchpad.net/~sergio-br2/+recipe/vbam-fixes ? | 22:05 |
| sergio-br2 | maybe, there is no option in recipe yet? | 22:05 |
| sergio-br2 | yeah | 22:05 |
| cjwatson | There are a number of variables you can use there; https://help.launchpad.net/Packaging/SourceBuilds/Recipes has a list. | 22:06 |
| cjwatson | I suspect that simply specifying a static version number, as you're doing, won't work very well, but there are some other options. | 22:07 |
| cjwatson | Not actually sure why we bother appending the .1 after the release given that that's just static. | 22:07 |
| cjwatson | It was "~trusty1" or similar before. | 22:08 |
| cjwatson | (And the "1" there seems similarly pointless.) | 22:08 |
| cjwatson | Possibly hard to change now though. | 22:09 |
| cjwatson | So I'd suggest you use one of the revno family of substitution variables to make the version fully unique. | 22:09 |
| sergio-br2 | so, if i use recipe like this: # bzr-builder format 0.3 deb-version {debupstream}~0 | 22:09 |
| sergio-br2 | it's hard to get 14.04.1 --> 14.04.2 | 22:10 |
| cjwatson | You won't be able to get 14.04.2, but you can put something else in your version that makes it distinct. | 22:10 |
| sergio-br2 | or i need to change upstream number, or i put 0ubuntuXY | 22:10 |
| cjwatson | Like {revno} or {revno:somebranch}. | 22:10 |
| cjwatson | As I say, see the page I linked to above for details. | 22:10 |
| sergio-br2 | hum, like my branch in baazar | 22:10 |
| cjwatson | {debupstream}~0 is rather unlikely to be anything like unique enough. | 22:11 |
| sergio-br2 | ok | 22:11 |
| cjwatson | Right, you might typically use the revno of the packaging branch or something like that. | 22:11 |
| cjwatson | Or you just have one branch so you could just use {revno}. | 22:11 |
| cjwatson | It generally doesn't make sense to build the recipe again without one of the branches involved changing. | 22:13 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!