Skip to content

Adding a new Source file to be tracked via vcs instead of lookaside cache #2365

@LecrisUT

Description

@LecrisUT

What happened? What is the problem?

The current workflow seems to be that any file mentioned in Source will be uploaded to the lookaside cache, unless the file is already in the dist-git vcs.

packit/packit/api.py

Lines 1632 to 1634 in 2e75e6f

if not archive_path.exists() or local_archive in [
path for path, _ in self.dg.local_project.git_repo.index.entries
]:

But if we want to add a new file to be tracked by vcs, e.g. Source: pkg.service, than it will automatically be added to the lookaside cache instead of vcs.

What did you expect to happen?

Have some interface to control this. Not sure how that should look like, either:

  • opt-in for the files/glob-patterns to upload to the lookaside cache
  • opt-in for the files (or only Source) files to be tracked by vcs

I am rather inclined for the former, but how would one deal with Source0 archive, especially since the pattern is hard to predict, e.g. *.crate for rust

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!)

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions