Learn more about these different git repos.
Other Git URLs
Sorry if this is the wrong place for this -- I don't want to retire BleachBit entirely just yet, but it relies on Python2. The upstream developers are working on porting to Python3, but there's no published estimate on when that will finish.
In the meanwhile, in Rawhide and I think maybe F31, Python2-based packages are being removed. I have gotten a report of BleachBit failing to install because the dependency gnome-python2 is missing. I would have thought the package should have just failed to build in Koji if that were the case. But wherever Python2 packages are being removed, BleachBit should also be removed, at least until the Python3 conversion finishes.
gnome-python2
@terrycloth We can retire it for F31 and F32 for now and when the upstream is ready, you can request for unretirement and we will unretire it for you, is that what you want?
Note: If its retired for more than 8 weeks, then you need to submit a review request again.
I don't really want to retire the package, especially if it will likely mean having to do a new package review when the upstream finally finishes porting to Python 3. But unless we can make an exception for all of BleachBit's Python 2 dependencies, and figure out how to get gnome-python2 building again, I figured retiring it would be necessary.
You'd probably know better than me what's best in this situation.
@terrycloth I think we could leave it as is for now and it will get retired if its still in failed to build state before next mass branching. I hope it will be fixed by then and you can build it and no action is needed, if the work is not done by then, it will get retired automatically and you have to do a review request to package it again.
Closing this ticket and please open it if anything is required from us.
Thanks.
Metadata Update from @mohanboddu: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.