On Thu, 13 May 2021 at 21:54, Benjamin Gilbert <bgilb...@backtick.net> 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 and > https://github.com/coreos/go-systemd/issues/371 for examples. > It's not that different from deleting or archiving old tarball downloads - yes it keeps things clean and tidy for upstream, but it will break someone's automated build that way, no matter how obsolete the code being downloaded. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#151724): https://lists.openembedded.org/g/openembedded-core/message/151724 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] -=-=-=-=-=-=-=-=-=-=-=-
