compose-utils

#71 traceback from compose-changelog in rawhide
Closed: Fixed Opened by kevin.

Closed: Fixed
Reopen Issue

compose-utils-0.1.19-1.fc28.noarch

last nights rawhide has: 

Traceback (most recent call last):
  File "/usr/bin/compose-changelog", line 53, in <module>
    run(opts)
  File "/usr/bin/compose-changelog", line 25, in run
    data = changelog.get_changelog(old_compose, new_compose)
  File "/usr/lib/python3.6/site-packages/compose_utils/changelog.py", line 368, in get_changelog
    for i in get_changelog_diff_from_headers(old_package, new_package, max_logs):
  File "/usr/lib/python3.6/site-packages/compose_utils/changelog.py", line 112, in get_changelog_diff_from_headers
    if entry.time < old_time or (entry.time == old_time and new_nvr <= old_nvr):
  File "/usr/lib64/python3.6/distutils/version.py", line 58, in __le__
    c = self._cmp(other)
  File "/usr/lib64/python3.6/distutils/version.py", line 337, in _cmp
    if self.version < other.version:
TypeError: '<' not supported between instances of 'int' and 'str'

and the resulting email to devel/test lists is empty. ;(

This is a rather strange error. Getting changelog from Singular-4.1.0p3-9.fc29.src.rpm returns some unexpected data.

Spec file has this entry:

* Tue May 01 2018 Jonathan Wakely <jwakely@redhat.com> - 4.1.0p3-9
- Add BuildRequires: boost-python2-devel to fix build with boost-1.66.0-7.fc29

However rpm itself returns something else:

$ rpm -qp Singular-4.1.0p3-9.fc29.src.rpm --changelog | head -n2
* Tue May 01 2018 Jonathan Wakely <jwakely@redhat.com> - -9
- Add BuildRequires: boost-python2-devel to fix build with boost-1.66.0-7.fc29

The -9 is confusing the version comparison and is treated as a number.

This looks to me like a bug in RPM. I opened RHBZ#1585589. There still needs to be some error handling in the script to work around this though.

This should be fixed in compose-utils 0.1.20-1

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

I'm not sure what's going on. The same error happened again on Rawhide 20180610.n.0, but the traceback does not match the code in 0.1.20.

Here's the traceback: https://lists.fedoraproject.org/archives/list/releng-cron@lists.fedoraproject.org/thread/Y64RMFFS4ISBHNXKQZZPMXSV2HO7PRGK/

I'm not sure what's going on. The same error happened again on Rawhide 20180610.n.0, but the traceback does not match the code in 0.1.20.

Thats because I saw the traceback in 20180610.n.0 and was reminded to update compose-utils to fix this issue, so I then upgraded it to 0.1.20. The traceback happened at compose time when it was still 0.1.19. Sorry for confusion there...

Metadata
None
None
None
None
None
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.