To make this package compliant with Arch RFC 0016, could you please rewrite the license field as follows?
license=('Sleepycat')
see also: https://spdx.org/licenses/Sleepycat.html
| Git Clone URL: | https://aur.archlinux.org/db4.8.git (read-only, click to copy) |
|---|---|
| Package Base: | db4.8 |
| Description: | The Berkeley DB embedded database system 4.8 |
| Upstream URL: | http://www.oracle.com/technology/software/products/berkeley-db/index.html |
| Keywords: | db4.8 |
| Licenses: | custom |
| Submitter: | None |
| Maintainer: | pizzaman (Raansu) |
| Last Packager: | pizzaman |
| Votes: | 40 |
| Popularity: | 0.000000 |
| First Submitted: | 2010-11-26 09:45 (UTC) |
| Last Updated: | 2024-06-16 11:38 (UTC) |
To make this package compliant with Arch RFC 0016, could you please rewrite the license field as follows?
license=('Sleepycat')
see also: https://spdx.org/licenses/Sleepycat.html
Encountered the following error while compiling
checking for uintptr_t... yes
checking for socklen_t... yes
checking for ANSI C exit success/failure values... yes
checking for getopt optreset variable... no
checking for mutexes... UNIX/fcntl
configure: WARNING: NO SHARED LATCH IMPLEMENTATION FOUND FOR THIS PLATFORM.
configure: error: Unable to find a mutex implementation
==> ERROR: A failure occurred in build().
Aborting...
As suggested in https://github.com/bitcoin/bitcoin/issues/26860 added
CFLAGS=-Wno-error=implicit-function-declaration
Those files need change +w permission for apply the last patch:
repmgr/repmgr_net.c crypto/aes_method.c txn/txn.c
@pizzaman As was stated by Raansu, it was getting set automatically. But I wasn't sure where it was getting set.
@Raansu Thanks for fixing
Let me know of any issues!
Updated 04/22/2021
Added "format security" patch from https://git.sailfishos.org/mer-core/db4/blob/master/db-4.8.30-format-security.patch This deals with a change to the default makepkg.conf compile options as set by the Arch Linux maintainers that adds '-Werror=format-security' to the default compiling options.
Changed PKGBUILD to correctly identify the list of supported architectures this package can compile on. Theoretically this should compile and run on a wide range of processors so if I missed one let me know and I can add it in.
@pizzaman thank you for adding me back as a maintainer. The package has been updated.
@pizzaman I feel like I orphaned the package too soon. But I found out just recently that the default makepkg.conf file compiling options got changed recently. It seems like arch linux maintainers think " -Werror=format-security " is a good idea to have.
In the meantime I found a fix so db4.8 would compile with " -Werror=format-security " enabled from a Sailfish OS developer found here. https://git.sailfishos.org/mer-core/db4/blob/master/db-4.8.30-format-security.patch
Could you please add this?
@iohzrd I am wondering why are you compiling with the -Werror=format-security CFLAG?
@iohzrd I'm not 100% about this issue and I don't know how to best fix it.
Because of this I feel like I cannot support this package any further and I will orphaning this package so someone else can take over support.
Currently getting:
../dist/../repmgr/repmgr_net.c: In function ‘__repmgr_listen’:
../dist/../repmgr/repmgr_net.c:1334:2: error: format not a string literal and no format arguments [-Werror=format-security]
1334 | __db_err(env, ret, why);
| ^~~~~~~~
cc1: some warnings being treated as errors
make: *** [Makefile:1954: repmgr_net.lo] Error 1
==> ERROR: A failure occurred in build().
Aborting...
while trying to compile. Please advise.
Pinned Comments
Raansu commented on 2021-04-23 02:12 (UTC)
Let me know of any issues!
Updated 04/22/2021
Added "format security" patch from https://git.sailfishos.org/mer-core/db4/blob/master/db-4.8.30-format-security.patch This deals with a change to the default makepkg.conf compile options as set by the Arch Linux maintainers that adds '-Werror=format-security' to the default compiling options.
Changed PKGBUILD to correctly identify the list of supported architectures this package can compile on. Theoretically this should compile and run on a wide range of processors so if I missed one let me know and I can add it in.