Page 1 of 1

"No matching package name" on BookwormPup64 10.0.6

Posted: Wed Jun 26, 2024 5:15 am
by captainkennway

I was wondering, how come puppy manager doesn't find applications on Bookworm like the way I download packages on FossaPup. "Sorry no matching package name" is the error I keep receiving. Am I missing something or am I doing something in the wrong way here? Thanks for the help in advance.


Re: "No matching package name" on BookwormPup64 10.0.6

Posted: Wed Jun 26, 2024 7:08 am
by mikewalsh

@captainkennway :-

Mm. Well, I can't say with any certainty - I don't run it, y'see - but I suspect that Bookwormpup is set up to use Synaptic, rather than the PPM. I think you'll find the PPM is just used to access Puppy packages ONLY, from some of the existing Puppy-only repos.

That's my assumption, anyway. Others will be along with more concrete advice directly. Hang in there! :)

Mike. ;)


Re: "No matching package name" on BookwormPup64 10.0.6

Posted: Thu Jun 27, 2024 2:22 am
by bigpup

Correct.

PPM in BookwormPup64 10.0.6 only has access to the basic repositories of Puppy Linux. There is no repository of added software for BookwormPup64.
Has no access to Debian repositories or other Linux repositories.

Need to use Apt Package Manager or Synaptic GUI to get software.

Menu ->Help has an info for Apt and how to use it.


Re: "No matching package name" on BookwormPup64 10.0.6

Posted: Thu Jun 27, 2024 2:27 pm
by mikeslr

If you're wondering why Puppy Package Manager is still built-in, it's so that you can install applications (packaged as pets) that were specifically created for Puppys. For example, an update of Network Managers, https://www.forum.puppylinux.com/viewto ... 2241#p2241.

When using two Package Managers "the left hand won't know what the right hand is doing". Apt/synaptic keeps track of what it's installed but will be entirely ignorant of what PPM installed, and vice-versa. My practice is to only use PPM for special purposes such as updating built in applications, or applications I never expect to change such as when no longer available via synaptic. For the latter, I employ Bookworm's built-in Menu>Utility>NicOS-Utility-Suite's Save2SFS to create/update an adrv.sfs or ydrv.sfs. For example, my favorite pdf-editor is MasterPDFEditor-4. It is built against the Qt4 framework. Bookworm's repos don't offer Qt4 as it's moved on to Qt5. But I had MasterPDFEditor from earlier Puppys --MikeWalsh has also published a portable-- and Bookworm can use Qt4's if provided. I also package other 'alien' application in a ydrv.sfs so that they will always be available even if I boot pfix=ram.

My Bookworm's Opt via Save2SFS>ydrv.sfs

Bookworm's Opt via Save2SFS.png
Bookworm's Opt via Save2SFS.png (38.62 KiB) Viewed 218 times

Re: "No matching package name" on BookwormPup64 10.0.6

Posted: Thu Jun 27, 2024 5:49 pm
by Marv

I use Apt/synaptic, PPM, ydrvs and portables much as @mikeslr does in BookwormPup64 10.0.6. Generally works fine but I miss (or just haven't found yet) where Apt/synaptic keeps its' record of what it's installed. Is there somewhere analogous to the /var/packages directory that PPM accesses for a quick look/overview without invoking the installer?


Re: "No matching package name" on BookwormPup64 10.0.6

Posted: Thu Jun 27, 2024 6:13 pm
by fredx181
Marv wrote: Thu Jun 27, 2024 5:49 pm

I use Apt/synaptic, PPM, ydrvs and portables much as @mikeslr does in BookwormPup64 10.0.6. Generally works fine but I miss (or just haven't found yet) where Apt/synaptic keeps its' record of what it's installed. Is there somewhere analogous to the /var/packages directory that PPM accesses for a quick look/overview without invoking the installer?

That's all kept in /var/lib/dpkg/info/ .