“xxx-1.4.2.tgz” doesn’t look like a distribution archive

[strk]

I'm getting such message upon uploading a tgz file for "releasing" it to the public, but the message doesn't tell me what's wrong in it. The tarball unpacks in a directory with the name of the extension and does contain a META.json file. For a quick look I uploaded it on this temporary URL: http://strk.kbt.io/tmp/table_version-1.4.2.tgz - can you see what's wrong with it ?

It would be helpful if the UI would tell what's lacking/missing/doing wrong

[theory]

Yes, that certainly looks fine. I ran my validator on the META.json and it worked. I wonder if something is missing from the PGXN manager config since the server upgrade last week…

[theory]

Would you post a screenshot of the response, please? I'm not able to replicate the issue, and there's nothing in the logs. :-(

[strk]

[theory]

Try renaming the file to end in .tar.gz rather than .tgz.

[strk]

I tried both, the screenshot is for .tar.gz while the original report was for .tgz (same file, just renamed)

[theory]

Hrm. I just wrote a script trying to duplicate, and it worked, no error. WTF…

[theory]

I'll keep at it, but meanwhile, try uploading a zip file, instead.

[strk]

.zip worked

[theory]

So I see. WTF.

[strk]

How long does it take before the newly uploaded package is shown as latest ?

[theory]

It runs a cron job every 5 mins, but it will be on master now.

[beaud76]

Hi, I have had exactly the same problem yesterday with a new release of the E-Maj extension (2.3.0). Same message, same input formats (tar.gz and tgz), and same workaround by using a zip file. The tgz file is quite large: 4.3 Mb. But I tried with a smaller one (2.3Mb) with no success. Here is the faulting file: emaj-2.3.0.tar.gz