Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1422979

Summary: tarball packaging issues -> pypi different data
Product: [oVirt] ovirt-engine-sdk-python Reporter: Sandro Bonazzola <sbonazzo>
Component: BuildAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Pavol Brilla <pbrilla>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, juan.hernandez, mperina, omachace, sbonazzo
Target Milestone: ovirt-4.1.1Flags: rule-engine: ovirt-4.1+
Target Release: 4.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-ovirt-engine-sdk4-4.1.1-1.el7ev Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:38:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2017-02-16 17:32:36 UTC
Description of problem:
https://pypi.io/packages/source/o/ovirt-engine-sdk-python/ovirt-engine-sdk-python-4.1.0.tar.gz 

is missing examples which are instead packaged in 

http://resources.ovirt.org/pub/ovirt-4.1/src/python-ovirt-engine-sdk4/ovirt-engine-sdk-python-4.1.0.tar.gz

not sure if pypi archive is corrupted or why they differ.
In principle, the 2 tarball should have same checksum.

Comment 1 Juan Hernández 2017-02-16 17:41:34 UTC
Those are two different kinds or tarballs. The first is the source distribution, generated by 'setup.py sdist'. The second is a tarball generated by our automation scripts, not really useful. We should probably stop generate that second tarball using 'setup.py sdist' as well.

Is this causing a real problem?

Comment 2 Sandro Bonazzola 2017-02-17 14:13:52 UTC
(In reply to Juan Hernández from comment #1)
> Those are two different kinds or tarballs. The first is the source
> distribution, generated by 'setup.py sdist'. The second is a tarball
> generated by our automation scripts, not really useful. We should probably
> stop generate that second tarball using 'setup.py sdist' as well.
> 
> Is this causing a real problem?

Just seen it while building CentOS Virt SIG rpm. In CentOS Virt SIG rpm 4.0 I was using pypi tar.gz as source and I had the example directory shipped within the rpm.
In 4.1 pypi version the example directory is not shipped anymore so I noticed the issue.

Comment 3 Juan Hernández 2017-02-17 14:41:13 UTC
Strange, I think that the examples have never been included in the PyPI version. They should be now.

Comment 4 Pavol Brilla 2017-04-11 10:47:01 UTC
Check of package: 

https://pypi.io/packages/source/o/ovirt-engine-sdk-python/ovirt-engine-sdk-python-4.1.3.tar.gz 

contains examples directory.

But those 2 sources dont have same checksum

Source: https://pypi.io/packages/...
$ md5sum ovirt-engine-sdk-python-4.1.3.tar.gz 
20874fd9062072879e1786749f6be40f  ovirt-engine-sdk-python-4.1.3.tar.gz

Source: http://resources.ovirt.org/pub/...
$ md5sum ovirt-engine-sdk-python-4.1.3.tar.gz 
6ddf3758cfa7f978811002ce426da4b0  ovirt-engine-sdk-python-4.1.3.tar.gz

Comment 5 Pavol Brilla 2017-04-11 10:54:17 UTC
Check of package: 

https://pypi.io/packages/source/o/ovirt-engine-sdk-python/ovirt-engine-sdk-python-4.1.3.tar.gz 

contains examples directory.

But those 2 sources dont have same checksum

Source: https://pypi.io/packages/...
$ md5sum ovirt-engine-sdk-python-4.1.3.tar.gz 
20874fd9062072879e1786749f6be40f  ovirt-engine-sdk-python-4.1.3.tar.gz

Source: http://resources.ovirt.org/pub/...
$ md5sum ovirt-engine-sdk-python-4.1.3.tar.gz 
6ddf3758cfa7f978811002ce426da4b0  ovirt-engine-sdk-python-4.1.3.tar.gz