mapreri | So, I have a PPA with "Build debug symbols" and "Publish debug symbols" enabled, though even if -dbsym are in the pool, they are not in Packages. Is this expected? If so, is there a way I can get the -dbgsym listed in Packages? | 13:00 |
---|---|---|
mapreri | the ppa being ppa:scribus/ppa | 13:01 |
cjwatson | mapreri: they're in a separate section, main/debug | 13:26 |
mapreri | ooh | 13:27 |
cjwatson | $ curl -s http://ppa.launchpad.net/scribus/ppa/ubuntu/dists/xenial/main/debug/binary-amd64/Packages.xz | xzcat | grep-dctrl -nsPackage '' | xargs | 13:27 |
cjwatson | scribus-dbgsym scribus-trunk-dbgsym scribus-ng-dbgsym | 13:27 |
mapreri | is the addition of that line to apt's sources.list automated somehow? like, a flag with add-apt-repository or something like that? | 13:29 |
est31 | so a previous build for my ppa package failed | 14:08 |
est31 | and i now want to retry with an updated build script | 14:09 |
est31 | but it gives me "Could not be uploaded correctly" | 14:09 |
est31 | the log is here https://launchpadlibrarian.net/259659399/upload_1138577_log.txt | 14:12 |
est31 | and the recipe build overview is here: https://code.launchpad.net/~minetestdevs/+recipe/minetest-stable-precise | 14:12 |
cjwatson | mapreri: not that I know of, which is not to say there isn't | 14:18 |
cjwatson | est31: you need to arrange for the new source package to have a different version number; this is usually achieved by putting the revision number of the packaging branch in the version as well as the revision number of the upstream branch | 14:19 |
cjwatson | your version number actually seems to be constant and hardcoded in your recipe right now, which isn't the best way to do it | 14:20 |
cjwatson | https://help.launchpad.net/Packaging/SourceBuilds/Recipes has details of the kinds of things you can do | 14:21 |
* StevenK collapses into bed after a fun day of travelling from Stuttgart HBF to Düsseldorf HBF | 22:02 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!