Does anyone know why v4l-utils is so old at over 4 years?
I can understand why it may track SLE, but even that was issued with a version 2 years old.
Just why does this package have to track SLE at all???
Does anyone know why v4l-utils is so old at over 4 years?
I can understand why it may track SLE, but even that was issued with a version 2 years old.
Just why does this package have to track SLE at all???
Hi and welcome to the Forum
No stupidity involved since the package is not present in SLE… so it doesn’t track it at all…
You need to contact the maintainers or raise a bug report, it looks like the updated package has never been submitted by the maintainers.
That is strange, since Andreas Stieger, said “In openSUSE Leap 42.2, this package is inherited from SLE at this time.” in reply to Bug 1018193.
And he said, 1.10 is in the OBS and he is right.
for Example:
https://build.opensuse.org/package/show?project=devel%3Alibraries%3Ac_c%2B%2B&package=v4l-utils
Hi
Correct, but it wasn’t updated to the newer versions available, the maintainers didn’t submit a newer version to the Leap release, plus it was failing to build…
No packages follow SLE, it’s just a starting point, then it’s up to the maintainers for Leap to push updated packages as required/requested.
If package X is in SLE and is at version 1.2.3 it gets pushed to the Leap release as a starting point, if maintainer in Leap of package X says I have version 4.5.6 they push to Leap through the release cycle so when the next release is at GM it comes out, if no one on the openSUSE side makes/submits then it will stay at version 1.2.3. At that point they SLE folks may say we want to stay at version 1.2.3, so they do, but Leap releases with version 4.5.6. There is also nothing stopping the maintainer pushing version 4.5.6 to SUSE Package Hub so it’s also available to SLE users…