After install · SnipeOS 13D

Update SnipeOS 13D

One terminal command refreshes your sources, packages, SnipeOS patches, and branding layers. Prefer watching? See the update video.

Warning: These scripts are for SnipeOS 13D. If you are using SnipeOS 26, please click here.

Video walkthrough

Footage is from classic SnipeOS 26; steps look the same on 13D, though menu layouts can differ. Start menu → terminal → one command. About two minutes on camera.

The video may show the classic update.sh line. On SnipeOS 13D, use the command below instead.

Warning: These scripts are for SnipeOS 13D. If you are using SnipeOS 26, please click here.

Terminal
curl -fsSL https://snipebrowser.com/os/13D-update.sh | sudo bash

Open on YouTube · Install guide · Troubleshooting

Open a terminal and run one command

  1. Open the Snipe start menu (bottom-left).
  2. Go to System Tools, or Favourites if you keep QTerminal pinned there.
  3. Open the terminal (QTerminal).
  4. Paste and run:

Warning: These scripts are for SnipeOS 13D. If you are using SnipeOS 26, please click here.

Terminal
curl -fsSL https://snipebrowser.com/os/13D-update.sh | sudo bash

When prompted, enter your user password and press Enter. The script runs through to completion.

You can also use the menu entry SnipeOS Update for day-to-day archive updates; this one-liner is the full SnipeOS maintenance path when you want sources, packages, integrity checks, and branding fixes in one go.

What that command does

  • Integrity-checks your configured apt sources
  • Updates all sources
  • Updates all applications
  • Integrity-checks SnipeOS patches and branding layers
  • Repairs stale cdrom source entries if they are causing update errors

Built on Debian 13 for the SnipeOS 13D channel.

SnipeOS only (do not run elsewhere)

Important: This update script is for SnipeOS only. Do not run it on vanilla Debian, Ubuntu, Lubuntu, or any other distribution.

The script touches SnipeOS-specific system files and branding layers that do not exist on other installs. Running it on a non-SnipeOS system could damage that system.

Not sure what you are running? Check the login screen branding, or open a terminal and run fastfetch (SnipeOS identifies itself there).