specfile
specfile copied to clipboard
A library for parsing and manipulating RPM spec files
updates: - [github.com/asottile/pyupgrade: v3.15.0 → v3.17.0](https://github.com/asottile/pyupgrade/compare/v3.15.0...v3.17.0) - [github.com/psf/black: 24.2.0 → 24.10.0](https://github.com/psf/black/compare/24.2.0...24.10.0) - [github.com/pre-commit/pre-commit-hooks: v4.5.0 → v5.0.0](https://github.com/pre-commit/pre-commit-hooks/compare/v4.5.0...v5.0.0) - [github.com/PyCQA/flake8: 7.0.0 → 7.1.1](https://github.com/PyCQA/flake8/compare/7.0.0...7.1.1) - [github.com/pre-commit/mirrors-mypy: v1.8.0 → v1.11.2](https://github.com/pre-commit/mirrors-mypy/compare/v1.8.0...v1.11.2) - [github.com/teemtee/tmt.git: 1.31.0 →...
Currently, it is possible to create an object of `Specfile` like this: ```python # using an absolute path specfile = Specfile('/tmp/test.spec') # using a relative path and a different sourcedir...
Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/python-specfile.git): | dist-git branch | error | | --------------- | ----- | | `epel9` | See https://dashboard.stg.packit.dev/results/propose-downstream/1426 | | `f38` | See https://dashboard.stg.packit.dev/results/propose-downstream/1428...
### Description Right now, the user has to implement release bumping, which can be quite complicated. It would be nice if we could copy logic from rpmdev-bumpspec. That would honor...
### What happened? What is the problem? In case of [pg_auto_failover.spec](https://src.fedoraproject.org/rpms/pg_auto_failover/blob/9c7e2b1a9af7f174121b5f98cd5aaaf3793e780e/f/pg_auto_failover.spec#_50) or [xorgxrdp.spec](https://src.fedoraproject.org/rpms/xorgxrdp/blob/a2e0fe05f914afb0264e8da7e36fe6e7baa2ef34/f/xorgxrdp.spec#_34) begin of condition remains in main `package` section while `%endif` goes to sub-package. So you get `IndexError`...
### What happened? What is the problem? Looks like pytest fails in two units. ### What did you expect to happen? pytest should not fail. ### Example URL(s) N/A ###...
### Description We had some hiccups with using specfile initially: https://github.com/fedora-copr/copr/issues/2848 -> There are several types of tag resolution "expanded", "expanded with RPM", "unexpanded", some values can be defined multiple...
### Description Currently, it's possible to do this via a file path. In my use case, all I'm doing is fetching the specfile for multiple packages via OSC API and...