I'm getting the following error messages when attempting to install linux619

This is my last attempt. After running

sudo pacman-mirrors --fasttrack

[tracy@daphne ~]$ sudo mhwd-kernel -i linux619
[sudo] password for tracy: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
resolving dependencies...
looking for conflicting packages...

Packages (1) linux619-6.19.0-2

Total Download Size:   145.81 MiB
Total Installed Size:  152.10 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux619-6.19.0-2-x86_64          97.1 KiB  26.4 KiB/s 00:04 [##################################] 100%
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.kurdy.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.uni-kl.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.cicku.me : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.init7.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.syxpi.fr : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.it4i.cz : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.tu-chemnitz.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirrors.uk2.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.rz.tu-bs.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.ynh.ovh : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.vinehost.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.futureweb.be : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirrors.lavatech.top : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from www.mirrorservice.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.dotsrc.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.bouwhuis.network : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.easyname.at : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.manjaro.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.snt.utwente.nl : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.ft.uam.es : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ask4.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.alwyzon.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.23m.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirror.garr.it : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.netcologne.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.psnc.pl : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.alpix.eu : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirror.wearetriple.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.eric.ovh : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors2.manjaro.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.yandex.ru : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.free.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.gwdg.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ipng.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.belnet.be : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.lysator.liu.se : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.linux.org.tr : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.halifax.rwth-aachen.de : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.raiolanetworks.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.dkm.cz : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.mobinhost.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.telepoint.bg : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirror-services.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from nnenix.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from fosszone.csd.auth.gr : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from repo.ialab.dsu.edu : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from coresite.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ohioix.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from forksystems.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.gigenet.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from cofractal-ewr.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from southfront.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.grena.ge : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from nocix.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from volico.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from codingflyboy.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.ucr.ac.cr : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from edgeuno-bog2.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.math.princeton.edu : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from manjaro.mirror.liquidtelecom.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ziply.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.xenyth.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from irltoolkit.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror1.sox.rs : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.dc.uz : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.dimensiondata.com : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from opencolo.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirrors.atlas.net.co : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.csclub.uwaterloo.ca : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ftp.cc.uoc.gr : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.freedif.org : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.meowsmp.net : Connection timed out after 10002 milliseconds
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ct.mirror.garr.it : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from mirror.kamtv.ru : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from linorg.usp.br : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst' from ba.mirror.garr.it : The requested URL returned error: 404
error: failed retrieving file 'linux619-6.19.0-2-x86_64.pkg.tar.zst.sig' from mirror.xeonbd.com : Exceeded the maximum allowed file size (16384) with 16384 bytes
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

My vpn exit node is Germany, Frankfurt.

It looks like your metadata is not up-to-date.

 $ mbn info linux619 -q
Branch         : unstable
Name           : linux619
Version        : 6.19.3-1
Repository     : core
Build Date     : Fri 20 Feb 2026 04:49:52 
Packager       : Manjaro Build Server <build@manjaro.org>
Branch         : testing
Name           : linux619
Version        : 6.19.2-1
Repository     : core
Build Date     : Mon 16 Feb 2026 22:36:52 
Packager       : Manjaro Build Server <build@manjaro.org>
Branch         : stable
Name           : linux619
Version        : 6.19.2-1
Repository     : core
Build Date     : Mon 16 Feb 2026 22:36:52 
Packager       : Manjaro Build Server <build@manjaro.org>

Interesting.

When you use --fasttrack your mirror list changes, but it does not change the metadata, that is left for the package manager to handle.

If you use pacman -S linux618 you would also get 404 because the package version 6.19.0-2 no longer exist.

mhwd will call pacman

pacman -S --noconfirm linux619

It may of course have additional packages depending on what is currently installed as extra-modules for the running kernel.

Nostalgia:
When I was coding pacman-mirrors back in 2027/2018 some suggested that pacman-mirrors should trigger an update as well - which we after some ping-pong agreed to was not a good idea.

1 Like

So first try:

sudo pacman -Sy

Because:


-S, --sync
Synchronize packages. Packages are installed directly from the
remote repositories, including all dependencies required to run the
packages. For example, pacman-S qt will download and install qt and
all the packages it depends on. If a package name exists in more
than one repository, the repository can be explicitly specified to
clarify the package to install: pacman-S testing/qt. You can also
specify version requirements: pacman-S "bash>=3.2". Quotes are
needed, otherwise the shell interprets ">" as redirection to a file.

-y, --refresh
Download a fresh copy of the master package databases (repo.db) from
the server(s) defined in pacman.conf(5). This should typically be
used each time you use --sysupgrade or -u. Passing two --refresh or
-y flags will force a refresh of all package databases, even if they
appear to be up-to-date.

Yeah.

[tracy@daphne ~]$ sudo pacman -Sy
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
[tracy@daphne ~]$ sudo pacman -Syu linux619
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) linux619-6.19.0-2

That looks strange, the --fasttrack argument uses data from https://repo.manjaro.org more specifically it pulls the data file which the displayed data is based upon.

 $ sudo pacman-mirrors -z
[sudo] password for fh: 
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
....

What is the content of your mirrorlist when pacman returns linux619-6.19.0-2?

cat /etc/pacman.d/mirrorlist
[tracy@daphne ~]$ cat /etc/pacman.d/mirrorlist
##
## Manjaro Linux default mirrorlist
## Generated on 2026-02-27 20:47
##
## Please use 'pacman-mirrors -f [NUMBER] [NUMBER]' to modify mirrorlist
## (Use 0 for all mirrors)
##

## Country : United_Kingdom
Server = https://manjaro.mirrors.uk2.net/testing/$repo/$arch

## Country : France
Server = https://mirrors.eric.ovh/manjaro/testing/$repo/$arch

## Country : Germany
Server = https://ftp.halifax.rwth-aachen.de/manjaro/testing/$repo/$arch

## Country : United_States
Server = https://ziply.mm.fcix.net/manjaro/testing/$repo/$arch

## Country : Colombia
Server = https://mirrors.atlas.net.co/manjaro/testing/$repo/$arch


That explains why I’m seeing sound converter 4.1.1

That is very strange - looking at the mirror’s actual content

Index of /testing/core/x86_64

It shows it is up-to-date - linux619 in version 6.19.2-1

I don’t know the exact method - but I do think that a HEAD request is made to the metadata - and if the timestamp of the local file is the same or newer - the metadata will not be updated, thus the need for the doubled -yy aka forcing the refresh of the metadata

Example on my system

 $ curl -I https://mirrors.dotsrc.org/manjaro/unstable/core/x86_64/core.db
HTTP/2 200 
server: nginx/1.28.0
date: Fri, 27 Feb 2026 11:06:51 GMT
content-type: text/plain
content-length: 156035
last-modified: Fri, 27 Feb 2026 00:00:16 GMT
etag: "69a0de90-26183"
x-frame-options: SAMEORIGIN
referrer-policy: strict-origin
accept-ranges: bytes

Before sync metadata

 $ ls -l /var/lib/pacman/sync/core.db
-rw-r--r-- 1 root root 156031 25 feb 16:01 /var/lib/pacman/sync/core.db

After sync metadata

 $ ls -l /var/lib/pacman/sync/core.db
-rw-r--r-- 1 root root 156035 27 feb 01:00 /var/lib/pacman/sync/core.db

Yeah, but I’m requesting the earlier version, in fact I have linux619-6.19.0-2in the package db.

Then you could use what I always use - the servers of the country you are in:
sudo pacman-mirrors -c germany

… even without a VPN …

That was interesting.

[tracy@daphne ~]$ sudo pacman-mirrors -c germany
[sudo] password for tracy: 
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
  2.303 Germany        : https://mirror.alpix.eu/manjaro/
  1.826 Germany        : http://ftp.uni-kl.de/pub/linux/manjaro/
  2.404 Germany        : https://ftp.gwdg.de/pub/linux/manjaro/
  2.327 Germany        : https://mirror.23m.com/manjaro/
  2.416 Germany        : https://ftp.halifax.rwth-aachen.de/manjaro/
  2.109 Germany        : https://ftp.tu-chemnitz.de/pub/linux/manjaro/
  2.396 Germany        : https://mirror.netcologne.de/manjaro/
  2.121 Germany        : https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/
  1.736 Germany        : https://manjaro.kurdy.org/
::INFO Writing mirror list
::Germany         : https://manjaro.kurdy.org/testing
::Germany         : http://ftp.uni-kl.de/pub/linux/manjaro/testing
::Germany         : https://ftp.tu-chemnitz.de/pub/linux/manjaro/testing
::Germany         : https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/testing
::Germany         : https://mirror.alpix.eu/manjaro/testing
::Germany         : https://mirror.23m.com/manjaro/testing
::Germany         : https://mirror.netcologne.de/manjaro/testing
::Germany         : https://ftp.gwdg.de/pub/linux/manjaro/testing
::Germany         : https://ftp.halifax.rwth-aachen.de/manjaro/testing
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
[tracy@daphne ~]$ sudo pacman -Sy
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)
[tracy@daphne ~]$ sudo pacman -Sy
:: Synchronizing package databases...
error: failed to synchronize all databases (unable to lock database)

I have (currently) no idea why that would be so. :man_shrugging:
I would have gone straight to pacman -Syu
but the locked database issue would likely have been the same.

remove the database lock file - don’t know it’s location off the top of my head right now

Nor do I there are no other package managers running. I double checked.

lsof /var/lib/pacman/db.lck

:backhand_index_pointing_up: Might give you a better idea of what’s hogging it.

pamac update checker may lock the metadata - during an update check - not that it modifies the data - it is likely only to ensure the calculated update is correct.

Remove the lock file /var/lib/pacman/db.lck

I suggest you use sudo with that one - otherwise the output will be empty.

But during a pacman sync - the output is like this - at least partially…

 $ sudo lsof /var/lib/pacman/db.lck
[sudo] password for fh: 
COMMAND   PID USER FD   TYPE DEVICE SIZE/OFF     NODE NAME
pacman  42762 root 5w   REG  259,2        0 50725199 /var/lib/pacman/db.lck
pacman  42808 alpm 5w   REG  259,2        0 50725199 /var/lib/pacman/db.lck

pamac-tray-plasma may have been running concurrently with my testing. But nothing is currently holding db.lck, and I have removed it.

Still getting the same result with

[tracy@daphne pacman]$ sudo pacman -Sy
[sudo] password for tracy: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
[tracy@daphne pacman]$ sudo pacman -Syu linux619
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) linux619-6.19.0-2

Total Installed Size:  152.10 MiB

:: Proceed with installation? [Y/n] n

Is there anything I can rename, and then run -

sudo pacman -Sy

OK, I renamed /var/lib/pacman/sync to /var/lib/pacman/bu-sync and ran sudo pacman -Sy that refreshand resynced the database. I now have correct versions of packages.

I can now do a proper update, then install linux619-6.19.2-1

Thanks guys.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.