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

Bug#1002605: marked as done (`apt-get source calendar' downloads the wrong package)



Your message dated Thu, 30 Dec 2021 09:24:53 +0100
with message-id <837c2012-bb40-f09e-a01a-14d7f491263c@debian.org>
and subject line Re: Bug#1002605: `apt-get source calendar' downloads the wrong package
has caused the Debian Bug report #1002605,
regarding `apt-get source calendar' downloads the wrong package
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.)


-- 
1002605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002605
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 2.3.13
Severity: important

Dear Maintainer,

`apt-get source calendar' downloads the bsdmainutils source package
instead of calendar. I suspect this is because bsdmainutils is the
source package of the calendar binary package.

I think `apt-get source $FOO' should try to download $FOO if $FOO
exists as a source package, and only after fallback to downloading the
source package of $FOO if it exists only as a binary package.


Cheers,

-- 
Stéphane


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt depends on:
ii  adduser                 3.118
ii  debian-archive-keyring  2021.1.1
ii  gpgv                    2.2.27-2
ii  libapt-pkg6.0           2.3.13
ii  libc6                   2.33-1
ii  libgcc-s1               11.2.0-12
ii  libgnutls30             3.7.2-2
ii  libseccomp2             2.5.3-2
ii  libstdc++6              11.2.0-12
ii  libsystemd0             249.7-1

Versions of packages apt recommends:
ii  ca-certificates  20210119

Versions of packages apt suggests:
pn  apt-doc         <none>
ii  aptitude        0.8.13-3
ii  dpkg-dev        1.21.1
ii  gnupg           2.2.27-2
ii  gnupg2          2.2.27-2
ii  powermgmt-base  1.36
ii  synaptic        0.90.2+b1

-- no debconf information

--- End Message ---
--- Begin Message ---
Hello,

Le 29/12/2021 à 15:42, David Kalnischkies a écrit :
>> I agree and I cannot remember a single time when (in scripts or when running
>> apt manually) I wanted 'apt-get source' or 'apt-cache showsrc' to interpret the
>> package name as a binary package and not a source package. Because of that I
>> have
>>
>> APT::Get::Only-Source "true";
>>
>> in my system-wide apt config. I've never looked back.
> [...]
> Anyway, I don't see us reversing the default search order and not
> dropping binary lookup altogether (what the option does) either.
> (or outlawing these collisions as evil – somehow I get the feeling that
>  is what initial authors intended but failed as with many other small
>  things).

I understand. Besides, Johannes's tip is enough for me.

I don't see anything to be done, so I'm closing this bug.


Cheers,

-- 
Stéphane

--- End Message ---

Reply to: