- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version sort order is completely broken in MC 4.8.28 #4374
Comments
|
.mozilla.ram
I don't understand this sort order: .m*, .w*, .I*, .X*, .f*, .w*? What? Why? |
|
|
The maintainer in Fedora has applied the patch but it doesn't seem to work:
I don't understand this sort order. |
Congratulations! You found a bug (but probably this is a feature) in gnulib.
I installed coreutils-9.1 (that contains a gnulib commit [9f48fb992a3d7e96610c4ce8be969cff2d61a01b]) and I have the same result as above for ls -a1v and ls -a1 | sort -V:
|
Replying to andrew_b:
What's GNUlib? I don't have it installed on my Fedora 36 ;-)
Are you talking about glibc? |
On Fedora 36:
Looks correct.
Again, it's correct. |
Also correct. |
|
Replying to birdie:
No, I'm talking about gnulib, a base library for many GNU tools, including coreutils.
This says me nothing. I'm not Fedora user. Show the output of ls --version or rpm -q coreutuls. |
|
Change 9f48fb992a3d7e96610c4ce8be969cff2d61a01b was committed to gnulib 2022-02-12. Coreutils-9.1 was released 2022-04-15 and contains this change.
The version sort of ls-9.1 will differ than one of ls-9.0. Now this will not come as a surprise to you. |
I've emailed the gnulib bug mailing list, they've confirmed the regression and the patch has already been released.
It's quite disturbing how ostensibly millions of people use Linux, yet I uncover such major bugs. |
|
Branch: 4374_version_sort_fix2 |
Andrew, thanks a ton!
Is the patch from comment #3 still required? |
|
Important
This issue was migrated from Trac:
birdie
(aros@….com)See the attached screenshot
Note
Original attachments:
birdie
(aros@….com) onMay 23, 2022 at 9:41 UTC
The text was updated successfully, but these errors were encountered: