Add support for Debian 11

[sboyd-m]

I believe this will work.

Closes #187

[smortex]

This seem to unexpectedly change the behavior for Debian Buster.

Please update your code to keep the original behavior in place (unless it was broken?)

[bastelfreak]

please also add Debian 11 to the metadata.json

[sboyd-m]

@smortex Not sure what adjustments you are referring to. In glancing at the code, and some old commits for adding new OSes, the changes I made seemed to be correct. It looks like this module has default origins on Debian only for the current release, and older releases get security origins by default. Buster is now an older release, as of a few weeks ago. Bullseye is stable, and buster is oldstable. I'm happy to just change it back of course, but the code as I see it ought to be the way it is in the PR.

[smortex]

Ah! All good then, sorry for the confusion 😄.

I have just merged a bunch of PR to drop old releases and extend the test suite. Do you mind rebasing on top of it and fixing conflicts?

From your working directory:

git fetch origin         # Download the latest code we have here
git rebase origin/master # Move your commits on top of the main branch
# -- Here git will complain about the conflict, open metadata.json, fix the conflict, then
git add metadata.json    # Tell git this file is now fixed
git rebase --continue    # Ask git to continue it work
# -- End of conflict management
git push -f              # Send the changes (-f is required because we re-wrote history)

Thanks!

[sboyd-m]

Should be good then.

Also just a side note, there are more references to old OS in other_debians_spec. Since you just cleaned stuff out in the other PRs, I figured I would let you know. I don't want to bother in this PR, since it's slightly unrelated.

[smortex]

LGTM!

[smortex]

Also just a side note, there are more references to old OS in other_debians_spec. Since you just cleaned stuff out in the other PRs, I figured I would let you know. I don't want to bother in this PR, since it's slightly unrelated.

There is no strong policy here, when we "drop support", we stop making sure everything works and we are able to nuke legacy code. This rarely happen at the same time, so next major release which "drop support" will in fact probably work as well for legacy releases, but removing the corresponding code is a following move.

If you want to assist in this, feel free to send more PRs 😃

Thanks!