|
Packages | Any | Freedom Issue | Medium | Low | [oprofile] vague terminology "Linux" in description of ... | Closed | |
Task Description
This package contains vague terminology “Linux”:
community/oprofile 1.1.0-3
System-wide profiler for Linux systems
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux
It would be good example to set to have proper description of packages without using “Linux” as operating system.
eg.
System-wide profiler for GNU/Linux systems
|
|
Packages | Any | Freedom Issue | Medium | Low | [shorewall] vague terminology "Linux" in description of ... | Closed | |
Task Description
This package contains vague terminology “Linux”:
community/shorewall 5.1.4-1
An iptables-based firewall for Linux systems
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux
It would be good example to set to have proper description of packages without using “Linux” as operating system.
eg.
An iptables-based firewall for GNU/Linux systems
|
|
Packages | Any | Freedom Issue | Medium | Low | [shorewall6] vague terminology "Linux" in description o ... | Closed | |
Task Description
This package contains vague terminology “Linux”:
community/shorewall6 5.1.4-1
An iptables-based firewall for Linux systems (with IPv6 support)
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Linux” as operating system, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux
It would be good example to set to have proper description of packages without using “Linux” as operating system.
eg.
An iptables-based firewall for GNU/Linux systems (with IPv6 support)
|
|
Packages | Any | Freedom Issue | Medium | Low | [gmtp] vague terminology "MP3 Player" in description of ... | Closed | |
Task Description
This package contains vague terminology “MP3 Player”:
community/gmtp 1.3.10-2
A simple MP3 player client for MTP based devices
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “MP3 Player”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#MP3Player
It would be good example to set to have proper description of packages without using “MP3 Player”.
eg.
A simple audio player client for MTP based devices
|
|
Packages | Any | Freedom Issue | Medium | Low | [kdb] vague terminology "Vendor" in description of pack ... | Closed | |
Task Description
This package contains vague terminology “Vendor”:
extra/kdb 3.0.1.1-2
A database connectivity and creation framework for various database vendors
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor
It would be good example to set to have proper description of packages without using “Vendor”.
eg.
A database connectivity and creation framework for various database suppliers
|
|
Packages | Any | Freedom Issue | Medium | Low | [publicsuffix-list] vague terminology "Vendor" in descr ... | Closed | |
Task Description
This package contains vague terminology “Vendor”:
extra/publicsuffix-list 20170118.560.45a2bf8-1
Cross-vendor public domain suffix database
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor
It would be good example to set to have proper description of packages without using “Vendor”.
eg.
Cross-supplier public domain suffix database
|
|
Packages | Any | Freedom Issue | Medium | Low | [glide] vague terminology "Vendor" in description of pa ... | Closed | |
Task Description
This package contains vague terminology “Vendor”:
community/glide 0.12.3-1
Dependency management and vendoring for Go projects
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor
It would be good example to set to have proper description of packages without using “Vendor”.
eg.
Dependency management and suppliering for Go projects
|
|
Packages | Any | Freedom Issue | Medium | Low | [ndiswrapper-dkms] vague terminology "Vendor" in descri ... | Closed | |
Task Description
This package contains vague terminology “Vendor”:
community/ndiswrapper-dkms 1.60.20160717-1
Module for NDIS (Windows Network Drivers) drivers supplied by vendors.Use with DKMS
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Vendor”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Vendor
It would be good example to set to have proper description of packages without using “Vendor”.
eg.
Module for NDIS (Windows Network Drivers) drivers.Use with DKMS
|
|
Packages | Any | Freedom Issue | Very High | Critical | [warsow] contains Steam support | Closed | |
Task Description
Warsow contains a library called steamlib which is built from the source. It’s useful only for Steam support which is nonfree software.
|
|
Packages | Any | Freedom Issue | Medium | Low | [java-rhino] vague terminology "Open Source" in descrip ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/java-rhino 1.7.7.1-1.hyperbola1
Open-source implementation of JavaScript written entirely in Java - JAR
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
Free-software implementation of JavaScript written entirely in Java - JAR
|
|
Packages | Any | Freedom Issue | Medium | Low | [openslp] vague terminology "Open Source" in descriptio ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/openslp 2.0.0-2.hyperbola1
Open-source implementation of Service Location Protocol, with OpenRC support
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
Free-software implementation of Service Location Protocol, with OpenRC support
|
|
Packages | Any | Freedom Issue | Medium | Low | [rhino] vague terminology "Open Source" in description ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/rhino 1.7.7.1-1
Open-source implementation of JavaScript written entirely in Java
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
Free-software implementation of JavaScript written entirely in Java
|
|
Packages | Any | Freedom Issue | Medium | Low | [rhino-javadoc] vague terminology "Open Source" in desc ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/rhino-javadoc 1.7.7.1-1.hyperbola1
Open-source implementation of JavaScript written entirely in Java - Javadoc
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
Free-software implementation of JavaScript written entirely in Java - Javadoc
|
|
Packages | Any | Freedom Issue | Medium | Low | [luminancehdr] vague terminology "Open Source" in descr ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
community/luminancehdr 2.5.0-2
Open source graphical user interface application that aims to provide a workflow for HDR imaging
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
Free software graphical user interface application that aims to provide a workflow for HDR imaging
|
|
Packages | Any | Freedom Issue | Medium | Low | [bogofilter] vague terminology "Commercial" in descript ... | Closed | |
Task Description
This package contains vague terminology “Commercial”:
extra/bogofilter 1.2.4-2.hyperbola2
A fast Bayesian spam filtering tool, without noncommercial files
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Commercial”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Commercial”.
eg.
A fast Bayesian spam filtering tool, without nonfree files
|
|
Packages | Any | Freedom Issue | Very High | Critical | [man-pages] contains nonfree POSIX manual pages | Closed | |
Task Description
Description:
Arch distributes a version of man-pages with manual pages from the POSIX standard. The man-pages project is permitted to distribute them and Andries Brouwer assumes that re-distribution by vendors is permitted as well. However, modification is definitively not allowed, hence this contribution by The Institute of Electrical and Electronics Engineers and The Open Group render the entire man-pages package nonfree. The way to solve it is remove all nonfree POSIX manual pages from man-pages package.
Additional info:
* package version(s)
* config and/or log files etc.
The Institute of Electrical and Electronics Engineers (IEEE) and
The Open Group, have given us permission to reprint portions of
their documentation.
In the following statement, the phrase ``this text'' refers to
portions of the system documentation.
Portions of this text are reprinted and reproduced in electronic form
from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
-- Portable Operating System Interface (POSIX), The Open Group Base
Specifications Issue 7, Copyright (C) 2013 by the Institute of Electri-
cal and Electronics Engineers, Inc and The Open Group. (This is
POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
event of any discrepancy between this version and the original IEEE and
The Open Group Standard, the original IEEE and The Open Group Standard
is the referee document. The original Standard can be obtained online
at http://www.unix.org/online.html .
This notice shall appear on any product containing this material.
Redistribution of this material is permitted so long as this notice and
the corresponding notices within each POSIX manual page are retained on
any distribution, and the nroff source is included. Modifications to
the text are permitted so long as any conflicts with the standard
are clearly marked as such in the text.
Steps to reproduce:
|
|
Packages | Any | Freedom Issue | Medium | Low | [openssl] vague terminology "Open Source" in descriptio ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
core/openssl 1.1.0.e-1
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
The Free Software toolkit for Secure Sockets Layer and Transport Layer Security
|
|
Packages | Any | Freedom Issue | Medium | Low | [openjdk7-src] vague terminology "Open Source" in descr ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [openjdk8-src] vague terminology "Open Source" in descr ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [openjpeg] vague terminology "Open Source" in descripti ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/openjpeg 1.5.2-1
An open source JPEG 2000 codec
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
A free software JPEG 2000 codec
|
|
Packages | Any | Freedom Issue | Medium | Low | [openssl-1.0] vague terminology "Open Source" in descri ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/openssl-1.0 1.0.2.k-3
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security
According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html
We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open
It would be good example to set to have proper description of packages without using “Open Source”.
eg.
The Free Software toolkit for Secure Sockets Layer and Transport Layer Security
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-sans-cn-fonts] vague terminology "Ope ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-sans-jp-fonts] vague terminology "Ope ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-sans-kr-fonts] vague terminology "Ope ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-sans-otc-fonts] vague terminology "Op ... | Closed | |
Task Description
no task description |
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-sans-tw-fonts] vague terminology "Ope ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-serif-cn-fonts] vague terminology "Op ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-serif-jp-fonts] vague terminology "Op ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-serif-kr-fonts] vague terminology "Op ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-serif-otc-fonts] vague terminology "O ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [adobe-source-han-serif-tw-fonts] vague terminology "Op ... | Closed | |
|
|
Software Development | General | Implementation Request | Very High | Critical | POWER (ppc64le) porting | Closed | |
|
|
Software Development | General | Implementation Request | Defer | Critical | RISC-V (riscv64) porting + multilib support | Closed | |
|
|
Services | Flyspray Branding | Implementation Request | Medium | Medium | Add Hyperbola branding to HyperTask | Closed | |
|
|
Software Development | HyperBK | Implementation Request | Very High | Critical | Develop a BSD descendant kernel for HyperbolaBSD | Closed | |
|
|
Software Development | General | Implementation Request | Very High | High | Port Iceape to UXP platform | Closed | |
|
|
Packages | Any | Implementation Request | Medium | Medium | [wine-stable] add package | Closed | |
|
|
Software Development | General | Implementation Request | Very High | High | Port Icedove to UXP platform | Closed | |
|
|
Packages | Any | Implementation Request | Medium | Low | [hunspell-pt-br] add new package | Closed | |
|
|
Packages | Any | Implementation Request | Medium | Low | [hyphen-pt-br] add new package | Closed | |
|
|
Software Development | General | Implementation Request | Medium | High | Develop GNU/HyperBK patchset | Closed | |
|
|
Software Development | Iceweasel-UXP | Implementation Request | Defer | Low | Swiftweasel-UXP theme for Iceweasel-UXP | Closed | |
|
|
Software Development | Icedove-UXP | Implementation Request | Defer | Low | Swiftdove-UXP theme for Icedove-UXP | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [libreoffice*] contains Google API keys | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [cutegram] only useful with Telegram service | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [libqtelegram-ae] only useful with Telegram service | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [telegram-qt] only useful with Telegram service | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [telegramqml] only useful with Telegram service | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [telepathy-morse] only useful with Telegram service | Closed | |
|
|
Packages | Any | Privacy Issue | Very High | Critical | [telepathy-kde-accounts-kcm] recommends Telepathy-Morse ... | Closed | |
|
