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 2048091

Summary:	python3-javabridge provides python3dist(javabridge) = 0
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	python-javabridge	Assignee:	Raphael Groner <projects.rg>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	36	CC:	ksurma, projects.rg
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-11 15:30:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2048077

Description Miro Hrončok 2022-01-29 12:18:19 UTC

The package python3-javabridge has the following automatic provide:

  python3dist(javabridge) = 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 Raphael Groner 2022-01-30 18:29:55 UTC

I fail to see any relation to source tarball as there's definitely a version given as well in %prep to extract. 
To build, standard with macro %py3_build is used. Why setuptools_scm then as there's no BuildRequires for that?

Comment 2 Miro Hrončok 2022-01-30 21:14:05 UTC

setup.py has a complicated get_version() used. it tries to load info from git (and fails), then it tries javabridge/_version.py and fails as well, it returns None which is turned into 0.

Comment 3 Raphael Groner 2022-02-07 17:12:30 UTC

(In reply to Miro Hrončok from comment #2)
> setup.py has a complicated get_version() used. it tries to load info from
> git (and fails), then it tries javabridge/_version.py and fails as well, it
> returns None which is turned into 0.

Thanks for debugging. We should file that to upstream and ask for a good official version.

Comment 4 Ben Cotton 2022-02-08 20:08:36 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 5 Raphael Groner 2022-03-08 21:37:50 UTC

Well, first guess would be PEP 440 but there's no _version.py available to read from.

Comment 6 Karolina Surma 2022-11-11 15:30:49 UTC

This is a dead package.