[arch-general] problem installing custom kernel
Hi, I tried compiling and installing the linux kernel from ABS. I modified the PKGBUILD file as mentioned in the wiki. The kernel compiles fine and the pkg gets built with the name linux-custom as specified in the PKGBUILD. But when I try to install it I get the following error: $ sudo pacman -Uv linux-custom-3.2.2-1-x86_64.pkg.tar.xz Root : / Conf File : /etc/pacman.conf DB Path : /var/lib/pacman/ Cache Dirs: /var/cache/pacman/pkg/ Lock File : /var/lib/pacman/db.lck Log File : /var/log/pacman.log GPG Dir : /etc/pacman.d/gnupg/ Targets : linux-custom-3.2.2-1-x86_64.pkg.tar.xz loading packages... resolving dependencies... looking for inter-conflicts... :: linux-custom and linux are in conflict (kernel26). Remove linux? [y/N] N error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: linux-custom and linux are in conflict I have attached the PKGBUILD. -- Madhurya Kakati () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
On 1 February 2012 13:06, Madhurya Kakati <mkakati2805@gmail.com> wrote:
Hi, I tried compiling and installing the linux kernel from ABS. I modified the PKGBUILD file as mentioned in the wiki. The kernel compiles fine and the pkg gets built with the name linux-custom as specified in the PKGBUILD. But when I try to install it I get the following error:
$ sudo pacman -Uv linux-custom-3.2.2-1-x86_64.pkg.tar.xz Root : / Conf File : /etc/pacman.conf DB Path : /var/lib/pacman/ Cache Dirs: /var/cache/pacman/pkg/ Lock File : /var/lib/pacman/db.lck Log File : /var/log/pacman.log GPG Dir : /etc/pacman.d/gnupg/ Targets : linux-custom-3.2.2-1-x86_64.pkg.tar.xz loading packages... resolving dependencies... looking for inter-conflicts... :: linux-custom and linux are in conflict (kernel26). Remove linux? [y/N] N error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: linux-custom and linux are in conflict
I have attached the PKGBUILD. -- Madhurya Kakati
() ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
provides=('kernel26') conflicts=('kernel26') replaces=('kernel26') That's you problem in the PKGBUILD. Your custom kernel doesn't need to provide, conflict nor replace kernel26, as that is what causes it to conflict with the Arch one
On 02/01/12 at 01:13pm, Alexandre Ferrando wrote:
provides=('kernel26') conflicts=('kernel26') replaces=('kernel26')
That's you problem in the PKGBUILD. Your custom kernel doesn't need to provide, conflict nor replace kernel26, as that is what causes it to conflict with the Arch one
OK. I read the wiki page once more and found out my mistake. Since my kernel has already been compiled can I create the package without compiling it again? -- Madhurya Kakati () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
On 1 February 2012 13:24, Madhurya Kakati <mkakati2805@gmail.com> wrote:
On 02/01/12 at 01:13pm, Alexandre Ferrando wrote:
provides=('kernel26') conflicts=('kernel26') replaces=('kernel26')
That's you problem in the PKGBUILD. Your custom kernel doesn't need to provide, conflict nor replace kernel26, as that is what causes it to conflict with the Arch one
OK. I read the wiki page once more and found out my mistake. Since my kernel has already been compiled can I create the package without compiling it again? -- Madhurya Kakati
() ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
makepkg -R or makepkg --repackage
keskiviikko, 1. helmikuuta 2012 17:54:37 Madhurya Kakati kirjoitti:
OK. I read the wiki page once more and found out my mistake. Since my kernel has already been compiled can I create the package without compiling it again?
madkaka@archer# man makepkg
On 02/01/2012 05:24 AM, Madhurya Kakati wrote:
On 02/01/12 at 01:13pm, Alexandre Ferrando wrote:
provides=('kernel26') conflicts=('kernel26') replaces=('kernel26')
That's you problem in the PKGBUILD. Your custom kernel doesn't need to provide, conflict nor replace kernel26, as that is what causes it to conflict with the Arch one
OK. I read the wiki page once more and found out my mistake. Since my kernel has already been compiled can I create the package without compiling it again?
You can edit the .PKGINFO file directly that's within the .pkg.tar.xz. Also, you should leave provides (even make it provides=('linux')) so that if you ever want to remove the [core] kernel, you may do so.
participants (4)
-
Alexandre Ferrando
-
Jesse Juhani Jaara
-
Madhurya Kakati
-
Matthew Monaco