Packages / Debian 13 (Trixie) / libdevel / libmsi-dev

Package: libmsi-dev (0.106+repack-1)

Windows Installer file manipulation library - development files

Package information

Homepage
[https://wiki.gnome.org/msitools]
License
Unbekannt: in der indizierten Quelle nicht gemeldet
Downstream-Paketbetreuer
Stephen Kittskitt@debian.org
Quellpaket
[msitools]
Software project
[msitools]

Versions and downloads for libmsi-dev

Version / releaseArchitecture / repositoryPackage sizeInstalled sizeFilesPublisher repository artifact
0.106+repack-1trixie / mainamd64Debian 13 · main · amd6418 KiB138 KiBlist of fileslibmsi-dev_0.106+repack-1_amd64.deb
0.106+repack-1trixie / mainarm64Debian 13 · main · arm6418 KiB138 KiBlist of fileslibmsi-dev_0.106+repack-1_arm64.deb
About these downloads

Jede Zeile ist Paketindex-Metadaten für eine Version, Architektur, Suite und ein Repository. Namen, URLs und Größen stammen aus der Quelle; ein Link ist ein veränderbarer Abrufort, kein Weitergabanspruch von OpenFactory.

Other packages built from msitools

  • gir1.2-libmsi-1.0

    Windows Installer file manipulation library - gir bindings

  • libmsi-1.0-0

    Windows Installer file manipulation library

  • wixl

    Windows Installer creation tool

  • wixl-data

    Windows Installer creation tool — data files

Dependencies and recommendations for libmsi-dev

  • dep: [libmsi-1.0-0] (= 0.106+repack-1)

    Windows Installer file manipulation library

  • dep: gir1.2-gio-2.0-dev

    Package not available

  • dep: [gir1.2-glib-2.0-dev]

    GIR XML for GLib, GObject, Gio and GModule

  • dep: gir1.2-gobject-2.0-dev

    Package not available

  • dep: [gir1.2-libmsi-1.0] (= 0.106+repack-1)

    Windows Installer file manipulation library - gir bindings

Paketdateipfade (17)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /usr/include/libmsi-1.0/libmsi-database.h
  • /usr/include/libmsi-1.0/libmsi-enums.h
  • /usr/include/libmsi-1.0/libmsi.h
  • /usr/include/libmsi-1.0/libmsi-query.h
  • /usr/include/libmsi-1.0/libmsi-record.h
  • /usr/include/libmsi-1.0/libmsi-summary-info.h
  • /usr/include/libmsi-1.0/libmsi-types.h
  • /usr/lib/aarch64-linux-gnu/libmsi-1.0.so
  • /usr/lib/aarch64-linux-gnu/pkgconfig/libmsi-1.0.pc
  • /usr/lib/x86_64-linux-gnu/libmsi-1.0.so
  • /usr/lib/x86_64-linux-gnu/pkgconfig/libmsi-1.0.pc
  • /usr/share/doc/libmsi-dev/changelog.Debian.gz
  • /usr/share/doc/libmsi-dev/changelog.gz
  • /usr/share/doc/libmsi-dev/copyright
  • /usr/share/gir-1.0/Libmsi-1.0.gir
  • /usr/share/vala/vapi/libmsi-1.0.deps
  • /usr/share/vala/vapi/libmsi-1.0.vapi

Field source: Debian 13 (Trixie) main amd64

Bekannte Sicherheitslücken

Keine passenden Meldungen in den erfassten Quellen.

Zuletzt synchronisiert:

[CVE-Katalog]

Prüfsummen

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

0.106+repack-1 / amd64Beobachtet Sep 1, 2026sha256 56e4f19c89cd…0b32e3f9Prüfsumme der Quelle

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Prüfsumme der Quelle (sha256): 56e4f19c89cd79ff13a6ba75ca71e41fa34106dd8b3506c5c9b890990b32e3f9

Download prüfen

printf '%s %s\n' '56e4f19c89cd79ff13a6ba75ca71e41fa34106dd8b3506c5c9b890990b32e3f9' 'libmsi-dev_0.106+repack-1_amd64.deb' | sha256sum --check --strict -

Field source: Debian 13 (Trixie) main amd64

0.106+repack-1 / arm64Beobachtet Sep 1, 2026sha256 f0c601203959…ca7132daPrüfsumme der Quelle

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Prüfsumme der Quelle (sha256): f0c6012039597e5a52036a579730bab87965d879806f453144818ebfca7132da

Download prüfen

printf '%s %s\n' 'f0c6012039597e5a52036a579730bab87965d879806f453144818ebfca7132da' 'libmsi-dev_0.106+repack-1_arm64.deb' | sha256sum --check --strict -

Field source: Debian 13 (Trixie) main arm64

Quellen

  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    trixie-main-amd64:3ab4e811cf4f3e5a335d382c58cc19d85f1abe7a4ef4689160ca1f637fa0e9b3

    Repository-signature verification record
    Signed-object SHA-256
    98b25b5cd185c59d34aa6e4c3e9b5b8f01bbe9d104fe2dcfbcd30dc0a14a59ed
    Signer fingerprint
    4CB50190207B4758A3F73A796ED0E7B82643E131
    Keyring revision
    debian-archive-keyring.gpg
    SHA-256 506b815cbb32d9b6066b4a2aa524071e071761e7e7f68c3ac74f3061ba852017
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Path
    main/binary-amd64/Packages.xz
    Expected SHA-256
    3ab4e811cf4f3e5a335d382c58cc19d85f1abe7a4ef4689160ca1f637fa0e9b3
    Observed SHA-256
    3ab4e811cf4f3e5a335d382c58cc19d85f1abe7a4ef4689160ca1f637fa0e9b3
    Result
    match verified
  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    trixie-main-arm64:753da751bbc7a679f48bd1b623ffd4479cb6861c426118284c76eb82909e4908

    Repository-signature verification record
    Signed-object SHA-256
    98b25b5cd185c59d34aa6e4c3e9b5b8f01bbe9d104fe2dcfbcd30dc0a14a59ed
    Signer fingerprint
    4CB50190207B4758A3F73A796ED0E7B82643E131
    Keyring revision
    debian-archive-keyring.gpg
    SHA-256 506b815cbb32d9b6066b4a2aa524071e071761e7e7f68c3ac74f3061ba852017
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Path
    main/binary-arm64/Packages.xz
    Expected SHA-256
    753da751bbc7a679f48bd1b623ffd4479cb6861c426118284c76eb82909e4908
    Observed SHA-256
    753da751bbc7a679f48bd1b623ffd4479cb6861c426118284c76eb82909e4908
    Result
    match verified

Dieses Paket verwenden

OpenFactory kann dieses Betriebssystem in einer Browser-VM starten oder einen Image-Build mit dem nativen Paketnamen aus diesem Datensatz beginnen.