Lastly, I would like to thank Brian for his impressively 16-years long
work on
mime-support. Brian, feel free to stay among the uploaders !
Thanks. I wish I had the energy to make some of the much-needed changes
but I'm just not involved with the project enough these days to have a good
, Charles Plessy ple...@debian.org wrote:
Le Fri, Jul 13, 2012 at 10:12:34PM +0200, Brian White a écrit :
That seems a reasonable plan to me. I've orphaned the mime-support
package, however, because I have no time to work on it right now and do
not
expect to have any for the foreseeable future
That seems a reasonable plan to me. I've orphaned the mime-support
package, however, because I have no time to work on it right now and do not
expect to have any for the foreseeable future.
-- Brian
On Fri, Jul 13, 2012 at 8:26 PM, Vincent Bernat ber...@debian.org wrote:
❦ 13 juillet 2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 12 Feb 2012 21:06:40 +0100
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.52-1
Distribution: unstable
Urgency: low
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 12 Nov 2010 20:52:43 +0100
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.51-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 12 Nov 2010 20:54:06 +0100
Source: scribble
Binary: scribble
Architecture: source all
Version: 1.11-1
Distribution: unstable
Urgency: low
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh...@pobox.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 08 Dec 2009 19:15:04 +0100
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.48-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 18 Jun 2009 22:54:51 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.47-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 18 Jun 2009 22:04:29 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.45-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 18 Jun 2009 22:54:51 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.46-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White bcwh...@pobox.com
Changed-By: Brian White bcwh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Jun 2008 15:44:03 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.44-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 05 Jun 2008 14:43:44 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.43-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 28 May 2008 16:30:52 +0200
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.42-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 1 Jan 2008 17:35:48 +0100
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.40-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 19 Dec 2006 10:54:39 -0500
Source: scribble
Binary: scribble
Architecture: source all
Version: 1.10-2
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 4 Dec 2006 22:17:10 -0500
Source: scribble
Binary: scribble
Architecture: source all
Version: 1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 4 Dec 2006 15:09:27 -0500
Source: genpower
Binary: genpower
Architecture: source i386
Version: 1.0.5-2
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 4 Dec 2006 14:47:44 -0500
Source: squid-prefetch
Binary: squid-prefetch
Architecture: source all
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 4 Dec 2006 15:45:37 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.38-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 4 Dec 2006 22:22:38 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.39-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 16 Jul 2006 21:25:43 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.37-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 2 Mar 2006 20:09:20 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.36-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 22:11:35 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.35-1
Distribution: unstable
Urgency: high
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sat, 14 May 2005 09:07:29 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.34-1
Distribution: unstable
Urgency: high
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Thu, 5 May 2005 10:47:28 -0400
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.9-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Thu, 5 May 2005 10:42:00 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.32-1
Distribution: unstable
Urgency: high
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Thu, 5 May 2005 20:55:38 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.33-1
Distribution: unstable
Urgency: high
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Fri, 25 Mar 2005 23:06:27 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.8-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 21 Mar 2005 19:33:56 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 20 Mar 2005 21:56:07 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 22 Feb 2005 19:06:47 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.31-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 22 Feb 2005 00:48:40 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.30-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 4 Jan 2005 09:30:14 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.29-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 4 Jan 2005 09:39:52 -0500
Source: squid-prefetch
Binary: squid-prefetch
Architecture: source all
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 4 Jan 2005 17:18:24 -0500
Source: genpower
Binary: genpower
Architecture: source i386
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Fri, 16 Jul 2004 08:28:42 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.28-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 14 Jul 2004 20:48:53 -0400
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.27-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 5 May 2004 08:03:51 -0400
Source: signify
Binary: signify
Architecture: source all
Version: 1.14-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 7 Apr 2004 08:07:27 -0400
Source: signify
Binary: signify
Architecture: source all
Version: 1.13-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 5 Apr 2004 07:56:32 -0400
Source: squid-prefetch
Binary: squid-prefetch
Architecture: source all
Version: 0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 3 Mar 2004 07:47:41 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.26-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 16 Feb 2004 19:42:41 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 16 Feb 2004 20:47:03 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.25-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 11 Aug 2003 09:45:02 -0400
Source: squid-prefetch
Binary: squid-prefetch
Architecture: source all
Version: 0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 28 Jan 2004 15:50:00 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 27 Jan 2004 08:45:39 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 27 Jan 2004 08:49:39 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Tue, 27 Jan 2004 16:48:12 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sat, 17 Jan 2004 22:50:51 -0500
Source: scrabble
Binary: scrabble
Architecture: source all
Version: 1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 23 Feb 2003 12:42:07 -0500
Source: signify
Binary: signify
Architecture: source all
Version: 1.12-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sat, 17 Jan 2004 23:09:35 -0500
Source: genpower
Binary: genpower
Architecture: source i386
Version: 1.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sat, 17 Jan 2004 22:32:05 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.24-1
Distribution: unstable
Urgency: high
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
Brian White [EMAIL PROTECTED] wrote:
[...]
I've avoided changing to OpenSSH at home because I'm unsure how to
convert the keys from the SSH2 format to the OpenSSH format.
[...]
Afaict ssh-keygen from OpenSSH can do that:
-i This option will read an unencrypted private (or public
SCP doesn't work (I suspect) because I'm using the SSH2 package once
found in non-free.
Oh, ssh2 is broken, yes. Try 'scp -1', perhaps?
I don't keep ssh1 installed for security reasons. sigh
I mentioned this (and the reasons why) some time back.
Care to reiterate? I can't remember,
The queue daemon can no longer handle PGP 2.x keys; I don't know why
and since a) the number of developers still using these kind of keys
for uploads can be counted on the fingers of a mutilated hand, b)
there are alternative methods of uploads available to the few who do,
c) queued is in
* Brian White [EMAIL PROTECTED] [2003-09-20 07:37]:
Neither SCP nor anonymous-FTP methods work and I want to get that
fixed.
SSH works. SCP doesn't.
Well, it works for everyone else. So it would be good if you'd find
out why it doesn't work for you. In the meantime, you can put
What do I have to do to fix this problem? My key is valid, has been
signed, and was uploaded to the keyserver via gpg --send-keys.
Why do I continue to get these messages? The only way I can upload
packages is to use SSH to connect to ftp-master and then use wget
to fetch the various files from
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 11 Aug 2003 09:45:02 -0400
Source: squid-prefetch
Binary: squid-prefetch
Architecture: source all
Version: 0.5-1
Distribution: experimental
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Wed, 7 May 2003 11:58:11 -0400
Source: jukebox-mercury
Binary: jukebox-mercury
Architecture: source all
Version: 0.1-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 23 Feb 2003 13:27:20 -0500
Source: genpower
Binary: genpower
Architecture: source i386
Version: 1.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 23 Feb 2003 12:42:07 -0500
Source: signify
Binary: signify
Architecture: source all
Version: 1.11-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Sun, 23 Feb 2003 12:39:36 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.21-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 4 Nov 2002 23:07:16 -0500
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.20-1
Distribution: unstable
Urgency: medium
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 4 Nov 2002 22:42:56 -0500
Source: ferret
Binary: ferret
Architecture: source i386
Version: 2.4-3
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description:
ferret
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 4 Nov 2002 23:24:02 -0500
Source: signify
Binary: signify
Architecture: source all
Version: 1.10-1
Distribution: unstable
Urgency: low
Maintainer: Brian White [EMAIL PROTECTED]
Changed-By: Brian White [EMAIL PROTECTED]
Description
Is there anybody here using the Sangoma WANPIPE cards to do X.25?
Brian
( [EMAIL PROTECTED] )
---
When you love someone, you're always insecure.
Would somebody please moderate debian-devel-announce? There are just far
too many people posting to it about things that should not be there. A few
other people have already expressed concern over this. Thank you!
Brian
In accordance with the plan published last week, Slink should now
be in an unchanging state. Packages will be accepted only if
absolutely necessary. Bugs that still exist will probably be released.
All architectures should start making sure their distributions are up
to date with the others.
You know, I don't see this as grave. It means that a user can
effectively export to the world any file readable by www-data. In
general, this means only things that can be read by public. So,
the user can't intentionally export anything that he/she couldn't already
do by other means.
Previously Brian White wrote:
apache32204 user directories allow symlinks to other files
[0] (Johnie Ingram [EMAIL PROTECTED])
We should just force SymLinksIfOwnerMatch for /home to solve this.
You know, I don't see this as grave. It means that a user can
Hmmm... If things were installed by hand (dpkg --install dpkglib...)
or if install were to fail between the two packages, then you could have
a problem where the install tool doesn't function, right?
Right. But since libdpkg is still a part of the dpkg package we
shouldn't need to worry
Previously Brian White wrote:
apache32204 user directories allow symlinks to other files [0]
(Johnie Ingram [EMAIL PROTECTED])
We should just force SymLinksIfOwnerMatch for /home to solve this.
You know, I don't see this as grave. It means that a user can
effectively
To do so would indicate that Slink officially supports v2.2 of the kernel,
which it does not.
What about a README file that says: No, Debian doesn't officially
support 2.2, but for those people who hadn't enough bandwidth but
enough courage here are the sources.
I don't mind so much
In my more than honest opinion, I think util-linux 2.9g should be included
in slink. Developments in the computer business are going fast, as everyone
knows, and on the day slink will get released, I think a lot of people who
are going to upgrade to slink, also want to have the newest kernel,
Ok, so if we really want a Debian 2.1 that is 100% kernel 2.2.x
compatible it needs this package to be included in frozen.
I've just uploaded it in Incoming/ 10 minutes ago.
Non-developers can also access it at http://www.ldsol.com/~vincent/
(NB: there are _2_ binary packages to install:
We do not officially support the 2.2 kernel in Slink. People who want to
use 2.2 will have to compile it themselves and may have to upgrade some
packages.
But what about shipping an extra directory support_2.2 which
contains the kernel packages and the necessary utilities together
with
Including the source package I could be convinced of. At least then
people have to think about what they're doing before causing potential
problems.
This think about what they are doing thing is precisely one of the
reasons the extra priority does exist.
According to
Disclamers are of marginal use. It will appear as installable and tell
people to install me just as an elevator buttun tells people push me.
Installing a kernel 2.2 source package just dumps a tar file in /usr/src. I
don't see how this could break a system. Actually building and
Would anyone object if kernel 2.2 were packaged up at least as a
kernel-source package for slink? 2.0.3x would remain slink's default kernel,
would be used on the boot disks, etc, but this would let people get ahold of
kernel 2.2 easily on a debian cdrom, and it would let us say that debian
On Thu, Jan 21, 1999 at 12:34:57PM -0800, Joey Hess wrote:
Would anyone object if kernel 2.2 were packaged up at least as a
kernel-source package for slink? 2.0.3x would remain slink's default kernel,
I'de really like to see a kernel-image too, atleast for the non-i386 ports
to use. The
No. We had enough problems upgrading from 2.0.35 to 2.0.36. This would
be a major change and have corresponding reprocussions. I'm sure it's
very stable, but it will have incompatibilities.
No-one's saying this would be the default kernel. I think including a kernel
image would be
Would anyone object if kernel 2.2 were packaged up at least as a
kernel-source package for slink? 2.0.3x would remain slink's default kernel,
would be used on the boot disks, etc, but this would let people get ahold of
kernel 2.2 easily on a debian cdrom, and it would let us say that
Brian make any difference. Both will show up in dselect and it would
Brian be trivial for someone to install the new kernel... and then
Heh, thats the idea. :-)
Brian wonder why things don't work.
Little things that few notice, apparently -- I would've sworn slink
and 2.2.0-final
There is precedent for this as there is a 2.1.125 package in slink now.
I think it's not a big deal if there are big disclaimers attached that
slink is not a 2.2 targetted dist.
Disclamers are of marginal use. It will appear as installable and tell
people to install me just as an
Including the source package I could be convinced of. At least then
people have to think about what they're doing before causing potential
problems.
This think about what they are doing thing is precisely one of the
reasons the extra priority does exist.
According to this it should
After considerable delay, Slink is almost ready for release. As such, it
will go into the deep freeze on Wednesday, January 20th. New uploads
will be _greatly_ restricted. Also, the following packages will be
removed because of release-critical bugs still open against them:
Unless
Debian v2.1 (Slink) Deep Freeze
After considerable delay, Slink is almost ready for release. As such, it
will go into the deep freeze on Wednesday, January 20th.
Brian, will you please consider to do a ftp.debian.org bug hunting *before*
doing any deep freeze?
The
dpkg 17624 dpkg: installs regular dir when .deb contains
symlink !
21182 dpkg: dpkg can go into an infinite loop with
--force-configure-any
28519 dpkg: dpkg creates circular symlinks
28817 dpkg takes no care over
, but with luck it can be as
early as the end of January. More likely, though, is mid-February.
Brian White [EMAIL PROTECTED]
Debian Release Manager
What do you think we should do with the Gnome stuff?
The Gnome 0.30 stuff is still under rather heavy development. The
current packages in Slink are pretty much alpha-quality. Lots of
things don't work. It sounds like there will probably be a 1.0
release coming up in a few months that
smb2www 27641 perl 5.005-02 breaks smb2www [0] (Craig Small
[EMAIL PROTECTED])
This one also refers to the version of perl which has been
removed. (It broke every module, so there are several such bug reports)
I knew about it, but not which bugs it affected. I'll
So far, Alpha is looking near ready and we are shooting to release with
slink/i386. A caveat, however, is that we need to resolve some big egcs
issues SOON or else we can't release (as is, 1.1b will not compile two or
three vital packages correctly).
There is one, MAJOR, huge, massive,
Oh, i can generate a kernel-image_2.1.125-1_powerpc.deb along with source
and dsc files and upload it to master, but will you and the other arch
maintainer agree with this??
If it's a powerpc package only, I don't see why there would be a problem.
It should get installed
On Wed, Oct 14, 1998 at 12:19:30PM -0400, Brian White wrote:
strace26065 strace confused about sigaction flags [51]
(Wichert Akkerman [EMAIL PROTECTED])
Hmm. Why is this bug important anyway? I've looked at the bug report and
found no explanation.
Darn. I downgraded
Could I get some official word on which architectures wish to be included
in the 2.1 release of Debian? Thanks!
Brian
( [EMAIL PROTECTED] )
---
Could I get some official word on which architectures wish to be included
in the 2.1 release of Debian? Thanks!
So far, Alpha is looking near ready and we are shooting to release with
slink/i386. A caveat, however, is that we need to resolve some big egcs
issues SOON or else we can't
25412 htdig: htdig ignores config file stuff/absolute
pathnames compiled in [70] (Gergely Madarasz [EMAIL PROTECTED])
infocom 21478 infocom: Integrating infocom interpreters [175]
(Brian White [EMAIL PROTECTED])
jdk1.127097 jdk1.1: error in installing jdk1.1: links
perl 27604 Perl @INC needs /usr/lib/perl5 [7] (Darren
Stalder [EMAIL PROTECTED])
perl 27738 perl: @INC does not contain /usr/lib/perl5 [0]
(Darren Stalder [EMAIL PROTECTED])
This doesn't affect the current perl version but the version to be
used in 2.2.
All packages destined for Slink must have been uploaded to master.debian.org's
incoming directory no later than October 16th, 18:30 GMT.
The process of freezing Hamm will take place over the weekend. No new
uploads will be processed after 18:30 GMT that day.
Could I get some official word on which architectures wish to be included
in the 2.1 release of Debian? Thanks!
PowerPC has more or less given up on making 2.1. We're moving well,
but I'm of the inclination we shouldn't release until we have a truly
stabilized libc - or at least
1 - 100 of 180 matches
Mail list logo
