You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2009-10-28 04:48:23
- Falcata
- Member
- From: Michiana
- Registered: 2008-01-23
- Posts: 501
- Website
Apparent bug in makepkg
Running makepkg with the --skipinteg flag will cause makepkg to skip integrity checks with md5sums, but not sha256sums. I ran into this problem while making a bin32-wine package with a custom build of wine, and had to comment out the sha256sums line in the PKGBUILD in order to get the package to build.
Offline
#2 2009-10-28 04:51:19
- lucke
- Member
- From: Poland
- Registered: 2004-11-30
- Posts: 4,019
Re: Apparent bug in makepkg
--skipinteg doesn't ignore *sums, it just makes makepkg not fail when *sums aren't present (emulating default behaviour prior to pacman 3.3).
Offline
#3 2009-10-28 04:51:58
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,651
- Website
Re: Apparent bug in makepkg
Can you give exact output from makepkg and the PKGBUILD being used? Even better, do it in a bug report....
Offline
#4 2009-11-01 20:20:36
- Falcata
- Member
- From: Michiana
- Registered: 2008-01-23
- Posts: 501
- Website
Re: Apparent bug in makepkg
[zauber@myhost bin32-wine]$ makepkg --skipinteg
==> Making package: bin32-wine 1.1.32-1 x86_64 (Sun Nov 1 15:12:44 EST 2009)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found wine-1.1.32-1-i686.pkg.tar.gz in build dir
==> Validating source files with md5sums...
wine-1.1.32-1-i686.pkg.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!Offline
#5 2009-11-01 23:37:37
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,651
- Website
Re: Apparent bug in makepkg
That is an issue with the bin32-wine package. It seems to need its md5sums corrected.
Offline
Pages: 1