June 2011 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel package versioning
by Michal Marek 14 Jun '11

14 Jun '11

Hi, Today I finally got round to properly fix the versioning mess in master and the upstream branches (vanilla and linux-next). This mail is meant to document how it's supposed to work. You can skip to the table at the end of the mail for a summary. In upstream ~~~~~~~~~~~ Upstream git tags look like "v3.0-rc1", "v3.0-rc2", the final tag is going to be "v3.0" and the subsequent stable releases will be tagged as "v3.0.1", "v3.0.2" and so on. The tarballs are named after these tags, so we have linux-3.0-rc2.tar.bz2 that contains the linux-3.0-rc2 directory. HOWEVER: Several userspace programs expect the kernel release string be three numbers and fail if it isn't the case. This also affects depmod, so omitting the third zero would break all setups using modules. So the kernel continues to call itself "3.0.0-rc2" and this will probably stay for some time now. In short, there are two version numbers now: I'll refer to them as the "tarball" version and the "uname" version (might differ from the "tarball" version in the trailing zero). In openSUSE ~~~~~~~~~~~ The SRCVERSION variable in the config.sh file is set to the "tarball" version. The mkspec script takes this and generates two more versions: The "uname" version (appends a zero if necessary), that is used during the build (so the actual build didn't require any modifications in the end) and the "rpm" version. I used the fact that the build was broken anyway as an opportunity to revamp the way the rpm packages are numbered. The final releases will have three numbers, i.e. "kernel-desktop-3.0.0-...", "kernel-desktop-3.0.1-...", etc. However, -rc releases will use the "rcX" tag instead of the last zero, so the current package will look like "kernel-desktop-3.0.rc2-...". Letters sort before numbers in rpm, so this will not break ordering and at the same time you will be able to tell the upstream version from the rpm version easily. Until now, we abused the rpm Release: field for this, but this only worked in the Kernel:* projects and not in the official distribution. To summarize, the mapping will be like: rpm tarball uname -r kernel-desktop-3.0.rc2-* linux-3.0-rc2.tar.bz2 3.0.0-rc2-*-desktop kernel-desktop-3.0.0-* linux-3.0.tar.bz2 3.0.0-*-desktop kernel-desktop-3.0.1-* linux-3.0.1.tar.bz2 3.0.1-*-desktop The "*" above is the rpm Release: number assigned by the build service. I hope that despite the long mail, the scheme will actually be easy to understand, that would will be able to quickly tell what kernel is in the distro by just looking at the rpm packages. Michal PS: I didn't cover KMPs at all at this point, they might work or there might be some fixes needed, I'll look into this later. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

4 6

[opensuse-kernel] Kernel:HEAD failure
by Cristian Rodríguez 13 Jun '11

13 Jun '11

Hi: Currently Kernel:HEAD failed to build completely All packages fail with ake: Leaving directory `/usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2' ++ make -s kernelrelease -C /usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2 O=/usr/src/packages/BUILD/kernel-desktop-3.0/linux-obj + krel=3.0.0-rc2-1-desktop + '[' 3.0.0-rc2-1-desktop '!=' 3.0-rc2-1-desktop ']' + echo 'Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop' Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.t9w0V6 (%prep) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

5 8

[opensuse-kernel] BNC #608060 Status
by Andi Sugandi 13 Jun '11

13 Jun '11

Hello developers! I filled a bug[0] about a year ago, and now find it can be resolved by installing these packages on openSUSE 11.4: rtl8192se-kmp-desktop-0019.1207.2010_k2.6.37.6_0.5-1.4.x86_64 rtl8192se-0019.1207.2010-1.4.x86_64 rtl8192se-firmware-0019.1207.2010-1.4.noarch *Btw, is it needed by all of those three packages or only rtl8192se-kmp-desktop to get the device work?* from driver:/wireless/11.4-update repository. Should I change the status to: RESOLVED - FIX *or* RESOLVED - UPSTREAM ? Because I have no idea about the "resolved" process, whether it is fixed by openSUSE Team or by upstream work. Thanks in advance. [0] https://bugzilla.novell.com/show_bug.cgi?id=608060 Best regards, -- Andi Sugandi. Bandung, Indonesia. openSUSE-id Team, openSUSE Community Member. http://en.opensuse.org/User:Andisugandi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] How do I submit a new package to opensuse-contrib
by doiggl＠velocitynet.com.au 12 Jun '11

12 Jun '11

On Sat, 11 Jun 2011 19:51:47 +0200, Pavol Rusnak <prusnak(a)opensuse.org> wrote: > On 11/06/11 16:38, doiggl(a)velocitynet.com.au wrote: >> Hello >> How do I submit a new package to opensuse-contrib ? >> It does not exist in factory. >> It has been built in bs [1] and announced on [2][3] >> >> What do I do next for submission to opensuse-contrib ? > > In general, we try not to add more packages to Contrib and submit them > directly to Factory instead. This is somehow special case. Please ask on > opensuse-kernel(a)opensuse.org mailinglist what would be the best option ... Hello The above answer I got on the opensuse-contrib(a)opensuse.org [4] I'll re-ask the original question in this list. opensuse-kernel(a)opensuse.org How do I submit a new package to opensuse-contrib ? It does not exist in factory. It has been built in bs [1] and announced on [2][3] What do I do next for submission to opensuse-contrib ? Hopefully this is the correct list to ask. Thanks Glenn [1] https://build.opensuse.org/package/show?package=kernel-reiser4&project=home… [2] http://www.spinics.net/lists/reiserfs-devel/msg02830.html [3] https://reiser4.wiki.kernel.org/index.php/Main_Page [4] http://lists.opensuse.org/opensuse-contrib/2011-06/msg00005.html -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 1

[opensuse-kernel] Kernel:HEAD failure
by Cristian Rodríguez 11 Jun '11

11 Jun '11

Hi: Currently Kernel:HEAD failed to build completely All packages fail with ake: Leaving directory `/usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2' ++ make -s kernelrelease -C /usr/src/packages/BUILD/kernel-desktop-3.0/linux-3.0-rc2 O=/usr/src/packages/BUILD/kernel-desktop-3.0/linux-obj + krel=3.0.0-rc2-1-desktop + '[' 3.0.0-rc2-1-desktop '!=' 3.0-rc2-1-desktop ']' + echo 'Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop' Kernel release mismatch: 3.0.0-rc2-1-desktop != 3.0-rc2-1-desktop + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.t9w0V6 (%prep) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0

[opensuse-kernel] FYI - an announcement on news.o.o.
by Andreas Jaeger 07 Jun '11

07 Jun '11

The news team just published "Get your fresh kernels from openSUSE and test Linux 3.0!" http://news.opensuse.org/2011/06/06/get-your-fresh-kernels-from-opensuse-an… test-linux-3-0/ Thanks Michal for your input on this! Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

3 2

Re: [opensuse-kernel] Will OpenSuse 12 release with pvops Kernel 3.0, and Xen to match?
by Jan Beulich 05 Jun '11

05 Jun '11

>>> 06/03/11 5:10 PM >>> >If so, will that be the pvops-capable kernel? Or a port, as is current, >to a non-pvops, traditional kernel? > >I'm looking to know if v12 will release with native/pvops Xen support >(http://blog.xen.org/index.php/2011/06/02/xen-celebrates-full-dom0-and-domu-…) >or whether we'll still need to use versions of SuSE's forward ported >kernels. A firm decision wasn't made afaik, but I'm personally expecting to continue the forward port route until the pv-ops code is really on par wrt features currently present in the forward ported version, and shows an acceptable rate of regressions. >If pvops, I gather that Xen itself will need to be compiled against/for >the pvops kernel. Is that also the plan for v12? Xen doesn't get built for a particular guest OS, even less a particular implementation of one. Jan

2 1

[opensuse-kernel] Will OpenSuse 12 release with pvops Kernel 3.0, and Xen to match?
by p17000＠operamail.com 03 Jun '11

03 Jun '11

@openSUSE:Factory_versions states "the current version of" kernel --> v2.6.39. I was informed in #opensuse-factory that that's going to be bumped to new '3.0' kernel, which ,iiuc, is "just" a version numbering change, with no functional changes (not 100% sure of that yet)? Is that correct? If so, will that be the pvops-capable kernel? Or a port, as is current, to a non-pvops, traditional kernel? I'm looking to know if v12 will release with native/pvops Xen support (http://blog.xen.org/index.php/2011/06/02/xen-celebrates-full-dom0-and-domu-…) or whether we'll still need to use versions of SuSE's forward ported kernels. If pvops, I gather that Xen itself will need to be compiled against/for the pvops kernel. Is that also the plan for v12? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

1 0