Dev1 Galaxy Forum / [SOLVED] Five-or-more pinning to older version

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (rolfie) — Fri, 16 Dec 2022 18:49:43 +0000

Well, don't fully understand the reasoning. The filename did not include the epoch, and I used that info for the pref file. The epoch is present in Synpatic and when you look closely to the printout of apt policy, but I never thought it would be important, based on the examples I saw.

So far so bad, its solved. Again what learned ....

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (Head_on_a_Stick) — Fri, 16 Dec 2022 18:43:05 +0000

rolfie wrote:

Why is this "1:" you call it epoch required?

The epoch is part of the version string. See also https://www.debian.org/doc/debian-polic … ml#version.

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (rolfie) — Fri, 16 Dec 2022 18:37:41 +0000

Why is this "1:" you call it epoch required? Well it works this way.

I scanned through the man apt_preferences, the Ubuntu wiki article, and other in the internet before posting here, didn't see that in the examples given ....

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (Head_on_a_Stick) — Fri, 16 Dec 2022 18:16:01 +0000

You forgot to add the epoch:

Package: five-or-more*
Pin: version 1:3.30.0*
Pin-Priority: 1001

Tested and works for me.

EDIT: added asterisk after package name to cover multi-arch systems.

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (rolfie) — Fri, 16 Dec 2022 18:14:30 +0000

# apt policy
Paketdateien:
 100 /var/lib/dpkg/status
     release a=now
 500 http://deb.devuan.org/merged daedalus/non-free i386 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=non-free,b=i386
     origin deb.devuan.org
 500 http://deb.devuan.org/merged daedalus/non-free amd64 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=non-free,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged daedalus/contrib i386 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=contrib,b=i386
     origin deb.devuan.org
 500 http://deb.devuan.org/merged daedalus/contrib amd64 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=contrib,b=amd64
     origin deb.devuan.org
 500 http://deb.devuan.org/merged daedalus/main i386 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=main,b=i386
     origin deb.devuan.org
 500 http://deb.devuan.org/merged daedalus/main amd64 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
Mit Pinning verwaltete Pakete:
# apt policy five-or-more
five-or-more:
  Installiert:           1:3.30.0-2
  Installationskandidat: 1:3.32.3-1
  Versionstabelle:
     1:3.32.3-1 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
 *** 1:3.30.0-2 100
        100 /var/lib/dpkg/status

Re: [SOLVED] Five-or-more pinning to older version

dummy@example.com (Head_on_a_Stick) — Fri, 16 Dec 2022 18:07:40 +0000

Can we see

apt policy
apt policy five-or-more

Thanks!

[SOLVED] Five-or-more pinning to older version

dummy@example.com (rolfie) — Fri, 16 Dec 2022 18:03:52 +0000

Daedalus with Cinnamon DE.

The counting of results of the game five-or-more is broken since Chimaera, and hasn't been fixed in Daedalus. I removed the package from the installation, downloaded the older version five-or-more_3.30.0-2_amd64.deb from Beowulf and installed it with dpkg -i. I think I had to install an additional dependency. The older program is working.

To keep the package, I added a file five-or-more to /etc/apt/preferences.d with the contents:

Package: five-or-more
Pin: version 3.30.0*
Pin-Priority: 1001

When I run an apt update this setting is ignored, I still get the version 3.32.3 listed as installation candidate.

What is wrong in my setup? Why is the preference ignored? Shouldn't I see the setting immediately in apt-cache policy?

rolfie