Thanks for the reply and a good hot summer sat/sun to evryone..
I have solved, and I don't really know if everyone already spotted these details before. However, I was with my 11years old station doing the usual pkg_add -u to complete my upgrade and I have been stack on this output message for a *couple* of times. The prb was not only to grasp what was going on but I would underline the computation speed of the 7.7 upgrade on my old hardware, expecially going to aggregate dependencied of python package (I believe). My old hardware was really slow to exit from the *stalling situation*, and it has been my first time in a decade. I solved deciding to dedicate myself upgrading pkg_add -u libnotify-0.8.3: the computation speed in the stalling moments was slighting better .. althought I have slept a while while stack with my angry mind. Finished this upgrade I proceeded with a classic pkg_add -u and all the *aggregation moments* went mostly circunvented and I was able to finish my job. The matter was caused stack on these esclamation points and due to the stall I was not able to grasp (without a proper indication too) about it so that I continued to abandon the pkg upgrade. Hope this can eventually help someone. Jul 5, 2025 22:17:54 Nick Holland <n...@holland-consulting.net>: > On 7/5/25 11:38 AM, dan wrote: >> Hello, >> Updating stable to 7.7 I continue to get this: >> https://gaox.io/l/77upd1 >> Any suggestion before to start from a fresh copy? > > ok, so your subject line is incorrect -- you upgraded to 7.7 (maybe) > from something, on some platform on some hardware. > But your actual problem comes when trying to update packages, not the > system. > > So...what did you start from? What did you actually end up at? What > did you do to break the packaging system? Rather than taking pictures > of PART of the output, redirect output and error to a file and put > that in the body of the message. > > Make sure you are pulling packages from the 7.7 or 7.7-stable package > directory, not a previous release or snapshots. > > You really don't need to start from fresh. WORST case, I think you > can uninstall all your current packages, and reinstall the ones you > need. Along the way, you might actually find the problem. > > Nick.
