Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2048101 - spectrographic provides python3dist(spectrographic) = 0
Summary: spectrographic provides python3dist(spectrographic) = 0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spectrographic
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artur Frenszek-Iwicki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: python3dist0
TreeView+ depends on / blocked
 
Reported: 2022-01-29 12:26 UTC by Miro Hrončok
Modified: 2022-12-01 03:18 UTC (History)
1 user (show)

Fixed In Version: spectrographic-0.9.3-11.fc37 spectrographic-0.9.3-9.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-01 01:30:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2022-01-29 12:26:10 UTC 
The package spectrographic has the following automatic provide:

  python3dist(spectrographic) = 0

It appears that the actual package version was lost during the packaging process. 

In most cases, this is caused by using a Source that misses version information, e.g. A GitHub tarball when the project uses setuptools_scm or pbr. See https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_source_files_from_pypi

This bugzilla was created in a batch, so it does not have information about the exact cause for this package. If you need help figuring out why this happens in this particular package, feel free to ask.
Comment 1 Ben Cotton 2022-02-08 20:25:48 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.
Comment 2 Fedora Update System 2022-11-22 12:45:57 UTC 
FEDORA-2022-bd9b3fb276 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bd9b3fb276
Comment 3 Fedora Update System 2022-11-22 13:10:01 UTC 
FEDORA-2022-29fc719877 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-29fc719877
Comment 4 Fedora Update System 2022-11-23 02:19:34 UTC 
FEDORA-2022-29fc719877 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-29fc719877`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-29fc719877

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2022-11-23 03:17:00 UTC 
FEDORA-2022-bd9b3fb276 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-bd9b3fb276`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bd9b3fb276

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-12-01 01:30:10 UTC 
FEDORA-2022-bd9b3fb276 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 7 Fedora Update System 2022-12-01 03:18:05 UTC 
FEDORA-2022-29fc719877 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.