Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 1914
Today's Topics:
Re: How to check if a DVD is damaged [ Brad Rogers ]
Using apt-zip -was Re: Upgrade on bo [ Felix Karpfen ]
Re: BAD Error Installing new Apache2 [ Andrew Sackville-West ]
mutt folder browser broken? [ Andrew Sackville-West ]
Date: Sat, 7 Jul 2007 22:06:01 +0100
From: Brad Rogers <brad@fineby.me.uk>
To: debian-user@lists.debian.org
Subject: Re: How to check if a DVD is damaged?
Message-ID: <20070707220601.202e40ad@abydos.stargate.org.uk>
Content-Type: multipart/signed; boundary="Sig_jZjJwiJn=mlf=mOBQW4QI+Q";
protocol="application/pgp-signature"; micalg=PGP-SHA1
--Sig_jZjJwiJn=mlf=mOBQW4QI+Q
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Sat, 7 Jul 2007 20:46:06 +0000
"Manon Metten" <manon.metten@gmail.com> wrote:
Hello Manon,
> Right. You could also consider using GSpace. That's what I do with
You are joking, right? GSpace depends *entirely* on the goodwill of
Google. GSpace isn't endorsed by Google, and can disappear without
warning, if Google make any (un)suitable changes to their system. Even
the people that created it don't place that much faith in it. This
taken from their "Legal issues";
<quote>
This extension may be discontinued at any point. we shall not be held
responsible for the discontinuation of this extention.
</quote>
For that reason alone I wouldn't consider it even as a tertiary backup.
It wouldn't be quite so bad if it were a paid for solution, but even
they are subject to problems of control. Or rather, lack of it, from
the user's point of view.
--=20
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
A friend of a friend he got beaten
I Predict A Riot - Kaiser Chiefs
--Sig_jZjJwiJn=mlf=mOBQW4QI+Q
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGkAA8SXvR9Iq2E38RAn/6AJ4zT/dN0yruA92+Tfdoxg7MbX81qACgj9Ac
f3wCKmAf1yvJ4vjqykJLw/I=
=cAk+
-----END PGP SIGNATURE-----
--Sig_jZjJwiJn=mlf=mOBQW4QI+Q--
Date: Sat, 7 Jul 2007 20:58:55 +0000 (UTC)
From: Felix Karpfen <felixk@webone.com.au>
To: debian-user@lists.debian.org
Subject: Using apt-zip -was Re: Upgrade on box not on Net
Message-ID:
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Thu, 05 Jul 2007 16:02:44 -0400, Celejar wrote:
> On Thu, 5 Jul 2007 20:25:09 +0100
> John K Masters <johnmasters@oxtedonline.net> wrote:
>=20
>> Is it possible to upgrade a box not connected to the Internet?
>>=20
>=20
> This is what the apt-zip package is for.
2 simple queries:
- ZIP drives are a thing of the past. Presumably apt-zip works equally
well with usb memory-sticks; and
- My daughter - who has broadband access - uses a Mac. Can that be
used to download the packages identified by apt-zip?
Felix Karpfen
--=20
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)
Date: Sat, 7 Jul 2007 22:46:31 +0200
From: Florian Kulzer <florian.kulzer+debian@icfo.es>
To: debian-user@lists.debian.org
Subject: Re: Cannnot authenticate debian archive packages
Message-ID: <20070707204631.GA7834@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
[ Please do not top-post. ]
On Sat, Jul 07, 2007 at 14:31:56 +0530, Bhasker C V wrote:
> Hi all,
>
> I have similar problem.
> The only thing is that instead of installing from DVD, i put the DVD
> images on to a server which loop-back mounts the DVD. I have added
> the local server address to the sources.list.
> But on the Etch DVD there is no Release.gpg file.
> Now, how can i avoid the authetication warning without using
> APT::Get::AllowUnauthenticated 1
How did you add the mounted DVD image to your sources.list? Did you use
"file:" URIs?
man sources.list | egrep 'deb(-src)? file'
> OR
>
> can i download the GPG keys from the etch website and then have it> installed in my machine so that i can avoid the authentication > warning ? If so can someone point me to the website and the method> to import the keys
--
Regards, |
http://users.icfo.es/Florian.Kulzer
Florian |
Date: Sat, 7 Jul 2007 17:06:57 -0400
From: Douglas Allan Tutty <dtutty@porchlight.ca>
To: debian-user@lists.debian.org
Subject: Re: lenny comfortable yet?
Message-ID: <20070707210657.GA12223@titan>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Thanks all for your input.
I may brave Lenny soon, but I think I've decided (I may change my mind)
to give the chroot option from the amd64-HOWTO a try. Its probably not
much more hastle as upgrading to Lenny but then it should (hope) just
work from then on.
Doug.
Date: Sat, 7 Jul 2007 21:30:01 +0000
From: "Manon Metten" <manon.metten@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: How to check if a DVD is damaged?
Message-ID: <5da176070707071430i6440f536u7f847b380c02b387@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_50390_15338535.1183843801794"
------=_Part_50390_15338535.1183843801794
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Brad,
On 7/7/07, Brad Rogers <brad@fineby.me.uk> wrote:
> Right. You could also consider using GSpace. That's what I do with
>
> You are joking, right? GSpace depends *entirely* on the goodwill of
> Google. GSpace isn't endorsed by Google, and can disappear without
> warning, if Google make any (un)suitable changes to their system. Even
> the people that created it don't place that much faith in it. This
> taken from their "Legal issues";
>
> <quote>
> This extension may be discontinued at any point. we shall not be held
> responsible for the discontinuation of this extention.
> </quote>
>
> For that reason alone I wouldn't consider it even as a tertiary backup.
Even if GSpace is discontinued, I can download the uploaded data by
accessing my gmail account. So, for a secondary backup, apart from
backups on cd/dvd, it will do for me. And I cannot anticipate on Google
(dis)continuing gmail etc. For the unlikely case that my house burns
down and Google discontinuing gmail on the same day ... But then
again, maybe tonight the ceiling will come down ... (if you know what I
mean).
Manon.
------=_Part_50390_15338535.1183843801794
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Brad,<br><br><div><span class="gmail_quote">On 7/7/07, <b class="gmail_sendername">Brad Rogers</b> <<a href="mailto:brad@fineby.me.uk">brad@fineby.me.uk</a>> wrote:<br></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Right. You could also consider using GSpace. That's what I do with<br><br>You are joking, right? GSpace depends *entirely* on the goodwill of<br>Google. GSpace isn't endorsed by Google, and can disappear without
<br>warning, if Google make any (un)suitable changes to their system. Even<br>the people that created it don't place that much faith in it. This<br>taken from their "Legal issues";<br><br><quote><br>
This extension may be discontinued at any point. we shall not be held<br>responsible for the discontinuation of this extention.<br></quote><br><br>For that reason alone I wouldn't consider it even as a tertiary backup.
</blockquote><div><br><br>Even if GSpace is discontinued, I can download the uploaded data by<br>accessing my gmail account. So, for a secondary backup, apart from<br>backups on cd/dvd, it will do for me. And I cannot anticipate on Google
<br>(dis)continuing gmail etc. For the unlikely case that my house burns<br>down and Google discontinuing gmail on the same day ... But then<br>again, maybe tonight the ceiling will come down ... (if you know what I<br>mean).
<br><br>Manon.<br><br></div></div>
------=_Part_50390_15338535.1183843801794--
Date: Sat, 7 Jul 2007 16:43:19 -0500
From: ArcticFox <genkokitsu@insightbb.com>
To: debian-user@lists.debian.org
Subject: Re: Enabling SFTP under Debian 4.0r0
Message-Id: <92440871b39ea42453d3f684a81c782b@insightbb.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
On Jul 7, 2007, at 1:29 PM, Bob Proulx wrote:
> ArcticFox wrote:
>> Kent West wrote:
>>> Again, what happens when you attempt to connect from/to the same
>>> Linux box?
>>
>> Both the remote terminal and local terminal give the same error.
>> (Request for subsystem... blah blah blah)
>
> Yes. Please debug this on the local host first. That will be much
> simpler.
>
> Try it again on the local host and show us the error output.
>
> ssh -v localhost
>
> And then again with sftp.
>
> sftp -v localhost
>
> Also show us the entire /etc/ssh/sshd_config file.
>
>
Ok, here's ssh -v localhost:
foxpaws:/home/fox# ssh -v localhost
OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version lshd-2.0.2
lsh - a GNU ssh
debug1: no match: lshd-2.0.2 lsh - a GNU ssh
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client 3des-cbc hmac-md5 none
debug1: kex: client->server 3des-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'localhost' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: password,publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password
root@localhost's password:
debug1: Authentications that can continue: password,publickey
Permission denied, please try again.
root@localhost's password:
And here's sftp:
foxpaws:/home/fox# sftp -v localhost
Connecting to localhost...
OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version lshd-2.0.2
lsh - a GNU ssh
debug1: no match: lshd-2.0.2 lsh - a GNU ssh
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client 3des-cbc hmac-md5 none
debug1: kex: client->server 3des-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'localhost' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: password,publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password
root@localhost's password:
debug1: Authentications that can continue: password,publickey
Permission denied, please try again.
root@localhost's password:
and here's /etc/ssh/sshd_config:
# Package generated configuration file
# See the sshd(8) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will
bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for
RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues
with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
UsePAM yes
Date: Sat, 7 Jul 2007 23:38:52 +0100
From: Dale Stephens <dsstephens@ukfsn.org>
To: debian-user@lists.debian.org
Subject: Re: Possible problems with kscreensaver in Lenny?? [solved]
Message-Id: <200707072338.52492.dsstephens@ukfsn.org>
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Saturday 07 July 2007 19:01, Dale Stephens wrote:
> Hello all,
>
> After recent updates of kde from v3.5.5 to v3.5.7 on Lenny, my kscreensav=
er
> seems to have stopped working completely. =A0Also, Control Centre crashes
> when I try to access the Screen Saver section in Appearance and Themes (b=
ut
> seems OK elsewhere). =A0
>
> I have not altered the config at all before/during/after the updates.
> =A0Also, other KDE programs seem to run normally.
>
> Is anyone else having these problems, or is it just me?
>
> Regards,
>
> Dale Ess
Please disregard this topic. The problem seems to have solved itself. =20
Date: Sat, 07 Jul 2007 15:48:14 -0700
From: Jim McCloskey <mcclosk@ucsc.edu>
To: debian-user@lists.debian.org
Subject: Re: nvidia-kernel package: compilation failure with 2.6.21
Message-Id: <1183848494.7112.10.camel@localhost.localdomain>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hugo Vanwoerkom <hvw59601@care2.com> wrote:
|> Extensively discussed here:
|> http://www.nvnews.net/vbulletin/showthread.php?t=90214
|>
|> The problem is that post 2.6.18 Debian kernels have PARAVIRT_CONFIG
|> and nvidia does not like that.
|>
|> You can either rebuild the kernel and turn that off (Note: but in
|> that case I had hard hangs in qemu!) *or* use the descriptions
|> in that page to rebuild the kbuild .deb and install nvidia so it does
|> not mind paravirt.
|>
|> You'll hit the problem both with m-a *and* the nvidia installer.
Thanks very much to all of you who responded---all interesting and all
helpful. I've compiled a new kernel with PARAVIRT_CONFIG turned off.
I'll reboot into the new kernel on Monday morning (I need to be at the
keyboard in case something goes wrong) and try again with the nvidia
kernel module.
In the meantime I'm very grateful to you all,
Jim
Date: Sat, 7 Jul 2007 16:51:16 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: BAD Error Installing new Apache2 & PHP?
Message-ID: <20070707235116.GA15316@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline
--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jul 06, 2007 at 03:40:27PM -0700, Aikins, Ronald (Ron) (CIV) wrote:
> Andrew,
>=20
> You may have forgotten this thread. Thanks for your previous
> suggestions.=20
>=20
> (BTW, your domain made me curious. Spokane, eh? I spent a very hot 4
> days up there a few years ago attending a BMW motorcycle rally. From
> what I see on the weather map, you're steamin' again!)
yep. plenty hot. might have to invest in AC which is a luxury around
here...
>=20
> I'm currently running 'sarge' & am trying to upgrade to the latest in
> sarge before upgrading to 'etch'. The problems I'm having doing this
> make me reluctant to try & jump straight to etch before I get this
> install worked out.
I heartily suggest you follow Florian's advice. He knows what he's
talking about.=20
A
--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGkCb0aIeIEqwil4YRAoK+AJ4kgFtk89qNXJcjNUzqaaKzFPsM9QCglMUj
xSSe/YZP6ImD3j8czIVWOnQ=
=xtkl
-----END PGP SIGNATURE-----
--wRRV7LY7NUeQGEoC--
Date: Sat, 7 Jul 2007 18:19:27 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: Enabling SFTP under Debian 4.0r0
Message-ID: <20070708001927.GA8128@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
ArcticFox wrote:
> foxpaws:/home/fox# ssh -v localhost
> OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
So far so good.
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Applying options for *
> debug1: Connecting to localhost [127.0.0.1] port 22.
> debug1: Connection established.
> debug1: permanently_set_uid: 0/0
> debug1: identity file /root/.ssh/identity type -1
> debug1: identity file /root/.ssh/id_rsa type -1
> debug1: identity file /root/.ssh/id_dsa type -1
> debug1: Remote protocol version 2.0, remote software version lshd-2.0.2 lsh - a GNU ssh
> debug1: no match: lshd-2.0.2 lsh - a GNU ssh
Where did that come from? Do you have lsh-server installed instead of
openssh-server?
A stock Etch machine with openssh-server would respond here with the
following:
debug1: Remote protocol version 1.99, remote software version OpenSSH_4.3p2 Debian-9
debug1: match: OpenSSH_4.3p2 Debian-9 pat OpenSSH*
Bit it looks to me that you are not using OpenSSH at all but are
instead using lsh-server.
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9
> debug1: An invalid name was supplied
> Configuration file does not specify default realm
>
> debug1: An invalid name was supplied
> A parameter was malformed
> Validation error
>
> debug1: An invalid name was supplied
> Configuration file does not specify default realm
>
> debug1: An invalid name was supplied
> A parameter was malformed
> Validation error
Those look scary but ignore them for now. They are not related to
your present problem. This is related to GSSAPI Authentication.
> and here's /etc/ssh/sshd_config:
The sshd_config file looks perfectly good and normal to me. However
I believe you are not using it and are instead using the lsh-server.
Bob
Date: Sat, 07 Jul 2007 20:20:38 -0400
From: "H.S." <hs.samix@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: tetex and texlive: changes in Debian?
Message-ID: <f6palk$gss$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
H.S. wrote:
>
> Same here. From all the texlive packages that are to be intall, there at
> least a few tetex package still, e.g. tetex-bin tetex-extra.
>
> These packages I would expect to be purged by aptitude automatically (by
> reporting they are no longer used) some time "soon".
>
> ->HS
>
Just now did an update and upgrade and a huge bunch of texlive packages
are to removed because they 'are unused':
$> sudo aptitude dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages are unused and will be REMOVED:
preview-latex-style texlive-bibtex-extra texlive-font-utils
texlive-fonts-extra texlive-generic-extra texlive-lang-croatian
texlive-lang-cyrillic texlive-lang-czechslovak texlive-lang-danish
texlive-lang-dutch texlive-lang-finnish texlive-lang-french
texlive-lang-german texlive-lang-greek texlive-lang-hungarian
texlive-lang-italian texlive-lang-latin texlive-lang-mongolian
texlive-lang-norwegian texlive-lang-other texlive-lang-polish
texlive-lang-portuguese texlive-lang-spanish texlive-lang-swedish
texlive-lang-vietnamese texlive-latex-extra texlive-math-extra
texlive-pictures texlive-publishers texpower texpower-manual
0 packages upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 400MB will be freed.
Do you want to continue? [Y/n/?]
Hmm ... maybe things are settling down after all.
->HS
>> (except for a
>> few camera / photo packages that are still only partially installed).
>>
>>
>> Tyler
>>
>>
>>
>
>
Date: Sat, 7 Jul 2007 17:41:13 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: mutt folder browser broken?
Message-ID: <20070708004112.GA15565@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV"
Content-Disposition: inline
--HcAYCG3uE/tztfnV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Anyone else seeing weird behavior with the mutt folder browser?=20
mine no longer shows the message count (imap mailboxes) or mbox file
size. just shows a 0. and there is no "new message" "N" shown
either. buffy list works fine, btw.=20
A
--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGkDKoaIeIEqwil4YRAi7SAKDEvnPx5VmBv2QhB1OROHYou+iXSwCffMx5
7SJsMZHEZyZ1e+xIPNJJd6w=
=FZsx
-----END PGP SIGNATURE-----
--HcAYCG3uE/tztfnV--
Date: Sat, 7 Jul 2007 19:32:06 -0500
From: ArcticFox <genkokitsu@insightbb.com>
To: debian-user@lists.debian.org
Subject: Re: Enabling SFTP under Debian 4.0r0
Message-Id: <01e131c02b7c4f83591da5ec2dd4d6cb@insightbb.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
On Jul 7, 2007, at 7:19 PM, Bob Proulx wrote:
> ArcticFox wrote:
>> foxpaws:/home/fox# ssh -v localhost
>> OpenSSH_4.3p2 Debian-9, OpenSSL 0.9.8c 05 Sep 2006
>
> So far so good.
>
>> debug1: Reading configuration data /etc/ssh/ssh_config
>> debug1: Applying options for *
>> debug1: Connecting to localhost [127.0.0.1] port 22.
>> debug1: Connection established.
>> debug1: permanently_set_uid: 0/0
>> debug1: identity file /root/.ssh/identity type -1
>> debug1: identity file /root/.ssh/id_rsa type -1
>> debug1: identity file /root/.ssh/id_dsa type -1
>> debug1: Remote protocol version 2.0, remote software version
>> lshd-2.0.2 lsh - a GNU ssh
>> debug1: no match: lshd-2.0.2 lsh - a GNU ssh
>
> Where did that come from? Do you have lsh-server installed instead of
> openssh-server?
Looks like both were installed, I'm removing lsh-server. Ok, removed
but it's saying now that the connection is being refused on port 22.
It's refusing ssh and sftp, I ran ssh with the -v option and all it
spat out was connection refused.
>
> A stock Etch machine with openssh-server would respond here with the
> following:
>
> debug1: Remote protocol version 1.99, remote software version
> OpenSSH_4.3p2 Debian-9
> debug1: match: OpenSSH_4.3p2 Debian-9 pat OpenSSH*
>
> Bit it looks to me that you are not using OpenSSH at all but are
> instead using lsh-server.
>
>> debug1: Enabling compatibility mode for protocol 2.0
>> debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9
>> debug1: An invalid name was supplied
>> Configuration file does not specify default realm
>>
>> debug1: An invalid name was supplied
>> A parameter was malformed
>> Validation error
>>
>> debug1: An invalid name was supplied
>> Configuration file does not specify default realm
>>
>> debug1: An invalid name was supplied
>> A parameter was malformed
>> Validation error
>
> Those look scary but ignore them for now. They are not related to
> your present problem. This is related to GSSAPI Authentication.
>
Apache is also complaining about not being able to find the server
name, not sure if that's related.
Date: Sat, 7 Jul 2007 18:33:47 -0600
From: bob@proulx.com (Bob Proulx)
To: debian-user@lists.debian.org
Subject: Re: [SOLVED] Re: Installing a JRE plug-in
Message-ID: <20070708003347.GB8128@dementia.proulx.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
andy wrote:
> That was a useful overview to alternatives: I wasn't aware of that, and
> how (seemingly) prevalent it is with Debian. Wouldn't you guess it ...
> yep, when I run I am showing manual. I've corrected that now to auto.
Note that Red Hat is now using a forked copy of the alternatives too.
They use it for different reasons and for different commands. But it
is spreading beyond the Debian distro.
> I also note from Jeff's post that the site I was using to test this with
> threw up the same response to his testing, so that increases the
> likelihood of it being a site issue.
I should have added previously that if Java shows up as installed in
"about:plugins" as suggested by Jeff that I would trust that list. If
you see Java there then I would assume that it is installed and
working. If you don't then the opposite and it really is not
installed in a way that iceweasil can find it. But I think it is
installed okay in your case.
Bob
Date: Sat, 07 Jul 2007 19:38:00 -0500
From: Seb <spluque@gmail.com>
To: debian-user@lists.debian.org
Subject: procedure for "abandoned" packages
Message-ID: <87r6njybkn.fsf@patagonia.sebmags.homelinux.org>
Content-Type: text/plain; charset=us-ascii
Hi,
What is the appropriate procedure that a normal user can follow when a
package seems completely abandoned by the maintainer. By abandoned I mean
there are no updates in unstable for more than 3 months since the sources
for the upstream package have a new major version. Additionally, attempts
to contact the maintainer have gone unanswered for roughly that time.
Thanks.
Cheers,
--
Seb
End of debian-user-digest Digest V2007 Issue #1914
**************************************************
Received on Sat Jul 7 21:00:50 2007