libdrm_2.4.103-2_source.changes uploaded successfully to localhost
along with the files:
libdrm_2.4.103-2.dsc
libdrm_2.4.103-2.debian.tar.xz
libdrm_2.4.103-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Fri, 27 Nov 2020 07:48:37 +
with message-id
and subject line Bug#975658: fixed in libdrm 2.4.103-2
has caused the Debian Bug report #975658,
regarding libdrm2: Invalid read after the end of block in xf86drm.c:3594
to be marked as done.
This means that you claim that the pro
Processing commands for cont...@bugs.debian.org:
> reopen 909436
Bug #909436 {Done: Timo Aaltonen } [src:libdrm] libdrm:
FTBFS on hurd-i386
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No
We've detected instances of this bug crashing Firefox. The corresponding
bug in our tracker is this one:
https://bugzilla.mozilla.org/show_bug.cgi?id=1679430
Note that the crash doesn't seem to be present in upstream libdrm, it
seems to me that the `hurd-port.diff` patch applied to the Debian
pac
On Fri, Nov 27, 2020 at 12:04:07AM +, Thorsten Glaser wrote:
> Hi Thomas,
>
> >If you're going to compile it, the debug-trace can be useful
> >(--enable-trace). If not, the -report-fonts option is helpful.
>
> I hadn’t recompiled, at least not with actual changes.
> The -report-fonts output
Hi Thomas,
>If you're going to compile it, the debug-trace can be useful
>(--enable-trace). If not, the -report-fonts option is helpful.
I hadn’t recompiled, at least not with actual changes.
The -report-fonts output is attached, fNorm is the one
in question.
I did a little bisecting: Debian’s
On Thu, Nov 26, 2020 at 10:52:38PM +, Thorsten Glaser wrote:
> Thomas Dickey dixit:
>
> >"Recently" could be something overlooked in #362's change
>
> No, 362 is the current one, and I definitely had this in
> the previous version shipped in Debian as well, but I can’t
> narrow it down furthe
Thomas Dickey dixit:
>"Recently" could be something overlooked in #362's change
No, 362 is the current one, and I definitely had this in
the previous version shipped in Debian as well, but I can’t
narrow it down further than that. According to apt history
log, that was 361.
>On the other hand (i
Your message dated Thu, 26 Nov 2020 22:00:12 +
with message-id
and subject line Bug#975259: fixed in xcb-util 0.4.0-1
has caused the Debian Bug report #975259,
regarding xcb-util: Please update to ≥ 0.3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 25 Nov 2020 15:01:35 +0200
Source: xcb-util
Binary: libxcb-util-dev libxcb-util0-dev libxcb-util1
Architecture: source amd64
Version: 0.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Forc
Your message dated Thu, 26 Nov 2020 22:00:12 +
with message-id
and subject line Bug#965884: fixed in xcb-util 0.4.0-1
has caused the Debian Bug report #965884,
regarding xcb-util: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the
Your message dated Thu, 26 Nov 2020 22:00:12 +
with message-id
and subject line Bug#928586: fixed in xcb-util 0.4.0-1
has caused the Debian Bug report #928586,
regarding Updating the xcb-util Uploaders list
to be marked as done.
This means that you claim that the problem has been dealt with.
On Wed, Nov 25, 2020 at 06:26:14AM +0100, Thorsten Glaser wrote:
> Package: xterm
> Version: 362-1
> Severity: normal
> X-Debbugs-Cc: t...@mirbsd.de
>
> I’ve got the following in my ~/.xinitrc…
>
> /usr/bin/xterm +sb -fg black -geom 78x10+1+637 \
> -bg slateblue -e top &
> /
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 26 Nov 2020 14:55:39 +0200
Source: libxkbcommon
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force
Changed-By: Timo Aaltonen
Closes: 975895
Changes:
l
Your message dated Thu, 26 Nov 2020 13:19:12 +
with message-id
and subject line Bug#975895: fixed in libxkbcommon 1.0.3-2
has caused the Debian Bug report #975895,
regarding libxkbregistry-dev: missing dependency on libxml2-dev
to be marked as done.
This means that you claim that the problem
libxkbcommon_1.0.3-2_source.changes uploaded successfully to localhost
along with the files:
libxkbcommon_1.0.3-2.dsc
libxkbcommon_1.0.3-2.debian.tar.xz
libxkbcommon_1.0.3-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Package: libxkbregistry-dev
Version: 1.0.3-1
Severity: important
Tags: patch
If you have libxkbregistry-dev installed, but not libxml2-dev:
$ pkg-config --cflags --libs xkbregistry
Package libxml-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory con
17 matches
Mail list logo
