DragonFly 6.2 released
Justin Sherrill
justin at shiningsilence.com
Mon Jan 10 16:52:58 PST 2022
What Dan said is correct, but here's some detail: You fetch the repository
files - the "origin". You then create a local branch for 6.2, and connect
it to the remote version (the "origin") with the same name. You then
checkout the branch files. At this point, the 6.2 source files are on
disk. You could probably get away without the git pull command but it
doesn't hurt.
On Mon, Jan 10, 2022 at 5:56 PM Mario Marietto <marietto2008 at gmail.com>
wrote:
> I am not very experienced. So,which commands should I issue ?
>
> Il giorno lun 10 gen 2022 alle ore 23:54 Dan Cross <crossd at gmail.com> ha
> scritto:
>
>> On Mon, Jan 10, 2022 at 5:47 PM Mario Marietto <marietto2008 at gmail.com>
>> wrote:
>>
>>> Something is not went well here I think :
>>>
>>> I'm using this version before the upgrade :
>>>
>>> root at marietto:/usr/src # uname -a
>>>
>>> DragonFly marietto 6.1-DEVELOPMENT DragonFly
>>> v6.1.0.589.gd52e31-DEVELOPMENT #1: Sat Jan 1 17:38:32 CET 2022
>>> marietto at marietto:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64
>>>
>>> So,I want to upgrade it to 6,2 and I do :
>>>
>>> root at marietto:/home/marietto # cd /usr/src
>>>
>>> root at marietto:/usr/src # git fetch origin
>>> remote: Enumerating objects: 96, done.
>>> remote: Counting objects: 100% (96/96), done.
>>> remote: Compressing objects: 100% (68/68), done.
>>> remote: Total 68 (delta 56), reused 0 (delta 0), pack-reused 0
>>> Unpacking objects: 100% (68/68), 9.08 KiB | 31.00 KiB/s, done.
>>> From git://git.dragonflybsd.org/dragonfly
>>> d52e317013..1dddac0a52 master -> origin/master
>>> * [new branch] DragonFly_RELEASE_6_2 ->
>>> origin/DragonFly_RELEASE_6_2
>>> * [new tag] v6.2.1 -> v6.2.1
>>> * [new tag] v6.3.0 -> v6.3.0
>>>
>>> root at marietto:/usr/src # git branch DragonFly_RELEASE_6_2
>>> origin/DragonFly_RELEASE_6_2
>>> Branch 'DragonFly_RELEASE_6_2' set up to track remote branch
>>> 'DragonFly_RELEASE_6_2' from 'origin'.
>>>
>>> root at marietto:/usr/src # git checkout DragonFly_RELEASE_6_2
>>> Switched to branch 'DragonFly_RELEASE_6_2'
>>> Your branch is up to date with 'origin/DragonFly_RELEASE_6_2'.
>>>
>>> root at marietto:/usr/src # git pull
>>> Already up to date. ---> already up to date ? it's not true,since I'm
>>> using 6.1....shouldn't it get the new source code here ?
>>>
>>
>> You did when you checked out the branch. I believe the `git pull` is in
>> these instructions in the off-chance that somethings is backported to the
>> DragonFly_RELEASE_6_2 branch after this is written but before someone
>> upgrades.
>>
>> - Dan C.
>>
>> Il giorno lun 10 gen 2022 alle ore 21:12 Justin Sherrill <
>>> justin at shiningsilence.com> ha scritto:
>>>
>>>> DragonFly 6.2.1 is released - here's the release page:
>>>>
>>>> https://www.dragonflybsd.org/release62/
>>>>
>>>> 6.2.0 was never released cause I screwed up tagging, so you can go
>>>> right from 6.0 to 6.2.1. Here's the 6.2.1 tag with a list of the commits
>>>> since 5.8:
>>>>
>>>>
>>>> https://lists.dragonflybsd.org/pipermail/commits/2022-January/820802.html
>>>>
>>>> The normal ISO and IMG files are available for download and install,
>>>> plus an uncompressed ISO image for those installing remotely.
>>>>
>>>> If updating from an older version of DragonFly, bring in the 6.2 source:
>>>>
>>>> > cd /usr/src
>>>> > git fetch origin
>>>> > git branch DragonFly_RELEASE_6_2 origin/DragonFly_RELEASE_6_2
>>>> > git checkout DragonFly_RELEASE_6_2
>>>> > git pull
>>>>
>>>> And then rebuild: (still in /usr/src)
>>>> > make build-all
>>>> > make install-all
>>>> > make upgrade
>>>>
>>>> After your next reboot, you can optionally update your rescue system:
>>>>
>>>> (reboot)
>>>> > cd /usr/src
>>>> > make initrd
>>>>
>>>> Don't forget to upgrade your existing packages if you haven't recently:
>>>>
>>>> > pkg update
>>>> > pkg upgrade
>>>>
>>>>
>>>
>>> --
>>> Mario.
>>>
>>
>
> --
> Mario.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20220110/48699ade/attachment-0002.htm>
More information about the Users
mailing list