Documentation bug: Update via Git #11326

New Issue

adam · 2025-12-29T21:43:40+01:00

adam commented

2025-12-29 21:43:40 +01:00

Originally created by @dieck on GitHub (Jun 27, 2025).

Originally assigned to: @dieck on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.10

Steps to Reproduce

As per https://netboxlabs.com/docs/netbox/installation/upgrading/, Option B: Check Out a Git Release:
=> Current version is v4.3.3

Next step:
cd /opt/netbox && sudo git fetch && sudo git checkout v4.3.3
=> error: pathspec 'v4.3.3' did not match any file(s) known to git

(on Ubuntu 22.04LTS, git v2.34.1)

Expected Behavior

Checkout requested version

Observed Behavior

Git raised an error:
error: pathspec 'v4.3.3' did not match any file(s) known to git

Originally created by @dieck on GitHub (Jun 27, 2025). Originally assigned to: @dieck on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.8 ### Python Version 3.10 ### Steps to Reproduce As per https://netboxlabs.com/docs/netbox/installation/upgrading/, Option B: Check Out a Git Release: => Current version is v4.3.3 Next step: cd /opt/netbox && sudo git fetch && sudo git checkout v4.3.3 => error: pathspec 'v4.3.3' did not match any file(s) known to git (on Ubuntu 22.04LTS, git v2.34.1) ### Expected Behavior Checkout requested version ### Observed Behavior Git raised an error: error: pathspec 'v4.3.3' did not match any file(s) known to git

adam added the status: accepted type: documentation complexity: low labels 2025-12-29 21:43:40 +01:00

adam closed this issue

2025-12-29 21:43:41 +01:00

adam commented

2025-12-29 21:43:42 +01:00

@dieck commented on GitHub (Jun 27, 2025):

Solution: git fetch needs --tags

Fix is simple: 5efade4a81
(but policy does not allow me to pull request until this issue is accepted and assigned)

@dieck commented on GitHub (Jun 27, 2025): Solution: git fetch needs --tags Fix is simple: https://github.com/dieck/netbox/commit/5efade4a81bdfad55a7b57732089b52ef751a6b0 (but policy does not allow me to pull request until this issue is accepted and assigned)

adam commented

2025-12-29 21:43:42 +01:00

@Mattz0r commented on GitHub (Jun 27, 2025):

Awesome, this helped me upgrade! Thank you :)

@Mattz0r commented on GitHub (Jun 27, 2025): Awesome, this helped me upgrade! Thank you :)

adam commented

2025-12-29 21:43:42 +01:00

@arthanson commented on GitHub (Jun 30, 2025):

@dieck do you want me to assign to you so you can create a PR for this?

@arthanson commented on GitHub (Jun 30, 2025): @dieck do you want me to assign to you so you can create a PR for this?

adam commented

2025-12-29 21:43:42 +01:00

@jeremystretch commented on GitHub (Jun 30, 2025):

In the future please use the documentation change issue template for such issues.

@jeremystretch commented on GitHub (Jun 30, 2025): In the future please use the [documentation change](https://github.com/netbox-community/netbox/issues/new?template=03-documentation_change.yaml) issue template for such issues.

adam commented

2025-12-29 21:43:43 +01:00

@dieck commented on GitHub (Jun 30, 2025):

@dieck do you want me to assign to you so you can create a PR for this?

Hi!
If you need me to, I can do that.
If you have a simplier way of adding those 7 chars (including space ;)), feel free to do so :)

In the future please use the documentation change issue template for such issues.

Sorry, must have missed this, if I come upon something else, I will try to remember!

@dieck commented on GitHub (Jun 30, 2025): > [@dieck](https://github.com/dieck) do you want me to assign to you so you can create a PR for this? Hi! If you need me to, I can do that. If you have a simplier way of adding those 7 chars (including space ;)), feel free to do so :) > In the future please use the [documentation change](https://github.com/netbox-community/netbox/issues/new?template=03-documentation_change.yaml) issue template for such issues. Sorry, must have missed this, if I come upon something else, I will try to remember!

adam commented

2025-12-29 21:43:43 +01:00

@jnovinger commented on GitHub (Jul 2, 2025):

@dieck do you want me to assign to you so you can create a PR for this?

Hi! If you need me to, I can do that. If you have a simplier way of adding those 7 chars (including space ;)), feel free to do so :)

@dieck , I went ahead and created a PR from the branch/change you linked. Thanks!

@jnovinger commented on GitHub (Jul 2, 2025): > > [@dieck](https://github.com/dieck) do you want me to assign to you so you can create a PR for this? > > Hi! If you need me to, I can do that. If you have a simplier way of adding those 7 chars (including space ;)), feel free to do so :) @dieck , I went ahead and created a PR from the branch/change you linked. Thanks!

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#11326