Upstream software project

berusky2

logic game Bugs Escape 3D

About berusky2

logic game Bugs Escape 3D

This project links 4 native package records across 2 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 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records. Catalog coverage diagram, not an application screenshot.berusky2: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
berusky2
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13
License expression
Not reported
Source repository
Not reported

Source-reported description

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

logic game Bugs Escape 3D -- data files

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 12 (Bookworm)

  1. Package berusky2

    bookworm (Debian 12 (Bookworm)) (games): logic game Bugs Escape 3D

    0.12-3: amd64 arm64

  2. Package berusky2-data

    bookworm (Debian 12 (Bookworm)) (games): logic game Bugs Escape 3D -- data files

    0.12-2: all

Debian 13 (Trixie)

  1. Package berusky2

    trixie (Debian 13 (Trixie)) (games): logic game Bugs Escape 3D

    0.12-5: amd64 arm64

  2. Package berusky2-data

    trixie (Debian 13 (Trixie)) (games): logic game Bugs Escape 3D -- data files

    0.12-2: all

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.