Paul Wise

PS: please note that even if you don't get a sponsor immediately, keep updating the package on mentors.d.n and keep updating the RFS bug when the package version changes.

Ah, woops! I thought your name sounded familiar :) -- bye, pabs https://bonedaddy.net/pabs3/

Woops, forgot to attach the [backtrace](https://github.com/BestImageViewer/geeqie/files/5180829/crash.txt).

Take any manual page URL, replace the suite/codename with one of the oldstable oldoldstable oldoldoldstable suites and you get a redirect that lands on the bullseye codename. -- bye, pabs...

Correct: https://manpages.debian.org/stable/i3-wm/i3.1.en.html -> https://manpages.debian.org/bullseye/i3-wm/i3.1.en.html Incorrect: https://manpages.debian.org/oldstable/i3-wm/i3.1.en.html -> https://manpages.debian.org/bullseye/i3-wm/i3.1.en.html https://manpages.debian.org/oldoldstable/i3-wm/i3.1.en.html -> https://manpages.debian.org/bullseye/i3-wm/i3.1.en.html https://manpages.debian.org/oldoldoldstable/i3-wm/i3.1.en.html -> https://manpages.debian.org/bullseye/i3-wm/i3.1.en.html -- bye, pabs https://bonedaddy.net/pabs3/

Ah, that makes more sense now, I guess that is why non-supported suites have the same behaviour.

No, keeping one copy around and then instead of having redirects, just have one symlink per suite name pointing at the corresponding codename, preferably automatically updated after each release, or...

Thanks, that sounds much more complicated than I thought. Do you know if it is possible to put a regular rewrite before the RewriteMap, but passing the final rewrite decision...

Excellent, thanks for the update. Once the forked libs are dropped and if you want to get Kurento into Debian yourselves, please refer to this document and the links in...

It might be a good idea to add a label like `release-2.0` to the issues that you consider mandatory to fix before 2.0 can be released.