[From nobody Sat May 23 19:43:05 2026
Received: (at submit) by bugs.debian.org; 22 Aug 2022 07:09:13 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02
 (2018-09-13) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-17.3 required=4.0 tests=BAYES_00,DIGITS_LETTERS,
 FOURLA,FROMDEVELOPER,MD5_SHA1_SUM,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,
 SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 139; spammy,
 0. spammytokens: hammytokens:0.000-+--bookworm,
 0.000-+--H*M:reportbug, 
 0.000-+--H*MI:reportbug, 0.000-+--H*x:reportbug,
 0.000-+--H*UA:reportbug
Return-path: &lt;slomo@debian.org&gt;
Received: from coaxion.net ([2001:bc8:331f::2]:34976)
 by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.92) (envelope-from &lt;slomo@debian.org&gt;) id 1oQ1Yf-0000ib-IN
 for submit@bugs.debian.org; Mon, 22 Aug 2022 07:09:13 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: =?utf-8?q?Sebastian_Dr=C3=B6ge?= &lt;slomo@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: Ships autogenerated files that can't be renegerated with the code in
 Debian main
Message-ID: &lt;166115154351.76334.317696963720914800.reportbug@lotus.lan&gt;
X-Mailer: reportbug 11.5.1
Date: Mon, 22 Aug 2022 09:59:03 +0300
X-Greylist: delayed 600 seconds by postgrey-1.36 at buxtehude;
 Mon, 22 Aug 2022 07:09:12 UTC
Delivered-To: submit@bugs.debian.org

Source: vala
Version: 0.56.2-1
Severity: serious
Tags: upstream

Hi,

See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html

While that discussion is about Rust packages that were rejected, the same
situation also applies to Vala unfortunately. For more details how to solve
this in a way that makes ftp-masters happy, please refer to them.


The whole vapi subdirectory of the source package currently contains
autogenerated files for which the original source is not available in Debian.

Some examples for this are

  - gstreamer-audio-1.0.vapi: This was generated from the gir file of the
    corresponding library. While the library does exist in Debian and also the
    gir file (libgstreamer-plugins-base1.0-dev), the same version does not
    exist and regenerating it from the version in Debian will introduce
    changes due to being older.

    As of 0.56.2 the file was generated from an unspecified git snapshot after
    the last GStreamer release, see
      https://gitlab.gnome.org/GNOME/vala/-/commit/6d80e07996834ace2a8d0f994913bc9cc623ec9b

  - gnet-2.0.vapi: The corresponding library does not even exist in Debian.

This is not a full list. You'll have to check one by one for all of these
autogenerated files and provide the original source in the correct version, or
ideally regenerate the files based on the source code in Debian on every
build.

&gt;From my understanding, regenerating the files with whatever version is
available in Debian at build time is not an option if you don't want to lose
upstream support for any vapi-related bugs.

These files are also included in binary packages.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (500, 'unstable-debug'), (100, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
]