Przejdź do treści
Biblioteka skilli
DevOps i chmura · Analiza

os-debian

/os-debian

Diagnozuje i utrzymuje systemy Debian: wsparcie wydań, źródła APT, awarie pakietów, trwałość usług, sieć i obsługiwane aktualizacje.

Repozytorium
octomind-tap ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
11
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Diagnozuje i utrzymuje systemy Debian: wsparcie wydań, źródła APT, awarie pakietów, trwałość usług, sieć i obsługiwane aktualizacje.

Oryginalny opis (EN)

Diagnose and maintain Debian systems: release support, APT sources, package failures, service persistence, networking, and supported upgrades. Use for Debian hosts and Debian-based images.

Jak działa

  1. Overview
  2. Mental model
  3. Releases and support
  4. Debian 13 compatibility changes
  5. APT sources and transactions
  6. Services, networking, and Python
  7. Release upgrades
  8. Read-only diagnostic example
  9. Checklist
  10. References
Sekcje z nagłówków SKILL.md, w oryginale · 69 linii, 859 słów
Podgląd SKILL.md
---
name: os-debian
title: "Debian Operations"
description: "Diagnose and maintain Debian systems: release support, APT sources, package failures, service persistence, networking, and supported upgrades. Use for Debian hosts and Debian-based images."
license: Apache-2.0
compatibility: "Debian userspace; commands depend on installed tools and privileges."
domains: devops
rules:
  - content(debian)
---

## Overview

Operate Debian according to its installed release and package policy. Baseline checked 2026-10-12: Debian 13 “trixie” is stable (point release 13.7, September 2026); Debian 14 “forky” is testing with no release date. Recheck release and security notices before lifecycle decisions. Read `/etc/os-release`, package architecture, repository suites, and deployment configuration before choosing commands. Apply [shared Linux guidance](../os-linux/SKILL.md) for host/container boundaries and general service diagnostics.

## Mental model

Debian's userspace release, running kernel, package candidates, and active configuration are separate facts. A Debian container can run on another distribution's kernel. A successful package installation does not prove that a service started, uses the intended configuration, or will survive recreation.

## Releases and support

- Prefer a supported stable release for new general-purpose production deployments. Stable receives backported fixes; an older upstream version string alone does not prove a missing security fix. Check the Debian package revision and security tracker.
- Debian 13 has regular support through August 2028 and LTS through June 2030. LTS has package and architecture limits; it is not blanket coverage for every installed package. Inspect `check-support-status` when available.
- Debian 12 left regular security support on 2026-07-11 and is in LTS until 2028-06-30; Debian 11's LTS ended 2026-08-31. Third-party extended LTS is a separate arrangement. Use published dates when a status label on an older page conflicts with the calendar.
- Pin the intended codename in managed sources. The alias `stable` moves to a new major release. Point releases collect updates within one release; they are not separate upgrade channels.

## Debian 13 compatibility changes

- `i386` now serves legacy userspace on amd64: there is no official i386 kernel or installer. Don't upgrade a standalone Debian 12 i386 system to trixie; plan an amd64 reinstall where hardware permits.
- All architectures except i386 now use 64-bit `time_t`. On `armel`/`armhf`, library ABIs changed without necessarily changing sonames. Rebuild third-party native packages and test data exchange before deployment; a binary loading successfully does not establish compatibility or rule out silent data loss.

## APT sources and transactions

- For new source entries, use deb822 `.sources` stanzas under `/etc/apt/sources.list.d/`: `Types`, `URIs`, `Suites`, `Components`, and `Signed-By`. Inspect existing `.list` files too; duplicate entries and mismatched options can break updates.
- Keep `trixie`, `trixie-updates`, and `trixie-security` coherent with the installed release; security uses the Debian security archive. Enable only required components, including `non-free-firmware` when needed. Use release-matched backports selectively; don't mix testing, unstable, Ubuntu repositories, or PPAs into stable to obtain one package.
- Scope repository trust with `Signed-By`. Package-managed keyrings belong in `/usr/share/keyrings`; operator-managed ones in `/etc/apt/keyrings`, readable by `_apt`. Obtain keys from the repository publisher and verify identity. Don't use global `apt-key` trust, `trusted=yes`, or disabled signature checks to bypass a failure.
- Use `apt` interactively and `apt-get` in scripts. Refresh indexes before resolving new installs; where supported, `apt-get update --error-on=any` makes partial download failures explicit. Stop on errors instead of silently using stale indexes or switching mirrors/releases.
- `-y` answers APT questions; `DEBIAN_FRONTEND=noninteractive` selects debconf defaults. Neither defines every conffile decision or prevents service restarts. Scope automation settings to the command and make configuration/restart policy deliberate.
- Diagnose with `apt-cache policy PACKAGE`, `apt-mark showhold`, `dpkg --audit`, and APT/dpkg logs. Review `apt-get -s` simulations before removals or dependency repairs. `dist-upgrade` may remove packages; don't use it, `autoremove`, or forced dpkg options as unexplained repairs. Never delete an active package-manager lock.

## Services, networking, and Python

- Check PID 1 before using systemd. Inspect `systemctl cat UNIT`, status, and the unit journal; use `/etc/systemd/system/UNIT.d/` overrides rather than editing packaged unit files. Reloading unit definitions does not restart a running service. Verify runtime behavior and boot enablement separately.
- Discover the manager for the affected interface: ifupdown (`/etc/network/interfaces`), NetworkManager, systemd-networkd, or image-managed configuration. Don't assume Netplan or systemd-resolved is installed. Avoid competing managers and edits to generated resolver files; temporary `ip` changes don't persist.
- Keep Debian's externally managed Python intact. Use distro packages for OS integration, virtual environments for applications, and pipx for isolated Python CLIs. Don't replace `/usr/bin/python3`, remove the external-management marker, or use `--break-system-packages` as a routine fix.

## Release upgrades

Follow the target release notes; Debian 13 supports upgrading from Debian 12, not skipping older releases. Check third-party packages, holds, disk space, backups, recovery access, and service downtime first. Apply the documented staged upgrade and review conffile changes. Verify boot, services, mounts, and application data afterward; an APT exit code alone is insufficient.

## Read-only diagnostic example

Inspect package state without refreshing indexes or changing packages:

```sh
cat /etc/os-release
dpkg --print-architecture
apt-cache policy openssl
apt-mark showhold
dpkg --audit
```

Candidates reflect cached indexes; report their freshness separately.

## Checklist

- [ ] Release, architecture, support coverage, and execution boundary are established.
- [ ] Sources and keys match the intended release; failures remain visible.
- [ ] Dependency changes, restarts, and persistent configuration match the task.
- [ ] Report observed results, changes performed, and unverified runtime behavior separately.

## References

- [Debian releases](https://www.debian.org/releases/), [security tracker](https://security-tracker.debian.org/tracker/), and [LTS package coverage](https://wiki.debian.org/LTS/Using).
- [Debian 13 ABI changes](https://www.debian.org/releases/trixie/release-notes/whats-new.html#bit-time-t-abi-transition) and [i386 restrictions](https://www.debian.org/releases/trixie/release-notes/issues.html#reduced-support-for-i386).
- [APT sources](https://manpages.debian.org/trixie/apt/sources.list.5.en.html), [apt-get](https://manpages.debian.org/trixie/apt/apt-get.8.en.html), and [debconf](https://manpages.debian.org/trixie/debconf-doc/debconf.7.en.html).
- [Debian 13 upgrade procedure](https://www.debian.org/releases/trixie/release-notes/upgrading.html) and [network configuration](https://www.debian.org/doc/manuals/debian-reference/ch05.en.html).
- [Externally managed Python](https://packaging.python.org/en/latest/specifications/externally-managed-environments/).

Wersje

W bazie nie ma innych skilli o nazwie os-debian.

Migawka bazy z 13.11.2026 · wersja paczki a41a00269513 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100debian
    Obejmuje pracę z Debianem w wydaniach 11, 12 i 13: apt i dpkg z pinningiem i backportami, preseed, biuletyny DSA, AppArmor, debsecan oraz system BTS.
  • 100linux-package-management-apt-dnf-pacman
    Instaluje, aktualizuje i diagnozuje pakiety w Debian, Fedora/RHEL i Arch Linux przez apt, dnf i pacman.
  • 100aptly
    Obsługuje repozytoria APT zarządzane przez aptly (nkmideb i sorah-ruby w S3) skryptami bin/sorah-aptly-*: dodawanie pakietów .deb/.dsc, publikację, wsparcie nowych wydań Debiana i Ubuntu oraz usuwanie wadliwych wersji.
  • 100package-management
    Instaluje, aktualizuje i usuwa pakiety w systemach z rodziny Debian i Red Hat przez apt, dpkg, yum lub rpm, także przy naprawie plików.
  • 100fail2ban-setup
    Audytuje lub konfiguruje jaile SSH w Fail2ban na Ubuntu i Debian: backendy logów, zachowanie filtrów i egzekwowanie banów.
  • 100linux-inmemory-stores
    Instaluje, zabezpiecza, wymiaruje i diagnozuje Redis oraz Memcached na Debian/Ubuntu i rodzinie RHEL: bind i uwierzytelnianie, eviction oraz trwałość Redis.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.