Search Criteria
Package Details: osslsigncode 2.15-2
Package Actions
| 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-3.0-or-later |
| Submitter: | mbunkus |
| Maintainer: | zen |
| Last Packager: | zen |
| Votes: | 16 |
| Popularity: | 0.91 |
| First Submitted: | 2016-01-10 13:03 (UTC) |
| Last Updated: | 2026-11-07 08:01 (UTC) |
Dependencies (6)
- curl (curl-gitAUR, curl-c-aresAUR)
- openssl (openssl-gitAUR, openssl-aegisAUR, openssl-staticAUR)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (make)
- libfaketime (check)
Required by (2)
- procertum-simplysign-desktop (optional)
- uur (optional)
Latest Comments
1 2 3 4 Next › Last »
marmis commented on 2026-11-14 01:55 (UTC)
By the way, this project has a man page now. It requires
pandocto build, though. https://github.com/mtrojnar/osslsigncode/blob/master/cmake/CMakeDoc.cmakemarmis commented on 2026-08-21 05:46 (UTC)
Hi, I just noticed that this package was not applying my LTO and debug flags.
Checking the PKGBUILD, I can see that it's caused first by the CMake configuration step in
prepare(). Note thatprepare()runs before/usr/share/makepkg/buildenv.shis applied, so theCFLAGSare just using the default ones.Then there's
CMAKE_BUILD_TYPE=Release, which could be replaced with eitherRelWithDebInfoorNoneso debug info is kept in the binaries. Note that makepkgCFLAGSalready include optimization, so, in general, you would wantNoneto respect them. However some packages do enable extra optimizations inReleaseorRelWithDebInfothat are either outside the realm ofCFLAGSor too non-standard to be enabled by default. Even withRelWithDebInfo, the defaultOPTIONS=(strip)in makepkg should lead to thin binaries in the final package, not so different as building inRelease(sometimes even smaller).See CMake package guidelines for more information.
zen commented on 2026-08-04 11:49 (UTC)
The AUR is down due to maintenance. git push has been disable. I cant update right now
dextercd commented on 2025-09-09 20:01 (UTC)
The tests run successfully now. Unfortunately, they're all simply skipped if you don't have the
python-cryptographypackage installed.I think it might be good to add this dependency to the
checkdependsarray.mbunkus commented on 2025-05-08 19:41 (UTC) (edited on 2025-05-08 19:51 (UTC) by mbunkus)
Yeah, I know. I currently am not motivated to analyze why the tests fail. I build with
--nocheckmyself; the resulting binary still does what it should do.If you or someone else wants to investigate & provide a fix, I'd really appreciate it.
Edit: I've found the issue[1] over on Github & have added more information. This doesn't seem to be a packaging issue per se, rather the official instructions how to run the tests might be wrong — or the test server start code might be buggy. Let's see how the issue shakes out.
[1] https://github.com/mtrojnar/osslsigncode/issues/433
crunk1 commented on 2025-05-08 19:25 (UTC) (edited on 2025-05-08 19:25 (UTC) by crunk1)
Test errors, missing test files. Seeing various errors like
gsus commented on 2025-03-26 15:34 (UTC) (edited on 2025-03-26 15:37 (UTC) by gsus)
Hello I have problems to pass the tests the python start_server.py script does not work.
On the logs I only get timeout.
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_proxyat the start ofprepare()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
1 2 3 4 Next › Last »