Bug#1067733: iptables: regression in 1.8.9 with -n breaks portblock in resource-agents

[Fabio Pedretti]

> Version 1.8.10 fixed this bug (see "udp" and "tcp" in "prot") in
> https://git.netfilter.org/iptables/commit/?id=34f085b1607364f4eaded1140060dcaf965a2649

iptables 1.8.10 was released on 2023-10-10, but this commit was merged
in 2024-02-07, so it is not fixed in 1.8.10, but it will be in the
release after that.

Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

[Fabio Pedretti]

Version: 24.0.3-1+b1

Great, they belong to the same source package and should be both upgraded.
Closing.

> With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64
> 23.3.3-3, the result is the same.
>
> But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue
> is fixed.

Bug#1067207: mesa: switch statement too large, might need -mlong-jump-table-offsets

[Fabio Pedretti]

Maybe it's better to file an issue or send a MR upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests

It looks like m68k was considered in the past:
https://cgit.freedesktop.org/mesa/mesa/log/?qt=grep=m68k

Bug#405859: GLUT_ALPHA does not work with DRI

[Fabio Pedretti]

Version: 8.0-1

mga driver was removed from mesa since 8.0 in 2012:
https://docs.mesa3d.org/relnotes/8.0.html

Bug#646929: libgl1-mesa-glx: message "failed to create drawable" when starting Firefox

[Fabio Pedretti]

Version: 8.0-1

It looks like this was addressed in mesa years ago with this commit:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=4833104718677caad0027d5e7539ca9bba389392

Bug#775235: use llvm's getCPUTargetFeatures() over getHostCPUName()

[Fabio Pedretti]

It looks like the src/gallium/auxiliary/gallivm/lp_bld_misc.cpp file
in mesa was heavily updated for managing newer llvm versions, even if
mesa is still using getHostCPUName and still not getCPUTargetFeatures.

Michael, do you think there is still something to do in mesa?

Steve and Bernhard, are you still able to reproduce the original issue?

Bug#901533: mesa: please build intel_sanitize_gpu tool

[Fabio Pedretti]

There is a MR here, but needs to be updated:
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/26

Bug#1018207: mesa: missing svga gallium driver for arm64

[Fabio Pedretti]

Version: 22.2.0-1

"svga" gallium driver was added in 22.2.0-1.

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Fabio Pedretti]

This was fixed in mutter 43.8 and 44.4 as per mutter report
https://gitlab.gnome.org/GNOME/mutter/-/issues/2602

Bug#1041647: radeonsi: no VAAPI support (regression)

[Fabio Pedretti]

Closing as per previous comment.

Bug#1065131: electron: GPU process crash with AMDGPU, ac: Unknown GPU, using 0 for raster_config

[Fabio Pedretti]

Can you try again with 24.0.3-1 ?
Thanks.

Il giorno ven 1 mar 2024 alle ore 00:12 Alexis Murzeau
 ha scritto:
>
> Package: mesa-va-drivers
> Version: 24.0.1-1
> Severity: important
>
> * What led up to the situation?
> Upgrading mesa-va-drivers to version 24.0.1-1 cause GPU process craches
> in electron based applications.

Bug#1017819: libgl1-mesa-dri: Memory leak in iris_dri.so causes Xorg to eat all memory and crash every few days

[Fabio Pedretti]

Current Debian stable (12, bookworm) has the fix.

Bug#1001836: libgl1-mesa-dri: Incorrect texture blitting/mapping seen on Intel (Mesa issue #4412)

[Fabio Pedretti]

Version: 21.0.3-1

Fixed since 21.0.3-1, as per upstream bug report.

Bug#1065654: mesa ftbfs with time_t64

[Fabio Pedretti]

Il Ven 8 Mar 2024, 11:21 Matthias Klose  ha scritto:

> On 08.03.24 11:00, Fabio Pedretti wrote:
> > Already fixed upstream, the patch will be included since 24.0.3 (will
> > be released in 5 days):
> >
> https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854
>
> no, that commit is only fixing one occurrence.
>

The other file is not built in Debian, a fix will anyway also be included
in 24.0.3.

>

Bug#1065654: mesa ftbfs with time_t64

[Fabio Pedretti]

Already fixed upstream, the patch will be included since 24.0.3 (will
be released in 5 days):
https://cgit.freedesktop.org/mesa/mesa/commit/?h=staging/24.0=8ea039019761ecc25d49f075aef50de6e81db854


Il giorno ven 8 mar 2024 alle ore 10:27 Matthias Klose
 ha scritto:
>
> Package: src:mesa
> Version: 24.0.2-1
> Severity: serious
> Tags: sid trixie patch
>
> mesa ftbfs with time_t64, patch attached. I didn't check if the
> _TIMET_BITS are used in the affected files.
>
> There's also a bug in the profile support. WINE cannot be built without
> LLVM, and therefore should be disabled.

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

[Fabio Pedretti]

Ubuntu fixed it with this patch:
https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz

Bug#1056117: meson: generates non-determinstic .pkgconfig files

[Fabio Pedretti]

Source-Version: 1.3.1-1

Fixed upstream in 1.3.1.

Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

[Fabio Pedretti]

You can try installing version 24.0.0~rc3-1 in experimental, which
should have this issue fixed.

Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

[Fabio Pedretti]

Hi jim_p, if you are referring to:
https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080
I don't think is related to this issue.
I suggest to report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues
In your log this looks relevant:
[   0.318][v][vo/gpu/vaapi] using EGL dmabuf interop
[   0.319][v][vo/gpu/vaapi] Trying to open a x11 VA display...
[   0.319][d][vo/gpu/vaapi/vaapi] libva: VA-API version 1.20.0
[   0.319][d][vo/gpu/vaapi/vaapi] libva: Trying to open
/usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
[   0.328][d][vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_20
[   0.340][d][vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0
[   0.341][v][vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20
[   0.341][d][ffmpeg] AVHWDeviceContext: VAAPI driver: Mesa Gallium
driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM
17.0.6).
[   0.341][d][ffmpeg] AVHWDeviceContext: Driver not found in known
nonstandard list, using standard behaviour.
[   0.341][v][vo/gpu/vaapi] Going to probe surface formats (may log
bogus errors)...
[   0.344][d][vo/gpu/vaapi] Failed to create mapper
[   0.344][d][vo/gpu/vaapi] Unsupported format: yuyv422
[   0.345][d][vo/gpu/vaapi] Failed to create mapper
[   0.345][d][vo/gpu/vaapi] Unsupported format: uyvy422
[   0.346][d][vo/gpu/vaapi] vaExportSurfaceHandle() failed (an
unsupported memory type was supplied)
[   0.346][d][vo/gpu/vaapi] Unsupported format: argb
[   0.346][d][vo/gpu/vaapi] Supported formats:
[   0.346][d][vo/gpu/vaapi]  nv12
[   0.346][d][vo/gpu/vaapi]  p010
[   0.346][d][vo/gpu/vaapi]  yuv420p
[   0.346][d][vo/gpu/vaapi]  gray
[   0.346][d][vo/gpu/vaapi]  yuv444p
[   0.346][d][vo/gpu/vaapi]  bgra
[   0.346][d][vo/gpu/vaapi]  rgba
[   0.346][d][vo/gpu/vaapi]  bgr0
[   0.346][d][vo/gpu/vaapi]  rgb0
[   0.346][v][vo/gpu/vaapi] Done probing surface formats.

Bug#787764: libvpx2: vp9 encoding is significantly slower in 1.4.0 than in 1.3.0

[Fabio Pedretti]

Hi Matt, can you check if the performance regression you noticed with
1.4.0 was resolved with a newer libvpx release?
You may also eventually check the upstream issues report at
https://bugs.chromium.org/p/webm/issues/list
Thanks.

Bug#1015532: libvpx: ftbfs with LTO (link time optimization) enabled

[Fabio Pedretti]

forwarded 1015532 https://bugs.chromium.org/p/webm/issues/detail?id=1736
thanks

Bug#1056906: debuild: cannot disable lintian

[Fabio Pedretti]

Please close this issue. Thanks.

Bug#1054645:

[Fabio Pedretti]

forwarded 1054645 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10228
thanks

Bug#1056906: debuild: cannot disable lintian

[Fabio Pedretti]

Il giorno dom 26 nov 2023 alle ore 14:37 Adam D. Barratt
 ha scritto:
>
> Control: tags -1 + moreinfo
>
> On Sun, 2023-11-26 at 14:06 +0100, Fabio Pedretti wrote:
> > when I add --no-lintian (as found in debuild man page) option
> > to debuild, I get the following error:
> >
> > ...
> >  dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian
> > dpkg-buildpackage: error: unknown option or argument --no-lintian
>
> That suggests you've added it in the wrong part of the command line.
> https://manpages.debian.org/bookworm/devscripts/debuild.1.en.html
> clearly shows in the synopsis that all debuild-specific options must
> come _before_ any dpkg-buildpackage-specific options, and that --(no-
> )lintian affects the behaviour of debuild itself, so falls into the
> former set.
>
> What *exactly* does your debuild invocation look like?

You are right, I was calling it this way:
debuild -S -sd -d -kMYKEY --no-lintian
while this way it works:
debuild --no-lintian -S -sd -d -kMYKEY

About the man page, it says:
debuild [debuild options] [dpkg‐buildpackage options] [--lintian‐opts
lintian options]
which let me suppose lintian options have to be called at last. But it
is just for the specific --lintian‐opts, not --(no-)lintian, OK.

> > I also tried setting:
> > export DEBUILD_LINTIAN=no
> > but it still uses lintian.
> >
>
> If you've added that to your shell, or a file like .profile, then
> that's not particularly surprising, given that the same manpage also
> says that DEBUILD_LINTIAN is a configuration variable, which is read
> from one of two files, and "[e]nvironment variable settings are ignored
> when these configuration files are read". (In common with almost every
> variable any script in devscripts uses.)

/etc/devscripts.conf says "This file is sourced by /bin/bash ...",
however, as you says, there is that note in debuild man page.

Thanks for the quick reply, I suppose we could close this issue.

Bug#1053241: glibc: please apply upstream patch to fix slow fstat

[Fabio Pedretti]

Il giorno dom 26 nov 2023 alle ore 16:28 Aurelien Jarno
 ha scritto:
>
> Hi,
>
> On 2023-09-29 21:52, Fabio Pedretti wrote:
> > Package: glibc
> > Version: 2.36-9+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Dear Maintainer,
> >
> > glibc uses a slow version of fstat. Details are documented
> > here: https://lwn.net/Articles/944214/
> >
> > A patch to fix this was merged in glibc:
> > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f
> >
> > The patch applies cleanly and builds fine also on bookworm glibc.
> > Please consider apply it to fix slow fstat.
>
> This patch changes the syscall used by binaries, so it has to be
> considered with a lot of care in a stable release, it could break
> existing seccomp filters. In any case it has to live a few months in
> testing/unstable first.
>
> Note that the kernel patch that improves the performance of fstatat, has
> not been merge to the upstream stable tree, nor to bookworm.
>
> In order to better understand the need for this patch in bookworm, could
> you please give some details about your workload and the performance
> impact it has?

I did some test with my use case, borg backup with many unchanged
files, see https://github.com/borgbackup/borg/issues/4498 for some
background and system calls impact, where borg 1.2 slow downs a lot
vs. borg 1.1.

I checked using strace the patch, it did the job (newfstatat calls
were replaced with fstat), and I'd hoped that it would improve
performance, however my use case improved just marginally (difficult
to have reproducible data in my case, but it was like 5%).

I didn't notice any other regression, however.

I see the glibc patch is still only on 2.39, while even Debian
experimental has just 2.38.

The alternative kernel patch is in 6.6 (as you say, still not in Debian).

Given all of this, I agree we can wait to land it on trixie and leave
bookworm as is, so feel free to just close the issue in this case.

Thanks for your time.

Bug#1056906: debuild: cannot disable lintian

[Fabio Pedretti]

Package: devscripts
Version: 2.23.6
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

when I add --no-lintian (as found in debuild man page) option
to debuild, I get the following error:

...
 dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian
dpkg-buildpackage: error: unknown option or argument --no-lintian

Use --help for program usage information.
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian failed
...

I also tried setting:
export DEBUILD_LINTIAN=no
but it still uses lintian.

Bug#1053241: glibc: please apply upstream patch to fix slow fstat

[Fabio Pedretti]

Package: glibc
Version: 2.36-9+deb12u1
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

glibc uses a slow version of fstat. Details are documented
here: https://lwn.net/Articles/944214/

A patch to fix this was merged in glibc:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f

The patch applies cleanly and builds fine also on bookworm glibc.
Please consider apply it to fix slow fstat.

Thanks.

Bug#1052453: rust-bindgen-cli: Build error: Unknown section 'FIXME-IN-THE-SOURCE-SECTION'

[Fabio Pedretti]

Package: rust-bindgen-cli
Version: 0.66.1-3
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

trying to build the package on Ubuntu, the package get rejected with
this error:

Unknown section 'FIXME-IN-THE-SOURCE-SECTION'

Thanks.

Bug#1050664: firehol: please install contrib/ipset-apply.sh into firehol-tools

[Fabio Pedretti]

Package: firehol
Version: 3.1.7+ds-2.1
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

firehol source package has 2 tools in the contrib dir: dnsbl-ipset.sh
and ipset-apply.sh.
The latter however is not installed. Please install also ipset-apply.sh
since it is a useful tool.

Thanks.

Bug#943865: src:mesa: Please build Mesa SWR rasterizer on amd64 and i386

[Fabio Pedretti]

block 943865 with 1006202
thanks

SWR was removed from mesa, but it is still available in mesa-amber

Bug#1041243: mesa: please remove control file, as control.in is present

[Fabio Pedretti]

Il Mar 25 Lug 2023, 09:54 Timo Aaltonen  ha scritto:

> On 16.7.2023 15.30, Fabio Pedretti wrote:
> > Source: mesa
> > Version: 22.3.6-1+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Please remove control file in git, since there is already control.in,
> and
> > control is automatically generated during build.
>
> regeneration doesn't work when d/control is removed
>

Mmm, I didn't tryed, but there are other .in files (libglx-mesa0.links.in
and libosmesa6.links.in) without the generated file... maybe control is
special.

>

Bug#1009027: mesa: Please enable these new drivers and features available since mesa 22

[Fabio Pedretti]

> There is also the VULKAN_DRIVERS virtio-experimental , I don't know
> however if it's ready for use (archlinux ships it
> https://bbs.archlinux.org/viewtopic.php?id=265471 ).

Since 23.2 virtio-experimental was renamed upstream to virtio and is
no longer considered experimental:
https://cgit.freedesktop.org/mesa/mesa/commit?id=7d76038712ea099424e906d8a4c19ad5c932f7e3
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bdc82f52d7d16b05a9922534be00fba39e3a1c5b

Bug#1041243: mesa: please remove control file, as control.in is present

[Fabio Pedretti]

Source: mesa
Version: 22.3.6-1+deb12u1
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Please remove control file in git, since there is already control.in, and
control is automatically generated during build.

Bug#1036970: 0ad: third party library (mbedtls) needs to be updated

[Fabio Pedretti]

forwarded 1036970 https://trac.wildfiregames.com/ticket/6816
thanks

Bug#1032851: mesa: FTBFS in dirty env if clang-14 is installed

[Fabio Pedretti]

On ubuntu jammy it breaks even with clang-15 installed, if
libclang1-14 is also installed, see:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8470

Bug#919234: ttls fails with tls 1.3, enabled by default

[Fabio PEDRETTI]

Hi, 3.2.1 currently in testing fixed most issues, however there is
still an issue preventing freeradius working with TLS 1.3.

The issue was reported upstream at:
https://github.com/FreeRADIUS/freeradius-server/issues/4878
and the commit fixing it is:
https://github.com/FreeRADIUS/freeradius-server/commit/0812bc1768cedc420adc03e86893d798fa19e872

That commit is already included in upstream 3.2.2.

So please consider upgrading to 3.2.2 (suggested, given this release
also fixes some other bugs), or apply the mentioned commit.

I updated the severity and forwarded bug reflecting this.

Thanks!

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 

Bug#919234:

[Fabio PEDRETTI]

-- 
ing. Fabio Pedretti
Responsabile U.O.C. "Reti e Sicurezza Informatica"
Università degli Studi di Brescia
Via Valotti, 9 - 25121 Brescia
E-mail: fabio.pedre...@unibs.it

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 
<https://www.unibs.it/it/node/1452>

Bug#1027867: Unable to run X server since 22.3.1-1 upgrade

[Fabio Pedretti]

Since this also happens of Fedora, I think it's best to add every
additional info on the upstream report
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007 , also click on
the "thumbs up".

Il giorno sab 28 gen 2023 alle ore 13:38 наб
 ha scritto:
>
> On Wed, Jan 18, 2023 at 10:25:38AM +0100, Fabio Pedretti wrote:
> > Can you check with 22.3.3-1 (now in testing) or 23.0.0~rc1-1 (in
> > experimental) if the issue is fixed or still not?
>
> Same error with 23.0.0~rc1-1; log below.

Bug#1027867: Bug#1028439: Unable to run X server since 22.3.1-1 upgrade

[Fabio Pedretti]

Can you also check with 23.0.0~rc1-1 in experimental?

Il giorno mer 18 gen 2023 alle ore 16:48 Cédric Nisio
 ha scritto:
>
> As I answered on gitlab I tried 22.3.3-1 with the same backtrace & error logs.
> I rolled back to 22.2.4-1.
>
> Happy to help if I can.

Bug#1027867: Unable to run X server since 22.3.1-1 upgrade

[Fabio Pedretti]

Can you check with 22.3.3-1 (now in testing) or 23.0.0~rc1-1 (in
experimental) if the issue is fixed or still not?

Bug#1027791: Unable to run X server since 22.3.1-1 upgrade

[Fabio Pedretti]

Can you try with 22.3.3-1 (currently in unstable) or 23.0.0~rc1-1 (in
experimental) if the issue is fixed or still not?

Bug#1028266: libegl-mesa0: terminology segfaults after ugprade to 22.3.2-1

[Fabio Pedretti]

Can you update to packaged 22.3.3-1 and confirm if it's fixed now?

Il giorno mar 10 gen 2023 alle ore 10:49 Fabio Pedretti
 ha scritto:
>
> Nice, that patch is already in the 22.3 branch, and 22.3.3 should be
> released in a few days.
>
> Il giorno mar 10 gen 2023 alle ore 07:32 Ross Vandegrift
>  ha scritto:
> > I think this is the issue:
> >   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7949
> > And the fix is in this MR:
> >   https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20479/diffs
> >
> > The diff applies to the version in unstable.  I ran into some challenges 
> > trying
> > to test, but will try again another day.

Bug#1025297: Fixed in 22.3.2-1

[Fabio Pedretti]

Version: 22.3.2-1

Il giorno sab 7 gen 2023 alle ore 16:12 Sylvain Archenault
 ha scritto:
>
> After upgrading to 22.3.2-1 - issue seems resolved for me.

Bug#1028266: libegl-mesa0: terminology segfaults after ugprade to 22.3.2-1

[Fabio Pedretti]

Nice, that patch is already in the 22.3 branch, and 22.3.3 should be
released in a few days.

Il giorno mar 10 gen 2023 alle ore 07:32 Ross Vandegrift
 ha scritto:
> I think this is the issue:
>   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7949
> And the fix is in this MR:
>   https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20479/diffs
>
> The diff applies to the version in unstable.  I ran into some challenges 
> trying
> to test, but will try again another day.

Bug#1028362: xserver-xorg: Please add a Recommends on mesa-vulkan-drivers, along libgl1-mesa-dri

[Fabio Pedretti]

Package: xserver-xorg
Version: 1:7.7+23
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

xserver-xorg properly Recommends libgl1-mesa-dri, with OpenGL mesa
drivers, however it doesn't Recommends mesa-vulkan-drivers, with
Vulkan mesa drivers.

This way when using some Debian packaged apps or games (optionally)
supporting Vulkan, like warzone2100 >= 4.3.3-2 we are unable to use it
(when enabling Vulkan inside the game).

So, please add it, since Vulkan is becoming widely used in a desktop
environment.

Note: ubuntu is already doing this in its xserver-xorg package since
1:7.7+19ubuntu10 years ago, see also
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742714 .

Thanks.

Versions of packages xserver-xorg depends on:
pn  x11-xkb-utils   
ii  xkb-data2.35.1-1
pn  xserver-xorg-core   
pn  xserver-xorg-input-all | xorg-driver-input  
pn  xserver-xorg-video-all | xorg-driver-video  

Versions of packages xserver-xorg recommends:
ii  libgl1-mesa-dri  22.3.2-1
pn  xserver-xorg-legacy  

xserver-xorg suggests no packages.

Bug#1028266: libegl-mesa0: terminology segfaults after ugprade to 22.3.2-1

[Fabio Pedretti]

Can you check if a similar issue is already reported at
https://gitlab.freedesktop.org/mesa/mesa/-/issues and eventually open
a new issue there?

Il giorno lun 9 gen 2023 alle ore 00:09 Ross Vandegrift
 ha scritto:
> After upgrading to mesa 22.3.2-1, terminology (a terminal emulater, package 
> has
> the same name) began randomly crashing.  Crashes were triggered by tab
> switching or window resizing.  Downgrading back to 22.2.4-1 fixes the issue.

Bug#1027650: warzone2100: FTBFS: urlrequest.cpp:535:42: error: ‘CURLOPT_PROTOCOLS’ is deprecated: since 7.85.0. Use CURLOPT_PROTOCOLS_STR [-Werror=deprecated-declarations]

[Fabio Pedretti]

tags 1027650 fixed-upstream

Fixed upstream in 4.3.3 with:
https://github.com/Warzone2100/warzone2100/commit/6016da0ba8c0a1b5963993d9f60c76c60bee7d48

Bug#765933: mesa-common-dev: glx.h should not include glxext.h when GL_GLEXT_LEGACY is defined

[Fabio Pedretti]

The upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=83631
was closed years ago.

Can the Debian bug also be closed now?

Bug#1020391: mesa: Updates to 22.2 RCs cause blank screen on some VirtIO graphics

[Fabio Pedretti]

So, is your issue still reproducible with 22.3.1-1?
If yes, is there a similar issue already reported at
https://gitlab.freedesktop.org/mesa/mesa/-/issues ?
If not, can you open a new report there?

Il giorno mer 4 gen 2023 alle ore 07:00 Ben Westover
 ha scritto:
> I don't see how that issue is related to mine. It supposedly only occurs

Bug#1027791: Unable to run X server since 22.3.1-1 upgrade

[Fabio Pedretti]

Hi, please open a new bug report here:
https://gitlab.freedesktop.org/mesa/mesa/-/issues

Bug#980388: apache2: please consider enabling http2 by default

[Fabio Pedretti]

Il giorno lun 18 gen 2021 alle ore 18:26 Xavier  ha scritto:
> Le 18/01/2021 à 18:01, Fabio Pedretti a écrit :
> > Package: apache2
> > Version: 2.4.46-4
> > Severity: wishlist
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Dear Maintainer,
> >
> > http2 module is available since some releases, please consider enabling
> > it by default.
> >
> > Thanks.
>
> Hi,
>
> there were a lot of issues in this module in the 3 last versions, I
> propose to differ this change after Bullseye release to minimize
> potential security problems.
>
> Cheers,
> Xavier

Hi, can you consider enabling it now for bookworm?
Thanks.

Bug#1020391: mesa: Updates to 22.2 RCs cause blank screen on some VirtIO graphics

[Fabio Pedretti]

You don't provide many details, but at a quick search your issue may
be this one:
https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655

Which is fixed in the version 22.3.1-1 currently in Debian testing / unstable.

Ben, can you check and report back?

Bug#415292: libgl1-mesa-glx: assertion failure in libGL.so.1

[Fabio Pedretti]

forwarded 415292 https://gitlab.freedesktop.org/mesa/mesa/-/issues/49
thanks

Il giorno lun 2 gen 2023 alle ore 19:03 G. Branden Robinson
 ha scritto:
>
> At 2023-01-02T18:54:02+0100, Fabio Pedretti wrote:
> > upstream bug report was closed with:
> > "This code has been rewritten since and almost certainly fixed,
> > closing."
>
> Jesus.  I'd never trust a claim like that without output from a formal
> verification suite to confirm it.
>
> I think we may have a brogrammer at play.

Well, this Debian bug report is over 15 years old. :)

Il giorno lun 2 gen 2023 alle ore 19:03 G. Branden Robinson
 ha scritto:
>
> At 2023-01-02T18:54:02+0100, Fabio Pedretti wrote:
> > upstream bug report was closed with:
> > "This code has been rewritten since and almost certainly fixed,
> > closing."
>
> Jesus.  I'd never trust a claim like that without output from a formal
> verification suite to confirm it.
>
> I think we may have a brogrammer at play.
>
> Regards,
> Branden

Bug#415292: libgl1-mesa-glx: assertion failure in libGL.so.1

[Fabio Pedretti]

Hi Nikita,

upstream bug report was closed with:
"This code has been rewritten since and almost certainly fixed, closing."

Can you try with a recent Debian system and report back?

Thanks.

Bug#1019984: libglx-mesa0: GL_VERSION update

[Fabio Pedretti]

Hi Alexandre,

Can you try again with mesa 22.3.1-1, which is in testing now, and
report back if the issue is fixed?

Thanks.

Bug#1025213: gnome-shell: Flickering and mangled screens on wayland if dri driver not available

[Fabio Pedretti]

Hi Gert and others,

mesa Debian package 22.3.0-3 added again i915 gallium driver.

Can you try again with mesa 22.3.1-1, which is in testing now, and report back?

Thanks.

Bug#1027722: warzone2100: Please upgrade to 4.3.3 and enable Vulkan API (adding libshaderc-dev dep)

[Fabio Pedretti]

Source: warzone2100
Version: 4.2.7-2
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

version 4.3.3 of warzone2100 was released, please update the package
(currently in Debian there is 4.2.7).

Also, shaderc source package is now in Debian. Please add libshaderc-dev
as a build dependency, so that Vulkan API can be enabled. Actually
libvulkan-dev is already a dependency, but it is not enough to enable
Vulkan. Indeed, in the current package build log:

-- Detected Vulkan headers (VK_HEADER_VERSION: 216): /usr/include
-- Found VulkanHeaders: /usr/include (found suitable version "216", minimum 
required is "148") 
-- GLSLC shader compiler not found - disabling Vulkan backend

Bug#1027647: libgl1-mesa-dri: Crash when using basic application like "git gui"

[Fabio Pedretti]

Hi, it looks you are using Debian testing, can you please update mesa
packages (you should get 22.3.1-1) and report back if the issue is
fixed?
Thanks.

Bug#1020421: If I start some programs (i.e. gimp), system gets me out of the session and show me login again

[Fabio Pedretti]

Hi, since mesa 22.3.0-3 the i915 gallium drives is enabled again in
mesa, no need to install amber package.
It looks you are using testing or unstable, can you please update mesa
packages and report if the issue is fixed?
Thanks.

Bug#761163: libgl1-mesa-dri: DRI3 causes error messages on i915 driver

[Fabio Pedretti]

Are you still able to reproduce this on a newer Debian system?

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

[Fabio Pedretti]

Hi, i965 driver was removed, and replaced by iris, crocus and (gallium
version of) i915.

Did you have any reference to i965 in your configuration?

cd /etc/ && grep -ri i965

If so try to remove them, the system should be able to pick up the
proper driver.

Il giorno dom 1 gen 2023 alle ore 23:47 Eduard Bloch  ha scritto:
>
> So was THAT supposed to replace i965 support in mesa-22?

Bug#861923:

[Fabio Pedretti]

The entry in the changelog tells a different bug (_9_61923), please correct
it in the next upload.
Thanks

Bug#1025659: libgl1-mesa-dri: mesa causes xorg segfault; regression against 22.2.0-1

[Fabio Pedretti]

Is this still an issue with 22.3.1-1?

Bug#1025389:

[Fabio Pedretti]

@Felix

There is i915g gallium driver in mesa, that replaced old classic
unmantained and removed upstream i915, but i915g is currently not enabled
in Debian mesa package.

Bug#1012129:

[Fabio Pedretti]

This is fixed also in the dco branch now:
https://github.com/OpenVPN/openvpn/commits/dco?after=63409150834208582031876dab70beefa2ee48f6+34=dco_name=refs%2Fheads%2Fdco

Bug#1012358: apache2: apache on Debian is several times slower than on other distros, according to Phoronix

[Fabio Pedretti]

Related Ubuntu bug:
https://bugs.launchpad.net/debian/+source/apache2/+bug/1977687

Bug#1012358: apache2: apache on Debian is several times slower than on other distros, according to Phoronix

[Fabio Pedretti]

Package: apache2
Severity: normal
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

according to this recent Phoronix test apache on Debian is several times
slower than on other distros:
https://www.phoronix.com/scan.php?page=article=h1-2022-linux=7

It is not entirely clear how the test was performed, and given the test
says version is 2.4.48 it may be using a custom build apache version and
not the Debian package.

Also it may be an issue not strictly related to apache, since that test
shows that other tests are also a lot slower on Debian.

Nonetheless, given that apache is a common work usage on Debian, I
report this issue in case someone has interest in checking what's going
on.

Thanks.

Bug#1011041:

[Fabio PEDRETTI]

It should be fixed in upstream 3.2.0, which is the release just after
3.0.25.

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 

Bug#1009027: mesa: Please enable these new drivers and features available since mesa 22

[Fabio Pedretti]

>> GALLIUM_DRIVERS
>> - asahi (driver for Apple M1)
>
> I'm assuming this is for arm64?

I think so.

>> - i915 (new i915 gallium driver, replaces old i915 classic driver)
>
> If both i915g and i915 classic (from mesa-amber) are installed, which
> one is used?

They have the same path / filename, so it won't be a problem. I'd
suggest to ship the gallium version in mesa rather than the old
classic in amber. I enabled it in my PPA (
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/ ) and
got positive feedback.

Eventually the amber version could be compiled and shipped renamed, so
the packages won't conflicts and the user could change the driver
setting MESA_LOADER_DRIVER_OVERRIDE variable.


There is also the VULKAN_DRIVERS virtio-experimental , I don't know
however if it's ready for use (archlinux ships it
https://bbs.archlinux.org/viewtopic.php?id=265471 ).

Bug#1009027: mesa: Please enable these new drivers and features available since mesa 22

[Fabio Pedretti]

Source: mesa
Version: 22.0.1-2
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

please consider enablig the following new drivers and features available
since mesa 22:

GALLIUM_DRIVERS
- asahi (driver for Apple M1)
- i915 (new i915 gallium driver, replaces old i915 classic driver)

VULKAN_DRIVERS
- panfrost (there is already a gallium driver for this)

confflags_VULKAN
- intel-nullhw (this layer disables all rendering & compute commands in the
command parsing HW. It can be useful to identify CPU bottlenecks.)

Thanks.

Bug#973922: New upstream (2.19)

[Fabio PEDRETTI]

Any news on upgrading radvd in Debian to latest 2.19?
Thanks.


Il giorno gio 7 gen 2021 alle ore 20:57 Geert Stappers
 ha scritto:
>
> On Thu, Jan 07, 2021 at 08:19:21PM +0100, Geert Stappers wrote:
> > On Thu, Jan 07, 2021 at 07:00:42PM +0100, Fabio Pedretti wrote:
> > > 2.18 was uploaded to Debian
> > > while 2.19 is already available upstream?
> >
> > Something between  yes and no.
> >
> >
> > The 2.19 version lacks a signature from upstream.
> > 2.18 has a signature from upstream.
> >
> > In other words: radvd 2.18 is complete in Debian,
> > v2.19 of radvd waits on signature from upstream ...
>
> At https://github.com/reubenhwk/radvd/issues/129#issuecomment-728848196
> is expressed what we are waiting on.
>
>
> Regards
> Geert Stappers
> Maintainer of radvd in Debian
> --
> Silence is hard to parse

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 
<https://www.unibs.it/it/node/1452>

Bug#1000917: Please remove from Debian sid and experimental

[Fabio Pedretti]

Hi, libclc was merged into upstream llvm and is provided by
llvm-toolchain-XX Debian packages (since llvm-toolchain-12 1:12.0.0-3).

libclc Debian source package should be removed from sid and experimental
(already removed from bookworm).

Thanks.

Bug#890472: warzone2100 needing glslc

[Fabio Pedretti]

warzone2100 fails to enable Vulkan backend due to missing glslc:

-- GLSLC shader compiler not found - disabling Vulkan backend

https://buildd.debian.org/status/fetch.php?pkg=warzone2100=all=4.2.1-2=1637664767=0

Thanks

Bug#980559: angelscript: FTBFS on arm64: test error

[Fabio Pedretti]

angelscript 2.35.1 was released and has at least 2 arm64 fixes:
https://www.angelcode.com/angelscript/changes.php

Can you try upgrading Debian angelscript package to 2.35.1 and see if
this fixes arm64 build?

Note that angelscript with arm64 build is needed by supertuxkart, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995771

Thanks.

Bug#995771: supertuxkart: Please depends on angelscript-dev

[Fabio Pedretti]

Source: supertuxkart
Version: 1.3+dfsg1-1
Severity: normal

Dear Maintainer,

supertuxkart fails to build on armhf on Ubuntu impish: 
https://github.com/supertuxkart/stk-code/issues/4638

As said in that issue supertuxkart could use angelscript-dev if
available, and that would also avoid the build issue in the embedded
angelscript.

So, please add angelscript-dev as a build dependency.

Thanks.

Bug#992017: Alpha 25 packaging

[Fabio Pedretti]

Hi and thank you for working on this!
Before pushing the new release please consider the following:
1) 0ad 0.0.25b (aka Re-release of 0 A.D. Alpha 25) was just released
with some urgent fixes:
https://play0ad.com/re-release-of-0-a-d-alpha-25-yauna/ , please use
this rather than plani 0.0.25
2) lower icu dependency to at least 66.1-2~ : I built it this way and
it works flawlessly (I have a PPA here:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/+packages).
This would make backporting to Ubuntu 20.04 easier
Thanks!

Bug#785487: supertuxkart: Crash when loading 'Solo' or 'History' screens

[Fabio Pedretti]

Hi Fabien,
are you still able to reproduce this issue?

Bug#992170: 0ad: lzma error: compressed data is corrupt

[Fabio Pedretti]

Can you check if you have enough free space on your drive?

Il giorno sab 14 ago 2021 alle ore 22:06 Robbi Nespu 
ha scritto:

> Package: 0ad
> Version: 0.0.23.1-5+b1
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
> Failed to install
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  $ sudo apt-get install 0ad
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following additional packages will be installed:
>   0ad-data
> The following NEW packages will be installed:
>   0ad 0ad-data
> 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
> Need to get 707 MB of archives.
> After this operation, 2,114 MB of additional disk space will
> be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ftp.jp.debian.org/debian bullseye/main amd64
> 0ad-data all 0.0.23.1-1.1 [702 MB]
> Get:2 http://ftp.jp.debian.org/debian bullseye/main amd64 0ad
> amd64 0.0.23.1-5+b1 [5,589 kB]
> Fetched 707 MB in 13min 49s (853 kB/s)
> (Reading database ... 541240 files and directories currently
> installed.)
> Preparing to unpack .../0ad-data_0.0.23.1-1.1_all.deb ...
> Unpacking 0ad-data (0.0.23.1-1.1) ...
> dpkg-deb (subprocess): decompressing archive
> '/var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb' (size=701833824)
> member 'data.tar': lzma error: compressed data is corrupt
> dpkg-deb: error:  subprocess returned error exit
> status 2
> dpkg: error processing archive
> /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb (--unpack):
>  cannot copy extracted data for
> './usr/share/games/0ad/mods/public/public.zip' to
> '/usr/share/games/0ad/mods/public/public.zip.dpkg-new': unexpected end of
> file or stream
> Selecting previously unselected package 0ad.
> Preparing to unpack .../0ad_0.0.23.1-5+b1_amd64.deb ...
> Unpacking 0ad (0.0.23.1-5+b1) ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> $ md5sum /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb
> 2688ba115bc50916975827a9f57052bd
> /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb
>
>
>* What was the outcome of this action?
> Fail corupted
>
>* What outcome did you expect instead?
>0ad should be install without any file corruption
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: 11.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages 0ad depends on:
> pn  0ad-data   
> ii  0ad-data-common0.0.23.1-1.1
> ii  dpkg   1.20.9
> ii  libboost-filesystem1.74.0  1.74.0-9
> ii  libc6  2.31-13
> ii  libcurl3-gnutls7.74.0-1.3+b1
> ii  libenet7   1.3.13+ds-1
> ii  libgcc-s1  10.2.1-6
> ii  libgl1 1.3.2-1
> ii  libgloox18 1.0.24-2
> ii  libicu67   67.1-7
> ii  libminiupnpc17 2.2.1-1
> ii  libnspr4   2:4.29-1
> ii  libnvtt2   2.0.8-1+dfsg-8.2+b1
> ii  libopenal1 1:1.19.1-2
> ii  libpng16-161.6.37-3
> ii  libsdl2-2.0-0  2.0.14+dfsg2-3
> ii  libsodium231.0.18-1
> ii  libstdc++6 10.2.1-6
> ii  libvorbisfile3 1.3.7-1
> ii  libwxbase3.0-0v5   3.0.5.1+dfsg-2
> ii  libwxgtk3.0-gtk3-0v5   3.0.5.1+dfsg-2
> ii  libx11-6   2:1.7.2-1
> ii  libxcursor11:1.2.0-2
> ii  libxml22.9.10+dfsg-6.7
> ii  zlib1g 1:1.2.11.dfsg-2
>
> 0ad recommends no packages.
>
> 0ad suggests no packages.
>
> -- debconf-show failed
>
>

Bug#968614:

[Fabio Pedretti]

Waqar, are you still able to reproduce this issue with current version
in bullseye, 1.8.7-1?

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#947689:

[Fabio Pedretti]

tags 947689 fixed-upstream

This issue should be fixed in this upstream commit:
https://git.netfilter.org/iptables/commit/?id=5f1fcacebf9b4529950b6e3f88327049a0ea7cd2

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#763982:

[Fabio Pedretti]

Currently both zlib and Intel zlib are no longer actively developed,
however there is zlib-ng with optimization for many architectures:
https://github.com/zlib-ng/zlib-ng

Bug#599884: speed-dreams

[Fabio Pedretti]

I uploaded the package in my Ubuntu PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/+packages?field.name_filter=speed-dreams

Note that non amd64 builds fail with:
/<>/src/modules/graphic/osggraph/Utils/OsgAtomic.h:51:4:
error: #error
   51 | #  error
  |^

Bug#599884: speed-dreams

[Fabio Pedretti]

This game is a definitive improvement over its predecessor torcs!
It would be nice to have it in Debian (11?). :)

I attach a simple patch to fix the build on Debian testing. Changes:
* fix openscenegraph dependency
* order dependency by name and put each one on a new line

With the patch the game builds and runs fine.
Please consider applying.
diff --git a/debian/control b/debian/control
index 690481e..a295334 100644
--- a/debian/control
+++ b/debian/control
@@ -3,13 +3,32 @@ Section: games
 Priority: optional
 Maintainer: Debian Games Team 
 Uploaders: Gürkan Myczko 
-Build-Depends: debhelper (>= 11), libplib-dev, libsdl2-dev, libogg-dev, cmake, libopenscenegraph-3.4-dev, libexpat1-dev, libopenal-dev, libenet-dev, libpng-dev, libjpeg-dev, libxmu-dev, libvorbis-dev, libcurl4-gnutls-dev
+Build-Depends:
+ debhelper (>= 11),
+ cmake,
+ libcurl4-gnutls-dev,
+ libenet-dev,
+ libexpat1-dev,
+ libjpeg-dev,
+ libogg-dev,
+ libopenal-dev,
+ libopenscenegraph-dev (>= 3.4),
+ libplib-dev,
+ libpng-dev,
+ libsdl2-dev,
+ libvorbis-dev,
+ libxmu-dev
 Standards-Version: 4.3.0
 Homepage: https://www.speed-dreams.org/
 
 Package: speed-dreams
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, speed-dreams-data, ttf-bitstream-vera, symlinks
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+ speed-dreams-data,
+ symlinks,
+ ttf-bitstream-vera
 Description: Open source motorsport simulation
  This is a 3d cross-platform, open source motorsport simulation and racing
  game. It is a fork of the open racing car simulator Torcs, aiming to implement
@@ -19,7 +38,8 @@ Description: Open source motorsport simulation
 
 Package: speed-dreams-data
 Architecture: all
-Depends: ${misc:Depends}
+Depends:
+ ${misc:Depends}
 Description: Open source motorsport simulation, data files
  This is a 3d cross-platform, open source motorsport simulation and racing
  game. It is a fork of the open racing car simulator Torcs, aiming to implement

Bug#643775:

[Fabio Pedretti]

php-xcache is no longer in Debian.
Closing.

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#980388: apache2: please consider enabling http2 by default

[Fabio Pedretti]

Package: apache2
Version: 2.4.46-4
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

http2 module is available since some releases, please consider enabling
it by default.

Thanks.

Bug#979591: llvm-toolchain-11: Please enable libclc

[Fabio Pedretti]

Source: llvm-toolchain-11
Version: 1:11.0.1-2
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Debian has the libclc source package, but it looks like it is no longer
available upstream.
Actually the web page https://libclc.llvm.org/ points to a dead git
repository.

The mirror repo at https://github.com/llvm-mirror/libclc says:
Mirror kept for legacy. Moved to https://github.com/llvm/llvm-project

Indeed what was inside libclc git repo it is now inside
llvm-toolchain-11 package (see 
https://sources.debian.org/src/llvm-toolchain-11/1:11.0.1-2/libclc/)
and it also has some additional fixes.

So it would be nice to build updated libclc from llvm-toolchain-11 and
then remove the obsolete libclc source package from Debian.

Thanks

Bug#974586:

[Fabio Pedretti]

According to upstream changelog:
https://github.com/rsyslog/loganalyzer/blob/master/ChangeLog
multiple php 7.x issues are also fixed in 4.1.7 and 4.1.8.

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956621

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#973922: New upstream (2.19)

[Fabio Pedretti]

2.18 was uploaded to Debian while 2.19 is already available upstream?

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#979515:

[Fabio Pedretti]

Note the first patch (removal of libxdamage-dev dependency) should not be
applied to 20.3 series, but just to the 21 series.

Bug#979515: mesa: A couple of cleanup for mesa

[Fabio Pedretti]

Source: mesa
Version: 20.3.2-1
Severity: normal
Tags: patch
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,
please apply the following patches to cleanup build process:

libxdamage-dev dependency is no longer need since:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=94a9867b0569c6f6d65b27f69b678f7f1785f3ad

diff -purN debian-hirsute-orig/control debian-hirsute/control
--- debian-hirsute-orig/control 2021-01-07 14:40:01.753039182 +0100
+++ debian-hirsute/control  2021-01-07 15:11:10.795224886 +0100
@@ -16,7 +17,6 @@ Build-Depends:
  libexpat1-dev,
  libsensors-dev [!hurd-any],
  libxfixes-dev,
- libxdamage-dev,
  libxext-dev,
  libva-dev (>= 1.6.0) [linux-any kfreebsd-any] ,
  libvdpau-dev (>= 1.1.1) [linux-any kfreebsd-any],


use enabled rather than true, as done elsewhere

diff -purN debian-hirsute-orig/rules debian-hirsute/rules
--- debian-hirsute-orig/rules   2021-01-07 14:40:01.761039224 +0100
+++ debian-hirsute/rules2021-01-07 15:14:25.552308206 +0100
@@ -59,7 +77,7 @@ else
   endif
 
   ifeq ($(DEB_HOST_ARCH_OS), linux)
-   confflags_DRI3 = -Ddri3=true
+   confflags_DRI3 = -Ddri3=enabled
DRI_DRIVERS += nouveau
# Gallium drivers which require kernel support, not yet ported to 
non-Linux
GALLIUM_DRIVERS += nouveau virgl

Bug#975729: isc-dhcp: Please upgrade to latest upstream release 4.4.2

[Fabio Pedretti]

Source: isc-dhcp
Version: 4.4.1-2.1
Severity: wishlist
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

please upgrade to latest upstream release 4.4.2, which fixes some issues
and add some minor features. Release notes:
https://downloads.isc.org/isc/dhcp/4.4.2/dhcp-4.4.2-RELNOTES

Thanks.

Bug#838055: 0ad: Embedded libsquish library now available in debian

[Fabio Pedretti]

Hi, I closed this issue years ago because actually 0ad doesn't use the
squish library which is in the 0ad source.

It's a problem strictly related to the nvidia-texture-tools package.
Actually 0ad source could also be repackaged to remove squish and nvtt
directory, which are not used. Since there is already bug #838056 for
nvidia-texture-tools there is nothing to be done here and this one
could actually be closed. But I'll leave that up to you.

Related:
https://github.com/castano/nvidia-texture-tools/pull/244

Bug#968938: nvidia-texture-tools: Please update to 2.1.2

[Fabio Pedretti]

Source: nvidia-texture-tools
Version: 2.0.8-1+dfsg-8.2
Severity: important
X-Debbugs-Cc: pedretti.fa...@gmail.com

Dear Maintainer,

nvidia-texture-tools is used by the 0ad Debian package. SVN version of
0ad includes version 2.1.1:
https://trac.wildfiregames.com/changeset/23305

and requires at least nvidia-texture-tools version 2.1 to build:
https://trac.wildfiregames.com/changeset/23974

So please consider updating nvidia-texture-tools to latest upstrem
version 2.1.2, so that the package can be used to build SVN and
future releases of 0ad.

Thanks.

Bug#967118: 0ad: Unversioned Python removal in sid/bullseye

[Fabio Pedretti]

I think this issue is still not properly closed.
The package removal reported in the first mail includes
python-minimal, which has the /usr/bin/python executable.
This is still used by libraries/source/cxxtest-4.4/bin/cxxtestgen file.
Indeed Ubuntu also has this patch.

diff -pruN 0.0.23.1-4/debian/patches/python2.patch
0.0.23.1-4ubuntu5/debian/patches/python2.patch
--- 0.0.23.1-4/debian/patches/python2.patch1970-01-01
00:00:00.0 +
+++ 0.0.23.1-4ubuntu5/debian/patches/python2.patch2020-02-06
12:02:59.0 +
@@ -0,0 +1,12 @@
+Description: Update cxxtestgen shebang.
+Author: Dimitri John Ledkov 
+
+
+--- 0ad-0.0.23.1.orig/libraries/source/cxxtest-4.4/bin/cxxtestgen
 0ad-0.0.23.1/libraries/source/cxxtest-4.4/bin/cxxtestgen
+@@ -1,4 +1,4 @@
+-#! /usr/bin/env python
++#! /usr/bin/env python2
+ #
+ # The CxxTest driver script, which uses the cxxtest Python package.
+ #

Bug#705592:

[Fabio Pedretti]

The game now requires premake5, which is not packaged in Debian.
The current 0ad version in Debian includes premake4 and premake5, but
actually uses premake5 during build.
The SVN version removes premake4 altogether.
I think this bug can be closed.

Bug#794562: nvtt 2.1 now required

[Fabio Pedretti]

SVN version of 0ad now includes nvtt 2.1.1:
https://trac.wildfiregames.com/changeset/23305

And also require a new version to properly build:
https://trac.wildfiregames.com/changeset/23974

Bug#964014:

[Fabio Pedretti]

Given the many bugs of the default -nft alternative, maybe the best option
for buster would be to revert to using the -legacy version.

Bug#932899: Fixed upstream

[Fabio Pedretti]

For reference the patch was committed in:
http://git.netfilter.org/iptables/commit/?id=26ec09bf6b9b674a7e3a65fc9c12599bd81dfe0f
And will be included in the release after 1.8.5.

Il lun 3 ago 2020, 14:33 Oldřich Jedlička  ha scritto:

> Hi,
>
> this is fixed upstream now:
> https://bugzilla.netfilter.org/show_bug.cgi?id=1423
>
> Regards,
> Oldrich.
>

Bug#946996:

[Fabio Pedretti]

Do you still have this issue with updated iptables 1.8.5-2 in testing?
Thanks

-- 


Informativa sulla Privacy: http://www.unibs.it/node/8155 

Bug#961117:

[Fabio Pedretti]

I can confirm this issue in Debian 10.
But I also tried it in Debian testing (with iptables 1.8.5-2 and linux
5.6.14-2) and the counters properly increased.