Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-07 Thread David Wright
On Fri 06 Apr 2018 at 08:54:56 (+), Curt wrote: > On 2018-04-06, David Wright wrote: > >> > >> Certainly I have no proof except my experience > > > > Correct me if I'm wrong but I don't think you've shared any. > > I've found something ambivalently concrete. > >

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-06 Thread Curt
On 2018-04-06, David Wright wrote: >> >> Certainly I have no proof except my experience > > Correct me if I'm wrong but I don't think you've shared any. I've found something ambivalently concrete. Note Since apt / apt-get and aptitude share auto-installed package

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-05 Thread David Wright
On Fri 06 Apr 2018 at 07:36:09 (+0900), Mark Fletcher wrote: > On Wed, Mar 28, 2018 at 09:31:11AM +0200, to...@tuxteam.de wrote: > > On Wed, Mar 28, 2018 at 07:47:05AM +0900, Mark Fletcher wrote: > > > > [...] > > > > > I'm not sure if you really did what it sounds like you did here, but if > >

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-05 Thread Mark Fletcher
On Wed, Mar 28, 2018 at 09:31:11AM +0200, to...@tuxteam.de wrote: > On Wed, Mar 28, 2018 at 07:47:05AM +0900, Mark Fletcher wrote: > > [...] > > > I'm not sure if you really did what it sounds like you did here, but if > > you did... you can't mix and match commands to apt-get and aptitude. >

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-02 Thread David Wright
On Mon 02 Apr 2018 at 10:53:07 (+0200), Jean-Baptiste Thomas wrote: > The reason why it failed is that it looked for Packages.xz which > did not exist on my mirror. The reason why my mirror did not > have a Packages.xz file is that it was made with the version of > debmirror in Debian 8, which

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-04-02 Thread Jean-Baptiste Thomas
>> What I'd like to know now is : what prevents apt-get from >> downloading the Packages file from the mirror ? Wget can ! > > Move all the files out of /var/lib/apt/lists/ so that apt-get update > has to download fresh copies. That should get you back on track. > > By all means take the

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-28 Thread David Wright
On Wed 28 Mar 2018 at 21:07:35 (+0200), Jean-Baptiste Thomas wrote: > > Try running: > > sudo apt-get update # one more time, to be sure > > # then > > apt-cache policy ntp > > > > and see what version it refers to. > > Thanks for the suggestions folks but there's not much to see > there, no

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-28 Thread songbird
Jean-Baptiste Thomas wrote: > /var/lib/apt/lists/, which may be why it thinks that not being > able to download it is not a problem. > > Unfortunately, the Packages file in /var/lib/apt/lists/ is out > of date by months because it pertains to 9.2 while the mirror > has 9.4. Diffing the two shows

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-28 Thread Jean-Baptiste Thomas
> Try running: > sudo apt-get update # one more time, to be sure > # then > apt-cache policy ntp > > and see what version it refers to. Thanks for the suggestions folks but there's not much to see there, no packages are pinned. I've made some progress, though. A closer look at the output reveals

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-28 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 28, 2018 at 07:47:05AM +0900, Mark Fletcher wrote: [...] > I'm not sure if you really did what it sounds like you did here, but if > you did... you can't mix and match commands to apt-get and aptitude. I think this is false, at least

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-27 Thread John Crawley (johnraff)
On 2018-03-28 02:50, Jean-Baptiste Thomas wrote: After apt-get update, attempting to install ntp tries to download version 1:4.2.8p10+dfsg-3+deb9u1 and fails. It tries to download +deb9u1 because $ aptitude show ntp Package: ntp Version: 1:4.2.8p10+dfsg-3+deb9u1 State: not installed

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-27 Thread Mark Fletcher
On Tue, Mar 27, 2018 at 07:50:03PM +0200, Jean-Baptiste Thomas wrote: > After apt-get update, attempting to install ntp tries to > download version 1:4.2.8p10+dfsg-3+deb9u1 and fails. It tries > to download +deb9u1 because > > $ aptitude show ntp > Package: ntp > Version:

Re: apt{-cache,-get,itude} show wrong version of package after update

2018-03-27 Thread Abdullah Ramazanoglu
On Tue, 27 Mar 2018 19:50:03 +0200 (CEST) Jean-Baptiste Thomas said: > How is this possible ? I'm confused. In my Buster system the situation is like this: ~$ apt-cache policy ntp ntp: Installed: (none) Candidate: 1:4.2.8p10+dfsg-6 Version table: 1:4.2.8p10+dfsg-6 500 500

apt{-cache,-get,itude} show wrong version of package after update

2018-03-27 Thread Jean-Baptiste Thomas
After apt-get update, attempting to install ntp tries to download version 1:4.2.8p10+dfsg-3+deb9u1 and fails. It tries to download +deb9u1 because $ aptitude show ntp Package: ntp Version: 1:4.2.8p10+dfsg-3+deb9u1 State: not installed [...] and it fails because the version of the