Trying to upgrade Haiku to latest available nightly or stable fails

[tps800]

I've configured Haiku with

~> pkgman list-repos
        Haiku
                base-url:  https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current
                url:       https://hpkg.haiku-os.org/haiku/master/x86_64/current
                priority:  1
        HaikuPorts
                base-url:  https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current
                url:       https://hpkg.haiku-os.org/haikuports/master/x86_64/current
                priority:  1
        clasqm's x86_64 repo
                base-url:  http://clasquin-johnson.co.za/michel/repo_64
                url:       http://clasquin-Johnson.co.za/michel/repo_64
                priority:  2

Now trying to upgrade fails with:

*** Failed! Server not found

Inserting the repos baseurl https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current/into some browser window gives back:

Route { branch: "master", arch: "x86_64", version: "r1~beta2_hrev54907", path: "master/x86_64/r1~beta2_hrev54907" }

With this information pkgman tries to fetch from server https://hpkg.haiku-os.org/haiku/master/x86_64/current and this leads to NXDOMAIN-Errors.

Same for Haikuports. eu.hpkg.haiku-os.org exists and is resolvable, but hpkg.haiku-os.org does not exist within DNS and leads to error: Server not found.

[waddlesplash]

What hrev are you on? There was a nightly build a few days ago that had broken DNS resolution.

[tps800]

hrev54154_111-x86_64 - as downloadable by this "Download it now! beta2"-button on https://www.haiku-os.org

But I do not think this is the problem here: take curl and have the same result from any other Linux/BSD/Windows.

https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current delivers Route { branch: "master", arch: "x86_64", version: "r1~beta2_hrev54907", path: "master/x86_64/r1~beta2_hrev54907" }

pkgman takes this, tries to access: https://hpkg.haiku-os.org/haiku/master/x86_64/r1~beta2_hrev54907

Failing with hpkg.haiku-os.org because of NXDOMAIN.

$ host eu.hpkg.haiku-os.org
eu.hpkg.haiku-os.org is an alias for ingress.haiku-os.org.
ingress.haiku-os.org is an alias for limerick.ams3.haiku-os.org.
limerick.ams3.haiku-os.org has address 104.248.198.131
limerick.ams3.haiku-os.org has IPv6 address 2a03:b0c0:2:d0::3481:e001

while

$ host hpkg.haiku-os.org
Host hpkg.haiku-os.org not found: 3(NXDOMAIN)

So why does pkgman while adding repos change eu.hpkg.haiku-os.org to hpkg.haiku-os.org

instead of taking eu.hpkg.haiku-os.org

entering for repos:

        Haiku
                base-url:  https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current
                url:       https://hpkg.haiku-os.org/haiku/master/x86_64/current
                priority:  1
        HaikuPorts
                base-url:  https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current
                url:       https://hpkg.haiku-os.org/haikuports/master/x86_64/current
                priority:  1

instead of

        Haiku
                base-url:  https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current
                url:       https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current
                priority:  1
        HaikuPorts
                base-url:  https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current
                url:       https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current
                priority:  1

what would work!

[waddlesplash]

The "url" is actually an "identifier", the "base-url" is where it fetches packages from. We really should change this terminology, as it is indeed confusing.

[tps800]

Hmmmm. Changing url from

https://hpkg.haiku-os.org/haiku/master/x86_64/current

to

https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current

within pkgman configuration makes pkgman work as expected ...

[waddlesplash]

That is very strange, and not what I would expect. Maybe something changed recently that I missed...

[waddlesplash]

We now clearly identify which URL is the real one and which is the "identifier", and now use "tag" URIs in the "identifier" field.

[tps800]

This was fixed some builds later. It now finds the servers, even if updates have to use some proxy to access the servers.