-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redirect bpf to bpf.2, not bpf.4freebsd #68
Comments
|
Thanks for your report! bpf.4freebsd wins because it’s in jessie, whereas bpf.2 isn’t. Hence, the redirector first filled in the suite to jessie, then had only one choice left to hand out to you. I’m not sure what we can do here, as this seems like an edge case (which will also solve itself with the next stable release). If you have any ideas, please feel free to reopen. |
|
On 2017-04-10 23:42:05, Michael Stapelberg wrote:
Thanks for your report!
bpf.4freebsd wins because it’s in jessie, whereas bpf.2 isn’t. Hence, the redirector first filled in the suite to jessie, then had only one choice left to hand out to you.
I’m not sure what we can do here, as this seems like an edge case (which will also solve itself with the next stable release).
If you have any ideas, please feel free to reopen.
Well, i was actually a little surprised to hit jessie by default. While
I see that it could make sense, I am not sure it's the right
decision. There's this example, but there's also SEO: all those
redirections will keep on changing from release to release, which will
lead to poor SEO.
But maybe I could open a separate issue for this?
|
|
Sure, if you’d like to discuss this, please open a separate issue. |
|
understood, see #69 then |
What I was looking for is more the Linux kernel bpf manpage:
https://manpages.debian.org/unstable/manpages-dev/bpf.2.en.html
not sure why the freebsd manpages win in this case?
The text was updated successfully, but these errors were encountered: