packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

mhertz · 2011-03-02 18:40:15

Hmm, the new packer update prompts me for my root password allthough I have those prompts disabled in my /etc/sudoers file and I get no prompts when running sudo commands in the terminal...

Edit: The issue is also the same with the previous packer version, and it only occures when using sudo v1.8 from testing and not with v1.7.4.p6 from core. Downgrading sudo and running packer with '--ignore sudo' fixes this issue completelly! There's no problems mentioned about sudo v1.8 on arch-dev-public...

Again, I can run e.g. 'sudo pacman -Syu' and other sudo commands without being asked for my root password, and it's just packer who prompts me to enter it even though i have the following uncommented in /etc/sudoers: '%wheel ALL=(ALL) NOPASSWD: ALL' and is using a user account which is member of the wheel group...

Last edited by mhertz (2011-03-03 01:55:06)

sknd · 2011-03-02 22:38:57

what abouts showing the [INSTALLED] and maybe the number of votes on the package? are they gonna be impemented?

mhertz · 2011-03-03 13:45:03

Allan has posted a message on arch-dev-public about an issue with sudo 1.8 from [testing], so that must be the explenation to the issue about packer and sudo v1.8 from [testing] which I edited into my post from yesterday: http://mailman.archlinux.org/pipermail/ … 19602.html

Also yaourt seems to suffer from the exact same thing as posted in the testing repo subforum...

Last edited by mhertz (2011-03-04 17:42:58)

mhertz · 2011-03-04 18:34:23

With sudo-1.8-2 from [testing] then the issue about sudo -l <command> always returning 1 is fixed, but there remains an issue with the: 'sudo -v' in line 67:

elif sudo -v &>/dev/null && sudo -l "$@" &>/dev/null; then

In the old sudo then that would return a 0 return value, but it returns a non-zero return value in the new sudo.

So the fix is to change the 'sudo -v' to 'sudo -V' on line 67, which I also believe should have been done all along, as there's no documented -v option, but only a -V, but where the -v option just happened to also work with the old sudo, but not anymore(if using [testing])...

Last edited by mhertz (2011-03-07 12:11:39)

mhertz · 2011-03-05 22:37:58

I mailed bruenig about the sudo issue and a couple of minutes after I got a reply that it was fixed and to run packer -S packer to update!

Quick service indeed!

DasFox · 2011-03-07 00:32:52

mhertz wrote:

@DasFox
Hi there! I unfortunetly don't know anything about your issue, and we must wait untill bruenig returns, but I would like to ask you if you would kindly do me a favor and try to run 'packer -Syu --devel' on a fully updated system, and see if packer does update(reinstall) anything? Even if you don't have any devel packages installed from aur, then it should atleast update packer itself which is a devel package also...
Thanks in advance!
Edit: I've just got my notebook back from repair and i then runned 'packer -Syu --devel' on that and saw that the issue is the same there as on my stationary system, so it should be a packer issue then... (Doh! I could just have made a VM and tested in before that)
Edit2: Cool! bruenig has comed to the rescue again and made a commit that fixes the new AUR url scheme, so manually run 'packer -S packer' and everything is fine again! Thanks alot bruenig, you rock!

Ok I ran packer -S packer...

We'll see how this goes and THANKS bruenig!

By the way when installing a new pack out of AUR through packer, it's not making it into a tar and placing it in /var/cache/pacman/pkg/ ?

It just compiles and installs it and leaves us with no tar?

Also what about the packerbuild-0 and packertmp-0 in /tmp is this safe to delete once packer has been installed?

THANKS

Last edited by DasFox (2011-03-07 00:38:04)

mhertz · 2011-03-07 09:44:45

Yes, packer builds packages in /tmp and dosen't cache them in /var/cache/pacman/pkg. You can delete these dirs in /tmp fine, but they are both deleted by packer on next run + the /tmp dir is emptied anyways upon reboots...

@all

Btw, the sudo-1.8-3 just released to [testing], includes an upstream patch for fixing the sudo issue I reported earlier, but it's not in [core] yet...

Last edited by mhertz (2011-03-07 12:13:14)

oliver · 2011-03-07 15:31:29

DasFox wrote:

By the way when installing a new pack out of AUR through packer, it's not making it into a tar and placing it in /var/cache/pacman/pkg/ ?
It just compiles and installs it and leaves us with no tar?

I have PKGDEST defined in /etc/makepkg.conf and any packer built AUR packages are placed there after installation

$ grep ^PKGDEST /etc/makepkg.conf 
PKGDEST=/home/packages

Last edited by oliver (2011-03-07 16:10:58)

mhertz · 2011-03-08 08:32:24

I just wanted to clarify that my fix of changing -v to -V was wrong as I misunderstood what the code was trying to archive, and so I mailed bruenig about it and he reverted the commit, and I have "strike-throughed" my previous edits about this fix.

So, if using [tesing] then you have no problems, as sudo-1.8-3 includes an upstream patch that fixes the issue, but if using core, then you'll still have to live with the issue untill sudo-1.8-3 comes out of testing, i.e. sudo isn't used even if installed, and instead su is, which means having to input password upon each and every installed/upgraded package!

Sorry about that!

Procyon · 2011-03-08 12:42:59

Could you allow pkg.tar extension?

The references are in line 303, 305, 309, 311 as *.pkg.tar.*, and would work as well as with *.pkg.tar*

oliver · 2011-03-08 14:10:26

just got sudo 1.8.0-3 from core and all is good again for me :-)

archman-cro · 2011-03-16 00:54:33

Thank you for this amazing application! For both this one and 'downgrade'!

ngoonee · 2011-03-19 00:40:41

Where do I make feature requests?

falconindy · 2011-03-19 01:14:46

Procyon wrote:

Could you allow pkg.tar extension?
The references are in line 303, 305, 309, 311 as *.pkg.tar.*, and would work as well as with *.pkg.tar*

I'd recommend using an extglob here for precision: *.pkg.tar?(.*)

JerichoKru · 2011-03-20 20:46:11

I came across this earlier in my hunt for a DM that'll work properly (and that I like).

yaourt -Ss display manager

extra/gdm 2.32.0-5 (gnome-extra)
    Gnome Display Manager (a reimplementation of xdm)
extra/libxdmcp 1.1.0-1 [installed]
    X11 Display Manager Control Protocol library
extra/lxdm 0.3.0-1 (lxde)
    Lightweight Display Manager (part of LXDE)
extra/xorg-xdm 1.1.10-2
    X Display Manager
community/wdm 1.28-4
    An replacement X window display manager similar to, and based on XDM
multilib/lib32-libxdmcp 1.1.0-1 [installed]
    X11 Display Manager Control Protocol library (32-bit)
archlinuxfr/libfm 0.1.14-5 (lxde)
    the core of next generation file manager PCManFM - doesn't display loops
aur/cdm 0.5.3-1 (146)
    The Console Display Manager
aur/cdm-git 20110102-1 (27)
    The Console Display Manager
aur/debian-gdm-themes 0.6.1-1 (20)
    Themes for the GNOME Display Manager
aur/elsa-svn 52188-1 (11)
    Successor of the e17 display manager - Entrance
aur/gdm-old 2.20.11-1 (191)
    Gnome Display Manager (a reimplementation of xdm)
aur/lightdm 0.2.3-1 (20)
    A lightweight display manager
aur/lxdm-git 20101010-1 [installed: 20110320-1] (53)
    Lightweight Display Manager (part of LXDE)
aur/nodm 0.7-11 (0)
    X display manager for automatic logins
aur/orthos 0.2-1 (10)
    An X Display Manager with simplistic design and no need for qt/gtk/other 
    libraries

VS

packer -Ss display manager

extra/gdm 2.32.0-5 (gnome-extra)
    Gnome Display Manager (a reimplementation of xdm)
extra/libxdmcp 1.1.0-1 [installed]
    X11 Display Manager Control Protocol library
extra/lxdm 0.3.0-1 (lxde)
    Lightweight Display Manager (part of LXDE)
extra/xorg-xdm 1.1.10-2
    X Display Manager
community/wdm 1.28-4
    An replacement X window display manager similar to, and based on XDM
multilib/lib32-libxdmcp 1.1.0-1 [installed]
    X11 Display Manager Control Protocol library (32-bit)
archlinuxfr/libfm 0.1.14-5 (lxde)
    the core of next generation file manager PCManFM - doesn't display loops

I have no AUR results with packer. Does it support more that one search term?

mhertz · 2011-03-20 22:17:41

Use double-quotes i.e.:

packer -Ss "display manager"

, and the aur results will also show...

JerichoKru · 2011-03-21 19:53:30

mhertz wrote:

Use double-quotes i.e.:
packer -Ss "display manager"
, and the aur results will also show...

Ah. That works, thanks.

outerdark · 2011-03-23 16:38:40

Is there any reason why packer is adding all versions of package xyz from $PKGDEST into the pacman install queue?

pacman -U $pkgname*.pkg.tar.*

With the newest version of pacman, packer also aborts with the message "duplicate target of xyz".

Patch: http://pastie.org/1704582

falconindy · 2011-03-23 17:42:11

outerdark wrote:

Patch: http://pastie.org/1704582

Perhaps you means something more like this? Please don't use ls programatically. Also, is this against 3.5.0? or 3.5.1?

outerdark · 2011-03-23 17:50:18

That's what i meant

It's against pacman 3.5.0, just updated to 3.5.1 but doesn't make any difference to the "duplicate target" error. To clarify ... the error only shows up if the targets are globbed into the pacman installation queue.

splippity · 2011-03-24 02:14:24

I just started using packer on this current install where bauerbill and pacman work just fine but currently I have a problem where I do packer -Syu and it prompts me for a password 2X in a row before proceeding. this happens every time.

anyone else? any ideas? thanks

ngoonee · 2011-03-24 02:35:47

Is it possible to tell packer to use another build directory than in /tmp?

jolinfire · 2011-03-24 06:07:04

At least - and until another aur wrapper is updated - packer will do the job for me. And as Pacman 3.5.1 is in core...

outerdark · 2011-03-24 10:06:10

outerdark wrote:

Is there any reason why packer is adding all versions of package xyz from $PKGDEST into the pacman install queue?
pacman -U $pkgname*.pkg.tar.*
With the newest version of pacman, packer also aborts with the message "duplicate target of xyz".
Patch: http://pastie.org/1704582

My old patch could break the installation target queue in cases if someone installs fbsplash and have another packages fbsplash-extras in his $PKGDEST.
Original packer globbes both into arguments to install with pacman.

The new Patch just adds more explicite globbing with version and release nr.
http://pastie.org/1707575

Last edited by outerdark (2011-03-24 10:06:31)

hagabaka · 2011-03-25 01:24:46

Is it possible to configure where the build files are stored? I use cower with "-t ~/aur" so I have a directory for each AUR package like ~/aur/packagename/, containing PKGBUILD, src, pkg etc. However packer seems to use /tmp/packerbuild-1000/packagename/packagename instead.

Also I haven't been able to test whether packer will checkout/clone again when upgrading a VCS package or it can just update/pull based on the previously built revision. Yaourt apparently can only do the first. These problems are what made me want to switch from yaourt.

Last edited by hagabaka (2011-03-25 01:25:39)

Arch Linux

#476 2011-03-02 18:40:15

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#477 2011-03-02 22:38:57

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#478 2011-03-03 13:45:03

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#479 2011-03-04 18:34:23

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#480 2011-03-05 22:37:58

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#481 2011-03-07 00:32:52

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#482 2011-03-07 09:44:45

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#483 2011-03-07 15:31:29

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#484 2011-03-08 08:32:24

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#485 2011-03-08 12:42:59

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#486 2011-03-08 14:10:26

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#487 2011-03-16 00:54:33

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#488 2011-03-19 00:40:41

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#489 2011-03-19 01:14:46

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#490 2011-03-20 20:46:11

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#491 2011-03-20 22:17:41

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#492 2011-03-21 19:53:30

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#493 2011-03-23 16:38:40

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#494 2011-03-23 17:42:11

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#495 2011-03-23 17:50:18

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#496 2011-03-24 02:14:24

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#497 2011-03-24 02:35:47

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#498 2011-03-24 06:07:04

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#499 2011-03-24 10:06:10

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

#500 2011-03-25 01:24:46

Re: packer - New bash aur+pacman wrapper (replaces poorly written yaourt)

Board footer