Open V-Z opened 2 years ago
The error is triggered from this commit: https://github.com/openSUSE/osc/commit/c61e4a514ee0128d78f8598a23e78b6684913a56.
I wonder if this check is needed and if osc simply should manage these logs itself.
I'd prefer not to build any workarounds around vc
in osc, because the problem would be fixed in one tool only.
That's why I believe this belongs to vc
tool in https://github.com/openSUSE/obs-build
Isn’t Meego completely dead, buried, not even smelling any more?
The changelog style is still used in regular RPM Redhat style and in Sailfish OS.
I'd prefer not to build any workarounds around
vc
in osc, because the problem would be fixed in one tool only. That's why I believe this belongs tovc
tool in https://github.com/openSUSE/obs-build
I think you confuse the SUSE vc and the Meego/Intel vc. Osc refers to the latter I think.
However meego style could be added to this vc from the original meego vc.
I couldn't find any archive of the Meego vc besides the Debian source mirror: https://bazaar.launchpad.net/~ubuntu-branches/debian/sid/meego-packaging-tools/sid/view/head:/bin/vc
Using that script osc works as intended.
Also I'm not sure if it makes sense to extended the SUSE vc when osc itself doesn't even use it for the SUSE changelog style?
When updating an older package having its
muscle.changes
(in this example, probably output ofrpm -q --changelog
) likerunning
osc vc
end withError: you need meego-packaging-tools for /usr/bin/vc command
.After removing that file,
osc vc
worked as expected, producingNotes from discussion in IRC opensuse-buildesrvice
^\*\W+(.+\W+\d{1,2}\W+20\d{2})\W+(.+)\W+<(.+)>\W+(.+)$
; problem is that current suse style is the same meanwhile at this point; so, not really possible to detect if it is meego or suse style that way^
and prefix by a-{66}
line or so. inmeego/rpm
, the date starts after^\*\