[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#408134: marked as done (module-assistant versioning inconsistent with linux-modules-*-2.6)

Your message dated Fri, 2 May 2008 10:40:09 -0500
with message-id <20080502154008.GA12893@cat-in-the-hat.dnsalias.com>
and subject line linux-modules-* fixes probably unnecessary
has caused the Debian Bug report #408134,
regarding module-assistant versioning inconsistent with linux-modules-*-2.6
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 owner@bugs.debian.org
immediately.)


-- 
408134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408134
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kqemu-source
Version: 1.3.0~pre9-10
Severity: normal

Hi,

If using kqemu-source and module-assistant to build kqemu-modules against the
current stock kernel - currently linux-image-2.6.18-3-686 (2.6.18-8), and upgrade
of the system will cause the locally built package to be downgraded to the version
available from the mirrors. See the following output which might be much clearer:

$ LANG=C apt-cache policy kqemu-modules-2.6.18-3-686
kqemu-modules-2.6.18-3-686:
  Installed: 1.3.0~pre9-10+2.6.18-8
  Candidate: 2.6.18+1.3.0~pre9-3
  Version table:
     2.6.18+1.3.0~pre9-3 0
        500 http://ftp.fr.debian.org unstable/non-free Packages
 *** 1.3.0~pre9-10+2.6.18-8 0
        100 /var/lib/dpkg/status

2.6.18+1.3.0~pre9-3 is actually lower than 1.3.0~pre9-10+2.6.18-8, although 
dpkg --compare-version doesn't consider it to be.

Maybe it is a bug in module-assistant (which I doubt as I do not have this issue with
other modules) or in the autobuilding process, as I haven't found any other modules
with the kernel version before the module version.

I don't know the process of automatically built kernel modules, but the best way to
fix this bug would be that the kqemu-modules-$KVERS-$ARCH are uploaded at the same time
as is kqemu-source, but don't know if it is possible, especially with non-free modules.

Cheers,
Julien

-- System Information: Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages kqemu-source depends on:
ii  bzip2                         1.0.3-6    high-quality block-sorting file co
ii  debhelper                     5.0.42     helper programs for debian/rules
ii  dpatch                        2.0.21     patch maintenance system for Debia
ii  make                          3.81-3     The GNU version of the "make" util
ii  module-assistant              0.10.10    tool to make module package creati

kqemu-source recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
After consulting with Daniel Baumann <daniel@debian.org>, it appears
that it's unnecessary for linux-modules-* to add an epoch or change
its versioning scheme. modules-assistant still requires fixing, by
adding an epoch to all modules it creates, and reversing the version
number to match linux-modules-*'s scheme, however no coordination with
linux-modules-* is necesary.

I am closing the bugs againt linux-modules-*.

--Ken

-- 
Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: