Re: [] Bug#27841: apt: apt depends on a missing library

[Dan Jacobowitz]

On Thu, Oct 15, 1998 at 09:49:22PM -0700, Ben Gertzfield wrote:
> > "Dan" == Dan Jacobowitz <[EMAIL PROTECTED]> writes:
> 
> Dan> See, it's not "Is anyone going to?" or "Do we agree we
> Dan> should?" right now.  It's "does anyone but Dan have the time
> Dan> to look at http://master.debian.org/~dan and figure out why
> Dan> the compiled libstdc++2.8 package whose source is there is
> Dan> missing a lot of important symbols".  I can't figure it out.
> 
> Ben> The source in http://master.debian.org/~dan in the libstdc
> Ben> sir is for 2.9. Could this be the problem?
> 
> Dan> I present
> Dan> http://master.debian.org/~dan/libstdc/libstdc++_2.90.29-1.dsc
> Dan> for your enjoyment...
> 
> Dan> Notice it says Binary: libstdc++2.8.
> 
> Wow. How does 2.90 compile out to become 2.8?

The same way egcs 1.1b becomes gcc 2.91.53.  The one is an interface
number and the other an internal version.

Dan

Re: moving mutt-i from non-us to main

[Steve Greenland]

On 15-Oct-98, 18:02 (CDT), [EMAIL PROTECTED] wrote: 
> Marc Singer writes:
> > I was under the impression that putting hooks in to use crypto was enough
> > to raise the hackles of the export hounds.
> 
> Standing near the border and thinking about prime numbers is enough to
> raise the hackles of the export kooks.  Ihere has got to be some limit to
> the amount of crap we'll take from these jerks.  Ignore the nonsense about
> 'hooks' and ship it.

While I agree in principle, you might want to ask Michael Elkins first;
it's conceivable that he could be brought into any litigation (on the
"let's accuse everyone whose name we can find anywhere near it" theory).
This came up a lot when I was reading the mutt lists (back in the 0.4x
era), and IIRC Michael was very concerned about being charged with a
crypto violation, not because he believed he was guilty, but because
simply having to defend himself legally would pretty much ruin him
financially. Whether we agree or not, I think we should respect the 
author's wishes (as we did when we pulled the MP3 thingie (8hz?)).

Steve Greenland

Re: Intend to package, create OSS/Free

[Hamish Moffatt]

On Fri, Oct 16, 1998 at 12:36:21AM -0500, Manoj Srivastava wrote:
>   I can arrange to have the debian version passed in the ENV
>  variable KDREV, or something. That would be clean.

That sounds excellent. I will await it eagerly :-)


Hamish
-- 
Hamish Moffatt VK3TYD  [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org

Re: [] Bug#27841: apt: apt depends on a missing library

[Ben Gertzfield]

> "Dan" == Dan Jacobowitz <[EMAIL PROTECTED]> writes:

Dan> See, it's not "Is anyone going to?" or "Do we agree we
Dan> should?" right now.  It's "does anyone but Dan have the time
Dan> to look at http://master.debian.org/~dan and figure out why
Dan> the compiled libstdc++2.8 package whose source is there is
Dan> missing a lot of important symbols".  I can't figure it out.

Ben> The source in http://master.debian.org/~dan in the libstdc
Ben> sir is for 2.9. Could this be the problem?

Dan> I present
Dan> http://master.debian.org/~dan/libstdc/libstdc++_2.90.29-1.dsc
Dan> for your enjoyment...

Dan> Notice it says Binary: libstdc++2.8.

Ben> Wow. How does 2.90 compile out to become 2.8?

Dan> The same way egcs 1.1b becomes gcc 2.91.53.  The one is an
Dan> interface number and the other an internal version.

Well, I've given this a compile and you're right.

[EMAIL PROTECTED]:~/src/libstdc]% mysql
mysql: error in loading shared libraries
/usr/lib/libstdc++.so.2.8: undefined symbol: __ti9exception
[EMAIL PROTECTED]:~/src/libstdc]% exit

I can't find any mention of anything like this in the libstdc++
sources. Have you mailed the egcd team?

-- 
Brought to you by the letters T and U and the number 15.
"We are the music makers. And we are the dreamers of dreams." -- Willy Wonka
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.

Re: what is non-free in this license?

[Joseph Carter]

On Fri, Oct 16, 1998 at 03:47:16PM -0400, Peter S Galbraith wrote:
> > > THERE IS NO WARRANTY FOR THIS PROGRAM - whatsoever. You use it entirely
[..]
> > 
> > What I hi-lighted I do believe violates the DFSG..
> > 
> > Zephaniah E, Hull.
> 
> Huh?  Where do the DFSG say this?
> See http://www.debian.org/social_contract#guidelines
> 
> Go into Emacs and type C-h C-w 

That had been highlighted by the original author...  =>


pgpUkqxVZhK2c.pgp
Description: PGP signature

Re: moving mutt-i from non-us to main

[john]

Steve Greenland writes:
> While I agree in principle, you might want to ask Michael Elkins first;
> it's conceivable that he could be brought into any litigation

I didn't realize that the author of mutt-i was a US resident (I don't use
mutt at all, myself).

> ...simply having to defend himself legally would pretty much ruin him
> financially.

I think he'd find people standing line to defend him for free.

> I think we should respect the author's wishes...

Yes.  Perhaps we should ask what they are?
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI

Re: PROPOSAL: one debian list for all porting efforts

[Martin Mitchell]

John Goerzen <[EMAIL PROTECTED]> writes:

> around compiling all the i386 stuff for the other archs.  But nobody
> goes around compiling the stuff from the other archs for i386!  So if
> I suddenly do all my package development on Alpha, the Alpha will have 
> the current versions, and perhaps the Sparc and m68k too, but i386
> will be obsolete!  Fix anybody?

I have been compiling the enscript package for i386, which Hartmut Koptein
maintains on powerpc. So there are people doing this, it just isn't
widespread at the moment.

Martin.

Re: Removing Packages in Slink for Debian 2.1

[Manoj Srivastava]

Hi,
>>"Michael" == Michael Alan Dorman <[EMAIL PROTECTED]> writes:

 Michael> I don't know.  I thought: 1) Manoj took over the package with my
 Michael> blessings, and 2) he did so with the specific intention of fixing the
 Michael> bug.


And I did. I uploaded a package, and closed all bugs. Before
 the freeze, even. It is under my name in the BTS. It was put into the
 archive way before the freeze. 

 Michael> However, looking at the package as it stands, I see that in fact the
 Michael> upgrades I thought Manoj did were actually done by Turbo as NMUs
 Michael> (which would explain why it was still being listed as my package).

It is now listed as my package! II even posted on this earlier
 that the bugs have been fixed.

 Michael> I've done a new release which I believe fixes all outstanding bugs.
 Michael> Turbo, would you like to take over the package?

NO NO n

Please look berfore you do this!. You have effectively
 hijacked my package. Please do not offer it to other people. Please
 retract your upload. I am no lonmger willing to give up this package,
 after all the effort that I have put in it. 

manoj

cat /home/Debian/ftp/private/project/Incoming/DONE/gnus_5.6.44-2_i386.changes 
-BEGIN PGP SIGNED MESSAGE-

Format: 1.5
Date: Thu, 15 Oct 1998 01:32:41 -0500
Source: gnus
Binary: gnus
Architecture: source all
Version: 5.6.44-2
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <[EMAIL PROTECTED]>
Description: 
 gnus   - A versatile News and mailing list reader for Emacsen
Changes: 
 gnus (5.6.44-2) unstable; urgency=low
 .
   * New maintainer.
   * Enhanced the Long description.
   * Made all the maintainer scripts follow the Skeleton maintainer scripts
 Written by Charles Briscoe-Smith, March-June 1998.
   * Fixed the location of the emacsen remove call, which should clear out
 the problem faced while removing the package. Make sure the script is
 way more robust about misssing directories and all. closes: Bug#25609
   * Changed dependency to xemacs20-bin instead of xemacs20 (which does
 not, in fact, exist). closes: Bug#25585
   * Made the install/remove scripts always return a valid exit status, and
 be generally better behaved. closes: Bug#26536
   * Made the rules file more genralized, and more in line with my ther
 packages.
   * Also install the HTML documentation, since we are supposed to be moving
 to HTML, after all
   * Fix the control file. There was no section and priority information,
 so dpkg-genchanges complained.
Files: 
 a5973df16ed2551eb15a906fe48d69d4 660 news optional gnus_5.6.44-2.dsc
 ea5a156d11facf2e6153eb68ef6acf27 7399 news optional gnus_5.6.44-2.diff.gz
 c47e7d0401df364a03f754b7c054c198 1039142 news optional gnus_5.6.44-2_all.deb

-BEGIN PGP SIGNATURE-
Version: 2.6.3a
Charset: noconv
Comment: Requires PGP version 2.6 or later.

iQCVAwUBNiWps23FgPXHJhCVAQEf+AP+J/j390LSPBHf1ZiXSVty3DEe/b1tYfVE
w7Ikl/I/S9rigNqQYRKeuZD9r9spRw0+PLcH8l7UcooqEExjZxWEqCRLWcLn/tck
GY5FxZ8tTbFQPRhkgYlvblBDAkXDpJMi7OYnBuqlzKYspTDupW3WBnBTyd+BCGca
ahlGKZk6Z2o=
=QX6J
-END PGP SIGNATURE-

-- 
 "Security is mostly a superstition.  It does not exist in
 nature... Life is either a daring adventure or nothing." Helen Keller
Manoj Srivastava  <[EMAIL PROTECTED]> 
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E

Re: moving mutt-i from non-us to main

[Dan Jacobowitz]

On Fri, Oct 16, 1998 at 08:38:57PM -0500, [EMAIL PROTECTED] wrote:
> Steve Greenland writes:
> > While I agree in principle, you might want to ask Michael Elkins first;
> > it's conceivable that he could be brought into any litigation
> 
> I didn't realize that the author of mutt-i was a US resident (I don't use
> mutt at all, myself).
> 

He isn't. ME no longer does the mutt-i patches; they are maintained in
Germany.

Dan

Re: (WARNING) xfree86 3.3.2.3a-2 (source all i386) uploaded to master

[Joseph Carter]

On Fri, Oct 16, 1998 at 12:40:53PM -0700, Ben Gertzfield wrote:
> > "Branden" == Branden Robinson <[EMAIL PROTECTED]> writes:
> 
> Branden> Topi Miettinen has done some research on this.  When we
> Branden> get SysV-style pty support in glibc, xterm can lose its
> Branden> root privileges altogether.  I hear th= is will be in
> Branden> glibc 2.1?
> 
> SysV-style pty support is a kernel option in linux kernel 2.1.xx
> (where xx is pretty recent :) so I know the kernel supports it.
> 
> I don't know how glibc deals with them.

Newer 2.1.x kernels and glibc 2.1 support them.


pgpKr0r2ESaQV.pgp
Description: PGP signature

Re: updates to Debian pages

[Adam P. Harris]

"James A. Treacy" <[EMAIL PROTECTED]> writes:
>A link has been added from all the /Pics -> ../english/Pics on 
> master.
>They weren't added to CVS as it doesn't handle special files very well.
>Its only important that master have them anyway, so the pages the public 
> sees
>have the tags.

Actually, it's pretty easy to support symlinks in CVS in a robust
fashion.  If you want to create the link on either checkout or export,
hack the modules file like so:

addressbook -e $CVSROOT/CVSROOT/addressbook -o $CVSROOT/CVSROOT/addressbook 
debian/addressbook

Then you add 'CVSROOT/addressbook' to robustly create the links.  Cf
my included file for an example.

.A. P. [EMAIL PROTECTED]http://www.onShore.com/>


addressbook
Description: Binary data

Re: (WARNING) xfree86 3.3.2.3a-2 (source all i386) uploaded to master

[Joel Klecker]

At 14:02 -0400 1998-10-16, Branden Robinson wrote:
Topi Miettinen has done some research on this.  When we get SysV-style pty
support in glibc, xterm can lose its root privileges altogether.  I hear this
will be in glibc 2.1?
Yes, that's correct.
--
Joel Klecker (aka Espy)
mailto:[EMAIL PROTECTED]>http://web.espy.org/>
  Debian GNU/Linux user/developer on i386 and powerpc.
mailto:[EMAIL PROTECTED]>  http://www.debian.org/>

Re: Bugs with X

[Joel Klecker]

At 13:53 -0400 1998-10-16, Branden Robinson wrote:
I definitely want to build debugging versions of the X libraries, but as
yet I don't know how to do it.  The makefiles for X are byzantine.
[snip]
But I do want to get debugging versions of the libraries soon.  As soon as
I can figure out how.
It's quite simple, pass -g in CFLAGS or whatever, and copy the libs 
(unstripped) into xlib6{,g}-dbg.
--
Joel Klecker (aka Espy)
mailto:[EMAIL PROTECTED]>http://web.espy.org/>
  Debian GNU/Linux user/developer on i386 and powerpc.
mailto:[EMAIL PROTECTED]>  http://www.debian.org/>

Re: moving mutt-i from non-us to main

[Alexander Koch]

On Fri, 16 October 1998 20:38:57 -0500, [EMAIL PROTECTED] wrote:
> I didn't realize that the author of mutt-i was a US resident (I don't use
> mutt at all, myself).

Some time ago (can't remember any version numbers) the PGP
version was hacked by Thomas Roessler <[EMAIL PROTECTED]>
right after the normal version came out.

Right now Michael Elkins has a job enslaving (sp?) him to
use a Mickeysoft OS any he doesn't have the time for much
of the former codings any more.

Thomas Roessler is the keeper of the source at the moment.
Perhaps Roland Rosenfeld can ask him what he thinks of it?

Alexander

-- 
"The creatures outside looked from pig to man, and from man to pig, and from
 pig to man again: but already it was impossible to say which was which"
(George Orwell, The Animal Farm, very last sentence)
Alexander Koch - <>< - aka Efraim - PGP - 0xE7694969 - Hannover - Germany

What Bruce had to say about non-Pixar names. Re: what's after slink

[Christopher Barry]

Saw this posting from Bruce on Slashdot:

http://www.slashdot.org/comments.pl?sid=98/10/15/1011208&pid=128#147


[EMAIL PROTECTED] wrote:
> 
> On Thu, Oct 15, 1998 at 03:45:49PM -0700, Joseph Carter wrote:
> > On Thu, Oct 15, 1998 at 03:29:34PM -0700, Joey Hess wrote:
> > > theone wrote:
> > > > Names after Slink is very simple.  They should just be named after 
> > > > userfriendly characters.
> > >
> > > Oooh.. that means our releases would even have their own geek code blocks
> > > (http://www.userfriendly.org/cast/)  ;-)
> > >
> > > dust_puppy
> > > pitr
> > > aj
> > > chief
> > > cobb
> > > erwin
> > > greg
> > > hillary
> > > mike
> > > smiling_man
> > > stef
> > > tanya
> >
> > miranda now too...  Don't forget her.
> >
> > (I still want an iWhack)
> 
> Debian GNU/Linux Erwin/iWhack!
> 
> Zephaniah E, Hull, <--- Thought he suggested this before?
> 
>   
> 
>Part 1.2   Type: application/pgp-signature

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[Martin Schulze]

Christopher Barry wrote:
> Saw this posting from Bruce on Slashdot:
> 
> http://www.slashdot.org/comments.pl?sid=98/10/15/1011208&pid=128#147

Do you want us to hurry up in order to catch up with the new 'whole
bunch' of code names?

scnr

Joey

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

Re: 1FA: problem still in hamm disks

[Tom Lees]

On Fri, Oct 16, 1998 at 12:34:09PM -0700, Ben Gertzfield wrote:
> > "Brent" == Brent Fulgham <[EMAIL PROTECTED]> writes:
> 
> Brent> I'd like to chime in -- It's a real annoyance that the base
> Brent> disks don't set up lilo to let you boot into multiple
> Brent> operating systems.  Couldn't it ask if you want to
> Brent> dual-boot with windows, or whatever, and generate an
> Brent> appropriate lilo.conf file?
> 
> Sure. How about you write the script to do so?

While I'm at it, *PLEASE* drop the dependency of lilo on mbr. I don't want
a new mbr eg if I want to install LILO to use on a floppy ONLY (I use
GRUB on my HD). Change it to Recommends. mbr being a high priority and/or
essential (can't remember if it is) should be enough.

> Brent> This is an area where RedHat has a significant lead over
> Brent> us.  One of the guys I work with is a huge RedHat fan
> Brent> because he can just pop a RH CD into the drive, windows
> Brent> will autorun it, and RedHat install starts.  It sets up
> Brent> almost everything for the user.
> 
> If RH has released this code under the GPL, then why don't we borrow
> it for our use? I know that it's as simple as having an 'autorun'
> directory on the CD image.

IIRC there is an "autorun.cfg" or similar too.

> Brent> I know we support far more configurations, etc. etc. etc.,
> Brent> but for the average Joe New-User this is a large hurdle.
> 
> I'm sure Enrique is always happy to accept code to do so. :)

Just out of interest, how does the autorun bit work? You can't just run
loadlin straight from Windoze.

-- 
Tom Lees <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>  http://www.lpsg.demon.co.uk/
PGP Key: finger [EMAIL PROTECTED], http://www.lpsg.demon.co.uk/pgpkeys.asc.

Re: (WARNING) xfree86 3.3.2.3a-2 (source all i386) uploaded to master

[Tom Lees]

On Fri, Oct 16, 1998 at 02:02:21PM -0400, Branden Robinson wrote:
> On Fri, Oct 16, 1998 at 10:25:57AM -0700, Ben Gertzfield wrote:
> > Branden Robinson <[EMAIL PROTECTED]> writes:
> > 
> > > W: xext: shlib-without-dependency-information
> > > usr/X11R6/lib/modules/xf86Jstk.so 
> > 
> > > I have always gotten this error.  I don't know how to fix it, but it
> > > doesn't seem to hurt anyone.
> > 
> > Well, this isn't a shared library that's going to be linked to, so
> > there should be a way to override lintian's behavior.
> 
> Oh, I get it.  The complaint's not about the file itself, but the absence
> of mention in a shlibs file.  Okay.  Well, yeah, that should be overridden.
> The only thing that uses those modules is the X server.

If you ask me, lintian should ignore files like this outside standard library
directories (/lib, /usr/lib, /usr/X11R6/lib). They are almost always modules,
eg netscape plugins, etc.

-- 
Tom Lees <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>  http://www.lpsg.demon.co.uk/
PGP Key: finger [EMAIL PROTECTED], http://www.lpsg.demon.co.uk/pgpkeys.asc.

syntax highlighting in gtk

[Michael Meskes]

I read so much about a patch needed to get syntax highlighting. Do we have
that patch in out gtk libs? If no, why not?

Michael
-- 
Dr. Michael Meskes  | Th.-Heuss-Str. 61, D-41812 Erkelenz | Go SF49ers!
Senior-Consultant   | business: [EMAIL PROTECTED] | Go Rhein Fire!
Mummert+Partner |  private: [EMAIL PROTECTED]| Use Debian
Unternehmensberatung AG |   [EMAIL PROTECTED]| GNU/Linux!

Intend to package gxedit

[Michael Meskes]

I just found it and on first glance it looks great. It looks like a very
nice editor. Also provided is a small tool to show some information about
the system named xproc. 

If anyone else is interested I would give him the links but if noone is I
will package it as time permits.

Michael
-- 
Dr. Michael Meskes  | Th.-Heuss-Str. 61, D-41812 Erkelenz | Go SF49ers!
Senior-Consultant   | business: [EMAIL PROTECTED] | Go Rhein Fire!
Mummert+Partner |  private: [EMAIL PROTECTED]| Use Debian
Unternehmensberatung AG |   [EMAIL PROTECTED]| GNU/Linux!

More interesting gnome/gtk software

[Michael Meskes]

I found more than GXedit. There is a nice task timer available named gtimer.
I might package that one too. Also there is a GTK mp3 player named replay.
It is GPLed but based on amp. I wonder if this is correct. Anyway, since I
seldom play MP3s I let this to someone else.

I also wanted to try gqmpeg(mpeg viewer) and gtksee(ACD See look alike) but
both sources didn't make it to my site completely.

Finally I'm very interested and might consider packaging xnet, a GTK tool
for PPP links. But I have yet to see it. It doesn't compile for me. And the
provided binary seg faults.

Michael
-- 
Dr. Michael Meskes  | Th.-Heuss-Str. 61, D-41812 Erkelenz | Go SF49ers!
Senior-Consultant   | business: [EMAIL PROTECTED] | Go Rhein Fire!
Mummert+Partner |  private: [EMAIL PROTECTED]| Use Debian
Unternehmensberatung AG |   [EMAIL PROTECTED]| GNU/Linux!

Re: [owner@bugs.debian.org: Debian bugs information: logs for bug#26827]

[Michael Meskes]

On Fri, Oct 16, 1998 at 07:00:23PM -0400, [EMAIL PROTECTED] wrote:
> > [EMAIL PROTECTED]:~$ sudo su -s /bin/sh nobody -c "ls /"
> > Unknown option -s
> 
> sudo? adding a unnessary layer here, but anyways..

Just to make sure I don't have to enter any passwords. :-)

> It IS implied that its FULLY gnu-su compatible, if it is not then it

Where did you find that? I never read it.

> should not provide su, very very simple..

But then gnu-su is not your standard su. As usually with gnu tools it has
much more features than the su you find on other unix versions. I still
don't see why this is important enough to warrant a removal of secure-su.

Michael

-- 
Dr. Michael Meskes  | Th.-Heuss-Str. 61, D-41812 Erkelenz | Go SF49ers!
Senior-Consultant   | business: [EMAIL PROTECTED] | Go Rhein Fire!
Mummert+Partner |  private: [EMAIL PROTECTED]| Use Debian
Unternehmensberatung AG |   [EMAIL PROTECTED]| GNU/Linux!

Re: moving mutt-i from non-us to main

[Roland Rosenfeld]

Alexander Koch <[EMAIL PROTECTED]> wrote:

> Some time ago (can't remember any version numbers) the PGP version
> was hacked by Thomas Roessler <[EMAIL PROTECTED]> right after the
> normal version came out.

> Right now Michael Elkins has a job enslaving (sp?) him to use a
> Mickeysoft OS any he doesn't have the time for much of the former
> codings any more.

> Thomas Roessler is the keeper of the source at the moment.

I don't understand, what the Author (Michael Elkins) or the current
Maintainer of the upstream version (Thomas Roessler) have to do with
us (Debian) offering their program on our US ftp servers. IMHO only
those people are responsible for export from US to the free world, who 
put it on the FTP servers without restriction. So if a Debian mutt in
main is illegal according to US law, than Debian (or the owner of the
FTP servers) are responsible, not the author of the program.

It's another question, whether exporting a program, with simply calls
pgp (and parses the PGP keyring), breaks the US exporting laws.
When we mean, that this is illegal, we should move dpkg-buildpackage
to non-US, because this calls pgp, too...

Tscho

Roland

-- 
  * Internet: [EMAIL PROTECTED] * Fido: 2:2450/42 *
 PGP: 1024/DD08DD6D   2D E7 CC DE D5 8D 78 BE  3C A0 A4 F1 4B 09 CE AF

gtimer

[Michael Meskes]

I just notices that it has already be packaged. Great.

Michael
-- 
Dr. Michael Meskes  | Th.-Heuss-Str. 61, D-41812 Erkelenz | Go SF49ers!
Senior-Consultant   | business: [EMAIL PROTECTED] | Go Rhein Fire!
Mummert+Partner |  private: [EMAIL PROTECTED]| Use Debian
Unternehmensberatung AG |   [EMAIL PROTECTED]| GNU/Linux!

mutt

[Marco d'Itri]

Look like there is consensus to move mutt-i to main.
In the next days I will upload it along with some fixes.

-- 
ciao,
Marco

g++ dependency problem

[Shaleh]

The latest g++ on debian.midco.net (2.9.57-4) depends on libstd++ (>= +2.9.57).
 The plus there seems to be causing a problem as all that can be found is
2.9.57.

RE: g++ dependency problem

[Shaleh]

Of course that should have read 2.91.57 (-:

On 17-Oct-98 Shaleh wrote:
> The latest g++ on debian.midco.net (2.9.57-4) depends on libstd++ (>=
> +2.9.57).
>  The plus there seems to be causing a problem as all that can be found is
> 2.9.57.
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 1FA: problem still in hamm disks

[Michael Stone]

Quoting Tom Lees ([EMAIL PROTECTED]):
> While I'm at it, *PLEASE* drop the dependency of lilo on mbr. I don't want
> a new mbr eg if I want to install LILO to use on a floppy ONLY (I use
> GRUB on my HD). Change it to Recommends. mbr being a high priority and/or
> essential (can't remember if it is) should be enough.

Can someone explain what the point of mbr is? Why not just install lilo
directly to the mbr? (I always go back and do this for security reasons
anyway: I've disabled floppy boot in the bios, why do I want an mbr
that re-enables it?)

Mike Stone

intent to package xmeter

[Bo Branten]

Description: rstat display for X
 Xmeter displays a periodically updating histogram  of  the
 system  statistics  gathered by rstat(3) for the specified
 hosts.  Meters can be displayed in a vertical,  horizontal
 or rectangular arrangement.  As statistics range between 4
 user defineable levels (OK, WARN,  ERROR  or  FATAL),  the
 background,  foreground,  highlight,  border  and internal
 border colors, and the background bitmap of each meter can
 be changed.

intent to package minfo

[Bo Branten]

Description: GNU Info file browser for X

Re: moving mutt-i from non-us to main

[john]

Roland writes:
> I don't understand, what the Author (Michael Elkins) ...

Mr. Elkins should be innocent even by the standards of the anti-encryption
kooks as long as he had nothing to do with the installation of the
encryption hooks.

> ...or the current Maintainer of the upstream version (Thomas Roessler)
> have to do with us (Debian) offering their program on our US ftp
> servers. IMHO only those people are responsible for export from US to the
> free world, who put it on the FTP servers without restriction.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI

Re: mutt

[john]

Marco writes:
> Look like there is consensus to move mutt-i to main.  In the next days I
> will upload it along with some fixes.

Do you think we should check with ME first?  While I don't believe he is at
any risk of prosecution, we should respect his wishes.

We should also consider moving any other software that is non-us because of
encryption hooks out of non-us.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI

Re: KDE gone, Linux next?

[Christian Hammers]

On Wed, Oct 14, 1998 at 09:06:32PM +1000, Matthew Parry wrote:
> As Linux becomes more popular the hardware manufacturers will start
> giving away drivers with the hardware, as they do for WIN95/NT/Mac.
> If we give them the option to release the drivers as closed source
> then most of them will.  But if we force them to release as open
> source then they'll still release the drivers - because market
> demand requires it - but they'll release them as free software 

Maybe somewhen this will happen, but during the next few years, the 
hardware manufacturer will rather ship NO drivers for special kinds of 
hardware than open software. :-(

Of course open software has the advantage that one could recompile it
more easily if the kernel version changes (which company bothers with
35 patches of a stable kernel ! Even MS does not produce such many 
patches).

But I would only try to encourage them to produce linux driver. In a way
they like. If one does not like it, one could wait for the hackers out
there to produce a working freeware driver. 


> In the case of word processors, I could care less.  But when
> it comes to something like the kernel - something that at times
> requires fast bugfixes - it is extreemly important.
Remember, if you do not have a driver for your hardware it becomes quite
unimportant how fast bugfixes would be made. 
First we must get the companies to PRODUCE drivers for Linux at all !

> Matthew Parry
read you,

  -christian-

-- 
Linux - the choice of the GNU generation.  Join the Debian Project 
 http://www.debian.org 
Christian Hammers * Oberer Heidweg 35 * D-52477 Alsdorf * Tel: 02404-25624
50 3C 52 26 3E 52 E7 20  D2 A1 F5 16 C4 C9 D4 D3  1024/925BCB55 1997/11/01

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[john]

Joey writes:
> Do you want us to hurry up in order to catch up with the new 'whole
> bunch' of code names?

I'd still like to use penguins.
-- 
John HaslerThis posting is in the public domain.
[EMAIL PROTECTED]  Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[Dirk Eddelbuettel]

  john>  I'd still like to use penguins.

Indeed, that was the best proposal yet.

-- 
Linux is not only free; it is, arguably, a better operating system, offering
a degree of stability and an ability to scale up that NT cannot match.
 -- The Economist, Oct 3, 1998

Re: mutt

[Dan Jacobowitz]

On Sat, Oct 17, 1998 at 09:42:54AM -0500, [EMAIL PROTECTED] wrote:
> Marco writes:
> > Look like there is consensus to move mutt-i to main.  In the next days I
> > will upload it along with some fixes.
> 
> Do you think we should check with ME first?  While I don't believe he is at
> any risk of prosecution, we should respect his wishes.
> 
> We should also consider moving any other software that is non-us because of
> encryption hooks out of non-us.

And I maintain that we can not do this.  Much as I wish we could.  Note
that mutt-i has a separate upstream source - in Germany.

Dan

/var/lib/dpkg/info/*.shlibs

[Russell Coker]

How are these files generated using dh_gencontrol?  IIn the following file
the version number of libkdeui should be 2.  However it gets generated as 1
and I can't work out how I'm supposed to make it 2.

Apart from this my kdelibs0g and kdesupport0g packages are coming along well.
I got the impression that these packages are suitable for inclusion in the
non-free section of Debian (it's just all the other KDE packages that are
out).  If that is correct then I will shortly submit my application to
become a registered Debian developer to maintain these packages.

[EMAIL PROTECTED]:/var/lib/dpkg/info$cat kdelibs0g.shlibs
libjscript 1 kdelibs0g
libkab 1 kdelibs0g
libkdecore 1 kdelibs0g
libkdeui 1 kdelibs0g
libkfile 1 kdelibs0g
libkfm 1 kdelibs0g
libkhtmlw 1 kdelibs0g
libkspell 1 kdelibs0g
libmediatool 1 kdelibs0g

--
I'll be in Denver from 30 Oct 1998 to 7 Nov 1998 (or maybe a few days longer).
I'll be in London from ~9 Nov 1998.  I'd like to meet any Linux users or
users groups in these places at these times.
I plan to work in London for 3 - 6 months...

Re: moving mutt-i from non-us to main

[Alexander Koch]

Hi Roland.

On Sat, 17 October 1998 10:36:48 +, Roland Rosenfeld wrote:
> I don't understand, what the Author (Michael Elkins) or the current
> Maintainer of the upstream version (Thomas Roessler) have to do with
> us (Debian) offering their program on our US ftp servers.

I meant it'd be nice to ask them... nothing more. ,-))
And if they would (have) object(ed), that should have a certain ..
influence on the decision besides *any* export and crypto stuff.

> When we mean, that this is illegal, we should move dpkg-buildpackage
> to non-US, because this calls pgp, too...

*grin*
Your point.

Alexander

-- 
"The creatures outside looked from pig to man, and from man to pig, and from
 pig to man again: but already it was impossible to say which was which"
(George Orwell, The Animal Farm, very last sentence)
Alexander Koch - <>< - aka Efraim - PGP - 0xE7694969 - Hannover - Germany

Re: KDE gone, Linux next?

[Steve Greenland]

On 17-Oct-98, 08:33 (CDT), Christian Hammers <[EMAIL PROTECTED]> wrote: 
> On Wed, Oct 14, 1998 at 09:06:32PM +1000, Matthew Parry wrote:
>> [forcing manufacturers to release device drivers as free software] 
> Maybe somewhen this will happen, but during the next few years, the 
> hardware manufacturer will rather ship NO drivers for special kinds of 
> hardware than open software. :-(

But if they are allowed to released closed-source drivers, then there
is no incentive for them to *ever* release free ones. In the meantime,
I will continue to buy supported hardware, and occasionally inform a
manufacturer that I chose not to buy their device because they did
not support Linux (either buy providing the driver, or by providing
sufficient info for someone to write the driver).

Steve

SUMMARY -- (was Bug#27823: proftpd: non-maintainer upload (alpha) diffs)

[Adam P. Harris]

Joey Hess <[EMAIL PROTECTED]> writes:
> One wonders why you don't. Thisporting effort seems to lead to a lot of
> bitter people being involved in it. One wonders why. Anyhow, TTFN.

Well, I think I can see why.  Because porting is a thankless and
gruelling task.  You come head to head with every little packaging
mistake, get bit by the flubs of newbie Debian developers and silly
oversights by developers who should know better, and face the fear,
hostility, and a general lack of understanding by quite a few
(i386-centric) Debian folks.

I think this whole discussion got off on the wrong foot because the
issues got confused.  Let's try to break them out so we can address
them constructively.

ISSUE 1:

Portability or packaging fixes made by porters should propogate into
the "upstream" Debian package.

 Solution: porters must submit bugs for their fixes to the BTS

This is *already* the case, so this is a non-issue, IMHO.  Asking
porters to wait for the upstream maintainer to respond and fix the bug
does *not* scale to the level of packages that porters routinely have
to deal with.  I think that porters should be allowed and encouraged
to do binary-only NMUs + BTS bug filed against package (which some
caveats, see licensing below).

Asking porters to wait is basically like trying to kill the porting
effort, which Mssr. Hess should try to realize.


ISSUE 2:

There are a lot of common errors made by package maintainers, i.e.,
wrong architecture in debian/control, leaving 'debian/files' in the
source package.

 Solution: work with the lintian maintainer and have error conditions
or warnings generated for these cases, if it is not already the case.
Write a section for the packaging manual on dos and don'ts based on
the unique experience of the porters.


ISSUE 3:

Binary-only packages w/o source may break some licenses.  A lot of
this comes down to whether distributing source via the ftp archive,
and patches via the BTS, conform to a given license's requirements.

This issue is being hashed out in , so I really don't
want to go into it here.  Basically my stand is that assuming that the
patch has been submitted to the BTS, porters should simply be able to
state in the changelog something like "patches for this port available
on the Debian Bug Tracking System http://www.debian.org/Bugs>".

I think it's important that our ass is covered for GPL and NPL and MPL
packages (or any license w/ the source availability requirement), but
I really don't think ports can succeed if uploading binaries with
minor portability fixes is a major hassle.



Any other issues?  I'm about to go toddle off to the Developer's
Reference and add a section for porters.  I think a clearly documented
practice for porters would be a good thing, i.e., less verbal lore for
porters to have to know, so becoming a porter would be easier, and
more comprehension of the process by x86-centric maintainers.

.A. P. [EMAIL PROTECTED]http://www.onShore.com/>

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[Alexander Koch]

On Sat, 17 October 1998 11:10:10 -0400, Dirk Eddelbuettel wrote:
>   john>  I'd still like to use penguins.
> Indeed, that was the best proposal yet.

Hmh.. no. ,-)
I prefer comics and things like that.. argh, so to say. :-)

Alexander

-- 
"Matthias needs someone to smack him upside with an iron cluebat,
 several times." -- Joseph Carter ...
Alexander Koch - <>< - aka Efraim - PGP - 0xE7694969 - Hannover - Germany

Re: Bug#27823: proftpd: non-maintainer upload (alpha) diffs

[Adam P. Harris]

"Christopher C. Chimelis" <[EMAIL PROTECTED]> writes:
> This is true, and this should be fixed, IMO.  If "Debian", as an entity,
> is making a decision to become multi-arch supportive, then maybe it's
> time to update the older rules that were made when x86 was the only
> arch, and time to implement some rules and methods that are more
> consistent with multi-architecture development.  In short, instead of
> arguing here, let's try to learn to work together on this.

I agree, although I'd like to know exactly what in Policy is
anti-porter, and how, specifically, we can improve the process and the
quality of the ports.

What parts of policy are unfriendly to porters?  I will personnally do
my utmost to correct and bugs in Policy, if you could point me to the
actual sections which have the problems.

> Ideally, ALL maintainers would have access to a machine of every arch
> to compile their own packages on it, but I still have a feeling that
> alot of maintainers wouldn't bother compiling their packages on any
> other arch than x86.

I'd love to be able to do this, as an x86 maintainer.  Are the
accounts available to x86-maintainers on other boxes?  How do x86
maintainers go about getting such an account?  I'd be happy to add
this information to the Developer's Reference, if you can give me some
information.

> > Why are the different?  Aside from Binary-only apparantly breaking
> > current policy?

Where in policy does it state this?  I've seen this claim put forth
many times but I don't see any section of Policy that states this.  I
think Policy is broken if it does state this, but I'm sure that's a
controversial claim.

> > The only think that I know of that makes ports second-class citizens is
> > you claiming that because you are different, you should follow
> > different rules.
> > I don't think Joey is anti-non-i386, but that he instead wants everyone
> > to play by the same rules.

IMHO, Porters do have slightly different rules, because their duties
as packagers are so radically different from the duties of normal
package maintainers.  Maintaining a port *is* different from
maintaining just one package for one architecture.  We have to realize
this, and allow for it.

> I think that other archs ARE being treated like second-class citizens in
> more regards than just NMUs.  I *wish* I had more interest from
> maintainers as to whether their packages compile ok on Alphas or not.
> To date, I've only had three maintainers actually ask me to test build
> their packages on Alphas and run some tests (which they provided)
> to make sure things worked ok.  I was more than willing to do this.
> However, on the flip side, I've also received feedback from a couple of
> maintainers that basically said that they don't really care about us.

I'll try to add some stronger wording about porting and why
maintainers *must* care about them if they're going to maintain a
package.  We can't force people to care, but if they don't care, maybe
they shouldn't be a Debian maintainer at all?

> In short, if *you* think the current rules are multi-arch-friendly, then
> I might as well stop porting to the Alpha totally.  Like it or not,
> other archs have to get some latitude because of the problems that come
> with being on a machine that most maintainers DON'T have access to.

No, but I'd like to know specific steps we can take to fix this.

> Hey, if you really want, I can start dbuild on the master archive and
> just forward all of the build reports to the main maintainers.  If it
> doesn't build, it doesn't build.  It would then be up to the maintainer
> to fix it a billion times until it passed a dbuild (because most
> maintainers don't know the quirks of other archs), and in the meantime,
> the other arch ports NEVER get released.
> 
> Is that a better solution?  I hope you don't think it is

Definately not.  Maybe it would be a good idea if we had
source-depends though.  AFAIK, the lack of source-depends is one of
the most annoying problems that porters have to deal with.  Do you
think we could add an extra field to control files to get this going?
Just so long as it was understood by dbuild, we would be in pretty
good shape to start getting source-depends working.  Then we could
require that field by Policy... ?

(Yes, I know this is a complex issue, but I'd like to see interest in
this functionality revived.)

> > A source package which doesn't compile out-of-the-box in the standard
> > Debian environment (egcs2.9, gcc2.7, libc6/libc++2.9, binutils2.9, etc
> > for i386, glibc2.1 plus whatever compiler/libraries/binutils is used
> > for m86k, and so forth) has a bug -- unless it is specifically
> > architechture dependent. 

Well, sometimes it requires other programs to be installed, like
debiandoc-sgml.  This is not a bug in the package, really.

> > It's not a bug with the m68k version only,
> > it's a bug, plain and simple.  If it fails on m68k because the
> > maintainer unconsiously thought that All The World's 

apt: small download

[Bernd Eckenfels]

Hello,

I would like to see a possibility to stop apt-get from downloading all
necessarry packages. Eighter by breaking the download (like it is possible
with dpkg-ftp ^c) or by giving the amount of files i want to download.

This will give me the possibility to upgrade my system even with a small
cache and with less impact on the cpu resources.

Greetings
Bernd
-- 
  (OO)  -- [EMAIL PROTECTED] --
 ( .. )  [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/
  o--o *plush*  2048/93600EFD  [EMAIL PROTECTED]  +497257930613  BE5-RIPE
(OO)   If privacy is outlawed only Outlaws have privacy

Re: Bug with xv?

[Jaakko Niemi]

>> 
>> Hi all,
>> 
>> I was just working away on my machine, and using xv to display the latest
>> results from my raytracing project.  The pic came out too small, and so I
>> went to press shift '>' to zoom it up, only I missed and hit shift '<'.
>> 
>> Low and behold my xserver crashed.
>> 
>> I've since tested and found that if you open xv, and press shift '<'
>> continually until the window becomes small enough, the xserver dies.
>> 
>> Can anyone else verify this?
>> 
>> I am running XF86_SVGA server, at 1280x1024 res, 16-bit.  I am running
>> slink and have updated everything to the latest releases.

 Are you sure it is the X server that crashed, and not the window-manager ?
 I cannot reproduce this with slink X packages and fvwm2. Same server, reso-
 lution and color-depth (Matrox Millenium I 4mb).

--j

Re: moving mutt-i from non-us to main

[Bart Schuller]

People,

The fact that there even exist two debian versions of mutt should tell
you that it was an issue for people. Looking through the changelogs, I
see that mutt was moved to non-US in Feb. 1997:

mutt (0.61.1-1) unstable; urgency=low

  * New upstream release. 
  * Now non-US. (Bug #7257)

 -- J.H.M. Dassen <[EMAIL PROTECTED]>  Tue, 11 Feb 1997 14:15:27 +0100

Has anything changed since then, or do we have a too short collective
memory?

-- 
The idea is that the first face shown to people is one they can readily
accept - a more traditional logo. The lunacy element is only revealed
subsequently, via the LunaDude. [excerpted from the Lunatech Identity Manual]

Intent to package sart and panorama

[Ole J. Tetlie]

Sart is a ray-tracer written in Scheme.

Panorama is a framework for 3D graphics production from GNU.

None of them are finished, but they could be quite useable before
our next release.

-- 
The only way tcsh "rocks" is when the rocks are attached to its feet
in the deepest part of a very deep lake. (Linus Torvalds)
[EMAIL PROTECTED]   [-: .elOle. :-]   [EMAIL PROTECTED]

Is rvplayer working for others?

[Rob Browning]

I've installed the rvplayer package, but even something as simple as

  rvplayer /usr/doc/rvplayer/examples/welcome.rm

doesn't work.  The app comes up, and then it just sits there.  Does
this work for others?  (verson 5.0-6)

Thanks

-- 
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930

Re: moving mutt-i from non-us to main

[Joseph Carter]

On Sat, Oct 17, 1998 at 09:55:48PM +0200, Bart Schuller wrote:
> People,
> 
> The fact that there even exist two debian versions of mutt should tell
> you that it was an issue for people. Looking through the changelogs, I
> see that mutt was moved to non-US in Feb. 1997:
> 
> mutt (0.61.1-1) unstable; urgency=low
> 
>   * New upstream release. 
>   * Now non-US. (Bug #7257)
> 
>  -- J.H.M. Dassen <[EMAIL PROTECTED]>  Tue, 11 Feb 1997 14:15:27 +0100
> 
> Has anything changed since then, or do we have a too short collective
> memory?

The bug was filed probably because it seemed likely that it was the easiest
and safest course.  Some of us in the world (or at least in the US) believe
we should have taken a stand long ago.

There is no crypto hook in mutt that does not exist in bash or worse, in
perl which can also read PGP key files just like mutt can.  Are they non-us
too?


pgp6Sz5QLgeHH.pgp
Description: PGP signature

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[Dave Swegen]

> On Sat, 17 October 1998 11:10:10 -0400, Dirk Eddelbuettel wrote:
> >   john>  I'd still like to use penguins.
> > Indeed, that was the best proposal yet.

Cool, a linux named Opus. Can it get better?

Cheers
Dave

Re: moving mutt-i from non-us to main

[john]

Bart Schuller writes:
> Has anything changed since then, or do we have a too short collective
> memory?

I had always assumed that everything in non-us contained encryption code,
as do the few things in it that I have actually used.
-- 
John HaslerThis posting is in the public domain.
[EMAIL PROTECTED]  Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.

something is f***ed

[Stephen Crowley]

Ok, i just apt-get upgraded about an hour ago, to my horror i can no
longer login, nor can I su, it just sits there doing nothing. I
also cannot telnet to localhost. Someone on irc just upgraded also and got
the exact same problem. What is going on!?


-- 
Stephen Crowley
Debian GNU/Linux Developer 
--


pgpNutPIpUfen.pgp
Description: PGP signature

Re: What Bruce had to say about non-Pixar names. Re: what's after slink

[Jeff Noxon]

On Sat, Oct 17, 1998 at 09:57:50PM +0100, Dave Swegen wrote:
> > On Sat, 17 October 1998 11:10:10 -0400, Dirk Eddelbuettel wrote:
> > >   john>  I'd still like to use penguins.
> > > Indeed, that was the best proposal yet.
> 
> Cool, a linux named Opus. Can it get better?

Chilly Willy was another famous cartoon penguin.

Regards,

Jeff

--
It's time to close windows and open source.
Linux is a trademark of Linus Torvalds.

Re: something is f***ed

[Stephen Crowley]

I found out the problem is in sysklogd, not sure what is going on though.

-- 
Stephen Crowley
Debian GNU/Linux Developer 
--


pgp8zboM3TGbD.pgp
Description: PGP signature