On Sat, 7 Jun 2025 10:29:41 +0300 "Kim B. Heino" <b...@bbbs.net> wrote:
Hi,

It's been a month. Any progress?



Hi Kim,

Sorry for the long delay. Unfortunately, it seems Jeremy is currently unavailable for sponsoring given their lack of follow up on this bug.

To move things along:

 1) I have granted you commit access (developer) to
    https://salsa.debian.org/debian/foomuuri in case you want to move
    the packaging there.

    If you are not planning to move the packaging there (although, I
    hope you will), the `Vcs-*` fields should be updated to the repo
    used.


 2) I am ok with sponsoring your package in its current form, though I
    would like to confirm with you that you are okay targeting unstable.

    We are in the hard freeze, so there is no guarantee that the upload
    will make it into testing. Particularly, the [freeze policy] has
    headlines such as "No large/disruptive changes" and "Be careful with
    new upstream releases".

    If the release team and you are not aligned here, `foomuuri` might
    end up blocked and even later removed because of the "unstable and
    testing must be in sync" policy unless we revert back to
    foomuuri/0.27 (usually in the form of 0.28-1+really0.27-1). That is
    the risk of uploading to unstable right now. The release team will
    not be open for negotiation at this point of the freeze, so any
    regressions or problems will likely call for an unconditional
    revert on this side of the release.

    I have limited understanding of foomuuri and also limited time to
    get up to speed, so it will be your call. Do we proceed with the
    unstable upload accepting the risk or would you rather target
    experimental and then we re-upload to unstable after the freeze?

    (If you go for experimental, please update the packaging
    accordingly)


Additionally, one minor tweak you can consider (irrelevant to whether it will be sponsored): When you add build-dependencies for testing only like in 2a88e1c71135d306dcb4185b8e70d00d6ed446a4, consider tagging them with `<!nocheck>` (such as `nftables <!nocheck>`). This means rebuilds that does not run tests can skip those dependencies and as long as you use `dh_auto_test` (via `dh` in this case), the relevant build time skipping of tests are handled for you automatically.

You mention a backport upload as well. The one I can find is https://salsa.debian.org/kimheino/foomuuri/-/commits/bookworm-backports?ref_type=heads. If so, then that is currently not actionable as the version being uploaded to backports must be in testing already and 0.28 is not. If you are still aiming for this, then foomuuri must be uploaded to unstable and migrate before I can help there. Alternatively, you might be able to use -backports-sloppy, but I do not know the rules of that nor do I plan on using bandwidth on learning them, so that would be a conversation with a different sponsor.


Hope that was helpful. Once you have answered/handled 2), we can proceed with the upload.


Best regards,
Niels


[freeze policy]: https://release.debian.org/testing/freeze_policy.html

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to