hi kevin,
thanks for replying
but look at this output...
```
❯ zcat packages-meta-ext-v1.json.broken.gz > packages-meta-ext-v1.broken.json
gzip: packages-meta-ext-v1.json.broken.gz: invalid compressed data--crc error
gzip: packages-meta-ext-v1.json.broken.gz: invalid compressed data--length erro
As per the previous archive spec in the project (PHP), we've
intended to persist the `Content-Type: text/plain` +
`Content-Encoding: gzip` headers with our new archives, as should
be supported with all archives found in the AUR.
This wasn't being handled correctly by aur.al's nginx frontend
and a
* Kevin Morris via aur-general (aur-general@lists.archlinux.org) wrote:
> The files are downloadable in gzip format; when you receive
> the file, you'll need to uncompress it.
There might in fact be an issue here, as I've ran into it. The file
might be unexpectedly returned uncompressed by some c
Kevin, great -- thanks very much! i find the metadata archives very
valuable. cheers, Greg
Hi zoorat,
The files are downloadable in gzip format; when you receive
the file, you'll need to uncompress it.
Example:
$ curl --output packages-meta-ext-v1.json.gz \
'https://aur.archlinux.org/packages-meta-ext-v1.json.gz'
# zcat is cat for gz files; it uncompresses and cats th
Hi Dmitry,
The ordering is definitely a bug here that we should fix up and
will. Otherwise, we'd just like to make sure that the info format
is uniform with the RPC; beyond that, we can without a doubt add
other fields if they're needed for good reason.
Do you mind reporting that in the form of a
Hi!
> In addition to pre-existing archives, we've introduced two new
> archives that can be used instead of bulk queries against the RPC.
Thanks a lot for doing this, I'm switching Repology right onto the new
dump. This simplifies and speeds up repository metadata update in many
ways and also pro
