Mepis 11.0 Preferences Pinning

Discussion about the MEPIS Community's Repo.
Message
Author
User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 8895
Age: 57
Joined: Wed Jul 12, 2006 2:26 pm

Mepis 11.0 Preferences Pinning

#1 Postby kmathern » Sun Feb 13, 2011 6:31 pm

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

Package: *
Pin: release o=Mepis community repository, n=mepis11cr
Pin-Priority: 901


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.

User avatar
sdbingm
Forum Regular
Forum Regular
Posts: 276
Age: 55
Joined: Sun Mar 02, 2008 11:50 am

Re: Mepis 11.0 Preferences Pinning

#2 Postby sdbingm » Sun Feb 13, 2011 8:54 pm

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 :rolleyes:
AMD Phenom II X6 1055T Processor, Nvidia GTS 450, LG W2042TQ (1680x1050)/ViewSonic VP191b(1280x1024), Broadcom BCM4306 Wireless, 8GB RAM
M11-64, +sid, +KDE SC 4.11.3, liquorix 3.12-4 , Nvidia 331.20
Image

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 8895
Age: 57
Joined: Wed Jul 12, 2006 2:26 pm

Re: Mepis 11.0 Preferences Pinning

#3 Postby kmathern » Sun Feb 13, 2011 9:10 pm

sdbingm wrote: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 :rolleyes:

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}

User avatar
sdbingm
Forum Regular
Forum Regular
Posts: 276
Age: 55
Joined: Sun Mar 02, 2008 11:50 am

Re: Mepis 11.0 Preferences Pinning

#4 Postby sdbingm » Sun Feb 13, 2011 9:16 pm

kmathern wrote:
sdbingm wrote: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 :rolleyes:

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.


I know, that's what I did, I was just commenting on the suggested pin level. Still needs evaluation I guess.
AMD Phenom II X6 1055T Processor, Nvidia GTS 450, LG W2042TQ (1680x1050)/ViewSonic VP191b(1280x1024), Broadcom BCM4306 Wireless, 8GB RAM
M11-64, +sid, +KDE SC 4.11.3, liquorix 3.12-4 , Nvidia 331.20
Image

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 10941
Age: 57
Joined: Fri Dec 15, 2006 8:07 pm

Re: Mepis 11.0 Preferences Pinning

#5 Postby Stevo » Mon Feb 14, 2011 1:43 am

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

User avatar
DBeckett
Forum Veteran
Forum Veteran
Posts: 3064
Joined: Sat May 16, 2009 3:59 pm

Re: Mepis 11.0 Preferences Pinning

#6 Postby DBeckett » Mon Feb 14, 2011 2:48 am

.
That's what I did, and it worked great. Curiously, after the install it set itself back to "prefer highest version."
Gigabyte 990FXA-UD3, AMD FX-6100 hex-core, 3.3GHz, 8G, Radeon HD6570

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 8895
Age: 57
Joined: Wed Jul 12, 2006 2:26 pm

Re: Mepis 11.0 Preferences Pinning

#7 Postby kmathern » Mon Feb 14, 2011 12:09 pm

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

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.

Code: Select all

kent@mepis1:~$ apt-cache policy digikam
digikam:
  Installed: 2:1.2.0-7+b1
  Candidate: 2:1.2.0-7+b1
  Version table:
     2:1.8.0-1mcr110+1 0
        901 http://main.mepis-deb.org/mepiscr/repo/ mepis11cr/main i386 Packages
 *** 2:1.2.0-7+b1 0
        990 ftp://ftp.mepis.com/mepis/ mepis-11.0/main i386 Packages
        100 /var/lib/dpkg/status
     2:1.2.0-7 0
        801 ftp://ftp.debian.org/debian/ squeeze/main i386 Packages
 kent@mepis1:~$


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.
(snippet from Warren's Mepis 11.0 repository release file: ftp://ftp.mepis.com/mepis/dists/mepis-11.0/Release)

Origin: MEPIS
Label: MEPIS
Suite: mepis
Codename: mepis-11.0
Version: 11.0
Date: Sun, 13 Feb 2011 01:34:34 UTC
Architectures: i386 amd64
Components: main
Description: MEPIS 11.0
MD5Sum: .....

(snippet from the Mepis 11 CR repository release file: http://main.mepis-deb.org/mepiscr/repo/ ... cr/Release)

Origin: Mepis community repository
Label: Mepis community repository
Suite: mepis
Codename: mepis11cr
Version: 11.0
Date: Fri, 11 Feb 2011 22:00:28 UTC
Architectures: i386 amd64
Components: main non-free restricted restricted-non-free
Description: This is the Mepis community repository
MD5Sum:.....

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.
(snippet from Warren's Mepis 7.0 repository release file: ftp://ftp.mepis.com/mepis/dists/mepis-7.0/Release)

Origin: MEPIS
Label: MEPIS
Suite: mepis
Codename: mepis-7.0
Version: 7.0
Date: Sat, 26 Jul 2008 11:09:15 +0000
Architectures: i386 amd64
Components: main
Description: MEPIS 7.0
MD5Sum: .....

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.
(snippet from the Mepis 7.0 CR repository release file: http://main.mepis-deb.org/mepiscr/repo/ ... cr/Release)

Origin: Mepis community repository
Label: Mepis community repository
Suite: mepis
Codename: mepis7cr
Version: 7.0
Date: Sat, 25 Apr 2009 14:03:46 +0000
Architectures: i386 amd64
Components: main non-free restricted restricted-non-free
Description: This is the Mepis community repository
MD5Sum:.....


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}

Code: Select all

kent@mepis1:~$ apt-cache policy digikam
digikam:
  Installed: 2:1.2.0-7+b1
  Candidate: 2:1.8.0-1mcr110+1
  Version table:
     2:1.8.0-1mcr110+1 0
        990 http://main.mepis-deb.org/mepiscr/repo/ mepis11cr/main i386 Packages
 *** 2:1.2.0-7+b1 0
        990 ftp://ftp.mepis.com/mepis/ mepis-11.0/main i386 Packages
        100 /var/lib/dpkg/status
     2:1.2.0-7 0
        801 ftp://ftp.debian.org/debian/ squeeze/main i386 Packages
 kent@mepis1:~$


Return to “CR Discussion”

Who is online

Users browsing this forum: No registered users and 1 guest