Deb wrote: > I ran cruft through sudo in my three-day-old Jessie amd64 install on my > personal home tower, and redirected output to a text file. This error > message displayed on standard console output and was absent from the file: > > > find: `/run/user/1000/gvfs': Permission denied I don't think cruft should be searching down the /run tmpfs filesystem. I suggest filing a bug against it. I don't see one for that problem. > Tne application did output successfully and I got a 1,219-line file with > only one missing DPKG: > > > /usr/lib/libept.so.1.0.5.4.12 $ dpkg -L libept1.4.12 | grep libept.so.1.0.5.4.12 /usr/lib/libept.so.1.0.5.4.12 Why is that reported as being missing? Perhaps you should reinstall that package?? # apt-get install --reinstall libept1.4.12 > and I got the following broken symlinks: > > > /usr/share/man/man3/cerfcl.3.gz > > /usr/share/man/man3/cerfcf.3.gz > > /usr/share/man/man3/cerff.3.gz > > /usr/share/man/man3/cerfl.3.gz > > /usr/lib/python2.6/dist-packages/python-support.pth See Bug#765592 which is as yet not fixed. http://bugs.debian.org/765592 > Could someone explain the standard console output to me and tell me whether > the dpkg and symlink outputs are anything to worry about? Bugs. I think they are simply bugs. But it is possible that it detected an installation problem with libept1.4.12 on your system. Bob
Attachment:
signature.asc
Description: Digital signature