Package fstrcmp is gone from TW 20231003 - on purpose?
Hi there, it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore. This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman. TIA, cheers. l8er manfred
On 05.10.2023 13:34, Manfred Hollstein wrote:
Hi there,
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
TIA, cheers.
l8er manfred
bor@bor-Latitude-E5450:~$ osc rq list --type delete --state accepted openSUSE:Factory fstrcmp 1114756 State:accepted By:anag+factory When:2023-10-02T18:07:12 Created by: dirkmueller delete: openSUSE:Factory/fstrcmp Review by User is accepted: licensedigger(licensedigger) Review by User is accepted: factory-auto(factory-auto) Review by Group is accepted: factory-staging(anag+factory) Review by Project is accepted: openSUSE:Factory:Staging:adi:56(anag+factory) Review by Group is accepted: factory-staging(anag+factory) Review by Project is accepted: openSUSE:Factory:Staging:adi:58(anag+factory) Descr: fails to build and is unused Comment: Staging Project openSUSE:Factory:Staging:adi:58 got accepted. bor@bor-Latitude-E5450:~$
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll. Cheers. l8er manfred
On Thursday 2023-10-05 14:27, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll.
You can just bring it back for openSUSE:Factory. If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed build failure reports and there is less of a chance someone swings the package axe.
On Thu, 05 Oct 2023, 15:53:26 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 14:27, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll.
You can just bring it back for openSUSE:Factory. If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed build failure reports and there is less of a chance someone swings the package axe.
I just requested maintainership for d:l:c/fstrcmp. Once I get access rights, I'll resurrect the stuff in PMBS again. Thanks for pointing me in the right direction! Cheers. l8er manfred
On 05.10.2023 17:10, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 15:53:26 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 14:27, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
it looks like the last Tumbleweed snapshot 20231003 removed package fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't contain it anymore.
This package is still needed by Kodi which now shows one orphaned package. Was the removal on purpose? In that case we would have to start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll.
You can just bring it back for openSUSE:Factory. If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed build failure reports and there is less of a chance someone swings the package axe.
I just requested maintainership for d:l:c/fstrcmp. Once I get access rights, I'll resurrect the stuff in PMBS again.
E-h-h ... if you get maintainership, what stops you from submitting it back to Factory? Why keep it external?
Thanks for pointing me in the right direction!
Cheers.
l8er manfred
On Thu, 05 Oct 2023, 16:23:04 +0200, Andrei Borzenkov wrote:
On 05.10.2023 17:10, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 15:53:26 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 14:27, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote:
> > it looks like the last Tumbleweed snapshot 20231003 removed package > fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't > contain it anymore. > > This package is still needed by Kodi which now shows one orphaned > package. Was the removal on purpose? In that case we would have to > start building it for Tumbleweed on Packman.
Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll.
You can just bring it back for openSUSE:Factory. If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed build failure reports and there is less of a chance someone swings the package axe.
I just requested maintainership for d:l:c/fstrcmp. Once I get access rights, I'll resurrect the stuff in PMBS again.
E-h-h ... if you get maintainership, what stops you from submitting it back to Factory? Why keep it external?
You got me wrong. Once I have maintainership, I'll re-create the package in d:l:c and submit it again to openSUSE:Factory. When that is done, I'll re-create the situation in PMBS as it was before. Right now, it's just a stop gap solution so new users will be able to install kodi on TW at all. Cheers. l8er manfred
On Thu, 05 Oct 2023, 16:27:09 +0200, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 16:23:04 +0200, Andrei Borzenkov wrote:
On 05.10.2023 17:10, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 15:53:26 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 14:27, Manfred Hollstein wrote:
On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote:
On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote: > > > > it looks like the last Tumbleweed snapshot 20231003 removed package > > fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't > > contain it anymore. > > > > This package is still needed by Kodi which now shows one orphaned > > package. Was the removal on purpose? In that case we would have to > > start building it for Tumbleweed on Packman. > > Descr: fails to build and is unused
The buildfailure is easy to fix (already identified to require groff-full), but the deletion crowd went chopping in the woods quicker than anything else.
Yeah, I stored the deleted files in the devel:libraries:c_c++ project and created a new package A_tw-fstrcmp in PMBS/Staging, which only builds for Tumbleweed and Slowroll.
You can just bring it back for openSUSE:Factory. If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed build failure reports and there is less of a chance someone swings the package axe.
I just requested maintainership for d:l:c/fstrcmp. Once I get access rights, I'll resurrect the stuff in PMBS again.
E-h-h ... if you get maintainership, what stops you from submitting it back to Factory? Why keep it external?
You got me wrong. Once I have maintainership, I'll re-create the package in d:l:c and submit it again to openSUSE:Factory. When that is done, I'll re-create the situation in PMBS as it was before. Right now, it's just a stop gap solution so new users will be able to install kodi on TW at all.
FWIW, I have now created SR https://build.opensuse.org/request/show/1115896 hoping it'll make its way to openSUSE:Factory :) BTW, thanks to Jan for assigning maintainership to me! Cheers. l8er manfred
participants (3)
-
Andrei Borzenkov -
Jan Engelhardt -
Manfred Hollstein