Help with ABS

BlackArts · 2011-02-05 14:43:25

Hi. 2 days ago, I managed to setup photoshop cs4 runing on wine, but suddenly it stopped working today when after system upgrade. I noticed that wine version changed, so I searched on wiki to find how to get previous versions. Now... I found article on ABS, so I copied wine folder from abs tree, to my home/my username/abs directory. In wine pkgbuild I found in copied directory, I modified version to 1.2.2 which is last stable as I read on winehq. When I go to abs/wine and run makepkg -s I get this:

==> Making package: wine 1.2.2-1 (Sat Feb  5 15:37:06 CET 2011)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found wine-1.2.2.tar.bz2
==> Validating source files with md5sums...
    wine-1.2.2.tar.bz2 ... FAILED
==> ERROR: One or more files did not pass the validity check!

Anyway, I thought that abs is created so that I can get source from some completely unknown software, and, I don't know.., compile it and make some sort of installation script for arch, and this is same as downloading from aur and running makepkg -si. Am I getting something wrong? Because, I've allready downloaded source from winehq, so I was kind of disappointed. I expected that I'll have to put this source into abs/wine folder and then do something with it.

Any ideas how to make this work? Here's PKGBUILD:

# $Id: PKGBUILD 38999 2011-02-04 20:31:47Z svenstaro $
# Maintainer: Sven-Hendrik Haase <sh@lutzhaase.com>
# Contributor: Jan "heftig" Steffens <jan.steffens@gmail.com>
# Contributor: Eduardo Romero <eduardo@archlinux.org>
# Contributor: Giovanni Scafora <giovanni@archlinux.org>

pkgname=wine
pkgver=1.2.2
pkgrel=1

_pkgbasever=${pkgver/rc/-rc}

source=(http://ibiblio.org/pub/linux/system/emulators/$pkgname/$pkgname-$_pkgbasever.tar.bz2)
md5sums=('e6d4cd7e51678f90760e2193893637aa')

pkgdesc="A compatibility layer for running Windows programs"
url="http://www.winehq.com"
arch=(i686 x86_64)
license=(LGPL)
install=wine.install

depends=(
  fontconfig      lib32-fontconfig
  mesa            lib32-mesa 
  libxcursor      lib32-libxcursor
  libxrandr       lib32-libxrandr
  libxdamage      lib32-libxdamage
  libxxf86dga     lib32-libxxf86dga
  alsa-lib        lib32-alsa-lib
)

makedepends=(autoconf ncurses bison perl fontforge flex prelink
  'gcc>=4.5.0-2'  'gcc-multilib>=4.5.0-2'
  giflib          lib32-giflib
  libxpm          lib32-libxpm
  libpng          lib32-libpng
  libxinerama     lib32-libxinerama
  libxcomposite   lib32-libxcomposite
  libxmu          lib32-libxmu
  libxxf86vm      lib32-libxxf86vm
  libxml2         lib32-libxml2
  libxslt         lib32-libxslt
  libldap         lib32-libldap
  lcms            lib32-lcms
  mpg123          lib32-mpg123
  openal          lib32-openal
  jack            lib32-jack
  libcups         lib32-libcups
  gnutls          lib32-gnutls
  v4l-utils       lib32-v4l-utils
)
  
optdepends=(
  giflib          lib32-giflib
  libpng          lib32-libpng
  libldap         lib32-libldap
  lcms            lib32-lcms
  libxml2         lib32-libxml2
  mpg123          lib32-mpg123
  openal          lib32-openal
  jack            lib32-jack
  libcups         lib32-libcups
  gnutls          lib32-gnutls
  v4l-utils       lib32-v4l-utils
)

if [[ $CARCH == i686 ]]; then
  # Strip lib32 etc. on i686
  depends=(${depends[@]/*32-*/})
  makedepends=(${makedepends[@]/*32-*/})
  makedepends=(${makedepends[@]/*-multilib*/})
  optdepends=(${optdepends[@]/*32-*/})
else
  provides=("bin32-wine=$pkgver" "wine-wow64=$pkgver")
  conflicts=('bin32-wine' 'wine-wow64')
  replaces=('bin32-wine')
fi

build() {
  cd "$srcdir"

  # Allow ccache to work
  mv $pkgname-$_pkgbasever $pkgname

  # Get rid of old build dirs
  rm -rf $pkgname-{32,64}-build
  mkdir $pkgname-32-build

  if [[ $CARCH == x86_64 ]]; then
    msg2 "Building Wine-64..."

    mkdir $pkgname-64-build
    cd "$srcdir/$pkgname-64-build"
    ../$pkgname/configure \
      --prefix=/usr \
      --sysconfdir=/etc \
      --libdir=/usr/lib \
      --with-x \
      --enable-win64

    make

    _wine32opts=(
      --libdir=/usr/lib32
      --with-wine64="$srcdir/$pkgname-64-build"
    )

    export PKG_CONFIG_PATH="/usr/lib32/pkgconfig"
  fi

  msg2 "Building Wine-32..."
  cd "$srcdir/$pkgname-32-build"
  ../$pkgname/configure \
    --prefix=/usr \
    --sysconfdir=/etc \
    --with-x \
    "${_wine32opts[@]}"

  make
}

package() {
  msg2 "Packaging Wine-32..."
  cd "$srcdir/$pkgname-32-build"

  if [[ $CARCH == i686 ]]; then
    make prefix="$pkgdir/usr" install
  else
    make prefix="$pkgdir/usr" \
      libdir="$pkgdir/usr/lib32" \
      dlldir="$pkgdir/usr/lib32/wine" install

    msg2 "Packaging Wine-64..."
    cd "$srcdir/$pkgname-64-build"
    make prefix="$pkgdir/usr" \
      libdir="$pkgdir/usr/lib" \
      dlldir="$pkgdir/usr/lib/wine" install
  fi
}

# vim:set ts=8 sts=2 sw=2 et:

EDIT: Just to make a note. I uninstalled official wine version with pacman and removed .wine from my home. And btw, I'm seeing this md5 checksums all over the web lately, so I'm guessing it's some way to check weather package is corrupted or not? If someone can explane me how can I check package with md5checksum in addition, that would be cool.

EDIT: One more thing. It says in wiki "now you just need to build that from source..." does that mean I have tounpack tar I just got from running makepkg -s and run install script?

Last edited by BlackArts (2011-02-05 14:49:55)

thisoldman · 2011-02-05 20:50:10

You didn't want to use the ABS, you wanted to downgrade the Wine package. I expect you may still downgrade without too much trouble.

You should use this wiki article as your guide: https://wiki.archlinux.org/index.php/Do … g_Packages

BlackArts wrote:

I'm seeing this md5 checksums all over the web lately, so I'm guessing it's some way to check weather package is corrupted or not? If someone can explane me how can I check package with md5checksum in addition, that would be cool.

An md5sum is an integrity check to ensure that copies of a file match the original file. You can easily Google for linux howtos.

An ABS pkgbuild contains md5sums for the files in the current Arch version of the software. The md5sums should not match previous versions of the software. The files are not the same.

If you have problems downgrading Wine, others will help, I'm sure.

BlackArts · 2011-02-05 21:41:45

thisoldman wrote:

You didn't want to use the ABS, you wanted to downgrade the Wine package. I expect you may still downgrade without too much trouble.
You should use this wiki article as your guide: https://wiki.archlinux.org/index.php/Do … g_Packages
BlackArts wrote:
I'm seeing this md5 checksums all over the web lately, so I'm guessing it's some way to check weather package is corrupted or not? If someone can explane me how can I check package with md5checksum in addition, that would be cool.
An md5sum is an integrity check to ensure that copies of a file match the original file. You can easily Google for linux howtos.
An ABS pkgbuild contains md5sums for the files in the current Arch version of the software. The md5sums should not match previous versions of the software. The files are not the same.
If you have problems downgrading Wine, others will help, I'm sure.

Thank you, you're awesome. I'm using linux for about 3.5 weeks now, and I never would have thought that there would be something like A.R.M. Now I can test those wine versions to see with which photoshop work best. Linux is awesome! XD (had to say that, but can't say arch explicitly, cos I haven't tried other versions )

ewaller · 2011-02-06 00:22:10

I realize the point is moot, but let me close the loop on the ABS question.

You were very, very close. What you would have had to do is run makepkg -g It would have calculated new MD5 sums for the files you are trying to use in the package and printed them to the console. When you are sure the files are the ones you want to install to your system, you would incorporate those new checksums into the PKGBUILD, replacing the old ones. They are the key to making certain the PKGBUILD does not get tricked into installing something other than the maintainer of the PKGBUILD intended. Note that by changing the PKGBUILD, you are the maintainer (on your system).

BlackArts · 2011-02-06 09:21:26

I'm not sure if I should ask this here, but I'm little bit confused with naming standards for this wine package. In official repository Community, I can see that wine version is 1.3.13-1, but when I search in arm for wine, I find even greater versions Arm search. So I tried to download wine-1.3.12-1-i686.pkg.tar.xz package, for which I assumed was predcessor to current package that was updated few days ago. And since I installed wine just a day before the update, I know it's only one version difference. But with this package I downloaded I can't run photoshop. It says module not found (and I installed all the required stuff with winetricks).

So, is there a way to find out what exact package was before the current one, because it seems something's wrong with naming, unless arm also archives the future -.- (which I highly doubt).

thisoldman · 2011-02-06 10:02:07

The previous version was wine-1.3.12-1. The current version I have installed is wine-1.3.13-1.

Are you sure you're on a 32-bit machine? The "686" in the package name means it's for the 32-bit Arch installations. The 64-bit versions have "x86-64" in the package names.

You can check if the older version is still in your pacman cache. On my machine:

$ ls /var/cache/pacman/pkg/wine*
/var/cache/pacman/pkg/wine-1.3.12-1-x86_64.pkg.tar.xz
/var/cache/pacman/pkg/wine-1.3.13-1-x86_64.pkg.tar.xz

abenson · 2011-02-12 00:58:56

If you need to downgrade you can have a look at the package change history in the svn/git tree

http://projects.archlinux.org/svntogit/ … .git/tree/
find wine and then go to log

you should end up at

http://projects.archlinux.org/svntogit/ … t/log/wine

then have a look at the various upgrades - they will have a commit message something like

upgpkg: wine 1.3.12-1

click on the commit and you will be shown a diff of what changed (- red=old, +green=new)

you can even download the commit as a patch which you could apply in reverse (-R) to the latest PKGBUILD to get the old one

patch -R -p3 -i patchname

N.B. the patches are for files relative to the top of the git tree so you need to use -pn to 'slice off' n levels of directories

Arch Linux

#1 2011-02-05 14:43:25

Help with ABS

#2 2011-02-05 20:50:10

Re: Help with ABS

#3 2011-02-05 21:41:45

Re: Help with ABS

#4 2011-02-06 00:22:10

Re: Help with ABS

#5 2011-02-06 09:21:26

Re: Help with ABS

#6 2011-02-06 10:02:07

Re: Help with ABS

#7 2011-02-12 00:58:56

Re: Help with ABS

Board footer