Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #195970 > unrolled thread

Re: O/S upgrade - dpkg still shows old version for some packages

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: O/S upgrade - dpkg still shows old version for some packages Greg Wooledge <wooledg@eeg.ccf.org> - 2018-05-21 19:10 +0200
    Re: O/S upgrade - dpkg still shows old version for some packages Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-21 20:00 +0200
      Re: O/S upgrade - dpkg still shows old version for some packages John Horne <john.horne@plymouth.ac.uk> - 2018-05-22 17:10 +0200
        Re: O/S upgrade - dpkg still shows old version for some packages Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-22 19:00 +0200
          Re: O/S upgrade - dpkg still shows old version for some packages John Horne <john.horne@plymouth.ac.uk> - 2018-05-23 19:30 +0200
            Re: O/S upgrade - dpkg still shows old version for some packages Abdullah Ramazanoğlu <ar018@yahoo.com> - 2018-05-23 21:10 +0200
    Re: O/S upgrade - dpkg still shows old version for some packages John Horne <john.horne@plymouth.ac.uk> - 2018-05-22 13:50 +0200

#195970 — Re: O/S upgrade - dpkg still shows old version for some packages

On Mon, May 21, 2018 at 11:29:53AM +0000, John Horne wrote:
> dpkg -p nodejs
> ...
> Version: 0.10.37-1chl1~lucid1
> 
> nodejs -v
> v4.8.2

You probably have nodejs installed locally, outside of the packaging
system.  What does "type -a nodejs" tell you (in bash)?

[toc] | [next] | [standalone]

#195974

On Mon, 21 May 2018 13:06:37 -0400 Greg Wooledge said:

> On Mon, May 21, 2018 at 11:29:53AM +0000, John Horne wrote:
> > dpkg -p nodejs
> > ...
> > Version: 0.10.37-1chl1~lucid1
> > 
> > nodejs -v
> > v4.8.2  
> 
> You probably have nodejs installed locally, outside of the packaging
> system.  What does "type -a nodejs" tell you (in bash)?

~$ apt-cache policy nodejs

might give a more complete view.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#195995

On Mon, 2018-05-21 at 20:50 +0300, Abdullah Ramazanoğlu wrote:
> On Mon, 21 May 2018 13:06:37 -0400 Greg Wooledge said:
>
> > On Mon, May 21, 2018 at 11:29:53AM +0000, John Horne wrote:
> > > dpkg -p nodejs
> > > ...
> > > Version: 0.10.37-1chl1~lucid1
> > >
> > > nodejs -v
> > > v4.8.2
> >
> > You probably have nodejs installed locally, outside of the packaging
> > system.  What does "type -a nodejs" tell you (in bash)?
>
> ~$ apt-cache policy nodejs
>
> might give a more complete view.
>
the output for this shows:

======
nodejs:
  Installed: 4.8.2~dfsg-1
  Candidate: 4.8.2~dfsg-1
  Version table:
 *** 4.8.2~dfsg-1 500
        500 http://http.debian.net/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status
======


I also tried 'dpkg -s' as you suggested. The output was:

======
Package: nodejs
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 13928
Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.de
bian.org>
Architecture: amd64
Version: 4.8.2~dfsg-1
...
======



John.

--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>

This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

[toc] | [prev] | [next] | [standalone]

#195997

On Tue, 22 May 2018 11:33:40 +0000 John Horne said:
> On Mon, 2018-05-21 at 20:50 +0300, Abdullah Ramazanoğlu wrote:

>> ~$ apt-cache policy nodejs
>>
>> might give a more complete view.
>  
> the output for this shows:
> 
> ======
> nodejs:
>   Installed: 4.8.2~dfsg-1
>   Candidate: 4.8.2~dfsg-1
>   Version table:
>  *** 4.8.2~dfsg-1 500
>         500 http://http.debian.net/debian stretch/main amd64 Packages
>         100 /var/lib/dpkg/status
> ======
> 
> I also tried 'dpkg -s' as you suggested. The output was:
> 
> ======
> Package: nodejs
> Status: install ok installed
> Priority: optional
> Section: web
> Installed-Size: 13928
> Maintainer: Debian Javascript Maintainers
> <pkg-javascript-devel@lists.alioth.de bian.org>  
> Architecture: amd64
> Version: 4.8.2~dfsg-1
> ...
> ======

So there is no problem.

dpkg -p is shows the available packages for dselect. Since apt and dselect uses
different mechanisms for tracking package status, dselect's availability
database (/var/lib/dpkg/available) is not getting updated, hence reflects
initial installation status.

You can update this database with "dpkg --update-avail" but since you won't be
using dselect anyway, it is futile to do so.

So I would suggest use "dpkg -s" for actual installed package status, and
forget about dselect's idea of available packages (dpkg -p).

More information can be found in dpkg(1) man page.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#196021

On Tue, 2018-05-22 at 19:57 +0300, Abdullah Ramazanoğlu wrote:

>
> dpkg -p is shows the available packages for dselect. Since apt and dselect
> uses different mechanisms for tracking package status, dselect's availability
> database (/var/lib/dpkg/available) is not getting updated, hence reflects
> initial installation status.
>
Wow! I know nothing about Debian's internals, but you're saying that one
command (dpkg) will use different mechanisms and which one is used depends on
the command options used. That seems really confusing!

>
> So I would suggest use "dpkg -s" for actual installed package status, and
> forget about dselect's idea of available packages (dpkg -p).
>
Okay, thanks for that. And thanks for the info generally.



John.

--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>

This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

[toc] | [prev] | [next] | [standalone]

#196022

On Wed, 23 May 2018 13:52:38 +0000 John Horne said:

> Wow! I know nothing about Debian's internals, but you're saying that one
> command (dpkg) will use different mechanisms and which one is used depends on
> the command options used. That seems really confusing!

Sometimes it's confusing for me too.

As I understand it (and I may be wrong), dpkg is the low level package
management tool, while dselect (practically obsolete) and apt are high level
ones. As a legacy, dpkg has some organic integration with dselect, such as
keeping dselect's package selection status (which should have nothing to do
with dpkg per-se). OTOH apt keeps its own package status database separately.
Now that dselect is being phased out into legacy, dpkg's residual dselect
integration features seem out of place and confusing. There may be better /
more correct explanations, but this is the best I have.

In my current system dselect is not installed but available in repositories for
installation. I don't know if it has been used one-shot during initial system
installation. The fact that there is /var/lib/dpkg/available file suggests so.

So I prefer ignoring dselect and the residue it left in dpkg.

I would be glad to learn more, if someone with more insight explains it better.

Regards
-- 
Abdullah Ramazanoğlu

[toc] | [prev] | [next] | [standalone]

#195989

On Mon, 2018-05-21 at 13:06 -0400, Greg Wooledge wrote:
> On Mon, May 21, 2018 at 11:29:53AM +0000, John Horne wrote:
> > dpkg -p nodejs
> > ...
> > Version: 0.10.37-1chl1~lucid1
> >
> > nodejs -v
> > v4.8.2
>
> You probably have nodejs installed locally, outside of the packaging
> system.  What does "type -a nodejs" tell you (in bash)?
>
The output is:

nodejs is /usr/bin/nodejs



John.

--
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
________________________________
[http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>

This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web