Since we know of a number of things that have been broken in 2.0.30
(such as IP masquerading being totally hosed), why are we distributing
that version with 1.3? It seems like a rather bad idea because it
could very well break the setups of a number of people.
--
John Goerzen | Running
Vincent Renardias <[EMAIL PROTECTED]> writes:
> On 21 May 1997, Darren/Torin/Who Ever... wrote:
>
> > 2. The man-pages and html-docs would go into a separate perl-doc
> >package.
>
> I agree for the html docs, but I think each manpage should go into the
> package containing the feature it d
Joey Hess <[EMAIL PROTECTED]> writes:
> This all seems ok except for maybe the export restrictions section. We don't
> have a non-Cuba-Yugoslavia-Hati-Iran-Iraq-North-Korea-and-Syria section like
> we have a non-us section.. so does abuse belong in non-free or on some
> us-only ftp site, or what?
Jim Pick:
> > Restrictions :
> >Crack dot Com retains ownership of the Abuse Trademark and data sets.
>
> What does data sets mean?
I think it means the levels, sounds, artwork, etc that the abuse engine
uses.
> Sounds like the libs can go into the free section. Cool.
If by "libs" you mea
Helmut Geyer <[EMAIL PROTECTED]> writes:
> based on | package name| hierarchy locations
> ---
> libc6 | libfoo-dev | /usr/{lib,include}
> libc5 | libfoo-libc5-altdev | /usr/i486-linuxlibc1
> Crack dot Com has decided to release abuse as public domain software. So no
> more a.out abuse, once I get the new one built. But I do have a couple of
> questions about their copyright:
>
> This release is to the public domain, meaning there are very few
> restrictions in on use. But here a
In article <[EMAIL PROTECTED]>,
Brian White <[EMAIL PROTECTED]> wrote:
>***
>** **
>** Debian 1.3 Release Candidate
Crack dot Com has decided to release abuse as public domain software. So no
more a.out abuse, once I get the new one built. But I do have a couple of
questions about their copyright:
This release is to the public domain, meaning there are very few
restrictions in on use. But here are a few :
[EMAIL PROTECTED] wrote on 19.05.97 in <[EMAIL PROTECTED]>:
> Basically, mailx conflicts with smail.
>
> dpkg: error processing xmysql (--configure):
> dependency problems - leaving unconfigured
> Setting up smail (3.2-3) ...
> Error: system's FQDN hostname (citytel_prct40.citytel.net) doesn't m
On Wed, 21 May 1997, Tim Sailer wrote:
> Can someone verify that this is a problem? I installed ssleay and ssltelnet,
> and when ssltelnet ripped through the install, it never paused for me
> to enter the info for the certificate.. This is what it looked like:
>
> Generating a 512 bit private
> > (looks like we beat Red Hat, go figure...)
>
> Much more CDs of RedHat have probably been sold than Debian CDs, and
> people installing from CDs may not have internet access and not register
> with the linux counter? Also that's only statistics...
I just thought it was neat. Anyways, the
On Wed, 21 May 1997, Jim Pick wrote:
> This might be a mini-project for someone:
>
> I'd like to see a graph of the total number of bugs, number of open bugs
> plotted on a graph vs. the date. Perhaps superimposing the release dates
> on it too.
Sure! I'd love to see that. _(;
(Quick s
I dont care how the prompt looks. Just pick one and dont leave it the way
it is. Who is the maintainer of the package in question? Let him decide.
On Wed, 21 May 1997, Chris Fearnley wrote:
>'=?iso-8859-1?Q?Nicol=E1s_Lichtmaier?= wrote:'
>>
>> So I say: PS1="[\\u] \\h:\\w\\$ " =D
>
>No, PS1
'=?iso-8859-1?Q?Nicol=E1s_Lichtmaier?= wrote:'
>
> So I say: PS1="[\\u] \\h:\\w\\$ " =D
No, PS1='[EMAIL PROTECTED]:\w\$ ' !
I guess this will become a flame war. So I'd prefer to leave prompt
alone. Or maybe the boot disks can have a dialog script to help the
user choose a prompt?
--
Vincent Renardias <[EMAIL PROTECTED]> writes:
> I think perl-base should not be Essential, since it will be replaced
> anyway once the installation completes. "perl" should be essential though.
> (Or can "essential" packages be replaced by dpkg?)
I think maybe you misread the proposal. Under th
> libc6 | libfoo-dev | /usr/{lib,include}
> libc5 | libfoo-libc5-dev| /usr/{lib,include}
I still have trouble with this. There is already a
libc5 | libfoo-dev| /usr/{lib,include}
for each libfoo out there. When people upgrade from 1.3->2.0, what's
*s
This might be a mini-project for someone:
I'd like to see a graph of the total number of bugs, number of open bugs
plotted on a graph vs. the date. Perhaps superimposing the release dates
on it too.
It would be cool if we could somehow track the number of machines/users we
had too.
I checked
'Karl M. Hegbloom wrote:'
>
>Since the output from cron jobs is mailed anyhow, as it should be, I
>think that all cron scripts should report in as they are run, and that
>this should be made a standard. Here's why.
But if they complete successfully they should be quiet. Maybe this
would work:
s
On 21 May 1997, Darren/Torin/Who Ever... wrote:
> 1. Split the main executable and a small set of base files into
>perl-base. This would be Priority: required, should it be Essential?
>There will still be a main Perl package but it would supplement
>perl-base instead of replacing it.
On Wed, 21 May 1997, Tim Sailer wrote:
> In your email to me, Jim Pick, you wrote:
> > > In case you're interessed, I just got the acknowledgement of bug report
> > > #1 (which happen to be a documentation buglet in package qt-doc).
> > > *cracks open a virtual beer* _(;
> > >
> > > Out o
In your email to me, Jim Pick, you wrote:
>
> --==_Exmh_1577184704P
> Content-Type: text/plain; charset=us-ascii
>
>
> >
> > In case you're interessed, I just got the acknowledgement of bug report
> > #1 (which happen to be a documentation buglet in package qt-doc).
> > *cracks open a virt
>
> In case you're interessed, I just got the acknowledgement of bug report
> #1 (which happen to be a documentation buglet in package qt-doc).
> *cracks open a virtual beer* _(;
>
> Out of those ~1 bug reports, about 2200 are still outstanding.
Congratulations.
BTW, if you believe th
Can someone verify that this is a problem? I installed ssleay and ssltelnet,
and when ssltelnet ripped through the install, it never paused for me
to enter the info for the certificate.. This is what it looked like:
Generating a 512 bit private key
+
..+
wr
Brian Mays <[EMAIL PROTECTED]> writes:
> The rxvt authors claim that programs such as JED, slrn, Midnight
> Commander check this variable. I don't know since I don't use any of
> these applications.
These are all programs that don't use the standard ncurses interface,
I believe. As such, they a
[EMAIL PROTECTED] (Brian C. White) writes:
> *** ***
> *** Release of Bo is HOLDING for CRITICAL BUGS!***
> *** ***
> *** There is one remaining c
In case you're interessed, I just got the acknowledgement of bug report
#1 (which happen to be a documentation buglet in package qt-doc).
*cracks open a virtual beer* _(;
Out of those ~1 bug reports, about 2200 are still outstanding.
Cordialement,
--
- ** Linux ** +
Did anyone make sure that this is really a bug? In all my testing I did
not encounter this. The upgrade I did yesterday did not show anything.
Reputation: We are just confirming our bad reputation in not being able to
get things out of the door...
There are still nasty bugs in bo that will probab
>Generally, after installing any system, I add this to ~/.profile for
>root:-
>
>alias rm="/bin/rm -i"
This is a BAD thing to do. If you want this use a different name, like:
alias del="/bin/rm -i"
Otherwise it is all too easy to get into the habit of doing
rm *
and picking the ones you w
On Tue, 20 May 1997, Enrique Zanardi wrote:
> On Tue, 20 May 1997, Nicol=E1s Lichtmaier wrote:
>
> > I think that this is the kind of thinking that is killing Debian.
> >=20
> > 1) Newbie setting doesn't mean annoying settings.
> > 2) `real men' like you can change those settings.
> > 3) Conf
I can put that into the chris-cust package ...
On Tue, 20 May 1997, Tom Lees wrote:
>On Mon, 19 May 1997, Christoph Lameter wrote:
>
>> >Anybody should know that before typing "rm -rf *" or an equivolent,
>> >you THINK FIRST, every time.
>>
>> The problem does not arise when you type rm the firs
On Mon, 19 May 1997, Christoph Lameter wrote:
> >Anybody should know that before typing "rm -rf *" or an equivolent,
> >you THINK FIRST, every time.
>
> The problem does not arise when you type rm the first time but after you
> have some confidence and you think you know what you are doing.
>
>
-BEGIN PGP SIGNED MESSAGE-
On Wed, 21 May 1997, Bruce Perens wrote:
> There's something like /etc/inittab.real, diff it against inittab.
> This is a result of a failure in an installation script that should
> have moved inittab.real to inittab . Probably you control-C-ed out of
> the root
Christoph Lameter <[EMAIL PROTECTED]> writes:
> Have a look at the bug report. I dont know why no one has marked it as
> done yet. There is a file lists in the but report ending in .dpkg-tmp
> evidently from a crash. Dont be buerocratic about releasing 1.3.
Brian should resist releasing 1.3 if a
[EMAIL PROTECTED] (Brian Mays) wrote on 20.05.97 in <[EMAIL PROTECTED]>:
> I would not advocate implementing such a package this way. Most of
> the config files that we would be interested in fixing for newbies can
> include or source another file. Take sh-like shells for example. We
> would h
On May 21, Darren/Torin/Who Ever... wrote
> I'd really appreciate your input on these issues, so that I can go
> forward with the Perl package.
Don't let this slow down your work, but: one thing I've been
itching for is a mechanism for CPAN installation to interoperate
with the Debian package mana
On May 20, Buddha Buck wrote
> Even with this, I can't get it to work. I'm running into the same
> problem Mr. Hess reported. Using dir: /debian dist: unstable, I have
> been able to get hamm, but no combination I've tried has allowed me to
> get hamm/non-free or hamm/contrib. I can get the p
-BEGIN PGP SIGNED MESSAGE-
I have some ideas on what I'm planning on doing with the Debian Perl
package in the near future.
1. Split the main executable and a small set of base files into
perl-base. This would be Priority: required, should it be Essential?
There will still be a mai
Darren/Torin/Who Ever... wrote:
> Actually, as opposed t a security measure, I would've found something
> like this useful as a backup-check measure.
>
> I had a nasty head-crash last week. Thankfully, I had recent backups.
> Unfortunately, I had upgraded a number of packages after the latest
> b
-BEGIN PGP SIGNED MESSAGE-
Chris Fearnley, in an immanent manifestation of deity, wrote:
>'Amos Shapira wrote:'
>>many "use tripwire" answers, and one which says that RPM has a verify
>>mode which checks for files which were changed since they were
>
>What does the rpm verify give you? As
> "John" == John Goerzen <[EMAIL PROTECTED]> writes:
John> I don't think Debian is really aiming at newbies. (RedHat
John> is) Debian is aiming at the power user or admin type -- the
John> people that already know Unix.
But you have to consider the case of an ISP that wants to u
...
>based on | package name | library location
>
> libc6 | libfoo | /usr/lib/libfoo.so.
> libc5 | libfoo-libc5 | /usr/lib/libc5-compat/libfoo.so.
>
...
> based on | package name| hierarchy loc
Hi,
> Presumably, you installed xdm after installing shadow. shadowconfig edits
> /etc/init.d/xdm to switch between using xdm and xdm-shadow, so all you need
> to
> do is:
>
> shadowconfig off
> shadowconfig on
>
> and all should be well.
Yes, thank you!
But I think, the xbase package
Hi,
>>"SirDibos" == <[EMAIL PROTECTED]> writes:
SirDibos> On Tue, 20 May 1997, Mike Orr wrote:
SirDibos> You are right. However, what solution do you suggest in my
SirDibos> case, where I have 6 different kernels cluttering up my / ?
SirDibos> I use all of em, 1 is a backup, some implement di
Hi,
I got it by applying this patch posted a couple of weeks ago
by Tomislav Vujec <[EMAIL PROTECTED]>:
Tomislav> If you're using dselest's ftp method (dpkg-ftp), you'll need
Tomislav> this small patch, which I included in bug report 8762 for
Tomislav> dpkg-ftp:
--- /usr/lib/dpkg/metho
=?iso-8859-1?Q?Nicol=E1s_Lichtmaier?= <[EMAIL PROTECTED]> writes:
> I see a `config package' as a package that includes/modifies other
> packages conffiles. Using packages for this is ignoring the concept of a
> package. What if you remove one of these packages? What if some programs
> whose file
Hi Folks!
The late discussion here on migration to libc6 indicates that a
statement on the requirements of library run time and development
packages is to be included in the policy manual. This is how I recall
the discussion we had about this topic some weeks ago. It might be
that I am a little b
On Tue, 20 May 1997, Mike Orr wrote:
> It should be copied, and not symlinked. /boot must not have any symlinks
> into /usr, in case /usr is trashed and you're trying to recover.
>
> If the symlink went the other way, from /usr/src/linux/.config into
> /boot/.config, then "make config" would b
> Joey Hess <[EMAIL PROTECTED]> writes:
>
> > dpkg-ftp downloads the Packages files ok using this, but when I go to
> > download, it can't find the files:
>
> Actually you should use
>
> distribution base: .../debian/dists/unstable
> section list: main non-free contrib
>
> Use unstable or froze
On Mon, 19 May 1997 [EMAIL PROTECTED] wrote:
> Just, let it be symlinked to
> /usr/src/linux/.config too, ok? =)
It should be copied, and not symlinked. /boot must not have any symlinks
into /usr, in case /usr is trashed and you're trying to recover.
If the symlink went the other way, from /us
Gregor Hoffleit wrote:
>
> > Include the multi-thread support patch for the Objective-C runtime lib (???)
>
> bo includes gstep-base-0.2.12 and gstep-base-0.2.12 includes a patch file
> gcc-2.7.2.1-objc.diff, which therefore should be applied to the gcc in bo
> (the patch applies fine to gcc-2.7.
50 matches
Mail list logo
