Your message dated Wed, 03 Dec 2008 21:42:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#507712: Followup-For: Bug #502375- seem to be a 
problem with  version notation change
has caused the Debian Bug report #507712,
regarding Followup-For: Bug #502375- seem to be a problem with version notation 
change
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
507712: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507712
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: virtualbox-ose-modules-2.6.26-1-686
Version: 1.6.6-dfsg-3+2.6.26-10

*** Please type your report below this line ***
version notation changed from  2.6.26+1.6.2-dfsg-4 to 1.6.6-dfsg-3+2.6.26-10
apparantly causing update-manager to consider the former as latest.
solved locally by locking version in synaptic after doing the proposed a-i.
should be fixed by reformatting version number of new (or old) package

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages virtualbox-ose-modules-2.6.26-1-686 depends on:
ii  linux-image-2.6.26-1-686 [lin 2.6.26-10  Linux 2.6.26 image on PPro/Celeron

Versions of packages virtualbox-ose-modules-2.6.26-1-686 recommends:
ii  virtualbox-ose              1.6.6-dfsg-3 x86 virtualization solution - bina

virtualbox-ose-modules-2.6.26-1-686 suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
[EMAIL PROTECTED] wrote:
> version notation changed from  2.6.26+1.6.2-dfsg-4 to 1.6.6-dfsg-3+2.6.26-10
> apparantly causing update-manager to consider the former as latest.
> solved locally by locking version in synaptic after doing the proposed a-i.
> should be fixed by reformatting version number of new (or old) package

this is not a bug; see bts history for this.


-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          [EMAIL PROTECTED]
Internet:       http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---

Reply via email to