Closed izzergh closed 1 year ago
There was an issue in the regex parsing apt
's results. I just fixed it upstream in 8bd5a770a5171b5d78fac7b771b64ce2c7dc4145.
The fix will be available in the upcoming release of mpm
5.13.0.
FYI meta-package-manager v5.13.0 has just been released.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
The goal was to install
snapd
usingapt
viampm
.mpm search snapd
revealed the only package manager I had installed that could installsnapd
wasapt
, so I didmpm install snapd
, which failed as no package manager could find that package.Trying
mpm -v DEBUG --apt install snapd
reveals something weird:mpm
claimsapt
can't find asnapd
, yet it reveals exactly one result somewhere in between.I tested to see if it was an issue with that specific package, I tried the same with
git
with the same results, and I tried with some random package already installed viaapt
with the same result again.Apologies for any weird formatting in the following sections, this is a brand-new install and I haven't had time to install and mess with my preferred terminal emulator.
List package managers
Meta Package Manager version
Meta Package Manager configuration