Bug 31376 - ctags should be switched to new upstream universal-ctags
Summary: ctags should be switched to new upstream universal-ctags
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: Mageia 9
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-05 20:38 CET by David Walser
Modified: 2023-01-07 12:48 CET (History)
2 users (show)

See Also:
Source RPM: ctags-5.8-18.mga9.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2023-01-05 20:38:30 CET 
+++ This bug was initially created as a clone of Bug #31359 +++

Debian-LTS has issued an advisory on December 31:
https://www.debian.org/lts/security/2022/dla-3254

The issue appears to be fixed in version 6.0.0 of apparent fork universal-ctags, which Debian has packaged.  We should probably switch Cauldron to this version.

Mageia 8 is also affected.

Security issue has been patched, but we still need to switch to the new maintained upstream.  As noted in the previous bug, Gentoo has also switched:
https://packages.gentoo.org/packages/dev-util/ctags
Comment 1 Nicolas Salguero 2023-01-06 10:35:36 CET 
Hi,

ctags-6.0.0-1.mga9 built successfully.  It now needs to be tested to see if upgrading from the previous version works correctly because I am not an expert of update-alternatives.

Best regards,

Nico.

CC: (none) => nicolas.salguero

Comment 2 David Walser 2023-01-07 03:41:06 CET 
Indeed, I asked for testing on qa-discuss and Dave said the alternative link didn't get updated.  I wonder if there needs to be a scriptlet that triggers on pre-6.0 versions that needs to delete /etc/alternatives/ctags to allow update-alternatives to reset the link.
Comment 3 David Walser 2023-01-07 12:48:15 CET 
Jani fixed it.  Thanks!

CC: (none) => jani.valimaa
Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.