On 1/16/20, David Christensen <[email protected]> wrote: > On 2020-01-16 02:31, Brian wrote: >> Shouldn't that be >> >> apt install ./freebsd-buildutils_10.3~svn296373-7_amd64.deb ? > > Repeating my command: > > 2020-01-16 06:16:33 root@tinkywinky /home/dpchrist/build > # apt install freebsd-buildutils_10.3~svn296373-7_amd64.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package freebsd-buildutils_10.3~svn296373-7_amd64.deb > E: Couldn't find any package by glob > 'freebsd-buildutils_10.3~svn296373-7_amd64.deb' > E: Couldn't find any package by regex > 'freebsd-buildutils_10.3~svn296373-7_amd64.deb' > > > Using your command: > > 2020-01-16 06:16:22 root@tinkywinky /home/dpchrist/build > # apt install ./freebsd-buildutils_10.3~svn296373-7_amd64.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'freebsd-buildutils' instead of > './freebsd-buildutils_10.3~svn296373-7_amd64.deb' > freebsd-buildutils is already the newest version (10.3~svn296373-7). > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > > That was unexpected.
I hope I'm understanding this correctly (AND that I maintained proper quote attributions, grin). I JUST encountered that one aspect there two nights ago (AGAIN). It's complaining that we're just supposed to use the base package name, NOT the whole long version/release number up to and including the dotDEB part. My latest encounter with it was with dpkg. When I installed a package (on a different operating system), it was "dpkg -i wvdial[version].deb". When I decided to try and purge, that's when I received something similar to yours here: > Note, selecting 'freebsd-buildutils' instead of > './freebsd-buildutils_10.3~svn296373-7_amd64.deb' That's when the little 4-watt light bulb went off overhead for me (AGAIN for the umpteenth time). :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
