Nano-syntax-highlighting in Testing is different to Arch, Unstable and Stable branches

[scotty65]

Just updated Firefox and received a nano-syntax-highlighting in local (2022.11.02.r102.gbb94603-1) is newer than in extra (2020.10.10-2) warning. My mirrors are all up-to-date.

A branch compare shows Testing to be the odd one out:

mbn info nano-syntax-highlighting -q
Branch         : archlinux
Name           : nano-syntax-highlighting
Version        : 2022.11.02.r102.gbb94603-1
Repository     : extra
Build Date     : Tue 17 Sep 2024 22:49:49 
Packager       : Andreas Radke <andyrtr@archlinux.org>
Branch         : unstable
Name           : nano-syntax-highlighting
Version        : 2022.11.02.r102.gbb94603-1
Repository     : extra
Build Date     : Tue 17 Sep 2024 22:49:49 
Packager       : Andreas Radke <andyrtr@archlinux.org>
Branch         : testing
Name           : nano-syntax-highlighting
Version        : 2020.10.10-2
Repository     : extra
Build Date     : Sat 13 Jul 2024 09:51:56 
Packager       : T.J. Townsend <blakkheim@archlinux.org>
Branch         : stable
Name           : nano-syntax-highlighting
Version        : 2022.11.02.r102.gbb94603-1
Repository     : extra
Build Date     : Tue 17 Sep 2024 22:49:49 
Packager       : Andreas Radke <andyrtr@archlinux.org>

[cscs]

As with all examples of newer than you can run pacman -Syuu to align with the repos.

( double u allows downgrades when syncing )

This same thing happened with this package at least one other time in the last few months …

This is going to continue to be likely so long the versioning is the weird vcs style.

[scotty65]

Thanks for the fast reply @cscs

As I already have the newer version installed & don’t seem to be experiencing any issues, I won’t bother with running the pacman -Syuu command at the moment.

I just found it a little unusual that the version was rolled back in only the Testing repo.

[cscs]

@scotty65

I just found it a little unusual that the version was rolled back in only the Testing repo.

Oh. Yeah. It is.
I think it is by mistake.

(It also would not be the first time that Testing was skipped … for kernels, etc)

https://manjaristas.org/branch_compare?q=nano-syntax-highlighting

Under just about no circumstances should Testing be behind Stable.

I raised it over on Update requests for packages imported from Arch Linux - #371 by cscs

EDIT.

@scotty65
According to phil … the package was pushed as a fix to stable but not testing.

@philm

already answered that. see previous post. the package got forwarded as an to stable branch to fix an issue, but not to testing. Sync packages were versioned in both branches as 2020.10.10-2

[omano]

phil’s “explanation” made no sense to me I can’t understand why it is like that even when he thinks he explained it.