Bug 1777494

Created attachment 1640162 [details]
[patch] Update to 18.5.0 (#1777494)

the-new-hotness/release-monitoring.org's scratch build of python-cherrypy-18.5.0-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=39378662

Latest upstream release: 18.6.0
Current version/release in rawhide: 18.4.0-2.fc32
URL: https://pypi.python.org/pypi/CherryPy

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/3799/

Created attachment 1679743 [details]
[patch] Update to 18.6.0 (#1777494)

the-new-hotness/release-monitoring.org's scratch build of python-cherrypy-18.6.0-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=43497530

This depends on https://src.fedoraproject.org/rpms/python-jaraco-collections/pull-request/1

Matthias merged the above jaraco-collections PR#1, and I am able to build 18.6.0 for Fedora 33 with the tests re-enabled now.

Matthias would you please merge my changes here? https://src.fedoraproject.org/rpms/python-cherrypy/pull-request/11

There is a build failure, may require another kick after some time.

DEBUG file_util.py:30:  touching file: /var/lib/mock/f34-build-25288674-2871276/root/.initialized
INFO backend.py:377:  Running in chroot: ['fedpkg', 'sources']
DEBUG util.py:624:  child environment: None
DEBUG util.py:542:  Executing command: ['fedpkg', 'sources'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False
DEBUG util.py:444:    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
DEBUG util.py:444:                                   Dload  Upload   Total   Spent    Left  Speed
DEBUG util.py:444:  
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
DEBUG util.py:444:  curl: (22) The requested URL returned error: 404 Not Found
DEBUG util.py:598:  Child return code was: 22
DEBUG util.py:169:  kill orphans
DEBUG util.py:624:  child environment: None
DEBUG util.py:542:  Executing command: ['/bin/umount', '-n', '-

It seems the source was missing, even if the sources file contained it.

Yeah, sorry, I should have uploaded it when I published the pull request.

I'm not sure what the "proper" etiquette is in these cases where I'm not the official package maintainer.

(In reply to Ken Dreyer (Red Hat) from comment #11)
> Yeah, sorry, I should have uploaded it when I published the pull request.
> 
> I'm not sure what the "proper" etiquette is in these cases where I'm not the
> official package maintainer.

no worries. Tbh, I'm not aware of any etiquette here, it is pretty much undefined. Personally, I wouldn't be mad if someone (aka proven packager) pushes changes directly. At the end, it's all in git. Thanks again for your PR.