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

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

How to get rid of the synaptic message (mentioned below) at the end of installing a package?

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

Contents

  How to get rid of the synaptic message (mentioned below) at the end  of installing a package? "Susmita/Rajib" <bkpsusmitaa@gmail.com> - 2023-04-01 08:50 +0200
    Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? davidson <davidson@freevolt.org> - 2023-04-03 05:20 +0200
    Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? "Susmita/Rajib" <bkpsusmitaa@gmail.com> - 2023-04-05 17:00 +0200
      Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? "Susmita/Rajib" <bkpsusmitaa@gmail.com> - 2023-04-06 08:10 +0200
        Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? "Susmita/Rajib" <bkpsusmitaa@gmail.com> - 2023-04-06 08:30 +0200
    Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? David Wright <deblis@lionunicorn.co.uk> - 2023-04-06 01:40 +0200
      Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? zithro <slack@rabbit.lu> - 2023-04-06 15:40 +0200
        Re: How to get rid of the synaptic message (mentioned below) at the  end of installing a package? David Wright <deblis@lionunicorn.co.uk> - 2023-04-07 00:50 +0200

#256590 — How to get rid of the synaptic message (mentioned below) at the end of installing a package?

My illustrious team leaders and senior debian-user list-members,

My present Debian system installed from "Official Debian GNU/Linux
Live 11.6.0 lxde 2022-12-17T11:46"

While installing a package I receive this following message:

W: Download is performed unsandboxed as root as file
'/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
pkgAcquire::Run (13: Permission denied)

What should I do to address this report or stop receiving this
message? It doesn't appear to be a harmful report so far as my system
is concerned. My user-id can't access root report, I guess. But any
advice would be welcome.

Best wishes,
Rajib B
Etc.

[toc] | [next] | [standalone]

#256661 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

On Sat, 1 Apr 2023 Susmita/Rajib wrote:
> My illustrious team leaders and senior debian-user list-members,
>
> My present Debian system installed from "Official Debian GNU/Linux
> Live 11.6.0 lxde 2022-12-17T11:46"
>
> While installing a package I receive this following message:

I do not use synaptic, and know nothing about it other than that it is
a GUI package manager.

The warning below looks to me as though synaptic tried (and failed) to
store a temporary file in root's home directory.

If I were in your place, I would wonder why it did not use the
invoking user's home directory instead.

Maybe there are reasons. I would want to know what they are, and
endeavor to judge for myself whether they are good ones.

> W: Download is performed unsandboxed as root as file
> '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
> pkgAcquire::Run (13: Permission denied)

This matches a bug report:

   Bug #864179 - synaptic: Message appears:
   "W: Download is performed unsandboxed as root as file
   '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
   pkgAcquire::Run (13: Permiso denegado)"

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864179

> What should I do to address this report [...]

You could send a message to

  864179@bugs.debian.org

informing the maintainer that the bug affects you.

> [...] or stop receiving this message?

You could use a different tool for package management, like apt,
aptitude, or apt-{get,cache,etc}.

> It doesn't appear to be a harmful report so far as my system is
> concerned.

I am not qualified to confirm or deny the accuracy of this perception.

> My user-id can't access root report, I guess.

What you mean by this is unclear to me. Are you not the administrator
of the machine? What "root report" are you referring to?

> But any advice would be welcome.

I would not ignore warnings from a package manager.

-- 
Hackers are free people. They are like artists. If they are in a good
mood, they get up in the morning and begin painting their pictures.
-- Vladimir Putin

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

#256783 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

    To: debian-user@lists.debian.org
    Subject: Re: How to get rid of the synaptic message (mentioned
below) at the end of installing a package?
    From: davidson <davidson@freevolt.org>
    Date: Mon, 3 Apr 2023 03:10:28 +0000 (UTC)
    Message-id: <[🔎] alpine.DEB.2.21.2304030310190.28350@azone.org>
    In-reply-to: <[🔎]
CAEG4cZVJtcgcaNK_0uCbt+DPGUcSSoHJEtxVbkNGx8aPh++APA@mail.gmail.com>
    References: <[🔎]
CAEG4cZVJtcgcaNK_0uCbt+DPGUcSSoHJEtxVbkNGx8aPh++APA@mail.gmail.com>

I tried multiple times to post this message. But the Earlier identical Messages
dated Mon, 3 Apr 2023 13:55:33 +0530 (IndianST) / Mon, 3 Apr 2023
01:25:33 -0700 (PDT), Mon, 3 Apr 2023 20:11:27 +0530 (IndianST) / Mon,
3 Apr 2023 07:41:27 -0700 (PDT),
Mon, 3 Apr 2023 20:59:20 +0530 (IndianST) / Mon, 3 Apr 2023 08:29:20
-0700 (PDT),
Tue, 4 Apr 2023 21:42:15 +0530 (IndianST) / Tue, 4 Apr 2023 09:12:15
-0700 (PDT) and some more appear to have been lost.

Finally, I heard from the List Maintainer the reason for my messages
getting dropped, confirming what Mr. Davison had indicated earlier. I
have removed offending url that caused my multiple emails getting
dropped by the List's spam protection because of BIT_LY_SPAM_BODY
rule. If only I could have been sent a warning message informing me of
the reason why my message won't be allowed would have saved a lot of
my time. Anyway, what is lost is already lost.


In reply to Mr. Davidson's email:

   [   ...   ]
I do not use synaptic, and know nothing about it other than that it is
a GUI package manager.

The warning below looks to me as though synaptic tried (and failed) to
store a temporary file in root's home directory.

If I were in your place, I would wonder why it did not use the
invoking user's home directory instead.

Maybe there are reasons. I would want to know what they are, and
endeavor to judge for myself whether they are good ones.

    W: Download is performed unsandboxed as root as file
    '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
    pkgAcquire::Run (13: Permission denied)


This matches a bug report:

  Bug #864179 - synaptic: Message appears:
  "W: Download is performed unsandboxed as root as file
  '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
  pkgAcquire::Run (13: Permiso denegado)"

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

Thank you.

   [   ...   ]
You could send a message to

 864179@bugs.debian.org

informing the maintainer that the bug affects you.
   [   ...   ]

Ok. And done


   [   ...   ]
You could use a different tool for package management, like apt,
aptitude, or apt-{get,cache,etc}.
   [   ...   ]

Beyond me to read the man pages and make out something meaningful out
of them. I have a very limited comprehension. I had posted a note to
the debian-user list group about this. The emails are here:
(1)     https://lists.debian.org/debian-user/2021/04/msg00552.html
(2)     https://lists.debian.org/debian-user/2021/06/msg00432.html
with an illustrative, but incomplete, Mind Map at:
the OFFENDING URL with /Apt_readingManPages, which is very pertinent
for this conversation and doesn't contain offending content.

   [   ...   ]
I am not qualified to confirm or deny the accuracy of this perception.
   [   ...   ]
:)  :D


   [   ...   ]
What you mean by this is unclear to me. Are you not the administrator
of the machine? What "root report" are you referring to?
   [   ...   ]
I meant that I was using the computer as a user, but for installing
packages, I entered my root password for synaptic. I thought synaptic
wasn't properly configured to report outputs from root tasks to the
user.

   [   ...   ]
I would not ignore warnings from a package manager.
   [   ...   ]
But I am limited.

Thank you for replying to my email.
Best wishes.
Rajib
Etc.

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

#256800 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

    To: debian-user@lists.debian.org
    Subject: Re: How to get rid of the synaptic message (mentioned
below) at the end of installing a package?
    From: David Wright <deblis@lionunicorn.co.uk>
    Date: Wed, 5 Apr 2023 18:30:24 -0500
    Message-id: <ZC4EkMptNTzJT/5r@axis.corp>
    Reply-to: debian-user@lists.debian.org
    In-reply-to: <[🔎]
CAEG4cZVJtcgcaNK_0uCbt+DPGUcSSoHJEtxVbkNGx8aPh++APA@mail.gmail.com>
    References: <[🔎]
CAEG4cZVJtcgcaNK_0uCbt+DPGUcSSoHJEtxVbkNGx8aPh++APA@mail.gmail.com>

[    ...   ]

Dear Mr. Wright,

I remember our earlier interactions. But this time the length you have
gone to to help me gain a perspective is beyond thanks. It is
admirable, particularly for a novice who wouldn't likely make a
difference to the world.

You said, "... It's trivial to provoke this message, though I can't be sure of
precisely why APT generates it ..."

You added, "... This time there's no warning, and the package is
cached ... I guess you have to sort out why a file would be being read
from /root/.synaptic/tmp//tmp_sh. I know next to nothing about
synaptic ..."

I have read the lines generated by apt while installing, though they
are very complicated for me.

In the matter of your uncertainty, please try to imagine my condition
then. Which is why I need GPT advanced. We can't access our
subconscious processing. We are easily tired, but AI won't tire. If my
questions are reasonable and clear, all of them would be answered. I
would then be able to learn and solve from a,b,c to 1,2,3 of gates,
flip-flops and storage to AI-level computing and illuminate the grey
areas within. So AGI is a demand that shall be met, eventually.

I have the other post in this thread, to Mr. Davidson, which explains
why I am stuck with synaptic and do not venture out to explore apt.
man pages are mostly without examples and are to be linearly learned,
whereas real-time computing using the terminals require a very
complicated intermesh of learning, analyses, syntheses, evaluations,
experience and intuition.

I have my idea recorded in the Google Drive folder that could be
accessed from a Shortener Link That Must Not Be Named other than BIT
and the LY accompanying it with a clear example of how I visualise our
Enhanced Manual (EnMan) Pages should be.

It is not that I fear adventure, but I fear that I won't receive any
support precisely with explanations on the 'why' part, when I need
them the most. I find that we are all virtually like tiny lamps with a
lot of darkness around us. At least, some brighter lamps came together
and produced this Open Source system where and in whih one is not
taxed to breathe air.

So bottom-line that I derive from your explanation is:    it is better
to ignore the warnings altogether unless and until the system fails.

But I must thank you for your kind explanations. Mr. Davidson has also
been very kind to me. Many of the senior members I have interacted
with here have been very kind and accommodating. Free Software
Movement upholds that people generally barter and share. It must be
the environment that empowers kindness. I thank you all. But I lament
that we all are ultimately limited.

We live in an era of confusion because of the limitations in human
processing abilities, particularly in computing. Hopefully, this
limitations too shall be our past.

I very firmly believe that Debian should explore the OpenAI so long as
it is open, and the AGI domain, to create an offshoot of the GPTn,
HuggingGPT, et al, to implement it to harmonise various aspects of the
Debian universe, particularly, replacing the man pages with something
more reflective of the mesh network that the various computing domains
represent.

Another aspect which I expect is a pre-determined size,
time-dependent, log / index file, recording CPU processing steps, each
step at a time, even if the computation speed reduces to half, and let
GPT derive associations between the steps and the problems that the
system faces. This General Transformer is really an interesting field.
I hope to find someone who could teach me the mathematical basis for
these transformers to work, without my joining a paid institution with
a syllabus and structured learning with Time-Bound, Roted, Closed-Book
Exams.

Best wishes,
Rajib
Etc.

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

#256801 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

Bottomline:
---------------
The very question :
[Quote]
How to get rid of the synaptic message (mentioned below) at the end of
installing a package?
[EndQuote]
becomes immaterial as, like Mr. Davidson so discreetly mentions, THIS IS A BUG.

SO, MAY THIS THREAD BE TREATED AS CLOSED.

Best wishes,
Rajib
Etc.

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

#256799 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

On Sat 01 Apr 2023 at 11:58:49 (+0530), Susmita/Rajib wrote:
> My present Debian system installed from "Official Debian GNU/Linux
> Live 11.6.0 lxde 2022-12-17T11:46"
> 
> While installing a package I receive this following message:
> 
> W: Download is performed unsandboxed as root as file
> '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
> pkgAcquire::Run (13: Permission denied)
> 
> What should I do to address this report or stop receiving this
> message? It doesn't appear to be a harmful report so far as my system
> is concerned. My user-id can't access root report, I guess. But any
> advice would be welcome.

It's trivial to provoke this message, though I can't be sure of
precisely why APT generates it. Here's an example of installing
the new yt-dlp program. This system runs bullseye, but I'm going
to install a downloaded copy of the bookworm¹ version (and so no
disturbance of the sources.list).

  # ls -l yt-dlp_2023.0*
  -rw-r--r-- 1 root root 1739188 Jan  6 21:12 yt-dlp_2023.01.06-1_all.deb
  -rw-r--r-- 1 root root 1777260 Mar 26 03:43 yt-dlp_2023.03.04-1~bpo11+1_all.deb
  # apt-get install ./yt-dlp_2023.01.06-1_all.deb 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'yt-dlp' instead of './yt-dlp_2023.01.06-1_all.deb'
  Suggested packages:
    libfribidi-bin | bidiv phantomjs
  The following NEW packages will be installed:
    yt-dlp
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/1739 kB of archives.
  After this operation, 9644 kB of additional disk space will be used.
  Get:1 /root/yt-dlp_2023.01.06-1_all.deb yt-dlp all 2023.01.06-1 [1739 kB]
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done
  Selecting previously unselected package yt-dlp.
  (Reading database ... 357613 files and directories currently installed.)
  Preparing to unpack .../yt-dlp_2023.01.06-1_all.deb ...
  Unpacking yt-dlp (2023.01.06-1) ...
  Setting up yt-dlp (2023.01.06-1) ...
  Processing triggers for man-db (2.9.4-2) ...
  Scanning processes...
  Scanning processor microcode...
  Scanning linux images...
  Running kernel seems to be up-to-date.
  The processor microcode seems to be up-to-date.
  No services need to be restarted.
  No containers need to be restarted.
  No user sessions are running outdated binaries.
  N: Download is performed unsandboxed as root as file '/root/yt-dlp_2023.01.06-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
  # ls -l /var/cache/apt/archives/
  total 4
  -rw-r----- 1 root root    0 Jan  1  2022 lock
  drwx------ 2 _apt root 4096 Apr  5 14:09 partial
  # 

There's your warning. Note that the archives/ directory is still
empty, and also who owns partial/.

Now I'll purge yt-dlp and install it again, but the bullseye-backports
version this time. For a level playing field, I'll install a downloaded
copy again. My sources.list does contain backports, but I don't know
whether that's relevant or not.

  # apt-get purge yt-dlp
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer required:
    python3-brotli python3-pycryptodome python3-websockets
  Use 'apt autoremove' to remove them.
  The following packages will be REMOVED:
    yt-dlp*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  After this operation, 9644 kB disk space will be freed.
  Do you want to continue? [Y/n] 
  (Reading database ... 358704 files and directories currently installed.)
  Removing yt-dlp (2023.01.06-1) ...
  Processing triggers for man-db (2.9.4-2) ...
  # apt-get install ./yt-dlp_2023.03.04-1~bpo11+1_all.deb 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'yt-dlp' instead of './yt-dlp_2023.03.04-1~bpo11+1_all.deb'
  Suggested packages:
    libfribidi-bin | bidiv phantomjs
  The following NEW packages will be installed:
    yt-dlp
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1777 kB of archives.
  After this operation, 9864 kB of additional disk space will be used.
  Get:1 http://deb.debian.org/debian bullseye-backports/main amd64 yt-dlp all 2023.03.04-1~bpo11+1 [1777 kB]
  Fetched 1777 kB in 1s (3370 kB/s)
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done
  Selecting previously unselected package yt-dlp.
  (Reading database ... 357613 files and directories currently installed.)
  Preparing to unpack .../yt-dlp_2023.03.04-1~bpo11+1_all.deb ...
  Unpacking yt-dlp (2023.03.04-1~bpo11+1) ...
  Setting up yt-dlp (2023.03.04-1~bpo11+1) ...
  Processing triggers for man-db (2.9.4-2) ...
  Scanning processes...
  Scanning processor microcode...
  Scanning linux images...
  Running kernel seems to be up-to-date.
  The processor microcode seems to be up-to-date.
  No services need to be restarted.
  No containers need to be restarted.
  No user sessions are running outdated binaries.
  # ls -l /var/cache/apt/archives/
  total 1740
  -rw-r----- 1 root root       0 Jan  1  2022 lock
  drwx------ 2 _apt root    4096 Apr  5 14:11 partial
  -rw-r--r-- 1 root root 1777260 Mar 26 03:43 yt-dlp_2023.03.04-1~bpo11+1_all.deb
  # 

This time there's no warning, and the package is cached.

User _apt (UID 100) does not own much:

  # find / -mount -user 100 -printf '%u\t%g\t%p\n'
  _apt    root    /var/lib/apt/lists/partial
  _apt    root    /var/lib/apt/lists/auxfiles
  _apt    root    /var/cache/apt/archives/partial
  # 

AIUI partial/ is designed to avoid ever having partially downloaded
files kicking around in their parent directory. I don't know any more
of the details than that.

I guess you have to sort out why a file would be being read from
/root/.synaptic/tmp//tmp_sh. I know next to nothing about synaptic.

¹ All the dependencies of yt-dlp are unversioned, so installing
  a "foreign" version is unlikely to cause trouble.

Cheers,
David.

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

#256806 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

On 06 Apr 2023 01:30, David Wright wrote:
> On Sat 01 Apr 2023 at 11:58:49 (+0530), Susmita/Rajib wrote:
>> My present Debian system installed from "Official Debian GNU/Linux
>> Live 11.6.0 lxde 2022-12-17T11:46"
>>
>> While installing a package I receive this following message:
>>
>> W: Download is performed unsandboxed as root as file
>> '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
>> pkgAcquire::Run (13: Permission denied)
>>
>> What should I do to address this report or stop receiving this
>> message? It doesn't appear to be a harmful report so far as my system
>> is concerned. My user-id can't access root report, I guess. But any
>> advice would be welcome.
> It's trivial to provoke this message, though I can't be sure of
> precisely why APT generates it. Here's an example of installing
> the new yt-dlp program. This system runs bullseye, but I'm going
> to install a downloaded copy of the bookworm¹ version (and so no
> disturbance of the sources.list).
>
>    # ls -l yt-dlp_2023.0*
>    -rw-r--r-- 1 root root 1739188 Jan  6 21:12 yt-dlp_2023.01.06-1_all.deb
>    -rw-r--r-- 1 root root 1777260 Mar 26 03:43 yt-dlp_2023.03.04-1~bpo11+1_all.deb
>    # apt-get install ./yt-dlp_2023.01.06-1_all.deb
>    Reading package lists... Done
>    Building dependency tree... Done
>    Reading state information... Done
>    Note, selecting 'yt-dlp' instead of './yt-dlp_2023.01.06-1_all.deb'
>    Suggested packages:
>      libfribidi-bin | bidiv phantomjs
>    The following NEW packages will be installed:
>      yt-dlp
>    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>    Need to get 0 B/1739 kB of archives.
>    After this operation, 9644 kB of additional disk space will be used.
>    Get:1 /root/yt-dlp_2023.01.06-1_all.deb yt-dlp all 2023.01.06-1 [1739 kB]
>    Retrieving bug reports... Done
>    Parsing Found/Fixed information... Done
>    Selecting previously unselected package yt-dlp.
>    (Reading database ... 357613 files and directories currently installed.)
>    Preparing to unpack .../yt-dlp_2023.01.06-1_all.deb ...
>    Unpacking yt-dlp (2023.01.06-1) ...
>    Setting up yt-dlp (2023.01.06-1) ...
>    Processing triggers for man-db (2.9.4-2) ...
>    Scanning processes...
>    Scanning processor microcode...
>    Scanning linux images...
>    Running kernel seems to be up-to-date.
>    The processor microcode seems to be up-to-date.
>    No services need to be restarted.
>    No containers need to be restarted.
>    No user sessions are running outdated binaries.
>    N: Download is performed unsandboxed as root as file '/root/yt-dlp_2023.01.06-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
>    # ls -l /var/cache/apt/archives/
>    total 4
>    -rw-r----- 1 root root    0 Jan  1  2022 lock
>    drwx------ 2 _apt root 4096 Apr  5 14:09 partial
>    #
>
> There's your warning. Note that the archives/ directory is still
> empty, and also who owns partial/.
>
> Now I'll purge yt-dlp and install it again, but the bullseye-backports
> version this time. For a level playing field, I'll install a downloaded
> copy again. My sources.list does contain backports, but I don't know
> whether that's relevant or not.
>
>    # apt-get purge yt-dlp
>    Reading package lists... Done
>    Building dependency tree... Done
>    Reading state information... Done
>    The following packages were automatically installed and are no longer required:
>      python3-brotli python3-pycryptodome python3-websockets
>    Use 'apt autoremove' to remove them.
>    The following packages will be REMOVED:
>      yt-dlp*
>    0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>    After this operation, 9644 kB disk space will be freed.
>    Do you want to continue? [Y/n]
>    (Reading database ... 358704 files and directories currently installed.)
>    Removing yt-dlp (2023.01.06-1) ...
>    Processing triggers for man-db (2.9.4-2) ...
>    # apt-get install ./yt-dlp_2023.03.04-1~bpo11+1_all.deb
>    Reading package lists... Done
>    Building dependency tree... Done
>    Reading state information... Done
>    Note, selecting 'yt-dlp' instead of './yt-dlp_2023.03.04-1~bpo11+1_all.deb'
>    Suggested packages:
>      libfribidi-bin | bidiv phantomjs
>    The following NEW packages will be installed:
>      yt-dlp
>    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>    Need to get 1777 kB of archives.
>    After this operation, 9864 kB of additional disk space will be used.
>    Get:1http://deb.debian.org/debian  bullseye-backports/main amd64 yt-dlp all 2023.03.04-1~bpo11+1 [1777 kB]
>    Fetched 1777 kB in 1s (3370 kB/s)
>    Retrieving bug reports... Done
>    Parsing Found/Fixed information... Done
>    Selecting previously unselected package yt-dlp.
>    (Reading database ... 357613 files and directories currently installed.)
>    Preparing to unpack .../yt-dlp_2023.03.04-1~bpo11+1_all.deb ...
>    Unpacking yt-dlp (2023.03.04-1~bpo11+1) ...
>    Setting up yt-dlp (2023.03.04-1~bpo11+1) ...
>    Processing triggers for man-db (2.9.4-2) ...
>    Scanning processes...
>    Scanning processor microcode...
>    Scanning linux images...
>    Running kernel seems to be up-to-date.
>    The processor microcode seems to be up-to-date.
>    No services need to be restarted.
>    No containers need to be restarted.
>    No user sessions are running outdated binaries.
>    # ls -l /var/cache/apt/archives/
>    total 1740
>    -rw-r----- 1 root root       0 Jan  1  2022 lock
>    drwx------ 2 _apt root    4096 Apr  5 14:11 partial
>    -rw-r--r-- 1 root root 1777260 Mar 26 03:43 yt-dlp_2023.03.04-1~bpo11+1_all.deb
>    #
>
> This time there's no warning, and the package is cached.
>
> User _apt (UID 100) does not own much:
>
>    # find / -mount -user 100 -printf '%u\t%g\t%p\n'
>    _apt    root    /var/lib/apt/lists/partial
>    _apt    root    /var/lib/apt/lists/auxfiles
>    _apt    root    /var/cache/apt/archives/partial
>    #
>
> AIUI partial/ is designed to avoid ever having partially downloaded
> files kicking around in their parent directory. I don't know any more
> of the details than that.
>
> I guess you have to sort out why a file would be being read from
> /root/.synaptic/tmp//tmp_sh. I know next to nothing about synaptic.
>
> ¹ All the dependencies of yt-dlp are unversioned, so installing
>    a "foreign" version is unlikely to cause trouble.
>
> Cheers,
> David.
>

Strange, the second install, even if providing a local file, is still 
fetching the file from "deb.debian.org".

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

#256825 — Re: How to get rid of the synaptic message (mentioned below) at the end of installing a package?

On Thu 06 Apr 2023 at 15:37:24 (+0200), zithro wrote:
> On 06 Apr 2023 01:30, David Wright wrote:
> > On Sat 01 Apr 2023 at 11:58:49 (+0530), Susmita/Rajib wrote:
> > > My present Debian system installed from "Official Debian GNU/Linux
> > > Live 11.6.0 lxde 2022-12-17T11:46"
> > > 
> > > While installing a package I receive this following message:
> > > 
> > > W: Download is performed unsandboxed as root as file
> > > '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. -
> > > pkgAcquire::Run (13: Permission denied)

> > I guess you have to sort out why a file would be being read from
> > /root/.synaptic/tmp//tmp_sh. I know next to nothing about synaptic.

From the name of the file, tmp_sh, I would hazard a guess that
some process has written a shell script of files to download,
but that script has not been placed in a world-readable location.
User _apt can't read it to perform the sandboxed download, so
user=root has to do it instead.

> Strange, the second install, even if providing a local file, is still
> fetching the file from "deb.debian.org".

So AIUI, the sequence is (user == root):

. read the control file from the /path-to/foo.deb and obtain the
  package name, version and dependencies.

. is that package/version locatable using sources.list?

. if so, _apt downloads from Debian and caches the file as per usual. Install.

. is /path-to/foo.deb world-readable?

. if so, _apt "downloads" from /path-to/foo.deb. Install, no Warn.

. if not, user/root performs an unsandboxed (no _apt involvement)
  "download" from /path-to/foo.deb instead. Install and Warn.

Cheers,
David.

[toc] | [prev] | [standalone]

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

csiph-web