-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netbox: 3.7.8 -> 4.1.3 #331750
netbox: 3.7.8 -> 4.1.3 #331750
Conversation
Result of 1 package blacklisted:
5 packages failed to build:
16 packages built:
|
@xanderio your nixpkgs-review might have failed because this PR depends on the djangorestframework PR. While testing my changes, I had those djangorestframework changes in my local tree. |
That explains it |
41d5642
to
eab9adc
Compare
Dependent PR was merged, so this is now ready for review! Both the Result of 1 package blacklisted:
22 packages built:
|
Happy to report the nixpkgs-review is happy again :D Result of 1 package blacklisted:
22 packages built:
|
pkgs/development/python-modules/django-choices-field/default.nix
Outdated
Show resolved
Hide resolved
This fixes an issue with Django 5 pytest checks were removed due to a dependency on model_mommy, which is deprecated.
Migrate to pkgs/by-name, and update the test so that it passes for all versions This version is added as EOL, since NetBox 4.1 is out, but it might be still useful in case of an upgrade issue.
also switch the netbox-upgrade test to check upgrade from 3.7 -> 4.1
since the script does database migrations and index, it could timeout on slower system with a big enough database
needed by the NetBox 4.0+ upgrade
Merging, as this is the last day breaking changes are allowed. If this causes issues (hopefully not), I'll open follow-up PRs. |
@minijackson My netbox instance is partly broken now ;( It might be related to something in my setup... |
@felbinger I can reproduce the issue on an instance upgraded from 3.7, but not on a fresh 4.1 instance. Not sure where this comes from yet. I think the demo instance is recreated from scratch on each upgrade, so this doesn't tell us if the issue is from the packaging or on the NetBox side, unfortunately. |
@felbinger Okay, I think I found the issue, and I'll open a fix tomorrow. In the meantime you can run: rm -rf /var/lib/netbox/static
netbox-manage collectstatic and hard refresh / clear the cache of the page in your browser. |
We probably want to save the version of netbox somewhere in /var/lib/netbox a d when that changes invalidate the static cache. Or can we use a cheap symlink? |
thanks a lot, it's working! |
or maybe we can build it at runtime like paperless-ngx does
|
We're actually already doing that here: nixpkgs/nixos/modules/services/web-apps/netbox.nix Lines 301 to 303 in 71408df
The issue was that old files were not cleared, and it seems upstream's
That's a great suggestion, I was thinking of putting the hash in order for the upgrade script to be run when plugins are added, but the symlink is probably even simpler. Thanks!
I'm not completely sure of the advantages / drawbacks of doing that, but I actually didn't know of the |
Description of changes
Finally!
Some upgrades and new Python packages were needed by the NetBox upgrade.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
netbox
andnetbox-upgrade
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)cc NetBox maintainers: @RaitoBezarius & @n0emis
django-mptt maintainer: @mweinelt
and people interested in the upgrade: @KiruyaMomochi & @xanderio & @Xyz00777
Add a 👍 reaction to pull requests you find important.