From somenxavier at posteo.net  Wed Aug  1 13:15:54 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Wed, 1 Aug 2018 14:15:54 +0200
Subject: [Assist] Some packages are incompatible with your-initfreedom
Message-ID: <20180801141554.5e4a38e21269dc24a4adc8ef@posteo.net>

I have parabola with openrc installed. I want to upgrade but I get:

:: your-initfreedom i libsystemd-dummy tenen conflictes (libsystemd). Elimino libsystemd-dummy? [s/N] s
:: your-initfreedom i systemd-dummy tenen conflictes (systemd). Elimino systemd-dummy? [s/N] s
Error: ha fallat preparar la transacci? (no s'han pogut satisfer les depend?ncies)
:: no es pot satisfer la depend?ncia "libsystemd" requerida per device-mapper
:: no es pot satisfer la depend?ncia "libsystemd" requerida per dhcpcd
:: no es pot satisfer la depend?ncia "systemd" requerida per lighttpd
:: no es pot satisfer la depend?ncia "libsystemd" requerida per lvm2
:: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per libusb
:: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per pcmciautils
:: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per procps-ng
:: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per rpcbind
:: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per syslog-ng



So procps-ng, rpcbind, syslog-ng, libusb, pcmciautils, lvm2, lighttpd, dhcpcd, device-mapper are incompatible with your-initfreedom. What can I do?

Thanks in advance,
Xavier

From somenxavier at posteo.net  Wed Aug  1 13:23:32 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Wed, 1 Aug 2018 14:23:32 +0200
Subject: [Assist] Fw: Re: Unable to boot my parabola "error while loading
 shared libraries libjson-c.so.4"
Message-ID: <20180801142332.80f15db50c10335c1be090d3@posteo.net>



Begin forwarded message:

Date: Sun, 22 Jul 2018 15:22:03 +0200
From: "Xavier B." <somenxavier at posteo.net>
To: Luke Shumaker <lukeshu at lukeshu.com>
Cc: assist at lists.parabola.nu
Subject: Re: [Assist] Unable to boot my parabola "error while loading shared libraries libjson-c.so.4"


On Wed, 18 Jul 2018 11:49:59 -0400
Luke Shumaker <lukeshu at lukeshu.com> ha escrit:

> On Sat, 14 Jul 2018 18:23:25 -0400,
> Xavier B. wrote:
> > After upgrading my system, I'm not be able to boot my system (see 
> > photo). It seems it's an issue with systemd. What can I do? After this 
> > shot, the keyboard does not respond.
> 
> Yes, you should be able to arch-chroot in to the system from a live
> USB/CD, in order to fix it and grab logs.
> 


It worked. I runned this after booting live USB:

$ loadkeys es
$ fdisk -l
$ swapon /dev/sda2
$ mount /dev/sda1 /mnt
$ mount /dev/sda2 /mnt/var
$ arch-chroot /mnt
$ pacman -Syu

I have to disable checking because some package downloads failed (see screenshot)

Perhaps you have some *trouble* with PGP packets verifying. I experimented a cycle: download a package, then the signature is not trust, delete package, etc.


Xavier


From freemor at freemor.ca  Wed Aug  1 14:05:38 2018
From: freemor at freemor.ca (Freemor)
Date: Wed, 1 Aug 2018 10:05:38 -0300
Subject: [Assist] Some packages are incompatible with your-initfreedom
In-Reply-To: <20180801141554.5e4a38e21269dc24a4adc8ef@posteo.net>
References: <20180801141554.5e4a38e21269dc24a4adc8ef@posteo.net>
Message-ID: <20180801130538.GB17828@freemor.ca>

On Wed, Aug 01, 2018 at 02:15:54PM +0200, Xavier B. wrote:
> I have parabola with openrc installed. I want to upgrade but I get:
> 
> :: your-initfreedom i libsystemd-dummy tenen conflictes (libsystemd). Elimino libsystemd-dummy? [s/N] s
> :: your-initfreedom i systemd-dummy tenen conflictes (systemd). Elimino systemd-dummy? [s/N] s
> Error: ha fallat preparar la transacci? (no s'han pogut satisfer les depend?ncies)
> :: no es pot satisfer la depend?ncia "libsystemd" requerida per device-mapper
> :: no es pot satisfer la depend?ncia "libsystemd" requerida per dhcpcd
> :: no es pot satisfer la depend?ncia "systemd" requerida per lighttpd
> :: no es pot satisfer la depend?ncia "libsystemd" requerida per lvm2
> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per libusb
> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per pcmciautils
> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per procps-ng
> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per rpcbind
> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per syslog-ng
> 
> 
> 
> So procps-ng, rpcbind, syslog-ng, libusb, pcmciautils, lvm2, lighttpd, dhcpcd, device-mapper are incompatible with your-initfreedom. What can I do?
> 
> Thanks in advance,
> Xavier
> _______________________________________________
> Assist mailing list
> Assist at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/assist

IIRC your-initfeedom come from the expiremental [nonsystemd] repo. The things
done there are no longer fnctional with the changes Lukeshu has done recently
to make openrc work out of the box. you'll need to remove your-initfreedom and
switch from it's system-dummy to the newer one in the main repo. Plus you'lll
probably need to make a couple of other tweaks (cant get the package names
right now as I'm out and about and thus away from my parabola system.) 

Basically thanks to Lukeshu's hard work [nonsystemd] is no longer required.

I'll post clearer details or catch you on IRC later when I'm back on my
Parabola machine

Regards, 
Freemor


-- 
Want to send me an encrypted reply?
Click here: https://hawkpost.co/box/e414d311-bd6a-4429-8e9e-6a690d5ad034
The rest of my contact details are at:
https://freemor.ca/contact
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180801/16119e9c/attachment.bin>

From bill-auger at peers.community  Wed Aug  1 19:46:03 2018
From: bill-auger at peers.community (bill-auger)
Date: Wed, 1 Aug 2018 14:46:03 -0400
Subject: [Assist] Fw: Re: Unable to boot my parabola "error while
 loading shared libraries libjson-c.so.4"
In-Reply-To: <20180801142332.80f15db50c10335c1be090d3@posteo.net>
References: <20180801142332.80f15db50c10335c1be090d3@posteo.net>
Message-ID: <20180801144603.aa5e7cfd01f29b69a5479181@peers.community>

try refreshing the keyring like section #1 on this wiki page:

https://wiki.parabola.nu/Parabola_Keyring

that should allow you to verify all package signatures again
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180801/5b2132b1/attachment.bin>

From megver83 at hyperbola.info  Thu Aug  2 23:14:42 2018
From: megver83 at hyperbola.info (Megver83)
Date: Thu, 2 Aug 2018 18:14:42 -0400
Subject: [Assist] Some packages are incompatible with your-initfreedom
In-Reply-To: <20180801130538.GB17828@freemor.ca>
References: <20180801141554.5e4a38e21269dc24a4adc8ef@posteo.net>
 <20180801130538.GB17828@freemor.ca>
Message-ID: <031adde9-1bea-3352-2a37-50d2f4edb66b@hyperbola.info>

El 01/08/18 a las 09:05, Freemor escribi?:
> On Wed, Aug 01, 2018 at 02:15:54PM +0200, Xavier B. wrote:
>> I have parabola with openrc installed. I want to upgrade but I get:
>>
>> :: your-initfreedom i libsystemd-dummy tenen conflictes (libsystemd). Elimino libsystemd-dummy? [s/N] s
>> :: your-initfreedom i systemd-dummy tenen conflictes (systemd). Elimino systemd-dummy? [s/N] s
>> Error: ha fallat preparar la transacci? (no s'han pogut satisfer les depend?ncies)
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per device-mapper
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per dhcpcd
>> :: no es pot satisfer la depend?ncia "systemd" requerida per lighttpd
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per lvm2
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per libusb
>> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per pcmciautils
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per procps-ng
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per rpcbind
>> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per syslog-ng
>>
>>
>>
>> So procps-ng, rpcbind, syslog-ng, libusb, pcmciautils, lvm2, lighttpd, dhcpcd, device-mapper are incompatible with your-initfreedom. What can I do?
>>
>> Thanks in advance,
>> Xavier
>> _______________________________________________
>> Assist mailing list
>> Assist at lists.parabola.nu
>> https://lists.parabola.nu/mailman/listinfo/assist
> 
> IIRC your-initfeedom come from the expiremental [nonsystemd] repo. The things
> done there are no longer fnctional with the changes Lukeshu has done recently
> to make openrc work out of the box. you'll need to remove your-initfreedom and
> switch from it's system-dummy to the newer one in the main repo. Plus you'lll
> probably need to make a couple of other tweaks (cant get the package names
> right now as I'm out and about and thus away from my parabola system.) 
> 
> Basically thanks to Lukeshu's hard work [nonsystemd] is no longer required.
> 
> I'll post clearer details or catch you on IRC later when I'm back on my
> Parabola machine
> 
> Regards, 
> Freemor
> 

[nonsystemd] packages is more than just your-initfreedom. Think on the
packages (like xdg-user-dirs) which run systemd commands in
post_install(). Then it doesn't matter that you split systemd in 100
packages, a non-systemd user doesn't care about systemd. Period.

I added systemd to your-initfreedom because the intention of
[nonsystemd] packages is to basically do not depend on systemd, so you
don't need systemd-dummy-like packages. However, I'm conscious that
lukeshu may (soon) make (not)systemd work without bothering elogind,
opensysusers and opentmpfiles. When that happens, the criteria[0] of
packages built in [nonsystemd] will simply change.

Consider that while some packages depend on systemd when they don't
really do (in which case you can simply use notsystemd to satisfy the
dependency) some others have a systemd integration which makes them work
worse (that's why there are the -elogind packages), so then I patch and
build them in [nonsystemd], like with mkinitcpio[1].

[0] https://wiki.parabola.nu/Nonsystemd#Criteria
[1] https://git.parabola.nu/abslibre.git/tree/nonsystemd/mkinitcpio

-- 
~Megver83

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180802/1c79b9ed/attachment-0001.bin>

From somenxavier at posteo.net  Fri Aug  3 10:10:03 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Fri, 3 Aug 2018 11:10:03 +0200
Subject: [Assist] Some packages are incompatible with your-initfreedom
Message-ID: <20180803111003.b6cba0cdf5541aa2df5301d1@posteo.net>

So what's the solution on that?


Message: 8
Date: Thu, 2 Aug 2018 18:14:42 -0400
From: Megver83 <megver83 at hyperbola.info>
To: assist at lists.parabola.nu
Subject: Re: [Assist] Some packages are incompatible with
	your-initfreedom
Message-ID: <031adde9-1bea-3352-2a37-50d2f4edb66b at hyperbola.info>
Content-Type: text/plain; charset="windows-1252"

El 01/08/18 a las 09:05, Freemor escribi?:
> On Wed, Aug 01, 2018 at 02:15:54PM +0200, Xavier B. wrote:
>> I have parabola with openrc installed. I want to upgrade but I get:
>>
>> :: your-initfreedom i libsystemd-dummy tenen conflictes (libsystemd). Elimino libsystemd-dummy? [s/N] s
>> :: your-initfreedom i systemd-dummy tenen conflictes (systemd). Elimino systemd-dummy? [s/N] s
>> Error: ha fallat preparar la transacci? (no s'han pogut satisfer les depend?ncies)
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per device-mapper
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per dhcpcd
>> :: no es pot satisfer la depend?ncia "systemd" requerida per lighttpd
>> :: no es pot satisfer la depend?ncia "libsystemd" requerida per lvm2
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per libusb
>> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per pcmciautils
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per procps-ng
>> :: eliminar libsystemd-dummy trenca la depend?ncia "libsystemd" requerida per rpcbind
>> :: eliminar systemd-dummy trenca la depend?ncia "systemd" requerida per syslog-ng
>>
>>
>>
>> So procps-ng, rpcbind, syslog-ng, libusb, pcmciautils, lvm2, lighttpd, dhcpcd, device-mapper are incompatible with your-initfreedom. What can I do?
>>
>> Thanks in advance,
>> Xavier
>> _______________________________________________
>> Assist mailing list
>> Assist at lists.parabola.nu
>> https://lists.parabola.nu/mailman/listinfo/assist
> 
> IIRC your-initfeedom come from the expiremental [nonsystemd] repo. The things
> done there are no longer fnctional with the changes Lukeshu has done recently
> to make openrc work out of the box. you'll need to remove your-initfreedom and
> switch from it's system-dummy to the newer one in the main repo. Plus you'lll
> probably need to make a couple of other tweaks (cant get the package names
> right now as I'm out and about and thus away from my parabola system.) 
> 
> Basically thanks to Lukeshu's hard work [nonsystemd] is no longer required.
> 
> I'll post clearer details or catch you on IRC later when I'm back on my
> Parabola machine
> 
> Regards, 
> Freemor
> 

[nonsystemd] packages is more than just your-initfreedom. Think on the
packages (like xdg-user-dirs) which run systemd commands in
post_install(). Then it doesn't matter that you split systemd in 100
packages, a non-systemd user doesn't care about systemd. Period.

I added systemd to your-initfreedom because the intention of
[nonsystemd] packages is to basically do not depend on systemd, so you
don't need systemd-dummy-like packages. However, I'm conscious that
lukeshu may (soon) make (not)systemd work without bothering elogind,
opensysusers and opentmpfiles. When that happens, the criteria[0] of
packages built in [nonsystemd] will simply change.

Consider that while some packages depend on systemd when they don't
really do (in which case you can simply use notsystemd to satisfy the
dependency) some others have a systemd integration which makes them work
worse (that's why there are the -elogind packages), so then I patch and
build them in [nonsystemd], like with mkinitcpio[1].

[0] https://wiki.parabola.nu/Nonsystemd#Criteria
[1] https://git.parabola.nu/abslibre.git/tree/nonsystemd/mkinitcpio

-- 
~Megver83

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 520 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180802/1c79b9ed/attachment.bin>

------------------------------

Subject: Digest Footer

_______________________________________________
Assist mailing list
Assist at lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/assist


------------------------------

End of Assist Digest, Vol 59, Issue 1

From somenxavier at posteo.net  Fri Aug  3 10:32:10 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Fri, 3 Aug 2018 11:32:10 +0200
Subject: [Assist] Fw: Re: Unable to boot my parabola "error while
 loading shared libraries libjson-c.so.4"
Message-ID: <20180803113210.254a63f7b1bc3013a6d20c4d@posteo.net>

Thanks a lot, Bill.
It works

How can I reinstall non-verified local packages?

Message: 7
Date: Wed, 1 Aug 2018 14:46:03 -0400
From: bill-auger <bill-auger at peers.community>
To: assist at lists.parabola.nu
Subject: Re: [Assist] Fw: Re: Unable to boot my parabola "error while
	loading shared libraries libjson-c.so.4"
Message-ID: <20180801144603.aa5e7cfd01f29b69a5479181 at peers.community>
Content-Type: text/plain; charset="us-ascii"

try refreshing the keyring like section #1 on this wiki page:

https://wiki.parabola.nu/Parabola_Keyring

that should allow you to verify all package signatures again
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180801/5b2132b1/attachment-0001.bin>

From freemor at freemor.ca  Fri Aug  3 12:57:53 2018
From: freemor at freemor.ca (Freemor)
Date: Fri, 3 Aug 2018 08:57:53 -0300
Subject: [Assist] Some packages are incompatible with your-initfreedom
In-Reply-To: <20180803111003.b6cba0cdf5541aa2df5301d1@posteo.net>
References: <20180803111003.b6cba0cdf5541aa2df5301d1@posteo.net>
Message-ID: <20180803115738.GC17828@freemor.ca>

On Fri, Aug 03, 2018 at 11:10:03AM +0200, Xavier B. wrote:
> So what's the solution on that?

To Fix this and move fully onto Lukeshu's work you'd need to

uninstall your-initfreedom
make sure you are using the newer systemd-dummy 1-1
install libsystemd, notsystemd-common, systemd-libsystemd

I know from the names that seems like your adding a lot of "systemd". But
Lukeshu has done some major work to split system tools/libs that systemd has
laid claim to out of systemd proper. Your init system will still be fully
openrc/runit 

You may have to mess with the order of the steps a bit. I did then over time as
lukeshu was making the changes. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180803/9414545e/attachment.bin>

From somenxavier at posteo.net  Fri Aug  3 15:46:38 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Fri, 3 Aug 2018 16:46:38 +0200
Subject: [Assist] Fw: Re: Unable to boot my parabola "error while
 loading shared libraries libjson-c.so.4"
In-Reply-To: <20180803092934.0f644de9f6160651368c8f53@peers.community>
References: <20180803113210.254a63f7b1bc3013a6d20c4d@posteo.net>
 <20180803092934.0f644de9f6160651368c8f53@peers.community>
Message-ID: <20180803164638.698cc320db5ceead211d2730@posteo.net>

No. It's another question: if I installed packages not verifying them, how can I reinstalling it?

1. Is there any way to find if I have non-verified packages on my pc?
2. How to reinstall them

Thanks

On Fri, 3 Aug 2018 09:29:34 -0400
bill-auger <bill-auger at peers.community> ha escrit:

> On Fri, 3 Aug 2018 11:32:10 +0200 Xavier wrote:
> > How can I reinstall non-verified local packages?
> 
> i dont understand - if you want to "reinstall" then you must have installed them previously
> 
> how did you install them previously?
> why cant you do it that way again?
> how did they get uninstalled?
> why are they non-verified?
> why are they local?

From somenxavier at posteo.net  Sun Aug  5 18:38:28 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Sun, 5 Aug 2018 19:38:28 +0200
Subject: [Assist] Fw: Re: Unable to boot my parabola "error while
 loading shared libraries libjson-c.so.4"
In-Reply-To: <20180803202900.3bf48ad820976e0a6ce145b4@peers.community>
References: <20180803113210.254a63f7b1bc3013a6d20c4d@posteo.net>
 <20180803092934.0f644de9f6160651368c8f53@peers.community>
 <20180803164638.698cc320db5ceead211d2730@posteo.net>
 <20180803202900.3bf48ad820976e0a6ce145b4@peers.community>
Message-ID: <20180805193828.935fe5ede8bc9b834d1027e1@posteo.net>

Thanks

On Fri, 3 Aug 2018 20:29:00 -0400
bill-auger <bill-auger at peers.community> ha escrit:

> On Fri, 3 Aug 2018 16:46:38 +0200 Xavier wrote:
> > 1. Is there any way to find if I have non-verified packages on my pc?
> 
> i dont think there is any way to identify them - pacman does not keep package signatures - i do think it should, but it does not
> 
> 
> > 2. How to reinstall them
> 
> you can force any installed package to re-install with pacman -S --overwrite pkg-name - the big hammer approach to re-install every package retaining their explicit/dependency relationships you can try this (YMMV):
> 
>   # pacman -Syu
>   # yes | pacman -Scc
>   # pacman -S --overwrite          $(pacman -Qenq)
>   # pacman -S --overwrite --asdeps $(pacman -Qdnq)
> 

From somenxavier at posteo.net  Wed Aug  8 16:53:30 2018
From: somenxavier at posteo.net (Xavier B.)
Date: Wed, 8 Aug 2018 17:53:30 +0200
Subject: [Assist] Some packages are incompatible with your-initfreedom
Message-ID: <20180808175330.5c9500429eb7149ba7e1b1cf@posteo.net>

> Freemor freemor at freemor.ca
> Fri Aug 3 12:57:53 BST 2018
> 
>     Previous message (by thread): [Assist] Some packages are incompatible with your-initfreedom
>     Next message (by thread): [Assist] Fw: Re: Unable to boot my parabola "error while loading shared libraries libjson-c.so.4"
>     Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 
> On Fri, Aug 03, 2018 at 11:10:03AM +0200, Xavier B. wrote:
> > So what's the solution on that?
> 
> To Fix this and move fully onto Lukeshu's work you'd need to
> 
> uninstall your-initfreedom
> make sure you are using the newer systemd-dummy 1-1
> install libsystemd, notsystemd-common, systemd-libsystemd
> 
> I know from the names that seems like your adding a lot of "systemd". But
> Lukeshu has done some major work to split system tools/libs that systemd has
> laid claim to out of systemd proper. Your init system will still be fully
> openrc/runit 
> 
> You may have to mess with the order of the steps a bit. I did then over time as
> lukeshu was making the changes. 


So, we have to update the wiki, haven't we?

From rudolf.dovicin at gmail.com  Thu Aug  9 09:23:41 2018
From: rudolf.dovicin at gmail.com (=?UTF-8?B?UnVkb2xmIERvdmnEjcOtbg==?=)
Date: Thu, 9 Aug 2018 10:23:41 +0200
Subject: [Assist] icu 62.1-1 breaks dependency icu<62 required by iceweasel
Message-ID: <CAOq1RDrD0nrBneCnUhKGP+=A8kZd4=V9+Q8Gab2ZSfqdpJfj2A@mail.gmail.com>

I cannot upgrade ICU due conflict with Iceweasel:

# LANG=C; date -u +%FT%T%:z; pacman -Syu
2018-08-09T08:20:06+00:00
:: Synchronizing package databases...
 nonprism is up to date
 libre is up to date
 core is up to date
 extra is up to date
 community is up to date
 pcr is up to date
 libre-multilib is up to date
 multilib is up to date
 kernels is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (62.1-1) breaks dependency 'icu<62' required by iceweasel

Is it anticipated behaviour, because working on newer version of
Iceweasel is in progress?
Or is unexpected error somewhere?
-- 
Rudolf Dovi??n
Matice slovenskej 1260/4-7
957 04  B?novce nad Bebravou 4
SLOVENSKO
mailto:Rudolf.Dovicin at Gmail.com
(cellular: +421 940 872 846, short messages only)

From bill-auger at peers.community  Fri Aug 10 09:17:46 2018
From: bill-auger at peers.community (bill-auger)
Date: Fri, 10 Aug 2018 04:17:46 -0400
Subject: [Assist] icu 62.1-1 breaks dependency icu<62 required by
 iceweasel
In-Reply-To: <CAOq1RDrD0nrBneCnUhKGP+=A8kZd4=V9+Q8Gab2ZSfqdpJfj2A@mail.gmail.com>
References: <CAOq1RDrD0nrBneCnUhKGP+=A8kZd4=V9+Q8Gab2ZSfqdpJfj2A@mail.gmail.com>
Message-ID: <ecf8975c-0080-da55-8e1e-38cda90a0302@peers.community>

On 08/09/2018 04:23 AM, Rudolf Dovi??n wrote:
> I cannot upgrade ICU due conflict with Iceweasel:

related to redmine issue - https://labs.parabola.nu/issues/1941

-------------- 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/assist/attachments/20180810/d35cc819/attachment-0001.bin>

From c.monty at web.de  Wed Aug 15 21:20:07 2018
From: c.monty at web.de (Thomas)
Date: Wed, 15 Aug 2018 22:20:07 +0200
Subject: [Assist] Wifi Card Intel Advanced-N 6200
Message-ID: <73111932-cf5e-6353-7a07-d02183bcddb0@web.de>

Hi,

is there any way to run Parabola Linux with wifi card /Intel Advanced-N
6200/ (03:00.0 Network controller: Intel Corporation Centrino Advanced-N
6200 (rev 35))?

THX
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180815/00f34de8/attachment.html>

From isacdaavid at isacdaavid.info  Wed Aug 15 23:27:22 2018
From: isacdaavid at isacdaavid.info (Isaac David)
Date: Wed, 15 Aug 2018 17:27:22 -0500
Subject: [Assist] Wifi Card Intel Advanced-N 6200
In-Reply-To: <73111932-cf5e-6353-7a07-d02183bcddb0@web.de>
References: <73111932-cf5e-6353-7a07-d02183bcddb0@web.de>
Message-ID: <4CC3D5FD-D63D-49C0-9376-3F01A9648320@isacdaavid.info>

Le 15 ao?t 2018 15:20:07 GMT-05:00, Thomas <c.monty at web.de> a ?crit :
>Hi,
>
>is there any way to run Parabola Linux with wifi card /Intel Advanced-N
>6200/ (03:00.0 Network controller: Intel Corporation Centrino
>Advanced-N
>6200 (rev 35))?
>
>THX


All Intel cards require nonfree software to work. Depending on your motherboard you might be able to replace the internal WiFi silicon, or just use a USB plug. Check on h-node.org

-- 
Isaac David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180815/f2747904/attachment.bin>

From drew at dangerfields.ca  Fri Aug 17 15:16:56 2018
From: drew at dangerfields.ca (Drew)
Date: Fri, 17 Aug 2018 07:16:56 -0700
Subject: [Assist] Lib x264
Message-ID: <165483f0ccb.b899b964132787.6926768425398534371@dangerfields.ca>

As usual, immediately after booting, I ran sudo pacman -Syu and receiving a prompt asking if I want to replace libx264 with extra/x264. ?I entered N and then received a prompt saying there were unresolved conflicts. Do I want to replace libx264? ?Why? Thank you. Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180817/e9679df4/attachment.html>

From freemor at freemor.ca  Fri Aug 17 15:35:48 2018
From: freemor at freemor.ca (Freemor)
Date: Fri, 17 Aug 2018 11:35:48 -0300
Subject: [Assist] Lib x264
In-Reply-To: <165483f0ccb.b899b964132787.6926768425398534371@dangerfields.ca>
References: <165483f0ccb.b899b964132787.6926768425398534371@dangerfields.ca>
Message-ID: <20180817143548.GA28435@freemor.ca>

What conflicts? It could be that something else need to be rebuilt against the
new x264

Also what Architecture are you using x86_64, i686, arm?

Thanks 
Freemor


On Fri, Aug 17, 2018 at 07:16:56AM -0700, Drew wrote:
> As usual, immediately after booting, I ran sudo pacman -Syu and receiving a
> prompt asking if I want to replace libx264 with extra/x264. ?I entered N and
> then received a prompt saying there were unresolved conflicts. Do I want to
> replace libx264? ?Why? 
> Thank you. 
> Drew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180817/3fd29471/attachment.bin>

From bill-auger at peers.community  Sat Aug 18 01:27:49 2018
From: bill-auger at peers.community (bill-auger)
Date: Fri, 17 Aug 2018 20:27:49 -0400
Subject: [Assist] Lib x264
In-Reply-To: <165483f0ccb.b899b964132787.6926768425398534371@dangerfields.ca>
References: <165483f0ccb.b899b964132787.6926768425398534371@dangerfields.ca>
Message-ID: <20180817202720.6e67e136@parabola>

generally, whatever pacman asks you to do is the correct thing to do;
unless you have a very good reason not to - packages get moved/renamed/replaced
often - that is probably all that happened

if ever you do what pacman suggests and that somehow breaks your system; then
that is a bug to report - in this case, the bug you are reporting is probably
caused by not doing what pacman suggests
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180817/a7ff2d93/attachment.bin>

From ineiev at gnu.org  Thu Aug 23 12:01:43 2018
From: ineiev at gnu.org (Ineiev)
Date: Thu, 23 Aug 2018 07:01:43 -0400
Subject: [Assist] recent news entry
Message-ID: <20180823110143.GP16821@gnu.org>

Hello,

Recent Parabola news[0] says, "The unar package has been dropped in
favor of Arch Linux's unarchiver."

It seems to me that Parabola maintainers could consider using
"GNU/Linux" when naming the operating system [1] in their official
messages.

Thank you!

[0] https://parabolagnulinux.org/news/unar-being-replaced-by-unarchiver/
[1] https://www.gnu.org/gnu/gnu-linux-faq.html#distronames1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180823/5752bb86/attachment-0001.bin>

From rudolf.dovicin at gmail.com  Thu Aug 23 20:44:13 2018
From: rudolf.dovicin at gmail.com (=?UTF-8?B?UnVkb2xmIERvdmnEjcOtbg==?=)
Date: Thu, 23 Aug 2018 21:44:13 +0200
Subject: [Assist] Iceweasel: iceweasel-branding.js: prefs parse errors
Message-ID: <CAOq1RDoBTGuQ9pET_f32-VNPCHWMMWFtvhUX14kZbwJ9ZdkAaw@mail.gmail.com>

Hello.

I have updated system including Iceweasel and it has started to behave
strangely:
All histories have dissapeared (passwords, cookies, visited links,
etc...), preferences are without text and it writes errors about
parsing:

defaults/preferences/firefox-branding.js:1: prefs parse error: unknown keyword
/usr/lib/iceweasel/browser/defaults/preferences/iceweasel-branding.js:849:
prefs parse error: unknown keyword
/usr/lib/iceweasel/browser/defaults/preferences/iceweasel-branding.js:923:
prefs parse error: unknown keyword
/usr/lib/iceweasel/browser/defaults/preferences/iceweasel-branding.js:1197:
prefs parse error: unexpected character

Please, where is the problem?
-- 
Rudolf Dovi??n
Matice slovenskej 1260/4-7
957 04  B?novce nad Bebravou 4
SLOVENSKO
mailto:Rudolf.Dovicin at Gmail.com
(cellular: +421 940 872 846, short messages only)

From bill-auger at peers.community  Sat Aug 25 23:46:05 2018
From: bill-auger at peers.community (bill-auger)
Date: Sat, 25 Aug 2018 22:46:05 +0000
Subject: [Assist] recent news entry
In-Reply-To: <20180823110143.GP16821@gnu.org>
References: <20180823110143.GP16821@gnu.org>
Message-ID: <20180825224351.09dc4a74@peers.community>

On Thu, 23 Aug 2018 07:01:43 -0400 Ineiev <ineiev at gnu.org> wrote:

if you were suggesting that "Arch GNU/Linux" or "ArchLinux GNU/Linux"
would be better? - "Arch GNU/Linux" may appear to be more correct but
it is in fact no less of a misnomer than "Arch Linux" - "ArchLinux
GNU/Linux" may look incorrect or contradictory but is actually more
correct

if you prefer the former then you are assuming that the name of the
operating system is "Arch" and it claims to be a kind of "Linux" - the
latter indicates that the formal name of the operating system is
"ArchLinux" without claiming to be any kind of anything - so that
"ArchGNU/Linux" would be an inappropriate mutation of the formal name;
but appending "GNU/Linux" to that indicates the type of thing that this
thing with the name: "ArchLinux" actually is - if you are still not
convinced, there is an entire wiki article on this very topic[1] that
should be more illuminating


[1]: https://wiki.parabola.nu/The_ArchLinux_Misnomer

From ineiev at gnu.org  Sun Aug 26 11:48:16 2018
From: ineiev at gnu.org (Ineiev)
Date: Sun, 26 Aug 2018 06:48:16 -0400
Subject: [Assist] recent news entry
In-Reply-To: <20180825224351.09dc4a74@peers.community>
References: <20180823110143.GP16821@gnu.org>
 <20180825224351.09dc4a74@peers.community>
Message-ID: <20180826104814.GA16821@gnu.org>

On Sat, Aug 25, 2018 at 10:46:05PM +0000, bill-auger wrote:
> On Thu, 23 Aug 2018 07:01:43 -0400 Ineiev <ineiev at gnu.org> wrote:
> 
> if you were suggesting that "Arch GNU/Linux" or "ArchLinux GNU/Linux"
> would be better?

I guess, "Arch GNU/Linux" [0]. it was clearly named after the operating
system.

[0] https://www.gnu.org/distros/common-distros.html#Arch

> if you prefer the former then you are assuming that the name of the
> operating system is "Arch" and it claims to be a kind of "Linux" - the
> latter indicates that the formal name of the operating system is
> "ArchLinux" without claiming to be any kind of anything - so that
> "ArchGNU/Linux" would be an inappropriate mutation of the formal name;
> but appending "GNU/Linux" to that indicates the type of thing that this
> thing with the name: "ArchLinux" actually is - if you are still not
> convinced, there is an entire wiki article on this very topic[1] that
> should be more illuminating

I believe this is actually addressed by the FAQ entry I referred to
in my previous message.

> [1]: https://wiki.parabola.nu/The_ArchLinux_Misnomer

I'll try to cover the points it makes.

> "ArchLinux" and "Arch Linux" are registered trademarks of a
> particular product.

I don't think this may matter. we may have _permission_ to use
other people trademarks, but I don't think we have any obligation
to use it [1]. and the trademark still refers to the operating
system rather than to the kernel.

[1] https://www.gnu.org/p/why-call-it-the-swindle.html

[reordered]
> The tacet error is that the word "Arch" does not
> precisely name any distro.
...
> That product is the distro which is often
> referred to informally by the nick-name "arch" in the same way that
> some people may call their VolksWagon Beetle a "vee-wee bug"; but no
> one thinks that car is an insect by the virtue of it's misleading
> marketing name.

So "Arch" in fact _can_ be accepted as a name of that distro. using it
alone would be less problematic than calling it Linux.

> To be clear, there is a software project named "Arch" that pre-dates
> the ArchLinux distro and it actually is a GNU project (and not a
> distro).

This would be essential if there were a considerable chance of
confusion between them, but in fact any reasonable context makes
the difference clear.

> the "ArchLinux" project and the distro
> that it produces by the same name; in which the letters "L-i-n-u-x"
> are not descriptive, but an integral part of the single-word project
> name spelling.

I don't believe it isn't descriptive. it may be a single word,
but it's a compound word composed of a qualifier and a wrongly
named operating system.

> Suppose now, that someone says, "Fred Flintstone should be called
> Fred Flintperson; because after all, he is not a stone.".

The analogy doesn't hold. the person was named because of someone's
relation to a stone, not to a hypothetical flintperson that must
have never existed. then, the relation between the particular
person and the flintstone the name derives from may be and typically
is merely symbolic, because it's likely to be a name inherited
from distant ancestors. the distro was named after the operating
system, and (which is more important) the relation of the distro
to that system has never been broken.

Yet if people think that the name Fred Flintstone is problematic
for some reasons (for example, if that name sounds obscene
in the cultural context where that person is called), they still
may and should rename that person in a more acceptable way.

> the name "VolksWagon" may suggest to some that the company makes
> wagons).

This example isn't perfect. "wagon" includes "car" (in English,
and "Wagen" includes "car" in German), so "VolksWagen" may make cars;
in contrast, the distro makes a GNU/Linux distribution rather than
the kernel. more important, they don't disrespect anybody
if their name suggests they make "cars", "wagons" or "vehicles".
if their name suggested that they primarily use the work
of beekeepers, _that_ would be wrong (unless their cars, for example,
would be made mostly of vax and on apiaries).

Did Parabola maintainers discuss the issue with the FSF?

--
The opinion of this author may and/or may not coincide with his and/or
her own point of view.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: Digital signature
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20180826/d786729e/attachment.bin>

From bill-auger at peers.community  Sun Aug 26 23:01:21 2018
From: bill-auger at peers.community (bill-auger)
Date: Sun, 26 Aug 2018 22:01:21 +0000
Subject: [Assist] Iceweasel: iceweasel-branding.js: prefs parse errors
In-Reply-To: <CAOq1RDoBTGuQ9pET_f32-VNPCHWMMWFtvhUX14kZbwJ9ZdkAaw@mail.gmail.com>
References: <CAOq1RDoBTGuQ9pET_f32-VNPCHWMMWFtvhUX14kZbwJ9ZdkAaw@mail.gmail.com>
Message-ID: <20180826220121.1e43ccd9@peers.community>

related to issue #1969 https://labs.parabola.nu/issues/1969

From bill-auger at peers.community  Mon Aug 27 08:18:50 2018
From: bill-auger at peers.community (bill-auger)
Date: Mon, 27 Aug 2018 07:18:50 +0000
Subject: [Assist] recent news entry
In-Reply-To: <20180826104814.GA16821@gnu.org>
References: <20180823110143.GP16821@gnu.org>
 <20180825224351.09dc4a74@peers.community>
 <20180826104814.GA16821@gnu.org>
Message-ID: <20180827071850.75a92619@peers.community>

hey thanks for the rebuttal - i love this topic :)

On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> I don't think this may matter. we may have _permission_ to use
> other people trademarks, but I don't think we have any obligation
> to use it

whether or not it is permissible or obligatory to use the trademark is
is not the point - the point is that it is the name chosen by the only
people who have any right to name it - one may refer to that thing by
any other name; but any other name would be completely arbitrary and
incorrect; because it is not the actual name of that actual thing


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> So "Arch" in fact _can_ be accepted as a name of that distro. using it
> alone would be less problematic than calling it Linux.

"Arch" is not an acceptable name of that distro because it is not the
name of that distro (or any distro) - just as "bug" is not the accepted
name of a volkswagon - it merely a commonly used "nickname"

i do agree that using "arch" alone is less problematic than calling it
any kind of "linux" - but "less problematic" or "politically correct" is
not the same thing as: "actually correct"; which is what one should
strive to be when using proper names, especially in a professional
context

for example, i do not know how to pronounce "Ineiev" - so, shall i call
you Alice? or Bob perhaps? - either of those would be "less problematic"
for me; but neither would be correct, and so it would be somewhere
between pretentious to arrogant for me to use them while referring to
you - and after you protest (which you may do rightfully so), would it
be polite of me to insist on always calling you Bob anyways; simply
because i like that name better than the one you have already? - and
surely, i should not be foolish enough to expect you to answer me when
i say: "Hey Bob !!"; nor for any other person to know that i am
referring to you when i say: "Bob thinks we should change archlinux's
name"


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> This would be essential if there were a considerable chance of
> confusion between them, but in fact any reasonable context makes
> the difference clear.

im not convinced of that - there are many people in the world
sharing the name "bob smith" and it takes much more than context to
distinguish them

both "arch" projects are free and open-source software projects - it
would be different if one were a dog shampoo or automobile; but two
free and open-source software projects is the very same context -
further more, only one of them is actually a GNU project - so
associating "gnu" with the other would only make them less clearly
distinguishable - then they would be two free and open-source software
projects both with "arch" and "gnu" in their names


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> I don't believe it isn't descriptive. it may be a single word,
> but it's a compound word composed of a qualifier and a wrongly
> named operating system.

and "flintstone" is the combination of two rocks - but that does not
change that fact that it is his proper formal name that was given to him
by the only person who had the right to name him - i am not that person;
so i would be pretentious at best, to call him anything that he does
not answer to, merely because i dont think his name is sufficiently
descriptive of his nature


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> The analogy doesn't hold. the person was named because of someone's
> relation to a stone

whatever was the reason why he was given that name, does not
change the fact that he was in fact given that name, and not some
other, more accurately descriptive name - and it does not give me nor
anyone besides fred himself the right to change that name

the fact that the name "stone" does not accurately describe that person
is not a counter-argument - it is exactly making my point

indeed, fred may have been named in explicit tribute to some famous
stone; but that would not imply that he *is* any kind of stone, nor that
the person who named him intended any deception, nor that any
reasonable person would interpret it as such - a name is not a
description and should never be taken to be descriptive - that
statement was assuming that the name of the OS is "arch" and it is
claiming to be a type of "linux" - i am not convinced that was actually
the intention of the people who named it - i think they were two
names that were merged together, not a name plus a description -
after-all, "linux" itself, is also just a name - it is not a
description of anything either - "linux mint" is surely not any kind of
mint - that name is not descriptive of anything; although when read
naively, it seem to be describing some kind of mint - why doesnt that
bother anyone?


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> Yet if people think that the name Fred Flintstone is problematic
> for some reasons (for example, if that name sounds obscene
> in the cultural context where that person is called), they still
> may and should rename that person in a more acceptable way.

to be clear, only someone who is legally authorized to do such renaming
has the right to do so - and the only acceptable way to rename it, is
some way that is acceptable to the person who has the authority to
rename it - in the case of Fred Flintstone, that person is Fred
Flintstone - in the case of archlinux, those persons are Aaron Griffin
and Judd Vinet - notice, how i did not say those people are "Aaron
FlintGriffin" and "Judd GnuVinet" - there is a very good reason i did
not do that - that is because i wanted to be clear and correct about the
actual persons to whom i was referring; so i used their actual
formal names properly without embellishment - in fact there are probably
not any people in the world with those particular names; so i would be
referring to exactly "nothing" that actually exists (the very same
"nothing" as the fabled operating system named "arch" that presumably
claims to be some sort of "linux" without actually existing)

as i said, anyone is free to use whatever words or nicknames of their
own choosing in whatever context they happen to be in, especially if
it is an informal context; but the use of nicknames is unprofessional
because nicknames do not properly refer to any specific things, and are
very often more misleading than helpful - the only professional manor in
which to refer to some person or some entity by name is to use its
proper formal given name - thus, the only acceptable way to denote
archlinux as some type of gnu/linux is: "archlinux gnu/linux"; and that
appears anywhere from dumb to arrogant - so if the choice is between
looking unprofessional on the one hand, and looking dumb or arrogant on
the other hand, then i prefer to avoid naming it at all in a
professional context


On Sun, 26 Aug 2018 06:48:16 -0400 Ineiev <ineiev at gnu.org> wrote:
> Did Parabola maintainers discuss the issue with the FSF?

oh yes - it appears than many calories were burned over this some years
ago - i suspect that you will be happy to see the decision that was
codified in the "Parabola Social Contract" to be "Arch (the GNU/Linux
distribution)"[1]

unfortunately, there does not exist any such "GNU/linux distribution"
that has as it's name: "Arch" - there is one of those things named:
"ArchLinux"; but that is not the one named in the "Parabola Social
Contract" - so that statement is either incorrectly referring to the
"GNU/linux distribution" that is named: "ArchLinux", or it is referring
to absolutely nothing that actually exists, and embarrassingly so IMHO,
as this is in the context of a formal mission statement

the "archlinux misnomer" wiki article is a commentary on that formal
decision and nothing more - but im glad you liked it :)


[1]: https://wiki.parabola.nu/Parabola_Social_Contract