Zip warning name not matched ошибка

I have a folder of around 180 GBs, I need to zip it like:

zip -p password /Volumes/GGZ/faster/mybigfolder/* /Volumes/Storage\ 4/archive.zip

But it says:

    zip warning: name not matched: /Volumes/Storage 4/archive.zip

So how do I do this? On another note, archive.zip does not exist, but I’m trying to create it.

Use the recursive flag (-r) instead of glob (*) to match files to compress. In addition, specify the archive name first and then give the list of files:

zip -p password -r /Volumes/Storage\ 4/archive.zip /Volumes/GGZ/faster/mybigfolder/

answered Feb 5, 2019 at 9:05

I have a folder of around 180 GBs, I need to zip it like:

zip -p password /Volumes/GGZ/faster/mybigfolder/* /Volumes/Storage\ 4/archive.zip

But it says:

    zip warning: name not matched: /Volumes/Storage 4/archive.zip

So how do I do this? On another note, archive.zip does not exist, but I’m trying to create it.

Use the recursive flag (-r) instead of glob (*) to match files to compress. In addition, specify the archive name first and then give the list of files:

zip -p password -r /Volumes/Storage\ 4/archive.zip /Volumes/GGZ/faster/mybigfolder/

answered Feb 5, 2019 at 9:05

I am getting the following error while using zip in my bash script

zip warning: name not matched: test.png test2.png

#!/bin/bash
files_to_zip="test.png test2.png"
zipfile_name=result$(date "+%Y.%m.%d-%H.%M.%S").zip
zip "$zipfile_name"  "$files_to_zip"

Note: The images are in the same directory as the script and when i execute zip test.zip test.png test2.png , the zip get created just fine.

• bash
• unix
• zip

asked Sep 2, 2017 at 15:13

When names are combined inside same quotes whole string is treated as file name. Use

zip "$zipfile_name" $files_to_zip

instead. And if your png names have special characters like spaces — add quotes or escape this characters inside the $files_to_zip variable

answered Sep 2, 2017 at 16:05

While utilizing zip in my bash script, I am encountering the subsequent error.


zip warning: name not matched: test.png test2.png


#!/bin/bash
files_to_zip="test.png test2.png"
zipfile_name=result$(date "+%Y.%m.%d-%H.%M.%S").zip
zip "$zipfile_name"  "$files_to_zip"

Please note that the images are located in the script’s directory and the zip file is successfully created when executing

zip test.zip test.png test2.png

.

When multiple names are enclosed within the same quotation marks, the entire string is considered as a file name. Utilize this method.

zip "$zipfile_name" $files_to_zip

In case your
png names
contains special characters such as spaces, it is advisable to either enclose them in quotes or escape these characters within the

$files_to_zip

variable instead.

Operating in Cygwin on Windows 10, I encountered an error while utilizing zip on the command line in Cygwin after installing and subsequently uninstalling 7-Zip. This error arises whenever I attempt to zip any files.

    zip warning: name not matched: Files\7-zip
    zip warning: name not matched: testing

E.g. zipping 2 files a and b:

zip testing a b

Encountering the error, how can I eliminate this annoyance? Unfortunately, reinstalling the zip file did not provide a solution.

Following an extensive search that yielded no answers, I eventually discovered the cause of the problem.

7-Zip creates an environment variable named

\
\ \ \ \ ZIP=C:\Program\ Files\7\-zip\
\ \ \

which, for unknown reasons, causes a conflict with the GNU zip utility when there is a
ZIP variable
present.

To remove ZIP, I performed

ctrl-Esc

and entered

env

. This action displayed the control panel option »
Edit environment variables
for your account,» allowing me to eliminate the ZIP variable and restore functionality.

The vulnerability can be found at https://snyk.io/research/
zip-slip
.

Users are required to manually create the contents of this zip file. Although the zip specification permits it, most archive creation tools do not allow the addition of files with such paths. Nevertheless, it is simple to create files with these paths using the appropriate tools.

I am looking to generate a test payload in order to verify my zip handling logic, but I am unable to find any guidance on how to do so.

:~/Desktop # touch "../../../../../../../../tmp/evil.sh"
:~/Desktop # ll
:~/Desktop # ll /tmp/evil.sh
-rw-r--r-- 1 root root 0 Jun 14 09:27 /tmp/evil.sh

Maybe

zip zipslip.zip ../../../../../../../../tmp/evil.sh

In this small example, everything should function properly if we exclude the occurrence of

VILLAIN

. Surprisingly, this term causes an error, although not in the location I anticipated…

The error:

$ make
mkdir -p obj
zip out.exe obj/foo.o obj/bar.o obj/baz.o
        zip warning: name not matched: obj/foo.o
        zip warning: name not matched: obj/bar.o
        zip warning: name not matched: obj/baz.o
zip error: Nothing to do! (out.exe)
Makefile:9: recipe for target 'out.exe' failed
make: *** [out.exe] Error 12

Make appears to be attempting to progress too quickly by executing a recipe without ensuring that its dependencies (obj/foo.o …) have been created. In fact, I anticipated receiving an error message such as: «Unable to locate VILLAIN for generating obj/foo.o».

The Makefile:

#!/usr/bin/env make
SRCDIR = src
OBJDIR = obj
SRC = $(addsuffix .c,foo bar baz)
OBJ = $(addprefix $(OBJDIR)/, $(notdir $(SRC:c=o)))
out.exe: $(OBJ)
    zip $@ $^ 
$(OBJDIR)/%.o: $(SRCDIR)/%.c VILLAIN
    cp $< $@
$(OBJ) : | $(OBJDIR)
$(OBJDIR):
    mkdir -p $@
clean:
    rm -f *.c
    rm -rf $(OBJDIR)/ $(SRCDIR)/
    mkdir -p $(SRCDIR)/
    touch $(addprefix $(SRCDIR)/,$(SRC))

Nevertheless, the removal of the antagonist results in smooth operation.

$ make clean
rm -f *.c
rm -rf obj/ src/
mkdir -p src/
touch src/foo.c src/bar.c src/baz.c
$ make
mkdir -p obj
cp src/foo.c obj/foo.o
cp src/bar.c obj/bar.o
cp src/baz.c obj/baz.o
zip out.exe obj/foo.o obj/bar.o obj/baz.o
  adding: obj/foo.o (stored 0%)
  adding: obj/bar.o (stored 0%)
  adding: obj/baz.o (stored 0%)

Why attempt to establish a goal without first constructing the necessary foundation?

In terms of this aspect,
Pattern rules
operates differently than
explicit rule
. Numerous variations of
pattern rules
could be utilized to achieve the same objective (for example, a

.o

can be generated from a C source file, a C++ source file, and so on).

When attempting to identify a pattern rule to construct a target, make will attempt to build all the prerequisites to determine if the pattern matches. If one of the prerequisites cannot be constructed, it is not considered an error. Make will simply move on to the next matching pattern rule and attempt that. Therefore, the absence of

VILLIAN

and its inability to be constructed signifies that make will never choose this pattern rule due to unsatisfactory prerequisites. It is important to note that this is not an error, and no message will be displayed (unless observed in make’s debug output).

In the process of building

obj/foo.o

, it will be noticed that there are no existing rules in place. Normally, one would anticipate an error at this stage, but due to the addition of a specific rule, no error will occur.

$(OBJ) : | $(OBJDIR)

By declaring

obj/foo.o

as a target, you inform the make system about it, preventing any complaints regarding the non-existence of the target. To enhance clarity, consider including the order-only prerequisite in the pattern rule.

$(OBJDIR)/%.o: $(SRCDIR)/%.c VILLAIN | $(OBJDIR)
        cp $< $@
$(OBJDIR):
        mkdir -p $@

Gives:

make: *** No rule to make target 'obj/foo.o', needed by 'out.exe'.  Stop.