Your message dated Fri, 10 Apr 2020 12:34:29 +0200
with message-id <96e5a7c0-f187-ea86-ccdb-d988198c6...@debian.org>
and subject line Re: gxr: FTBFS with gulkan 0.14
has caused the Debian Bug report #955606,
regarding gxr: FTBFS with gulkan 0.14
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
955606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gxr
Version: 0.13.2-2
Severity: serious
Tags: ftbfs sid buster
Justification: fails to build from source (but built successfully in the past)

The gulkan transition started, but gxr fails to build against the new
gulkan version:
| Run-time dependency gulkan-0.13 found: NO (tried pkgconfig)
|
| ../meson.build:64:0: ERROR: Dependency "gulkan-0.13" not found, tried 
pkgconfig
|
| A full log can be found at 
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

Cheers
-- 
Sebastian Ramacher

--- End Message ---
--- Begin Message ---
Version: 0.14.0-1

On Fri, 3 Apr 2020 11:01:22 +0200 Sebastian Ramacher <sramac...@debian.org> 
wrote:
> Source: gxr
> Version: 0.13.2-2
> Severity: serious
> Tags: ftbfs sid buster
> Justification: fails to build from source (but built successfully in the past)
> 
> The gulkan transition started, but gxr fails to build against the new
> gulkan version:
> | Run-time dependency gulkan-0.13 found: NO (tried pkgconfig)
> |
> | ../meson.build:64:0: ERROR: Dependency "gulkan-0.13" not found, tried 
> pkgconfig
> |
> | A full log can be found at 
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt

This is now fixed in gxr 0.14.0.

Cheers,
Emilio

--- End Message ---

Reply via email to