Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

error: blackarch database is inconsistent: version mismatch on package bluebox-ng... #2392

Closed
GasparVardanyan opened this issue Jul 1, 2019 · 19 comments
Closed

error: blackarch database is inconsistent: version mismatch on package bluebox-ng... #2392

GasparVardanyan opened this issue Jul 1, 2019 · 19 comments
Assignees
@noptrix
Labels
complexity::high A bug that is hard to fix severity::low

Comments

@GasparVardanyan
Copy link

Error message:
$ yay -Fyy
.....
$ yay -Fo /bin/urxvt
error: blackarch database is inconsistent: version mismatch on package bluebox-ng
error: blackarch database is inconsistent: version mismatch on package metasploit
error: blackarch database is inconsistent: version mismatch on package perl-http-parser-xs
error: blackarch database is inconsistent: version mismatch on package python2-coloredlogs
@Edu4rdSHL
Copy link
Contributor

Hello, @GasparVardanyan thanks for reporting. It doesn't affect the functionality still if pacman say "error", we will investigate what's causing that but it's with lower priority.

@noraj
Copy link
Contributor

noraj commented Oct 2, 2019

Reproducted with pacman in the BA sandbox

blackarch-devtools -t -e 'pacman -Fyy && pacman -Fo /bin/urxvt' -p ./gobuster-2:281.f7ed22d-1-x86_64.pkg.tar.xz
loading packages...
warning: gobuster-2:281.f7ed22d-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) gobuster-2:281.f7ed22d-1

Total Installed Size:  7,11 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                                                 [########################################################################################] 100%
(1/1) checking package integrity                                                                                                               [########################################################################################] 100%
(1/1) loading package files                                                                                                                    [########################################################################################] 100%
(1/1) checking for file conflicts                                                                                                              [########################################################################################] 100%
(1/1) checking available disk space                                                                                                            [########################################################################################] 100%
:: Processing package changes...
(1/1) reinstalling gobuster                                                                                                                    [########################################################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Package ./gobuster-2:281.f7ed22d-1-x86_64.pkg.tar.xz installed correctly! Testing it now...
:: Synchronizing package databases...
 core                                                                                                                 835.6 KiB   475K/s 00:02 [########################################################################################] 100%
 extra                                                                                                                  8.8 MiB  2.20M/s 00:04 [########################################################################################] 100%
 community                                                                                                             19.3 MiB  2.12M/s 00:09 [########################################################################################] 100%
 multilib                                                                                                             254.1 KiB  0.00B/s 00:00 [########################################################################################] 100%
 blackarch                                                                                                              7.1 MiB  9.20M/s 00:01 [########################################################################################] 100%
 blackarch.sig                                                                                                        566.0   B  0.00B/s 00:00 [########################################################################################] 100%
error: blackarch database is inconsistent: version mismatch on package bluebox-ng
error: blackarch database is inconsistent: version mismatch on package metasploit
error: blackarch database is inconsistent: version mismatch on package perl-http-parser-xs
error: blackarch database is inconsistent: version mismatch on package python2-coloredlogs

@noraj noraj added the status::investigating Bug in the process of searching what is the root cause. label Oct 2, 2019
@noptrix
Copy link
Contributor

noptrix commented Apr 16, 2020

guys any news on this?

@noraj
Copy link
Contributor

noraj commented Apr 17, 2020

No and I don't really understand what cause an issue here.

@crabdancing
Copy link

crabdancing commented May 3, 2020 •
edited

It happened on my machine too. :(

$ pacman -F /usr/bin/bash
usr/bin/bash is owned by core/bash 5.0.016-1
error: blackarch database is inconsistent: version mismatch on package bluebox-ng
error: blackarch database is inconsistent: version mismatch on package metasploit
error: blackarch database is inconsistent: version mismatch on package perl-http-parser-xs
error: blackarch database is inconsistent: version mismatch on package python2-coloredlogs

@Edu4rdSHL
Copy link
Contributor

It's a minor issue, doesn't interfere with pacman or utilities work.

@noraj
Copy link
Contributor

noraj commented May 3, 2020

Also -Fyy leads to partial upgrade.

@Edu4rdSHL
Copy link
Contributor

It doesn't. -F option works apart from -S option, they use two different databases.

@noraj
Copy link
Contributor

noraj commented May 3, 2020

My bad so 😅

@crabdancing
Copy link

crabdancing commented May 6, 2020 •
edited

This error should be an easy fix. I believe the problem is a version inconsistency between the files database and the sync database, in the BlackArch repos.
For example, let's compare the version numbers of bluebox-ng as shown in files versus in sync.

$ pacman --machinereadable -F bluebox-ng
error: blackarch database is inconsistent: version mismatch on package bluebox-ng
error: blackarch database is inconsistent: version mismatch on package metasploit
error: blackarch database is inconsistent: version mismatch on package perl-http-parser-xs
error: blackarch database is inconsistent: version mismatch on package python2-coloredlogs
blackarchbluebox-ng1:0.1.8-1usr/bin/bluebox-ng

Version: 1:0.1.8-1 (AFAIK the only way to get pacman to spit out the version number is with --machinereadable.)

$ pacman -Ss bluebox-ng
blackarch/bluebox-ng 1:1.1.0-4 (blackarch blackarch-voip blackarch-scanner blackarch-fuzzer)
    A GPL VoIP/UC vulnerability scanner.

Version: 1:1.1.0-4

Any idea how such a large gap in version numbers was caused, but only for these specific packages?

Edit:

So, from what I can see, either:

  • Somehow the files database is not updating for these packages.

  • These files db has been updating, but the version number isn't.

It should be noted that, obviously, in the former case, using -F commands to search for a package by the files contained within it, might not work as expected if those files changed.

Edit 2:

I just tried -Qling bluebox-ng, and comparing that with -Fl. The file list looks identical, which seems implausible if the file info was that out of date. So it seems likely to me that the version number simply isn't updating for these packages' files db entries.

@crabdancing
Copy link

AGHHH why will no one fix this it's so irritating

@livello
Copy link

livello commented Aug 14, 2020

I am very disappointed with it!

❯ sudo pacman -Fyy GLES/gl.h
:: Synchronizing package databases...
 core                                                                   878.5 KiB  3.73 MiB/s 00:00 [##########################################################] 100%
 extra                                                                    9.0 MiB  3.75 MiB/s 00:02 [##########################################################] 100%
 community                                                               21.4 MiB  3.99 MiB/s 00:05 [##########################################################] 100%
 multilib                                                               231.0 KiB  2.69 MiB/s 00:00 [##########################################################] 100%
 repo-ck                                                                  2.1 MiB  1014 KiB/s 00:02 [##########################################################] 100%
 blackarch                                                                8.1 MiB  2.71 MiB/s 00:03 [##########################################################] 100%
 blackarch.sig                                                          566.0   B  0.00   B/s 00:00 [##########################################################] 100%
error: blackarch database is inconsistent: version mismatch on package bluebox-ng
error: blackarch database is inconsistent: version mismatch on package metasploit
error: blackarch database is inconsistent: version mismatch on package perl-http-parser-xs
error: blackarch database is inconsistent: version mismatch on package python2-coloredlogs

@livello
Copy link

livello commented Aug 14, 2020

I found workaround!
Disable blackarch repo in /etc/pacman.conf
after that
sudo pacman -Fyy gl.h
Then enable blackarch repo and repeat
sudo pacman -Fyy gl.h
It works now.

@MiskolcziRichard
Copy link

Re-enabling the blackarch repo didn't solve it for me. It produces the same error message

@Edu4rdSHL
Copy link
Contributor

Just for your information: this issue does not affect the functionality, stability or performance of BlackArch in any way.

@aancw
Copy link
Member

aancw commented Feb 10, 2021

Is this issue still used or can be closed?

@Edu4rdSHL
Copy link
Contributor

It's still present but really doesn't affect anything. We can keep it open but I doubt it would be "fixed".

@Edu4rdSHL Edu4rdSHL removed the status::investigating Bug in the process of searching what is the root cause. label Mar 15, 2021
@Edu4rdSHL
Copy link
Contributor

Hey @noptrix , please can you take a look in the server to the pacman's database/files for these packages? Seems that we need to rebuild the databases to fix it.

@BlackArch BlackArch locked and limited conversation to collaborators Apr 7, 2021
@BlackArch BlackArch deleted a comment from rebelld1312 Apr 7, 2021
@BlackArch BlackArch deleted a comment from Edu4rdSHL Apr 7, 2021
@BlackArch BlackArch deleted a comment from rebelld1312 Apr 7, 2021
@BlackArch BlackArch deleted a comment from Edu4rdSHL Apr 7, 2021
@BlackArch BlackArch deleted a comment from Edu4rdSHL Apr 7, 2021
@BlackArch BlackArch deleted a comment from rebelld1312 Apr 7, 2021
@Edu4rdSHL Edu4rdSHL added the wont label Apr 29, 2021
@Edu4rdSHL
Copy link
Contributor

As it issue is really very low priority, doesn't affect the users/pacman results in any way but to "fix" it we need to do a lot of work that can lead to a general database corruption in our mirrors, we will leave it.

@Edu4rdSHL Edu4rdSHL added complexity::high A bug that is hard to fix severity::low labels Apr 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@noptrix noptrix

Labels
complexity::high A bug that is hard to fix severity::low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@noptrix @aancw @livello @noraj @crabdancing @Edu4rdSHL @GasparVardanyan @MiskolcziRichard