Date: Sat, 05 Mar 2022 05:53:04 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262348 --- Comment #2 from Hubert Tournier <firstname.lastname@example.org> --- Yes, I'm sure that I already had all the distfiles downloaded (including the 3.4 GB texlive-20210325-texmf.tar.xz in /usr/ports/distfiles/TeX) and the first time I did the upgrade it got stuck for 2 days on a big server before I interrupted the upgrade (after compiling successfully texlive-texmf and attempting to install it). I made several tries after that, each time getting to this strange side effect, including tries where I previously wiped every trace of protobuf-c, doxygen and TeX on my system before restarting. This may be disk related, as I see that all the stuck processes are in D state, which "Marks a process in disk (or other short term, uninterruptible) wait" but there are no interesting messages in /var/log/messages. Only meaningful traces in /var/log/messages are: Mar 4 22:38:56 arche7 pkg-static: tex-kpathsea-6.3.3 installed Mar 4 22:39:03 arche7 pkg-static: tex-ptexenc-1.3.9 installed Mar 4 22:39:38 arche7 pkg-static: tex-web2c-20210325 installed Mar 4 22:40:14 arche7 pkg-static: tex-basic-engines-20210325 installed Mar 4 22:41:07 arche7 pkg-static: texlive-tlmgr-20210325_1 installed Mar 4 22:44:41 arche7 pkg-static: texlive-base-20210325 installed I worked around the issue by cutting the "LaTeX support" in doxygen or the "Build documentation with Doxygen" in protobuf-c, and then So one of: # cd /usr/ports/devel/doxygen ; make config # cd /usr/ports/devel/protobuf-c ; make config But I see this more as a worrying system side effect, than as an issue with a port upgrade that I don't really need. -- You are receiving this mail because: You are the assignee for the bug.