Unable to create PKGBUILD successfully

sundar_ima · 2014-04-27 13:00:25

Hi,
This is the first time I am creating package and would like to maintain this package https://aur.archlinux.org/packages/mult … setlang=en as I am the author of upstraem package. Here is the git code https://github.com/mbusb/multibootusb . I have read and tried to create PKGBUILD using https://projects.archlinux.org/abs.git/ … thon.proto . However, It does not seems to create any package at all. Here is the contenet of my PKGBUILD:-

# Contributor: Jonas Heinrich <onny@project-insanity.org>
# Maintainer: sundar_ima <feedback.multibootusb@gmail.com>

pkgname=multibootusb
pkgver=7.1.0
pkgrel=1
pkgdesc="Boot multiple live Linux distros from a usb flash drive"
arch=('any')
url="http://multibootusb.org"
license=('gpl3')
depends=('python-pyqt4' 'python2-psutil' 'mtools')
sha512sums=('81a3680b42d49107ff8a05e7bdb856d2c75f24173cc836920b83deba20e321acc09fa17605f88cce10a09f23db242fe50cdee3e3d04b55ed4047683a7b69555e')
#makepkgopt = strip
#makepkgopt = docs
#makepkgopt = libtool
#makepkgopt = emptydirs
#makepkgopt = zipman
#makepkgopt = purge
#makepkgopt = !upx
source=("http://downloads.sourceforge.net/project/$pkgname/${pkgver}/Source/$pkgname-${pkgver}.tar.gz")

package () {
    cd "$srcdir/$pkgname-$pkgver"
	python2.7 setup.py install --root="$pkgdir/" --optimize=1
}

# vim:set ts=4 sw=4 et:

When I tried to check PKGBUILD using namcap, it does not produce error at all. Any help to create successful PKGBUILD is appriciated.

Thanks in advance.

Last edited by sundar_ima (2014-04-28 00:08:35)

Spider.007 · 2014-04-27 13:06:54

So what exactly is the problem? After creating this file; run `makepkg` in the same directory and it produces multibootusb-7.1.0-1-any.pkg.tar.xz (it does here); which is your package; which you can install if you'd like

Last edited by Spider.007 (2014-04-27 13:07:06)

clfarron4 · 2014-04-27 13:08:58

Most PKGBUILDS I have seen have the first bracket for the checksums on the same line as the checksum used, so I see this:

sha512sums=('81a3680b42d49107ff8a05e7bdb856d2c75f24173cc836920b83deba20e321acc09fa17605f88cce10a09f23db242fe50cdee3e3d04b55ed4047683a7b69555e')

sundar_ima · 2014-04-27 13:24:03

@Spider.007

That is the problem. It does not create any package here? Are you able to install it successfully?

Trilby · 2014-04-27 13:32:06

The line wrapping issues (and one I had trying to copy and paste this code) come from the OP using quote tags rather than code tags. Sundar_ima, would you mind editing your first post to fix those?

This does also successfuly build what looks like a complete package here and it can be installed with a total of 108 files installed. I don't know how to use this, so I can't test actual end product functionality, but I assume that isn't an issue here: the PKGBUILD works as it should.

Sundar_ima, what output do you get when you run `makepkg` (or `makepkg -s`)? Do you have the base-devel group installed?

EDIT: the package does still get a *lot* of namcap warnings about improper dependency listing, and also (to me) a more significant issue of where this is installed: quite of bit lands in a new /usr/multiboot folder - is this intended? This does not seem like a good place. Namcap doesn't seem to mind this, but I think the standard licenses are generally capitalized (GPL3 rather than gpl3) but this may simply be convention rather than requirement.

Last edited by Trilby (2014-04-27 13:45:32)

sundar_ima · 2014-04-28 00:21:05

@ Trilby

I have modified the first post to use code. multibootusb is simmilar to unetbootin. However, many distros can be installed/ uninstalled. The famous linux version of YUMI by pendrivelinux.com is a fork of multibootusb. I hope you understand what my software does.

There seems to be a difference between "makepkg" and "makepkg -S". Package has been succesfully created using "makepkg". However, it does not when I used "makepkg -S". Here is the out put I got when I used "makepkg -S"

[sundar@arch arch]$ makepkg -S
==> Making package: multibootusb 7.1.0-1 (Mon Apr 28 05:41:38 IST 2014)
==> Retrieving sources...
  -> Downloading multibootusb-7.1.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100  662k  100  662k    0     0  73219      0  0:00:09  0:00:09 --:--:-- 56066
==> Validating source files with sha512sums...
    multibootusb-7.1.0.tar.gz ... Passed
==> Entering fakeroot environment...
==> Creating source package...
  -> Adding PKGBUILD...
  -> Compressing source package...
==> Leaving fakeroot environment.
==> Source package created: multibootusb (Mon Apr 28 05:41:48 IST 2014)
[sundar@arch arch]$ ls
multibootusb-7.1.0-1.src.tar.gz  multibootusb-7.1.0.tar.gz  PKGBUILD  src

But the wiki says that "makepkg -S" is used "To build the package and install needed dependencies automatically" .

Regarding namcap warning, I have kept additional data required by multibootusb under python's system prefix. I had to do this as different distro uses different path for system prefix. Any suggestion to remove this warning is appriciated. Also this warning by namcap:-

multibootusb W: Dependency included and not needed ('python-pyqt4')
multibootusb W: Dependency included and not needed ('python2-psutil')
multibootusb W: Dependency included and not needed ('mtools')

does not seems to be true. These pacakages are must to run multibootusb.

Last edited by sundar_ima (2014-04-28 00:27:28)

Trilby · 2014-04-28 00:28:12

Not quite. Flags are case sensitive: `makepkg -s` != `makepkg -S`.

The latter makes the "source tarball" which is what gets uploaded to the AUR website.

As for the warnings - they are 'just' warnings, so they aren't show stoppers. But personally I'd be most concerned with creating the new dir in /usr/, though this might just be me. If possible I'd suggest /usr/share/multiboot/ if these are data or config type files, or /usr/lib/multiboot/ if these are scripts or object files.

Last edited by Trilby (2014-04-28 00:30:34)

sundar_ima · 2014-04-28 00:36:32

@Trilby
Yeh. You are correct. `makepkg -s` != `makepkg -S`. :-))

Now the package build successfully. And for the namcap error, wiki says that

dependency-not-needed (warning) This dependency is not required by any file present in the program (as far as namcap could deduce). This does not work properly yet for scripts (like python or perl packages) though; there you will have to figure out the dependencies on your own

That means that the warning message is OK.

sundar_ima · 2014-04-28 00:39:38

Trilby wrote:

But personally I'd be most concerned with creating the new dir in /usr/, though this might just be me. If possible I'd suggest /usr/share/multiboot/ if these are data or config type files, or /usr/lib/multiboot/ if these are scripts or object files.

Ok. I will ammend my source code to move the data files to

/usr/share/multibootusb

Thanks for pointing out this issue.

Arch Linux

#1 2014-04-27 13:00:25

Unable to create PKGBUILD successfully

#2 2014-04-27 13:06:54

Re: Unable to create PKGBUILD successfully

#3 2014-04-27 13:08:58

Re: Unable to create PKGBUILD successfully

#4 2014-04-27 13:24:03

Re: Unable to create PKGBUILD successfully

#5 2014-04-27 13:32:06

Re: Unable to create PKGBUILD successfully

#6 2014-04-28 00:21:05

Re: Unable to create PKGBUILD successfully

#7 2014-04-28 00:28:12

Re: Unable to create PKGBUILD successfully

#8 2014-04-28 00:36:32

Re: Unable to create PKGBUILD successfully

#9 2014-04-28 00:39:38

Re: Unable to create PKGBUILD successfully

Board footer