Your message dated Mon, 16 Jun 2025 07:32:41 +0200
with message-id <aE-seWMnCa2za-Kj@vis>
and subject line Re: Bug#1107743: weasyprint: apt weasyprint install fails with
unpack error on libboost1.74-dev:arm64
has caused the Debian Bug report #1107743,
regarding weasyprint: apt weasyprint install fails with unpack error on
libboost1.74-dev:arm64
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 [email protected]
immediately.)
--
1107743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107743
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: weasyprint
Version: 57.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
On a first-time install of weasyprint, using 'apt install weasyprint', I
receive the following error related to libboost:
Unpacking libboost1.74-dev:arm64 (1.74.0+ds1-21) ...
dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
dpkg: error processing archive
/var/cache/apt/archives/libboost1.74-dev_1.74.0+ds1-21_arm64.deb (--unpack):
cannot copy extracted data for
'./usr/include/boost/compute/algorithm/detail/merge_sort_on_cpu.hpp' to
'/usr/include/boost/compute/algorithm/detail/merge_sort_on_cpu.hpp.dpkg-new':
unexpected end of file or stream
Errors were encountered while processing:
/var/cache/apt/archives/libboost1.74-dev_1.74.0+ds1-21_arm64.deb
Re-running 'apt install weasyprint' just says libboost is not going to be
installed, and running
'apt --fix-broken install' just gets the same error exit again.
-- System Information:
Debian Release: 12.11
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.1.0-34-cloud-arm64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages weasyprint depends on:
iu libpango-1.0-0 1.50.12+ds-1
iu libpangoft2-1.0-0 1.50.12+ds-1
ii python3 3.11.2-1+b1
iu python3-cffi 1.15.1-5
ii python3-cffi-backend [python3-cffi-backend-api-min] 1.15.1-5+b1
pn python3-cffi-backend-api-max <none>
iu python3-cssselect2 0.7.0-1
iu python3-fonttools 4.38.0-1+b1
iu python3-html5lib 1.1-3
iu python3-pil 9.4.0-1.1+deb12u1
iu python3-pydyf 0.5.0-3
iu python3-pyphen 0.13.2-1
iu python3-tinycss2 1.2.1-2
iu shared-mime-info 2.2-1
Versions of packages weasyprint recommends:
ii ca-certificates 20230311
weasyprint suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
* Kirk Parker <[email protected]> [2025-06-15 21:01]:
I upped the size of the virtual server (doubling the RAM) and now the
install worked fine.
I do think that if out-of-memory was the issue than the gunzip (whatever is
unpacking the module) should say so, rather than
"unexpected end of file or stream"
since this gives no clue as to the remedy.
I agree the more information would be nice here but that's not always
possible. The process only get's the information that it is killed and
not why. You can probably see more information with journalctl.
Anyway, thanks so much for pointing me in the right direction!
Great, closing accordingly.
On Sat, Jun 14, 2025 at 1:35 AM Jochen Sprickerhof <[email protected]>
wrote:
Control: tags -1 moreinfo
Hi Kirk,
* Kirk Parker <[email protected]> [2025-06-13 08:18]:
>On a first-time install of weasyprint, using 'apt install weasyprint', I
receive the following error related to libboost:
>
> Unpacking libboost1.74-dev:arm64 (1.74.0+ds1-21) ...
> dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
> dpkg: error processing archive
/var/cache/apt/archives/libboost1.74-dev_1.74.0+ds1-21_arm64.deb (--unpack):
> cannot copy extracted data for
'./usr/include/boost/compute/algorithm/detail/merge_sort_on_cpu.hpp' to
'/usr/include/boost/compute/algorithm/detail/merge_sort_on_cpu.hpp.dpkg-new':
unexpected end of file or stream
> Errors were encountered while processing:
> /var/cache/apt/archives/libboost1.74-dev_1.74.0+ds1-21_arm64.deb
I was not able to reproduce this on an up to date stable, tagging
moreinfo accordingly.
> dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
Especially this makes me wonder if this was a problem on your system
specifically. Maybe your system ran out of memory or is flaky in some
other way?
Also this is likely not a bug in the weasyprint package (nor in
libboost1.74-dev) so I propose to downgrade the bug in a few days,
unless you disagree.
>Re-running 'apt install weasyprint' just says libboost is not going to be
installed, and running
>'apt --fix-broken install' just gets the same error exit again.
Not sure how to recover your system can you try
apt remove libboost1.74-dev
And send the output?
Cheers Jochen
--
------------------------------------
Kirk Parker
Edge Technologies, Inc.
[email protected]
signature.asc
Description: PGP signature
--- End Message ---
