Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unknown error executing apt-key #1500

Closed
EdNett opened this issue Jun 11, 2020 · 2 comments
Closed

unknown error executing apt-key #1500

EdNett opened this issue Jun 11, 2020 · 2 comments

Comments

@EdNett
Copy link

EdNett commented Jun 11, 2020

Hello, I found the following error - I wonder if it is important and needs to be resolved or does it refer to deprecated packages? (after update to latest head sith mariadb 10.3 and php 7.3):

gist:
https://gist.github.com/EdNett/d8e86d02dc1415ccb66eab00bc9cb758

boa info more:
https://gist.github.com/EdNett/23d459b34e826cc27d0c47e1d2487c83

Best

Ed

@ar-jan
Copy link
Contributor

ar-jan commented Jun 27, 2020

I just got this after upgrading from Jessie to Stretch. There's already an issue, and this proposal solved it for me.

@omega8cc
Copy link
Owner

This is normal on Stretch, if you try to run apt-get or aptitude manually, outside of running it via barracuda script.

BOA automatically creates /etc/apt/apt.conf.d/00sandboxtmp file with line disabling sandboxing temporarily during the upgrade:

echo "APT::Sandbox::User \"root\";" > /etc/apt/apt.conf.d/00sandboxtmp

Allegedly it's not recommenced to keep this file always present, so barracuda deletes it at final cleanup.

Perhaps we should make it permanent just to stop the confusion and breaking apticron.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants