Bug#1134471: RFS: ruby-chef-utils/19.2.12-0.1 [RC] -- Basic utility functions for Core Chef Infra development

Norwid Behrnd <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.general,gmane.linux.debian.devel.mentors
Message-ID <fJnk6Vicg0bPuPl63UG152D1mBKkzJIqTo-UjIKicYX4qc6p_eQaUSDctTCXaAgf-wyecTx6gu7KRl03ctK3QisghdgFH7Co9X_8hV7mP7E=@protonmail.com>
Hello Tobi

Thank you for joining the thread.

> NMUs should be minimal [1], every fix needs to target (a reported) bug.

If you recommend to split the current results, to address one issue per one NMU at a time, a sequence plausible to me could be

1) let debian/salsa-ci.yml work to completion.  For a reason unknown to me, Lucas Nussbaum initiated such a run (September 6, 2025) which however was cancelled.  This was about 4 months after the last upload from the blessed repository on salsa to debian.

2) set d/watch back into action (bug 1127665), perhaps 2b) an update to current syntax Version 5.

3) address that ruby-chef-utils doesn't faithfully build from source (bug 1123467).

4) an upstream update which equally accounts for current policies (d/watch version=4 -> Version: 5, etc).

Surely I could revise the upload, or set up an additional clone of `ruby-chef-utils` in my salsa profile; upload to the mentors page would await passing manual acceptance though intermediate steps would be marked as not passing the current policy.  I do not know if this wanted; let me know if there is a better way (first time if ever NMU).

> Have you checked whether the new upstream version breaks reverse
> depdendencies?

No I did not specifically look into this.  Since the upload by 2026-04-20 passed both the checks of lintian in a local instance (then Debian 13/testing) as well within reason the ones on the mentors page, I presumed there would be no grave break.  I discounted yellow indicators (like d/watch) to "tests on the mentors.net are not yet updated to the current policy".  Test results collected then may be different to ones of today, and an incomplete analysis.

> 
> NMUs needs to be announced to the package maintainer, you'll find
> nmudiff(1) handy for this task. (just tweak the text of nmudiff to
> point to this RFS.)

I recognize this as an error on my side, I did not file an additional NMU bug.   Because <https://tracker.debian.org/pkg/ruby-chef-utils> mentions Priate Praveen as the package's main uploader, I however reached out for him on salsa -- prior to starting the work.  About a month later, I informed him about my RFS for the NMU.  Because the
blessed repository is within the name space of the Debian Ruby Team, I presumed either Pirate Praveen, or another member of the Ruby Team would have a look on this when time is suitable for him / another team member, at <https://salsa.debian.org/ruby-team/ruby-chef-utils/-/merge_requests/2>  So far, no reply from this side however I'll check into nmudiff you recommend.

Since "you can invite, but not force the volunteers" (Andreas Tille, at a packaging workshop at CLT 2026) and given the history of bug 1123467 I left my results for feedback by others and possible continuation (by me, or by others) on the mentors page.

Best regards,
Norwid
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.