[Git][xorg-team/lib/libxres][debian-unstable] control: Migrate to x11proto-dev.

2020-03-09 Thread Timo Aaltonen
Timo Aaltonen pushed to branch debian-unstable at X Strike Force / lib / libxres Commits: 4ccd20d4 by Timo Aaltonen at 2020-03-09T09:29:29+02:00 control: Migrate to x11proto-dev. - - - - - 2 changed files: - debian/changelog - debian/control Changes: =

Processing of mesa_20.0.1-1_source.changes

2020-03-09 Thread Debian FTP Masters
mesa_20.0.1-1_source.changes uploaded successfully to localhost along with the files: mesa_20.0.1-1.dsc mesa_20.0.1.orig.tar.gz mesa_20.0.1-1.diff.gz mesa_20.0.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

mesa_20.0.1-1_source.changes ACCEPTED into experimental

2020-03-09 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Mar 2020 17:40:08 +0200 Source: mesa Architecture: source Version: 20.0.1-1 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Changes: mesa (20.0.1-1) exp

Processed: Re: Internal error: Could not resolve keysym XF86FullScreen

2020-03-09 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 xkbcomp: Internal error: Could not resolve keysym XF86FullScreen Bug #953032 [x11-xkb-utils] Internal error: Could not resolve keysym XF86FullScreen Changed Bug title to 'xkbcomp: Internal error: Could not resolve keysym XF86FullScreen' from 'Internal er

Bug#953032: Internal error: Could not resolve keysym XF86FullScreen

2020-03-09 Thread Thorsten Glaser
Package: x11-xkb-utils Version: 7.7+5 Followup-For: Bug #953032 Control: retitle -1 xkbcomp: Internal error: Could not resolve keysym XF86FullScreen The high keycode errors went away, but this one still happens. (Can I tell it to load a .Xmodmap file instead, by the way? I anyway load one as par

Bug#953032: Internal error: Could not resolve keysym XF86FullScreen

2020-03-09 Thread Timo Aaltonen
On 9.3.2020 21.41, Thorsten Glaser wrote: > Package: x11-xkb-utils > Version: 7.7+5 > Followup-For: Bug #953032 > Control: retitle -1 xkbcomp: Internal error: Could not resolve keysym > XF86FullScreen > > The high keycode errors went away, but this one still happens. The reason, as I see it, is

[Git][xorg-team/lib/mesa] Pushed new tag mesa-20.0.1-1

2020-03-09 Thread Timo Aaltonen
Timo Aaltonen pushed new tag mesa-20.0.1-1 at X Strike Force / lib / mesa -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/tree/mesa-20.0.1-1 You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa] Pushed new tag mesa-20.0.1-2

2020-03-09 Thread Timo Aaltonen
Timo Aaltonen pushed new tag mesa-20.0.1-2 at X Strike Force / lib / mesa -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/tree/mesa-20.0.1-2 You're receiving this email because of your account on salsa.debian.org.

Processing of mesa_20.0.1-2_source.changes

2020-03-09 Thread Debian FTP Masters
mesa_20.0.1-2_source.changes uploaded successfully to localhost along with the files: mesa_20.0.1-2.dsc mesa_20.0.1-2.diff.gz mesa_20.0.1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

mesa_20.0.1-2_source.changes ACCEPTED into experimental

2020-03-09 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Mar 2020 23:20:30 +0200 Source: mesa Architecture: source Version: 20.0.1-2 Distribution: experimental Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Changes: mesa (20.0.1-2) exp

Bug#953032: Internal error: Could not resolve keysym XF86FullScreen

2020-03-09 Thread 積丹尼 Dan Jacobson
Glad somebody found the cause, because it could quickly fill up disks with logged error messages.