Bug#903440: xserver-xorg-dev: depends on empty dummy packages

2018-07-09 Thread Damir R. Islamov 
Package: xserver-xorg-dev
Version: 2:1.20.0-3
Severity: minor
Tags: a11y

Dear Maintainer,

xserver-xorg-dev has a lot of deps and build-deps on empty transitional dummy 
packages:

Versions of packages xserver-xorg-dev depends on:
ii  libpciaccess-dev  0.14-1
ii  libpixman-1-dev   0.34.0-2
ii  libxfont-dev  1:2.0.3-1
ii  libxkbfile-dev1:1.0.9-2
ii  mesa-common-dev   18.1.3-1
ii  x11proto-core-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-dev [x11proto-xinerama-dev]  2018.4-4
ii  x11proto-dri2-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-dri3-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-fonts-dev2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-gl-dev   2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-input-dev2018.4-4 transitional dummy package, 
replaced by x11proto-dev
pn  x11proto-kb-dev  transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-present-dev  2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-randr-dev2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-render-dev   2:2018.4-4 transitional dummy 
package, replaced by x11proto-dev
ii  x11proto-resource-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-scrnsaver-dev2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-video-dev2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-xext-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-xf86bigfont-dev  2018.4-4 transitional dummy package, 
replaced by x11proto-dev
pn  x11proto-xf86dri-dev transitional dummy package, 
replaced by x11proto-dev
ii  x11proto-xinerama-dev 2018.4-4 transitional dummy package, 
replaced by x11proto-dev


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xserver-xorg-dev depends on:
ii  libpciaccess-dev  0.14-1
ii  libpixman-1-dev   0.34.0-2
ii  libxfont-dev  1:2.0.3-1
ii  libxkbfile-dev1:1.0.9-2
ii  mesa-common-dev   18.1.3-1
ii  x11proto-core-dev 2018.4-4
ii  x11proto-dev [x11proto-xinerama-dev]  2018.4-4
ii  x11proto-dri2-dev 2018.4-4
ii  x11proto-dri3-dev 2018.4-4
ii  x11proto-fonts-dev2018.4-4
ii  x11proto-gl-dev   2018.4-4
ii  x11proto-input-dev2018.4-4
pn  x11proto-kb-dev   
ii  x11proto-present-dev  2018.4-4
ii  x11proto-randr-dev2018.4-4
ii  x11proto-render-dev   2:2018.4-4
ii  x11proto-resource-dev 2018.4-4
ii  x11proto-scrnsaver-dev2018.4-4
ii  x11proto-video-dev2018.4-4
ii  x11proto-xext-dev 2018.4-4
ii  x11proto-xf86bigfont-dev  2018.4-4
pn  x11proto-xf86dri-dev  
ii  x11proto-xinerama-dev 2018.4-4

xserver-xorg-dev recommends no packages.

xserver-xorg-dev suggests no packages.

-- no debconf information

Processed: Re: Bug#903373: kitty: image rendering seems to be broken

2018-07-09 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 libxkbcommon-x11-0 0.8.0-2
Bug #903373 [kitty] kitty: image rendering seems to be broken
Bug reassigned from package 'kitty' to 'libxkbcommon-x11-0'.
No longer marked as found in versions kitty/0.11.2-3.
Ignoring request to alter fixed versions of bug #903373 to the same values 
previously set
Bug #903373 [libxkbcommon-x11-0] kitty: image rendering seems to be broken
Marked as found in versions libxkbcommon/0.8.0-2.
> retitle -1 "not a valid UTF-8 string" errors creating compose table in en_IN 
> locale
Bug #903373 [libxkbcommon-x11-0] kitty: image rendering seems to be broken
Changed Bug title to '"not a valid UTF-8 string" errors creating compose table 
in en_IN locale' from 'kitty: image rendering seems to be broken'.

-- 
903373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#903373: kitty: image rendering seems to be broken

2018-07-09 Thread James McCoy 
Control: reassign -1 libxkbcommon-x11-0 0.8.0-2
Control: retitle -1 "not a valid UTF-8 string" errors creating compose table in 
en_IN locale

On Mon, Jul 09, 2018 at 11:15:49AM +0530, Ritesh Raj Sarraf wrote:
> Thank you for packaging the newer version of kitty.
> 
> With this version, the `icat` and `diff` commands fail with the
> following error:

This also happens simply when starting kitty, but those go into your
session error log.

> rrs@priyasi:~$ kitty diff rrs-home/Data/Pictures/debian-transparent.png 
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:87:34: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:88:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:89:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:90:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:91:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:92:27: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:93:27: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:94:27: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:95:27: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:96:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: string 
> literal is not a valid UTF-8 string
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: too many 
> errors
> xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:97:29: failed to 
> parse file
> [190 11:11:39.666312] [glfw error 65544]: Failed to create XKB compose table
> 
> 
> Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en 
> (charmap=UTF-8)

That error is directly from xkbcommon's code[0].  If you instead use
LANG=en_IN.UTF-8, then there are no issues.  It appears that xkbcommon
is falling back incorrectly when there isn't an explicit codeset.

[0]: 
https://sources.debian.org/src/libxkbcommon/0.8.0-2/src/compose/parser.c/?hl=207#L207

That being said, just "en_IN" is what "dpkg-reconfigure locales"
generates when selecting that locale.  Both reportbug and "locale -c
charmap" are able to figure out that the codeset is UTF-8.

kitty is using essentially the exact code[1] that xkbcommon's
documentation suggests to use when calling
xkb_compose_table_new_from_locale().

I'm reassigning to xkbcommon to see if there's something they can do to
better handle this.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#891287: Works with xserver-xorg 2:1.20.0-2

2018-07-09 Thread Mariusz Bialonczyk 
On Mon, 25 Jun 2018 16:18:46 +0200
Paul van Tilburg  wrote:

> Hey,
> 
> Also note that if you to test this, that it seems that they have renamed
> the extension from "Composite" to "COMPOSITE".  (I have no idea why
> anyone would do this, without mentioning it in the changelog even, but
> that is besides the issue here).
> 
> So my test config for the 1.20 Xorg server is now:
> 
>   # Test the X server without compositing support
>   Section "Extensions"
>   Option "COMPOSITE" "Disable"
>   EndSection

Paul,
Sorry for the delay.
Thank you for your tip: Indeed without capitalize extension name, xorg
was throwing an error about no such extension.

I only want to finally confirm that the bug which I reported here
was fixed with upstream commit:

https://cgit.freedesktop.org/xorg/xserver/commit/?id=1326ee0bc5eb858c3c00847b3ba65134e4ca2e2d

I had to manually apply this commit on top of 2:1.19.6-1, because every newer 
debian xorg
release is crashing during startup (probably something is wrong in nouveau 
driver according
to backtrace), but this seems totally another and not related bug.

Anyway - this bug is now fixed, so please close it. :-)
Thank you!

ps. I'll also close the upstream related bug.

regards,
-- 
Mariusz Białończyk | xmpp/e-mail: ma...@skyboo.net
http://manio.skyboo.net | https://github.com/manio

Bug#903426: libdrm-nouveau2: "[TTM] Buffer eviction failed" followed by system hanging

2018-07-09 Thread Eric Cooper 
Package: libdrm-nouveau2
Version: 2.4.92-1
Severity: important

This has been happening frequently, but not repeatably so far.
It seems to be triggered by something Chromium is doing when I have
lots of browser windows and tabs open.

I've included the portion of syslog when this occurs.

Once it does happen, the system soon becomes unusable: I can't use X,
and if I ssh in from another machine, I can't kill X; all I can do is reboot.

Jul  9 12:53:47 xyz kernel: [ 3737.149732] WARNING: CPU: 1 PID: 9025 at 
/build/linux-uwVqDp/linux-4.16.16/drivers/gpu/drm/nouveau/nvif/vmm.c:71 
nvif_vmm_put+0x6a/0x80 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149734] Modules linked in: ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter cpufreq_powersave 
cpufreq_conservative cpufreq_userspace usblp snd_usb_audio snd_usbmidi_lib 
snd_hwdep snd_rawmidi snd_seq_device snd_pcm nouveau intel_powerclamp mxm_wmi 
kvm_intel wmi snd_timer video snd evdev ttm drm_kms_helper drm i2c_algo_bit kvm 
irqbypass iTCO_wdt iTCO_vendor_support soundcore asus_atk0110 shpchp 
intel_cstate intel_uncore i7core_edac serio_raw lpc_ich sg button coretemp 
cdc_acm acpi_cpufreq binfmt_misc nfsd parport_pc auth_rpcgss ppdev nfs_acl 
lockd grace sunrpc lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache 
jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 uas 
usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ata_piix 
pata_via
Jul  9 12:53:47 xyz kernel: [ 3737.149793]  ehci_pci crc32c_intel libata 
ehci_hcd r8169 psmouse firewire_ohci i2c_i801 mii scsi_mod firewire_core 
usbcore crc_itu_t usb_common
Jul  9 12:53:47 xyz kernel: [ 3737.149807] CPU: 1 PID: 9025 Comm: kworker/1:2 
Not tainted 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jul  9 12:53:47 xyz kernel: [ 3737.149808] Hardware name: System manufacturer 
System Product Name/P7P55-M, BIOS 110109/04/2012
Jul  9 12:53:47 xyz kernel: [ 3737.149859] Workqueue: events nouveau_cli_work 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149890] RIP: 0010:nvif_vmm_put+0x6a/0x80 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149891] RSP: 0018:b0094d6d3de0 EFLAGS: 
00010282
Jul  9 12:53:47 xyz kernel: [ 3737.149893] RAX: fffe RBX: 
b0094d6d3e08 RCX: 
Jul  9 12:53:47 xyz kernel: [ 3737.149895] RDX:  RSI: 
b0094d6d3d50 RDI: b0094d6d3df0
Jul  9 12:53:47 xyz kernel: [ 3737.149896] RBP: b0094d6d3e38 R08: 
05927000 R09: 
Jul  9 12:53:47 xyz kernel: [ 3737.149897] R10:  R11: 
0073 R12: a046fc484a80
Jul  9 12:53:47 xyz kernel: [ 3737.149899] R13: a0475f7ba280 R14: 
dead0100 R15: a046fc484a90
Jul  9 12:53:47 xyz kernel: [ 3737.149901] FS:  () 
GS:a0477f24() knlGS:
Jul  9 12:53:47 xyz kernel: [ 3737.149903] CS:  0010 DS:  ES:  CR0: 
80050033
Jul  9 12:53:47 xyz kernel: [ 3737.149904] CR2: 7fb227855818 CR3: 
00015540a000 CR4: 06e0
Jul  9 12:53:47 xyz kernel: [ 3737.149905] Call Trace:
Jul  9 12:53:47 xyz kernel: [ 3737.149958]  nouveau_vma_del+0x70/0xc0 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150008]  
nouveau_gem_object_delete_work+0x2d/0x50 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150058]  nouveau_cli_work_flush+0xf8/0x150 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150063]  process_one_work+0x17b/0x360
Jul  9 12:53:47 xyz kernel: [ 3737.150066]  worker_thread+0x2e/0x390
Jul  9 12:53:47 xyz kernel: [ 3737.150069]  ? process_one_work+0x360/0x360
Jul  9 12:53:47 xyz kernel: [ 3737.150072]  kthread+0x113/0x130
Jul  9 12:53:47 xyz kernel: [ 3737.150075]  ? 
kthread_create_worker_on_cpu+0x70/0x70
Jul  9 12:53:47 xyz kernel: [ 3737.150078]  ? SyS_exit+0x13/0x20
Jul  9 12:53:47 xyz kernel: [ 3737.150082]  ret_from_fork+0x35/0x40
Jul  9 12:53:47 xyz kernel: [ 3737.150084] Code: 00 00 00 48 89 e2 be 02 00 00 
00 48 c7 04 24 00 00 00 00 48 89 44 24 08 e8 74 eb ff ff 85 c0 75 0a 48 c7 43 
08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 9d 32 59 e6 0f 1f 00 66 2e 0f 1f 84 00 00 
00 00
Jul  9 12:53:47 xyz kernel: [ 3737.150130] ---[ end trace b3857888a2e5e0a9 ]---
Jul  9 12:53:47 xyz kernel: [ 3737.151286] WARNING: CPU: 1 PID: 9025 at 
/build/linux-uwVqDp/linux-4.16.16/drivers/gpu/drm/nouveau/nvif/vmm.c:71 
nvif_vmm_put+0x6a/0x80 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.151287] Modules linked in: ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter cpufreq_powersave 
cpufreq_conservative cpufreq_userspace usblp snd_usb_audio snd_usbmidi_lib 
snd_hwdep snd_rawmidi snd_seq_device snd_pcm nouveau intel_powerclamp mxm_wmi 
kvm_intel wmi snd_timer video snd evdev ttm drm_kms_helper drm i2c_algo_bit kvm 
irqbypass iTCO_wdt iTCO_vendor_support soundcore asus_atk0110 shpchp 
intel_cstate intel_uncore i7core_edac serio_raw lpc_ich sg button coretemp 
cdc_acm acpi_cpufreq binfmt_misc nfsd parport_pc auth_rpcgss ppdev nfs_acl 
lockd grace

[bts-link] source package libinput

2018-07-09 Thread debian-bts-link 
#
# bts-link upstream status pull for source package libinput
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #902665 (http://bugs.debian.org/902665)
# Bug title: libinput-tools: libinput list-devices fails with segmentation fault
#  * https://gitlab.freedesktop.org/libinput/libinput/issues/50
#  * remote status changed: (?) -> closed
#  * closed upstream
tags 902665 + fixed-upstream
usertags 902665 + status-closed

thanks

Processed: [bts-link] source package libinput

2018-07-09 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package libinput
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #902665 (http://bugs.debian.org/902665)
> # Bug title: libinput-tools: libinput list-devices fails with segmentation 
> fault
> #  * https://gitlab.freedesktop.org/libinput/libinput/issues/50
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 902665 + fixed-upstream
Bug #902665 [libinput-tools] libinput-tools: libinput list-devices fails with 
segmentation fault
Added tag(s) fixed-upstream.
> usertags 902665 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 851810 to X.Org [WAS: xcalib: "Error - unsupported ramp size 0" when trying to invert screen]

2018-07-09 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 xserver-xorg-core
Bug #851810 [xcalib] xcalib: "Error - unsupported ramp size 0" when trying to 
invert screen
Bug reassigned from package 'xcalib' to 'xserver-xorg-core'.
No longer marked as found in versions xcalib/0.8.dfsg1-2.
Ignoring request to alter fixed versions of bug #851810 to the same values 
previously set
> retitle -1 X.org: [stretch] regression impacting accessibility tool xcalib
Bug #851810 [xserver-xorg-core] xcalib: "Error - unsupported ramp size 0" when 
trying to invert screen
Changed Bug title to 'X.org: [stretch] regression impacting accessibility tool 
xcalib' from 'xcalib: "Error - unsupported ramp size 0" when trying to invert 
screen'.
> tags -1 patch stretch
Bug #851810 [xserver-xorg-core] X.org: [stretch] regression impacting 
accessibility tool xcalib
Added tag(s) stretch and patch.
> forwarded -1 https://lists.x.org/archives/xorg-devel/2017-October/054991.html
Bug #851810 [xserver-xorg-core] X.org: [stretch] regression impacting 
accessibility tool xcalib
Set Bug forwarded-to-address to 
'https://lists.x.org/archives/xorg-devel/2017-October/054991.html'.
> found -1 2:1.19.1-4
Bug #851810 [xserver-xorg-core] X.org: [stretch] regression impacting 
accessibility tool xcalib
Marked as found in versions xorg-server/2:1.19.1-4.
> fixed -1 2:1.20.0-1
Bug #851810 [xserver-xorg-core] X.org: [stretch] regression impacting 
accessibility tool xcalib
Marked as fixed in versions xorg-server/2:1.20.0-1.

-- 
851810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

reassign 851810 to X.Org [WAS: xcalib: "Error - unsupported ramp size 0" when trying to invert screen]

2018-07-09 Thread Paul Gevers 
Control: reassign -1 xserver-xorg-core
Control: retitle -1 X.org: [stretch] regression impacting accessibility tool 
xcalib
Control: tags -1 patch stretch
Control: forwarded -1 
https://lists.x.org/archives/xorg-devel/2017-October/054991.html
Control: found -1 2:1.19.1-4
Control: fixed -1 2:1.20.0-1

Dear Debian X Strike Force,

Last year, bug 851810 was reported against xcalib. This program is an
accessibility tool that helps in low contrast situations to improve
readability. It turns out that the issue was in Xorg, not in the tool itself.

On Sat, 10 Mar 2018 00:09:45 +0300 =?UTF-8?B?UmluYXQgSWJyYWdpbW92?=
 wrote:
> Patch was merged in [1]. It's not going to make into any 1.19.x releases, but 
> most probably
> will be included in 1.20.x. (I'm talking about X.Org, not xcalib). Then 
> xcalib should work again.
> 
> [1] 
> https://cgit.freedesktop.org/xorg/xserver/commit/?id=ac138f9b31b0fba00742edbc3326afe66e28099a

Please consider fixing this issue in Stretch. Don't hesitate to ask on
debian-accessibil...@lists.debian.org for more in-depth justification
(for this one-line patch (yes, I know)).

Paul



signature.asc
Description: OpenPGP digital signature

Re: Bug#900108: xserver-xorg-video-geode: FTBFS with xserver 1.20

2018-07-09 Thread Martin-Éric Racine 
It ought to be noted that:

1) This bug was fixed ages ago.
2) It only concerns building against Xserver 1.20, which has been
stuck in unstable for ages.
3) Basically, the version in testing works as expected with the
Xserver that is in testing.

Despite this, xf86-video-geode has been slated for removal.  I'd
really like to know why.

Martin-Éric

2018-05-26 12:28 GMT+03:00 Emilio Pozuelo Monfort :
> Source: xserver-xorg-video-geode
> Version: 2.11.19-3
> Severity: serious
> Tags: patch
>
> geode fails to build with xserver 1.20. There is a patch available
> upstream but no release at this time:
>
> https://cgit.freedesktop.org/xorg/driver/xf86-video-geode/commit/?id=8382e6bb0c76a8029493eae3f2d7a3dbfd0cfc12
>
> Emilio

[Git][xorg-team/wayland/weston][debian-unstable] Fix the watch file

2018-07-09 Thread Emilio Pozuelo Monfort 
Emilio Pozuelo Monfort pushed to branch debian-unstable at X Strike Force / 
wayland / weston


Commits:
f62a1f41 by Emilio Pozuelo Monfort at 2018-07-09T14:46:39+02:00
Fix the watch file

- - - - -


2 changed files:

- debian/changelog
- debian/watch


Changes:

=
debian/changelog
=
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 weston (4.0.0-2) UNRELEASED; urgency=medium
 
   * Update build dependencies.
+  * Update the watch file for the new upstream website layout.
 
  -- Emilio Pozuelo Monfort   Sat, 19 May 2018 17:41:08 +0200
 


=
debian/watch
=
--- a/debian/watch
+++ b/debian/watch
@@ -1,3 +1,3 @@
 #git=git://anongit.freedesktop.org/wayland/weston
 version=3
-https://wayland.freedesktop.org/releases/weston-(.*)\.tar\.xz
+https://wayland.freedesktop.org/releases.html releases/weston-(.*)\.tar\.xz



View it on GitLab: 
https://salsa.debian.org/xorg-team/wayland/weston/commit/f62a1f4139a1f63155d8aadb6a189c3c472aad89

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/wayland/weston/commit/f62a1f4139a1f63155d8aadb6a189c3c472aad89
You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa][debian-unstable] Make libwayland-dev Build-Depends consistent with -dev Depends

2018-07-09 Thread Julien Cristau 
Julien Cristau pushed to branch debian-unstable at X Strike Force / lib / mesa


Commits:
db11d152 by Simon McVittie at 2018-07-09T13:02:21+01:00
Make libwayland-dev Build-Depends consistent with -dev Depends

Commit 4e7be21 added a versioned runtime dependency but didn't
increase the corresponding build-time dependency. This has no
practical effect in testing/unstable, but could become significant
in backports.

Signed-off-by: Simon McVittie 

- - - - -


2 changed files:

- debian/changelog
- debian/control


Changes:

=
debian/changelog
=
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+mesa (18.1.3-2) UNRELEASED; urgency=medium
+
+  * Make libwayland-dev Build-Depends consistent with -dev Depends
+
+ -- Simon McVittie   Mon, 09 Jul 2018 13:02:03 +0100
+
 mesa (18.1.3-1) unstable; urgency=medium
 
   * New upstream release.


=
debian/control
=
--- a/debian/control
+++ b/debian/control
@@ -42,7 +42,7 @@ Build-Depends:
  bison,
  llvm-6.0-dev (>= 1:6.0~) [amd64 arm64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64 sparc64 ppc64el],
  libelf-dev [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips 
mips64el mipsel powerpc ppc64 sparc64 ppc64el],
- libwayland-dev (>= 1.11.0) [linux-any],
+ libwayland-dev (>= 1.15.0) [linux-any],
  libclang-6.0-dev (>= 1:6.0~) [amd64 arm64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64 sparc64 ppc64el],
  libclc-dev (>= 0.2.0+git20180312-1~) [amd64 arm64 armel armhf i386 
kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64 sparc64 
ppc64el],
  wayland-protocols (>= 1.9),



View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/commit/db11d152ded5a9f9686af0fed809a00ac2ac9d94

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/commit/db11d152ded5a9f9686af0fed809a00ac2ac9d94
You're receiving this email because of your account on salsa.debian.org.

wayland-protocols_1.15-1_source.changes ACCEPTED into unstable

2018-07-09 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 09 Jul 2018 12:46:00 +0200
Source: wayland-protocols
Binary: wayland-protocols
Architecture: source
Version: 1.15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Emilio Pozuelo Monfort 
Description:
 wayland-protocols - wayland compositor protocols
Changes:
 wayland-protocols (1.15-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update watchfile for new upstream website layout.
Checksums-Sha1:
 23ff5887afb08d5e71bc36640262ee5c7b7ed22f 2071 wayland-protocols_1.15-1.dsc
 6d44d07280213506ba4958faeeed40a65a5b8a4f 100816 
wayland-protocols_1.15.orig.tar.xz
 2259544f5fd50e185a4e0c3c44fa34873b904c8e 8508 
wayland-protocols_1.15-1.debian.tar.xz
 87d7297fe271fcaac9724d80b41df9ea4a215ae5 5564 
wayland-protocols_1.15-1_source.buildinfo
Checksums-Sha256:
 90cc5dce49d332b38066d90eb592c5490652a5d52cc4dd361befb071714aa256 2071 
wayland-protocols_1.15-1.dsc
 dabb727a4b64e87bfa8c025c1d63919ce12100b49fdeded31857644a59729ee2 100816 
wayland-protocols_1.15.orig.tar.xz
 20667ff0c71a321b491636968234acb73d8dc12b01315474cb12e3b3c578efee 8508 
wayland-protocols_1.15-1.debian.tar.xz
 367e2e51ffd33c70410082d861c0a660c228de825b1076c603f3e18b93524252 5564 
wayland-protocols_1.15-1_source.buildinfo
Files:
 cb3f71abf6968eec52ac4f4cb04ab517 2071 x11 optional wayland-protocols_1.15-1.dsc
 d75ec11e8443946b4795e4be1cf22db8 100816 x11 optional 
wayland-protocols_1.15.orig.tar.xz
 352aecb6f05189bc432e958d0a8bc746 8508 x11 optional 
wayland-protocols_1.15-1.debian.tar.xz
 449efbea11586bba3d921fd7f9f73c0d 5564 x11 optional 
wayland-protocols_1.15-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAltDPPgACgkQnUbEiOQ2
gwJPgw/9H46SQ3hhBgEaHxNWCQIYpsjUuePMQyFg3yRWoq+DrQKh3y1z7XZjyZB8
fHT95G7ZTIEzSwIMMhfMszNTmwIqvgIu9lHWHBW1IiUeZPKf4izziklf7QjF3j2o
MMJ6PM0yZvrtULsTr0crYSnYJvczcehTlrjCmu2aJt/fflo9VhciFKKkRrbbgHbp
ucq8mKgBHN9dilm9ZarIJnwrpf2U3erUdESNyth8ngpy90ubPqY2ooAmcOdPFeMG
kEUawXWhQUX7kjnC+/NweaSoLZ8s41mKH09MRNmon6AKwO33iC/1b3h7H8zS/yBA
cJ+7CGdnBZ31pxOCtyrSDj8SEY4xTc4iCczPAybGrFNaivcvsTyGWDuJ+E84wgPP
mAnjPc3PNW0zdB1NuVWeoxl1GMEn79bcKTS17pYsqn3Ei3nNGJSZMA6c+dyITT9/
1TlvxGvpyg/1LQqm+jshNjG9fq6eceFNmoXiJJclB7/BHWtDLz0P/1Lkp3dEX7IB
/duXhcw/+gv47K8iiHSxp3iIHghXNOtNX2u1+33BzeAbuKmxWB40XchSZWy1gYdd
LBJiJc7+9N3sli8AGy+vEiYmnVhjFSro2RHQxSjOeUbSinpSqKYa8CdGN5lzzSHi
zIrsCT2359yUG9gyKEp0YOzLrtxDt48YioF3fsYubE7VEf3dCGw=
=MlAU
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of wayland-protocols_1.15-1_source.changes

2018-07-09 Thread Debian FTP Masters 
wayland-protocols_1.15-1_source.changes uploaded successfully to localhost
along with the files:
  wayland-protocols_1.15-1.dsc
  wayland-protocols_1.15.orig.tar.xz
  wayland-protocols_1.15-1.debian.tar.xz
  wayland-protocols_1.15-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

[Git][xorg-team/wayland/wayland-protocols] Pushed new tag wayland-protocols-1.15-1

2018-07-09 Thread Emilio Pozuelo Monfort 
Emilio Pozuelo Monfort pushed new tag wayland-protocols-1.15-1 at X Strike 
Force / wayland / wayland-protocols

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/wayland/wayland-protocols/tree/wayland-protocols-1.15-1
You're receiving this email because of your account on salsa.debian.org.