Packages

This package contains vague terminology “Content”:

community/drupal 8.3.2-1
    A PHP-based content management platform

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Content”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

It would be good example to set to have proper description of packages without using “Content”.

eg.

A PHP-based web site revision system platform

This package contains vague terminology “Linux”:

community/clamtk 5.24-1
    Easy to use, light-weight, on-demand virus scanner 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.

Easy to use, light-weight, on-demand virus scanner for GNU/Linux systems

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

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

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)

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

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

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

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

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

Description:

community/ext3grep 0.10.2-4
    A tool to investigate an ext3 file system for deleted content and possibly recover it

Description is vague because of the word “content”. Why not say instead “data”?

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

Description:

community/webfs 1.21-13
    Simple and instant http server for mostly static content.

Description is vague because of the word “content”. Why not simply say “files” instead and be more specific.

Even empty files without data inside can be served.

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

Description:

community/openstreetmap-map-icons-svn 31588-1 [installed]
    A set of public domain licensed map icons for general OSM use

It is questionable if it is “Licensed” or dedicated.

See the file:
/usr/share/licenses/openstreetmap-map-icons/svg-twotone/LICENSE.txt

it does not matter if the file is named “LICENSE”, it could be also named anyhow else.

There must be reason why the organization Creative Commons is not using the word “License” in that text, and that is why I propose to simply say in description:

    A set of public domain map icons for general OSM use

community/autoconf-archive 1:2017.03.21-1
    A collection of freely re-usable Autoconf macros

See:
https://www.gnu.org/philosophy/words-to-avoid.html#FreelyAvailable

Don’t use “freely available software” as a synonym for “free software.” The terms are not equivalent. Software is “freely available” if anyone can easily get a copy. “Free software” is defined in terms of the freedom of users that have a copy of it. These are answers to different questions.

community/python-biopython 1.69-1
    Freely available Python tools for computational molecular biology

See:
https://www.gnu.org/philosophy/words-to-avoid.html#FreelyAvailable

Don’t use “freely available software” as a synonym for “free software.” The terms are not equivalent. Software is “freely available” if anyone can easily get a copy. “Free software” is defined in terms of the freedom of users that have a copy of it. These are answers to different questions.

community/python2-biopython 1.69-1
    Freely available Python tools for computational molecular biology

See:
https://www.gnu.org/philosophy/words-to-avoid.html#FreelyAvailable

Don’t use “freely available software” as a synonym for “free software.” The terms are not equivalent. Software is “freely available” if anyone can easily get a copy. “Free software” is defined in terms of the freedom of users that have a copy of it. These are answers to different questions.

Description:

community/man-pages-de 1.22-1
     German Linux man pages

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

Description:

community/man-pages-ru 4.08_2329_2272_20170321-2
     Russian Linux man pages

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

Description:

community/man-pages-zh_cn 1.6.3.1-1
     Simplified Chinese Linux man pages

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

Description:

community/man-pages-zh_tw 1.6.3.1-1
     Traditional Chinese Linux man pages

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Linux

Description:

• replace deprecated GNU Bazaar to Brezy for Canis Major

Additional info:

• bzr 2.7.0-2
• GNU Bazaar will be unmaintained (for now, there are only bug fixes)
• GNU Bazaar only supports Python 2.
• Python 2.7 is the end of the Python 2 line of development. [0]
• There never will be an official Python 2.8 release.
• Or use Tauthon (fork of Python 2.7) as dependency.

Note: It needs a provide: bazaar and brezy

Steps to reproduce:

• broken package

aqemu only lists GNU/Linux and GNU/Hurd. Since LibertyBSD is also free it should also be added.

Description: Per a user request and to better secure the kernel, we can embed the cryptsetup and ciphers in the kernel. This would mean rather than exposed modules, they are built-in to the kernel and ready to use even without an intramfs.

To be embedded: ciphers aes, twofish, serpent; sha256, sha512 - and the necessary modules (don’t forget the block modes xts, lvm and cryptsetup …)

Additionally, we could include USB Guard and any other features that meet our social contract and security outlook.

I know that upgrading Qt is not a trivial task, but would it be possible to do this anyway? Qt 5.8 has issues that other versions do not have. See for example the discussion here about Projecteur, a very useful tool. Hyperbola seems to be the only Linux distribution unable to run it, just because of Qt 5.8:

https://github.com/jahnf/Projecteur/issues/26

As even the support for GCC 7 is now ending with the release of version 7.5 (https://gcc.gnu.org/ml/gcc/2019-11/msg00099.html) I’d like to propose a renewal of the building-stack - which I think is also needed in time. Also a renewal of the glibc would be good at all!