Request History
yast-team created request
submit new version 3.3.0
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:184"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:184
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added factory-repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
factory-repo-checker reopened review
Execution plan: YaST:Head/openSUSE_Factory
can't install yast2-rear-3.3.0-1.1.noarch:
nothing provides yast2-storage-ng needed by yast2-rear-3.3.0-1.1.noarch
Execution plan: YaST:Head/openSUSE_Tumbleweed
can't install yast2-rear-3.3.0-1.1.noarch:
nothing provides yast2-storage-ng needed by yast2-rear-3.3.0-1.1.noarch
dimstar_suse set openSUSE:Factory:Staging:E as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:E"
dimstar_suse accepted review
Moved to openSUSE:Factory:Staging:E
factory-repo-checker reopened review
Couldn't find a rpmlint.log in the build results in /home/repochecker/co/openSUSE:Factory:Staging:E/libstorage-ng. This is mandatory
can't install yast2-update-3.3.0-1.1.x86_64:
package libstorage-ng1-3.3.0-5.1.x86_64 obsoletes libstorage7 provided by libstorage7-2.26.12-1.5.x86_64
package libstorage-ng-ruby-3.3.0-5.1.x86_64 requires libstorage-ng.so.1()(64bit), but none of the providers can be installed
package libstorage-ng-ruby-3.3.0-5.1.x86_64 requires libstorage-ng1 = 3.3.0, but none of the providers can be installed
package yast2-storage-3.2.17-1.2.x86_64 requires libstorage.so.7()(64bit), but none of the providers can be installed
package yast2-storage-3.2.17-1.2.x86_64 requires libstorage7 >= 2.26.6, but none of the providers can be installed
package yast2-storage-ng-3.3.0-2.1.noarch requires libstorage-ng-ruby, but none of the providers can be installed
package yast2-installation-3.3.5-1.1.noarch requires yast2-storage >= 2.24.1, but none of the providers can be installed
package yast2-update-3.3.0-1.1.x86_64 requires yast2-storage-ng >= 0.1.32, but none of the providers can be installed
package yast2-update-3.3.0-1.1.x86_64 requires yast2-installation, but none of the providers can be installed
found conflict of libstorage-ng-python-3.3.0-5.1.x86_64 with libstorage-python-2.26.12-1.5.x86_64:
- /usr/lib64/python2.7/site-packages/_storage.so
- /usr/lib/python2.7/site-packages/storage.py
- /usr/lib/python2.7/site-packages/storage.pyc
- /usr/lib/python2.7/site-packages/storage.pyo
found conflict of libstorage-ng-ruby-3.3.0-5.1.x86_64 with libstorage-ruby-2.26.12-1.5.x86_64:
- /usr/lib64/ruby/vendor_ruby/2.4.0/x86_64-linux-gnu/storage.so
found conflict of yast2-storage-3.2.17-1.2.x86_64 with yast2-storage-ng-3.3.0-2.1.noarch:
- /usr/share/YaST2/clients/inst_disk_proposal.rb
- /usr/share/YaST2/clients/inst_prepdisk.rb
- /usr/share/YaST2/clients/partitions_proposal.rb
- /usr/share/YaST2/clients/storage.rb
- /usr/share/YaST2/scrconf/etc_mtab.scr
factory-repo-checker reopened review
Couldn't find a rpmlint.log in the build results in /home/repochecker/co/openSUSE:Factory:Staging:E/libstorage-ng. This is mandatory
Couldn't find a rpmlint.log in the build results in /home/repochecker/co/openSUSE:Factory:Staging:E/yast2-country. This is mandatory
Couldn't find a rpmlint.log in the build results in /home/repochecker/co/openSUSE:Factory:Staging:E/yast2-network. This is mandatory
can't install yast2-update-3.3.0-1.1.x86_64:
package libstorage-ng1-3.3.0-5.1.x86_64 obsoletes libstorage7 provided by libstorage7-2.26.12-1.5.x86_64
package libstorage-ng-ruby-3.3.0-5.1.x86_64 requires libstorage-ng.so.1()(64bit), but none of the providers can be installed
package libstorage-ng-ruby-3.3.0-5.1.x86_64 requires libstorage-ng1 = 3.3.0, but none of the providers can be installed
package yast2-storage-3.2.17-1.2.x86_64 requires libstorage.so.7()(64bit), but none of the providers can be installed
package yast2-storage-3.2.17-1.2.x86_64 requires libstorage7 >= 2.26.6, but none of the providers can be installed
package yast2-storage-ng-3.3.0-2.1.noarch requires libstorage-ng-ruby, but none of the providers can be installed
package yast2-installation-3.3.5-1.1.noarch requires yast2-storage >= 2.24.1, but none of the providers can be installed
package yast2-update-3.3.0-1.1.x86_64 requires yast2-storage-ng >= 0.1.32, but none of the providers can be installed
package yast2-update-3.3.0-1.1.x86_64 requires yast2-installation, but none of the providers can be installed
found conflict of libstorage-ng-python-3.3.0-5.1.x86_64 with libstorage-python-2.26.12-1.5.x86_64:
- /usr/lib64/python2.7/site-packages/_storage.so
- /usr/lib/python2.7/site-packages/storage.py
- /usr/lib/python2.7/site-packages/storage.pyc
- /usr/lib/python2.7/site-packages/storage.pyo
found conflict of libstorage-ng-ruby-3.3.0-5.1.x86_64 with libstorage-ruby-2.26.12-1.5.x86_64:
- /usr/lib64/ruby/vendor_ruby/2.4.0/x86_64-linux-gnu/storage.so
found conflict of yast2-storage-3.2.17-1.2.x86_64 with yast2-storage-ng-3.3.0-2.1.noarch:
- /usr/share/YaST2/clients/inst_disk_proposal.rb
- /usr/share/YaST2/clients/inst_prepdisk.rb
- /usr/share/YaST2/clients/partitions_proposal.rb
- /usr/share/YaST2/clients/storage.rb
- /usr/share/YaST2/scrconf/etc_mtab.scr
factory-repo-checker accepted review
Migrated to new repo checker
dimstar_suse added repo-checker as a reviewer
Add new repo-checker review
jengelh declined review
no reviewer seems willing to ack it, and the submitter isn't willing to fix it. This seems like a classical lose-lose situation :-D
jengelh declined request
no reviewer seems willing to ack it, and the submitter isn't willing to fix it. This seems like a classical lose-lose situation :-D
jengelh reopened request
dimstar accepted review
repo-checker accepted review
cycle and install check passed
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory
Someone better adjust the description of yast2-storage-ng not to be an example if it gets seriously used like yast2-rear suggests.
The description needs to be changed in a different package - so why decline this request?
see the decline text (comments still are a second-class citizen in OBS sadly).
Where is the URL? Please also use full source URLs.
a) none of the yast2 packages do - the tarball is fed by jenkins
b) it is not mandated - if it does not fit the process, it does not fit