Package Base Details: distccd-alarm

Git Clone URL: (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 28
Popularity: 0.28
First Submitted: 2017-09-14 21:47
Last Updated: 2020-01-05 23:34

Latest Comments

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

sehraf commented on 2018-05-20 10:56

The PKGBUILD is broken when using a separated build directory:

from /etc/makepkg.conf

-- Specify a directory for package building.


When building i get the following error (using yaourt or pacaur): cp: cannot stat '/tmp/yaourt-tmp-user/aur-distccd-alarm-armv7h/armv5.install': No such file or directory

This is the directory where yaourt places the PKGBUILD (/tmp/yaourt-tmp-user/aur-distccd-alarm-armv7h/PKGBUILD) (same goes for pacaur /home/user/.cache/pacaur/distccd-alarm/PKGBUILD)

But the file in question is located in /tmp/makepkg/distccd-alarm/armv5.install since this is where the build process is done.

This might also related: i get these errors: "distccd[540] (dcc_check_compiler_whitelist) CRITICAL! armv7l-unknown-linux-gnueabihf-g++ not in /usr/lib/distcc whitelist." I saw your post here and i don't have these sym links on my system (i built the package by removing the install="$1.install" entry :P )

kprkpr commented on 2018-05-14 14:42

+mickael9 The link works again, but I will update with versioned one, that seems better option now

mickael9 commented on 2018-05-09 18:17

The download links are dead, they seem to be versioned now:

graysky commented on 2017-12-12 08:13

@rcf - Yes, it looks like they repacked without bumping the pkgver or pkgrel :/

rcf commented on 2017-12-12 04:01

The MD5s have changed (as seen on the wiki):

md5sums=('9cfadee932063e8341c14036c5c10e90' '12ae25e2529387fe7a038c24429bad81' 'b2abddab4c216150b3be8854d6b4afd6' 'ceed447e8789f7579e7b99a394c02a82' '48b71f968488a4322a715d633eb6879e' '7e664f8ce386f467f1a7381c9ac3c06f')

graysky commented on 2017-11-09 23:42

@FallenSnow - Builds fine for me... just slow downloads from upstream. I will say that I have always experienced problems removing ./src due to some permissions within the upstream files... removing it requires root.

FallenSnow commented on 2017-11-09 17:09

I'm getting a bunch of `Can't unlink already-existing object errors`. Don't know if this is something on my side or not...

==> Extracting sources...
-> Extracting x-tools-7.2.0-1-20170910.tar.xz with bsdtar
x-tools/arm-unknown-linux-gnueabi/build.log.bz2: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/ccomplex: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/future: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/codecvt: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/ios: Can't unlink already-existing object
x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include/c++/7.2.0/typeinfo: Can't unlink already-existing object

graysky commented on 2017-09-17 14:22

@WarheadsSE - Fixed the spelling typo. I didn't push a PR to you for a few reasons:

1) You write out to /usr/local which violates the packaging standards[1].
2) Your configs contain specific variables not unique to all systems/LANS (ie --allow and --port lines for each subarch).
3) My improvised method to keep book on the toolchain version might offend a real developer.
4) I assumed (perhaps incorrectly) that the changes in 1 and 2 were part of the Arch ARM build system or something similar so you would just reject the PR.

I am happy to send one though if you wish.


WarheadsSE commented on 2017-09-17 14:11

Silly question: why not MR these changes to my original repo?

Also, the English word is `Contributor`

graysky commented on 2017-09-15 20:02

Thanks for the feedback, all. I got the md5sum issue sorted... upstream simply did not create a corresponding directory for the 7.2.0-1 release it seems. From now on, I will record the date stamp in the tarball to avoid confusion. Please try this release.