Unable to update repository FreeBSD

hruodr said:
The whole afternoon until the night upgrading to 13,
I ended with broken X11, a lot of time wasted with X11,
then tryied to upgrade to 14, I went at 3 am to bed and left upgrade,
now upgrading packages, who knows if I will have X11 running ...

Do you see that I have a reason not to upgrade a working system?
Click to expand...

Most X11 servers will be broken when the machine is in a state of updated base and un-updated packages.

This freebsd-upgrade is unusable.
Click to expand...

Seems to work for a lot of people, including me.

If you want help you need to get better at copy'n'pasting the actual things you do and what happens as a result.
 
cracauer@ said:
in a state of updated base and un-updated packages.
Click to expand...

No, system was upgraded and packages updated, but X11 broken. I have this experience almost after every upgrade,
but with FreeBSD 11 was worse.

cracauer@ said:
you need to get better at copy'n'pasting the actual things you do
Click to expand...
With broken X11?!

I think, no help will made it faster, only a supercomputer on a very fast internet node.

And no help is needed to edit master.password and sendmail.mc, but I do not
want to do it when I in middle of the upgrade process, but with the necessary care these delicate files
demand.
 
Each upgrade brings its batch of broken things. And to be honest, from my point of view, it became worse with time. This not only concerns the base but also and mainly each package upgrade.

I think this is because most of the packages are written for Linux (especially the ones related to Xorg and wayland). And here, maintainers just try to adapt that ecosystem to FreeBSD. They are few and lack of them is one of the problems.

FreeBSD is like an island on the sea of Linux distributions. There is nothing to do against that except make FreeBSD more popular (in order to get more ressources). But, this implies to follow the Linux move in some ways. And no one, or few, want that for our preferred OS.

So, yes I don't like to edit config files during upgrade. I don't like to repair things after almost each upgrade. I hate to fail when accomplishing this.

But I can use Linux or Windows if I want something different.

My point is there is no use to complain about the very roots of FreeBSD.
 
I too have been having problems with pkg. New installs of 14.0, 14.1, 14.2 all give the same error messages as the opening post. Tried 13.5 today and pkg does not exist in repos according to the new fresh install. Tried to build from ports & got the make deinstall & make reinstall routine and still pkg update -f errors out with no repositories available. What gives? Has the FreeBSD servers been hacked and taken offline? I've been pounding my head on this for 2 days now. Thankfully I have 2 backup drives with 12.2, 12.3 & 13.4 functioning flawlessly. Scared to attempt to update anything as that is what broke a 14.2 disk that started this whole fiasco.
 
SirDice said:
What does pkg -vv | grep -A10 Repositories show?
Click to expand...
Today I attempted to replicate the pkg issue. Downloaded & installed 14.2. So far it installed flawlessly to an XFCE desktop with Nvidia driver & everything updated to latest without complaints. Curious & strange for 2 days giving hair-pulling-out issues & today all is hunky dory. Leaves me wondering if DDOS attacks my ISP has been having the past few months had anything to do with those issues, except all other internet access seemed unaffected at the time. Different day, different results. I'll try a clean install of 13.5 next just to see if the pkg problem is still present there. Thanks for the reply & assistance.
I'll use that command handy if I still see any related problems.
 
You must log in or register to reply here.
Back
Top