ajakk
ajakk
According the the FHS, manpages go in /usr/share/man: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s11.html#usrsharemanManualPages But sshping currently installs its manpage to ${CMAKE_INSTALL_PREFIX}/man. One could Set CMAKE_INSTALL_PREFIX to /usr/share, but then one would get the sshping...
**Environment information** * Operating System: * Cutter version: * Obtained from: - [x] Built from source - [X] Downloaded release from Cutter website or GitHub - [ ] Distribution repository...
Bug: https://bugs.gentoo.org/863512 Signed-off-by: John Helmert III
Work in progress, this splits edk2-ovmf and seabios-bin into their own packages, to simplify the ebuilds by avoiding dealing with both source and binary builds in the same ebuilds. This...
Wire version: Version 3.26.2941 (running from flatpak, but also had the issue with native wire-desktop) Wire for web version: 2021.12.02.12.20 Operating system: Gentoo Linux Which antivirus software do you have...
For example, `net-misc/hylafaxplus` and `app-misc/physlock` both have a `` tag in their `metadata.xml`, but running `pquery --blame` and `pquery --one-attr maintainers` produces incongruent output: ```sh ~ $ pquery --blame net-misc/hylafaxplus...
It would be nice for the pkgcore API (and maybe even `pquery` or something on the command line) to support retrieving the packages in a repository which match a CPE...
Setting the columns to "unlimited" can be necessary when piping the output of bugz: ``` pybugz $ ./lbugz search pybugz * Info: Using [Gentoo] (https://bugs.gentoo.org/xmlrpc.cgi) * Info: Searching for bugs...
https://bugs.gentoo.org/704154 for example. The end of bugz output (where a link to a PR should exist): ``` [Comment #7] [email protected] : 20191229T17:25:57 ---------------------------------------------------------------------------------------------------------------------------------------- 0.5.2 is old. The latest release (0.6.1)...
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22371 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22850 An upstream report indicates these issues weren't actually fixed upstream: https://github.com/keystone-engine/keystone/issues/516 And the commit that ostensibly fixes the oss-fuzz issues don't seem at all relevant - it seems...