Bug#1068609: marked as done (libreoffice: FTBFS on arrmhf: testContentGnumeric assertion failed,- Expression: xServiceInfo->supportsService("com.sun.star.sheet.SpreadsheetDocument"))
Your message dated Sun, 7 Apr 2024 23:16:47 +0200
with message-id <acf42187-fbc7-4c40-84f7-f5adbc485e70@debian.org>
and subject line Re: Bug#1068609: libreoffice: FTBFS on arrmhf: testContentGnumeric assertion failed,- Expression: xServiceInfo->supportsService("com.sun.star.sheet.SpreadsheetDocument")
has caused the Debian Bug report #1068609,
regarding libreoffice: FTBFS on arrmhf: testContentGnumeric assertion failed,- Expression: xServiceInfo->supportsService("com.sun.star.sheet.SpreadsheetDocument")
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1068609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068609
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libreoffice
Version: 4:24.2.0-1
Severity: serious
Tags: trixie ftbfs
Hi,
Am 30.03.24 um 12:56 schrieb Rene Engelhard:
Am 30.03.24 um 08:49 schrieb Rene Engelhard:
That would mean a bin-NMU of liborcus would work and then a rebuild
of libreoffice (gb, but I need a new upload anyway)
So we probably missed a rename? (Or more for stuff silently using
time-date?)
boost1.83 (iostream)? liborcus? Both?
I prepared a time_t rename of liborcus. Can upload it (to NEW...) any
time.
A bin-NMU would also work, except for a needed runtime dependency,
then again it's "only" the gnumeric filter...). I wouldn't mind a
simple bin-NMU at least.
That one got done on April 1 :)
> Ran the full tests with it. Passed.
(Unfortunately) that (expectedly) now causes the reverse issue in
testing. Just verified in a local build.
Fortunately the startup of LO works fine (tried on my machine here) so
it's probably "just" gnumeric (and maybe other gnumeric-using filters)
affected.
Filing a bug for reference. This is fixed in 4:24.2.2-3, will mark it as
such when I get the bug number.
Regards,
Rene
--- End Message ---
--- Begin Message ---
Version: 4:24.2.2-3
Hi,
Am 07.04.24 um 23:13 schrieb Rene Engelhard:
Filing a bug for reference. This is fixed in 4:24.2.2-3, will mark it
as such when I get the bug number.
As said.
Regards,
Rene
--- End Message ---
Reply to: