Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Gitsync'd to 2.4 by mistake - going back?

    2.3.1 Snapshots Testing and Feedback - ARCHIVED
    3
    4
    2.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • luckman212L
      luckman212 LAYER 8
      last edited by

      I made a mistake this morning (do not operate firewalls before proper dosage of caffeine!) and issued the following from the dev shell

      playback gitsync master

      when I should have specified RELENG_2_3 as the branch. I wound up with something that said "2.4" on the dashboard which I didn't want. So I logged back in and ran

      playback gitsync RELENG_2_3

      which ran very quickly and didn't seem to change much but lo and behold my dash now says 2.3.1-DEVELOPMENT (amd64) again. Anything to worry about? Do I have a Frankenstein system now and if so is there any proper way to get back or do I need to pave over this? Seems to work ok  :P

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        It's fine at this point to gitsync back to RELENG_2_3.

        1 Reply Last reply Reply Quote 0
        • luckman212L
          luckman212 LAYER 8
          last edited by

          Thanks again - seems to work!

          "pfSense - The Friday the 13th Edition"   :o

          1 Reply Last reply Reply Quote 0
          • PerforadoP
            Perforado Rebel Alliance
            last edited by

            Best one yet. Sadly no hockey mask included  ;D

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.