upstream_package_name required?
See original GitHub issue[dhodovsk@shiny avocado]$ cat .packit.yml
specfile_path: python-avocado.spec
[dhodovsk@shiny avocado]$ packit srpm
Following kwargs were not processed:{'authentication': {'github.com': {'token': '.....'}, 'pagure': {'token': '...', 'instance_url': 'https://src.fedoraproject.org'}}}
Packit 0.7.2.dev172+g29b9412 is being used.
Input is a directory: /tmp/avocado
Input directory is an upstream repository.
ERROR Preparing of the upstream to the SRPM build failed: "upstream_package_name" is not set: unable to fix the spec file; please set it.
In PR it works without it - https://github.com/dhodovsk/avocado/pull/1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Set up upstream sources for your feed - Azure Artifacts
Select the package types you want to use, select the View and name your upstream source. Select Save when you are done.
Read more >UpstreamGuide
http://bugs.debian.org/package where package is the name of the package in Debian. This page lists all bugs that have been reported by Debian ...
Read more >Requesting a package version with upstream repositories
If a requested package version is found in an upstream repository, a reference to it is retained and is always available from the...
Read more >dh_make - prepare upstream source for Debian packaging
-p, --packagename name Force the package name to be name, good for packages with hyphens in their name or other strangeness. You can...
Read more >What do the different version elements specify in debian ...
This part is omitted for upstream Debian packages, i.e. packages (normally ... Different releases may need different meta information, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It works:
packit-service/ogr#318 has been fixed.
@dhodovsk can this be closed? If so, please do. Thanks