Solved FreeBSD 14 is ready?

While upgrading to 14.0-RELEASE, I am running to this issue and I don't know my options. I rather not do anything but I don't seem to have that possibility. Any workaround? Thank you.
Code: 
s Enter to edit this file in vi and resolve the conflicts
manually...
<<<<<< current version
# $FreeBSD$
#
wheel:*:0:root,job
=======
wheel:*:0:root
>>>>>>> 14.0-RELEASE
daemon:*:1:
kmem:*:2:
sys:*:3:
tty:*:4:
operator:*:5:root
mail:*:6:
bin:*:7:
news:*:8:
man:*:9:
games:*:13:
ftp:*:14:
staff:*:20:
sshd:*:22:
smmsp:*:25:
mailnull:*:26:
guest:*:31:
video:*:44:
realtime:*:47:
idletime:*:48:
bind:*:53:
unbound:*:59:
proxy:*:62:
authpf:*:63:
_pflogd:*:64:
_dhcp:*:65:
uucp:*:66:
dialer:*:68:
network:*:69:
audit:*:77:
www:*:80:
u2f:*:116:
ntpd:*:123:
_ypldap:*:160:
hast:*:845:
tests:*:977:
nogroup:*:65533:
nobody:*:65534:
job:*:1001:
messagebus:*:556:
polkitd:*:565:
avahi:*:558:
cups:*:193:
colord:*:970:
pulse:*:563:
pulse-access:*:564:
pulse-rt:*:557:
cyrus:*:60:
gdm:*:92:
_sndio:*:702:
mpd:*:137:
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
:q!

Merge conflict markers remain in: /etc/group
These must be resolved for the system to be functional.

Press Enter to return to editing this file.
 
I edited the file
Code: 
# $FreeBSD$
#
wheel:*:0:root,job
=======
wheel:*:0:root,job
>>>>>>> 14.0-RELEASE

exited vi with ":wq" but then I still get this

Code: 
/var/db/freebsd-update/merge/new//etc/group: 57 lines, 739 characters.

Merge conflict markers remain in: /etc/group
These must be resolved for the system to be functional.

Press Enter to return to editing this file.
 
Makes me think that the first line in that merge file was the culprit:
joplass said:
Code: 
# $FreeBSD$
#
[COLOR=rgb(226, 80, 65)]wheel:*:0:root,job[/COLOR]
=======
wheel:*:0:root,job
>>>>>>> 14.0-RELEASE
Click to expand...
As in the first line that says, wheel:*:0:root,job... I'd remove that. I frankly only once did freebsd-update upgrade - from 13.0-RELEASE to 13.1-RELEASE, back then.
 
Let's try an annotated example:
Code: 
<<<<<< current version                                  <---- remove this line
# $FreeBSD$                                             <---- remove this line
#                                                       <---- remove this line
wheel:*:0:root,job                                      <---- LEAVE this line IN. It is your current configured wheel group
=======                                                 <---- remove this line
wheel:*:0:root                                          <---- remove this line
>>>>>>> 14.0-RELEASE                                    <---- remove this line
daemon:*:1:
Now save and quit.
 
rmomota said:
Lost some software:
firefox was gone after restart
sudo was gone also... why?!?!
Click to expand...

for me firefox, chromium, node and postgresql were gone.

So, dump your databases before upgrading FreeBSD.

Code: 
pg_dumpall -v > db12.out

But, nothing that cannot be repaired with pkg install.

And somehow terminal access feels way faster.
 

Generally (not specific 14.0)​

There should be greater awareness of this UPDATING page:

github.com

freebsd-ports/UPDATING at main · freebsd/freebsd-ports

FreeBSD ports tree (read-only mirror). Contribute to freebsd/freebsd-ports development by creating an account on GitHub.
github.com github.com
  • to be read, or reviewed, before any pkg or port upgrade routine.
sremick said:
torrents
Click to expand...

I forgot this topic, which now includes a link to your bug report (thanks):

forums.freebsd.org

FreeBSD RELEASE torrents, including magnet URLs

https://fosstorrents.com/distributions/freebsd/ https://wiki.freebsd.org/Torrents Any other sites? Related FreeBSD 13.1 Release Information | The FreeBSD Project includes FreeBSD 13.1 Release Checksum Signatures Cross-reference: FreeBSD: torrents, magnet URLs etc.
forums.freebsd.org forums.freebsd.org

weberjn said:
firefox, chromium, node and postgresql were gone.
Click to expand...

If the fallout page for a port (via FreshPorts) does not explain its absence, then – in nearly all cases – an explanation will be found in build records.

forums.freebsd.org

Using package build records at pkg-status.freebsd.org

https://people.freebsd.org/~grahamperrin/pkg-status/ This brief guide includes: screenshots an explanation of why the latest option – not to be confused with packages from the main branch of the ports tree (familiarly known as latest) – is not reliable a hint about the current requirement to...
forums.freebsd.org forums.freebsd.org

(Quite complicated, sorry.)
 
  • Thanks
Reactions: sko
Okay, final 14.0 is out but as I am reading there are problems with upgrade. I am thinking to upgrade my 13.2 - RELEASE p5 this weekend because I have time but is is still scary a little because there are many complains. I am running FreeBSD on laptop and everything good. Is is desktop laptop with UFS system.
I did run freebsd-update fetch but there are anything to update. I will use as usual freebsd-update.
Should I expect some bigger problems, please?
Thank you.
 
fernandel said:
I did run freebsd-update fetch but there are anything to update
Click to expand...
That won't work for a major release update. See https://docs.freebsd.org/en/books/handbook/cutting-edge/ -- in particular section 26.2.3. I think there is a reddit page which lists last minute issues but I don't have its URL.

I have had no issues with 14.0 release on amd64 and pi4 (but I don't use freebsd-update).

*Generally* major-release.0 is always less polished than major-release.1 or later so if you don't have a strong need to update, you can wait. But if you have a strong *desire* to update, you must be brave :)
 
fernandel it's a good idea to learn how to update the boot loader, even if you don't need the knowledge at this time.

Fairly comprehensive, at a glance:

forums.freebsd.org

Update of the bootcodes for a GPT scheme (x64 architecture)

This how-to is about the update of the bootcodes on FreeBSD as it's little to no documented. It only covers the GPT scheme and is intended for people with little knowledge of FreeBSD. When to update? At each upgrade of the system whenever it's a minor or a major one. In general, the system is...
forums.freebsd.org forums.freebsd.org
 
bakul said:
That won't work for a major release update. See https://docs.freebsd.org/en/books/handbook/cutting-edge/ -- in particular section 26.2.3. I think there is a reddit page which lists last minute issues but I don't have its URL.

I have had no issues with 14.0 release on amd64 and pi4 (but I don't use freebsd-update).

*Generally* major-release.0 is always less polished than major-release.1 or later so if you don't have a strong need to update, you can wait. But if you have a strong *desire* to update, you must be brave :)
Click to expand...
Thank you very much. It is not about to be brave, I do not have needs to spend day to fix a problem if my system works. This time I will wait to 14.1 :).
 
You must log in or register to reply here.
Back
Top