Package: libgl1-mesa-dri
Version: 24.1.1-1
Severity: serious
Control: block -1 by 1067699
I just had to downgrade a bunch of packages from src:mesa to version
24.1.0-2, because the installation of libllvm18:i386 failed due to a
file conflict that has been present for a few months, see #1067699.
Package: elpa-magit
Version: 3.3.0+git20231219.1.c7ab6931-1
Severity: serious
After loading magit Emacs displayed the following message in the
*Warnings* buffer:
,
| Emergency (magit): Magit requires ‘transient’ >= 0.5.0,
| but due to bad defaults, Emacs’ package manager, refuses to
|
; for that bug to be fixed to do an upload without the pages.
Note that manpages-dev 6.7-2 has dropped the clashing files for the time
being. I do not think there is any need to hurry, so I am downgrading
the severity of this bug. Whenever the glibc-doc package in unstable
drops the manpages, we should file a bug against manpages-dev to include
them again.
Cheers,
Sven
Package: bsdgames
Version: 2.17-31
Severity: serious
Your package fails to configure in a fresh installation (but not when
upgrading from a previous version). This is what happens in a throwaway
chroot (unrelated lines stripped from apt/dpkg output):
,
| # apt install bsdgames
| Selecting
On 2024-04-01 19:02 +0200, Alejandro Colomar wrote:
> Hi Sven,
>
> On Mon, Apr 01, 2024 at 06:38:52PM +0200, Sven Joachim wrote:
>> Makes perfect sense, but at the moment it can only be uploaded to
>> experimental.
>>
>> > We're not in a freeze, so I
On 2024-04-01 18:00 +0200, Alejandro Colomar wrote:
> Hi Sven,
>
> On Mon, Apr 01, 2024 at 05:35:18PM +0200, Sven Joachim wrote:
>> Obviously the manpages-dev package should not have shipped these files
>> as long as there are in glibc-doc; this is tracked in #1068166.
>
n experimental and will remain there for
several weeks if not months. I think manpages-dev should drop these
files for now and re-include either when glibc 2.38 is in unstable or
when it is in testing.
There is also the problem that some derivatives (most notably Ubuntu)
are already shipping glibc 2.39 and will have to adjust Breaks/Replaces
versions in manpages-dev accordingly. Thoughts?
Cheers,
Sven
Control: tags -1 + patch
On 2024-04-01 06:41 +0200, Sven Joachim wrote:
> Control: notfound -1 6.05.01-1
> Control: found -1 6.7-1
>
> On 2024-04-01 06:17 +0200, Bas Couwenberg wrote:
>
>> Source: manpages
>> Version: 6.05.01-1
>> Severity: serious
>> Justi
uld include this manpage.
There is a script debian/check-conflicts in the manpages source package
which is supposed to detect such clashing files, but it is buggy because
it only scans the contents of amd64 packages, while glibc-doc is an
arch:all package.
Cheers,
Sven
owerpc buildds have an outdated
version of dpkg-dev installed, although a newer one has been available
for over a week. I could and maybe should add dpkg-dev (>= 1.22.6) to
Build-Depends, but that is one more thing that needs to be reverted when
#1066968 gets fixed.
Cheers,
Sven
On 2024-03-13 18:07 +0100, Sven Joachim wrote:
> Control: forwarded -1
> https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569
>
> On 2024-03-13 12:47 +0100, Lucas Nussbaum wrote:
>
>> Source: xserver-xorg-video-nouveau
>> Version: 1:1.
r. I am afraid it will take weeks or even months to fix this
bug.
On the other hand I could override dpkg by injecting
-Wno-error=implicit-function-declaration. Would that be acceptable?
Cheers,
Sven
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
(the latest stable
release), but fixed as of tack 1.09-20230201 (the latest development
snapshot).
@Thomas: since tack 1.09 is more than four years old and there has been
no new snapshot for over a year, how about releasing tack 1.10? This
bug will likely hit other distros as they upgrade to GCC 14.
Cheers,
Sven
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
On 2024-02-17 18:53 +0100, Sven Joachim wrote:
> Control: severity -1 grave
>
> On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote:
>
>> Package: libgl1-mesa-dri
>> Version: 24.0.1-1
>>
CPPFLAGS lets the build
succeed, but I have not tested the resulting binary package yet. See
commit d7ba24fb6e4f ("wfb: Fix missing init function decls behind
FB_ACCESS_WRAPPER") which noticed and fixed the missing function
declaration, but got reverted in commit ca13913aaf7e.
Cheers,
Sven
Control: tags -1 + patch
On 2024-03-07 18:49 +0100, Sven Joachim wrote:
> Package: wv
> Version: 1.2.9-6.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
> /usr/share/d
Package: wv
Version: 1.2.9-6.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
After renaming the libwv-1.2-4 library package to libwv-1.2-4t64, the
/usr/share/doc/wv symlink has become dangling.
,
| $ file /usr/share/doc/wv
| /usr/share/doc/wv: broken symbolic link to libwv
Control: tags -1 + patch
On 2024-03-05 11:47 +0100, Sven Joachim wrote:
> Package: perl-base
> Version: 5.38.2-3.1
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> On i386, perl-base provides perlapi-5.38.2t64 rather than
> perlapi-5.38.2. Thi
Package: perl-base
Version: 5.38.2-3.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
On i386, perl-base provides perlapi-5.38.2t64 rather than
perlapi-5.38.2. This makes tons of packages uninstallable or
unbuildable and is not what has been agreed upon in #1060246.
The reason
Error 2
>
> Given the time and the architectures failing, this is probably related
> to dpkg switching on -Werror=implicit-function-declaration on these
> architectures (see https://bugs.debian.org/1065371 and a good summary
> of a similar case in https://bugs.debian.org/1065431 against lintian).
Not really, these arches now default to a 64-bit time_t and therefore
you get the conflicting types (suseconds_t is a long int,
__suseconds64_t a long long int). This has nothing to do with implicit
function declarations.
Cheers,
Sven
Package: libuuid1
Version: 2.39.3-7
Severity: serious
The last upload renamed libuuid1t64 back to libuuid1, but because the
former has an unversioned Replaces: on the latter, it will not take the
library files back. Removing the libuuid1t64 package will therefore
silently lose the files.
It
Control: tags -1 + patch
On 2024-02-29 23:26 +0100, Sven Joachim wrote:
> Package: xdelta
> Version: 1.1.3-10.5
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek
>
>
> The xdelta package still depends on libxdelta2, rather than on
> libxdelta2t64 as it s
Package: xdelta
Version: 1.1.3-10.5
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek
The xdelta package still depends on libxdelta2, rather than on
libxdelta2t64 as it should.
The build log on m68k[1] shows that on this architecture libxdelta2t64
gained a dependency on libxdelta2
;safety, removals";
This does cause aptitude to hold apt back by default, rather than remove
libapt-pkg6.0. You can press 'n' at the prompt, the next solution
aptitude then suggests is to upgrade apt.
Cheers,
Sven
hclient, but left the old
configfile around.
While installing your test package I lost wifi connection, but I think
that was not from your package but from updating network-manager from
unstable at the same time (did dist-upgrade), which always breaks my
network.
c'ya
sven-haegar
--
Three may keep
Package: console-setup
Version: 1.225
Severity: grave
After the upgrade from 1.223, console-setup.service failed to start due
to a syntax error in the setupcon script:
,
| $ setupcon
| /usr/bin/setupcon: 1386: Syntax error: Missing '))'
`
It looks like dash does not like the construct
libvte9 (<< 1:0.28)
> +Breaks: libvte9t64 (<< 1:0.28)
This change (and the corresponding one in control.in) looks incorrect to
me. Old versions of the library package (in this case versions before
1:0.28) are not going to be renamed retroactively, so the Breaks should
be left alone.
Bug in your conversion script?
Cheers,
Sven
000 +
> +++ libcdk5-5.0.20180306/debian/libcdk5nc6t64.lintian-overrides
> 2024-01-31 20:15:03.0 +
> @@ -0,0 +1,2 @@
> +libcdk5nc6t64: package-name-doesnt-match-sonames libcdk5
> +libcdk5nc6t64: package-name-doesnt-match-sonames libcdk5nc6
This ad
Source: directfb
Version: 1.7.7-11.1~exp1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Sven Joachim , Michael Hudson-Doyle
, Steve Langasek
The experimental upload of directfb FTBFS on all architectures[1],
because debian/libdirectfb-1.7-7t64.install is supposed to be run by
dh-exec
his probably means that the
menu_choose() function needs some substantial changes. I have not
investigated further, if somebody cares about this package and the old
AP points it supports they will have to do the work.
Cheers,
Sven
lyzers/src/watch/CMakeFiles/watch.dir/nc_windows/header_window.cpp.o]
> Error 1
The attached patch fixes these errors and similar ones in
analyzers/src/watch/nc_windows/statistics_window.cpp. Note that
getmaxx(window) returns window->_maxx + 1, and similar for getmaxy().
Disclaimer: I have only te
id use of incomplete typedef ‘ITEM’ {aka ‘struct
> tagITEM’}
> 236 | menu_items[i]->userptr = conf_item; /* the xml conf */
> |^~
> make[3]: *** [Makefile:308: gui.o] Error 1
The attached patch fixes this, but I have only tested
}
> 180 | ex < getbegx(below->win))
> | ^~
> [more errors snipped]
I have not tested it myself, but these errors should be fixed in libgnt
2.14.4 which has been released upstream the other day. See
https://keep.imfreedom.org/libgnt/libgnt/rev/2da723f790d6, which
explicitly mentions this bug.
Cheers,
Sven
ssed
directly anymore. The remedy is rather simple: instead of
item->index, use item_index(item) to retrieve the index. See the
attached patch which can be added to the series file.
Disclaimer: I have only tested that the package builds, not if it works.
Cheers,
Sven
From 037e6dd
^~
`
The attached patch fixes them and lets the package build, but I have
not tested if it actually works.
Cheers,
Sven
Description: Fix build with opaque ncurses
Since ncurses patchlevel 20231021 the WINDOW structure is opaque, its
members cannot be
; ydpdict.c:856:27: error: invalid use of incomplete typedef ‘WINDOW’ {aka
> ‘struct _win_st’}
> 856 | event.x > (window->_begx + correct3) && event.x <
> (window->_begx + window->_maxx + correct4))
> | ^~
> ydpdict.c:940:53: note: in expansion of
^~
There are quite a few more instances of such errors across the source
code, the attached patch should fix all of them. The package builds and
from a cursory look appears to work, but it would be good if a potential
NMU'er reviews and tests the patch before uploading.
Cheers,
cury,stdscr->_curx-1);
> |^~
> bosh.c:454:34: error: invalid use of incomplete typedef ‘WINDOW’ {aka ‘struct
> _win_st’}
> 454 | move(stdscr->_cury,stdscr->_curx-1);
> | ^~
The attached patch fixes that, using the getcury(
42 | typedef struct _win_st WINDOW;
The attached patch, which can be added to the series file fixes, these
errors and two additional ones in src/linpac.cc, but I have only tested
that the package builds, not if it works. Note that getmaxx(win)
returns win->_maxx + 1, and similar for getmaxy.
tailsWin->_maxy - 2;
> |^~
The attached patch, which can be added to the series file, fixes these
errors, but I have only tested that the package builds, not if it works.
Note that getmaxx(win) returns win->_maxx + 1, and similar f
with ncurses 6.5 this option is enabled by default;
| older versions disable it by default.
`
While ncurses 6.5 has not been released yet, the change has already been
made in the patchlevel Debian is shipping. From the NEWS file:
,
| 20231021
| + change defaults for configure opaq
has not been released yet, the change has already been
made in the patchlevel Debian is shipping. From the NEWS file:
,
| 20231021
| + change defaults for configure opaque and widec options (prompted by
| discussion with Branden Robinson).
`
Cheers,
Sven (ncurses maintainer in
Package: rust-urlshortener
Version: 3.0.2-1
Severity: grave
Justification for severity: Policy violation
During a rebuild of Debian testing, we ran into this test failing during an
sbuild controlled build on a VM with limit network connectivity (only
configured APT repositories usable). See log
ting (like
the "forwarded" bug) but erroring out on imprecise measurements.
If I recall correctly, there is a separate issue on github about this,
somehow related to font rendering(?). However, I can't seem to find it
anymore.
Kind regards,
Sven
Control: tag -1 pending
Hello,
Bug #1056340 in ncurses reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Severity: serious
Package: faad2
Tags: patch upstream security fixed-upstream
Please apply upstream fix
https://github.com/knik0/faad2/commit/1001f9576cbb29242671c489cd861de61cfe08e2?diff=unified
Kind regards,
Sven
that it's not using external resolvers.
Kind regards,
Sven
(as
per its own dicumentation) and a working alternative exists for
LWP::Protocol::http::SocketUnix exists, my suggestion and the graveness of
this bug is still valid.
Grüße,
Sven.
and working version in
LWP::Protocol::http::SocketUnixAlt, I suggest packaging that and
removing liblwp-protocol-http-socketunix-perl from Debian.
Grüße,
Sven.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug
Control: tag -1 pending
Hello,
Bug #1054022 in ncurses reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
her
| environment variables or ioctl is used. The ncurses test-program
| with options "-E -T" demonstrates this feature.
`
Reverting ncurses/tinfo/lib_setup.c to the 20230923 patchlevel made the
problem disappear. I'll leave it to Thomas to work out the details.
Cheers,
Sven
pop -a || test $? = 1
> returned exit code 1
> make: *** [debian/rules:4: clean] Error 25
This is a bug in dh_quilt_unpatch which makes many packages FTBFS.
Cheers,
Sven
Package: libgprofng0
Version: 2.40.90.20230729-1
Severity: grave
Tags: patch
The new versions of binutils is not installable:
,
| $ LANG=C apt -s install binutils binutils-x86-64-linux-gnu
| [...]
| Some packages could not be installed. This may mean that you have
| requested an impossible
type... x86_64-pc-linux-gnu
>> checking whether the C compiler works... no
>> configure: error: in `/<>/debian/build-gtk'
>> configure: error: C compiler cannot create executables
The compiler is CC=gcc-12, which is apparently not present because emacs
does not build-depend on it.
Cheers,
Sven
On 2023-07-23 10:57 +0300, Adrian Bunk wrote:
> On Sun, Jul 23, 2023 at 09:03:24AM +0200, Sven Joachim wrote:
>> On 2023-07-23 09:37 +0300, Adrian Bunk wrote:
>>
> I haven't checked whether the replacement package names are correct,
>> > but the = dependences
.1+20181013-2+deb10u2) in Depends.
> ...
>
>
> I haven't checked whether the replacement package names are correct,
> but the = dependences hardcoded in debian/control are clearly wrong.
Hardcoding a dependency on libtinfo6 is also wrong, but libncurses-dev
is indeed the successor of libncurses5-dev.
Cheers,
Sven
; and here it's also on amd64, but a seemingly very different NVidia
> graphics card.
Quite likely the same issue, I would say.
Cheers,
Sven
Control: tags -1 + patch
On 2023-07-01 20:32 +0200, Sven Joachim wrote:
> Source: debian-installer-utils
> Version: 1.146
> Severity: serious
> Tags: trixie sid ftbfs
>
> Unfortunately your package FTBFS after the recent ncurses upload. From
> my suild log:
>
>
Source: debian-installer-utils
Version: 1.146
Severity: serious
Tags: trixie sid ftbfs
Unfortunately your package FTBFS after the recent ncurses upload. From
my suild log:
,
|debian/rules override_dh_auto_install
| make[1]: Entering directory '/<>'
| for file in
thunderbird exits with the last line of "Exiting due to channel
> error.":
Yeah, seen by other peopl as well.
> Versions of packages thunderbird depends on:
> ii libnss3 2:3.90-2
Downgrade that to version 2:3.89-2, and you're a happy camper.
Cheers,
Sven
Package: libnss3
Version: 2:3.90-2
Severity: grave
X-Debbugs-Cc: Sven Joachim , Carsten Schoenert
After upgrading libnss3 thunderbird no longer starts, in a terminal
window I see these messages:
,
| $ thunderbird
| ATTENTION: default value of option mesa_glthread overridden by environment
Unblock requested:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034621
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
ou still believe the service
file should be moved back to /lib from /usr/lib.
Andreas, I am not sure how it might be possible to have everything
created automatically by debhelper, especially the part creating an
initial configuration from user input might prevent this. If you have
any sugg
needs
a binNMU, its version in bookworm is the same as in bullseye).
I think that libswipl9 should be split into its own package after the
bookworm release, the freeze policy forbids doing that now.
Cheers,
Sven
From b9d119873ed8d7fa891bce356cffe4432c82f517 Mon Sep 17 00:00:00 2001
From:
Package: tzdata-legacy
Version: 2022g-7exp1
Severity: serious
There was an error installing your package:
,
| Unpacking tzdata-legacy (2022g-7exp1) ...
| dpkg: error processing archive
/var/cache/apt/archives/tzdata-legacy_2022g-7exp1_all.deb (--unpack):
| trying to overwrite
ould not migrate to
testing while gdb is kept out there by both #1031745 and a manual block
request by the release team.
Please keep this bug open until gdb 13.1 migrates.
Cheers,
Sven
that additional check. Let me know if you
> cannot reproduce.
I can reproduce this, but only if the target directory
(/run/runit/supervise) actually exists. Otherwise dpkg-source does not
complain.
Lintian reports the absolute symlink as a warning, but maybe turning it
into an error would be more appropriate.
Cheers,
Sven
[Switching over to the cloned bug.]
On 2023-02-09 12:31 -0500, Theodore Ts'o wrote:
> On Thu, Feb 09, 2023 at 06:04:23PM +0100, Sven Joachim wrote:
>>
>> Thanks from me as well :-). To prevent e2fsprogs from migrating to
>> testing before grub2 and breaking d-i, I
t would also be a good idea to add a versioned
"Breaks: grub2-common (<< 2.06-8~)" to e2fsprogs.
Cheers,
Sven
md64.udeb
> rebranded as 1.48, which made the problem disappear.
It is the metadata_csum_seed feature that is now enabled by default
which grub-install does not grok. This has been reported "recently"[1].
Cheers,
Sven
1. https://bugs.debian.org/866603
ot break
anything beyond itself and its reverse dependencies.
Use mpv instead of mplayer, it works.
Cheers,
Sven
1. https://bugs.debian.org/1004579
2. https://www.debian.org/Bugs/Developer#severities
Package: libreoffice-common
Version: 4:7.4.4-7
Severity: serious
The Breaks in libreoffice-common need to be adjusted for the recent
epoch bumps. Among others, libreoffice-common Breaks
libreoffice-core (>= 1:7.5~), making libreoffice-core 4:7.4.4-7
not installable.
Good luck figuring out what
Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-1
Severity: grave
Justification: renders package unusable
Hi,
with the introduction of Python 3.11 offlineimap does no longer work
due to a failing multithread safety check for SQLite.
The issue was handled upstream in
On 2023-01-08 02:56 +0100, Vincent Lefevre wrote:
> On 2023-01-07 20:05:59 +0100, Sven Joachim wrote:
>> >> If not, you may have been bitten by bug #1019554 in
>> >> anacron which needs manual restore as mentioned in
>> >> https://lists.debian.org/debi
On 2023-01-07 19:48 +0100, Vincent Lefevre wrote:
> On 2023-01-07 19:20:56 +0100, Sven Joachim wrote:
>> On 2023-01-07 18:53 +0100, Vincent Lefevre wrote:
>> > zira:~> ll /var/lib/dlocate
>> > total 109172
>> > -rw-r--r-- 1 root root 55750318 2022-11-25 00
y have been bitten by bug #1019554 in
anacron which needs manual restore as mentioned in
https://lists.debian.org/debian-devel-announce/2022/11/msg1.html.
Cheers,
Sven
Control: tags -1 - patch
On 2023-01-03 11:03 +0100, Sven Joachim wrote:
> Control: reassign -1 vim-common 2:9.0.1000-2
> Control: retitle -1 vim-common: debian.vim installed into the wrong directory
> Control: severity -1 serious
> Control: tags -1 patch
>
> On 2023-01-03
On 2023-01-02 19:08 +0100, Vincent Lefevre wrote:
> On 2023-01-02 18:07:52 +0100, Sven Joachim wrote:
>> On 2023-01-02 16:34 +0100, Vincent Lefevre wrote:
>> > There is no such issue under bullseye (Debian 11.6), which also has
>> > GNU Screen 4.09.00, so the breakage
n the following line.
I failed to reproduce that step, the 'v' appears on the last column for
me.
Cheers,
Sven
Hi,
I just wanted to give a heads up, that earlier today I uploaded an NMU
to DELAYED+5 containing upstream version 1.7.4 which should fix this bug.
I pushed the changes to the packaging repository on salsa, so I assume a
debdiff of the NMU is not required here.
Regards
Sven
Hi,
I just noticed that the current upstream release 1.7.2 still has a bug
very similar to this bug present.
(https://projects.torsion.org/borgmatic-collective/borgmatic/issues/590)
It's basically the same bug, only with `patterns_from` instead of
`patterns`.
Regards
Sven
Audacity 3.2.0 is available upstream, fixing this.
the bug causes borgmatic to
produce effectively empty backups, while the user may believe to have
secure backups, which qualifies as data loss to me. Feel free to lower
the severity to normal if you disagree.
Regards
Sven
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
fixed 1017862 1.8.1-8
thanks
Upload of 1.8.1-8 contained
https://salsa.debian.org/python-team/packages/scipy/-/blob/master/debian/patches/pythran_type_PR16646.patch
- which fixes this both according to the original failure report and
my build of scipy for i386.
Cheers,
Sven
n/turn/blob/master/client_test.go#L47
Cheers,
Sven
package: unpaper
Version: 6.1-2
Severity: serious
Build log excerpt below. There is a new upstream version, but I'm not
sure if that builds cleanly against the new ffmpeg.
ffmpeg version: 7:5.0.1-3 (lbavformat-dev and friends)
dpkg-buildpackage
-
Command: dpkg-buildpackage
The bug report is apparently erroneously reported against tilix
version 1.9.5-1 - which actually fixed the issue, as far as I can
tell.
Version 1.9.5-1 is installable (no "impossible dependency") in debian/sid
Hi there.
Just a side note: The test fails on my test builds (with the same error as
in the original report. Because it relies on having a working network
connection. Which it shouldn't do. (my test builds are on a connection that
only allows access to a Debian mirror).
Cheers,
Sven
(nearly) all maintainers received a lot of these mails
one hour ago. But maybe it was just a temporary glitch
Kind regards,
Sven
signature.asc
Description: This is a digitally signed message part.
this while trying to see what the
differences between poppler and mupdf would be. After this I will
probably go back to poppler myself.
I'll have a closer look at this in the coming days.
Since the fix was relatively simple, I opened a merge request on salsa[1].
Regards
Sven
[1]: https
Just a quick update:
The problem of this particular one is:
in puppet/file_system.rb
def self.symlink(path, dest, options = {})
@impl.symlink(assert_path(path), dest, options)
end
Changing this to:
def self.symlink(path, dest, **options)
@impl.symlink(assert_path(path), dest,
Package: puppet
Version: 5.5.22-4
Severity: serious
Justification: Fails at core functions
Since testing switched /usr/bin/ruby to use ruby3.0, a previously working
Puppet manifest fails:
s...@larsa.muc:/tmp$ ruby3.0 /usr/bin/puppet apply t.pp
Notice: Compiled catalog for
as no member named
>> ‘bool’; did you mean ‘boolean’?
>> 322 | # define HWCursor PublicOption[ATI_OPTION_HWCURSOR].value.bool
>> | ^~~~
>> ../../src/aticonfig.c:459:13: note
c.h"
>> | ^~
>> compilation terminated.
>> make[3]: *** [Makefile:539: blade_accel.lo] Error 1
The reason is the removal of ramdac drivers in xserver 1.21[1].
Upstream's git repository for -trident has a patch[2] which works for me
(only build-time test
On Fri, 20 Mar 2020 17:59:09 +0100 Hans-Christoph Steiner
wrote:
>
> Once kotlin is in Debian, then we can use newer upstream versions, which
> support the latest JDK.
>
>
Kotlin version 1.3.31 seems to be in Unstable now.
Package: ilorest
Version: 3.2.2+ds1-2
Severity: serious
When rebuilding ilorest, I ran into error below on my build server
which has limited network access. AFAICT, adding a build-dependency on
python3-pbr should address this failure.
Cheers,
Sven
+ python3.9 setup.py install --install-layout
I cannot reproduce this bug any more. Connecting to the Kademlia
network works again without any issues.
No packages had been upgraded since the initial bug report.
I suggest to reduce the bug's severity to normal.
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
Hi Hilmar.
I'm on vacation and don't currently have access to a computer other than my
mobile phone. Anyhow, your command to check for the vulnerable class looks
right to me.
No clue when the relevant class started being included in Arara and TeX
live.
Cheers,
Sven
Hilmar Preuße schrieb am Sa
Package: texlive-extra-utils
Severity: grave
Version: 2021.20211127-1
Tags: security
texlive-extra-utils contains arara (https://github.com/islandoftex/arara)
which was updated two days ago via TeX Live (https://www.tug.org/texlive/)
which was updated slightly after that. Please update to the
Further observations:
Setting ConnectToKad=0 in ~/.aMule/amule.conf lets amuled start up as
expected, but of course without connecting to the Kademlia network.
Activating Kademlia later on via amulegui > Preferences > Connection >
Networks and bootstraping from known clients makes amuled crash
1 - 100 of 1678 matches
Mail list logo
