How to locate software packages in antiX repos

[seaken64]

So, I noticed that several of the disabled repos in my antiX-16 system are for "stretch". I also noticed that I had the choice to install antiX-16.3 with the "stretch" repo (I chose Jessie).

Why does this antiX-16.3 install have the option to use the stretch repos? I thought it was Jessie based.

Maybe I should put this question in another topic.

Seaken64

[seaken64]

Streamtuner 2.2.1 backports to a Jessie base, so here's MX 15 along with MX 17 packages. You'll need to install the python3-pyquery deb in the pyquery folder first for a Jessie base--Stretch already has it.

https://drive.google.com/open?id=1rSUyh ... zWy92tiatr

Thank you Stevo,

I downloaded your zip file. If I understand you correctly I need to move two .deb files to my antiX-16 system and run the python3-pyquery.deb first and then the streamtuner2_mx15.deb second. And I use the "gdebi" program to install the .deb files?

Seaken64

[seaken64]

I noticed that the Debian testing repo is on my list of sources, but disabled. Repology says streamtuner2_2.2.1 is in that repo. Would it be okay to enable that repo and then install it and then disable it?

Or is it better to use the package from the MX-15 repo, assuming Stevo is planning to put that in the MX repos?

What would be the difference?

Seaken64

[asqwerth]

I noticed that the Debian testing repo is on my list of sources, but disabled. Repology says streamtuner2_2.2.1 is in that repo. Would it be okay to enable that repo and then install it and then disable it?

Seaken64

No. I have already informed you in another thread that Debian Testing is not MX Test Repo and is based on a different Debian base from the one you are on.

antiX has that source disabled because during Installation, you could choose to install antiX as a Debian Stable, or Testing or Unstable (Sid) distro.

[seaken64]

Okay, I kind of understand, maybe. Debian testing is based on stretch? and not Jessie. When Jessie was current testing was compatible with Jessie, but no more since they have moved on to Stretch? Is that correct?

[asqwerth]

You are on Jessie for antiX16. When antiX16 (Jessie) was FIRST released, Testing was compatible with Stretch. If you had chosen Testing as your base upon installation, you would not be on Jessie base. You would be on a Debian sort of rolling distro based on Testing, and by now your system would be essentially at Debian Buster level.

The use of the generic "Testing" means it's what's currently inside as at present date, not at the time antiX16 was released. So right now if you enable Debian Testing, you get what's inside it RIGHT NOW, which is Debian Buster stuff.

That is WAY newer than Jessie base that you are on.

[caprea]

The current state of play is as follows

jessie=oldstable
stretch=stable
buster=testing
sid=unstable

But this is an ongoing process.At the time of the release of antiX16 jessie was the stable.Now stretch is stable (antiX17)
In 2019 buster will get the stable, stretch the oldstable and so on.
jessie will get Long Term Support until June 30, 2020, but this is mainly about security
https://wiki.debian.org/LTS

On antiX and also on MX you should never mix stable with unstable or testing (buster with stretch or jessie). Sooner or later it will break your system.
This has nothing to do with the MX-test repo, which are special backported packages in a safe manner by the devs.

But with antiX you also have the possibility to set your complete system to testing repos (not buster but just testing).
And testing will always stay testing, same as sid, sid will always stay sid.Both keep rolling.
That means then you have a rolling distribution, and also means you have always the newest software. I have one antiX-installation rolling with testing since four years,and I know there are people who did this already much longer.

I hope this gives a first impression of how things behave on antiX.

Not sure why apt policy doesn't work for you on antiX16, maybe apt-cache policy works.
And don't mix the repos.

[asqwerth]

As I understand it, in Jessie and older, Debian was not using the apt family of commands (which were Ubuntu-derived, I think). Debian's commands were all:

Code: Select all

apt-[another word] something

For example:

Code: Select all

apt-get install packagename

From Debian Stretch onwards, you are able to use

Code: Select all

apt install [packagename]

So the apt series of commands are now used more or less interchangeably with the apt-[another word] family of commands

[cyrilus31]

@seaken : Just curious...As you made a complete installation, why did you choose antiX 16 instead of the latest version?

[Jerry3904]

@seaken : Just curious...As you made a complete installation, why did you choose antiX 16 instead of the latest version?

That is THE question!