> On Fri, Jan 22, 2016 at 1:12 PM, Joan Figueras wrote:
> Hi Javier,
>
> try to switch python to python2 during the build, then you can switch back
> to python3:
>
> $ sudo ln -sf /usr/bin/python2 /usr/bin/python
> [ do the build ]
> $ sudo ln -sf /usr/bin/python3 /usr/bin/python
>
> It's ugly, I
On Sun, Jan 24, 2016 at 9:03 PM, Jayesh Badwaik
wrote:
> >On Monday, 25 January 2016 03:23:25 IST Levente Polyak wrote:
> >> Looks like people tend to forget about updating pacman keyring.
> >>
> >> pacman-key --refresh-keys
>
>
> >Oops, feel very silly now.
>
>
Interesting, I just had a simi
On Monday, 25 January 2016 03:23:25 IST Levente Polyak wrote:
> Looks like people tend to forget about updating pacman keyring.
>
> pacman-key --refresh-keys
Oops, feel very silly now.
--
Cheers
Jayesh Badwaik
On 01/25/2016 03:17 AM, Jayesh Badwaik wrote:
> Hi,
>
> I'm receiving message about unknown trust while trying to install the confuse
> package.
>
Looks like people tend to forget about updating pacman keyring.
pacman-key --refresh-keys
cheers,
anthraxx
signature.asc
Description: Op
Hi,
I'm receiving message about unknown trust while trying to install the confuse
package.
$ sudo pacman -S confuse
resolving dependencies...
looking for conflicting packages...
Packages (1) confuse-2.8-1
Total Download Size: 0.03 MiB
Total Installed Size: 0.11 MiB
:: Proceed with install
On 24.01.2016 16:14, Genes Lists wrote:
> The message from you to the list is DKIM signed and appears to check out
> - but the outgoing message from the arch mail server fails DKIM. So
> anyone rejecting invalid DKIM will reject list mail - yahoo may be doing
> that now I don't know.
That's pos
This may be part of the problem. The arch mail server is passing thru
contributers DKIM signatures leading to list mail being DKIM invalid.
You domain has DKIM signed mail and therefore suffers this problem
For example, looking at your last message.
The message from you to the list is DKIM sig
On 16.01.2016 05:38, Natu wrote:
> You don't say what yahoo's reject message is, ...
I guess it's possible that some users simply marked mailing list mails
as spam and we got blacklisted because of that. The reject message is this:
421 4.7.1 [TS03] All messages from 5.9.250.164 will be permanentl
8 matches
Mail list logo