It would be upgraded to 580.95.05 on next pkg builds.
I refer back to one of my previous posts- there are heuristics to avoid publishing a set that is far too broken, but obviously you'll win some and lose some. That's the nature of software- pkg or poudriere could probably handle something better here, but I don't think I've really seen any workable proposals (and certainly nobody willing to help out with It).
Well, rank-and-file users are seeing an awful lot of failures lately, and are getting disillusioned with those heuristics because of those failures. Not directly, but I was hoping that the packagers see that connection, and maybe try do something...
That a relatively small amount of packages that you have, My conclusion is more and more based on experiences that PKG utilitiy is not good at managing a big amount of packages and dependencies.Just did pkg update / pkg upgrade -- and it worked flawlessly !
I picked up around ~471 packages and made ~880 changes. And I (did not) have to manually recompile drm-61-kmod this time! Fantastic ! NVidia upgraded to 580.82.
Awesome job FreeBSD package maintainers !
I'll be sure to laugh at you when you'll be the one facing issues.
Just from one of the secondary installs (not even my main desktop which has way more pkgs, but I'm booted in Alt Linux ATM building 16.6.7 kernel for QEMU aarch64 Gentoo – it will take some time)
pkg info | wc -l
1768Yeah, that's a proper spirit of OSS collaboration and helping fellow users /s
I don't care whom you are or pretend to be. I surely didn't learn anything from his last comment here. Yeah, plenty to learn for sure. But is sound like if you want to do me a moral course here. Is it supposed to be my fault if PKG did that? Is PKG supposed to do that? Is it is intended behaviour to fuck up the installation? To say to the user, I'll do it and instead do something else ??? Sure I'm a just a newbie, a bad admin and I deserve to be laughed at plus having to be taught a lesson, that's the spirit of OSS, thanks. Good for you if you know a thing or two, I should know like you do, isnt it?
Who or Whom?
That's sad
Personally, I don't give 2 eFs about morals, only thing that I do care about is ethics.
Looks like it.
No and no.
IDK from where (that was discussed here) you draw up premises to come up with those conclusions, but I'm certainly not qualified to help you with any of that. I'm just a regular FreeBSD user and self-proclaimed OS tinkerer, so if you need help with your install, I'll be glad to help to the best of my ability.
LOL surely you are reference ! My ass too is prestigious. Am I the one going to troll on other's thread? if you do troll on my thread be warned you ll get what you deserve. I dont care. dont fuck with me.
Your added value on this thread = none. bye bye troll.
I used FreeBSD since 14.1 and afaik always used pkg. I have enough experience Win98/XP days to know any major OS upgrades will likely result in more troubleshooting than a clean-install to the updated version is worth
I think when it comes to PKG update and upgrade, which are two common basic administration command, no thinking of this kind should be necessary, unless PKG is to be classified as an unstable tool for managing packages. If not, then it's nothing else but confusing.
pkg(8) works just fine – TBH most of the time. For the very rare cases when it's not, there are numerus prevention and mitigation strategies already discussed here ad nauseam (and in the various other sites & docs)
RTFM and listen to the more experienced users to get some clarity on the matter.
If you insist on using such approach to people and on offending them, you can – but don't expect any help down the road you are on, at least not from me.
Yes it have never failed either. There must be some warning after simulation regarding what will hapen and wait for confirmation before doing/installing anything. You could have avoid the mess. It may happen if some packge/s were deleted earlier and then failed to run
pkg autoremove. You would have see the same warning.