On Tue, Jul 19, 2016 at 04:36:57PM +0200, Vincent Lefevre wrote: > while I have: > > Package: libutf8proc1 > Architecture: amd64 > Auto-Installed: 0 > > However, this package was installed automatically. From the apt > history: > > Start-Date: 2016-07-13 21:37:27 > Commandline: apt install julia julia-doc > Install: julia:amd64 (0.4.6-1), libopenlibm2:amd64 (0.5.1+dfsg-1, automatic), libutf8proc1:amd64 (1.3.1-2, automatic), libjs-mathjax:amd64 (2.6.1-1, automatic), julia-doc:amd64 (0.4.6-1), libspqr2:amd64 (1:4.5.3-1, automatic), libdsfmt-19937-1:amd64 (2.2.3+dfsg-2, automatic), fonts-mathjax:amd64 (2.6.1-1, automatic), libjs-underscore:amd64 (1.7.0~dfsg-1, automatic), sphinx-rtd-theme-common:amd64 (0.1.9-1, automatic), libpcre2-8-0:amd64 (10.21-1, automatic), libopenblas-base:amd64 (0.2.18-1, automatic), libunwind8:amd64 (1.1-4.1, automatic), julia-common:amd64 (0.4.6-1, automatic), libarpack2:amd64 (3.4.0-1, automatic), libopenspecfun1:amd64 (0.5.2-1, automatic), libjs-modernizr:amd64 (2.6.2+ds1-1, automatic), libjs-sphinxdoc:amd64 (1.4.4-3, automatic) > End-Date: 2016-07-13 21:37:40 > > So, the bug is still there in apt 1.3~pre2 (I had upgraded to this > version a few days before). $ ssh barriere.debian.org # debian amd64 porterbox (porter)$ mysid=sid$RANDOM (porter)$ schroot -b -c stretch -n $mysid # 'apt' isn't allowed ATM in porterboxes, but it makes no difference here anyhow (porter)$ dd-schroot-cmd -c $mysid apt-get update (porter)$ dd-schroot-cmd -c $mysid apt-get upgrade (porter)$ dd-schroot-cmd -c $mysid apt-get install julia julia-doc (porter)$ schroot -r -c $mysid (chroot)$ grep -o 'libutf8[^ ]* ([^)]*)' /var/log/apt/history.log libutf8proc1:amd64 (1.3.1-2, automatic) (chroot)$ apt-mark showmanual libutf8proc1:amd64 (chroot)$ apt-mark showauto libutf8proc1:amd64 libutf8proc1 So, in the six days since you installed libutf8proc1 something happened which marked it as manually installed, which usually is the case if you (or something else on your "behalf" even without your explicit knowledge) runs 'apt install libutf8proc1' – even if that ends up doing "nothing". Either way, without you telling us what "you" did this remains as unactionable as before. Best regards David Kalnischkies P.S.: In the meantime the explaination involving 'gnome-core' (aka metapackages) above is outdated as the handling doesn't kick in on install anymore, but on remove – see git commit 7c2cc4a7 for details (5f4495e3 has also relations to this general topic).
Attachment:
signature.asc
Description: PGP signature