Older kernel cleanup command is inflexible and unportable

Bug #753147 reported by Sergey "Shnatsel" Davidoff
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
elementary OS
Fix Released
Undecided
Sergey "Shnatsel" Davidoff

Bug Description

The current command for removing obsolete kernel package - apt-get remove -f -y --purge linux-image-2.6.35-22 - is inflexible. It works for Maverick but doesn't work if I want to run ebuild in Lucid or Natty or to update Jupiter image or whatever.

Tags: ebuild

Related branches

Changed in elementaryos:
status: New → In Progress
assignee: nobody → Sergey "Shnatsel" Davidoff (shnatsel)
Revision history for this message
Avi Romanoff (aroman) wrote :

eBuild is meant only to run on the specified target version. i.e Jupiter only Maverick ONLY.

Subsequent versions will use the appropriate kernel version corresponding to their respective base distro.

Changed in elementaryos:
status: In Progress → Won't Fix
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Hey, why "won't fix" when I've marked that I'm working on it?
And I've got a fix already, see the linked branch.

BTW: A good tool is useful where it's expected to work. A great tool is useful in completely unexpected places. For example, I want to build an LTS image with ebuild. And maintaining ebuild having kernel version hard-coded will be time-consuming (read: it's simply a waste of time).

Revision history for this message
Avi Romanoff (aroman) wrote :

I marked it as won't fix because this version of eBuild will not be used going forward.
eBuild is only to be used with the specific targeted version.
Though the kernel image detection is a good idea. I'll mark this as fixed, and be sure that change gets incorporated into the J+1 ebuild. thanks =)

Changed in elementaryos:
status: Won't Fix → Fix Committed
Revision history for this message
Eduard Gotwig (gotwig) wrote :

hm, its still a bit uncomfortable. you have to change the kernel number manual at the line: mkinitramfs -o /initrd.gz 2.6.****-generic, in conf.sh

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Do we need an mkinitramfs command at all? Isn't it handled by postinst script in the kernel package? It worked fine for me without this command in UCK.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

OK, converted it to using the latest kernel version as well (if we'd use UCK, we wouldn't have to think about it)

Changed in elementaryos:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.