On 13.05.21 21:54, Benjamin Gilbert wrote:
On Thu, May 13, 2021 at 12:36 PM, Alexander Kanavin wrote:They're not useless though. As a layer maintainer I absolutely want those checks, as I want to be aware of any branch configuration changes upstream, and to ensure I'm not accepting a change in source revision that points to an unattached commit, or one from a branch that's not supposed to be used at all.Yup, if downstream packagers want to manually review such cases, no objection from me. My concern is upstream getting bug reports that say "please reinstate this branch and never delete it again or you'll break our builds". See https://github.com/ostreedev/ostree/issues/2360 <https://github.com/ostreedev/ostree/issues/2360> and https://github.com/coreos/go-systemd/issues/371 <https://github.com/coreos/go-systemd/issues/371> for examples.
But the genie has been out of the bottle already - revision x was published on branch y - so for me changing the (branch, revision) tuple is as suspicious as a forced rewrite.
Best, --Benjamin Gilbert
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#151723): https://lists.openembedded.org/g/openembedded-core/message/151723 Mute This Topic: https://lists.openembedded.org/mt/82782995/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
