How do I disable the MX Test Repository?

[eband]

I learned that that after installing stuff from the MX Test Repository, I should disable it.

I upgraded some packages, so how do I disable it?

[dolphin_oracle]

post your quick-system-info please.

the short side is do the opposite that you did to enable it.

the long side is that the test repo tab in mx packageinstaller enables and disables test repo on the fly. it enables for the install, then disables after.

your qsi will confirm whether the repo is disabled or enabled.

[FullScale4Me]

Ah, beat me to it. NM!

[Adrian]

MX Repo Manager allows to tick off to disable repos.

[MXRobo]

@eband
"I learned that that after installing stuff from the MX Test Repository, I should disable it."
You may have learned incorrectly because that statement implies that you would first enable it.

The testrepo in MX-Repo-Manger>Individual Sources – mx.list in normally disabled, but when installing a package from MXPI>MX-Test-Repo, the repo is temporarily enabled so that it can install those packages, after installing it is disabled, this avoids dependency conflicts. So really no need to touch it in MX-Repo-Manager.
HTH

[eband]

So, it's done automatically for me.

[MXRobo]

Yes!
And I'm fairly sure it's the same for the Debian Backports tap.

[eband]

Well, one less thing to worry about.

Thanks!

[asqwerth]

well, to be safe, what is the output of

inxi -r

if you run that command in terminal?

If the list of repos displayed doesn't include MX Test Repo and Debian Backports, it shows the position to be as default, ie Test and Backports are normally turned off. That way, MX Packageinstaller (MXPI) will work normally and only turn Test or Backports on when you are actually installing a package from there via MXPI.

[Stevo]

Adrian has coded MXPI to handle things pretty much automagically for users, but one needs know to use MXPI in the first place. Many have assumed that MX works the exact same way as plain Debian, or Ubuntu with its exclusive PPAs.