Re: Why am I receiving still mails from this list?

[Joe Drew]

On Mon, 2002-08-19 at 11:34, Matt Zimmerman wrote:
> On Mon, Aug 19, 2002 at 05:18:52PM +0200, Arvid Warnecke wrote:
> > I try to unsubscribe from this list for about a week now. I just got the
> > message that I am no member of the list anymore, but still get the
> > mails. I tried to unsubscribe again, but I got the message, that this is
> > not possible because I am no member.
> > Why do I still get the mails?
> 
> Read the instructions at the bottom of each message that you receive from this
> list.

Which he obviously did, given that he stated that he unsubscribed once,
apparently successfully, still received mails, and then tried again, and
the list said he wasn't subscribed.

-- 
Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

"This particular group of cats is mostly self-herding." -- Bdale Garbee

Re: Are libtool .la files in non-dev library packages bugs?

[Jason Gunthorpe]

On Mon, 19 Aug 2002, Ben Collins wrote:

> > > Not only that, it's only useful for linking, so has no reason being in
> > > the primary runtime.
> > 
> > ltdl needs them at runtime.
> 
> Then ltdl is broken. How does one install libfoo.so.1 and libfoo.so.2
> and only have libfoo.la, and ltdl expect to work?

I was always under the impression that ltdl only really needed the .la
files on defective OS's, not on linux.. 

Just look in a .la, there is nothing in there that can't be properly done
by ld.so. 

Jason

Re: tenative ITP linux-wlan-ng; soliciting advice

[Daniel Jacobowitz]

On Mon, Aug 19, 2002 at 05:39:56PM -0400, Michael Alan Dorman wrote:
> [EMAIL PROTECTED] (Paul Hedderly) writes:
> > No. the hostap dirver is excellent. Written by Jean Tour... something.
> > He works for SSH Corp. google for "linux prism2 driver". It does pcmcia
> > and pci brilliantly but doesnt support usb yet. works with prism2/2.5/3
> > cards - and most orinoco cards too. supports kysmet.
> 
> Nope, you're confusing authors with the in-kernel orinoco driver,
> which Jean Tourrilhes (who works for HP) has maintained at various
> points, though the current "real" maintainer is David Gibson, IIRC.

He was almost right:
Author: Jouni Malinen, <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>

For HostAP, that is.  Which I still recommend.

-- 
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer

Re: Are libtool .la files in non-dev library packages bugs?

[Anthony Towns]

On Mon, Aug 19, 2002 at 09:22:54PM -0400, Ben Collins wrote:
> On Mon, Aug 19, 2002 at 07:29:23PM -0500, Adam Heath wrote:
> > On Mon, 19 Aug 2002, Ben Collins wrote:
> > > Not only that, it's only useful for linking, so has no reason being in
> > > the primary runtime.
> > ltdl needs them at runtime.
> Then ltdl is broken. How does one install libfoo.so.1 and libfoo.so.2
> and only have libfoo.la, and ltdl expect to work?

Possibly you can't. *shrug*

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

 ``If you don't do it now, you'll be one year older when you do.''

Re: Menu system rewrite update (Aug 6 2002)

[Peter S Galbraith]

Joey Hess <[EMAIL PROTECTED]> wrote:

> Andreas Tille wrote:
> > In fact you are right.  I would vote for a mandatory menu entry for every
> > program which has a user interface.
> 
> I "vote" that you get to write the menu file for gnuplot, which after
> all has a graphical user interface, if it's fed the proper data file.

Or fix my bug http://bugs.debian.org/139482

I need a dialog utility to prompt for the file name (with a file
browser) and then start the program with that as argument.

[no subject]

[Æ®À©½º]

[no subject]

[Æ®À©½º]

Re: list of valid distributions in Debian changelog file.

[Peter S Galbraith]

Martin Schulze <[EMAIL PROTECTED]> wrote:

> Peter S Galbraith wrote:
> > Hi,  What are the currently valid distribution to which we can make
> > uploads to?
> > 
> > debian-changelog-mode.el currently allows the user to set the
> > distribution field for an upload to multiple distributions, e.g.
> > 
> > xwatch (2.11-8) frozen unstable; urgency=low
> > 
> > The list of possibilities is currently set to:
> 
> The following are very bad and likely not to work properly with katie
> and the SRM, hence, I guess that it would make sense to not include
> them directly:
> 
> >   stable unstable
> >   stable frozen
> >   stable frozen unstable

Thanks, I have removed the possibility of setting multiple distributions
in the latest veersion of debian-changelog-mode.
 
> Additionally, for security we have:
> 
>oldstable-security
>stable-security
>testing-security
> 
> However, I'd like people to upload through the security team so we
> don't suffer from broken distributions or broken versions when working
> on a security problem.  Yes, such things happen, way too often,
> unfortunately.  Hence, it may be wise to add these only as a comment
> in some document but not in the actual debian-changelog-mode.

I see.  I had included them, but I can remove them again.

Thanks!

Peter

business assistance

[Mustapha Mutala]

Petroleum (Special) Trust Fund
Contract Award Committee
National Secretariat
Victoria-Island
Lagos-Nigeria.
Email: [EMAIL PROTECTED]


ATTENTION: THE MANAGING DIRECTOR,

  The Petroleum Special Trust Fund was set up by the
late Head of State General Sani Abacha who died on 8th
June 1998, to manage the excess revenue accruing from
the sale of petroleum and its allied products as a
result of domestic increase in the prices of petroleum
products.

 The estimated annual revenue for 1999 was 45 billion
US Dollars Ref. FMF A26 Unit 3B paragraph "D" of the
Auditor General of the Federal Republic of Nigeria
Report of NOV. 1999 on estimated revenue.

 I am the Chairman of the Contract Award committee
and my committee is solely responsible for awarding
and payment of contracts on behalf of the Federal
Government of Nigeria .

 My Committee awarded contracts to foreign contractors
for the supply of Agricultural Machines and spare
parts to the Ministry of Agriculture and Natural
Resources. We overshot the contract sum by USD35
Million. We have paid the contractors and withholding
the balance of 35 Million United States Dollars.

 Beceause of existing domestic laws forbidding civil
servants from opening, operating and maintaining
foreign accounts, we do not have the expertise to
transfer this balance of funds to a foreign account.

However, this balance of 35 Million United States
Dollars($35 million USD) has been secured in form of credit/payment to a 
foreign contractor.Hence, we wish to transfer into your bank account as the 
beneficiary of the funds.

 We have also arrived at a conclusion that you will be
compensated to the tune of 25% of the total sum
transfered while 5% will be reserved for incidental
expenses that both parties will incur in the course of
actualizing this transaction and  the balance of 70%
will be kept for the Committee members.

 If you know you are capable of helping us actualize
our life's dream,You should send to me immediately the
details of your bank particulars or open a new account
where we can transfer the money(US$35M)which you will
hold in trust for us until we come over there for our
own share.Your nature of business does not matter in this transaction.

 As soon as you open the account, send by e-mail  immediately  with thedetails 
of the account viz: Name of bank, address,
routing number, telex number, Account number, Tel and
Fax number.You should also include the name of your
company, your personal address, Tel and Fax numbers
for further communication.

 Note that this transaction will be concluded within
10 working days from the day you give your consent.

 Sincerely yours,

 Mustapha Mutala

Re: Are libtool .la files in non-dev library packages bugs?

[Adam Heath]

On Mon, 19 Aug 2002, Ben Collins wrote:

> Then ltdl is broken. How does one install libfoo.so.1 and libfoo.so.2
> and only have libfoo.la, and ltdl expect to work?

libtool itself is broken, but I digress.

Re: Are libtool .la files in non-dev library packages bugs?

[Ben Collins]

On Mon, Aug 19, 2002 at 07:29:23PM -0500, Adam Heath wrote:
> On Mon, 19 Aug 2002, Ben Collins wrote:
> 
> > Not only that, it's only useful for linking, so has no reason being in
> > the primary runtime.
> 
> ltdl needs them at runtime.

Then ltdl is broken. How does one install libfoo.so.1 and libfoo.so.2
and only have libfoo.la, and ltdl expect to work?

Broken...

-- 
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
Deqo   - http://www.deqo.com/

Re: Are libtool .la files in non-dev library packages bugs?

[Luca Barbieri]

> ltdl needs them at runtime.

If so, how should parallel installation be handled?
How does one decide whether the .la file should be put in the main
package or the dev one?

The shared library packaging manual should be updated to included this
information if this is the case.



signature.asc
Description: This is a digitally signed message part

Re: tenative ITP linux-wlan-ng; soliciting advice

[Michael Alan Dorman]

Ian Eure <[EMAIL PROTECTED]> writes:
> On Monday 19 August 2002 02:39 pm, Michael Alan Dorman wrote:
> > [EMAIL PROTECTED] (Paul Hedderly) writes:
> > > No. the hostap dirver is excellent. Written by Jean Tour... something.
> > > He works for SSH Corp. google for "linux prism2 driver". It does pcmcia
> > > and pci brilliantly but doesnt support usb yet. works with prism2/2.5/3
> > > cards - and most orinoco cards too. supports kysmet.
> >
> > Nope, you're confusing authors with the in-kernel orinoco driver,
> > which Jean Tourrilhes (who works for HP) has maintained at various
> > points, though the current "real" maintainer is David Gibson, IIRC.
> >
> > Apparently the 2.4.19 orinoco includes prism2/PCI (aka prism2.5, I
> > believe) support.  Don't know about the prism3---is that 802.11a?
> >
> Prism2 and Prism2.5 are not the same thing.

My understanding, perhaps flawed, is that Prism2.5 is basically a
Prism2 with a direct PCI interface---no pcmcia baggage, etc.  The
Linksys WPM11, for instance.

Regardless, the orinoco driver in the 2.4.19 kernel supports them.
>From Configure.help:

Prism 2.5 PCI 802.11b adaptor support
CONFIG_PCI_HERMES
  Enable support for PCI and mini-PCI 802.11b wireless NICs based on
  the Prism 2.5 chipset.  These are true PCI cards, not the 802.11b
  PCMCIA cards bundled with PCI<->PCMCIA adaptors which are also
  common.  Some of the built-in wireless adaptors in laptops are of
  this variety.

> I haven't used the driver in the kernel, but the Orinoco driver
> shipped with pcmcia-source (pcmcia-cs 3.1.33) only supports Prism2
> cards.
> 
> I strongly recommend anyone with a Prism chipset use linux-wlan-ng,
> since pcmcia-cs's Orinoco driver sucks pretty hard.

To each their own---I have used the orinoco driver that comes with the
kernel from day one with no particular problems---and it supports the
standard (at least in-kernel-standard) interfaces for configuration,
etc., whereas wlan-ng does its own thing.

Mike.

Re: Are libtool .la files in non-dev library packages bugs?

[Christian Marillat]

Adam Heath <[EMAIL PROTECTED]> writes:

> On Mon, 19 Aug 2002, Ben Collins wrote:

> Not only that, it's only useful for linking, so has no reason being in
> the primary runtime.

> ltdl needs them at runtime.

and librep9 too.

Christian

Re: Are libtool .la files in non-dev library packages bugs?

[Adam Heath]

On Mon, 19 Aug 2002, Ben Collins wrote:

> Not only that, it's only useful for linking, so has no reason being in
> the primary runtime.

ltdl needs them at runtime.

Re: Are libtool .la files in non-dev library packages bugs?

[Ben Collins]

On Tue, Aug 20, 2002 at 01:50:22AM +0200, Luca Barbieri wrote:
> According to Junichi's manual they should be in -dev packages (that
> makes sense, since they are only used by libtool builds).

Yes, it's a bug. Consider that the .la file is usually without soname
(e.g. libfoo.la) it will clash when the next so version of the same lib
is added to the dist.

Not only that, it's only useful for linking, so has no reason being in
the primary runtime.

-- 
Debian - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
Deqo   - http://www.deqo.com/

Are libtool .la files in non-dev library packages bugs?

[Luca Barbieri]

According to Junichi's manual they should be in -dev packages (that
makes sense, since they are only used by libtool builds).

The following packages might be affected. The list only includes
packages from unstable in libs/ with digits in the name.

hamlib1
kdelibs3
kdelibs3-cups
libaspell10
libcapi20
libdcopc1
libelastic8
libesmtp5
libflux0
libfwbuilder2
libgdkxft0
libgoops5
libgretl0
libguile9
libicq1
libkdenetwork1
libkdexparts1
libkonq3
libkore0
libkscan1
libkxmleditor1
liblircclient0
liblzo1
libmagick5
libmagick++5
libmimelib1
libmng1
libprelude0
libpspell-ispell1
librrd0
libsword1
libyahoo0
vflib2



signature.asc
Description: This is a digitally signed message part

Re: tenative ITP linux-wlan-ng; soliciting advice

[Ian Eure]

On Monday 19 August 2002 02:39 pm, Michael Alan Dorman wrote:
> [EMAIL PROTECTED] (Paul Hedderly) writes:
> > No. the hostap dirver is excellent. Written by Jean Tour... something.
> > He works for SSH Corp. google for "linux prism2 driver". It does pcmcia
> > and pci brilliantly but doesnt support usb yet. works with prism2/2.5/3
> > cards - and most orinoco cards too. supports kysmet.
>
> Nope, you're confusing authors with the in-kernel orinoco driver,
> which Jean Tourrilhes (who works for HP) has maintained at various
> points, though the current "real" maintainer is David Gibson, IIRC.
>
> Apparently the 2.4.19 orinoco includes prism2/PCI (aka prism2.5, I
> believe) support.  Don't know about the prism3---is that 802.11a?
>
Prism2 and Prism2.5 are not the same thing. I haven't used the driver in the 
kernel, but the Orinoco driver shipped with pcmcia-source (pcmcia-cs 3.1.33) 
only supports Prism2 cards.

I strongly recommend anyone with a Prism chipset use linux-wlan-ng, since 
pcmcia-cs's Orinoco driver sucks pretty hard.

-- 
Komm auf meine Sonnenbarke!

David D.W. Downey - libpam-pgsql Maintainer/Upstream (Status Update)

[David D.W. Downey]

Evening ladies and gents,


OK, I know I've been an on again/off again maintainer so far.
Unfortunately, that trend will continue for a bit longer. (even longer
than *I* expected).

I've had quite a few In Real Life problems surface that are demanding
100% of my time at the moment. (I don't even have net access on
consistent basis yet.)

I finally made the move from Susanville, CA USA to Buffalo, NY USA. In
the process of the move, several life altering issues cropped up. First,
it's become necessary for me to start and extremely involved court
process to force the mother of one of my children to recognize paternl
standing. (Long involvedissue where I just found out I had a daughter I
never knew existed. All I'm willing to state on a public forum).

The final issue, however, is of a much larger caliber and could vastly
affect my online status and my work with Debian and libpam-pgsql. (Yes,
I fully recognize and accept that my record for stability has not been
the best so far as it is.)   Those of you that I talk to privately know
I've been having medical problems as of late. Well, the doctors at the
Veterans Hospital have explained why I've been so sick lately. Seems, I
have colon cancer. 

I'm not willing to just walk away from Debian, libpam-pgsql, or any
future pacakges I may be graced with the care of. However, until these
two monumental issues in my life both allow me some semblance of mental
equilibrium, and time to concentrate on other issues I find myself
unable to manage.

Anyone out there willing to do NMUs, please do so with my blessings,
with 2 caveats. 1) No drastic changes to the core functionality (aka no
rewrites). Bug fixes for what's on the BTS right now and future security
patches to any popup issues is fine. Several people have written patches
that have not been incorporated and tested, and they've emailed my
consistently about it privately. To them I say, your voice has not gone
unnoticed. Life just has not been dealing a workable hand at the present
time. Your time and effort will be rewarded. 2) No deleting or changing out
of the dependancy of pam-pgsql on mhash/mhash2, as the FreeBSD maintainer has
requested. I'm not opposed to the change *after* much more careful
consideration, and indepth talks between myself and him occur. Not to
mention the required (to me) discourse of such a fundamental change in
the package on the debian-devel list among interested parties.

I'm hoping to be back online within a month or two. I'm also hoping to
be capable of working on these issues and others by then, though I
make no promises at all. (The cancer issue alone decries that
capability). I will be monitoring my email sporatically (even more so
than before, unfortunately), but I will try to answer.

Thanks for understanding folks. I truly do want to help with Debian. I
do believe in the Social Contract and the potential for honest, open
source, high quality software to affect a change for good in man's
technological evolution. I agree and accept that my participation up to
now has been rather spotty. I can only say that I plan to change that,
once I stabilize my life.

-- 
David D.W. Downey <[EMAIL PROTECTED]>
Upstream - libpam-pgsql.codecastle.com
Debian - Woody: 0.5.2-3 Sid: 0.5.2-5
State - bugs.debian.org/libpam-pgsql
"The price of Free Software is Eternal Literacy."

"I'd rather die on my feet, than live on my knees."
Deloris Clayborn


pgp740XoZ909y.pgp
Description: PGP signature

Re: How to transition to G++ 3.2 wthout any breakage

[Josselin Mouette]

Le sam 17/08/2002 à 18:50, Luca Barbieri a écrit :
> I forgot an important thing: all new non-C++ packages should be tagged
> as non-C++ in some way so that dpkg doesn't need to scan them.
> 
> This should of course be done by having the build tools scan the package
> build directory and set either a new field ('Uses-C++-ABI: No') or by
> dependency on the new dpkg (dh_shlibdeps seems a good place to do this,
> but not everything uses it).

Thank you for this moment of great fun.
Next time, could you please post on debian-curiosa ? This is the right
place for such things.

-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom


signature.asc
Description: PGP signature

Re: tenative ITP linux-wlan-ng; soliciting advice

[Michael Alan Dorman]

[EMAIL PROTECTED] (Paul Hedderly) writes:
> No. the hostap dirver is excellent. Written by Jean Tour... something.
> He works for SSH Corp. google for "linux prism2 driver". It does pcmcia
> and pci brilliantly but doesnt support usb yet. works with prism2/2.5/3
> cards - and most orinoco cards too. supports kysmet.

Nope, you're confusing authors with the in-kernel orinoco driver,
which Jean Tourrilhes (who works for HP) has maintained at various
points, though the current "real" maintainer is David Gibson, IIRC.

Apparently the 2.4.19 orinoco includes prism2/PCI (aka prism2.5, I
believe) support.  Don't know about the prism3---is that 802.11a?

Mike.

Re: GCC 3.2 transition

[Ulrich Eckhardt]

On Friday 16 August 2002 21:47, Martin v. Loewis wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > How would this work?  Would those using gcc-2.95 software have to set an
> > rpath or $LD_LIBRARY_PATH to take advantage of the compat libs?  If so,
> > it hardly seems worth the effort; manual intervention is still required
> > to make legacy binaries work.
>
> Not necessarily: you can write wrapper scripts around the executable
> which automatically set LD_LIBRARY_PATH, then invoke the original
> binary. That has worked very well in the past.
>
While this hack would make it unnecessary, I consider it a lack in the 
linker. In my eyes, the program should ask the linker at startup to provide a 
specified set functions. For since C++ has bigger requirements that stem from 
function overloading and other stuff, the specification consists of the API 
(which is -oversimplified- the version of the header files) and the ABI 
(which must match the compiler the app was compiled with). 

I'm not totally aware of the way the dynamic linker works or how an ELF 
executable is structured, but I believe it would be possible to add a field 
in ELFs header that says which ABI to use and get the linker to parse it.

Still, I have one question left: will C++ be the only language that profits 
from this, are there other languages that have different ABI by different 
compilers ? And would such a function be used again even for C++ ? (hint: 
multi-vendor ABI standard)

At last a crazy idea: what happens if I link object files from two different 
compilers into one lib? I mean I compile foo.cpp once with compiler A and 
then again with compier B and create a lib from both of them. The only 
drawback I see at the moment is that the resulting lib would be approximately 
be twice the size and, even worse, global objects would be instantiated 
twice, bad if they acquire and lock some kind of resource .

cheers 
Uli

PS: is there any way to get the BTS to spew out a list of all bugs of 
packages that don't build with a more standard-conformant compiler (GCC3) ?

Re: Upcoming bug mass-filing re. non-free TrueType fonts in main

[Glenn Maynard]

On Mon, Aug 19, 2002 at 06:03:12PM -0300, Ben Armstrong wrote:
> > I think something like the LPPL would merely do the trick. Modifying the
> > font would be allowed, but would also require a name change.
> 
> After looking over the LPPL, it looks like it would do the job.  Do you know
> of any precedent for LPPL being used for packages containing nothing but
> fonts, and in particular, fonts not specific to TeX/LaTeX?  It would be nice
> to be able to cite such precedents when recommending the license to
> fontographers.

There was a very long thread about the LPPL on debian-legal, and it hasn't
been settled.  (Requiring name changes are allowed by the DFSG, but there's
no consensus that this includes *filename* changes.)  I'd strongly suggest
avoiding this license.

-- 
Glenn Maynard

Re: Upcoming bug mass-filing re. non-free TrueType fonts in main

[Ben Armstrong]

On Mon, Aug 19, 2002 at 10:43:06PM +0200, Josselin Mouette wrote:
> I think something like the LPPL would merely do the trick. Modifying the
> font would be allowed, but would also require a name change.

After looking over the LPPL, it looks like it would do the job.  Do you know
of any precedent for LPPL being used for packages containing nothing but
fonts, and in particular, fonts not specific to TeX/LaTeX?  It would be nice
to be able to cite such precedents when recommending the license to
fontographers.

Ben
-- 
nSLUG   http://www.nslug.ns.ca  [EMAIL PROTECTED]
Debian  http://www.debian.org   [EMAIL PROTECTED]
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0  1B B1 31 ED C6 A9 39 4F ]
[ gpg key fingerprint = 395C F3A4 35D3 D247 1387  2D9E 5A94 F3CA 0B27 13C8 ]

Re: Upcoming bug mass-filing re. non-free TrueType fonts in main

[Josselin Mouette]

Le mer 14/08/2002 à 20:48, Ben Armstrong a écrit :

> I'd like to educate about DFSG-free licensing.  Unfortunately, it's going to
> be rough sledding unless I can find a license that is likely to address the
> problems fontographers typically face when deciding how to license their
> work (like: "How am I going to deal with it when someone changes my font to
> something ugly and it reflects poorly on my skills as a fontographer?")

I think something like the LPPL would merely do the trick. Modifying the
font would be allowed, but would also require a name change.

-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom


signature.asc
Description: PGP signature

Re: More GPL fonts

[Erich Schubert]

> I will be packaging a number of truetype fonts for inclusion in debian
> somehow, but the details are not fully worked out yet. I'll take a
> look at these for to include in that package, or in a package of just
> your fonts. 

When packaging many fonts with defoma, could you please tell me if you
experience the same major slowdowns i get (with certain defoma-dependant
packages installed)?

Please check out my defoma-enabled ttf-larabie packages on
http://people.debian.org/~erich/ttf-larabie/

the -uncommon took some minutes to install here... defoma using all CPU.
See #143818... I think it is some broken font...
havn't had time to find out which of these > 100 ttfs...
Still defoma isn't stopped at one font, it just gets very very slow.

Greetings,
Erich

-- 
erich@(mucl.de|debian.org)--GPG Key ID: 4B3A135C
 A man doesn't know what he knows until he knows what he doesn't know.
Liebe ist eine schwere Geisteskrankheit (Platon)
"Wissen ist Macht" - wenn man das richtige daraus macht.

Re: Apache2

[Bernd Eckenfels]

On Mon, Aug 19, 2002 at 04:12:55PM +0100, Matt Kern wrote:
> I can see the advantages of all the separate configuration
> directories, but cannot see quite how everything fits together.  I
> understand the include mechanism and most of the files under
> /etc/apache2, but where are the referred to binaries addhost,
> ap2addhost and a2enhost (or whatever they are called in the files and
> postings I have read)?  I can't find anything on my system that makes
> use of the *.d directories in /etc/vhost.

apache2 packages will include all files from /etc/apache2-enabled/ and
generate vhosts with the configs in /etc/apache2/sites-enabled/.

You basically use the /etc/apache2/mods-available/ files as templates. there
is a load directive and some config stuff. the a2enmod is simply moving the
files from the avbailable dir into the enabled dir. It is a simple readable
shell script and i dont think it is a good idea to have them lay around and
clutter the namespace.

I dont know about the vhost stuff besides the site dir.

> Have I caught the apache2 package in a state of extreme development?

the packages are pretty new, but working well for me.

Greetings
Bernd

Re: More GPL fonts

[Michael Cardenas]

On Mon, Aug 19, 2002 at 12:34:40PM -0700, Dustin Norlander wrote:
> I have GPL'ed many of my freeware fonts.  They are all decorative fonts, so 
> they wont be of much use as screenfonts, but are good for logos, design 
> stuff ect..  A couple of them are quit old and not that great, but someone 
> might be able to make some use of them :)
> 
> Michael - I'll leave it up to you if you want to package any of these.
> 
> http://www.dustismo.com/fonts/balker.zip
> http://www.dustismo.com/fonts/flatline.zip
> http://www.dustismo.com/fonts/ItWasntMe.zip
> http://www.dustismo.com/fonts/Junkyard.zip
> http://www.dustismo.com/fonts/MarkedFool.zip
> http://www.dustismo.com/fonts/Progenisis.zip
> http://www.dustismo.com/fonts/Swift.zip
> http://www.dustismo.com/fonts/Wargames.zip
> http://www.dustismo.com/fonts/Winks.zip
> 
> Thanks
> Dustin
> 
> 
> 

Great, Dustin, thank you. 

I will be packaging a number of truetype fonts for inclusion in debian
somehow, but the details are not fully worked out yet. I'll take a
look at these for to include in that package, or in a package of just
your fonts. 

Thanks again
  michael

-- 
michael cardenas | lead software engineer | lindows.com | hyperpoem.net

"Try and be a sheet of paper with nothing on it. Be a spot on the ground where 
nothing is growing, where something might be planted, a see possibly, from the 
Absolute."
- Rumi


pgpK1OewEbEod.pgp
Description: PGP signature

Bug#157294: ITP: ion-sfx -- keyboard friendly wm, includes support for menues, docks and tasklists

[andreashappe]

Package: wnpp
Version: N/A; reported 2002-08-19
Severity: wishlist

* Package name: ion-sfx
  Version : 20020706
  Upstream Author : Andreas Happe <[EMAIL PROTECTED]>
* URL : http://modeemi.fi/~tuomov/ion/
* License : Artistic
  Description : keyboard friendly wm, includes support for menues, docks 
and tasklists


-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux imladis.homelinux.net 2.5.31 #7 Tue Aug 13 10:02:03 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C

Re: Why am I receiving still mails from this list?

[Erich Schubert]

> Received: from sphinx.rz.tu-clausthal.de
> Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com
> Received: from fwd04.sul.t-online.de
> Received: from bombadil.xmldesign.de ([EMAIL PROTECTED])

that obviously is the copy of the mail i sent to you directly.
it never used a debian server. me, t-online, tu-clausthal.

Greetings,
Erich

-- 
erich@(mucl.de|debian.org)--GPG Key ID: 4B3A135C
There are only 10 types of people in the world:
Those who understand binary and those who don't
Die kürzeste Verbindung zwischen zwei Menschen ist ein Lächeln.
Der Wissende weiß, dass er glauben muß.

More GPL fonts

[Dustin Norlander]

I have GPL'ed many of my freeware fonts.  They are all decorative fonts, so 
they wont be of much use as screenfonts, but are good for logos, design 
stuff ect..  A couple of them are quit old and not that great, but someone 
might be able to make some use of them :)

Michael - I'll leave it up to you if you want to package any of these.
http://www.dustismo.com/fonts/balker.zip
http://www.dustismo.com/fonts/flatline.zip
http://www.dustismo.com/fonts/ItWasntMe.zip
http://www.dustismo.com/fonts/Junkyard.zip
http://www.dustismo.com/fonts/MarkedFool.zip
http://www.dustismo.com/fonts/Progenisis.zip
http://www.dustismo.com/fonts/Swift.zip
http://www.dustismo.com/fonts/Wargames.zip
http://www.dustismo.com/fonts/Winks.zip
Thanks
Dustin

Re: [OT] MES-2 [Was: Re: Linux Fonts]

[Branden Robinson]

On Mon, Aug 19, 2002 at 11:11:06PM +1000, Drew Parsons wrote:
> On Sun, Aug 18, 2002 at 06:25:28PM +0200, Radovan Garabik wrote:
> > free high quality variable width font. Dustimo could become
> > base of such a font, if it covered at least MES-2 repertoire (maybe
> > without Georgian and Armenian characters for the beginning).
> 
> Just out of interest, what is MES-2?

http://www.cl.cam.ac.uk/~mgk25/ucs/mes-2-rationale.html

-- 
G. Branden Robinson|
Debian GNU/Linux   | Cogitationis poenam nemo meretur.
[EMAIL PROTECTED] |
http://people.debian.org/~branden/ |


pgpg68Axgx2ZL.pgp
Description: PGP signature

Re: GCC 3.2 transition

[Gerhard Tonn]

On Saturday 17 August 2002 19:28, you wrote:
>
> I am currently doing this experiment on s390 without uploading of course. I
> have grepped the build logs of about 4000 packages that I have access to
> for g++|c++ and about 900 packages qualified. I am currently rebuilding
> these packages with gcc-3.2 using a local wanna-build DB. This will take
> some days. I will let you know the results.
>

I have put the preliminary data to 
http://people.debian.org/~gt/gcc-3.2_transition/ .The file Packages contains 
all files currently being rebuilt. The subdirectory failed contains the build 
logs of all failed packages, still a lot, mainly due to c++ default argument 
check changes since gcc 3.0. The subdirectory dep-wait contains the build 
logs of all packages that depend on another package being built with gcc 3.2. 
I have qualified the dependency with subdirectories if known. The 
subdirectory 1iteration contains the build logs of all packages that compiled 
successfully during the first iteration, i.e. only dependent on libstdc++. 
The subdirectory 2iteration will contain the build logs of all packages that 
will compile successfully during the second iteration and so on.

I will update the data once a day. Currently about 300 packages have been 
touched.

I hope the data helps with any transition plan.

I think Matthew has presented a fine plan, but it is open how long the 
transition will take with this plan. Maybe a deadline will be helpful, after 
that source NMUs should be done.

Doing binary NMUs for each platform as in my experiment would also work but 
needs a volunteer for each platform and a lot of bug reports for all the 
failed builds.

Both approaches will duplicate the size of the affected packages in the 
archive of course.

Gerhard

Re: Why am I receiving still mails from this list?

[Federico Sevilla III]

On Mon, Aug 19, 2002 at 05:37:07PM +0200, Arvid Warnecke wrote:
> Okay then, here is the header of your mail which came through the list.
> And I unsubscribed with this address.

I don't think the headers you're quoting are of the email from Erich
Schubert that came through the list, but the one that got to you
directly.

> The header:
...
> Received: from fwd04.sul.t-online.de  
>   
> by mailout01.sul.t-online.com with smtp   
>   
> id 17goSC-00029v-01; Mon, 19 Aug 2002 17:28:28 +0200  
>   
> Received: from bombadil.xmldesign.de ([EMAIL PROTECTED]) by 
> +fmrl04.sul.t-online.com
> with esmtp id 17goRy-07G93oC; Mon, 19 Aug 2002 17:28:14 +0200
> Received: by bombadil.xmldesign.de (Postfix, from userid 1000)
> id 7E7B0932D7; Mon, 19 Aug 2002 17:27:12 +0200 (CEST)
> Date: Mon, 19 Aug 2002 17:27:12 +0200
...

This came from Erich's system and went straight to yours. This didn't
pass through the Debian list servers.

I'm not cc'ing you this message. If it gets to you examine the headers
and find to which address the Debian list servers sent it to and
unsubscribe that.

You should probably be looking for a received line from murphy like so:

   Received: from murphy.debian.org (murphy.debian.org [65.125.64.134])
by gusi.leathercollection.ph (Postfix) with SMTP id 8092DC0482F
for <[EMAIL PROTECTED]>; Mon, 19 Aug 2002 23:39:05 +0800 (PHT)

Cheers.

 --> Jijo

-- 
Federico Sevilla III   :  http://jijo.free.net.ph
Network Administrator  :  The Leather Collection, Inc.
GnuPG Key ID   :  0x93B746BE

Re: Apache2

[Thom May]

* Matt Kern ([EMAIL PROTECTED]) wrote :
> I have just installed apache2 (out of sid onto a woody based system)
> and am having a little trouble understanding the new methodology.
> 
> I can see the advantages of all the separate configuration
> directories, but cannot see quite how everything fits together.  I
> understand the include mechanism and most of the files under
> /etc/apache2, but where are the referred to binaries addhost,
> ap2addhost and a2enhost (or whatever they are called in the files and
> postings I have read)?  I can't find anything on my system that makes
> use of the *.d directories in /etc/vhost.
> 
> Have I caught the apache2 package in a state of extreme development?

No, you've caught the vhost system in a state of extreme unworkingness -
there was a very rough version that maybe worked a while back, but it
seriously needs a rewrite and some love.

It is however entirely workable without vhost-base; add sites and modules to
/etc/apache2/{sites,mods}-available, and enable them with a symlink into
/etc/apache2/{sites,mods}-enabled 


A more suitable list for further discussion is debian-apache, and the
reply-to is set accordingly.
-Thom

-- 
Thom May -> [EMAIL PROTECTED]

 Hello!
 What is the voting period? From Mar 24th until?
 until the candidate manoj wants to win is in the lead
* asuffield ducks into the icbm shelter

Re: Yet another stupid suggestion (Re: GCC 3.2 transition )

[Eduard Bloch]

#include 
* Allan Sandfeld Jensen [Mon, Aug 19 2002, 02:58:06PM]:
> libraries are placed under /usr/lib/g++2.95 and the new ones under 
> /usr/lib/g++3.1. The defaults are symbolic linked from /usr/lib. We can 
> either hack ld.so to search the correct path (using some g++ calling cards) 
> or recompile all the old C++ packages with an new rpath or load them with a 

IMHO yes. I do not see why the usage of Rpath has reputation of beeing
evil noadays, it should be the most reliable way to go in this phase,
instead of hacking linkers and loaders. Once the transition is done and
all libraries got appropriate package names, the rpath changes may be
removed, but don't have to.

Gruss/Regards,
Eduard.
-- 
Der Nachteil an Linux ist, dass man sich irgendwann nicht mehr an den
Installationsvorgang erinnern kann.

Re: Why am I receiving still mails from this list?

[Arvid Warnecke]

On Mon, Aug 19, 2002 at 05:27:12PM +0200, Erich Schubert wrote:
> > I try to unsubscribe from this list for about a week now. I just got the
> > message that I am no member of the list anymore, but still get the
> > mails. I tried to unsubscribe again, but I got the message, that this is
> > not possible because I am no member.
> > Why do I still get the mails?
> We are not magicians, quote some headers so we can find out...
> Probably you subscribed with a different address than the one you
> unsubscribed?
> 
Okay then, here is the header of your mail which came through the list.
And I unsubscribed with this address.
The header:

Delivered-To: [EMAIL PROTECTED] 
Received: from localhost (localhost [127.0.0.1])
by hasseroeder.heim2.tu-clausthal.de (Postfix) with ESMTP id
279065BEE8 
for <[EMAIL PROTECTED]>; Mon, 19 Aug 2002 17:31:05 +0200 (CEST) 
  
Received: from mail.rz.tu-clausthal.de [139.174.2.34]   
by localhost with POP3 (fetchmail-5.9.11)   
for [EMAIL PROTECTED] (single-drop); Mon, 19 Aug 2002 17:31:05
+0200  
+(CEST) 
Received: from sphinx.rz.tu-clausthal.de
(sphinx.rz.tu-clausthal.de [139.174.2.44])  
by sinfonix.rz.tu-clausthal.de (8.9.3/8.9.3) with ESMTP 
id RAA12201 for <[EMAIL PROTECTED]>;   
Mon, 19 Aug 2002 17:28:31 +0200 (MET DST)   
Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com   
+[194.25.134.80])   
by sphinx.rz.tu-clausthal.de (8.12.5/8.12.5) with ESMTP id  
+g7JFSrNY086731 
for <[EMAIL PROTECTED]>; Mon, 19 Aug 2002 17:28:53
+0200   
+(CEST) 
(envelope-from [EMAIL PROTECTED])
Received: from fwd04.sul.t-online.de
by mailout01.sul.t-online.com with smtp 
id 17goSC-00029v-01; Mon, 19 Aug 2002 17:28:28 +0200
Received: from bombadil.xmldesign.de ([EMAIL PROTECTED])
by 
+fmrl04.sul.t-online.com
with esmtp id 17goRy-07G93oC; Mon, 19 Aug 2002 17:28:14 +0200   
Received: by bombadil.xmldesign.de (Postfix, from userid 1000)  
id 7E7B0932D7; Mon, 19 Aug 2002 17:27:12 +0200 (CEST)   
Date: Mon, 19 Aug 2002 17:27:12 +0200   
From: Erich Schubert <[EMAIL PROTECTED]>
 
To: Arvid Warnecke <[EMAIL PROTECTED]> 
Cc: debian-devel@lists.debian.org   
Subject: Re: Why am I receiving still mails from this list? 
Message-ID: <[EMAIL PROTECTED]>  
Mail-Followup-To: Erich Schubert <[EMAIL PROTECTED]>,   
 
Arvid Warnecke <[EMAIL PROTECTED]>,
debian-devel@lists.debian.org   
References: <[EMAIL PROTECTED]>  
Mime-Version: 1.0   
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline 
Content-Transfer-Encoding: 8bit 
In-Reply-To: <[EMAIL PROTECTED]> 
User-Agent: Mutt/1.4i   
X-GPG: 4B3A135C 6073 C874 8488 BCDA A6A9  B761 9ED0 78EF 4B3A 135C  
X-Eric-Conspiracy: There is no conspiracy   
X-Sender: [EMAIL PROTECTED]
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) 
X-UIDL: lE8!!lQm"!\http://nostalgix.org ] [PGP-Subject: get pgp key]
`. `'  Linux 2.4.19-gentoo-r5 i686  XFree86 Version 4.2.0  Uptime: 1 day, 44 min
  `--  BOFH #1: clock speed

Re: Why am I receiving still mails from this list?

[Matt Zimmerman]

On Mon, Aug 19, 2002 at 05:18:52PM +0200, Arvid Warnecke wrote:

> I try to unsubscribe from this list for about a week now. I just got the
> message that I am no member of the list anymore, but still get the
> mails. I tried to unsubscribe again, but I got the message, that this is
> not possible because I am no member.
> Why do I still get the mails?

Read the instructions at the bottom of each message that you receive from this
list.

-- 
 - mdz

Re: Menu system rewrite update (Aug 6 2002)

[Joey Hess]

Andreas Tille wrote:
> In fact you are right.  I would vote for a mandatory menu entry for every
> program which has a user interface.

I "vote" that you get to write the menu file for gnuplot, which after
all has a graphical user interface, if it's fed the proper data file.

-- 
see shy jo, handing andreas a thinner brush

Re: Why am I receiving still mails from this list?

[Erich Schubert]

> I try to unsubscribe from this list for about a week now. I just got the
> message that I am no member of the list anymore, but still get the
> mails. I tried to unsubscribe again, but I got the message, that this is
> not possible because I am no member.
> Why do I still get the mails?

We are not magicians, quote some headers so we can find out...
Probably you subscribed with a different address than the one you
unsubscribed?

Greetings,
Erich

-- 
erich@(mucl.de|debian.org)--GPG Key ID: 4B3A135C
  Go away or i'll replace you with a very small shell script.
 Mancher findet sein Herz nicht eher, als bis er seinen Kopf verliert.
Der Wissende weiß, dass er glauben muß.

Why am I receiving still mails from this list?

[Arvid Warnecke]

Hello,

I try to unsubscribe from this list for about a week now. I just got the
message that I am no member of the list anymore, but still get the
mails. I tried to unsubscribe again, but I got the message, that this is
not possible because I am no member.
Why do I still get the mails?

Cheers,
Arvid

-- 
 .''`. [Arvid Warnecke] [ [EMAIL PROTECTED] ]  [05323-715724]
: :' : [IRC madhatter] [ http://nostalgix.org ] [PGP-Subject: get pgp key]
`. `'  Linux 2.4.19-gentoo-r5 i686  XFree86 Version 4.2.0  Uptime: 1 day, 27 min
  `--  BOFH #308: CD-ROM server needs recalibration

Apache2

[Matt Kern]

I have just installed apache2 (out of sid onto a woody based system)
and am having a little trouble understanding the new methodology.

I can see the advantages of all the separate configuration
directories, but cannot see quite how everything fits together.  I
understand the include mechanism and most of the files under
/etc/apache2, but where are the referred to binaries addhost,
ap2addhost and a2enhost (or whatever they are called in the files and
postings I have read)?  I can't find anything on my system that makes
use of the *.d directories in /etc/vhost.

Have I caught the apache2 package in a state of extreme development?

Matt

-- 
Matt Kern
http://www.undue.org/

Re: GCC 3.2 transition

[Marcelo E. Magallon]

>> Colin Watson <[EMAIL PROTECTED]> writes:

 > That could be interesting. How far back is RUNPATH supported? (I seem to
 > recall that it's a relatively new introduction to ELF, but if it's in
 > stable then that's good enough for me.)

 Good question.  Looking at the changelogs:

 1999-07-24  Ulrich Drepper  <[EMAIL PROTECTED]>

[...]
* elf/link.h (struct link_map): Add l_runpath_dirs.
* elf/dl-load.c: Pretty print.
(decompose_rpath): Take new parameter with info from where the path
comes.  Pass it the fillin_rpath.
(_dl_init_paths): Initialize l_runpath_dirs.
(_dl_map_object): Don't search using RPATHs if object has RUNPATH.
Search using RUNPATH after LD_LIBRARY_PATH.

 and later:

 1999-11-13  Roland McGrath  <[EMAIL PROTECTED]>

* Versions.def (libc): Add GLIBC_2.1.3.

 Roland's changelog doesn't mention a release and the NEWS file doesn't
 mention dates.  2.1.3 was released with potato, the first release
 entered the archive arround Feb 2000.  So, we have RUNTIME support all
 the way to potato.

-- 
Marcelo | This signature was automatically generated with
[EMAIL PROTECTED] | Signify v1.07.  For this and other cool products,
| check out http://www.debian.org/

Re: xmms needs rebuild in sid

[Adam Heath]

On Sun, 18 Aug 2002, Jack Howarth wrote:

> Josip,
> Changing the font didn't help, but deleting my .xmms
> directory in my account seemed to have cured it. Odd.
> Jack

Never delete.  Rename/move/copy.  Make backups.  Even of bad stuff.

Praise & Thanks

[Andree Leidenfrost]

Dear Debian developers

I am currently running seven Debian machines both at home and at work
(with another one at work coming soon).

I have just upgraded my headless (!) gateway machine at home from potato
to woody without any problem at all: The upgrade went entirely well
including extremely usable hints for what has changed. I have just
rebooted and the machine came back up without any glitches.

Some machines were following testing for a while and three are still on
potato but not for much longer!

I think you have done an incredible job again and I would like to thank
you very, very much for bringing such a fantastic operating system to
the world (and to me personally ;-) ). You certainly make a difference!

Thank you very much again, you are all stars!

Best regards
Andree
-- 
Andree Leidenfrost
Sydney - Australia

[OT] MES-2 [Was: Re: Linux Fonts]

[Drew Parsons]

On Sun, Aug 18, 2002 at 06:25:28PM +0200, Radovan Garabik wrote:
> free high quality variable width font. Dustimo could become
> base of such a font, if it covered at least MES-2 repertoire (maybe
> without Georgian and Armenian characters for the beginning).

Just out of interest, what is MES-2?

Drew

-- 
PGP public key available at http://people.debian.org/~dparsons/drewskey.txt
Fingerprint: A110 EAE1 D7D2 8076 5FE0  EC0A B6CE 7041 6412 4E4A

/bin/login hanging around

[Russell Coker]

Why is it that /bin/login seems to hang around for the duration of the user's 
session on other distributions but not on Debian?

Why do other distributions choose to have it keep running until the end of 
the session while we did not?

-- 
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.

Yet another stupid suggestion (Re: GCC 3.2 transition )

[Allan Sandfeld Jensen]

On Friday 16 August 2002 15:51, Matthew Wilcox wrote:
> -
>   The Debian GCC 3.2 Transition Plan
>
> This is a proposal. You will be notified when this is a real plan
>

Nice plan all in all, although I am going to hate the new package names. Some 
people talked about avoiding breakage, but I think most developers will agree 
that changing the so-names is not the solution. Basically we now have this 
problem due to the ELF-format. It is unrealistic to change the loader format 
now, but it might be a good idea to ask the gnu-binutils people to invent a 
new loader/linker format, that can be made compiler-ABI aware, and perhaps 
even architecture-extention aware(MMX, SSE, Altivec).

But for the people lobbying for a solution that avoids breakage, I have a 
loose idea as well:
The gcc 3.2 is really an architecture change, but for C++ libraries only. On 
other operating systems when they deal with different architectures the norm 
is to use $LIBDIR/$ARCH. That way 64bit libraries in Solaris is placed under 
/usr/lib/sparcv9 and in HP-UX under pa20_64. 

My suggestion for consideration is then to force C++ libraries to enter 
subdirectories until they have a proven compatible ABI-standard. So the old 
libraries are placed under /usr/lib/g++2.95 and the new ones under 
/usr/lib/g++3.1. The defaults are symbolic linked from /usr/lib. We can 
either hack ld.so to search the correct path (using some g++ calling cards) 
or recompile all the old C++ packages with an new rpath or load them with a 
LD_LIBRARY_PATH= script. 
This way both old and new packages will work during the actual transition. We 
are also guarenteed complience with LSB packages because we have the defaults 
symbolic linked.

The problem is we will still have a transition to the new style, but at least 
we are prepared for the next C++ ABI breakage in g++ (likely in gcc 3.4). And 
in theory users can then compile packages with different C++ compilers. (e.g. 
kcc, icc)

So is this just another stupid suggestion or a good idea?
`Allan

Re: GCC 3.2 transition

[Colin Watson]

On Mon, Aug 19, 2002 at 02:41:44PM +0200, Marcelo E. Magallon wrote:
> >> "Marcelo E. Magallon" <[EMAIL PROTECTED]> writes:
>  >  Just the normal linker with a different set of default paths.  This
>  >  is like using an -rpath.  The problem with -rpath is that it has
>  >  precedence over LD_LIBRARY_PATH.  So, the simplest solution is for
>  >  g++-3.2 to indicate a different dynamic linker when linking
>  >  programs.
> 
>  The problem with this solution is that it's not particularly backwards
>  compatible.  Systems without this special linker won't be able to run
>  the binaries, which is a *big* problem.

Yes ...

>  Fiddling arround the ld.so sources to understand how if finds the
>  libraries it wants to use, I noticed it looks for two tags in the ELF
>  object: DT_RPATH and DT_RUNPATH.  RUNPATH has two nice poperties: it's
>  looked at *after* LD_LIBRARY_PATH and it doesn't contaminate other ELF
>  objects, that is, it affects *only* the lookup process for the current
>  ELF object (that's the documented behaviour at least, I have yet to
>  check that ld.so does indeed behave like this).

That could be interesting. How far back is RUNPATH supported? (I seem to
recall that it's a relatively new introduction to ELF, but if it's in
stable then that's good enough for me.)

-- 
Colin Watson  [EMAIL PROTECTED]

Re: GCC 3.2 transition

[Michael Alan Dorman]

Colin Watson <[EMAIL PROTECTED]> writes:
> That problem shouldn't arise if the hack is done the other way
> round: new libraries go to /usr/lib/gcc3.2, say, in cases where the
> ABI differs. It does mean we can never get rid of it, but if the C++
> ABI changes in later versions of G++ then we may have to repeat this
> transition in future anyway.

The sad fact is, this may actually turn out to be the most sensible
solution, given that, like any standard, there are grey areas, and the
day before 3.2's release, the gcc team found just such a grey area
where gcc's implementation differed from Intel's, although it agreed
with HP's.

Mike.

Re: GCC 3.2 transition

[Marcelo E. Magallon]

>> "Marcelo E. Magallon" <[EMAIL PROTECTED]> writes:

 >  I was toying with that idea in my head.  There's no need for a
 >  special C++ compiler, is there?

 "linker" I meant, obviously.
 
 >  Just the normal linker with a different set of default paths.  This
 >  is like using an -rpath.  The problem with -rpath is that it has
 >  precedence over LD_LIBRARY_PATH.  So, the simplest solution is for
 >  g++-3.2 to indicate a different dynamic linker when linking
 >  programs.

 The problem with this solution is that it's not particularly backwards
 compatible.  Systems without this special linker won't be able to run
 the binaries, which is a *big* problem.

 Fiddling arround the ld.so sources to understand how if finds the
 libraries it wants to use, I noticed it looks for two tags in the ELF
 object: DT_RPATH and DT_RUNPATH.  RUNPATH has two nice poperties: it's
 looked at *after* LD_LIBRARY_PATH and it doesn't contaminate other ELF
 objects, that is, it affects *only* the lookup process for the current
 ELF object (that's the documented behaviour at least, I have yet to
 check that ld.so does indeed behave like this).

 I've managed to place such a tag on an excecutable, with the annoying
 side-effect that RPATH also gets set.  I haven't found a way to store
 only DT_RUNPATH on the ELF object.  In order to achive this you have to
 pass the --enable-new-dtags and -rpath options to the linker.  This
 seems to be ok, since the precense of RUNPATH overrides RPATH (again,
 this is the documented behaviour).

 The end effect of this is that a) binaries still work on other systems
 (with no larger breakage than what we see even today -- unresolved
 symbols and so on) b) doesn't touch the dynamic linker c) gives us what
 we want using a very well contained change (modifying the G++ frontend)
 and recompiling.

 Does this have drawbacks?

-- 
Marcelo | Bishops move diagonally. That's why they often turn up
[EMAIL PROTECTED] | where the kings don't expect them to be.
| -- (Terry Pratchett, Small Gods)

Re: man/tbl portability

[Colin Watson]

On Mon, Aug 19, 2002 at 02:33:08PM +0200, Mikael Hedin wrote:
> Oh, I tried not using tbl, but could not find anything else to produce
> something sensible.  If there is an alternative, please educate me.

In the cases where you find yourself wanting to use tbl because doing it
in plain nroff is too much work, it's usually the best option. If you're
talking about the table of actions from ogle 0.8.5-2, it looks fine to
me, except perhaps for being a little wide (it overflows an 80-column
terminal).

-- 
Colin Watson  [EMAIL PROTECTED]

Re: man/tbl portability

[Mikael Hedin]

Oh, I tried not using tbl, but could not find anything else to produce
something sensible.  If there is an alternative, please educate me.

/Micce


-- 
Mikael Hedin, MSc +46 (0)8 344979 (home) +46 (0)70 5891533 (mobile)
[gpg key fingerprint = 387F A8DB DC2A 50E3 FE26  30C4 5793 29D3 C01B 2A22]

Re: man/tbl portability

[Mikael Hedin]

Turned out to be "apostrophe, backslash, dubblequote, space, t".  Fun
and insane!

Tanks,

Micce

-- 
Mikael Hedin, MSc +46 (0)8 344979 (home) +46 (0)70 5891533 (mobile)
[gpg key fingerprint = 387F A8DB DC2A 50E3 FE26  30C4 5793 29D3 C01B 2A22]

Re: man/tbl portability

[Colin Watson]

On Mon, Aug 19, 2002 at 01:43:01PM +0200, Daniel Kobras wrote:
> See the NOTES section in man(7).  You need '\ t' at the beginning of the
> man page.  But also have a look at section SAFE SUBSET, which suggests
> to not use those macros in the first place.

It does say "if you must, go ahead and use tbl(1)". While I wouldn't
consider eqn or refer or whatever all that portable to other tools, I
don't think I'd have any qualms about using tbl. It will certainly be
available with any half-decent nroff installation.

-- 
Colin Watson  [EMAIL PROTECTED]

Re: man/tbl portability

[Colin Watson]

On Mon, Aug 19, 2002 at 01:25:26PM +0200, Mikael Hedin wrote:
> I've enhanced oglerc(5) by adding a tbl section (.TS and .TE and the
> things in between).  On my system (sid) it is preproccessed by tbl(1)
> when I run 'man ./oglerc.5', but on the upstream author's sytem
> (solaris something), the tbl preprocessing does not happen.

Debian's man-db scans not only for preprocessor hints [1], but also for
.TS/.TE in the body of the page. For portability, use the hint too.

[1] '\" t
as the first line of the page

-- 
Colin Watson  [EMAIL PROTECTED]

Re: man/tbl portability

[Daniel Kobras]

On Mon, Aug 19, 2002 at 01:25:26PM +0200, Mikael Hedin wrote:
> I've enhanced oglerc(5) by adding a tbl section (.TS and .TE and the
> things in between).  On my system (sid) it is preproccessed by tbl(1)
> when I run 'man ./oglerc.5', but on the upstream author's sytem
> (solaris something), the tbl preprocessing does not happen.  Did I
> miss some magic to insert?  Or does this just not work on other
> Unices?  (The man page is in the ogle packge >= 0.8.5-2).

See the NOTES section in man(7).  You need '\ t' at the beginning of the
man page.  But also have a look at section SAFE SUBSET, which suggests
to not use those macros in the first place.

Regards,

Daniel.

Re: HELP - Screen is flooded with DHCP messages.

[Javier Fernández-Sanguino Peña]

On Mon, Aug 19, 2002 at 01:04:39PM +0200, Martin Schulze wrote:
> Javier Fernández-Sanguino Peña wrote:
> > On Sat, Aug 17, 2002 at 11:17:03PM +0200, J.H.M. Dassen (Ray) wrote:
> > > On Sat, Aug 17, 2002 at 20:56:48 +, Andrew M.A. Cater wrote:
> > > > Now flooded with screens full of
> > > > IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:04:76:de:b9:53:08:00 SRC=0.0.0.0 
> > > > DST=255,255,255,255 LEN=328 TOS=0x10 PREC=0x00 TTL=64 ID=0 PROTO=UDP 
> > > > SPT=68 DPT=67 LEN=308
> > > > on all machines.
> > > > 
> > > > Advice please
> > > 
> > > http://lists.debian.org/debian-user/2002/debian-user-200203/msg03266.html
> > > 
> > 404 Not found.
> 
> Huh?
> 
You are right (the 'l' didn't get copy & pasted)

Javi

man/tbl portability

[Mikael Hedin]

Hi,

I've enhanced oglerc(5) by adding a tbl section (.TS and .TE and the
things in between).  On my system (sid) it is preproccessed by tbl(1)
when I run 'man ./oglerc.5', but on the upstream author's sytem
(solaris something), the tbl preprocessing does not happen.  Did I
miss some magic to insert?  Or does this just not work on other
Unices?  (The man page is in the ogle packge >= 0.8.5-2).

TIA,

Micce

-- 
Mikael Hedin, MSc +46 (0)8 344979 (home) +46 (0)70 5891533 (mobile)
[gpg key fingerprint = 387F A8DB DC2A 50E3 FE26  30C4 5793 29D3 C01B 2A22]

Fwd: Bug#157231: devfsd: perms for the rio500 device

[Russell Coker]

Could you please send me suggestions (off-list) as to which would be the best 
default group for such a device, audio or disk.

--  Forwarded Message  --

Subject: Bug#157231: devfsd: perms for the rio500 device
Date: Mon, 19 Aug 2002 05:51:04 +0100
From: Bastien Nocera <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>

Package: devfsd
Version: 1.3.25-8
Severity: wishlist

Heya,

Could you add this line to /etc/devfsd/perms:
REGISTER ^usb/rio500$ PERMISSIONS root.disk 0660

disk is the same group as the one used by flash devices, seems ok,
maybe audio would make more sense, I leave that up to you.

Cheers

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux dozo 2.4.19-rc3-ben0 #1 Sat Jul 27 03:04:34 BST 2002 ppc
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set)

Versions of packages devfsd depends on:
ii  libc6 2.2.5-14   GNU C Library: Shared libraries
 an

-- no debconf information

---

-- 
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
>From field.

Re: GCC 3.2 transition

[Colin Watson]

On Mon, Aug 19, 2002 at 11:32:24AM +0100, Richard Kettlewell wrote:
> Panu A Kalliokoski <[EMAIL PROTECTED]> writes:
> > Well, it is sufficient that the linker gets the additional
> > information from somewhere. Of the two ways (hacking the linker to
> > use different versions depending on the ABI, or having two dynamic
> > linkers) the latter is IMO cleaner, but neither will break anything.
> 
> I'm not yet convinced that the "hack the linker" approach actually
> works properly; it requires Debian to move one set of libraries (say,
> those with the older ABI) to a new path.  It can and may do this for
> libraries in Debian packages, but cannot and must not for libraries
> installed into /usr/local.

That problem shouldn't arise if the hack is done the other way round:
new libraries go to /usr/lib/gcc3.2, say, in cases where the ABI
differs. It does mean we can never get rid of it, but if the C++ ABI
changes in later versions of G++ then we may have to repeat this
transition in future anyway.

-- 
Colin Watson  [EMAIL PROTECTED]

Re: debian-security-announce and bugtraq

[Martin Schulze]

Daniel Jacobowitz wrote:
> On Sat, Aug 17, 2002 at 09:46:42PM +0200, Erich Schubert wrote:
> > it seems like people still don't get that bugtraq is subscribed to
> > debian-security-announce...
> > And bugtraq seems unable to add some Footer to the posts that clarifies
> > this...
> > 
> > Couldn't we
> > - unsubscribe bugtraq from our list

No.

> > - send out security-announces to bugtraq separately?

They're already slightly different, but not different enough.  I'll
reinvestigate that some day.

> > P.S. Or wasn't this recent mail from branden another try to unsubscribe
> > from our postings to bugtraq? I don't remember much recent complaints...
> > maybe that issue is already settled.
> 
> They chose (and choose, repeatedly) to subscribe.  There's really squat
> we can do about it except continue complaining to them.

I've been told that [EMAIL PROTECTED] is the address bounces
should be sent to.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Re: HELP - Screen is flooded with DHCP messages.

[Martin Schulze]

Javier Fernández-Sanguino Peña wrote:
> On Sat, Aug 17, 2002 at 11:17:03PM +0200, J.H.M. Dassen (Ray) wrote:
> > On Sat, Aug 17, 2002 at 20:56:48 +, Andrew M.A. Cater wrote:
> > > Now flooded with screens full of
> > > IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:04:76:de:b9:53:08:00 SRC=0.0.0.0 
> > > DST=255,255,255,255 LEN=328 TOS=0x10 PREC=0x00 TTL=64 ID=0 PROTO=UDP 
> > > SPT=68 DPT=67 LEN=308
> > > on all machines.
> > > 
> > > Advice please
> > 
> > http://lists.debian.org/debian-user/2002/debian-user-200203/msg03266.html
> > 
> 404 Not found.

Huh?

luonnotar!joey(ttyp4):~> HEAD 
http://lists.debian.org/debian-user/2002/debian-user-200203/msg03266.html
200 OK
Connection: close
Date: Mon, 19 Aug 2002 11:04:14 GMT
Accept-Ranges: bytes
ETag: "63abab-119c-3c96d1d5"
Server: Apache/1.3.9 (Unix) Debian/GNU PHP/4.0.3pl1
Content-Length: 4508
Content-Type: text/html
Last-Modified: Tue, 19 Mar 2002 05:51:17 GMT
Client-Date: Mon, 19 Aug 2002 11:04:16 GMT
Client-Response-Num: 1

Looks quite different from 404

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.

Re: Bug#156852: ITP: ttf-dustismo -- general purpose gpl'ed truetype sans serif font

[Ben Armstrong]

On Mon, Aug 19, 2002 at 12:12:41AM -0400, Joey Hess wrote:
> That doesn't mean we have to mindlessly stick to it when packaging a 100k
> font though. We also have the example of freefont, which used uner 3 mb for
> 79 smaller type 1 fonts.

No, but neither does it mean we need to follow the freefont example.  That
case is a licensing nightmare and is in non-free.  Even though the proposed
package would be entirely free, you still may end up with a mishmash of
licenses.  So what is to be done about that?  One package per license?  One
per foundry?  I'm not sure what kind of grouping makes sense.

> > > Note the existing freefont and sharefont packages, which were compiled
> > > by a Debian developer. Why should truetype fonts be packaged any
> > > differently?
> > > 
> > 
> > I don't think they should. My original intent was to make a
> > free-ttffont package, and I'd rather do that.
> 
> That makes sense to me.

I would rather see some compromise between one font per package and all
fonts in one package.  Some breakdown of fonts into separate packages is
convenient for users who want to pick and choose.  And in particular, I
think it's nice if a game can say "Depends: ttf-blah" instead of having its
own private copy of a given font.  If, on the other hand, the font is one of
80 in a 3M package, it is less attractive to do so, which is going to
encourage maintainers to leave the font as an embedded font in the package
(which is probably how upstream distributes it).

Ben
-- 
nSLUG   http://www.nslug.ns.ca  [EMAIL PROTECTED]
Debian  http://www.debian.org   [EMAIL PROTECTED]
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0  1B B1 31 ED C6 A9 39 4F ]
[ gpg key fingerprint = 395C F3A4 35D3 D247 1387  2D9E 5A94 F3CA 0B27 13C8 ]

Re: GCC 3.2 transition

[Richard Kettlewell]

Panu A Kalliokoski <[EMAIL PROTECTED]> writes:
> Richard Kettlewell wrote:

>> I think you've answered your own question; it _can_ known which
>> soname to use, and to discover it, it should check the version of
>> the compiler.
> 
> I'm not sure whether you're actually proposing changing the SONAMEs
> so that the library will compile itself with different SONAME
> depending on the compiler,

Yes, that sounds exactly like what I'm saying.

> but let me say some more problems with using SONAME for the
> transition (even if upstream could be convinced to do this, which in
> practice most certainly is the biggest problem):
> 
> Let's say libfoo version 17.1.6 will be the first libfoo to compile
> itself under libfoo.so.8 if gcc 2 is being used, libfoo.so.9 if gcc 3 is
> being used. You're right, this seems sensible because the libraries do
> have incompatible ABI's. Further releases will retain this separation.
> But what will happen when the library's *own* ABI (the thing SONAMEs are
> really meant for) changes? Will libfoo 18.0.1 install itself under
> libfoo.so.10 if gcc 2 is being used, libfoo.so.11 if gcc 3?

That seems a reasonable approach for as long as both ABIs need to be
supported.  What's the problem with that?

> Or is support for gcc 2 to be dropped from these releases? Why
> should it be a library's business at all to provide information
> about what compiler the user programs should use, and to dictate
> when they cannot use compiler X anymore?

This happens already; for instance, the kernel has a preferred gcc
versions required to build it, and this changes from time to time.

With C++ at the moment we'll probably see more of that rather than
less: the older compilers don't even implement the full language
correctly.  So I suspect the fear of having to support multiple
compiler ABIs for many years hence is unfounded in practice.

> The basic problem here is that SONAMEs contain insufficient
> information, which for example in the case of libc transition was
> too weak to express which other libraries the library is linked
> against, and now is (and should IMO not be made otherwise) too weak
> to tell which compiler was used to compile the library.

Another variant that I think would work but haven't tried, would be to
have the information encoded in the name part of the soname rather
than the number, thus somewhat breaking the relationship between the
name that you link against at compile time and the soname.  I've never
actually tried this but I believe it would work.

But you can pack lots and lots of information into an integer.  I
think the choice of approach can be left to upstream, as long as they
do _something_ to signal the ABI change.

>> Not changing sonames[1] when the ABI changes would also be
>> incredibly painful; bits of software that people use and depend on
>> would start crashing.
> 
> Well, it is sufficient that the linker gets the additional
> information from somewhere. Of the two ways (hacking the linker to
> use different versions depending on the ABI, or having two dynamic
> linkers) the latter is IMO cleaner, but neither will break anything.

I'm not yet convinced that the "hack the linker" approach actually
works properly; it requires Debian to move one set of libraries (say,
those with the older ABI) to a new path.  It can and may do this for
libraries in Debian packages, but cannot and must not for libraries
installed into /usr/local.

-- 
http://www.greenend.org.uk/rjk/

Bug#157248: ITP: zthread -- C++ thread library

[Ivo Timmermans]

Package: wnpp
Version: N/A; reported 2002-08-19
Severity: wishlist

* Package name: zthread
  Version : 2.2.9
  Upstream Author : Eric Crahen <[EMAIL PROTECTED]>
* URL : http://zthread.sourceforge.net/
* License : LGPL
  Description : C++ thread library

The ZThread package is an advanced object-oriented, cross-platform, C++
threading and synchronization library.  It provides a high level
abstraction of the native threading mechanisms to offer a great deal of
flexibility and control.

This software features interruptible Thread and Runnable objects for
C++, control objects and implementations of concurrency design patterns.
This includes semaphores, mutexes, condition variabes as well as other
more complex components.

Existing threading APIs do not provide a consistent and portable means
for exercising control over concurrently executing software. Thread
cancellation a nd termination is one example of this complexity.
ZThreads includes an elegant method of safely terminating threads
without the complications of using cancellation handlers or other
similar constructs.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux phoenix 2.4.19-xfs #3 SMP di aug 6 16:52:17 CEST 2002 i686
Locale: LANG=C, [EMAIL PROTECTED]

-- no debconf information

Re: HELP - Screen is flooded with DHCP messages.

[Javier Fernández-Sanguino Peña]

On Sat, Aug 17, 2002 at 11:17:03PM +0200, J.H.M. Dassen (Ray) wrote:
> On Sat, Aug 17, 2002 at 20:56:48 +, Andrew M.A. Cater wrote:
> > Now flooded with screens full of
> > IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:04:76:de:b9:53:08:00 SRC=0.0.0.0 
> > DST=255,255,255,255 LEN=328 TOS=0x10 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=68 
> > DPT=67 LEN=308
> > on all machines.
> > 
> > Advice please
> 
> http://lists.debian.org/debian-user/2002/debian-user-200203/msg03266.html
> 
404 Not found.

Regards

Javi

redistribution of M$ fonts [nelson@crynwr.com: [Familiar] fonts]

[Stefano Zacchiroli]

FYI

- Forwarded message from Russell Nelson <[EMAIL PROTECTED]> -

Date: Sun, 18 Aug 2002 14:34:28 -0400 (EDT)
From: Russell Nelson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Familiar] fonts

http://corefonts.sourceforge.net/ distributes the Microsoft core
fonts.

-- 
-russ nelson  http://russnelson.com |
Crynwr sells support for free software  | PGPok | businesses persuade
521 Pleasant Valley Rd. | +1 315 268 1925 voice | governments coerce
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   |
___
The Familiar Linux Distribution
Familiar mailing list
[EMAIL PROTECTED]
http://handhelds.org/mailman/listinfo/familiar
irc://irc.openprojects.net #familiar

- End forwarded message -

-- 
Stefano Zacchiroli - undergraduate student of CS @ Univ. Bologna, Italy
[EMAIL PROTECTED] | ICQ# 33538863 | http://www.cs.unibo.it/~zacchiro
"I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant!" -- G.Romney

Re: list of valid distributions in Debian changelog file.

[Martin Schulze]

Peter S Galbraith wrote:
> Hi,  What are the currently valid distribution to which we can make
> uploads to?
> 
> debian-changelog-mode.el currently allows the user to set the
> distribution field for an upload to multiple distributions, e.g.
> 
> xwatch (2.11-8) frozen unstable; urgency=low
> 
> The list of possibilities is currently set to:

The following are very bad and likely not to work properly with katie
and the SRM, hence, I guess that it would make sense to not include
them directly:

>   stable unstable
>   stable frozen
>   stable frozen unstable

Additionally, for security we have:

   oldstable-security
   stable-security
   testing-security

However, I'd like people to upload through the security team so we
don't suffer from broken distributions or broken versions when working
on a security problem.  Yes, such things happen, way too often,
unfortunately.  Hence, it may be wise to add these only as a comment
in some document but not in the actual debian-changelog-mode.

Regards,

Joey

-- 
GNU GPL: "The source will be with you... always."

Please always Cc to me when replying to me on the lists.

Re: New ALSA packages (0.9.0rc3) for test

[Bastian Kleineidam]

On Mon, Aug 19, 2002 at 03:55:33PM +0900, Masato Taruishi wrote:
> 
> cool. I'm quite a busy to maintain alsa. If you want, could you
> take over them?
Only if you sponsor me. My GPG key has expired on the keyring and
the new one (this is the one I am signing this mail with) is not
yet accepted.
So if you can be my sponsor I will send you the packages ready
for an official upload.


Cheers, Bastian

-- 
Bastian Kleineidam · [EMAIL PROTECTED] · GPG key ID 32EC6F3E


pgpF7R5c5oSTZ.pgp
Description: PGP signature

Re: New ALSA packages (0.9.0rc3) for test

[Masato Taruishi]

cool. I'm quite a busy to maintain alsa. If you want, could you
take over them?

At Sun, 18 Aug 2002 19:30:25 +0200,
Bastian Kleineidam wrote:

> I compiled for myself the new ALSA rc3 packages and put them into
> deb http://people.debian.org/~calvin/debian/ ./
> deb-src http://people.debian.org/~calvin/debian/ ./
> 
> These packages work for me, but you can report any bugs to
> [EMAIL PROTECTED] (not in the BTS).
> 
> Junichi, if you choose to upload some of these packages, please remove
> the "Private package" lines from all control description entries.
> And you might want to revert some changes I made, as I have done
> these changes without your experience on these packages.
> 
> Now on to the debian/changelogs:
> 
> alsa-driver (0.9.0rc3-1) unstable; urgency=low
> 
>   * New upstream release (closes: #122632, #151502).
>   * The gusextreme module load problem should be also fixed by now:
> hwdep.o is included, mpu401_uart.o is included, the
> opl3_new_device function does not exist any more. (closes: #54131)
>   * The new upstream adds the missing hwdep object file for
> some SoundBlaster cards (closes: #148900).
>   * The new upstream uses linux/slab.h instead of linux/malloc.h
> (closes: #114598)
>   * work around missing symbols in 2.2 Kernels (closes: #147383)
>   * move debconf-utils from recommends to depends
> (closes: #85242, #104163)
>   * move debhelper from recommends to depends. This and the above
> make the check-debian-rules-pkg unnecessary.
> (closes: #95920, #135535)
>   * updated all depends for new version (and debhelper 3)
>   * standards version 3.5.6.1
>   * fix minor spellings in alsa-source README.Debian (closes: #147013)
>   * Generated packages depend on the appropriate kernel image.
> If you want to compile kernels manually *without* Debian packaging,
> you should not use this package but compile ALSA also from source.
> (closes: #94564)
>   * delete call of unused dh_install{cron,manpages,info,menu}
>   * add russion translation to alsa-source template (closes: #138322).
>   * update german translation of alsa-base.template, other languages are
> still lagging behind (debconf-margetemplates rejects them).
>   * add german translation of alsa-source.template and control.
>   * updated cards database (closes: #141154)
>   * remove obsolete debian/debconf/cards.sh
> 
>  -- Bastian Kleineidam <[EMAIL PROTECTED]>  Thu, 15 Aug 2002 14:13:54 +0200
> 
> alsa-lib (0.9.0rc3-1) unstable; urgency=low
> 
>   * New upstream release.
>   * New upstream has updated iatomic.h for mips 
> (closes: #149159, #145016)
>   * Removed unnecessary powerpc patch
>   * Removed libtool hack (dont know why this was there)
>   * Removed call to auto* tools, adjust build-depends
>   * Build-depend on latest alsa-headers
>   * Standards-Version: 3.5.6.1
>   * DH_COMPAT=3; change debian/tmp references to debian/$(package)
> (closes: #157056)
>   * Update config.{guess,sub}, ran libtoolize (closes: #101287)
>   * Do s/make/$(MAKE)/ in debian/rules.
>   * Add install target to debian/rules.
>   * Removed unnecessary debian/libasound0.4*.
>   * Removed unnecessary debian/postinst.
>   * Link asound.1 to undocumented.
> 
>  -- Bastian Kleineidam <[EMAIL PROTECTED]>  Sun, 18 Aug 2002 13:51:22 +0200
> 
> alsa-utils (0.9.0rc3-1) unstable; urgency=low
> 
>   * New upstream release (closes: #139318).
>   * Standards-Version: 3.5.6.1
>   * Use absolute filenames in dh_link (closes: #148323).
>   * Testing/stable versions are consistent (closes: #124127).
>   * Update dependencies version of alsa-base to rc3
>   * Conflict with alsa-utils-0.5, I dont provide it installed together
> with alsa-utils-0.9.
> 
>  -- Bastian Kleineidam <[EMAIL PROTECTED]>  Sun, 18 Aug 2002 17:21:05 +0200

Re: Next Debconf

[Joe Drew]

On Thu, 2002-08-15 at 12:20, Tollef Fog Heen wrote:
> since nobody else has taken up the thread:

I long ago declared my intention to organize debconf 3 in montreal or
vancouver, but I am absolutely not opposed to having the "in-between"
debconf outside of Canada.
 
> I am planning Debconf 3 to be held in Oslo, from Friday July 18th to
> Sunday July 20th.

You'll be interested in bug#152529, which details the request for a
debian-conference list. This will help all debconfs in the future,
whenever it gets created.

-- 
Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

"This particular group of cats is mostly self-herding." -- Bdale Garbee