Arch Linux

ManceRayder

Member

Registered: 2013-02-02

Posts: 3

PKGBUILD request for evasi0n

This is a little premature as it is still in beta for at least another day (the goal was to release it tomorrow, but it looks like it may be a few more days before testing is completed). Anyway, I was wondering if anyone was planning on building evasi0n (a jailbreak tool for iOS 6.x) for AUR. I see that some jailbreak tools for older versions of iOS are up there (redsn0w, absinthe). Project website: www.evasi0n.com .

Thanks!

cinelli

Package Maintainer (PM)

From: Los Angeles, California

Registered: 2012-08-10

Posts: 22

Website

Re: PKGBUILD request for evasi0n

This is a little premature as it is still in beta for at least another day (the goal was to release it tomorrow, but it looks like it may be a few more days before testing is completed). Anyway, I was wondering if anyone was planning on building evasi0n (a jailbreak tool for iOS 6.x) for AUR. I see that some jailbreak tools for older versions of iOS are up there (redsn0w, absinthe). Project website: www.evasi0n.com .

Thanks!

https://aur.archlinux.org/packages/evasi0n/

---

aur::dotshare.it::blog
"Stay true."

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,267

Re: PKGBUILD request for evasi0n

While I'm sure that PKGBUILD works, there's a LOT of problems with it.

1. pkgrel starts at 1, not 0.
2. you should delete empty variables, groups(), optdepends(), etc.
3. run ldd evasi0n.x86_64, there's actually a whole lot of dependencies.
4. gcc should not be in the makedeps, it's part of base-devel. I don't see where it's used anyway.
5. it doesn't need to "provide" itself
6. it certainly shouldn't "replace" itself
7. PKGBUILDs shouldn't reference $pkgdir in the build() function
8. PKGBUILDs should always have a package() function, and will be REQUIRED to in the future.
9. this really isn't an "any" architecture package, it's 'i686' and 'x86_64'. 'any' is for packages with just things like scripts or data that are architecture independent.
10. if you're going to use tar instead of bsdtar, it will need to be in the makedeps. bsdtar is a requirement of pacman/makepkg so is guaranteed to be there.
11. why are extracting it manually, anyway? makepkg does that for you.

Last edited by Scimmia (2013-02-06 12:03:36)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,267

Re: PKGBUILD request for evasi0n

Here's a more sane PKGBUILD. All of the deps appear to be satisfied by gtk2.

The i686 binary is linked to an old version of libssl. I don't know how it will affect functionality with that missing.

Also notice the use of a sha1sum instead of an md5sum. When upstream provides a checksum, you should use it.

pkgname=evasi0n
pkgver=1.0
pkgrel=1
pkgdesc="iOS 6.x Jailbreak"
arch=('i686'  'x86_64')
url="http://www.evasi0n.com"
license=('GPL')
depends=('gtk2')
source=('https://evad3rs.box.com/shared/static/5dped2c9ejnk5r6ahfpg.lzma')
sha1sums=('c9e4b15a161b89f0e412721f471c5f8559b6054f')

package() {
  cd "$srcdir/$pkgname-linux-$pkgver"

  install -Dm644 changelog.txt "$pkgdir/usr/share/$pkgname/changelog.txt"
  install -Dm644 README.txt "$pkgdir/usr/share/$pkgname/README.txt"

  install -Dm755 $pkgname "$pkgdir/usr/bin/$pkgname"
  if [[ "$CARCH" == "i686" ]]; then
    install -Dm755 $pkgname.x86 "$pkgdir/usr/bin/$pkgname.x86"
  else
    install -Dm755 $pkgname.x86_64 "$pkgdir/usr/bin/$pkgname.x86_64"
  fi
}

cinelli

Package Maintainer (PM)

From: Los Angeles, California

Registered: 2012-08-10

Posts: 22

Website

Re: PKGBUILD request for evasi0n

It was quick and rather dirty. Had a long day yesterday. But I did test it to make sure it worked.. All fixed though.

---

aur::dotshare.it::blog
"Stay true."

unifiedlinux

Member

Registered: 2012-11-03

Posts: 20

Re: PKGBUILD request for evasi0n

Hello everyone,

here's a updated version of the previous PKGBUILD for version 1.1 :

pkgname=evasi0n
pkgver=1.1
pkgrel=1
pkgdesc="iOS 6.x Jailbreak"
arch=('i686'  'x86_64')
url="http://www.evasi0n.com"
license=('GPL')
depends=('gtk2')
source=('https://evad3rs.box.com/shared/static/8smyi2ud2ts41icmtf50.lzma')
sha1sums=('6c06a6be87e003eee470eb749b42ffbaafcc9e62')

package() {
  cd "$srcdir/$pkgname-linux-$pkgver"

  install -Dm644 changelog.txt "$pkgdir/usr/share/$pkgname/changelog.txt"
  install -Dm644 README.txt "$pkgdir/usr/share/$pkgname/README.txt"

  install -Dm755 $pkgname "$pkgdir/usr/bin/$pkgname"
  if [[ "$CARCH" == "i686" ]]; then
    install -Dm755 $pkgname.x86 "$pkgdir/usr/bin/$pkgname.x86"
  else
    install -Dm755 $pkgname.x86_64 "$pkgdir/usr/bin/$pkgname.x86_64"
  fi
}

however in my case i have a problem, here are the errors i get :

/usr/bin/evasi0n.x86_64: /usr/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/evasi0n.x86_64)
/usr/bin/evasi0n.x86_64: /usr/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/evasi0n.x86_64)

and evasi0n doesn't detect my iPhone 5, even when libimobiledevice, libplist and usbmuxd are installed
i'm gonna try on another computer (with Archlinux).

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,267

Re: PKGBUILD request for evasi0n

The error means that evasi0n is being built against a copy of OpenSSL which contains versioned symbols. Upstream doesn't so this, so it's probably done in a patch maintained by the distribution they're using (Debian?). I THINK it should still work correctly.

cinelli

Package Maintainer (PM)

From: Los Angeles, California

Registered: 2012-08-10

Posts: 22

Website

Re: PKGBUILD request for evasi0n

The error means that evasi0n is being built against a copy of OpenSSL which contains versioned symbols. Upstream doesn't so this, so it's probably done in a patch maintained by the distribution they're using (Debian?). I THINK it should still work correctly.

It does.  It was tested.

Edit:
In 1.1 it seems to be fixed.. I had symlinks in the PKGBUILD to satisfy the libraries it complains about but was notified that it was no longer needed.

Last edited by cinelli (2013-02-08 09:04:55)

---

aur::dotshare.it::blog
"Stay true."