On Tue, 12 Nov 2024 at 12:25, Enrico Jörns <[email protected]> wrote:
> Last time I updated this, I assumed my version bump patch was not taken 
> because patchtest complained
> about a missing description.
> Thus I took a look at other version bumps and decided it might be desired to 
> have a short note on
> the main changes or a link to the changelog in the commit message.
> Is that the case? Are the changes I see in other recipes all generated by 
> hand?

The changelog is not required. And missing description is not a hard
blocker; it's at the discretion of the submitter to add something.

> Another thing I noticed is that I did not get a mail from the AUH for 
> barebox-tools 2024.10 so far.
> (But this would update barebox-tools only, maybe for the same reason the 
> maintainer check failed
> initially (barebox recipe not being a default provider)).

The last AUH run got somehow stuck and was killed on timeout. I'd wait
and see what happens in three days time.

> > I think we need to put SRC_URI items into a shared .inc file,
> > otherwise people will easily forget about this, and update one recipe
> > but not the other.
>
> Looks like this currently is the way to ensure this, yes. Can the upgrade 
> helper handle this
> properly? I wouldn't yet do it now to not interfere with these patches, but 
> If I should step in,
> just let me know.

Yes. AUH detects if recipes share an include file, and if so, updates
them in lockstep and makes a single patch.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#207046): 
https://lists.openembedded.org/g/openembedded-core/message/207046
Mute This Topic: https://lists.openembedded.org/mt/109531959/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to