From bill-auger at peers.community Sat Feb 1 14:13:00 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Feb 2020 09:13:00 -0500 Subject: [Dev] [PATCH] Update [libre/nextcloud-client] to v2.6.2 In-Reply-To: <20200102113251.5rlwtzotl6dukhau@RainbowWarrior.localdomain> References: <20200102113251.5rlwtzotl6dukhau@RainbowWarrior.localdomain> Message-ID: <20200201091300.3d101565@parabola> denis - i just started toward getting this package out; and i noticed theova's patch is already applied in abslibre - but it looks like the packages never got published id like to suggest that it would be better to avoid publishing PKGBUILDs for packages that are not actually in the repos - they are likely to become forgotten otherwise i always wait until after the package is in the repos for at least one arch, before pushing changes to abslibre; except in rare cases when someone else wants to take over mid-way, wrestling with one of the more pesky packages - in those cases, i mark the commit with 'WIP' to indicate that it is not a published package, and may not build From bill-auger at peers.community Sat Feb 1 14:45:26 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Feb 2020 09:45:26 -0500 Subject: [Dev] [PATCH] Update [libre/nextcloud-client] to v2.6.2 In-Reply-To: <20200201091300.3d101565@parabola> References: <20200102113251.5rlwtzotl6dukhau@RainbowWarrior.localdomain> <20200201091300.3d101565@parabola> Message-ID: <20200201094526.5e697c07@parabola> oh another thing i just remembered is that we had the idea to make an abslibre 'wip' branch for PKGBIULDs that are not yet built - that still may not prevent any from being forgotten; but it would allow the master branch to accurately reflect what is in the repos From grizzlyuser at protonmail.com Sun Feb 2 11:19:32 2020 From: grizzlyuser at protonmail.com (grizzlyuser) Date: Sun, 02 Feb 2020 11:19:32 +0000 Subject: [Dev] [PATCH] Iceweasel update to 72.0.2-1 for all architectures In-Reply-To: <_sRrdMLQ1R7pU2as8dMKoABlQY36UFXrt_KwOT1l5IJdQ3IgwPOGgThSYRd6YkB5zl5BM-5cZZlR0604XkRw5hqE1A92EAwtHNzWOyFSx10=@protonmail.com> References: <_sRrdMLQ1R7pU2as8dMKoABlQY36UFXrt_KwOT1l5IJdQ3IgwPOGgThSYRd6YkB5zl5BM-5cZZlR0604XkRw5hqE1A92EAwtHNzWOyFSx10=@protonmail.com> Message-ID: <6DrWdGwEgQsytolI-pqvAozYS9u1TRm4ZnhgluFoNSiGoM70ffXo3bL7oK6nixl04eq9AN6tCFJQrFAhDn7liZBOJXLyKz-vG4X3WaAbWeg=@protonmail.com> Please excuse me for not mentioning this initially, but the following make option for ARM has been copied from Arch ARM sources: mk_add_options MOZ_MAKE_FLAGS="-j2" I'm not sure why do they need it in the first place, probably for stable building on their machines or actual ARM hardware. If that's not necessary in Parabola, then please just omit this option, because obviously it makes build slower than optimal if there are more than 2 CPU cores. On another note, what's the preferred way of sending patches in this ML - inline (plain text) or as attachments? Are there any other rules? I couldn't find any. Thanks From bill-auger at peers.community Sun Feb 2 18:16:33 2020 From: bill-auger at peers.community (bill-auger) Date: Sun, 2 Feb 2020 13:16:33 -0500 Subject: [Dev] [PATCH] Iceweasel update to 72.0.2-1 for all architectures In-Reply-To: <6DrWdGwEgQsytolI-pqvAozYS9u1TRm4ZnhgluFoNSiGoM70ffXo3bL7oK6nixl04eq9AN6tCFJQrFAhDn7liZBOJXLyKz-vG4X3WaAbWeg=@protonmail.com> References: <_sRrdMLQ1R7pU2as8dMKoABlQY36UFXrt_KwOT1l5IJdQ3IgwPOGgThSYRd6YkB5zl5BM-5cZZlR0604XkRw5hqE1A92EAwtHNzWOyFSx10=@protonmail.com> <6DrWdGwEgQsytolI-pqvAozYS9u1TRm4ZnhgluFoNSiGoM70ffXo3bL7oK6nixl04eq9AN6tCFJQrFAhDn7liZBOJXLyKz-vG4X3WaAbWeg=@protonmail.com> Message-ID: <20200202131633.0b5bfc32@parabola> i tried building 72.0.1 for ARM several times - the build keeps freezing around 400 minutes in - the last try i let it run for 5 days and it never got past that point and never quit i also noticed the explicit MOZ_MAKE_FLAGS and i omitted it also - i just pushed my wip ARM-specific sections to abslibre, if anyone wants to give it a try attachments are the conventional way to send patches - some email clients such as claws anticipate that, and will present them with built-in syntax coloring From nobody at parabola.nu Mon Feb 3 05:04:45 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 03 Feb 2020 05:04:45 -0000 Subject: [Dev] Orphan Pcr package [tryton] marked out-of-date Message-ID: <20200203050445.665749.54737@winston.parabola.nu> nona at labs.parabola.nu wants to notify you that the following packages may be out-of-date: * tryton 4.2.1-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/tryton/ * tryton 4.2.1-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/tryton/ * tryton 4.2.1-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/tryton/ The user provided the following additional text: Modifications to PKGBUILD --- pkgver=5.4.3 _pkgdir=5.4 ... depends=('python>=3.5' 'python-cairo' 'python-dateutil' 'python-pygobject-stubs' 'pygobject-devel') ... build() { cd $srcdir/$pkgname-$pkgver # This should be optional (privacy) sed -i "s-'client.check_version': True-'client.check_version': False-g" tryton/config.py python setup.py build } package() { cd $srcdir/$pkgname-$pkgver python setup.py install --root=$pkgdir --optimize=1 install -D -m644 $srcdir/$pkgname.desktop $pkgdir/usr/share/applications/$pkgname.desktop } --- Modifications end ??* consider adding the icon * Note about the sed command: without that line, the client connects to demo.tryton.org on the first run. There is no easy way to change it otherwise. Once the user runs the application, she can decide whether connecting to the server is fine from the main menu. This decision belongs to the user, not the developer. From nobody at parabola.nu Mon Feb 3 05:21:33 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 03 Feb 2020 05:21:33 -0000 Subject: [Dev] Orphan Pcr package [trytond] marked out-of-date Message-ID: <20200203052133.665749.89627@winston.parabola.nu> nona at labs.parabola.nu wants to notify you that the following packages may be out-of-date: * trytond 4.2.1-1 [pcr] (armv7h): https://parabolagnulinux.org/packages/pcr/armv7h/trytond/ * trytond 4.2.1-1 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/trytond/ * trytond 4.2.1-1 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/trytond/ The user provided the following additional text: Hi, please check these: https://notabug.org/broncodev/trytond-pkgbuild/commit/e385905c8fef0903ebc7df7145788cf3357eee37 https://notabug.org/broncodev/tryton-setup Thanks. From theova at bluewin.ch Mon Feb 3 20:00:41 2020 From: theova at bluewin.ch (theova) Date: Mon, 3 Feb 2020 21:00:41 +0100 Subject: [Dev] [PATCH] Update [libre/qutebrowser] to 1.10.0 Message-ID: <20200203200041.oyt6l2fg2fcpqryq@RainbowWarrior.localdomain> Version 1.10.0 of qutebrowser is out. The patch below updates the according package in [libre]. Built on all three architectures, tested successfully on x86_64. Changelog: - Bump version and checksum Thanks a lot for having a look at it. -------------- next part -------------- From 55df4ede00f909f6d2702c57cefab923791e8c8e Mon Sep 17 00:00:00 2001 From: Theo von Arx Date: Mon, 3 Feb 2020 12:00:44 +0100 Subject: [PATCH] Update [libre/qutebrowser] to 1.10.0 --- libre/qutebrowser/PKGBUILD | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/libre/qutebrowser/PKGBUILD b/libre/qutebrowser/PKGBUILD index dc154da18..c473001bd 100644 --- a/libre/qutebrowser/PKGBUILD +++ b/libre/qutebrowser/PKGBUILD @@ -9,9 +9,9 @@ # - set webkit backend as default pkgname=qutebrowser -_pkgver_armv7h=1.9.0 # this could be an 'any' package -_pkgver_i686=1.9.0 # but our different arches do not always roll at the same speed -_pkgver_x86_64=1.9.0 +_pkgver_armv7h=1.10.0 # this could be an 'any' package +_pkgver_i686=1.10.0 # but our different arches do not always roll at the same speed +_pkgver_x86_64=1.10.0 eval "pkgver=\$_pkgver_${CARCH}" pkgrel=1 pkgrel+=.par1 @@ -34,13 +34,13 @@ source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/q "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc" "webkit-warning.patch") validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") # Florian Bruhin -_sha256sums_x86_64=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_x86_64=('7ecd7a08380b22eb1268fcc4446ba9d4d005601cb9366097779255edd9683bdf' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') -_sha256sums_i686=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_i686=('7ecd7a08380b22eb1268fcc4446ba9d4d005601cb9366097779255edd9683bdf' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') -_sha256sums_armv7h=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_armv7h=('7ecd7a08380b22eb1268fcc4446ba9d4d005601cb9366097779255edd9683bdf' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') eval "sha256sums=(\${_sha256sums_${CARCH}[@]})" -- 2.25.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From theova at bluewin.ch Mon Feb 3 20:14:53 2020 From: theova at bluewin.ch (theova) Date: Mon, 3 Feb 2020 21:14:53 +0100 Subject: [Dev] Plans for nonprism [was neutered geoclue] In-Reply-To: <20191215215021.4aa1d2af@parabola> References: <20191216022307.GD32068@freemor.ca> <20191215215021.4aa1d2af@parabola> Message-ID: <20200203201453.j5q22vg35hdp2wui@RainbowWarrior.localdomain> The point of having a privacy-as-default repository with less maintenance workload is absolutely right for me. What is the current status on this? Is there any help needed? I could investigate, test or build packages. Otherwise I can also look at today's [nonprism] packages and keep them up-to-date. bill-auger schrieb am Sun, 15. Dec 19 21:50: >i like the idea of the name change - it is probably was never >meaningful to most people unless they read the wiki article >first - a concise name like 'privacy' would make its purpose much >more obvious > >AFAIK the repo name itself could be changed arbitrarily; but >each of the packages also have ".nonprismN" in the 'pkgrel' - im >not sure why that is necessary (likewise for ".nonsystemdN") - >packages in [libre] and [pcr] do not end with ".libreN" or >".pcrN" > >in my experience, `pacman -Syu` will not automatically upgrade a >newer version of some duplicated package if it is in a >lower-priority repo - it is absolutely necessary to have the >repos declared in pacman.conf in the expected order of priority >- so, it should be totally sane to drop the special descriptors >".nonprismN" and ".nonsystemdN" from the 'pkgver', and have the >same ".parabolaN", or ".parN" for all packages, right? > >maybe im confused about that; but it is common when packaging >with libretools, that some package conflicts arise because some >package needs to be deleted from the local /repo, which >is shadowing the one in the public repos, because of its >priority in the chroot pacman.conf >_______________________________________________ >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 theova at bluewin.ch Mon Feb 3 20:23:04 2020 From: theova at bluewin.ch (theova) Date: Mon, 3 Feb 2020 21:23:04 +0100 Subject: [Dev] [PATCH] Update [libre/gnome-boxes] to 3.34.3 Message-ID: <20200203202304.slalxylokmqyygix@RainbowWarrior.localdomain> The patch below updates [libre/gnome-boxes] to 3.34.3 Chanelog: - Bump version number, git tag and checksum Built on all three architectures, successfully tested on x86_64. -------------- next part -------------- From 64796145f69374001debc948109ea9a619d06434 Mon Sep 17 00:00:00 2001 From: Theo von Arx Date: Thu, 30 Jan 2020 21:03:15 +0100 Subject: [PATCH] libre/gnome-boxes update to 3.34.3 --- libre/gnome-boxes/PKGBUILD | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libre/gnome-boxes/PKGBUILD b/libre/gnome-boxes/PKGBUILD index 638585df8..a3da929b0 100644 --- a/libre/gnome-boxes/PKGBUILD +++ b/libre/gnome-boxes/PKGBUILD @@ -10,7 +10,7 @@ # - Replace Windows with Parabola in documention pkgname=gnome-boxes -pkgver=3.34.2 +pkgver=3.34.3 pkgrel=2 pkgrel+=.par1 pkgdesc="Simple GNOME application to access remote or virtual systems" @@ -25,7 +25,7 @@ groups=('gnome') depends=('cdrtools' 'gtk-vnc' 'libarchive' 'libgudev' 'libosinfo' 'libsecret' 'libvirt-glib' 'mtools' 'qemu' 'spice-gtk' 'tracker' 'webkit2gtk' 'freerdp') makedepends=('git' 'gobject-introspection' 'yelp-tools' 'meson' 'spice-protocol' 'vala') -_commit=2edb94153b163759d18195c511d6cf5212fd1bfe # tags/v3.34.2^0 +_commit=c3bce5984eb53cc883850969f3e4a3e8e2cc6d44 # tags/v3.34.3^0 source=("git+https://gitlab.gnome.org/GNOME/gnome-boxes.git#commit=$_commit" "git+https://gitlab.gnome.org/GNOME/gtk-frdp.git" "git+https://gitlab.gnome.org/felipeborges/libovf-glib.git") @@ -33,7 +33,7 @@ source+=(hide_download_button.patch) sha256sums=('SKIP' 'SKIP' 'SKIP') -sha256sums+=('74f0d30e4ca280afe4c1f532ecc2856e8ee850a0e3d1812138536b4b9e7e2e7f') +sha256sums+=('0539b344dc0bc8424539f747ed9c638ea414fe96153b803dae50bf5bf2d5aae5') pkgver() { cd $pkgname -- 2.25.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From megver83 at hyperbola.info Tue Feb 4 04:06:46 2020 From: megver83 at hyperbola.info (Megver83) Date: Tue, 04 Feb 2020 01:06:46 -0300 Subject: [Dev] Creation for a new wiki user Message-ID: Hi, I want to create a wiki user for mai (read here[0] to get in context). However, I'd like to know how can I create users (from winston?). And regarding the wiki page openness, do we still need registrations to be closed? I remember the spam attack problem, but haven't anyone got a solution? a captcha or sth. like the typical "what is the output of "? [0] https://labs.parabola.nu/issues/2372#note-42 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: This is a digitally signed message part URL: From freemor at freemor.ca Tue Feb 4 12:53:28 2020 From: freemor at freemor.ca (Freemor) Date: Tue, 4 Feb 2020 08:53:28 -0400 Subject: [Dev] Plans for nonprism [was neutered geoclue] In-Reply-To: <20200203201453.j5q22vg35hdp2wui@RainbowWarrior.localdomain> References: <20191216022307.GD32068@freemor.ca> <20191215215021.4aa1d2af@parabola> <20200203201453.j5q22vg35hdp2wui@RainbowWarrior.localdomain> Message-ID: <20200204125328.GA19651@freemor.ca> This is still ongoing but more slowly due to me having to step back a bit. I've most recently bee working through the less popular packages in nonprism and been bringing them up-to-date. Darktable is a stumbling block as it now olny supports 64 bit code and thus the latest version wont compile for 1686/armv7h. I haven't had the chance to dig in yet and see if this is an actual problem or just something they have stuck in the bre-build checks so they don't have to worry about 32 bit clean code. In doing the there are some things in nonprism that possibly should be moved to libre because the reason for them being in there is disabling third party site add-ons (gthumb comes to mind) and isn't not suggesting non-free services under the libre/parabola social contract/etc umbrella. What would be useful is if you could glance through the PKGBUILDS and compile a list of the packages by: Only removes geoclue - these we could lose thanks to the neutered geoclue Only removes addon or access to non-free service - some of these might be candidates for moving to libre Actual privacy enhancing - the "hardened" packages/etc. things that actually move the privacy bar a bit higher What I'm seeing is that nonprism, especially given the name, was probably created around the time of the Snowden leaks and some of the things in there look a little more reactionary then a well defined curated collection. WRT the above. One thing that is needed and that you and others can help with is discussion here so create a clear, concise, idea of what should be in "privacy-enhanced". By which I'm not meaning actual package but a set of guidelines. a la "Things that remove tracking/dialing home". And also what kinds of things should not be included because they fall under the umbrella of security (we should probably think about a "Security-enhanced" down the road), or should be in libre, etc. Another thing that would be good is some sort of naming convention so an end user can easily see whats "enhanced" like foo-TR-GlR for program foo but with tracking removed and geolocation removed. Or could be that each package has a .txt file that lives in /usr/shae/doc/privacy-enhanced/ that describes what was changed and why. On Mon, Feb 03, 2020 at 09:14:53PM +0100, theova wrote: > The point of having a privacy-as-default repository with less > maintenance workload is absolutely right for me. > > What is the current status on this? Is there any help needed? > I could investigate, test or build packages. > > Otherwise I can also look at today's [nonprism] packages and keep them > up-to-date. > > bill-auger schrieb am Sun, 15. Dec 19 21:50: > >i like the idea of the name change - it is probably was never > >meaningful to most people unless they read the wiki article > >first - a concise name like 'privacy' would make its purpose much > >more obvious > > > >AFAIK the repo name itself could be changed arbitrarily; but > >each of the packages also have ".nonprismN" in the 'pkgrel' - im > >not sure why that is necessary (likewise for ".nonsystemdN") - > >packages in [libre] and [pcr] do not end with ".libreN" or > >".pcrN" > > > >in my experience, `pacman -Syu` will not automatically upgrade a > >newer version of some duplicated package if it is in a > >lower-priority repo - it is absolutely necessary to have the > >repos declared in pacman.conf in the expected order of priority > >- so, it should be totally sane to drop the special descriptors > >".nonprismN" and ".nonsystemdN" from the 'pkgver', and have the > >same ".parabolaN", or ".parN" for all packages, right? > > > >maybe im confused about that; but it is common when packaging > >with libretools, that some package conflicts arise because some > >package needs to be deleted from the local /repo, which > >is shadowing the one in the public repos, because of its > >priority in the chroot pacman.conf > >_______________________________________________ > >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 -- Want to send me an encrypted reply? Click here: https://hawkpost.co/box/e414d311-bd6a-4429-8e9e-6a690d5ad034 The rest of my contact details are at: http://freemor.ca/contact -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From bill-auger at peers.community Tue Feb 4 16:48:18 2020 From: bill-auger at peers.community (bill-auger) Date: Tue, 4 Feb 2020 11:48:18 -0500 Subject: [Dev] Creation for a new wiki user In-Reply-To: References: Message-ID: <20200204114818.27631072@parabola> the solution i have been leaning toward is to move the wiki pages into redmine, and delete mediawiki - that way users would need only one set of login credentials, the captcha is already in place for redmine, and it would be one less service running on the server i dont know how to add a wiki from a shell, or if thats even possible - i have been doing it through the website in the normal way From theova at bluewin.ch Thu Feb 6 16:49:24 2020 From: theova at bluewin.ch (theova) Date: Thu, 6 Feb 2020 17:49:24 +0100 Subject: [Dev] Plans for nonprism [was neutered geoclue] In-Reply-To: <20200204125328.GA19651@freemor.ca> References: <20191216022307.GD32068@freemor.ca> <20191215215021.4aa1d2af@parabola> <20200203201453.j5q22vg35hdp2wui@RainbowWarrior.localdomain> <20200204125328.GA19651@freemor.ca> Message-ID: <20200206164924.27udfl7ciyx34vzw@RainbowWarrior.localdomain> Sounds like a plan. I will try to sort the [nonprism] packages the next days. Could someone give me more privileges on redmine, so that I can group issues? My account is "theova" (https://labs.parabola.nu/users/4743). I think having /usr/share/privacy-enhanced/*.txt may simplify the activation of the privacy-enhanced repo. This could also force package maintainers to document the modification of package - never a bad idea. Freemor schrieb am Tue, 04. Feb 20 08:53: > This is still ongoing but more slowly due to me having to step back a bit. >I've most recently bee working through the less popular packages in nonprism >and been bringing them up-to-date. Darktable is a stumbling block as it now >olny supports 64 bit code and thus the latest version wont compile for >1686/armv7h. I haven't had the chance to dig in yet and see if this is an >actual problem or just something they have stuck in the bre-build checks so they >don't have to worry about 32 bit clean code. > > In doing the there are some things in nonprism that possibly should be moved to >libre because the reason for them being in there is disabling third party site >add-ons (gthumb comes to mind) and isn't not suggesting non-free services under >the libre/parabola social contract/etc umbrella. > > What would be useful is if you could glance through the PKGBUILDS and compile a >list of the packages by: > >Only removes geoclue - these we could lose thanks to the neutered geoclue >Only removes addon or access to non-free service - some of these might be > candidates for moving to libre >Actual privacy enhancing - the "hardened" packages/etc. things that actually > move the privacy bar a bit higher > > What I'm seeing is that nonprism, especially given the name, was probably >created around the time of the Snowden leaks and some of the things in there >look a little more reactionary then a well defined curated collection. > > > WRT the above. One thing that is needed and that you and others can help with is >discussion here so create a clear, concise, idea of what should be in >"privacy-enhanced". By which I'm not meaning actual package but a set of >guidelines. a la "Things that remove tracking/dialing home". And also what >kinds of things should not be included because they fall under the umbrella of >security (we should probably think about a "Security-enhanced" down the road), >or should be in libre, etc. > > Another thing that would be good is some sort of naming convention so an end >user can easily see whats "enhanced" like foo-TR-GlR for program foo but with >tracking removed and geolocation removed. Or could be that each package has a >.txt file that lives in /usr/shae/doc/privacy-enhanced/ that describes what was >changed and why. > > > >On Mon, Feb 03, 2020 at 09:14:53PM +0100, theova wrote: >> The point of having a privacy-as-default repository with less >> maintenance workload is absolutely right for me. >> >> What is the current status on this? Is there any help needed? >> I could investigate, test or build packages. >> >> Otherwise I can also look at today's [nonprism] packages and keep them >> up-to-date. >> >> bill-auger schrieb am Sun, 15. Dec 19 21:50: >> >i like the idea of the name change - it is probably was never >> >meaningful to most people unless they read the wiki article >> >first - a concise name like 'privacy' would make its purpose much >> >more obvious >> > >> >AFAIK the repo name itself could be changed arbitrarily; but >> >each of the packages also have ".nonprismN" in the 'pkgrel' - im >> >not sure why that is necessary (likewise for ".nonsystemdN") - >> >packages in [libre] and [pcr] do not end with ".libreN" or >> >".pcrN" >> > >> >in my experience, `pacman -Syu` will not automatically upgrade a >> >newer version of some duplicated package if it is in a >> >lower-priority repo - it is absolutely necessary to have the >> >repos declared in pacman.conf in the expected order of priority >> >- so, it should be totally sane to drop the special descriptors >> >".nonprismN" and ".nonsystemdN" from the 'pkgver', and have the >> >same ".parabolaN", or ".parN" for all packages, right? >> > >> >maybe im confused about that; but it is common when packaging >> >with libretools, that some package conflicts arise because some >> >package needs to be deleted from the local /repo, which >> >is shadowing the one in the public repos, because of its >> >priority in the chroot pacman.conf >> >_______________________________________________ >> >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 > > >-- >Want to send me an encrypted reply? >Click here: https://hawkpost.co/box/e414d311-bd6a-4429-8e9e-6a690d5ad034 >The rest of my contact details are at: >http://freemor.ca/contact >_______________________________________________ >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 bill-auger at peers.community Thu Feb 6 17:20:23 2020 From: bill-auger at peers.community (bill-auger) Date: Thu, 6 Feb 2020 12:20:23 -0500 Subject: [Dev] Plans for nonprism [was neutered geoclue] In-Reply-To: <20200206164924.27udfl7ciyx34vzw@RainbowWarrior.localdomain> References: <20191216022307.GD32068@freemor.ca> <20191215215021.4aa1d2af@parabola> <20200203201453.j5q22vg35hdp2wui@RainbowWarrior.localdomain> <20200204125328.GA19651@freemor.ca> <20200206164924.27udfl7ciyx34vzw@RainbowWarrior.localdomain> Message-ID: <20200206122023.3a9faef2@parabola> theova - you are a full moderator on redmine now From GNUtoo at cyberdimension.org Sat Feb 8 05:50:59 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Sat, 8 Feb 2020 06:50:59 +0100 Subject: [Dev] Getting ARM computers, Was: A10 OLinuxino Lime not booting In-Reply-To: References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> Message-ID: <20200208065059.6207b2ba@primarylaptop.localdomain> On Fri, 31 Jan 2020 13:05:58 -0300 Megver83 wrote: > However, I see more hope in olimex since, as you said, they proudly > proclaim parabola as a working OS for their SBC. A good excuse to ask > for one is having it so we make sure Parabola remains working in such > device. We could also ask for some arm64 board(s) that are already supported in upstream u-boot and Linux. The only arm64 board I have has an integrated bootloader with (unsigned) nonfree software, but it's supported by Linux upstream, so I could at least test the linux-libre-aarch64 kernel on it. To fully support arm64 we would need to package some bootloaders as well. Right now I'm also too busy with other things, so if someone else want to try it would be great. > P.S: This last week I've got some money from Liberapay donations > through paypal which is almost the half of the price of the C201. If I > get enough from the donations I will inmediately buy a C201. Once you do, it would be a good idea to contact Paul Kocialkowski to try to get a servo too. This would give us the ability to get the boot logs through the serial port. It's probably also nice to do automatic testing on the device as it can probably control it completely through software. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From GNUtoo at cyberdimension.org Sat Feb 8 05:42:57 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Sat, 8 Feb 2020 06:42:57 +0100 Subject: [Dev] A10 OLinuxino Lime not booting In-Reply-To: <20200131021433.021e125a@parabola> References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> Message-ID: <20200208064257.5a615f6c@primarylaptop.localdomain> On Fri, 31 Jan 2020 02:14:32 -0500 bill-auger wrote: > i glossed over this message because of the title > > a few months back, olimex released a new post proudly > proclaiming that parabola works well on it - this just shows how > difficult these ARM devices are to support, especially if none > of us actually have one I've a pcduino lite with an A10. I could try to find the time to check if it still boots. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From GNUtoo at cyberdimension.org Sat Feb 8 17:47:26 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Sat, 8 Feb 2020 18:47:26 +0100 Subject: [Dev] A10 OLinuxino Lime not booting In-Reply-To: <20200208064257.5a615f6c@primarylaptop.localdomain> References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> <20200208064257.5a615f6c@primarylaptop.localdomain> Message-ID: <20200208184726.0f538dd1@primarylaptop.localdomain> On Sat, 8 Feb 2020 06:42:57 +0100 Denis 'GNUtoo' Carikli wrote: > I've a pcduino lite with an A10. I could try to find the time to check > if it still boots. My pcduino lite still boots after pacman -Syuu. I'm using uboot4extlinux-linksprite_pcduino with it. Is there some references or logs about the A10 Lime not booting? Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From lovell.joshyyy at gmail.com Sun Feb 9 15:07:39 2020 From: lovell.joshyyy at gmail.com (Josh Branning) Date: Sun, 9 Feb 2020 15:07:39 +0000 Subject: [Dev] A10 OLinuxino Lime not booting, LXDE switch, openrc In-Reply-To: <20200208184726.0f538dd1@primarylaptop.localdomain> References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> <20200208064257.5a615f6c@primarylaptop.localdomain> <20200208184726.0f538dd1@primarylaptop.localdomain> Message-ID: <373e827e-7649-0b7e-6405-bdbfa58a804c@gmail.com> Hi, I have an A10 OLinuxino Lime, and it doesn't boot with parabola. I think the issue is the [generic] arm kernel, as it hangs after u-boot stage. I successfully compiled a different GNU/Linux OS for this device, it's also worth noting that alarm also works for this device. It's probably not just an issue with the kernel, I see part of the problem may be that HDMI isn't set up in the script.bin. Regarding LXDE, I prefer GTK over QT. I am in the process of moving my machines to something custom [xfce4-panel, openbox, xdm, xfce4-terminal, spacefm] xfce has made the move to GTK3 which is the way forward IMO. I use this because I'd rather a system based on C than C++. Thanks for the work on openrc, this is much appreciated, and again, preferred imo too. I do not check my emails very often, so probably won't be able to read all your lovely replies, but again, thanks so much for the work you all are putting into this, it's much appreciated, Josh On 08/02/20 17:47, Denis 'GNUtoo' Carikli wrote: > On Sat, 8 Feb 2020 06:42:57 +0100 > Denis 'GNUtoo' Carikli wrote: > >> I've a pcduino lite with an A10. I could try to find the time to check >> if it still boots. > My pcduino lite still boots after pacman -Syuu. I'm using > uboot4extlinux-linksprite_pcduino with it. > > Is there some references or logs about the A10 Lime not booting? > > Denis. > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > From bill-auger at peers.community Mon Feb 10 03:09:12 2020 From: bill-auger at peers.community (bill-auger) Date: Sun, 9 Feb 2020 22:09:12 -0500 Subject: [Dev] A10 OLinuxino Lime not booting, LXDE switch, openrc In-Reply-To: <373e827e-7649-0b7e-6405-bdbfa58a804c@gmail.com> References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> <20200208064257.5a615f6c@primarylaptop.localdomain> <20200208184726.0f538dd1@primarylaptop.localdomain> <373e827e-7649-0b7e-6405-bdbfa58a804c@gmail.com> Message-ID: <20200209220912.0b3f3f14@parabola> FWIW, LXDE also has a GTK3 port - either version is in the parabola repos From lovell.joshyyy at gmail.com Mon Feb 10 17:25:33 2020 From: lovell.joshyyy at gmail.com (lovell.joshyyy) Date: Mon, 10 Feb 2020 17:25:33 +0000 Subject: [Dev] A10 OLinuxino Lime not booting, LXDE switch, openrc In-Reply-To: <20200209220912.0b3f3f14@parabola> References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> <20200208064257.5a615f6c@primarylaptop.localdomain> <20200208184726.0f538dd1@primarylaptop.localdomain> <373e827e-7649-0b7e-6405-bdbfa58a804c@gmail.com> <20200209220912.0b3f3f14@parabola> Message-ID: Apologies if this email is incorrectly formatted, I'm using webmail. Below is the script I used to try and get the a10 olinuxino lime to work. It was run from a debian-based machine. I could try retest, but I am [non-literally] flooded at the moment. I may retest if I get the time. #!/bin/sh if ! [ -b "$1" ]; then echo "Be careful ..." echo "Run as root and enter the device block as the first argument, good luck!" exit 1 fi ##Install for creating boot.scr apt-get install u-boot-tools mkdir workingDir cd workingDir ##Download the stuff wget https://www.parabola.nu/packages/libre/armv7h/uboot4extlinux-a10-olinuxino-lime/download/ wget https://repomirror.parabola.nu/iso/systemd-cli-2018-02-06/parabola-systemd-cli-armv7h-tarball-2018-02-06.tar.gz wget https://git.parabola.nu/abslibre.git/plain/libre/uboot-sunxi/boot.txt ##Fresh the sdcard shred "$1" ##Do the stuff tar -xf uboot4extlinux* #we do this in two separate steps ... create the partition table ... printf "o\nw\n" | fdisk --wipe always "$1" #... and create the partition printf "n\np\n1\n\n\nw\n" | fdisk --wipe always "$1" mkfs.ext4 "${1}1" mkdir mnt mount "${1}1" mnt tar -xf parabola-*-armv7h-*.tar.gz -C mnt cp -a boot/extlinux mnt/boot/ cp -a boot/u-boot mnt/boot/ dd if=boot/u-boot/images/u-boot-sunxi-with-spl.bin of=${1} bs=1024 seek=8 cp -a boot.txt mnt/boot sed -i "s#console=\${console}#console=ttyS0,115200 console=tty0 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1280x720p60#g" mnt/boot/boot.txt mkimage -A arm -O linux -T script -C none -n "U-Boot boot script" -d mnt/boot/boot.txt boot.scr cp -a boot.scr mnt/boot sync umount mnt On Mon, Feb 10, 2020 at 3:13 AM bill-auger wrote: > FWIW, LXDE also has a GTK3 port - either version is in the > parabola repos > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From GNUtoo at cyberdimension.org Tue Feb 11 04:30:04 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Tue, 11 Feb 2020 05:30:04 +0100 Subject: [Dev] A10 OLinuxino Lime not booting, LXDE switch, openrc In-Reply-To: References: <88f7f32f19fc2ec79e376f3d1cc967b333f61140.camel@hyperbola.info> <20191210202724.509c02d4@primarylaptop.localdomain> <20191211041338.394b4759@parabola> <3cc20083-b202-1e89-48b7-10f968ad2650@gmail.com> <20200131021433.021e125a@parabola> <20200208064257.5a615f6c@primarylaptop.localdomain> <20200208184726.0f538dd1@primarylaptop.localdomain> <373e827e-7649-0b7e-6405-bdbfa58a804c@gmail.com> <20200209220912.0b3f3f14@parabola> Message-ID: <20200211053004.1364fb8b@primarylaptop.localdomain> On Mon, 10 Feb 2020 17:25:33 +0000 "lovell.joshyyy" wrote: I checked in u-boot v2019.10 and we have CONFIG_DISTRO_DEFAULTS=y: > $ export ARCH=arm > $ make A10-OLinuXino-Lime_defconfig > $ grep CONFIG_DISTRO_DEFAULTS .config > CONFIG_DISTRO_DEFAULTS=y So this means that we can use /boot/extlinux/extlinux.conf instead of boot.scr as it is easier to work with. Else you would need the boot.scr to conform to u-boot's distro boot requirements. > ##Download the stuff > wget > https://www.parabola.nu/packages/libre/armv7h/uboot4extlinux-a10-olinuxino-lime/download/ > wget > https://repomirror.parabola.nu/iso/systemd-cli-2018-02-06/parabola-systemd-cli-armv7h-tarball-2018-02-06.tar.gz It'd be better to check that stuff with packan-key or gpg. > wget > https://git.parabola.nu/abslibre.git/plain/libre/uboot-sunxi/boot.txt I've quoted that script below: > part uuid ${devtype} ${devnum}:${bootpart} uuid I did a quick look, and bootpart is probably not part of the u-boot environment anymore. Also it seems that we don't have compatibility with old boot scripts: $ grep CONFIG_OLD_SUNXI_KERNEL_COMPAT .config # CONFIG_OLD_SUNXI_KERNEL_COMPAT is not set > setenv bootargs console=${console} root=PARTUUID=${uuid} rw rootwait > > if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/vmlinuz-linux-libre; then > if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/linux-libre/${fdtfile}; then > if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux-libre.img; then > bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}; > else > bootz ${kernel_addr_r} - ${fdt_addr_r}; > fi; > fi; > fi So that probably fails because of the bootpart. The addresses look compliant, devtype and devnum probably works as they are widely used, but I didn't see them mentioned in doc/README.distro. > if load ${devtype} ${devnum}:${bootpart} 0x48000000 /boot/uImage; then There is no /boot/uImage + the bootpart probably fails too here, it would also need the devicetree and so on to work. > if load ${devtype} ${devnum}:${bootpart} 0x43000000 /boot/script.bin; then > setenv bootm_boot_mode sec; > bootm 0x48000000; > fi; > fi > cp -a boot.txt mnt/boot > mnt/boot/boot.txt > mkimage -A arm -O linux -T script -C none -n "U-Boot boot script" -d > mnt/boot/boot.txt boot.scr > cp -a boot.scr mnt/boot Try to rm mnt/boot/boot.scr, because u-boot probably tries that script first, before trying /boot/extlinux/extlinux.conf. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Tue Feb 11 10:46:21 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 11 Feb 2020 10:46:21 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20200211104621.665749.89682@winston.parabola.nu> ugw.ugw at gmail.com wants to notify you that the following packages may be out-of-date: * iceweasel 1:72.0.1-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/ * iceweasel 1:72.0.1-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Firefox 73 has been released. As an FYI, an Iceweasel build will fail if it can't find a file at branding/content/firefox-wordmark.svg, similar to the issue with aboutlogins.svg a few versions ago. From grizzlyuser at protonmail.com Wed Feb 12 13:17:46 2020 From: grizzlyuser at protonmail.com (grizzlyuser) Date: Wed, 12 Feb 2020 13:17:46 +0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date In-Reply-To: <20200211104621.665749.89682@winston.parabola.nu> References: <20200211104621.665749.89682@winston.parabola.nu> Message-ID: If anyone is interested, please find updated patches for Iceweasel 73.0-1 Please note that this is WIP. I didn't build it for any of the architectures. Just started libremakepkg for all 3, and made sure it proceeded successfully to "compiling..." stage. Currently x86_64 build is running on my machine. Will post results for it and also for other two if / when they are ready. Also note that for ARM patch the option "mk_add_options MOZ_MAKE_FLAGS="-j2"" is still included, but commented out. I want to see if it builds without that one. Commit messages are included in all the patches, please refer to them for explanations of the changes. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Sync-with-changes-from-Arch-Linux-Firefox-73.0-1.patch Type: text/x-patch Size: 5392 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Sync-with-changes-from-Arch-Linux-ARM-Firefox-73.0-1.patch Type: text/x-patch Size: 4422 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-Drop-patching-of-source-code-comments-and-non-user-f.patch Type: text/x-patch Size: 3946 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0004-Update-rebranding-of-DevTools-What-s-New-tab.patch Type: text/x-patch Size: 1380 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0007-Rebrand-wordmark-in-new-tab-in-Private-Browsing-mode.patch Type: text/x-patch Size: 1257 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0006-Disable-What-s-New-gift-icon-in-toolbar-and-main-men.patch Type: text/x-patch Size: 932 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0005-Change-search-placeholder-in-about-addons.patch Type: text/x-patch Size: 1097 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0008-updpkgsums-and-minor-fixes-for-i686.patch Type: text/x-patch Size: 3745 bytes Desc: not available URL: From grizzlyuser at protonmail.com Fri Feb 14 21:52:25 2020 From: grizzlyuser at protonmail.com (grizzlyuser) Date: Fri, 14 Feb 2020 21:52:25 +0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date In-Reply-To: References: <20200211104621.665749.89682@winston.parabola.nu> Message-ID: Please find updated patches for iceweasel 73.0-1 attached. Built and smoke tested for x86_64, armv7h, i686. iceweasel_branding_73.0-1.patch should be applied to the contents of [1]. I couldn't find actual git repository for those. Please apply the patch with 'git apply' rather than 'patch', because it looks like the latter doesn't handle symlink renaming. Branding changes are necessary because of the missing 'firefox-wordmark.svg' mentioned earlier. I chose to generate it the same way as 'about-wordmark.svg'. Overall, it seems branding package needs to be updated according to latest changes from Firefox, and to replace glyphs of nonfree font in the logo (see [2]). Successfully built the package for ARM without "mk_add_options MOZ_MAKE_FLAGS="-j2"" But it still took about 8 hours on six x86_64 cores. [1] https://repo.parabola.nu/other/iceweasel/iceweasel_70.0-1.branding.tar.xz [2] https://labs.parabola.nu/issues/2488#note-8 -------------- next part -------------- A non-text attachment was scrubbed... Name: iceweasel_73.0-1.patch Type: text/x-patch Size: 22449 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: iceweasel_branding_73.0-1.patch Type: text/x-patch Size: 11000 bytes Desc: not available URL: From nobody at parabola.nu Sat Feb 15 01:37:22 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 15 Feb 2020 01:37:22 -0000 Subject: [Dev] Orphan Libre package [blender] marked out-of-date Message-ID: <20200215013722.665747.89363@winston.parabola.nu> a.reviewer1234 at yahoo.com wants to notify you that the following packages may be out-of-date: * blender 17:2.81.a-3.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/blender/ * blender 17:2.81.a-3.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/blender/ * blender 17:2.81.a-3.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/blender/ The user provided the following additional text: 2.82 :) From nobody at parabola.nu Sun Feb 16 11:01:53 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 16 Feb 2020 11:01:53 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20200216110153.665747.77734@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * linux-libre 5.5.1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 5.5.1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-chromebook 5.5.1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-chromebook/ * linux-libre-docs 5.5.1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 5.5.1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 5.5.1-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 5.5.1-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://linux-libre.fsfla.org/pub/linux-libre/releases/ From nobody at parabola.nu Sun Feb 16 11:06:45 2020 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 16 Feb 2020 11:06:45 -0000 Subject: [Dev] Orphan Libre package [openexr] marked out-of-date Message-ID: <20200216110645.665748.84381@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * openexr 2.4.0-5.par2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/openexr/ * openexr 2.4.0-5.par2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/openexr/ * openexr 2.4.0-5.par2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/openexr/ The user provided the following additional text: Thank you for maintaining this package! A new pkgrel is available in Arch Linux: https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/openexr From ced at cyberbits.eu Mon Feb 17 14:28:37 2020 From: ced at cyberbits.eu (ced at cyberbits.eu) Date: Mon, 17 Feb 2020 14:28:37 +0000 Subject: [Dev] New rsync mirror Message-ID: <521c6b27-9004-4210-aa75-6090ff6f0ac3@cyberbits.eu> Hi, I run and recently added a rsync endpoint in addition to HTTP(S): rsync://rsync.cyberbits.eu/parabola/ It's got a 1 Gbps uplink. More details can be found at Thanks, Ced -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From theova at bluewin.ch Wed Feb 19 20:01:57 2020 From: theova at bluewin.ch (theova) Date: Wed, 19 Feb 2020 21:01:57 +0100 Subject: [Dev] [PATCH] Update [libre/qutebrowser] to 1.10.1 In-Reply-To: <20200203200041.oyt6l2fg2fcpqryq@RainbowWarrior.localdomain> References: <20200203200041.oyt6l2fg2fcpqryq@RainbowWarrior.localdomain> Message-ID: <20200219200157.5hni52u7eaa6s2m6@RainbowWarrior.localdomain> Version 1.10.1 of qutebrowser is out. The patch below updates the according package in [libre]. Built on all three architectures, tested successfully on x86_64. Changelog: - Bump version and checksum Thanks a lot for having a look at it. -------------- next part -------------- From e3fe1e4c9d1304453a8cef3048db680224f48e3e Mon Sep 17 00:00:00 2001 From: Theo von Arx Date: Wed, 19 Feb 2020 20:58:05 +0100 Subject: [PATCH] Update [libre/qutebrowser] to 1.10.1 --- libre/qutebrowser/PKGBUILD | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/libre/qutebrowser/PKGBUILD b/libre/qutebrowser/PKGBUILD index dc154da18..874518b1d 100644 --- a/libre/qutebrowser/PKGBUILD +++ b/libre/qutebrowser/PKGBUILD @@ -9,9 +9,9 @@ # - set webkit backend as default pkgname=qutebrowser -_pkgver_armv7h=1.9.0 # this could be an 'any' package -_pkgver_i686=1.9.0 # but our different arches do not always roll at the same speed -_pkgver_x86_64=1.9.0 +_pkgver_armv7h=1.10.1 # this could be an 'any' package +_pkgver_i686=1.10.1 # but our different arches do not always roll at the same speed +_pkgver_x86_64=1.10.1 eval "pkgver=\$_pkgver_${CARCH}" pkgrel=1 pkgrel+=.par1 @@ -34,13 +34,13 @@ source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/q "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc" "webkit-warning.patch") validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") # Florian Bruhin -_sha256sums_x86_64=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_x86_64=('a8ed72d40b4b2283b61b939bb358ada2270fe153bccb8ee012e94fb29cb66c19' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') -_sha256sums_i686=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_i686=('a8ed72d40b4b2283b61b939bb358ada2270fe153bccb8ee012e94fb29cb66c19' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') -_sha256sums_armv7h=('2748fef2d0360000f6f814dae99ad8ad08b040cb4cf0e1e6d1e199ec70c01ef8' +_sha256sums_armv7h=('a8ed72d40b4b2283b61b939bb358ada2270fe153bccb8ee012e94fb29cb66c19' 'SKIP' '8509032254715a09d807ac5901657e66d0d0780e47bbe2b06f634d7b7c9792d0') eval "sha256sums=(\${_sha256sums_${CARCH}[@]})" -- 2.25.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From theova at bluewin.ch Wed Feb 19 20:36:46 2020 From: theova at bluewin.ch (theova) Date: Wed, 19 Feb 2020 21:36:46 +0100 Subject: [Dev] [PATCH] Update [libre/nextcloud-client] to v2.6.3 In-Reply-To: <20200102113251.5rlwtzotl6dukhau@RainbowWarrior.localdomain> References: <20200102113251.5rlwtzotl6dukhau@RainbowWarrior.localdomain> Message-ID: <20200219203646.stm63f7ezn45qo7s@RainbowWarrior.localdomain> The patch below updates [libre/nextcloud-client] to the newest version 2.6.3. The changelog is included in the patch. >Tested on x86_64, successfully built on i686. The arm build failes on my >arm chroot, but it is possible, that it compiles on others (such as the >one in beefcake) as discussed with Freemor on IRC. -------------- next part -------------- From 6be3ca2a35c82052ff1716f41c9ca0db532af256 Mon Sep 17 00:00:00 2001 From: Theo von Arx Date: Wed, 19 Feb 2020 21:20:57 +0100 Subject: [PATCH] Update [libre/nextcloud-client] to 2.6.3 - Bump version number, commit, and checksum - Add Nextcloud.conf to disable built-in updater - Built and successfully tested on x86_64 - Built on i686 - Build on armv7h failed --- libre/nextcloud-client/Nextcloud.conf | 2 ++ libre/nextcloud-client/PKGBUILD | 16 +++++++++++----- 2 files changed, 13 insertions(+), 5 deletions(-) create mode 100644 libre/nextcloud-client/Nextcloud.conf diff --git a/libre/nextcloud-client/Nextcloud.conf b/libre/nextcloud-client/Nextcloud.conf new file mode 100644 index 000000000..232a67665 --- /dev/null +++ b/libre/nextcloud-client/Nextcloud.conf @@ -0,0 +1,2 @@ +[General] +skipUpdateCheck=true diff --git a/libre/nextcloud-client/PKGBUILD b/libre/nextcloud-client/PKGBUILD index 2fe462798..080dbd2ba 100644 --- a/libre/nextcloud-client/PKGBUILD +++ b/libre/nextcloud-client/PKGBUILD @@ -8,8 +8,8 @@ pkgname=nextcloud-client -pkgver=2.6.2 -_commit=1d745535f7a95ff2265d6b6b47121200338fce83 +pkgver=2.6.3 +_commit=5880c4954e0e8fcaed9df59f1134958be3f60c06 pkgrel=1 pkgrel+=.parabola1 pkgdesc='Nextcloud desktop client' @@ -30,7 +30,8 @@ source=("$pkgname::git+https://github.com/nextcloud/desktop.git?signed#commit=$_ issue1458-workaround.patch::https://github.com/yan12125/desktop/commit/7da680ef7843a52c3136916744f50d4a003bb8b5.patch issue1458-2.patch::https://github.com/yan12125/desktop/commit/2b313368325dac5b8d0e69394cfcc4faaa745f75.patch $pkgname-fix-build.diff - $pkgname-FS64630.diff) + $pkgname-FS64630.diff + Nextcloud.conf) source+=(remove-qtwebengine.patch) validpgpkeys=( A26B951528EA1BA1678C7AE5D406C75CEE1A36D6 # one of keys controlled by github.com/camilasan @@ -40,9 +41,11 @@ sha256sums=('SKIP' '07cd68f54c004175b4a09cce25830a357d0ebaafaf4e4cabfb8b0d4deeded2f3' '157c87a789219a3442ca5947c48dcd1ef3898612ff32070bf8842a42bfbe857a' '8b257a0554ceb54a7ed320dbfa3becb97d6845338e28a8aa0a4f6239f3141645' - '6dea4453f220b63b993722cb155d567959600af261403870f5e34d35144a4fa7') + '6dea4453f220b63b993722cb155d567959600af261403870f5e34d35144a4fa7' + '5f51e41ef01d4e5b88a4735531105b84b4fb5317adc2a2996117c03fe5a44fc7') sha256sums+=('77d7afd2dc65a7625e1617dd2c287c1be004deca2f64ecc18a96bb6c3cd733cf') -backup=('etc/Nextcloud/sync-exclude.lst') +backup=('etc/Nextcloud/sync-exclude.lst' + 'etc/Nextcloud/Nextcloud.conf') prepare() { # tmpdir for check() @@ -97,4 +100,7 @@ package() { cd $pkgname/build make DESTDIR="$pkgdir" install + + # Disables built-in update checker + install -Dm644 "$srcdir/Nextcloud.conf" -t "$pkgdir"/etc/Nextcloud } -- 2.25.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From theova at bluewin.ch Wed Feb 19 21:31:16 2020 From: theova at bluewin.ch (theova) Date: Wed, 19 Feb 2020 22:31:16 +0100 Subject: [Dev] [PATCH] Update [libre/gnome-boxes] to 3.34.4 In-Reply-To: <20200203202304.slalxylokmqyygix@RainbowWarrior.localdomain> References: <20200203202304.slalxylokmqyygix@RainbowWarrior.localdomain> Message-ID: <20200219213116.trtsjeezigbo74hs@RainbowWarrior.localdomain> The patch below updates [libre/gnome-boxes] to 3.34.4 Chanelog: - Bump version number, git tag and checksum Built on all three architectures, successfully tested on x86_64. theova schrieb am Mon, 03. Feb 20 21:23: >The patch below updates [libre/gnome-boxes] to 3.34.3 >Chanelog: >- Bump version number, git tag and checksum > >Built on all three architectures, successfully tested on x86_64. >From 64796145f69374001debc948109ea9a619d06434 Mon Sep 17 00:00:00 2001 >From: Theo von Arx >Date: Thu, 30 Jan 2020 21:03:15 +0100 >Subject: [PATCH] libre/gnome-boxes update to 3.34.3 > >--- > libre/gnome-boxes/PKGBUILD | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > >diff --git a/libre/gnome-boxes/PKGBUILD b/libre/gnome-boxes/PKGBUILD >index 638585df8..a3da929b0 100644 >--- a/libre/gnome-boxes/PKGBUILD >+++ b/libre/gnome-boxes/PKGBUILD >@@ -10,7 +10,7 @@ > # - Replace Windows with Parabola in documention > > pkgname=gnome-boxes >-pkgver=3.34.2 >+pkgver=3.34.3 > pkgrel=2 > pkgrel+=.par1 > pkgdesc="Simple GNOME application to access remote or virtual systems" >@@ -25,7 +25,7 @@ groups=('gnome') > depends=('cdrtools' 'gtk-vnc' 'libarchive' 'libgudev' 'libosinfo' 'libsecret' > 'libvirt-glib' 'mtools' 'qemu' 'spice-gtk' 'tracker' 'webkit2gtk' 'freerdp') > makedepends=('git' 'gobject-introspection' 'yelp-tools' 'meson' 'spice-protocol' 'vala') >-_commit=2edb94153b163759d18195c511d6cf5212fd1bfe # tags/v3.34.2^0 >+_commit=c3bce5984eb53cc883850969f3e4a3e8e2cc6d44 # tags/v3.34.3^0 > source=("git+https://gitlab.gnome.org/GNOME/gnome-boxes.git#commit=$_commit" > "git+https://gitlab.gnome.org/GNOME/gtk-frdp.git" > "git+https://gitlab.gnome.org/felipeborges/libovf-glib.git") >@@ -33,7 +33,7 @@ source+=(hide_download_button.patch) > sha256sums=('SKIP' > 'SKIP' > 'SKIP') >-sha256sums+=('74f0d30e4ca280afe4c1f532ecc2856e8ee850a0e3d1812138536b4b9e7e2e7f') >+sha256sums+=('0539b344dc0bc8424539f747ed9c638ea414fe96153b803dae50bf5bf2d5aae5') > > pkgver() { > cd $pkgname >-- >2.25.0 > >_______________________________________________ >Dev mailing list >Dev at lists.parabola.nu >https://lists.parabola.nu/mailman/listinfo/dev -------------- next part -------------- From 89f118edaa39cc357d3113c7b2cae6f7bf085eb4 Mon Sep 17 00:00:00 2001 From: Theo von Arx Date: Wed, 19 Feb 2020 22:06:57 +0100 Subject: [PATCH 3/3] Update [libre/gnome-boxes] to 3.34.4 --- libre/gnome-boxes/PKGBUILD | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/libre/gnome-boxes/PKGBUILD b/libre/gnome-boxes/PKGBUILD index a3da929b0..8915b9fe2 100644 --- a/libre/gnome-boxes/PKGBUILD +++ b/libre/gnome-boxes/PKGBUILD @@ -10,8 +10,8 @@ # - Replace Windows with Parabola in documention pkgname=gnome-boxes -pkgver=3.34.3 -pkgrel=2 +pkgver=3.34.4 +pkgrel=1 pkgrel+=.par1 pkgdesc="Simple GNOME application to access remote or virtual systems" pkgdesc+=", without suggestions (and logos) of nonfree operating systems" @@ -25,7 +25,7 @@ groups=('gnome') depends=('cdrtools' 'gtk-vnc' 'libarchive' 'libgudev' 'libosinfo' 'libsecret' 'libvirt-glib' 'mtools' 'qemu' 'spice-gtk' 'tracker' 'webkit2gtk' 'freerdp') makedepends=('git' 'gobject-introspection' 'yelp-tools' 'meson' 'spice-protocol' 'vala') -_commit=c3bce5984eb53cc883850969f3e4a3e8e2cc6d44 # tags/v3.34.3^0 +_commit=e51a85c734cb6e4baaf1b77c4ad5d8fe032488f6 # tags/v3.34.4^0 source=("git+https://gitlab.gnome.org/GNOME/gnome-boxes.git#commit=$_commit" "git+https://gitlab.gnome.org/GNOME/gtk-frdp.git" "git+https://gitlab.gnome.org/felipeborges/libovf-glib.git") @@ -44,8 +44,8 @@ prepare() { cd $pkgname git submodule init - git config --local submodule.subprojects/gtk-frdp.url "$srcdir/gtk-frdp" - git config --local submodule.subprojects/libovf-glib.url "$srcdir/libovf-glib" + git submodule set-url subprojects/gtk-frdp "$srcdir/gtk-frdp" + git submodule set-url subprojects/libovf-glib "$srcdir/libovf-glib" git submodule update # remove recommended downloads of nonfree OS -- 2.25.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From GNUtoo at cyberdimension.org Sat Feb 22 22:13:22 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Sat, 22 Feb 2020 23:13:22 +0100 Subject: [Dev] Fixing the PKGBUILD licensing issue Message-ID: <20200222231322.4d51a948@primarylaptop.localdomain> Hi, As some of you may have noticed, Parabola has no license for the PKGBUILD. This issue probably comes from the arch GNU/Linux distribution that has the same issue. For example Gentoo, which uses something similar to the PKGBUILDs that are called ebuild have their ebuilds under the GPLv2 as per of the header that is included on top of each ebuild[1]. Guix use the GPLv3[2] for their package definition. The OpenWRT packages definitions are under the GPLv2[3]. The Yocto project uses a mix of GPLv2 and MIT[4] with the packages definition being MIT. The 19 December 2019, I was told in #archlinux that the package definitions were considered as copyrightable by some archlinux developers, but that nobody cared enough to fix the issue by choosing a license. I was also told that the only way to make things progress would be to have people starting to start add license to the PKGBUILDS they wrote. So I did just that and added the GPLv3 to the PKGBUILDs I wrote from scratch. I encourage other people to also choose a free software license for their PKGBUILDs and either add it as COPYING or mention in the PKGBUILD header. I'm also open to re-license the PKGBUILDs I wrote under any free software license when we start having a consensus on which license to choose, and/or even before that. References: ----------- [1]https://gitweb.gentoo.org/repo/gentoo.git/tree/header.txt [2]https://git.savannah.gnu.org/cgit/guix.git/tree/COPYING [3]https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=LICENSE;h=d60c31a97a544b53039088d14fe9114583c0efc3;hb=refs/tags/v19.07.1 [4]https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/LICENSE Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From grizzlyuser at protonmail.com Tue Feb 25 07:12:54 2020 From: grizzlyuser at protonmail.com (grizzlyuser) Date: Tue, 25 Feb 2020 07:12:54 +0000 Subject: [Dev] What about Zstandard instead of xz for package compression? Message-ID: I think pretty much everybody already knows about this, Arch Linux made a switch to Zstandard [1], but anyway. Are there any plans to do the same thing for Parabola? [1] https://www.archlinux.org/news/now-using-zstandard-instead-of-xz-for-package-compression/ From megver83 at hyperbola.info Wed Feb 26 16:30:33 2020 From: megver83 at hyperbola.info (Megver83) Date: Wed, 26 Feb 2020 13:30:33 -0300 Subject: [Dev] should libre/kio be, in fact, in [nonprism]? Message-ID: I wanted to build a [pcr] but it needed kio 5.67.0, and we've 5.66.0 in [libre], so I just started the build to update it. However, I noticed that the only problem with it are the non-privacy search engines, which is good to remove, but that doesn't qualify kio to be in [libre] but in [nonprism]. IMO, it's better to move it there to avoid breakages like the one I mentioned with the pkg I wanted to build, and afaik it doesn't not have major freedom issues (this is a privacy issue instead), but I wanted to discuss it here before doing anything, because idk if the person who put it in the your-freedom blacklist or someone else knows if there's other special reason for kio to be in [libre] rather than [nonprism] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part URL: