Upstream software project

kup-backup

Backup scheduler for the Plasma desktop

About kup-backup

Backup scheduler for the Plasma desktop

This project links 9 native package records across 6 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 2 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.kup-backup: recorded package coverageDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.62 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
kup-backup
Publisher
Not authoritatively mapped
Native package records
9
Operating systems
debian-13, fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-3.0-or-later
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Kup is created for helping people to keep up-to-date backups of their personal files. Connecting a USB hard drive is the primary supported way to store files, but saving files to a server over a network connection is also possible for advanced users. When you plug in your external hard drive Kup will automatically start copying your latest changes, but of course it will only do so if you have been active on your computer for some number of hours since the last time you took a backup (and it can of course ask you first, before copying anything). In general Kup tries to not disturb you needlessly.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 13 (Trixie)

  1. Package kup-backup

    trixie (Debian 13 (Trixie)) (kde): backup tool for KDE's Plasma desktop

    0.10.0-1+b1: amd64 arm64

    Source: kup-backup

Fedora 43

  1. Package kup-backup

    43 (Fedora 43) (Unspecified): Backup scheduler for the Plasma desktop

    0.10.0^git20260214.094327.92115c2-1.fc43: aarch64 i686 x86_64

    Source: kup-backup

Fedora 44

  1. Package kup-backup

    44 (Fedora 44) (Unspecified): Backup scheduler for the Plasma desktop

    0.10.0^git20260214.094327.92115c2-1.fc44: aarch64 i686 x86_64

    Source: kup-backup

openSUSE Leap 15.6

  1. Package kup-backup

    leap-15.6 (openSUSE Leap 15.6) (System/GUI/KDE): Backup scheduler for the Plasma desktop

    0.9.1-bp156.4.10: aarch64 ppc64le s390x x86_64

    Source: kup-backup

  2. Package kup-backup-lang

    leap-15.6 (openSUSE Leap 15.6) (System/Localization): Translations for package kup-backup

    0.9.1-bp156.4.10: noarch

    Source: kup-backup

openSUSE Leap 16.0

  1. Package kup-backup

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Backup scheduler for the Plasma desktop

    0.10.0-bp160.1.16: aarch64 ppc64le s390x x86_64

    Source: kup-backup

  2. Package kup-backup-lang

    leap-16.0 (openSUSE Leap 16.0) (System/Localization): Translations for package kup-backup

    0.10.0-bp160.1.16: noarch

    Source: kup-backup

openSUSE Tumbleweed

  1. Package kup-backup

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Backup scheduler for the Plasma desktop

    0.10.0-2.6: x86_64

    Source: kup-backup

  2. Package kup-backup-lang

    tumbleweed (openSUSE Tumbleweed) (System/Localization): Translations for package kup-backup

    0.10.0-2.6: noarch

    Source: kup-backup

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.