On Fri, 4 Oct 2024, Bill Allombert wrote:
>On Tue, Oct 01, 2024 at 12:45:13AM +0200, Thorsten Glaser wrote:
>> Package: popularity-contest
>> Version: 1.76
>> Severity: normal
>> X-Debbugs-Cc: t...@mirbsd.de
>>
>> -rw-r--r-- 1 root root 21239 Sep
Package: popularity-contest
Version: 1.76
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
-rw-r--r-- 1 root root 21239 Sep 26 11:06 popularity-contest
-rw-r--r-- 1 root root 21260 Sep 26 06:25 popularity-contest.0
-rw-r--r-- 1 root root 4875 Sep 19 11:06 popularity-contes
Package: mc
Version: 3:4.8.26-1.1
Severity: normal
I move to a .css file and press F3 and get:
║╔══ Error
═══╗ 0:43║
║║
On Tue, 24 Sep 2024, Ben Hutchings wrote:
>> Two, say people are expected to create the directories first.
>> But in that case, copy_exec also must not create any missing
>> directories any more *at all*,
>
>No, it was documented to do that for the case where no target argument
>was given, and cha
On Tue, 24 Sep 2024, Ben Hutchings wrote:
>I suppose I can make this work again for bookworm, but I won't do so
>for unstable.
Then, perhaps issue a visible warning so that people can change
their scripts?
>This was not an intended feature. When specifiing a diectory as the
>target you are supp
Package: initramfs-tools-core
Version: 0.142+deb12u1
Severity: serious
Justification: hidden breakage for users, ought to be fixed in stable-pu
X-Debbugs-Cc: t...@mirbsd.de
In bullseye, this would work:
copy_exec /usr/lib/klibc/bin/rnd_shuf /usr/libexec/
copy_exec /usr/sbin/rdate /usr/libexec/
I
Hi Timo,
>$ ssh-keygen -t ed25519 -f /tmp/test
>$ ssh-add /tmp/test < /dev/null
>E: /usr/bin/ssh-askpass[39]: too many open files (3 -> 212): Success
>$ echo $?
>1
>
>key is not added to the agent
this is quite puzzling.
First guess: is $DISPLAY set and points to a usable X11 server?
Second gue
On Thu, 12 Sep 2024, Paul Menzel wrote:
> Using Debian sid/unstable with *gnome-shell* 47~rc-3 from the suite
> *experimental*, and scaling the screen content to 200 %, the buttons
> are too big in MuseScore as seen in the attachment.
Hmm.
Asides from this potentially being a GNOME issue, there’
Hi наб,
>Quoth cvs(1):
the manpage is autogenerated from *parts* of the
texinfo source, using arcane and weird scripts.
> suck, update, server & pserver, CVS commands
> suck‒Download RCS ,v file raw
> suck module/pa/th
> [...]
>
> update, , suck, CVS commands
> update‒
Package: hunspell-en-gb
Version: 1:7.1.0~rc3-3
Severity: normal
X-Debbugs-Cc: t...@x61p.mirbsd.org
Not sure whether this is an actual problem, but
/var/lib/dictionaries-common/hunspell/ contains
what I think are registration files for both
hunspell-en-us and myspell-de-de-1901 but
hunspell-en-gb i
Package: src:linux
Version: 5.10.223-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
In /etc/rc.local I write a text file to /dev/tty11.
I have getty on 1-6 as usual and syslog on 12.
After booting the system, I can confirm this works.
A day or two later (I have not timed this exactly),
I can st
Package: lintian
Version: 2.118.0
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I have trouble creating an override file that works for all
architectures.
On some architectures, lintian (correctly) issues:
mksh: statically-linked-binary [bin/lksh]
I can override this.
But on other architectures,
Package: ansiweather
Version: 1.11-1.1
Severity: normal
Tags: l10n
X-Debbugs-Cc: t...@mirbsd.de
ansiweather insists on using the weird AM/PM format
used by a vast minority of people instead of 24-hour
clock format for e.g. sunrise/sundown, even if I set
the metric option or the locale.
-- System
in Message ---
Hi,
On 2023-08-04 21:40, Thorsten Glaser wrote:
> Hi,
>
> some of the buildds still use Linux 4.19 but klibc has started to
> require Linux 5.1-specific features with the latest sid upload.
> This has implications on mksh (for the mksh-static and lksh binaries
reassign 1006451 ftp.debian.org
retitle 1006451 RM: minify-maven-plugin -- RoM; only remaining user gone
severity 1006451 normal
thanks
guacamole-client was RoQA'd in #926276
so this can be garbage-collected
Simon McVittie dixit:
>was rather recent at that time, but hopefully we no longer have any
>machines that are running Debian 8 kernels...
The varios MIPS buildds run 4.19 and some even 4.9 kernels
(AFAIHH due to hardware/patch constraints), which has led
to problems (e.g. I had to disable klibc b
Hi Simon,
thanks for testing.
>I'm using Thorsten's regression report in #983423 as my representative
>sample of a package that regressed with schroot 1.6.13-4, because mksh
>builds much more quickly than gcc-14
(You can add mksh-firstbuilt to DEB_BUILD_OPTIONS so it doesn’t build
and test binar
Simon McVittie dixit:
>> as well as open("/dev/tty", O_RDWR, 0)
>
>Asserting that /dev/tty is the correct device node and has appropriate
>permissions should cover that.
Totally not, unfortunately: it only works when it actually has a ctty.
>> and later F_DUPFD and F_SETFD, FD_CLOEXEC fcntl
>
>T
Simon McVittie dixit:
>On Mon, 19 Aug 2024 at 16:27:24 +0000, Thorsten Glaser wrote:
>> mksh actually does things inside script(1) that use the tty
>
>For the purposes of having a test-case for schroot that doesn't require
>mksh, perhaps a good approximation to this would b
Package: firefox-esr
Version: 115.14.0esr-1~deb11u1
Followup-For: Bug #911312
X-Debbugs-Cc: t...@mirbsd.de
Control: severity -1 serious
The binary plugin is still automatically downloaded (and likely used).
This is likely a violation of “main” rules.
-- Package-specific info:
-- Addons package
Simon McVittie dixit:
>On Sun, 18 Aug 2024 at 23:44:57 +0000, Thorsten Glaser wrote:
>> On three buildds, mksh FTBFS already because the whole
>> /dev/ptmx and /dev/pts stuff is malfunctioning again
>
>Which buildds? Are you referring to -ports builds
>https://buildd.deb
Hi,
have you actually tested that this works?
On three buildds, mksh FTBFS already because the whole
/dev/ptmx and /dev/pts stuff is malfunctioning again,
after like 15 years of it working after having had to
fight for packages being allowed to depend on it to
obtain a pty/tty for tests during bu
Package: lintian
Version: 2.118.0
lintian reports now, after dh_movetousr:
X: mksh: bin-sbin-mismatch bin/mksh -> usr/bin/mksh
[usr/share/doc/mksh/examples/uhr]
I can only assume that this is due to the #!/bin/mksh shebang
in that file. If so, please carry a list of interpreters in
lintian whos
Santiago Vila dixit:
> El 15/8/24 a las 22:49, Thorsten Glaser escribió:
>> a package that Build-Depends on pmake and uses it
>> in its debian/rules build targets in a clean bullseye chroot
>
> Did you really mean bmake (not pmake) here?
No, pmake.
> If yes: Can y
retitle 1078772 pmake: “bmake: no system rules (sys.mk).” under qemu-user
severity 1078772 important
thanks
Dixi quod…
>Hm, but I just tested with pmake_1.111-3.2_armel.deb from
>the archive, and it also failed.
>
>Is it possible that it doesn’t work right under qemu-user?
Apparently, this is it
Dixi quod…
>stracing shows that, despite the -m option being passed by
>the pmake wrapper, it still accesses /usr/share/mk/.
Hm, but I just tested with pmake_1.111-3.2_armel.deb from
the archive, and it also failed.
Is it possible that it doesn’t work right under qemu-user?
(Which would also be
Package: bmake
Version: 20200710-14+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: t...@mirbsd.de
Building a package that Build-Depends on pmake and uses it
in its debian/rules build targets in a clean bullseye chroot
completely fails with:
bmake: no system rules (s
Paul Gevers dixit:
> The Release Team considers packages that ship files in /usr-merged aliased
> locations RC buggy.
>
> We have put our trust in Helmut to come up with the right solutions during the
> preparation for trixie
Hmpf. He’s doing the dirty work for Md and bluca now.
>, so I'm asking
Helmut Grohne dixit:
>> Maybe the protective diversions also protect against this problem as well
>> as the problem of moved files? I unfortunately failed to spot where the
>> protective diversions were added in dh_movetouser (if that even is the
>> right place to be looking), so I'm fairly sure
(Another data point is that there’s versions of mksh with
version numbers larger than what’s in sid around in my own
repo, for those wanting to follow CVS snapshots more closely,
backported to all versions up to sarge, so bookworm users
can very well have mksh packages with a version number that
is
Helmut Grohne dixit:
>that the way people tend to use mksh is by adding a local diversion for
Unfortunately not.
The way we have to do it since squeeze, when dash unilaterally broke
cross-package coordination, is:
dpkg-reconfigure dash ⇒ remove its owning of /bin/sh
(so it reverts to bash)
ln
Russ Allbery dixit:
>Thorsten Glaser writes:
>
>> You got your merged /usr already, and to force packages to move their
>> files WILL break users’ systems. In particular, mksh as /bin/sh is a
>> supported configuration.
>
>Could you explain how this would break a us
Helmut Grohne dixit:
>I expect this policy change to come into effect before trixie is
>released and the current mksh and pax will be violating said policy.
I’m veto’ing this.
>> 1. the /bin symlink
>>
>> The implicit Pre-Depends on the Essential set being unpacked,
>> where base-files contains
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Helmut Grohne dixit:
>I would like to take the opportunity make you aware of a Debian policy
>change #1074014 about merged-/usr. I mentioned your approach in mksh and
>pax and the consensus among discussion participants was that policy
>should not a
submitter 919265 !
retitle 919265 RFH: xloadimage -- Graphics file viewer under X11
thanks
I’m taking over xloadimage and fixing the RC and some of the other
bugs, but I originally wanted to reduce, not increase, my involvement
in post-bullseye Debian, and I don’t know X11 programming well, so
I w
retitle 1077944 FAQ: musescore4 packaging
tags 1077944 = wontfix
thanks
Hi Tuxicoman,
>I wonder if Musescore 4 will be packaged in Debian or if there are any concerns
>preventing it ?
yes, there are concerns. They’ve arrived too late for bookworm, but the
https://packages.debian.org/sid/musescor
On Thu, 1 Aug 2024, Mark Hindley wrote:
>On Thu, Aug 01, 2024 at 09:02:07AM +0200, Gian Piero Carrubba wrote:
>> The problem is registering an xdm-initiated session with elogind.
>> /etc/pam.d/xdm includes /etc/pam.d/common-session that calls
>> libpam-elogind, so in this sense xdm uses elogind.
Package: apache2-bin
Version: 2.4.61-1~deb11u1
Severity: normal
Adding “IndexOptions FoldersFirst” to a .htaccess does have the
(desired) effect to disable fancy indexing, but the sorting the
directories first does not work (it does in Apache httpd 1.3.x).
-- Package-specific info:
-- System In
Package: debootstrap
Version: 1.0.136
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
It is a useless dependency, only used when no script is given
after all (thankfully; the Depends gave me a shock thinking newer
debootstrap versions can no longer just be used on any Linux).
-- System Information
Package: molly-guard
Version: 0.7.2
Followup-For: Bug #1010627
X-Debbugs-Cc: t...@mirbsd.de
You could scan the crypttab on nōn-systemd services for devices
with “initramfs” in the last field, and/or offer an /etc/defaults/
file where one could list their crypt devices to check (the raw
names, i.e.
Package: cryptsetup-initramfs
Version: 2:2.3.7-1+deb11u1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The /cryptroot/crypttab file in the initramfs contains lines like:
cPV UUID=---- none discard,luks,initramfs
This is bad because these are less stable than t
Helge Deller dixit:
>* Thorsten Glaser :
>>
>> Maybe other 5/6-argument syscalls also need review…
>
>Yes, and basically I tink it's stupid to try to distinguish syscalls
>with 1-4 arguments from those which use 5 or 6 arguments.
>With every added syscall someo
Helge Deller dixit:
> The attached patch fixes the dietlibc testsuite crash on hppa
> in the socketfns testcase.
Thanks, applied.
> So, instead of adding and ifdef for hppa/syscall6_weak, simply
> drop the weak function and call the normal __unified_syscall6.
Looking at the nm output of libc.a,
Helge Deller dixit:
> Maybe sigset_t needs to be removed from
> klibc/include/arch/parisc/klibc/archsignal.h ?
That (with a versioned Depends on the newer kernel headers)
or with a #if LINUX_VERSION_CODE < KERNEL_VERSION(6, 9, 0)
(which will end up causing similar hassle should the change
be back
Package: libklibc-dev
Version: 2.0.13-4
Severity: important
X-Debbugs-Cc: t...@mirbsd.de, Helge Deller
] In file included from /usr/lib/klibc/include/signal.h:14,
] from /usr/lib/klibc/include/sys/select.h:11,
] from /usr/lib/klibc/include/unistd.h:13,
]
Helge Deller dixit:
> Beside the kernel & glibc patches some qemu-user patches will probably
> be necessary as well.
I think so, given how it basically interposes for both.
> I think disabling such tests is probably best right now.
OK. I’ll try debootstrapping an hppa chroot in qemu and see
if
Helge Deller dixit:
> I just did a give-back, and this time the build succeeded (on the
> "c8000" buildd server). The last build failed on the "pasta" buildd
> server, which is a qemu-user based build machine, while "c8000" is
> a physical server which runs the *very latest* stable native
> Linux
Helge Deller dixit:
> Ok, so we have to wait until at least the oldstable kernels are "new" enough.
Given hppa is a ports architecture and this had some time to percolate,
I applied the patches now.
However, I get a (possibly unrelated) build failure on hppa now
(dietlibc in experimental): debia
tags 1069365 + confirmed pending
thanks
Lucas Nussbaum dixit:
>> E: Build killed with signal TERM after 150 minutes of inactivity
Indeed, it busy-spins in diet(1):
include/sys/cdefs.h:#define __likely(foo) __expect((foo),1)
29 size_t strlen(const char *s)
30 {
42 register si
Bastian Germann dixit:
> Please move from to-be-removed jsdoc-toolkit to node-jsdoc2.
Aah!
(Translation: can the nodejs world even do *anything* stable?)
Given I’m also now upstream but have practically no idea about
jsdoc-what
Steve McIntyre dixit:
>we no longer have a signed
>shim. Signed GRUB and fwupd-efi packages will also be removed soon.
Might want to note this on amd64 as well, for those
64-bit systems with 32-bit EFI.
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Hi Guillem,
>These directories are included because the package should be
>self-contained and ship all required parent directories, otherwise
>dpkg would fail to unpack as you mentioned (even though there's
right.
>generally the Essential set in play), and so that the directory
>"ref-counting" (
Dixi quod…
>Or, better yet, absence of that entry in the ustar (possibly
>combined with a Pre-Depends). It’s ridiculous that every pak‐
>kage ships all those directory entries anyway. That avoids
Hmh, lintian warns, and dpkg needs the directories present if
not in the .deb, but most likely we c̲a
Dixi quod…
>If your only concern is the “undeclared symlink conflict”,
>I’d be willing to entertain considering adding a Pre-Depends
>and/or changing the top-level “bin” in the data.tar.xz member
Or, better yet, absence of that entry in the ustar (possibly
combined with a Pre-Depends). It’s ridic
Helmut Grohne dixit:
>There is a significant difference here. mksh has an undeclared directory
>vs symlink conflict with base-files about /bin. This is known to cause
>problems.
But there’s handling in installers to deal with that,
and by keeping the files in mksh in the same location,
there won’
close 1073608
close 1073622
thanks
Helmut Grohne dixit:
>This package is part of the /usr-move (DEP17) transition, because it
>contains files in aliased locations and should have those files moved to
No. The files in both packages are in their canonical location.
And if you use a usrmerged syste
On Mon, 17 Jun 2024, Aron Xu wrote:
>Control: tags -1 - pending
Oops, right.
>It looks that this libxml2 update is causing more troubles than
>expected, I would like to ask for your opinion whether it's better to
>revert to an older version for the moment?
Might be useful while you ask upstream
On Sun, 16 Jun 2024, Thorsten Glaser wrote:
>Better prevent this from landing in trixie until the package
>gets its soname bumped.
In fact, unless someone has the tuits to diff every single
API and ABI surface of the package between trixie (ideally
bookworm) and sid versions, it would be b
clone 1073313 -1
reassign -1 libxml2
found -1 2.12.7+dfsg-3
retitle -1 libxml2: just another API+ABI break; please bump soname
severity -1 serious
tags -1 sid
thanks
On Sun, 16 Jun 2024, Thorsten Glaser wrote:
>This is not the first time in *very* recent history that libxml2
>has an ABI
On Sun, 16 Jun 2024, Yavor Doganov wrote:
>IMVHO removing a public struct member constitutes an API break.
Definitely. I just took a peek at this.
>It is also an ABI break, because if a program or a library accesses
>such member and is compiled against an old libxml2 version that is
>supposed to
Theodore Ts'o dixit:
>That being said, a quick Google search would have turned up this
>explanation of the orphan_file feature, from the kernel documentation:
>
>
> https://www.kernel.org/doc/html/latest/filesystems/ext4/globals.html#orphan-file
Yes, that’s what I found later as well, when I wa
Package: e2fsprogs
Version: 1.47.1~rc2-1
Severity: normal
Tags: bookworm trixie sid
X-Debbugs-Cc: t...@mirbsd.de
Looking at the whole metadata_csum_seed and orphan_file thing,
I wanted to see in the manpages where they are described, also
so I can find them for copy/pasting later for disabling whe
Package: apache2
Version: 2.4.59-1~deb11u1
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de
The W3C validator is not quite happy with the default directory indicēs.
Applying the following change to its config…
- IndexOptions FancyIndexing VersionSort HTMLTable NameWidth=*
De
Package: debian-installer
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso
I was booting in expert mode and expecting between the mirror select
and the installing of the base system there to be an option to sel
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: christ...@iwakd.de, t...@mirbsd.de, bastian.germ...@gmx.de
Control: blocks -1 1067946 1069365
Dear ftpmasters,
in #1067946 it was reported that some consider the sunrpc code as
included in dietlibc nōn-free.
Given that the actual wording is…
Bastian Germann dixit:
>> Do you have a link?
>
> No. It is not a public address.
Ah, yes, that is unfortunate. I used to be subscribed and have no
idea why I’m not, but I re-subscribed (though have not yet seen any
traffic in the last couple of days).
>> What did upstream say?
>
> No upstream r
Moritz Mühlenhoff dixit:
>Am Fri, May 10, 2024 at 06:39:20PM + schrieb Thorsten Glaser:
>> This is a bit like the limited security support for binutils,
>> I suppose. Could/should we document that in the same places?
>
>Sure thing, this sounds similar to what was done fo
Dixi quod…
>Huh. MuseScore (Studio) is a desktop application.
I’ll add a README.Debian note about that fact and that upstream
has never considered crashes on invalid input a bug and that it
hasn’t been designed as a remotely accessible service, but as a
desktop application, and that users should
Moritz Mühlenhoff dixit:
>| MuseScore CAP File Parsing Heap-based Buffer Overflow Remote Code
>| Execution Vulnerability. This vulnerability allows remote attackers
Huh. MuseScore (Studio) is a desktop application.
I will have to investigate whether they mean indeed this
or the musescore.com site
Dmitry Shachnev dixit:
>Will you be able to forward your patch upstream when you finalize it?
Sort of. I can do the CLA, Gerrit, etc. dance, but I probably cannot
respond well if they want me to test things with vanilla upstream
(instead of the packaging), or if they have requests I as a C (but
n
Dixi quod…
>Dmitry Shachnev dixit:
>>Now that you dug so deeply, maybe you can try to replace qRound in those
>>three lines that you mentioned with TO_TTF, and check if it fixes the bug
>
>That *and* figure out somehow how to fix the PDF /FontBBox, at
>least… (though I binary-patched the hhea ascen
Dixi quod…
>values). I’ll build it now so I don’t know if it even compiles yet…
font.hhea.ascender = TO_TTF(properties.ascent.toReal());
font.hhea.descender = TO_TTF(-properties.descent.toReal());
font.hhea.lineGap = TO_TTF(properties.leading.toReal());
g/debian/changelog 2024-05-05
23:58:03.0 +0200
@@ -1,3 +1,10 @@
+qtbase-opensource-src (5.15.2+dfsg-9.0.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/bug1070406.diff
+
+ -- Thorsten Glaser Sun, 05 May 2024 23:58:03 +0200
+
qtbase-opensource-src (5.15.
Hi Dmitry,
(you use Googlemail, which is problematic, I picked your reply
from the BTS; perhaps send to 1070406-submitter@b.d.o instead
which should arrive)
>I checked Qt 4 history [1] and there this code dates back to “Long live Qt!”
>commit from 2009. So it’s unlikely that we can find the origi
Dixi quod…
>correct… but it only changes the metrics in the head table, not
>in the OS/2 or hhea tables (as can be seen when loading the font
>from the PDF in FontForge). Furthermore, the /FontBBox in the PDF
>is constructed from the values from the original font.
And Atril uses the values from t
Dixi quod…
>$ atril moo.pdf
Further debugging reveals the cause:
When Qt5 embeds a font, it scales it to 2048 ppem, no matter if
it was 1000 ppem (PS/CFF) or 1024 ppem (TTF) before. I think this
is because [QTBUG-586] it cannot embed CFF fonts, so it always
converts to TTF (apparently even if it
Package: qtbase5-dev
Version: 5.15.10+dfsg-7.2+b1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Control: found -1 5.15.2+dfsg-9
Control: found -1 5.7.1+dfsg-3+deb9u4
Control: affects -1 musescore
Control: affects -1 musescore3
I’ve received reports that PDFs generated by Mu͒seScore when
viewed in
Hi Bastian,
>I have already informed upstream about it.
did you do that on a mailing list? Do you have a link?
What did upstream say?
Still unconvinced,
//mirabilos
--
If Harry Potter gets a splitting headache in his scar
when he’s near Tom Riddle (aka Voldemort),
does Tom get pain in the arse
Jay Berkenbilt dixit:
>How's that?
That explains it very well and not ambiguous to nōn-native
speakers (I hope).
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Hi Georgios,
why not just ensure the parent directory of the chroot is not
traversable for just any normal user?
That would allow preserving /tmp/buildd as build place as well
as retaining stuff under /run which packages create and which
is, in practice, often needed for chroots where initscripts
Richard Lewis dixit:
>would it make a difference if the somewhat ambiguous line "CVEs" was
>changed to "Fixes the following CVEs:" ?
It’s very much not ambiguous, as the entire entry is a list of
fixes, that’d be reducing the signal:noise ratio (besides this
part of the changelog is copy-pasted f
Christoph Anton Mitterer dixit:
>So Thorsten, in case you or someone else is aware of any [intermediate]
>results from these task forces ([9[) it would be nice to hear about
>them or better even in form of some "official" statement from Debian.
JFTR I’m not involved in those myself.
bye,
//mirab
Package: lintian
Version: 2.117.0
P: openjdk-8-doc: debian-changelog-line-too-short CVEs
[usr/share/doc/openjdk-8-doc/changelog.Debian.gz:4]
The changelog in question is:
* New upstream release
* CVEs
- CVE-2024-21011
- CVE-2024-21085
- CVE-2024-21068
- CVE-2024-21094
* Se
tags 1069678 + pending
thanks
I’m working on it. Upload should come RSN.
AIUI the security team can feel free to ignore openjdk-8
as it’s in sid for bootstrapping and preparing ELTS upgrades
and downstreams purposes, and not “as is” security-supported
in Debian, so if it helps lowering the worklo
Hi Nilesh,
>Right. AFAICS, lintian spews that warning because the header in that patch in
>incomplete. It also needs a "From" and "Subject" (which can be same as commit
this is not entirely correct.
The full patch header is:
Description: fix typeset -p confusion between empty and unset
Origin:
Dixi quod…
>>I’ll recompile with re-enabled alignment on the missing base
>
>Seems to be only one.
>
>--- src/hotspot/share/memory/allocation.hpp~ 2024-04-12 23:52:54.0
>+
>+++ src/hotspot/share/memory/allocation.hpp2024-04-12 23:52:56.0
>+
>@@ -276,7 +276,7 @@ clas
Jay Berkenbilt dixit:
>As it happens, I am upstream.
Oh, nice ☻ in that case, thanks for qpdf.
>---
>It is not generally practical to remove objects from QDF files without
>messing up object numbering, but if you remove all indirect references
>to an object (without removing the object itself),
Bernhard Übelacker dixit:
> On Thu, 4 Apr 2024 21:00:59 + (UTC) Thorsten Glaser
> wrote:
>> Sometimes, it does not crash with a smashed stack but instead:
>>
>> Setting up sasl2-bin (2.1.28+dfsg1-6+b1) ...
>> BDB0002 __fop_file_setup: Retry limit (100) ex
Dixi quod…
>I’ll recompile with re-enabled alignment on the missing base
Seems to be only one.
--- src/hotspot/share/memory/allocation.hpp~2024-04-12 23:52:54.0
+
+++ src/hotspot/share/memory/allocation.hpp 2024-04-12 23:52:56.0
+
@@ -276,7 +276,7 @@ class CHeapO
Dixi quod…
>>(This is what I found trying to build openjdk-20, but it’ll be
>>needed in 21 as well. Even getting to this point took 13½ days
>>already…)
>
>And turns out that this isn’t the cause.
>
>In 17, we’ve got src/hotspot/share/memory/allocation.hpp to
>align all CHeapObj, StackObj, Metaspa
Dixi quod…
>(This is what I found trying to build openjdk-20, but it’ll be
>needed in 21 as well. Even getting to this point took 13½ days
>already…)
And turns out that this isn’t the cause.
In 17, we’ve got src/hotspot/share/memory/allocation.hpp to
align all CHeapObj, StackObj, MetaspaceObj, e
Hi Vladimir,
if you have any suggestions as to what to do best with openjdk-8,
feel free to say.
In Debian, it’s only relevant in unstable, ELTS stretch and jessie,
but for Ubuntu it’s used in more.
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Source: openjdk-21
X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org
Please add the following patch e.g. to debian/patches/m68k-support.diff
for more making implicit alignment assumptions (here by the futex
syscall) explicit:
--- src/hotspot/os/linux/waitBarrier_linux.hpp~ 2024-04-12 18:2
Sergio Durigan Junior dixit:
>-export LANG=C
>-export LC_ALL=C
>+export LANG="${LANG:-C}"
>+export LC_ALL="${LC_ALL:-C}"
Ouch, no.
IMHO, they ought to really be unset for sane build environments,
and if the thing to be built needs locales, it can set its own.
Passing environment variables, even
Jay Berkenbilt dixit:
>Can you tell me where in the docs it says what you're describing?
>Here's a direct quote from the current qpdf documentation:
>
>It is not generally practical to remove objects from QDF files without
>messing up object numbering, but if you remove all references to an
>objec
Jonathan Wiltshire dixit:
>Please go ahead.
Thanks. Do you need a blurb for the point release notes
or something?
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Rich Felker dixit:
>Is there anything weird about how these objects were declared that
>might have caused ld not to resolve them statically like it should? It
>seems odd that these data symbols, but not any other ones, would be
>left as symbolic relocations.
I don’t think so?
In I already
poste
Markus Wichmann dixit:
>I may not really know what I am talking about, so take this with a grain
>of salt, but isn't this missing a -Bsymbolic somewhere? Ironically, that
>switch causes ld to not emit symbolic relocations. I seem to remember
>reading long ago in Rich's initial -static-pie proposal
Markus Wichmann dixit:
>can check with readelf -r what the relocation types are. If they are not
>relative, they will not be processed.
Gotcha! They are all R_390_RELATIVE except for:
00045ff0 00110016 R_390_64 00042c58 u_ops + 70
00045ff8 00110016 R_390_64
Hi,
I don’t think a /etc/cron.yearly/ should be created as directory,
given that the default /etc/crontab never executes anything in it
even if anacron may do.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer
1 - 100 of 2237 matches
Mail list logo
