Timo Aaltonen pushed new tag mesa-18.0.0-rc4-1 at X Strike Force / lib / mesa
---
View it on GitLab:
https://salsa.debian.org/xorg-team/lib/mesa/tree/mesa-18.0.0-rc4-1
You're receiving this email because of your account on salsa.debian.org.
mesa_18.0.0~rc4-1_source.changes uploaded successfully to localhost
along with the files:
mesa_18.0.0~rc4-1.dsc
mesa_18.0.0~rc4.orig.tar.gz
mesa_18.0.0~rc4-1.diff.gz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 12 Feb 2018 10:43:32 +0200
Source: mesa
Binary: libxatracker2 libxatracker-dev libgbm1 libgbm-dev libegl-mesa0
libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa
libgles2-mesa-dev libglapi-mesa libg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 12 Feb 2018 10:43:32 +0200
Source: mesa
Binary: libxatracker2 libxatracker-dev libgbm1 libgbm-dev libegl-mesa0
libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa
libgles2-mesa-dev libglapi-mesa libglx-mesa0 libg
On 10.02.2018 20:57, Eric Valette wrote:
> Package: libgl1-mesa-dri
> Version: 18.0.0~rc2-1
> Severity: critical
> Justification: breaks unrelated software
>
> After sucesfully upgrading this machine with experimental kde; libc6, mesa, I
> went down and upgraded htpc and kids pc that are
>
> AMD
On 02/11/2018 02:20 PM, Michael Stapelberg wrote:
> Given that it has been two weeks, I don’t think we’re going to get a
> reply from debian-x :)
It's not clear to me what the question is. I've also never used
git-buildpackage, so may be missing context.
Cheers,
Julien
>
> I’d suggest to just
When cloning a git repository containing Debian packaging (no matter
whether you use git-clone or gbp-clone), you’ll end up with one or more
branches all tracking the remote from which you cloned (e.g. alioth, or
salsa).
In debian-x, there is
https://salsa.debian.org/xorg-team/debian/xsf-tools/blo
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package xorg-server
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debi
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:wayland
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debi
On 2/12/18 10:36 AM, Timo Aaltonen wrote:
On 10.02.2018 20:57, Eric Valette wrote:
Package: libgl1-mesa-dri
Version: 18.0.0~rc2-1
Severity: critical
Justification: breaks unrelated software
After sucesfully upgrading this machine with experimental kde; libc6, mesa, I
went down and upgraded htp
Excellent, thank you for the update!
On Sat, Feb 10, 2018 at 7:55 AM, Timo Aaltonen wrote:
> Brett Johnson kirjoitti 09.02.2018 klo 18:50:
> > Any chance of a response to this request? If y'all think it's a bad
> > idea, or don't want to do it, that's OK, I'll go back to the drawing
> > board a
Package: xinit
Version: 1.3.4-3+b1
Severity: normal
Hello!
*startx* script ignores many signals, SIGTERM in particular; it causes
problems with process supervision.
Please consider applying following patch, which fulfil intended purpose
of ``trap`` statement, keeping process resposible to signa
12 matches
Mail list logo
