Robert Scheck

I like the proposal from @alvarezp in #62. Given I'm not sure where v3.1 would originate from (because I never saw a v3.0 so far), I am not sure what...

As per 0.3.0 the RIPE notice still exists (without passing `-v` to `rsync` or to `rpki-client`).

It gets silent once I pass `--no-motd` to Samba rsync. This however would require a code change like (a conditional) `args[i++] = "--no-motd";` at [main.c:719](https://github.com/kristapsdz/rpki-client/blob/master/main.c#L719), because `openrsync` doesn't seem to...

Confirming, flash-plugin-24.0.0.186-release.x86_64 also breaks with DRM here on CentOS 6.8 (which even ships the "original" hal-0.5.14-14.el6.x86_64), only downgrading to previous flash-plugin-11.2.202.644-release.x86_64 gets DRM related things working again.

I followed up @aristocrates, however on a CentOS 7. TL;DR: No DRM even with `libpepflashplayer.so` from ChromeOS That's what I did in detail, in case somebody cares or would like...

The regression was introduced by commit ca75f0085104d01bddb283a53bd9c6af6affbf92, because: ``` $ wget -q https://raw.githubusercontent.com/decalage2/oletools/f56062def0e72718201c50392d866c2cdbeb3b7e/oletools/mraptor.py -O mraptor-f56062d.py $ python3 mraptor-f56062d.py virusexcel.xlsm MacroRaptor 0.54dev14 - http://decalage.info/python/oletools This is work in progress, please report...

Good question…using `BUNDLED_LIBBSD=1` is likely the approach that the Fedora Packaging Guidelines enjoy the least. I've now asked the package maintainer about updating to [libbsd 0.11.x on all active Fedora...

CentOS 7 uses glibc, not uclibc-ng.

Has the patch mentioned by @ffontaine a chance to make it upstream? Or is upstream's recommendation to keep this patch downstream only? The patch solves the build failure and doesn't...

@dhendrix, so this means EPEL 7 should keep the patch mentioned by @ffontaine downstream only?