Re: Issue with creating an archive with reproducible content

On Sat, 2024-04-27 21:23:37 +0200, Jan-Benedict Glaw wrote: > I'm trying to generate a reproducible archive of a directory > contianing a number of files using tar 1.34; there are just [...] > It boils down to a call like this: > > tar

Re: Issue with creating an archive with reproducible content

On Sat, 2024-04-27 21:23:37 +0200, Jan-Benedict Glaw wrote: [...] > tar --sort=name > \ > --mtime="@${SOURCE_DATE_EPO

Issue with creating an archive with reproducible content

is didn't work. Do you have any suggestion for me to get rid of the devmajor/devminor content in the headers? Or should my approach in theory work and it's a small bug that it doesn't remove the "000"? Thanks, Jan-Benedict Glaw -- signature.asc Description: PGP signature

Re: [Bug-tar] (no subject)

sir... File names with spaces are no problem. MfG, JBG -- Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481 Signature of: Zensur im Internet? Nein danke! the second : signature.asc Description: Digital signature

Re: [Bug-tar] tar-1.20 and filepaths containing \r

is probably send through unquote_string(). My initial fear was that the supplied filename is taken as a printf format argument, but on the first glance, I cannot see how you could exploid unquote_string(), despite not backing up some files (or restoring them.) MfG, JBG -- Jan-Benedict Glaw

Re: [Bug-tar] tar-1.20 and filepaths containing \r

On Fri, 2008-09-12 18:08:38 +0300, Sergey Poznyakoff [EMAIL PROTECTED] wrote: Jan-Benedict Glaw [EMAIL PROTECTED] ha escrit: If you strace it, you see that the '\r' decoded to ^M and that's what I have misread the initial post then, because I thought that \r *does* stand for ^M. If you

Re: [Bug-tar] Re: unexpected EOF

is that this is an old system that can only handle files = 2GB, but I guess it's the former issue that's biting you). You cannot do anything against that, except try to get your hands on the original archive if it still exists somewhere... MfG, JBG -- Jan-Benedict Glaw [EMAIL

Re: [Bug-tar] (no subject)

Is this a bug, or is my script wrong? Your script is wrong. Depending on what you actually want to achieve, you're either omitting the output filename, or the list of entities being backed up. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature

Re: [Bug-tar] GNU tar, star and BSD tar speed comparision +script

of the tests, we see that GNU tar ist quite fast all the time, though there seems to be a shortcoming for the compare operation. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature of: Zensur im Internet? Nein danke

Re: [Bug-tar] GNU TAR or STAR -- speed comparision

On Thu, 2007-10-18 20:24:33 +0200, Joerg Schilling [EMAIL PROTECTED] wrote: Jan-Benedict Glaw [EMAIL PROTECTED] wrote: If you like to compare this, you would need to either call star as tar or tell star to be as insecure as GNU tar is. So test again with star -no-fsync

Re: [Bug-tar] minor warning glitch in tar 1.19 on Solaris 8 (sparc) with GCC 4.2.1

-- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature of: really soon now: an unspecified period of time, likly to the second : be greater than any reasonable definition of soon

Re: [Bug-tar] Robustness of tar.gz files?

compresses each file individualy, instead of the whole archive's stream. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature of: Alles wird gut! ...und heute wirds schon ein bißchen besser. the second : signature.asc Description: Digital signature

Re: [Bug-tar] [GNU tar 1.18]

for MorphOS? I just checked the first two results and they're both caused because `genfile' is missing in $PATH, or wasn't built at all. Please check if it actually *was* built and why it didn't end up being either called fully qualified or put into $PATH. MfG, JBG -- Jan-Benedict Glaw

Re: [Bug-tar] Using tar on a file with a non-ASCII filename

I need to convert them into a different format each time? tar will just put all the files (and their names) as-is into the archive, and extract them as-is. You have to make sure that the operating systems as well as file systems are compatible. MfG, JBG -- Jan-Benedict Glaw [EMAIL

Re: [Bug-tar] Extract error after failed open()

On Thu, 2006-11-30 19:41:06 +0100, Jan-Benedict Glaw [EMAIL PROTECTED] wrote: On Thu, 2006-11-30 11:51:29 +0200, Sergey Poznyakoff [EMAIL PROTECTED] wrote: GNU tar signals the open() error and prints a message like skipping to next header, but with my (real 16 GB) copy, skipping to next

Re: [Bug-tar] Extract error after failed open()

reformat with VFAT, large enough to keep up with that amount of data... MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED] +49-172-7608481 Signature of:Lauf nicht vor Deinem Glück davon: the second : Es könnte hinter Dir

[Bug-tar] Extract error after failed open()

: Call skip_member() in the error path as it is done in a different case. Copyright assignment with FSF is in place (initially filed for binutils/gcc/glibc). Please Cc: me, because I'm not subscribed. Thanks, Jan-Benedict Glaw --- tar-1.16/src/extract.c~ 2006-11-28 23:21

[Bug-tar] Archive isn't fully extracted after error on open()

: Call skip_member() in the error path as it is done in a different case. Thanks, Jan-Benedict Glaw --- tar-1.16/src/extract.c~ 2006-11-28 23:21:47.0 +0100 +++ tar-1.16/src/extract.c 2006-11-28 23:22:07.0 +0100 @@ -751,6 +751,7 @@ if (fd 0