From nobody at parabola.nu  Wed Nov  1 15:52:05 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Wed, 01 Nov 2017 15:52:05 -0000
Subject: [Dev] Orphan Pcr package [gtk-theme-numix] marked out-of-date
Message-ID: <20171101155205.1246.90031@proton.parabola.nu>

parabola at remireuvekamp.nl wants to notify you that the following packages may be out-of-date:


* gtk-theme-numix 1.4-1 [pcr] (any): https://parabolagnulinux.org/packages/pcr/any/gtk-theme-numix/


The user provided the following additional text:

Numix is around version 2.6 at the moment.

The community repository also contains a version of Numix ( https://www.parabola.nu/packages/community/any/numix-gtk-theme/ ).

Thanks for maintaining this package!

 - remi



From nobody at parabola.nu  Thu Nov  2 01:15:55 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 02 Nov 2017 01:15:55 -0000
Subject: [Dev] Orphan Libre package [opencv] marked out-of-date
Message-ID: <20171102011555.1245.22539@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* opencv 3.3.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/opencv/
* opencv 3.3.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/opencv/


The user provided the following additional text:

Current release is 3.3.1



From fauno at endefensadelsl.org  Sat Nov  4 13:31:27 2017
From: fauno at endefensadelsl.org (fauno)
Date: Sat, 04 Nov 2017 10:31:27 -0300
Subject: [Dev] Use of donations for DNS / future of donations
In-Reply-To: <87vaivtgcb.wl-lukeshu@lukeshu.com>
References: <87vaivtgcb.wl-lukeshu@lukeshu.com>
Message-ID: <87po8yw4pc.fsf@endefensadelsl.org>

Luke Shumaker <lukeshu at lukeshu.com> writes:

> On Mon, 30 Oct 2017 10:26:59 -0400,
> fauno wrote:
>> i've asked tct if we can renew the [parabolagnulinux.org] domain for
>> many years with the parabola funds and he said it's ok.  is anyone
>> against?  i'll wait a few days.

i'll go ahead then :)

-- 
:O
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 617 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171104/64a9bc0e/attachment.sig>

From aurelien at hackers.camp  Sun Nov  5 15:37:05 2017
From: aurelien at hackers.camp (aurelien)
Date: Sun, 05 Nov 2017 16:37:05 +0100
Subject: [Dev] Use of donations for DNS / future of donations
In-Reply-To: <87po8yw4pc.fsf@endefensadelsl.org> (fauno@endefensadelsl.org's
 message of "Sat, 04 Nov 2017 10:31:27 -0300")
References: <87vaivtgcb.wl-lukeshu@lukeshu.com>
 <87po8yw4pc.fsf@endefensadelsl.org>
Message-ID: <87vaio7n4u.fsf@hackers.camp>

fauno <fauno at endefensadelsl.org> writes:

> Luke Shumaker <lukeshu at lukeshu.com> writes:
>
>> On Mon, 30 Oct 2017 10:26:59 -0400,
>> fauno wrote:
>>> i've asked tct if we can renew the [parabolagnulinux.org] domain for
>>> many years with the parabola funds and he said it's ok.  is anyone
>>> against?  i'll wait a few days.
>
> i'll go ahead then :)

:-)

--
Aurelien DESBRIERES


From megver83 at hyperbola.info  Mon Nov  6 17:02:46 2017
From: megver83 at hyperbola.info (Megver83)
Date: Mon, 6 Nov 2017 14:02:46 -0300
Subject: [Dev] Buildbot
Message-ID: <99c50328-2ae2-7fff-74c6-89ebc75614a7@hyperbola.info>

As we will have a build server soon, thanks to lukeshu for that, I was
thinking on what features should the autobuilder have. I read about
Buildbot which seems very interesting

https://buildbot.net/

I think that our autobuilder should compile when we specify it on the
commit. E.g. when the commit begins like "updpkg: <repo>/<pkgbase>
<version>" then compile it in the background, because if for any reason
the packager disconnects from the SSH then the compilation would stop,
but not if is in the background. That's one of the features I'm thinking
about RN.
-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171106/28c38da9/attachment.sig>

From andreas at grapentin.org  Mon Nov  6 17:11:48 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Mon, 6 Nov 2017 18:11:48 +0100
Subject: [Dev] Buildbot
In-Reply-To: <99c50328-2ae2-7fff-74c6-89ebc75614a7@hyperbola.info>
References: <99c50328-2ae2-7fff-74c6-89ebc75614a7@hyperbola.info>
Message-ID: <20171106171148.GA19654@parabola-pocket.localdomain>


as for batch processing of jobs, we should probably take a look at
pcr/task-spooler. it's great and I've been using it for queueing builds
on my crunching box for a while.

by the way, I would personally discourage using text parsing on git
commits for triggering builds. it's prone to mistakes, and doesn't
follow the principle of least astonishment [1]. Would probably be better
to get a cli tool on the server to do it, or, if people prefer that, a
website or something.

Come to think of it, what might work would be having a git hook that
activates upon a pushed commit, scanning for updated pkgbuild files, and
rebuilding them, if a certain flag is set or something. But we'd better
document the hell out of this or it will come back and bite us in the
ass.

 [1] - https://en.wikipedia.org/wiki/Principle_of_least_astonishment



On Mon, Nov 06, 2017 at 02:02:46PM -0300, Megver83 wrote:
> As we will have a build server soon, thanks to lukeshu for that, I was
> thinking on what features should the autobuilder have. I read about
> Buildbot which seems very interesting
> 
> https://buildbot.net/
> 
> I think that our autobuilder should compile when we specify it on the
> commit. E.g. when the commit begins like "updpkg: <repo>/<pkgbase>
> <version>" then compile it in the background, because if for any reason
> the packager disconnects from the SSH then the compilation would stop,
> but not if is in the background. That's one of the features I'm thinking
> about RN.
> -- 
> ~Megver83
> 
> SIP: megver83 at sip.linphone.org
> XMPP: megver83 at jabjab.de
> Tox: megver83 at toxme.io
> GPG: 0x227CA7C556B2BA78
> GNUSocial: @megver82 at quitter.cl
> Diaspora*: megver83 at diasp.org
> Matrix: @Megver83:matrix.org
> 




> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171106/433bcff1/attachment.sig>

From megver83 at hyperbola.info  Mon Nov  6 17:19:31 2017
From: megver83 at hyperbola.info (Megver83)
Date: Mon, 6 Nov 2017 14:19:31 -0300
Subject: [Dev] Buildbot
In-Reply-To: <20171106171148.GA19654@parabola-pocket.localdomain>
References: <99c50328-2ae2-7fff-74c6-89ebc75614a7@hyperbola.info>
 <20171106171148.GA19654@parabola-pocket.localdomain>
Message-ID: <e721a002-78d7-82c7-e745-10fbcc6b43a9@hyperbola.info>

El 06/11/17 a las 14:11, Andreas Grapentin escribi?:
> 
> as for batch processing of jobs, we should probably take a look at
> pcr/task-spooler. it's great and I've been using it for queueing builds
> on my crunching box for a while.
> 
> by the way, I would personally discourage using text parsing on git
> commits for triggering builds. it's prone to mistakes, and doesn't
> follow the principle of least astonishment [1]. Would probably be better
> to get a cli tool on the server to do it, or, if people prefer that, a
> website or something.
> 
> Come to think of it, what might work would be having a git hook that
> activates upon a pushed commit, scanning for updated pkgbuild files, and
> rebuilding them, if a certain flag is set or something. But we'd better
> document the hell out of this or it will come back and bite us in the
> ass.
> 
>  [1] - https://en.wikipedia.org/wiki/Principle_of_least_astonishment
> 
> 
> 
> On Mon, Nov 06, 2017 at 02:02:46PM -0300, Megver83 wrote:
>> As we will have a build server soon, thanks to lukeshu for that, I was
>> thinking on what features should the autobuilder have. I read about
>> Buildbot which seems very interesting
>>
>> https://buildbot.net/
>>
>> I think that our autobuilder should compile when we specify it on the
>> commit. E.g. when the commit begins like "updpkg: <repo>/<pkgbase>
>> <version>" then compile it in the background, because if for any reason
>> the packager disconnects from the SSH then the compilation would stop,
>> but not if is in the background. That's one of the features I'm thinking
>> about RN.
>> -- 
>> ~Megver83
>>
>> SIP: megver83 at sip.linphone.org
>> XMPP: megver83 at jabjab.de
>> Tox: megver83 at toxme.io
>> GPG: 0x227CA7C556B2BA78
>> GNUSocial: @megver82 at quitter.cl
>> Diaspora*: megver83 at diasp.org
>> Matrix: @Megver83:matrix.org
>>
> 
> 
> 
> 
>> _______________________________________________
>> 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
> 
or it could maybe detect the changes in a .SRCINFO file like AUR does?

-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171106/27750ca8/attachment.sig>

From lukeshu at lukeshu.com  Tue Nov  7 01:19:01 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Mon, 06 Nov 2017 20:19:01 -0500
Subject: [Dev] Build server Xen vs KVM
Message-ID: <87wp32zy0q.wl-lukeshu@lukeshu.com>

Hi all,

In the original email, I had said that I planned on using Xen on the
build server.  I suppose I should ask though: Does anyone have a
strong opinion on KVM vs Xen?

(Just waiting on the the mobo now.  Also, my RAM seller had
mis-counted his inventory, and so I'm only getting 16GB in this
order).

-- 
Happy hacking,
~ Luke Shumaker


From lovell.joshyyy at gmail.com  Tue Nov  7 01:21:28 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Tue, 7 Nov 2017 01:21:28 +0000
Subject: [Dev] Build server Xen vs KVM
In-Reply-To: <87wp32zy0q.wl-lukeshu@lukeshu.com>
References: <87wp32zy0q.wl-lukeshu@lukeshu.com>
Message-ID: <5A010A98.3040701@gmail.com>

On 07/11/17 01:19, Luke Shumaker wrote:
> Hi all,
>
> In the original email, I had said that I planned on using Xen on the
> build server.  I suppose I should ask though: Does anyone have a
> strong opinion on KVM vs Xen?
>
> (Just waiting on the the mobo now.  Also, my RAM seller had
> mis-counted his inventory, and so I'm only getting 16GB in this
> order).
>

KVM, built into kernel. Last time I checked Xen required lots of 
dependencies.

Other question to consider is the overhead added as it's a build server, 
but if it's para-visualization shouldn't be so much of a problem.

Josh


From lukeshu at lukeshu.com  Tue Nov  7 02:05:42 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Mon, 06 Nov 2017 21:05:42 -0500
Subject: [Dev] Install media releng / I made some changes
Message-ID: <87tvy6zvux.wl-lukeshu@lukeshu.com>

Hi all,

(I apologize, there isn't much structure to this email)

I wanted to create a thread to discuss release engineering on our
install media.  What the processes are when creating those releases,
how we test them, and what changes we want to make.

In my view, there are 3 install classes of install images:
 - x86 ISOs
 - iPXE images (we don't currently make these, and it is blocking and
   update of ParabolaWeb)
 - ARM images (we don't currently make these, and we totally should)

Changes I've made
 - I've re-added the 'latest' symlink in the '/iso/' folder on repo.
 - I've merge the '/iso-previous/' folder on repo back in to '/iso/'.
   There's no need to split them off.
Changes I'm doing
 - Adjusting repoindex and parabolaweb so that parabolaweb's
   `syncisos` command works (and add that to the crontab), so that our
   releases show up at https://www.parabola.nu/releng/releases/ and
   https://www.parabola.nu/releng/releases/

Things I'm concerned about:
 - Do we put the sourceballs on the install CD?  If not, do we ensure
   that sourceballs for old packages don't get cleaned up if that
   package is on a CD we still publish?
 - `archboot` is a testing replacement for `archiso`.  Do we have any
   plans to ditch `parabolaiso` for a `parabolaboot`?
 - I think it would be really cool if any files not owned by a package
   or modified from the vanilla version on the install media were
   managed by [holo][].
 - Bill Auger tells me that parabolaiso requires root.  I'd like to
   understand why.  Can we use unprivileged user/mount namespaces to
   avoid this on the build server?
 - I think the release process should be more documented, and more
   automated (FOSS automation scripts are the best form of process
   documentation :P)

[holo]: http://holocm.org/

That said, install media creation is the part of Parabola that I am
most removed from and ignorant to.

-- 
Happy hacking,
~ Luke Shumaker


From lukeshu at lukeshu.com  Tue Nov  7 02:35:51 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Mon, 06 Nov 2017 21:35:51 -0500
Subject: [Dev] Build server Xen vs KVM
In-Reply-To: <5A010A98.3040701@gmail.com>
References: <87wp32zy0q.wl-lukeshu@lukeshu.com>
	<5A010A98.3040701@gmail.com>
Message-ID: <87shdqzugo.wl-lukeshu@lukeshu.com>

On Mon, 06 Nov 2017 20:21:28 -0500,
Josh Branning wrote:
> On 07/11/17 01:19, Luke Shumaker wrote:
> > Hi all,
> > 
> > In the original email, I had said that I planned on using Xen on the
> > build server.  I suppose I should ask though: Does anyone have a
> > strong opinion on KVM vs Xen?
> > 
> > (Just waiting on the the mobo now.  Also, my RAM seller had
> > mis-counted his inventory, and so I'm only getting 16GB in this
> > order).
> > 
> 
> KVM, built into kernel. Last time I checked Xen required lots of
> dependencies.

KVM is a mechanism built into the kernel, but you still need external
(userspace) programs to do everything but CPU virtualization; which
probably means QEMU.

The dependency lists of QEMU and Xen aren't that different.

(NB: much Xen's para-virtualized device code comes from QEMU)

> Other question to consider is the overhead added as it's a build
> server, but if it's para-visualization shouldn't be so much of a
> problem.

Both KVM and Xen will be using HVM for CPU virtualization these days
(well, KVM always used HVM; Xen used to use para-virtualization for
CPU though); the real overhead will be with devices.

Both KVM/QEMU and Xen should be using virtio (para-virtualization) for
most devices.  I don't know what KVM/QEMU's para-virtualized devices
story is like these days.

One thing to note, while KVM can hot-plug add more CPUs, Xen has
support for hot-plugging and unplugging them.  I said that 16 of the
CPU cores would be dedicated to the build server VM, but Xen would
give the possiblity to rig up a system to allow "ballooning" the
number of cores up to 31 (I'd keep one reserved for dom0) if other VMs
are inactive.

-- 
Happy hacking,
~ Luke Shumaker


From fauno at endefensadelsl.org  Tue Nov  7 11:01:48 2017
From: fauno at endefensadelsl.org (fauno)
Date: Tue, 07 Nov 2017 08:01:48 -0300
Subject: [Dev] Build server Xen vs KVM
In-Reply-To: <87wp32zy0q.wl-lukeshu@lukeshu.com>
References: <87wp32zy0q.wl-lukeshu@lukeshu.com>
Message-ID: <8760amwdwj.fsf@endefensadelsl.org>

Luke Shumaker <lukeshu at lukeshu.com> writes:

> Hi all,
>
> In the original email, I had said that I planned on using Xen on the
> build server.  I suppose I should ask though: Does anyone have a
> strong opinion on KVM vs Xen?
>
> (Just waiting on the the mobo now.  Also, my RAM seller had
> mis-counted his inventory, and so I'm only getting 16GB in this
> order).

i just built a kvm host using parabola, the vms are qemu + systemd
services.  it's a simple setup really

just ask me anything :)

-- 
:O
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 617 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/ee5ba309/attachment.sig>

From fauno at endefensadelsl.org  Tue Nov  7 11:10:02 2017
From: fauno at endefensadelsl.org (fauno)
Date: Tue, 07 Nov 2017 08:10:02 -0300
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <87tvy6zvux.wl-lukeshu@lukeshu.com>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
Message-ID: <87375qwdit.fsf@endefensadelsl.org>

Luke Shumaker <lukeshu at lukeshu.com> writes:

> Hi all,
>
> (I apologize, there isn't much structure to this email)
>
> I wanted to create a thread to discuss release engineering on our
> install media.  What the processes are when creating those releases,
> how we test them, and what changes we want to make.
>
> In my view, there are 3 install classes of install images:
>  - x86 ISOs
>  - iPXE images (we don't currently make these, and it is blocking and
>    update of ParabolaWeb)

i was just asking about pxe support on our images, because i needed to
install a parabola system and had to use an arch iso which has it
built-in while ours doesn't.  it's supposed to be on archiso and added
automatically.  bill told me i should test the new isos to see if there
was support for it, but it was too late :)

>  - ARM images (we don't currently make these, and we totally should)
>
> Changes I've made
>  - I've re-added the 'latest' symlink in the '/iso/' folder on repo.
>  - I've merge the '/iso-previous/' folder on repo back in to '/iso/'.
>    There's no need to split them off.
> Changes I'm doing
>  - Adjusting repoindex and parabolaweb so that parabolaweb's
>    `syncisos` command works (and add that to the crontab), so that our
>    releases show up at https://www.parabola.nu/releng/releases/ and
>    https://www.parabola.nu/releng/releases/

great!

> Things I'm concerned about:
>  - Do we put the sourceballs on the install CD?  If not, do we ensure
>    that sourceballs for old packages don't get cleaned up if that
>    package is on a CD we still publish?
>  - `archboot` is a testing replacement for `archiso`.  Do we have any
>    plans to ditch `parabolaiso` for a `parabolaboot`?

i'm not really sure parabolaiso is still following archiso's
development? (see above about pxe) from what i gather of bill and
megver's email there's at least two forks in play??

>  - I think it would be really cool if any files not owned by a package
>    or modified from the vanilla version on the install media were
>    managed by [holo][].

what i always wondered about shipping conf files as pacman packages is
how will they be treated since they belong to another package.  for
instance if you ship pacman.conf and then install the holo package,
won't you get it as pacman.conf.pacnew?

>  - Bill Auger tells me that parabolaiso requires root.  I'd like to
>    understand why.  Can we use unprivileged user/mount namespaces to
>    avoid this on the build server?
>  - I think the release process should be more documented, and more
>    automated (FOSS automation scripts are the best form of process
>    documentation :P)

+1 a few years ago we even talked of a community repository for parabola
isos :P

> [holo]: http://holocm.org/
>
> That said, install media creation is the part of Parabola that I am
> most removed from and ignorant to.
>
> -- 
> Happy hacking,
> ~ Luke Shumaker
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev

-- 
 D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 617 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/075ec87d/attachment.sig>

From bill-auger at peers.community  Tue Nov  7 14:31:28 2017
From: bill-auger at peers.community (bill-auger)
Date: Tue, 7 Nov 2017 09:31:28 -0500
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <87tvy6zvux.wl-lukeshu@lukeshu.com>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
Message-ID: <da320cd0-79a8-723b-289a-00c73674d9f4@peers.community>



On 11/06/2017 09:05 PM, Luke Shumaker wrote:
> What the processes are when creating those releases,
> how we test them, and what changes we want to make.
> 

the build process is rather simple now - just clone the parabolaiso repo
and run the build script - the build script has many options to decide
which type of ISO is made - i took care to update the docs and explain
as much as could about the process[1]

"testing" them is entirely manual with eyeballs and mouse-clicks but
automated acceptance testing would be a very nice addition to the
work-flow especially if the ISOs were also built in the server - the
opensuse build service has that feature which would be fun to investigate

as for changes, i have made several already - parabolaiso can now build
separate ISOs for i686 and x86 along with the dual-arch kind
it can also build ISO that can install offline - rather than having
seperate trees for each edition, there is now a single build script can
build any combination of target archs, init system, and WM/DE - i am
working now at extracting the user skeleton and artwork out of the
parabolaiso repo and into a distinct package that can be used also by
the calamares installer - the ISO also boots automatically now whcih it
did not before - not a huge gain for the CLI and GUI ISOs but as for the
Talking ISO intended for blind people, that seems like something that
should never have been over-looked


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
> In my view, there are 3 install classes of install images:
>  - x86 ISOs
>  - iPXE images (we don't currently make these, and it is blocking and
>    update of ParabolaWeb)
>  - ARM images (we don't currently make these, and we totally should)
> 

according to the docs "All ISOs are ready to act as PXE server"[2] - i
have not verified this though - in the past i have used the arch-netboot
iPXE kernel that makes PXE boot possible even for those without PXE
hardware support - i assume that could easily be adapted for parabola -
there is a package in the AUR that builds iPXE compatible images[3][4]
for that use-case

i agree that an ARM installer is a good idea - ARM devices are only
going to get more popular - many come with some OS pre-installed
(typically berry-flavored) but today it is generally non-trivial to
replace it safely


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
> Changes I've made
>  - I've re-added the 'latest' symlink in the '/iso/' folder on repo.
>  - I've merge the '/iso-previous/' folder on repo back in to '/iso/'.
>    There's no need to split them off.

the 'latest' symlinks are for the benefit of mirrors is assume? they not
very useful for user downloads though because the actual files are dated
like: 'parabola-2017.05.28-dual.iso' - i started writing a PHP script to
redirect web browsers based on the dates in the directory names - but it
is not clear if keeping old releases around is at all valuable - as i
remember the 'iso-previous' dir was not there before about a month ago -
they never had links on the web - i think i added that as a stash only
in case i needed to revert a release during development of the new set -
i assumed all along that there should be only the latest release
published at any one time because there were no old releases there at
the time and it seems reasonable not to keep them taking up space on the
mirrors

in the future there will be a minimum of 18 ISOs (total ~21GB) available
on the downloads page at any one time - if these are rebuilt regularly
(say every 6 months or so) they will soon be requiring an absurd amount
of disk space or mirrors for somethings that quite likely no one will
ever want - as i said 18 is the current minimum - the build matrix
supports as many as 12 ISOs for each release variant - there are
currently 3 such variants (CLI, LXDE, and talking) and i think 6 of each
is enough - each new variant (KDE for example) would add 6 more  - im
not saying the old ones must be destroyed but i do think at least they
should be stored in a separate location that will not be sync'ed by
mirrors - perhaps a separate archive mirror but in that case i will add
that it would be far more useful to keep an archive of previous packages
which parabola also does not do currently

for the curious, the maximal build matrix looks like this:

  CLI             OpenRC          i686              net-install
  LXDE       x               x    x86_64       x
  Talking         SystemD         dual-arch         complete


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
>  - Do we put the sourceballs on the install CD?  If not, do we ensure
>    that sourceballs for old packages don't get cleaned up if that
>    package is on a CD we still publish?

im not quite sure what this is asking but there is no source code on the
ISOs - the 'complete' editions for offline install include a full cache
of binary packages though - if you are thinking to release periodic
source snapshots that is a good idea but i suggest that be a separate
ISO in order to keep the size down - the 'dual-complete' ISOs are
already 3.5 GB


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
>  - `archboot` is a testing replacement for `archiso`.  Do we have any
>    plans to ditch `parabolaiso` for a `parabolaboot`?

i though about this quite a lot while adding the new features to
parabolaiso - as i see it now that there is probably less benefit to
taking anything from arch than it is worth (even merging the latest
archiso will be tedious at best) - especially if the upstream is
dropping i686 support there could be more lost than gained - another
tool that looks interesting is 'manjaro-tools' which has native support
for exporting calamares build configs - unfortunately it is not licensed
properly and they have ignored my requests[5][6] so i went forward with
upgrading the capabilities of parabolaiso - as it is now, it works well,
it is easy to use, it does everything we need it to do, and it is KISS
and easy to understand (only about 1000 LOC) and easy adapt to future
use-cases (such as ARM builds) so i dont see any reason to replace it


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
>  - I think it would be really cool if any files not owned by a package
>    or modified from the vanilla version on the install media were
>    managed by [holo][].

as i said earlier i have extracted most such files into a dedicated
'parabola-laf' package - probably the only ones left are the CLI install
scripts which could go in the 'parabolaiso-data' package which the
builds already require - the only thing in that package now are two
blobs downloaded from sourceforge for EFI boot (yes it downloads only
the pre-built blobs - no sources) so really everything in the new
'parabola-laf' package could go in that but for semantics


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
>  - Bill Auger tells me that parabolaiso requires root.  I'd like to
>    understand why.  Can we use unprivileged user/mount namespaces to
>    avoid this on the build server?

i have not tried to work around this but the superficial reasons are
that it operates much like pacstrap - it needs to mount the special
files like /dev /sys /proc onto the chroot and install packages - also
there are obviously many critical files that it writes which inevitably
need to be owned by 0:0 such as /etc/init yes?


On 11/06/2017 09:05 PM, Luke Shumaker wrote:
>  - I think the release process should be more documented, and more
>    automated (FOSS automation scripts are the best form of process
>    documentation :P)

having a build server will open up many possibilities - i have not done
so formally yet but i would like to discuss using the opensuse build
service to build the entire parabola system - i mean ALL packages - take
nothing from arch but PKGBUILDS - OBS manages the entire system and has
nice features such as triggering a cascade of rebuilds automatically
when a lower level dependency is rebuilt - for example: trigger a
rebuild of 'libfoo' and any package that depends on it is automatically
rebuilt and then on and on to any dependents farther on until the entire
system is sane again - never again would a user run a program that
worked yesterday but today cannot find it's dependency simply because
the dependency version was upgraded

as for the ISOs being built on a server - it is much as i described
already - the process is very simple now - it is literally a single
command line - again to note on the other hand that OBS has another
attractive feature that can automatically build ISOs, boot them, and run
a GUI-enabled test suite



[1]:
https://notabug.org/bill-auger/parabolaiso/src/refactor/docs/README.build
[2]:
https://notabug.org/bill-auger/parabolaiso/src/refactor/docs/README.altbootmethods#L85
[3]: https://aur.archlinux.org/packages/ipxe-netboot
[4]: https://www.archlinux.org/releng/netboot/
[5]: https://github.com/manjaro/manjaro-tools/pull/273
[6]: https://github.com/manjaro/iso-profiles/pull/75

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/4fb90b4e/attachment.sig>

From bill-auger at peers.community  Tue Nov  7 14:58:21 2017
From: bill-auger at peers.community (bill-auger)
Date: Tue, 7 Nov 2017 09:58:21 -0500
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <87375qwdit.fsf@endefensadelsl.org>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <87375qwdit.fsf@endefensadelsl.org>
Message-ID: <e2220dcc-2796-97a4-7cad-da17e8989e1a@peers.community>



On 11/07/2017 06:10 AM, fauno wrote:
> i'm not really sure parabolaiso is still following archiso's
> development? (see above about pxe) from what i gather of bill and
> megver's email there's at least two forks in play??


parabolaiso has not intentionally gone in it's own direction but i would
not say "following" would apply either, simply because it has not been
updated since 2013 - the only forking has been in the last month between
myself and megver - his branch is still in the main line with the
archiso->parabolaiso lineage and is the current HEAD of the
git.parabola.nu repo - the changes i have been making that i described
in the previous message are more internal but still would not prevent
merging with upstream as i have tried hard to keep it backward
compatible - i will be merging with megver's openrc changes soon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/a7d44f51/attachment.sig>

From lukeshu at lukeshu.com  Tue Nov  7 17:58:32 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Tue, 07 Nov 2017 12:58:32 -0500
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <87375qwdit.fsf@endefensadelsl.org>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <87375qwdit.fsf@endefensadelsl.org>
Message-ID: <8760amynqv.wl-lukeshu@lukeshu.com>

On Tue, 07 Nov 2017 06:10:02 -0500,
fauno wrote:
> >  - I think it would be really cool if any files not owned by a package
> >    or modified from the vanilla version on the install media were
> >    managed by [holo][].
> 
> what i always wondered about shipping conf files as pacman packages is
> how will they be treated since they belong to another package.  for
> instance if you ship pacman.conf and then install the holo package,
> won't you get it as pacman.conf.pacnew?

I've never liked how the Holo docs explain this (translation: I've
been meaning to file a PR against the Holo docs.  So let's have a stab
at it!).

Let's draw a distinction between big-picture the "Holo" system
(capitol-H), and the specific "holo" package/program (lowercase-h).

Holo is a configuration management system that isn't.  Conf files are
just files owned by package-manager packages.  This works out
splendidly when the default .conf file does something like "include
/etc/pkgname.d/*.conf" and Holo configuration packages ("holograms")
can just drop new files in "pkgname.d".  Nowhere in that description
did we describe a new piece of software to call Holo, we just
described normal operating system packages!  You can successfully use
Holo without using holo.

But there is of course the problem that sometimes a hologram needs to
edit a file that is owned by another package; for example
/etc/collectd.conf can't be owned by both "collectd" and by
"hologram-my-collectd-config".  This is where the "holo"
package/program comes in.  "holo" hooks in to the package manager's
hooks system (yay pacman 5), to be able to patch files as they are
installed by the package manager.

So, to take the collectd.conf example,
"hologram-my-collectd-config" is a normal package that depends
on "collectd" (whose config files it will be editing), and "holo"
(since it will be needing to edit files owned by another package), and
providing a file under /usr/share/holo/ that will specify how
collectd.conf is to be modified.

 - Installing/updating the hologram: "hologram-my-collectd-config"
   will have post_install, post_update, and post_remove scripts that
   all call `holo apply etc/collectd.conf`, which will use the file
   under /usr/share/holo/ to modify collectd.conf.

 - Updating the base package: When collectd updates their default
   configuration file, pacman will try to install it, but see that
   /etc/collectd.conf was modified (by holo), and install it as
   collectd.conf.pacnew; but then it will run
   /usr/share/libalpm/hooks/01-holo-resolve-pacnew.hook, which will
   end up calling `holo apply etc/collectd.conf` which will use the
   file under /usr/share/holo/ to modify the .pacnew file (just as it
   did the original collectd.conf), and install that as the new
   collectd.conf.

As long as nothing else modifies the file other than "holo" (`holo
apply` keeps track of how it left the file, and can detect if it has
been changed), it should always be able to merge the .pacnew file
without conflict.

-- 
Happy hacking,
~ Luke Shumaker


From bill-auger at peers.community  Tue Nov  7 19:17:57 2017
From: bill-auger at peers.community (bill-auger)
Date: Tue, 7 Nov 2017 14:17:57 -0500
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <8760amynqv.wl-lukeshu@lukeshu.com>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <87375qwdit.fsf@endefensadelsl.org> <8760amynqv.wl-lukeshu@lukeshu.com>
Message-ID: <9103a82f-7fee-6013-365b-799d464f5ca8@peers.community>

that halo tool seems very nifty - the actual configuration is minimal
and the modifications are trivial though - a configuration management
tool would be "managing" very little

these are all of the modifications to existing files owned by other
packages:

for all ISOs:
* 4 languages are un-commented in /etc/locale.gen
* the edition title is injected into /etc/motd

for the 'complete' ISOs only:
* the definition of the local on-disk package repo is added to
/etc/pacman.conf

of those, the edition title is the only dynamic value - it contains the
build date matching the output filename - even that is fully
deterministic it needs not be a date - it is actually the version string
that is printed verbatim as passed into the build script on the command
line - the others are static values will apply with the current values
to ISOs present and future (unless a new locale is added) - but the live
environment does not use a DM so im not even sure if the locales are
applicable to anything but the CLI install script (which is being phased
out)

there are a small number of files in the 'root-image' overlay that are
copied directly to the live environment filesystem (so not owned by any
package that is installed in the live environment) - i would eventually
like to put these all in the 'parabolaiso-data' package which could be
installed in the live environment and the 'root-image' overlay feature
could be removed or at least unused - that is the original intended way
to customize the install with anything specific to the live environment
that did not belong in any standard package (e.g. service files,
password-less sudoers file, ssh root login)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/d8aa9e65/attachment.sig>

From nobody at parabola.nu  Tue Nov  7 19:53:11 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 07 Nov 2017 19:53:11 -0000
Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date
Message-ID: <20171107195311.1244.87811@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* kinfocenter 5.11.2-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kinfocenter/
* kinfocenter 5.11.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kinfocenter/


The user provided the following additional text:

Current release is 5.11.3



From jc_gargma at iserlohn-fortress.net  Tue Nov  7 19:56:08 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 07 Nov 2017 11:56:08 -0800
Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date
In-Reply-To: <20171107195311.1244.87811@proton.parabola.nu>
References: <20171107195311.1244.87811@proton.parabola.nu>
Message-ID: <12379624.GDE53Fjarx@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update kinfocenter and khotkeys to 5.11.3


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-kinfocenter-and-khotkeys-to-5.11.3.patch
Type: text/x-patch
Size: 2011 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/ddf1a2c3/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/ddf1a2c3/attachment.sig>

From nobody at parabola.nu  Tue Nov  7 20:23:39 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 07 Nov 2017 20:23:39 -0000
Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date
Message-ID: <20171107202339.1244.14910@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* icecat-noscript 5.1.3-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-noscript/


The user provided the following additional text:

Current release is 5.1.5



From megver83 at hyperbola.info  Tue Nov  7 20:28:17 2017
From: megver83 at hyperbola.info (Megver83)
Date: Tue, 7 Nov 2017 17:28:17 -0300
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <9103a82f-7fee-6013-365b-799d464f5ca8@peers.community>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <87375qwdit.fsf@endefensadelsl.org> <8760amynqv.wl-lukeshu@lukeshu.com>
 <9103a82f-7fee-6013-365b-799d464f5ca8@peers.community>
Message-ID: <176d6263-1e6a-e8dc-3f48-8d1a35e8f1ab@hyperbola.info>

El 07/11/17 a las 16:17, bill-auger escribi?:
> that halo tool seems very nifty - the actual configuration is minimal
> and the modifications are trivial though - a configuration management
> tool would be "managing" very little
> 
> these are all of the modifications to existing files owned by other
> packages:
> 
> for all ISOs:
> * 4 languages are un-commented in /etc/locale.gen
> * the edition title is injected into /etc/motd

LXDE OpenRC have 8 languages uncommented, fyi

> 
> for the 'complete' ISOs only:
> * the definition of the local on-disk package repo is added to
> /etc/pacman.conf
> 
> of those, the edition title is the only dynamic value - it contains the
> build date matching the output filename - even that is fully
> deterministic it needs not be a date - it is actually the version string
> that is printed verbatim as passed into the build script on the command
> line - the others are static values will apply with the current values
> to ISOs present and future (unless a new locale is added) - but the live
> environment does not use a DM so im not even sure if the locales are
> applicable to anything but the CLI install script (which is being phased
> out)
> 
> there are a small number of files in the 'root-image' overlay that are
> copied directly to the live environment filesystem (so not owned by any
> package that is installed in the live environment) - i would eventually
> like to put these all in the 'parabolaiso-data' package which could be
> installed in the live environment and the 'root-image' overlay feature
> could be removed or at least unused - that is the original intended way
> to customize the install with anything specific to the live environment
> that did not belong in any standard package (e.g. service files,
> password-less sudoers file, ssh root login)
> 
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 


-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/2ced3cc6/attachment.sig>

From jc_gargma at iserlohn-fortress.net  Tue Nov  7 20:28:52 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 07 Nov 2017 12:28:52 -0800
Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date
In-Reply-To: <20171107202339.1244.14910@proton.parabola.nu>
References: <20171107202339.1244.14910@proton.parabola.nu>
Message-ID: <1999350.BMcCnhMmJ0@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update icecat/iceweasel-noscript to 5.1.5


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-icecat-iceweasel-noscript-to-5.1.5.patch
Type: text/x-patch
Size: 1749 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/c6b150d0/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171107/c6b150d0/attachment.sig>

From isacdaavid at isacdaavid.info  Wed Nov  8 05:00:30 2017
From: isacdaavid at isacdaavid.info (Isaac David)
Date: Tue, 07 Nov 2017 23:00:30 -0600
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <da320cd0-79a8-723b-289a-00c73674d9f4@peers.community>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <da320cd0-79a8-723b-289a-00c73674d9f4@peers.community>
Message-ID: <1510117230.1748.0@plebeian.isacdaavid.info>

bill-auger wrote :
> Luke Shumaker wrote:
>> In my view, there are 3 install classes of install images:
>>  [...]
>>  - ARM images (we don't currently make these, and we totally should)
> 
> i agree that an ARM installer is a good idea - ARM devices are only
> going to get more popular - many come with some OS pre-installed
> (typically berry-flavored) but today it is generally non-trivial to
> replace it safely

absolutely, this has been a huge omission from our part.

i would be interested to know how this would play out...

- whether there's a point in mastering an ISO image or just making a
  tarball of the filesystem.
- what packages to include. install ISO-like environment? just the
  base group?  booloaders?.
- whether we want to blow up that release matrix by a factor of the
  number of devices.
- finally, what the interplay between ARM releases and x86 releases
  would be.

there's at least one unofficial image out there[1]. not to mention
that some EOMA68 cards will come out with Parabola -- sooner or later
-- which reminds me of the need to package LKCL's version of uboot for
it.

[1]: https://wiki.parabola.nu/ARM_Installation_Guide#BeagleBone_Black_2

-- 
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
<https://isacdaavid.info/donate>



From lovell.joshyyy at gmail.com  Wed Nov  8 10:49:52 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 8 Nov 2017 10:49:52 +0000
Subject: [Dev] Install media releng / I made some changes
In-Reply-To: <1510117230.1748.0@plebeian.isacdaavid.info>
References: <87tvy6zvux.wl-lukeshu@lukeshu.com>
 <da320cd0-79a8-723b-289a-00c73674d9f4@peers.community>
 <1510117230.1748.0@plebeian.isacdaavid.info>
Message-ID: <5A02E150.4040202@gmail.com>

On 08/11/17 05:00, Isaac David wrote:
> bill-auger wrote :
>> Luke Shumaker wrote:
>>> In my view, there are 3 install classes of install images:
>>>  [...]
>>>  - ARM images (we don't currently make these, and we totally should)
>>
>> i agree that an ARM installer is a good idea - ARM devices are only
>> going to get more popular - many come with some OS pre-installed
>> (typically berry-flavored) but today it is generally non-trivial to
>> replace it safely
>
> absolutely, this has been a huge omission from our part.
>
> i would be interested to know how this would play out...
>
> - whether there's a point in mastering an ISO image or just making a
>   tarball of the filesystem.
> - what packages to include. install ISO-like environment? just the
>   base group?  booloaders?.
> - whether we want to blow up that release matrix by a factor of the
>   number of devices.
> - finally, what the interplay between ARM releases and x86 releases
>   would be.

I suggest releasing a rootfs tarball and let people dd bootloader 
separately. Makes sense, and seems to be the way for Arch Linux ARM.

https://archlinuxarm.org/platforms/armv7/allwinner/a10-olinuxino-lime#installation

>
> there's at least one unofficial image out there[1]. not to mention
> that some EOMA68 cards will come out with Parabola -- sooner or later
> -- which reminds me of the need to package LKCL's version of uboot for
> it.
>
> [1]: https://wiki.parabola.nu/ARM_Installation_Guide#BeagleBone_Black_2
>



From nobody at parabola.nu  Thu Nov  9 17:40:35 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 09 Nov 2017 17:40:35 -0000
Subject: [Dev] Orphan Nonprism package [gnome-settings-daemon] marked
 out-of-date
Message-ID: <20171109174035.1245.77092@proton.parabola.nu>

dikasetyaprayogi at gmail.com wants to notify you that the following packages may be out-of-date:




The user provided the following additional text:

please update to macth gnome 3.26 version



From dikasetyaprayogi at gmail.com  Thu Nov  9 17:54:08 2017
From: dikasetyaprayogi at gmail.com (Dika SP)
Date: Fri, 10 Nov 2017 00:54:08 +0700
Subject: [Dev] Orphan Nonprism package [gnome-settings-daemon] marked
 out-of-date
In-Reply-To: <20171109174035.1245.77092@proton.parabola.nu>
References: <20171109174035.1245.77092@proton.parabola.nu>
Message-ID: <CAKpbLobku0pXYfSRKFGOU9fRxpLNnG-DnE7Oy2SFTD=7HuPLVA@mail.gmail.com>

... following packages may be out-of-date
gnome-settings-daemon 3.24.2-1.nonprism1 [nonprism] (i686)
gnome-settings-daemon 3.24.2-1.nonprism1 [nonprism] (x86_64)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171110/05bbc9b8/attachment.htm>

From nobody at parabola.nu  Fri Nov 10 06:55:17 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Fri, 10 Nov 2017 06:55:17 -0000
Subject: [Dev] Orphan Libre package [kdebase-runtime] marked out-of-date
Message-ID: <20171110065517.1245.91465@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* kdebase-runtime 17.08.2-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kdebase-runtime/
* kdebase-runtime 17.08.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kdebase-runtime/


The user provided the following additional text:

Current release is 17.08.3



From jc_gargma at iserlohn-fortress.net  Fri Nov 10 07:00:04 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Thu, 09 Nov 2017 23:00:04 -0800
Subject: [Dev] Orphan Libre package [kdebase-runtime] marked out-of-date
In-Reply-To: <20171110065517.1245.91465@proton.parabola.nu>
References: <20171110065517.1245.91465@proton.parabola.nu>
Message-ID: <5379322.cthus2Nuqp@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git-format patch to update the following to 17.08.3:
akonadi-contacts
ark
kdebase-runtime
kdelibs
kdenetwork-kopete
kio-extras
konqueror
okular


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-ark-akonadi-contacts-kdebase-runtime-kdelibs.patch
Type: text/x-patch
Size: 8983 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171109/b9fdb976/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171109/b9fdb976/attachment.sig>

From megver83 at hyperbola.info  Fri Nov 10 18:37:18 2017
From: megver83 at hyperbola.info (Megver83)
Date: Fri, 10 Nov 2017 15:37:18 -0300
Subject: [Dev] EOMA68 card
In-Reply-To: <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
Message-ID: <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>

El 26/10/17 a las 15:59, SohKa escribi?:
>> To clarify, though: are we talking about an official release board,
> which at this ponint don't have a release date, or do you have an actual
> physical preview board on your hands?
> 
> Unfortunately, it's an official release board. So yeah, I don't have it
> and there is no release date. The project page on Crowdsupply says that
> the cards will be shipped in November 2017, but it seems unlikely.
> 
>> BTW did you got Parabola working on that device?
> 
> As I said above, I don't have it. The idea would be to change the
> shipping address in my Crowdsupply account for the one that you (or
> somebody else, if you change your mind) will choose.
> 
> I ordered a card with a preinstalled Debian. But it was also possible to
> choose Parabola. So I suppose the dev will support it at a minimum. :)
> 
> Kind regards,
> 
> sohka
> 
> 
> On 10/26/2017 06:35 AM, Andreas Grapentin wrote:
>> On Wed, Oct 25, 2017 at 07:18:54PM -0300, Megver83 wrote:
>>> I remember that Andreas was moving some things regarding our ARM port
>>> -maybe he needs it more than me?- and the EOMA68 thing, so I'd like to
>>> hear his opinion about this, before accepting it.
>> I am currently building packages on a beaglebone black, and I'm probably
>> still in the loop for a preview board, so I don't need it that bad.
>>
>> To clarify, though: are we talking about an official release board,
>> which at this ponint don't have a release date, or do you have an
>> actual physical preview board on your hands? In the second case, I would
>> be very much interested :)
>>
>> Thanks,
>> Andreas
>>
>>
>>
>>> _______________________________________________
>>> 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
> 
ummm, just got the email after various days :S
I offer to receive it, as I like developing on ARM

-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171110/3a853dc6/attachment.sig>

From isacdaavid at isacdaavid.info  Fri Nov 10 19:20:20 2017
From: isacdaavid at isacdaavid.info (Isaac David)
Date: Fri, 10 Nov 2017 13:20:20 -0600
Subject: [Dev] EOMA68 card
In-Reply-To: <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
Message-ID: <1510341620.20307.0@plebeian.isacdaavid.info>

Megver83 wrote :
> ummm, just got the email after various days :S

nobody was around to approve it. SohKa isn't subscribed.

-- 
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
<https://isacdaavid.info/donate>



From happy_gnu at teknik.io  Fri Nov 10 20:14:03 2017
From: happy_gnu at teknik.io (happy gnu)
Date: Fri, 10 Nov 2017 14:14:03 -0600
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <1510341620.20307.0@plebeian.isacdaavid.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
Message-ID: <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>

I read a thread about Chromium having issues to be considered free
software. But what about iridium??
https://iridiumbrowser.de/downloads/linux.html

It is listed on the FSF directory:? https://directory.fsf.org/wiki/Iridium

But as it is based on Chromium and you have discussed this before, I
wanted to ask your opinion.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x62E52D85.asc
Type: application/pgp-keys
Size: 3147 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171110/dbbc4a03/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171110/dbbc4a03/attachment.sig>

From bill-auger at peers.community  Sat Nov 11 17:17:22 2017
From: bill-auger at peers.community (bill-auger)
Date: Sat, 11 Nov 2017 12:17:22 -0500
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
Message-ID: <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>



On 11/10/2017 03:14 PM, happy gnu wrote:
> But what about iridium?

there is an open issue about this on the parabola bug tracker that you
can watch if you like

https://labs.parabola.nu/issues/1167

i asked donaldr about this last week and he asked that i post to the FSD
mailing list so hopefully that will re-kindle some discussion -
unfortunately no one from the FSF has commented on it so that's still
where it stands today

this issue is almost 10 years old now and it seems highly doubtful that
it will be resolved ever - if parabola is waiting for the FSF to declare
chromium to be free then parabola will probably be blacklisting chromium
and all qtwebengine-based and electron-based programs forever

https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171111/6f874519/attachment.sig>

From isacdaavid at isacdaavid.info  Sat Nov 11 18:01:16 2017
From: isacdaavid at isacdaavid.info (Isaac David)
Date: Sat, 11 Nov 2017 12:01:16 -0600
Subject: [Dev] [dbscripts]: Arch Linux 32 support [annoucement]. ABS' future
 [RFC]
Message-ID: <1510423276.27338.0@plebeian.isacdaavid.info>

hi,

i've been working over the last few days on getting dbscripts to
import i686 packages from archlinux32.org. this resulted on a single
script (db-import-pkg) shared by our 3 upstream providers, with common
routines from the previous separate scripts modularised, de-duplicated
and (briefly) documented. armv7h and i686 will also stop duplicating
arch=(any) packages first obtained from Arch proper.

that's it for the cursory announcement/overview of the impending
dbscripts release, which probably affects no one but our server.

on a related topic, we no longer have a (working) tool to retrieve
sources per package. Arch's [deprecation of ABS][] also spelled the end
of Parabola's dbscripts program that dealt with populating our own
ABS-like tree.

because .src tarballs are completely lacking from ALARM and Arch32,
it's clear to me that the only way forward is to pull from VC systems
themselves and cook one full Parabola source tree from there. that is,
one per upstream/architecture, overriding with customized PKGBUILDs.

but what about the client? what are your views regarding fixing and
continuing abs vs adopting and adapting the newer --and apparently
more complex-- [asp][]?

[deprecation of ABS]: https://www.archlinux.org/news/deprecation-of-abs/
[asp]: https://github.com/falconindy/asp

-- 
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
<https://isacdaavid.info/donate>



From nobody at parabola.nu  Sat Nov 11 21:27:56 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Sat, 11 Nov 2017 21:27:56 -0000
Subject: [Dev] Orphan Libre package [kile] marked out-of-date
Message-ID: <20171111212756.1243.16365@proton.parabola.nu>

christian at openmailbox.org wants to notify you that the following packages may be out-of-date:


* kile 2.1.3-7.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kile/
* kile 2.1.3-7.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kile/
* kile 2.1.3-7.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kile/


The user provided the following additional text:

way out of date and will not even install



From nobody at parabola.nu  Sat Nov 11 23:14:08 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Sat, 11 Nov 2017 23:14:08 -0000
Subject: [Dev] Orphan Libre package [mesa] marked out-of-date
Message-ID: <20171111231408.1246.73685@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* mesa 17.2.3-2.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/mesa/
* mesa 17.2.3-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/mesa/


The user provided the following additional text:

Current release is 17.2.5



From nobody at parabola.nu  Mon Nov 13 02:35:38 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Mon, 13 Nov 2017 02:35:38 -0000
Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date
Message-ID: <20171113023538.1246.76837@proton.parabola.nu>

nowhere at example.com wants to notify you that the following packages may be out-of-date:


* linux-libre 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/
* linux-libre 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/
* linux-libre-docs 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/
* linux-libre-docs 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/
* linux-libre-headers 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/
* linux-libre-headers 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/


The user provided the following additional text:

https://linux-libre.fsfla.org/pub/linux-libre/releases/4.14-gnu/



From andreas at grapentin.org  Mon Nov 13 07:24:44 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Mon, 13 Nov 2017 08:24:44 +0100
Subject: [Dev] [RFC] adding pdftk & gcc-gcj-ecj to pcr/
Message-ID: <20171113072444.GA31898@parabola-pocket.localdomain>


Hi everyone,

I was in the process of adding pdftk and gcc-gcj-ecj to prc/, and
normally I would just go ahead and commit/push, but I feel like my head
is screwed on backwards today it seems to make sense to have a second
pair of eyes look at this.

The licenses look good, but I'm concerned because gcc-gcj-ecj is
basically a binary package (downloading a release jar) and I haven't
found a better way to build it.

I have attached a patch. Any comments are welcome.

Best,
Andreas

-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdftk_gcc-gcj-ecj.patch
Type: text/x-diff
Size: 4430 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/b77dbebc/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/b77dbebc/attachment.sig>

From lovell.joshyyy at gmail.com  Mon Nov 13 07:40:24 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Mon, 13 Nov 2017 07:40:24 +0000
Subject: [Dev] [RFC] adding pdftk & gcc-gcj-ecj to pcr/
In-Reply-To: <20171113072444.GA31898@parabola-pocket.localdomain>
References: <20171113072444.GA31898@parabola-pocket.localdomain>
Message-ID: <5A094C68.5090801@gmail.com>

On 13/11/17 07:24, Andreas Grapentin wrote:
>
> Hi everyone,
>
> I was in the process of adding pdftk and gcc-gcj-ecj to prc/, and
> normally I would just go ahead and commit/push, but I feel like my head
> is screwed on backwards today it seems to make sense to have a second
> pair of eyes look at this.
>
> The licenses look good, but I'm concerned because gcc-gcj-ecj is
> basically a binary package (downloading a release jar) and I haven't
> found a better way to build it.

You have seen ftp://sourceware.org/pub/java/ecj-4.9-source.tar.bz2 from 
sourceware's ftp I take it? Or is there a problem building?

>
> I have attached a patch. Any comments are welcome.
>
> Best,
> Andreas
>

Josh


From andreas at grapentin.org  Mon Nov 13 09:58:08 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Mon, 13 Nov 2017 10:58:08 +0100
Subject: [Dev] [RFC] adding pdftk & gcc-gcj-ecj to pcr/
In-Reply-To: <5A094C68.5090801@gmail.com>
References: <20171113072444.GA31898@parabola-pocket.localdomain>
 <5A094C68.5090801@gmail.com>
Message-ID: <20171113095808.GA4988@parabola-pocket.localdomain>


On Mon, Nov 13, 2017 at 07:40:24AM +0000, Josh Branning wrote:
> You have seen ftp://sourceware.org/pub/java/ecj-4.9-source.tar.bz2 from
> sourceware's ftp I take it? Or is there a problem building?

I had indeed not seen that yet, thanks for the pointer. I attached an
updated patch that I will commit later, unless more issues are pointed
out.

Thanks for the assistance :)

-Andreas

-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdftk_gcc-gcj-ecj.patch
Type: text/x-diff
Size: 6294 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/a943c3fa/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/a943c3fa/attachment.sig>

From andreas at grapentin.org  Mon Nov 13 09:59:54 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Mon, 13 Nov 2017 10:59:54 +0100
Subject: [Dev] [RFC] adding pdftk & gcc-gcj-ecj to pcr/
In-Reply-To: <20171113095808.GA4988@parabola-pocket.localdomain>
References: <20171113072444.GA31898@parabola-pocket.localdomain>
 <5A094C68.5090801@gmail.com>
 <20171113095808.GA4988@parabola-pocket.localdomain>
Message-ID: <20171113095954.GA9112@parabola-pocket.localdomain>


Ignore my last mail, there were issues with the patch.
I've attached the correct one now.

-A

On Mon, Nov 13, 2017 at 10:58:08AM +0100, Andreas Grapentin wrote:
> 
> On Mon, Nov 13, 2017 at 07:40:24AM +0000, Josh Branning wrote:
> > You have seen ftp://sourceware.org/pub/java/ecj-4.9-source.tar.bz2 from
> > sourceware's ftp I take it? Or is there a problem building?
> 
> I had indeed not seen that yet, thanks for the pointer. I attached an
> updated patch that I will commit later, unless more issues are pointed
> out.
> 
> Thanks for the assistance :)
> 
> -Andreas
> 
> -- 
> 
> ------------------------------------------------------------------------------
> my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
> ------------------------------------------------------------------------------

> diff --git a/pcr/gcc-gcj-ecj-bin/PKGBUILD b/pcr/gcc-gcj-ecj-bin/PKGBUILD
> new file mode 100644
> index 000000000..16bd7de2f
> --- /dev/null
> +++ b/pcr/gcc-gcj-ecj-bin/PKGBUILD
> @@ -0,0 +1,28 @@
> +# Maintainer: Andreas Grapentin <andreas at grapentin.org>
> +# Maintainer (AUR): Joey Dumont <joey.dumont at gmail.com>
> +# Contributor (AUR): Pierre Bourdon <delroth at gmail.com>
> +# Contributor (AUR): larsrh <hupel at in.tum.de>
> +
> +pkgname=gcc-gcj-ecj
> +
> +pkgver=4.9
> +pkgrel=4.parabola1
> +arch=(any)
> +
> +pkgdesc="A fork of the Eclipse Java bytecode compiler for GCJ"
> +url="http://gcc.gnu.org/java/"
> +license=(EPL)
> +
> +depends=(gcc6-gcj)
> +provides=(eclipse-ecj)
> +conflicts=(eclipse-ecj)
> +
> +source=(http://mirrors.kernel.org/sources.redhat.com/java/ecj-$pkgver.jar ecj1)
> +md5sums=('7339f199ba11c941890031fd9981d7be'
> +         'ee312c2f80c73152dde859ea66e494d0')
> +noextract=("ecj-$pkgver.jar")
> +
> +package() {
> +	install -D -m644 $srcdir/ecj-$pkgver.jar $pkgdir/usr/share/java/eclipse-ecj.jar
> +	install -D -m755 $srcdir/ecj1 $pkgdir/usr/bin/ecj1
> +}
> diff --git a/pcr/gcc-gcj-ecj-bin/ecj1 b/pcr/gcc-gcj-ecj-bin/ecj1
> new file mode 100755
> index 000000000..eee1f3363
> --- /dev/null
> +++ b/pcr/gcc-gcj-ecj-bin/ecj1
> @@ -0,0 +1,5 @@
> +#!/bin/sh
> +gij-6 -cp /usr/share/java/eclipse-ecj.jar \
> +	org.eclipse.jdt.internal.compiler.batch.GCCMain \
> +	${1+"$@"}
> +
> diff --git a/pcr/gcc-gcj-ecj/PKGBUILD b/pcr/gcc-gcj-ecj/PKGBUILD
> new file mode 100644
> index 000000000..0f5e7d983
> --- /dev/null
> +++ b/pcr/gcc-gcj-ecj/PKGBUILD
> @@ -0,0 +1,49 @@
> +# Maintainer: Andreas Grapentin <andreas at grapentin.org>
> +# Maintainer (AUR): Joey Dumont <joey.dumont at gmail.com>
> +# Contributor (AUR): Pierre Bourdon <delroth at gmail.com>
> +# Contributor (AUR): larsrh <hupel at in.tum.de>
> +
> +pkgname=gcc-gcj-ecj
> +
> +pkgver=4.9
> +pkgrel=4.parabola1
> +arch=(any)
> +
> +pkgdesc="A fork of the Eclipse Java bytecode compiler for GCJ"
> +url="http://gcc.gnu.org/java/"
> +license=(EPL)
> +
> +makedepends=(eclipse-ecj java-environment)
> +depends=(gcc6-gcj)
> +provides=(eclipse-ecj)
> +conflicts=(eclipse-ecj)
> +
> +source=("ftp://sourceware.org/pub/java/ecj-$pkgver-source.tar.bz2"
> +        "https://git.eclipse.org/c/jdt/eclipse.jdt.core.git/snapshot/R4_3_1.tar.gz"
> +        "ecj1")
> +sha256sums=('a48a8bfc419fab20646c49069ae2e0c07b4e73fc56572ac3b7e0151a0388f1c5'
> +            'affb39ca4f5fab6800846e4279fcd0684ddd3753a3bde475e6505f715af9ec61'
> +            '3dcf27b250ff7766a9240159b30b4eb5bf8544da93984154643c3068c5dca2d4')
> +noextract=("ecj-$pkgver-source.tar.bz2")
> +
> +prepare() {
> +  mkdir -p $pkgname-$pkgver
> +  cd $pkgname-$pkgver
> +
> +  tar -xf ../ecj-$pkgver-source.tar.bz2
> +  mv ../R4_3_1.tar.gz .
> +
> +  make checkout
> +}
> +
> +build() {
> +  cd $pkgname-$pkgver
> +
> +  make compile
> +  make ecj.jar ecj-source.tar.bz2
> +}
> +
> +package() {
> +	install -D -m644 $srcdir/$pkgname-$pkgver/ecj.jar $pkgdir/usr/share/java/eclipse-ecj.jar
> +	install -D -m755 $srcdir/ecj1 $pkgdir/usr/bin/ecj1
> +}
> diff --git a/pcr/gcc-gcj-ecj/ecj1 b/pcr/gcc-gcj-ecj/ecj1
> new file mode 100644
> index 000000000..eee1f3363
> --- /dev/null
> +++ b/pcr/gcc-gcj-ecj/ecj1
> @@ -0,0 +1,5 @@
> +#!/bin/sh
> +gij-6 -cp /usr/share/java/eclipse-ecj.jar \
> +	org.eclipse.jdt.internal.compiler.batch.GCCMain \
> +	${1+"$@"}
> +
> diff --git a/pcr/pdftk/Makefile.Parabola b/pcr/pdftk/Makefile.Parabola
> new file mode 100644
> index 000000000..7a0dd09d6
> --- /dev/null
> +++ b/pcr/pdftk/Makefile.Parabola
> @@ -0,0 +1,22 @@
> +# Based on 'Makefile.Arch', part of pdftk
> +# Copyright (c) 2004-2012 Sid Steward
> +
> +export CXX= g++-6
> +export GCJ= gcj-6
> +export GIJ= gij-6
> +export GCJH= gcjh-6
> +export GJAR= gjar-6
> +export CC1PLUS= cc1plus-6
> +export LIBGCJ= /usr/share/java/libgcj.jar
> +export AR= ar
> +export RM= rm
> +export ARFLAGS= rs
> +export RMFLAGS= -vf
> +export CPPFLAGS= -DPATH_DELIM=0x2f -DASK_ABOUT_WARNINGS=false -DUNBLOCK_SIGNALS -fdollars-in-identifiers -fPIC
> +GCC6VER=`gcc -dumpversion`
> +export CXXFLAGS= -O2 -fPIC -I/usr/lib/gcc/x86_64-pc-linux-gnu/${GCC6VER}/include/c++/ -I/usr/lib/gcc/x86_64-pc-linux-gnu/${GCC6VER}/include/c++/x86_64-pc-linux-gnu
> +export GCJFLAGS= -Wno-all -fsource=1.3 -O2 -fPIC
> +export GCJHFLAGS= -force
> +export LDLIBS= -lgcj
> +
> +include Makefile.Base
> diff --git a/pcr/pdftk/PKGBUILD b/pcr/pdftk/PKGBUILD
> new file mode 100644
> index 000000000..5fde66018
> --- /dev/null
> +++ b/pcr/pdftk/PKGBUILD
> @@ -0,0 +1,61 @@
> +# Maintainer: Andreas Grapentin <andreas at grapentin.org>
> +# Maintainer (AUR): Joey Dumont <joey.dumont at gmail.com>
> +# Contributor (AUR): osc
> +# Contributor (AUR): StefanHusmann
> +# Contributor (AUR): larsrh <hupel at in.tum.de>
> +
> +pkgname=pdftk
> +
> +pkgver=2.02
> +pkgrel=18.parabola1
> +arch=(i686 x86_64)
> +
> +pkgdesc="Pdftk is a simple tool for doing everyday things with PDF documents"
> +url="http://www.pdfhacks.com/pdftk"
> +license=(GPL)
> +
> +depends=(gcc6-gcj gcc-gcj-ecj)
> +options=('!makeflags')
> +
> +source=("http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/$pkgname-$pkgver-src.zip"
> +        "Makefile.Parabola"
> +        "pdftk"
> +)
> +sha256sums=('118f6a25fd3acaafb58824dce6f97cdc07e56050e666b90e4c4ef426ea37b8c1'
> +            '4451a807817b5e40755b79686bce5751c70758c83302a4214c23c4f361168620'
> +            '9c49337ed05759e986f24ac4173f727567c617e5f160e4c9ec7e089e120af3c3')
> +
> +prepare() {
> +  cd "$srcdir/$pkgname-$pkgver-dist/$pkgname"
> +
> +  cp "$srcdir/Makefile.Parabola" .
> +}
> +
> +build() {
> +  cd "$srcdir/$pkgname-$pkgver-dist/$pkgname"
> +
> +  make -f Makefile.Parabola
> +}
> +
> +package() {
> +  cd "$srcdir/$pkgname-$pkgver-dist/$pkgname"
> +
> +  # Install binary
> +  install -D -m 755 pdftk $pkgdir/usr/bin/pdftk-bin
> +
> +  # Install licenses and adjust permissions
> +  cd ..
> +  LICENSE_DIR="$pkgdir/usr/share/licenses/$pkgname"
> +  mkdir -p "$LICENSE_DIR"
> +  cp -R license_gpl_pdftk/* "$LICENSE_DIR"
> +  chmod -R 0755 "$LICENSE_DIR"
> +  find "$LICENSE_DIR" -type f -exec chmod -x {} \;
> +
> +  # Install manpage
> +  install -D -m 644 "pdftk.1" "$pkgdir/usr/share/man/man1/pdftk.1"
> +
> +  # Install wrapper that sets the proper environment variables.
> +  sed -i "s/CARCH/${CARCH}/" ${srcdir}/pdftk
> +  sed -i "s/GCCVER/`gcc-6 -dumpversion`/" ${srcdir}/pdftk
> +  install -D -m 755 ${srcdir}/pdftk ${pkgdir}/usr/bin/pdftk
> +}
> diff --git a/pcr/pdftk/pdftk b/pcr/pdftk/pdftk
> new file mode 100644
> index 000000000..12d821bd0
> --- /dev/null
> +++ b/pcr/pdftk/pdftk
> @@ -0,0 +1,3 @@
> +#!/bin/bash
> +export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib/gcc/CARCH-pc-linux-gnu/GCCVER
> +pdftk-bin "$@"




> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdftk_gcc-gcj-ecj.patch
Type: text/x-diff
Size: 4821 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/8243faba/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/8243faba/attachment.sig>

From megver83 at hyperbola.info  Mon Nov 13 18:20:15 2017
From: megver83 at hyperbola.info (Megver83)
Date: Mon, 13 Nov 2017 15:20:15 -0300
Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date
In-Reply-To: <20171113023538.1246.76837@proton.parabola.nu>
References: <20171113023538.1246.76837@proton.parabola.nu>
Message-ID: <7d99b6e3-6965-2267-a023-a66737017308@hyperbola.info>

El 12/11/17 a las 23:35, Parabola Website Notification escribi?:
> nowhere at example.com wants to notify you that the following packages may be out-of-date:
> 
> 
> * linux-libre 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/
> * linux-libre 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/
> * linux-libre-docs 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/
> * linux-libre-docs 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/
> * linux-libre-headers 4.13.12_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/
> * linux-libre-headers 4.13.12_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/
> 
> 
> The user provided the following additional text:
> 
> https://linux-libre.fsfla.org/pub/linux-libre/releases/4.14-gnu/
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 
nowhere at example.com? is this a bot? plus, we won't go ahead with 4.14
immediately since Arch hasn't launched an update, yet

-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/e61f07e6/attachment.sig>

From nobody at parabola.nu  Mon Nov 13 18:48:46 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Mon, 13 Nov 2017 18:48:46 -0000
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
Message-ID: <20171113184846.1244.71257@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* kio 5.39.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kio/
* kio 5.39.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kio/


The user provided the following additional text:

Current release is 5.40



From jc_gargma at iserlohn-fortress.net  Mon Nov 13 18:50:44 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Mon, 13 Nov 2017 10:50:44 -0800
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
In-Reply-To: <20171113184846.1244.71257@proton.parabola.nu>
References: <20171113184846.1244.71257@proton.parabola.nu>
Message-ID: <167884637.iPegsGXH93@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update kio to 5.40


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-kio-to-5.40.patch
Type: text/x-patch
Size: 1240 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/361ce62c/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/361ce62c/attachment.sig>

From andreas at grapentin.org  Mon Nov 13 18:59:47 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Mon, 13 Nov 2017 19:59:47 +0100
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
In-Reply-To: <167884637.iPegsGXH93@iserlohn-fortress.net>
References: <20171113184846.1244.71257@proton.parabola.nu>
 <167884637.iPegsGXH93@iserlohn-fortress.net>
Message-ID: <20171113185947.GA1020@parabola-pocket.localdomain>


I don't say this as often as I should, but these patches are very much
appreciated :)

-A

On Mon, Nov 13, 2017 at 10:50:44AM -0800, jc_gargma wrote:
> > The user provided the following additional text:
> I've attached a git format-patch to update kio to 5.40
> 
> 
> -jc

> From e339f84707296a717ebae25b1783107f9ce1f744 Mon Sep 17 00:00:00 2001
> From: jc_gargma <jc_gargma at iserlohn-fortress.net>
> Date: Mon, 13 Nov 2017 10:10:03 -0800
> Subject: [PATCH] Updated kio to 5.40
> 
> ---
>  libre/kio/PKGBUILD | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/libre/kio/PKGBUILD b/libre/kio/PKGBUILD
> index 6a4f1de2b..b519d746a 100644
> --- a/libre/kio/PKGBUILD
> +++ b/libre/kio/PKGBUILD
> @@ -5,7 +5,7 @@
>  # Contributor (Arch): Andrea Scarpino <andrea at archlinux.org>
>  
>  pkgname=kio
> -pkgver=5.39.0
> +pkgver=5.40.0
>  pkgrel=1.parabola1
>  pkgdesc='Resource and network access abstraction, without non-privacy search engines'
>  arch=('i686' 'x86_64' 'armv7h')
> @@ -20,7 +20,7 @@ groups=('kf5')
>  source=("https://download.kde.org/stable/frameworks/${pkgver%.*}/${pkgname}-${pkgver}.tar.xz"{,.sig}
>          'duckduckgo_html.desktop'
>          'duckduckgo_lite.desktop')
> -sha256sums=('96cbea5aba34b4e1b0df5ecfb4aaf65ff324341fb00f99796146536557232f24'
> +sha256sums=('30ea0b231b995faaf4283b9c9ecfaffb589268f5d7b5b805f69ed95601ac389b'
>              'SKIP'
>              '31910ab7393e67609f15e04a57f6406f63e6dae58b01bce0787741bc5958f292'
>              '40466a9dad7075f2525e9e024720da7d7b49a22892b6fca8b81cc0e6408d2f7d')
> -- 
> 2.15.0
> 




> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/6e81d0d2/attachment.sig>

From nobody at parabola.nu  Mon Nov 13 21:03:03 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Mon, 13 Nov 2017 21:03:03 -0000
Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked out-of-date
Message-ID: <20171113210303.1243.89917@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* icecat-ublock-origin 1.14.16-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-ublock-origin/


The user provided the following additional text:

Current release is 1.14.18



From jc_gargma at iserlohn-fortress.net  Mon Nov 13 21:04:47 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Mon, 13 Nov 2017 13:04:47 -0800
Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked
 out-of-date
In-Reply-To: <20171113210303.1243.89917@proton.parabola.nu>
References: <20171113210303.1243.89917@proton.parabola.nu>
Message-ID: <75570653.XcsIiRuzro@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update to 1.14.18:
icecat-ublock-origin
iceweasel-ublock-origin


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-icecat-iceweasel-ublock-origin-to-1.14.18.patch
Type: text/x-patch
Size: 2170 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/a3252b54/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/a3252b54/attachment.sig>

From nobody at parabola.nu  Tue Nov 14 00:59:44 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 14 Nov 2017 00:59:44 -0000
Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date
Message-ID: <20171114005944.1243.27467@proton.parabola.nu>

jfc at posteo.net wants to notify you that the following packages may be out-of-date:


* iceweasel 1:56.0.2-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/
* iceweasel 1:56.0.2-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/


The user provided the following additional text:

Firefox 57 drops today, just a friendly reminder :)



From eliotreyna at cock.email  Tue Nov 14 01:38:31 2017
From: eliotreyna at cock.email (Eliot Reyna)
Date: Mon, 13 Nov 2017 20:38:31 -0500
Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date
Message-ID: <b0e14rt0wl8wnny9d7muwa0f.1510623511060@email.android.com>

However, the official release date (including source code) is wednesday.


Enviado desde Samsung Mobile.

<div>-------- Mensaje original --------</div><div>De: Parabola Website Notification <nobody at parabola.nu> </div><div>Fecha:13/11/2017  07:59 PM  (GMT-05:00) </div><div>A: dev at lists.parabola.nu </div><div>Asunto: [Dev] Orphan Libre package [iceweasel] marked out-of-date </div><div>
</div>jfc at posteo.net wants to notify you that the following packages may be out-of-date:


* iceweasel 1:56.0.2-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/
* iceweasel 1:56.0.2-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/


The user provided the following additional text:

Firefox 57 drops today, just a friendly reminder :)

_______________________________________________
Dev mailing list
Dev at lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171113/decb8bf0/attachment.htm>

From nobody at parabola.nu  Tue Nov 14 18:30:35 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 14 Nov 2017 18:30:35 -0000
Subject: [Dev] Orphan Nonprism package [gnome-weather] marked out-of-date
Message-ID: <20171114183035.1245.59533@proton.parabola.nu>

nowhere at example.com wants to notify you that the following packages may be out-of-date:




The user provided the following additional text:

3.26.0 is in Extra.



From nobody at parabola.nu  Tue Nov 14 20:01:29 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 14 Nov 2017 20:01:29 -0000
Subject: [Dev] Orphan Libre package [iceweasel-l10n-es-ar] marked out-of-date
Message-ID: <20171114200129.1246.14962@proton.parabola.nu>

eliotreyna at cock.email wants to notify you that the following packages may be out-of-date:


* iceweasel-l10n-ach 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ach/
* iceweasel-l10n-af 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-af/
* iceweasel-l10n-an 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-an/
* iceweasel-l10n-ar 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ar/
* iceweasel-l10n-as 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-as/
* iceweasel-l10n-ast 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ast/
* iceweasel-l10n-az 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-az/
* iceweasel-l10n-be 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-be/
* iceweasel-l10n-bg 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-bg/
* iceweasel-l10n-bn-bd 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-bn-bd/
* iceweasel-l10n-bn-in 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-bn-in/
* iceweasel-l10n-br 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-br/
* iceweasel-l10n-bs 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-bs/
* iceweasel-l10n-ca 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ca/
* iceweasel-l10n-cak 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-cak/
* iceweasel-l10n-cs 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-cs/
* iceweasel-l10n-cy 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-cy/
* iceweasel-l10n-da 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-da/
* iceweasel-l10n-de 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-de/
* iceweasel-l10n-dsb 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-dsb/
* iceweasel-l10n-el 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-el/
* iceweasel-l10n-en-gb 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-en-gb/
* iceweasel-l10n-en-us 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-en-us/
* iceweasel-l10n-en-za 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-en-za/
* iceweasel-l10n-eo 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-eo/
* iceweasel-l10n-es-ar 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-es-ar/
* iceweasel-l10n-es-cl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-es-cl/
* iceweasel-l10n-es-es 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-es-es/
* iceweasel-l10n-es-mx 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-es-mx/
* iceweasel-l10n-et 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-et/
* iceweasel-l10n-eu 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-eu/
* iceweasel-l10n-fa 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-fa/
* iceweasel-l10n-ff 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ff/
* iceweasel-l10n-fi 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-fi/
* iceweasel-l10n-fr 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-fr/
* iceweasel-l10n-fy-nl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-fy-nl/
* iceweasel-l10n-ga-ie 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ga-ie/
* iceweasel-l10n-gd 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-gd/
* iceweasel-l10n-gl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-gl/
* iceweasel-l10n-gn 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-gn/
* iceweasel-l10n-gu-in 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-gu-in/
* iceweasel-l10n-he 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-he/
* iceweasel-l10n-hi-in 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-hi-in/
* iceweasel-l10n-hr 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-hr/
* iceweasel-l10n-hsb 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-hsb/
* iceweasel-l10n-hu 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-hu/
* iceweasel-l10n-hy-am 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-hy-am/
* iceweasel-l10n-id 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-id/
* iceweasel-l10n-is 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-is/
* iceweasel-l10n-it 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-it/
* iceweasel-l10n-ja 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ja/
* iceweasel-l10n-ka 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ka/
* iceweasel-l10n-kab 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-kab/
* iceweasel-l10n-kk 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-kk/
* iceweasel-l10n-km 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-km/
* iceweasel-l10n-kn 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-kn/
* iceweasel-l10n-ko 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ko/
* iceweasel-l10n-lij 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-lij/
* iceweasel-l10n-lt 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-lt/
* iceweasel-l10n-lv 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-lv/
* iceweasel-l10n-mai 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-mai/
* iceweasel-l10n-mk 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-mk/
* iceweasel-l10n-ml 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ml/
* iceweasel-l10n-mr 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-mr/
* iceweasel-l10n-ms 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ms/
* iceweasel-l10n-my 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-my/
* iceweasel-l10n-nb-no 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-nb-no/
* iceweasel-l10n-nl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-nl/
* iceweasel-l10n-nn-no 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-nn-no/
* iceweasel-l10n-or 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-or/
* iceweasel-l10n-pa-in 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-pa-in/
* iceweasel-l10n-pl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-pl/
* iceweasel-l10n-pt-br 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-pt-br/
* iceweasel-l10n-pt-pt 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-pt-pt/
* iceweasel-l10n-rm 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-rm/
* iceweasel-l10n-ro 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ro/
* iceweasel-l10n-ru 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ru/
* iceweasel-l10n-si 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-si/
* iceweasel-l10n-sk 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-sk/
* iceweasel-l10n-sl 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-sl/
* iceweasel-l10n-son 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-son/
* iceweasel-l10n-sq 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-sq/
* iceweasel-l10n-sr 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-sr/
* iceweasel-l10n-sv-se 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-sv-se/
* iceweasel-l10n-ta 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ta/
* iceweasel-l10n-te 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-te/
* iceweasel-l10n-th 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-th/
* iceweasel-l10n-tr 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-tr/
* iceweasel-l10n-uk 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-uk/
* iceweasel-l10n-ur 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-ur/
* iceweasel-l10n-uz 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-uz/
* iceweasel-l10n-vi 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-vi/
* iceweasel-l10n-xh 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-xh/
* iceweasel-l10n-zh-cn 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-zh-cn/
* iceweasel-l10n-zh-tw 1:56.0.2-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/iceweasel-l10n-zh-tw/


The user provided the following additional text:

Please update Iceweasel to the version 57. It now works with Quantum.

More information about the source code updates of Firefox: 

https://www.mozilla.org/en-US/firefox/57.0/releasenotes/



From jc_gargma at iserlohn-fortress.net  Tue Nov 14 22:16:04 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 14 Nov 2017 14:16:04 -0800
Subject: [Dev] Orphan Libre package [kdepim-addons] marked out-of-date
In-Reply-To: <20170823200407.917.27384@proton.parabola.nu>
References: <20170823200407.917.27384@proton.parabola.nu>
Message-ID: <2135327.ofVlESJd5H@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update kdepim-addons to 17.08.3


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-kdepim-addons-to-17.08.3.patch
Type: text/x-patch
Size: 4182 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171114/fcd8b399/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171114/fcd8b399/attachment.sig>

From adfeno at hyperbola.info  Wed Nov 15 16:42:19 2017
From: adfeno at hyperbola.info (Adonay Felipe Nogueira)
Date: Wed, 15 Nov 2017 14:42:19 -0200
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 (bill-auger@peers.community's message of "Sat, 11 Nov 2017 12:17:22
 -0500")
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
Message-ID: <87zi7nxzmc.fsf@hyperbola.info>

I also have contributed to that thread on directory-discuss mailing
list.

I hope it helps somehow. ;)

bill-auger <bill-auger at peers.community> writes:

> there is an open issue about this on the parabola bug tracker that you
> can watch if you like
>
> https://labs.parabola.nu/issues/1167
>
> i asked donaldr about this last week and he asked that i post to the FSD
> mailing list so hopefully that will re-kindle some discussion -
> unfortunately no one from the FSF has commented on it so that's still
> where it stands today
>
> this issue is almost 10 years old now and it seems highly doubtful that
> it will be resolved ever - if parabola is waiting for the FSF to declare
> chromium to be free then parabola will probably be blacklisting chromium
> and all qtwebengine-based and electron-based programs forever
>
> https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html
>
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (n?o confundir com
  gratis).
- "WhatsApp"? Ele n?o ? livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endere?o abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padr?o ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.


From lovell.joshyyy at gmail.com  Wed Nov 15 19:26:54 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 15 Nov 2017 19:26:54 +0000
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <87zi7nxzmc.fsf@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info>
Message-ID: <5A0C94FE.1070906@gmail.com>

On 15/11/17 16:42, Adonay Felipe Nogueira wrote:
> I also have contributed to that thread on directory-discuss mailing
> list.
>
> I hope it helps somehow. ;)
>
> bill-auger <bill-auger at peers.community> writes:
>
>> there is an open issue about this on the parabola bug tracker that you
>> can watch if you like
>>
>> https://labs.parabola.nu/issues/1167
>>
>> i asked donaldr about this last week and he asked that i post to the FSD
>> mailing list so hopefully that will re-kindle some discussion -
>> unfortunately no one from the FSF has commented on it so that's still
>> where it stands today
>>
>> this issue is almost 10 years old now and it seems highly doubtful that
>> it will be resolved ever - if parabola is waiting for the FSF to declare
>> chromium to be free then parabola will probably be blacklisting chromium
>> and all qtwebengine-based and electron-based programs forever
>>
>> https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.parabola.nu
>> https://lists.parabola.nu/mailman/listinfo/dev
>

I think the main problem with chromium was that the licenses were/are 
not clear enough for some of the files - in that it didn't pass the 
ubuntu license checker [1]. What's also concerning, is that it's 
suggested on the linked thread, that they are mixing GPL code with other 
licenses. I don't think the GPL permits that (even if the code is only 
distributed in source form). This may have changed since ... and I am 
not a lawyer.

Licenses aside, chromium apparently links with non-free plugins (not 
sure if this is fixed in Iridium).

But long and short is it may be worth attempting to run the license 
checker on Iridium and QTWebengine. I'm speculating that QTWebengine 
probably has a higher chance of passing (if either of them actually do), 
as there is some confusion over whether the whole engine is included in 
the software [or not] ... it has been stated both ways.

I can see why it's difficult, because if code with unknown licenses were 
accepted and then found to be non-free, it may subsequently effect lots 
of derivative projects and code (inc. QTWebengine). I guess this is why 
some people are nervous about giving chromium the benefit over the doubt 
and including it on the basis of good faith.

Finally the bug in the link below has been closed, if it's a problem 
that can be fixed I suggest someone attempts to "re-triage the issue" if 
at-all possible.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=28291



From adfeno at hyperbola.info  Wed Nov 15 20:00:52 2017
From: adfeno at hyperbola.info (Adonay Felipe Nogueira)
Date: Wed, 15 Nov 2017 18:00:52 -0200
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <5A0C94FE.1070906@gmail.com> (Josh Branning's message of "Wed, 15
 Nov 2017 19:26:54 +0000")
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
Message-ID: <87bmk3xqff.fsf@hyperbola.info>

See the response I gave ([1]) to the new thread in the directory-discuss
mailing list ([2]).

Apparently it didn't change much, also considering the ambiguities I
noted on [1]..

I'll try doing the same steps for Iridium and QtWebEngine.

[1] <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00014.html>.

[2] <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html>.

Josh Branning <lovell.joshyyy at gmail.com> writes:

> I think the main problem with chromium was that the licenses were/are
> not clear enough for some of the files - in that it didn't pass the
> ubuntu license checker [1]. What's also concerning, is that it's
> suggested on the linked thread, that they are mixing GPL code with
> other licenses. I don't think the GPL permits that (even if the code
> is only distributed in source form). This may have changed since
> ... and I am not a lawyer.
>
> Licenses aside, chromium apparently links with non-free plugins (not
> sure if this is fixed in Iridium).
>
> But long and short is it may be worth attempting to run the license
> checker on Iridium and QTWebengine. I'm speculating that QTWebengine
> probably has a higher chance of passing (if either of them actually
> do), as there is some confusion over whether the whole engine is
> included in the software [or not] ... it has been stated both ways.
>
> I can see why it's difficult, because if code with unknown licenses
> were accepted and then found to be non-free, it may subsequently
> effect lots of derivative projects and code (inc. QTWebengine). I
> guess this is why some people are nervous about giving chromium the
> benefit over the doubt and including it on the basis of good faith.
>
> Finally the bug in the link below has been closed, if it's a problem
> that can be fixed I suggest someone attempts to "re-triage the issue"
> if at-all possible.
>
> [1] https://bugs.chromium.org/p/chromium/issues/detail?id=28291


From lovell.joshyyy at gmail.com  Wed Nov 15 20:08:35 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 15 Nov 2017 20:08:35 +0000
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <87bmk3xqff.fsf@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
 <87bmk3xqff.fsf@hyperbola.info>
Message-ID: <5A0C9EC3.7040006@gmail.com>

Thank you for this.

Could I also request you upload the text file(s) somewhere? I can't seem 
to download them from the lists.gnu.org archive, and that may be a 
problem for people who wish to help try and clarify the licenses.

May also be worth creating a pad, and seeing if people are willing to 
help if it's a long list?

Josh

On 15/11/17 20:00, Adonay Felipe Nogueira wrote:
> See the response I gave ([1]) to the new thread in the directory-discuss
> mailing list ([2]).
>
> Apparently it didn't change much, also considering the ambiguities I
> noted on [1]..
>
> I'll try doing the same steps for Iridium and QtWebEngine.
>
> [1] <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00014.html>.
>
> [2] <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html>.
>
> Josh Branning <lovell.joshyyy at gmail.com> writes:
>
>> I think the main problem with chromium was that the licenses were/are
>> not clear enough for some of the files - in that it didn't pass the
>> ubuntu license checker [1]. What's also concerning, is that it's
>> suggested on the linked thread, that they are mixing GPL code with
>> other licenses. I don't think the GPL permits that (even if the code
>> is only distributed in source form). This may have changed since
>> ... and I am not a lawyer.
>>
>> Licenses aside, chromium apparently links with non-free plugins (not
>> sure if this is fixed in Iridium).
>>
>> But long and short is it may be worth attempting to run the license
>> checker on Iridium and QTWebengine. I'm speculating that QTWebengine
>> probably has a higher chance of passing (if either of them actually
>> do), as there is some confusion over whether the whole engine is
>> included in the software [or not] ... it has been stated both ways.
>>
>> I can see why it's difficult, because if code with unknown licenses
>> were accepted and then found to be non-free, it may subsequently
>> effect lots of derivative projects and code (inc. QTWebengine). I
>> guess this is why some people are nervous about giving chromium the
>> benefit over the doubt and including it on the basis of good faith.
>>
>> Finally the bug in the link below has been closed, if it's a problem
>> that can be fixed I suggest someone attempts to "re-triage the issue"
>> if at-all possible.
>>
>> [1] https://bugs.chromium.org/p/chromium/issues/detail?id=28291
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
>



From jc_gargma at iserlohn-fortress.net  Wed Nov 15 20:12:23 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Wed, 15 Nov 2017 12:12:23 -0800
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <87bmk3xqff.fsf@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <5A0C94FE.1070906@gmail.com> <87bmk3xqff.fsf@hyperbola.info>
Message-ID: <188848491.vilEeLjz0v@iserlohn-fortress.net>

> I'll try doing the same steps for Iridium and QtWebEngine.
When you post the results of QtWebEngine, please cc qtwebengine at qt-project.org 
so that they are not left out of the loop this time.
Qt is a friend to the free software community. Please give them the chance to 
fix the issues.


-jc
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171115/2bd281ae/attachment.sig>

From adfeno at hyperbola.info  Wed Nov 15 20:39:25 2017
From: adfeno at hyperbola.info (Adonay Felipe Nogueira)
Date: Wed, 15 Nov 2017 18:39:25 -0200
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <5A0C9EC3.7040006@gmail.com> (Josh Branning's message of "Wed, 15
 Nov 2017 20:08:35 +0000")
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
 <87bmk3xqff.fsf@hyperbola.info> <5A0C9EC3.7040006@gmail.com>
Message-ID: <87vaibwa2q.fsf@hyperbola.info>

I'd prefer a wiki or a temporary repository. Pads are OK but hard to
keep track of changes without a browser with enough resources and speed
to run the JS and live updates. I'll see where I can put the list.

I just notice that the FSD is having some downtime, perhaps they're
doing maintainance.

Josh Branning <lovell.joshyyy at gmail.com> writes:

> Thank you for this.
>
> Could I also request you upload the text file(s) somewhere? I can't
> seem to download them from the lists.gnu.org archive, and that may be
> a problem for people who wish to help try and clarify the licenses.
>
> May also be worth creating a pad, and seeing if people are willing to
> help if it's a long list?
>
> Josh
>
> On 15/11/17 20:00, Adonay Felipe Nogueira wrote:
>> See the response I gave ([1]) to the new thread in the directory-discuss
>> mailing list ([2]).
>>
>> Apparently it didn't change much, also considering the ambiguities I
>> noted on [1]..
>>
>> I'll try doing the same steps for Iridium and QtWebEngine.
>>
>> [1]
>> <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00014.html>.
>>
>> [2]
>> <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html>.
>>
>> Josh Branning <lovell.joshyyy at gmail.com> writes:
>>
>>> I think the main problem with chromium was that the licenses were/are
>>> not clear enough for some of the files - in that it didn't pass the
>>> ubuntu license checker [1]. What's also concerning, is that it's
>>> suggested on the linked thread, that they are mixing GPL code with
>>> other licenses. I don't think the GPL permits that (even if the code
>>> is only distributed in source form). This may have changed since
>>> ... and I am not a lawyer.
>>>
>>> Licenses aside, chromium apparently links with non-free plugins (not
>>> sure if this is fixed in Iridium).
>>>
>>> But long and short is it may be worth attempting to run the license
>>> checker on Iridium and QTWebengine. I'm speculating that QTWebengine
>>> probably has a higher chance of passing (if either of them actually
>>> do), as there is some confusion over whether the whole engine is
>>> included in the software [or not] ... it has been stated both ways.
>>>
>>> I can see why it's difficult, because if code with unknown licenses
>>> were accepted and then found to be non-free, it may subsequently
>>> effect lots of derivative projects and code (inc. QTWebengine). I
>>> guess this is why some people are nervous about giving chromium the
>>> benefit over the doubt and including it on the basis of good faith.
>>>
>>> Finally the bug in the link below has been closed, if it's a problem
>>> that can be fixed I suggest someone attempts to "re-triage the issue"
>>> if at-all possible.
>>>
>>> [1] https://bugs.chromium.org/p/chromium/issues/detail?id=28291
>> _______________________________________________
>> 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
>

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (n?o confundir com
  gratis).
- "WhatsApp"? Ele n?o ? livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endere?o abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padr?o ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.


From lovell.joshyyy at gmail.com  Wed Nov 15 20:43:03 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 15 Nov 2017 20:43:03 +0000
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <87vaibwa2q.fsf@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
 <87bmk3xqff.fsf@hyperbola.info> <5A0C9EC3.7040006@gmail.com>
 <87vaibwa2q.fsf@hyperbola.info>
Message-ID: <5A0CA6D7.4030607@gmail.com>

Yes, on a wiki would be good/fine. :)

Unsure about any maintenance ...

Thanks again,

Josh

On 15/11/17 20:39, Adonay Felipe Nogueira wrote:
> I'd prefer a wiki or a temporary repository. Pads are OK but hard to
> keep track of changes without a browser with enough resources and speed
> to run the JS and live updates. I'll see where I can put the list.
>
> I just notice that the FSD is having some downtime, perhaps they're
> doing maintainance.
>
> Josh Branning <lovell.joshyyy at gmail.com> writes:
>
>> Thank you for this.
>>
>> Could I also request you upload the text file(s) somewhere? I can't
>> seem to download them from the lists.gnu.org archive, and that may be
>> a problem for people who wish to help try and clarify the licenses.
>>
>> May also be worth creating a pad, and seeing if people are willing to
>> help if it's a long list?
>>
>> Josh
>>
>> On 15/11/17 20:00, Adonay Felipe Nogueira wrote:
>>> See the response I gave ([1]) to the new thread in the directory-discuss
>>> mailing list ([2]).
>>>
>>> Apparently it didn't change much, also considering the ambiguities I
>>> noted on [1]..
>>>
>>> I'll try doing the same steps for Iridium and QtWebEngine.
>>>
>>> [1]
>>> <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00014.html>.
>>>
>>> [2]
>>> <https://lists.gnu.org/archive/html/directory-discuss/2017-11/msg00001.html>.
>>>
>>> Josh Branning <lovell.joshyyy at gmail.com> writes:
>>>
>>>> I think the main problem with chromium was that the licenses were/are
>>>> not clear enough for some of the files - in that it didn't pass the
>>>> ubuntu license checker [1]. What's also concerning, is that it's
>>>> suggested on the linked thread, that they are mixing GPL code with
>>>> other licenses. I don't think the GPL permits that (even if the code
>>>> is only distributed in source form). This may have changed since
>>>> ... and I am not a lawyer.
>>>>
>>>> Licenses aside, chromium apparently links with non-free plugins (not
>>>> sure if this is fixed in Iridium).
>>>>
>>>> But long and short is it may be worth attempting to run the license
>>>> checker on Iridium and QTWebengine. I'm speculating that QTWebengine
>>>> probably has a higher chance of passing (if either of them actually
>>>> do), as there is some confusion over whether the whole engine is
>>>> included in the software [or not] ... it has been stated both ways.
>>>>
>>>> I can see why it's difficult, because if code with unknown licenses
>>>> were accepted and then found to be non-free, it may subsequently
>>>> effect lots of derivative projects and code (inc. QTWebengine). I
>>>> guess this is why some people are nervous about giving chromium the
>>>> benefit over the doubt and including it on the basis of good faith.
>>>>
>>>> Finally the bug in the link below has been closed, if it's a problem
>>>> that can be fixed I suggest someone attempts to "re-triage the issue"
>>>> if at-all possible.
>>>>
>>>> [1] https://bugs.chromium.org/p/chromium/issues/detail?id=28291
>>> _______________________________________________
>>> 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
>>
>



From jc_gargma at iserlohn-fortress.net  Wed Nov 15 23:57:34 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Wed, 15 Nov 2017 15:57:34 -0800
Subject: [Dev] Orphan Libre package [kipi-plugins] marked out-of-date
In-Reply-To: <1521632.bjf1Z60nF5@iserlohn-fortress.net>
References: <20170704011849.1111.63457@proton.parabola.nu>
 <2456672.6fNLqgmKQ0@iserlohn-fortress.net>
 <1521632.bjf1Z60nF5@iserlohn-fortress.net>
Message-ID: <5175338.PZpMReLMfC@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update kipi-plugins to 5.7.0


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-kipi-plugins-to-5.7.0.patch
Type: text/x-patch
Size: 2583 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171115/ac96bb97/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171115/ac96bb97/attachment.sig>

From nobody at parabola.nu  Thu Nov 16 01:19:32 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 16 Nov 2017 01:19:32 -0000
Subject: [Dev] Orphan Nonprism package [webkitgtk] marked out-of-date
Message-ID: <20171116011932.1245.51570@proton.parabola.nu>

robsan at tutanota.com wants to notify you that the following packages may be out-of-date:




The user provided the following additional text:

I'm getting a message from my-privacy with the following message:

:: Starting full system upgrade...
warning: webkit2gtk: local (2.18.3-1) is newer than nonprism (2.18.2-1.nonprism1)




From lukeshu at lukeshu.com  Fri Nov 17 05:21:40 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Fri, 17 Nov 2017 00:21:40 -0500
Subject: [Dev] Winston / 1984 is feeling sad
Message-ID: <87efoxiior.wl-lukeshu@lukeshu.com>

TL;DR: 1984 is having issues with some of their infrastructure, I've
removed one of their DNS servers that seems down from
winston.parabola.nu's network config.

The process:
 - Try to install something with pacman
 - Get timeouts
 - Discover that repomirror is taking 5-10 seconds to respond to each
   request
 - Log on to winston, notice that repomirror is leaking memory, and
   eating all the swap
 - Restart repomirror at winston
 - Still slow
 - Profiling says waiting for
   <https://www.parabola.nu/mirrors/status/tier/1/json/> is taking the
   time
 - Log on to proton, see nothing obvious, but things are slow
 - See most of the swap space belongs to uwsgi processes; restart all
   uwsgi services on proton, see better iowait / latency
 - Verify that the mirrors json URL now comes back quickly
 - repomirror still slow
 - Mirrors json URL is only slow *from winston*.
 - ping says connection between winston and proton is plenty fast, but
   took a while to say it
 - Verify that DNS lookup of www.parabola.nu is what is slow (winston
   uses 1984's DNS)
 - Try to log in to 1984 management panel to see what's up
 - Can't log in, get "Sorry, but it seems the backend server is
   feeling sad." from 1984's site.
 - See in winston's /etc/netctl/... that there are 2 DNS servers
   configured.  Ping them each.
 - One seems to be totally down, the other seems fine.
 - Comment out the down one, reload net configuration
 - Everything seems happy now
 - Notice pbot is offline, assume bad DNS killed him, restart him

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sad.png
Type: image/png
Size: 45490 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171117/dba2ae6c/attachment.png>
-------------- next part --------------

-- 
Happy hacking,
~ Luke Shumaker

From megver83 at hyperbola.info  Sat Nov 18 18:59:40 2017
From: megver83 at hyperbola.info (Megver83)
Date: Sat, 18 Nov 2017 15:59:40 -0300
Subject: [Dev] [RFC] More init systems
Message-ID: <471b4a7f-4308-3ec0-e7b4-c0168f8bcdbc@hyperbola.info>

Since I've seen a lot of Arch-based distros offering not only OpenRC as
an alternative to Systemd but also other inits such as runit, s6, sinit,
busybox, daemontools, etc. I thought on why not doing the same.

I've added Runit[0][1] to [pcr] (I already tested it *a lot* to make it
work well). I "borrowed" the PKGBUILD from Artix, but did some
modifications to it so it provides /sbin/init.

As OpenRC can work well with the provided init program (it used to do
with sysvinit by default), I modified it to package openrc-init in a
separated package[3] called 'openrc-init' which, like the package
'runit', provides and conflicts 'init'.

Our runit version, different from Artix's, can (optionally) work with
OpenRC through 'runit-scripts'[1][4] which will invoke /sbin/openrc if
it exists[5]. As agetty is started by the init program (in this case
runit[6] of course), I've pulled /etc/{conf,init}.d/agetty.* from
'openrc' to 'openrc-init' (also the poweroff, shutdown, halt and reboot
scripts, which work only with openrc-shutdown. Maybe that binary I
should also move it to openrc-init).

Which are your thoughts on this? I thought on, later, add S6-rc from
Obarun[7], as it has many init scripts and looks more active[8] that
others like runit or sinit (which haven't got update for like 2-3 years,
but at least they KISS)

[0]
https://git.parabola.nu/abslibre.git/diff/pcr/runit/PKGBUILD?id=c799f6ae2ec796e75d399028736c9d70c021dcd7
[1]
https://git.parabola.nu/abslibre.git/diff/pcr/runit-scripts/PKGBUILD?id=c799f6ae2ec796e75d399028736c9d70c021dcd7
[3]
https://git.parabola.nu/abslibre.git/commit/?id=c799f6ae2ec796e75d399028736c9d70c021dcd7
[4] https://gitlab.com/Megver83/runit-scripts
[5] https://gitlab.com/Megver83/runit-scripts/blob/master/1#L5
[6] https://gitlab.com/Megver83/runit-scripts/blob/master/2
[7] https://web.obarun.org/
[8] https://git.skarnet.org/cgi-bin/cgit.cgi/s6/
-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171118/bf2552ae/attachment.sig>

From bill-auger at peers.community  Sat Nov 18 21:04:43 2017
From: bill-auger at peers.community (bill-auger)
Date: Sat, 18 Nov 2017 16:04:43 -0500
Subject: [Dev] [RFC] More init systems
In-Reply-To: <471b4a7f-4308-3ec0-e7b4-c0168f8bcdbc@hyperbola.info>
References: <471b4a7f-4308-3ec0-e7b4-c0168f8bcdbc@hyperbola.info>
Message-ID: <da838209-1264-9eeb-741b-2ef00bfa1304@peers.community>

GNU shepherd may also be an appropriate init system for parabola - it is
maintained by the guix team for guixSD

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171118/ab4d1ca9/attachment.sig>

From megver83 at hyperbola.info  Sat Nov 18 21:20:13 2017
From: megver83 at hyperbola.info (Megver83)
Date: Sat, 18 Nov 2017 18:20:13 -0300
Subject: [Dev] [RFC] More init systems
In-Reply-To: <da838209-1264-9eeb-741b-2ef00bfa1304@peers.community>
References: <471b4a7f-4308-3ec0-e7b4-c0168f8bcdbc@hyperbola.info>
 <da838209-1264-9eeb-741b-2ef00bfa1304@peers.community>
Message-ID: <035b1a48-8a66-1034-df4e-d8535ab7b283@hyperbola.info>

El 18/11/17 a las 18:04, bill-auger escribi?:
> GNU shepherd may also be an appropriate init system for parabola - it is
> maintained by the guix team for guixSD
> 
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 
Thanks for mentioning it, I forgot it. Yes, I think shepherd is also
getting into Parabola, after s6 and sinit

-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171118/08b67420/attachment.sig>

From nobody at parabola.nu  Sun Nov 19 20:10:29 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Sun, 19 Nov 2017 20:10:29 -0000
Subject: [Dev] Orphan Libre package [icecat] marked out-of-date
Message-ID: <20171119201029.26946.50914@proton.parabola.nu>

tplaten at posteo.de wants to notify you that the following packages may be out-of-date:


* icecat 52.3.0_gnu1-2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/icecat/
* icecat 52.3.0_gnu1-2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/icecat/
* icecat-debug 52.3.0_gnu1-2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/icecat-debug/
* icecat-debug 52.3.0_gnu1-2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/icecat-debug/


The user provided the following additional text:

icecat depends on an outdated icu, it cannot be installed at the moment



From nobody at parabola.nu  Sun Nov 19 21:13:56 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Sun, 19 Nov 2017 21:13:56 -0000
Subject: [Dev] Orphan Libre package [icedove] marked out-of-date
Message-ID: <20171119211356.26946.28835@proton.parabola.nu>

robsan at tutanota.com wants to notify you that the following packages may be out-of-date:


* icedove 1:52.4.0-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/icedove/
* icedove 1:52.4.0-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/icedove/


The user provided the following additional text:

error: failed to prepare transaction (could not satisfy dependencies)
:: icecat: installing icu (60.1-1) breaks dependency 'icu=59.1'
:: icedove: installing icu (60.1-1) breaks dependency 'icu=59.1'
:: iceweasel: installing icu (60.1-1) breaks dependency 'icu=59.1'



From lovell.joshyyy at gmail.com  Sun Nov 19 23:29:59 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Sun, 19 Nov 2017 23:29:59 +0000
Subject: [Dev] Patching a free version of BOINC
Message-ID: <5A1213F7.4060203@gmail.com>

This would be good. Like ct-ng, I am interested enough, so may try to 
make a patch I have time. It probably help if we could work out together 
which projects all_projects_list.xml [1] are free/non-free. Perhaps a 
wiki page/entry (again) would work.

Josh

[1] https://boinc.berkeley.edu/dev/forum_thread.php?id=10496


From lukeshu at lukeshu.com  Mon Nov 20 04:40:06 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Sun, 19 Nov 2017 23:40:06 -0500
Subject: [Dev] [RFC] More init systems
In-Reply-To: <035b1a48-8a66-1034-df4e-d8535ab7b283@hyperbola.info>
References: <471b4a7f-4308-3ec0-e7b4-c0168f8bcdbc@hyperbola.info>
 <da838209-1264-9eeb-741b-2ef00bfa1304@peers.community>
 <035b1a48-8a66-1034-df4e-d8535ab7b283@hyperbola.info>
Message-ID: <87vai54l7d.wl-lukeshu@lukeshu.com>

On Sat, 18 Nov 2017 16:20:13 -0500,
Megver83 wrote:
> El 18/11/17 a las 18:04, bill-auger escribi?:
> > GNU shepherd may also be an appropriate init system for parabola - it is
> > maintained by the guix team for guixSD
>
> Thanks for mentioning it, I forgot it. Yes, I think shepherd is also
> getting into Parabola, after s6 and sinit

+1

Most of the others to me are fun "because-we-can" things, but Shephard
is the only one that I'm actually interested in using.

-- 
Happy hacking,
~ Luke Shumaker


From eliotreyna at cock.email  Tue Nov 21 00:48:31 2017
From: eliotreyna at cock.email (eliotreyna at cock.email)
Date: Mon, 20 Nov 2017 19:48:31 -0500
Subject: [Dev] Iceweasel 57 status
Message-ID: <fe79d299865cbcc0b98aa3480fef0744@cock.email>

Greetings.

Since the release of Firefox 57 officially in wedmesday, existed some 
issues related to the release of Iceweasel. However, due to the big 
changes that has been made from the source code, exists a delay with the 
release of Iceweasel 57.

If we can help about the changes that has been made in the source code 
for apply the rebranding and/or another variables for make the browser 
free.

If we can improve the progress of Iceweasel 57, we can follow this 
developer release notes:
https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/57

PS: Can I make an Iceweasel rebrand for the version 59 for the release 
of Quantum source code for ESR branch?

Thanks.


From nobody at parabola.nu  Tue Nov 21 04:15:32 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 21 Nov 2017 04:15:32 -0000
Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date
Message-ID: <20171121041532.26947.10411@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* icecat-noscript 5.1.5-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-noscript/


The user provided the following additional text:

Current release is 5.1.7



From jc_gargma at iserlohn-fortress.net  Tue Nov 21 04:20:19 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Mon, 20 Nov 2017 20:20:19 -0800
Subject: [Dev] Orphan Libre package [icecat-noscript] marked out-of-date
In-Reply-To: <20171121041532.26947.10411@proton.parabola.nu>
References: <20171121041532.26947.10411@proton.parabola.nu>
Message-ID: <1809014.8dVBUU0HjN@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update icecat-noscript and iceweasel-
noscript to 5.1.7


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-icecat-iceweasel-noscript-to-5.1.7.patch
Type: text/x-patch
Size: 4658 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171120/b012f4d6/attachment.bin>
-------------- 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: <https://lists.parabola.nu/pipermail/dev/attachments/20171120/b012f4d6/attachment.sig>

From megver83 at hyperbola.info  Tue Nov 21 17:42:28 2017
From: megver83 at hyperbola.info (Megver83)
Date: Tue, 21 Nov 2017 14:42:28 -0300
Subject: [Dev] Iceweasel 57 status
In-Reply-To: <fe79d299865cbcc0b98aa3480fef0744@cock.email>
References: <fe79d299865cbcc0b98aa3480fef0744@cock.email>
Message-ID: <c2a61a47-1d10-0461-3df4-f5caee26241e@hyperbola.info>

El 20/11/17 a las 21:48, eliotreyna at cock.email escribi?:
> Greetings.
> 
> Since the release of Firefox 57 officially in wedmesday, existed some
> issues related to the release of Iceweasel. However, due to the big
> changes that has been made from the source code, exists a delay with the
> release of Iceweasel 57.
> 
> If we can help about the changes that has been made in the source code
> for apply the rebranding and/or another variables for make the browser
> free.

Andreas, its maintainer, just has to adapt the rebranding, if necessary.
I don't think, however, that it would be such a big deal.

> 
> If we can improve the progress of Iceweasel 57, we can follow this
> developer release notes:
> https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/57
> 
> PS: Can I make an Iceweasel rebrand for the version 59 for the release
> of Quantum source code for ESR branch?

If you know how to do it, of course. You should then get in contact with
oaken-source (Andreas's nick on IRC)

> 
> Thanks.
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171121/bde71b1d/attachment.sig>

From andreas at grapentin.org  Tue Nov 21 22:02:47 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Wed, 22 Nov 2017 07:02:47 +0900
Subject: [Dev] Iceweasel 57 status
In-Reply-To: <c2a61a47-1d10-0461-3df4-f5caee26241e@hyperbola.info>
References: <fe79d299865cbcc0b98aa3480fef0744@cock.email>
 <c2a61a47-1d10-0461-3df4-f5caee26241e@hyperbola.info>
Message-ID: <20171121220247.GA32275@parabola-pocket.localdomain>


Hi,

sorry I'll promptly get back to you guys, I am presently on a conference
and have limited time available.

I am aware of the iceweasel issue, and there are currently two problems
that need solving:

 a) the branding patches are broken and need to be updated
 b) firefox-57 has removed support for legacy extensions, so all addon
    packages need to be verified if they still work. At least noscript
    needs to migrate to 10.x

I hope I'll get to doing that today or tomorrow.

I am not sure if we particularily need an iceweasel-esr version, that
role has typically been filled by icecat, which will probably switch to
59 soon as well, once all the issues are ironed out, but it can't hurt I
guess. But that's an issue I'd assign a lower priority to, unless
someone sais it's important to them :)

Best,
Andreas

On Tue, Nov 21, 2017 at 02:42:28PM -0300, Megver83 wrote:
> El 20/11/17 a las 21:48, eliotreyna at cock.email escribi?:
> > Greetings.
> > 
> > Since the release of Firefox 57 officially in wedmesday, existed some
> > issues related to the release of Iceweasel. However, due to the big
> > changes that has been made from the source code, exists a delay with the
> > release of Iceweasel 57.
> > 
> > If we can help about the changes that has been made in the source code
> > for apply the rebranding and/or another variables for make the browser
> > free.
> 
> Andreas, its maintainer, just has to adapt the rebranding, if necessary.
> I don't think, however, that it would be such a big deal.
> 
> > 
> > If we can improve the progress of Iceweasel 57, we can follow this
> > developer release notes:
> > https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/57
> > 
> > PS: Can I make an Iceweasel rebrand for the version 59 for the release
> > of Quantum source code for ESR branch?
> 
> If you know how to do it, of course. You should then get in contact with
> oaken-source (Andreas's nick on IRC)
> 
> > 
> > Thanks.
> > _______________________________________________
> > Dev mailing list
> > Dev at lists.parabola.nu
> > https://lists.parabola.nu/mailman/listinfo/dev
> 
> 
> -- 
> ~Megver83
> 
> SIP: megver83 at sip.linphone.org
> XMPP: megver83 at jabjab.de
> Tox: megver83 at toxme.io
> GPG: 0x227CA7C556B2BA78
> GNUSocial: @megver82 at quitter.cl
> Diaspora*: megver83 at diasp.org
> Matrix: @Megver83:matrix.org
> 




> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171122/dde665dd/attachment.sig>

From megver83 at hyperbola.info  Tue Nov 21 22:48:05 2017
From: megver83 at hyperbola.info (Megver83)
Date: Tue, 21 Nov 2017 19:48:05 -0300
Subject: [Dev] Iceweasel 57 status
In-Reply-To: <20171121220247.GA32275@parabola-pocket.localdomain>
References: <fe79d299865cbcc0b98aa3480fef0744@cock.email>
 <c2a61a47-1d10-0461-3df4-f5caee26241e@hyperbola.info>
 <20171121220247.GA32275@parabola-pocket.localdomain>
Message-ID: <4692788b-ae65-46ca-21eb-94831354f066@hyperbola.info>

El 21/11/17 a las 19:02, Andreas Grapentin escribi?:
> 
> Hi,
> 
> sorry I'll promptly get back to you guys, I am presently on a conference
> and have limited time available.
> 
> I am aware of the iceweasel issue, and there are currently two problems
> that need solving:
> 
>  a) the branding patches are broken and need to be updated
>  b) firefox-57 has removed support for legacy extensions, so all addon
>     packages need to be verified if they still work. At least noscript
>     needs to migrate to 10.x
> 
> I hope I'll get to doing that today or tomorrow.
> 
> I am not sure if we particularily need an iceweasel-esr version, that
> role has typically been filled by icecat, which will probably switch to
> 59 soon as well, once all the issues are ironed out, but it can't hurt I
> guess. But that's an issue I'd assign a lower priority to, unless
> someone sais it's important to them :)
> 
> Best,
> Andreas
> 

Right, well in that case you can try to get the rebranding for these new
versions and upload iceweasel on [libre-testing] until we've migrated
all the extensions from the iceweasel-addons group (which may also go to
[libre-testing] if the testing version of iceweasel is there)

-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171121/f47f8eac/attachment.sig>

From happy_gnu at teknik.io  Wed Nov 22 02:17:42 2017
From: happy_gnu at teknik.io (happy gnu)
Date: Tue, 21 Nov 2017 20:17:42 -0600
Subject: [Dev] Iceweasel 57 status
In-Reply-To: <20171121220247.GA32275@parabola-pocket.localdomain>
References: <fe79d299865cbcc0b98aa3480fef0744@cock.email>
 <c2a61a47-1d10-0461-3df4-f5caee26241e@hyperbola.info>
 <20171121220247.GA32275@parabola-pocket.localdomain>
Message-ID: <69752a1a-a029-7fda-56dd-ca5cc477de84@teknik.io>

NoScript has already migrated and works in Quantum now, you can verify
it here:

https://noscript.net/

Also I have it working on Nightly, is kind of bad UI, but is there at
last and it worksk.


El 21/11/17 a las 16:02, Andreas Grapentin escribi?:
> Hi,
>
> sorry I'll promptly get back to you guys, I am presently on a conference
> and have limited time available.
>
> I am aware of the iceweasel issue, and there are currently two problems
> that need solving:
>
>  a) the branding patches are broken and need to be updated
>  b) firefox-57 has removed support for legacy extensions, so all addon
>     packages need to be verified if they still work. At least noscript
>     needs to migrate to 10.x
>
> I hope I'll get to doing that today or tomorrow.
>
> I am not sure if we particularily need an iceweasel-esr version, that
> role has typically been filled by icecat, which will probably switch to
> 59 soon as well, once all the issues are ironed out, but it can't hurt I
> guess. But that's an issue I'd assign a lower priority to, unless
> someone sais it's important to them :)
>
> Best,
> Andreas
>
> On Tue, Nov 21, 2017 at 02:42:28PM -0300, Megver83 wrote:
>> El 20/11/17 a las 21:48, eliotreyna at cock.email escribi?:
>>> Greetings.
>>>
>>> Since the release of Firefox 57 officially in wedmesday, existed some
>>> issues related to the release of Iceweasel. However, due to the big
>>> changes that has been made from the source code, exists a delay with the
>>> release of Iceweasel 57.
>>>
>>> If we can help about the changes that has been made in the source code
>>> for apply the rebranding and/or another variables for make the browser
>>> free.
>> Andreas, its maintainer, just has to adapt the rebranding, if necessary.
>> I don't think, however, that it would be such a big deal.
>>
>>> If we can improve the progress of Iceweasel 57, we can follow this
>>> developer release notes:
>>> https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/57
>>>
>>> PS: Can I make an Iceweasel rebrand for the version 59 for the release
>>> of Quantum source code for ESR branch?
>> If you know how to do it, of course. You should then get in contact with
>> oaken-source (Andreas's nick on IRC)
>>
>>> Thanks.
>>> _______________________________________________
>>> Dev mailing list
>>> Dev at lists.parabola.nu
>>> https://lists.parabola.nu/mailman/listinfo/dev
>>
>> -- 
>> ~Megver83
>>
>> SIP: megver83 at sip.linphone.org
>> XMPP: megver83 at jabjab.de
>> Tox: megver83 at toxme.io
>> GPG: 0x227CA7C556B2BA78
>> GNUSocial: @megver82 at quitter.cl
>> Diaspora*: megver83 at diasp.org
>> Matrix: @Megver83:matrix.org
>>
>
>
>
>> _______________________________________________
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171121/6eb298fa/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171121/6eb298fa/attachment.sig>

From powers at copper.net  Sat Nov 25 00:27:29 2017
From: powers at copper.net (powers at copper.net)
Date: Fri, 24 Nov 2017 16:27:29 -0800
Subject: [Dev] OpenRC editions
Message-ID: <20171124162729.30F20A5E@m0117460.ppops.net>

An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171124/940f2473/attachment.htm>

From megver83 at hyperbola.info  Sat Nov 25 17:30:06 2017
From: megver83 at hyperbola.info (Megver83)
Date: Sat, 25 Nov 2017 14:30:06 -0300
Subject: [Dev] OpenRC editions
In-Reply-To: <20171124162729.30F20A5E@m0117460.ppops.net>
References: <20171124162729.30F20A5E@m0117460.ppops.net>
Message-ID: <7360ac56-2dda-d284-8c78-ee9fa9496713@hyperbola.info>

El 24/11/17 a las 21:27, powers at copper.net escribi?:
> Happy to see your OpenRC editions.? Interested in getting away from
> systemd where possible.
> .

:)

> Live CDs look great.? Installed both Mate & Lxde initial releases to usb
> thumb drives for testing.
> No usable X-windows on either one - only twm, caja, & not much else.
> 

OpenRC-MATE is unsupported and no longer maintained. Do not use

> Installed 2nd release of Lxde - no auto start of X and no login
> manager.? Login from command
> line, ran startx, enable wifi, ran updates.? All good.? Installed Xfce
> (my preferred desktop), added
> it to my .initrc, rebooted, login, and startx brings me into Xfce.? Also
> installed Mate but so far
> haven't figured out how to start it.
> 
> Anxiously awaiting the next release.? Keep up the good work.? I still
> use the 16.03 Mate systemd
> release with Xfce added,? but expect to switch to the OpenRC version
> when it matures.? Thanks
> for all your hard work.

Next release? why? do I missed sth? everything was tested and proved to
work. If I launch a second release, would be to include
archlinux32-keyring (which I plan to do when linux-libre 4.14 gets into
[libre])

> 
> Incidentally, I tried the 17.05 Mate dual iso and encountered several
> other problems besides the
> no-desktop-icons bug, so did not try to install it.? No such problems
> with the 16.03 release.

Do not use MATE ISOs. Not even the old systemd ISO, because it's too
outdated.

> 
> Carl
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 


-- 
~Megver83

SIP: megver83 at sip.linphone.org
XMPP: megver83 at jabjab.de
Tox: megver83 at toxme.io
GPG: 0x227CA7C556B2BA78
GNUSocial: @megver82 at quitter.cl
Diaspora*: megver83 at diasp.org
Matrix: @Megver83:matrix.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171125/9cab8b2b/attachment.sig>

From nobody at parabola.nu  Sun Nov 26 07:58:39 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Sun, 26 Nov 2017 07:58:39 -0000
Subject: [Dev] Orphan Pcr package [imagemagick-nox] marked out-of-date
Message-ID: <20171126075839.26947.49813@proton.parabola.nu>

lists+dev-parabolagnulinux at donderklumpen.de wants to notify you that the following packages may be out-of-date:


* imagemagick-nox 6.9.0.5-2 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/imagemagick-nox/
* imagemagick-nox 6.9.0.5-2 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/imagemagick-nox/


The user provided the following additional text:

Is this package still being maintained?

imagemagick-nox current version is 6.9.0.5-2 [pcr] (x86_64) dating back to 2015-03-22 while imagemagick version is 6.9.9.23-1.

upgrading the system, pacman throws this warning:
running 'detect-old-perl-modules.hook'...
WARNING: '/usr/lib/perl5/vendor_perl' contains data from at least 1 packages which will NOT be used by the installed perl interpreter.
-> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/vendor_perl'

pacman -Qqo '/usr/lib/perl5/vendor_perl' then shows
imagemagick-nox



From jc_gargma at iserlohn-fortress.net  Tue Nov 28 18:09:52 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 28 Nov 2017 10:09:52 -0800
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
In-Reply-To: <20171113185947.GA1020@parabola-pocket.localdomain>
References: <20171113184846.1244.71257@proton.parabola.nu>
 <167884637.iPegsGXH93@iserlohn-fortress.net>
 <20171113185947.GA1020@parabola-pocket.localdomain>
Message-ID: <2572736.AuDWCX5kz0@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to hotfix kio due to a folder creation bug 
introduced by Qt 5.9.3


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-kio-Hotfix-folder-creation-bug-induced-by-Qt-5.9.3.patch
Type: text/x-patch
Size: 2418 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/a700483a/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/a700483a/attachment.sig>

From andreas at grapentin.org  Tue Nov 28 18:19:19 2017
From: andreas at grapentin.org (Andreas Grapentin)
Date: Tue, 28 Nov 2017 19:19:19 +0100
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
In-Reply-To: <2572736.AuDWCX5kz0@iserlohn-fortress.net>
References: <20171113184846.1244.71257@proton.parabola.nu>
 <167884637.iPegsGXH93@iserlohn-fortress.net>
 <20171113185947.GA1020@parabola-pocket.localdomain>
 <2572736.AuDWCX5kz0@iserlohn-fortress.net>
Message-ID: <20171128181919.GA32241@parabola-pocket.localdomain>


the patch doesn't include contents of kio-new-folder*.patch - is this
intentional?

-A

On Tue, Nov 28, 2017 at 10:09:52AM -0800, jc_gargma wrote:
> > The user provided the following additional text:
> I've attached a git format-patch to hotfix kio due to a folder creation bug 
> introduced by Qt 5.9.3
> 
> 
> -jc

> From b5c30c84020302dcfb9064b924143c66b2a108ad Mon Sep 17 00:00:00 2001
> From: jc_gargma <jc_gargma at iserlohn-fortress.net>
> Date: Tue, 28 Nov 2017 10:00:51 -0800
> Subject: [PATCH] kio/Hotfix folder creation bug induced by Qt 5.9.3
> 
> ---
>  libre/kio/PKGBUILD | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/libre/kio/PKGBUILD b/libre/kio/PKGBUILD
> index 39cea862f..7a8507c28 100644
> --- a/libre/kio/PKGBUILD
> +++ b/libre/kio/PKGBUILD
> @@ -7,7 +7,7 @@
>  pkgname=kio
>  
>  pkgver=5.40.0
> -pkgrel=1.parabola1
> +pkgrel=3.parabola1
>  arch=(i686 x86_64 armv7h)
>  
>  pkgdesc="Resource and network access abstraction, without non-privacy search engines"
> @@ -23,11 +23,15 @@ groups=(kf5)
>  
>  source=("https://download.kde.org/stable/frameworks/${pkgver%.*}/$pkgname-$pkgver.tar.xz"{,.sig}
>          "duckduckgo_html.desktop"
> -        "duckduckgo_lite.desktop")
> +        "duckduckgo_lite.desktop"
> +        kio-new-folder.patch::"https://cgit.kde.org/kio.git/patch/?id=2353119a"
> +        kio-new-folder2.patch::"https://cgit.kde.org/kio.git/patch/?id=298c0e73")
>  sha256sums=('30ea0b231b995faaf4283b9c9ecfaffb589268f5d7b5b805f69ed95601ac389b'
>              'SKIP'
>              '31910ab7393e67609f15e04a57f6406f63e6dae58b01bce0787741bc5958f292'
> -            '40466a9dad7075f2525e9e024720da7d7b49a22892b6fca8b81cc0e6408d2f7d')
> +            '40466a9dad7075f2525e9e024720da7d7b49a22892b6fca8b81cc0e6408d2f7d'
> +            '12066a895dc95e7892260044ad9e6fdd242b9b24b914f556e8505489926bf1a6'
> +            'ff8de054b53b14c0917689a80245558502a03ef8ac42f187b10180227724d5f4')
>  validpgpkeys=(53E6B47B45CEA3E0D5B7457758D0EE648A48B3BB) # David Faure <faure at kde.org>
>  
>  prepare() {
> @@ -35,6 +39,10 @@ prepare() {
>  
>    cd $pkgname-$pkgver
>  
> +  # Fix creating new folders with Qt 5.9.3
> +  patch -p1 -i ../kio-new-folder.patch
> +  patch -p1 -i ../kio-new-folder2.patch
> +
>    # Removing non-privacy search providers
>    rm -v src/urifilters/ikws/searchproviders/{7digital,acronym,amazon{,_mp3},amg,backports,baidu,bing,blip,cia,dbug,deb,duckduckgo{,_info,_shopping},facebook,ecosia,feedster,flickr,flickrcc,google,google_advanced,google_code,google_groups,google_images,google_lucky,google_maps,google_movie,google_news,google_shopping,imdb,jamendo,jeeves,magnatune,metacrawler,msdn,nl-telephone,nl-teletekst,python,rpmfind,tvtome,uspto,vimeo,voila,yahoo,yahoo_image,yahoo_local,yahoo_shopping,yahoo_video,youtube}.desktop
>  
> -- 
> 2.15.0
> 




> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

------------------------------------------------------------------------------
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/3b91be2c/attachment.sig>

From nobody at parabola.nu  Tue Nov 28 18:22:08 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Tue, 28 Nov 2017 18:22:08 -0000
Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date
Message-ID: <20171128182208.26947.45709@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* kinfocenter 5.10.5-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kinfocenter/
* kinfocenter 5.11.3-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kinfocenter/
* kinfocenter 5.11.3-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kinfocenter/


The user provided the following additional text:

Current release is 5.11.4



From jc_gargma at iserlohn-fortress.net  Tue Nov 28 18:31:59 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 28 Nov 2017 10:31:59 -0800
Subject: [Dev] Orphan Libre package [kio] marked out-of-date
In-Reply-To: <20171128181919.GA32241@parabola-pocket.localdomain>
References: <20171113184846.1244.71257@proton.parabola.nu>
 <2572736.AuDWCX5kz0@iserlohn-fortress.net>
 <20171128181919.GA32241@parabola-pocket.localdomain>
Message-ID: <4682277.tgJLtCVGA7@iserlohn-fortress.net>

> the patch doesn't include contents of kio-new-folder*.patch - is this
> intentional?
It's a direct copy of what Arch is doing upstream. I can update the commit to 
include them directly if that is preferred.


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/04b9b484/attachment.sig>

From jc_gargma at iserlohn-fortress.net  Tue Nov 28 18:33:09 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Tue, 28 Nov 2017 10:33:09 -0800
Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date
In-Reply-To: <20171128182208.26947.45709@proton.parabola.nu>
References: <20171128182208.26947.45709@proton.parabola.nu>
Message-ID: <9510258.mnEZijzp5A@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update kinfocenter and khetkeys to 5.11.4


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-kinfocenter-and-khotkeys-to-5.11.4.patch
Type: text/x-patch
Size: 2012 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/09483879/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171128/09483879/attachment.sig>

From lukeshu at lukeshu.com  Wed Nov 29 22:16:13 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Wed, 29 Nov 2017 17:16:13 -0500
Subject: [Dev] Winston network usage
Message-ID: <87shcwras2.wl-lukeshu@lukeshu.com>

Hi,

As you know, 1984 web hosting graciously donates the
winston.parabola.nu server.  They have assigned it a transfer "quota"
of 900.00 GB/month; we have transferred 1461.80 GB in the last month.
I assume what normally happens when you go over is you get billed;
since we have "Free service", that hasn't happened.  1984 hasn't said
anything to us about it, but I'd like to be courteous and stay within
the quota.

My first reaction was to suggest that we demote most of the mirrors to
be tier-2, and have them sync with tier-1 instead of with winston
(tier-0).  But, looking a bit closer at the control panel, it seems
that the bulk of it is winston *receiving* data:

     - Transfer quota:: 900.00 GB/month
     - Received: 1352.28 GB
     - Transmitted: 109.52 GB
     - Total: 1461.80 GB

    [[[[[[[[[[[[[[[[[   162%   ]]]]]]]]]]]]]]]]]

Beside being rude to 1984/their other customers, that is alarming to
me.  I'd like to at least know what all that data is.  Someone (maybe
me) should look in to this in the coming days.

-- 
Happy hacking,
~ Luke Shumaker


From lovell.joshyyy at gmail.com  Wed Nov 29 22:34:15 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 29 Nov 2017 22:34:15 +0000
Subject: [Dev] Winston network usage
In-Reply-To: <87shcwras2.wl-lukeshu@lukeshu.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com>
Message-ID: <5A1F35E7.6070302@gmail.com>

On 29/11/17 22:16, Luke Shumaker wrote:
> Hi,
>
> As you know, 1984 web hosting graciously donates the
> winston.parabola.nu server.  They have assigned it a transfer "quota"
> of 900.00 GB/month; we have transferred 1461.80 GB in the last month.
> I assume what normally happens when you go over is you get billed;
> since we have "Free service", that hasn't happened.  1984 hasn't said
> anything to us about it, but I'd like to be courteous and stay within
> the quota.
>
> My first reaction was to suggest that we demote most of the mirrors to
> be tier-2, and have them sync with tier-1 instead of with winston
> (tier-0).  But, looking a bit closer at the control panel, it seems
> that the bulk of it is winston *receiving* data:
>
>       - Transfer quota:: 900.00 GB/month
>       - Received: 1352.28 GB
>       - Transmitted: 109.52 GB
>       - Total: 1461.80 GB
>
>      [[[[[[[[[[[[[[[[[   162%   ]]]]]]]]]]]]]]]]]
>
> Beside being rude to 1984/their other customers, that is alarming to
> me.  I'd like to at least know what all that data is.  Someone (maybe
> me) should look in to this in the coming days.
>

Do those numbers even make sense?

How big is the hard disk?

Is it bigger than 1242.76GB (1352.28 - 109.52)?

Josh


From lukeshu at lukeshu.com  Wed Nov 29 22:44:24 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Wed, 29 Nov 2017 17:44:24 -0500
Subject: [Dev] Winston network usage
In-Reply-To: <5A1F35E7.6070302@gmail.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com>
	<5A1F35E7.6070302@gmail.com>
Message-ID: <87r2sgr9h3.wl-lukeshu@lukeshu.com>

On Wed, 29 Nov 2017 17:34:15 -0500,
Josh Branning wrote:
> On 29/11/17 22:16, Luke Shumaker wrote:
> >       - Transfer quota:: 900.00 GB/month
> >       - Received: 1352.28 GB
> >       - Transmitted: 109.52 GB
> >       - Total: 1461.80 GB
> 
> Do those numbers even make sense?
> 
> How big is the hard disk?
> 
> Is it bigger than 1242.76GB (1352.28 - 109.52)?

It's a 500GB disk.

-- 
Happy hacking,
~ Luke Shumaker


From lovell.joshyyy at gmail.com  Wed Nov 29 22:46:54 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 29 Nov 2017 22:46:54 +0000
Subject: [Dev] Winston network usage
In-Reply-To: <87r2sgr9h3.wl-lukeshu@lukeshu.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com> <5A1F35E7.6070302@gmail.com>
 <87r2sgr9h3.wl-lukeshu@lukeshu.com>
Message-ID: <5A1F38DE.10503@gmail.com>

On 29/11/17 22:44, Luke Shumaker wrote:
> On Wed, 29 Nov 2017 17:34:15 -0500,
> Josh Branning wrote:
>> On 29/11/17 22:16, Luke Shumaker wrote:
>>>        - Transfer quota:: 900.00 GB/month
>>>        - Received: 1352.28 GB
>>>        - Transmitted: 109.52 GB
>>>        - Total: 1461.80 GB
>>
>> Do those numbers even make sense?
>>
>> How big is the hard disk?
>>
>> Is it bigger than 1242.76GB (1352.28 - 109.52)?
>
> It's a 500GB disk.
>

In that case I guess it could be downloading then purging, or getting 
flooded with requests. Either wouldn't require disk space.

Josh


From lovell.joshyyy at gmail.com  Wed Nov 29 23:01:52 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 29 Nov 2017 23:01:52 +0000
Subject: [Dev] Winston network usage
In-Reply-To: <5A1F38DE.10503@gmail.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com> <5A1F35E7.6070302@gmail.com>
 <87r2sgr9h3.wl-lukeshu@lukeshu.com> <5A1F38DE.10503@gmail.com>
Message-ID: <5A1F3C60.1050308@gmail.com>

On 29/11/17 22:46, Josh Branning wrote:
> On 29/11/17 22:44, Luke Shumaker wrote:
>> On Wed, 29 Nov 2017 17:34:15 -0500,
>> Josh Branning wrote:
>>> On 29/11/17 22:16, Luke Shumaker wrote:
>>>>        - Transfer quota:: 900.00 GB/month
>>>>        - Received: 1352.28 GB
>>>>        - Transmitted: 109.52 GB
>>>>        - Total: 1461.80 GB
>>>
>>> Do those numbers even make sense?
>>>
>>> How big is the hard disk?
>>>
>>> Is it bigger than 1242.76GB (1352.28 - 109.52)?
>>
>> It's a 500GB disk.
>>
>
> In that case I guess it could be downloading then purging, or getting
> flooded with requests. Either wouldn't require disk space.
>
> Josh

Not much you can do about the latter (the requests will go down the wire 
either way, even if the server does not respond), so basically about all 
you can do is check on the former in this regard.

Josh


From bill-auger at peers.community  Wed Nov 29 23:14:35 2017
From: bill-auger at peers.community (bill-auger)
Date: Wed, 29 Nov 2017 18:14:35 -0500
Subject: [Dev] Winston network usage
In-Reply-To: <5A1F38DE.10503@gmail.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com> <5A1F35E7.6070302@gmail.com>
 <87r2sgr9h3.wl-lukeshu@lukeshu.com> <5A1F38DE.10503@gmail.com>
Message-ID: <a077a3c4-d20b-6bc7-0f8e-0492a29cbbe3@peers.community>

one thing that comes to mind is the large number of ISO files i have
been uploading which are all being mirrored as they appear - the total
size of all new ISOs is about 30GB (x6 mirrors = 180GB) so i would think
that could not account for all the extra bandwidth but it is significant

also that is not accounting for any users downloading them - as i
mentioned in a previous thread, the wiki hyperlinks to all of the
previous ISOs pass ?noredirect to repo.parabola.nu - i have since been
adding the new beta ISOs without that flag but the new openrc ISOs which
seem to be popular specify ?noredirect

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171129/6cf6d3dd/attachment.sig>

From lovell.joshyyy at gmail.com  Wed Nov 29 23:28:59 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Wed, 29 Nov 2017 23:28:59 +0000
Subject: [Dev] Winston network usage
In-Reply-To: <a077a3c4-d20b-6bc7-0f8e-0492a29cbbe3@peers.community>
References: <87shcwras2.wl-lukeshu@lukeshu.com> <5A1F35E7.6070302@gmail.com>
 <87r2sgr9h3.wl-lukeshu@lukeshu.com> <5A1F38DE.10503@gmail.com>
 <a077a3c4-d20b-6bc7-0f8e-0492a29cbbe3@peers.community>
Message-ID: <5A1F42BB.6050202@gmail.com>

On 29/11/17 23:14, bill-auger wrote:
> one thing that comes to mind is the large number of ISO files i have
> been uploading which are all being mirrored as they appear - the total
> size of all new ISOs is about 30GB (x6 mirrors = 180GB) so i would think
> that could not account for all the extra bandwidth but it is significant

If 1984 hosts more than one server and the received figure was for those 
6 mirrors also, it would make sense.

If the figures are for a single server and not the mirrors, then it 
wouldn't, as only ~30GB would have been received by that server in 
relation to the ISOs.

That said the mirrors would have to download from the server, and ~180GB 
is greater than the transmitted figure (109.52), which generally leads 
me to believe the transfer quota figures aren't right.

>
> also that is not accounting for any users downloading them - as i
> mentioned in a previous thread, the wiki hyperlinks to all of the
> previous ISOs pass ?noredirect to repo.parabola.nu - i have since been
> adding the new beta ISOs without that flag but the new openrc ISOs which
> seem to be popular specify ?noredirect

But the issue isn't so much with what's transmitted from the server 
(downloads), the bulk of the problem is in theory lots of data being 
either requested or uploaded to the server ie. received (and then purged).

Josh


From nobody at parabola.nu  Thu Nov 30 00:13:58 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 30 Nov 2017 00:13:58 -0000
Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked out-of-date
Message-ID: <20171130001358.26946.23746@proton.parabola.nu>

jc_gargma at iserlohn-fortress.net wants to notify you that the following packages may be out-of-date:


* icecat-ublock-origin 1.14.18-1 [libre] (any): https://parabolagnulinux.org/packages/libre/any/icecat-ublock-origin/


The user provided the following additional text:

Current release is 1.14.20



From jc_gargma at iserlohn-fortress.net  Thu Nov 30 00:16:50 2017
From: jc_gargma at iserlohn-fortress.net (jc_gargma)
Date: Wed, 29 Nov 2017 16:16:50 -0800
Subject: [Dev] Orphan Libre package [icecat-ublock-origin] marked
 out-of-date
In-Reply-To: <20171130001358.26946.23746@proton.parabola.nu>
References: <20171130001358.26946.23746@proton.parabola.nu>
Message-ID: <3881105.P9d7gNdTel@iserlohn-fortress.net>

> The user provided the following additional text:
I've attached a git format-patch to update icecat/iceweasel-ublock-origin to 
1.14.20


-jc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-icecat-iceweasel-ublock-origin-to-1.14.20.patch
Type: text/x-patch
Size: 1847 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171129/9a704ca5/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171129/9a704ca5/attachment.sig>

From nobody at parabola.nu  Thu Nov 30 08:45:11 2017
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 30 Nov 2017 08:45:11 -0000
Subject: [Dev] Orphan Pcr package [pycryptopp] marked out-of-date
Message-ID: <20171130084511.26947.56849@proton.parabola.nu>

arunisaac at systemreboot.net wants to notify you that the following packages may be out-of-date:


* pycryptopp 0.6.0-2 [pcr] (i686): https://parabolagnulinux.org/packages/pcr/i686/pycryptopp/
* pycryptopp 0.6.0-2 [pcr] (x86_64): https://parabolagnulinux.org/packages/pcr/x86_64/pycryptopp/


The user provided the following additional text:

Version 0.7.1 is available. Could you please update?

Thanks for maintaining this package.



From adfeno at hyperbola.info  Thu Nov 30 12:02:11 2017
From: adfeno at hyperbola.info (Adonay Felipe Nogueira)
Date: Thu, 30 Nov 2017 10:02:11 -0200
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <5A0C9EC3.7040006@gmail.com> (Josh Branning's message of "Wed, 15
 Nov 2017 20:08:35 +0000")
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
 <87bmk3xqff.fsf@hyperbola.info> <5A0C9EC3.7040006@gmail.com>
Message-ID: <87zi74560s.fsf@hyperbola.info>

See the update in the related thread. I'm seeding the text file.

2017-11-15T20:08:35+0000 Josh Branning wrote:
> Thank you for this.
>
> Could I also request you upload the text file(s) somewhere? I can't
> seem to download them from the lists.gnu.org archive, and that may be
> a problem for people who wish to help try and clarify the licenses.
>
> May also be worth creating a pad, and seeing if people are willing to
> help if it's a long list?
>
> Josh


From fauno at endefensadelsl.org  Thu Nov 30 14:19:04 2017
From: fauno at endefensadelsl.org (fauno)
Date: Thu, 30 Nov 2017 11:19:04 -0300
Subject: [Dev] Winston network usage
In-Reply-To: <87shcwras2.wl-lukeshu@lukeshu.com>
References: <87shcwras2.wl-lukeshu@lukeshu.com>
Message-ID: <87o9njonmv.fsf@endefensadelsl.org>

Luke Shumaker <lukeshu at lukeshu.com> writes:
> Beside being rude to 1984/their other customers, that is alarming to
> me.  I'd like to at least know what all that data is.  Someone (maybe
> me) should look in to this in the coming days.

do we have vnstat or some other network monitor on winston?

-- 
https://lainventoria.com.ar/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 617 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20171130/89e741f4/attachment.sig>

From lovell.joshyyy at gmail.com  Thu Nov 30 14:35:14 2017
From: lovell.joshyyy at gmail.com (Josh Branning)
Date: Thu, 30 Nov 2017 14:35:14 +0000
Subject: [Dev] Is Iridium safe to use?
In-Reply-To: <87zi74560s.fsf@hyperbola.info>
References: <b59d4e1d-dca8-e3ce-f599-48adb280ade2@sohka.eu>
 <fa9584e4-43a1-4e09-8c08-f864a4d20842@hyperbola.info>
 <20171026043517.GA24177@parabola-pocket.localdomain>
 <1ab38e36-b2a6-fd52-1e15-3606fd569495@sohka.eu>
 <da374989-b85b-b6c3-dd95-870761ee5768@hyperbola.info>
 <1510341620.20307.0@plebeian.isacdaavid.info>
 <309d919c-64ae-952b-1451-504bab40c50b@teknik.io>
 <3ea54e1a-5e48-6d8e-4101-0a5488f86cd4@peers.community>
 <87zi7nxzmc.fsf@hyperbola.info> <5A0C94FE.1070906@gmail.com>
 <87bmk3xqff.fsf@hyperbola.info> <5A0C9EC3.7040006@gmail.com>
 <87zi74560s.fsf@hyperbola.info>
Message-ID: <5A201722.5030805@gmail.com>

That's marvelous, thanks again,

Josh

On 30/11/17 12:02, Adonay Felipe Nogueira wrote:
> See the update in the related thread. I'm seeding the text file.
>
> 2017-11-15T20:08:35+0000 Josh Branning wrote:
>> Thank you for this.
>>
>> Could I also request you upload the text file(s) somewhere? I can't
>> seem to download them from the lists.gnu.org archive, and that may be
>> a problem for people who wish to help try and clarify the licenses.
>>
>> May also be worth creating a pad, and seeing if people are willing to
>> help if it's a long list?
>>
>> Josh
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
>



From lukeshu at lukeshu.com  Thu Nov 30 15:53:10 2017
From: lukeshu at lukeshu.com (Luke Shumaker)
Date: Thu, 30 Nov 2017 10:53:10 -0500
Subject: [Dev] Winston network usage
In-Reply-To: <87o9njonmv.fsf@endefensadelsl.org>
References: <87shcwras2.wl-lukeshu@lukeshu.com>
 <87o9njonmv.fsf@endefensadelsl.org>
Message-ID: <87o9njrcex.wl-lukeshu@lukeshu.com>

On Thu, 30 Nov 2017 09:19:04 -0500,
fauno wrote:
> Luke Shumaker <lukeshu at lukeshu.com> writes:
> > Beside being rude to 1984/their other customers, that is alarming to
> > me.  I'd like to at least know what all that data is.  Someone (maybe
> > me) should look in to this in the coming days.
> 
> do we have vnstat or some other network monitor on winston?

collectd is logging eth0 throughput

https://winston.parabola.nu/collectd/winston.parabola.nu/interface-eth0/

-- 
Happy hacking,
~ Luke Shumaker