From nobody at parabola.nu Sat Dec 2 19:08:01 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 02 Dec 2017 19:08:01 -0000 Subject: [Dev] Orphan Libre package [mesa] marked out-of-date Message-ID: <20171202190801.26949.53640@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * mesa 17.2.1-3.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/mesa/ * mesa 17.2.5-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/mesa/ The user provided the following additional text: Current release is 17.2.6 From nobody at parabola.nu Sun Dec 3 18:06:11 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 03 Dec 2017 18:06:11 -0000 Subject: [Dev] Orphan Nonprism package [gnome-settings-daemon] marked out-of-date Message-ID: <20171203180611.26948.13641@proton.parabola.nu> jdoe at example.com wants to notify you that the following packages may be out-of-date: The user provided the following additional text: The latest version of g-s-d is 3.26.2. From nobody at parabola.nu Sun Dec 3 20:50:58 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 03 Dec 2017 20:50:58 -0000 Subject: [Dev] Orphan Libre package [iceweasel-noscript] marked out-of-date Message-ID: <20171203205058.26948.43707@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * iceweasel-noscript 10.1.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-noscript/ The user provided the following additional text: Current release is 10.1.5.3 From jc_gargma at iserlohn-fortress.net Sun Dec 3 20:52:51 2017 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Sun, 03 Dec 2017 12:52:51 -0800 Subject: [Dev] Orphan Libre package [iceweasel-noscript] marked out-of-date In-Reply-To: <20171203205058.26948.43707@proton.parabola.nu> References: <20171203205058.26948.43707@proton.parabola.nu> Message-ID: <3126710.bmJ0n5kxfu@iserlohn-fortress.net> > The user provided the following additional text: I've attached a git format-patch to update iceweasel-noscript to 10.1.5.3 -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-iceweasel-noscript-to-10.1.5.3.patch Type: text/x-patch Size: 1026 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From nobody at parabola.nu Tue Dec 5 03:06:11 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 05 Dec 2017 03:06:11 -0000 Subject: [Dev] Orphan Libre package [calibre] marked out-of-date Message-ID: <20171205030611.26949.59322@proton.parabola.nu> darien at cock.li wants to notify you that the following packages may be out-of-date: * calibre 3.12.0-2.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/calibre/ * calibre 3.12.0-2.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/calibre/ * calibre 3.12.0-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/calibre/ The user provided the following additional text: this package is outdated, thank you! From beebe at math.utah.edu Wed Dec 6 15:14:07 2017 From: beebe at math.utah.edu (Nelson H. F. Beebe) Date: Wed, 6 Dec 2017 08:14:07 -0700 Subject: [Dev] texlive-core problem, and repairs Message-ID: I built a new machine running Hyperbola 0.2.1 in our test farm of Unix(-like) systems, and successfully installed more than 650 packages on it with "pacman -Sy", based on a similar list from an Arch Linux system in the farm. One package, texlive-core, failed to install completely, however, and I diagnosed the problem, and found a workaround logged in these system notes: When I installed texlive-core, I found that the installation step failed because of missing Czech fonts (.../cs/cs*.mf). A comparison with Arch Linux showed that Hyperbola is missing many files: hyperbola: # pacman -Fl texlive-core | wc -l 16266 archlinux: # pacman -Fl texlive-core | wc -l 24069 I was able to temporarily repair the problem like this: # fmtutil-sys --listcfg # fmtutil-sys --disablefmt csplain # fmtutil-sys --disablefmt cslatex # fmtutil-sys --all Now the Czech fonts are disabled, and the remaining *.fmt files are created: hyperbola: # find /var/lib/texmf/web2c -name '*.fmt' |wc -l 18 archlinux: # find /var/lib/texmf/web2c -name '*.fmt' |wc -l 38 It is unclear why almost 8000 files are missing from texlive-core compared to the package on Arch Linux. I'm a member of the TeX Live team that prepares the annual releases, and I have TeX installed on almost 200 systems in the farm without ever seeing a problem like this, until I build the Hyperbola system. ------------------------------------------------------------------------------- - Nelson H. F. Beebe Tel: +1 801 581 5254 - - University of Utah FAX: +1 801 581 4148 - - Department of Mathematics, 110 LCB Internet e-mail: beebe at math.utah.edu - - 155 S 1400 E RM 233 beebe at acm.org beebe at computer.org - - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ - ------------------------------------------------------------------------------- From megver83 at hyperbola.info Wed Dec 6 18:07:59 2017 From: megver83 at hyperbola.info (Megver83) Date: Wed, 6 Dec 2017 15:07:59 -0300 Subject: [Dev] texlive-core problem, and repairs In-Reply-To: References: Message-ID: <8d56c72d-1ed8-72d8-dd84-4e9f5deeb4f5@hyperbola.info> El 06/12/17 a las 12:14, Nelson H. F. Beebe escribi?: > I built a new machine running Hyperbola 0.2.1 in our test farm of > Unix(-like) systems, and successfully installed more than 650 > packages on it with "pacman -Sy", based on a similar list from > an Arch Linux system in the farm. I'm sorry, but I think you confused the mailing list. This is Parabola's dev list, not Hyperbola's nor Arch's. > > One package, texlive-core, failed to install completely, however, > and I diagnosed the problem, and found a workaround logged in > these system notes: > > When I installed texlive-core, I found that the installation step > failed because of missing Czech fonts (.../cs/cs*.mf). A comparison > with Arch Linux showed that Hyperbola is missing many files: > > hyperbola: > # pacman -Fl texlive-core | wc -l > 16266 > > archlinux: > # pacman -Fl texlive-core | wc -l > 24069 > > I was able to temporarily repair the problem like this: > > # fmtutil-sys --listcfg > # fmtutil-sys --disablefmt csplain > # fmtutil-sys --disablefmt cslatex > # fmtutil-sys --all > > Now the Czech fonts are disabled, and the remaining *.fmt files are created: > > hyperbola: > # find /var/lib/texmf/web2c -name '*.fmt' |wc -l > 18 > > archlinux: > # find /var/lib/texmf/web2c -name '*.fmt' |wc -l > 38 > > It is unclear why almost 8000 files are missing from texlive-core > compared to the package on Arch Linux. > > I'm a member of the TeX Live team that prepares the annual releases, > and I have TeX installed on almost 200 systems in the farm without > ever seeing a problem like this, until I build the Hyperbola system. > > ------------------------------------------------------------------------------- > - Nelson H. F. Beebe Tel: +1 801 581 5254 - > - University of Utah FAX: +1 801 581 4148 - > - Department of Mathematics, 110 LCB Internet e-mail: beebe at math.utah.edu - > - 155 S 1400 E RM 233 beebe at acm.org beebe at computer.org - > - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ - > ------------------------------------------------------------------------------- > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > -- ~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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From christianity at posteo.net Mon Dec 4 16:41:43 2017 From: christianity at posteo.net (Christian) Date: Mon, 4 Dec 2017 11:41:43 -0500 Subject: [Dev] PCR requests Message-ID: <20171204114143.71cbc23a@posteo.net> Hello, Would anyone be willing to add mist and bisq from the AUR to the PCR? Thanks! -Christian From bill-auger at peers.community Thu Dec 7 00:57:31 2017 From: bill-auger at peers.community (bill-auger) Date: Wed, 6 Dec 2017 19:57:31 -0500 Subject: [Dev] PCR requests In-Reply-To: <20171204114143.71cbc23a@posteo.net> References: <20171204114143.71cbc23a@posteo.net> Message-ID: On 12/04/2017 11:41 AM, Christian wrote: > Hello, > > Would anyone be willing to add mist and bisq from the AUR to the PCR? there exist open package requests for these on the bug tracker mist: https://labs.parabola.nu/issues/1482 bisq: https://labs.parabola.nu/issues/1481 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From andreas at grapentin.org Fri Dec 8 05:54:16 2017 From: andreas at grapentin.org (Andreas Grapentin) Date: Fri, 8 Dec 2017 06:54:16 +0100 Subject: [Dev] texlive-core problem, and repairs In-Reply-To: <8d56c72d-1ed8-72d8-dd84-4e9f5deeb4f5@hyperbola.info> References: <8d56c72d-1ed8-72d8-dd84-4e9f5deeb4f5@hyperbola.info> Message-ID: <20171208055416.GA28865@parabola-pocket.localdomain> On Wed, Dec 06, 2017 at 03:07:59PM -0300, Megver83 wrote: > El 06/12/17 a las 12:14, Nelson H. F. Beebe escribi?: > > I built a new machine running Hyperbola 0.2.1 in our test farm of > > Unix(-like) systems, and successfully installed more than 650 > > packages on it with "pacman -Sy", based on a similar list from > > an Arch Linux system in the farm. > > I'm sorry, but I think you confused the mailing list. This is Parabola's > dev list, not Hyperbola's nor Arch's. While Megver is technically correct, this is an issue that *does* affect us as well, and I have noticed it before when using LaTeX: # pacman -Fl texlive-core | wc -l 16194 > > > > > One package, texlive-core, failed to install completely, however, > > and I diagnosed the problem, and found a workaround logged in > > these system notes: > > > > When I installed texlive-core, I found that the installation step > > failed because of missing Czech fonts (.../cs/cs*.mf). A comparison > > with Arch Linux showed that Hyperbola is missing many files: > > > > hyperbola: > > # pacman -Fl texlive-core | wc -l > > 16266 > > > > archlinux: > > # pacman -Fl texlive-core | wc -l > > 24069 > > > > I was able to temporarily repair the problem like this: > > > > # fmtutil-sys --listcfg > > # fmtutil-sys --disablefmt csplain > > # fmtutil-sys --disablefmt cslatex > > # fmtutil-sys --all > > > > Now the Czech fonts are disabled, and the remaining *.fmt files are created: > > > > hyperbola: > > # find /var/lib/texmf/web2c -name '*.fmt' |wc -l > > 18 > > > > archlinux: > > # find /var/lib/texmf/web2c -name '*.fmt' |wc -l > > 38 > > > > It is unclear why almost 8000 files are missing from texlive-core > > compared to the package on Arch Linux. This is probably due to the fact that we remove a bunch of nonfree parts of texlive-core, that have incompatible licenses, or no license at all. You can have a look at the script that generates the package here: https://git.parabola.nu/abslibre.git/tree/libre/texlive-core/PKGBUILD From the issues you describe, I guess we are removing some things incorrectly, ore incompletely. Can you maybe take a look at the PKGBUILD and suggest a possible improvement? :) Thanks for reporting this, Andreas -- ------------------------------------------------------------------------------ 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 andreas at grapentin.org Fri Dec 8 05:58:28 2017 From: andreas at grapentin.org (Andreas Grapentin) Date: Fri, 8 Dec 2017 06:58:28 +0100 Subject: [Dev] PCR requests In-Reply-To: References: <20171204114143.71cbc23a@posteo.net> Message-ID: <20171208055828.GB28865@parabola-pocket.localdomain> bisq looks ok, but the mist PKGBUILD on the AUR is unusable, because it builds the package from .deb packages rather that from source. -A On Wed, Dec 06, 2017 at 07:57:31PM -0500, bill-auger wrote: > > > On 12/04/2017 11:41 AM, Christian wrote: > > Hello, > > > > Would anyone be willing to add mist and bisq from the AUR to the PCR? > > there exist open package requests for these on the bug tracker > mist: https://labs.parabola.nu/issues/1482 > bisq: https://labs.parabola.nu/issues/1481 > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ 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 megver83 at hyperbola.info Fri Dec 8 13:55:41 2017 From: megver83 at hyperbola.info (Megver83) Date: Fri, 8 Dec 2017 10:55:41 -0300 Subject: [Dev] PCR requests In-Reply-To: <20171208055828.GB28865@parabola-pocket.localdomain> References: <20171204114143.71cbc23a@posteo.net> <20171208055828.GB28865@parabola-pocket.localdomain> Message-ID: <1e1c1f06-b583-1faf-98c4-1e748fb103ba@hyperbola.info> El 08/12/17 a las 02:58, Andreas Grapentin escribi?: > > bisq looks ok, but the mist PKGBUILD on the AUR is unusable, because it > builds the package from .deb packages rather that from source. > > -A > > On Wed, Dec 06, 2017 at 07:57:31PM -0500, bill-auger wrote: >> >> >> On 12/04/2017 11:41 AM, Christian wrote: >>> Hello, >>> >>> Would anyone be willing to add mist and bisq from the AUR to the PCR? >> >> there exist open package requests for these on the bug tracker >> mist: https://labs.parabola.nu/issues/1482 >> bisq: https://labs.parabola.nu/issues/1481 >> > > > > >> _______________________________________________ >> Dev mailing list >> Dev at lists.parabola.nu >> https://lists.parabola.nu/mailman/listinfo/dev > > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > most AUR PKGBUILDs are crappy, sometimes I prefer to make my own PKGBUILDs which build from source correctly. -- ~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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Sat Dec 9 20:10:29 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 09 Dec 2017 20:10:29 -0000 Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date Message-ID: <20171209201029.26946.64195@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * icecat-noscript 5.1.7-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-noscript/ The user provided the following additional text: Current release is 5.1.8.2 From jc_gargma at iserlohn-fortress.net Sat Dec 9 20:12:27 2017 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Sat, 09 Dec 2017 12:12:27 -0800 Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date In-Reply-To: <20171209201029.26946.64195@proton.parabola.nu> References: <20171209201029.26946.64195@proton.parabola.nu> Message-ID: <2457245.SA3szlaFZz@iserlohn-fortress.net> > The user provided the following additional text: I've attached a git format-patch to update icecat-noscript to 5.1.8.2 -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-icecat-noscript-to-5.1.8.2.patch Type: text/x-patch Size: 999 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From nobody at parabola.nu Tue Dec 12 12:51:07 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 12 Dec 2017 12:51:07 -0000 Subject: [Dev] Orphan Libre package [tp_smapi] marked out-of-date Message-ID: <20171212125107.26948.80424@proton.parabola.nu> kaito.rtrt at gmail.com wants to notify you that the following packages may be out-of-date: * tp_smapi 0.42-31.parabola1.basekernel4.13 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/tp_smapi/ * tp_smapi 0.42-31.parabola1.basekernel4.13 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/tp_smapi/ The user provided the following additional text: Now the base kernel should be 4.14. Thanks. From fjdksl at cock.li Wed Dec 13 05:19:32 2017 From: fjdksl at cock.li (Attic Hermit) Date: Wed, 13 Dec 2017 14:19:32 +0900 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. Message-ID: <87fu8fi4rf.fsf@gmail.com> Dear Parabola hackers. I think there's a bug in the latest update related with cryptsetup and linux-libre-4.14.4_gnu-1, which makes fully encrypted systems unbootable. My system configuration is like below: /dev/sda1 : GRUB-BIOS /dev/sda2 : /boot (plain) /dev/sda3 : / (encrypted) The latest update of Parabola makes my system unbootable. When I booted the system, system kept prompting that the kernel doesn't support aes-xts-plain. So I booted into the system with the rescue USB thumb, and tried to reinstall the kernel, linux-libre-4.14.4_gnu-1 and saw the error like below: [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/lib/systemd/systemd-udevd' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/udevadm' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/systemd-tmpfiles' I thought the above was probably caused by cryptsetup-2.0.0-1 which updated recently, so I downgraded it to cryptsetup-1.7.5-2 and reinstalled the kernel, and successfully booted into the system. Here's the full log message where I got the error: [2017-12-13 13:38] [ALPM] reinstalled linux-libre (4.14.4_gnu-1) [2017-12-13 13:38] [ALPM-SCRIPTLET] /tmp/alpm_fZaZCJ/.INSTALL: line 6: syntax error near unexpected token `}' [2017-12-13 13:38] [ALPM-SCRIPTLET] /tmp/alpm_fZaZCJ/.INSTALL: line 6: `}' [2017-12-13 13:38] [ALPM-SCRIPTLET] /usr/bin/bash: post_upgrade: command not found [2017-12-13 13:38] [ALPM] transaction completed [2017-12-13 13:38] [ALPM] running '60-linux-libre.hook'... [2017-12-13 13:38] [ALPM] running '90-linux-libre.hook'... [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'default' [2017-12-13 13:38] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre.img [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Starting build: 4.14.4-gnu-1 [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [base] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [udev] [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/lib/systemd/systemd-udevd' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/udevadm' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/systemd-tmpfiles' [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [autodetect] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [keymap] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [block] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_crypt' [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_snapshot' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_cache' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_cache_smq' [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_thin_pool' [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [fsck] [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> WARNING: No modules were added to the image. This is probably not what you want. [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre.img [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. Here's the full log message after the downgrade: [2017-12-13 13:43] [PACMAN] Running 'pacman -U cryptsetup-1.7.5-2-x86_64.pkg.tar.xz' [2017-12-13 13:43] [ALPM] transaction started [2017-12-13 13:43] [ALPM] downgraded cryptsetup (2.0.0-1 -> 1.7.5-2) [2017-12-13 13:43] [ALPM] transaction completed [2017-12-13 13:43] [ALPM] running '90-linux-libre.hook'... [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'default' [2017-12-13 13:43] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre.img [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Starting build: 4.13.11-gnu-1 [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [base] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [udev] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [autodetect] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keymap] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [block] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [fsck] [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Generating module dependencies [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre.img [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Image generation successful [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'fallback' [2017-12-13 13:43] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre-fallback.img -S autodetect [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Starting build: 4.13.11-gnu-1 [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [base] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [udev] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keymap] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [modconf] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [block] [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: isci [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [fsck] [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Generating module dependencies [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre-fallback.img [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Image generation successful [2017-12-13 13:43] [ALPM] running 'systemd-update.hook'... P.S. I'm not confident that this is the right ML to post a bug like this. -- Attic Hermit From uaqben at disroot.org Wed Dec 13 08:56:48 2017 From: uaqben at disroot.org (Ben) Date: Wed, 13 Dec 2017 09:56:48 +0100 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. In-Reply-To: <87fu8fi4rf.fsf@gmail.com> References: <87fu8fi4rf.fsf@gmail.com> Message-ID: <2e2cedfd-5a8e-9e07-97cf-88e3847bd3aa@disroot.org> On 12/13/2017 06:19 AM, Attic Hermit wrote: > > Dear Parabola hackers. > > I think there's a bug in the latest update related with cryptsetup and > linux-libre-4.14.4_gnu-1, which makes fully encrypted systems > unbootable. > > My system configuration is like below: > > /dev/sda1 : GRUB-BIOS > /dev/sda2 : /boot (plain) > /dev/sda3 : / (encrypted) > > The latest update of Parabola makes my system unbootable. When I booted > the system, system kept prompting that the kernel doesn't support > aes-xts-plain. So I booted into the system with the rescue USB thumb, > and tried to reinstall the kernel, linux-libre-4.14.4_gnu-1 and saw the > error like below: > > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/lib/systemd/systemd-udevd' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/udevadm' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/systemd-tmpfiles' > > I thought the above was probably caused by cryptsetup-2.0.0-1 which > updated recently, so I downgraded it to cryptsetup-1.7.5-2 and > reinstalled the kernel, and successfully booted into the system. > > Here's the full log message where I got the error: > > [2017-12-13 13:38] [ALPM] reinstalled linux-libre (4.14.4_gnu-1) > [2017-12-13 13:38] [ALPM-SCRIPTLET] /tmp/alpm_fZaZCJ/.INSTALL: line 6: syntax error near unexpected token `}' > [2017-12-13 13:38] [ALPM-SCRIPTLET] /tmp/alpm_fZaZCJ/.INSTALL: line 6: `}' > [2017-12-13 13:38] [ALPM-SCRIPTLET] /usr/bin/bash: post_upgrade: command not found > [2017-12-13 13:38] [ALPM] transaction completed > [2017-12-13 13:38] [ALPM] running '60-linux-libre.hook'... > [2017-12-13 13:38] [ALPM] running '90-linux-libre.hook'... > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'default' > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre.img > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Starting build: 4.14.4-gnu-1 > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [base] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [udev] > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/lib/systemd/systemd-udevd' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/udevadm' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libcryptsetup.so.4' not found for `/usr/bin/systemd-tmpfiles' > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [autodetect] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [keymap] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [modconf] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [block] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_crypt' > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_snapshot' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_cache' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_cache_smq' > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> ERROR: module not found: `dm_thin_pool' > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] > [2017-12-13 13:38] [ALPM-SCRIPTLET] -> Running build hook: [fsck] > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> WARNING: No modules were added to the image. This is probably not what you want. > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre.img > [2017-12-13 13:38] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete. > > Here's the full log message after the downgrade: > > [2017-12-13 13:43] [PACMAN] Running 'pacman -U cryptsetup-1.7.5-2-x86_64.pkg.tar.xz' > [2017-12-13 13:43] [ALPM] transaction started > [2017-12-13 13:43] [ALPM] downgraded cryptsetup (2.0.0-1 -> 1.7.5-2) > [2017-12-13 13:43] [ALPM] transaction completed > [2017-12-13 13:43] [ALPM] running '90-linux-libre.hook'... > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'default' > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre.img > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Starting build: 4.13.11-gnu-1 > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [base] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [udev] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [autodetect] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keymap] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [modconf] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [block] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [fsck] > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Generating module dependencies > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre.img > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Image generation successful > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-libre.preset: 'fallback' > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux-libre -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-libre-fallback.img -S autodetect > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Starting build: 4.13.11-gnu-1 > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [base] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [udev] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keyboard] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [keymap] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [consolefont] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [modconf] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [block] > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: isci > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [encrypt] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [lvm2] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [filesystems] > [2017-12-13 13:43] [ALPM-SCRIPTLET] -> Running build hook: [fsck] > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Generating module dependencies > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-libre-fallback.img > [2017-12-13 13:43] [ALPM-SCRIPTLET] ==> Image generation successful > [2017-12-13 13:43] [ALPM] running 'systemd-update.hook'... > > P.S. I'm not confident that this is the right ML to post a bug like > this. > I just had the same error messages upon upgrading; so without rebooting I've just downgraded cryptsetup back to 1.7.5-2 From fjdksl at cock.li Wed Dec 13 13:48:42 2017 From: fjdksl at cock.li (Attic Hermit) Date: Wed, 13 Dec 2017 22:48:42 +0900 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. In-Reply-To: <87fu8fi4rf.fsf@gmail.com> References: <87fu8fi4rf.fsf@gmail.com> Message-ID: <87374epwlh.fsf@gmail.com> And this bug causes that the system can't mount encrypted storages either. I downgraded cryptsetup to 1.7.5-2, but some reason, the system fails with prompting "'bd_crypto_luks_open_blob' called, but not implemented!". So I restore my system from a snapshot and downgraded completely. -- Attic Hermit From uaqben at disroot.org Wed Dec 13 14:57:44 2017 From: uaqben at disroot.org (Ben) Date: Wed, 13 Dec 2017 15:57:44 +0100 Subject: [Dev] Net Neutrality / tomorrow's EEUU vote Message-ID: Are we joining https://www.battleforthenet.com/breaktheinternet ? From nobody at parabola.nu Wed Dec 13 16:08:35 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 13 Dec 2017 16:08:35 -0000 Subject: [Dev] Orphan Libre package [asciidoc] marked out-of-date Message-ID: <20171213160835.26949.18918@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * asciidoc 8.6.9-3.parabola1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/asciidoc/ The user provided the following additional text: Current release is 8.6.10 From nobody at parabola.nu Wed Dec 13 16:20:55 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 13 Dec 2017 16:20:55 -0000 Subject: [Dev] Orphan Libre package [iceweasel-noscript] marked out-of-date Message-ID: <20171213162055.26946.90104@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * iceweasel-noscript 10.1.5.5-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-noscript/ The user provided the following additional text: Current release is 10.1.5.7 From jc_gargma at iserlohn-fortress.net Wed Dec 13 16:23:08 2017 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Wed, 13 Dec 2017 08:23:08 -0800 Subject: [Dev] Orphan Libre package [iceweasel-noscript] marked out-of-date In-Reply-To: <20171213162055.26946.90104@proton.parabola.nu> References: <20171213162055.26946.90104@proton.parabola.nu> Message-ID: <2322822.HXcs5qXJdL@iserlohn-fortress.net> > The user provided the following additional text: I've attached a git format-patch to update iceweasel-noscript to 10.1.5.7 -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-iceweasel-noscript-to-10.1.5.7.patch Type: text/x-patch Size: 1029 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From nobody at parabola.nu Wed Dec 13 22:26:16 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 13 Dec 2017 22:26:16 -0000 Subject: [Dev] Orphan Libre package [kio] marked out-of-date Message-ID: <20171213222616.26949.5242@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * kio 5.38.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kio/ * kio 5.40.0-3.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kio/ * kio 5.40.0-3.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio/ The user provided the following additional text: Current release is 5.41.0 From jc_gargma at iserlohn-fortress.net Wed Dec 13 22:30:36 2017 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Wed, 13 Dec 2017 14:30:36 -0800 Subject: [Dev] Orphan Libre package [kio] marked out-of-date In-Reply-To: <20171213222616.26949.5242@proton.parabola.nu> References: <20171213222616.26949.5242@proton.parabola.nu> Message-ID: <33628412.KJRFI5G0Fl@iserlohn-fortress.net> > The user provided the following additional text: I've attached a git format-patch to update kio to 5.41.0 -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-kio-to-5.41.0.patch Type: text/x-patch Size: 2109 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From andreas at grapentin.org Thu Dec 14 13:46:41 2017 From: andreas at grapentin.org (Andreas Grapentin) Date: Thu, 14 Dec 2017 14:46:41 +0100 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. In-Reply-To: <87374epwlh.fsf@gmail.com> References: <87fu8fi4rf.fsf@gmail.com> <87374epwlh.fsf@gmail.com> Message-ID: <20171214134641.GA30948@parabola-pocket.localdomain> This is the combination of 2 problems: first, kernel version 4.14.4 was broken, and we downgraded the repos to back to the latest 4.13 kernel to adress this issue secondly, and completely unrelatedly, arch pushed a major version updat to cryptsetup from 1.* to 2.0, which broke our systemd build. This has also been corrected through a rebuild of systemd. So in theory, it should be safe again to upgrade. Best, Andreas On Wed, Dec 13, 2017 at 10:48:42PM +0900, Attic Hermit wrote: > > And this bug causes that the system can't mount encrypted storages > either. I downgraded cryptsetup to 1.7.5-2, but some reason, the system > fails with prompting "'bd_crypto_luks_open_blob' called, but not > implemented!". > > So I restore my system from a snapshot and downgraded completely. > > -- > Attic Hermit > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ 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 fauno at endefensadelsl.org Thu Dec 14 17:52:19 2017 From: fauno at endefensadelsl.org (fauno) Date: Thu, 14 Dec 2017 14:52:19 -0300 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. In-Reply-To: <20171214134641.GA30948@parabola-pocket.localdomain> References: <87fu8fi4rf.fsf@gmail.com> <87374epwlh.fsf@gmail.com> <20171214134641.GA30948@parabola-pocket.localdomain> Message-ID: <87a7ylmc30.fsf@endefensadelsl.org> Andreas Grapentin writes: > This is the combination of 2 problems: > > first, kernel version 4.14.4 was broken, and we downgraded the repos to > back to the latest 4.13 kernel to adress this issue > > secondly, and completely unrelatedly, arch pushed a major version updat > to cryptsetup from 1.* to 2.0, which broke our systemd build. This has > also been corrected through a rebuild of systemd. > > So in theory, it should be safe again to upgrade. awesome! is it possible to make systemd have a hard depend on cryptsetup's libraries? -- }(:= -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 617 bytes Desc: not available URL: From nobody at parabola.nu Thu Dec 14 19:35:15 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 14 Dec 2017 19:35:15 -0000 Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked out-of-date Message-ID: <20171214193515.26946.85442@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * icecat-ublock-origin 1.14.20-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-ublock-origin/ The user provided the following additional text: Current release is 1.14.22 From jc_gargma at iserlohn-fortress.net Thu Dec 14 19:38:22 2017 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Thu, 14 Dec 2017 11:38:22 -0800 Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked out-of-date In-Reply-To: <20171214193515.26946.85442@proton.parabola.nu> References: <20171214193515.26946.85442@proton.parabola.nu> Message-ID: <5690371.aPG1Qs4RVA@iserlohn-fortress.net> > The user provided the following additional text: I've attached a git format-patch to update icecat-ublock-origin and iceweasel- ublock-origin to 1.14.22 -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-icecat-iceweasel-ublock-origin-to-1.14.22.patch Type: text/x-patch Size: 1847 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From mcgregor at mailoo.org Thu Dec 14 21:01:14 2017 From: mcgregor at mailoo.org (mcgregor at mailoo.org) Date: Thu, 14 Dec 2017 22:01:14 +0100 Subject: [Dev] cryptsetup-2.0.0-1 makes system unbootable. In-Reply-To: <20171214134641.GA30948@parabola-pocket.localdomain> References: <87fu8fi4rf.fsf@gmail.com> <87374epwlh.fsf@gmail.com> <20171214134641.GA30948@parabola-pocket.localdomain> Message-ID: <87a7yldnxh.fsf@MiddleEarth.home> Andreas Grapentin writes: > > So in theory, it should be safe again to upgrade. After downgrading linux-libre and cryptsetup, all is fine again. From lukeshu at lukeshu.com Sat Dec 16 02:26:45 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Fri, 15 Dec 2017 21:26:45 -0500 Subject: [Dev] [RFC] modular pacman.conf and makepkg.conf by default Message-ID: <87lgi3o1ay.wl-lukeshu@lukeshu.com> Hi, What do you guys think about modifying the default pacman.conf to have this at the end: Include = /etc/pacman.d/*.conf and the default makepkg.conf to have this at the end: for file in /etc/makepkg.d/*.conf; do if [[ -f "$file" ]]; then source "$file" fi done unset file This would make it easier for configuration packages (like Holo packages or / ) to add bits to their configurations. - As an admin of several Parabola-running servers, including the parabola.nu servers, that is appealing to me. - As the developer of a package (libretools) that has to modify the default makepkg.conf, that is appealing to me. - As someone involved in Holo, which works best with modular config files, that is appealing to me. One of the few things that I like more than writing code is deleting code. And it would let me phase-out and delete the `librefetch-install` program. On one hand, we don't like unnecessarily modifying the default configuration files from upstream; but we're patching makepkg anyway; and we are the single source of truth for the default pacman & makepkg configs on Parabola. -- Happy hacking, ~ Luke Shumaker From info at jeweet.net Sat Dec 16 09:39:05 2017 From: info at jeweet.net (jeweet) Date: Sat, 16 Dec 2017 10:39:05 +0100 Subject: [Dev] Repo mirror Message-ID: <1513417145.5857.11.camel@jeweet.net> Hi guys, I have a mirror up and running on https://jeweet.net/repo/parabola. Currently it has a 30mbit bandwith limit (this can be more in the future, I don't know what amount of traffic to expect). The repo is based in the Netherlands. It sync's every 10 minutes with repo.parabola.nu via rsync. If it fits the public interest in this way, can I offer it to be on the list of mirrors on the wiki? Cheers, jeweet_ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From nobody at parabola.nu Sat Dec 16 20:45:50 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 16 Dec 2017 20:45:50 -0000 Subject: [Dev] Orphan Libre package [doublecmd-qt] marked out-of-date Message-ID: <20171216204550.26948.49784@proton.parabola.nu> woroof at gmail.com wants to notify you that the following packages may be out-of-date: * doublecmd-gtk2 0.7.8-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/doublecmd-gtk2/ * doublecmd-gtk2 0.7.8-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/doublecmd-gtk2/ * doublecmd-qt 0.7.8-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/doublecmd-qt/ * doublecmd-qt 0.7.8-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/doublecmd-qt/ The user provided the following additional text: Thank you for maintaining this package! A new version has been released: https://sourceforge.net/p/doublecmd/news/2017/12/double-commander-080-beta-released/ https://www.archlinux.org/packages/community/x86_64/doublecmd-qt/ From megver83 at hyperbola.info Sat Dec 16 21:01:38 2017 From: megver83 at hyperbola.info (Megver83) Date: Sat, 16 Dec 2017 18:01:38 -0300 Subject: [Dev] Linux-libre 4.14 available at [libre-testing] Message-ID: <9126c7a2-d663-475a-b020-de9d6b17b6b8@hyperbola.info> I've recently added Linux-libre 4.14.4 to [libre-testing], for all its architectures. https://git.parabola.nu/abslibre.git/commit/?id=f0d3a651744c676c319564cc0004526999412c3e Before moving it to [libre], I'd like that ppl with encrypted partitions test it and give me some feedback, since they where the ones who suffered more on the last update. Feel free to assign me new issues on the bug tracker or simply contact me on #parabola. I expect to see linux-libre 4.14.x on [libre] soon (a week maybe?), so please test it. Regards, -- ~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 -------------- 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 Sat Dec 16 21:17:12 2017 From: megver83 at hyperbola.info (Megver83) Date: Sat, 16 Dec 2017 18:17:12 -0300 Subject: [Dev] [RFC] modular pacman.conf and makepkg.conf by default In-Reply-To: <87lgi3o1ay.wl-lukeshu@lukeshu.com> References: <87lgi3o1ay.wl-lukeshu@lukeshu.com> Message-ID: <0042713e-bdea-21d0-5f9e-8b4fb1d25836@hyperbola.info> El 15/12/17 a las 23:26, Luke Shumaker escribi?: > Hi, > > What do you guys think about modifying the default pacman.conf to have > this at the end: > > Include = /etc/pacman.d/*.conf Sure, why not. In that way anyone can set up its custom repos in separated files rather than in pacman.conf itself. > > and the default makepkg.conf to have this at the end: > > for file in /etc/makepkg.d/*.conf; do > if [[ -f "$file" ]]; then > source "$file" > fi > done > unset file > I imagine that then pacman should come with an empty /etc/makepkg.d dir? Because I don't see it in my /etc dir. > This would make it easier for configuration packages (like Holo > packages or / > ) to add bits to their > configurations. > > - As an admin of several Parabola-running servers, including the > parabola.nu servers, that is appealing to me. > > - As the developer of a package (libretools) that has to modify the > default makepkg.conf, that is appealing to me. > > - As someone involved in Holo, which works best with modular config > files, that is appealing to me. > > One of the few things that I like more than writing code is deleting > code. And it would let me phase-out and delete the > `librefetch-install` program. Yea, deleting code rocks! specially when it's crappy and badly written :) > > On one hand, we don't like unnecessarily modifying the default > configuration files from upstream; but we're patching makepkg anyway; > and we are the single source of truth for the default pacman & makepkg > configs on Parabola. > -- ~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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From nospam at curso.re Sun Dec 17 14:42:48 2017 From: nospam at curso.re (nospam at curso.re) Date: Sun, 17 Dec 2017 14:42:48 +0000 Subject: [Dev] GNU Cash broken and gone from repositories? Message-ID: <87tvwpbdye.fsf@example.com> Hello, I was trying to run gnucash today and got the following error > $ gnucash > gnucash: error while loading shared libraries: libenchant.so.1: cannot > open shared object file: No such file or directory OK, I remember seeing an upgrade to enchant, I'll try to rebuild gnucash against the new version... but I could find the PKGBUILD only in AUR[1]. I could not find trace of gnucash in either the Arch nor the Parabola repos. In fact, pacman -Ss gnucash returns no result. Does anyone have any pointers to solve this issue? Thanks! FTR, the details of the package are (strangely, there is no dependency on enchant): $ pacman -Qi gnucash Name : gnucash Version : 2.6.16-3 Description : A personal and small-business financial-accounting application Architecture : x86_64 URL : http://www.gnucash.org Licenses : GPL Groups : None Provides : None Depends On : guile slib goffice0.8 libdbi-drivers libmariadbclient postgresql-libs aqbanking desktop-file-utils webkitgtk2 libgnome-keyring libgnomecanvas dconf Optional Deps : evince: for print preview yelp: help browser [installed] perl-finance-quote: for stock information lookups perl-date-manip: for stock information lookups Required By : None Optional For : None Conflicts With : None Replaces : None Installed Size : 47.94 MiB Packager : Juergen Hoetzel Build Date : Tue 20 Jun 2017 05:17:15 PM BST Install Date : Wed 21 Jun 2017 07:09:50 AM BST Install Reason : Explicitly installed Install Script : No Validated By : Signature -- S. [1] https://aur.archlinux.org/packages/gnucash/ From lukeshu at lukeshu.com Sun Dec 17 16:53:56 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sun, 17 Dec 2017 11:53:56 -0500 Subject: [Dev] [FYI] port 22 on servers going away Message-ID: <87o9mxxpln.wl-lukeshu@lukeshu.com> Hi all, For security and administration reasons, the Parabola servers have pretty much always had SSH on port 1863. However, some people previously involved with the project also enabled it on port 22. We'll be dropping that the next time we -Syu, which I anticipate to be this week. It's possible you have some configs or workflows that will need to be adjusted. Your ~/.ssh/config can be adjusted to have 1863 be the default port for Parabola's servers by adding Host parabola.nu *.parabola.nu parabolagnulinux.org *.parabolagnulinux.org Port 1863 Git remote URLs that don't specify a port should obey that setting. But, to set the port in git remote URLs, it is formatted like this: ssh://git at git.parabola.nu:1863/~git/whatever.git To set the port on an IP or hostname in ~/.ssh/known_hosts, you need to wrap the IP/hostname in square brackets: [proton.parabola.nu]:1863,[80.87.129.244]:1863 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBMADiqJyJfjxXv+8FC3JxSfGBFmhevhHTWJEoe1gc5TVEOuvPD8XXy2o5EN9IzBLLFGlZbAEKYdt3apAFPJtwfE= For Emacs TRAMP users, you set the port like /ssh:hostname#port:/path/to/file -- Happy hacking, ~ Luke Shumaker From nobody at parabola.nu Mon Dec 18 05:07:32 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 18 Dec 2017 05:07:32 -0000 Subject: [Dev] Orphan Libre package [kio-extras] marked out-of-date Message-ID: <20171218050732.1417.97560@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * kio-extras 17.08.1-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kio-extras/ * kio-extras 17.08.3-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kio-extras/ * kio-extras 17.08.3-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio-extras/ The user provided the following additional text: Current release is 17.12.0 From isacdaavid at isacdaavid.info Tue Dec 19 02:43:22 2017 From: isacdaavid at isacdaavid.info (Isaac David) Date: Mon, 18 Dec 2017 20:43:22 -0600 Subject: [Dev] Repo mirror In-Reply-To: <1513417145.5857.11.camel@jeweet.net> References: <1513417145.5857.11.camel@jeweet.net> Message-ID: <1513651402.13038.0@plebeian.isacdaavid.info> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 NotDashEscaped: You need gpg to verify this message jeweet wrote : > Hi guys, > > I have a mirror up and running on https://jeweet.net/repo/parabola. that's some sleek mirror! i'm also a bit shocked to learn that the repo consumes almost 200 GiB nowadays. > Currently it has a 30mbit bandwith limit (this can be more in the > future, I don't know what amount of traffic to expect). this is megabits _per second_, right? i don't have an estimate, but i can tell it will be very much welcome among users. the more bandwidth gets added to the pool, the merrier. > If it fits the public interest in this way, can I offer it to be on > the list of mirrors on the wiki? adding it as we speak. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEONM+8pp2kRNDV2SHM0ZuEux7qUMFAlo4fJkACgkQM0ZuEux7 qUOunhAAmTI3vOltW6K/c4puqdkDa2pkPYIChrFf5GfEydgckPD8rn9A35GQ2zQ4 POenE12Yoo5lXBk7g4qYwMGVsLEXbYxQqCRb5tX9rOz30TZ/oDDy/Vs0eW/SKk6x /JbrK7blYXPr5FQtHwvQZeVXMuyihdphsc6qrqMTU9rjeFP7CnoRuKTVIvjZ5Dwr T63BH7rrye/r7n1lMnI5DCS+AdrMhRkPDUnQmnGZIuIEDxO9VTs7VoPAR6FiVBOY eKxvNas9vQjDDQjSix4JYWbXU11didnnWyVZ/D8P7BvsATVhIOjRXFOM1x2cx6Sd 96YjWdTHXeRiCHqliDLy8dktWbJjb3gkHLsWUuu9fKCLXmWgDA4ZbhQZK12rZkKG 344cU5wfcjRLsuaHEZbi6ZOQqpmE+RJ2Rre571yrWLdfpDvG/AtC/1NGVdYlb0yw ZypGZRXq5RN7+5JVJXb/JxB+aG1LD9n7fqbcHxTmz+SBCwthMJcmsmIALcURJCb5 C/FMM6Ui2iWnlz9rNEES6LDhR0OEtnARkl3xHF5WIG9v5zGrR+LsHQIyZU1pA7Ws hGu9bCJifYK309rkV6kO9h0mmscoFpL8X0ektS7F+AOx1d+G+ppP6NC/EIwDfJey gKerkLMpRJbwpqSrqDVA+o0L34HjPrMX0eaNuM4HzPdaSH6wNB0= =ky5E -----END PGP SIGNATURE----- From nobody at parabola.nu Tue Dec 19 02:52:48 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 19 Dec 2017 02:52:48 -0000 Subject: [Dev] Orphan Libre package [iceweasel-noscript] marked out-of-date Message-ID: <20171219025248.1416.31955@proton.parabola.nu> jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date: * iceweasel-noscript 10.1.5.7-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-noscript/ The user provided the following additional text: Current release is 10.1.6 From andreas at grapentin.org Tue Dec 19 13:30:54 2017 From: andreas at grapentin.org (Andreas Grapentin) Date: Tue, 19 Dec 2017 14:30:54 +0100 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <87tvwpbdye.fsf@example.com> References: <87tvwpbdye.fsf@example.com> Message-ID: <20171219133054.GA17243@parabola-pocket.localdomain> The pkgbuild on the AUR is pretty new, which leads me to think that the package used to be in the official repos, but was demoted. this probably calls for an addition to PCR :) -A On Sun, Dec 17, 2017 at 02:42:48PM +0000, nospam at curso.re wrote: > > Hello, > > I was trying to run gnucash today and got the following error > > > $ gnucash > > gnucash: error while loading shared libraries: libenchant.so.1: cannot > > open shared object file: No such file or directory > > OK, I remember seeing an upgrade to enchant, I'll try to rebuild gnucash > against the new version... but I could find the PKGBUILD only in AUR[1]. > > I could not find trace of gnucash in either the Arch nor the Parabola > repos. In fact, pacman -Ss gnucash returns no result. > > Does anyone have any pointers to solve this issue? Thanks! > > FTR, the details of the package are (strangely, there is no dependency > on enchant): > > $ pacman -Qi gnucash > Name : gnucash > Version : 2.6.16-3 > Description : A personal and small-business financial-accounting application > Architecture : x86_64 > URL : http://www.gnucash.org > Licenses : GPL > Groups : None > Provides : None > Depends On : guile slib goffice0.8 libdbi-drivers libmariadbclient postgresql-libs aqbanking desktop-file-utils webkitgtk2 libgnome-keyring libgnomecanvas > dconf > Optional Deps : evince: for print preview > yelp: help browser [installed] > perl-finance-quote: for stock information lookups > perl-date-manip: for stock information lookups > Required By : None > Optional For : None > Conflicts With : None > Replaces : None > Installed Size : 47.94 MiB > Packager : Juergen Hoetzel > Build Date : Tue 20 Jun 2017 05:17:15 PM BST > Install Date : Wed 21 Jun 2017 07:09:50 AM BST > Install Reason : Explicitly installed > Install Script : No > Validated By : Signature > > > -- S. > > [1] https://aur.archlinux.org/packages/gnucash/ > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ 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 joseph at xylon.me.uk Tue Dec 19 17:46:51 2017 From: joseph at xylon.me.uk (Joseph Graham) Date: Tue, 19 Dec 2017 17:46:51 +0000 Subject: [Dev] [FYI] port 22 on servers going away In-Reply-To: <87o9mxxpln.wl-lukeshu@lukeshu.com> References: <87o9mxxpln.wl-lukeshu@lukeshu.com> Message-ID: <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> On Sun, Dec 17, 2017 at 11:53:56AM -0500, Luke Shumaker wrote: > For security and administration reasons, the Parabola servers have > pretty much always had SSH on port 1863. Fake security. Pointless and annoying. -- Joseph Graham, techno-philosopher and Free Software advocate. My PGP key: 0x8cd7227da467d3ed404f6eefdb590f739e5ac458 I have two blogs: www.naughtycomputer.uk and www.technologicallyadvancedhuman.uk I write software: https://www.suckmore.uk I run a web forum: https://www.freesoftwareuk.org.uk I run a public Taskenizer installation: https://taskenizer.xylon.me.uk And a platform for Free Software success stories: www.freedcomputer.net From bill-auger at peers.community Tue Dec 19 18:07:40 2017 From: bill-auger at peers.community (bill-auger) Date: Tue, 19 Dec 2017 13:07:40 -0500 Subject: [Dev] Repo mirror In-Reply-To: <1513651402.13038.0@plebeian.isacdaavid.info> References: <1513417145.5857.11.camel@jeweet.net> <1513651402.13038.0@plebeian.isacdaavid.info> Message-ID: <2b38a0b6-8022-4204-b7a4-5913ae83da70@peers.community> it should be said though, as i have noted elsewhere, that in most typical cases the parabola mirrors never get hit - if the redirector is the first mirror to try it directs to arch servers and the speed is very slow (by todays standards) - for me typically about 200kb/s - so most users never get the benefit of these nice high speed mirrors except for the libre and pcr packages do the parabola mirrors carry all of the upstream packages also? - if so perhaps it is time to stop redirecting to arch or have 2 redirectors - a new high priority one that redirects only to parabola mirrors and the existing redirector moved down to a lower priority -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Tue Dec 19 19:10:37 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 19 Dec 2017 19:10:37 -0000 Subject: [Dev] Orphan Libre package [calibre] marked out-of-date Message-ID: <20171219191037.872.81067@proton.parabola.nu> darien at cock.li wants to notify you that the following packages may be out-of-date: * calibre 3.13.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/calibre/ * calibre 3.13.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/calibre/ The user provided the following additional text: The new version is 3.14 From isacdaavid at isacdaavid.info Wed Dec 20 05:55:19 2017 From: isacdaavid at isacdaavid.info (Isaac David) Date: Tue, 19 Dec 2017 23:55:19 -0600 Subject: [Dev] Repo mirror In-Reply-To: <2b38a0b6-8022-4204-b7a4-5913ae83da70@peers.community> References: <1513417145.5857.11.camel@jeweet.net> <1513651402.13038.0@plebeian.isacdaavid.info> <2b38a0b6-8022-4204-b7a4-5913ae83da70@peers.community> Message-ID: <1513749319.3497.0@plebeian.isacdaavid.info> bill-auger wrote : > it should be said though, as i have noted elsewhere, that in most > typical cases the parabola mirrors never get hit well, that assumes most users never change the default setting. > if the redirector is the first mirror to try it directs to arch > servers and the speed is very slow (by todays standards) - for me > typically about 200kb/s should i read that as kilobits...?, because i'm getting several tens of times that speed, although i must admit i normally use my own, mirror for obvious testing reasons. > do the parabola mirrors carry all of the upstream packages also? yes, unless excluded by mirror owners. > perhaps it is time to stop redirecting to arch or have 2 redirectors - > a new high priority one that redirects only to parabola mirrors and > the existing redirector moved down to a lower priority i think the whole point of going with that order was to offload repo.parabola.nu first of all, but also our mirrors, which aren't that numerous. i like the idea of leveraging Arch. if speed is the concern then we can think of going with faster ones (shouldn't be too hard to change). surely there must be many. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From marcel at roethke.info Tue Dec 19 12:20:52 2017 From: marcel at roethke.info (=?UTF-8?Q?Marcel_R=c3=b6thke?=) Date: Tue, 19 Dec 2017 13:20:52 +0100 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <87tvwpbdye.fsf@example.com> References: <87tvwpbdye.fsf@example.com> Message-ID: On 17.12.2017 15:42, nospam at curso.re wrote: > > Hello, > > I was trying to run gnucash today and got the following error > >> $ gnucash >> gnucash: error while loading shared libraries: libenchant.so.1: cannot >> open shared object file: No such file or directory > > OK, I remember seeing an upgrade to enchant, I'll try to rebuild gnucash > against the new version... but I could find the PKGBUILD only in AUR[1]. > > I could not find trace of gnucash in either the Arch nor the Parabola > repos. In fact, pacman -Ss gnucash returns no result. > > Does anyone have any pointers to solve this issue? Thanks! gnucash was removed from the arch repos because in depends on the unmaintained and therefore unsafe webkitgtk2 package. The gnucash devs are changing that afaik, but it takes time. > > FTR, the details of the package are (strangely, there is no dependency > on enchant): While gnucash itself does not depend on enchant, webkitgtk2 does. Rebuilding the later unfortunately takes a lot of time, even more so because it is in a split package with webkitgtk(the gtk3 version), however you can modify the pkgbuild to only build the gtk2 version. From lukeshu at lukeshu.com Thu Dec 21 05:40:40 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Thu, 21 Dec 2017 00:40:40 -0500 Subject: [Dev] [FYI] port 22 on servers going away In-Reply-To: <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> References: <87o9mxxpln.wl-lukeshu@lukeshu.com> <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> Message-ID: <87lghwy6xz.wl-lukeshu@lukeshu.com> On Tue, 19 Dec 2017 12:46:51 -0500, Joseph Graham wrote: > On Sun, Dec 17, 2017 at 11:53:56AM -0500, Luke Shumaker wrote: > > For security and administration reasons, the Parabola servers have > > pretty much always had SSH on port 1863. > > Fake security. Pointless and annoying. It's not really security. It's administration. On port 22, there are so many bogus requests, that looking at the SSH logs is pointless, there's too much noise. On a weird port, you can look at the logs, and have it be useful. And having admins that look at the logs is better security. -- Happy hacking, ~ Luke Shumaker From lukeshu at lukeshu.com Thu Dec 21 06:22:13 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Thu, 21 Dec 2017 01:22:13 -0500 Subject: [Dev] problems with replacements for blacklisted packages Message-ID: <87h8sky50q.wl-lukeshu@lukeshu.com> Hi guys, I wrote a little pyalpm script for finding blacklist replacements (as in the second column in blacklist.txt). I'll be polishing it up and committing it soon, but it did identify a few problems/concerns. - unrar is replaced by both libre/unar and pcr/gna-unrar. libre/unar should drop the replaces=(unrar) line, and pcr/gna-unrar should be moved to libre. - tensorflow has several other versions that are not blacklisted: tensorflow-opt and tensorflow-opt-cuda. I think that this is an argument toward prioritizing switching to pkgbase-based blacklisting. - b43-fwcutter is not replaced by, but is provided by libre/b43-tools. For one, I am flabbergasted that whatever freedom issues b43-fwcutter has aren't also issues with b43-tools. Secondly, b43-tools should probably replaces=(b43-fwcutter), or be renamed to b43-fwcutter. - Why does linux-libre-pck provide linux-zen? Replacing it (which it doesn't do) makes a little bit of sense, but providing it makes no sense to me. - What's the deal with pcr/mesa-vanilla replacing a bunch of nvidia stuff? It seems that mesa-vanilla is unmaintained since emulatorman and coadde left, we should just drop it? - The following packages are on pcr, but should be moved to libre: figlet, mplayer-vaapi -- Happy hacking, ~ Luke Shumaker From bill-auger at peers.community Thu Dec 21 07:12:07 2017 From: bill-auger at peers.community (bill-auger) Date: Thu, 21 Dec 2017 02:12:07 -0500 Subject: [Dev] [FYI] port 22 on servers going away In-Reply-To: <87lghwy6xz.wl-lukeshu@lukeshu.com> References: <87o9mxxpln.wl-lukeshu@lukeshu.com> <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> <87lghwy6xz.wl-lukeshu@lukeshu.com> Message-ID: this is long overdue and so much that it may not even be worth mentioning - i looked at the wiki and it has specified using only port 1863 since about 2011 - so that port 22 is open is probably not even documented and very few people with any legitimate business on the parabola servers know about it -------------- 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 Dec 21 07:20:07 2017 From: bill-auger at peers.community (bill-auger) Date: Thu, 21 Dec 2017 02:20:07 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <87h8sky50q.wl-lukeshu@lukeshu.com> References: <87h8sky50q.wl-lukeshu@lukeshu.com> Message-ID: <52bf13f7-7187-a482-fd1b-23bb24c10342@peers.community> i do not know the answer to any of those questions but it is good that you looked into it so thoroughly - one thing i have been recommending for is to ensure that each blacklisted or replaced package has some meaningful description noting (however tersely) some rationale as to why it was originally declared to be the non-free status that it has and how any libre replacements address the issue -------------- 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 Dec 21 10:10:50 2017 From: bill-auger at peers.community (bill-auger) Date: Thu, 21 Dec 2017 05:10:50 -0500 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: References: <87tvwpbdye.fsf@example.com> Message-ID: <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> On 12/19/2017 07:20 AM, Marcel R?thke wrote: >> I could not find trace of gnucash in either the Arch nor the Parabola >> repos. In fact, pacman -Ss gnucash returns no result. gnucash is in the repo for ARM - im not sure why it is not build for other archs - was it previously? https://www.parabola.nu/packages/extra/armv7h/gnucash/ On 12/19/2017 07:20 AM, Marcel R?thke wrote: > gnucash was removed from the arch repos because in depends on the > unmaintained and therefore unsafe webkitgtk2 package. to be clear - i think what you meant to say was that archlinux does not build 'webkitgtk' anymore - it is not at all correct to say that webkitgtk is un-maintained nor would that imply that it is necessarily "un-safe" - webkitgtk is an actively maintained project and there was a new release just 2 days ago - also, 'webkitgtk' is still an available parabola package in the non-prism repos so it matters not what the status of that package is in archlinux - parabola will continue to build it for as long as it is useful https://webkitgtk.org/2017/12/19/webkitgtk2.18.4-released.html https://www.parabola.nu/packages/nonprism/x86_64/webkitgtk/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From marcel at roethke.info Thu Dec 21 13:29:46 2017 From: marcel at roethke.info (=?UTF-8?Q?Marcel_R=c3=b6thke?=) Date: Thu, 21 Dec 2017 14:29:46 +0100 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> References: <87tvwpbdye.fsf@example.com> <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> Message-ID: <5c38c77c-e94a-f0a8-4edb-7102b58bb864@roethke.info> On 21.12.2017 11:10, bill-auger wrote: > > On 12/19/2017 07:20 AM, Marcel R?thke wrote: >> gnucash was removed from the arch repos because in depends on the >> unmaintained and therefore unsafe webkitgtk2 package. > to be clear - i think what you meant to say was that archlinux does not > build 'webkitgtk' anymore - it is not at all correct to say that > webkitgtk is un-maintained nor would that imply that it is necessarily > "un-safe" - webkitgtk is an actively maintained project and there was a > new release just 2 days ago - also, 'webkitgtk' is still an available > parabola package in the non-prism repos so it matters not what the > status of that package is in archlinux - parabola will continue to build > it for as long as it is useful > > https://webkitgtk.org/2017/12/19/webkitgtk2.18.4-released.html > > https://www.parabola.nu/packages/nonprism/x86_64/webkitgtk/ I was referring to the archlinux package webkitgtk{,2} which provided the old api, the last release branch with that api available was 2.4.x. There seem to be numerous security problems in that version as explained on arch-dev-public[0] and the gnome blog[1]. The current stable of gnucash depends on the old api, which is not available in the repos anymore and quite frankly should be be available. [0] https://lists.archlinux.org/pipermail/arch-dev-public/2017-January/028634.html [1] https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ From raphael.melotte at gmail.com Thu Dec 21 14:19:31 2017 From: raphael.melotte at gmail.com (=?UTF-8?B?UmFwaGHDq2wgTcOpbG90dGU=?=) Date: Thu, 21 Dec 2017 15:19:31 +0100 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> References: <87tvwpbdye.fsf@example.com> <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> Message-ID: 2017-12-21 11:10 GMT+01:00 bill-auger : > > to be clear - i think what you meant to say was that archlinux does not > build 'webkitgtk' anymore - it is not at all correct to say that > webkitgtk is un-maintained nor would that imply that it is necessarily > "un-safe" - webkitgtk is an actively maintained project and there was a > new release just 2 days ago - also, 'webkitgtk' is still an available > parabola package in the non-prism repos so it matters not what the > status of that package is in archlinux - parabola will continue to build > it for as long as it is useful > > Some versions of webkitgtk and webkitgtk2 (the one used by gnucash) have known vulnerabilities that won't be patched (see [1]). Although it's not a problem in the case of gnucash as it uses html only locally (see [2]), I wouldn't recommend anyone to use any browser based on it. The package named webkit2gtk is the maintained version of webkitgtk and is the one to use for web browsing with webkit. [1]: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ [2]: https://lists.gnucash.org/pipermail/gnucash-user/2015-December/063251.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From bill-auger at peers.community Thu Dec 21 17:20:02 2017 From: bill-auger at peers.community (bill-auger) Date: Thu, 21 Dec 2017 12:20:02 -0500 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <5c38c77c-e94a-f0a8-4edb-7102b58bb864@roethke.info> References: <87tvwpbdye.fsf@example.com> <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> <5c38c77c-e94a-f0a8-4edb-7102b58bb864@roethke.info> Message-ID: <9681759f-97fd-61ba-c486-72d0f1116dc9@peers.community> On 12/21/2017 08:29 AM, Marcel R?thke wrote: > I was referring to the archlinux package webkitgtk{,2} which provided > the old api, the last release branch with that api available was 2.4.x. > > The current stable of gnucash depends on the old api, which is not > available in the repos anymore and quite frankly should be be available. i am still confused - what exactly are you suggesting that parabola should do? you say that the version you want is 2.4.x but archlinux has stopped packaging it - i am saying that it does not matter what decision archlinux has made about that package because parabola does not take that package from archlinux - parabola builds it's own version of that package for parabola - the version that is currently available in parabola today is 2.4.11 - so what exactly is the problem here? https://www.parabola.nu/packages/nonprism/x86_64/webkitgtk2/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Thu Dec 21 17:32:56 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 21 Dec 2017 17:32:56 -0000 Subject: [Dev] Orphan Libre package [linux-libre-hardened] marked out-of-date Message-ID: <20171221173256.870.64212@proton.parabola.nu> husut at amail.club wants to notify you that the following packages may be out-of-date: * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened/ * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened/ * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened/ * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened-docs/ * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened-docs/ * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened-docs/ * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened-headers/ * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened-headers/ * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened-headers/ The user provided the following additional text: https://www.parabola.nu/packages/libre/x86_64/linux-libre/ https://github.com/copperhead/linux-hardened/releases From lukeshu at lukeshu.com Thu Dec 21 18:14:39 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Thu, 21 Dec 2017 13:14:39 -0500 Subject: [Dev] [FYI] port 22 on servers going away In-Reply-To: References: <87o9mxxpln.wl-lukeshu@lukeshu.com> <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> <87lghwy6xz.wl-lukeshu@lukeshu.com> Message-ID: <87fu84x81c.wl-lukeshu@lukeshu.com> On Thu, 21 Dec 2017 02:12:07 -0500, bill-auger wrote: > this is long overdue and so much that it may not even be worth > mentioning - i looked at the wiki and it has specified using only port > 1863 since about 2011 - so that port 22 is open is probably not even > documented and very few people with any legitimate business on the > parabola servers know about it In 2011, we were only using port 1863. Port 22 was added in 2014, IIRC. -- Happy hacking, ~ Luke Shumaker From megver83 at hyperbola.info Thu Dec 21 21:31:48 2017 From: megver83 at hyperbola.info (Megver83) Date: Thu, 21 Dec 2017 18:31:48 -0300 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <87h8sky50q.wl-lukeshu@lukeshu.com> References: <87h8sky50q.wl-lukeshu@lukeshu.com> Message-ID: El 21/12/17 a las 03:22, Luke Shumaker escribi?: > Hi guys, > > I wrote a little pyalpm script for finding blacklist replacements (as > in the second column in blacklist.txt). > > I'll be polishing it up and committing it soon, but it did identify a > few problems/concerns. > > - unrar is replaced by both libre/unar and pcr/gna-unrar. libre/unar > should drop the replaces=(unrar) line, and pcr/gna-unrar should be > moved to libre. > +1 > - tensorflow has several other versions that are not blacklisted: > tensorflow-opt and tensorflow-opt-cuda. I think that this is an > argument toward prioritizing switching to pkgbase-based > blacklisting. I agree, for example the 'linux' package from arch is an split package which compiles 'linux', 'linux-headers' and 'linux-docs'. Although it might make difficult to specify its replacement. I mean, let's say we blacklist linux and linux-docs/linux-headers are automatically blacklisted. All right up to there, but where do we specify that linux-headers' replacement is linux-libre-headers? (same for -docs) > > - b43-fwcutter is not replaced by, but is provided by > libre/b43-tools. For one, I am flabbergasted that whatever freedom > issues b43-fwcutter has aren't also issues with b43-tools. > Secondly, b43-tools should probably replaces=(b43-fwcutter), or be > renamed to b43-fwcutter. Did not know about this. > > - Why does linux-libre-pck provide linux-zen? Replacing it (which it > doesn't do) makes a little bit of sense, but providing it makes no > sense to me. The Parabola Community Kernel *has the linux-zen patch* (which has BFQ, BFS and gracy's gcc kernel patch) plus a few others (as of now, apart from ZEN, it has TuxOnIce, UKSM and AUFS). So technically it does replace and provides linux-zen since, as I said, ZEN is one if the patches from PCK. > > - What's the deal with pcr/mesa-vanilla replacing a bunch of nvidia > stuff? It seems that mesa-vanilla is unmaintained since > emulatorman and coadde left, we should just drop it? We should look for packages that depend on it. If there aren't, I don't see why not removing it. > > - The following packages are on pcr, but should be moved to libre: > figlet, mplayer-vaapi > > -- ~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 -------------- 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 Thu Dec 21 21:33:36 2017 From: megver83 at hyperbola.info (Megver83) Date: Thu, 21 Dec 2017 18:33:36 -0300 Subject: [Dev] Orphan Libre package [linux-libre-hardened] marked out-of-date In-Reply-To: <20171221173256.870.64212@proton.parabola.nu> References: <20171221173256.870.64212@proton.parabola.nu> Message-ID: El 21/12/17 a las 14:32, Parabola Website Notification escribi?: > husut at amail.club wants to notify you that the following packages may be out-of-date: > > > * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened/ > * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened/ > * linux-libre-hardened 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened/ > * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened-docs/ > * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened-docs/ > * linux-libre-hardened-docs 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened-docs/ > * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-hardened-headers/ > * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-hardened-headers/ > * linux-libre-hardened-headers 4.13.13_gnu.a-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-hardened-headers/ > > > The user provided the following additional text: > > https://www.parabola.nu/packages/libre/x86_64/linux-libre/ > > https://github.com/copperhead/linux-hardened/releases > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > I haven't upgraded this pkg since there were issues with linux-libre 4.14, but as the things have improved I might update this one soon. -- ~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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Fri Dec 22 19:27:20 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 22 Dec 2017 19:27:20 -0000 Subject: [Dev] Orphan Kernels package [linux-libre-xtreme] marked out-of-date Message-ID: <20171222192720.869.54998@proton.parabola.nu> alexdowson at mailbox.org wants to notify you that the following packages may be out-of-date: The user provided the following additional text: Behind current linux-libre 4.14.8_gnu-1. From isacdaavid at isacdaavid.info Fri Dec 22 22:37:03 2017 From: isacdaavid at isacdaavid.info (Isaac David) Date: Fri, 22 Dec 2017 16:37:03 -0600 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <87h8sky50q.wl-lukeshu@lukeshu.com> References: <87h8sky50q.wl-lukeshu@lukeshu.com> Message-ID: <1513982223.29715.0@plebeian.isacdaavid.info> Luke Shumaker wrote : > I wrote a little pyalpm script for finding blacklist replacements (as > in the second column in blacklist.txt). cool. i'm eager to compare it against the one i wrote for libreblacklist using expac.[1][] i'm hoping that we will move forward with the idea sketched in [2][]. from your observations it seems that yours is doing more than just finding replacements, like delving into pkgbase and splits, and checking for accompanying provides=(). > I'll be polishing it up and committing it soon, but it did identify a > few problems/concerns. > > - unrar is replaced by both libre/unar and pcr/gna-unrar. libre/unar > should drop the replaces=(unrar) line, and pcr/gna-unrar should be > moved to libre. you packaged pcr/gna-unrar :) > - tensorflow has several other versions that are not blacklisted: > tensorflow-opt and tensorflow-opt-cuda. I think that this is an > argument toward prioritizing switching to pkgbase-based > blacklisting. sounds practical from a your-freedom perspective, but it will require that dbscripts learns how to expand pkgbase for a given Arch package, or something like that. i'm thinking of the import script specifically: there's one entry per pkgname in the databases, and pkgbase only exists as metadata IIRC. keeping the specificity might be more practical in the end. > - b43-fwcutter is not replaced by, but is provided by > libre/b43-tools. For one, I am flabbergasted that whatever freedom > issues b43-fwcutter has aren't also issues with b43-tools. > Secondly, b43-tools should probably replaces=(b43-fwcutter), or be > renamed to b43-fwcutter. i'm scratching my head over this too. their respective PKGBUILDs aren't like each other, but where does b43-tools even come from? it's not in the AUR. [1]: https://git.parabola.nu/packages/libretools.git/commit/?h=isacdaavid&id=313d1ee619363eca0b8b0742a2d58c9ce18877fd [2]: https://lists.parabola.nu/pipermail/dev/2017-October/005936.html -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From isacdaavid at isacdaavid.info Fri Dec 22 23:05:24 2017 From: isacdaavid at isacdaavid.info (Isaac David) Date: Fri, 22 Dec 2017 17:05:24 -0600 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: References: <87h8sky50q.wl-lukeshu@lukeshu.com> Message-ID: <1513983924.29715.1@plebeian.isacdaavid.info> Megver83 wrote : > let's say we blacklist linux and linux-docs/linux-headers are > automatically blacklisted. All right up to there, but where do we > specify that linux-headers' replacement is linux-libre-headers? (same > for -docs) in the PKGBUILD, as is currently done. the idea is to get rid of replacement info in blacklist.txt, and allow your-freedom to query the repos to know what it should and shouldn't conflict with. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From isacdaavid at isacdaavid.info Fri Dec 22 23:13:41 2017 From: isacdaavid at isacdaavid.info (Isaac David) Date: Fri, 22 Dec 2017 17:13:41 -0600 Subject: [Dev] GNU Cash broken and gone from repositories? In-Reply-To: <9681759f-97fd-61ba-c486-72d0f1116dc9@peers.community> References: <87tvwpbdye.fsf@example.com> <4d31e939-a028-fd6d-5f36-afc90887ea81@peers.community> <5c38c77c-e94a-f0a8-4edb-7102b58bb864@roethke.info> <9681759f-97fd-61ba-c486-72d0f1116dc9@peers.community> Message-ID: <1513984421.29715.2@plebeian.isacdaavid.info> bill-auger wrote : > i am still confused - what exactly are you suggesting that parabola > should do? you say that the version you want is 2.4.x but archlinux > has stopped packaging it. Bill, i think you misread his comment. it didn't sound like a suggestion or request to me. rather, he was explaining why GNU Cash disappeared from Arch in the first place. -- Isaac David GPG: 38D33EF29A7691134357648733466E12EC7BA943 Ring: c8ba5620e080bef9470efb314c257304ff9480f5 Tox: 0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C From fauno at endefensadelsl.org Sat Dec 23 01:48:05 2017 From: fauno at endefensadelsl.org (fauno) Date: Fri, 22 Dec 2017 22:48:05 -0300 Subject: [Dev] [FYI] port 22 on servers going away In-Reply-To: <87lghwy6xz.wl-lukeshu@lukeshu.com> References: <87o9mxxpln.wl-lukeshu@lukeshu.com> <20171219174651.w6zpjyzxizpzmvvb@avalon-stretch.home> <87lghwy6xz.wl-lukeshu@lukeshu.com> Message-ID: <87tvwikyei.fsf@endefensadelsl.org> Luke Shumaker writes: > On Tue, 19 Dec 2017 12:46:51 -0500, > Joseph Graham wrote: >> On Sun, Dec 17, 2017 at 11:53:56AM -0500, Luke Shumaker wrote: >> > For security and administration reasons, the Parabola servers have >> > pretty much always had SSH on port 1863. >> >> Fake security. Pointless and annoying. > > It's not really security. It's administration. On port 22, there are > so many bogus requests, that looking at the SSH logs is pointless, > there's too much noise. On a weird port, you can look at the logs, > and have it be useful. And having admins that look at the logs is > better security. and also because corporate networks usually block most outgoing ports including ssh but leave (left?) port 1863 open because of msn messenger B) -- :D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 617 bytes Desc: not available URL: From fauno at endefensadelsl.org Sat Dec 23 01:50:48 2017 From: fauno at endefensadelsl.org (fauno) Date: Fri, 22 Dec 2017 22:50:48 -0300 Subject: [Dev] Repo mirror In-Reply-To: <1513749319.3497.0@plebeian.isacdaavid.info> References: <1513417145.5857.11.camel@jeweet.net> <1513651402.13038.0@plebeian.isacdaavid.info> <2b38a0b6-8022-4204-b7a4-5913ae83da70@peers.community> <1513749319.3497.0@plebeian.isacdaavid.info> Message-ID: <87r2rmky9z.fsf@endefensadelsl.org> Isaac David writes: > > a new high priority one that redirects only to parabola mirrors and > > the existing redirector moved down to a lower priority > > i think the whole point of going with that order was to offload > repo.parabola.nu first of all, but also our mirrors, which aren't that > numerous. i like the idea of leveraging Arch. if speed is the concern > then we can think of going with faster ones (shouldn't be too hard > to change). surely there must be many. those arch mirrors were randomly selected for the redirector poc, but they can be changed to something better :) iirc lukeshu made it redirect to parabola mirrors for [libre*] and [pcr] repos? -- :D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 617 bytes Desc: not available URL: From lukeshu at lukeshu.com Sat Dec 23 02:52:45 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Fri, 22 Dec 2017 21:52:45 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <1513982223.29715.0@plebeian.isacdaavid.info> References: <87h8sky50q.wl-lukeshu@lukeshu.com> <1513982223.29715.0@plebeian.isacdaavid.info> Message-ID: <87d136xiiq.wl-lukeshu@lukeshu.com> On Fri, 22 Dec 2017 17:37:03 -0500, Isaac David wrote: > > Luke Shumaker wrote : > > I wrote a little pyalpm script for finding blacklist replacements (as > > in the second column in blacklist.txt). > > cool. i'm eager to compare it against the one i wrote for > libreblacklist using expac.[1][] i'm hoping that we will > move forward with the idea sketched in [2][]. > > from your observations it seems that yours is doing more than just > finding replacements, like delving into pkgbase and splits, and > checking for accompanying provides=(). > > [1]: https://git.parabola.nu/packages/libretools.git/commit/?h=isacdaavid&id=313d1ee619363eca0b8b0742a2d58c9ce18877fd > [2]: https://lists.parabola.nu/pipermail/dev/2017-October/005936.html https://git.parabola.nu/blacklist.git/commit/?id=d13133aec0060f975c410bd95156ad9369e80188 It works very similarly to your expac version. The expac one looks at pkgname, replaces, and provides; mine looks at pkgname and replaces only, but if there are 0 pkgname/replaces matches, *then* it falls back to looking at provides as "suggestions". It has a very similar list of caveats to the expac one: - It shows all replacements (comma-separated), rather than just one. By grepping for comma, I identified packages with multiple replacements, which I consider to be an error. - It uses the repos on the system, configured in pacman.conf - Replacements are show as repo/pkgname, rather than just pkgname. By grepping for lines that don't contain "libre/" or "libre-multilib/", I identified packages that should be moved to [libre], as well as identifying variants of non-free packages from Arch that aren't blacklisted ("community/tensorflow-opt" showing up as a suggested replacement for tensorflow). -- Happy hacking, ~ Luke Shumaker From lukeshu at lukeshu.com Sat Dec 23 03:06:56 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Fri, 22 Dec 2017 22:06:56 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <1513982223.29715.0@plebeian.isacdaavid.info> References: <87h8sky50q.wl-lukeshu@lukeshu.com> <1513982223.29715.0@plebeian.isacdaavid.info> Message-ID: <87bmiqxhv3.wl-lukeshu@lukeshu.com> On Fri, 22 Dec 2017 17:37:03 -0500, Isaac David wrote: > Luke Shumaker wrote : > > - b43-fwcutter is not replaced by, but is provided by > > libre/b43-tools. For one, I am flabbergasted that whatever freedom > > issues b43-fwcutter has aren't also issues with b43-tools. > > Secondly, b43-tools should probably replaces=(b43-fwcutter), or be > > renamed to b43-fwcutter. > > i'm scratching my head over this too. their respective PKGBUILDs > aren't like each other, but where does b43-tools even come from? it's > not in the AUR. > > [1]: https://git.parabola.nu/packages/libretools.git/commit/?h=isacdaavid&id=313d1ee619363eca0b8b0742a2d58c9ce18877fd > [2]: https://lists.parabola.nu/pipermail/dev/2017-October/005936.html I asked Emulatorman on #hyperbola Rough timeline: - core/b43-fwcutter is only useful with non-free firmware - core/b43-fwcutter is blacklisted because of the above - openfwwf, a libre b43 firmware, is released - Emulatorman packages libre/b43-tools for openfwwf, either not realizing that core/b43-fwcutter would work with openfwwf, or forgetting that core/b43-fwcutter ever existed. The b43-fwcutter program in both packages is identical. The difference is that b43-tools also includes other utilities like b43-asm. So, what we should do: - unblacklist core/b43-fwcutter - have libre/b43-tools provides=() and conflicts=() b43-fwcutter, but not replaces=() - verify that openfwwf can be built with core/b43-fwcutter (that it doesn't need b43-asm or any of the other programs included in libre/b43-tools but not core/b43-fwcutter). * if it can: - move b43-tools to pcr - have openfwwf reference b43-fwcutter instead of b43-tools -- Happy hacking, ~ From bill-auger at peers.community Sat Dec 23 07:05:08 2017 From: bill-auger at peers.community (bill-auger) Date: Sat, 23 Dec 2017 02:05:08 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <87bmiqxhv3.wl-lukeshu@lukeshu.com> References: <87h8sky50q.wl-lukeshu@lukeshu.com> <1513982223.29715.0@plebeian.isacdaavid.info> <87bmiqxhv3.wl-lukeshu@lukeshu.com> Message-ID: On 12/22/2017 06:05 PM, Isaac David wrote: > the idea is to get rid of replacement info in blacklist.txt to this i want to add again that this single line of explanation in the blacklist.txt is in most cases the only documentation of why the package is blacklisted and what are the remedies - so this would make it even more imperative that the blacklisting process be fully documented On 12/22/2017 10:06 PM, Luke Shumaker wrote: > - have libre/b43-tools provides=() and conflicts=() b43-fwcutter, but > not replaces=() just to point out again what i learned from reading the archwiki on the topic of provides vs. conflicts vs. replaces that this suggestion is not in line with the original intention - not to say that it is necessarily a bad thing but when making a break from convention it is wise to be aware that it is a break from convention - e.g. the semantics of provides vs. conflicts vs. replaces in any packages from upstream are different from how parabola uses those lists - but more importantly that these are not intended to be informational in the way being described here - these attributes are functional and trigger specific behaviors in the package management tools to re-iterate the semantics as the upstream describes it: * 'provides' - is used for dependency checking - multiple packages may 'provides' (and therefore satisfy) the same dependency and any number of them may be installed at the same time * 'conflicts' - is used for conflict resolution - at most one conflicting package may be installed at any time - if you try to install a conflicting package then the package manager will ask to remove the one that is installed * replaces - is the important one for this discussion - according to the docs, when any new package is added to the repo that states that it 'replaces' another, it has the definite, immediate, and specific effect of forcefully removing the specified package from any user's system, and without asking (i think), and replacing it with the new replacement package - this happens the next time that the user `pacman -Syu` and it may even ignore any "hold" on the old package - this was intended to be used only for emergencies if, for example, some malware got into the system again im not saying that breaking convention is bad but if the package manager has these specific behaviors triggered by these lists care must be taken to ensure that the new semantics have no unintended practical side-effects if the suggestion here is for parabola to use the 'replaces' attribute for some purpose other than what is described above it may be instead a better idea to introduce a new list such as: 'libre_replaces=()' that pacman will ignore -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From lukeshu at lukeshu.com Sat Dec 23 16:36:03 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sat, 23 Dec 2017 11:36:03 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: References: <87h8sky50q.wl-lukeshu@lukeshu.com> <1513982223.29715.0@plebeian.isacdaavid.info> <87bmiqxhv3.wl-lukeshu@lukeshu.com> Message-ID: <878tdtxuz0.wl-lukeshu@lukeshu.com> The following is a discussion of the semantics of provides/conflicts/replaces. It uses b43-fwcutter as an example, but isn't about b43-fwcutter; it is written accepting the everything in my previous email as accurate; which isn't true. What we actually should do is keep blacklisting core/b43-fwcutter, remove the /usr/bin/b43-fwcutter program from libre/b43-tools, and have b43-tools make no reference to b43-fwcutter in any of provides/conflicts/replaces (perhaps note the absence of b43-fwcutter in the pkgdesc). But, in order to more directly and clearly address Bill's points, I'm going to pretend that's not true, and that the b43-fwcutter program is fine. On Sat, 23 Dec 2017 02:05:08 -0500, bill-auger wrote: > On 12/22/2017 10:06 PM, Luke Shumaker wrote: > > - have libre/b43-tools provides=() and conflicts=() b43-fwcutter, but > > not replaces=() > > just to point out again what i learned from reading the archwiki on the > topic of provides vs. conflicts vs. replaces that this suggestion is not > in line with the original intention It surely is in line with the original intention. core/b43-fwcutter provides the /usr/bin/b43-fwcutter program (and man page); libre/b43-tools also provides that program, as well as a few others. > > to re-iterate the semantics as the upstream describes it: > * 'provides' - is used for dependency checking - multiple packages may > 'provides' (and therefore satisfy) the same dependency and any number of > them may be installed at the same time If a program has b43-fwcutter as a dependency, it would be satisfied by the version of /usr/bin/b43-fwcutter included in libre/b43-tools (it is built from exactly the same sources as the version in core/b43-fwcutter; `diff -r` says so). > * 'conflicts' - is used for conflict resolution - at most one > conflicting package may be installed at any time - if you try to install > a conflicting package then the package manager will ask to remove the > one that is installed Both core/b43-fwcutter and libre/b43-tools include the file /usr/bin/b43-fwcutter; they cannot both be installed at the same time. > * replaces - is the important one for this discussion - according to the > docs, when any new package is added to the repo that states that it > 'replaces' another, it has the definite, immediate, and specific effect > of forcefully removing the specified package from any user's system, and > without asking (i think), and replacing it with the new replacement > package - this happens the next time that the user `pacman -Syu` and it > may even ignore any "hold" on the old package Pacman will prompt "Replace A with B? [Y/n]:". This can be disabled by adding the replacement to IgnorePkg in pacman.conf. > - this was intended to be > used only for emergencies if, for example, some malware got into the system This isn't only for emergencies. It is used whenever one package is dropped in favor of another package (perhaps just a package rename). When eigen3 got renamed to eigen, eigen now replaces=(eigen3). When libdbus got merged in to the dbus package, dbus now replaces=(libdbus) because otherwise -Syu wouldn't upgrade it for a user who had libdbus installed, but not dbus; they'd silently end up with an old libdbus package (it would show up in `pacman -Qm` though). If we wanted drop core/b43-fwcutter from our repos (blacklist it), then libre/b43-tools *should* replaces=() it because we are dropping one implementation of /usr/bin/b43-fwcutter for another, and the new one should replace the old one. One way of looking at it is that provides=() and conflicts=() affect all users, while replaces=() only affects *upgrades*, not *new installs*. > again im not saying that breaking convention is bad but if the package > manager has these specific behaviors triggered by these lists care must > be taken to ensure that the new semantics have no unintended practical > side-effects > > if the suggestion here is for parabola to use the 'replaces' attribute > for some purpose other than what is described above it may be instead a > better idea to introduce a new list such as: 'libre_replaces=()' that > pacman will ignore We do use replaces=() for the intended purpose. A user migrating from Arch should be asked "Replace linux with linux-libre?", "Replace firefox with iceweasel?" From the user's/pacman's perspective, upstream dropped linux in favor of linux-libre; that's exactly what replaces=() is for. -- Happy hacking, ~ Luke Shumaker From lukeshu at lukeshu.com Sat Dec 23 17:32:33 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sat, 23 Dec 2017 12:32:33 -0500 Subject: [Dev] problems with replacements for blacklisted packages In-Reply-To: <87bmiqxhv3.wl-lukeshu@lukeshu.com> References: <87h8sky50q.wl-lukeshu@lukeshu.com> <1513982223.29715.0@plebeian.isacdaavid.info> <87bmiqxhv3.wl-lukeshu@lukeshu.com> Message-ID: <877etdxscu.wl-lukeshu@lukeshu.com> On Fri, 22 Dec 2017 22:06:56 -0500, Luke Shumaker wrote: > > Luke Shumaker wrote : > > > - b43-fwcutter is not replaced by, but is provided by > > > libre/b43-tools. For one, I am flabbergasted that whatever freedom > > > issues b43-fwcutter has aren't also issues with b43-tools. > > > Secondly, b43-tools should probably replaces=(b43-fwcutter), or be > > > renamed to b43-fwcutter. > > I asked Emulatorman on #hyperbola > > Rough timeline: > > - core/b43-fwcutter is only useful with non-free firmware > - core/b43-fwcutter is blacklisted because of the above > - openfwwf, a libre b43 firmware, is released > - Emulatorman packages libre/b43-tools for openfwwf, either not > realizing that core/b43-fwcutter would work with openfwwf, or > forgetting that core/b43-fwcutter ever existed. > > The b43-fwcutter program in both packages is identical. The > difference is that b43-tools also includes other utilities like > b43-asm. > > So, what we should do: > > - unblacklist core/b43-fwcutter > - have libre/b43-tools provides=() and conflicts=() b43-fwcutter, but > not replaces=() > - verify that openfwwf can be built with core/b43-fwcutter (that it > doesn't need b43-asm or any of the other programs included in > libre/b43-tools but not core/b43-fwcutter). > * if it can: > - move b43-tools to pcr > - have openfwwf reference b43-fwcutter instead of b43-tools openfwwf requires the b43-asm program to build; core/b43-fwcutter does not provide that program; b43-tools needs to stay in [libre]. openfwwf does not depends on the b43-fwcutter program at all; it only depends on other programs included in b43-tools. The b43-fwcutter program is not useful with openfwwf. Therefore, we should - continue blacklisting core/b43-fwcutter - remove /usr/bin/b43-fwcutter from libre/b43-tools - do not include b43-fwcutter in any of libre/b43-tools' provides/conflicts/replaces Emulatorman agrees with the above assessment. - perhaps mention the absence of b43-fwcutter in libre/b43-tools' pkgdesc I have updated the documentation on the issue with b43-fwcutter on the LibrePlanet list of software that does not respect the FSDG[1], as well as in our blacklist.txt[2]. I have not yet updated the libre/b43-tools package. [1]: https://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines#b43-fwcutter_.2F_b43-tools [2]: https://git.parabola.nu/blacklist.git/commit/?id=c7ea5d453d6b3cf5e554c48707aa2e1b295c2f82 -- Happy hacking, ~ Luke Shumaker From XCH at protonmail.ch Sun Dec 24 13:37:52 2017 From: XCH at protonmail.ch (XCH) Date: Sun, 24 Dec 2017 08:37:52 -0500 Subject: [Dev] PCR Request - openfortivpn Message-ID: Hi! Can I please request inclusion of openfortivpn [1] and networkmanager-fortisslvpn-git [2] in PCR package repository? These are free software packages that enable users to connect to FortiClient VPN servers. [1] https://aur.archlinux.org/packages/openfortivpn (GPL v3) [2] [https://aur.archlinux.org/packages/networkmanager-fortisslvpn-git](https://aur.archlinux.org/packages/networkmanager-fortisslvpn-git/) (GPL v2) Many thanks, XCH Sent with [ProtonMail](https://protonmail.com) Secure Email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nobody at parabola.nu Mon Dec 25 15:06:37 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 25 Dec 2017 15:06:37 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20171225150637.869.29490@proton.parabola.nu> hobbledehoy899 at ProtonMail.com wants to notify you that the following packages may be out-of-date: * linux-libre 4.14.8_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 4.14.8_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ * linux-libre 4.14.8_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-docs 4.14.8_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 4.14.8_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ * linux-libre-docs 4.14.8_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 4.14.8_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 4.14.8_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ * linux-libre-headers 4.14.8_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: Linux 4.14.9 is out. (Merry Christmas.) From nobody at parabola.nu Mon Dec 25 15:07:43 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 25 Dec 2017 15:07:43 -0000 Subject: [Dev] Orphan Libre package [linux-libre-lts] marked out-of-date Message-ID: <20171225150743.871.21112@proton.parabola.nu> hobbledehoy899 at ProtonMail.com wants to notify you that the following packages may be out-of-date: * linux-libre-lts 4.9.70_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts/ * linux-libre-lts 4.9.70_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts/ * linux-libre-lts 4.9.70_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts/ * linux-libre-lts-docs 4.9.70_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-docs/ * linux-libre-lts-docs 4.9.70_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts-docs/ * linux-libre-lts-docs 4.9.70_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-docs/ * linux-libre-lts-headers 4.9.70_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-headers/ * linux-libre-lts-headers 4.9.70_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts-headers/ * linux-libre-lts-headers 4.9.70_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-headers/ The user provided the following additional text: Linux 4.9.72 is out. (Merry Christmas.) From nobody at parabola.nu Mon Dec 25 15:08:36 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 25 Dec 2017 15:08:36 -0000 Subject: [Dev] Orphan Kernels package [linux-libre-lts-xtreme] marked out-of-date Message-ID: <20171225150836.869.47333@proton.parabola.nu> hobbledehoy899 at ProtonMail.com wants to notify you that the following packages may be out-of-date: The user provided the following additional text: Linux 4.9.72 is out. (Merry Christmas.) From nobody at parabola.nu Mon Dec 25 15:13:52 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 25 Dec 2017 15:13:52 -0000 Subject: [Dev] Orphan Libre package [linux-libre-pck] marked out-of-date Message-ID: <20171225151352.871.73268@proton.parabola.nu> hobbledehoy899 at ProtonMail.com wants to notify you that the following packages may be out-of-date: * linux-libre-pck 4.13.12_gnu.pck1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-pck/ * linux-libre-pck 4.13.12_gnu.pck1-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-pck/ * linux-libre-pck 4.13.12_gnu.pck1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-pck/ * linux-libre-pck-docs 4.13.12_gnu.pck1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-pck-docs/ * linux-libre-pck-docs 4.13.12_gnu.pck1-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-pck-docs/ * linux-libre-pck-docs 4.13.12_gnu.pck1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-pck-docs/ * linux-libre-pck-headers 4.13.12_gnu.pck1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-pck-headers/ * linux-libre-pck-headers 4.13.12_gnu.pck1-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-pck-headers/ * linux-libre-pck-headers 4.13.12_gnu.pck1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-pck-headers/ The user provided the following additional text: Linux 4.14.9 is out. (Merry Christmas.) From lukeshu at lukeshu.com Tue Dec 26 16:45:42 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Tue, 26 Dec 2017 11:45:42 -0500 Subject: [Dev] CrazyToon has passed away Message-ID: <87y3lpwi89.wl-lukeshu@lukeshu.com> A former Parabola contributor, CrazyToon, has passed away earlier today, December 26th at 4:40 AM UTC, at the age of 60. On September 30th, he suffered two cerebral aneurysms and intracranial hemorrhages. Surgery was performed on October 13th and he entered into coma until November 1st. On November 10th, he suffered two cerebral strokes and lost all possibility of recovering his health. He proceeded to have catatonic stupor state, hard convulsions, continuous high pressure, fever and general hemorrhages. He will be remembered as the father of two other Parabola contributors, Andr? Silva ("Emulatorman") and M?rcio Silva ("coadde"); for his artwork, including Parabola's mascot; as a Free Software and Free Culture activist; and as a founder of the Hyperbola project. -- ~ Luke Shumaker From megver83 at hyperbola.info Tue Dec 26 17:50:08 2017 From: megver83 at hyperbola.info (Megver83) Date: Tue, 26 Dec 2017 14:50:08 -0300 Subject: [Dev] CrazyToon has passed away In-Reply-To: <87y3lpwi89.wl-lukeshu@lukeshu.com> References: <87y3lpwi89.wl-lukeshu@lukeshu.com> Message-ID: <65508247-29f8-277b-39a2-27aef3380444@hyperbola.info> El 26/12/17 a las 13:45, Luke Shumaker escribi?: > A former Parabola contributor, CrazyToon, has passed away earlier > today, December 26th at 4:40 AM UTC, at the age of 60. > > On September 30th, he suffered two cerebral aneurysms and intracranial > hemorrhages. Surgery was performed on October 13th and he entered > into coma until November 1st. On November 10th, he suffered two > cerebral strokes and lost all possibility of recovering his health. > He proceeded to have catatonic stupor state, hard convulsions, > continuous high pressure, fever and general hemorrhages. > > He will be remembered as the father of two other Parabola > contributors, Andr? Silva ("Emulatorman") and M?rcio Silva ("coadde"); > for his artwork, including Parabola's mascot; as a Free Software and > Free Culture activist; and as a founder of the Hyperbola project. > Thanks, for all of your work Crazytoon. All of us will remember you, your work, and your will. R.I.P. -- ~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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From adfeno at hyperbola.info Tue Dec 26 18:58:26 2017 From: adfeno at hyperbola.info (Adonay Felipe Nogueira) Date: Tue, 26 Dec 2017 16:58:26 -0200 Subject: [Dev] CrazyToon has passed away In-Reply-To: <87y3lpwi89.wl-lukeshu@lukeshu.com> (Luke Shumaker's message of "Tue, 26 Dec 2017 11:45:42 -0500") References: <87y3lpwi89.wl-lukeshu@lukeshu.com> Message-ID: <87tvwdfh9p.fsf@hyperbola.info> Thanks for your work CrazyToon, may you find peace. We'll miss you! ;) 2017-12-26T11:45:42-0500 Luke Shumaker wrote: > A former Parabola contributor, CrazyToon, has passed away earlier > today, December 26th at 4:40 AM UTC, at the age of 60. > > On September 30th, he suffered two cerebral aneurysms and intracranial > hemorrhages. Surgery was performed on October 13th and he entered > into coma until November 1st. On November 10th, he suffered two > cerebral strokes and lost all possibility of recovering his health. > He proceeded to have catatonic stupor state, hard convulsions, > continuous high pressure, fever and general hemorrhages. > > He will be remembered as the father of two other Parabola > contributors, Andr? Silva ("Emulatorman") and M?rcio Silva ("coadde"); > for his artwork, including Parabola's mascot; as a Free Software and > Free Culture activist; and as a founder of the Hyperbola project. -- - https://libreplanet.org/wiki/User:Adfeno - Palestrante e consultor sobre /software/ livre (n?o confundir com gratis). - "WhatsApp"? Ele n?o ? livre. Por favor, veja formas de se comunicar instantaneamente comigo no endere?o abaixo. - Contato: https://libreplanet.org/wiki/User:Adfeno#vCard - Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft Office, MP3, MP4, WMA, WMV. - Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU GIMP, Inkscape SVG, JPG, LibreOffice (padr?o ODF), OGG, OPUS, PDF (apenas sem DRM), PNG, TXT, WEBM. From alejandrohp at openmailbox.org Tue Dec 26 19:17:22 2017 From: alejandrohp at openmailbox.org (alejandrohp at openmailbox.org) Date: Tue, 26 Dec 2017 19:17:22 -0000 Subject: [Dev] CrazyToon has passed away Message-ID: <20171226191725.C0F874FC701@mta-1.openmailbox.org> > A former Parabola contributor, CrazyToon, has passed away earlier > today, December 26th at 4:40 AM UTC, at the age of 60. > > On September 30th, he suffered two cerebral aneurysms and intracranial > hemorrhages. Surgery was performed on October 13th and he entered > into coma until November 1st. On November 10th, he suffered two > cerebral strokes and lost all possibility of recovering his health. > He proceeded to have catatonic stupor state, hard convulsions, > continuous high pressure, fever and general hemorrhages. > > He will be remembered as the father of two other Parabola > contributors, Andr? Silva ("Emulatorman") and M?rcio Silva ("coadde"); > for his artwork, including Parabola's mascot; as a Free Software and > Free Culture activist; and as a founder of the Hyperbola project. > > -- > ~ Luke Shumaker > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev : _ _ _ ( From fauno at endefensadelsl.org Tue Dec 26 21:46:59 2017 From: fauno at endefensadelsl.org (fauno) Date: Tue, 26 Dec 2017 18:46:59 -0300 Subject: [Dev] CrazyToon has passed away In-Reply-To: <87tvwdfh9p.fsf@hyperbola.info> References: <87y3lpwi89.wl-lukeshu@lukeshu.com> <87tvwdfh9p.fsf@hyperbola.info> Message-ID: <87efnhkvqk.fsf@endefensadelsl.org> Adonay Felipe Nogueira writes: > Thanks for your work CrazyToon, may you find peace. We'll miss you! ;) sad news :( i remember we met a few years ago and had a chat over beer (or maybe i was the only beer drinker?) with emulatorman and coadde, then he bought socks from a pushy street vendor :) -- D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 617 bytes Desc: not available URL: From andreas at grapentin.org Wed Dec 27 07:32:45 2017 From: andreas at grapentin.org (Andreas Grapentin) Date: Wed, 27 Dec 2017 08:32:45 +0100 Subject: [Dev] PCR Request - openfortivpn In-Reply-To: References: Message-ID: <20171227073245.GA32138@parabola-pocket.localdomain> Hi, we are tracking packaging requests in our issue tracker here: https://labs.parabola.nu/projects/issue-tracker/issues?set_filter=1&tracker_id=7 if possible, could you add an issue for the packages you linked? That makes it easier for us to keep track of things :) Thanks, Andreas On Sun, Dec 24, 2017 at 08:37:52AM -0500, XCH wrote: > Hi! > > Can I please request inclusion of openfortivpn [1] and networkmanager-fortisslvpn-git [2] in PCR package repository? These are free software packages that enable users to connect to FortiClient VPN servers. > > [1] https://aur.archlinux.org/packages/openfortivpn (GPL v3) > [2] [https://aur.archlinux.org/packages/networkmanager-fortisslvpn-git](https://aur.archlinux.org/packages/networkmanager-fortisslvpn-git/) (GPL v2) > > Many thanks, > XCH > > Sent with [ProtonMail](https://protonmail.com) Secure Email. > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ 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 bill-auger at peers.community Wed Dec 27 08:25:31 2017 From: bill-auger at peers.community (bill-auger) Date: Wed, 27 Dec 2017 03:25:31 -0500 Subject: [Dev] PCR Request - openfortivpn In-Reply-To: <20171227073245.GA32138@parabola-pocket.localdomain> References: <20171227073245.GA32138@parabola-pocket.localdomain> Message-ID: <0f96e482-495f-a7de-0d80-05dc8ad7a40a@peers.community> i did not reply to this one because i think it may be against the FSDG to endorse this service - even if the client is open-source the third-party service it connects to is probably proprietary - unless the source code for the service backend were AGPL then parabola may be obliged to avoid directing users to this service -------------- 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 Wed Dec 27 08:28:29 2017 From: bill-auger at peers.community (bill-auger) Date: Wed, 27 Dec 2017 03:28:29 -0500 Subject: [Dev] PCR Request - openfortivpn In-Reply-To: <0f96e482-495f-a7de-0d80-05dc8ad7a40a@peers.community> References: <20171227073245.GA32138@parabola-pocket.localdomain> <0f96e482-495f-a7de-0d80-05dc8ad7a40a@peers.community> Message-ID: On 12/27/2017 03:25 AM, bill-auger wrote: > - unless the > source code for the service backend were AGPL then parabola may be > obliged to avoid directing users to this service s/AGPL/freely licensed/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From XCH at protonmail.ch Wed Dec 27 08:59:21 2017 From: XCH at protonmail.ch (XCH) Date: Wed, 27 Dec 2017 03:59:21 -0500 Subject: [Dev] PCR Request - openfortivpn In-Reply-To: <0f96e482-495f-a7de-0d80-05dc8ad7a40a@peers.community> References: <20171227073245.GA32138@parabola-pocket.localdomain> <0f96e482-495f-a7de-0d80-05dc8ad7a40a@peers.community> Message-ID: Hi, This is my concern, too. FortiClient VPN service is part of Fortinet Endpoint Protection software by Fortinet. I cannot find any trace that could suggest the software running on Fortinet devices is free software. I would assume then that it is proprietary unless proven otherwise. Personally, openfortvpn saved me from purchasing hardware with non-free OS. Fortinet offers client software (FortiClient) only for non-free OS-es and FortiClient itself is non-free I believe. Installing non-free software is unacceptable for me, but using free software to connect to this server was the only option to connect to corporate network which enforced VPN connections via their FortiClient hardware. This is not to say that I don't understand FSDG and risk of exposing Parabola users to this service that could inadverently be a form of endorsing this service. In this situation I am going to leave the packages for myself where there is no harm to the community. Ultimately the only disadvantage for me would be manual updates of the packages. Taking the opportunity I want to learn why other packages of similar characteristics are included in Parabola's repo. - freerdp [1] enables connection to Windows machines. RDP protocol originates and is predominantly used to connect to Microsoft non-free OS-es - openvpn [2] enables connecting to proprietary VPN servers communicating with standard VPN protocols [1] https://www.parabola.nu/packages/community/x86_64/freerdp/ [2] https://www.parabola.nu/packages/core/x86_64/openvpn/ Regards, XCH Sent with [ProtonMail](https://protonmail.com) Secure Email. > -------- Original Message -------- > Subject: Re: [Dev] PCR Request - openfortivpn > Local Time: 27 grudnia 2017 9:25 AM > UTC Time: 27 grudnia 2017 08:25 > From: bill-auger at peers.community > To: dev at lists.parabola.nu > > i did not reply to this one because i think it may be against the FSDG > to endorse this service - even if the client is open-source the > third-party service it connects to is probably proprietary - unless the > source code for the service backend were AGPL then parabola may be > obliged to avoid directing users to this service > > --------------------------------------------------------------- > > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From emulatorman at hyperbola.info Wed Dec 27 14:27:15 2017 From: emulatorman at hyperbola.info (=?UTF-8?Q?Andr=c3=a9_Silva?=) Date: Wed, 27 Dec 2017 14:27:15 +0000 Subject: [Dev] Thank you Crazytoon - you will be missed In-Reply-To: <95f547d1-b89a-0cae-887d-d62f8e7a1ee2@hyperbola.info> References: <95f547d1-b89a-0cae-887d-d62f8e7a1ee2@hyperbola.info> Message-ID: <2bf71edc-a7bf-afc7-b68e-b3eeba31056b@hyperbola.info> All I can say is thank you all for your support in this hard moment. God bless you and protect your love ones. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Fri Dec 29 07:12:42 2017 From: bill-auger at peers.community (bill-auger) Date: Fri, 29 Dec 2017 02:12:42 -0500 Subject: [Dev] keyring problem Message-ID: <4ea34ca4-7f1a-838b-2920-c3f58edebea0@peers.community> when running from the LiveISOs, certain packages fail to install due to unknown trust / invalid signature - i suspect this is the root cause or at least an indicator of the broken ISOs from last year and perhaps some other similar troubles with packages on which the key should be valid but require resetting the keyring manually - the problem is not specific to the ISOs though but they exhibit this behavior in the fresh default state - i have narrowed it down to some small test cases that should expose the problem on any parabola system - if anyone can, please verify these on your installed system (enable pcr-testing) on a sane system this command succeeds: $ sudo pacman -S wbar --noconfirm as well these commands: $ sudo pacman-key --init $ sudo pacman-key --populate parabola $ sudo pacman -S wbar --noconfirm but this sequence of commands fails to install the package : $ sudo rm -rf /etc/pacman.d/gnupg/ $ sudo pacman-key --init $ sudo pacman-key --populate parabola $ sudo pacman -S wbar --noconfirm and this this sequence of commands fails also: $ sudo rm -rf /etc/pacman.d/gnupg/ $ sudo pacman-key --init $ sudo pacman-key --populate parabola $ sudo pacman-key --refresh-keys $ sudo pacman -S wbar --noconfirm and this sequence of commands will succeed installing the package: $ sudo rm -rf /etc/pacman.d/gnupg/ $ sudo pacman-key --init $ sudo pacman -S wbar --noconfirm $ sudo pacman-key --populate parabola $ sudo pacman -S wbar --noconfirm the first pacman command here actually plays a role in that it imports the obviously missing key but then fails to verify the package .... :: Import PGP key 2048R/3954A7AB837D0EA9CFA9798925DB7D9B5A8D4B40, "bill-auger ", created: 2016-11-30? [Y/n] (1/1) checking package integrity error: wbar: signature from "bill-auger " is unknown trust .... then the `pacman-key --populate` command signs the key then the second pacman command succeeds - this indicates that the signing key is not in the parabola-keyring package - but it is, though you may notice two different email addresses so i suspect that one of the IDs is not known to the keyring - but they are both IDs on the same key and the key is signed by the `pacman-key --populate` command even without importing it explicitly as above - demonstrated with these commands: $ sudo rm -rf /etc/pacman.d/gnupg/ $ sudo pacman-key --init $ sudo pacman-key --populate parabola .... -> Locally signing key 3954A7AB837D0EA9CFA9798925DB7D9B5A8D4B40... .... i can only assume i have found a bug because i would think pacman should handle this situation but i dont know well enough what the intended behavior is to investigate further - for example, what should happen when pacman downloads a package signed by an unknown key as above - should that package have been validated without being signed by the local keyring master as is done in the `pacman-key --populate` command? - should it have been automatically signed by the local keyring master and then validated? - or is it expected behavior to reject the package? in which case why would it bother asking to import the key? note that the signing key is mine so i can fiddle with it if necessary - i suspect that rebuilding the parabola-keyring package would resolve this problem but i do not want to attempt that until i discover why this is happening so that i know the best procedure to use on the ISOs to make them viable for longer periods of time - perhaps the keyring should be rebuilt more regularly on a cron task or maybe pacman needs a patch to handle this without flaking out - i dunno yet - but i could use some help nailing this down from someone more experienced with pacman's innerds -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Fri Dec 29 08:42:05 2017 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 29 Dec 2017 08:42:05 -0000 Subject: [Dev] Orphan Pcr package [armory] marked out-of-date Message-ID: <20171229084205.872.42107@proton.parabola.nu> reg+parabola at disroot.org wants to notify you that the following packages may be out-of-date: * armory 0.92.3-2 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/armory/ The user provided the following additional text: https://github.com/etotheipi/BitcoinArmory/releases From bill-auger at peers.community Sat Dec 30 01:42:47 2017 From: bill-auger at peers.community (bill-auger) Date: Fri, 29 Dec 2017 20:42:47 -0500 Subject: [Dev] keyring problem In-Reply-To: <4ea34ca4-7f1a-838b-2920-c3f58edebea0@peers.community> References: <4ea34ca4-7f1a-838b-2920-c3f58edebea0@peers.community> Message-ID: <012e4a87-b3b6-8510-daef-2926d5d59f3a@peers.community> today i discovered another sequence of commands that can get this package installed that does not require installing that package twice but instead installing the keyring package twice the following command fail to install the package: # rm -rf /etc/pacman.d/gnupg/ # pacman-key --init # pacman -S --noconfirm parabola-keyring # pacman-key --populate parabola # pacman -S --noconfirm parabola-keyring # pacman -S --noconfirm wbar the following command succeed installing the package: # rm -rf /etc/pacman.d/gnupg/ # pacman-key --init # pacman -S --noconfirm parabola-keyring # pacman-key --populate parabola # pacman-key --refresh-keys # pacman -S --noconfirm parabola-keyring # pacman -S --noconfirm wbar -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From lukeshu at lukeshu.com Sun Dec 31 18:18:14 2017 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Sun, 31 Dec 2017 13:18:14 -0500 Subject: [Dev] Contributing upstream Message-ID: <87incmwyl5.wl-lukeshu@lukeshu.com> Hey, I've talked a bit about it on IRC, but I wanted there to be a real record: Recently, some of my contributions to Parabola haven't... been to Parabola. # glibc There was a bug in glibc that caused problems in systemd-nspawn that caused problems in devtools that caused problems in libretools. I wrote a patchset for it, submitted it upstream, got it on master, and then it got backported to the 2.26 stable backports branch (we have breakage in Fedora to thank for speedy backporting). And then that filtered back down to Arch glibc! bug upstream https://sourceware.org/bugzilla/show_bug.cgi?id=22145 bug Arch https://bugs.archlinux.org/task/56529 bug Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1468837 patchset master https://sourceware.org/ml/libc-alpha/2017-11/msg00546.html # QEMU The old libre/qemu-static 2.8 was increasingly complaining about unknown syscalls. So I went to upgrade it to the latest qemu, 2.11.0. Now, I discovered a major performance regression in qemu-arm when statically linked. As in 3-second startup time before it even starts emulation. I filed a bug upstream, and wrote a patchset, which is applied to the libre/qemu-user-static package. The patchset has not yet been reviewed upstream. I expect this to attract more attention once one of the major distros upgrades from 2.10. bug https://bugs.launchpad.net/qemu/+bug/1740219 patchset https://lists.nongnu.org/archive/html/qemu-devel/2017-12/msg05237.html The new qemu-user-static package hasn't yet hit i686 yet because I'm waiting for util-linux 2.31 -> 2.31.1 upgrade from archlinux32. -- Happy hacking, ~ Luke Shumaker