Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #263372 > unrolled thread

PATH question

Back to article view | Back to linux.debian.user

Contents

  PATH question Thomas George <debianlist@mailfence.com> - 2023-11-11 19:10 +0100
    Re: PATH question Greg Wooledge <greg@wooledge.org> - 2023-11-11 19:30 +0100
      Re: PATH question Thomas George <debianlist@mailfence.com> - 2023-11-11 19:50 +0100
        Re: PATH question David <bouncingcats@gmail.com> - 2023-11-11 23:20 +0100
          Re: PATH question Greg Wooledge <greg@wooledge.org> - 2023-11-12 01:20 +0100
            Re: PATH question The Wanderer <wanderer@fastmail.fm> - 2023-11-12 01:30 +0100
              Re: PATH question Thomas George <debianlist@mailfence.com> - 2023-11-12 15:30 +0100
                Re: PATH question Greg Wooledge <greg@wooledge.org> - 2023-11-12 15:40 +0100
                  Re: PATH question Max Nikulin <manikulin@gmail.com> - 2023-11-12 16:10 +0100
                  Re: PATH question Charles Kroeger <mbone@gmx.co.uk> - 2023-11-18 08:40 +0100

#263372 — PATH question

In a newly installed bookworm I edited PATH to 
/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin in order to 
install google-chrome.  This worked but the installed PATH had  two 
other entries, something about games?

I failed to save and did not take note of all the installed PATH entries.

I have no sound with bookworm. Could these other entries be the problem?

I would appreciate if anyone responding includes the missing PATH entries

Tom

[toc] | [next] | [standalone]

#263373

On Sat, Nov 11, 2023 at 01:03:45PM -0500, Thomas George wrote:
> In a newly installed bookworm I edited PATH to
> /usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin

What, exactly, did you edit?

> in order to
> install google-chrome.

Now that makes no sense... unless you ran into the buster su issue.

Please see <https://wiki.debian.org/NewInBuster#Changes>.

>  This worked but the installed PATH had  two other
> entries, something about games?

/usr/local/games and /usr/games

> I failed to save and did not take note of all the installed PATH entries.
> 
> I have no sound with bookworm. Could these other entries be the problem?

I sincerely doubt it.

[toc] | [prev] | [next] | [standalone]

#263374

I downloaded the google-chrome deb file to /opt/

used dpkg to install the program.

initial attempt failed, two lib files missing.

added the sbin entries to path and tried again

missing files found on the dvd installation disk and google-chrome 
successfully installed

On 11/11/23 13:22, Greg Wooledge wrote:
> On Sat, Nov 11, 2023 at 01:03:45PM -0500, Thomas George wrote:
>> In a newly installed bookworm I edited PATH to
>> /usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin
> What, exactly, did you edit?
>
>> in order to
>> install google-chrome.
> Now that makes no sense... unless you ran into the buster su issue.
>
> Please see <https://wiki.debian.org/NewInBuster#Changes>.
>
>>    This worked but the installed PATH had  two other
>> entries, something about games?
> /usr/local/games and /usr/games
>
>> I failed to save and did not take note of all the installed PATH entries.
>>
>> I have no sound with bookworm. Could these other entries be the problem?
> I sincerely doubt it.
>

[toc] | [prev] | [next] | [standalone]

#263384

On Sat, 11 Nov 2023 at 18:42, Thomas George <debianlist@mailfence.com> wrote:

> I downloaded the google-chrome deb file to /opt/
>
> used dpkg to install the program.
>
> initial attempt failed, two lib files missing.
>
> added the sbin entries to path and tried again

Hi, the 'apt install' command does have the capability to install a local .deb
package file together with its dependencies if they are available in
the configured repositories.

This capability seems to be not mentioned in the manpages
of 'apt' or 'apt-get' [1].

Looking for an authoritative source of information to show you,
I found only this:
  https://wiki.debian.org/DebianPackageManagement#Installing_and_removing_packages
which says:
  You can also install a .deb file with:
  # apt install </path/to/deb/file/debfile.deb>

My understanding is that the <target> must look like a pathname.
So, to install 'debfile.deb' in the current directory, it should look like
  apt install ./debfile.deb

Maybe someone else knows where the authoritative documentation
of this capability can be read, if there is any.

Maybe someone else knows why this isn't documented in the manpages.
I have a hazy recollection of possibly reading sometime that 'apt'
authors might
intend to rewrite the package regex handling in future, so maybe how this
works might change, so that might be why it hasn't been documented.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874763

[toc] | [prev] | [next] | [standalone]

#263391

On Sat, Nov 11, 2023 at 10:17:09PM +0000, David wrote:
> Looking for an authoritative source of information to show you,
> I found only this:
>   https://wiki.debian.org/DebianPackageManagement#Installing_and_removing_packages
> which says:
>   You can also install a .deb file with:
>   # apt install </path/to/deb/file/debfile.deb>
> 
> My understanding is that the <target> must look like a pathname.
> So, to install 'debfile.deb' in the current directory, it should look like
>   apt install ./debfile.deb
> 
> Maybe someone else knows where the authoritative documentation
> of this capability can be read, if there is any.

I think you've found it.  It's not in ANY man page that I'm aware of.

[toc] | [prev] | [next] | [standalone]

#263392

[Multipart message — attachments visible in raw view] — view raw

On 2023-11-11 at 19:09, Greg Wooledge wrote:

> On Sat, Nov 11, 2023 at 10:17:09PM +0000, David wrote:
>
>> Looking for an authoritative source of information to show you,
>> I found only this:
>>   https://wiki.debian.org/DebianPackageManagement#Installing_and_removing_packages
>> which says:
>>   You can also install a .deb file with:
>>   # apt install </path/to/deb/file/debfile.deb>
>> 
>> My understanding is that the <target> must look like a pathname.
>> So, to install 'debfile.deb' in the current directory, it should look like
>>   apt install ./debfile.deb
>> 
>> Maybe someone else knows where the authoritative documentation
>> of this capability can be read, if there is any.
> 
> I think you've found it.  It's not in ANY man page that I'm aware of.

My reflexive reaction was "that sounds like something that warrants a
wishlist-level bug report".

Then I went looking, and I found a *normal*-level bug report that seems
to cover the matter: https://bugs.debian.org/874763

And that bug report is from 2017, and has no replies.

Unless someone is interested enough to write up a patch for apt.8 and
send it to that bug report, I suspect that this will go unaddressed for
a while longer.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#263412

Alternately dpkg -i debfile.deb works.

Tom George

On 11/11/23 19:28, The Wanderer wrote:
> On 2023-11-11 at 19:09, Greg Wooledge wrote:
>
>> On Sat, Nov 11, 2023 at 10:17:09PM +0000, David wrote:
>>
>>> Looking for an authoritative source of information to show you,
>>> I found only this:
>>>    https://wiki.debian.org/DebianPackageManagement#Installing_and_removing_packages
>>> which says:
>>>    You can also install a .deb file with:
>>>    # apt install </path/to/deb/file/debfile.deb>
>>>
>>> My understanding is that the <target> must look like a pathname.
>>> So, to install 'debfile.deb' in the current directory, it should look like
>>>    apt install ./debfile.deb
>>>
>>> Maybe someone else knows where the authoritative documentation
>>> of this capability can be read, if there is any.
>> I think you've found it.  It's not in ANY man page that I'm aware of.
> My reflexive reaction was "that sounds like something that warrants a
> wishlist-level bug report".
>
> Then I went looking, and I found a *normal*-level bug report that seems
> to cover the matter: https://bugs.debian.org/874763
>
> And that bug report is from 2017, and has no replies.
>
> Unless someone is interested enough to write up a patch for apt.8 and
> send it to that bug report, I suspect that this will go unaddressed for
> a while longer.
>

[toc] | [prev] | [next] | [standalone]

#263417

On Sun, Nov 12, 2023 at 09:25:26AM -0500, Thomas George wrote:
> Alternately dpkg -i debfile.deb works.

That doesn't install the dependencies.  It may leave your packages in
a semi-broken state, requiring you to run "apt-get -f install" afterward
to fix it.

Using "apt install ./debfile.deb" pulls in the dependencies and keeps
things in a working state at all times, if possible.

Using "dpkg -i" and then "apt-get -f install" was the old way.  You'll
still see people recommending it, because they don't know any better,
and old methods that still "work" (most of the time) take a long time
to die out.

It doesn't help that "apt install ./file" is not documented in the
official man pages.  People can only learn about it from the wiki, or
from word of mouth.

[toc] | [prev] | [next] | [standalone]

#263421

On 12/11/2023 21:37, Greg Wooledge wrote:
> It doesn't help that "apt install ./file" is not documented in the
> official man pages.  People can only learn about it from the wiki, or
> from word of mouth.

It is documented in various guides:

https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#listofadvancedpagementoperations

> Table 2.13. List of advanced package management operations

> apt install /path/to/package_filename.deb 	install a local package to the system, meanwhile try to resolve dependency automatically 

https://www.debian.org/doc/manuals/debian-handbook/sect.apt-get.en.html#id-1.9.17.11.31
> If the package to install has been made available to you under the form
> of a simple .deb file without any associated package repository, it is
> still possible to use APT to install it together with its dependencies
> (provided that the dependencies are available in the configured
> repositories) with a simple command: apt install
> ./path-to-the-package.deb. The leading ./ is important to make it clear
> that we are referring to a filename and not to the name of a package
> available in one of the repositories.

[toc] | [prev] | [next] | [standalone]

#263640

> apt-get -f install

dpkg --configure -a 

I had to use that this morning after the many nvidia related updates that
failed to build the module required to set up the packages in waiting. 

-- 
CK

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web