Bug #1100335 reports this for openjdk-23
Bug #1098957 reports this for openjdk-21
Sounds like tests depend on being executed in CET (central europe time),
but Europe switched to CEST around that time (From 29th to 30th switch to
CEST happened).
When ignoring deprecation warnings, the following errors remain:
1. msd-a11y-keyboard-atspi.c
msd-a11y-keyboard-atspi.c:131:53: error: passing argument 1 of
‘atspi_device_listener_new’ from incompatible pointer type
[-Wincompatible-pointer-types]
131 | self->listener = atspi_device_liste
When building with -Wno-deprecated-declarations the warnings listed below
remain.
=> so it seems the use of an incompatible type is the culprit here.
tray.c:634:19: error: assignment to ‘GtkWidget *’ {aka ‘struct _GtkWidget
*’} from incompatible pointer type ‘GObject *’ {aka ‘struct _GObject *’}
See
https://github.com/lxde/lxterminal/commit/a942d552276e3d2b98803b0f2a979eab337d6af1
for the corresponding upstream fix.
When building with -Wno-deprecated-declarations the warnings listed below
remain.
When building with -Wno-incompatible-pointer-types the build is successful.
=> so it seems the three instance of incompatible types are the culprit
here.
lxterminal.c: In function ‘terminal_new’:
lxterminal.c:1205:
This does not reproduce for me on recent trixie. Neither 2.25.1 nor 2.25.2
nor latest 2.25.5.
Also building seems to work in the Debian build-infrastructure according to
https://tracker.debian.org/pkg/devscripts
Your output looks like building is done in parallel, are there some
additional option
Upstream provides most of the changes to support qt6 already, see
https://github.com/openscad/openscad/issues/4909 for progress.
retitle 1033436 Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.3:test
merge 1033407 1032989
--
These two bug-reports sound very similar, #1032989 has a lot of
investigation already.
Works as expected on a fresh installation of bookworm.
Can you provide the output of the following command
dpkg --list | grep dbus
P.S. Regarding "First, any recommended application is expected to work
without any issue" => This sounds a bit strange when you are actually using
a totally free op
A stacktrace from the segmentation fault looks like follows.
It triggers consistently for me with the following steps in a source-tree
fakeroot debian/rules binary
cd sample_data/
/tmp/salmon-1.9.0+ds1/obj-x86_64-linux-gnu/src/salmon index -t
transcripts.fasta -i sample_salmon_quasi_index
#0 0
It seems the module does not yet support Python newer than 3.7 (3.9 in the
latest version on Github), see
https://github.com/ilius/pyglossary/tree/master/pyglossary/plugin_lib
Copying the folder pyglossary/plugin_lib/py37 to py310 and py311 fixes this
build-error for me.
The next minor version 20.2.0 has this test removed as part of removing
support for Python2 and 3.5, see commit
https://github.com/hynek/structlog/commit/f65309d4f66fbd44c09288a485107d725c3da1d4#diff-673441c4b6dbee451d8130f1e9bb48f3dbc44d5d3acf1c21d52d0904002342d5
So it might be justified to simpl
Package: laminard
Version: 1.1-1+b2
Severity: grave
Justification: renders package unusable
laminar currently uses Chart.js 2.7.2 (also in newer version 1.2 and on latest
master)
Debian packaging replaces this with the version packaged in Debian, which is
3.9.x
curently, the bookworm-package o
The necessary fix seems to be at
https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de,
applying this fixes building the package.
Bug #925533 re-adds the messaging and jms modules in libspring, so this bug
could be merged as duplicate with that one now.
Bug #925533 re-adds the messaging and jms modules in libspring, so this bug
could be merged as duplicate with that one now.
Not sure if I read the package-pages correctly, but
https://packages.debian.org/search?keywords=libspring-jms-java&searchon=names&suite=all§ion=all
looks to me like libspring-jms-java is still (or again) available both in
buster and sid, so this bug is not a problem any more, right?
Yes, sorry, I found how it was fixed by a followup upload, -5 did not as
far as I see, only -6 will fix it I think. I am also a bit new to the
Debian Bug-via-mail interface, I'll try to fix the bug-state. Sorry for the
spam.
I think the current changes do not properly fix this, I created
https://salsa.debian.org/java-team/netlib-java/merge_requests/2 with the
set of changes based on previous patches that I think would make the
classes be built again and also improve error handling slightly to make it
easier to spot the
This is the same as bug #923759 as far as I see
23 matches
Mail list logo