f15 2.6.39 rebase
mkkp4x4 at gmail.com
Thu Jun 30 20:10:41 UTC 2011
W dniu 30 czerwca 2011 21:49 użytkownik Genes MailLists
<lists at sapience.com> napisał:
> On 06/30/2011 03:04 PM, Michał Piotrowski wrote:
>> W dniu 30 czerwca 2011 20:58 użytkownik Dave Jones <davej at redhat.com> napisał:
>>> A lot of broken software is assuming version numbers are 2.6.x. We could push a load
>>> of userspace packages to fix it, but that's just the stuff we control. 3rd party add-ons
>>> would break for no good reason.
>>> This deviates from what upstream calls it, but it's just a number, and not breaking
>>> existing code in an update is more important here.
>> Of course you are absolutely right at this point :)
>> Thanks for your answer.
>>> For f16 of course, we'll make
>>> the 3.0 transition, because moving to a new release has differing expectations,
>>> and by the time it ships, hopefully everything that cares will be fixed.
> For what its worth - so far - running 3.0 on F15 I did need procps &
> mdadm updated - otherwise I've not seen too many issues that I know about.
> What else do you think might be breaking / broken / grumpy ?
It seems to me that the answer should be - check the package
requirements - but in this case probably is not so.
dracut >= 001-7
grubby >= 7.0.10-1
initscripts >= 8.11.1-1
linux-firmware >= 20100806-2
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
Obsoletes No Obsoletes
device-mapper-libs < 1.02.63-2
e2fsprogs < 1.37-4
initscripts < 7.23
iptables < 1.3.2-1
ipw2200-firmware < 2.4
isdn4k-utils < 3.2-32
iwl4965-firmware < 228.57.2
jfsutils < 1.1.7-2
mdadm < 3.2.1-5
module-init-tools < 3.13-1
nfs-utils < 1.0.7-12
oprofile < 0.9.1-2
ppp < 2.4.3-3
procps < 3.2.5-6.3
reiserfs-utils < 3.6.19-2
selinux-policy-targeted < 1.25.3-14
squashfs-tools < 4.0
udev < 063-6
util-linux < 2.12
wireless-tools < 29-3
xfsprogs < 2.6.13-4
More information about the kernel