Package Details: osslsigncode 2.9-1

Git Clone URL: https://aur.archlinux.org/osslsigncode.git (read-only, click to copy)
Package Base: osslsigncode
Description: OpenSSL based Authenticode signing for PE/MSI/Java CAB files
Upstream URL: https://github.com/mtrojnar/osslsigncode
Licenses: GPL
Submitter: mbunkus
Maintainer: mbunkus
Last Packager: mbunkus
Votes: 10
Popularity: 0.010268
First Submitted: 2016-01-10 13:03 (UTC)
Last Updated: 2024-07-19 07:32 (UTC)

Latest Comments

1 2 3 Next › Last »

kusoneko commented on 2024-03-26 11:56 (UTC) (edited on 2024-03-26 11:57 (UTC) by kusoneko)

Hello,

The latest version, 2.8, does not compiles in a clean chroot due to it missing python. Please add it to the depends array.

Thank you.

lacsaP commented on 2024-01-12 13:39 (UTC) (edited on 2024-01-12 14:17 (UTC) by lacsaP)

hi,

I've just built osslsigncode and realized that using a proxy to download the sources interferes with the tests carried out at the end of the build.

adding unset http_proxy at the start of prepare() function avoids interference.

regards, lacsaP.

mbunkus commented on 2023-12-22 09:56 (UTC)

The tests work just fine for me at the moment.

With the upload of 2.7-1 I also fixed the issue of having that server_http.py process lying around after the tests. It's due to a bug in upstream that I reported here[1] and that's been fixed since. I apply a similar fix within the PKGBUILD until the next release comes out.

If tests other than the "stop_server" one are failing, I cannot really help you with those. They work fine on my end. Maybe try building from the git master (it's dead simple) & report resulting test failure issues upstream. Also look at the log file the tests produce ("Testing/Temporary/LastTest.log" in the build directory) for possible reasons.

[1] https://github.com/mtrojnar/osslsigncode/issues/331

crunk1 commented on 2023-12-22 05:46 (UTC)

As mbunkus pointed out on 2023-11-10, I'm seeing CTest failures in 2.7-1. Tests 108-147, 153-157 fail.

mbunkus commented on 2023-11-10 08:21 (UTC)

You'll have to file an issue with the upstream. I only execute the totally normal ctest Release command during the check phase. If that one leaves processes around, it's a bug in their cmake setup, I think.

MS-DTYP commented on 2023-11-09 23:18 (UTC)

I've discovered this in my processlist after yay -S osslsigncode:

/usr/bin/python3.11 /home/test/.cache/yay/osslsigncode/src/build/Testing/server_http.py

mbunkus commented on 2023-07-24 08:59 (UTC)

Good point & done.

grawity commented on 2023-07-24 04:37 (UTC)

Not really an issue but I believe libfaketime should be only a checkdepends, not a makedepend (for correctness and for those who yolo it with --nocheck)

ziltoid commented on 2023-07-21 16:15 (UTC)

Installing the libfaketime package solved the problem. Thank you very much for the help.

mbunkus commented on 2023-07-21 15:14 (UTC)

Judging from the cmake output it seems like it's looking for a binary called faketime which you don't have. I do have it installed, it's coming from a package called libfaketime. It's quite possible the failing tests rely on said binary.

Please install the libfaketime package & try building osslsigncode again. If that fixes it, I'll add it to the makedepends.

1 2 3 Next › Last »