pacman, exclude specific version of package

M5Hc6UsQ · 2019-10-28 10:55:54

Hi,

is it possible to exclude a specific version of a package from updating? I've found the '--ignore' flag, but the manual doesn't mentions how to specify a version number. I'd like to exclude a package version without missing further updates. Current example is 'mpv 0.30' which has some bugs and requires a downgrade to 0.29, at least when used with smplayer.

schard · 2019-10-28 11:28:52

There are no native means of doing this. IgnorePkg from pacman.conf does not consider package versions.
Your best option would be to re-package 0.29 as 0.30 and install it.

Last edited by schard (2019-10-28 11:29:27)

progandy · 2019-10-28 13:00:24

pacman prints a warning when an update is ignored. This warning includes the new version number, so when you notice a fixed version you can remove the ignore entry again.

Anyways, with mpv/smplayer the fix will probably be in the smplayer package, so there will be no new fixed release of the mpv package and this version-specific ignore wouldn't solve your issue. https://app.assembla.com/spaces/smplaye … mmits/9232

Last edited by progandy (2019-10-28 13:07:53)

M5Hc6UsQ · 2019-10-28 15:12:55

schard wrote:

Your best option would be to re-package 0.29 as 0.30 and install it.

Is it possible to just change the version number without re-building the whole package?

progandy wrote:

pacman prints a warning when an update is ignored. This warning includes the new version number, so when you notice a fixed version you can remove the ignore entry again.

Yes that's what I currently do. The issue I have with this is that I always have to remember or look up the version I want to ignore because the warning is shown everytime I upgrade and not only if there is a new version in the database.

progandy wrote:

Anyways, with mpv/smplayer the fix will probably be in the smplayer package, so there will be no new fixed release of the mpv package and this version-specific ignore wouldn't solve your issue. https://app.assembla.com/spaces/smplaye … mmits/9232

Thanks for the info!

Last edited by M5Hc6UsQ (2019-10-28 15:14:29)

loqs · 2019-10-28 16:22:24

Would it not be better to apply the fix?

git clone git://git.archlinux.org/svntogit/community.git --single-branch --branch "packages/smplayer" #clone PKGBUILD
cd community trunk
svn diff -r 9231:9232 https://subversion.assembla.com/svn/smplayer/smplayer/trunk > 9232.patch #obtain patch

diff of changes to PKGBUILD to apply patch

diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index 485049d..474d9db 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -18,14 +18,18 @@ optdepends=('smplayer-themes: icon themes collection'
             'smtube: browse and play youtube videos'
             'youtube-dl: youtube videos and streaming'
             'mplayer: alternative multimedia engine')
-source=(https://downloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.bz2)
-sha256sums=('b5cb2b37fc9a225bb7287bf26a0a499f7b46bff688161b8e5eae0d96d74daaf5')
-sha512sums=('ee19186b3f4eac94b06a1e389e42edb8c2b22f8182b679bdc40e3ae1569a6c69f168260abfee3b2827b71b10eb353e7a3821805798f37aae2600af3b73d25ca1')
+source=(https://downloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.bz2
+        9232.patch)
+sha256sums=('b5cb2b37fc9a225bb7287bf26a0a499f7b46bff688161b8e5eae0d96d74daaf5'
+            'cc230766a833f51d1e1b9ef11938c86a27db6a4e1cc4489f91040e40fca212c0')
+sha512sums=('ee19186b3f4eac94b06a1e389e42edb8c2b22f8182b679bdc40e3ae1569a6c69f168260abfee3b2827b71b10eb353e7a3821805798f37aae2600af3b73d25ca1'
+            '2312190dfd4b859a81581972048de4b80b708f47d69effb9145e95c4730d766e0837e49d4a175a73875b6a0b63462837c3ad2e0f0457d1c37901eb6e72c37dda')
 
 prepare() {
   cd ${pkgname}-${pkgver}
   # make build reproducible, we compress ourselves
   sed '/gzip -9/d' -i Makefile
+  patch -p0 -i ../9232.patch
 }
 
 build() {

makepkg -rsi #to install package

M5Hc6UsQ · 2019-10-31 14:02:18

@loqs Yes that solves the issue with smplayer/mpv, but doesn't answers my question. The issue with the mpv package was just the latest example.

loqs · 2019-10-31 17:42:54

Looking at the questions you asked the only one I have not seen answered is:

M5Hc6UsQ wrote:

Is it possible to just change the version number without re-building the whole package?

Which I have never attempted.

Lone_Wolf · 2019-11-01 11:22:15

Maybe ayekat' tool remakepkg can do that https://bbs.archlinux.org/viewtopic.php?id=234936

WorMzy · 2019-11-01 12:24:16

Pacman's db is just text files and directories, you can modify/forge entries with mv and a text editor, but this is not something you should be doing routinely just to avoid an update.

Arch Linux

#1 2019-10-28 10:55:54

pacman, exclude specific version of package

#2 2019-10-28 11:28:52

Re: pacman, exclude specific version of package

#3 2019-10-28 13:00:24

Re: pacman, exclude specific version of package

#4 2019-10-28 15:12:55

Re: pacman, exclude specific version of package

#5 2019-10-28 16:22:24

Re: pacman, exclude specific version of package

#6 2019-10-31 14:02:18

Re: pacman, exclude specific version of package

#7 2019-10-31 17:42:54

Re: pacman, exclude specific version of package

#8 2019-11-01 11:22:15

Re: pacman, exclude specific version of package

#9 2019-11-01 12:24:16

Re: pacman, exclude specific version of package

Board footer