On Fri, Oct 08, 2004 at 03:07:24PM +0200, Wouter Verhelst wrote:
I can imagine that there are more candidates than the ones in
non-US/non-free now.
Indeed. I maintain ckermit, and would like to enable the crypto
options, which would mean a move to non-US/non-free.
A while ago, I offered to
* Ian Beckwith ([EMAIL PROTECTED]) [041013 15:35]:
As nothing has been uploaded to non-US/non-free since before the
compromise, I suspect it hasn't been reenabled yet.
Exactly. But we need to update non-US before release of sarge.
I suspect, since the crypto-in-main move, that crypto no
On Wed, Oct 13, 2004 at 02:30:24PM +0100, Ian Beckwith wrote:
I suspect, since the crypto-in-main move, that crypto no longer needs
to live in non-US/non-free, and could move to non-free.
No, this is not the case.
The expert restrictions which prompted the non-US archive still exist,
they have
On Wed, Oct 13, 2004 at 03:54:33PM +0200, Wouter Verhelst wrote:
On Wed, Oct 13, 2004 at 02:30:24PM +0100, Ian Beckwith wrote:
I suspect, since the crypto-in-main move, that crypto no longer needs
to live in non-US/non-free, and could move to non-free.
No, this is not the case.
The
On Wed, Oct 13, 2004 at 03:41:49PM +0200, Andreas Barth wrote:
* Ian Beckwith ([EMAIL PROTECTED]) [041013 15:35]:
As nothing has been uploaded to non-US/non-free since before the
compromise, I suspect it hasn't been reenabled yet.
Exactly. But we need to update non-US before release of
Florian Weimer wrote:
* Andreas Barth:
So, the only thing left now is pgp5i in non-US/non-free (and AFAICS this
can't go to non-free).
What's the security patching status of pgp5i?
What are you referring to?
Regards,
Joey
--
The good thing about standards is that there are
* Martin Schulze:
Florian Weimer wrote:
* Andreas Barth:
So, the only thing left now is pgp5i in non-US/non-free (and AFAICS this
can't go to non-free).
What's the security patching status of pgp5i?
What are you referring to?
I've checked in the meantime. The RNG issue has been
* Andreas Barth ([EMAIL PROTECTED]) [040928 18:36]:
The only package in non-US/main left over is vtun. I spoke with the
maintainer, and he wants to do a new upload as soon as the new release
of vtun happens. I specifically asked him to upload his package to main
ASAP if this is ok from the
On Fri, Oct 08, 2004 at 10:12:24AM +0200, Andreas Barth wrote:
* Andreas Barth ([EMAIL PROTECTED]) [040928 18:36]:
The only package in non-US/main left over is vtun. I spoke with the
maintainer, and he wants to do a new upload as soon as the new release
of vtun happens. I specifically asked
* Wouter Verhelst ([EMAIL PROTECTED]) [041008 17:00]:
On Fri, Oct 08, 2004 at 10:12:24AM +0200, Andreas Barth wrote:
* Andreas Barth ([EMAIL PROTECTED]) [040928 18:36]:
The only package in non-US/main left over is vtun. I spoke with the
maintainer, and he wants to do a new upload as soon
* Andreas Barth:
So, the only thing left now is pgp5i in non-US/non-free (and AFAICS this
can't go to non-free).
What's the security patching status of pgp5i?
Hi,
I did some analysis of the packages in non-US. Short summary: Only two
are left over, but both have an interessted maintainer. One of them
could be moved to main, the other is in non-US/non-free, and needs to
stay there.
The only package in non-US/main left over is vtun. I spoke with the
Hi Andreas,
On Tuesday, 28 Sep 2004, you wrote:
The only package in non-free left over is pgp5i; it is orphaned, but
somebody wants to adopt it and has already made packages (quite
recently). See http://bugs.debian.org/237370 for details.
non-free
Package: pgp5i
ITA, #237370
On 2004-06-26 Branden Robinson [EMAIL PROTECTED] wrote:
On Wed, Jun 23, 2004 at 08:01:16AM +0200, Andreas Metzler wrote:
[...]
15 soon. links-ssl will be replaced by a dummy-package depending on
elinks if the ftp-master's approve the respective upload.[1]
I found no footnote [1] in your
On Wed, Jun 23, 2004 at 08:01:16AM +0200, Andreas Metzler wrote:
On 2004-06-23 Frederik Schueler [EMAIL PROTECTED] wrote:
Since sarge will release with crypto in main, what is the current
status of the remaining packages in non-US? Can't all packages be
migrated into main so sarge can
On 2004-06-23 Frederik Schueler [EMAIL PROTECTED] wrote:
Since sarge will release with crypto in main, what is the current
status of the remaining packages in non-US? Can't all packages be
migrated into main so sarge can release without non-US?
According to the Sources.gz files on
Hi,
Since sarge will release with crypto in main, what is the current
status of the remaining packages in non-US? Can't all packages be
migrated into main so sarge can release without non-US?
According to the Sources.gz files on non-us.debian.org we have 16
source packages left in non-us/main
On Wed, Jun 23, 2004 at 12:50:05AM +0200, Frederik Schueler wrote:
Since sarge will release with crypto in main, what is the current
status of the remaining packages in non-US? Can't all packages be
migrated into main so sarge can release without non-US?
According to the Sources.gz files
18 matches
Mail list logo