archzfs-kernels repo is moving

[endreszabo]

First of all, I'm sorry for posting this request here, but formerly the SSL cert expiration of my archzfs kernels repo ended up here before. :)

Anyways, I'd like to move my semi-official archzfs-kernels repo off of my end.re domain of my blog as I would like to move the blog to github pages.

People sync my repo 100-160k times a month, so apparently, this move affects a lot of people.

My idea is a subdomain delegation of kernels.archzfs.com to my nameservers so that I can acquire a TLS cert for it using the Let's Encrypt dns-01 challenge validation. (Not that TLS would make it more secure as packages are officially signed.)

FAQ

Why don't you put the packages up on the GitHub pages as well?

While GH Pages has an allowance of 1 TB of storage, the kernel packages account for 745MB of space usage which is not great to host in a git repo anyway. Moreover, since yesterday, I started to answer a HTTP 301 redirection for the package requests to the archive.archlinux.org so that packages will be downloaded from there instead. It might be faster for you this way. GitHub Pages does not support this kind of redirection matching at all:

    location ~ ^/archzfs-kernels/(?<fn>(?<pn>(?<fl>.).+?)-[0-9].+pkg\.tar.+)$ {
            rewrite ^(.*) https://archive.archlinux.org/packages/$fl/$pn/$fn permanent;
    }

Will you share with us the script that generates the repo?

It is right there, executed in place every day at 00:00 UTC.

Will there be any migration period to change pacman.conf?

Sure. After that period I'll answer a 301 (permanent redirect) and later 410 (content gone) for a while on the original URL.

What is needed to be set in pacman.conf for the new location of the repo?

If agreed to use kernels.archzfs.com, then:

[kernels.archzfs.com]
Server = http://$repo/

If not, I'll make use of one of my spare domains.

Maybe it's safe to tag @minextu here as he seemed to be dealing with archzfs related web issues so far.

[minextu]

Yeah I think having kernels.archzfs.com for this would be a great idea.
I can setup a NS record on that domain, just let me know where to point it to.

[endreszabo]

I can setup a NS record on that domain, just let me know where to point it to.

for NS records:

kernels.archzfs.com.		IN	NS	iedub0.kernels.archzfs.com.
kernels.archzfs.com.		IN	NS	hubud0.kernels.archzfs.com.

and since they are in-zone, the glue records:

iedub0.kernels.archzfs.com.	IN	A	54.77.48.44
iedub0.kernels.archzfs.com.	IN	AAAA	2a05:d018:563:7900::25
hubud0.kernels.archzfs.com.	IN	A	88.151.99.71
hubud0.kernels.archzfs.com.	IN	AAAA	2a01:270:9047::1

[minextu]

I had some problems setting up glue records on my registrar. So I used iedub0.archzfs.com instead. Can you work with that?

[endreszabo]

Thanks, works just fine. While we are at it, one of their nameservers called maceio.porkbun.com is not responding. :/

[endreszabo]

Ok, I'm done setting up the web server for that.

PUBLIC ANNOUNCEMENT:

In order to use the repository from the new location simply change your previous archzfs-kernels pacman.conf entry to this one:

[archzfs-kernels]
Server = http://kernels.archzfs.com/$repo/$arch

Or this one if you really want to be a minimalist:

[kernels.archzfs.com]
Server = http://$repo/

[endreszabo]

Fixed a bug that caused kernel from the 4.x series added to the repo instead of the now-current 5.x. It came from the zfs-archiso-linux dependency.

[heinrich5991]

http://kernels.archzfs.com/ redirects to a 404 page.

[ivdimitro]

At least since 02.12 neither the new nor the old repo are working.

[endreszabo]

You're right. My script failed to build the repo as newly introduced packages have conflicting dependencies .. that can't be referenced in a single repo.

So either I'll have to blacklist some packages or split the repo for each one of them.

[endreszabo]

So either I'll have to blacklist some packages or split the repo for each one of them.

For the record before this issue I already had to blacklist processing of the zfs-archiso package as it depends on an older linux package than the zfs-linux itself. And, as we know, a single repository can't hold multiple versions of the same package.

I think the safe and future proof way is to split up the repo to one unique repos, one per archzfs package.

[endreszabo]

http://kernels.archzfs.com/ redirects to a 404 page.

Ah I missed this comment here. :/ This was due to a change to my blog structure which altered the URL of the actual post. Fixed.

[endreszabo]

Ok, I finally got time to modify my script.

The repository has been split up into many repositories each referencing different kernel packages supported by archzfs. From now on please use the kernels.archzfs.com repository as below:

For example, if you use the linux-lts kernel package, you should specify:

[zfs-linux-lts]
Server = http://kernels.archzfs.com/$repo/

or...

[kernels.archzfs.com]
Server = http://$repo/zfs-linux-lts/

...whichever you like

[grawlinson]

Thanks for providing all this support, @endreszabo! 👍

The unofficial user repositories page will need to be updated as well.

[endreszabo]

The unofficial user repositories page will need to be updated as well.

Indeed, thanks.