All Projects

Description:
Was wondering if there is any issue in terms of freedom andor privacy for the inclusion of elogind? Feedback will be apreciated Cheers.

this was recently implemented in gentoo.

source:
https://libregit.org/i3_relativism/elogind

references:
https://blogs.gentoo.org/leio/2019/03/26/gnome-3-30/#comment-9555 https://forums.gentoo.org/viewtopic-t-1094796.html

contact gentoo developer for help in implementation:
https://wiki.gentoo.org/wiki/User:Leio/TODO

The RFC 3461 would allow Hyperbola email accounts to request the destination email providers to point out if an email was successfully delivered.

It might not cover all transport failures, but at least has a chance to know in advance whether the message was delivered, discarding the events that happen afterwards (be it to the main inbox or subject to filtering rules such as moving to other folder, marking as spam or deleted after receipt).

“appmenu-qt4”[0][2] is a deprecated package (release in 2012)[1] and use qt4 unsupported/non-lts software[3], but “appmenu-qt5” not contains any release source code[2]

$ pacman -Si appmenu-qt4
Repository : community
Name : appmenu-qt4
Version : 0.2.6-1
Description : Export Qt4 applications menus over D-Bus
Architecture : x86_64
URL : https://launchpad.net/appmenu-qt Licenses : GPL Groups : None
Provides : None
Depends On : libdbusmenu-qt4
Optional Deps : None
Conflicts With : appmenu-qt
Replaces : appmenu-qt
Download Size : 16.55 KiB
Installed Size : 48.00 KiB
Packager : Antonio Rojas arojas@archlinux.org Build Date : Tue 28 Feb 2017 05:59:31 AM -03
Validated By : MD5 Sum SHA-256 Sum Signature

[0]:https://launchpad.net/appmenu-qt (qt4)
[1]:https://launchpad.net/appmenu-qt/+download [2]:https://launchpad.net/appmenu-qt5 [3]:https://en.wikipedia.org/wiki/Qt_5.6_LTS

Create hypertools to replace libretools package for HyperbolaBSD and GNU/Linux

It’s long period to develop this package.
For now, a systemd-nspawn wrapper is being developed for “libretools”[0]

[0]:https://issues.hyperbola.info/index.php?do=details&task_id=86

Add “nut” package.

Useful for uninterruptible power supplies, power distribution units, solar controllers and servers power supply units.

This is a GnuPG-like unix program for encryption and signing that uses only quantum-computer-resistant algorithms:

  McEliece cryptosystem (compact QC-MDPC variant) for encryption
  Hash-based Merkle tree algorithm (FMTSeq variant) for digital signatures

Codecrypt is free software. The code is licensed under terms of LGPL3 in a good hope that it will make combinations with other tools easier.

I have noticed that the version of scribus that is available in hyperbola does not have the option of spelling correction and by references of the official scribus channel indicate that scribus has to be built with hunspell. I do not understand how that is done, I just need to be able to correct spelling from scribus.

Description: As mentioned in Bug #18, our VLC plugin was not maintained in some time and the deprecated addon was removed. However, upstream is actively working on the plugin as per: https://code.videolan.org/videolan/npapi-vlc/tree/master

We should build this from source and re-package.

Description:

lsusb does not resolve device names from /var/lib/usbutils/usb.ids

The same thing as described here: https://unix.stackexchange.com/questions/220759/lsusb-doesnt-list-device-names

Description:

• Fix package name to erlang-headless that is the correct name for packages without graphical user interface support. nox suffix is incorrect because Hyperbola supports Wayland too, not only X.Org.

Additional info:
* package version(s)

• 19.3-3

* config and/or log files etc.

Steps to reproduce:

• None

Description:

• Fix package name to qbittorrent-headless that is the correct name for packages without graphical user interface support. nox suffix is incorrect because Hyperbola supports Wayland too, not only X.Org.

Additional info:
* package version(s)

• 3.3.11-1

* config and/or log files etc.

Steps to reproduce:

• None

Description:

crystal build src/invidious.cr –release

Error in src/invidious.cr:19: while requiring "kemal"

require "kemal"
^

in lib/kemal/src/kemal.cr:4: while requiring "./kemal/*"

require "./kemal/*"
^

in lib/kemal/src/kemal/config.cr:26: expanding macro

    property static_headers : (HTTP::Server::Response, String, File::Info -> Void)?
    ^~~~~~~~

in lib/kemal/src/kemal/config.cr:26: expanding macro

    property static_headers : (HTTP::Server::Response, String, File::Info -> Void)?
    ^

in macro 'property' expanded macro: macro_48177600:567, line 4:

   1.       
   2.         
   3.           
>  4.             @static_headers : (HTTP::Server::Response, String, File::Info -> Void) | ::Nil
   5. 
   6.             def static_headers : (HTTP::Server::Response, String, File::Info -> Void) | ::Nil
   7.               @static_headers
   8.             end
   9. 
  10.             def static_headers=(@static_headers : (HTTP::Server::Response, String, File::Info -> Void) | ::Nil)
  11.             end
  12.           
  13.         
  14.       
  15.     

undefined constant File::Info

Additional info:
* package version(s)

Crystal 0.22.0 (2017-04-22) LLVM 4.0.0

Steps to reproduce:

Description: opmsg is a replacement for gpg which can encrypt/sign/verify your mails or create/verify detached signatures of local files. Even though the opmsg output looks similar, the concept is entirely different.

Additional info:
https://aur.archlinux.org/packages/opmsg/

Cinnamon currently does not support elogind, and depends on systemd. A patch is needed to fix this issue.

http://scidvspc.sourceforge.net/

«Unlike most chess engines, Stockfish is open source (GPL license). That means you can read the code, modify it, contribute back, and even use it in your own projects.» I do not know if it is libre. If it is, together with Scid, Hyperbola is one step closer for every chess lover out there who also loves freedom!
https://stockfishchess.org/

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

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

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

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

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)

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

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

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

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

This package contains vague terminology “Open Source”:

extra/libical 2.0.0-2
    An open source reference implementation of the icalendar data type and serialization format

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 reference implementation of the icalendar data type and serialization format

This package contains vague terminology “Open Source”:

extra/liblouis 3.0.0-2
    Open-source braille translator and back-translator

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 braille translator and back-translator

This package contains vague terminology “Open Source”:

extra/libofa 0.9.3-6
    An open-source audio fingerprint by MusicIP

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 audio fingerprint by MusicIP

This package contains vague terminology “Open Source”:

extra/libomxil-bellagio 0.9.3-1
    An opensource implementation of the OpenMAX Integration Layer 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 OpenMAX Integration Layer API

This package contains vague terminology “Open Source”:

extra/libupnp 1.6.21-1
    Portable Open Source UPnP Development Kit

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 UPnP Development Kit

This package contains vague terminology “Open Source”:

extra/mlt 6.4.1-6
    An open source multimedia framework

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 multimedia framework

This package contains vague terminology “Open Source”:

extra/mlt-python-bindings 6.4.1-6
    An open source multimedia framework

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 multimedia framework

This package contains vague terminology “Open Source”:

extra/opencore-amr 0.1.5-1
    Open source implementation of the Adaptive Multi Rate (AMR) speech 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.

extra/opencore-amr 0.1.5-1
    Free software implementation of the Adaptive Multi Rate (AMR) speech codec

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

This package contains vague terminology “Open Source”:

extra/openjpeg2 2.1.2-2
    An open source JPEG 2000 codec, version 2.1.2

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, version 2.1.2

This package contains vague terminology “Open Source”:

extra/sofia-sip 1.12.11-3
    An open-source SIP User-Agent 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.

A free-software SIP User-Agent library

This package contains vague terminology “Open Source”:

extra/swt 4.6.2-3
    An open source widget toolkit for 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.

A free software widget toolkit for Java

This package contains vague terminology “Open Source”:

extra/tomcat7 7.0.76-1
    Open source implementation of the Java Servlet 3.0 and JavaServer Pages 2.2 technologies

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 the Java Servlet 3.0 and JavaServer Pages 2.2 technologies

This package contains vague terminology “Open Source”:

extra/tomcat8 8.0.42-1
    Open source implementation of the Java Servlet 3.1 and JavaServer Pages 2.3 technologies

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 the Java Servlet 3.1 and JavaServer Pages 2.3 technologies

This package contains vague terminology “Open Source”:

extra/unixodbc 2.3.4-2
    ODBC is an open specification for providing application developers with a predictable API with which to access Data 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.

ODBC is a free specification for providing application developers with a predictable API with which to access Data Sources

This package contains vague terminology “Open Source”:

extra/wildmidi 0.4.0-1
    Open Source MIDI Synthesizer

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 MIDI Synthesizer

This package contains vague terminology “Open Source”:

extra/x265 2.4-1
    Open Source H265/HEVC video encoder

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 H265/HEVC video encoder

This package contains vague terminology “Open Source”:

extra/xapian-core 1:1.4.2-1
    Open source search engine 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.

Free software search engine library.

This package contains vague terminology “Open Source”:

extra/xsd 4.0.0-2
    An open-source, cross-platform W3C XML Schema to C++ data binding compiler

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, cross-platform W3C XML Schema to C++ data binding compiler

This package contains vague terminology “Open Source”:

extra/xvidcore 1.3.4-1 [installed]
    XviD is an open source MPEG-4 video 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.

XviD is a free software MPEG-4 video codec

This package contains vague terminology “Open Source”:

community/beignet 1.3.1-2
    An open source OpenCL implementation for Intel IvyBridge+ iGPUs

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 OpenCL implementation for Intel IvyBridge+ iGPUs

This package contains vague terminology “Open Source”:

community/bzrtp 1.0.5-1
    Opensource implementation of ZRTP keys exchange protocol

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 ZRTP keys exchange protocol

This package contains vague terminology “Open Source”:

community/cimg 1.7.1-1
    Open-source C++ toolkit for image processing

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 C++ toolkit for image processing

This package contains vague terminology “Open Source”:

community/displaycal 3.2.4.0-1
    Open Source Display Calibration and Characterization powered by Argyll CMS (Formerly known as dispcalGUI)

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 Display Calibration and Characterization powered by Argyll CMS (Formerly known as dispcalGUI)

This package contains vague terminology “Open Source”:

community/dokuwiki 20170219_b-1
    Simple to use and highly versatile Open Source wiki software

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.

Simple to use and highly versatile free wiki software