![]() $ cd temp1 sudo apt-get source gnupg2 # gives warning message: Of course, you'll then have to put a more reasonable ownership on this base folder once you're done, because it is strange to be owned by _apt:root.Īre the results the same with or without the warning message? # - TEST 1: get source into folder owned by user. So if you $ mkdir temp sudo chown _apt:root temp sudo -s and # cd temp apt-get source. ![]() where the source will get put) is owned by _apt:root. You have to make sure the folder your sitting in (i.e. ![]() It seems this is a case where the user named root simply can't do what the user named _apt can do.Ī partial solution, (one you really don't want to use): ( ref: Kusalananda)Īs Florian pointed out, "apt uses the user _apt to download packages". A warning being something that is abnormal, but that doesn't stop the program from continuing to operate. It seems like after this _apt change was made, a whole bunch of things broke that haven't yet been fully fixed.įirst, apt result lines with a W: prefix are only warnings. Clearly huge numbers of people have been having trouble with the apt tools ever since it was changed to use _apt for it's sand-boxed, secure operations. ![]() ![]() The web is thick with questions about this warning message, with many different suggested solutions. , even if I try and download as root, like with sudo or su, (Debian 10.4 and apt 1.8.2.1). I get it when I try and download source, with apt-get source. They're non-fatal, and for the most part you can't fix this, and you'll get the same results with or without the warning.Įven when Florian Diesch's fine answer here is implemented, I'm still getting this warning. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |