Hi Lorenzo, Lorenzo <plorenzo@disroot.org> writes: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "runit-services": > > > * Package name : runit-services > Version : 0.7.0 [snip] > * Import the runscript from mini-httpd-run package: > - change the runscript to use the default config file > - d/control: runit-services Provides mini-httpd-run I'm unfamiliar with runit, but does anything need to be done in the mini-httpd package to support your work in this upload? By the way, thank you for writing such nice commit messages! https://salsa.debian.org/Lorenzo.ru.g-guest/runit-services/-/commit/566393e02ab8010405d14e38c0e02f4bea51afc8 I appreciate the thought and the openness that went into that work. One minor comment here: I'd recommend filing a bug against mini-httpd-run shortly after the upload of runit-services_0.7.0, because otherwise someone might potentially see a neglected package and then adopt it. This bug would make the plan from your commit message more visible and official. It will also give the Quality Assurance team the opportunity to support your plan, and this seems like it will be required for a Request of QA Team (RoQA) removal--unless you adopt mini-httpd-run and file a Request of Maintainer (RoM). Maybe one of these approaches is already part of your plan? Also, thank you for thinking about smoothing the transition for users by using Provides; although, I wonder how this will actually function, because mini-httpd-run's version 1.0+nmu1 >> runit-services' 0.7.0. You're right, Conflicts isn't required and it doesn't seem like Breaks would be appropriate either. Have you considered using versioned Provides? This would make it more clear, in dependency resolution, that mini-httpd-run is now an obsolete cruft package. https://www.debian.org/doc/debian-policy/ch-relationships.html#virtual-packages-provides Alternatively if the transition requires user/sysadmin intervention, then why wouldn't a debian/NEWS file be a good thing? Kind regards, Nicholas
Attachment:
signature.asc
Description: PGP signature