Arch Linux

stefano

Member

Registered: 2011-04-09

Posts: 258

dvzrv.db for dvzrv repo has disappeared (404 error) [SOLVED]

Pacman can no longer find the db file for the dvzrv repo at https://pkgbuild.com/~dvzrv/repo/$arch . In fact the file does not seem to be there any longer.

I honestly can't remember why I added that repo to my pacman.conf file and I have spent the last 30 minutes trying to find out a pacman search option that would allow me to figure out what a repo provides to no avail. I suppose it is not possible through pacman (at least the -Qi output does not provide any repo info, so perhaps it is not stored anywhere). I have removed the repo for the time being, but I would like to solve the issue in a more satisfactory way.

Suggestions?

Last edited by stefano (2021-08-31 19:18:14)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,671

Re: dvzrv.db for dvzrv repo has disappeared (404 error) [SOLVED]

Granted you've ran -Sy in some form while it was present, you will have the sync database and can query with -Sl dvzrv the entire contents according to your sync database.

a821

Member

Registered: 2012-10-31

Posts: 381

Re: dvzrv.db for dvzrv repo has disappeared (404 error) [SOLVED]

it seems the repo was renamed??
https://wiki.archlinux.org/title/Unoffi … s#realtime

stefano

Member

Registered: 2011-04-09

Posts: 258

Re: dvzrv.db for dvzrv repo has disappeared (404 error) [SOLVED]

it seems the repo was renamed??
https://wiki.archlinux.org/title/Unoffi … s#realtime

Thank you, that was it, the real time kernel extensions. Works like a charm now.

stefano

Member

Registered: 2011-04-09

Posts: 258

Re: dvzrv.db for dvzrv repo has disappeared (404 error) [SOLVED]

Granted you've ran -Sy in some form while it was present, you will have the sync database and can query with -Sl dvzrv the entire contents according to your sync database.

That, unfortunately, did not work, even though I update my system once  a week on average, so I'm sure I did it with that repo active. Luckily, I was able to solve the issue after a821 pointer. Thanks anyways! I'm sure that command will come handy sooner or later