question-mark
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 requires sources file in dist-git

See original GitHub issue

When we use propose-update for a new package (e.g. requre in this case), the sources file is created only when we upload archive to the lookaside-cache => since we do that only once, it’s created only for the first branch and the command fails for the other ones.

The temporary solution is to use --force-new-sources option.

10:27:12.565 base_git.py       DEBUG  Running ActionName.post_upstream_clone hook.
10:27:12.565 base_git.py       DEBUG  Running ActionName.post_upstream_clone.
10:27:12.565 base_git.py       DEBUG  Running default implementation for ActionName.post_upstream_clone.
Checking out upstream version 0.4.0.
10:27:12.576 base_git.py       DEBUG  Allowed GPG keys are not set, skipping the verification.
10:27:12.576 base_git.py       DEBUG  Running ActionName.pre_sync hook.
10:27:12.576 base_git.py       DEBUG  Running ActionName.pre_sync.
10:27:12.576 base_git.py       DEBUG  Running default implementation for ActionName.pre_sync.
Using 'f32' dist-git branch.
10:27:12.586 distgit.py        DEBUG  About to update branch 'f32'.
10:27:14.670 api.py            DEBUG  README: /tmp/packit-dist-git6ytaz_94/README.packit
10:27:14.672 base_git.py       DEBUG  Running ActionName.prepare_files.
10:27:14.672 base_git.py       DEBUG  Running default implementation for ActionName.prepare_files.
WARNING  There is not spec file downstream: Specfile /tmp/packit-dist-git6ytaz_94/python-requre.spec not found., copying the one from upstream.
08:27:14.819 sync.py           DEBUG  Copy synced files [RawSyncFilesItem(src=/var/home/flachman/Projects/packit-service/requre/.packit.yaml, dest=/tmp/packit-dist-git6ytaz_94/.packit.yaml, dist_is_dir=False)]
08:27:14.819 sync.py           DEBUG  src = /var/home/flachman/Projects/packit-service/requre/.packit.yaml, dest = /tmp/packit-dist-git6ytaz_94/.packit.yaml
Copying /var/home/flachman/Projects/packit-service/requre/.packit.yaml to /tmp/packit-dist-git6ytaz_94/.packit.yaml.
08:27:14.951 distgit.py        DEBUG  Upstream archive name: requre-0.4.0.tar.gz
Archive 'requre-0.4.0.tar.gz' found in lookaside cache (skipping upload).
08:27:15.324 distgit.py        DEBUG  Upstream archive name: requre-0.4.0.tar.gz
ERROR    [Errno 2] No such file or directory: '/tmp/packit-dist-git6ytaz_94/sources'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/packit/cli/utils.py", line 62, in covered_func
    func(config=config, *args, **kwargs)
  File "/usr/lib/python3.8/site-packages/packit/cli/update.py", line 129, in update
    api.sync_release(
  File "/usr/lib/python3.8/site-packages/packit/api.py", line 256, in sync_release
    self._handle_sources(
  File "/usr/lib/python3.8/site-packages/packit/api.py", line 390, in _handle_sources
    if self.dg.upstream_archive_name not in sources_file.read_text():
  File "/usr/lib64/python3.8/pathlib.py", line 1232, in read_text
    with self.open(mode='r', encoding=encoding, errors=errors) as f:
  File "/usr/lib64/python3.8/pathlib.py", line 1218, in open
    return io.open(self, mode, buffering, encoding, errors, newline,
  File "/usr/lib64/python3.8/pathlib.py", line 1074, in _opener
    return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/packit-dist-git6ytaz_94/sources'
08:27:15.388 local_project.py  DEBUG  Cleaning: /tmp/packit-dist-git6ytaz_94

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
TomasTomecekcommented, Sep 25, 2020

we could potentially check for presence of the sources file and run new-sources if it’s not present, WDYT?

0reactions
stale[bot]commented, Jun 2, 2021

This issue has been marked as stale because it hasn’t seen any activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are never marked as stale.)

Read more comments on GitHub >

github_iconTop Results From Across the Web

dist-git/dist-git.spec at main · release-engineering/dist ... - GitHub
Summary: Package source version control system ... Requires: (dist-git-selinux if selinux-policy-targeted) ... %systemd_postun dist-git.socket. %files.
Read more >
2019 - Packit
packit propose-update — Opens a pull request in dist-git for the latest upstream release of a ... You need to have spec file...
Read more >
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 ...
Read more >
Is dist-git a good place for work? - devel - Fedora Mailing-Lists
Dist-git would still be the authoritative source and a place where ... need to take a closer look) The spec file is being...
Read more >
dist-git explained - YouTube
Miroslav Suchý explains the dist-git concept and how it is used by Fedora Linux packagers.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found