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

Bug#617672: marked as done ("apt-get source linux-image-2.6.37-2-amd64" returns source of "linux-2.6-2.6.38~rc6")

Your message dated Thu, 10 Mar 2011 17:21:37 +0100
with message-id <AANLkTimSsS+SKjFFaaWD143q5tNdzScfrA_+6BHOkZVY@mail.gmail.com>
and subject line Re: "apt-get source linux-image-2.6.37-2-amd64" returns source of "linux-2.6-2.6.38~rc6"
has caused the Debian Bug report #617672,
regarding "apt-get source linux-image-2.6.37-2-amd64" returns source of "linux-2.6-2.6.38~rc6"
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.)


-- 
617672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617672
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.37-2
Severity: normal

I believe that "apt-get source linux-image-2.6.37-2-amd64" should give
me the linux-2.6.37-2 source code, and not the linux-2.6 2.6.38~rc6-1
source code.

But when run:

t@h ~/linux-2.6-2.6.38~rc6> apt-get source linux-image-2.6.37-2-amd64  
Indlæser pakkelisterne... Færdig
Opbygger afhængighedstræ        
Læser tilstandsoplysninger... Færdig
Vælger 'linux-2.6' som kildepakke fremfor 'linux-image-2.6.37-2-amd64'
BEMÆRK: Pakning af 'linux-2.6' vedligeholdes i versionskontrolsystemet 'Svn' på:
svn://svn.debian.org/svn/kernel/dists/sid/linux-2.6/
94,9 MB skal hentes fra kildetekst-arkiverne.
Henter:1 http://ftp.dk.debian.org/debian/ experimental/main linux-2.6 2.6.38~rc6-1~experimental.1 (dsc) [5.392 B]
Henter:2 http://ftp.dk.debian.org/debian/ experimental/main linux-2.6 2.6.38~rc6-1~experimental.1 (tar) [94,3 MB]
[...]

Regards, Thue

--- End Message ---
--- Begin Message --- 
Hi *,

[I assume you don't have a default release set (APT::Default-Release)]

As said in the manpage apt-get source will download the newest available
version of the source package - that you gave a binary package name and
that is mapped to a source package is just a convenience helper for you -
which currently is 2.6.38~rc6. If you don't like that, either set a default
release in the config or give it at runtime explicitly:
apt-get source linux-image-2.6.37-2-amd64/sid or
apt-get source linux-image-2.6.37-2-amd64 -t unstable or even
apt-get source linux-2.6=2.6.37-2
Should all work.

In this specific case its maybe a bit misfortune as a version number is
written in the binary package name but its the same for libraries in case
of changing their soname. libc6 will give you the source of libc7 if it
should ever be published in the future. In contrast to this, if you want
to get the source of libc6 on an oldstable system you will get a different
source (glibc) than the one you will get in stable and above (eglibc) simply
because the binary to source mapping is taken from the candidate version of
the binary package (we can argue that this makes sense e.g. in the light of
package renames like the "fight" around git: git-core vs. gnuit).

If we would use the version number from it too your problem would be fixed,
but we would have changed the default and no longer get the newest but the
source of the candidate of this binary package.

Given that many people use the source command to get the newest version
of the source e.g. to backport this newer version to their system,
this behavior-switch would be a bad default.

So sorry, but that is a non-bug and documented that way.
(Closing the bug again… oh, i hate this type of ping-pong game…)


Best regards

David Kalnischkies

--- End Message ---
Reply to: