Re: Broken dpkg-source in the newest dpkg (warning).

[Joey Hess]

Robert Luberda wrote:
> dpkg 1.8.1, which was installed a few hours ago, comes with broken
> dpkg-source. You can't make your packages with it.
> 
> Please see #81152 and #65021 for more info. 

Hmm, I just built a diff.gz with it and it is fine. Does the bug only
occur under some circumstances?

-- 
see shy jo

Re: BIND 9.X, shared libraries, and package pools

[Bdale Garbee]

[EMAIL PROTECTED] (Brian May) writes:

> Does bind come with multiple libraries?

Yes.  Four, I think.

Ok, I haven't looked at our policies for shared libs for a while, and I 
obviously have some reading to do.  Thanks for the warnings.

Bdale

mail-followup-to and Mutt

[Neil Schemenauer]

To get the mail-followup-to header to work in Mutt you must use
the subscribe command and not the lists command to indicate which
mailing lists your on.  If you use lists then Mutt thinks you are
not on the list and adds your address to the mail-followup-to
hedaer.

It took me a while to figure this out even though it is
documented.  I think I had an old config file that used lists
before subscribe even existed.  Making this error defeats the
purpose of mail-followup-to and I suspect other people have made
the same error.  Perhaps the Mutt manual should be updated to
make this more clear.

  Neil

Re: Broken dpkg-source in the newest dpkg (warning).

[Joey Hess]

Joey Hess wrote:
> Robert Luberda wrote:
> > dpkg 1.8.1, which was installed a few hours ago, comes with broken
> > dpkg-source. You can't make your packages with it.
> > 
> > Please see #81152 and #65021 for more info. 
> 
> Hmm, I just built a diff.gz with it and it is fine. Does the bug only
> occur under some circumstances?

--- lm-sensors-2.5.4.orig/debian/changelog
+++ /dev/null
@@ -0,0 +1,328 @@
+lm-sensors (2.5.4-3) unstable; urgency=low

Ugh, now I see.

[EMAIL PROTECTED]:~/tmp>dpkg-source -x ~/debian/packages/lm-sensors_2.5.4-3.dsc
dpkg-source: error: line after --- for file
lm-sensors-2.5.4.orig/debian/changelog isn't as expected
+ exit 29

Bleck. 

[EMAIL PROTECTED]:/org/ftp.debian.org/incoming>zgrep '+++ /dev/null' *.diff.gz
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null
qiv_1.5-1.diff.gz:+++ /dev/null

Only one package affected so far? Someone should make sure broken
packages do not dinstall.

-- 
see shy jo

Re: Broken dpkg-source in the newest dpkg (warning).

[Joey Hess]

Argh. I just grepped every source package in the archive, and these are
broken:

[EMAIL PROTECTED]:/org/ftp.debian.org/ftp>find |grep diff.gz | xargs zgrep -l
'+++ /dev/null'
./pool/main/d/docbook-stylesheets/docbook-stylesheets_1.60-1.diff.gz
./pool/main/g/guppi/guppi_0.35.2-4.diff.gz
./pool/main/l/lsb-release/lsb-release_1.4-1.diff.gz

Ok, it could be worse.

-- 
see shy jo

Re: BIND 9.X package status

[Nate Duehr]

On Sat, Jan 06, 2001 at 10:48:47AM +1100, Brian May wrote:
> I have to wonder if it is really worth having a different name for the
> newer package version. Are the versions really that different?
> Personally, I would prefer to have apt-get automatically upgrade the
> package, and that will be disabled once you include the version number
> in the package number.

Knowing that Bdale's a busy guy, I thought I might summarize some of the
information out there at ISC and via my own experiences with BIND
recently for those who don't want to keep up with the bind-isc mailing
list (you think debian-devel or debian-user are bad?  read 40-100 "Why
doesn't my domain name work?" generic messages a day!  ;)

At this point in their development cycles I wouldn't call BIND 9 an
upgrade for BIND 8.  In fact if you read the history file at isc.org,
BIND 9 is a complete re-write.  Hardly an 8 to 9 upgrade.

I think Bdale's plan is a good one, but there may be some breakage if
ISC doesn't release a BIND 9 that fully supports the BIND 8 style zone
files.  Up until the latest Beta release of BIND 9, it didn't even
understand $GENERATE statements!

Those who can live without the features they left behind in BIND 8
and didn't implement, and especially those who want the new features
in BIND 9 are encouraged to switch.

BIND 8 and BIND 9 are still not quite the same nameserver yet, however.

BIND 9.1.0 fixes the most grevious problem with migration for many
people which was that BIND 9.0.1 did not understand $GENERATE
statements in zone files at all.

In BIND 9.1.0's doc/misc/migration file:

"BIND 9 is designed to be mostly upwards compatible with BIND 8, but
there is still a number of caveats you should be aware of when
upgrading an existing BIND 8 installation to use BIND 9."

You can see the docs in the source for the specifics, but it's not ready
to use as a drop-in replacement yet.  It does have a huge number of NEW
features, but some old features are lagging behind. 

Plopping BIND 9 binaries in over BIND 8 zone files was almost guaranteed
to break something in all but the most "plain vanilla" configurations
until the (still Beta) release of BIND 9.1.0.

Currently there are four major BIND's in the wild that folks might be
using if they're keeping up-to-date:


BIND 8.2.2-P7 (what's in Debian) -- OFFICIAL RELEASE ON BIND 8 PLATFORM

BIND 8.2.3-T9B - has a few new features on old codebase and mostly NT
build bugfixes, but some general bugfixes too.

BIND 9.0.1 (bugfixes) -- OFFICIAL RELEASE BIND 9 PLATFORM 

BIND 9.1.0b2 - second Beta of BIND 9 platform (first to have $GENERATE)


There are a LOT of changes, and I'm still playing around with BIND 9 on
a non-production server to see what all is different, but it's
definitely not going to be a smooth upgrade path right now unless 
BIND 9.2 finishes up most/all of the leftover stuff that's not
implemented.  

ISC has not been very public about their plans for full backward
compatibility (although they appear to be striving towards it)
nor have I seen a release plan for when they will have that done -- and
stop support for BIND 8.  But right now they're running both versions
(and releases) in parallel.

I should clarify that by "public" I mean their web pages.  There have
been some comments made by developers in the bind-isc mailing list, but
their web pages are falling behind again.  (They don't have history
notes past BIND 8.2.2-P5 in the "Highlights of BIND 8.x" section yet.

In addition many commercial products and other free software (some
packaged for Debian, some not yet) expect all the BIND 8 zone file
features to be working.  Especially software that generates zone files
automatically from databases.  (Many of which actually leverage the
special statements available from the BIND 8 zone parsing engine and
cheat heavily.)

Anyone who's playing with BIND 9 and wants to trade notes as you go
along, I'll be happy to share anything I find useful/annoying/crazy/fun,
just e-mail me privately off-list.

-- 
Nate Duehr <[EMAIL PROTECTED]>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.

ITO: wterm

[Mark Triggs]

Hi,

Due to lack of time on my part, but more importantly due to a
discontinuation of upstream development, I'm orphaning my packages 'wterm' and
'wterm-ml'.

If anyone wants to take over this package, please let me know.

Regards, happy new year, etc..

 Mark



-- 
<[EMAIL PROTECTED]> || <[EMAIL PROTECTED]>  
Fingerprint: 1024D/3A2EC93E 901A DCF2 C894 7115 BFFF  D2B0 50E1 989F 3A2E C93E

Re: egcs/gcc?

[Tommi Virtanen]

On Fri, Jan 05, 2001 at 06:08:44PM +, J.H.M. Dassen (Ray) wrote:
> On Fri, Jan 05, 2001 at 19:03:45 +0100, Wichert Akkerman wrote:
> > Previously J.H.M. Dassen (Ray) wrote:
> > >   - x25tap
> > >   - kerneli crypto patches
> > >   - ReiserFS
> > In that case ReiserFS is a really bad example, it might never be in 2.2
> > and Linus said it will be added in the 2.4 series.
> All of them are "add-ons" to vanilla 2.2. My point is that even if vanilla
> 2.4 supports all that 2.2 supports, there are still a lot of feature patches
> outside vanilla 2.2 for which no 2.4 equivalent may be available for quite
> some time to come.

And you are pretty wrong there; reiserfs for 2.4 has
been there for a while.

-- 
[EMAIL PROTECTED],havoc,gaeshido}.fi,{debian,wanderer}.org,stonesoft.com}
Perl this: sub stack() {my @a; sub [EMAIL PROTECTED](@a,@_):pop(@a)}}

Re: mail-followup-to and Mutt

[Marco d'Itri]

On Jan 06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:

 >the same error.  Perhaps the Mutt manual should be updated to
 >make this more clear.
README.Debian.

-- 
ciao,
Marco

Re: DEBIAN IS LOOSING PACKAGES AND NOBODY CARES!!!

[Ola Lundqvist]

On Mon, Jan 01, 2001 at 01:05:17AM +1000, Anthony Towns wrote:
> Happy new year from this side of the world,
> 
> On Sun, Dec 31, 2000 at 01:06:18PM +0100, [EMAIL PROTECTED] wrote:
> > Three packages (w3mir, webmin, and fancylogin) that were definitely
> > available in Debian main some time ago, and that are still present
> > in the BTS (all have outstanding bugs), COMPLETELY DISAPPEARED from
> > Debian.
> 
> webmin:
> ] Subject: webmin_0.80-1_i386.changes REJECTED
> ]  Depends: perl5, debconf, libnet-ssleay-perl
> ]   ^^
> ] libnet-ssleay-perl is in non-US, packages in main may not depend on
> ] packages outside of main.  This package belongs in either contrib or
> ] non-US/main.
> 
> The other two were also deliberately removed, dunno why offhand.

Well there are always reasons for packages to been removed. I can only
answer for webmin. I uploaded the 0.80-1 version and it was placed in
main (it should be in non-US). But that is not the reason why it was
removed because I just had to upload a new version and ask somebody to
change the override file.

The reason is that Jaldhar is about adopt them (he have a better
packaging structure) and he is working on it. For more webmin status
see some other threads on this list. :)

To upload the new webmin packages the orginal webmin package had
to be removed so thats why. I think webmin is about to be released
soon, but he'll know better than I do.

// Ola

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Björnkärrsgatan 5 A.11   \
|  [EMAIL PROTECTED] 584 36 LINKÖPING |
|  +46 (0)13-17 69 83  +46 (0)70-332 1551   |
|  http://www.opal.dhs.org UIN/icq: 4912500 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Re: maybe ITP rsync mirror script for pools

[Peter Gervai]

On Wed, Jan 03, 2001 at 11:57:07PM +0100, Marco d'Itri wrote:

> Please don't encourage private mirrors!
> 
> I have been the administrator of ftp.it.debian.org since a long time,
> and I notice there are many sites doing nightly mirrors for their own
> use.

I believe "their own use" is a bit too broad.
I do a nightly mirror for example "for my own use", which means
covering local MAN networks and even some farther, national users.

Not everyone is able to wait for 10 times longer for apt-getting,
when the "official" national mirror slow (or doesn't exist at all),
and the international ones are slow as hell (because national bandwidth
is much more bigger and cheaper for the providers).


It would be, however, maybe nice to make a free-for-everyone unofficial
mirror registration webpage, where people could register their mirror site,
location, update rate, accessiblity, and many other properties. Maybe there
is such page, I don't know. 

I'm sure many larger local networks mirror for the users: often it's cheaper
than any other methods. If people would find a closer, faster mirror, maybe
they'd stop mirroring for themselves.

> They could save bandwidth and disk space just by using a correctly
> configured squid cache.

You mean a squid accepting 50MB+ files for caching? Memory isn't *THAT*
cheap. I don't know how much memory would it use... (Bigger files mean
bigger memory hotlist plus bigger disk space requirements which means even
bigger memory footprint.) I don't think this is a good idea, but the
mileages tend to spend their valuable times with varying, cough, cough.


cya,
grin

Re: lilo.conf

[Gordon Sadler]

On Sat, Jan 06, 2001 at 12:04:52PM +, Lars Wirzenius wrote:
> Russell Coker <[EMAIL PROTECTED]>:
> > I am working on the Debian package of lilo and am writing code for
> > auto-generating lilo.conf files.
> 
> Presumably, if there is a /etc/lilo.conf file already on the system, you
> will ask whether to keep that as it is or whether to create a new one?
> (I'd like confirmation about this, in light of the other lilo related
> thread.)

Just FYI, as of now, the package available in sid/unstable does NOT ask
to save your /etc/lilo.conf. If you install the current deb backup your
lilo.conf file first.

Re: lilo.conf

[Peter Makholm]

Russell Coker <[EMAIL PROTECTED]> writes:

> boot=/dev/ide/host0/bus0/target0/lun0/disc
> root=/dev/ide/host0/bus0/target0/lun0/part3

Don't assume devfs! A lot of us uses it, but before our standard
kernel uses it our lilo package shouldn't assume it unless it is very
sure that it will work.

Re: tar -I incompatibility

[Scott Ellis]

> Goswin Brederlow wrote:
> > the Author of tar changed the --bzip option again. This time its even
> > worse than the last time, since -I is still a valid option but with a
> > totally different meaning.
> >
> > This totally changes the behaviour of tar and I would consider that a
> > critical bug, since backup software does break horribly with the new
> > semantic.
>
> Yes, I think that this should definetely be changed back. The first time
> I encountered this problem, I thought that the tar.bz2 archive was
> broken from the error message tar reported. (Not a valid tar archive or
> so.) This change is confusing and unreasonable IMHO.

Of course the -I option to tar was completely non-standard.  The changelog
explains why it changed, to be consistant with Solaris tar.  I'd prefer
portability and consistancy any day, it shouldn't take that long to change
any custom scripts you have.  I always use long options for nonstandard
commands when building scripts anyway :)

Re: lilo.conf

[Cosimo Alfarano]

On Sat, Jan 06, 2001 at 01:33:57PM +0100, Peter Makholm wrote:
> Don't assume devfs! A lot of us uses it, but before our standard
> kernel uses it our lilo package shouldn't assume it unless it is very
> sure that it will work.

He shouldn't assume it even if debian standard kernel package uses it.
A lot of users don't use them (both std kernel and devfs).

bye,
KA.
-- 
Cosimo Alfarano  - Kame Alfa on UseNet|IRC
  Undergraduate Student in Computer Science  @  Bologna University [Italy] 
0DBD 8FCC 4F6B 8D41 8F43  63A1 E43B 153C CB46 7E27 - 0xCB467E27/1024

Re: tar -I incompatibility

[Roland Bauerschmidt]

Scott Ellis wrote:
> Of course the -I option to tar was completely non-standard.  The changelog
> explains why it changed, to be consistant with Solaris tar.  I'd prefer
> portability and consistancy any day, it shouldn't take that long to change
> any custom scripts you have.  I always use long options for nonstandard
> commands when building scripts anyway :)

Well, ok, I didn't know about Solaris tar. Probably, they are right
then, but nevertheless, it is a pain. Maybe there should be a debconf
text message, priority low, that informs the user about it if Debconf is
installed?

Roland

-- 
Roland Bauerschmidt <[EMAIL PROTECTED]>

Re: What to do about /etc/debian_version

[Santiago Vila]

On Sat, 6 Jan 2001, Christopher Yeoh wrote:

> > So: Is there a *technical* reason to change /etc/debian_version other
> > than it being just "nicer"?
>
> This information could instead be stored in /etc/lsb-release. One of
> the reasons for the creation of this file was to standardise across
> the distributions the name and format of the file which contains this
> type of information.

Interesting. Is that file in /etc because of it being a static,
non-shareable file (like /etc/debian_version), or it is also meant to
be changed by the sysadmin? Could you point me to the specs for that
file? (i.e. something that tells me what should be its contents for
Debian 2.2 and for Debian woody/sid).

Thanks.

Re: lilo.conf

[Mark Brown]

On Sat, Jan 06, 2001 at 06:06:47AM -0600, Gordon Sadler wrote:

> Just FYI, as of now, the package available in sid/unstable does NOT ask
> to save your /etc/lilo.conf. If you install the current deb backup your
> lilo.conf file first.

If you've done the upgrade already note that it does save it itself to 
/etc/lilo.conf.old (although it does this each time it's reconfigured so
you'll only have the previous lilo.conf in there).

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/


pgpO9GSNETMOA.pgp
Description: PGP signature

Re: mail-followup-to and Mutt

[Matt Zimmerman]

On Sat, Jan 06, 2001 at 11:13:22AM +0100, Marco d'Itri wrote:

> On Jan 06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> 
>  >the same error.  Perhaps the Mutt manual should be updated to
>  >make this more clear.
> README.Debian.

ITYM README.UPGRADE.

-- 
 - mdz

Re: LILO 21.6-2

[Hamish Moffatt]

On Fri, Jan 05, 2001 at 08:08:05PM -0800, Joey Hess wrote:
>   Please verify lilo.conf by hand and send comments to [EMAIL PROTECTED]

Also, [EMAIL PROTECTED] would really be better than a specific address.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Re: LILO 21.6-2

[Adam Heath]

On Sun, 7 Jan 2001, Hamish Moffatt wrote:

> On Fri, Jan 05, 2001 at 08:08:05PM -0800, Joey Hess wrote:
> >   Please verify lilo.conf by hand and send comments to [EMAIL PROTECTED]
> 
> Also, [EMAIL PROTECTED] would really be better than a specific address.

Not if he isn't the current maintainer of lilo.

BEGIN GEEK CODE BLOCK
Version: 3.12
GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-END GEEK CODE BLOCK-
BEGIN PGP INFO
Adam Heath <[EMAIL PROTECTED]>Finger Print | KeyID
67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA  3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-END PGP INFO-

Re: lilo.conf

[Matt Zimmerman]

On Sat, Jan 06, 2001 at 01:58:48PM +0100, Cosimo Alfarano wrote:

> On Sat, Jan 06, 2001 at 01:33:57PM +0100, Peter Makholm wrote:
> > Don't assume devfs! A lot of us uses it, but before our standard
> > kernel uses it our lilo package shouldn't assume it unless it is very
> > sure that it will work.
> 
> He shouldn't assume it even if debian standard kernel package uses it.
> A lot of users don't use them (both std kernel and devfs).

Especially since devfs support is still considered experimental.

-- 
 - mdz

Re: What to do about /etc/debian_version

[Christopher Yeoh]

Santiago Vila writes:
> > This information could instead be stored in /etc/lsb-release. One of
> > the reasons for the creation of this file was to standardise across
> > the distributions the name and format of the file which contains this
> > type of information.
> 
> Interesting. Is that file in /etc because of it being a static,
> non-shareable file (like /etc/debian_version), or it is also meant to
> be changed by the sysadmin? 

It'd be pretty rare that a sysadmin would want to change it - although
there are some programs around that attempt to work out what distro
they're on and refuse to install/run if its not the right one - so it
can be useful to be able to lie to them :-)

> Could you point me to the specs for that
> file? (i.e. something that tells me what should be its contents for
> Debian 2.2 and for Debian woody/sid).

Its also used by the lsb_release (package lsb-release) program. There
is a man page for it and the latest version is available from:

https://sourceforge.net/project/showfiles.php?group_id=1107&release_id=19799

(version 1.3 is in unstable - I'm not sure if 1.4 has been put in yet
as it was only released a couple of days ago).

Chris.
-- 
[EMAIL PROTECTED]
Support Open Source Ice-Cream

Re: rsync mirror script for pools - first pre alpha release

[Goswin Brederlow]

> " " == esoR ocsirF <[EMAIL PROTECTED]> writes:

 > I would like to set up our local partial mirror to run without
 > attendance through multiple releases. If I hard code the
 > release candidate name into the mirror script, wont it just
 > break when testing goes stable?

The problem is that those are links and rsync can eigther keep links
or follow them.

At the moment there are a lot for links in potato/woody so I can't
follow links, so no mirroring of stable/unstable/testing.

I could check what stable/testing/unstable is and then mirror what
they point to, but who cares. In a year or so an update or
debian-mirror will ask you weather you want to start mirroring the new
unstable and weather to drop the old stable.

MfG
Goswin

Re: Upcoming Events in Germany

[Goswin Brederlow]

> " " == Martin Schulze <[EMAIL PROTECTED]> writes:

 > May 19-20 Berliner Linux Infotage
 > http://www.belug.org/infotage/

Intresting. Gotta check my calendar for a vistit to my parents in
Berlin during that time.

 > July 5-8 LinuxTag 2001, Stuttgart http://www.linuxtag.org/
 > http://www.infodrom.ffis.de/Debian/events/LinuxTag2001/

Already planed to be there.

MfG
Goswin

Re: What to do about /etc/debian_version

[Marco d'Itri]

On Jan 06, Joey Hess <[EMAIL PROTECTED]> wrote:

 >[EMAIL PROTECTED]:/tmp>mount -o loop foo 1
Why don't we just patch mount to use /var/run/mtab?
I don't know about any other program which modifies it.

-- 
ciao,
Marco

Re: diskless package and devfs (Linux 2.4.x)

[Goswin Brederlow]

> " " == Brian May <[EMAIL PROTECTED]> writes:

 > Hello, would anyone object if I made the diskless package
 > depend on devfs support from 2.4.x in future versions?

Please do.

MfG
Goswin (a devfs fan).

Re: tar -I incompatibility

[Goswin Brederlow]

> " " == Scott Ellis <[EMAIL PROTECTED]> writes:

>> Goswin Brederlow wrote: > the Author of tar changed the --bzip
>> option again. This time its even > worse than the last time,
>> since -I is still a valid option but with a > totally different
>> meaning.  > > This totally changes the behaviour of tar and I
>> would consider that a > critical bug, since backup software
>> does break horribly with the new > semantic.
>> 
>> Yes, I think that this should definetely be changed back. The
>> first time I encountered this problem, I thought that the
>> tar.bz2 archive was broken from the error message tar
>> reported. (Not a valid tar archive or so.) This change is
>> confusing and unreasonable IMHO.

 > Of course the -I option to tar was completely non-standard.
 > The changelog explains why it changed, to be consistant with
 > Solaris tar.  I'd prefer portability and consistancy any day,
 > it shouldn't take that long to change any custom scripts you
 > have.  I always use long options for nonstandard commands when
 > building scripts anyway :)

The problem is that -I works although it should completly break
everything. The only difference is that the tar file won't be
compressed anymore.

No warning, no error and noone reads changelogs unless something
breaks. (well, most people don't).

"mkdir bla"
"tar -cIvvf bla.tar.bz2 bla" should give:

"bla.tar.bz2: No such file" Since -I reads the files to be included
from a file.

"bla: Failed to open file, bla is a directory"  Since tar should try
to create a tra file named bla, which is a directoy.

or

"tar: cowerdly refusing to create empty archive"Since there
are no file given as parameters and none read from
bla.tar.bz2.

So where are the errors?

MfG
Goswin

PS: Why not change the Solaris version to be compatible with the widely used 
linux version? I'm sure there are more people and tools out there for linux 
using -I then there are for solaris.

Re: LILO 21.6-2

[Russell Coker]

On Sunday 07 January 2001 00:46, Adam Heath wrote:
> On Sun, 7 Jan 2001, Hamish Moffatt wrote:
> > On Fri, Jan 05, 2001 at 08:08:05PM -0800, Joey Hess wrote:
> > >   Please verify lilo.conf by hand and send comments to
> > > [EMAIL PROTECTED]
> >
> > Also, [EMAIL PROTECTED] would really be better than a specific
> > address.
>
> Not if he isn't the current maintainer of lilo.

True.

So how do I get registered as the maintainer?  The previous maintainer has 
agreed to me taking it over.  I've uploaded a package with me listed as the 
maintainer (which hasn't worked).  So obviously there's something else I have 
to do.  Could someone please tell me what it is?

I'm sure that I could find it somewhere on the web pages.  But it's 1:30 here 
and I'm staying up late to release a new lilo package to address all the 
issues that have been discussed here and elsewhere...

-- 
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/   Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page

[devfs users]: evaluate a patch please

[Martin Bialasinski]

Hi,

there is a bug in the mc package, that most likely is related to
devfs. I can't reproduce it, nor does it seem to be common.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=57557&repeatmerged=yes

mc hangs occasionally on starup on the VC.

There is a patch on the buttom of the report.

Could you tell me, if it is formally OK and if it fixes the problem
for you, if you can reproduce the bug?

Thanks,
Martin

Re: What to do about /etc/debian_version

[Matt Zimmerman]

On Sat, Jan 06, 2001 at 02:19:36PM +0100, Santiago Vila wrote:

> On Sat, 6 Jan 2001, Christopher Yeoh wrote:
> > This information could instead be stored in /etc/lsb-release. One of
> > the reasons for the creation of this file was to standardise across
> > the distributions the name and format of the file which contains this
> > type of information.
> 
> Interesting. Is that file in /etc because of it being a static,
> non-shareable file (like /etc/debian_version), or it is also meant to
> be changed by the sysadmin? Could you point me to the specs for that
> file? (i.e. something that tells me what should be its contents for
> Debian 2.2 and for Debian woody/sid).

The fact is, files like this usually lie.  What information can you really get
from such a file?  If you want to know which version of a certain program is
installed, that information can be had as easily (and more accurately) from
other sources.  If you want to know where apt is downloading new software from,
that information is also elsewhere.  This file doesn't even serve to tell
whether the system originally was installed from a certain source media, as it
could be easily and automatically upgraded along with the rest of the system.

Even in the case of Big Commercial OS's with large, tagged releases (such as
Solaris), much of the system is often modified by patches, so that it is not
sufficient to simply test the version of the OS, but whether certain patches
are installed.

-- 
 - mdz

Re: What to do about /etc/debian_version

[Ethan Benson]

On Sat, Jan 06, 2001 at 01:49:59PM +0100, Marco d'Itri wrote:
> On Jan 06, Joey Hess <[EMAIL PROTECTED]> wrote:
> 
>  >[EMAIL PROTECTED]:/tmp>mount -o loop foo 1
> Why don't we just patch mount to use /var/run/mtab?
> I don't know about any other program which modifies it.

because /var is not always on the same partition as /

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpCm5HRdFdRO.pgp
Description: PGP signature

Re: tar -I incompatibility

[Colin Watson]

"Scott Ellis" <[EMAIL PROTECTED]> wrote:
>Of course the -I option to tar was completely non-standard.  The
>changelog explains why it changed, to be consistant with Solaris tar.

I don't see the reasoning in the changelog, but I may just have missed
it.

>I'd prefer portability and consistancy any day, it shouldn't take that
>long to change any custom scripts you have.

Why not have portability, consistency, *and* backward compatibility?
Make -I an alias for -j, problem solved. Unless Solaris tar has -I as an
alias for -T - I suppose it must, as I can't think of any reason for
such a blatantly incompatible change.

>I always use long options for nonstandard commands when building
>scripts anyway :)

All the upstream tar people are doing is encouraging people to go back
to 'bzip2 -dc foo.tar.bz2 | tar xvf -', I think. And, hell, if you want
to be portable across Unixes you have to do that anyway.

-- 
Colin Watson [EMAIL PROTECTED]

What is wrong with kde2.1 and unstable ?

[Michael Meding]

Hi all,

as of three days ago, every attempt to do a dist-upgrade tries to uninstall 
almost every kde package. What is wrong there.

Maybe the package maintainer knows ?

Thanks in advance

Greetings

Michael Meding

Re: LILO 21.6-2

[Colin Watson]

Russell Coker <[EMAIL PROTECTED]> wrote:
>On Sunday 07 January 2001 00:46, Adam Heath wrote:
>> On Sun, 7 Jan 2001, Hamish Moffatt wrote:
>> > Also, [EMAIL PROTECTED] would really be better than a specific
>> > address.
>>
>> Not if he isn't the current maintainer of lilo.
>
>True.
>
>So how do I get registered as the maintainer?

You are:

  [EMAIL PROTECTED] ~]$ grep '^lilo ' Maintainers 
  lilo Russell Coker <[EMAIL PROTECTED]>

Maybe the same thing happened to you as to me with shaper; it took until
the next dinstall run for the BTS to get up to date, so perhaps there
was some transient problem. See the sequence of events in #81327.

-- 
Colin Watson [EMAIL PROTECTED]

Bug#81396: root shell fscked after upgrade to woody

[Eray 'exa' Ozkural]

Package: general
Version: N/A; reported 2001-01-06
Severity: important

After I upgraded from potato to woody on
an i386 machine, I observed a strange sympton

I login as root. It doesn't matter where, console, X or
from network...
When I check the environment, normal user environment is
present. If I run apt-get upgrade for instance the program
will complain that path doesn't have the *sbin directories
which is the way it should be. The quickest way to fix it
is to type
# su
and then I can run any root process without errors on this
child shell.

I observed the exact error on another installation while
upgrading from slink to potato so I presume this is a bug
which has not been addressed yet. I had then thought this
was a "feature" not a "bug" but now I'm certainly sure it's
a bug because the machines I installed from scratch *never*
show this behaviour.

Thanks,

-- System Information
Debian Release: woody
Architecture: i386
Kernel: Linux borg 2.2.14 #1 Wed Mar 29 19:43:52 EEST 2000 i686

Re: package pool and big Packages.gz file

[Andrew Stribblehill]

Quoting Goswin Brederlow <[EMAIL PROTECTED]>:
> > " " == Sami Haahtinen <[EMAIL PROTECTED]> writes:
>
>  > Or, can rsync sync binary files?
> 
> Of cause, but forget it with compressed data.

Doesn't gzip have a --rsync option, or somesuch? Apparently Andrew
Tridgell (Samba, Rsync) has a patch to do this, but I don't know
whether he passed it onto the gzip maintainers.

(Apparently he's working on a --fuzzy flag for matching rsyncs
between, say foo-1.0.deb and foo-1.1.deb. He says it should be
called the --debian flag.)

Cheerio,

Andrew Stribblehill
Systems programmer, IT Service, University of Durham, England

[authorization] fails silently for normal users, cannot start server

[Eray 'exa' Ozkural]

Package: xserver-xfree86
Version: 4.0.1-9
Severity: important

When I try to start X server as a user, the X server complains that
the authorization has failed and terminates. Likewise when
trying to login from gdm (tried other display managers, too)

I can't paste anything now but as far as I can summarize:

from auth.log, a message like

PAM_unix[...]: authentication failure; (uid=0) -> exa for gdm service

exa is a normal user here, and gdm is the standard gdm. exa's uid is 1000

That's when I try to login from gdm. When I try to login from console
the error is more silent.

PAM_unix[..]: (login) session opened for user exa by LOGIN(uid=0)

what is going on here? :((( none of our users can login to X for the past 6
weeks!!!

help please.

Thanks,

-- System Information
Debian Release: woody
Architecture: i386
Kernel: Linux borg 2.2.14 #1 Wed Mar 29 19:43:52 EEST 2000 i686

Versions of packages xserver-xfree86 depends on:
ii  debconf   0.5.34 Debian configuration management sy
ii  libc6 2.2-6  GNU C Library: Shared libraries an
ii  xserver-common4.0.1-11   files and utilities common to all 
ii  zlib1g1:1.1.3-11 compression library - runtime 

Re: What is wrong with kde2.1 and unstable ?

[Colin Watson]

[EMAIL PROTECTED] wrote:
>as of three days ago, every attempt to do a dist-upgrade tries to uninstall 
>almost every kde package. What is wrong there.

Use dselect or some apt frontend to find out what the conflicts are or
what dependencies are missing. It's easier for you to do this work
yourself than for debian-devel subscribers to try to work it out at a
distance.

-- 
Colin Watson [EMAIL PROTECTED]

Re: tar -I incompatibility

[Michael Stone]

On Sat, Jan 06, 2001 at 07:42:30AM -0500, Scott Ellis wrote:
> Of course the -I option to tar was completely non-standard.  The changelog
> explains why it changed, to be consistant with Solaris tar.  I'd prefer
> portability and consistancy any day, it shouldn't take that long to change
> any custom scripts you have.  I always use long options for nonstandard
> commands when building scripts anyway :)

I think it would be best for *our* tar to move bzip to -j and *not have
a -I at all*. 

-- 
Mike Stone

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Branden Robinson]

reassign 81397 gdm
thanks

On Sat, Jan 06, 2001 at 05:20:42PM +0200, Eray 'exa' Ozkural wrote:
> Package: xserver-xfree86
> Version: 4.0.1-9
> Severity: important
> 
> When I try to start X server as a user, the X server complains that
> the authorization has failed and terminates. Likewise when
> trying to login from gdm (tried other display managers, too)
> 
> I can't paste anything now but as far as I can summarize:
> 
> from auth.log, a message like
> 
> PAM_unix[...]: authentication failure; (uid=0) -> exa for gdm service

As you've demonstrated so amply on the Debian mailing lists, you are an
idiot.

Whether gdm can get auth credentials back from PAM involves the X server
not at all.

This bug may not be gdm's fault either, but it's a far better approximation
than bitching about xserver-xfree86.

> help please.

No one in Debian can give you the help you need.  You need powerful
antipsychotic drugs.

Don't even think about replying privately.

-- 
G. Branden Robinson |I am sorry, but what you have mistaken
Debian GNU/Linux|for malicious intent is nothing more
[EMAIL PROTECTED]  |than sheer incompetence!
http://www.debian.org/~branden/ |-- J. L. Rizzo II


pgpmhuoG4A6Op.pgp
Description: PGP signature

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 10:36:33AM -0500, Branden Robinson wrote:
> reassign 81397 gdm
> thanks
> 

hi branden,

if you read the bug report carefully, you'll see that
I complain about not being able to login from *anywhere*
including gdm. 

I'm working on it now, and it seems I can't start X
as a normal user from console. And also I can't start it
from neither xdm, wings or gdm

Additional info: with the default xdm (apt-get install xdm)
I read in the xdm log something like
sessreg: not found

where is this sessreg binary supposed to be found? [xutils which
doesn't exist??? :(]

 Please Read *

Anyway, here is what I get:

[EMAIL PROTECTED]:~$ startx

X: user not authorized to run the X server, aborting.
xinit:  unexpected signal 2

[EMAIL PROTECTED]:~$

Is this normal? Users could start their X servers before
upgrading a couple of weeks ago so I presume the upgrade
corrupts something in the way. How do I fix this?

please reopen the bug

thanks,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

ITP: lib-bsf-java

[Ola Lundqvist]

Package: wnpp
Severity: whishlist

It seems like this package have not been packaged yet. Even if quite a lot
of packages needs it.

Url: http://oss.software.ibm.com/developerworks/opensource/bsf/
License: IBM Public License (is that an ok license?), url:
http://oss.software.ibm.com/developerworks/opensource/license10.html

// Ola

I'm not a member of debian-legal so please keep it on debian-devel, or
cc me, thanks.

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Björnkärrsgatan 5 A.11   \
|  [EMAIL PROTECTED] 584 36 LINKÖPING |
|  +46 (0)13-17 69 83  +46 (0)70-332 1551   |
|  http://www.opal.dhs.org UIN/icq: 4912500 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Re: ITP: lib-bsf-java

[Henning Makholm]

Scripsit Ola Lundqvist <[EMAIL PROTECTED]>

> Package: wnpp
> Severity: whishlist

ATTENTION! The original message was cc:ed to [EMAIL PROTECTED]
in addition to two Debial mailing lists. Subscribers to these lists
risk inadvertantly opening new unrelated bug numbers if they use a
standard "wide reply" feature to follow up.

Everyone please trim [EMAIL PROTECTED] from the To: and Cc:
fields when you reply.

The correct way to do this is to instruct the Bug Tracking System to
send copies to the lists when it has assigned a bug number to the
original message. This can be done using a pseudo-header; the BTS
documentation gives the details (sorry, but I'm away from my web
browser right now, so can't check).

> License: IBM Public License (is that an ok license?)

Yes, unless they changed it recently.

-- 
Henning Makholm   "No one seems to know what
   distinguishes a bell from a whistle."

Re: tar -I incompatibility

[Miles Bader]

Goswin Brederlow <[EMAIL PROTECTED]> writes:
> PS: Why not change the Solaris version to be compatible with the
> widely used linux version? I'm sure there are more people and tools
> out there for linux using -I then there are for solaris.

One point the maintainer has made on the gnu mailing lists in response
to complaints about this change is that there has actually been no
*released* version of gnu tar that uses -I for bzip (I don't know
whether it's true or not).

-Miles
-- 
Love is a snowmobile racing across the tundra.  Suddenly it flips over,
pinning you underneath.  At night the ice weasels come.  --Nietzsche

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Samuel Hocevar]

On Sat, Jan 06, 2001, Eray Ozkural wrote:

> Anyway, here is what I get:
> 
> [EMAIL PROTECTED]:~$ startx
> 
> X: user not authorized to run the X server, aborting.
> xinit:  unexpected signal 2
> 
> [EMAIL PROTECTED]:~$
> 
> Is this normal? Users could start their X servers before
> upgrading a couple of weeks ago so I presume the upgrade
> corrupts something in the way. How do I fix this?

   You might be interested in RTFMing, or checking past bugs, or having
a look at /etc/X11/Xwrapper.config.

Best regards,
Sam.
-- 
Samuel Hocevar <[EMAIL PROTECTED]> 
for DVDs in Linux screw the MPAA and ; do dig $DVDs.z.zoy.org ; done | \
  perl -ne 's/\.//g; print pack("H224",$1) if(/^x([^z]*)/)' | gunzip

Re: tar -I incompatibility

[Michael Stone]

On Sun, Jan 07, 2001 at 01:17:40AM +0900, Miles Bader wrote:
> One point the maintainer has made on the gnu mailing lists in response
> to complaints about this change is that there has actually been no
> *released* version of gnu tar that uses -I for bzip (I don't know
> whether it's true or not).

Who cares? It adds no new functionality and is obviously breaking
things.

-- 
Mike Stone

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 05:18:56PM +0100, Samuel Hocevar wrote:

>You might be interested in RTFMing, or checking past bugs, or having
> a look at /etc/X11/Xwrapper.config.
> 

I did RTFM mf. Got any idea why this is happening? The problem is that
we just upgraded, didn't alter anything and ended up with a broken
xinit. How can this be possible?

Regards,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

Re: LILO 21.6-2

[Russell Coker]

On Saturday 06 January 2001 15:08, Joey Hess wrote:
> Russell Coker wrote:
> > I have just uploaded LILO 21.6-2 to Woody.  I have made it use debconf
> > for all the common settings (I can configure lilo.conf for all my
> > machines using only debconf).  Please test it and let me know of any
> > other settings that should be added for debconf.
> >
> > Also I am concerned about the risk of breaking things.  Please let me
> > know how it works.
>
> Well I rather agree with the bug reports that state it should not
> overwrite existing working configurations.
>
> Also, it broke my configuration by pointing to these images:
>
> image=/vmlinuz
> label=Linux
> image=/vmlinuz.old
> label=old
>
> That doesn't work, I have kernel-package configured to put them in
> /boot.

I have a new version online at http://www.coker.com.au/lilo/ .  It adds 
/boot/vmlinuz-* automatically and doesn't look for anything in the root 
directory.  Please try it out and let me know what you think.

Also currently if you don't have debconf configured to display "high" 
priority messages then the configure phase of installation won't run.  The 
problem line is:
db_text high lilo/createdit

I believe that this line should be critical priority anyway so this problem 
should go away.  But what do I do when I want to display text at a 
non-critical level?  Is this a bug in debconf or am I misusing it?

-- 
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/   Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page

Re: tar -I incompatibility

[Neal H Walfield]

On Sat, Jan 06, 2001 at 11:20:58AM -0500, Michael Stone wrote:
> On Sun, Jan 07, 2001 at 01:17:40AM +0900, Miles Bader wrote:
> > One point the maintainer has made on the gnu mailing lists in response
> > to complaints about this change is that there has actually been no
> > *released* version of gnu tar that uses -I for bzip (I don't know
> > whether it's true or not).
> 
> Who cares? It adds no new functionality and is obviously breaking
> things.

I think that your argument is equivalent to someone complaining that
unstable is broken.  Of course it is, nothing has been finalized and it
is, by definition, unstable.  If you want stability, use the released
version, not unstable or code in CVS, otherwise, realize that our first
instincts are not always correct.

-Neal


pgpBDzmuz0Ht3.pgp
Description: PGP signature

Re: ITP: lib-bsf-java

[Ola Lundqvist]

On Sat, Jan 06, 2001 at 05:17:33PM +0100, Henning Makholm wrote:
> Scripsit Ola Lundqvist <[EMAIL PROTECTED]>
> 
> > Package: wnpp
> > Severity: whishlist
> 
> ATTENTION! The original message was cc:ed to [EMAIL PROTECTED]
> in addition to two Debial mailing lists. Subscribers to these lists
> risk inadvertantly opening new unrelated bug numbers if they use a
> standard "wide reply" feature to follow up.

Oops. I did not know that.

> Everyone please trim [EMAIL PROTECTED] from the To: and Cc:
> fields when you reply.

There will probably not be anymore because you have answered all my
quiestions, thanks.

> The correct way to do this is to instruct the Bug Tracking System to
> send copies to the lists when it has assigned a bug number to the
> original message. This can be done using a pseudo-header; the BTS
> documentation gives the details (sorry, but I'm away from my web
> browser right now, so can't check).

Ok thanks, I'll check myself next time.

> > License: IBM Public License (is that an ok license?)
> 
> Yes, unless they changed it recently.

Good, then where will soon be a fresh new package. :)

// Ola

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Björnkärrsgatan 5 A.11   \
|  [EMAIL PROTECTED] 584 36 LINKÖPING |
|  +46 (0)13-17 69 83  +46 (0)70-332 1551   |
|  http://www.opal.dhs.org UIN/icq: 4912500 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Re: LILO 21.6-2

[Russell Coker]

On Saturday 06 January 2001 16:22, Chris Rutter wrote:
> On Sat, 6 Jan 2001, Russell Coker wrote:
> > You don't have sym-links to the root directory?  Why not?
>
> There's absolutely no need or necessarily a desire to do so; besides
> which, the point is moot: if you're in the automation arena, you'll
> notice that kernel-package no longer produces them.

OK, done that.

> Trying to create a GUI interface to something with the free-formality
> and complexity of lilo.conf, even totally disregarding the idea of
> trying to allow interoperation between a human editor and your
> configurator, is /seriously hard/ to achieve plausibly.

Generating files that satisfy 99% of all users is quite achievable.  Having 
an option to allow the other 1% to edit the files by hand should satisfy 
everyone.

>   * human prefers editing all files by hand, beautifully laid out in every
> typographical sense;
>
>   * your configurator generates a perfectly adequate file, and human has
> no desire nor understanding to ever modify it in any way;
>
>   * your configurator is not advanced enough to cater for the user's needs;
> not even close;
>
>   * your configurator generates a file that's /almost perfect/, but just
> needs one or two tiny tweaks (like adding `lba32', say) -- human wants
> to use your program to do the hard work but preserve the tweaks.
>
> You could perhaps model this by offering a few options during the postinst:
>
>   1) ignore lilo.conf and never touch it again, leaving it all to the human;
>
>   2) generate a template file in /etc/lilo.conf.template, and then switch
> back to mode (1);
>
>   3) generate the master file, /etc/lilo.conf.

1 is done.

2 will be done as soon as I figure out how.

What exactly do you mean by 3?

> the other slightly easier and simpler examples of this sort of thing,
> and for the time being, it might be better avoided, or at least /not/
> shoved in people's faces as it now is: never the best way to endear
> people to your work [viz. M$].

The comparison with MS is unfair.  MS don't do public betas and what they 
deign to give you is what you have to use.  Software in unstable is a public 
beta.  Which features of the public beta go into production is dependant on 
input from users.  I've been discussing these issues with more than 20 people 
and my latest package solves almost all the issues that have been discussed 
(the next one will solve all of them).

-- 
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/   Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Samuel Hocevar]

On Sat, Jan 06, 2001, Eray Ozkural wrote:
 
> I did RTFM mf. Got any idea why this is happening? The problem is that
> we just upgraded, didn't alter anything and ended up with a broken
> xinit. How can this be possible?

   Dunno. Shit may happen, you know. But I don't think it's worth Cc:ing
debian-devel and debian-x every time a configuration file changes in
unstable.

Sam.
-- 
Samuel Hocevar <[EMAIL PROTECTED]> 
for DVDs in Linux screw the MPAA and ; do dig $DVDs.z.zoy.org ; done | \
  perl -ne 's/\.//g; print pack("H224",$1) if(/^x([^z]*)/)' | gunzip

Re: Upcoming Events in Germany

[Christian Kurz]

On 01-01-06 Goswin Brederlow wrote:
> > " " == Martin Schulze <[EMAIL PROTECTED]> writes:
>  > July 5-8 LinuxTag 2001, Stuttgart http://www.linuxtag.org/
>  > http://www.infodrom.ffis.de/Debian/events/LinuxTag2001/

> Already planed to be there.

I will be there any way, but I have to work out some other things
before.

Ciao
 Christian
-- 
  Debian Developer and Quality Assurance Team Member
1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853


pgpQ1JrRxlart.pgp
Description: PGP signature

Re: lilo.conf

[Christian Kurz]

On 01-01-06 Matt Zimmerman wrote:
> On Sat, Jan 06, 2001 at 01:58:48PM +0100, Cosimo Alfarano wrote:
> > On Sat, Jan 06, 2001 at 01:33:57PM +0100, Peter Makholm wrote:
> > > Don't assume devfs! A lot of us uses it, but before our standard
> > > kernel uses it our lilo package shouldn't assume it unless it is very
> > > sure that it will work.
> > 
> > He shouldn't assume it even if debian standard kernel package uses it.
> > A lot of users don't use them (both std kernel and devfs).

> Especially since devfs support is still considered experimental.

Hm, it's not marked as experimental in kernel 2.4.0, but as work in
progress. So support for it would be really good.

Ciao
 Christian
-- 
  Debian Developer and Quality Assurance Team Member
1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853


pgpE1qLPfiAvx.pgp
Description: PGP signature

Re: tar -I incompatibility

[Michael Stone]

On Sat, Jan 06, 2001 at 11:43:10AM -0500, Neal H Walfield wrote:
> I think that your argument is equivalent to someone complaining that
> unstable is broken.  Of course it is, nothing has been finalized and it
> is, by definition, unstable.  If you want stability, use the released
> version, not unstable or code in CVS, otherwise, realize that our first
> instincts are not always correct.

NO. NO. NO. I've already heard it and I won't accept it. The so-called
stable version of tar has *serious known bugs*. If upstream will not
accept the responsibility of periodically updating tar with bug fixes,
they must assume that people will follow the so-called unstable
versions. 

Maybe, just maybe, upstream's instincts are wrong on the matter of -I
also. Maybe, just maybe, if we hadn't followed upstream into using -I
rather than -y we wouldn't be having a problem. Maybe we should just
yank out -I and wait for upstream to catch up. 

Is there any guarantee that if we switch to -j it won't change again?

-- 
Mike Stone

Re: lilo.conf

[Matt Zimmerman]

On Sat, Jan 06, 2001 at 05:40:53PM +0100, Christian Kurz wrote:

> On 01-01-06 Matt Zimmerman wrote:
> > On Sat, Jan 06, 2001 at 01:58:48PM +0100, Cosimo Alfarano wrote:
> > > On Sat, Jan 06, 2001 at 01:33:57PM +0100, Peter Makholm wrote:
> > > > Don't assume devfs! A lot of us uses it, but before our standard
> > > > kernel uses it our lilo package shouldn't assume it unless it is very
> > > > sure that it will work.
> > > 
> > > He shouldn't assume it even if debian standard kernel package uses it.
> > > A lot of users don't use them (both std kernel and devfs).
> 
> > Especially since devfs support is still considered experimental.
> 
> Hm, it's not marked as experimental in kernel 2.4.0, but as work in
> progress. So support for it would be really good.

mizar:[~/src/linux/2.4.0/linux] egrep 'VERSION|LEVEL' Makefile  | head -3
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 0
mizar:[~/src/linux/2.4.0/linux] grep -B 1 ^CONFIG_DEVFS_FS 
Documentation/Configure.help
/dev file system support (EXPERIMENTAL)
CONFIG_DEVFS_FS
mizar:[~/src/linux/2.4.0/linux] grep ' CONFIG_DEVFS_FS ' fs/Config.in
dep_bool '/dev file system support (EXPERIMENTAL)' CONFIG_DEVFS_FS 
$CONFIG_EXPERIMENTAL

It will only show up if CONFIG_EXPERIMENTAL is defined.

-- 
 - mdz


pgpXTlv2p4GM6.pgp
Description: PGP signature

Re: tar -I incompatibility

[Michael Stone]

Since solaris compat is now a release goal for tar, should we also
expect dramatic changes in the behavior of the following options?
(Some of these are actually supported on more platforms than just
solaris; gtar is the only oddball.)
F
i
k
l
o
P

-- 
Mike Stone

useradd problem(!)

[Sven Burgener]

Hello

When I first installed Debian GNU/Linux on this machine, I reconfigured
it so that there is a "central" user-group called "users" which all
users of this system belong to.

I have now reconfigured it back to the default:

/etc/adduser.conf
[...]
USERGROUPS=yes
[...]


When running useradd, though, I get the following:

# useradd -m test
# ls -l /home
[...]
drwxr-sr-x   18 svn  users1024 Jan  4 23:28 svn
drwxr-xr-x2 test users1024 Jan  4 23:30 test

There. The new user 'test' still belongs to 'users' and doesn't get a
new group called 'test'.

I was curious, so I ran strace over adduser:

[first deleted 'test' again]

# strace useradd -m test
[...]
open("/etc/default/useradd", O_RDONLY)  = -1 ENOENT (No such file or directory)
[...]
access("/home/test", F_OK)  = -1 ENOENT (No such file or directory)
mkdir("/home/test", 0)  = 0
[...]
chown("/home/test", 1001, 100)  = 0  <-- why GID 100?
[...]

(sorry for the long lines)

First, why is useradd looking for a file at /etc/default/useradd? Is
this an old location or what? I have only the following there:

total 8
-rw-r--r--1 root root   92 Aug 18 23:32 devpts
-rwxr--r--1 root root  641 Aug 18 23:33 rcS

Second, and this is my main problem, why is the GID 100? I have
explicitly configured "USERGROUPS=yes" in /etc/adduser.conf!

I run an up-to-date woody/testing here.

Help greatly appreciated,
Sven
-- 
Powered by Debian GNU/Linux

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

This is my answer to a private mail (it seems...) I don't want to talk
about these in private. Please note the reason why I carried this bug
report to the list.

On Sat, Jan 06, 2001 at 02:59:31PM -0200, Henrique de Moraes Holschuh wrote:
> You've already gotten into Branden's permanent shitlist. Please be more
> reserved on ANYTHING you do that might even remotely involve his packages,
> ok? We don't need him going psycothic again.
> 

What is this supposed to mean? There are many users here suffering from this
problem since this is a multi-user system and none of them have the time
to learn the peculiarities of x. They, and I, just want to use this stuff
and I moved the system to unstable because it seemed we needed some of
the bug fixes...

BTW, the users here are not at all interested in the psychological state
of a particular developer. On the contrary, every developer should be required
to deal with every bug report in an objective manner. [*] Which I think is the
way Branden did it, due to the big number of bug reports he must have skimmed
quickly and reassigned it to gdm. I'm sure that he will check the upgrade
path after the additional information I gave. [+]

> Now, back to your problem. Please verify if /etc/X11/Xwrapper.config lists
> allowed_users=something.  You want to make that 'something' "console" or
> "any" I think.

Okay, i'll check that. Hadn't found that myself. Thanks. I'm downgrading X
now, but I might need this information.

> This was discussed in d-user, d-devel and numerous bug reports to the point
> that Branden would go "Overfiend" on *anyone* asking it again.
> 

I've never seen this mentioned, nor is it written down anywhere and I don't
think that mailing search stuff really works... And I wouldn't think I'd be
able to find it with this much info (i can't start x as a user). Point
me to an FAQ, and I will understand it then. I thought this might be some
common case and fiddled with some "security" options but wasn't able to resolve
the problem which led me to ask it here, because I didn't find an FAQ. "Deal 
with it,
or quit." isn't the kind of answer I expect about a display system that we use
daily.

Regards,

[*] Inappropriate dismissal or incorrect evaluation of bug reports could
be dealt with if bug reports were subject to peer review. That's why I
posted here. I'm not blaming Branden, nor do I say that this is a very
important bug. However, it is generating a lot of dissatisfaction with
the system here, and I have to solve it. I thought that review by
wider audience would be instrumental in that.

[+] Not because I'm especially fond of the developer in question. It is
not a matter of personal liking.

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

Re: What do you wish for in an package manager? Here you are!

[Thorsten Wilmer]

Hello
Petr Èech wrote:
>Adam Lazur wrote:
>> The ability to install more than one version of a package simultaneously.
>
>Hmm. SO you install bash 2.04-1 and bash 2.02-3. Now what will be /bin/bash
>2.04 or 2.02 version? You will divert both of them and symlink it to the old
>name - maybe, but but how will you know, to what name it diverts to use it?
>
>Give me please 3 sane examples, why you need this. And no, shared libraries
>are NOT an excuse for this.


I or my University needs such a functionallity:

We use already such a system under Solaris which you can find on
www.modules.org

This works quite well for us with Solrais, but we have to recompile each
Package, we want to install...

As Debian has already a large Number of Packages it would be impracticle
for us to do all the work again... So why not let the Package Mangement
do it...

O.K. Here are a few examples, why we need such system...
Our Software is installed on decentarlized fileserveres for many Useres
whith different tasks and projects.

The Sys-Admin can not be able to check if an old version is still needed
or if someone dislikes the new Version, here are some User-Space
Programms, which will or would have produced Problems due to a lag of
compatibility with older Versions
You cannot use some Version of Documents created with lyx 1.3 in 1.5 as
the file Format has changed at some Places, while the unknown users
which have to use such a Programm are not able to fix their Problems on
their own. Or they have not enough time to port their Files to new
Version, so if the Sysadmin would have killed the older Version and
replaced with the new one some projects would have had more work than
switching to the new Version

Think of some gcc versions... you used a trick to get Your programm
work, and then some Specifications changed and your Programm will not
compile any more...
This could be your Diplomatheses which could be in Danger!


Or Gimp us not able any longer to read gifs, but some users don't know
any other program, but want to use gif, so they can use the older
version...

Or the User-Interface has been changed and the User is not willed or has
not the time to learn the User-Interface of the new Version

Some users might want to live on the bleading edge and others want to
have their version forever, and others want stable well tested Versions
of programms...


And the users like our Module-system and they miss it on Debian...



I hope this are enogh Arguments for a Modulesystem  (whith different
Versions installed)



The current module System has one big disadvantage, it uses the PATH
environment for version switching, and as the space in the enviroment is
very limited we use env-Modules Modules which kontain many other
Programs.
If we would like to konvert Debian Packages to Modules we only could
load about 14 Modules and then our Path becomes too long. So we would
still have to rebuild env-Packages...


A new Idea from me is, let the Module System create Symlinks under the
Users Home directory to Programms and Libaries Docs he wants to execute
or to see, then the Path and LD_Path  is very short...

A typical link would look like this

/home/use/.Modules/usr/bin/emacs ->
/app/modul-system/arch/emacs/20.1/usr/bin/emacs

 ^
Here would the standard Debian Package be 
extracted

The Addition of a Module would mean:
Check for Package Dependencies and install/remove them first... (Ask the
User, to do this!)
Link all Files of the Package to the User's Homedircetory

The Removement of a Module would mean:
Check Module Dependencies, aks if some other Modules should also be
removed...
Look at the ModuleDirectory and unlink all files from the User's
Homedirectory...


This Method has three disatvanages...
1) It need Symlinks which could be expensive on Systems with 1000 Users
and 1000 Programmms (Files)
2) It only works on a per User Base and not on a per Shell Base (which
is sometimes confusing the Users)
3) Not Standard Conformant

But some big Advantages
1) No need For reloading all the Modules again and again
2) No need for Recompilation or Modification of Debian-Packages...
3) Should work right out of the Box


What do you think?


Yours 
 Thorsten Wilmer

Re: useradd problem(!)

[Malcolm Parsons]

On Thu, Jan 04, 2001 at 11:52:54PM +0100, Sven Burgener wrote:
> /etc/adduser.conf
... 
> When running useradd, though, I get the following:

useradd and adduser are two different programs from two different pacakges,
the configuration of one does not affect the other:

[EMAIL PROTECTED]:~$ dpkg -S /usr/sbin/useradd
passwd: /usr/sbin/useradd
[EMAIL PROTECTED]:~$ dpkg -S /usr/sbin/adduser   
adduser: /usr/sbin/adduser

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Steve Langasek]

On Sat, 6 Jan 2001, Eray Ozkural wrote:

> On Sat, Jan 06, 2001 at 05:18:56PM +0100, Samuel Hocevar wrote:
> 
> >You might be interested in RTFMing, or checking past bugs, or having
> > a look at /etc/X11/Xwrapper.config.

> I did RTFM mf.

Clearly not, or you would know that XFree4 requires explicit configuration to
allow non-root users to run the X server.  This is most definitely a FEATURE,
added to improve security, /not/ a bug.

Being ignorant of this is excusable; Debian developers are not expected to
know everything about everything that's in unstable.  Whining to debian-devel
because installing unstable broke things for your users, and Cc:ing
debian-devel on all of your bug reports, is NOT excusable.  I don't know why
you think your personal bug reports are so important that they demand the
attention of not only the package maintainer, but *also* everyone subscribed
to d-d, but please stop.

> Got any idea why this is happening? The problem is that
> we just upgraded, didn't alter anything and ended up with a broken
> xinit. How can this be possible?

Despite the inappropriate manner in which this is being reported (and despite 
having nothing to do with the bug that was actually filed), it's true that we
won't want people upgrading from potato to woody to be caught unawares by this
new feature.  Branden, perhaps the XFree4 server package should check if the
previously-installed version was a 3.3 server, and offer to set up the
Xwrapper.config file appropriately?

Regards,
Steve Langasek
postmodern programmer

Re: What to do about /etc/debian_version

[Steve Langasek]

On Sat, 6 Jan 2001, Marco d'Itri wrote:

> On Jan 06, Joey Hess <[EMAIL PROTECTED]> wrote:

>  >[EMAIL PROTECTED]:/tmp>mount -o loop foo 1
> Why don't we just patch mount to use /var/run/mtab?
> I don't know about any other program which modifies it.

If we use /var/run/mtab, how does mount update it when our /var partition
hasn't been mounted yet?  We want accurate information about the root fs to be
there, too.

Steve Langasek
postmodern programmer

Re: [devfs users]: evaluate a patch please

[Goswin Brederlow]

> " " == Martin Bialasinski <[EMAIL PROTECTED]> writes:

 > Hi, there is a bug in the mc package, that most likely is
 > related to devfs. I can't reproduce it, nor does it seem to be
 > common.

 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=57557&repeatmerged=yes

 > mc hangs occasionally on starup on the VC.

Oh, thats the reason why it hangs. I wondered about that.

 > There is a patch on the buttom of the report.

 > Could you tell me, if it is formally OK and if it fixes the
 > problem for you, if you can reproduce the bug?

Gotta test that.

I will be back.
Goswin

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Matt Zimmerman]

On Sat, Jan 06, 2001 at 07:29:35PM +0200, Eray Ozkural wrote:

> What is this supposed to mean? There are many users here suffering from this
> problem since this is a multi-user system and none of them have the time
> to learn the peculiarities of x. They, and I, just want to use this stuff
> and I moved the system to unstable because it seemed we needed some of
> the bug fixes...

Bugfixes are not a good reason to upgrade to unstable.  You are likely to
introduce more bugs than you fix.  Instead, try:

1. Isolate the bugs that are causing your problems

  THEN

2a. Install (or recompile) the specific packages from unstable that fix the
bugs
  OR
2b. Backport the fixes

-- 
 - mdz

Re: LILO 21.6-2

[Manoj Srivastava]

>>"Brian" == Brian May <[EMAIL PROTECTED]> writes:

> "Adam" == Adam Heath <[EMAIL PROTECTED]> writes:
 Adam> On Sat, 6 Jan 2001, Russell Coker wrote:
 >>> You don't have sym-links to the root directory?  Why not?
 >>> 

 Adam> kernel-package doesn't do them anymore.

This is not quite correct. The kernel-image postinst can
 optionally *not* do the symlinks -- however, it does do the symlink
 changes as a default, unless asked not to.

 Brian> What is the current practise? Have lilo specifically use the kernel
 Brian> version number (eg. /boot/vmlinuz-2.2.18 instead of using /vmlinuz or
 Brian> /vmlinuz.old)?

*My* current practice is to allow kernel package to manage
 /vmlinuz and /vmlinuz.old, and manage /vmlinuz.stable,
 /vmlinuz.unstable manually, and have /boot/linux.bin and
 /boot/root.bin as rescue kernels

manoj
-- 
 We should often be ashamed of our very best actions, if the world
 only saw the motives which caused them.  -- La Rochefoucauld
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: What do you wish for in an package manager? Here you are!

[Goswin Brederlow]

> " " == Thorsten Wilmer <[EMAIL PROTECTED]> writes:

 > Hello Petr Èech wrote:
>> Adam Lazur wrote:
>>> The ability to install more than one version of a package
>>> simultaneously.
>>  Hmm. SO you install bash 2.04-1 and bash 2.02-3. Now what will
>> be /bin/bash 2.04 or 2.02 version? You will divert both of them
>> and symlink it to the old name - maybe, but but how will you
>> know, to what name it diverts to use it?
>> 
>> Give me please 3 sane examples, why you need this. And no,
>> shared libraries are NOT an excuse for this.

The only useable way is to have /bin/bash allways point to a stable
version.

Apart from that, anyone who cares what version to use must use the
full path to the binary or a versioned name, like /bin/bash-2.04-1.

I would like binaries to be compiled to reside in versioned
directories but I also see a lot of problems with it as
well. Especially with the /etc /usr /usr/share and so on. Every
directory would have to have a subdir for every package that has files
there. What a chaos.

Of cause in spezial cases you can install all packages to
/usr/share/software/package-version/ and symlinc, but thats not a
general solution to the problem. For stuff like /bin/sh a network
filesystem doesn't work.

MfG
Goswin

Re: LILO 21.6-2

[Manoj Srivastava]

>>"Russell" == Russell Coker <[EMAIL PROTECTED]> writes:

 Russell> On Saturday 06 January 2001 16:22, Chris Rutter wrote:
 >> On Sat, 6 Jan 2001, Russell Coker wrote:
 >> > You don't have sym-links to the root directory?  Why not?
 >> 
 >> There's absolutely no need or necessarily a desire to do so; besides
 >> which, the point is moot: if you're in the automation arena, you'll
 >> notice that kernel-package no longer produces them.

 Russell> OK, done that.

May I point out again that kernel package does indeed still
 create the /vmlinuz links? Why can't people look?

 >> Trying to create a GUI interface to something with the free-formality
 >> and complexity of lilo.conf, even totally disregarding the idea of
 >> trying to allow interoperation between a human editor and your
 >> configurator, is /seriously hard/ to achieve plausibly.

 Russell> Generating files that satisfy 99% of all users is quite
 Russell> achievable.  Having an option to allow the other 1% to edit
 Russell> the files by hand should satisfy everyone.

If you were merely generating files where none existed, that
 would be fine. Destroying a hand cra\fted lilo.conf is unacceptable.

manoj
-- 
 After winning the pennant one year, Casey Stengel commented, "I
 couldn'ta done it without my players."
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Henrique M Holschuh]

> This is my answer to a private mail (it seems...) I don't want to talk
> about these in private. Please note the reason why I carried this bug
> report to the list.

Well, sorry but now you're in MY non-permanent (YET) shitlist for violating
netiquette, and I'll have to acknowledge that Branden Was Right (tm) about
you.

Hint: next time, ASK FOR PERMISSION FIRST before you do a public posting of
private email. Geez. You'd have gotten it, but it is a matter of principle
to ask first.

> On Sat, Jan 06, 2001 at 02:59:31PM -0200, Henrique de Moraes Holschuh wrote:
> > You've already gotten into Branden's permanent shitlist. Please be more
> > reserved on ANYTHING you do that might even remotely involve his packages,
> > ok? We don't need him going psycothic again.

Branden, please understand this for what it is meant: "Branden does not like
to be poked. He seems to like even less to be poked by you. Please don't
poke him, he'll bite back and we get to watch the fallout."

> What is this supposed to mean? There are many users here suffering from this
> problem since this is a multi-user system and none of them have the time
> to learn the peculiarities of x. They, and I, just want to use this stuff
> and I moved the system to unstable because it seemed we needed some of
> the bug fixes...

It means your X *may* be configured not to allow anyone but root to execute
the wrapper. Check the damn Xwrapper.config file. I even said that over
private mail to be nicer and not bother this list with yet another redudant
reply...

The Xrapper.config issue has been documented in a number of bug reports
(search the BTS), and probably many -user and -devel posts (search the list
archives, mind the sometimes quirky search engine).

> of a particular developer. On the contrary, every developer should be required
> to deal with every bug report in an objective manner. [*] Which I think is the

Most developers (if not all of them) deal with bug reports in an objective
manner, or don't deal with them at all (because they're MIA or are very
short on time).

> Okay, i'll check that. Hadn't found that myself. Thanks. I'm downgrading X
> now, but I might need this information.

FYI I'm running up-to-date sid X packages here, and they seem to work just
fine.

> > This was discussed in d-user, d-devel and numerous bug reports to the point
> > that Branden would go "Overfiend" on *anyone* asking it again.
> 
> I've never seen this mentioned, nor is it written down anywhere and I don't
> think that mailing search stuff really works... And I wouldn't think I'd be

That mailing search stuff has some weird problems, yes. As for not being
written down anywhere, the postinst asks you about it. I think there is a
manpage for Xwrappers.config, but it's not installed in my system.

> able to find it with this much info (i can't start x as a user). Point
> me to an FAQ, and I will understand it then. I thought this might be some

Hmm... why didn't you look at what X asks during configure phase, as well as
the files in /etc/X11?  That's usually a very good first check before
posting a question.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


pgpiFdiMiBngq.pgp
Description: PGP signature

Re: useradd problem(!)

[Juan Fuentes]

* Sven Burgener ([EMAIL PROTECTED]) wrote:
>Hello
>
>When I first installed Debian GNU/Linux on this machine, I reconfigured
>it so that there is a "central" user-group called "users" which all
>users of this system belong to.
>
>I have now reconfigured it back to the default:
>
>/etc/adduser.conf
>[...]
>USERGROUPS=yes
>[...]
>
>
>When running useradd, though, I get the following:
>
># useradd -m test
># ls -l /home
>[...]
>drwxr-sr-x   18 svn  users1024 Jan  4 23:28 svn
>drwxr-xr-x2 test users1024 Jan  4 23:30 test


>
>There. The new user 'test' still belongs to 'users' and doesn't get a
>new group called 'test'.

Firstwhat version of adduser?? because in my version  of adduser(3.11.1) 
idon't have that -m flag, now looking at the code, i didn't find it and
in the man page i didn't find it either. About the user bit, the thing
is if you have USERGROUPS=yes, and you have USER_GID=100 adduser it
apparently is defaulting to use this value, i don't know why but it 
doesn't make sense the code is very sane, and in my interpretation of it 
this shouldn't happen maybe a bug don't know yet *shrug*, try using the 
--gid flag and see if it's fixed.

>
>I was curious, so I ran strace over adduser:
>
>[first deleted 'test' again]
>
># strace useradd -m test
>[...]
>open("/etc/default/useradd", O_RDONLY)  = -1 ENOENT (No such file or directory)
>[...]
>access("/home/test", F_OK)  = -1 ENOENT (No such file or directory)
>mkdir("/home/test", 0)  = 0
>[...]
>chown("/home/test", 1001, 100)  = 0  <-- why GID 100?
>[...]

See above.

>
>(sorry for the long lines)
>
>First, why is useradd looking for a file at /etc/default/useradd? Is
>this an old location or what? I have only the following there:

I don't know if it's an old location, but it seems it checks to see if
that file exist for some reason *shrug*. I don't see no reference to
this in the code i have.

>
>total 8
>-rw-r--r--1 root root   92 Aug 18 23:32 devpts
>-rwxr--r--1 root root  641 Aug 18 23:33 rcS
>
>Second, and this is my main problem, why is the GID 100? I have
>explicitly configured "USERGROUPS=yes" in /etc/adduser.conf!
>
>I run an up-to-date woody/testing here.

I run up to date woody too, and i don't have this problem if i do
useradd test 

i get the whole bunch of questions and the output of /home/test is:

 drwxr-xr-x2 test test1024 Jan  6 13:30 test

HTH,

Juan Fuentes 

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Manoj Srivastava]

>>"Eray" == Eray Ozkural (exa) <[EMAIL PROTECTED]> writes:

 Eray> This is my answer to a private mail (it seems...) I don't want to talk
 Eray> about these in private. Please note the reason why I carried this bug
 Eray> report to the list.

You have the gall to quote private email on a public list, and
 expect people to accord you any attention whatsoever? Have you ever
 heard of nettiquette? 

*plonk*

manoj
-- 
 "Sudden de-compression Sucks!" Dennis Robert Gorrie,
 [EMAIL PROTECTED]
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: LILO 21.6-2

[Manoj Srivastava]

>>"Russell" == Russell Coker <[EMAIL PROTECTED]> writes:


 Russell> I have a new version online at http://www.coker.com.au/lilo/ .  It 
adds 
 Russell> /boot/vmlinuz-* automatically and doesn't look for anything in the 
root 
 Russell> directory.  Please try it out and let me know what you think.

This is a bug. /boot is not the only location kernel-image
 packages may put image files in. The kernel-image packages go to a
 great deal of  trouble to correctly create /vmlinuz and /vmlinuz.old
 symbolic links (unless asked not to do so). Ignoring them means that
 my lilo.conf file shall need to be constantly updated every time I
 install a new kernel. I consider this a serious degradation of
 functionality.


At the moment, if there is no lilo.conf, the kernel-image
 postinst creates a functioanl lilo.conf that takes into account
 symbolic links, the location of the iomage files (if it is not /boot,
 takes into account reverse symlinks, image in boot. and other
 options, and creates a working lilo.conf that can be added to by the
 user.

It does not ever destroy a working lilo.conf file.

I would expect lilo itself to do at least as good a job as the
 postinst of another package.

manoj
-- 
 baz bat bamus batis bant. James Troup
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 01:16:22PM -0500, Matt Zimmerman wrote:
> 2a. Install (or recompile) the specific packages from unstable that fix the
> bugs

That I should have done...

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

Re: lilo.conf

[Manoj Srivastava]

Hi,
>>"Russell" == Russell Coker <[EMAIL PROTECTED]> writes:


 Russell> other=/dev/ide/host0/bus0/target0/lun0/part1
 Russell> label=part1
 Russell> table=/dev/ide/host0/bus0/target0/lun0/disc

Eh? I have an SCSI only machine which does not do devfs. Does
 the postinst handle that?

manoj

-- 
 If I had done everything I'm credited with, I'd be speaking to you
 from a laboratory jar at Harvard. Frank Sinatra AS USUAL, YOUR
 INFORMATION STINKS. Frank Sinatra, telegram to "Time" magazine
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 12:43:15PM -0600, Manoj Srivastava wrote:
>   You have the gall to quote private email on a public list, and
>  expect people to accord you any attention whatsoever? Have you ever
>  heard of nettiquette? 

There is nothing personal in my reply and neither in quoted text and
I addressed the whole list not particularly the sender. If these aren't
satisfactory, very well.

What happens is that I've got a real-world problem but I am being told of
the complex-es of the maintainer of that package.

Then, the guys who like him come in and tell me things that do not interest
me at all... Are you guys on crack?

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 04:39:43PM -0200, Henrique M Holschuh wrote:
> Branden, please understand this for what it is meant: "Branden does not like
> to be poked. He seems to like even less to be poked by you. Please don't
> poke him, he'll bite back and we get to watch the fallout."
> 

Great kiss ass.

> Most developers (if not all of them) deal with bug reports in an objective
> manner, or don't deal with them at all (because they're MIA or are very
> short on time).
> 

I don't think so.

Re: LILO 21.6-2

[Peter Makholm]

Manoj Srivastava <[EMAIL PROTECTED]> writes:

>   At the moment, if there is no lilo.conf, the kernel-image
>  postinst creates a functioanl lilo.conf that takes into account

Is this wise?

I assume that in a perfect world the lilo package would be better to
configure itself than some "random" other package. The lilo package
would have more knowledge of which special things to consider,
eventually after consulting the user.

Consider this: Kernel-image gets installed and finds no lilo.conf and
makes a minimal but functional lilo.conf. Then lilo gets installed, it
finds a lilo.conf and decides not to touch it (what a nice
package). What the user now doesn't know is that the lilo packages
configuration of lilo.conf would have given him the oputunity to use a
password on lilo or some other fancy feature.

Nobody should touch the configuration files belonging to lilo but the
local sysadmin and the lilo package itself. And the lilo package
should rather  be a little less fancy in it's install than destroying
existing configurations.

ITA gnucash?

[Ola Lundqvist]

Hi

I just want to ask if somebody knows if the maintainer is still
active. Gnucash have now quite a lot of bugs and there is a new
stable version. If he is not active anymore I'll gladly adopt this package.

// Ola

-- 
 - Ola Lundqvist ---
/  [EMAIL PROTECTED] Björnkärrsgatan 5 A.11   \
|  [EMAIL PROTECTED] 584 36 LINKÖPING |
|  +46 (0)13-17 69 83  +46 (0)70-332 1551   |
|  http://www.opal.dhs.org UIN/icq: 4912500 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Re: BIND 9.X, shared libraries, and package pools

[Josip Rodin]

On Sat, Jan 06, 2001 at 11:44:01AM +1100, Brian May wrote:
> Josip> Oh, of course. (Packages including several shared libraries
> Josip> suck as far as our naming scheme is concerned :o)
> 
> Does bind come with multiple libraries? If so, I think they should
> really be split up, according to standard convention. (unless there
> really are too many libraries to split up).
[snip]

Yes. There can be exceptions, though, like packages that contain two
libraries that will always have the same version number in the SONAME and
will not have these problems. OTOH there's hardly ever a reason for those to
exist, but it can happen. For example, when a package contains two binaries
that both need similar features, but one binary gets linked to libfooa.so
and the other one with libfoob.so. Or something like that.

-- 
Digital Electronic Being Intended for Assassination and Nullification

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Josip Rodin]

On Sat, Jan 06, 2001 at 08:56:41PM +0200, Eray Ozkural wrote:
> > You have the gall to quote private email on a public list, and
> >  expect people to accord you any attention whatsoever? Have you ever
> >  heard of nettiquette? 
> 
> There is nothing personal in my reply and neither in quoted text and
~~
Um, there is. The thing that caused you to say "Great kiss ass" to hmh.

> What happens is that I've got a real-world problem but I am being told of
> the complex-es of the maintainer of that package.
> 
> Then, the guys who like him come in and tell me things that do not interest
> me at all... Are you guys on crack?

Oh, of course. It's just you who is not, isn't it obvious? :>

-- 
Digital Electronic Being Intended for Assassination and Nullification

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Henrique M Holschuh]

On Sat, 06 Jan 2001, Eray Ozkural wrote:
> On Sat, Jan 06, 2001 at 04:39:43PM -0200, Henrique M Holschuh wrote:
> > Branden, please understand this for what it is meant: "Branden does not like
> > to be poked. He seems to like even less to be poked by you. Please don't
> > poke him, he'll bite back and we get to watch the fallout."
> > 
> 
> Great kiss ass.

Flamewar taken to private mail. Move along people, there's nothing to see
here (I hope, that is).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


pgpEW4AvZmpdc.pgp
Description: PGP signature

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Branden Robinson]

On Sat, Jan 06, 2001 at 04:39:43PM -0200, Henrique M Holschuh wrote:
> That mailing search stuff has some weird problems, yes. As for not being
> written down anywhere, the postinst asks you about it. I think there is a
> manpage for Xwrappers.config, but it's not installed in my system.

There is.  I forgot to add it to debian/xserver-common.files.  I have now
done so and it will appear in the next release.  Thanks for pointing this
out.

In the meantime, I have MIME-attached it.  To view it, use the following
command:

nroff -man whatever-you-save-it-as | pager

-- 
G. Branden Robinson |Convictions are more dangerous enemies
Debian GNU/Linux|of truth than lies.
[EMAIL PROTECTED]  |-- Friedrich Nietzsche
http://www.debian.org/~branden/ |
.\" This manpage is copyright (C) 2000 Progeny Linux Systems, Inc.
.\" Author: Branden Robinson <[EMAIL PROTECTED]>
.\"
.\" This is free software; you may redistribute it and/or modify
.\" it under the terms of the GNU General Public License as
.\" published by the Free Software Foundation; either version 2,
.\" or (at your option) any later version.
.\"
.\" This is distributed in the hope that it will be useful, but
.\" WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public License
.\" along with the Debian GNU/Linux system; if not, write to the Free
.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
.\" 02111-1307 USA
.TH Xwrapper.config 5 "17 Dec 2000" "Debian GNU/Linux"
.SH NAME
Xwrapper.config \- configuration options for X server wrapper
.SH DESCRIPTION
.I /etc/X11/Xwrapper.config
contains a set of flags that determine some of the behavior of Debian's X
server wrapper, which is installed on the system as
.IR /usr/X11R6/bin/X .
The purpose of the wrapper, and of this configuration file, is twofold:
firstly, to implement sound security practice.  Since the X server requires
superuser privileges, it may be unwise to permit just any user on the
system to execute it.  Even if the X server is not exploitable in the sense
of permitting ordinary users to gain elevated privileges, a poorly-written
or insufficiently-tested hardware driver for the X server may cause bus
lockups and freeze the system, an unpleasant experience for anyone using it
at the time.
.PP
Secondly, a wrapper is a convenient place to set up an execution
environment for the X server distinct from the configurable parameters
of the X server itself.
.PP
.B Xwrapper.config
may be edited by hand, but it is typically configured via debconf, the
Debian configuration tool.  The X server wrapper is part of the
.I xserver-common
Debian package, therefore the parameters of
.B Xwrapper.config
may be changed with the command
.IR "dpkg-reconfigure xserver-common" .
See
.IR dpkg-reconfigure (8)
for more information.
.PP
The format of
.B Xwrapper.config
is a text file containing a series of lines of the form
.TP
.IR name = value
.PP
where
.I name
is a variable name containing any combination of numbers, letters, or
underscore (_) characters, and
.I value
is any combination of letters, numbers, underscores (_), dashes (-).
.I value
may also contain spaces as long as there is at least one character from the
list above bounding the space(s) on both sides.  Whitespace before and
after
.IR name , value ,
or the equals sign is legal but ignored.  Any lines not matching the above
described legal format are ignored.  Note that this specification may
change as the X server wrapper develops.
.PP
Available options are:
.IP allowed_users
may be set to one of the following values:
.BR rootonly , console , anybody .
"rootonly" indicates that only the root user may start the X server;
"console" indicates that root, or any user whose controlling TTY is a
virtual console, may start the X server; and "anybody" indicates that any
user may start the X server.
.IP nice_value
may be any integer in the interval [-20,20].  This is used to set the
executing X server's process priority.  See
.IR nice (1).
.SH SEE ALSO
.IR dpkg-reconfigure (8),
.IR nice (1)
.SH AUTHOR
This manpage was written by Branden Robinson for Progeny Linux Systems,
Inc., and Debian GNU/Linux.


pgp5XjeDeij0w.pgp
Description: PGP signature

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Erik Hollensbe]

(this is not directed specifically at anyone)

I don't quite get this... This list is moderated. Is it not too much for
the moderator to moderate these postings and/or the user instead of
drawing hte hounds just because one guy things a bug should be in a
different spot?

Some logical discussion, or perhaps some without the interspersement of
flames, would be a fresh change.

I have a hard time finding the logic in wasting your time complaing about
how your time is being wasted. What does this solve?

-- 
Erik Hollensbe <[EMAIL PROTECTED]>
Programmer, Powells Internet Division
"I respect a man who lets me know where he stands, even if he is wrong."
- Malcolm X

On Sat, 6 Jan 2001, Josip Rodin wrote:

> On Sat, Jan 06, 2001 at 08:56:41PM +0200, Eray Ozkural wrote:
> > >   You have the gall to quote private email on a public list, and
> > >  expect people to accord you any attention whatsoever? Have you ever
> > >  heard of nettiquette?
> >
> > There is nothing personal in my reply and neither in quoted text and
> ~~
> Um, there is. The thing that caused you to say "Great kiss ass" to hmh.
>
> > What happens is that I've got a real-world problem but I am being told of
> > the complex-es of the maintainer of that package.
> >
> > Then, the guys who like him come in and tell me things that do not interest
> > me at all... Are you guys on crack?
>
> Oh, of course. It's just you who is not, isn't it obvious? :>
>
>

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Branden Robinson]

On Sat, Jan 06, 2001 at 12:01:42PM -0600, Steve Langasek wrote:
> Branden, perhaps the XFree4 server package should check if the
> previously-installed version was a 3.3 server, and offer to set up the
> Xwrapper.config file appropriately?

I considered this, but judged that the cost of writing a parser for the old
format that would be used only once -- when people would be quizzed by
debconf anyway -- exceeded the benefit.

If someone want to write some code that will parse the old /etc/X11/Xserver
file and load up the debconf database with values from it, and submit a
patch to xserver-common.config as a wishlist bug, please feel free.  I'll
give it serious consideration (especially if it's well written, matches my
shell scripting style, and has been tested).

-- 
G. Branden Robinson |   I just wanted to see what it looked like
Debian GNU/Linux|   in a spotlight.
[EMAIL PROTECTED]  |   -- Jim Morrison
http://www.debian.org/~branden/ |


pgpUosA2FBOt4.pgp
Description: PGP signature

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

On Sat, Jan 06, 2001 at 08:28:53PM +0100, Josip Rodin wrote:
> > There is nothing personal in my reply and neither in quoted text and
> ~~
> Um, there is. The thing that caused you to say "Great kiss ass" to hmh.
> 

Well, his answer to the quoted text was what caused me to do it. Sorry if
it sounded too offensive, but it looked like that.

What is more, I honestly did consider if there was anything that would
be wrong to show publicly. Perhaps I assumed that everybody knew how
unnecessarily aggressive the xfree86 maintainer is, and thus nobody
would find hmh's remarks outrageous. As I was writing the reply I'd thought
it had come from the list, but then I saw that it was private then I posted
it. I thought the point I made was more important than anything said about
the xfree86 maintainer.

> > me at all... Are you guys on crack?
> 
> Oh, of course. It's just you who is not, isn't it obvious? :>

:> I wish the xfree86 maintainer had taken this lightly, too. Instead he
chose to launch his usual array of derogatory remarks. Had it been
a salient developer, I might have felt hurt. Now, I have managed to
get the sid version here working and hope the lusers here will be happier.
Had to stand a lot of flames to get a small answer. :/

Thanks,

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo

Re: LILO 21.6-2

[Manoj Srivastava]

>>"Peter" == Peter Makholm <[EMAIL PROTECTED]> writes:

 Peter> Manoj Srivastava <[EMAIL PROTECTED]> writes:
 >> At the moment, if there is no lilo.conf, the kernel-image
 >> postinst creates a functioanl lilo.conf that takes into account

 Peter> Is this wise?

You are asking my opinion? Absolutely. 

 Peter> I assume that in a perfect world the lilo package would be
 Peter> better to configure itself than some "random" other
 Peter> package. The lilo package would have more knowledge of which
 Peter> special things to consider, eventually after consulting the
 Peter> user.

That does not yet happen to be the case. 

Additionally, this functionality has been in the kernel image
 package for about 4 years now; and lilo.conf was never a conffile. 

Additionally, creating a lilo.conf is done with full admin
 approval -- and, IMHO, does a reasonable job of the lilo.conf
 file. In absennce of any capability in the lilo package this was
 required to have a system bootable after installing a kernel
 image. Now that lilo may be doing the job on its own, the need for a
 ``random'' third package to handle what should always have been
 lilo's job is reduced. 

I suggest that the lilo package create a /usr/sbin/liloconfig,
 or some such, which can be invoked at the admins behest and
 convenience.

 Peter> Consider this: Kernel-image gets installed and finds no lilo.conf and
 Peter> makes a minimal but functional lilo.conf. Then lilo gets installed, it
 Peter> finds a lilo.conf and decides not to touch it (what a nice
 Peter> package). What the user now doesn't know is that the lilo packages
 Peter> configuration of lilo.conf would have given him the oputunity to use a
 Peter> password on lilo or some other fancy feature.

Nice hypothesis -- and when it becomes close to reality
 kernel-package shall be changed. All I was commenting was that the
 lilo config needs to be improved to subsume the capability of the
 kernel image postinst (surely not too much to ask for). 

 Peter> Nobody should touch the configuration files belonging to lilo but the
 Peter> local sysadmin and the lilo package itself. And the lilo package
 Peter> should rather  be a little less fancy in it's install than destroying
 Peter> existing configurations.

Were lilo.conf a conffile you would be correct. But it has not
 been so until fairly recently; and, in any case, no lilo.conf was not
 better than a minimal one. I have never said that once we have a
 reasonably competent lilo config process I would not change
 kernel-package. 

Incidentally, an argument could be made that the local admin
 created the file, using the postinst as an intelligent language
 sensitive editor rather than vi.

manoj
-- 
 Magnocartic, adj.: Any automobile that, when left unattended,
 attracts shopping carts. Sniglets, "Rich Hall & Friends"
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Branden Robinson]

On Sat, Jan 06, 2001 at 09:00:38PM +0200, Eray Ozkural wrote:
> On Sat, Jan 06, 2001 at 04:39:43PM -0200, Henrique M Holschuh wrote:
> > Branden, please understand this for what it is meant: "Branden does not like
> > to be poked. He seems to like even less to be poked by you. Please don't
> > poke him, he'll bite back and we get to watch the fallout."
> > 
> 
> Great kiss ass.

I can handle it just fine when clueful people characterize me as
"psychotic".  When professional ignorami like you get hysterical on two
mailing lists and the BTS simultaneously over a FAQ, because you upgraded
your production system to an unstable, unreleased operating system in a fit
of hallucinogenic stupor, you do nothing but earn my contempt and a
deserved rant.

-- 
G. Branden Robinson |   If you have the slightest bit of
Debian GNU/Linux|   intellectual integrity you cannot
[EMAIL PROTECTED]  |   support the government.
http://www.debian.org/~branden/ |   -- anonymous


pgpnGaiA8dLAE.pgp
Description: PGP signature

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[Henrique M Holschuh]

Hi Erik!

On Sat, 06 Jan 2001, Erik Hollensbe wrote:
> I don't quite get this... This list is moderated. Is it not too much for

Not that I know of.

> I have a hard time finding the logic in wasting your time complaing about
> how your time is being wasted. What does this solve?

Humans are hardly logic beings. And you're right, it does solve nothing,
which is probably the reason why a lot of people do it at least once :)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Bug#81396: root shell fscked after upgrade to woody

[Manoj Srivastava]

Hi,
>>"Eray" == Eray 'exa' Ozkural <[EMAIL PROTECTED]> writes:

 Eray> After I upgraded from potato to woody on
 Eray> an i386 machine, I observed a strange sympton

 Eray> I login as root. It doesn't matter where, console, X or
 Eray> from network...
 Eray> When I check the environment, normal user environment is
 Eray> present. If I run apt-get upgrade for instance the program
 Eray> will complain that path doesn't have the *sbin directories
 Eray> which is the way it should be. The quickest way to fix it
 Eray> is to type
 >> su
 Eray> and then I can run any root process without errors on this
 Eray> child shell.

 Eray> I observed the exact error on another installation while
 Eray> upgrading from slink to potato so I presume this is a bug
 Eray> which has not been addressed yet. I had then thought this
 Eray> was a "feature" not a "bug" but now I'm certainly sure it's
 Eray> a bug because the machines I installed from scratch *never*
 Eray> show this behaviour.

There is not enough information in this report to actually do
 anything about debugging the problem. You don't even mention what
 shell you are using as /bin/sh; what you have in /etc/environemnt;
 what you have in the configuration files for the rot user, whether
 you have tried any debugging echo statements (or set -x); whether you
 have wnything in /etc/profile


In other words, an important bug on general, no attempt to
 resolve the problem, and no infromation to allow other to help with
 the problem either.

I would expect a better report from a developer.

manoj
-- 
 The right half of the brain controls the left half of the body.  This
 means that only left handed people are in their right mind.
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: tar -I incompatibility

[Nicolás Lichtmaier]

> > Of course the -I option to tar was completely non-standard.  The changelog
> > explains why it changed, to be consistant with Solaris tar.  I'd prefer
> > portability and consistancy any day, it shouldn't take that long to change
> > any custom scripts you have.  I always use long options for nonstandard
> > commands when building scripts anyway :)
> I think it would be best for *our* tar to move bzip to -j and *not have
> a -I at all*. 

 Or alias -I to -j, but print a warning to stderr:

tar: warning: Using the -I option for bzip compression is an obsolete
functionality and it will removed in future versions of tar,

 Then, in the woody+1 we make -I work as upstream tar does now.

How to report bugs (was glibc thing)

[Greg Stark]

"Eray Ozkural (exa)" <[EMAIL PROTECTED]> writes:

> The preprocessor macro seems to be undefined. There are also other
> subtleties while using pthread lib, such as the __USE_UNIX_98 stuff,
> which I really don't know (I only use c++, and UNIX_98 sections don't
> seem to come along. Why is that?)
> ...
> Now, I think what I say is fairly obvious but the package maintainer
> dismisses this bug like this with a changelog entry:

No, while there were maybe more polite ways to ask for more information I'm
sure it gets tiresome doing so repeatedly on a large package like glibc.

The fact is this is *not* a useful bug report.

To be useful a bug report must answer the following questions:

1) What did you do to cause the bug
2) What did you observe
3) What did you expect to observe
4) Why do you think what you observed was a bug

In this case saying it "seems to be undefined" leaves a million and one
questions unanswered. Do you mean you couldn't find it in the include files?
Or did your program fail because it wasn't defined? Which include files were
you including? What other defines did already have? ...

A useful bug report would have been of the form:

I compiled the following C or C++ file with the following options: 
...
I got the following error indicating this macro wasn't defined: 
...
I expected the macro to be defined and this file should compile because: 
...

Just writing in your conclusions is useless 90% of the time. Your conclusions
may be right but the maintainer doesn't have ESP and can't necessarily deduce
where they came from and what the bug is.

-- 
greg

ITP: worker - filemanager

[Rick Younie]

Package: wnpp
Severity: wishlist

worker is a two-paned directory utility much like the Amiga's
DirectoryOpus.  License is GPL.

Home page: http://www.boomerangsworld.de/worker
Screenshots: http://www.boomerangsworld.de/worker/wscreenshots.php3

What to do about /etc/mtab

[Nicolás Lichtmaier]

> >  >[EMAIL PROTECTED]:/tmp>mount -o loop foo 1
> > Why don't we just patch mount to use /var/run/mtab?
> > I don't know about any other program which modifies it.
> 
> because /var is not always on the same partition as /

 /etc/mtab shouldn't exist, all the information should be handled by the
kernel itself. But for the time being, I think I have a better solution than
the current one:

 Allocate a shared memory area. SHM areas are kept in memory like small
ramdisk. /etc/mtab is rather small, never longer than a 4k page, besides the
memory is swappable.

 And there's an advantage: With a SHM capable mount program there would be
no problem when mounting root read only.

Re: Obsolete software in /usr/local

[Greg Stark]

Ben Armstrong <[EMAIL PROTECTED]> writes:

> On Fri, Jan 05, 2001 at 01:31:42PM -0400, Ben Armstrong wrote:
> > Changes in version 1.9.2:
> > 
> > Removed /usr/local/lib from the default /etc/ld.so.conf
> > for Debian (Bug#8181).
> 
> oops, except that mod is *ancient*.  way before potato.  dunno why this
> would change between potato and woody. 

I've been meaning to bring this up for a while: 
Why on earth was this change ever made?

/usr/local/lib is the supported place for the local admin to put libraries
available to all programs. Every admin who wants to use /usr/local as intended
will have to manually add this entry to have a working system.

In general debian packages ship with empty /usr/local directories but are
configured to automatically use files put in those directories by the
administrator. Why should /usr/local/lib be any different?

Incidentally, by the same logic /usr/local/bin should be in the standard path
and /usr/local/sbin should be in root's standard path as well.

-- 
greg

Re: LILO 21.6-2

[Joey Hess]

Russell Coker wrote:
> Also currently if you don't have debconf configured to display "high" 
> priority messages then the configure phase of installation won't run.  The 
> problem line is:
> db_text high lilo/createdit

You probably want to use the 'note' data type, not 'text'. See the
debconf tutorial.

The debconf shell library causes the db_text (which is just an alias for
db_input) command to return an exit code of 30 if the question was not
displayed to the user. Ignore the return code (|| true) if you want to.

-- 
see shy jo

testing ipv6 tools

[Pierfrancesco Caci]

Maybe I'm missing some important pieces, but is there someone who can
get this to work ?

[EMAIL PROTECTED]:/home/ik5pvx # ping6 fe80::250:4ff:fe38:a630
connect: Invalid argument


the address is the site-wide one automatically assigned to the eth0 of
another computer on the lan.

here's a strace of the command above:

[EMAIL PROTECTED]:/home/ik5pvx # strace ping6 fe80::250:4ff:fe38:a630
execve("/bin/ping6", ["ping6", "fe80::250:4ff:fe38:a630"], [/* 39 vars */]) = 0
uname({sys="Linux", node="penny", ...}) = 0
brk(0)  = 0x806da98
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x40017000
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat64(0x3, 0xbfffebfc)= 0
old_mmap(NULL, 57790, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
close(3)= 0
open("/lib/i686/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340(\0"..., 1024) = 
1024
fstat64(0x3, 0xbfffec44)= 0
old_mmap(NULL, 70628, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40027000
mprotect(0x40035000, 13284, PROT_NONE)  = 0
old_mmap(0x40035000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 
0xd000) = 0x40035000
old_mmap(0x40036000, 9188, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40036000
close(3)= 0
open("/lib/i686/libc.so.6", O_RDONLY)   = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0l\313\1"..., 1024) = 
1024
fstat64(0x3, 0xbfffec34)= 0
old_mmap(NULL, 1179140, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40039000
mprotect(0x4014e000, 44548, PROT_NONE)  = 0
old_mmap(0x4014e000, 28672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 
0x114000) = 0x4014e000
old_mmap(0x40155000, 15876, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40155000
close(3)= 0
open("/lib/i686/libc.so.6", O_RDONLY)   = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0l\313\1"..., 1024) = 
1024
fstat64(0x3, 0xbfffebc4)= 0
close(3)= 0
munmap(0x40018000, 57790)   = 0
getpid()= 10950
socket(PF_INET6, SOCK_RAW, 58)  = 3
SYS_199(0x401542c4, 0, 0x40154f20, 0x40151630, 0x2) = 0
msgget(IPC_PRIVATE, 0)  = 0
socket(PF_INET6, SOCK_DGRAM, 0) = 4
connect(4, {sin_family=AF_INET6, sin6_port=htons(1025), inet_pton(AF_INET6, 
"fe80::250:4ff:fe38:a630", &sin6_addr), sin6_flowinfo=htonl(0)}}, 24) = -1 
EINVAL (Invalid argument)
write(2, "connect: Invalid argument\n", 26connect: Invalid argument
) = 26
_exit(2)= ?
[EMAIL PROTECTED]:/home/ik5pvx # 





-- 

---
 Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED]  -  
http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
 Linux penny 2.4.0 #1 Sat Jan 6 14:27:38 CET 2001 i686 unknown

Re: Release-critical Bugreport for January 5, 2001

[Laurent Bonnaud]

Hi,

would it be possible to clarify the title of this post by adding for
which distribution it is about: "testing" or "unstable" ?  I guess it
is for "unstable", but packages in "unstable" are not meant to be
released, only packages in "testing".

Even if "testing" does not import packages with RC bugs from
"unstable", RC bugs may be found *after* the package inclusion into
"testing".  So it might be useful to have this post for both "testing"
and "unstable".

How hard would it be to implement ?

-- 
Laurent.

Re: tar -I incompatibility

[Sebastian Rittau]

On Sat, Jan 06, 2001 at 02:53:06PM +, Colin Watson wrote:
> "Scott Ellis" <[EMAIL PROTECTED]> wrote:

> >Of course the -I option to tar was completely non-standard.  The
> >changelog explains why it changed, to be consistant with Solaris tar.
> 
> I don't see the reasoning in the changelog, but I may just have missed
> it.

It's actually in the NEWS file:

| * The short name of the --bzip option has been changed to -j,
|   and -I is now an alias for -T, for compatibility with Solaris tar.

 - Sebastian

Re: Bug#81397: [authorization] fails silently for normal users, cannot start server

[exa]

Excuse me, I had not read the latter amusing part of the mail.
I'd just seen the reassign part.

It looks like Branden makes another hopeless attempt at defamation
of a bug reporter and fellow contributor with his underrated
literary skills.

On Sat, Jan 06, 2001 at 10:36:33AM -0500, Branden Robinson wrote:
> As you've demonstrated so amply on the Debian mailing lists, you are an
> idiot.
> 

Things you have demonstrated would need so much space to tell
that it wouldn't be fitting to tell them here. As you have noticed,
I'm not taking such lame remarks seriously and arguing over a public
list like adolescent lusers.

However, there is one thing that I do remember about your behavior
on this list. You are continously trying to correct other people's
spelling mistakes and I remember that you have written mails exclusively
about spelling a couple of times. Which is not a nice thing to do.
Whatever your English skills are not that relevant here.

Now, I'm sure you believe that you are a skilled programmer or an
extremely valuable member of the free software community. But then
of course, beliefs may not correspond to reality. A mere build and
configuration task...

Such primitive reaction of yours is not likely to arouse interest
in prospective contributors; to join debian and to work with people
like you.