Your message dated Fri, 22 Jul 2022 13:28:51 +0200
with message-id <ytqj82dm+al4+...@xanadu.blop.info>
and subject line Re: mscgen: FTBFS: configure: error: Package requirements
(gdlib) were not met
has caused the Debian Bug report #1015033,
regarding mscgen: FTBFS: configure: error: Package requirements (gdlib) were
not met
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.)
--
1015033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mscgen
Version: 0.20-14
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking pkg-config is at least version 0.9.0... yes
> checking for unistd.h... (cached) yes
> checking for limits.h... yes
> checking for gdlib-config... no
> checking for gdlib... no
> configure: error: Package requirements (gdlib) were not met
>
> Package 'libwebp', required by 'gdlib', not found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables GDLIB_CFLAGS
> and GDLIB_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> cd _build && tail -v -n \+0 config.log
The full build log is available from:
http://qa-logs.debian.net/2022/07/16/mscgen_0.20-14_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Hi Niels,
On 22/07/22 at 11:51 +0200, Niels Thykier wrote:
> Control: tags -1 moreinfo
>
> On Sat, 16 Jul 2022 15:37:05 +0200 Lucas Nussbaum <lu...@debian.org> wrote:
> > Source: mscgen
> > Version: 0.20-14
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20220716 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> >
> > Relevant part (hopefully):
> > > checking pkg-config is at least version 0.9.0... yes
> > > checking for unistd.h... (cached) yes
> > > checking for limits.h... yes
> > > checking for gdlib-config... no
> > > checking for gdlib... no
> > > configure: error: Package requirements (gdlib) were not met
> > >
> > > Package 'libwebp', required by 'gdlib', not found
> > >
> > > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > > installed software in a non-standard prefix.
> > >
> > > Alternatively, you may set the environment variables GDLIB_CFLAGS
> > > and GDLIB_LIBS to avoid the need to call pkg-config.
> > > See the pkg-config man page for more details.
> > > cd _build && tail -v -n \+0 config.log
> >
> >
> > [...]
>
> This looks suspiciously like #1014759, which was fixed the same day as
> you filed this bug. Could I have you please confirm this is still an
> issue with libgd2/2.3.3-6 or later? (I noted your test used 2.3.3-3,
> which current at the time)
I confirm that mscgen now builds fine (and I'm closing this bug).
Lucas
--- End Message ---
