Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] 7zip errors when compressing directories containing broken symlinks
Date: Fri, 29 Dec 2023 14:23:16 +0100	[thread overview]
Message-ID: <20231229132316.q4X12_40IUQqORTxqFyhKSBJu6gKUss36C-_HQKFWTc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47938@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

Closed issue by Samueru-sama on void-packages repository

https://github.com/void-linux/void-packages/issues/47938

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.8_1 x86_64 GenuineIntel uptodate rrrmFFFF

### Package(s) Affected

7zip-23.01_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Compressing any directory should just work even if it contains a broken symlink

### Actual behaviour

7zip throws file not found errors for the broken symlink that causes file-roller to not create the compressed file while xarchiver gives a warning. 

### Steps to reproduce

For this I used thunar with thunar-archive-plugin and file-roller and xarchiver:

Make a directory, place a broken symlink inside and then try to compress it to 7zip.


This entire reddit thread has video demonstration of the issue on void and also a comparison with the same steps on arch. 

https://old.reddit.com/r/voidlinux/comments/18s3hf0/cant_compress_directories_to_7zip_if_they_contain/

In the end I tested using the 7zip binaries from arch on void and the issue went away. 



  reply	other threads:[~2023-12-29 13:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 13:42 [ISSUE] " Samueru-sama
2023-12-29 13:23 ` ahesford [this message]
2023-12-29 13:23 ` ahesford
2023-12-29 13:34 ` Samueru-sama
2023-12-29 14:04 ` Samueru-sama
2023-12-29 14:05 ` Samueru-sama
2023-12-29 14:05 ` Samueru-sama
2023-12-29 15:01 ` ahesford
2023-12-29 15:02 ` oreo639
2023-12-29 15:06 ` oreo639
2023-12-29 15:08 ` oreo639
2023-12-29 15:09 ` oreo639
2023-12-29 15:10 ` classabbyamp
2023-12-29 15:35 ` oreo639
2023-12-29 15:36 ` Samueru-sama

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231229132316.q4X12_40IUQqORTxqFyhKSBJu6gKUss36C-_HQKFWTc@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).