linux-kernel - Re: bzip2 tarball 2.6.19-rc2 packaged wrong?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4530B897.3010403@lsrfire.ath.cx>
Date:	Sat, 14 Oct 2006 12:14:47 +0200
From:	Rene Scharfe <rene.scharfe@...fire.ath.cx>
To:	Shawn Starr <shawn.starr@...ers.com>,
	Linus Torvalds <torvalds@...l.org>
CC:	linux-kernel mailing list <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: bzip2 tarball 2.6.19-rc2 packaged wrong?

Shawn Starr schrieb:
> Linus, something in git  broke the prepackaged tarball/bzip2 generation?
> 
> $ tar -jxvf linux-2.6.19-rc2.tar.bz2
> linux-2.6.19-rc2.gitignore
> linux-2.6.19-rc2COPYING
> linux-2.6.19-rc2CREDITS
> linux-2.6.19-rc2Documentation/
> linux-2.6.19-rc2Documentation/00-INDEX
> linux-2.6.19-rc2Documentation/ABI/
> linux-2.6.19-rc2Documentation/ABI/README
> 
> -rc1 was ok.

Perhaps tar generation has been switched to using git-archive instead of
git-tar-tree?  There's an, admittedly, subtle difference in how the two
handle prefixes/basedirs.  The following two commands do the same:

   $ git-tar-tree rev basedir
   $ git-archive --prefix=basedir/ rev

If you use --prefix and you want a base directory then you have to
provide your own slash (basedir = prefix + path_separator).

René
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/