Cannot parse vlc.spec

[xsuchy]

What happened? What is the problem?

With this script:

#!/usr/bin/python3                                                                                                                                                                           
from specfile import Specfile
import sys

# this is dump, but do the work
filename = sys.argv[1]
specfile = Specfile(filename, force_parse=True)

with specfile.sections() as sections:
    print(sections.changelog)

I cannot parse vlc.spec from Fedora.

It fails with this TB:

Created dummy sources for nonexistent files:
rpm-specs/macros.vlc
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 226, in get_rpm_spec
    return rpm.spec(tmp.name, flags)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: can't parse specfile


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 294, in _do_parse
    spec = get_rpm_spec(content, rpm.RPMSPEC_ANYARCH | rpm.RPMSPEC_FORCE)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 228, in get_rpm_spec
    raise RPMException(stderr=stderr) from e
specfile.exceptions.RPMException: /tmp/tmp5e9nmd30: line 51: failed to load macro file rpm-specs/macros.vlc

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 226, in get_rpm_spec
    return rpm.spec(tmp.name, flags)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: can't parse specfile


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/msuchy/projects/license-validate/./print-spec-changelog.py", line 7, in <module>
    specfile = Specfile(filename, force_parse=True)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/specfile/specfile.py", line 72, in __init__
    self._parser.parse(str(self))
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 380, in parse
    self.spec, self.tainted = self._do_parse(content, extra_macros)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 319, in _do_parse
    spec = get_rpm_spec(
           ^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/specfile/spec_parser.py", line 228, in get_rpm_spec
    raise RPMException(stderr=stderr) from e
specfile.exceptions.RPMException: file trigger conditions must begin with '/': %{vlc_plugindir}

What did you expect to happen?

Printing changelog of this specfile.

Example URL(s)

No response

Steps to reproduce

No response

Workaround

• There is an existing workaround that can be used until this issue is fixed.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)

[nforro]

I don't think there is much that can be done about this - parsing depends on a macro that has to start with a /. For example this will succeed:

spec = Specfile('vlc.spec', force_parse=True, macros=[("vlc_plugindir", "/")])

I think for cases like this it would make sense to make Specfile usable even if rpm parsing failed, as proposed in #233 (comment).

[mfocko]

Still relevant.

[xsuchy]

And I can still reproduce it.

[asmorodskyi]

Hi I have such spec file from https://build.opensuse.org/ :

%{?sle15_python_module_pythons}
Name:           python-BTrees
Version:        6.2
Release:        0
Summary:        Persistent B-tree object containers for Python
License:        ZPL-2.1
URL:            https://github.com/zopefoundation/BTrees
Source:         https://files.pythonhosted.org/packages/source/b/btrees/btrees-%{version}.tar.gz
BuildRequires:  %{python_module devel >= 3.10}

on line with BuildRequires it fails with error : specfile.exceptions.RPMException: line 28: Dependency tokens must begin with alpha-numeric, '_' or '/': BuildRequires: %{python_module devel >= 3.10} . This issue looks like culprit for my problem but I am not 100% sure . WDYT ?

[nforro]

it fails with error : specfile.exceptions.RPMException: line 28: Dependency tokens must begin with alpha-numeric, '_' or '/': BuildRequires: %{python_module devel >= 3.10}

The error simply means the python_module macro wasn't expanded. The workaround suggested above will work for you.