Bug#862866: upgrade-reports: Error message after installation/Upgrade (Synaptic)
On 5/17/17, Bill Allombert <ballombe@debian.org> wrote:
> On Wed, May 17, 2017 at 11:36:50PM +0300, Geo Pe wrote:
>> Package: upgrade-reports
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate
>> ***
>>
>> * What led up to the situation?
>> I upgraded from stable to testing. Try to install/upgrade various
>> packages
>>
>> * What exactly did you do (or not do) that was effective (or
>> ineffective)?
>> Tried to install netbeans. The problem is repeaded with other packages.
>> * What was the outcome of this action?
>> Netbeans was installed but i got the following message after
>> installation:
>>
>> "W: Download is performed unsandboxed as root as file
>> '/var/cache/apt/archives/partial/libminizip1_1.1-8+b1_amd64.deb' couldn't
>> be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"
>>
>> * What outcome did you expect instead?
>> Message for successfull installation.
>
> Hello Geo Pe,
> This is not an error but a warning (W: mean warning).
> You should check the permission of
> /var/cache/apt/archives/partial/
>
> Cheers,
> --
> Bill. <ballombe@debian.org>
>
> Imagine a large red swirl here.
I've received that warning in the past. There obviously could be
multiple causes for seeing it. In my case and purely discovered by
accident, the warning occurred because I had symlinked to
'/var/cache/apt/archives which was on an external hard drive.
No matter where the target '/var/cache/apt/archives/ was placed in a
data'esque hierarchy on that external hard drive, I still received
that error. Permissions *appeared* to be correct, but that also didn't
seem to make a difference.
As a matter of record as long as the topic is here, that symlinking
also caused my debootstrap chroot user "root" to have an identity
crisis where it kept yelling, "I Have No Name!"
As soon as I removed the symlink to '/var/cache/apt/archives/ and
moved files back in the primary hierarchy, debootstrap's chroot user
root found itself again as "root". If I'm remembering correctly, that
instance was ultimately traced back to my missing a similar
permissions denied warning early on in debootstrap. That warning
disappeared immediately upon removal of the package archives directly
symlink.
Hope this some day helps somehow..
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *
Reply to: