How do you know which repo to use

[Soapm]

I have trouble knowing which repository a given package is on. Let's take the below link for instance for transmission, how do I know the repository to make sure is correctly in my source.list and how would I know if I need "main" vs. "contrib" vs. "non-free". I'm sure it's on the page somewhere and obvious but I'ver scoured and scoured that page and can't tell how to know when your source.list is right for a given package.

https://packages.debian.org/search?keyw ... ansmission

[sunrat]

contrib or non-free are usually marked in red on the package page, otherwise it will be in main. eg:
https://packages.debian.org/search?suit ... re-atheros

[Soapm]

Thanks, I never noticed the red before, I guess I haven't looked up a package on non-free...

The strange thing and the other reason I'm asking is because my system is staying one version below the one on the linked page. I was wondering if I'm using the wrong repository or why I'm not updating to the latest version. This is my source.list

Code: Select all

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

But how do you tell if a package is on the regular repository vs multimedia, security etc...?

[4D696B65]

like this

Code: Select all

apt-cache policy nvidia-driver
nvidia-driver:
  Installed: 375.82-5
  Candidate: 375.82-5
  Version table:
 *** 375.82-5 500
        500 http://ftp.ca.debian.org/debian unstable/non-free amd64 Packages

[Soapm]

Cool...

Does this show I have the latest version or any reason mines won't update? The above link says 2.84-0.2 is the latest version.

Code: Select all

root@lenny:/# apt-cache policy transmission
transmission:
  Installed: 2.84-1
  Candidate: 2.84-1
  Version table:
 *** 2.84-1 0
        100 /var/lib/dpkg/status
     2.84-0.2 0
        500 http://deb.debian.org/debian/ jessie/main amd64 Packages

But also, so I'm clear, you have to install the package to know what repository the package is on???

[4D696B65]

But also, so I'm clear, you have to install the package to know what repository the package is on???

Code: Select all

 apt-cache policy firmware-atheros
firmware-atheros:
  Installed: (none)
  Candidate: 20170823-1
  Version table:
     20170823-1 500
        500 http://ftp.ca.debian.org/debian unstable/non-free amd64 Packages

[Soapm]

I see, the command works if the package is on your system or not.

[stevepusser]

You have an XY problem; you are using Jessie, the older version of Debian, and looking at the version in the current release of Debian, Stretch. And no, don't add the Stretch repo, that will break Jessie if you don't do a full upgrade to Stretch.

The normal method of getting a newer application onto an older Debian without breaking it is to see if it's in the backports repository, or see if you can find it in another backports repo, or try and backport it yourself.

The "multimedia" repo packages are not official Debian, and some of those have caused big problems to users in the past. And they have "dmo" in the version.

[RU55EL]

I see, the command works if the package is on your system or not.

As long as the package is included in what is accessible by your sources.list file.

For example, this is my sources.list file:

Code: Select all

deb  http://deb.debian.org/debian/ stretch main

deb  http://deb.debian.org/debian/ stretch-updates main

deb http://security.debian.org/ stretch/updates main

When I try something that is not in "main":

Code: Select all

russel@nuc-desktop:~$ apt-cache policy firmware-atheros
N: Unable to locate package firmware-atheros

When I try something that is in "main":

Code: Select all

russel@nuc-desktop:~$ apt-cache policy transmission
transmission:
  Installed: (none)
  Candidate: 2.92-2
  Version table:
     2.92-2 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages

So, "non-free" and "contrib" need to be in your sources.list file entries to see the apt-cache policies from "non-free" and "contrib".

[Soapm]

I see, makes sense...

@steve... Actually the version I asked about is the Jessie version, Stretch has version 2.92-2.

I was doing all the last updates prior to upgrading to Stretch which is what made me notice the discrepancy. I botched my update from Wheezy so am being very careful not to mess up this one to Stretch.

[sunrat]

Does this show I have the latest version or any reason mines won't update? The above link says 2.84-0.2 is the latest version.

Code: Select all

root@lenny:/# apt-cache policy transmission
transmission:
  Installed: 2.84-1
  Candidate: 2.84-1
  Version table:
 *** 2.84-1 0
        100 /var/lib/dpkg/status
     2.84-0.2 0
        500 http://deb.debian.org/debian/ jessie/main amd64 Packages

It says the current version in Jessie is 2.84-0.2. 2.84-1 appears to be a more recent version than 2.84-0.2, how did you install that?

[Soapm]

Does this show I have the latest version or any reason mines won't update? The above link says 2.84-0.2 is the latest version.

Code: Select all

root@lenny:/# apt-cache policy transmission
transmission:
  Installed: 2.84-1
  Candidate: 2.84-1
  Version table:
 *** 2.84-1 0
        100 /var/lib/dpkg/status
     2.84-0.2 0
        500 http://deb.debian.org/debian/ jessie/main amd64 Packages

It says the current version in Jessie is 2.84-0.2. 2.84-1 appears to be a more recent version than 2.84-0.2, how did you install that?

Who knows, but that was my concern. I believe I would have used aptitude but that would have been back in 2014 when I got the new motherboard.

However, I just did my Stretch update and it updated this package to 2.92...

Code: Select all

root@lenny:/# apt-cache policy transmission
transmission:
  Installed: 2.92-2
  Candidate: 2.92-2
  Version table:
 *** 2.92-2 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status