History

Versions 36

Version Author Diff Last updated
v36 Jérôme Charaoui
add missing steps for dropping a suite
v35 Jérôme Charaoui
instructions for dropping a suite from deb.tpo
v34 Jérôme Charaoui
key for deb.tpo must not be expired
v33 Gabriel Filion
debian-archive: new suite, missing step. merge ci changes to version branch without this we end up without the new suite when we build a new version of the tor package.
v32 Gabriel Filion
debian-archive: CI pipeline for which of the commits we're pushing Yesterday I think I was watching what was happening on top of debian-0.4.8 and was confused about why the new packages were not visible in reprepro when it was all done. the next day though the new packages were there, so I was just watching the wrong pipeline.
v31 Gabriel Filion
debian-archive: little trick to make pushing pristine-tar less annoying
v30 Gabriel Filion
debian-archive: commands for new version and commit Since we're not using a remote branch for debian-merge-0.4.8 we're better off using a predictable commit message. This way it's easier to find where we should reset our local branch to.
v29 Gabriel Filion
debian-archive: don't split including commit list in separate point That's not a detail that should be done on its own after merging. It's part of how we want merges to be done. The rest is just renumbering list points accordingly.
v28 Gabriel Filion
debian-archive: how we should place debian-merge-0.4.8 is not clear I wonder why we're not pushing a branch for this? It would make it a lot easier to track where to start work from.
v27 Gabriel Filion
debian-archive: don't forget to update your local clone
v26 Gabriel Filion
debian: add emphasis on executing commands as non-root user this changes all of the commands listed: they should all happend with sudo -u tordeb. so it's important that this detail is more visible
v25 Gabriel Filion
debian: better formatting for commands in new suite the keyring package name is not complete. we should probably copy the keyring package first and then the tor package. there's no real implications but it feels more logical since the keyring package "bootstraps" the whole suite. the arguments `suite` and `suite-1` were not super clear. now this should be a bit easier to follow
v24 Gabriel Filion
debian new architecture: add note about echo "" pitfall this now looks similar to the instructions for a new tor package. it's very easy to miss the `echo " "` part and as a result just not be doing anything during that step
v23 Jérôme Charaoui
add steps in new suite for tor and keyring pkgs
v22 Jérôme Charaoui
be explicit about git push and what promote means
v21 Jérôme Charaoui
better link to dist tarballs the website may not be updated immediately after releases
v20 Gabriel Filion
Split setup actions into their own section the setup instructions are useful to follow before following any of the other sections, not just for new releases. those steps are also not really directly related to making a new package release.
v19 Jérôme Charaoui
improve tor debian archive docs use debian-main as the example branch, since it should always be updated, and specify that all supported release branches need to be updated as well mention the "# BPO" section which also needs updating when a new debian stable release is made
v18 Gabriel Filion
debian-archive: add quick description for the debian-main branch thanks lavamind for this info!
v17 Jérôme Charaoui
service/debian-archive: improve new suite docs