Skip to main content

27 posts tagged with "2023"

View All Tags

· One min read

End of the year in Packit

  • We have hit some issues with the firewall rules on the new cluster hosting our production. We are waiting for the required fix that is done outside of our team which should be deployed around January 11th. We will keep you informed about the current status. At the moment we are aware of the issues related to the:
    • pull-from-upstream jobs that have sources hosted at, and
    • jobs running on the in general
  • We have also fixed an issue that caused some Cockpit releases to fail, others might've been affected too, though there are no reports.

· One min read

Week 49 (December 5th – December 11th)

  • We have introduced new configuration options test_command.default_labels and test_command.default_identifier that are used by default when running /packit test comment command without any arguments (instead of specifying them via --labels/--identifier). (packit-service#2270)

  • We have fixed a bug that GithubRelease.url returned an API URL. (ogr#824)

· One min read

We, the packit team, are happy to invite you to our upcoming workshop about pulling upstream releases to Fedora using Packit.

When: Wed, Jan 10, 9:30 AM - Wed, Jan 10, 12:30 PM (GMT+1)

Where: Online!

Who should attend: Anyone who maintains a package in Fedora or EPEL and would like to automate syncing the upstream releases for it. The automation is most suitable for simple packages with straightforward update processes (e.g. without patches, or need to build in side-tags). It works without access to the upstream repository.

No package? It’s not an issue. The workshop can help you understand the Fedora release process and the services involved. During the workshop, you can help someone else automate their package or ask someone around if you can help with the maintenance (that’s usually very welcome!). You can also bring an orphaned package back to life!

Can’t make it this time? You can also follow our documentation and ask for help in case of any issue: (Matrix).

If you want to join us please fill this form or contact us on Matrix, and we will send you further details!

Looking forward to seeing you!

· One min read

Week 48 (November 28th – December 4th)

  • Packit now links the information related to upstream events in PRs opened when syncing a release. (packit#2173)

  • When accessing tags or macro definitions by name, specfile library now takes validity into account when looking for the best match. For example if there are two instances of Version tag, one in the true and one in the false branch of a condition, Specfile.version will always access the one that is in the true branch. This also applies to Packit when syncing a release and updating value of Version tag. (specfile#328)

· One min read

Week 46 (November 14th – November 20th)

  • Packit now supports pre-release version in propose_downstream and pull_from_upstream. A spec file update might be required, see the documentation for more details. (packit#2149)
    • In relation to that, specfile library has a new method, Specfile.update_version(), that allows updating spec file version even if it is a pre-release. (specfile#317)
  • Packit can now check, using the new update_version_mask configuration option, that the proposed version of new release and the current version of the dist-git branch are compatible and sync the dist-git branch only in that case. (packit#2156)
  • Packit is now able to get the version from spec file even if the Version tag is not present in the specfile directly, but e.g. imported from another file. (packit#2157)
  • PACKIT_COPR_PROJECT env var that is exposed to Testing Farm now includes the Copr project of the additional build specified in comment, if present. (packit-service#2253)