#7191 Untag NetworkManager VPN plugins w/o libnm-glib from f28
Closed: Can't Fix 6 years ago Opened 6 years ago by lkundrak.

Hi. I've disabled the long deprecated functionality from all VPN plugins but it turns out gnome-shell still used it. Patch for the shell is in review, until then the new builds should not be present in repositories otherwise they'll just break the Rawhide installations unnecessarily.

A fair number of packages is affected, it would be painful to rebuilt each of them. Temporarily untagging the builds seems like a better option, unfortunately I don't seem to be able to do that:

$ koji untag-build f28 NetworkManager-sstp-1.2.0-5.fc28 NetworkManager-ssh-1.2.6-4.fc28 NetworkManager-openvpn-1.8.0-4.fc28 NetworkManager-vpnc-1.2.4-5.fc28 NetworkManager-pptp-1.2.4-5.fc28 NetworkManager-openconnect-1.2.4-7.fc28 NetworkManager-libreswan-1.2.4-5.fc28 NetworkManager-l2tp-1.2.8-4.fc28 NetworkManager-iodine-1.2.0-5.fc28 NetworkManager-fortisslvpn-1.2.6-4.fc28
ActionNotAllowed: tag requires autosign permission

Or perhaps (so that the packages won't end up without a tag):

koji move-build f28 f28-updates-candidate NetworkManager-sstp-1.2.0-5.fc28 NetworkManager-ssh-1.2.6-4.fc28 NetworkManager-openvpn-1.8.0-4.fc28 NetworkManager-vpnc-1.2.4-5.fc28 NetworkManager-pptp-1.2.4-5.fc28 NetworkManager-openconnect-1.2.4-7.fc28 NetworkManager-libreswan-1.2.4-5.fc28 NetworkManager-l2tp-1.2.8-4.fc28 NetworkManager-iodine-1.2.0-5.fc28 NetworkManager-fortisslvpn-1.2.6-4.fc28
ActionNotAllowed: tag requires autosign permission

I'm wondering if anyone with appropriate permissions could run the command for me?

Thank you


Unfortunately, this has gone out in rawhide composes now... so we can't just untag it. ;(

Options:

  • Push newer versions with the change reverted

  • See if gnome-shell can carry the patch until it's upstreamed?

Sorry about this. I should have looked at untagging them when I noticed this issue... but too much else was going on. ;(

Random reminder that rpm-ostree was designed to fix exactly this problem; the OS (in this case desktop) is delivered as an atomic unit, should be tested that way, and if something is broken, it's not slaved to "higher version wins". Untagging will work just fine for Fedora Atomic {Host,Workstation} - and using dnf/yum in containers you can yum distro-sync and if something goes wrong just rerun from the base container.

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/IMPE6KCRBHCEJH5VBE6ZFIRLPAD743JT/ etc.

Login to comment on this ticket.

Metadata