On 26/08/2021 00:35, Steven Robbins wrote:
ldd /usr/bin/digikam |grep -i freetype
Hello,
I had a old libfreetype.so.6 sitting in /usr/local.
I did make searches for libfreetype but hadn't the reflexe of ldd digikam.
Sorry for the error and thanks for your help.
Best regards
Alain
Processing commands for cont...@bugs.debian.org:
> forwarded 992932 https://github.com/project-gemmi/gemmi/issues/136
Bug #992932 [src:gemmi] gemmi FTBFS on i386: pptest (Failed)
Set Bug forwarded-to-address to
'https://github.com/project-gemmi/gemmi/issues/136'.
> tags 992932 + confirmed
Processing control commands:
> severity -1 important
Bug #978695 [notepadqq] notepadqq: Input windows hangs so input is not possible
Severity set to 'important' from 'grave'
> tags -1 moreinfo unreproducible
Bug #978695 [notepadqq] notepadqq: Input windows hangs so input is not possible
Added
Control: severity -1 important
Control: tags -1 moreinfo unreproducible
On Wed, 30 Dec 2020 12:42:15 +0100 Michael Rasmussen wrote:
> Package: notepadqq
> Version: 2.0.0~beta1-1+b1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> When notepadqq is started you
I have the same error on Debian 11:
[...]
yowsup-cli v2.0.15
yowsup v2.5.7
[...]
INFO:yowsup.common.http.warequest:b'{"login":"XXX","param":"authkey","reason":"missing_param","status":"fail"}\n'
status: b'fail'
reason: b'missing_param'
param: b'authkey'
login: b'XXX'
On Tuesday, August 24, 2021 4:32:33 A.M. CDT Alain Bertrand wrote:
>
> Launching digikam
> digikam: symbol lookup error:
> /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol:
> FT_Palette_Select and digikam exits
I have not encountered this myself.
A quick google suggested
Your message dated Wed, 25 Aug 2021 22:19:28 +
with message-id
and subject line Bug#978856: fixed in libmatheval 1.1.11+dfsg-5
has caused the Debian Bug report #978856,
regarding libmatheval: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem has been
Hello Adrian,
thanks for making the failures visible with this bug.
I'm waiting for my access to porter boxes [1] in order to debug and fix
the issue(s).
In the meantime, do not hesitate to provide patch or any kind of help.
Best Regards,
François
[1]:
Your message dated Wed, 25 Aug 2021 20:37:38 +
with message-id
and subject line Bug#992968: fixed in xarchiver 1:0.5.4.17-3
has caused the Debian Bug report #992968,
regarding xarchiver FTBFS: configure: error: cannot find required auxiliary
files: compile
to be marked as done.
This means
Your message dated Wed, 25 Aug 2021 20:36:44 +
with message-id
and subject line Bug#983758: fixed in python-xarray 0.19.0-3
has caused the Debian Bug report #983758,
regarding python-xarray: autopkgtest regression on several architectures
to be marked as done.
This means that you claim that
On Mon, Aug 23, 2021 at 08:18:42AM -0400, Michael Lazin wrote:
> I am new to this list and would like to get involved, but I am a relative
> beginner in programming. I understand from looking at this CVE that it is
> triggered by a particular type of API call, which is probably unlikely in
> the
Severity: normal
Hello,
update/correction: the plugin still works with the usual
vim-addon-manager
Enrico
--
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini
Hi there,
Do you have any recommendations on where to start with this bug?
I've tried running autoupdate & autoreconf to no success -
hibby@fennec ~/D/D/a/aprx (master)> autoreconf
Your message dated Wed, 25 Aug 2021 19:35:25 +
with message-id
and subject line Bug#992921: fixed in timeshift 20.11.1-1.1
has caused the Debian Bug report #992921,
regarding timeshift: util-linux 2.37.2-1 breaks timeshift
to be marked as done.
This means that you claim that the problem has
Package: vim-syntastic
Version: 3.10.0-2
Severity: serious
Hello,
the upgrade instructions for bullseye say:
* Before upgrading, run "vam remove " for any addon in this package
that has been installed with "vam install ". Adjust the command
as necessary for system-wide installed
Source: plib
Version: 1.8.5-8
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://sourceforge.net/p/plib/bugs/55/
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for plib.
CVE-2021-38714[0]:
| In Plib
Processing control commands:
> severity -1 grave
Bug #992921 [timeshift] timeshift: util-linux 2.37.2-1 breaks timeshift
Severity set to 'grave' from 'important'
> tags -1 +bookworm +sid
Bug #992921 [timeshift] timeshift: util-linux 2.37.2-1 breaks timeshift
Added tag(s) bookworm.
Bug #992921
Source: xarchiver
Version: 1:0.5.4.17-2
Severity: serious
Tags: ftbfs
xarchiver fails to build from source in unstable, because configure
misses a compile file. The build ends with:
| dh_auto_configure -- --libexecdir=/usr/lib
| ./configure --build=x86_64-linux-gnu --prefix=/usr
Processing commands for cont...@bugs.debian.org:
> tags 992960 + pending
Bug #992960 [src:nfstrace] nfstrace: FTBFS due to RPC removal from glibc
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
992960:
Your message dated Thu, 26 Aug 2021 02:25:43 +0900
with message-id
and subject line Re: Bug#978923: wide-dhcpv6: ftbfs with autoconf 2.70
has caused the Debian Bug report #978923,
regarding wide-dhcpv6: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem
close 978818
thanks
i'm closing this as unreproducible.
E.g. in https://salsa.debian.org/multimedia-team/pd/gem/-/pipelines/280549 all
jobs succeed.
The builds use autoconf_2.71-2 (and 'malloc' is properly detected).
Processing commands for cont...@bugs.debian.org:
> close 978818
Bug #978818 [src:gem] gem: ftbfs with autoconf 2.70
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978818
Debian Bug
Your message dated Wed, 25 Aug 2021 16:34:17 +
with message-id
and subject line Bug#992902: fixed in lizzie 0.7.4+dfsg1-3
has caused the Debian Bug report #992902,
regarding lizzie build-depends on removed package
to be marked as done.
This means that you claim that the problem has been
Source: gadap
Version: 2.0-12
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got
Source: netkit-rwall
Version: 0.17-8
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it
Source: netkit-rusers
Version: 0.17-10
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it
Source: netkit-bootparamd
Version: 0.17-10
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and
Source: nfstrace
Version: 0.4.3.2+git20200805+b220d04-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from
Source: nx-libs
Version: 2:3.5.99.26-2
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it
Your message dated Wed, 25 Aug 2021 16:18:44 +
with message-id
and subject line Bug#992928: fixed in libtasn1-6 4.17.0-2
has caused the Debian Bug report #992928,
regarding libtasn1-6 arch-only FTBFS: Can't exec "gtkdocize": No such file or
directory at
Processing commands for cont...@bugs.debian.org:
> owner 992902 tmanc...@debian.org
Bug #992902 [lizzie] lizzie build-depends on removed package
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
992902:
On Tue, Aug 24, 2021 at 08:25:29PM +0100, peter green wrote:
> package: lizzie
> version: 0.7.4+dfsg1-2
> severity: serious
>
> lizzie build-depends on libjuniversalchardet-java-doc which is no longer
> built by the
> libjuniversalchardet-java source package. It is still present in unstable as
Your message dated Wed, 25 Aug 2021 15:49:02 +
with message-id
and subject line Bug#992844: fixed in mercurial 5.9-2
has caused the Debian Bug report #992844,
regarding mercurial: FTBFS on s390x (ERROR: test-upgrade-repo.t output changed)
to be marked as done.
This means that you claim that
Control: tags 978883 unreproducible moreinfo
Control: severity 978883 important
Hi Matthias,
I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and
GCC-10/11. I tested this package and 32 other packages with the same
bug. I wasn't able to reproduce this issue in 18 packages. Maybe it
Processing control commands:
> tags 978883 unreproducible moreinfo
Bug #978883 [src:pnscan] pnscan: ftbfs with autoconf 2.70
Added tag(s) unreproducible and moreinfo.
> severity 978883 important
Bug #978883 [src:pnscan] pnscan: ftbfs with autoconf 2.70
Severity set to 'important' from 'serious'
Processing control commands:
> tags 978906 unreproducible moreinfo
Bug #978906 [src:tcpxtract] tcpxtract: ftbfs with autoconf 2.70
Added tag(s) unreproducible and moreinfo.
> severity 978906 important
Bug #978906 [src:tcpxtract] tcpxtract: ftbfs with autoconf 2.70
Severity set to 'important' from
Control: tags 978906 unreproducible moreinfo
Control: severity 978906 important
Hi Matthias,
I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and
GCC-10/11. I tested this package and 32 other packages with the same
bug. I wasn't able to reproduce this issue in 18 packages. Maybe it
Em qua., 25 de ago. de 2021 às 06:30, Christoph Biedl
escreveu:
>
> Control: tags 978905 unreproducible moreinfo
>
> Matthias Klose wrote...
>
> > The package fails to build in a test rebuild on at least amd64 with
> > autoconf 2.70, but succeeds to build with autoconf 2.69. The
> > severity of
Hey Matthias,
> checking for library containing inet_pton... none required
> checking for library containing socket... none required
> checking for GNU libc compatible malloc... yes
> configure: error: cannot run /bin/sh ./config.sub
Can you double-check this/run a rebuild and see if it was a
Control: tags 991448 + patch
Control: tags 991448 + pending
I've prepared an NMU for ui-utilcpp (versioned as 1.10.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I should delay
it longer.
MR at https://salsa.debian.org/debian/ui-utilcpp/-/merge_requests/1 if
you want to
Your message dated Wed, 25 Aug 2021 14:28:32 +0200
with message-id
and subject line FTBFS failure with ac270 but not with ac271
has caused the Debian Bug report #978786,
regarding coinor-cbc: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem has been dealt
* Wookey [2021-08-25 12:30]:
On 24/08/2021 07:45, Rafael Laboissière wrote:
I am hereby reassigning the Bugs #979458 and #979459, which were
assigned to the binary jed and jed-common packages, to the jed
source package. I am also merging this two bug reports and rising
their severity level to
Your message dated Wed, 25 Aug 2021 11:33:32 +
with message-id
and subject line Bug#982791: fixed in mit-scheme 11.2-2
has caused the Debian Bug report #982791,
regarding mit-scheme FTBFS on i386: out of memory
to be marked as done.
This means that you claim that the problem has been dealt
On 24/08/2021 07:45, Rafael Laboissière wrote:
I am hereby reassigning the Bugs #979458 and #979459, which were
assigned to the binary jed and jed-common packages, to the jed source
package. I am also merging this two bug reports and rising their
severity level to serious.
The trivial patch
Your message dated Wed, 25 Aug 2021 12:24:07 +0200
with message-id
and subject line Re: Bug#992158: Race in ifup maybe related to brctl failure in
pre-up of network interface
has caused the Debian Bug report #992158,
regarding Race in ifup maybe related to brctl failure in pre-up of network
> Thank you for your assistance. With hint for the relevant man
> page "bridge-utils-interfaces" I found the bridge setup working
> using the configuration
>
> auto br0
> iface br0 inet static
> address 192.168.1.1
> network 192.168.1.0
> netmask 255.255.255.0
> bridge_ports none
>
Your message dated Wed, 25 Aug 2021 11:49:52 +0200
with message-id
and subject line Re: Bug#978905: tcpreplay: ftbfs with autoconf 2.70
has caused the Debian Bug report #978905,
regarding tcpreplay: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tags 978905 unreproducible moreinfo
Bug #978905 [src:tcpreplay] tcpreplay: ftbfs with autoconf 2.70
Added tag(s) unreproducible and moreinfo.
--
978905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978905
Debian Bug Tracking System
Contact
Control: tags 978905 unreproducible moreinfo
Matthias Klose wrote...
> The package fails to build in a test rebuild on at least amd64 with
> autoconf 2.70, but succeeds to build with autoconf 2.69. The
> severity of this report will be raised before the bookworm release,
> so nothing has to be
Processing control commands:
> tags 991448 + patch
Bug #991448 [ui-utilcpp] ui-utilcpp: migration to libtirpc-dev
Ignoring request to alter tags of bug #991448 to the same tags previously set
> tags 991448 + pending
Bug #991448 [ui-utilcpp] ui-utilcpp: migration to libtirpc-dev
Added tag(s)
Processing commands for cont...@bugs.debian.org:
> tags 992912 + upstream fixed-upstream
Bug #992912 [src:mat2] mat2: autopkgtests fail with ffmpeg 4.4
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
992912:
Processing commands for cont...@bugs.debian.org:
> reassign 966899 src:xneur
Bug #966899 [src:gxneur] gxneur: FTBFS: ld:
gxneur-trayicon.o:/usr/include/xneur/xneur.h:35: multiple definition of
`main_window'; gxneur-misc.o:/usr/include/xneur/xneur.h:35: first defined here
Bug reassigned from
Your message dated Wed, 25 Aug 2021 08:41:40 +
with message-id
and subject line Bug#992376: fixed in systemd 249.3-4
has caused the Debian Bug report #992376,
regarding systemd-standalone-{sysusers,tmpfiles}: missing Breaks+Replaces:
systemd (<< 249.3-2)
to be marked as done.
This means
Source: python-xarray
Version: 0.19.0-2
Followup-For: Bug #983758
The problem is exacerbated in 0.19.0-2 by this error during test
collection
/usr/lib/python3/dist-packages/xarray/tests/test_tutorial.py:9: in
class TestLoadDataset:
Source: ukui-media
Version: 3.0.3-1
Severity: serious
Tags: ftbfs
ukui-media fails to build from source. A parallel=1 build ends with:
| g++ -c -pipe -std=c++11 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++11
Source: libtasn1-6
Version: 4.16.0-2
Severity: serious
Tags: ftbfs
libtasn1-6 fails to perform an arch-only build (but succeeds a full
build). A build ends with:
| dh binary-arch
|dh_update_autotools_config -a
|dh_autoreconf -a
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR,
Package: mutt
Version: 2.0.5-4.1
Severity: grave
Justification: causes non-serious data loss
Mutt 2.1.2 is available. From the announce: "This is an important
bug-fix release, fixing a potential data-loss IMAP bug. IMAP users
are strongly advised to upgrade."
For stable and oldstable:
* Rafael Laboissière [2021-08-24 08:45]:
[…]
The trivial patch that fixes the problem is attached to this message.
Please, consider rather the patch that is attached to the present
message. The jed-common.prerm script must honor the failed-upgrade
argument, since the script in version
Processing commands for cont...@bugs.debian.org:
> tags 978824 + ftbfs
Bug #978824 [src:granule] granule: ftbfs with autoconf 2.70
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978824
Source: cod-tools
Version: 3.2.0+dfsg-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/i386/c/cod-tools/14823189/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/c/cod-tools/14823170/log.gz
...
Source: freefem++
Version: 4.9+dfsg1-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/arm64/f/freefem++/14730686/log.gz
https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/freefem++/14702337/log.gz
...
g++ -c -fPIC '-I/usr/include/freefem++' -g -O2 -fstack-protector-strong
Source: manaplus
Version: 2.1.3.17-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=manaplus=2.1.3.17-1
...
debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
chmod -x
Hi,
I can reproduce the autopkgtest failure on my system after only
upgrading xkb-data from 2.29-2 to 2.33-1.
I noticed that the xkb-data build has been changed to meson [1], and
it is no longer instructed to install xfree86 symlinks.
And also according to a debdiff, xfree86-related symlinks are
Source: gpgme1.0
Version: 1.16.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gpgme1.0=1.16.0-1
...
[-- Response --]
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
Your message dated Wed, 25 Aug 2021 09:16:53 +0200
with message-id <6c30fa3b-de06-bba0-1e8d-b2af7b25b...@debian.org>
and subject line Re: gold linker crashing with -Wl,--threads
has caused the Debian Bug report #978768,
regarding gold linker crashing with -Wl,--threads
to be marked as done.
This
Version: 2.37-4
builds fine at least on amd64.
66 matches
Mail list logo
