This Time Self-Hosted
dark mode light mode Search

The autoconf debacle

Okay seems like lately every time I try to do something I enjoy something ends up with more urgency, requiring my time and my (always stressed) CPU.

So, what’s today problem? Mike added autoconf 2.59d to ~arch lately, but seems like this move wasn’t liked by some packages, like transcode (the damned) and sshd (just a little package, eh? :|).

I’ve now masked latest autoconf, together with autoconf-wrapper and coreutils that needed it. It will be unmasked after a good part of the tree is checked and openssh is fixed. Leaving such a broken version of autoconf in tree is not a good idea.

Anyway, I’m now enslaving pitr box to build everything I maintain to check if there is something else that is blocking autoconf to go in ~arch (openssh IS blocking!). Let’s hope they are isolated cases (but I won’t count on that).

On the other hand, I’ve bumped libmp4v2 today to that fixes the problem of libmp4v2-1.5 with m4a files, so that Amarok is happy again πŸ˜›

And GIT for handling an SVN repository while writing patches is just wonderful πŸ™‚ Yes Maxi I know there’s dev-util/quilt, and I use it for almost everything (xine-lib patches, vlc, everything when I have to add a quick patch on the fly..), but it’s not a great idea when the soruces changes, for the way it tracks down them πŸ™‚ git does a quite nice job, although after importing the SVN is a good idea to git-repack it πŸ™‚

Okay now I have a few things to do anyway πŸ˜‰

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.