For reference, this was fixed in openjdk-11 (11.0.22+7-2) because of this
patch:
https://salsa.debian.org/openjdk-team/openjdk/-/blob/2aebf9c2fb202cf3648cbeda9d96d8b29650e79f/debian/patches/8307977-proposed.diff.
I think it would make sense to apply the same patch could to openjdk-17 as
well,
/2aebf9c2fb202cf3648cbeda9d96d8b29650e79f/debian/patches/8307977-proposed.diff,
but with some comments modified).
Best regards,
Per
From: Per Lundberg
Sent: Monday, January 29, 2024 10:17
To: 1034...@bugs.debian.org <1034...@bugs.debian.org>; d...@ubuntu.com
Subject: Re: Bug#1034600
you want me to create a new bug for this or just reopen+reassign this bug to
src:openjdk-17? (feel free to just reassign it yourself if you want to)
Best regards,
Per
From: Debian Bug Tracking System
Sent: Friday, January 26, 2024 22:45
To: Per Lundberg
Subject
FYI: An OpenJDK bug regarding this has now been opened as well:
https://bugs.openjdk.org/browse/JDK-8307977
--
Best regards,
Per
On 2023-04-20 00:03, Vladimir Petko wrote:
Oh, thank you for providing a patch for a quite annoying bug
The pleasure is ours. :-) (I didn't write the patch myself but I helped
out a bit with the initial debugging)
Would it be possible to add a header to the patch, so that it is
possible
On 2023-04-19 10:22, Thorsten Glaser wrote:
On Tue, 18 Apr 2023, Per Lundberg wrote:
wanted to share it with you as well. One option would be to include this in
Debian's set of local JDK patches
Shouldn’t this be added to 11 as well? Apparently, both are affected.
Good point. Yes
Hi,
A short update on this. This is a known regression in more recent
versions of Java: https://bugs.openjdk.org/browse/JDK-8226919
One of my colleagues (thanks, Sebastian!) managed to workaround this by
patching the JDK 17 sources to make it use plain /tmp in this case (when
ns_pid ==
Package: tomcat9
Version: 9.0.43-2~deb11u6
Severity: normal
X-Debbugs-Cc: sebastian.lovd...@hibox.tv
Hi,
We noticed while rolling out JDK 17 support for our in-house application
that the following command is "broken" (moral-martin is an LXD container
in my examples below, PID 4108 is the tomcat9
Hi Shengjing Zhu,
On 2023-02-21 11:44, Shengjing Zhu wrote:
Please read message#91
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975#91 and then
think about it.
If you still think there's a secure patch that we can apply, I'd like to review.
Hmm, you have some very valid points and
solved
upstream. We can't have programs that misbehave this badly in the
distribution, IMO.
Best regards,
Per Lundberg
Hi,
I think we are probably a number of people excited to see this (soon!) finally
making it into Debian proper. :) I am currently running LXD as a snap, but it
would just be so much nicer and cleaner to be able to use the "real" packages
for this.
The package is currently in the Debian "new"
Hi,
On 2022-03-02 17:24, Markus Koschany wrote:
(Speaking about tomcat10, I noted the package in experimental is really
old - doesn't seem to have been updated for a few years. Do you know if
anyone is working on updating the package to e.g. Tomcat 10.0.17 or will
it perhaps happen later in
Hi Markus,
On 2022-03-02 14:15, Markus Koschany wrote:
As a matter of fact OpenJDK 11 is the only supported Java version in oldstable,
stable and testing right now. We plan to release with Java 17 next year and one
of our goals is to ship only Tomcat 10 in Debian 12 "Bookworm". I think you are
reassign 1006647 tomcat9
thanks
This might better belong to this package, since the problem is that
tomcat9-common depends on default-jre-headless | java8-runtime-headless
| java8-runtime, while in reality it requires Java 11. (because of
Eclipse JDT 4.21, see original bug report for details)
Package: libeclipse-jdt-core-java
Version: 3.27.0+eclipse4.21-1
Severity: normal
Dear Maintainer,
The 3.27.0+eclipse4.21-1 version of the package has switched to using
the 4.21 version of the upstream package (libeclipse-jdt-core-java).
This is problematic for us and potentially others who are
fully supported yet, proceeding with
partial confinement Hello World!
bugs.debian.org
(Unsure about how to mark this as a duplicate with the Debian BTS, someone who
knows how to do it is welcome to do it.)
From: Per Lundberg
Sent: Thursday, September 2, 2021 14:15
T
This seems like a duplicate of #934372 to me.
On 2/4/19 10:07 PM, Moritz Mühlenhoff wrote:
> What is the specific use case for this, is there some package which
> needs 8 and can't be fixed in time for 11?
Yes, it was stated in this thread earlier that such packages do exist.
Emmanuel/others, is this the correct list of packages which can
On 2/1/19 11:20 AM, Matthias Klose wrote:
> On 01.02.19 10:03, Emmanuel Bourg wrote:
>> This is an excellent suggestion. We should file a bug for openjdk-8 to
>> implement that.
> please attach the patch.
Sure, I should be able to write something up. Forbear my ignorance:
should I use debconf
On 1/29/19 3:36 PM, Markus Koschany wrote:
> We usually ship only with one JDK per release because of security
> support. OpenJDK 8 will be EOL before the end of the Debian 10 release
> cycle. We still have a couple of packages that will not compile with
> OpenJDK 11 hence we also thought about
Hi Markus,
On 1/29/19 1:32 PM, Markus Koschany wrote:
>
>> I am sorry but OpenJDK 8 will not be supported at runtime in
>> Buster.
Another question: if this is the case, should the openjdk-8-jdk package
(and friends) be removed altogether in sid? I looked briefly but
couldn't find any bugs
On 1/29/19 1:32 PM, Markus Koschany wrote:
Hi Markus and Emmanuel,
Emmanuel - the problem is that VisualVM will display its splash screen,
then die with an error in the log about java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>> I am sorry but OpenJDK 8 will
FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version
11.0.2+7-1, but it _does not_ work correct any more with Java 8
(openjdk-8-jdk version 8u191-b12-2)
This worked correctly with 1.3.9-1 after downgrading the libnb-*-java
packages as suggested by Ben - visualvm worked fine on
FWIW, I have verified this bug on my machine - downgrading to
8.1+dfsg1-7 as suggested by Ben helped, making it work again. (Thanks, Ben!)
Here is the stack trace when running with 8.1+dfsg1-8. To me, this looks
like code compiled for Java 9+ trying to run on Java 8 (which I am
currently
FWIW, I tried doing a blank install with the Buster Alpha 3 installer,
putting /usr on a separate LVM volume to see if Debian Buster would
also be affected of this. It was not - /usr was mounted without any
obvious problems during bootup. (This seems to be different from
Ubuntu 18.04, but I
Package: lvm2
Version: 2.02.176-4.1
Severity: normal
Dear Maintainer,
We just noted on a fresh Ubuntu 18.04 installation after it failed to
mount the /usr partition on boot, that its /sbin/lvm tool depends on
libraries in /usr/lib. I assumed at first that this bug was local to
Ubuntu, but for
On 8/27/18 3:07 PM, Markus Koschany wrote:
I believe you both misunderstand the current issue at hand. In Debian we
default to OpenJDK 10 at the moment and soon OpenJDK 11 because this
will be the only supported (security wise) runtime environment for
Debian 10 "Buster". [...]
Thanks for the
On 8/26/18 12:46 AM, Markus Koschany wrote:
I believe we should tighten the dependency on default-jre-headless. We
currently have for tomcat8-common:
default-jre-headless | java8-runtime-headless | java8-runtime
We should simply change that to
default-jre-headless (>= 10) |
I agree, this seems to be a regression. The package was incorrectly
built with Java 10 previously, but this was fixed as part of #895866.
Apparently, the problem seems to have reappeared. Verified with Java
1.8.0_181-8u181-b13-1-b13 (package list below).
ii openjdk-8-jdk-headless:amd64
Package: python2.7
Version: 2.7.12-3
Severity: important
I get the error reported in when trying to configure this version of
python (which has been introduced in 'stretch' recently. I guess it could be
caused by some 3rd party library on my system?
Any suggestions on how to debug it further?
On Mon, 2006-01-16 at 15:22 -0800, Ryan Murray wrote:
On Mon, Jan 16, 2006 at 11:40:58PM +0100, Per Lundberg wrote:
This is the gdb output, including backtrace:
This is useless without debugging symbols for the related libs, and
indication of the LD_PRELOAD that was used at start time being
.so
#9 0x in ?? ()
--
Best regards,
Per Lundberg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: firefox
Version: 1.5.dfsg-4
Followup-For: Bug #348019
I have also reproduced this bug here. However, it worked for me with a
non-root user (another user account than the one that I regularly use), so
it is not a permissions problem. There was a .mozilla directory in the other
users home
Package: mysql-server
Version: 4.0.23-7
Followup-For: Bug #297283
This bug was reproduced on my system.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=C
34 matches
Mail list logo
