Package Base Details: distccd-alarm

Git Clone URL: (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 33
Popularity: 0.115104
First Submitted: 2017-09-14 21:47
Last Updated: 2020-11-06 21:34

Latest Comments

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

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.

lonaowna commented on 2017-09-15 12:49

Upstream link is broken, should be

gyscos commented on 2017-09-15 02:55

I confirm the md5s are incorrect.

Current PKGBUILD downloads file from this link:

The files there have these md5s:

1e289a79b68c6f1d4403ca767b426f5f x-tools-7.1.1-2.tar.xz
c4619cc2542a6bf0df5005fcb2334af7 x-tools6h-7.1.1-2.tar.xz
930e6469480395e028b4eb4000659fde x-tools7h-7.1.1-2.tar.xz
d1a7cb480f1090ce6a5a370cd5cec4cd x-tools8-7.1.1-2.tar.xz

graysky commented on 2017-09-14 23:48

Must be something on your end. The md5sums match those on their wiki[1]:

ARMv5te soft (1ade1ced844961a39e1e539fb04c1d65)
ARMv6l hard (bfe68188dae1512690d9981ff0ee7460)
ARMv7l hard (2ae08024566bd62249d4a83ee8d90124)
ARMv8 (79c3880c29bc8994d2136af553ca4d6d)


EDIT: I will say that download speeds now are horrible with some time outs. Recommend you delete the source tarballs and try again later.