Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

propose-update does not find release tarball in dist-git

See original GitHub issue

I’m currently trying to release cockpit-ostree 179 with packit. I’m running into a bug similar to issue #422 but without --dist-git-path:

❱❱❱ PYTHONPATH=~/tmp/packit/ python3 -m packit.cli.packit_base propose-update 
Input is a directory: /home/martin/upstream/cockpit-ostree
Using user-defined script for ActionName.post_upstream_clone: ['make cockpit-ostree.spec']
INFO: Running 'anitya' versioneer
ERROR: Failed to determine latest upstream version!
Check that the package exists on https://release-monitoring.org.
Version in upstream registries is None.
Version in spec file is '179'.
Picking version found in spec file.
Checking out upstream version 179
Using 'master' dist-git branch
INFO: Downloading file from URL https://src.fedoraproject.org/repo/pkgs/cockpit-ostree/cockpit-ostree-178.tar.gz/sha512/b0d940d912bfa81487a4967c5edadc0fb5900a86064fc8b3b0ea75d845c84064b1f022a008cf177677fe148274e7b9c755402fccd187beb44dc0dd1f8aa1cff5/cockpit-ostree-178.tar.gz
100%[=============================>]     1.12M  eta 00:00:00 
Downloaded archive: PosixPath('/tmp/packit-dist-gitf51mwppp/cockpit-ostree-179.tar.gz')
About to upload to lookaside cache
won't be doing kinit, no credentials provided
ERROR    Could not execute new_sources: Path does not exist or is not a file: /tmp/packit-dist-gitf51mwppp/cockpit-ostree-179.tar.gz

ERROR    Command ['fedpkg', 'new-sources', '/tmp/packit-dist-gitf51mwppp/cockpit-ostree-179.tar.gz'] failed
ERROR    Adding new sources failed:
ERROR    `fedpkg new-sources` failed for some reason. Either Fedora kerberos is invalid or there could be network outage.
ERROR    Command ['fedpkg', 'new-sources', '/tmp/packit-dist-gitf51mwppp/cockpit-ostree-179.tar.gz'] failed: Adding new sources failed:

I did kinit, and this is latest upstream master:

❱❱❱ git -C ~/tmp/packit/ rev-parse HEAD
efb466df8567c2050b09f6854b515250ac1dfa7a

So I did fedpkg clone cockpit-ostree to ~/tmp/cockpit-ostree, and used that with --dist-git-branch:

❱❱❱ PYTHONPATH=~/tmp/packit/ python3 -m packit.cli.packit_base propose-update  --dist-git-path ~/tmp/cockpit-ostree/

But this still fails… I’m reopening #422.

Issue Analytics

State:
Created 4 years ago
Comments:13 (11 by maintainers)

Top GitHub Comments

1reaction

TomasTomecekcommented, Aug 2, 2019

@FrNecas https://github.com/packit-service/packit/pull/458 Zuul is nice a guy, he can do it.

1reaction

martinpittcommented, Aug 2, 2019

Haha, I’m honored that cockpit-ostree made it into the test suite 😀

Top Results From Across the Web

packit/CHANGELOG.md at main - GitHub

(#1803); Packit now resets the Release tag during propose-downstream if the version is updated and the Release tag has not explicitly been overridden...

2019 - Packit

packit propose-update — Opens a pull request in dist-git for the latest upstream release of a selected repository. packit watch-releases — Watches events ......

Packit - packaging in Fedora with minimal effort

The command for this first use case is called propose-update (https://github.com/jpopelka/packit/blob/master/docs/propose_update.md). The ...

Python Setup.py - dependency as url to TAR or GIT

whl . I get: ERROR: Could not find a version that satisfies the requirement keras-contrib (from mypack==0.3 ...

How to Manage a Release - Apache Software Foundation

These are tarballs of the Impala source that follow the rules below. ... In particular, release managers are not permitted to store code...