Error with bitbucket access and baph installer

For a week or two on running -Syu although the update succeeds I get:
error: failed retrieving file ‘archlabs_repo.db’ from bitbucket.org : The requested URL returned error: 404

And (I don’t know if it is related) baph cannot install and returns, e.g.
baph -i anaconda
error: AUR (en) - anaconda responded 405, is the name spelled correctly

pacman.config contains:
[archlabs_repo]
Server = https://bitbucket.org/archlabslinux/$repo/raw/master/$arch
Server = https://github.com/ARCHLabs/$repo/raw/master/$arch
Server = archlabs - Browse Files at SourceForge.net

I have updated mirrorlist; run pacman-key --init + pacman-key --populate, -Scc & -Syyu
Then:
sudo pacman -S archlinux-keyring
warning: archlinux-keyring-20220831-1 is up to date – reinstalling
I reinstalled anyway, then
pacman -S archlabs-keyring
archlabs-keyring-2019.10.06-1 is up to date,
I reinstalled anyway:
:: Retrieving packages…
archlabs-keyring… 13.1 KiB 23.3 KiB/s 00:01 [----------------------] 100%
error: failed retrieving file ‘archlabs-keyring-2019.10.06-1-x86_64.pkg.tar.xz’ from bitbucket.org : Maximum file size exceeded


==> Appending keys from archlabs.gpg…
gpg: error reading key: No public key
==> Disabling revoked keys in keyring…
→ Disabled 1 keys.
==> Updating trust database…
gpg: next trustdb check due at 2022-11-16
:: Running post-transaction hooks…
(1/1) Arming ConditionNeedsUpdate…

Again: -Syu

warning: /etc/locale.gen installed as /etc/locale.gen.pacnew

Again: pacman -S archlabs-keyring
archlabs-keyring-2019.10.06-1 is up to date
I reinstalled again
didn’t get the error: failed retrieving file
just:

==> Appending keys from archlabs.gpg…
gpg: error reading key: No public key
==> Disabling revoked keys in keyring…
→ Disabled 1 keys.
==> Updating trust database…
gpg: next trustdb check due at 2022-11-16
:: Running post-transaction hooks…
(1/1) Arming ConditionNeedsUpdate…

After rebooting, the errors are the same

Well that sux, @dt78q , @natemaia s the one that maintains the repo, he ll get back to you on that one.

Edit my post while rereading it.

I would check on your mirrorlist laso, as for the link from @chroot below;

I also wonder if you cleared the cache also might help before updating

Also after reinstall the keyring, did you try to update by this command before rebooting;

sudo pacman -Scc

sudo pacman -syu

1 Like

I would also try this from another thread on post #38 or so from @chroot ;

1 Like

You need to change your pacman.conf.

Read the post on the web page dated back to 4 May 2021 - Manual Intervention Required

1 Like

I don’t know how I missed that - thanks very much

A ton of people will be having this issue as I looked into the download numbers for each and 80% of users never updated. I had to remove it eventually and it’s been over a year now.

Thanks for the coverage @chroot.

1 Like