Package Details: adguardhome 1:0.106.3-1

Git Clone URL: (read-only, click to copy)
Package Base: adguardhome
Description: Network-wide ads and trackers blocking DNS server
Upstream URL:
Licenses: GPL
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 10
Popularity: 0.130078
First Submitted: 2019-12-22 11:00
Last Updated: 2021-05-19 13:47

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

diegoduarte commented on 2021-02-11 22:33

@graysky the issue was resolved using 2GB of memory RAM on this VM

diegoduarte commented on 2021-02-11 16:04

@graysky Maybe, I have only 1GB of memory RAM available for this VM, but this OOM issue never happened before

graysky commented on 2021-02-11 14:13

You should not need to adjust your MAKEFLAGS. The PKGBUILD will do that. 1:0.105.0-3 builds for me in a clean chroot. Is this something in your environment? Are you out of physical memory?

diegoduarte commented on 2021-02-11 13:15

@graysky Using MAKEFLAGS "make -j1" I got "JavaScript heap out of memory" on the building process

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0x5613e1123fd1 node::Abort() [webpack] 2: 0x5613e1042144 node::FatalError(char const, char const) [webpack] 3: 0x5613e1303d62 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [webpack] 4: 0x5613e1303fc8 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [webpack] 5: 0x5613e14c3c36 [webpack] 6: 0x5613e14c3d8c [webpack] 7: 0x5613e14d1c4f v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [webpack] 8: 0x5613e14d2487 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack] 9: 0x5613e14d5b2c v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 10: 0x5613e14d5b94 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack] 11: 0x5613e149ad3b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack] 12: 0x5613e17e1bfa v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long, v8::internal::Isolate) [webpack] 13: 0x5613e1b3b779 [webpack] error Command failed with signal "SIGABRT". info Visit for documentation about this command. make: *** [Makefile:67: js-build] Error 1 ==> ERROR: A failure occurred in build(). Aborting... :: yarn is now an orphan package :: failed to build adguardhome package(s)

graysky commented on 2021-02-11 12:44

@diegoduarte -

EDIT: workaround is building with make -j1 which is now hard-coded into the PKGBUILD until upstream addresses it. Enjoy.

diegoduarte commented on 2021-02-11 11:09

@graysky I got the following error on the last release (1:0.105.0-1)

:: Building adguardhome package(s)... ==> Making package: adguardhome 1:0.105.0-1 (Thu 11 Feb 2021 11:05:40 AM WET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Removing existing $pkgdir/ directory... ==> Starting build()... npm --prefix client ci

added 1828 packages, and audited 1829 packages in 23s

13 vulnerabilities (10 low, 3 high)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details. yarn --cwd client2 install make: yarn: No such file or directory make: *** [Makefile:70: js-deps] Error 127 ==> ERROR: A failure occurred in build(). Aborting... :: failed to build adguardhome package(s)

graysky commented on 2020-10-30 09:57

@frantic - I think an epoch= is required here or we wait for a version that is greater than 0.104.0.

frantic1048 commented on 2020-10-30 09:37

According to latest version change from 0.104.0.beta3-1 to 0.104.0-1.

I found vercmp 0.104.0-1 0.104.0.beta3-1 returns -1, which means pacman thinks 0.104.0-1 is an older version compared to 0.104.0.beta3-1. May we bump a new pkgver to fix this?

graysky commented on 2020-08-01 10:48

@bhyoo - This is not a binary package.

bhyoo commented on 2020-08-01 03:59

@graysky How about just using official binaries?? They have updated Makefile and github action to build binaries for several platforms.