Package Details: rsyslog 8.2410.0-1

Git Clone URL: https://aur.archlinux.org/rsyslog.git (read-only, click to copy)
Package Base: rsyslog
Description: An enhanced multi-threaded syslogd with a focus on security and reliability
Upstream URL: http://www.rsyslog.com/
Licenses: GPL3
Submitter: Barthalion
Maintainer: fordprefect
Last Packager: fordprefect
Votes: 19
Popularity: 0.124238
First Submitted: 2018-01-07 12:53 (UTC)
Last Updated: 2024-11-17 13:55 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

dreieck commented on 2024-10-14 11:29 (UTC)

The license identifiers are not SPDX compliant, this should be changed: 

rsyslog E: GPL3 is not a valid SPDX license identifier. See https://spdx.org/licenses/ for valid identifiers, or prefix the identifier with 'LicenseRef-', if it is custom.

Regards and thanks for the package!

harre commented on 2024-07-05 16:09 (UTC)

You should have bumped the pkgrel when doing the build-fix as yay didn't pick up that the package had been updated.

https://wiki.archlinux.org/title/PKGBUILD

I did have to do:

rm -fr ~/.cache/yay/rsyslog

To be able to build the package

fordprefect commented on 2024-07-04 20:30 (UTC)

Dropped the install and the bogus spool directory. I think this was old cruft only.

thx1138 commented on 2024-07-04 20:27 (UTC)

@xiota Aha! Thanks. Still, rsyslog.install is not anywhere otherwise here linked from the AUR. It is not a file listed under "Sources" on this page.

By the way, I do not have a /var/spool/rsyslog directory, and there do not seem to be any consequences. man 5 rsyslog.conf and man 8 rsyslogd make no mention of a directory /var/spool/rsyslog. There is also no mention of a /var/spool/rsyslog in any of the sample .conf files in the build source.

Any idea why this package would want to install a /var/spool/rsyslog? Maybe the reference to /var/spool/rsyslog should be removed entirely?

fordprefect commented on 2024-07-04 20:07 (UTC) (edited on 2024-07-04 20:07 (UTC) by fordprefect)

Thanks everyone for looking into this. I tried to incorporate everything into the package, but could only do a few quick tests. Please report back if any issues remain.

xiota commented on 2024-07-03 22:17 (UTC)

@thx1138 File is there: rsyslog.install

That said, all it does it print: Create /var/spool/rsyslog directory before starting rsyslog

The .install file should be removed and following added to PKGBUILD:

options=(emptydirs)
package() {
  # ...
  install -dm755 "$pkgdir/var/spool/rsyslog"
}

thx1138 commented on 2024-07-03 21:48 (UTC) (edited on 2024-07-03 21:51 (UTC) by thx1138)

On a tangent - why is the line install=$pkgname.install in the PKGBUILD file? I don't find any such file "rsyslog.install", and makepkg simply complains without it: ==> ERROR: install file (rsyslog.install) does not exist or is not a regular file.

Easy enough to "comment it out".

And, to save others the trouble, after adding to source and sha256sums:

prepare() {
  cd $pkgname-$pkgver
  patch -p1 -i ../5406.patch
}

Thanks Lenny!

Lenny commented on 2024-07-03 13:33 (UTC)

There is a patch already available

https://patch-diff.githubusercontent.com/raw/rsyslog/rsyslog/pull/5406.patch

xiota commented on 2024-07-02 19:46 (UTC) (edited on 2024-07-02 19:50 (UTC) by xiota)

The libgcrypt-config command was intentionally removed. It most likely will not be back. Debian maintainers knew about it for at least a year. The (gcrypt) repo has commits removing it.

Someone familiar with the build system could probably update (rsyslog) in a few minutes.

fordprefect commented on 2024-07-02 18:56 (UTC)

But is it permanently gone or just an issue that will be resolved in a future release? The former would require a bug fix by rsyslog, the latter just a workaround or a word of caution for package users. Thanks for reporting upstream!

1 2 3 4 5 6 Next › Last »