action #14038
closed[perl] repo-checker must ensure two packages can't produce the same output
0%
Description
We had just seen the following issue in Tumbleweed:
- the long existing (source package libisoburn produces several subpackages. For this issue important is that it creates a xorriso-%version.rpm
- a new submission to Tumbleweed introduced a source package 'xorriso'. It produced a xorriso-%{verion}.rpm
repo-checker did not see this issue and accepted the new xorriso package.
For OBS, it is totally random which of the two resulting xorriso.rpm will be published: it depends on the build order which one wins.
Updated by lnussel over 8 years ago
- Category set to Development
- Estimated time set to 40.00 h
Same problem in leap now. Following packages are duplicates:
kjots
kjots-debuginfo
liblua5_2
liblua5_2-32bit
liblua5_2-debuginfo
liblua5_2-debuginfo-32bit
libopenssl0_9_8
libopenssl0_9_8-32bit
libopenssl0_9_8-debuginfo
libopenssl0_9_8-debuginfo-32bit
liburcu-devel
monitoring-plugins-snmp
novell-sound-theme
open-isns
open-isns-debuginfo
python-thrift
python-thrift-debuginfo
syslinux-debuginfo-x86_64
syslinux-debuginfo-x86_64
syslinux-x86_64
syslinux-x86_64
virt-v2v
Updated by mlin7442 over 8 years ago
repo-checker does not enable for Leap, why it is related?
Updated by dimstar about 2 months ago
- Status changed from New to Closed
prod builder refuses to generate an FTP tree by now that has duplicate binaries. Not perfect, but at least we catch those 'im time'