neuro-sig / NeuroFedora

#552 Using packit for some package updates (simpler python packages?)
Closed: Fixed by ankursinha. Opened by ankursinha.

Closed: Fixed
Reopen Issue

From the devel list post:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2F4NA62YHN2DMTECCSCT62MDOZWCGTSN/

2) Even better is Packit
  https://packit.dev/
  You have many ways to use it. My favorite way is to use pull-from-upstream
  https://packit.dev/posts/pull-from-upstream/
  You just make sure you have record in https://release-monitoring.org/ and then put
.packit.yaml in Fedora's dist-git.
And when upstream has a new release you will receive a pull request to
src.fedoraproject.org for all configure branches.
And when it merges it (can) build in Koji and submit Bodhi update for you.
  With Packit you can use full automation or only some steps. And combine it as you like
it. If you do not like
triggereing by release monitoring, you can initiate it from command line. It is up to
you.

Maybe we could use it for simpler python packages where we're fairly confident that minor version updates etc. are trivial and can be automated?

I haven't used it myself, but if it opens PRs, we still review the changes and decide if the update should be accepted.

Metadata Update from @ankursinha:
- Issue assigned to major

https://packit.dev/docs/fedora-releases-guide/#pull-from-upstream-job

looks simple enough: could someone do a quick check for this PR:

https://src.fedoraproject.org/rpms/snakemake/pull-request/19

It seems to work well. A few notes:

  • for the automated release-monitoring.org triggered workflow: make sure release-monitoring.org has the correct version prefix. For example, if the github tag is v1.23, v should be specified as the version prefix there. The bugs seem to be opened correctly even if this is not set, but packit cannot then figure out the right tag to checkout
  • also, if the tag is v1.2..., we need to set the upstream_tag_template: v{version}, See: https://src.fedoraproject.org/fork/mfocko/rpms/snakemake/blob/rawhide/f/.packit.yaml
  • packit bug: for manual triggers, it currently picks up packit config from the PR branch where the comment was made, instead of main: https://github.com/packit/packit-service/issues/2115
  • it'll start supporting full rpmautospec bits (%autoreleaes -b .. etc.) from Tuesday when a new deployment is made: the workers didn't have some package that was required to do this: https://github.com/packit/packit-service/pull/2142
  • the koji build task also works, but the dashboard doesn't currently show it: https://github.com/packit/dashboard/issues/214 + https://src.fedoraproject.org/rpms/python-datalad/blob/rawhide/f/.packit.yaml
  • it currently does not mention the bugs in the commits, so we need to link them manually to the bodhi updates etc. to close them: https://github.com/packit/packit/issues/1920

I think that's all. The packit dashboard is here: https://dashboard.packit.dev/jobs

The usual reminder that even when using this automation, we must:

  • check that the new updated version does not contain non FOSS
  • check that the license etc. has not changed
  • run an impact check to ensure that we don't break other packages
  • test the package locally to make sure it works

I filed an issue about this too:

https://github.com/packit/packit/issues/2035

Metadata Update from @ankursinha:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/neuro/NeuroFedora//issues/552
Metadata

D: Normal S: Needs review T: Software

None
None
Low
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.