You are not logged in.

#1 2010-07-26 13:13:27

remu
Member
From: Florida
Registered: 2010-03-04
Posts: 5
Website

makepkg not creating ANY packages

I am able to use makepkg from either a manually downloaded PKGBUILD or via packer, and it works fine, except for creating the actual package. Instead what happens is that makepkg usually creates "pkg" and a "src" directories. I am then able to issue makepkg -R which creates the package just fine.

Does anyone have any ideas as to what might be the issue?

This has not always happened to me, I used to be able to build packages just fine. Just recently it happens with every PKGBUILD. I have also deleted /etc/makepkg.conf, done a pacman -Scc and re-installed pacman which created the /etc/makepkg.conf again, but the issue persists.

Please let me know if I need to attach more information.

Thanks.


Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning. - Rick Cook

Offline

#2 2010-07-26 13:21:13

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: makepkg not creating ANY packages

http://projects.archlinux.org/pacman.gi … ?id=v3.4.0

- makepkg:
    - repackaging without a package() function is deprecated

Last edited by wonder (2010-07-26 13:22:34)


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2010-07-26 13:39:32

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,430
Website

Re: makepkg not creating ANY packages

Can you post some output?

Offline

#4 2010-07-26 16:24:33

remu
Member
From: Florida
Registered: 2010-03-04
Posts: 5
Website

Re: makepkg not creating ANY packages

I tried to install pidgin-libnotify-notify-osd.

When I ran makepkg in the directory with the PKGBUILD I got:

make[2]: Leaving directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14/src'
make[1]: Leaving directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14/src'
make[1]: Entering directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14'
make[2]: Entering directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14'
make[1]: Leaving directory `/home/n00657918/tmp/src/pidgin-libnotify-0.14'
==> Tidying install...
  -> Purging other files...

When I ran packer -S pidgin-libnotify-notify-osd I got:

make[2]: Leaving directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14/src'
make[1]: Leaving directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14/src'
make[1]: Entering directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14'
make[2]: Entering directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14'
make[1]: Leaving directory `/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14'
The build failed.

When I ran ls in both my working directory (where the PKGBUILD was located) and in the packer /tmp directory, I received the following list of files:

pidgin-libnotify-0.14.tar.gz
pidgin-notify-osd.patch
pkg
PKGBUILD
src

When I ran makepkg -R in either of the directories mentioned above I got:

==> Making package: pidgin-libnotify-notify-osd 0.14-3 (Mon Jul 26 12:22:38 EDT 2010)
==> Entering fakeroot environment...
==> WARNING: Repackaging without the use of a package() function is deprecated.
    File permissions may not be preserved.
==> WARNING: Package contains reference to $srcdir
==> Creating package...
  -> Generating .PKGINFO file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: pidgin-libnotify-notify-osd 0.14-3 (Mon Jul 26 12:22:38 EDT 2010)

Which then creates the appropriate package which can then be installed using pacman -U.


Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning. - Rick Cook

Offline

#5 2010-07-27 00:19:44

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: makepkg not creating ANY packages

I think

/tmp/packerbuild-1000/pidgin-libnotify-notify-osd/pidgin-libnotify-notify-osd/src/pidgin-libnotify-0.14

with two times pidgin-libnotify-notify-osd in the path is wrong and unattended. Seems a packer issue.

Offline

#6 2010-07-27 00:26:32

remu
Member
From: Florida
Registered: 2010-03-04
Posts: 5
Website

Re: makepkg not creating ANY packages

Even if the path should not have it twice, this method fails for every PKGBUILD, not just this one. It fails for packages that I can do fine using the makepkg;makepkg -R;pacman -U method.


Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning. - Rick Cook

Offline

#7 2010-07-27 19:13:43

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: makepkg not creating ANY packages

That makes me think more and more that it is a packer issue.

Offline

#8 2010-08-02 12:25:49

remu
Member
From: Florida
Registered: 2010-03-04
Posts: 5
Website

Re: makepkg not creating ANY packages

I don't see how this would be a packer issue? Since running makepkg on its own doesn't result in a package being created anymore. It used to work fine.

Or are you saying that makepkg's behaviour has been changed recently, and that it no longer creates packages by default with simply using "makepkg" in the same directory as the PKGBUILD?


Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning. - Rick Cook

Offline

#9 2010-08-04 06:33:54

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: makepkg not creating ANY packages

remu wrote:

Even if the path should not have it twice, this method fails for every PKGBUILD, not just this one. It fails for packages that I can do fine using the makepkg;makepkg -R;pacman -U method.

Am I getting you wrong? I understood that normal makepkg works fine, and using packer does not.

Offline

#10 2010-08-04 06:59:53

sand_man
Member
From: Australia
Registered: 2008-06-10
Posts: 2,164

Re: makepkg not creating ANY packages

Stefan Husmann wrote:
remu wrote:

Even if the path should not have it twice, this method fails for every PKGBUILD, not just this one. It fails for packages that I can do fine using the makepkg;makepkg -R;pacman -U method.

Am I getting you wrong? I understood that normal makepkg works fine, and using packer does not.

That's the way I interpreted the output.


neutral

Offline

#11 2010-08-04 10:34:04

jac
Member
From: /home/jac
Registered: 2009-05-19
Posts: 431
Website

Re: makepkg not creating ANY packages

I'm fairly certain the problem is that regular makepkg (and thus packer too) stop before creating the actual package. Then remu has to run "makepkg -R" to generate it in the first place.

Maybe the entire makepkg output would be more useful than just the last bit?

Offline

Board footer

Powered by FluxBB