No, everything is one one partition in my case—this Debian system just has a “/” partition, and a swap partition.gurfle wrote:For example, did you use a mount point on a different partition also? If not, then that is not the critical factor, but then can you post some more information on just what you did to get it to fail?
That’s my line of thinking, too. I cannot find much information about this “_apt” user, though, except that it was introduced for tightened security: it allows APT to drop its “root” privileges while downloading from the repositories. I’m puzzled, however, about which authorisations the user does or does not have, and where it gets them from.From the error messages, it looks nonetheless like some kind of permission issue, involving the "_apt" user, may be at the core of the problem. This is a feature not present in the version of apt that works for me in jessie, so perhaps something about the new "_apt" user needs to be tweaked?
Code: Select all
Err:4 file:/media/nick/DebianRepositori/debian-9.0.0-amd64-DVD-1 stretch/main amd64 Packages File not found - /media/nick/DebianRepositori/debian-9.0.0-amd64-DVD-1/dists/stretch/main/binary-amd64/Packages (2: No such file or directory) Reading package lists... Done N: Download is performed unsandboxed as root as file '/media/nick/DebianRepositori/debian-9.0.0-amd64-DVD-1/dists/stretch/InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Failed to fetch file:/media/nick/DebianRepositori/debian-9.0.0-amd64-DVD-1/dists/stretch/main/binary-amd64/Packages File not found - /media/nick/DebianRepositori/debian-9.0.0-amd64-DVD-1/dists/stretch/main/binary-amd64/Packages (2: No such file or directory)
I’m thinking of two further tests that could tell us which authorisation the “_apt” user is actually missing. Starting from the working configuration, we could:
- Move the mountpoint to the location that it has in the failing configuration, leaving the image file at its working location. My gut feeling tells me that this should work. If I’m right, then the mountpoint is not the problem, but the location of the image file probably is.
- Leave the mountpoint at its working location, moving the image file to its location in the failing configuration. This is, according to my gut feeling, more likely to fail.
Of course, just knowing which authorisation is missing, doesn’t explain why this happens, but at least it will narrow down the search field.
I’m afraid I will have to leave it at that for now. I probably won’t have the opportunity to pick it up again until the weekend.