warheadsse/pkgs

Arch PKGBUILDs for various items, may or may not be ARM only.

pkgs's Issues

the md5sums in distccd-alarm's PKGBUILD are out of date

linux-drm-intel-nightly: install: does it use the correct kernel?!

I came across https://github.com/WarheadsSE/PKGs/blob/master/linux-drm-intel-nightly/linux-drm-intel-nightly.install#L4-L12, and it looks like while the PKGBUILD would use pkgbase=linux-drm-intel-nightly for the kernel name (or derivations therefore), the install script would just use linux always?!

I have not tried to install it actually (yet).

MD5dums and distccmon

Md5sums had to be revised for the arm package. Also, is there a way to use distccmon-text with this package?

distcc-alarm: PKGBUILD has outdated md5s

The x-tools* md5sums in the distcc-alarm PKBUILD seem outdated.

md5sums=('1e289a79b68c6f1d4403ca767b426f5f'
         'c4619cc2542a6bf0df5005fcb2334af7'
         '930e6469480395e028b4eb4000659fde'
        'd1a7cb480f1090ce6a5a370cd5cec4cd'

The ones at https://archlinuxarm.org/wiki/Distcc_Cross-Compiling seem right:

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

Thanks

AUR

I like the idea of having a simple package for setting up distcc for a alarm device.
Could you up your packages on AUR? you could have a CI-server do that on push (e..g Travis)

distcc-alarm: PKGBUILD has outdated md5s

distccd-alarm seems to have outdated md5sumds in the PKGBUILD.

 md5sum x-tools*
13129e63d582c91bda6b76a23d7393b9  x-tools.tar.xz
a3ce73b9790056538dd77608dfd8b0f1  x-tools6h.tar.xz
162b43fdc0f2a3421c25aa45af77c916  x-tools7h.tar.xz
87a638a8409692b5ace07bd632ac20e9  x-tools8.tar.xz

From PKGBUILD:

a3a3f6f2866a06687e83677a74a9e75d # x-tools.tar.xz
1e3725360bc5600cb37e7cfdf88bc9e8 # x-tools6h.tar.xz
988ca5511f6ae080b8973ae7a42ded56 # x-tools7h.tar.xz
c459576a7145c421a1e9b5cfbbbbfd9a # x-tools8.tar.xz

The checksums on https://archlinuxarm.org/wiki/Distcc_Cross-Compiling also seem outdated.

MD5sums seem out of date

The files x-tools?.tar.xz fail to validate against the given md5-hashes.

Affected lines would be https://github.com/WarheadsSE/PKGs/blob/master/distccd-alarm/PKGBUILD#L30
+3 lines

Why are md5sums hardcoded in PKGBUILD

md5sums are hardcoded in the PKGBUILD file and it causes problems as soon as the files downloaded in the package build process change at the remote repository. The repository itself lacks pre-calculated and current (i.e. matching) md5sums for x-files, *.conf and *.service that could be used to compare with locally calculated md5sums. So, whoever produces new versions of the x-tools should also calculate md5sums and all md5sum problems would go away immediately, right?