Github messages for voidlinux
 help / color / mirror / Atom feed
From: Samueru-sama <Samueru-sama@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: 7zip errors when compressing directories containing broken symlinks
Date: Fri, 29 Dec 2023 15:04:24 +0100	[thread overview]
Message-ID: <20231229140424.rwIlnJ10JIdN-8REXZ5XW5SgVAYutqwxNcg43q13hAQ@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: 1052 bytes --]

New comment by Samueru-sama on void-packages repository

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

Comment:
> Comparing to Arch is moot because Arch uses a completely different upstream project.
> 
> Rejecting compression when attempting to follow broken symlinks is entirely reasonable. In any case, this is an issue that should be taken upstream.

It is not only arch, void is the only distro that I've ever encountered that has this issue. 

And it is not reasonable if it breaks file-roller and xarchiver. Also why does it need to follow the symlink? Is it going to try to take everything in the symlink to compress?

Say I have my steam directory symlinked in home and I try to compress my home dir for backup, I really hope it will not try to compress my entire steam library in the process. 

edit: In fact if I want to store what the symlinks 7z has the -l which does exactly that, it is something you need to tell to do and it does not come by default, and xarchiver is not passing that flag.

  parent reply	other threads:[~2023-12-29 14:04 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 ` [ISSUE] [CLOSED] " ahesford
2023-12-29 13:23 ` ahesford
2023-12-29 13:34 ` Samueru-sama
2023-12-29 14:04 ` Samueru-sama [this message]
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=20231229140424.rwIlnJ10JIdN-8REXZ5XW5SgVAYutqwxNcg43q13hAQ@z \
    --to=samueru-sama@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).