From nobody at parabola.nu Fri Jul 5 19:26:32 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 05 Jul 2019 19:26:32 -0000 Subject: [Dev] Orphan Libre package [minitube] marked out-of-date Message-ID: <20190705192632.1080.7267@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * minitube 2.9-3.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/minitube/ * minitube 2.9-3.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/minitube/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://flavio.tordini.org/minitube#news From lukeshu at lukeshu.com Wed Jul 10 04:35:04 2019 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 10 Jul 2019 00:35:04 -0400 Subject: [Dev] IPv6 for winston.parabola.nu Message-ID: <87k1cqpkw7.wl-lukeshu@lukeshu.com> Hi all, I've set up a Hurricane Electric IPv6 tunnel for winton.parabola.nu. It uses the same HE account as DNS. - I've added 3 AAAA records (parabola.nu, winston.parabola.nu, parabolagnulinux.org). - I've adjusted postfix to use IPv6 now. - https://labs.parabola.nu/issues/1286 Parabola infrastructure should now be IPv6 accessible. -- Happy hacking, ~ Luke Shumaker From lukeshu at lukeshu.com Wed Jul 10 16:43:12 2019 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 10 Jul 2019 12:43:12 -0400 Subject: [Dev] IPv6 for winston.parabola.nu In-Reply-To: <87k1cqpkw7.wl-lukeshu@lukeshu.com> References: <87k1cqpkw7.wl-lukeshu@lukeshu.com> Message-ID: <87ims9q1r3.wl-lukeshu@lukeshu.com> On Wed, 10 Jul 2019 00:35:04 -0400, Luke Shumaker wrote: > Hi all, > > I've set up a Hurricane Electric IPv6 tunnel for winton.parabola.nu. > It uses the same HE account as DNS. > > - I've added 3 AAAA records (parabola.nu, winston.parabola.nu, > parabolagnulinux.org). > - I've adjusted postfix to use IPv6 now. > - https://labs.parabola.nu/issues/1286 > > Parabola infrastructure should now be IPv6 accessible. Wait, I screwed up IPv6 rDNS, so some IPv6 mail servers were rejecting our email (including my mav.lukeshu.com). I've fixed the rDNS, and have disabled IPv6 in postfix until the 24 hour DNS ttl expires. Sorry for the inconvenience. -- Happy hacking, ~ Luke Shumaker From bill-auger at peers.community Wed Jul 10 18:14:07 2019 From: bill-auger at peers.community (bill-auger) Date: Wed, 10 Jul 2019 14:14:07 -0400 Subject: [Dev] IPv6 for winston.parabola.nu In-Reply-To: <87k1cqpkw7.wl-lukeshu@lukeshu.com> References: <87k1cqpkw7.wl-lukeshu@lukeshu.com> Message-ID: <20190710141407.28683754@parabola> On Wed, 10 Jul 2019 00:35:04 -0400 Luke wrote: > Parabola infrastructure should now be IPv6 accessible. welcome, all hacked IOT spambots :) From bill-auger at peers.community Thu Jul 11 13:58:14 2019 From: bill-auger at peers.community (bill-auger) Date: Thu, 11 Jul 2019 09:58:14 -0400 Subject: [Dev] IPv6 for winston.parabola.nu In-Reply-To: <87k1cqpkw7.wl-lukeshu@lukeshu.com> References: <87k1cqpkw7.wl-lukeshu@lukeshu.com> Message-ID: <20190711095814.2860a86a@parabola> lukeshu it looks like redmine is already getting hit with mass spam From bill-auger at peers.community Thu Jul 11 14:31:05 2019 From: bill-auger at peers.community (bill-auger) Date: Thu, 11 Jul 2019 10:31:05 -0400 Subject: [Dev] IPv6 for winston.parabola.nu In-Reply-To: <87k1cqpkw7.wl-lukeshu@lukeshu.com> References: <87k1cqpkw7.wl-lukeshu@lukeshu.com> Message-ID: <20190711103105.13621116@parabola> and mediawiki From nobody at parabola.nu Thu Jul 11 22:31:41 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 12 Jul 2019 01:31:41 +0300 Subject: [Dev] Website issues Message-ID: There are some issues with website. Please, check. From leo at leonunner.com Tue Jul 16 17:54:58 2019 From: leo at leonunner.com (Leo Nunner) Date: Tue, 16 Jul 2019 19:54:58 +0200 Subject: [Dev] Updates for flagged packages Message-ID: <2482698ee55811835a25d81d27c84af24728a90d.camel@leonunner.com> Greetings, I have updated the packages "command-not-found" and "ipmiutil", which were flagged as "out of date" to their newest versions. Changelog: command-not-found: Changed version from 0.6.1 to 0.6.2 and updated the sha256sums ipmiutil: Changed the version from 2.9.5 to 3.1.3 and updated the md5sums They both compiled under their given architectures (i686 and x86_64) using librechroot. -------------- next part -------------- # Maintainer (Arch): Bernhard Landauer # Contributor (Arch): Matthias Maennich # Maintainer: Omar Vega Ramos # Contributor: Luke Shumaker pkgname=command-not-found pkgver=0.6.2 pkgrel=2 pkgdesc="In case a command could not be found this utility searches for packages containing this or a similar command (bash,zsh)." arch=('i686' 'x86_64') url="https://github.com/metti/$pkgname" license=('GPL3') depends=('boost-libs' 'libarchive' 'tdb' 'wget') makedepends=('boost' 'cmake' 'git') install=$pkgname.install source=("$url/archive/v$pkgver.tar.gz") sha256sums=('a5946d2180b67ff16f0cd4d248dce3fcee36cbf535b946e50c90c55dc6cf31aa') build() { cd $pkgname-$pkgver cmake \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX="" \ src make } package(){ cd $pkgname-$pkgver make DESTDIR="$pkgdir" install } -------------- next part -------------- # Contributor (Arch): Florian Dejonckheere # Contributor (Arch): goodmen # Contributor (Arch): Gergely Imreh # Contributors: champus, madeye, Ranguvar and ninja_pt # Maintainer : Parabola GNU / Linux-libre Aur?lien DESBRI?RES pkgname=ipmiutil pkgver=3.1.3 pkgrel=1 pkgdesc="A simple program that lists results from the hardware detection library." arch=('i686' 'x86_64') url="http://sourceforge.net/projects/ipmiutil/" license=('BSD3') depends=('openssl') options=('!emptydirs') source=("http://prdownloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.gz") md5sums=('0d448d14726e2fda0eb9451fb2866a5c') build() { cd "${srcdir}/${pkgname}-${pkgver}" ./configure --enable-gpl --libdir=/usr/lib --bindir=/usr/bin make } package() { cd "${srcdir}/${pkgname}-${pkgver}" make DESTDIR="${pkgdir}" install cd "${pkgdir}" pwd mv -v usr/sbin/* usr/bin/ rmdir -v usr/sbin/ install -Dm644 "${srcdir}/${pkgname}-${pkgver}/COPYING" "${pkgdir}/usr/share/licenses/ipmiutil/LICENSE" } -------------- 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 bill-auger at peers.community Tue Jul 16 18:16:11 2019 From: bill-auger at peers.community (bill-auger) Date: Tue, 16 Jul 2019 14:16:11 -0400 Subject: [Dev] Updates for flagged packages In-Reply-To: <2482698ee55811835a25d81d27c84af24728a90d.camel@leonunner.com> References: <2482698ee55811835a25d81d27c84af24728a90d.camel@leonunner.com> Message-ID: <20190716141611.7a68fdf5@parabola> gj Leo - excellent report FWIW, probably the only reason that those packages do not have arm in the arch() array is they were added before parabola had an arm port - whenever i see one with arm missing i try to build it for arm - there are sometimes missing dependencies; but otherwise we should try to add as many packages to the arm port as is possible From leo at leonunner.com Tue Jul 16 19:54:50 2019 From: leo at leonunner.com (Leo Nunner) Date: Tue, 16 Jul 2019 21:54:50 +0200 Subject: [Dev] Updates for flagged packages In-Reply-To: <20190716141611.7a68fdf5@parabola> References: <2482698ee55811835a25d81d27c84af24728a90d.camel@leonunner.com> <20190716141611.7a68fdf5@parabola> Message-ID: <86376946fd1bf40a1fa885df411735e6b0c93825.camel@leonunner.com> On Tue, 2019-07-16 at 14:16 -0400, bill-auger wrote: > gj Leo - excellent report > > FWIW, probably the only reason that those packages do not have > arm in the arch() array is they were added before parabola had > an arm port - whenever i see one with arm missing i try to build > it for arm - there are sometimes missing dependencies; but > otherwise we should try to add as many packages to the arm port > as is possible > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev Both of these packages seem to build just fine for arm - see the updated versions in the attachments -------------- next part -------------- # Contributor (Arch): Florian Dejonckheere # Contributor (Arch): goodmen # Contributor (Arch): Gergely Imreh # Contributors: champus, madeye, Ranguvar and ninja_pt # Maintainer : Parabola GNU / Linux-libre Aur?lien DESBRI?RES pkgname=ipmiutil pkgver=3.1.3 pkgrel=1 pkgdesc="A simple program that lists results from the hardware detection library." arch=('i686' 'x86_64' 'armv7h') url="http://sourceforge.net/projects/ipmiutil/" license=('BSD3') depends=('openssl') options=('!emptydirs') source=("http://prdownloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.gz") md5sums=('0d448d14726e2fda0eb9451fb2866a5c') build() { cd "${srcdir}/${pkgname}-${pkgver}" ./configure --enable-gpl --libdir=/usr/lib --bindir=/usr/bin make } package() { cd "${srcdir}/${pkgname}-${pkgver}" make DESTDIR="${pkgdir}" install cd "${pkgdir}" pwd mv -v usr/sbin/* usr/bin/ rmdir -v usr/sbin/ install -Dm644 "${srcdir}/${pkgname}-${pkgver}/COPYING" "${pkgdir}/usr/share/licenses/ipmiutil/LICENSE" } -------------- next part -------------- # Maintainer (Arch): Bernhard Landauer # Contributor (Arch): Matthias Maennich # Maintainer: Omar Vega Ramos # Contributor: Luke Shumaker pkgname=command-not-found pkgver=0.6.2 pkgrel=2 pkgdesc="In case a command could not be found this utility searches for packages containing this or a similar command (bash,zsh)." arch=('i686' 'x86_64' 'armv7h') url="https://github.com/metti/$pkgname" license=('GPL3') depends=('boost-libs' 'libarchive' 'tdb' 'wget') makedepends=('boost' 'cmake' 'git') install=$pkgname.install source=("$url/archive/v$pkgver.tar.gz") sha256sums=('a5946d2180b67ff16f0cd4d248dce3fcee36cbf535b946e50c90c55dc6cf31aa') build() { cd $pkgname-$pkgver cmake \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX="" \ src make } package(){ cd $pkgname-$pkgver make DESTDIR="$pkgdir" install } -------------- 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 Tue Jul 16 20:06:01 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 16 Jul 2019 20:06:01 -0000 Subject: [Dev] Orphan Libre package [texlive-latexextra] marked out-of-date Message-ID: <20190716200601.22834.69780@winston.parabola.nu> theova at member.fsf.org wants to notify you that the following packages may be out-of-date: * texlive-latexextra 2018.49282-1.par1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/texlive-latexextra/ * texlive-latexextra 2018.49282-1.par1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/texlive-latexextra/ * texlive-latexextra 2018.49282-1.par1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/texlive-latexextra/ The user provided the following additional text: Version 2019.50920-1 is packaged in Arch Linux. This is probably related to issue #2347 (https://labs.parabola.nu/issues/2347). From bill-auger at peers.community Tue Jul 16 22:26:03 2019 From: bill-auger at peers.community (bill-auger) Date: Tue, 16 Jul 2019 18:26:03 -0400 Subject: [Dev] Updates for flagged packages In-Reply-To: <86376946fd1bf40a1fa885df411735e6b0c93825.camel@leonunner.com> References: <2482698ee55811835a25d81d27c84af24728a90d.camel@leonunner.com> <20190716141611.7a68fdf5@parabola> <86376946fd1bf40a1fa885df411735e6b0c93825.camel@leonunner.com> Message-ID: <20190716182603.13590512@parabola> they are all published - thanks for looking them over - do send as many more as you like - it is helpful, even for the easy ones, to know that they will not consume an entire afternoon to upgrade From nobody at parabola.nu Wed Jul 17 17:38:33 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 17 Jul 2019 17:38:33 -0000 Subject: [Dev] Orphan Libre package [kio] marked out-of-date Message-ID: <20190717173833.22832.80067@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * kio 5.59.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kio/ * kio 5.59.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://cgit.kde.org/kio.git From leo at leonunner.com Wed Jul 17 21:23:19 2019 From: leo at leonunner.com (Leo Nunner) Date: Wed, 17 Jul 2019 23:23:19 +0200 Subject: [Dev] Updates for flagged packages Message-ID: Greetings, I have updated the "pdsh" and "qutebrowser" packages to their newest versions. changelog: [pcr] pdsh: Changed version from 2.29 to 2.33 and updated the md5sums. The URL had to be changed from http://pdsh.googlecode.com/files/$pkgname-$pkgver.tar.bz2 to https://github.com/chaos/{$pkgname}/releases/download/{$pkgname}-{$pkgver}/{$pkgname}-${pkgver}.tar.gz . Also, the upstream URL doesn't have the latest version, it seems like the project moved to GitHub. Added armv7h support. Removed the "rmdir "${pkgdir}"/usr/sbin" line from the pkgbuild, as it would not build otherwise, complaining about not being able to find the directory. [libre] qutebrowser: Changed version from 1.6.2 to 1.6.3 and updated the sha256sums. I had to compile asciidoc inside the chroot first, as the signature of the package could not be verified. -------------- next part -------------- # Contributor (Arch): drrossum # Contributor (Arch): sh0 # Maintainer : Aur?lien Desbri?res pkgname=pdsh pkgver=2.33 pkgrel=1 pkgdesc='Parallel Distributed Shell' url='http://code.google.com/p/pdsh/' arch=('i686' 'x86_64' 'armv7h') license=('GPL') depends=('glibc' 'openssh' 'readline') optdepends=('perl: required by the dshbak utility') options=('libtool') source=("https://github.com/chaos/{$pkgname}/releases/download/{$pkgname}-{$pkgver}/{$pkgname}-${pkgver}.tar.gz") md5sums=('b49e7c1c74480c8d34efd04bf3d0fca2') build() { cd "${srcdir}/${pkgname}-${pkgver}" ./configure --prefix=/usr --mandir=/usr/share/man \ --without-rsh \ --with-ssh \ --with-dshgroups \ --with-readline || return 1 make || return 1 } package() { cd "${srcdir}/${pkgname}-${pkgver}" make DESTDIR="${pkgdir}/" install || return 1 } # vim:set ts=2 sw=2 et: -------------- next part -------------- # Maintainer (Arch): Morten Linderud # Contributor (Arch): Pierre Neidhardt # Contributor (Arch): Florian Bruhin (The Compiler) # Maintainer: Omar Vega Ramos # Contributor: Andr? Silva # parabola changes and rationale: # - removed qt5-webengine dependency # - set webkit backend as default pkgname=qutebrowser pkgver=1.6.3 pkgrel=1 pkgrel+=.par1 pkgdesc="A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit" pkgdesc+=", without nonfree qt5-webengine recommendation" arch=("any") url="http://www.qutebrowser.org/" license=("GPL") depends=("python-attrs" "python-jinja" "python-pygments" "python-pypeg2" "python-pyqt5>=5.7" "python-yaml" "qt5-base>=5.7.1" "qt5-webkit") makedepends=("asciidoc" "python-setuptools") optdepends=("gst-libav: media playback" "gst-plugins-base: media playback" "gst-plugins-good: media playback" "gst-plugins-bad: media playback" "gst-plugins-ugly: media playback" "pdfjs: displaying PDF in-browser") options=(!emptydirs) source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz" "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc") validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") sha256sums=('1ed27f8bc7ce3e0d3d1d8687de5280d0be62c899154c773a22196cba49b02a7d' 'SKIP') build() { cd "$pkgname-$pkgver" # make sure webkit is the default backend sed -i 's/webengine/webkit/' qutebrowser/config/configdata.yml a2x -f manpage doc/qutebrowser.1.asciidoc python setup.py build } package() { cd "$pkgname-$pkgver" make -f misc/Makefile DESTDIR="$pkgdir" PREFIX=/usr install } -------------- 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 bill-auger at peers.community Thu Jul 18 00:09:23 2019 From: bill-auger at peers.community (bill-auger) Date: Wed, 17 Jul 2019 20:09:23 -0400 Subject: [Dev] Luke R. expired GPG key Message-ID: <20190717200923.723be8f1@parabola> Luke R. - there are packages in the repo signed with your key that expired a few days ago - could you please update your GPG key and re-build the keyring? 4096 bit RSA key C3F4FFCF3EAE8697, created: 2015-06-22, expires: 2019-07-10 (expired) From theova at bluewin.ch Tue Jul 23 20:00:12 2019 From: theova at bluewin.ch (theova) Date: Tue, 23 Jul 2019 22:00:12 +0200 Subject: [Dev] Updates for flagged packages Message-ID: <20190723200012.xel6thwofwyht4mq@RainbowWarrior.localdomain> Hi, In the meantime, qutebrowser 1.7.0 was released. Changelog (pretty much the same): [libre] qutebrowser: Changed version from 1.6.2 to 1.7.0 and updated the sha256sums. I had to compile asciidoc inside the chroot first, as the signature of the package could not be verified. PKGBUILD: # Maintainer (Arch): Morten Linderud # Contributor (Arch): Pierre Neidhardt # Contributor (Arch): Florian Bruhin (The Compiler) # Maintainer: Omar Vega Ramos # Contributor: Andr? Silva # parabola changes and rationale: # - removed qt5-webengine dependency # - set webkit backend as default pkgname=qutebrowser pkgver=1.7.0 pkgrel=1 pkgrel+=.par1 pkgdesc="A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit" pkgdesc+=", without nonfree qt5-webengine recommendation" arch=("any") url="http://www.qutebrowser.org/" license=("GPL") depends=("python-attrs" "python-jinja" "python-pygments" "python-pypeg2" "python-pyqt5>=5.7" "python-yaml" "qt5-base>=5.7.1" "qt5-webkit") makedepends=("asciidoc" "python-setuptools") optdepends=("gst-libav: media playback" "gst-plugins-base: media playback" "gst-plugins-good: media playback" "gst-plugins-bad: media playback" "gst-plugins-ugly: media playback" "pdfjs: displaying PDF in-browser") options=(!emptydirs) source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz" "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc") validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") sha256sums=('f1f01b33669a9b08071997bb2642d46a1e5be9e293bdeb817d83db8dc5aad273' 'SKIP') build() { cd "$pkgname-$pkgver" # make sure webkit is the default backend sed -i 's/webengine/webkit/' qutebrowser/config/configdata.yml a2x -f manpage doc/qutebrowser.1.asciidoc python setup.py build } package() { cd "$pkgname-$pkgver" make -f misc/Makefile DESTDIR="$pkgdir" PREFIX=/usr install } The new Leo Nunner schrieb am Wed, 17. Jul 19 23:23: > Greetings, > > I have updated the "pdsh" and "qutebrowser" packages to their newest > versions. > > changelog: > > [pcr] pdsh: Changed version from 2.29 to 2.33 and updated the md5sums. > The URL had to be changed from > http://pdsh.googlecode.com/files/$pkgname-$pkgver.tar.bz2 to > https://github.com/chaos/{$pkgname}/releases/download/{$pkgname}-{$pkgver}/{$pkgname}-${pkgver}.tar.gz > . Also, the upstream URL doesn't have the latest version, it seems like > the project moved to GitHub. Added armv7h support. Removed the "rmdir > "${pkgdir}"/usr/sbin" line from the pkgbuild, as it would not build > otherwise, complaining about not being able to find the directory. > > [libre] qutebrowser: Changed version from 1.6.2 to 1.6.3 and updated > the sha256sums. I had to compile asciidoc inside the chroot first, as > the signature of the package could not be verified. > # Contributor (Arch): drrossum > # Contributor (Arch): sh0 > # Maintainer : Aur?lien Desbri?res > > pkgname=pdsh > pkgver=2.33 > pkgrel=1 > pkgdesc='Parallel Distributed Shell' > url='http://code.google.com/p/pdsh/' > arch=('i686' 'x86_64' 'armv7h') > license=('GPL') > depends=('glibc' 'openssh' 'readline') > optdepends=('perl: required by the dshbak utility') > options=('libtool') > source=("https://github.com/chaos/{$pkgname}/releases/download/{$pkgname}-{$pkgver}/{$pkgname}-${pkgver}.tar.gz") > md5sums=('b49e7c1c74480c8d34efd04bf3d0fca2') > > build() { > cd "${srcdir}/${pkgname}-${pkgver}" > ./configure --prefix=/usr --mandir=/usr/share/man \ > --without-rsh \ > --with-ssh \ > --with-dshgroups \ > --with-readline || return 1 > make || return 1 > } > > package() { > cd "${srcdir}/${pkgname}-${pkgver}" > make DESTDIR="${pkgdir}/" install || return 1 > } > > # vim:set ts=2 sw=2 et: > # Maintainer (Arch): Morten Linderud > # Contributor (Arch): Pierre Neidhardt > # Contributor (Arch): Florian Bruhin (The Compiler) > # Maintainer: Omar Vega Ramos > # Contributor: Andr? Silva > > # parabola changes and rationale: > # - removed qt5-webengine dependency > # - set webkit backend as default > > pkgname=qutebrowser > pkgver=1.6.3 > pkgrel=1 > pkgrel+=.par1 > pkgdesc="A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit" > pkgdesc+=", without nonfree qt5-webengine recommendation" > arch=("any") > url="http://www.qutebrowser.org/" > license=("GPL") > depends=("python-attrs" "python-jinja" "python-pygments" "python-pypeg2" > "python-pyqt5>=5.7" "python-yaml" "qt5-base>=5.7.1" "qt5-webkit") > makedepends=("asciidoc" "python-setuptools") > optdepends=("gst-libav: media playback" > "gst-plugins-base: media playback" > "gst-plugins-good: media playback" > "gst-plugins-bad: media playback" > "gst-plugins-ugly: media playback" > "pdfjs: displaying PDF in-browser") > options=(!emptydirs) > source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz" > "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc") > validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") > sha256sums=('1ed27f8bc7ce3e0d3d1d8687de5280d0be62c899154c773a22196cba49b02a7d' > 'SKIP') > > build() { > cd "$pkgname-$pkgver" > > # make sure webkit is the default backend > sed -i 's/webengine/webkit/' qutebrowser/config/configdata.yml > > a2x -f manpage doc/qutebrowser.1.asciidoc > python setup.py build > } > > package() { > cd "$pkgname-$pkgver" > make -f misc/Makefile DESTDIR="$pkgdir" PREFIX=/usr install > } > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev ----- End forwarded message ----- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From bill-auger at peers.community Wed Jul 24 00:25:29 2019 From: bill-auger at peers.community (bill-auger) Date: Tue, 23 Jul 2019 20:25:29 -0400 Subject: [Dev] Updates for flagged packages In-Reply-To: <20190723200012.xel6thwofwyht4mq@RainbowWarrior.localdomain> References: <20190723200012.xel6thwofwyht4mq@RainbowWarrior.localdomain> Message-ID: <20190723202529.283b2bd9@parabola> 'pdsh' has been upgraded to v2.33 'qutebrowser' has been upgraded to v1.7.0 From theova at bluewin.ch Fri Jul 26 20:52:28 2019 From: theova at bluewin.ch (theova) Date: Fri, 26 Jul 2019 22:52:28 +0200 Subject: [Dev] Orphan Libre package [texlive-latexextra] marked out-of-date In-Reply-To: <20190716200601.22834.69780@winston.parabola.nu> References: <20190716200601.22834.69780@winston.parabola.nu> Message-ID: <20190726205228.i4bho35rtlnwqgju@RainbowWarrior.localdomain> Here is an updated version of the PKGBUILD. Changelog: - Split mksource() to prepare() and build() to have a more standard PKGBUID closer to Arch's one. Remove the corresponding variables. - Add command to remove 'clock' from CONTENTS (line 43). It seems to me, that it was forgotten. PKGBUILD: # Maintainer (Arch): Firmicus # Maintainer (Arch): R?my Oudompheng # Contributor (Hyperbola): Andr? Silva # Maintainer: Micha? Mas?owski # Contributor: Isaac David pkgname=texlive-latexextra pkgver=2019.50920 _revnr=${pkgver#2019.} pkgrel=1 pkgrel+=.par1 pkgdesc="TeX Live - Large collection of add-on packages for LaTeX" pkgdesc+=", without nonfree add-on packages" license=('GPL') arch=(any) depends=('texlive-core' 'perl-file-which' # for pdfannotextractor ) optdepends=( 'python2-pygments: for pygmentex' 'texlive-genericextra: to use the calctab package' 'texlive-pictures: to use the package overpic' 'java-environment: to use pdfannotextractor' ) groups=('texlive-most') replaces=('texlive-latexextra-libre') conflicts=('texlive-latexextra-libre') url='http://tug.org/texlive/' options=('!emptydirs') source=("https://sources.archlinux.org/other/texlive/$pkgname-$pkgver-src.zip" "$pkgname.maps") sha256sums=('362fe75eafe2cdc8e6fd3bd7eb3b40420966ad87a264f2c553de93a41d7d455b' 'd53750a03a52472a1c7c5ba5142959ba382a5d69215471691c0b12c3663950ce') prepare() { # remove nonfree packages # no specific free license rm -v {authoraftertitle,clock,fnpara}.tar.xz # nonfree license (CC BY-NC) rm -v axessibility.tar.xz # remove nonfree packages references from package list sed -ri '/^(axessibility|authoraftertitle|clock|fnpara) /d' CONTENTS } build() { echo " --> extracting all packages... " for p in *.tar.xz; do bsdtar -xf $p done rm -rf {tlpkg,doc,source} || true } package() { install -m755 -d "$pkgdir"/var/lib/texmf/arch/installedpkgs sed -i '/^#/d' CONTENTS install -m644 CONTENTS "$pkgdir"/var/lib/texmf/arch/installedpkgs/${pkgname}_${_revnr}.pkgs install -m644 $srcdir/$pkgname.maps "$pkgdir"/var/lib/texmf/arch/installedpkgs/ install -m755 -d "$pkgdir"/usr/share wanteddirs=$(for d in *; do test -d $d && [[ $d != texmf* ]] && echo $d; done) || true for dir in $wanteddirs; do find $dir -type d -exec install -d -m755 "$pkgdir"/usr/share/texmf-dist/'{}' \; find $dir -type f -exec install -m644 '{}' "$pkgdir"/usr/share/texmf-dist/'{}' \; done if [[ -d texmf-dist ]]; then find texmf-dist -type d -exec install -d -m755 "$pkgdir"/usr/share/'{}' \; find texmf-dist -type f -exec install -m644 '{}' "$pkgdir"/usr/share/'{}' \; fi if [[ -d "$pkgdir"/usr/share/texmf-dist/scripts ]]; then find "$pkgdir"/usr/share/texmf-dist/scripts -type f -exec chmod a+x '{}' \; fi #add symlinks that were in texlive-bin: _linked_scripts=" authorindex/authorindex exceltex/exceltex glossaries/makeglossaries glossaries/makeglossaries-lite.lua l3build/l3build.lua makedtx/makedtx.pl pax/pdfannotextractor.pl perltex/perltex.pl pygmentex/pygmentex.py splitindex/splitindex.pl svn-multi/svn-multi.pl vpe/vpe.pl wordcount/wordcount.sh yplan/yplan " install -m755 -d "$pkgdir"/usr/bin for _script in ${_linked_scripts}; do _scriptbase=$(basename $_script) _scriptbase=${_scriptbase%.*} ln -s /usr/share/texmf-dist/scripts/${_script} ${pkgdir}/usr/bin/${_scriptbase} done rm "$pkgdir"/usr/share/texmf-dist/scripts/shipunov/biokey2html.bat } Parabola Website Notification schrieb am Tue, 16. Jul 19 20:06: >theova at member.fsf.org wants to notify you that the following packages may be out-of-date: > > >* texlive-latexextra 2018.49282-1.par1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/texlive-latexextra/ >* texlive-latexextra 2018.49282-1.par1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/texlive-latexextra/ >* texlive-latexextra 2018.49282-1.par1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/texlive-latexextra/ > > >The user provided the following additional text: > >Version 2019.50920-1 is packaged in Arch Linux. > >This is probably related to issue #2347 (https://labs.parabola.nu/issues/2347). > >_______________________________________________ >Dev mailing list >Dev at lists.parabola.nu >https://lists.parabola.nu/mailman/listinfo/dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From nobody at parabola.nu Sat Jul 27 01:47:12 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 27 Jul 2019 01:47:12 -0000 Subject: [Dev] Orphan Pcr package [xfce-theme-greybird] marked out-of-date Message-ID: <20190727014712.22831.8918@winston.parabola.nu> eliotreyna at cock.li wants to notify you that the following packages may be out-of-date: * xfce-theme-greybird 3.22.3-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/xfce-theme-greybird/ * xfce-theme-greybird 3.22.3-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/xfce-theme-greybird/ * xfce-theme-greybird 3.22.3-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/xfce-theme-greybird/ The user provided the following additional text: Greybird has a new version (3.22.10). It's avariable on: 1.- AUR: https://aur.archlinux.org/packages/xfce-theme-greybird/ 2.- GitHub repo: https://github.com/shimmerproject/Greybird Also, the detailed info about this version is variable here: https://github.com/shimmerproject/Greybird/releases Thanks. From nobody at parabola.nu Sat Jul 27 13:37:14 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 27 Jul 2019 13:37:14 -0000 Subject: [Dev] Orphan Libre package [linux-libre-lts] marked out-of-date Message-ID: <20190727133714.22833.3115@winston.parabola.nu> riku.viitanen0 at gmail.com wants to notify you that the following packages may be out-of-date: * linux-libre-lts 4.19.60_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts/ * linux-libre-lts 4.19.60_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts/ * linux-libre-lts 4.19.60_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts/ * linux-libre-lts-docs 4.19.60_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-docs/ * linux-libre-lts-docs 4.19.60_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts-docs/ * linux-libre-lts-docs 4.19.60_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-docs/ * linux-libre-lts-headers 4.19.60_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-lts-headers/ * linux-libre-lts-headers 4.19.60_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-lts-headers/ * linux-libre-lts-headers 4.19.60_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-lts-headers/ The user provided the following additional text: 4.19.61 is available. From nobody at parabola.nu Sat Jul 27 13:37:40 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 27 Jul 2019 13:37:40 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20190727133740.22833.12942@winston.parabola.nu> riku.viitanen0 at gmail.com wants to notify you that the following packages may be out-of-date: * linux-libre 5.2.2_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 5.2.2_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ * linux-libre 5.2.2_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-chromebook 5.2.2_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-chromebook/ * linux-libre-docs 5.2.2_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 5.2.2_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ * linux-libre-docs 5.2.2_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 5.2.2_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 5.2.2_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ * linux-libre-headers 5.2.2_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: 5.2.3 is available. From freemor at freemor.ca Wed Jul 31 01:28:16 2019 From: freemor at freemor.ca (Freemor) Date: Tue, 30 Jul 2019 22:28:16 -0300 Subject: [Dev] your-system-sanity Message-ID: <20190731012815.GB18936@freemor.ca> Ok, preliminary work on your-system-santiy went well. And got a surprising amount of interest from users considering that it was just in testing. I'm writing to the dev list to get input and kick the ball around on your-system-sanity before continuing. Things that I'd like to have solidly defined before proceeding are: scope - What do we want your-system-sanity to cover. My goal was to have it cover Third Party Package Managers (TPPMs) that are dangerous to the health of the users system python-pip is a leading example of this. The way it currently is, it install over system files often creating a real mess (I'll address actually fixing the TPPMs behaviours later). Which TPPMs fall into this category is up for discussion (Rust/cargo, Ruby/gems, perl/cpan, etc/etc). Do we warn about all TPPMs or do we only concern ourselves with the ones that Bork the system by default. Do we worry about TPPMs that offer non-free or should those be handled by the regular blacklist.txt Several users were wanting games with the built in ability to download non-free culture assets. I feel this is beyond that scope of your-system-sanity as it's purpose is system stability. What work needs to be done outside of the package itself. As I added gems to the initial list in your-system-sanity I had to rebuild ruby so the depend on gems was optional. I haven't looked at the Rust build yet as it is an Arch package but I do not see a separate cargo package. That would need to be addressed. Probably others. As I imagines this being part of base/base-openrc there is some concern that it could break builds in abslibre as it may effect their depends or the ability to build things if they require things like cargo,gems,maven,etc. This may actually be a desirable outcome as things shouldn't be using things like maven to pull in other source files during the build stage. bill-auger correctly pointed out that the best thing to ultimately do is get the TPPMs fixed upstream so the install into /usr/local/ or the users home dir. This may be an uphill battle as there is a strong pull everything from everywhere culture out there and so there may not be much interest in making it right. I did some digging and there is a BUG for PIP re: defaulting to /usr/local/ that has been going on for years, closed, re-opened, and on and on with no real concrete outcome I could see. Though it did seem that they added some ./configure options or the like to change how it behaves (I'll have to find it again. Will post it here when I do). As for the games/non-free assets downloading situation I personally feel that that is something better addressed with the existing blacklist (recommends-nonfree) or the like. So Let the input fly.. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From grizzlyuser at protonmail.com Wed Jul 31 13:55:56 2019 From: grizzlyuser at protonmail.com (grizzlyuser) Date: Wed, 31 Jul 2019 13:55:56 +0000 Subject: [Dev] your-system-sanity In-Reply-To: <20190731012815.GB18936@freemor.ca> References: <20190731012815.GB18936@freemor.ca> Message-ID: In my understanding, downstream distributions should always work with upstream first. If issues cannot be resolved upstream - make one step down the stream and work on that layer. Then the process repeats if there are multiple intermediate downstream layers and if necessary. If there's something critical though, downstream can decide to deploy a temporary solution themselves until the issue is resolved upstream. This can be anything from documentation of the workaround to actual patches or customizations. On Wednesday, July 31, 2019 4:28 AM, Freemor wrote: > Though it did seem that they added some ./configure options or the like to > change how it behaves (I'll have to find it again. Will post it here when I > do). Following the above principle, if the issue has already been reported upstream, then has it already been reported to Arch Linux bug tracker? If there are configuration options available, then what about shipping the package with the configuration or patch that allows it to work well with the rest of the system? Parabola / Arch is a distro, and of course they can do that stuff to maintain system stability. AFAIK, downloading of non-free assets has been already discussed, and one of the ideas was that allowing to download non-free is not equal to recommending non-free. What I understood was, for example, if some package has hard-coded download links to non-free things, then it's an issue. And it's not, if it has a link to a repository where both free and non-free things are distributed and it's up to the user to decide what to download. The issue of package managers being able to install non-free, looks complex. Ideally it'd be solved if each of them (including pacman) fully supports all of the following: 1. license filtering, so users can configure the PM to filter packages and all of their dependencies based on their licenses or license groups; 2. reproducible builds. In this case it looks like it wouldn't matter from which repository the package is downloaded, being it 1st- or 3rd-party. But that's in ideal world, of course. About the name of the package: there are lots of insane stuff in the software world... What about changing the name to something more specific? From labs at parabola.nu Thu Jul 11 10:45:12 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Thu, 11 Jul 2019 10:45:12 -0000 Subject: [Dev] [Servers - Bug #2354] recent arch packages not in parabola repos References: Message-ID: Issue #2354 has been updated by bill-auger. Description updated ---------------------------------------- Bug #2354: recent arch packages not in parabola repos https://labs.parabola.nu/issues/2354#change-12435 * Author: bill-auger * Status: confirmed * Priority: broken * Assignee: * Category: ---------------------------------------- _TLDR: if you have this problem today, open /etc/pacman.d/mirrorlist and copy one of the commented-out parabola mirrors to the top of the mirrorlist - then pacman -Syu _ the 'guile' package from arch was upgraded yesterday but the parabola repos still have the previous version, and the redirector can not find any arch mirror with that package - it is a dependency of 'make', so a rather important package https://www.archlinux.org/packages/extra/x86_64/guile/ today someone reported several haskel packages with the same situation perhaps related: i removed the 'gnutls-guile' package from the repos yesterday but the parabola mirrors still have it anyone using the redirector with these packages installed will not be able to upgrade 
error: failed retrieving file 
 from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files

where the currently known 
's are:
'guile-2.2.5-1-x86_64.pkg.tar.xz'
'haskell-microlens-0.4.11.2-1-x86_64.pkg.tar.xz' 
'haskell-typed-process-0.2.5.0-2-x86_64.pkg.tar.xz'
'haskell-rio-0.1.9.2-19-x86_64.pkg.tar.xz'
-- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Thu Jul 11 12:34:48 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Thu, 11 Jul 2019 12:34:48 -0000 Subject: [Dev] [Servers - Bug #2354] (fixed) recent arch packages not in parabola repos References: Message-ID: Issue #2354 has been updated by bill-auger. Status changed from confirmed to fixed ---------------------------------------- Bug #2354: recent arch packages not in parabola repos https://labs.parabola.nu/issues/2354#change-12439 * Author: bill-auger * Status: fixed * Priority: broken * Assignee: bill-auger * Category: ---------------------------------------- _TLDR: if you have this problem today, open /etc/pacman.d/mirrorlist and copy one of the commented-out parabola mirrors to the top of the mirrorlist - then pacman -Syu _ the 'guile' package from arch was upgraded yesterday but the parabola repos still have the previous version, and the redirector can not find any arch mirror with that package - it is a dependency of 'make', so a rather important package https://www.archlinux.org/packages/extra/x86_64/guile/ today someone reported several haskel packages with the same situation perhaps related: i removed the 'gnutls-guile' package from the repos yesterday but the parabola mirrors still have it anyone using the redirector with these packages installed will not be able to upgrade 
error: failed retrieving file 
 from redirector.parabola.nu : The requested URL returned error: 404
warning: failed to retrieve some files

where the currently known 
's are:
'cabal-install-2.4.0.0-108-x86_64.pkg.tar.xz'
'guile-2.2.5-1-x86_64.pkg.tar.xz'
'haskell-http-4000.3.14-4-x86_64.pkg.tar.xz'
'haskell-conduit-extra-1.3.2-4-x86_64.pkg.tar.xz'
'haskell-cryptohash-conduit-0.1.1-283-x86_64.pkg.tar.xz'
'haskell-cryptonite-conduit-0.2.2-177-x86_64.pkg.tar.xz'
'haskell-http-conduit-2.3.7.1-34-x86_64.pkg.tar.xz'
'haskell-microlens-0.4.11.2-1-x86_64.pkg.tar.xz' 
'haskell-monad-logger-0.3.30-63-x86_64.pkg.tar.xz'
'haskell-persistent-2.9.2-35-x86_64.pkg.tar.xz'
'haskell-persistent-sqlite-2.9.3-36-x86_64.pkg.tar.xz'
'haskell-persistent-template-2.6.0-52-x86_64.pkg.tar.xz'
'haskell-project-template-0.2.0.1-149-x86_64.pkg.tar.xz'
'haskell-rio-0.1.9.2-19-x86_64.pkg.tar.xz'
'haskell-typed-process-0.2.5.0-2-x86_64.pkg.tar.xz'
'pandoc-2.7.3-6-x86_64.pkg.tar.xz'
'stack-1.9.3.1-76-x86_64.pkg.tar.xz'
-- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Fri Jul 26 22:11:18 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Fri, 26 Jul 2019 22:11:18 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by bill-auger. Description updated ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12638 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Fri Jul 26 22:11:21 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Fri, 26 Jul 2019 22:11:21 +0000 Subject: [Dev] [libretools - Feature Request #2403] (info needed) [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been reported by bill-auger. ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Fri Jul 26 22:36:48 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Fri, 26 Jul 2019 22:36:48 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by bill-auger. Description updated ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12642 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person probably the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ignore it and ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow, even if that is simply moving the PKGBUILD to a private git branch this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list about this grey area * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Fri Jul 26 22:56:15 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Fri, 26 Jul 2019 22:56:15 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by freemor. I agree this should be automatic instead of the semi clunky mksource() approach The way I see it the issue is with Parabola trying to provide a source tarball as that forces us to make a libre one as we can not provide the non-libre one. The need to provide a libre tarball is unclear, if not false on its face as building "version next" of something will always require pulling the non-free source. It might be better to forget about source tarballs. PKGBUILDS pull the source they need. The PKGBUILDS in abslibre will always clean that source making it libre, As bill-auger pointed out above PKGBUILDS in abslibre in no way induce people to install non-free. The do the opposite and provide the path to freedom. Providing the "How" (as in how to clean that source) is always more instructive then just giving someone pre-cleaned source. Must people that will be playing at the show me the source/pkgbuild level will probably like myself see the libre package as an unnecessary hustle that I never really have to deal with as all the work in liberating the source would just move from prepare to mksource() but every version I'd end up pulling the non-free, figuring out what needs fixing, and adjusting mksource. rolling a tarball that no one will ever use, then building from the libre tarball instead of just doing in all in prepare() and forgetting about creating a next to unused libre source ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12643 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person probably the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ignore it and ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow, even if that is simply moving the PKGBUILD to a private git branch this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list about this grey area * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Fri Jul 26 23:12:48 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Fri, 26 Jul 2019 23:12:48 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by bill-auger. Description updated ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12644 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person probably the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ignore it and ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow, even if that is simply moving the PKGBUILD to a private git branch this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list about this grey area * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Wed Jul 31 17:15:33 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Wed, 31 Jul 2019 17:15:33 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by bill-auger. are you suggesting not to host any sources, or to continue hosting the pristine upstream sources warts and all? - that is the most important concern, regardless of what the tools do probably the original intention was that users should never need to download known non-free software; and to avoid publishing any tools that automatically do so - on the one hand, that would be even worse than what TPPMs do in terms of suggesting and leading users toward non-free software - on the other hand, i think we agree that this particular use-case is not "for practical use" ; so it may not be a strict FSDG requirement - if the source-balls are not clean though, as must be the case if they are created before prepare() runs, then PKGBUILD with the mksource() function are the only ones that produce pre-cleaned sources - everything in [libre] should have had that same treatment; and perhaps that was the goal - if nothing else in [libre] gets that treatment, then those few are just a drop in the bucket; and moving the mksource() procedure into prepare() for those few package which have it, would be barely significant to the big picture - that would be the easiest way to resolve the present issue; but its not a very satisfying solution if the suggestion was not to host any sources, the biggest concern i have with that is the obvious one - im not sure if the FSDG requires that; but it does require that we ensure all source code to available for the current release; and the only way to ensure that is to self-host it - that would make source code storage to be essential infrastructure; and it is always unwise to rely on third-parties to maintain your essential infrastructure , especially with no contract - regardless of the FSDG, the GPL alone extends that requrement to three years beyond the current release, for GPL programs - the only third-party code host that i would be comfortale using for that purpose would be the software heritage repos - i think they are a legitimate charity, so they do have some obligation to the public - that can not be said of most individual projects or any commercial freebie hosts; but it would be a lot of work to change every PKGBUILD to fetch from that host - also, i dont think they prioritize tracking the bleeding edge of changes; so that cuod be a no-starter for parabola aside from ensuring that sources are somehow available, there is the FSDG "self-hosting" requirement; according to which, one should be able to compile vN+1 of the distro using only vN of the distro and tools that are provided by the distro - i dont think that ubuquitous networking should be taken for granted as an excuse to avoid supplying everything required to build the distro - software curation is the one defining factor of what a distro is and what distro devs do - ideally, i would like to take that a step further and publish a sources ISO for offline/clean-room use - currently, a user would need to do an unreasonable amount of prep work, if they wanted to accomplish that; but we already have most of the tooling to make that a possibility im pretty sure that is why parabola mirrors everything from arch, rather than having users rely solely on the arch repos - some users are very concerned about to which servers they expose their IP - i would like to take that concern a step further and modify the redirector to always use a parabola mirror - if winston had a gigbit pipe with unlimited traffic, we could remove the redirector entirely - the redirector is a necessary compromise due to circumstances, in a similar way as relying on the upstreams to feed the user facing PKGBUILDs; but we do have the resources to avoid the latter because of the lesser damand for source-ball i think that complete self-reliance was a goal of the project that is still incomplete; so if we need to modify libretools, i would rather continue in that direction rather than removing relevent functionality - i like the idea of downloading from the upstream and running prepare() in memory, then creating the source-ball after prepare() has done its work; resulting in a cleaned tarball on the local filesystem - librestage and librerelease already are expecting that libremakepkg has created one - the only real problem with the current workflow is that the source-balls are not clean and the VCS ones are overweight - the latter can be solved simply by rm -rf the VCS data dir (.svn/, .git/, .hg/) an alternative idea, which i like better, would be to put those pre-cleaned source-balls into use by modifying makepkg to recognize, according to $pkgname-$pkgver, that a pre-cleaned source-ball exists on the parabola server and to pull that instead of the upstream sources, bypassing the prepare() function - if no pre-cleaned source-ball exists for that version, then that is unsupported software, just like AUR, and falling back on the upstream sources is the reasonable thing to do - as with the AUR, we could suggest against doing so "for practical use"; but endorese it only for the use-case of helping parabola devs liberate it "for practical use" by others ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12676 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person probably the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ignore it and ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow, even if that is simply moving the PKGBUILD to a private git branch this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list about this grey area * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From labs at parabola.nu Wed Jul 31 18:16:27 2019 From: labs at parabola.nu (labs at parabola.nu) Date: Wed, 31 Jul 2019 18:16:27 +0000 Subject: [Dev] [libretools - Feature Request #2403] [libremakepkg]: eradicate mksource() from abslibre References: Message-ID: Issue #2403 has been updated by eschwartz. The concept of "libre" tarballs is essentially the same concept as Debian's "orig" tarballs, where an upstream source release artifact is taken, but the distro decides it isn't "good enough" and determines to apply certain changes. In debian's case, that sometimes includes deleting lots of files that maybe aren't used by the package, for example if software contains a vendored copy of a library, with a configure switch to either use the vendored copy or a system copy... Debian might delete that. Debian might delete minified js from the source tarball. Debian might rename the directory it is stored in, Debian might just recompress the tarball so its checksums don't match but it takes less space on their mirror network. https://www.debian.org/doc/manuals/developers-reference/ch06.html#repackagedorigtargz The question is why this is necessary. Debian certainly seems to think it is so, but then, Debian hosts the sources for every package, no matter what. They also seem to be going to some lengths merely for the sake of prettiness. Does the DFSG truly require you to not make noncompliant source code available at all? If all you are doing is providing a persistent mirror of the upstream tarball, but the canonical "help" that Parabola offers, guiding people towards the act of building and installing the software, is the PKGBUILD, then the PKGBUILD -- regardless of the state of the sources themselves -- does not encourage using non-DFSG software. The PKGBUILD will, when left to its own devices, always build a DFSG-compliant binary product, and extracting the build information but removing the DFSG bits is not a supported or recommended route. >From my outside perspective, it would seem like Parabola should have the option to just upload mirrors of the tarball, but have the PKGBUILD perform all DFSG compliance modifications in prepare() -- with suitable comments saying "# these changes, in accordance with the DFSG, protect the user by removing nonfree software". The alternative is to make it difficult to use the PKGBUILD at all, causing users who want to use the PKGBUILD as a base for updating the version to give up and download something from Github or another upstream website and run ./configure; make; sudo make install without the benefit of a PKGBUILD or DFSG modifications. ---------------------------------------- Feature Request #2403: [libremakepkg]: eradicate mksource() from abslibre https://labs.parabola.nu/issues/2403#change-12683 * Author: bill-auger * Status: info needed * Priority: discussion * Assignee: * Category: ---------------------------------------- related to forum thread https://labs.parabola.nu/boards/18/topics/125 IIRC when discussing the 'ruby' package, we concluded that it was probably intended per the FSDG, to provide complete and pre-cleaned source-balls to the distro users; which entails the devs to keep some of the libre-fications tools private the FSDG does not require support for versions of 'foo' that were not included in any distro release however; but OTOH, this PKGBUILD contains instructions for downloading known non-free software on the third hand (the philosophical hand), the 'gist' of the four freedoms is not about possessing or sharing non-free software; but that the user is able to do with it as they see fit - if the only thing that one wishes to do with that software is to merely posses it or share it, then anything redistributable would satisfy the 'gist' of the four freedoms for that person probably the simplest way to resolve this class of issue, is to add a note to the PKGBULID with sed above every instance of 'mksource()', asking the reader to ignore it and ask a parabola dev to publish the intermediate source-ball, if they are building ahead of the current release; then to publish the missing source-ball for any enthusiastic user who asks for one - a better solution to this class of issue, would be for the PKGBUILD to explaining how to run mksource() and have the mksource() function create the source-ball with expected libre name in the sources() array - if that does not conflict with the FSDG - an even better solution to this class of issue, is to eliminate it by eradicating mksource() from abslibre somehow, even if that is simply moving the PKGBUILD to a private git branch this incident is not a peculiar though - it is currently systematic AFAIK; so i consulted the FSDG: "A free system distribution must not steer users towards obtaining any nonfree information for practical use, or encourage them to do so. The system should have no repositories for nonfree software and no specific recipes for installation of particular nonfree programs." there is another clause that might suggest that this use case is within the guidelines; although it is in the "Documentation" section "In general, something that helps people who already use nonfree software to use the free software better with it is acceptable, but something that encourages users of the free software to install nonfree software is not." libre-fications would seem to fit into that documentation exception - id say the key point is that such scripts do not install the program "for practical use" - the use-case in which the user is interested, is to download a non-free tarball, and to liberate it, without viewing or executing any of the files within it; for the sole purpose of using the cleaned sources in freedom - it would seems better to instruct people how to liberate non-free software rather than impeding their curiosity or ambition; though it may snag upon some FSDG caveat some options: * should consult the FSDG mailing list about this grey area * put these on the wiki as documentation, instead of in PKGBUILDs * libretools could be made to download the file into memory instead of writing a hard copy * hide all such scripts at the cost of impeding enthusiastic users who want to help -- -- ^^ Type your reply above this line ^^ -- -- Please keep the 'Subject' as it is -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://labs.parabola.nu/my/account From contact at sellegri.fr Mon Jul 29 09:09:55 2019 From: contact at sellegri.fr (sellegri) Date: Mon, 29 Jul 2019 11:09:55 +0200 Subject: [Dev] download signature? Message-ID: <20190729090955.GA22651@pc-fix.localdomain> Hi, Sorry for my language. I'm french. I'm new. My forum's account need yet approuvement... I'm happy to known that a honest distribution exist. I would like use it now, and maybe contribute to improve it. For moment I have a problem with the signature of the 64-systemd download. pacman-key and gnupg indicate that the signature is not correct... I have tried migration on my notebook and it not has work. Egal result with "normal" installation which indicate bad keys at the mirror-download step. What could I do? I 'm impatient to try your distribution and for sure show it to my friends. I have time, and I can contribute in artwork ; a part of my creations could be view on https://www.photogeny.com Thanks for your help on signature's problem. See you soon, Sellegri J?r?me.