Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Any way to verify your patch 'level'?

New to Debian (Or Linux in general)? Ask your questions here!
Message
Author
ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Any way to verify your patch 'level'?

#1 Post by ayarrington73 »

I've been struggling with 'package updater' telling me at first that no internet connection was detected and now 'there are no updates available'. I'm not confident it's telling me I'm all updated and not that it isn't connecting properly....is there any way otherwise to check an update "level" like a numerical value of some kind(like Windoze would have a build#)...
Thanks In Advance

User avatar
dasein
Posts: 7680
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: Any way to verify your patch 'level'?

#2 Post by dasein »

And the version of Debian that you're running is......... ????

(Sorry, flunked telepathy in school.)

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Any way to verify your patch 'level'?

#3 Post by GarryRicketson »

In this recent thread : http://forums.debian.net/viewtopic.php?f=30&t=133859 3 pages , goes into great detail .
Postby ayarrington73 » 2017-07-09 10:02
Package Updater says "no network connection was detected", although internet works fine(wireless) and I'm on it right now writing this post......any ideas? I'm a disabled i.t. pro, so I'm not hesitant to try ideas...
T.I.A.
-Al
Unless the OP has re-installed, as advised, then they should let us know what
version the used to re-install.
====================== edited =========
Also could the OP clarify, what is this
Package Updater
they are
referring to ? I just did a bunch of searches and can not find anything referring
to a "package updater", on Debian.
There are a wide range of tutorials and documentation on package management, but I find nothing on a "Package Updater"

https://www.debian.org/doc/manuals/debi ... ls.en.html
----------------------------------
https://www.debian.org/doc/manuals/debi ... 02.en.html
--------------------------------------
https://wiki.debian.org/DebianPackageManagement
----------------------
https://www.debian.org/doc/manuals/debi ... cs.en.html
------------------------------
https://raphaelhertzog.com/2011/06/20/a ... r-for-you/

User avatar
Lysander
Posts: 643
Joined: 2017-02-23 10:07
Location: London
Been thanked: 1 time

Re: Any way to verify your patch 'level'?

#4 Post by Lysander »

I think OP is referring to the Package Updater utility

Image

as far as I can see it's just a GUI version of entering

Code: Select all

# apt full-upgrade

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Any way to verify your patch 'level'?

#5 Post by GarryRicketson »

I don't know, I see it on your screen shot, but still can not find anything
about that in any searches. I have never seen anything like that on any of my Debian installations either.
Confusing name "Package Updater", if it does upgrades like you say:
as far as I can see it's just a GUI version of entering

Code: Select all
# apt full-upgrade

Seems like a more appropriate name would be "System Up-grader "

running :

Code: Select all

apt update
is a entirely different thing, then running :

Code: Select all

apt full-upgrade 
Maybe the OP should clarify what it is exactly they want to do.
Does the OP just want to update their sources, or are they trying to upgrade, ?

I give up, none of this is making sense to me .

User avatar
Lysander
Posts: 643
Joined: 2017-02-23 10:07
Location: London
Been thanked: 1 time

Re: Any way to verify your patch 'level'?

#6 Post by Lysander »

GarryRicketson wrote:I give up
I think that's wisest as far as this debacle is concerned.

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#7 Post by ayarrington73 »

I apologize for the confusion, guys.....I'm not sure how to check what version and update level, etc., I'm on......I'm also struggling with my sourcelist possibly being compromised, so I don't trust the messages 'package updater' in the system folder of the Applications Menu is giving me

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Any way to verify your patch 'level'?

#8 Post by stevepusser »

Have you tried managing your updates with Synaptic? It works well, and the "Status" section will show any upgradeable packages. This assumes that whoever had your netbook before didn't try any tricks with the apt-preferences for the repos; those can hide upgrades that normal users will see.
MX Linux packager and developer

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#9 Post by ayarrington73 »

If I try Synaptic Package Manager, I see there are several items not currently installed, but if I simply click the 'mark all upgrades' button, then the 'apply' button is still grayed out, presumably b/c it didn't find anything to mark I would guess?

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#10 Post by ayarrington73 »

dasein wrote:And the version of Debian that you're running is......... ????

(Sorry, flunked telepathy in school.)
from terminal:
dad@dadlinux:~$ cat /etc/issue
Debian GNU/Linux 8 \n \l

dad@dadlinux:~$ cat /etc/debian_version
8.8
dad@dadlinux:~$

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#11 Post by ayarrington73 »

also...
dad@dadlinux:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.8 (jessie)
Release: 8.8
Codename: jessie
dad@dadlinux:~$

User avatar
dasein
Posts: 7680
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: Any way to verify your patch 'level'?

#12 Post by dasein »

ayarrington73 wrote:I'm also struggling with my sourcelist possibly being compromised...
Which begs the question of why you didn't bother to mention it earlier, nor post its contents in your second message.

Some folks just want attention, not help.

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#13 Post by ayarrington73 »

dasein wrote:
ayarrington73 wrote:I'm also struggling with my sourcelist possibly being compromised...
Which begs the question of why you didn't bother to mention it earlier, nor post its contents in your second message.

Some folks just want attention, not help.
umm...rude.....no, I'm not looking for attention......I'm a disabled i.t. pro and my mind doesn't always fire at 100% anymore, so I'm trying to include any other details as they occur to me and seem applicable... :mrgreen:

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#14 Post by ayarrington73 »

Upon earlier advice, I had changed my sources.list to the following:

deb http://deb.debian.org/debian jessie main contrib non-free
deb http://deb.debian.org/debian jessie-updates main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free

Now, I'm not skilled at reading these, but it looks to me like the only sources listed are "non-free" and I wonder if that is limiting me from getting the "normal" free updates....

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Any way to verify your patch 'level'?

#15 Post by GarryRicketson »

That was confusing to me, and perhaps still is, but I think the fact that the lines
contain all 3,..
main contrib non-free
"main" is the main sources,
"contrib", is contrib sources, and "non-free" is the non-free sources,.....
ayarrington73 » the only sources listed are "non-free"
You have all 3 listed, so it is not only non-free, a line that was only non-free
would look like this:

Code: Select all

deb http://deb.debian.org/debian jessie non-free 
or one that does NOT contain "non-free" and "contrib" :

Code: Select all

deb http://deb.debian.org/debian jessie main 
Hope that makes sense, and also if I am not right on this, someone needs to clarify.

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#16 Post by ayarrington73 »

gotcha, thanks for the clarification!
does anything stick out to you as missing?

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Any way to verify your patch 'level'?

#17 Post by stevepusser »

I would say that all your packages are up to date. If in doubt, you can check what version you have installed in Synaptic, then cross-check the current version for Jessie at packages.debian.org.
MX Linux packager and developer

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#18 Post by ayarrington73 »

thanks!

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: Any way to verify your patch 'level'?

#19 Post by GarryRicketson »

Something that was not mentioned, or maybe it was, and the OP missed it, and me as well,
But anyway,
IMPORTANT:
After editing the /apt/etc/sources.list file, one all ways must also
run :

Code: Select all

apt update 
as su or root.
OR, if you are using synaptic package manager,
then "click" the "edit" > reload package info , which does the same as
'apt update'
Postby ayarrington73 » 2017-07-11 13:48
I've been struggling with 'package updater' ---snip---
If it is this "package upgrade" thing , then I have no idea, that seems to be
another 'new feature'.

ayarrington73
Posts: 55
Joined: 2017-02-02 18:38

Re: Any way to verify your patch 'level'?

#20 Post by ayarrington73 »

tks for the suggestion.....the cmd ran with an error at the end of:There is no public key available for the following key IDs:
1397BC53640DB551Failed to fetch http://dl.google.com/linux/chrome/deb/d ... le/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
Some index files failed to download. They have been ignored, or old ones used instead.

Post Reply