![](https://seccdn.libravatar.org/avatar/a961d54b41a44a48c5241aab3571178f.jpg?s=120&d=mm&r=g)
On Mon, Apr 18, Dominique Leuenberger / DimStar wrote:
On Mon, 2016-04-18 at 12:46 +0200, Olaf Hering wrote:
On Mon, Apr 18, Dominique Leuenberger / DimStar wrote:
https://build.opensuse.org/package/view_file/openSUSE:Factory/_product/obsol...
Thanks.
How are packages entered there? Unrelated to ffmpeg-devel, 'zypper packages --orphaned' lists a few items which should be part of that list.
It's auto-generated based on 'released produced to TW upgrade path'. I don't think we have a TW(Random)-to-TW upgrade test case.
Is there a way to add known-broken packages manually? Since some time three broken packages are reported during dup: libhdf5-10 libhdf5_hl10 liborcus-0_10-0 File /usr/lib64/libhdf5.so.10.1.0 from install of libhdf5-10-1.8.16-3.1.x86_64 (oss) conflicts with file from package libhdf5-11-1.8.16-1.1.x86_64 (@System) File /usr/lib64/libhdf5_hl.so.10.0.2 from install of libhdf5_hl10-1.8.16-3.1.x86_64 (oss) conflicts with file from package libhdf5_hl11-1.8.16-1.1.x86_64 (@System) File /usr/lib64/liborcus-0.11.so.0.0.0 from install of liborcus-0_11-0-0.11.0-2.2.x86_64 (oss) conflicts with file from package liborcus-0_10-0-0.11.0-1.2.x86_64 (@System) File /usr/lib64/liborcus-mso-0.11.so.0.0.0 from install of liborcus-0_11-0-0.11.0-2.2.x86_64 (oss) conflicts with file from package liborcus-0_10-0-0.11.0-1.2.x86_64 (@System) File /usr/lib64/liborcus-parser-0.11.so.0.0.0 from install of liborcus-0_11-0-0.11.0-2.2.x86_64 (oss) conflicts with file from package liborcus-0_10-0-0.11.0-1.2.x86_64 (@System) File /usr/lib64/liborcus-spreadsheet-model-0.11.so.0.0.0 from install of liborcus-0_11-0-0.11.0-2.2.x86_64 (oss) conflicts with file from package liborcus-0_10-0-0.11.0-1.2.x86_64 (@System) Olaf -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org