OK, now I know which mail to send it too, thanks!
No, the problem I'm talking about isn't with zstd but packages that have
been zstd'd. As an easy example, have a look at x86info-1.30 which by
normal (source is a tbz2 or tgz depending where you get it). It
compresses down to x86info-1.30.tzst by the ./scripts/Download utility.
But fails when ./scripts/Build-Target or Emerge-Pkg because it can't be
unpacked. On the other hand some packages seem to be built with their
compression still visable and a .zst added on the end (such as the 1.28
release of the same package in your mirror). The three .t?? package
types I listed are all out there and giving similar results.
regards
scsijon
On 06/16/2017 05:02 PM, René Rebe wrote:
Hi,
please direct all T2 related question to the list. Not only is my inbox
seriously overloaded, you also increase chances that someone else answers while
I’m busy ;-)
On Jun 15, 2017, at 12:48 PM, scsijon <[email protected]> wrote:
I've come across a problem.
In a small number of cases the packages are by nature natively packed in either
a .tgz, .tbz2 or .txz package format.
During processing the zst package is repacking them into a .tzst format and
not just a .zst.
However it can't seem to be able to unpack them back into their native packed
format and therefore thay are failing the unpacking process and therefore not
building them.
As we are on a proper “Unix” system you do not need build in support for zstd.
Just decompress it and pipe it into tar:
zstd -d < download/mirror/z/zstd-1.1.2.tar.zst | tar xv
The T2 scripts just do that and it works on all my systems.
Not sure what you can do about this Rene but it's messing the autobuilder up.
No idea what you have done to the scripts ;-) Maybe you run old script from
last year without the above zstd support? or you mis-editted them in other ways?
René
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
