[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

unsubscribe





-----Original Message-----
From: debian-devel-digest-request@lists.debian.org
To: debian-devel-digest@lists.debian.org
Sent: Thu, 27 Mar 2003 18:46:27 -0600 (CST)
Subject: debian-devel-digest Digest V2003 #375

To UNSUBSCRIBE, send email to debian-devel-digest-request@lists.debian.org with
a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


debian-devel-digest Digest				Volume 2003 : Issue 375

Today's Topics:
  =?GB2312?B?vtO80sLE0NCx2LG4o63KscnQx  [ "SHIBO" <SOHU@SOHU.COM> ]
  RE: Distribution of Authentication C  [ "Julian Mehnle" <lists@mehnle.net> ]
  Bug#186485: ITP: emacsbidi -- Emacs-  [ Ayman Negm <a.negm@hamburg.de> ]
  Bug#186489: ITP: ftp.debian.org -- p  [ Ayman Negm <a.negm@hamburg.de> ]
  Bug#186503: ITP: fibusql -- Web base  [ Martin Pitt <martin@piware.de> ]
  Re: should I orphan linux-wlan-ng?    [ Eduard Bloch <edi@gmx.de> ]
  Re: bugs in woody version, fixed in   [ Francesco Paolo Lovergine <frankie@ ]
  Re: BHS: Bug help system              [ Raphael Hertzog <hertzog@debian.org ]
  Re: manpage character cleanup for UT  [ Vineet Kumar <debian-devel@virtual. ]
  Bug#186511: ITP: wmfishtime -- Docka  [ Bastian Kleineidam <calvin@debian.o ]
  Re: manpage character cleanup for UT  [ Decklin Foster <decklin@red-bean.co ]
  Bug#186512: ITP: wiliki -- Yet anoth  [ YAEGASHI Takeshi <yaegashi@debian.o ]
  Re: manpage character cleanup for UT  [ Colin Watson <cjwatson@debian.org> ]
  Re: BHS: Bug help system              [ "H. S. Teoh" <hsteoh@quickfur.ath.c ]
  Re: Distribution of Authentication C  [ Bernd Eckenfels <lists@lina.inka.de ]
  perl and libtk-img                    [ davidw@dedasys.com (David N. Welton ]
  Re: how to handle "woody" bugs corre  [ Brian May <bam@debian.org> ]
  Re: ifupdown writes to /etc... a bug  [ Brian May <bam@debian.org> ]
  Re: RFC: New required package: libbl  [ Goswin Brederlow <goswin.brederlow@ ]
Date: Thu, 27 Mar 2003 18:05:09 +0800
From: "SHIBO" <SOHU@SOHU.COM>
To: debian-devel@lists.debian.org
Subject: =?GB2312?B?vtO80sLE0NCx2LG4o63KscnQxrfFxrPkxvi0srT6wO3P+srb?=
Message-Id: <E18yUGO-0008Gs-00@gluck.debian.org>
Reply-To: SOHU@SOHU.COM
Content-Type: text/html;charset="GB2312"

»òÐíµ±Äú¼ÒÀïÀ´¿Íºó£¬Ôø¾­ÎªÃ»Óеط½ÌṩסËÞ¶ø·¸³î£¬Ò²ÐíÄúΪ¾­³£°á¼Ò£¬´ó´²¼ÓС°ü¶ø·³ÄÕ£¬Ò²ÐíÄúΪÁ˶ȹýÒ°ÍâÒ»¸öÓä¿ìµÄÖÜÄ©²»µÃ²»°áÔË´óµÄ´²µæ£¬ÄúÊÇ·ñÏë¹ý£¬ÕâÒ»ÇÐÆäʵÓÃÒ»¸öʱÉеÄÆ·ÅƳäÆø´²¾Í¿ÉÒÔ½â¾ö£¿¹úÄÚÆ·ÖÊÒ»Á÷µÄ̤̤ÀÖÅƳäÆø´²·ÖÈýÖֳߴ磺90¡Á195¡Á20£¬137¡Á188¡Á23£¬150¡Á200¡Á23£¬²¢ÅäÓнÅ̤³äÆø±Ã£¬¿ÉÒÔÑ¡¹ºµç¶¯³äÆø±Ã¡£±¾É̳ǻ¹´úÀí¹úÄÚÆ·ÅÆÔö¸ßЬ¡¢µÈ¶àÖÖÉÌÆ·£¬»¶Ó­ÄúÑ¡¹º¡¢´¹Ñ¯¡£http://www.hitach.cn;http://www.shiboshop.com,Èç¹û¸ÃÓʼþÓдòÈÅÄú£¬ÇëÄúÖ±½Óɾ³ý¡£ÎÒÔÙ´ËÏòÄú±íʾǸÒ⣡£¡
Date: Thu, 27 Mar 2003 15:02:05 +0100
From: "Julian Mehnle" <lists@mehnle.net>
To: "Bernd Eckenfels" <lists@lina.inka.de>
Cc: <debian-devel@lists.debian.org>
Subject: RE: Distribution of Authentication Certificates
Message-ID: <EHEOIEJMBFBKCKMPHFJKCEOHDDAA.lists@mehnle.net>
In-Reply-To: <87of42z6f5.fsf@orcus.priv.at>
Content-Type: text/plain;
	charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Robert Bihlmeyer wrote:
> Bernd Eckenfels <lists@lina.inka.de> writes:
> > On Sun, Mar 16, 2003 at 09:35:00PM +0100, Robert Bihlmeyer wrote:
> > > TLS/SSL is a perfectly fine protocol with self-signed certificates.
> >
> > Unfortunatelly it does not support named based virtual hosts,
>
> mozilla has some code to allow matching multiple hosts with the cn
> (you can list them, and I think something like *.foo.bar is also
> possible). Dunno if that is standardised somewhere.

Netscape 4- uses the following scheme:

http://wp.netscape.com/eng/security/ssl_2.0_certificate.html#Site
(See "Subject Common Name" a bit further down)

I think Mozilla works the same way, plus it supports the "subjectAltName"
SSLv3 extension (as does Internet Explorer 5+, but not Opera 7-!).

Julian.
Date: Thu, 27 Mar 2003 16:24:39 +0100
From: Ayman Negm <a.negm@hamburg.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#186485: ITP: emacsbidi -- Emacs-bidi based on GNU Emacs-21.3.50 with 
Arabic and Hebrew support
Message-ID: <20030327152439.GA1418@matrix>
Reply-To: Ayman Negm <a.negm@hamburg.de>, 186485@bugs.debian.org
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: wnpp
Version: unavailable; reported 2003-03-27
Severity: wishlist


* Package name    : emacsbidi
  Version         : 0.9
  Upstream Author : http://www.m17n.org
* URL             : http://www.m17n.org/emacs-bidi/index.html
* License         : GPL
  Description     : Emacs-bidi based on GNU Emacs-21.3.50 with Arabic and Hebrew 
support

Emacs-Bidi is bases on the great GNU Emacs21 and it support UTF-8 and
bidi Language like Arabic and Hebrew and more like Japanese. It does
not have all the modules the Orginal one have like ECB but I hope soon.
I would like to maintian it, I have created a Package from it.


Regards
Ayman

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux matrix 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro


-- 
Date: Thu, 27 Mar 2003 16:58:26 +0100
From: Ayman Negm <a.negm@hamburg.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#186489: ITP: ftp.debian.org -- please remove uploaded package 
emacsbidi 21.3.50
Message-ID: <20030327155826.GA1453@matrix>
Reply-To: Ayman Negm <a.negm@hamburg.de>, 186489@bugs.debian.org
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: wnpp
Version: unavailable; reported 2003-03-27
Severity: wishlist


* Package name    : ftp.debian.org
  Version         : N/A
  Severity	  : Normal
	 
Please remove my uploaded package, because upstream changed
versioning-system.

please see #184831

Regards
Ayman

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux matrix 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro


-- 
Date: Thu, 27 Mar 2003 18:58:37 +0100
From: Martin Pitt <martin@piware.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#186503: ITP: fibusql -- Web based double-entry accounting
Message-Id: <E18ybe9-0002HE-00@donald.entenhausen.net>
Reply-To: Martin Pitt <martin@piware.de>, 186503@bugs.debian.org

Package: wnpp
Version: N/A; reported 2003-03-27
Severity: wishlist

  Package name    : fibusql
  Version         : 0.2.3
  Upstream Author : Martin Pitt <martin@piware.de>
  URL             : http://www.piware.de/projects.shtml
  License         : GPL
  Description     : Web based double-entry accounting

  FibuSQL is a web based double-entry accounting software mainly
  designed for private use, in the sense that it currently has no
  special support for tax accounts etc.

  It relies on a database to store all data; mySQL and PostgreSQL have
  been tested, but others supported by PEAR should work as well. 

  Currently, this package is only available in German language, but I
  will supply an English version soon.

  I intend to upload this package with the help of a sponsor.

Martin Pitt

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux donald 2.4.20-grsec #1 Mit Feb 26 19:39:59 CET 2003 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro
Date: Thu, 27 Mar 2003 14:35:15 +0100
From: Eduard Bloch <edi@gmx.de>
To: debian-devel@lists.debian.org
Subject: Re: should I orphan linux-wlan-ng?
Message-ID: <20030327133515.GA4108@zombie.inka.de>
References: <20030324175044.GA4107@dragon.kitenet.net> <200303262108.13844.ieure@debian.org>
In-Reply-To: <200303262108.13844.ieure@debian.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

#include <hallo.h>
* Ian Eure [Wed, Mar 26 2003, 09:08:13PM]:

> Please continue maintaining linux-wlan-ng and apt-src. I completely agree that 
> having the same sources in the archive twice is wasteful and technically 

Please check the sizes. We have additional kernel-source* .deb packages
in the archive, much bigger than all module-source packages and nobody
cares about it.

> inferior to using apt-src. apt-src has the potential to pull lots of users 
> from Gentoo and other source-based distros which have become popular in the 
> last couple years.
...
> I do think that we should eventuall phase out all the source-binary packages 
> in favor of using apt-src; a transition period of a release or two should be 
> sufficient.

I did not request anything different. Keep creating -source package as
usual, then extend apt-src to allow smooth transition, then extend
debian-cd to include such essential source packages in default config
and only then begin to kill -source packages. And not vice versa.

Gruss/Regards,
Eduard.
-- 
Damit immer mehr immer weniger tun können, müssen immer weniger immer
mehr tun.
Date: Thu, 27 Mar 2003 19:19:24 +0100
From: Francesco Paolo Lovergine <frankie@debian.org>
To: debian-devel@lists.debian.org
Subject: Re: bugs in woody version, fixed in woody-proposed-updates
Message-ID: <20030327181924.GA1218@gandalf.libero.it>
References: <20030324172003.GA753@nimrod> <Pine.LNX.4.53.0303241300420.3335@samadhi.braincells.com>
In-Reply-To: <Pine.LNX.4.53.0303241300420.3335@samadhi.braincells.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Mar 24, 2003 at 01:01:06PM -0500, Jaldhar H. Vyas wrote:
> On Mon, 24 Mar 2003, Oliver Kurth wrote:
> 
> > I have fixed a few bugs, which apply to the woody version of a package
> > only, and uploaded to stable, so the fixed packages are now in
> > woody-proposed-updates. What can I do with the bugs now? Close them, or
> > wait until they have made it to the next revision?
> >
> 
> Tag them pending until they actually enter woody.

IF they will be accepted in woody... That's not so obvious.

-- 
Francesco P. Lovergine
Date: Thu, 27 Mar 2003 19:42:08 +0100
From: Raphael Hertzog <hertzog@debian.org>
To: Debian Devel <debian-devel@lists.debian.org>
Subject: Re: BHS: Bug help system
Message-ID: <20030327184207.GA14371@home.ouaza.com>
References: <1048613100.13652.855.camel@pathfinderii.chu.cam.ac.uk> 
<20030325201158.GA3644@crystal> <3E81BE6A.1080103@beamnet.de> 
<20030326163119.GL1871@balrog.logic.univie.ac.at> <3E824D7F.4080701@beamnet.de> 
<E18yRkr-00018f-Oh@mid.downhill.at.eu.org> <3E82B85A.7080903@beamnet.de> 
<20030327094343.GA23148@crystal>
In-Reply-To: <20030327094343.GA23148@crystal>
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Le Thu, Mar 27, 2003 at 04:43:43AM -0500, H. S. Teoh écrivait:
> Now having said all that, I do agree that current NMU procedures could do
> with some massaging. It seems a bit pushing it to require at least 6 weeks
> to NMU a wishlist fix (2-4 weeks after submitting patch, 2 weeks to
> confirm maintainer is MIA, 2 weeks in delayed upload queue). Each step in
> itself is reasonable; you don't want to encourage hasty or careless NMU's,
> but added together, it seems a bit too tedious.

You haven't read the latest version of developers-reference. It's no
more so precise in the delays, it says :
- file bug
- wait a few days
- send patch
- wait a few days
- upload nmu to DELAYED/7-day and inform the maintainer (and send the
  patch for the complete NMU)

Of course if you file bug with patches, or if some bugs already have
patches, there's just one "wait a few days" and it's up to you to decide
if "few" is 2, 3, 4, 5 or more. :-)

I think the NMU rules are quite good now. But people keep complaining
about NMU rules instead of doing NMU ... ;-)

Cheers,

PS: http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-nmu-when
-- 
Raphaël Hertzog -+- http://www.ouaza.com
Formation Linux et logiciel libre : http://www.logidee.com
Date: Thu, 27 Mar 2003 11:15:13 -0800
From: Vineet Kumar <debian-devel@virtual.doorstop.net>
To: debian-devel@lists.debian.org
Subject: Re: manpage character cleanup for UTF-8 compatibility
Message-ID: <20030327191513.GB13011@doorstop.net>
References: <20030326000151.GA12397@doorstop.net> <20030326023025.GC18769@riva.ucam.org> 
<20030326035044.GB8835@doorstop.net> <1048696157.2871.2.camel@whosthere>
In-Reply-To: <1048696157.2871.2.camel@whosthere>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H"
Content-Disposition: inline

--4SFOXa2GPu3tIq4H
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Anthony DeRobertis <asd@suespammers.org> [20030326 09:31 PST]:
> On Tue, 2003-03-25 at 22:50, Vineet Kumar wrote:
>=20
> > Right.  That would help usability in the short term, but it feels more
> > like a workaround than a fix.=20
>=20
> Why should a user have to know the difference between a minus sign, en
> dash, em dash, hyphen, etc. to search a manpage? They all look
> approximately the same --- just different lengths, and sometimes
> different vertical position and width.

I agree that this is a UI improvement for the pager, but I don't think
it fully addresses the issue of using the wrong characters, specifically
because of the copy-paste problem.

good times,
Vineet
--=20
http://www.doorstop.net/
--=20
http://www.anti-dmca.org/=09

--4SFOXa2GPu3tIq4H
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+g03B7z3S33fUb9ERAlb/AKCS8O/e/RoP3UIkQwzZ1A/zTRtPOQCg8QGo
fmk/g1ypTjl7wbved5a9ILs=
=i6fz
-----END PGP SIGNATURE-----

--4SFOXa2GPu3tIq4H--
Date: Thu, 27 Mar 2003 20:23:43 +0100
From: Bastian Kleineidam <calvin@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#186511: ITP: wmfishtime -- Dockable clock app for WMaker, BlackBox, 
E, SawFish etc
Message-ID: <20030327192343.2093.qmail@localhost>
Reply-To: Bastian Kleineidam <calvin@debian.org>,
	186511@bugs.debian.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Package: wnpp
Version: unavailable; reported 2003-03-27
Severity: wishlist

* Package name    : wmfishtime
  Version         : 1.23
  Upstream Author : timecop <timecop@japan.co.jp>
* URL             : http://www.ne.jp/asahi/linux/timecop/software/wmfishtime-1.23.tar.gz
* License         : GPL
  Description     : Dockable clock app for WMaker, BlackBox, E, SawFish etc

Welcome to WMFishTime, winner of the "Best Waste Of CPU Power" award!
This is a dockable clock application for WMaker, BlackBox, E, SawFish etc. .

The features include gradient backdrop, anti-aliased hour, minute, second hands
alpha-blended bubbles, real-time sprite engine, precision accuracy,
and shows if you have unread mail (in the form of swaying weed blocking the 
day/month numbers).

Well, this is just your standard time dockapp. Top part has the clock face,
bottom part has day of the week, followed by day, followed by month. Yellow
hand counts seconds, green hand counts minutes, red hand counts hours. Few
seconds after startup there are at least 32 bubbles floating up behind the
clock face.  There are 4 fishes randomly swimming back and forth. If you move
your mouse inside the dockapp window, the fish will get scared and run away.
If you compiled in mail checking (default), then whenever you get new mail
in the file pointed to by the $MAIL variable, it will display green weed
partially blocking the day/month counter, to remind you to read your mail.
If $MAIL is not set, nothing happens.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux treasure 2.4.20-treasure1 #1 Wed Mar 5 21:30:50 CET 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE@euro
Date: Thu, 27 Mar 2003 14:27:44 -0500
From: Decklin Foster <decklin@red-bean.com>
To: debian-devel@lists.debian.org
Subject: Re: manpage character cleanup for UTF-8 compatibility
Message-ID: <20030327192744.GA2595@terminus.2y.net>
References: <20030326000151.GA12397@doorstop.net>
In-Reply-To: <20030326000151.GA12397@doorstop.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Vineet Kumar writes:

> The correct groff escape to use in things like command-line options is
> '\-', which renders as the 0x2D minus sign in both UTF-8 and ASCII
> locales.

Does this affect the the use of \- in man page headings to facilitate
parsing by mandb? For example:

.SH "NAME"
frob\-foo \- frobnicate a foo

It looks like that shouldn't be ambiguous (you can split on " \- "), but
I'm not sure that's what actually happens.

-- 
things change.
decklin@red-bean.com
Date: Fri, 28 Mar 2003 04:45:40 +0900
From: YAEGASHI Takeshi <yaegashi@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#186512: ITP: wiliki -- Yet another Wiki clone written in Scheme
Message-Id: <20030327194540.6908733C@arwen>
Reply-To: YAEGASHI Takeshi <yaegashi@debian.org>,
	186512@bugs.debian.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Package: wnpp
Version: unavailable; reported 2003-03-28
Severity: wishlist

* Package name    : wiliki
  Version         : 0.3
  Upstream Author : Shiro Kawai <shiro@acm.org>
* URL             : http://sourceforge.net/projects/wiliki
* License         : BSD
  Description     : Yet another Wiki clone written in Scheme

WiLiKi is yet another Wiki-clone suitable for intra-net collaborative
work in multilingual environment.  The features include multiple
back-end databases, permission and version control, and easy access
from other programs.
Date: Thu, 27 Mar 2003 20:14:51 +0000
From: Colin Watson <cjwatson@debian.org>
To: debian-devel@lists.debian.org
Cc: Decklin Foster <decklin@red-bean.com>
Subject: Re: manpage character cleanup for UTF-8 compatibility
Message-ID: <20030327201451.GA8457@riva.ucam.org>
References: <20030326000151.GA12397@doorstop.net> <20030327192744.GA2595@terminus.2y.net>
In-Reply-To: <20030327192744.GA2595@terminus.2y.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 27, 2003 at 02:27:44PM -0500, Decklin Foster wrote:
> Vineet Kumar writes:
> > The correct groff escape to use in things like command-line options is
> > '\-', which renders as the 0x2D minus sign in both UTF-8 and ASCII
> > locales.
> 
> Does this affect the the use of \- in man page headings to facilitate
> parsing by mandb? For example:
> 
> .SH "NAME"
> frob\-foo \- frobnicate a foo
> 
> It looks like that shouldn't be ambiguous (you can split on " \- "), but
> I'm not sure that's what actually happens.

That's fine; internally, mandb converts "\-" into "-" solely for the
purpose of parsing headers, and then splits on " - ". (So actually " - "
works on Debian, but " \- " is required for portability as well as to
look better in the way this thread describes.)

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]
Date: Thu, 27 Mar 2003 16:06:17 -0500
From: "H. S. Teoh" <hsteoh@quickfur.ath.cx>
To: Debian Devel <debian-devel@lists.debian.org>
Subject: Re: BHS: Bug help system
Message-ID: <20030327210617.GA29309@crystal>
References: <1048613100.13652.855.camel@pathfinderii.chu.cam.ac.uk> 
<20030325201158.GA3644@crystal> <3E81BE6A.1080103@beamnet.de> 
<20030326163119.GL1871@balrog.logic.univie.ac.at> <3E824D7F.4080701@beamnet.de> 
<E18yRkr-00018f-Oh@mid.downhill.at.eu.org> <3E82B85A.7080903@beamnet.de> 
<20030327094343.GA23148@crystal> <20030327184207.GA14371@home.ouaza.com>
In-Reply-To: <20030327184207.GA14371@home.ouaza.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU"
Content-Disposition: inline

--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 27, 2003 at 07:42:08PM +0100, Raphael Hertzog wrote:
[snip]
> You haven't read the latest version of developers-reference. It's no
> more so precise in the delays, it says :
> - file bug
> - wait a few days
> - send patch
> - wait a few days
> - upload nmu to DELAYED/7-day and inform the maintainer (and send the
>   patch for the complete NMU)

Mmmm, that's what happens when I don't keep up with these ever-changing
documents. :-)

> Of course if you file bug with patches, or if some bugs already have
> patches, there's just one "wait a few days" and it's up to you to decide
> if "few" is 2, 3, 4, 5 or more. :-)
>=20
> I think the NMU rules are quite good now. But people keep complaining
> about NMU rules instead of doing NMU ... ;-)
[snip]

Hmm, this does look much better now. :-) Potentially I can NMU within a
week and not break any rules. (Of course, I may get a few disgruntled DD's
on my back, but that's OK...)

Thanks for your corrections.


T

--=20
"A man's wife has more power over him than the state has." -- Ralph Emerson

--azLHFNyN32YCQGCU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+g2fJBgxOY7BxxAoRAgkWAJ9fr3Np4vKHmBe1sbSgq48EmoY2GgCcD5+q
Ej25CODouT+SDsg0QA7RcL8=
=oRNp
-----END PGP SIGNATURE-----

--azLHFNyN32YCQGCU--
Date: Thu, 27 Mar 2003 23:08:13 +0100
From: Bernd Eckenfels <lists@lina.inka.de>
To: debian-devel@lists.debian.org
Subject: Re: Distribution of Authentication Certificates
Message-ID: <20030327220813.GA8543@lina.inka.de>
References: <87of42z6f5.fsf@orcus.priv.at> <EHEOIEJMBFBKCKMPHFJKCEOHDDAA.lists@mehnle.net>
In-Reply-To: <EHEOIEJMBFBKCKMPHFJKCEOHDDAA.lists@mehnle.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 27, 2003 at 03:02:05PM +0100, Julian Mehnle wrote:
> > mozilla has some code to allow matching multiple hosts with the cn
> > (you can list them, and I think something like *.foo.bar is also
> > possible). Dunno if that is standardised somewhere.
> 
> Netscape 4- uses the following scheme:
> 
> http://wp.netscape.com/eng/security/ssl_2.0_certificate.html#Site
> (See "Subject Common Name" a bit further down)

The real problem is not the CN, but the certificate which the server
present. There is no way (other than having multiple ip addresses) for a
server to know which hostname was requested before the SSL handshake is
ended. This means, if you have domain1.com and domain2.com on a single name
based virtual server, you cant ship a certificate for the requested domain.

*.com or  {domain1,domain2}.com

are of course not a real solution. Personally I think it is good that IE
does not allow such a complicated pattern matching, and most CAs wont
vertify wildcard certificates, also.

Greetings
Bernd
-- 
  (OO)      -- Bernd_Eckenfels@Wendelinusstrasse39.76646Bruchsal.de --
 ( .. )  ecki@{inka.de,linux.de,debian.org} http://home.pages.de/~eckes/
  o--o     *plush*  2048/93600EFD  eckes@irc  +497257930613  BE5-RIPE
(O____O)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!
Date: 27 Mar 2003 14:38:48 -0800
From: davidw@dedasys.com (David N. Welton)
To: debian-devel@lists.debian.org
Subject: perl and libtk-img
Message-ID: <8765q4a0zr.fsf@dedasys.com>
Content-Type: text/plain; charset=us-ascii

[ Please CC me in replies ]

Hi, I have emailed the guy who submitted this bug, with no answer.
Any Perl people want to have a look at it and see if the problem
behavior is still there?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=142998

Thankyou,
-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/
Date: Fri, 28 Mar 2003 10:12:55 +1100
From: Brian May <bam@debian.org>
To: debian-devel@lists.debian.org
Subject: Re: how to handle "woody" bugs correctly
Message-ID: <20030327231254.GB26386@snoopy.apana.org.au>
References: <1048714262.27731.27.camel@p4.domain.lan> <E18yRs5-00018k-6r@mid.downhill.at.eu.org>
In-Reply-To: <E18yRs5-00018k-6r@mid.downhill.at.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 27, 2003 at 08:32:21AM +0100, Andreas Metzler wrote:
> If you take the quoted sentence literally you see that is not talking
> about "the Debian stable distribution" but about "the Debian archive",
> i.e. it is basically ok to simply close bugs that apply only to the
> version in woody, and it is done so frequently. OTOH if you keep it
> open and tag it woody you might not get another bugreport for the same
> problem.

It also gives positive feed back to anyone who experiences a bug "that
bug has already been reported and fixed in unstable" so they can make
decisions like "is it worth upgrading in order to eliminate this bug?"
-- 
Brian May <bam@debian.org>
Date: Fri, 28 Mar 2003 10:25:57 +1100
From: Brian May <bam@debian.org>
To: Russell Coker <russell@coker.com.au>
Cc: Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>,
	debian-devel@lists.debian.org
Subject: Re: ifupdown writes to /etc... a bug?
Message-ID: <20030327232557.GC26386@snoopy.apana.org.au>
References: <1048366825.2770.26.camel@thanatos> <200303230027.54467.russell@coker.com.au> 
<87ptoedlf5.fsf@mrvn.homelinux.org> <200303262318.49684.russell@coker.com.au>
In-Reply-To: <200303262318.49684.russell@coker.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Mar 26, 2003 at 11:18:49PM +0100, Russell Coker wrote:
> Samba has it's smbpasswd file that is written by network password changes, and 
> a few other writable files.

smpasswd is more like /etc/passwd.

It could perhaps be argued that maybe it should go under /var/lib.

In any case, smbpasswd isn't a requirement for using a samba server,
I believe you can use network based authentication...

> Please let me know when you've fixed sendmail, hotplug, ntpd, and samba, then 
> I'll update my SE Linux policy accordingly and give you a list of other 
> programs with write access.

I wouldn't complain if nobody updates sendmail...

Why does hotplug need to be changed?

/etc/ntp.drift and/or /etc/adjtime might be a problem, I gather not only
to they need to be writable at boot time, but the state needs to be
preserved across boots.
-- 
Brian May <bam@debian.org>
Date: 28 Mar 2003 01:12:17 +0100
From: Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: debian-devel@lists.debian.org
Subject: Re: RFC: New required package: libblkid1
Message-ID: <873cl85oym.fsf@mrvn.homelinux.org>
References: <E18vojj-0002Un-00@think.thunk.org>
	<buo4r5yq07k.fsf@mcspd15.ucom.lsi.nec.co.jp>
	<20030323195137.GF20673@alcor.net> <87znnic53l.fsf@mrvn.homelinux.org>
	<20030326193135.GC9369@alcor.net> <20030326235031.GA14905@svana.org>
In-Reply-To: <20030326235031.GA14905@svana.org>
Content-Type: text/plain; charset=us-ascii

Martijn van Oosterhout <kleptog@svana.org> writes:

> On Wed, Mar 26, 2003 at 02:31:35PM -0500, Matt Zimmerman wrote:
> > On Wed, Mar 26, 2003 at 08:14:54PM +0100, Goswin Brederlow wrote:
> > > That means it needs to change on nearly daily basis here.
> > 
> > "needs"?  It's a cache, and if you don't mind it scanning your devices when
> > you do a uuid-based mount, then you don't need it and if you insist on
> > having a read-only root partition, everything still works for you.  Where's
> > the problem?
> 
> I'm just trying to understand something. If you have 6000 partitions
> mounting by UUID without a cache, does this mean that mount would scan the
> partitions over 10 million times to complete it's job? Is this the problem
> being solved? Obviously mount -a could optimise but which 600 seperate mount
> commands I imagine this would be an issue.

Given that the major/minor numbers are pretty limited even having 6000
partitions would be pretty hard.

I think thats realy just said as an exageratede example to show the
point.

MfG
        Goswin

PS: How often do you think a system with 6000 partitions would get rebootet 
anyway? Who cares if it takes slightly longer? The UUIDs should all remain in the 
block caches so it shouldn't take that long to scan them all.

Reply to: