Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 RM: aiccu -- ROM; SixXS has been shut down and no
replacement popped up within 3 months
Control: reassign -2 ftp.debian.org
Hi,
Ansgar Burchardt wrote:
> SixXS will shutdown on 2017-06-06[1]. Unless there are other tunnel
>
Hi once again,
Ansgar Burchardt wrote:
> From a quick glance at [2], SixXS is the only provider using AYIYA and
> TIC
JFTR: It's not necessary that a (3rd party) tunnel service provider
exists for using aiccu. What equally suffices to make use of it (and
hence IMHO validates its existence in
On Tue, May 30, 2017 at 11:05 PM, Axel Beckert wrote:
> Control: severity -1 important
> Control: tag -1 confirmed
>
> Hi Ansgar,
>
> Ansgar Burchardt wrote:
>> Severity: serious
>
> I disagree with severity.
>
>> SixXS will shutdown on 2017-06-06[1].
>
> Yes, well-known and
Control: severity -1 important
Control: tag -1 confirmed
Hi Ansgar,
Ansgar Burchardt wrote:
> Severity: serious
I disagree with severity.
> SixXS will shutdown on 2017-06-06[1].
Yes, well-known and already discussed (on IRC IIRC) by us package
maintainers.
> Unless there are other tunnel
Agreed. It may be in our future to opensource the server implementation but
at that point we can stand up a repo for ourselves. Would you be open to
resubmitting in such a scenario?
Pim
On May 30, 2017 14:09, "Ansgar Burchardt" wrote:
> Source: aiccu
> Version: 20070115-17
>
Source: aiccu
Version: 20070115-17
Severity: serious
SixXS will shutdown on 2017-06-06[1]. Unless there are other tunnel
providers used with aiccu, it seems useless to include in stretch.
>From a quick glance at [2], SixXS is the only provider using AYIYA and
TIC which is what I believe aiccu
6 matches
Mail list logo