MEPIS Community Forum

For the Mepis 11.0 CR's I've added the follow pinning info to the Mepis 11 sources.list wiki article: http://www.mepis.org/docs/en/index.php? ... t_MEPIS_11



From the tests I've done it appears that the 'o=Mepis community repository, n=mepis11cr' gives the same pinning results as the 'a=mepis' that was used for Mepis 8.5 and it's clearer {to me anyway} as to which repo is being pinned. Feel free to change it if I'm wrong.

I got mixed results. After reloading, digikam-data from the 11CR repo was available for update but digikam itself was not. When I marked digikam-data and pressed apply it said it was going to remove digikam

If you force install digikam (click on digikam, press Ctrl+E and the choose the newest mepis version) you can install digikam 1.8.0.

In a different thread timkb4cq said the CR's pinning level should be '901'.

You need to 'force' install digikam because the default release setting in the /etc/apt/apt.conf file is setting the pinning of Warren's digikam package at the '990' level {instead of 901 or 902}

I know, that's what I did, I was just commenting on the suggested pin level. Still needs evaluation I guess.

Instead of force-installing, you can set Synaptic to prefer "mepis" packages, then the CR versions will be seen as upgrades.

.
That's what I did, and it worked great. Curiously, after the install it set itself back to "prefer highest version."

It seems to me that if the CR repos have been pinned properly, that you shouldn't need to change Synaptic's preferences or 'force install' to get an updated CR package installed.

I think that the APT::Default-Release "mepis-11.0"; setting from the /etc/apt/apt.conf file might be causing the problem.

The "mepis-11.0" sets Warren's repo as the default release and it bumps up the pinning level of his digikam package to a 990 pin level instead of a 901 or 902 level from the /etc/apt/preferences file.

Shown below is the output of the apt-cache policy command, note that the CR version of Digikam is not a 'Candidate' for upgrade.


The "xxxxx" part of the APT::Default-Release "xxxxx" entry can be one of several items {Origin, Label, Suite, Codename, Version} from a repository's release file.


Currently Warren is using the "mepis-11.0" codename of his repo to set the default release. Using "mepis-11.0" excludes the Mepis 11.0 CR repos from the default release.

In Mepis 7.0 the default release was "mepis" which is the 'Suite: mepis' entry in Warren's M7.0 repository release file.

The repository release files of the Mepis 7 CR's also had a 'Suite: mepis' entry so the Mepis 7.0 CR's were included as part of the default release for Mepis 7.0.


For Mepis 8.0 the default release was "8.0" which is the 'Version: 8.0' entry from Warren's M8.0 repository release file. The repository release files of the Mepis 8 CR's also had a 'Version: 8.0' entry so the Mepis 8.0 CR's were included as part of the default release for Mepis 8.0.

{Warren's Mepis 8.0 repository release file and the Mepis 8.0 CR repository release file are similar to the M7 snippets shown above except the 7's change to 8's}

For Mepis 11.0, instead of the current entry of "mepis-11.0", maybe the default release in the /etc/apt/apt.conf file should be set to either "mepis" or "11.0" which would allow the M11 community repositories to be included as part of the default release.

After changing the default release to "mepis" the newest Digikam is listed as an upgrade candidate as shown in the apt-cache policy command's output below. It's also a simple upgrade of the digikam package in Synaptic {just mark digikam for upgrade}