You are not logged in.
Hey everybody. SURPRISE RELEASE! 0.94.1 is out!
I managed to introduce a bug right before the last release that either no one has noticed or no one has reported. I find it particularly egregious and it has to do with some of the caching changes we made. The bug would store data in Paktahn's package cache after a successful install that paktahn couldn't read back in later. Not particularly scary but it did require you to quit and relaunch paktahn to finish certain installs. Terribly sorry. I'll give more details if anyone is interested.
Anyway, the fix is very simple and the bug was fairly annoying so I wanted to break with our usual habits and make a 0.94.1 point release (hopefully) before anyone got bitten. There's a 64-bit binary up on my website and there should be a 32-bit binary in a day or so.
Cheers.
Offline
I'm on paktahn-0.9.4.1-1-x86_64.pkg.tar.xz
Get this error:
[youri@nemesis ~]$ pak
==> Attempt to call an undefined alien function.
config.lisp like mentioned before was ignored. Not sure what to do!
Offline
youri: Thanks for the bug report. I'll do my best to get this taken care of by 20/03/2011 5pm EST.
Offline
Can you post the output of grep "alpm_db_register_local" /usr/include/alpm.h? If you install paktahn-0.9.4-1-x86_64.pkg.tar.xz from http://redlinernotes.com/docs/ and then upgrade via pak -S paktahn do you still have the problem?
Offline
It's also worth noting that if you're looking for an immediate fix you can just install one of the old paktahn binaries from http://redlinernotes.com/docs/ with pacman -U of course. Please give some info so I can debug though!
Offline
AHA! You folks are running the pacman 3.5 stuff from testing and the libalpm interface has changed. I'm looking into a fix right now. I'll have something by midnight.
Offline
Sorry, redline. I was away! You're right, I just checked and I'm running pacman from testing. Sorry that I didn't mention it, I didn't think about that!!! Thanks!!
Offline
0.94.3 is out! This is a minor bugfix release for users of pacman 3.5 from testing. I've tested it locally with pacman 3.4 which I'm on and it works fine but if you have any problems (errors from load-foreign-library or undefined alien functions) please let me know!
64 bit binary is here: http://redlinernotes.com/docs/paktahn-0 … pkg.tar.xz
youri: Sorry for the wait. Please try paktahn 0.94.3 which should fix paktahn for users of pacman/libalpm from testing. Let me know if there are any further problems.
Offline
is there a way to get features going to integrate it with yapan?
Offline
I am experiencing this with the latest paktahn:
[youri@nemesis ~]$ pak
debugger invoked on a SIMPLE-ERROR in thread #<THREAD "initial thread" RUNNING
{1004458BD1}>:
Error opening shared object "libalpm.so.5":
libalpm.so.5: cannot open shared object file: No such file or directory.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Skip this shared object and continue.
1: [RETRY ] Retry loading this shared object.
2: [CHANGE-PATHNAME] Specify a different pathname to load the shared object from.
(SB-SYS:DLOPEN-OR-LOSE
#S(SB-ALIEN::SHARED-OBJECT
:PATHNAME #P"libalpm.so.5"
:NAMESTRING "libalpm.so.5"
:HANDLE NIL
:DONT-SAVE NIL))
0]
Kind of weird I have libalpm.so.6 not 5! I'm going to debug this.
Offline
youri: I've got a VM that reproduces this issue but I'm still pretty confused by it. Conditionalizing on the user's version of libalpm is proving a bit more complicated than I expected. I'm a little slammed by school today or tomorrow but hpoefully I'll have a correct fix posted by Thursday or Friday. Sorry for all the trouble. The joys of running testing, eh?
Offline
I've found the problem and written a patch that seems to work. I'm going to do a little testing and should have a fresh, working paktahn version uploaded in the next 2-4 hours. Sorry for the delay everyone.
Offline
The patch works but local caching is slightly busted which prevents AUR upgrades. Shouldn't be much longer now.
Offline
0.94.6 is out! Sorry for the long wait. I found a regression in libalpm which has since been fixed by falconindy and should be in the next version but paktahn has a workaround for the time being.
I've tested what I can and there may still be bugs to ferret out but users of pacman 3.5 and earlier should all be fine on this release. If you notice anything wildly off, let me know what version of pacman/libalpm you're running.
Our next release, 0.95.0 will still mostly be about getting a solid test suite put together so that turnaround time on releases like this one is better and to minimize regressions going forward. I hope to have it out by the end of April but I'm also graduating and getting my first job so it could slip into May. Please be patient with me.
Offline
After installing I get this message:
* For users with light background terminals:
consult the documentation for setting the appropriate color scheme.
I use a white terminal. Better check this out.
So I did some pretty extensive looking around in all the places I could think of, and I couldn't find any documentation except the usage details.
Am I missing something obvious here?
EDIT:
Sorry, I figured it out. I needed to create a config.lisp file in my .paktahn folder and put in the lines dictated by the README that comes with the source. That information should probably be in a man file...
Last edited by bdjnk (2011-03-24 22:03:03)
Offline
bdjnk: Whoops. I'll add that to the TODO for 0.9.5. There is documentation in the README but I think the only place you'd really find that is github.
Add the following to ~/.paktahn/config.lisp:
(in-package :pak)
(setf *color-scheme* *color-scheme-lightbg*)
Offline
Beat me by 30 seconds. Thanks for this wonderful alternative to yaourt, and for exceedingly speedy updates and responses.
Offline
Things have been quiet here for a while and I'd like to apologize for that. I've graduated college and gotten my first programming job. I won't have time to hack on Paktahn until mid to late June except for serious bugs.
At that time, I'll spend a weekend or two hacking together 0.95 (and hopefully bringing a friend onboard as a new contributor). As always, thanks for your support and keep the bug reports, feature requests and love letters coming.
Offline
There's going to be a Paktahn hackathon tomorrow afternoon from about 11am EST to 1pm, a short break and then more hacking from 2:30-5 or so. If you have any interest in joining in (or issues to discuss), I'll be in #paktahn on freenode.
Offline
So a month has passed. My friend Trevis, who goes by trev311, has become a contributor on the project and will be helping me keep up with bugfixes now that I'm employed and a bit more distracted than I was before. We've made some progress already and I'm looking forward to making a bugfix release with a tentative target of July 16th. If there are any particularly evil bugs getting in your way, let us know ASAP so we can have a look at them before then. Cheers!
Offline
Dear ladies and gents, we are working now to get a paktahn release out to you. It's a beautiful Sunday here in Atlanta, GA and while it's been a while since the last release and I discussed a solid test suite that hasn't yet come to pass. On the other hand there are some new features, several bugfixes and a new contributor on the team. Practically all the work of the last month on Paktahn has come from Trevis and he'll be making the release announcement very soon...
Things are picking back up and hopefully Paktahn 0.9.6 will emerge with a solid test suite in the very near future.
Offline
Hy everyone, 0.9.5 is out! My name is Trevis. I'm a Math and CS student. I've been enjoying working on paktahn and look forward to helping push us closer to 1.0. In this release we've added: support for makepkg alternatives (i.e. unipkg), support for -Syu (previously only -Syu --aur was supported), and various bugfixes. An x86-64 binary can be found at http://redlinernotes.com/docs/paktahn-0 … pkg.tar.xz
Offline
Hi there. First of all, thank you for your work.
It seems that paktahn doesn't honour PKGBUILD's 'provides' field during dependency resolution. E.g. when I try to install the youtube-viewer aur package, paktahn tells me that it depends on mplayer, which conflicts with the mplayer-vdpau-svn package I have installed from aur, which has 'provides=("mplayer=${pkgver}-${pkgrel}")' in its PKGBUILD.
Running makepkg and installing with 'pacman -U' works as expected.
Sorry for not posting this before. I've seen your post just now.
Last edited by donbex (2011-07-04 20:49:30)
Offline
Hi, my name is Joshua and I'm willing to contribute to the project! This is my day-to-day tool and I really love it (especially for the AUR repo facilities (and thus one key part of my interest in ArchLinux)), but it lacks of stuff indicated in the TODO file that I really like it to have. In order to solve this, I would like to contribute to the code as I have strong fundaments of programming but I'm quite new to functional prog. I have little experience in Scheme/Racket since my Programming Languages course and I've been struggling with CL syntax reading the source code.
My question is: where can I go in order to start coding around in CL given my background? I know Paul Graham essays and heard about his books but where would you recommend me to go first?
And finally, congrats for this project guys, I really love it!
Offline
syb: Outstanding! I'm delighted you'd like to contribute. Common Lisp is pretty different from Racket+Scheme. It also doesn't care very much about whether or not you're functional which you'll begin to notice reading the Paktahn code. The general source most people recommend to get familiar with Common Lisp is Practical Common Lisp and I would echo that recommendation. It's readable, demonstrates good style and is both up to date and freely available online. See http://gigamonkeys.com/book/ Peter Seibel is kind of awesome.
If you'd like any personal mentoring I also try to hang out in #paktahn on Freenode a lot these days and would be happy to give you Common Lisp pointers and help acquaint you with confusing parts of the code. I'll likely contact you further after sleeping a few. Cheers, Joshua!
Offline