-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/07/14 01:24 AM, Ulrich Mueller wrote:
>> On Tue, 01 Jul 2014, Ian Stakenvicius wrote:
>
>> On 01/07/14 06:44 PM, Ciaran McCreesh wrote:
|| ( amd64? (
>>>
>>> I thought we were trying to discourage that abomination...
>
>> It's still
> On Tue, 01 Jul 2014, Ian Stakenvicius wrote:
> On 01/07/14 06:44 PM, Ciaran McCreesh wrote:
>>> || ( amd64? (
>>
>> I thought we were trying to discourage that abomination...
> It's still necessary, unfortunately, until such time as everything
> in the tree no longer needs/depends on the e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/07/14 06:44 PM, Ciaran McCreesh wrote:
> On Wed, 2 Jul 2014 00:38:53 +0200 Michał Górny
> wrote:
>> || ( amd64? (
>
> I thought we were trying to discourage that abomination...
>
It's still necessary, unfortunately, until such time as every
On Wed, 2 Jul 2014 00:38:53 +0200
Michał Górny wrote:
> || (
> amd64? (
I thought we were trying to discourage that abomination...
--
Ciaran McCreesh
signature.asc
Description: PGP signature
Hello, developers and users.
I'm pretty sure that all of you are waiting with bated breaths for news
on the multilib project, so I've scrambled this quick newsletter
listing our latest achievements, issues and other things you may want
to know.
In random order:
1. hasufell fixed the header wrapp
A quick test shows that the sshfp for the ed25519 key for the current
host is not published; those who configure ssh to prefer ssh-ed25519 and
VerifyHostKeyDNS will get an error about that, even after accepting the
key, just because the other keys' sshfps are published.
Please be sure to publish s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/07/14 07:57 AM, Andreas K. Huettel wrote:
>
> perl-core/Switch is now stabilized on "amd64 ppc x86", so this
> should be fixed.
>
>> On 30/06/14 04:46 AM, Andreas K. Huettel wrote:
>>> [snip!] * As Fabian pointed out, perl-core/Switch-2.160.0
On 30/06/14 18:16, Ian Stakenvicius wrote:
> On 30/06/14 04:46 AM, Andreas K. Huettel wrote:
>
> > [snip!] * As Fabian pointed out, perl-core/Switch-2.160.0 should
> > still go stable. Fine with me (but I can't read your minds about
> > future stabilizations, and the virtual only had ~arch reverse
On Tue, Jul 1, 2014 at 8:41 AM, Patrick Lauer wrote:
> On 06/30/14 22:15, Jeroen Roovers wrote:
>> On Mon, 30 Jun 2014 09:25:27 -0400
>> Rich Freeman wrote:
>>
>>> Agree 100%. I'm taking about masking things that HAVEN'T BEEN TESTED
>>> AT ALL. The maintainer knows that they compile, and that i
On 06/30/14 22:15, Jeroen Roovers wrote:
> On Mon, 30 Jun 2014 09:25:27 -0400
> Rich Freeman wrote:
>
>> Agree 100%. I'm taking about masking things that HAVEN'T BEEN TESTED
>> AT ALL. The maintainer knows that they compile, and that is it.
>
> Developers who "HAVEN'T [...] TESTED AT ALL" and
On 06/29/14 17:33, Markos Chandras wrote:
> On 06/29/2014 10:23 AM, Patrick Lauer wrote:
>> On Sunday 29 June 2014 17:03:52 Patrick Lauer wrote:
>>> On Sunday 29 June 2014 10:12:22 Tom Wijsman wrote:
On Sun, 29 Jun 2014 09:09:36 +0100
Markos Chandras wrote:
> It's been a long ti
> > It would be nice if something like a pkgmove be done on the virtual,
> > though, upon its elimintation; anyone that installed the virtual to
> > obtain perl Switch shouldn't have to unmerge and specifically emerge
> > perl-core/Switch. I'm not sure if pkgmove itself supports this, though..
>
perl-core/Switch is now stabilized on "amd64 ppc x86", so this should be
fixed.
> On 30/06/14 04:46 AM, Andreas K. Huettel wrote:
> > [snip!] * As Fabian pointed out, perl-core/Switch-2.160.0 should
> > still go stable. Fine with me (but I can't read your minds about
> > future stabilizations, a
On Mon, 30 Jun 2014 12:46:38 -0700 C.J. Adams-Collier KF7BMP wrote:
> Hello folks,
>
> I've got a project on my plate to automate and reduce the human error in
> adding new VLANs, subnets, addresses, etc. to our production firewall
> fleet. Today, we manually make modifications to the following o
14 matches
Mail list logo
