common.h.diff
> patching file src/glx/dri_common.h
> Hunk #1 succeeded at 57 (offset 2 lines).
>
> Applying patch bug102973-lima.diff
> patching file src/gallium/drivers/lima/lima_resource.c
>
> Now at patch bug102973-lima.diff
> ```
>
> HTH
--
Stuart Young (aka Cefiar)
ream tags are already added. Upload only for pending
> fix now. I have no information if a new version of rc has been
> released.
>
> --
> Cheers,
> Leandro Cunha
>
>
--
Stuart Young (aka Cefiar)
at 15:50, Stuart Young wrote:
> Patch for debian/rules attached to resolve this bug.
>
> Note: By just checking if the variable is empty first, the patch is
> non-specific to x32. It covers the x32 build issue, but will also avoid
> such issues for any platform that AMD vulkan drive
t these changes will become mandatory in the future, so best to
get the warnings sorted now.
Tested build on amd64.
Note: Doesn't seem to affect all options that take true/false, or at least
the ones that affect amd64.
--
Stuart Young (aka Cefiar)
--- a/debian/rules 2020-11-03 06:03:30.000
ulkan drivers.
--
Stuart Young (aka Cefiar)
--- a/debian/rules 2020-11-03 15:11:24.262177791 +1100
+++ b/debian/rules 2020-11-03 15:20:36.960909848 +1100
@@ -75,7 +75,12 @@
GALLIUM_DRIVERS += ,svga,zink
# svga needs xa state tracker
confflags_GALLIUM += -Dgallium-xa=true
- VULKAN_DR
rm is being built already on hurd.
Another way I that may work would be to disable EGL in debian/rules, but
not sure if that's a suitable option?
Note: I can't actually test anything further though as I can't currently
get either mesa 18.3.6 or 20.2.1 to work with qemu passthru on my machine.
--
Stuart Young (aka Cefiar)
ce-select-layer=true
-Dvulkan-overlay-layer=true
Notably from that:
-Dvulkan-drivers=",intel"
Suggest that lines 74-79 need to be modified to check if the VULKAN_DRIVERS
variable already has some value set or not, or treat x32 as a special case,
before adding ",intel" or "intel" to the VULKAN_DRIVERS variable as
appropriate.
Note: I don't have an x32 build env. I just saw the failed buildd logs via
the debian Mesa tracker.
--
Stuart Young (aka Cefiar)
If you are going to package mesa 20.1.10, would you consider applying this
patch?
--
Stuart Young (aka Cefiar)
Commit has made it into the queue for 18.2.2.
On Thu, 27 Sep 2018 at 18:12, Stuart Young wrote:
> This was an upstream issue due to new work in the vulkan driver that uses
> newer libxcb functions (only in 1.13+).
>
> For Mesa 18.2.1, the following upstream commit resolves the
it into Mesa 18.2.2 shortly.
--
Stuart Young (aka Cefiar)
2018 at 13:02, Stuart Young wrote:
> Update: Fix still not present in mesa 18.1.1, so the original patch is
> still required.
>
> On 30 May 2018 at 17:51, Stuart Young wrote:
>
>> Seems that the source issue of this patch is going to be addressed
>> upstream. This
Hi All,
Can any of you try the fix for Bug 901497 ?
This could be an Xwayland issue that until recently was hard to trigger.
Alternatively try using the X.org X server rather than the Wayland one to
see if that helps.
On Sat, 23 Jun. 2018, 02:33 Margot Berg, wrote:
> Hello Yves-Alexis,
>
> th
-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> --
> Laurent.
>
>
--
Stuart Young (aka Cefiar)
if you need more information please
> contact me.
>
> Regards, Robert
>
> --
> Tehnic
>
>
--
Stuart Young (aka Cefiar)
Update: Fix still not present in mesa 18.1.1, so the original patch is
still required.
On 30 May 2018 at 17:51, Stuart Young wrote:
> Seems that the source issue of this patch is going to be addressed
> upstream. This should mean that once it's addressed, the original
> gl
a-dev/2018-May/196034.html
https://lists.freedesktop.org/archives/mesa-dev/2018-May/196038.html
Note: Nothing has been accepted upstream yet. May or may not happen before
18.1.1 is released. Will update this bug if I can when this patch is no
longer needed.
--
Stuart Young (aka Cefiar)
Realised I got the files around the wrong way in the patch. While it'll
probably apply, it'd be better to get it right.
Correct patch attached.
On 14 May 2018 at 20:51, Stuart Young wrote:
> Source: libglu
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
>
Source: libglu
Severity: normal
Tags: patch
Dear Maintainer,
The current Vcs tags in debian/control still refer to git.debian.org
Attached is a patch to update them to point to the source at salsa.debian.org
--- libglu/debian/control 2018-05-14 20:44:04.912681221 +1000
+++ libglu/debian/co
27;)
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.16.6 (SMP w/3 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libclc-r600 depends on:
> ii libclang-common-6.0-dev 1:6.0-3
> ii libclc-dev 0.2.0+git20180312-2
>
> libclc-r600 recommends no packages.
>
> libclc-r600 suggests no packages.
>
> -- no debconf information
>
>
--
Stuart Young (aka Cefiar)
esting using kvm after installing kernel 4.16.0-1-amd64. With
> 4.15.0-3-amd64 no problem.
>
> Chris
>
>
>
--
Stuart Young (aka Cefiar)
merged with 897599, 897632 and 897917.
--
Stuart Young (aka Cefiar)
Source: mesa
Severity: wishlist
Tags: patch
Dear Maintainer,
Attached patch provides notes for the glvnd build patch shipped with Debian.
Note: I have not tried compiling without glvnd-fix-gl-dot-pc.patch so I have
no idea if this patch is even needed anymore, but having some provenance info
lis
Source: mesa
Severity: minor
Tags: patch
Dear Maintainer,
Attached is a patch that updates the Vcs-Git and Vcs-Browser fields in
debian/control to point at salsa rather than anonscm. This fixes current
lintian warnings on these entries.
Note: Patch should apply as is directly to both 17.3.9 (uns
Package: cyrus21-imapd
Followup-For: Bug #260833
I realise that no one upstream wants the autocreate patch, and that
it's unlikely to be included in Debian either. So after a little bit of
research, I decided to work my way around the problem by writing a
script that pulls all the users out of LDA
;Use a proxy
server' box is ticked in the server entry.
--
Stuart Young (aka Cef)
[EMAIL PROTECTED] is for Debian and related email only
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: reportbug
Version: 3.7.1
Severity: normal
Perhaps this should really be wishlist, but it's annoying none the less.
If you configure an smtphost for reportbug, and for some reason, the
smtphost is uncontactable, reportbug exits with an error (fortunately
after saving a copy of the bug in
Package: xchat
Version: 2.4.1-0.1
Severity: normal
I'm trying to use a Socks server with XChat. It just doesn't work,
and instead connects direct without even appearing to talk to the Socks
server.
The actual server is provided by ssh's -D option, and I'm telling
XChat in it's network settings to
27 matches
Mail list logo
