You are not logged in.
I was looking into the new PKGBUILD in the /var/abs/core/kernel26 folder, as I wanted to update my custom kernel. I was editing the new PKGBUILD when I saw something weird...references to kernel.org files and archlinux.org patch seems to be same as the 2.6.37 version. Is _basekernel value not updated? Am I wrong?
Take a look:
new PKGBUILD (I copied only relevant lines):
_basekernel=2.6.37
pkgver=${_basekernel}
pkgrel=6
_patchname="patch-${pkgver}-4-ARCH"
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/${_patchname}.bz2
now...these is exactly the same as PKGBUILD for 2.6.37. But the new files are:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.1.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/patch-2.6.37.1-1-ARCH.bz2
If I am right, someone has to update variable values...
TIA
Gemon
Last edited by gemon (2011-02-21 22:17:23)
Offline
Is don't think I get what you mean. The current kernel is 2.6.37.1-1. Have you updated your abs?
Offline
I think the confusion arises because the "ARCH" patch includes the upstream patch for 2.6.37.1.
Offline
yesterday night I updated abs and then made a pacman -Syu right after, just to discover the new kernel...either I've been unlucky and I got the period between package update and abs update, or I dunno...however I'm gonna check back when I get back home
My abs local repository should be up-to-date, since I've checked the signature line and I've found out that it was changed (I did grep -i pkgbuild /var/abs/core/kernel26/PKGBUILD). The one from previous abs refresh was:
# $Id: PKGBUILD 108125 2011-01-29 19:39:45Z tpowa $
Now I can't run abs since I'm behind a firewall blocking rsync traffic, but I'm pretty sure date was 2011-02-xx
Allan: do you mean that patch-2.6.37-4-ARCH includes 2.6.37.1-1 patches?
Gemon
Last edited by gemon (2011-02-21 11:09:08)
Offline
You're still out of date - the current Arch patch is 2.6.37.1-1-ARCH. And yes, it includes the upstream bump to 2.6.37.1.
Offline
well...I had time to check so...this is the content for the PKGBUILD after I run abs yesterday (pasted only relevant lines):
# $Id: PKGBUILD 109724 2011-02-12 08:01:06Z tpowa $
pkgbase="kernel26"
pkgname=('kernel26' 'kernel26-headers' 'kernel26-docs') # Build stock -ARCH kernel
_kernelname=${pkgname#kernel26}
_basekernel=2.6.37
pkgver=${_basekernel}
pkgrel=6
_patchname="patch-${pkgver}-4-ARCH"
this is the one I run tonight...looks updated now
# $Id: PKGBUILD 110322 2011-02-18 20:13:49Z tpowa $
pkgbase="kernel26"
pkgname=('kernel26' 'kernel26-headers' 'kernel26-docs') # Build stock -ARCH kernel
_kernelname=${pkgname#kernel26}
_basekernel=2.6.37
pkgver=${_basekernel}.1
pkgrel=1
_patchname="patch-${pkgver}-${pkgrel}-ARCH"
now patch filename and kernel sources correctly resolve to the latest ones.
but believe me, right after I had the 2.6.37.1-arch kernel, the abs PKGBUILD was outdated...probably it is updated after kernel package is released. doesn't matter
all in all...now it's ok
Gemon
Offline
I believe ABS only synchs once every 24 hours
Offline
I believe ABS only synchs once every 24 hours
Yes, and it looks like it's unlikely to change http://mailman.archlinux.org/pipermail/ … 18347.html
Offline
Get the latest PKGBUILD here (just search for kernel):
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline