On Mon, 22 Aug 2022 09:59:03 +0300 =?utf-8?q?Sebastian_Dr=C3=B6ge?=
<[email protected]> wrote:
> Source: vala
> Version: 0.56.2-1

.. and all other versions of the package currently in Debian ...

> 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
> 
>   - gnet-2.0.vapi: The corresponding library does not even exist in
> Debian.
> 
> 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.

These files may have been autogenerated at some time in the past, but
upstream are making manual changes to these files quite regularly. e.g.
The gnet file mentioned above appears to have been generated in 2008
but has been edited since.

https://github.com/GNOME/vala/commits/main/vapi/gnet-2.0.vapi

So maybe this bug isn't as clear as initially described. Filed in 2022,
it hasn't stopped vala being included in 3 stable releases, with these
files in place in all source and in each of the valac-<VER>-vapi binary
packages.

I'm not sure whether this bug should be downgraded (I only found it
because it's listed as RC in UDD) or actually closed as a
misinterpretation of the upstream vala source code and maintenance
practices. What started out as generated files do appear to be being
handled by upstream as typical source code.

-- 
Neil Williams
=============
[email protected]
https://www.codehelp.co.uk/

Reply via email to