Mailinglist Archive: opensuse-buildservice (77 mails)

< Previous Next >
[opensuse-buildservice] Linked spec files not updating after file is patched?

I'm having some problems with custom builds that require spec file changes. While the changes themselves work, it seems to cause OBS to stop tracking the upstream changes. I don't know whether this is a bug, expected behaviour, or something that I've done wrong.

I've branched Gnome Books from GNOME:Factory [1]. I'm fairly sure I didn't tick the "stay on this revision" box. I've added some diffs for custom patches and put a "<topadd>" tag in my _link [2] to add the patches without having to make an actual .diff file for the .spec.

Gnome 3.32 has been released* and the upstream spec file is showing v3.32 [3]. Meanwhile, my spec file is still showing 3.30.1 [4]. However, I *do* see the 3.32 tarball in my (merged) sources, as well as the old 3.30 one [5].

Is there a way to fix this so that my packages modify the .spec to add patches but also track the upstream changes? I'm happy to fix breakages if the spec file changes a lot upstream (as that's basically what I'd have to do with a diff file if upstream changed a lot).



* Yes, I know this breaks my example package, because Gnome Books has been separated, but I think that's separate from the underlying spec change issue

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups