Learn more about these different git repos.
Other Git URLs
libmemcached was retired from Fedora 34 and Rawhide:
libmemcached
$ koji list-history --package=libmemcached --after=2021-06-01 Wed Jul 14 06:17:37 2021 libmemcached-1.0.18-22.fc34 untagged from f35 by releng Wed Jul 14 06:17:39 2021 package owner changed for libmemcached in f35 by releng Wed Jul 14 06:17:39 2021 package list entry for libmemcached in f35 updated by releng blocked: False -> True Fri Jul 30 06:18:06 2021 package owner changed for libmemcached in f34 by releng Fri Jul 30 06:18:06 2021 package list entry for libmemcached in f34 updated by releng blocked: False -> True
I suspect that this was related to the replacement of libmemcached by libmemcached-awesome (https://fedoraproject.org/wiki/Changes/libmemcached-awesome) but that is a Fedora 35 change and should not have happened in the already-released Fedora 34, in which libmemcached is available in the Everything repo.
libmemcached-awesome
Everything
A consequence of this is that packages that pull in libmemcached as a dependency can no longer be built for Fedora 34. For example, a scratch proftpd build: https://koji.fedoraproject.org/koji/taskinfo?taskID=73380037
proftpd
Please unretire libmemcached in Fedora 34 to fix this mistake.
I see @remi has reverted the commit: https://src.fedoraproject.org/rpms/libmemcached/commits/f34
I wonder how is retiring on f34 even possible, it shouldn't be.
@churchyard, fedpkg checks if the release is active. But one can always commit&push it by git.
@humaton, that accounts for the state of the git repo, but not the blocking of the package in koji.
Exactly. Even if the push happens (and I think the git remote should block it), the package should have not been blocked in Koji.
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
https://pagure.io/releng/pull-request/10258 should fix this.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
That may prevent a repeat of this issue but it doesn't undo the breakage that's already done: libmemcached is still blocked for f34. Can we fix that too please?
Metadata Update from @pghmcfc: - Issue status updated to: Open (was: Closed)
The package is now unblocked for f34.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.