|
Packages | Any | Feature Request | High | High | [cyrus-sasl-ldap] adapt package in accordance with the ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [cyrus-sasl-sql] adapt package in accordance with the H ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [python2-gpgme] adapt package in accordance with the Hy ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [ostree] adapt package in accordance with the Hyperbola ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [argon2] adapt package in accordance with the Hyperbola ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [postgresql] adapt package in accordance with the Hyper ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [postgresql-docs] adapt package in accordance with the ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Feature Request | High | High | [postgresql-libs] adapt package in accordance with the ... | Closed | |
Task Description
Adapt package in accordance with the Hyperbola Packaging Guidelines to follow the Hyperbola Social Contract .
|
|
Packages | Any | Bug Report | Medium | Medium | [minicom][openrc] error: failed to commit transaction ( ... | Closed | |
Task Description
minicom conflicts against openrc package since both contains a file with the same name (/usr/bin/runscript)
# pacman -S minicom
resolving dependencies...
looking for conflicting packages...
Packages (1) minicom-2.7.1-1
Total Download Size: 0.18 MiB
Total Installed Size: 0.71 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
minicom-2.7.1-1-x86_64 186.7 KiB 170K/s 00:01 [########################################################] 100%
(1/1) checking keys in keyring [########################################################] 100%
(1/1) checking package integrity [########################################################] 100%
(1/1) loading package files [########################################################] 100%
(1/1) checking for file conflicts [########################################################] 100%
error: failed to commit transaction (conflicting files)
minicom: /usr/bin/runscript exists in filesystem
Errors occurred, no packages were upgraded.
$ pacman -Qo /usr/bin/runscript
/usr/bin/runscript is owned by openrc 0.28-8
|
|
Packages | Any | Bug Report | Medium | Medium | [cdemu-daemon] error: failed to prepare transaction (co ... | Closed | |
Task Description
cdemu-daemon requires a specific version of vhba-module. Since we are using vhba-module-lts with vhba-module in provides array but without a specific version, it generates the issue. Removing that specific version solves it.
# pacman -S cdemu-daemon
resolving dependencies...
warning: cannot resolve "vhba-module>=20140629", a dependency of "cdemu-daemon"
:: The following package cannot be upgraded due to unresolvable dependencies:
cdemu-daemon
:: Do you want to skip the above package for this upgrade? [y/N]
error: failed to prepare transaction (could not satisfy dependencies)
:: cdemu-daemon: requires vhba-module>=20140629
|
|
Packages | Any | Feature Request | Medium | Medium | [gdm] needs OpenRC init script | Closed | |
Task Description
$ pacman -Si gdm
Repository : extra
Name : gdm
Version : 3.24.1-1.hyperbola3
Description : Display manager and login screen, with elogind support
Architecture : x86_64
URL : https://wiki.gnome.org/Projects/GDM
Licenses : GPL
Groups : gnome
Provides : None
Depends On : gnome-shell gnome-session upower xorg-xrdb xorg-server xorg-server-xwayland xorg-xhost libgdm
Optional Deps : fprintd: fingerprint authentication
Conflicts With : None
Replaces : None
Download Size : 609.31 KiB
Installed Size : 5340.00 KiB
Packager : André Silva <emulatorman@hyperbola.info>
Build Date : Thu 14 Sep 2017 12:44:54 AM -03
Validated By : MD5 Sum SHA-256 Sum Signature
|
|
Packages | Any | Implementation Request | Medium | Medium | [wine-stable] add package | Closed | |
Task Description
Add Wine stable version (2.x) as default Wine package.
|
|
Packages | Any | Feature Request | Medium | Medium | [glusterfs] needs OpenRC init script | Closed | |
Task Description
Contains systemd unit files:
/usr/lib/systemd/
/usr/lib/systemd/system/
/usr/lib/systemd/system/glusterd.service
/usr/lib/systemd/system/glustereventsd.service
/usr/lib/systemd/system/glusterfssharedstorage.service
/usr/lib/tmpfiles.d/
/usr/lib/tmpfiles.d/glusterfs.conf
$ pacman -Si glusterfs
Repository : community
Name : glusterfs
Version : 1:3.10.1-1
Description : Is a cluster file-system capable of scaling to several peta-bytes.
Architecture : x86_64
URL : http://www.gluster.org/
Licenses : GPL2 LGPL3
Groups : None
Provides : None
Depends On : fuse python2 libxml2 libaio liburcu attr which
Optional Deps : rpcbind: NFS
glib2: qemu-block
Conflicts With : None
Replaces : None
Download Size : 3.14 MiB
Installed Size : 14.80 MiB
Packager : Sergej Pupykin <pupykin.s+arch@gmail.com>
Build Date : Fri 07 Apr 2017 06:29:27 AM -03
Validated By : MD5 Sum SHA-256 Sum Signature
|
|
Packages | Any | Feature Request | Medium | Medium | [iperf3] needs OpenRC init script | Closed | |
Task Description
$ pacman -Si iperf3
Repository : community
Name : iperf3
Version : 3.1.7-1
Description : Internet Protocol bandwidth measuring tool
Architecture : x86_64
URL : https://github.com/esnet/iperf
Licenses : BSD
Groups : None
Provides : None
Depends On : glibc
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 62.46 KiB
Installed Size : 181.00 KiB
Packager : Timothy Redaelli <timothy.redaelli@gmail.com>
Build Date : Fri 10 Mar 2017 01:06:09 PM -03
Validated By : MD5 Sum SHA-256 Sum Signature
$ pacman -Ql iperf3
iperf3 /usr/
iperf3 /usr/bin/
iperf3 /usr/bin/iperf3
iperf3 /usr/include/
iperf3 /usr/include/iperf_api.h
iperf3 /usr/lib/
iperf3 /usr/lib/libiperf.so
iperf3 /usr/lib/libiperf.so.0
iperf3 /usr/lib/libiperf.so.0.0.0
iperf3 /usr/share/
iperf3 /usr/share/licenses/
iperf3 /usr/share/licenses/iperf3/
iperf3 /usr/share/licenses/iperf3/LICENSE
iperf3 /usr/share/man/
iperf3 /usr/share/man/man1/
iperf3 /usr/share/man/man1/iperf3.1.gz
iperf3 /usr/share/man/man3/
iperf3 /usr/share/man/man3/libiperf.3.gz
|
|
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 | [aiksaurus] vague terminology "Open Source" in descript ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/aiksaurus 1.2.1-5
A cross-platform, open-source thesaurus
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 cross-platform, free-software thesaurus
|
|
Packages | Any | Freedom Issue | Medium | Low | [assimp] vague terminology "Open Source" in description ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/assimp 3.3.1-1
Portable Open Source library to import various well-known 3D model formats in an uniform manner
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.
Portable Free Software library to import various well-known 3D model formats in an uniform manner
|
|
Packages | Any | Freedom Issue | Medium | Low | [cmake] vague terminology "Open Source" in description ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/cmake 3.8.0-1
A cross-platform open-source make system
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 cross-platform free-software make system
|
|
Packages | Any | Freedom Issue | Medium | Low | [gstreamer] vague terminology "Open Source" in descript ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/gstreamer 1.12.0-1
GStreamer open-source multimedia framework core library
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.
GStreamer free-software multimedia framework core library
|
|
Packages | Any | Freedom Issue | Medium | Low | [java-openjfx] vague terminology "Open Source" in descr ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/java-openjfx 8.u121-1
Java OpenJFX 8 client application platform (open-source implementation of JavaFX)
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.
Java OpenJFX 8 client application platform (free-software implementation of JavaFX)
|
|
Packages | Any | Freedom Issue | Medium | Low | [java-openjfx-doc] vague terminology "Open Source" in d ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/java-openjfx-doc 8.u121-1
Java OpenJFX 8 client application platform (open-source implementation of JavaFX) - documentation
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.
Java OpenJFX 8 client application platform (free-software implementation of JavaFX) - documentation
|
|
Packages | Any | Freedom Issue | Medium | Low | [java-openjfx-src] vague terminology "Open Source" in d ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/java-openjfx-src 8.u121-1
Java OpenJFX 8 client application platform (open-source implementation of JavaFX) - sources
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.
Java OpenJFX 8 client application platform (free-software implementation of JavaFX) - sources
|
|
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 | [kdegames-kigo] vague terminology "Open Source" in desc ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/kdegames-kigo 17.04.0-1 (kde-applications kdegames)
An open-source implementation of the popular Go game
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 implementation of the popular Go game
|
|
Packages | Any | Freedom Issue | Medium | Low | [libgdiplus] vague terminology "Open Source" in descrip ... | Closed | |
Task Description
This package contains vague terminology “Open Source”:
extra/libgdiplus 4.2-1
An Open Source Implementation of the GDI+ API
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 Implementation of the GDI+ API
|
|
Packages | Any | Freedom Issue | Medium | Low | [libical] vague terminology "Open Source" in descriptio ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [liblouis] vague terminology "Open Source" in descripti ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [libofa] vague terminology "Open Source" in description ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [libomxil-bellagio] vague terminology "Open Source" in ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [libupnp] vague terminology "Open Source" in descriptio ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [mlt] vague terminology "Open Source" in description of ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [mlt-python-bindings] vague terminology "Open Source" i ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [opencore-amr] vague terminology "Open Source" in descr ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openjdk7-src] vague terminology "Open Source" in descr ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openjdk8-src] vague terminology "Open Source" in descr ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openjpeg] vague terminology "Open Source" in descripti ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openjpeg2] vague terminology "Open Source" in descript ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openslp] vague terminology "Open Source" in descriptio ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [openssl-1.0] vague terminology "Open Source" in descri ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [rhino] vague terminology "Open Source" in description ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [rhino-javadoc] vague terminology "Open Source" in desc ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [sofia-sip] vague terminology "Open Source" in descript ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [swt] vague terminology "Open Source" in description of ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [tomcat7] vague terminology "Open Source" in descriptio ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [tomcat8] vague terminology "Open Source" in descriptio ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [unixodbc] vague terminology "Open Source" in descripti ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [wildmidi] vague terminology "Open Source" in descripti ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [x265] vague terminology "Open Source" in description o ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [xapian-core] vague terminology "Open Source" in descri ... | Closed | |
|
|
Packages | Any | Freedom Issue | Medium | Low | [xsd] vague terminology "Open Source" in description of ... | Closed | |
|
