In article [EMAIL PROTECTED] you wrote:
number. Another thing where package build-stamps may help to generate a report.
Then just download the package file manually
My point was refering to the fact that one needs a tool to find those
problems, I know how to fix them :)
Greetings
Bernd
--
Hi,
On Sat, Sep 27, 2003 at 01:24:47AM +0200, Bernd Eckenfels wrote:
My point was refering to the fact that one needs a tool to find those
problems, I know how to fix them :)
To find them, try apt-show-versions.
Regards,
Nicolas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
In article [EMAIL PROTECTED] you wrote:
number. Another thing where package build-stamps may help to generate a
report.
Then just download the package file manually
My point was refering to the fact that one needs a tool to find those
problems, I know how to fix them :)
Greetings
Bernd
--
Hi,
On Sat, Sep 27, 2003 at 01:24:47AM +0200, Bernd Eckenfels wrote:
My point was refering to the fact that one needs a tool to find those
problems, I know how to fix them :)
To find them, try apt-show-versions.
Regards,
Nicolas
In article [EMAIL PROTECTED] you wrote:
+++-==-==-
ii ssh3.4p1-1.woody.3Secure rlogin/rsh/rcp replacement (OpenSSH)
ii ssh3.4p1-2Secure rlogin/rsh/rcp
On Wed, Sep 24, 2003 at 07:44:16PM +0200, Bernd Eckenfels wrote:
looks like somebody installed ssh some (long) time ago from testing or
unstable on server b. This is a problem, since it is the higher version
number. Another thing where package build-stamps may help to generate a report.
Then
On Thu, Sep 25, 2003 at 08:47:22AM +, [EMAIL PROTECTED] wrote:
serverB:~# apt-cache policy ssh
ssh:
Installed: 1:3.4p1-2
Candidate: 1:3.4p1-2
Version Table:
*** 1:3.4p1-2 0
100 /var/lib/dpkg/status
1:3.4p1-1.woody.3 0
500 http://security.debian.org
[EMAIL PROTECTED] crivait :
openssh (1:3.4p1-2) unstable; urgency=high
* Get a security-fixed version into unstable
* Also tidy README.Debian up a little
-- Matthew Vernon [EMAIL PROTECTED] Fri, 28 Jun 2002 17:20:59 +0100
Ok, Google says there was such a version, but it was from
Am 2003-09-24 09:14:52, schrieb Yogesh Sharma:
As far as my understanding goes, ssh was patched recently for security
fixes, so it should be coming from security.debian.org not us.debian.org.
Now security.debian.org is not at all mirrored for security reason than
how he has 2 different versions
On Thu, Sep 25, 2003 at 03:04:40PM +0700, Jean Christophe ANDR? wrote:
Anybody could give a hint on the right way to clean an entry from
/var/lib/dpkg/status? I've not investigated so far until now... :)
Is this using dselect update or thing like this? (I never use dselect)
Is that what dpkg
In article [EMAIL PROTECTED] you wrote:
+++-==-==-
ii ssh3.4p1-1.woody.3Secure rlogin/rsh/rcp replacement
(OpenSSH)
ii ssh3.4p1-2Secure rlogin/rsh/rcp
On Wed, Sep 24, 2003 at 07:44:16PM +0200, Bernd Eckenfels wrote:
looks like somebody installed ssh some (long) time ago from testing or
unstable on server b. This is a problem, since it is the higher version
number. Another thing where package build-stamps may help to generate a
report.
Then
On Thu, Sep 25, 2003 at 08:47:22AM +, [EMAIL PROTECTED] wrote:
serverB:~# apt-cache policy ssh
ssh:
Installed: 1:3.4p1-2
Candidate: 1:3.4p1-2
Version Table:
*** 1:3.4p1-2 0
100 /var/lib/dpkg/status
1:3.4p1-1.woody.3 0
500 http://security.debian.org
[EMAIL PROTECTED] écrivait :
openssh (1:3.4p1-2) unstable; urgency=high
* Get a security-fixed version into unstable
* Also tidy README.Debian up a little
-- Matthew Vernon [EMAIL PROTECTED] Fri, 28 Jun 2002 17:20:59 +0100
Ok, Google says there was such a version, but it was from
Am 2003-09-24 09:14:52, schrieb Yogesh Sharma:
As far as my understanding goes, ssh was patched recently for security
fixes, so it should be coming from security.debian.org not us.debian.org.
Now security.debian.org is not at all mirrored for security reason than
how he has 2 different versions
On Thu, Sep 25, 2003 at 03:04:40PM +0700, Jean Christophe ANDR? wrote:
Anybody could give a hint on the right way to clean an entry from
/var/lib/dpkg/status? I've not investigated so far until now... :)
Is this using dselect update or thing like this? (I never use dselect)
Is that what dpkg
On Wed, Sep 24, 2003 at 10:08:36PM +0700, Jean Christophe ANDR? wrote:
Could you please show us a apt-cache policy ssh on both servers?
Here is mine:
# apt-cache policy ssh
ssh:
Installed: 1:3.4p1-1.woody.3
Candidate: 1:3.4p1-1.woody.3
Version Table:
***
On Thu, Sep 25, 2003 at 02:27:01PM +0700, Jean Christophe ANDR? wrote:
What do you have in /usr/share/doc/ssh/changelog.Debian.gz?
openssh (1:3.4p1-2) unstable; urgency=high
* Get a security-fixed version into unstable
* Also tidy README.Debian up a little
-- Matthew Vernon [EMAIL
On Wed, Sep 24, 2003 at 10:08:36PM +0700, Jean Christophe ANDR? wrote:
Could you please show us a apt-cache policy ssh on both servers?
Here is mine:
# apt-cache policy ssh
ssh:
Installed: 1:3.4p1-1.woody.3
Candidate: 1:3.4p1-1.woody.3
Version Table:
***
On Thu, Sep 25, 2003 at 02:27:01PM +0700, Jean Christophe ANDR? wrote:
What do you have in /usr/share/doc/ssh/changelog.Debian.gz?
openssh (1:3.4p1-2) unstable; urgency=high
* Get a security-fixed version into unstable
* Also tidy README.Debian up a little
-- Matthew Vernon [EMAIL
I have strange result on two our debian servers - both are woody.
The first one (A) has kerenel 2.4.19, the other one (B) - 2.4.22.
The A server is almost daily checked against new packages, the B
server was upgraded yesterday. Both have the same sources.list
But server A:
serverA:~# dpkg -l ssh
On Wed, Sep 24, 2003 at 13:04:20 +, [EMAIL PROTECTED] wrote:
I have strange result on two our debian servers - both are woody. The
first one (A) has kerenel 2.4.19, the other one (B) - 2.4.22. The A server
is almost daily checked against new packages, the B server was upgraded
yesterday.
On Wed, Sep 24, 2003 at 02:46:44PM +0200, J.H.M. Dassen (Ray) wrote:
On Wed, Sep 24, 2003 at 13:04:20 +, [EMAIL PROTECTED] wrote:
I have strange result on two our debian servers - both are woody. The
first one (A) has kerenel 2.4.19, the other one (B) - 2.4.22. The A server
is almost
[EMAIL PROTECTED], Wed, Sep 24, 2003 at 01:04:20PM +:
Why the two servers, upgraded from the same server have different ssh
packages ? The same is with some other packages, e.g.: xfree86-common
I noticed the exact same behavior on one of my machines. After a number
of updates apt was
[EMAIL PROTECTED] wrote:
On Wed, Sep 24, 2003 at 02:46:44PM +0200, J.H.M. Dassen (Ray) wrote:
And /etc/apt/preferences? Sounds like they're using different pinning
settings.
serverA:~# cat /etc/apt/preferences
cat: /etc/apt/preferences: No such file or directory
The same on server
As far as my understanding goes, ssh was patched recently for security
fixes, so it should be coming from security.debian.org not us.debian.org.
Now security.debian.org is not at all mirrored for security reason than
how he has 2 different versions of ssh ?
1 Does he has proper
On Wed, Sep 24, 2003 at 01:04:20PM +, [EMAIL PROTECTED] wrote:
ii ssh3.4p1-2Secure rlogin/rsh/rcp replacement (OpenSSH)
This version of ssh is neither directly from woody (which still has
3.4p1-1) nor from security.debian.org (which has 1:3.4p1-1.woody.3, and
Yogesh Sharma, Wed, Sep 24, 2003 at 09:14:52AM -0700:
As far as my understanding goes, ssh was patched recently for security
fixes, so it should be coming from security.debian.org not us.debian.org.
Now security.debian.org is not at all mirrored for security reason than
how he has 2
I have strange result on two our debian servers - both are woody.
The first one (A) has kerenel 2.4.19, the other one (B) - 2.4.22.
The A server is almost daily checked against new packages, the B
server was upgraded yesterday. Both have the same sources.list
But server A:
serverA:~# dpkg -l ssh
On Wed, Sep 24, 2003 at 13:04:20 +, [EMAIL PROTECTED] wrote:
I have strange result on two our debian servers - both are woody. The
first one (A) has kerenel 2.4.19, the other one (B) - 2.4.22. The A server
is almost daily checked against new packages, the B server was upgraded
yesterday.
[EMAIL PROTECTED] wrote:
On Wed, Sep 24, 2003 at 02:46:44PM +0200, J.H.M. Dassen (Ray) wrote:
And /etc/apt/preferences? Sounds like they're using different pinning
settings.
serverA:~# cat /etc/apt/preferences
cat: /etc/apt/preferences: No such file or directory
The same on server
On Wed, Sep 24, 2003 at 01:04:20PM +, [EMAIL PROTECTED] wrote:
ii ssh3.4p1-2Secure rlogin/rsh/rcp replacement
(OpenSSH)
This version of ssh is neither directly from woody (which still has
3.4p1-1) nor from security.debian.org (which has 1:3.4p1-1.woody.3, and
Yogesh Sharma, Wed, Sep 24, 2003 at 09:14:52AM -0700:
As far as my understanding goes, ssh was patched recently for security
fixes, so it should be coming from security.debian.org not us.debian.org.
Now security.debian.org is not at all mirrored for security reason than
how he has 2
33 matches
Mail list logo
