Clyde - A better libalpm/makepkg wrapper

juster · 2011-02-19 22:27:31

I have released 0.03.13 with two more of Ramses's patches. Here is the Changelog for 0.03.13:

* Version 0.03.13 [2011-02-19 Sat]

** AUR Sysupgrade Is ... Upgraded

Thanks to RamsesDeNorre IgnorePkg will work properly when performing
a sysupgrade on AUR packages.

When you run sysupgrade for AUR packages it should also look a
little nicer. Now you can see what packages are being checked.

** Multiple Built Packages :BUG:

Multiple package files in the same build directory for an AUR package
would cause a bug. Fixed thanks to RamsesDeNorre's patch.

juster · 2011-02-20 05:52:51

I was in a hurry and I forgot to respond to your posts.

Berseker:

Berseker wrote:

juster have you taken a look also at this behaviour of clyde?
https://bbs.archlinux.org/viewtopic.php … 33#p864333
maybe you could fix that in one of next releases!

I will add that to my todo list. Since a custom builddir is already working only automatic cleanup is needed. Let me know if the current --builddir option/configure entry will not satisfy your requirements. Automatic cleanup should be fairly easy to do because we just need something like:

if config.autoclean then rmrf( builddir ) end

... in the appropriate location. I think I might add a --clean option and an AutoClean configure file entry. This might have to wait until next weekend though.

FrozenFox:
I forgot to mention that your problem should be fixed now but I see you have already noticed it. Thanks for reporting the bug!

juster · 2011-02-20 22:52:16

Another patch from RamsesDeNorre! Version is now 0.03.14.

* Version 0.03.14 [2011-02-20 Sun]

** Display versions when searching

Thanks to a patch from RamsesDeNorre, now when you search for a package
and it is already installed a version is printed if the search result
does not match your installed version.

** Color scheme change

I (juster) changed the color scheme for search results. I find it to
be less obnoxious. Let me know if you hate it. The colors for package
info was changed slightly to match the search results colors.

** PKGDEST / custom package cache problems :BUG:

A user could have a custom built package cache by exporting the
PKGDEST environment variable or setting it in /etc/makepkg.conf. Clyde
was acting buggy when it went searching for where the binary package file
ended up.

Reported by smferris. Thanks!

anish · 2011-02-23 21:03:34

seems to not work with the pycp/python-progreebar package

anish@cellardoor ~ $ sudo clyde -S pycp
:: pycp package not found, searching for group...
:: pycp group not found, searching AUR...

==> Installing the following packages from AUR
Targets (2): pycp python-progressbar

==> Proceed with installation? [Y/n] y
==> Downloading python-progressbar
==> Customizing python-progressbar...
==> WARNING: Packages from the AUR are potentially dangerous!
Edit the PKGBUILD? (recommended) [Y/n] n
error: /usr/share/lua/5.1/clydelib/aur.lua:246: attempt to concatenate upvalue 'mkpkgopts' (a nil value)

juster · 2011-02-24 00:59:22

anish: that bug has since been fixed. Be sure to re-install the clyde-git package to get the latest version of clyde.

forkboy · 2011-02-24 21:13:52

I can't get firebrand or thunderbrand packages from the AUR to install with clyde, it will find the packages when searching but not when trying to install.

[root@myhost john]# clyde -Ss firebrand
aur/firebrand 3.6-3 (181)
    A script to brand Firefox without recompiling.

[root@myhost john]# clyde -S firebrand
:: firebrand package not found, searching for group...
:: firebrand group not found, searching AUR...
error: 'firebrand': not found in sync db

Same happens with thunderbrand.

Awebb · 2011-02-24 21:36:24

forkboy wrote:

I can't get firebrand or thunderbrand packages from the AUR to install with clyde, it will find the packages when searching but not when trying to install.
Same happens with thunderbrand.

Both work for me. It's not a Clyde problem, it's a problem with your Clyde :-D

anonymous_user · 2011-02-24 22:48:30

I tried installing firebrand and had a different problem. For some reason it didn't want to install Firefox first:

:: firebrand package not found, searching for group...
:: firebrand group not found, searching AUR...

==> Installing the following packages from AUR
Targets (1): firebrand  

==> Proceed with installation? [Y/n] y
==> Downloading firebrand
==> Customizing firebrand...
==> WARNING: Packages from the AUR are potentially dangerous!
Edit the PKGBUILD? (recommended) [Y/n] n
==> Making package: firebrand 3.6-3 (Thu Feb 24 14:47:31 PST 2011)
==> Checking Runtime Dependencies...
==> Missing Dependencies:
  -> firefox>=3.6
==> Checking Buildtime Dependencies...
==> ERROR: Could not resolve all dependencies.
error: /usr/share/lua/5.1/clydelib/aur.lua:251: Build failed

Last edited by anonymous_user (2011-02-24 22:51:56)

rwd · 2011-02-26 20:52:17

Sorry if this has been mentioned before, but I noticed that a 'clyde -Sd <packagename>' does not skip dependency checks like I would expect, at least I noticed with nvidia-beta on aur. Also I tried searching if this was reported before but the url in the aur description of clyde, http://clyde.archuser.com/ does not work.

Ramses de Norre · 2011-02-26 23:48:39

The firebrand thingy has been fixed upstream, rebuilding clyde should fix it.

@rwd: best place to file bug reports is on github.

blasse · 2011-03-04 10:21:29

Another problem:

[sigma@blasse ~]$ clyde
lua: error loading module 'clydelib.colorize' from file '/usr/share/lua/5.1/clydelib/colorize.lua':
    /usr/share/lua/5.1/clydelib/colorize.lua:1: unexpected symbol
stack traceback:
    [C]: ?
    [C]: in function 'require'
    /usr/bin/clyde:4: in main chunk
    [C]: ?

Any solution?

juster · 2011-03-04 15:34:40

blasse wrote:

Another problem:

[sigma@blasse ~]$ clyde
lua: error loading module 'clydelib.colorize' from file '/usr/share/lua/5.1/clydelib/colorize.lua':
    /usr/share/lua/5.1/clydelib/colorize.lua:1: unexpected symbol
stack traceback:
    [C]: ?
    [C]: in function 'require'
    /usr/bin/clyde:4: in main chunk
    [C]: ?

Any solution?

That's very strange. What is actually in your colorize.lua file? You can use the head command to look:

head /usr/share/lua/5.1/clydelib/colorize.lua

blasse · 2011-03-08 18:10:38

juster wrote:

That's very strange. What is actually in your colorize.lua file? You can use the head command to look:
head /usr/share/lua/5.1/clydelib/colorize.lua

Command gives nothing - it looks like corrupted file... Tried recompiling clyde few times, but with no effect...

lagagnon · 2011-03-23 23:06:11

Any word as to when we might expect clyde to be compatible with pacman3.5 ? When it's ready ? ;-)

McFlow · 2011-03-26 12:05:15

After update to pacman 3.5 I receive this error:

lua: error loading module 'lualpm' from file '/usr/lib/lua/5.1/lualpm.so':
    /usr/lib/lua/5.1/lualpm.so: undefined symbol: alpm_sync_dbtarget
stack traceback:
    [C]: ?
    [C]: in function 'require'
    /usr/share/lua/5.1/clydelib/util.lua:2: in main chunk
    [C]: in function 'require'
    /usr/bin/clyde:5: in main chunk
    [C]: ?

Btw, I use clyde since a very long time and it's awesome.

Last edited by McFlow (2011-03-26 12:06:39)

Ramses de Norre · 2011-03-26 12:47:37

McFlow wrote:

After update to pacman 3.5 I receive this error:

lua: error loading module 'lualpm' from file '/usr/lib/lua/5.1/lualpm.so':
    /usr/lib/lua/5.1/lualpm.so: undefined symbol: alpm_sync_dbtarget
stack traceback:
    [C]: ?
    [C]: in function 'require'
    /usr/share/lua/5.1/clydelib/util.lua:2: in main chunk
    [C]: in function 'require'
    /usr/bin/clyde:5: in main chunk
    [C]: ?

Btw, I use clyde since a very long time and it's awesome.

Did you even read the last posts in this thread? Pacman 3.5 introduced an API change in libalpm so lualpm (and possibly clyde too?) needs to be ported to the new version.
In short: wait until clyde gets updated.

Last edited by Ramses de Norre (2011-03-26 12:47:58)

flan_suse · 2011-03-27 16:21:13

Ramses de Norre wrote:

Did you even read the last posts in this thread? Pacman 3.5 introduced an API change in libalpm so lualpm (and possibly clyde too?) needs to be ported to the new version.
In short: wait until clyde gets updated.

I'm a little late to the party, but I'll chime in. It appears that if you simply rebuild clyde-git after upgrading pacman, you should be good to go.

Ramses de Norre · 2011-03-27 16:21:57

flan_suse wrote:

Ramses de Norre wrote:
Did you even read the last posts in this thread? Pacman 3.5 introduced an API change in libalpm so lualpm (and possibly clyde too?) needs to be ported to the new version.
In short: wait until clyde gets updated.
I'm a little late to the party, but I'll chime in. It appears that if you simply rebuild clyde-git after upgrading pacman, you should be good to go.

It's been ported now, indeed

flan_suse · 2011-03-27 16:25:21

I had been using bauerbill in the past, but as some may know, it has been discontinued. Don't get me wrong, clyde is super fast. There's two things that I took for granted with bauerbill that I am unable to figure out with clyde.

1) Is there any way to pass makepkg arguments? With bauerbill, I added "-c" in its .conf file, and this would keep the build dir clean after a successful build.

2) Can clyde create its build dir automatically? Some people have certain mounts in ramdisk (e.g, /tmp), which is cleared on reboot. If I set the build dir to /tmp/clyde, it will tell me that the directory "does not exist". Maybe clyde can do "mkdir -p $buildir" or something when it is executed? Bauerbill would automatically create such a directory (owner is the user) on its own.

Last edited by flan_suse (2011-03-27 16:25:57)

Ramses de Norre · 2011-03-27 16:27:40

flan_suse wrote:

I had been using bauerbill in the past, but as some may know, it has been discontinued. Don't get me wrong, clyde is super fast. There's two things that I took for granted with bauerbill that I am unable to figure out with clyde.
1) Is there any way to pass makepkg arguments? With bauerbill, I added "-c" in its .conf file, and this would keep the build dir clean after a successful build.
2) Can clyde create its build dir automatically? Some people have certain mounts in ramdisk (e.g, /tmp), which is cleared on reboot. If I set the build dir to /tmp/clyde, it will tell me that the directory "does not exist". Maybe clyde can do "mkdir -p $buildir" or something when it is executed? Bauerbill would automatically create such a directory (owner is the user) on its own.

1) dunno, have you checked the man page?

2) clyde builds in /tmp by default, I have /tmp in ram and clyde makes a dir /tmp/clyde-<username> automatically. Is that good enough for you?

Last edited by Ramses de Norre (2011-03-27 16:27:55)

flan_suse · 2011-03-27 16:38:44

Ramses de Norre wrote:

1) dunno, have you checked the man page?
2) clyde builds in /tmp by default, I have /tmp in ram and clyde makes a dir /tmp/clyde-<username> automatically. Is that good enough for you?

1) There was no mention of passing makepkg arguments in either the Wiki, OP, or man page.

2) I saw, under /etc/clyde.conf, that the AUR builddir was set under /var/cache. When I changed it to /tmp/clyde, I receive this error:

error: The specified builddir (/tmp/clyde) does not exist!

Last edited by flan_suse (2011-03-27 16:46:01)

flan_suse · 2011-03-27 16:45:25

Some demonic force is playing tricks on me. I just commented out the builddir line under /etc/clyde.conf, and it works as you described. I could have sworn it was set to /var/cache inititially. Well, that's one thing out of the way. Thank you!

Last edited by flan_suse (2011-03-27 16:52:56)

juster · 2011-03-27 21:20:33

For some reason I put /var/cache/clyde in the comments for the config file. I'm not sure why. I cleaned up the config file generation code a little bit and fixed my typo.

The build dir logic is a little weird I guess. If you specify a builddir with the BuildDir config file entry or with the --builddir flag then that literal directory is used. Pretty simple. However, if you don't specify anything and a default must be used then the default is /tmp/clyde-(BuildUser).

If you don't specify a builduser in the config file then the BuildUser is determined at each runtime. The BuildUser is either read from the SUDO_USER environment variable or, finally, it is root.

edit: the two functions after line 56 in aur.lua sum it up much more succinctly

Last edited by juster (2011-03-27 21:23:19)

flan_suse · 2011-03-27 21:28:36

juster wrote:

The build dir logic is a little weird I guess. If you specify a builddir with the BuildDir config file entry or with the --builddir flag then that literal directory is used. Pretty simple. However, if you don't specify anything and a default must be used then the default is /tmp/clyde-(BuildUser).
If you don't specify a builduser in the config file then the BuildUser is determined at each runtime. The BuildUser is either read from the SUDO_USER environment variable or, finally, it is root.
edit: the two functions after line 56 in aur.lua sum it up much more succinctly

You summed it up quite well! Thanks for the clarification (and the peace of mind of knowing I'm not the victim of a demonic force!) I have the BuildUser set manually, and since I re-commented out the BuildDir, it works as mentioned above: /tmp/clyde-username

This works, and it'll be fine with /tmp mounted from a ramdisk, even after reboots.

juster wrote:

For some reason I put /var/cache/clyde in the comments for the config file. I'm not sure why. I cleaned up the config file generation code a little bit and fixed my typo.

If I rebuild clyde-git, it won't really matter since I already have a clyde.conf in place? This will only affect new installations of clyde, right?

juster · 2011-03-27 22:39:38

flan_suse wrote:

If I rebuild clyde-git, it won't really matter since I already have a clyde.conf in place? This will only affect new installations of clyde, right?

Don't worry the changes I made shouldn't affect anything, really. The last commit I made only changes the default configure file "template". It bothers me when lines are longer than 80 characters... I also reworded some comments, removed extra whitespace, refactored the code to be easier to read, and changed the logic to move the pacman.conf header to the top of clyde.conf in the process of copying pacman.conf into clyde.conf. But these are all cosmetic improvements (I hope).

I was going to change the behavior like you said earlier, to create the BuildDir directory automatically. This seemed simple but in the process I found some more bugs and more things to do... Anyways... What you said about having the [explicitly set] BuildDir inside /tmp made me think that maybe automatically mkdir-ing the BuildDir might be a good idea after all.

edit: fixed spelling errors

Last edited by juster (2011-03-27 22:41:52)

Arch Linux

#576 2011-02-19 22:27:31

Re: Clyde - A better libalpm/makepkg wrapper

#577 2011-02-20 05:52:51

Re: Clyde - A better libalpm/makepkg wrapper

#578 2011-02-20 22:52:16

Re: Clyde - A better libalpm/makepkg wrapper

#579 2011-02-23 21:03:34

Re: Clyde - A better libalpm/makepkg wrapper

#580 2011-02-24 00:59:22

Re: Clyde - A better libalpm/makepkg wrapper

#581 2011-02-24 21:13:52

Re: Clyde - A better libalpm/makepkg wrapper

#582 2011-02-24 21:36:24

Re: Clyde - A better libalpm/makepkg wrapper

#583 2011-02-24 22:48:30

Re: Clyde - A better libalpm/makepkg wrapper

#584 2011-02-26 20:52:17

Re: Clyde - A better libalpm/makepkg wrapper

#585 2011-02-26 23:48:39

Re: Clyde - A better libalpm/makepkg wrapper

#586 2011-03-04 10:21:29

Re: Clyde - A better libalpm/makepkg wrapper

#587 2011-03-04 15:34:40

Re: Clyde - A better libalpm/makepkg wrapper

#588 2011-03-08 18:10:38

Re: Clyde - A better libalpm/makepkg wrapper

#589 2011-03-23 23:06:11

Re: Clyde - A better libalpm/makepkg wrapper

#590 2011-03-26 12:05:15

Re: Clyde - A better libalpm/makepkg wrapper

#591 2011-03-26 12:47:37

Re: Clyde - A better libalpm/makepkg wrapper

#592 2011-03-27 16:21:13

Re: Clyde - A better libalpm/makepkg wrapper

#593 2011-03-27 16:21:57

Re: Clyde - A better libalpm/makepkg wrapper

#594 2011-03-27 16:25:21

Re: Clyde - A better libalpm/makepkg wrapper

#595 2011-03-27 16:27:40

Re: Clyde - A better libalpm/makepkg wrapper

#596 2011-03-27 16:38:44

Re: Clyde - A better libalpm/makepkg wrapper

#597 2011-03-27 16:45:25

Re: Clyde - A better libalpm/makepkg wrapper

#598 2011-03-27 21:20:33

Re: Clyde - A better libalpm/makepkg wrapper

#599 2011-03-27 21:28:36

Re: Clyde - A better libalpm/makepkg wrapper

#600 2011-03-27 22:39:38

Re: Clyde - A better libalpm/makepkg wrapper

Board footer