Package Details: python-dmidecode 3.12.3-2

Git Clone URL: (read-only, click to copy)
Package Base: python-dmidecode
Description: Python module to access DMI data
Upstream URL:
Licenses: GPL2
Submitter: robertfoster
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 3
Popularity: 0.000012
First Submitted: 2016-08-27 23:27 (UTC)
Last Updated: 2023-05-28 10:58 (UTC)

Latest Comments

atomicfs commented on 2023-04-09 10:20 (UTC)

I just came across the same problem, so I have marked the package as outdated. @robertfoster seems to be active on AUR, but he is maintaining a butload of packages, I my guess is that he just missed this.

newsboost commented on 2022-12-27 13:03 (UTC) (edited on 2022-12-27 13:06 (UTC) by newsboost)

@kyak: Thanks a lot. This is really terrible. It took some attempts and I think you're right that it has to fail the first time (as it copies a shared library into the build-folder), otherwise it'll write:

==> Starting package()...
python310 src/ build
/bin/bash: line 1: python310: command not found
make: *** [Makefile:65: build/lib.linux-x86_64-cpython-310/] Error 127

And still I had some minor issues. In the end I think I also had to run "makepkg -ei" to install and now it doesn't appear in the list of upgradeable packages and all seems good.

@robertfoster: Please look into this issue and respond (I might help if needed, but I don't know how to solve the problem of having to publish/upload a patch-file somewhere, for the prepare()-function).

I'm surprised there aren't more users needing this upgrade - but in any case, the instructions should be here now. Thanks @kyak!

kyak commented on 2022-12-27 03:12 (UTC)


Run makepkg the first time and let it fail. Then edit src/python-dmidecode-3.12.3/Makefile. After than, run makepkg -e.

I suggest you read man makepkg if you use AUR, it's enlightening.

And yes, it's pity that @robertfoster is not responding.

newsboost commented on 2022-12-26 18:16 (UTC) (edited on 2022-12-26 18:18 (UTC) by newsboost)

Also, I don't maintain this package and therefore can't change PKGBUILD anyway.

Oh, I'm sorry. I just assumed it was the maintainer who replied, I can see you're right... So we're at least 2 people with this problem (and I have 2 Arch pc's with this problem)... Would be nice if the maintainer wrote something now and either adopted the proposed Makefile-patch-solution or had an alternative solution...

It's a bit (=very) annoying that this is the only package I cannot update. How to force "makepkg" to install it with the workaround to the makefile you made, so this package doesn't constantly turn up as "upgradeable", which it currently isn't? Thanks a lot for your time and help!

kyak commented on 2022-12-26 17:33 (UTC)

What do you think about changing the PKGBUILD

I'd rather have it fixed upstream. But they are not able to reproduce. If they don't fix it upstream, it makes sense to simply carry on this Makefile patch for Arch Linux.

Also, I don't maintain this package and therefore can't change PKGBUILD anyway.

newsboost commented on 2022-12-26 17:20 (UTC) (edited on 2022-12-26 17:48 (UTC) by newsboost)

@kyak: Thanks a lot (and sorry, I think I made a mistake, apparently I hadn't enabled notifications, that has been rectified now). So, today I made a full upgrade on my other pc and from my point of view, maybe it's an "Arch Linux"-only issue. What do you think about changing the PKGBUILD so it somehow modifies:

build/lib.linux-x86_64-3.10/' -->

Just in the PKGBUILD for Arch Linux? Would be nice to hear if other people has (or has not) the problem on Arch Linux, but I've now had this issue with 2 pc's so I think it's probably the same story on all Arch Linux-systems...? hmm. I just tried to use your patch-file and follow the procedure here (including create the "prepare-function"): - but I'm having a problem, because I get:

==> Validating source files with sha256sums...
    python-dmidecode.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!

because I don't know where/how to upload the patch-file (which is similar to your makefile-diff) so it's available... I think you/we need to follow steps 1+2 here: and maybe later when Ubuntu/Debian folks will get python 3.10.9 (or maybe it's just Arch Linux?) they'll see the same problem? Just thinking out loud here, appreciate the upstream bug report, although they won't fix it when they don't see the issue...

kyak commented on 2022-12-19 20:10 (UTC)

@newsboost I was able to fix it by modifying the Makefile.

I've reported it upstream here:

They don't seem to be able to reproduce though.

newsboost commented on 2022-12-19 18:58 (UTC)

Hi. As @kyak wrote, this does not seem to work, as it tries to cp something that doesn't exist, resulting in "==> ERROR: A failure occurred in package()". Will this be fixed soon? How should PKGBUILD be modified to install correctly?

kyak commented on 2022-12-04 09:52 (UTC)

There is an error:

cp build/lib.linux-x86_64-3.10/
cp: cannot stat 'build/lib.linux-x86_64-3.10/': No such file or directory
make: *** [Makefile:63:] Error 1
==> ERROR: A failure occurred in package().

The correct path should be build/lib.linux-x86_64-cpython-310/