Re: does apt update also update 'command-not-found' and the newest 'apt-file' update as well ?

[shirish शिरीष <shirishag75@gmail.com>]

On 12/12/2015, Julian Andres Klode <jak@jak-linux.org> wrote:
> On 12 December 2015 at 11:27, shirish शिरीष <shirishag75@gmail.com> wrote:
>> Hi all,
>>
>> I today upgraded to the newest apt 1.1.4 as well as took the
>> opportunity to explore the newest apt-file ((3.0) as well as see the
>> command-not-found update cache.
>>
>> It seems you either run " $ sudo update-command-not-found" or "sudo
>> apt update" or "sudo apt-file update" all of them do the same thing,
>> they update the package repos using apt although "sudo
>> update-command-not-found" or "sudo apt update" the output is same,
>> updates the apt database.
>
> In fact update-command-not-found does not work at all with apt-file 3.0,
> this
> needs to be changed. I just reported me a bug for that.
>
> --
> Julian Andres Klode  - Debian Developer, Ubuntu Member
>
> See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
>

Could you share the link of the bug please.

I was just going to say to disregard as just saw
https://lists.debian.org/deity/2015/12/msg00036.html

and specifically -

* "apt-file update" will become a thin call to "apt update" - Niels Thykier

so at least partially found that I am right.

Look forward to seeing that bug fixed.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8