From nobody at parabola.nu Thu Jul 5 10:08:12 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 05 Jul 2018 10:08:12 -0000 Subject: [Dev] Orphan Libre package [calibre] marked out-of-date Message-ID: <20180705100812.1369.7835@proton.parabola.nu> patrick at bacha.dk wants to notify you that the following packages may be out-of-date: * calibre 3.20.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/calibre/ * calibre 3.20.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/calibre/ * calibre 3.20.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/calibre/ The user provided the following additional text: Is now 3.26.1: https://www.archlinux.org/packages/community/x86_64/calibre/ From nobody at parabola.nu Thu Jul 5 19:55:24 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 05 Jul 2018 19:55:24 -0000 Subject: [Dev] Orphan Libre package [uboot-mx6_cubox-i] marked out-of-date Message-ID: <20180705195524.1371.37696@proton.parabola.nu> robin.denhardteriksson at gmail.com wants to notify you that the following packages may be out-of-date: * uboot-mx6_cubox-i 2013.10-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/uboot-mx6_cubox-i/ The user provided the following additional text: ALARM has a newer version that is stable on my cubox i4x4 https://archlinuxarm.org/packages/armv7h/uboot-cubox-i The install script also addresses differences in device numbering, ie. root on /dev/mmcblk0 or /dev/mmcblk1 From nobody at parabola.nu Sat Jul 7 12:18:44 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:18:44 -0000 Subject: [Dev] Orphan Libre package [kio-extras] marked out-of-date Message-ID: <20180707121844.1368.70720@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * kio-extras 17.12.3-2.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kio-extras/ * kio-extras 17.12.3-2.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kio-extras/ * kio-extras 17.12.3-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio-extras/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://download.kde.org/stable/applications/18.04.2/src/kio-extras-18.04.2.tar.xz https://www.archlinux.org/packages/extra/x86_64/kio-extras/ From nobody at parabola.nu Sat Jul 7 12:21:57 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:21:57 -0000 Subject: [Dev] Orphan Libre package [ark] marked out-of-date Message-ID: <20180707122157.1371.46143@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * ark 17.12.3-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/ark/ * ark 17.12.3-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/ark/ * ark 18.04.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/ark/ * ark-debug 18.04.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/ark-debug/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: http://download.kde.org/stable/applications/18.04.2/src/ark-18.04.2.tar.xz https://www.archlinux.org/packages/extra/x86_64/ark/ From nobody at parabola.nu Sat Jul 7 12:27:08 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:27:08 -0000 Subject: [Dev] Orphan Libre package [khotkeys] marked out-of-date Message-ID: <20180707122708.1369.8143@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * khotkeys 5.12.4-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/khotkeys/ * khotkeys 5.12.4-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/khotkeys/ * khotkeys 5.12.4-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/khotkeys/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: http://download.kde.org/stable/plasma/5.13.2/khotkeys-5.13.2.tar.xz https://www.archlinux.org/packages/extra/x86_64/khotkeys/ From nobody at parabola.nu Sat Jul 7 12:28:26 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:28:26 -0000 Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date Message-ID: <20180707122826.1370.29593@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * kinfocenter 5.12.4-2.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kinfocenter/ * kinfocenter 5.12.4-2.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kinfocenter/ * kinfocenter 5.12.4-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kinfocenter/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: http://download.kde.org/stable/plasma/5.13.2/kinfocenter-5.13.2.tar.xz https://www.archlinux.org/packages/extra/x86_64/kinfocenter/ From nobody at parabola.nu Sat Jul 7 12:30:28 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:30:28 -0000 Subject: [Dev] Orphan Libre package [kio] marked out-of-date Message-ID: <20180707123028.1370.34101@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * kio 5.45.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kio/ * kio 5.45.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kio/ * kio 5.45.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: http://download.kde.org/stable/frameworks/5.47/kio-5.47.0.tar.xz https://www.archlinux.org/packages/extra/x86_64/kio/ From nobody at parabola.nu Sat Jul 7 12:32:26 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:32:26 -0000 Subject: [Dev] Orphan Libre package [libosinfo] marked out-of-date Message-ID: <20180707123226.1371.26599@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * libosinfo 1.1.0-1.parabola2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/libosinfo/ * libosinfo 1.1.0-1.parabola2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/libosinfo/ * libosinfo 1.1.0-1.parabola2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/libosinfo/ The user provided the following additional text: Thank you for maintaining this package! A new version of libosinfo 1.2.0 is available: https://libosinfo.org/download/ https://www.archlinux.org/packages/community/x86_64/libosinfo/ From nobody at parabola.nu Sat Jul 7 12:34:15 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:34:15 -0000 Subject: [Dev] Orphan Libre package [systemd] marked out-of-date Message-ID: <20180707123415.1368.98901@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * libsystemd 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/libsystemd/ * libsystemd 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/libsystemd/ * libsystemd 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/libsystemd/ * libsystemd-standalone 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/libsystemd-standalone/ * libsystemd-standalone 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/libsystemd-standalone/ * libsystemd-standalone 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/libsystemd-standalone/ * libudev 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/libudev/ * libudev 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/libudev/ * libudev 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/libudev/ * nss-myhostname 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/nss-myhostname/ * nss-myhostname 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/nss-myhostname/ * nss-myhostname 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nss-myhostname/ * nss-mymachines 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/nss-mymachines/ * nss-mymachines 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/nss-mymachines/ * nss-mymachines 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nss-mymachines/ * nss-resolve 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/nss-resolve/ * nss-resolve 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/nss-resolve/ * nss-resolve 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nss-resolve/ * nss-systemd 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/nss-systemd/ * nss-systemd 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/nss-systemd/ * nss-systemd 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nss-systemd/ * systemd 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/systemd/ * systemd 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/systemd/ * systemd 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/systemd/ * systemd-sysvcompat 238.76-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/systemd-sysvcompat/ * systemd-sysvcompat 238.76-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/systemd-sysvcompat/ * systemd-sysvcompat 238.76-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/systemd-sysvcompat/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://github.com/systemd/systemd/blob/v239/NEWS https://www.archlinux.org/packages/core/x86_64/systemd/ From nobody at parabola.nu Sat Jul 7 12:36:24 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 12:36:24 -0000 Subject: [Dev] Orphan Libre package [okular] marked out-of-date Message-ID: <20180707123624.1368.75781@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * okular 17.12.3-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/okular/ * okular 17.12.3-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/okular/ * okular 17.12.3-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/okular/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: http://download.kde.org/stable/applications/18.04.2/src/okular-18.04.2.tar.xz https://www.archlinux.org/packages/extra/x86_64/okular/ From nobody at parabola.nu Sat Jul 7 13:24:07 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 07 Jul 2018 13:24:07 -0000 Subject: [Dev] Orphan Pcr package [ttf-montserrat] marked out-of-date Message-ID: <20180707132407.1370.83079@proton.parabola.nu> nroof at protonmail.com wants to notify you that the following packages may be out-of-date: * ttf-montserrat 1.0-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/ttf-montserrat/ * ttf-montserrat 1.0-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/ttf-montserrat/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://aur.archlinux.org/packages/ttf-montserrat/ https://github.com/JulietaUla/Montserrat/releases From nobody at parabola.nu Sun Jul 8 16:21:08 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 08 Jul 2018 16:21:08 -0000 Subject: [Dev] Orphan Pcr package [i2p] marked out-of-date Message-ID: <20180708162108.1368.53039@proton.parabola.nu> gnu_stallman at protonmail.ch wants to notify you that the following packages may be out-of-date: * i2p 0.9.32-1 [pcr] (any): https://parabolagnulinux.org/packages/pcr/any/i2p/ The user provided the following additional text: 0.9.35 released (link needs i2p to get accessed) http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release From nobody at parabola.nu Sun Jul 8 20:51:02 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 08 Jul 2018 20:51:02 -0000 Subject: [Dev] Orphan Pcr package [guix] marked out-of-date Message-ID: <20180708205102.1368.28092@proton.parabola.nu> korobkov at vinterdalen.se wants to notify you that the following packages may be out-of-date: * guix 0.14.0-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/guix/ * guix 0.14.0-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/guix/ * guix 0.14.0-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/guix/ The user provided the following additional text: Please, update to the newly released 0.15 [0] [0] https://www.gnu.org/software/guix/blog/2018/gnu-guix-and-guixsd-0.15.0-released/ thanks in advance, Andrey From nobody at parabola.nu Mon Jul 9 16:52:20 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 09 Jul 2018 16:52:20 -0000 Subject: [Dev] Orphan Nonprism package [amarok] marked out-of-date Message-ID: <20180709165220.1368.58278@proton.parabola.nu> korobkov at vinterdalen.se wants to notify you that the following packages may be out-of-date: The user provided the following additional text: Please, update to 2.9.0 thanks, From nobody at parabola.nu Mon Jul 9 16:53:46 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 09 Jul 2018 16:53:46 -0000 Subject: [Dev] Orphan Kernels package [linux-libre-xtreme] marked out-of-date Message-ID: <20180709165346.1371.97066@proton.parabola.nu> korobkov at vinterdalen.se wants to notify you that the following packages may be out-of-date: The user provided the following additional text: Please, update to the latest 4.16.18 thanks in advance, Andrey From nobody at parabola.nu Tue Jul 10 22:50:06 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 10 Jul 2018 22:50:06 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20180710225006.1368.11203@proton.parabola.nu> brettg at posteo.net wants to notify you that the following packages may be out-of-date: * linux-libre 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ * linux-libre 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-docs 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ * linux-libre-docs 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ * linux-libre-headers 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: linux-libre is currently at 4.17.14 From megver83 at hyperbola.info Wed Jul 11 01:13:39 2018 From: megver83 at hyperbola.info (Megver83) Date: Tue, 10 Jul 2018 21:13:39 -0400 Subject: [Dev] Orphan Kernels package [linux-libre-xtreme] marked out-of-date In-Reply-To: References: Message-ID: <99c04193-02a8-dcc8-4ef8-94d6baf5e483@hyperbola.info> El 09/07/18 a las 12:53, Parabola Website Notification escribi?: > korobkov at vinterdalen.se wants to notify you that the following packages may be out-of-date: > > > > > The user provided the following additional text: > > Please, update to the latest 4.16.18 > > thanks in advance, > Andrey > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > Parabolaweb shows older versions of packages, Linux-libre-xtreme is on 4.17.3 -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: https://pixelfed.social/Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From brainblasted at disroot.org Wed Jul 11 01:47:13 2018 From: brainblasted at disroot.org (Christopher Davis) Date: Tue, 10 Jul 2018 21:47:13 -0400 Subject: [Dev] Fix plymouth "replaces" issue Message-ID: <1531273633.1211.0@disroot.org> Attached is a patch that fixes the plymouth bug at https://labs.parabola.nu/issues/1696. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-plymouth-replaces-issue.patch Type: text/x-patch Size: 1409 bytes Desc: not available URL: From brainblasted at disroot.org Wed Jul 11 01:48:37 2018 From: brainblasted at disroot.org (Christopher Davis) Date: Tue, 10 Jul 2018 21:48:37 -0400 Subject: [Dev] Fix plymouth "replaces" issue In-Reply-To: <1531273633.1211.0@disroot.org> References: <1531273633.1211.0@disroot.org> Message-ID: <1531273717.1211.1@disroot.org> Resending without HTML. On Tue, Jul 10, 2018 at 9:47 PM, Christopher Davis wrote: > Attached is a patch that fixes the plymouth bug at > https://labs.parabola.nu/issues/1696. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-plymouth-replaces-issue.patch Type: text/x-patch Size: 1409 bytes Desc: not available URL: From lukeshu at lukeshu.com Wed Jul 11 18:44:32 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 11 Jul 2018 14:44:32 -0400 Subject: [Dev] [PATCH] Fix plymouth "replaces" issue In-Reply-To: <1531273717.1211.1@disroot.org> References: <1531273633.1211.0@disroot.org> <1531273717.1211.1@disroot.org> Message-ID: <87y3eh1ujz.wl-lukeshu@lukeshu.com> On Tue, 10 Jul 2018 21:48:37 -0400, Christopher Davis wrote: > Previously plymouth-nosystemd would bug users on systems using plymouth > to replace plymotuh, even if the user was using systemd. This is because > plymouth-nosystemd erroneously included the "replaces" key when it > should have just set provides and conflicts. > > This commit removes the replaces key and bumps the pkgrel, > so that pacman will detect the change. > --- > pcr/plymouth-nosystemd/PKGBUILD | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/pcr/plymouth-nosystemd/PKGBUILD b/pcr/plymouth-nosystemd/PKGBUILD > index f4a3e679f..85c41e05a 100644 > --- a/pcr/plymouth-nosystemd/PKGBUILD > +++ b/pcr/plymouth-nosystemd/PKGBUILD > @@ -7,7 +7,7 @@ > pkgname=plymouth-nosystemd > _pkgname=plymouth > pkgver=0.9.2 > -pkgrel=1 > +pkgrel=2 > pkgdesc="A graphical boot splash screen with kernel mode-setting support for non systemd setups" > url="http://www.freedesktop.org/wiki/Software/Plymouth/" > > @@ -22,7 +22,6 @@ options=('!libtool' '!emptydirs') > > provides=('plymouth') > conflicts=('plymouth' 'plymouth-git') > -replaces=('plymouth' 'plymouth-git') > backup=('etc/plymouth/plymouthd.conf') > > source=("http://www.freedesktop.org/software/${_pkgname}/releases/${_pkgname}-${pkgver}.tar.bz2" Thanks! LGTM. However, I'm having trouble building the package because libremakepkg can't install the build deps because of a file conflict with libeudev and libudev that isn't declared. I guess I'll fight with that on my own. -- happy hacking, ~ Luke Shumaker From powers at copper.net Wed Jul 11 18:51:27 2018 From: powers at copper.net (Carl R. Powers) Date: Wed, 11 Jul 2018 12:51:27 -0600 Subject: [Dev] Issue 1838, OpenRC Install Media In-Reply-To: <270eb5c02bee1394f3fe458cff259e2354e932c7.camel@peers.community> References: <20180613191237.D255FE5C@m0117457.ppops.net> <270eb5c02bee1394f3fe458cff259e2354e932c7.camel@peers.community> Message-ID: On 06/13/2018 08:18 PM, bill-auger wrote: > this message contains not text but only an HTML part > > please re-send this message as raw text-only Updated.? Hope this looks better. lists.parabola.nu Using OpenRC install media (several releases), they used to work, but no longer. User creation fails - passwd & group files installed by base are incomplete (no users, lp, adm, etc).? Solved by copying passwd & group files from the install media after installing base.? This is I think the problem in Issue 1838. Installation of optional pkgs (lxde, etc) fails without installing anything. Able to stop screen scroll during failure.? Errors on "ath9k_htc-firmware" (only firmware package in list) not in target.? This package was recently replaced by a different named package in other distros but the target list has not been updated.? Solved by copying the installation scripts file, editing it to extract the package installation section and delete the missing package, then executing this new? pachage.sh script.? This was done before exiting the main install script by using chroot, or after rebooting if networking is working.? With these fixes, installation looks good. I now have one usable OpenRc installation to a usb stick after many failed attempts.? Will continue but hope to find updated install media sometime. As a side note - I tried the systemd lxde versions but they all fail with error message "sudoers directory not writeable" and unable to start networking on the openrc cli? version. Thanks for making these OpenRc versions available.? Lots of work, I know. Carl Powers Update:? I was elated to find the updated OpenRC LXDE install images after posting the above.? They semm to have fixed my user creation problem but not the installation of live image packages.? Tried both the from disc and from network modes with same results.? I was unable to modify the package script so again, resorted to manually installing all of the packages on the list.? Seems to work after fighting cups & hostname problems. Still trying to make sound work.? Have transferred this installation to 2 other computers using fsarchiver with mostly positive results. I would like to use the falkon browser but it depends on the qt5-webengine package which is not available.? Any chance of adding this the the repos? Thanks again. From freemor at freemor.ca Wed Jul 11 19:30:20 2018 From: freemor at freemor.ca (Freemor) Date: Wed, 11 Jul 2018 16:30:20 -0300 Subject: [Dev] Issue 1838, OpenRC Install Media In-Reply-To: References: <20180613191237.D255FE5C@m0117457.ppops.net> <270eb5c02bee1394f3fe458cff259e2354e932c7.camel@peers.community> Message-ID: <20180711193000.GA5142@freemor.ca> On Wed, Jul 11, 2018 at 12:51:27PM -0600, Carl R. Powers wrote: > I would like to use the falkon browser but it depends on the qt5-webengine > package which is not available.? Any chance of adding this the the repos? qt5-webengine has some freedom issues that are currently (I believe) being examined by the FSF. webengine is basically the guts of chrome. and as such have issues with google telemetry, among other things. It may get fixed at some point in the future but I would not expect to see anything requiring webengine in a libre distro any time soon. Sorry for the bad news. Freemor -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From bill-auger at peers.community Thu Jul 12 14:18:44 2018 From: bill-auger at peers.community (bill-auger) Date: Thu, 12 Jul 2018 10:18:44 -0400 Subject: [Dev] default redmine issue states Message-ID: the default state of a redmine issue is currently the extremely uninformative 'open' - it would be nice if these issue states were more semantic and used more optimally - i would like to propose that the default state of a redmine issue opened by a user to be 'unconfirmed' - then a privileged user could confirm the issue as a bug or freedom concern and set its state to 'confirmed' or 'in-progress' and assign it to the appropriate person, or set to 'info-needed' or 'invalid' if it can not be easily confirmed - it is not difficult or dangerous to manage these states - redmine makes it convenient to create, view, and manage these states via the web -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From freemor at freemor.ca Thu Jul 12 17:56:07 2018 From: freemor at freemor.ca (Freemor) Date: Thu, 12 Jul 2018 14:56:07 -0300 Subject: [Dev] submitting my SSH key Message-ID: <20180712175539.GC5142@freemor.ca> So I can further join the fun. :) -------------- next part -------------- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHuX5stLFkx33WSQ2mPLhhp6rv+cJOlY1IFUxIuMEzFs Key for Parabola work -------------- next part -------------- -----BEGIN PGP MESSAGE----- owEBwwI8/ZANAwAIARynGw3OwguzAax8Yg9pZF9wYXJhYm9sYS5wdWJbR5Jwc3No LWVkMjU1MTkgQUFBQUMzTnphQzFsWkRJMU5URTVBQUFBSUh1WDVzdExGa3gzM1dT UTJtUExoaHA2cnYrY0pPbFkxSUZVeEl1TUV6RnMgS2V5IGZvciBQYXJhYm9sYSB3 b3JrCokCMwQAAQgAHRYhBEaFzRmAm4P/AKxYyhynGw3OwguzBQJbR5JwAAoJEByn Gw3OwguzgRcP/0Rq7GMos+I8iMUCOEkdlEEmA3/XFng1eFqQIgTZKIObc7ECut3r /+gM6f2IrTg7WcJbAEaCxSQpj8jVzvxZqu66lsaCXOh5USoJu90hYZOhYL2g8Y8K HfsurbjJKlTWaw+mTMPOf/J2/Bq7fpWz3nt6enHbF9xbqRvflMFzRJEU+YbsgcR9 ApLyPxcdsvWKHA7pnhlY89mFjYXpUGjm8TLqkP+Ezq67eR0PQ67PKQyvMwlW0C5R hmB1h3D1r2OA3431TQ93bTx2CvfhLvIguksnq3DENjSL1w7dlXs/VXTMS9OvpUzn kk2Liz7E1+XOk8Jzq7STzu7cOZLM4/TP46+teOxA/UDpp9x2f2YhlAY1ezzeuFwJ ywnObRbDqlY6BIqUNihSWEEslSG2NqUBH5taNdSyiU29z66QBqvgZh/Rj8EHuV0G V23FMLcIQKMB85K2NWms0jw9alQBOuibbHD5XJYZ0YjrIU/+SIz/+R9GojMSG95G IuI3qH9af2EtDXfKi49IQ1l6DAt1+7s6TFf41ef+If/9mF92f3q4BJv5KYtSSZ6G gxEyvNFziFlVjT6SCj3DBMsdafitLoApw4sJhlzSppq8LU4TIKrsLmRIiZFoz7oD k99VuIWvit/y4BN8xYTX2667TwmKw6Djis3gVIwF6GxveprJnxcdfHwR =pFs1 -----END PGP MESSAGE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From bill-auger at peers.community Thu Jul 12 18:46:27 2018 From: bill-auger at peers.community (bill-auger) Date: Thu, 12 Jul 2018 14:46:27 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <20180712175539.GC5142@freemor.ca> References: <20180712175539.GC5142@freemor.ca> Message-ID: <112ffa46-12d0-b934-a9fb-de89aac6670b@peers.community> Freemor - can you write a bit about what your current talents or interests are and how they could fit into parabola the keys are mainly important for access to the servers, for example - i have seen you are very good a tech support and bug trouble-shooting - what are you most interested in doing? build and publish packages? administrate the servers? maintain the websites? triage bugs? all of the above? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From freemor at freemor.ca Thu Jul 12 20:06:17 2018 From: freemor at freemor.ca (Freemor) Date: Thu, 12 Jul 2018 17:06:17 -0300 Subject: [Dev] submitting my SSH key In-Reply-To: <112ffa46-12d0-b934-a9fb-de89aac6670b@peers.community> References: <20180712175539.GC5142@freemor.ca> <112ffa46-12d0-b934-a9fb-de89aac6670b@peers.community> Message-ID: <20180712200553.GD5142@freemor.ca> On Thu, Jul 12, 2018 at 02:46:27PM -0400, bill-auger wrote: > Freemor - > > can you write a bit about what your current talents or interests are and > how they could fit into parabola > > the keys are mainly important for access to the servers, for example - i > have seen you are very good a tech support and bug trouble-shooting - > what are you most interested in doing? > > build and publish packages? I'm still learning my way around libretools. But I've been makepkg'ing stuff from myself for some while so it shouldn't take too long. I'd really enjoy being able to take up some of the load for thing like out-of-date packages or those packages that just need a quick rebuild because some lib updates and it now needs to be rebuilt against the new ver on the lib. etc. As my skill and confidence improves I'd start branching into packing requests etc. > administrate the servers? I've run my own home server for years so sure > maintain the websites? that might be a bit of a learning curve. I do run my own site. but just lighttpd and flat html. So, I'd need time to get used to whatever lamp/Xamp set up is there. > triage bugs? Yes, as you know I enjoy doing so > all of the above? So yes, but with the caveat that I'll take things on when I'm sure I've got the skills not to accidentally make a major mess. Honestly I've been using Linux since the late 90's and computers since the late 70's so the hesitance isn't from a lack of skill but rather the fact that I've not been this deep at contributing to a large project like Parabola and so best to tread lightly till I get the lay of the land. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From brettg at posteo.net Thu Jul 12 20:46:54 2018 From: brettg at posteo.net (Brett Gilio) Date: Thu, 12 Jul 2018 15:46:54 -0500 Subject: [Dev] default redmine issue states In-Reply-To: References: Message-ID: Bill, So, the procedural order here would be for somebody to file a report with the "pending" or "unconfirmed" label. It would then be picked up by a privileged user to either reassign it a label, or confirm it and assign either themself or another privileged user to the task? If so, I think this sounds like a solid idea, assuming that the other privileged users are on-board. Brett Gilio brettg at posteo.net | bmg at member.fsf.org Free Software -- Free Society! On 07/12/2018 09:18 AM, bill-auger wrote: > the default state of a redmine issue is currently the extremely > uninformative 'open' - it would be nice if these issue states were more > semantic and used more optimally - i would like to propose that the > default state of a redmine issue opened by a user to be 'unconfirmed' - > then a privileged user could confirm the issue as a bug or freedom > concern and set its state to 'confirmed' or 'in-progress' and assign it > to the appropriate person, or set to 'info-needed' or 'invalid' if it > can not be easily confirmed - it is not difficult or dangerous to manage > these states - redmine makes it convenient to create, view, and manage > these states via the web > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > From brettg at posteo.net Thu Jul 12 20:54:48 2018 From: brettg at posteo.net (Brett Gilio) Date: Thu, 12 Jul 2018 15:54:48 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: <20180712175539.GC5142@freemor.ca> References: <20180712175539.GC5142@freemor.ca> Message-ID: <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> Would this be an appropriate time to refresh my keyring, then? Or should I wait? Brett Gilio brettg at posteo.net | bmg at member.fsf.org Free Software -- Free Society! On 07/12/2018 12:56 PM, Freemor wrote: > So I can further join the fun. :) > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > From isacdaavid at isacdaavid.info Thu Jul 12 21:19:28 2018 From: isacdaavid at isacdaavid.info (Isaac David) Date: Thu, 12 Jul 2018 16:19:28 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> Message-ID: <1531430368.1411.0@plebeian.isacdaavid.info> Brett Gilio wrote : > Would this be an appropriate time to refresh my keyring, then? Or > should I wait? every time is the right time for refreshing the keyring. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From brettg at posteo.net Thu Jul 12 21:23:48 2018 From: brettg at posteo.net (Brett Gilio) Date: Thu, 12 Jul 2018 16:23:48 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: <1531430368.1411.0@plebeian.isacdaavid.info> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> <1531430368.1411.0@plebeian.isacdaavid.info> Message-ID: <8cca8517-55ea-d97b-5a1f-212c121f2247@posteo.net> Fair enough. Brett Gilio brettg at posteo.net | bmg at member.fsf.org Free Software -- Free Society! On 07/12/2018 04:19 PM, Isaac David wrote: > Brett Gilio wrote : >> Would this be an appropriate time to refresh my keyring, then? Or >> should I wait? > > every time is the right time for refreshing the keyring. > From bill-auger at peers.community Thu Jul 12 21:24:40 2018 From: bill-auger at peers.community (bill-auger) Date: Thu, 12 Jul 2018 17:24:40 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> Message-ID: Brett - the keyring needs to be refreshed only when one of the existing keys has expired and renewed; but when the keyring package has not been regenerated - i still think this is a bug or a missing feature IMHO - if the keyring package were regenerated automatically each day, then no one would (ever?) need to refresh the keyring manually; pacman -Syu would be sufficient - when adding new key or removing an existing key, the keyring package will be regenerated and everyone will get it when next they pacman -Syu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Thu Jul 12 21:34:17 2018 From: bill-auger at peers.community (bill-auger) Date: Thu, 12 Jul 2018 17:34:17 -0400 Subject: [Dev] default redmine issue states In-Reply-To: References: Message-ID: <3ed6c4bc-83c8-0a35-a6ad-663b1c2d200e@peers.community> On 07/12/2018 04:46 PM, Brett Gilio wrote: > So, the procedural order here would be for somebody to file a report > with the "pending" or "unconfirmed" there is no order for unprivileged users - currently, every issue that an unprivileged user opens is 'open' - there is no option for it to be anything else - i would essentially just be changing that word 'open' to 'unconfirmed' > If so, I think this sounds like a solid idea, assuming that the other > privileged users are on-board. yes - that the main reason i sent this - i want everyone to know the new feature is there in hopes the semantics of issue states will be used optimally -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From brettg at posteo.net Thu Jul 12 23:48:52 2018 From: brettg at posteo.net (Brett Gilio) Date: Thu, 12 Jul 2018 18:48:52 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> Message-ID: <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> On 07/12/2018 04:24 PM, bill-auger wrote: > i still think this is a bug or a missing feature IMHO - if > the keyring package were regenerated automatically each day, then no one > would (ever?) need to refresh the keyring manually; pacman -Syu would be > sufficient I agree, that is why I have (for better or worse) have came to prefer using pacman-aur helpers what have some capability to automagically handle various types of keys. I wonder if pacman will ever get around to implementing something of the sort, of if the Arch Linux people have some aversion to this. -- Brett Gilio brettg at posteo.net | bmg at member.fsf.org Free Software -- Free Society! From brettg at posteo.net Fri Jul 13 05:24:52 2018 From: brettg at posteo.net (Brett Gilio) Date: Fri, 13 Jul 2018 00:24:52 -0500 Subject: [Dev] Bad Cheese Message-ID: Is there any way we can make gnome-control-center /not/ depend on cheese? How many of us actually use that dreaded application on a regular basis? -- Brett Gilio brettg at posteo.net | bmg at member.fsf.org https://www.parabola.nu/ | https://www.emacs.org/ Free Software -- Free Society! From nobody at parabola.nu Fri Jul 13 07:30:17 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 13 Jul 2018 07:30:17 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20180713073017.1369.79099@proton.parabola.nu> polaris at polaris.coffee wants to notify you that the following packages may be out-of-date: * iceweasel 1:59.0.2-3 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/iceweasel/ The user provided the following additional text: Iceweasel is out of date. It should be on version 61.x. Thanks, and have a nice day :) From nobody at parabola.nu Fri Jul 13 12:15:34 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 13 Jul 2018 12:15:34 -0000 Subject: [Dev] Orphan Libre package [avidemux-qt] marked out-of-date Message-ID: <20180713121534.1368.31707@proton.parabola.nu> uaqben at disroot.org wants to notify you that the following packages may be out-of-date: * avidemux-cli 2.7.0-4.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/avidemux-cli/ * avidemux-cli 2.7.0-4.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/avidemux-cli/ * avidemux-qt 2.7.0-4.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/avidemux-qt/ * avidemux-qt 2.7.0-4.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/avidemux-qt/ The user provided the following additional text: 2.7.1 was released on 2018-06-05. A further point release was made, but appears to be specific to a Ubuntu 18.04 lib issue. From bill-auger at peers.community Fri Jul 13 15:17:45 2018 From: bill-auger at peers.community (bill-auger) Date: Fri, 13 Jul 2018 11:17:45 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> Message-ID: <219be4f0-2124-fc6d-a8b9-558da4ff2a0b@peers.community> On 07/12/2018 07:48 PM, Brett Gilio wrote: > I wonder if pacman will ever get around to implementing something of the > sort, of if the Arch Linux people have some aversion to this. any proper distro would have an aversion to that - it seems that you are seeing a distro package manager as a tool to install prepared programs without needing to compile them by hand - that is missing the key aspect of package management - a distro package manager is first and foremost a way to ensure that all of the software you use has been approved and prepared by a single trusted source (your distro) who actively ensures that your software works well with the other programs they provide and does not abuse your system - it is always possible to install software from other sources using other tools but that is not endorsed by any distro that i know of; and the reason why should be obvious - they have no way of knowing what you install or where you got it from - it would be irresponsible to endorse things you have never seen -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From isacdaavid at isacdaavid.info Fri Jul 13 16:05:31 2018 From: isacdaavid at isacdaavid.info (Isaac David) Date: Fri, 13 Jul 2018 11:05:31 -0500 Subject: [Dev] Bad Cheese In-Reply-To: References: Message-ID: <1531497931.3913.0@plebeian.isacdaavid.info> Brett Gilio a ?crit : > Is there any way we can make gnome-control-center /not/ depend on > cheese? How many of us actually use that dreaded application on a > regular basis? this is a technical question for upstream. parabola does not repackage gnome-control-center (there are no FSDG issues with it AFAIK). my guess is that cheese is depended upon by the user accounts module (taking photos and adding them to user profiles). greetings. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From bill-auger at peers.community Fri Jul 13 16:11:39 2018 From: bill-auger at peers.community (bill-auger) Date: Fri, 13 Jul 2018 12:11:39 -0400 Subject: [Dev] Bad Cheese In-Reply-To: <1531497931.3913.0@plebeian.isacdaavid.info> References: <1531497931.3913.0@plebeian.isacdaavid.info> Message-ID: a very kludgey but effective solution would be to create you own dummy package named 'cheese' that puts an empty shell script in /usr/bin/cheese and set pacman to never upgrade the 'cheese' package - it may or may not work but it is pretty simpl to do -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From brettg at posteo.net Fri Jul 13 16:16:38 2018 From: brettg at posteo.net (Brett Gilio) Date: Fri, 13 Jul 2018 11:16:38 -0500 Subject: [Dev] Bad Cheese In-Reply-To: References: <1531497931.3913.0@plebeian.isacdaavid.info> Message-ID: <8e241a3d-9852-906f-0200-3df5e8fcef6a@posteo.net> On 07/13/2018 11:11 AM, bill-auger wrote: > a very kludgey but effective solution would be to create you own dummy > package named 'cheese' that puts an empty shell script in > /usr/bin/cheese and set pacman to never upgrade the 'cheese' package - > it may or may not work but it is pretty simpl to do That is what I was effectively planning on doing. I do not foresee any issues with that as long as I do not try to use any of the modules within gnome-control-center which depend on Cheese. Thanks for your help. -- Brett Gilio brettg at posteo.net | bmg at member.fsf.org https://www.parabola.nu/ | https://www.emacs.org/ Free Software -- Free Society! From lukeshu at lukeshu.com Sun Jul 15 22:41:47 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sun, 15 Jul 2018 18:41:47 -0400 Subject: [Dev] dbscripts 20180715 release announcement, and more! Message-ID: <87d0vof7f8.wl-lukeshu@lukeshu.com> I've rolled out version 20180715 of Parabola dbscripts. TL;DR: `db-move` and `db-remove` now work correctly! You can use them by ssh'ing to repo at repo.parabola.nu. This is essentially a bugfix release. Changes from 20180622 to 20180715: - The VCS backend is now configurable using config:VCS. This replaces using XBS to abstract away the VCS backend. * Currently, it has VCS=svn and VCS=none * By default VCS=none, which is consistent with the existing behavior (because XBS was always kind-of broken). * Eventually there will be a VCS=git or VCS=abslibre or VCS=srcpkg or something. - Unlike XBS, which was always kind-of broken, the VCS=none works correctly enough that `db-move` and `db-remove` work 100% correctly! - A dependency on expac was added. - Various test suite improvements. Known issues: - Documentation (`README.md`, `HACKING.org`) needs updated to reflect the above changes. - `sourceballs` won't work with VCS=none for obvious reasons (but that's OK, because we don't use `sourceballs` in Parabola) - `db-update` will erroneously agree to release binary packages that disagree with the PKGBUILD on file, because it doesn't know which PKGBUILD is on file, because VCS=none. Other notes: - Expect XBS to be removed in the next release of libretools. - On winston.parabola.nu, I have run: sudo pacman -Sy --needed dbscripts -- Happy hacking, ~ Luke Shumaker From brettg at posteo.net Sun Jul 15 22:47:19 2018 From: brettg at posteo.net (Brett Gilio) Date: Sun, 15 Jul 2018 17:47:19 -0500 Subject: [Dev] dbscripts 20180715 release announcement, and more! In-Reply-To: <87d0vof7f8.wl-lukeshu@lukeshu.com> References: <87d0vof7f8.wl-lukeshu@lukeshu.com> Message-ID: <87r2k42k20.fsf@posteo.net> Luke Shumaker writes: > I've rolled out version 20180715 of Parabola dbscripts. > > TL;DR: `db-move` and `db-remove` now work correctly! You can > use them > by ssh'ing to repo at repo.parabola.nu. > > This is essentially a bugfix release. > > Changes from 20180622 to 20180715: > > - The VCS backend is now configurable using config:VCS. This > replaces using XBS to abstract away the VCS backend. > * Currently, it has VCS=svn and VCS=none > * By default VCS=none, which is consistent with the existing > behavior (because XBS was always kind-of broken). > * Eventually there will be a VCS=git or VCS=abslibre or > VCS=srcpkg > or something. > - Unlike XBS, which was always kind-of broken, the VCS=none > works > correctly enough that `db-move` and `db-remove` work 100% > correctly! > - A dependency on expac was added. > - Various test suite improvements. > > Known issues: > > - Documentation (`README.md`, `HACKING.org`) needs updated to > reflect > the above changes. > - `sourceballs` won't work with VCS=none for obvious reasons > (but > that's OK, because we don't use `sourceballs` in Parabola) > - `db-update` will erroneously agree to release binary packages > that > disagree with the PKGBUILD on file, because it doesn't know > which > PKGBUILD is on file, because VCS=none. > > Other notes: > > - Expect XBS to be removed in the next release of libretools. > - On winston.parabola.nu, I have run: > sudo pacman -Sy --needed dbscripts Terrific work, Luke! Thank you for your dedication. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From lukeshu at lukeshu.com Mon Jul 16 02:46:47 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sun, 15 Jul 2018 22:46:47 -0400 Subject: [Dev] dbscripts 20180715 release announcement, and more! In-Reply-To: <87d0vof7f8.wl-lukeshu@lukeshu.com> References: <87d0vof7f8.wl-lukeshu@lukeshu.com> Message-ID: <87bmb7ganc.wl-lukeshu@lukeshu.com> On Sun, 15 Jul 2018 18:41:47 -0400, Luke Shumaker wrote: > - Unlike XBS, which was always kind-of broken, the VCS=none works > correctly enough that `db-move` and `db-remove` work 100% > correctly! Actually, they now *only* work with pkgbase; they no longer correctly accept a pkgver. For db-move I don't care, but that's a real problem for db-remove. Let's see if I can get a fix together in time to call it 20180715.1, or if I have to call it 20180716. -- Happy hacking, ~ Luke Shumaker From lukeshu at lukeshu.com Mon Jul 16 15:35:51 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Mon, 16 Jul 2018 11:35:51 -0400 Subject: [Dev] dbscripts 20180716 release announcement Message-ID: <87a7qrfb1k.wl-lukeshu@lukeshu.com> I've rolled out version 20180715 of Parabola dbscripts. This is a bugfix release. Changes from 20180715 to 20180716: - db-move, db-remove: Specifying pkgname (rather than pkgbase) now works again. This was broken in 20180715. - db-remove: Correctly handle split packages that have different pkgname=() lists on different architectures. I believe this has always been broken. - db-move, db-remove: Have more verbose, informative, friendly output. - Update documentation. Other notes: - On winston.parabola.nu, I have run: sudo pacman -Sy --needed dbscripts -- Happy hacking, ~ Luke Shumaker From nobody at parabola.nu Mon Jul 16 16:43:38 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 16 Jul 2018 16:43:38 -0000 Subject: [Dev] Orphan Libre package [qutebrowser] marked out-of-date Message-ID: <20180716164338.1368.33232@proton.parabola.nu> No0n3Left at openmailbox.org wants to notify you that the following packages may be out-of-date: * qutebrowser 1.2.1-1.parabola1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/qutebrowser/ The user provided the following additional text: Qutebrowser is now version 1.4.1, and two updates have contained security fixes (1.3.3 and 1.4.1). From brettg at posteo.net Mon Jul 16 18:11:38 2018 From: brettg at posteo.net (Brett Gilio) Date: Mon, 16 Jul 2018 13:11:38 -0500 Subject: [Dev] Orphan Libre package [qutebrowser] marked out-of-date In-Reply-To: <20180716164338.1368.33232@proton.parabola.nu> References: <20180716164338.1368.33232@proton.parabola.nu> Message-ID: <87k1pv125h.fsf@posteo.net> Parabola Website Notification writes: > No0n3Left at openmailbox.org wants to notify you that the following > packages may be out-of-date: > > > * qutebrowser 1.2.1-1.parabola1 [libre] (any): > https://parabolagnulinux.org/packages/libre/any/qutebrowser/ > > > The user provided the following additional text: > > Qutebrowser is now version 1.4.1, and two updates have contained > security fixes (1.3.3 and 1.4.1). Would it be unreasonable to report this on the issue tracker since I know several people, including myself, who use Qutebrowser and the security updates are of greater importance? -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From megver83 at hyperbola.info Tue Jul 17 16:56:43 2018 From: megver83 at hyperbola.info (Megver83) Date: Tue, 17 Jul 2018 12:56:43 -0400 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date In-Reply-To: <20180710225006.1368.11203@proton.parabola.nu> References: <20180710225006.1368.11203@proton.parabola.nu> Message-ID: <5ffedc5c-ef15-7b63-009e-b370ab2d286e@hyperbola.info> El 10/07/18 a las 18:50, Parabola Website Notification escribi?: > brettg at posteo.net wants to notify you that the following packages may be out-of-date: > > > * linux-libre 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ > * linux-libre 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ > * linux-libre 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ > * linux-libre-docs 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ > * linux-libre-docs 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ > * linux-libre-docs 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ > * linux-libre-headers 4.16.14_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ > * linux-libre-headers 4.16.14_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ > * linux-libre-headers 4.16.14_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ > > > The user provided the following additional text: > > linux-libre is currently at 4.17.14 That version doesn't exist (yet). Do not trust Parabolaweb, linux-libre is at 4.17.6. -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: https://pixelfed.social/Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From megver83 at hyperbola.info Tue Jul 17 17:01:10 2018 From: megver83 at hyperbola.info (Megver83) Date: Tue, 17 Jul 2018 13:01:10 -0400 Subject: [Dev] dbscripts 20180715 release announcement, and more! In-Reply-To: <87d0vof7f8.wl-lukeshu@lukeshu.com> References: <87d0vof7f8.wl-lukeshu@lukeshu.com> Message-ID: <9a7ef836-daa9-616e-f8e0-55d83dc23d8d@hyperbola.info> El 15/07/18 a las 18:41, Luke Shumaker escribi?: > TL;DR: `db-move` and `db-remove` now work correctly! Yeeeehaaa!!! -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: https://pixelfed.social/Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From brettg at posteo.net Tue Jul 17 17:52:57 2018 From: brettg at posteo.net (Brett Gilio) Date: Tue, 17 Jul 2018 12:52:57 -0500 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date In-Reply-To: <5ffedc5c-ef15-7b63-009e-b370ab2d286e@hyperbola.info> References: <20180710225006.1368.11203@proton.parabola.nu> <5ffedc5c-ef15-7b63-009e-b370ab2d286e@hyperbola.info> Message-ID: <87o9f5da12.fsf@posteo.net> Megver83 writes: > That version doesn't exist (yet). > > Do not trust Parabolaweb, linux-libre is at 4.17.6. I apologize, I marked this out of date before I realized the issue with parabolaweb. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From brettg at posteo.net Tue Jul 17 19:56:31 2018 From: brettg at posteo.net (Brett Gilio) Date: Tue, 17 Jul 2018 14:56:31 -0500 Subject: [Dev] Fwd: linux 4.17.7 not suitable for i386 References: <20180717153608.GA24505@jasmine.lan> Message-ID: <87bmb5d4b4.fsf@posteo.net> This is from the Guix mailing list, I am forwarding here just to make sure everybody is aware of this problem. Leo Famulari writes: > FYI, the latest stable Linux release (4.17.7) is not suitable > for i386 > (i686-linux) systems. Quoting Greg Kroah-Hartman: > > "NOTE, this kernel release is broken for i386 systems. If you > are > running such a machine, do NOT update to this release, you will > not be > able to boot properly. > > I did this release anyway with this known problem as there is a > fix in > here for x86-64 systems that was nasty to track down and was > affecting > people. Given that the huge majority of systems are NOT i386, I > felt > this was a safe release to do at this point in time." > > https://lkml.org/lkml/2018/7/17/434 > > So, we should take care to preserve the linux-libre 4.17.6 > package > definition for i686-linux, or skip this release. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From megver83 at hyperbola.info Tue Jul 17 20:16:07 2018 From: megver83 at hyperbola.info (Megver83) Date: Tue, 17 Jul 2018 16:16:07 -0400 Subject: [Dev] Fwd: linux 4.17.7 not suitable for i386 In-Reply-To: <87bmb5d4b4.fsf@posteo.net> References: <20180717153608.GA24505@jasmine.lan> <87bmb5d4b4.fsf@posteo.net> Message-ID: <8baed6f0-6f1f-01db-ccbc-0f81fd414217@hyperbola.info> El 17/07/18 a las 15:56, Brett Gilio escribi?: > > This is from the Guix mailing list, I am forwarding here just to make > sure everybody is aware of this problem. > > Leo Famulari writes: > >> FYI, the latest stable Linux release (4.17.7) is not suitable for i386 >> (i686-linux) systems. Quoting Greg Kroah-Hartman: >> >> "NOTE, this kernel release is broken for i386 systems.? If you are >> running such a machine, do NOT update to this release, you will not be >> able to boot properly. >> >> I did this release anyway with this known problem as there is a fix in >> here for x86-64 systems that was nasty to track down and was affecting >> people.? Given that the huge majority of systems are NOT i386, I felt >> this was a safe release to do at this point in time." >> >> https://lkml.org/lkml/2018/7/17/434 >> >> So, we should take care to preserve the linux-libre 4.17.6 package >> definition for i686-linux, or skip this release. > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > Thanks for the info. Will see what does ArchLinux32 does regarding this, but surely the easiest way is to skip linux-libre 4.17.7, which is about to be released. -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: https://pixelfed.social/Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From brettg at posteo.net Tue Jul 17 20:41:28 2018 From: brettg at posteo.net (Brett Gilio) Date: Tue, 17 Jul 2018 15:41:28 -0500 Subject: [Dev] Fwd: linux 4.17.7 not suitable for i386 In-Reply-To: <8baed6f0-6f1f-01db-ccbc-0f81fd414217@hyperbola.info> References: <20180717153608.GA24505@jasmine.lan> <87bmb5d4b4.fsf@posteo.net> <8baed6f0-6f1f-01db-ccbc-0f81fd414217@hyperbola.info> Message-ID: <87o9f5fvd3.fsf@posteo.net> Megver83 writes: > Thanks for the info. Will see what does ArchLinux32 does > regarding this, > but surely the easiest way is to skip linux-libre 4.17.7, which > is about > to be released. I am with you, the easiest solution is definitely just to skip 4.17.7 of linux-libre unless the FSFLA releases a patched version of the kernel. Upstream is already working on 4.17.8, so I do not see any reason to include 4.17.7 with this type of problem. Lets make sure that whoever maintains the linux-libre packages in Parabola is paying attention here, unless that is you Negver, in which case good work! -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From brettg at posteo.net Wed Jul 18 05:17:46 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 00:17:46 -0500 Subject: [Dev] Package Maintaining Message-ID: <87k1ptw29x.fsf@posteo.net> I asked this question in the IRC group, but I figured it might be more appropriate here. How exactly does one go about being considered to be a Parabola package maintainer? I have previous experience with maintaining packages and general package management, as well as a combined experience of about five years between Arch Linux and my transition to Libre w/ Parabola. I try to contribute in other ways, and be a proactive member of the community regardless. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From LucidEagle at protonmail.com Wed Jul 18 06:07:10 2018 From: LucidEagle at protonmail.com (Lucid Eagle) Date: Wed, 18 Jul 2018 02:07:10 -0400 Subject: [Dev] High Importance Message-ID: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> Hello everyone, hope you all are doing well. It has come to my attention that there may be a trojan in the official Parabola repos. As well as several other potential security issues as well. They may all just be false positives, but this one is rather alarming. /usr/bin/openal-info has a Unix.Trojan.Vali-6606621-0 Package Source: https://www.parabola.nu/packages/extra/x86_64/openal/ I have attached screen shots of all the results from the clamav scan on a fresh installation of Parabola GNU Linux. I am using the Cinnamon DE and I have just installed some of my favorite apps from only the official repos. I have also included a bash script that lists what I have done so far step by step after installing the system too. Please let me know if this is a real trojan and/or if the other issues are false positives. Thank you so much for all of your help. Take care and have a wonderful evening. Sincerely, Lucid Eagle Sent with [ProtonMail](https://protonmail.com) Secure Email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-55-09.png Type: image/png Size: 26985 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-17-15.png Type: image/png Size: 137736 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-18-06.png Type: image/png Size: 140918 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-18-22.png Type: image/png Size: 141398 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-18-41.png Type: image/png Size: 143259 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2018-07-18 01-18-50.png Type: image/png Size: 141831 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: quick-reset.sh Type: application/x-shellscript Size: 1452 bytes Desc: not available URL: From brettg at posteo.net Wed Jul 18 06:18:40 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 01:18:40 -0500 Subject: [Dev] High Importance In-Reply-To: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> References: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> Message-ID: <87in5dvzgf.fsf@posteo.net> Lucid Eagle writes: > It has come to my attention that there may be a trojan in the > official > Parabola repos. As well as several other potential security > issues as > well. They may all just be false positives, but this one is > rather > alarming. Thank you for your email, we will look into this. As for the PUAs, you can pretty much ignore them. You really do not need that setting to be enabled if you are not running an FTP server or anything of the sort on your machine where "drive-by" attacks can occur. As for the Trojan, I will look into it and report back if nobody else does in the morning. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From brainblasted at disroot.org Wed Jul 18 06:31:08 2018 From: brainblasted at disroot.org (Christopher Davis) Date: Wed, 18 Jul 2018 02:31:08 -0400 Subject: [Dev] High Importance In-Reply-To: <87in5dvzgf.fsf@posteo.net> References: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> <87in5dvzgf.fsf@posteo.net> Message-ID: <1531895468.31209.0@disroot.org> I have been looking into this, and it seems likely that this is a false positive. The code "6606621" was also used for a CUPS file, and according to VirusTotal only ClamAV reported an issue. Information here: https://www.virustotal.com/#/file/e770c592101a051e7a8d45a618c06244c301a8a6bcdec3f4dcc73a27b425c37b/detection Uploading to VirusTotal could help us figure out whether it's a valid report in this case too, though be aware that you will need to run non-free JS within your browser to use the page. On Wed, Jul 18, 2018 at 2:18 AM, Brett Gilio wrote: > > > > Lucid Eagle writes: >> It has come to my attention that there may be a trojan in the >> official >> Parabola repos. As well as several other potential security issues >> as >> well. They may all just be false positives, but this one is rather >> alarming. > > Thank you for your email, we will look into this. > > As for the PUAs, you can pretty much ignore them. You really do not > need > that setting to be enabled if you are not running an FTP server or > anything of the sort on your machine where "drive-by" attacks can > occur. > > As for the Trojan, I will look into it and report back if nobody else > does in the morning. > > -- > Brett M. Gilio > Free Software Foundation, Member > https://parabola.nu | https://emacs.org > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From brettg at posteo.net Wed Jul 18 07:00:36 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 02:00:36 -0500 Subject: [Dev] High Importance In-Reply-To: <1531895468.31209.0@disroot.org> References: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> <87in5dvzgf.fsf@posteo.net> <1531895468.31209.0@disroot.org> Message-ID: <87h8kxvxij.fsf@posteo.net> Christopher Davis writes: > I have been looking into this, and it seems likely that this is > a false > positive. The code "6606621" was > also used for a CUPS file, and according to VirusTotal only > ClamAV reported an > issue. Information > here: > https://www.virustotal.com/#/file/e770c592101a051e7a8d45a618c06244c301a8a6bcdec3f4dcc73a27b425c37b/detection > > Uploading to VirusTotal could help us figure out whether it's a > valid report in > this case too, > though be aware that you will need to run non-free JS within > your browser to use > the page. I did some research on the file in question, too. It seems that ClamAV flags it as a virus due to some bad checking on the hexcode in the file. This has actually been reported to ClamAV in the past. In summary, this package is not problematic. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From aurelien at hackers.camp Wed Jul 18 10:12:13 2018 From: aurelien at hackers.camp (aurelien at hackers.camp) Date: Wed, 18 Jul 2018 12:12:13 +0200 Subject: [Dev] High Importance In-Reply-To: <87h8kxvxij.fsf@posteo.net> (Brett Gilio's message of "Wed, 18 Jul 2018 02:00:36 -0500") References: <6pMrpUo7rbih1bZdIrbUzP8ipUepPZvH3k0Jh8Jncw9UIutiVF0jbHNpRkCRGrEjW53FVUf6b-4buxaVBAYrYky4diQAd5UVk1YBzuL_dis=@protonmail.com> <87in5dvzgf.fsf@posteo.net> <1531895468.31209.0@disroot.org> <87h8kxvxij.fsf@posteo.net> Message-ID: <87y3e8rgxu.fsf@hackers.camp> Brett Gilio writes: > Christopher Davis writes: > >> I have been looking into this, and it seems likely that this is a >> false >> positive. The code "6606621" was >> also used for a CUPS file, and according to VirusTotal only ClamAV >> reported an >> issue. Information >> here: >> https://www.virustotal.com/#/file/e770c592101a051e7a8d45a618c06244c301a8a6bcdec3f4dcc73a27b425c37b/detection >> >> Uploading to VirusTotal could help us figure out whether it's a >> valid report in >> this case too, >> though be aware that you will need to run non-free JS within your >> browser to use >> the page. > > I did some research on the file in question, too. It seems that ClamAV > flags it as a virus due to some bad checking on the hexcode in the > file. > This has actually been reported to ClamAV in the past. > > In summary, this package is not problematic. Hello mates, There is also the point the 'extra' repo is made of stuff from ArchLinux, so you can blacklist (temporarely/definitely) it to avoid the trouble. take care -- aurelien desbrieres From megver83 at hyperbola.info Wed Jul 18 18:13:51 2018 From: megver83 at hyperbola.info (Megver83) Date: Wed, 18 Jul 2018 14:13:51 -0400 Subject: [Dev] Package Maintaining In-Reply-To: <87k1ptw29x.fsf@posteo.net> References: <87k1ptw29x.fsf@posteo.net> Message-ID: <03b1d026-8891-5a41-333a-9b4a3cc88749@hyperbola.info> El 18/07/18 a las 01:17, Brett Gilio escribi?: > How exactly does one go about being considered to be a Parabola package > maintainer? I have previous experience with maintaining packages and > general package management, as well as a combined experience of about > five years between Arch Linux and my transition to Libre w/ Parabola. > A Parabola packager is basically anyone with access to our servers (proton.parabola.nu and winston.parabola.nu) and with his/her GPG key included in the parabola-keyring parackage. With that, you are ready to build and upload packages to the official repos (except [community], [core], [extra] and [multilib], plus their testing derivatives). -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: https://pixelfed.social/Megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Wed Jul 18 19:02:40 2018 From: bill-auger at peers.community (bill-auger) Date: Wed, 18 Jul 2018 15:02:40 -0400 Subject: [Dev] Package Maintaining In-Reply-To: <03b1d026-8891-5a41-333a-9b4a3cc88749@hyperbola.info> References: <87k1ptw29x.fsf@posteo.net> <03b1d026-8891-5a41-333a-9b4a3cc88749@hyperbola.info> Message-ID: <20180718150240.e235f307d4da59ec58dc10a8@peers.community> El 18/07/18 a las 01:17, Brett Gilio escribi?: > How exactly does one go about being considered to be a Parabola package > maintainer? there is a wiki article about that[1] - probably the most important criteria to tick there is the one about being around for a long time and a well known, trusted, and competent member of the parabola community there are no hard requirements to meet; but for example, freemor is next in line to join parabola - he has been around the community for some years now and has visibly contributed to parabola already in the form of filing and triaging bug reports and general user support guidance on the IRC and mailing list if you have experience with arch packaging and would like to help parabola , there is one task i could that would be very helpful that anyone could do - there is currently a long back-log of out-dated packages in an etherpad - it would be very helpful if someone could try building them, if only to keep note of which were trouble-free and which were problematic - even better if you could fix the ones that are problematic and post the changes to the mailing list - if this interests you, id invited you to work with freemor on that - i think that tending to that back-log is one of his stated first intentions as a parabola dev [1]: https://wiki.parabola.nu/How_to_become_a_Parabola_hacker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From brettg at posteo.net Wed Jul 18 20:29:37 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 15:29:37 -0500 Subject: [Dev] Kernel Followup Message-ID: <87in5cjnim.fsf@posteo.net> Just a follow up on the issue I noted about the instability of 4.17.7 kernel for 32-bit systems, the 4.17.8 kernel was just announced as stable and the linux-libre kernel will follow suit. There is still an option to cherry-pick the patch for the 4.17.7 kernel, but I maintain that we skip that update and just wait for linux-libre 4.17.8 -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From andreas at grapentin.org Wed Jul 18 21:04:38 2018 From: andreas at grapentin.org (Andreas Grapentin) Date: Wed, 18 Jul 2018 23:04:38 +0200 Subject: [Dev] submitting my SSH key In-Reply-To: <20180712200553.GD5142@freemor.ca> References: <20180712175539.GC5142@freemor.ca> <112ffa46-12d0-b934-a9fb-de89aac6670b@peers.community> <20180712200553.GD5142@freemor.ca> Message-ID: <20180718210437.GA26311@parabola-pocket.localdomain> On Thu, Jul 12, 2018 at 05:06:17PM -0300, Freemor wrote: > I'm still learning my way around libretools. But I've been makepkg'ing stuff > from myself for some while so it shouldn't take too long. I'd really enjoy > being able to take up some of the load for thing like out-of-date packages or > those packages that just need a quick rebuild because some lib updates and it > now needs to be rebuilt against the new ver on the lib. etc. > > As my skill and confidence improves I'd start branching into packing requests > etc. This is precisely how I started. Welcome aboard :) -- ------------------------------------------------------------------------------ my GPG Public Key: https://files.grapentin.org/.gpg/public.key ------------------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From lukeshu at lukeshu.com Wed Jul 18 22:29:50 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 18 Jul 2018 18:29:50 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> Message-ID: <87601cfa8x.wl-lukeshu@lukeshu.com> On Thu, 12 Jul 2018 19:48:52 -0400, Brett Gilio wrote: > > On 07/12/2018 04:24 PM, bill-auger wrote: > > > i still think this is a bug or a missing feature IMHO - if > > the keyring package were regenerated automatically each day, then no one > > would (ever?) need to refresh the keyring manually; pacman -Syu would be > > sufficient > > I agree, that is why I have (for better or worse) have came to prefer > using pacman-aur helpers what have some capability to automagically > handle various types of keys. It should. It's not clear why Parabola users need to refresh their keyring periodically besides just running `pacman -Syu`. Arch users don't normally need to do that. Parabola's pacman package as a workaround includes a systemd timer to refresh it periodically, but we really should get to the root of the issue. -- Happy hacking, ~ Luke Shumaker From brettg at posteo.net Wed Jul 18 22:36:49 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 17:36:49 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: <87601cfa8x.wl-lukeshu@lukeshu.com> References: <20180712175539.GC5142@freemor.ca> <886c6093-162c-5cbb-e81b-44d2f6ca9f80@posteo.net> <97d5f749-2c8c-a375-25b5-0bb28a63b835@posteo.net> <87601cfa8x.wl-lukeshu@lukeshu.com> Message-ID: <871sc0jhmm.fsf@posteo.net> Luke Shumaker writes: > On Thu, 12 Jul 2018 19:48:52 -0400, > Brett Gilio wrote: >> >> On 07/12/2018 04:24 PM, bill-auger wrote: >> >> > i still think this is a bug or a missing feature IMHO - if >> > the keyring package were regenerated automatically each day, >> > then no one >> > would (ever?) need to refresh the keyring manually; pacman >> > -Syu would be >> > sufficient >> >> I agree, that is why I have (for better or worse) have came to >> prefer >> using pacman-aur helpers what have some capability to >> automagically >> handle various types of keys. > > It should. It's not clear why Parabola users need to refresh > their > keyring periodically besides just running `pacman -Syu`. Arch > users > don't normally need to do that. Parabola's pacman package as a > workaround includes a systemd timer to refresh it periodically, > but we > really should get to the root of the issue. Luke, do we have an active bug report on the issue? I wouldn't mind taking a look into it to see if I can diagnose anything. I have a few hours this evening. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From lukeshu at lukeshu.com Wed Jul 18 22:41:36 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 18 Jul 2018 18:41:36 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <20180712175539.GC5142@freemor.ca> References: <20180712175539.GC5142@freemor.ca> Message-ID: <874lgwf9pb.wl-lukeshu@lukeshu.com> Hi Freemor, Could you submit to us the full information for your hackers.git profile? You can look at mine as an example https://git.parabola.nu/hackers.git/tree/users/1015.yml Don't worry about formatting it correctly. Some notes: - The first email listed will be publicly shown on www.parabola.nu - freemor at parabola.nu will forward to the first non- at parabola.nu email listed - Just put yourself in the "hackers" group - The email ident for the SSH keys needs to be freemor at something, but the "something" is purely informative for keeping track of multiple keys, it doesn't need to be a real hostname. Welcome aboard :) -- Happy hacking, ~ Luke Shumaker From freemor at freemor.ca Thu Jul 19 00:57:23 2018 From: freemor at freemor.ca (Freemor) Date: Wed, 18 Jul 2018 21:57:23 -0300 Subject: [Dev] submitting my SSH key In-Reply-To: <874lgwf9pb.wl-lukeshu@lukeshu.com> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> Message-ID: <20180719005723.GC21421@freemor.ca> On Wed, Jul 18, 2018 at 06:41:36PM -0400, Luke Shumaker wrote: > Hi Freemor, > > Could you submit to us the full information for your hackers.git > profile? You can look at mine as an example > https://git.parabola.nu/hackers.git/tree/users/1015.yml Don't worry > about formatting it correctly. > username: freemor fullname: Freemor #Only banks and .gov's use my legal name but if you need it I can provide. email: - freemor at freemor.ca groups: - hackers pgp_keyid: 17446CB76E250EE809DFE1F2A7DC2FC7EBC8F713 ssh_keys: ssh-ed25519AAAAC3NzaC1lZDI1NTE5AAAAIHuX5stLFkx33WSQ2mPLhhp6rv+cJOlY1IFUxIuMEzFs shell: "/bin/bash" extra: other_contact: 'irc freenode: freemor' 'xmpp: freemor at home.zom.im' 'ring: b8d73e82bd7be3cc01c7781900c3ba58d687314a' 'tox: 8D4973925FB8C27ABDC916C30344CF493EA7CA7854D2A801B85F3E8B3820A25FEF4BF65109A3' website: http://freemor.ca roles: TBD, but probably a little of everything yob: 1965 location: NB, Canada interests: free software, free culture, open hardware, SBC hacking languages: English > Welcome aboard :) Thanks for the warm welcome :) Glad to be aboard. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From freemor at freemor.ca Thu Jul 19 01:03:14 2018 From: freemor at freemor.ca (Freemor) Date: Wed, 18 Jul 2018 22:03:14 -0300 Subject: [Dev] submitting my SSH key In-Reply-To: <874lgwf9pb.wl-lukeshu@lukeshu.com> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> Message-ID: <20180719010314.GD21421@freemor.ca> On Wed, Jul 18, 2018 at 06:41:36PM -0400, Luke Shumaker wrote: > - The email ident for the SSH keys needs to be freemor at something, but > the "something" is purely informative for keeping track of multiple > keys, it doesn't need to be a real hostname. Realized I missed including that bit.. just make it freemor at freemor.ca -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From brettg at posteo.net Thu Jul 19 01:18:10 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 20:18:10 -0500 Subject: [Dev] submitting my SSH key In-Reply-To: <20180719005723.GC21421@freemor.ca> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> <20180719005723.GC21421@freemor.ca> Message-ID: <877elsdnvx.fsf@posteo.net> Freemor writes: > Thanks for the warm welcome :) Glad to be aboard. Freemor, >From a non-dev, I wish you the best in your contributions and I thank you for your present and future contributions to this terrific project. Congrats! -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From brettg at posteo.net Thu Jul 19 01:20:02 2018 From: brettg at posteo.net (Brett Gilio) Date: Wed, 18 Jul 2018 20:20:02 -0500 Subject: [Dev] Package Maintaining In-Reply-To: <20180718150240.e235f307d4da59ec58dc10a8@peers.community> References: <87k1ptw29x.fsf@posteo.net> <03b1d026-8891-5a41-333a-9b4a3cc88749@hyperbola.info> <20180718150240.e235f307d4da59ec58dc10a8@peers.community> Message-ID: <87601cdnst.fsf@posteo.net> bill-auger writes: > there is a wiki article about that[1] - probably the most > important criteria to tick there is the one about being around > for a long time and a well known, trusted, and competent member > of the parabola community Thank you for the link to the wiki article, Bill. > there are no hard requirements to meet; but for example, freemor > is next in line to join parabola - he has been around the > community for some years now and has visibly contributed to > parabola already in the form of filing and triaging bug reports > and general user support guidance on the IRC and mailing list > > if you have experience with arch packaging and would like to > help > parabola , there is one task i could that would be very helpful > that > anyone could do - there is currently a long back-log of > out-dated > packages in an etherpad - it would be very helpful if someone > could > try building them, if only to keep note of which were > trouble-free and > which were problematic - even better if you could fix the ones > that > are problematic and post the changes to the mailing list - if > this > interests you, id invited you to work with freemor on that - i > think > that tending to that back-log is one of his stated first > intentions as > a parabola dev Absolutely, I would be more than happy to help with that back-log in any way. -- Brett M. Gilio Free Software Foundation, Member https://parabola.nu | https://emacs.org From bill-auger at peers.community Thu Jul 19 03:51:46 2018 From: bill-auger at peers.community (bill-auger) Date: Wed, 18 Jul 2018 23:51:46 -0400 Subject: [Dev] submitting my SSH key In-Reply-To: <20180719005723.GC21421@freemor.ca> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> <20180719005723.GC21421@freemor.ca> Message-ID: <20180718235146.c86256c0187d80a84dcaf934@peers.community> Freemor - i actually already setup that ID card for you - you are hither-to-forth known as "Hacker #41" - i left all of the 'extra' fields empty for now - we just need to get your SSH key on the servers next - i figured you could fill out or delete the empty 'extra' data yourself and push it back to the server as a trial run to make sure you are setup properly - that git push will initiate the keyring rebuild and other magical things you can put "packager" for 'roles' of you want - you can change this 'extra' data at any time i also gave you escalated privilege on the redmine site so you can assign and close issues -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From freemor at freemor.ca Thu Jul 19 13:46:51 2018 From: freemor at freemor.ca (Freemor) Date: Thu, 19 Jul 2018 10:46:51 -0300 Subject: [Dev] submitting my SSH key In-Reply-To: <20180718235146.c86256c0187d80a84dcaf934@peers.community> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> <20180719005723.GC21421@freemor.ca> <20180718235146.c86256c0187d80a84dcaf934@peers.community> Message-ID: <20180719134651.GE21421@freemor.ca> On Wed, Jul 18, 2018 at 11:51:46PM -0400, bill-auger wrote: > Freemor - > > i actually already setup that ID card for you - you are hither-to-forth known > as "Hacker #41" - i left all of the 'extra' fields empty for now - we just > need to get your SSH key on the servers next - i figured you could fill out > or delete the empty 'extra' data yourself and push it back to the server as a > trial run to make sure you are setup properly - that git push will initiate > the keyring rebuild and other magical things Thanks! pulled, modified, but can't push yet.. Guess my key isn't populated yet. I'll try again a bit later. > i also gave you escalated privilege on the redmine site so you can assign and > close issues Also thanks. I'm off to see what that looks like. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nobody at parabola.nu Fri Jul 20 12:04:12 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 20 Jul 2018 12:04:12 -0000 Subject: [Dev] Orphan Pcr package [icinga2] marked out-of-date Message-ID: <20180720120412.13325.12695@proton.parabola.nu> korobkov at vinterdalen.se wants to notify you that the following packages may be out-of-date: * icinga2 2.8.1-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/icinga2/ * icinga2 2.8.1-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/icinga2/ * icinga2 2.8.1-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/icinga2/ * icinga2-common 2.8.1-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/icinga2-common/ * icinga2-common 2.8.1-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/icinga2-common/ * icinga2-common 2.8.1-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/icinga2-common/ * icinga-studio 2.8.1-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/icinga-studio/ * icinga-studio 2.8.1-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/icinga-studio/ * icinga-studio 2.8.1-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/icinga-studio/ The user provided the following additional text: Please, update to the latest 2.9 [0] [0] https://www.icinga.com/2018/07/17/icinga-2-9-0-released/ thanks in advance, Andrey From freemor at freemor.ca Fri Jul 20 17:11:22 2018 From: freemor at freemor.ca (Freemor) Date: Fri, 20 Jul 2018 14:11:22 -0300 Subject: [Dev] submitting my SSH key In-Reply-To: <20180719010314.GD21421@freemor.ca> References: <20180712175539.GC5142@freemor.ca> <874lgwf9pb.wl-lukeshu@lukeshu.com> <20180719010314.GD21421@freemor.ca> Message-ID: <20180720171105.GF21421@freemor.ca> Hi, I've been trying to update my 1041.yml on hackers.git but as yet I am unable to access the repo via git clone ssh and thus can't push the changes, So Either I'm using the wrong syntax for the URI or my keys are not added yet. I'm sending this to make sure that #1 is not the case. I've been trying to clone hackers.git via: git clone ssh://git at git.parabola.nu:1863/~git/hackers.git It tries but fails with a permission denied error. By making git use ssh -v as the ssh command I can see that: - it connects to the server - it offers the correct key - the key gets refused - the connection closes out with permission denied So I'm wondering if the user/server/folder are all correct? If me using a non RSA key caused an issue? Or if I just need to be patient (which isn't a problem). Regards, Freemor -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From brettg at posteo.net Sun Jul 22 00:41:57 2018 From: brettg at posteo.net (Brett Gilio) Date: Sat, 21 Jul 2018 19:41:57 -0500 Subject: [Dev] Fwd: Linux-libre-firmware 1.2.2 References: <1532218378.31497.1.camel@jxself.org> Message-ID: <871sbwhzje.fsf@posteo.net> Jason Self writes: > I'm announcing a new version of linux-libre-firmware. > > Version 1.2.2 fixes a problem that could cause intermittent > build > failures of the carl9170 firmware. This is the only change > compared to > 1.2.1. > > Version 1.2.2 can be found in the normal places: In git [0] or > as a > tarball [1] (which includes pre-compiled firmware.) > > [0] https://jxself.org/git/?p=linux-libre-firmware.git > [1] > https://jxself.org/firmware/_______________________________________________ > linux-libre mailing list > linux-libre at fsfla.org > http://www.fsfla.org/cgi-bin/mailman/listinfo/linux-libre -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From lukeshu at lukeshu.com Tue Jul 24 06:12:52 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Tue, 24 Jul 2018 02:12:52 -0400 Subject: [Dev] notsystemd v239.1 release announcement Message-ID: <877ellgo0r.wl-lukeshu@lukeshu.com> I am pleased to announce the 5th release of "notsystemd", v239.1. notsystemd is a project to turn the various components of systemd into independent pieces that can be used no matter which software is used for PID 1; in a similar spirit to eudev or elogind. This release adds support for running nspawn on non-systemd cgroup-v1/v2 hybrid setups, and drops support the GNU Autotools-base build system (the build system now depends on Meson and Ninja). At a minimum, the following utilities from notsystemd should be functional on non-systemd systems: systemd-nspawn systemd-machine-id-setup systemd-tmpfiles systemd-sysusers systemd-udevd udevadm The sources are at https://repo.parabola.nu/other/notsystemd/ Pre-built packages have been released to the [libre] repository for Parabola GNU/Linux-libre. -- Happy hacking, ~ Luke Shumaker From nobody at parabola.nu Wed Jul 25 06:30:52 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 25 Jul 2018 06:30:52 -0000 Subject: [Dev] Orphan Pcr package [i2p] marked out-of-date Message-ID: <20180725063052.13325.2308@proton.parabola.nu> jellyfish at riseup.net wants to notify you that the following packages may be out-of-date: * i2p 0.9.32-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/i2p/ * i2p 0.9.32-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/i2p/ * i2p 0.9.32-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/i2p/ The user provided the following additional text: recent version is 0.9.35 From nobody at parabola.nu Wed Jul 25 06:32:39 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 25 Jul 2018 06:32:39 -0000 Subject: [Dev] Orphan Pcr package [retroshare] marked out-of-date Message-ID: <20180725063239.13331.28191@proton.parabola.nu> jellyfish at riseup.net wants to notify you that the following packages may be out-of-date: * retroshare 0.6.3-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/retroshare/ * retroshare 0.6.3-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/retroshare/ * retroshare 0.6.3-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/retroshare/ The user provided the following additional text: current version is 6.4 From freemor at freemor.ca Fri Jul 27 17:01:46 2018 From: freemor at freemor.ca (Freemor) Date: Fri, 27 Jul 2018 14:01:46 -0300 Subject: [Dev] "systemd" placeholder for now? Message-ID: <20180727170146.GM21421@freemor.ca> Hello, I have been watching lukeshu's great work breaking down the monolithic systemd packages. And I agree with his view that packages that sloppily depend on systemd when what they really mean is depend udev should be fixed. It seems that the current lack of a "provides systemd" placeholder is causing issues. I was stuck with a ghosted (local/) systemd-dummy that was keeping libsystemd-shared-238.so hanging about and as it was now not in any repos it'd never get updated. Also "linka" in the IRC gave up on an openrc install due to all the things that were trying to pull in systemd and without a placeholder to make them happy they actually wanted to pull systemd. I'd like to propose a openrc-systemd-placehoder meta package for the time being to 1.) help people who still have systemd-dummy floating around. and 2.) Have a way for people doing an openrc install to keep the packages with sloppy depends happy until they can be fixed up. I have hacked up such a package (mostly to fix my systemd-dummy issue) but I'd like to suggest that it get made more official. Why didn't I just go ahead an commit it? 1.) I'm new the doing PKGBUILD so this is probably really rough and hackish 2.) I'm not experienced enough to be sure that it wouldn't cause instability for people that are using systemd by jumping ahead and being the default=1 choice during an install which would probably break all kinds of things. So here is that I hacked up. It fixed my systemd-dummy issue nicely and none of the 12 or so packages that sloppily depend "systemd"complained about no systemd ... yada yada ========= # Maintainer (Parabola): Freemor # A meta package to make packages that wrongly depends=('systemd') # When all they really wnat is udev happy in a non systemd system # # Designed for Parabola where notsystemd-common lives _spkgrel=1.parabola1 #_repo=https://repo.parabola.nu/libre/os #Not sure what this should be set to for this pkgbase=systemdcompat pkgname=('openrc-systemd-placeholder') pkgver=239 pkgrel=2 pkgrel+=.parabola1 arch=('any') license=('GPL2') groups=('base-openrc' 'openrc-base') pkgdesc="A meta package to provides systemd for packages that improperly depend on it; systemd compatibility package" provides=("systemd=${pkgver}") depends=("notsystemd-common") conflicts=('systemd' 'eudev-systemdcompat') replaces=('systemd-dummy') ======== -- Want to send me an encrypted reply? Click here: https://hawkpost.co/box/e414d311-bd6a-4429-8e9e-6a690d5ad034 The rest of my contact details are at: https://freemor.ca/contact -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From lukeshu at lukeshu.com Fri Jul 27 19:23:53 2018 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Fri, 27 Jul 2018 15:23:53 -0400 Subject: [Dev] "systemd" placeholder for now? In-Reply-To: <20180727170146.GM21421@freemor.ca> References: <20180727170146.GM21421@freemor.ca> Message-ID: <871sboh48m.wl-lukeshu@lukeshu.com> On Fri, 27 Jul 2018 13:01:46 -0400, Freemor wrote: > 1.) I'm new the doing PKGBUILD so this is probably really rough and hackish > 2.) I'm not experienced enough to be sure that it wouldn't cause instability > for people that are using systemd by jumping ahead and being the > default=1 choice during an install which would probably break all kinds > of things. It only provides the prompt for "virtual" packages, which are packages that no package actually has that name, and instead are *only* listed in provides=() for packages with different names. Because there's an actual pkgname=systemd package, it wouldn't trigger the prompt for "systemd" (but it might for "systemd-tools"). I've gone ahead made a few changes to the PKGBUILD and pushed this to [pcr], but made you Maintainer. ---- Feedback: $ namcap PKGBUILD PKGBUILD (systemdcompat) W: Missing Maintainer tag PKGBUILD (systemdcompat) E: Child package openrc-systemd-placeholder does not have a valid package() function PKGBUILD (openrc-systemd-placeholder) E: Missing url namcap ("pacman", backwards) is a linter for PKGBUILD and package files. We've decided that it has too many false-positives to build in to libremakepkg (it's commented out there), but it's a good idea to run it on all of your PKGBUILDs until you have a good idea about the things it complains about. > # Maintainer (Parabola): Freemor We only put " (Distro)" for things other than Parabola (otherwise namcap complains). > # A meta package to make packages that wrongly depends=('systemd') > # When all they really wnat is udev happy in a non systemd system > # > # Designed for Parabola where notsystemd-common lives > > > _spkgrel=1.parabola1 > #_repo=https://repo.parabola.nu/libre/os #Not sure what this should be set to for this `_repo` is a weird idiosyncrasy of Artix Linux packages; it only appears in PKGBUILDs we imported from there. Variables starting with `_` are "private" variables to that specific PKGBUILD, makepkg and other tools make no use of them; there's no need to set them if you don't use them. (Exception: Autobuilder makes special use of of `_commit` for packages that are built from software that lives at git.parabola.nu). > > pkgbase=systemdcompat > pkgname=('openrc-systemd-placeholder') pkgbase is only necessary for split packages--for that mater, so are the paraens on pkgname. You should have just written pkgname='openrc-systemd-placeholder' > pkgver=239 > pkgrel=2 > pkgrel+=.parabola1 There's no need to use more than a simple integer for a PKGBUILD that isn't based on another PKGBUILD. > arch=('any') > license=('GPL2') > groups=('base-openrc' 'openrc-base') > pkgdesc="A meta package to provides systemd for packages that improperly depend on it; systemd compatibility package" > provides=("systemd=${pkgver}") > depends=("notsystemd-common") > conflicts=('systemd' 'eudev-systemdcompat') > replaces=('systemd-dummy') -- Happy hacking, ~ Luke Shumaker From nobody at parabola.nu Tue Jul 31 03:00:00 2018 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 31 Jul 2018 03:00:00 -0000 Subject: [Dev] Orphan Libre package [hexchat] marked out-of-date Message-ID: <20180731030000.13327.61397@proton.parabola.nu> foodatrix at gmail.com wants to notify you that the following packages may be out-of-date: * hexchat 2.12.4-3.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/hexchat/ * hexchat 2.12.4-3.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/hexchat/ * hexchat 2.12.4-3.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/hexchat/ The user provided the following additional text: 2.14.1 is the latest