Description: Bug related to the font handling under Hyperbola. xfontsel doesn’t list the PCF bitmapped fonts, which are used for some legacy tools with Motif/Athena for instance. If you want to use a font with good coverage of symbols (misc fixed 10×20 iso10646-1) under DDD (for accented/non ASCII characters), you can’t, you are restricted to ASCII 9×15 fonts.
Additional info:
This error happens even if all -meta font meta-packages are installed.
$ hypervideo -F https://yewtu.be/watch?v=W5fFOECr3EI [youtube] W5fFOECr3EI: Downloading webpage
[youtube] W5fFOECr3EI: Downloading android player API JSON
[youtube] W5fFOECr3EI: Downloading player 11e3a4ec
WARNING: [youtube] nsig extraction failed: You may experience throttling for some formats
n = iXmUjcWoU-JB5WlM ; player = https://www.youtube.com/s/player/11e3a4ec/player_ias.vflset/en_US/base.js W5fFOECr3EI: Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/hypervideo_dl/extractor/youtube.py", line 2519, in _decrypt_nsig
self._player_cache[sig_id] = func(s)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/extractor/youtube.py", line 2551, in <lambda>
return lambda s: jsi.extract_function_from_code(*func_code)([s])
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 536, in resf
ret, should_abort = self.interpret_statement(stmt, var_stack)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 145, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 182, in interpret_expression
ret, should_abort = self.interpret_statement(try_expr, local_vars, allow_recursion - 1)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 145, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 182, in interpret_expression
ret, should_abort = self.interpret_statement(try_expr, local_vars, allow_recursion - 1)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 145, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 256, in interpret_expression
self.interpret_expression(sub_expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 326, in interpret_expression
left_val, should_abort = self.interpret_statement(
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 145, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 326, in interpret_expression
left_val, should_abort = self.interpret_statement(
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 145, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python3.8/site-packages/hypervideo_dl/jsinterp.py", line 464, in interpret_expression
raise ExtractorError('Unsupported JS expression %r' % expr)
hypervideo_dl.utils.ExtractorError: Unsupported JS expression ‘0⇐c[49]’; please report this issue on https://issues.hyperbola.info/ , filling out the appropriate issue template. Confirm you are on the latest version using pacman -Su
(caused by ExtractorError(”Unsupported JS expression ‘0⇐c[49]’; please report this issue on https://issues.hyperbola.info/ , filling out the appropriate issue template. Confirm you are on the latest version using pacman -Su”)); please report this issue on https://issues.hyperbola.info/ , filling out the appropriate issue template. Confirm you are on the latest version using pacman -Su
ERROR: [youtube] W5fFOECr3EI: Unable to extract uploader id; please report this issue on https://issues.hyperbola.info/ , filling out the appropriate issue template. Confirm you are on the latest version using pacman -Su
Description: Package xlsfonts is missing and should absolutely being added also within groups for ‘xenocara-apps’ and ‘xorg-apps’.
Description:
Additional info:
Note: needs a provide: bazaar
Steps to reproduce:
/sbin/openrc-run: bad interpreter: No such file or directory
I get this error whenever I try to start dhcpcd with sv /etc/runit/
And for sndiod I get this doing the same guide,
warning: sndiod: unable to open supervise/ok: file does not exist
Although rather ironically, If I type sndiod or dhcpcd into root, it works just fine.
Maybe its an FHS issue or possibly, I am screwing up? I am not sure. Feedback is welcome.
This is what I did:
=⇒ Add a service:
ln -s /etc/sv/<service> /var/service ==> Start/stop/restart a service: sv <start/stop/restart> <service>
more or less, I used this guide.
Description:
Additional info:
Steps to reproduce:
Hello,
When mounting an NFS share, I get a warning about missing idmpad.conf
rpc.idmapd: Skipping configuration file "/etc/idmapd.conf": No such file or directory 4341: * Stopping idmapd ...
Debian includes a default config file for idmap :
[General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs # set your own domain here, if id differs from FQDN minus hostname # Domain = localdomain [Mapping] Nobody-User = nobody Nobody-Group = nogroup
Description:
I saw errors in logs because fail2ban couldn’t find /usr/bin/sendmail, and discovered this:
[/etc/fail2ban] [0] $ grep /usr/bin/sendmail */* action.d/sendmail-buffered.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-buffered.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-buffered.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-buffered.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-common.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-common.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-geoip-lines.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-whois.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-whois-ipjailmatches.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-whois-ipmatches.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-whois-lines.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest> action.d/sendmail-whois-matches.conf: Fail2Ban" | /usr/bin/sendmail -f <sender> <dest>
Please, also check for other binaries with wrong locations
As of now, the solution is as simple as removing this line → https://git.hyperbola.info:50100/packages/community.git/tree/fail2ban/PKGBUILD#n79
Additional info:
* fail2ban-0.9.6-2.hyperbola3
Description:
Hyperbola has the following SPF implementations:
* libspf2
* perl-mail-spf
* perl-mail-spf-query
However, none of them work out of the box with postfix. There’s postfix-policyd-spf-perl, which uses one the current perl implementations (perl-mail-spf), takes no time to build and all the dependencies are already satisfied with Hyperbola’s packages
Here I made a PKGBUILD that’s compliant with the packaging standards:
pkgname=postfix-policyd-spf-perl
pkgver=2.011
pkgrel=1
pkgdesc='Postfix SPF policy engine, written in Perl'
arch=(i686 x86_64)
url='https://launchpad.net/postfix-policyd-spf-perl/'
license=(GPL)
depends=(perl-mail-spf perl-netaddr-ip perl-sys-hostname-long)
source=("https://launchpad.net/postfix-policyd-spf-perl/trunk/${pkgver}/+download/${pkgname}-${pkgver}.tar.gz"{,.asc})
sha512sums=('22fc00bf74912056a67e937a460ac1fd878f1cb1a3bfa7b19bc5f1e6bc1c36d815dcf8c945e818d242ed5e72a6295bb0e1569446e06b09aefb2842993b8016ba'
'SKIP')
validpgpkeys=(E7729BFFBE85400FEEEE23B178D7DEFB9AD59AF1) # Scott Kitterman
package() {
cd "${pkgname}-${pkgver}"
install -Dm755 "${pkgname}" "${pkgdir}/usr/libexec/postfix/${pkgname}"
install -Dm644 CHANGES INSTALL README -t "${pkgdir}/usr/share/doc/${pkgname}"
install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}
in the other hand, to give users the possibility of having more options, we could add pypolicyd-spf (AUR), which depends in pyspf (AUR) and other packages that Hyperbola has. In fact, ArchWiki talks about this implementation, but this might not be relevant.
dmcrypt service can’t umount luks filesystem on reboot/shutdown, device or resource busy:
* Removing dm-crypt mappings * foobar-pv device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy device-mapper: remove ioctl on foobar-pv failed: Device or resource busy Device foobar-pv is still in use [ !! ]