Learn more about these different git repos.
Other Git URLs
The unbound package bumped their so version. It is fully backwards compatible, so it should not pose any problems. Currently, autotrust, which depends on the newer unbound, cannot be build due to the missing bumped so version.
Could someone allow the new so version?
I believe this needs to be done for F-10 and F-11. Though I'm not sure about the status for F-12 (except I do not get reminder emails about that)
sounds like you want a newer built version of unbound to be tagged into the buildroot, so dependant packages can be rebuilt. If so, please provide the full NVR (name-version-release) of what needs to be tagged.
That would be: unbound-1.3.4-2.f10 unbound-1.3.4-2.f11 unbound-1.3.4-2.f12
What would be the proper way of asking this? As unbound-1.4.0 is about to be released, so i will have to repeat this exercise.
I tagged these for the buildroot, modulo typos (ie, f12 vs fc12).
Fwiw, I'd be wary of introducing big changes to F-10, it'll be EOL in under a month.
ping, it's been almost a month, are these buildroot tags still needed?
These are in updates and f12 release as-is, so have no need to be tagged (anymore).
Metadata Update from @pwouters: - Issue assigned to rdieter
Login to comment on this ticket.