Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26681 - [mc] u7z in midnight commander

Attached to Project: Community Packages
Opened by Valeriy Koval (vkoval) - Saturday, 29 October 2011, 18:41 GMT
Last edited by Jakob Gruber (schuay) - Sunday, 30 October 2011, 12:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jakob Gruber (schuay)
Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: previously both packages provided the file: /usr/share/mc/extfs/u7z (note: these were different) and the file was excluded from the mc. It was a mistake.
Now the mc package should contain the correct version because guys from p7zip don't support that file at all and the file from p7zip package produces wrong output for mc when user tries to open 7z archive. Also I checked the u7z file from the mc sources and it works good.

Additional info:
mc-4.8.0-1
p7zip 9.20.1-5
This task depends upon

Closed by  Jakob Gruber (schuay)
Sunday, 30 October 2011, 12:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  p7zip-9.20.1-6
mc-4.8.0-2
Comment by Jakob Gruber (schuay) - Saturday, 29 October 2011, 19:38 GMT
Please state exactly what you mean by 'and the file from p7zip package produces wrong output for mc when user tries to open 7z archive'.

Opening .7z files works just fine for me for what it's worth.
Just to be safe, could you try deleting ~/.mc and ~/.config/mc and trying to open the file again?
Comment by Valeriy Koval (vkoval) - Saturday, 29 October 2011, 21:26 GMT
First of all - I already moved ~/.mc to ~/.config/mc and did all other changes.
Secondly - when I'm opening the .7z archive (the subdirs are inside) with u7z from p7zip I get next (see attach1.png).
But when I'm doing the same with the u7z from the mc site (the link https://www.midnight-commander.org/browser/src/vfs/extfs/helpers/u7z) I get next (see attach2.png)
The difference is:
- in the first case I see some timestamps instead of dirs;
- in the second case - correct info.

P.S. It's regular .7z archive without any special files/dirs with specific chars in their names.
   attach1.png (859 KiB)
   attach2.png (777.8 KiB)
   1.7z (0.2 KiB)
Comment by Jakob Gruber (schuay) - Saturday, 29 October 2011, 21:27 GMT
@Gaetan, it does seem like it'd make more sense to use mc's included u7z file. The one from p7zip is dated 12 Nov 2005 while it's still being maintained @ midnight commander: https://www.midnight-commander.org/log/src/vfs/extfs/helpers/u7z

Any thoughts?
Comment by Jakob Gruber (schuay) - Saturday, 29 October 2011, 21:31 GMT
@vkoval, I can reproduce your issue now, thanks.
Comment by Valeriy Koval (vkoval) - Saturday, 29 October 2011, 21:34 GMT
I'm glad to hear it :)
Not at all.
Comment by Gaetan Bisson (vesath) - Sunday, 30 October 2011, 00:55 GMT
Jakob: Sure, what you say makes a lot of sense.
I'll push a p7zip package without that file in [testing], and you can push a new mc in [community-testing]; then I can move them both at the same time to [extra] and [community].
Comment by Gaetan Bisson (vesath) - Sunday, 30 October 2011, 02:04 GMT
Alright; p7zip-9.20.1-6 without /usr/lib/mc/extfs.d/u7z is in [testing].
Comment by Jakob Gruber (schuay) - Sunday, 30 October 2011, 09:46 GMT
mc-4.8.0-2 is in [community-testing], feel free to move them as soon as you are ready.

Can we be sure this file juggling between 2 packages won't cause 'file already exists in filesystem' errors on upgrade?
Comment by Valeriy Koval (vkoval) - Sunday, 30 October 2011, 10:40 GMT
I just updated both packages manually (-U) and mc works fine. Thank you guys!

Loading...