Control: severity serious
As systemd increased the limits againĀ¹, nocache is now unusable. It's
the
| apt: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed.
issue, triggered as simple as issuing "nocache true" - unless the system
has several Gigabytes of RAM. As systemd certainly
Control: clone -1 -2
Control: retitle -2 nocache.c:148: init_mutexes: Assertion `fds_lock != NULL'
failed.
Control: severity -2 normal
On 2019-01-05 08:54 +0100, Sven Joachim wrote:
> I get a different error here:
>
> ,
> | ## #916415
> | timeout 11 ./nocache apt show coreutils 1>>/dev/null
On Saturday, 5 January 2019 6:54:39 PM AEDT Sven Joachim wrote:
> I get a different error here:
>
> ,
>
> | ## #916415
> | timeout 11 ./nocache apt show coreutils 1>>/dev/null
> | apt: nocache.c:148: init_mutexes: Assertion `fds_lock != NULL' failed.
> | Aborted
> | make[1]: *** [debian/rules
Hi Santiago,
Thanks for the patch.
On Saturday, 5 January 2019 10:43:14 AM AEDT Santiago Vila wrote:
> ## #916415
> - timeout 11 ./nocache apt show coreutils 1>>/dev/null
> + timeout 60 ./nocache apt show coreutils 1>>/dev/null
I see, this issue is environment specific and seems to
On 2019-01-04 22:49 +, Santiago Vila wrote:
> Package: src:nocache
> Version: 1.1-1
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in sid but it failed:
>
>
> [...]
> deb
tags 918316 + patch
thanks
The patch below works for me:
--- a/debian/rules
+++ b/debian/rules
@@ -18,5 +18,5 @@ override_dh_auto_test:
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
# -NOCACHE_NR_FADVISE=2 dh_auto_test -v
## #916415
- timeout 11 ./nocache apt show coreutils
Package: src:nocache
Version: 1.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
7 matches
Mail list logo