Your message dated Mon, 4 Apr 2011 14:10:12 +0200
with message-id <20110404121011.gc25...@rivendell.home.ouaza.com>
and subject line Re: Bug#620699: dpkg-query: version string does not start with
digit
has caused the Debian Bug report #620699,
regarding dpkg-query: version string does not start with digit
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 ow...@bugs.debian.org
immediately.)
--
620699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.16.0
Severity: normal
I normally compile my own kernels. dpkg-query is giving errors
on these self-compiled kernels. (newmain.1 and newmain.2) are the
specific strings causing problems.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg depends on:
ii coreutils 8.5-1 GNU core utilities
ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libselinux1 2.0.98-1 SELinux runtime shared libraries
ii xz-utils 5.0.0-2 XZ-format compression utilities
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 0.8.13 Advanced front-end for dpkg
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
On Mon, 04 Apr 2011, Gordon Haverland wrote:
> linux-image-2.6.32_newmain.1.0_i386.deb
>
> It isn't restricted to kernels I made myself. For example, the
> entry for widelands generates the same error. Grepping
> /var/lib/dpkg/available for widelands, I get:
None of those packages are official Debian packages. I suggest you get in
touch with the providers of those packages so that they update them
accordingly.
As noted, it's not a bug but a deliberate change.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--- End Message ---
