April 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] rfc name for new library package
by Brian K. White 15 Apr '11

15 Apr '11

Hello, I've been maintaining and using a .so package of: http://freshmeat.net/projects/jbigkit for some time in a home repo, and recently got it added to graphics: https://build.opensuse.org/package/show?package=jbig-kit&project=graphics Next I want to submit it for inclusion in Factory so that it can then be used to add jbig support to libtiff, hylafax, ghostpdl, ghodtscript, others. Some of these already have jbig support but it's via direct code inclusion. But for example ./configure in current libtiff will automatically find and use the jbig include files and shared lib if the package above is installed. The change to the tiff3 .spec is merely to add jbigkit-devel to buildrequires. I've been doing that in my home repo for a while. However before submitting to Factory I want to see if the package name should be changed so that we're not either stuck with a stupid name forever, or change the name sometime later after it's been in use already. The only reason the package name is "jbigkit" or "JBIG-KIT" is because that's the name of the upstream tar. the only reason the upstream tar is named that is because that's what that is, a kit for demonstrating jbig and devoloping with it. The upstream code is really meant to be included directly within other programs, not packaged as a shared library. But the library itself is just "jbig" or "jbig2" So request for comments, I think I should: * Change the base package name to just jbig or jbig%{major}. * Have only the sample binaries and docs in the base package. * Move the libraries into a libjbig%{major} package Basically just like jpeg https://build.opensuse.org/package/view_file?file=jpeg8.spec&package=jpeg8&… And pretty much ignore the fact that the upstream tar is named "jbig-kit". The installed stuff is not a "kit" but a finished product that uses the original kit. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] by what process modules.dep created at new kernel installation?
by Felix Miata 14 Apr '11

14 Apr '11

I decided for various reasons to un-mothball a P3-700 system with latest installed anything 11.1M2 running some variant of 2.6.27. I used zypper to rm various non-necessities and streamline the dup process to Factory. After the rms I did in the following: rpm zypper libzypp satsolver-tools wget curl hal dbus-1 udev glibc mkinitrd openSUSE-release yast2-bootloader perl-Bootloader and the deps they pulled. Then I did in kernel-default, which failed to create initrd due to inability to find modules.dep for 2.6.38. At the time I didn't recognize what that meant, but since found that was what should have been installed as /lib/modules/2.6.38-4-default/modules.dep. The question is, by what process is modules.dep created? Is it supposed to be a part of the kernel rpm, or is it generated by calling depmod from the rpm installation script, or something else? It would no longer boot off either old kernel or new kernel, so I opened it via chroot to actually do the dup, which managed to install 2.6.38-4-pae with a modules.dep file. Did I catch a bad break by getting a broken 2.6.38-4-default rpm, or was some consequence of the partial upgrade from 11.2M2 to Factory 11.5 the problem, or something else? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Tumbleweed: YOU conflict error
by Greg Freemyer 14 Apr '11

14 Apr '11

All, Is there a simple way security updates can be tested to install cleanly on a Tumbleweed system? Can we make that part of the process somehow? == details I just tried to do a YOU, but I get a conflict that a typical user should not have to face just because they're using Tumbleweed: === #### YaST2 conflicts list - generated 2011-04-01 11:29:43 #### patch:python-virtualbox-4219.noarch conflicts with virtualbox-qt.x86_64 < 4.0.4-1.6.1 provided by virtualbox-qt-4.0.4-1.2.x86_64 [ ] Following actions will be done: install virtualbox-qt-4.0.4-1.6.1.x86_64 (with vendor change) obs://build.opensuse.org/openSUSE:Tumbleweed --> openSUSE install virtualbox-4.0.4-1.6.1.x86_64 (with vendor change) obs://build.opensuse.org/openSUSE:Tumbleweed --> openSUSE [ ] do not install patch:python-virtualbox-4219.noarch #### YaST2 conflicts list END ### ========== If I revert virtualbox-qt to the OSS version, it will break due to a kernel incompatibility I'm pretty sure. Because I know that, I can choose not to install the patch:python-virtualbox-4219.noarch. For me it's not that big an issue, but it is not knowledge a typical user has. Thanks Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 30

[opensuse-factory] multimedia:apps coriander links to DISCONTINUED:openSUSE:11.1 coriander
by Dave Plater 14 Apr '11

14 Apr '11

I just had a submit request to multimedia:apps coriander which had a broken link to "DISCONTINUED:openSUSE:11.1 coriander", the submitters package was also linked to "DISCONTINUED:openSUSE:11.1 coriander". I deleted mmaps coriander and used osc copypac from the submitters home project to recreate mmapps coriander and because it was there before, recreated the mmapps link. Can somebody enlighten me as to why coriander is linked to DISCONTINUED:openSUSE:11.1? Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 4

[opensuse-factory] [tumbleweed] no power down from init 0
by Felix Miata 13 Apr '11

13 Apr '11

The oldest system I have with 11.4 or newer is P3 f6 m8 s1 700MHz with PAE on a 440BX chipset (Tyan s1846). 10.2 with 2.6.18 kernel when init 0 from root powers down the system. With the 2.6.37 & 2.6.38 kernels on Tumbleweed & Factory, the init 0 process just stops after sending all processes the KILL signal. Turn off computer from KDM fails similarly. No menu.lst stanzas on any use *apic* or *apm* on cmdline. I don't recall my other systems with 11.4 or newer doing this, but they're all K7 or P4. What's up? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 9

[opensuse-factory] [tumbleweed] Welcome to openSUSE...
by Felix Miata 11 Apr '11

11 Apr '11

11.4??? Once Tumbleweed is enabled, wouldn't it be nice to be mentioned on the login screen, maybe via an appendage to /etc/SuSE-release? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Expected usage of Tumbleweed?
by Ken Savage 11 Apr '11

11 Apr '11

Hi folks, I had added Tumbleweed to my repo list waaaay back in the 11.3 days (can you *remember* those days!!? ;) .... and continued with it when I upgraded to 11.4. And certainly it works: if I zypper dup --from Tumbleweed, the latest shiny TW packages find their way into my system. What I'm wondering about is the discrepancy I see in the list of packages that will be upgraded when I issue a plain "zypper dup" compared to the TW-based list of packages. Fair enough that my Packman and VLC repos might have some newer files than what has managed to be CONFIRMED to be working in TW. But are the openSUSE BuildService repos more cutting edge than TW as well? What about the 11.4 Upgrades repo (/update/11.4) ? I guess my question boils down to this: Having added TW as a repo, are there other repos that I should make sure are deactivated, and from here forward, merely do zypper dup's from the TW repo? What's the generally anticipated usage pattern of a sysadmin who has hooked themselves into Tumbleweed? Many thanks for your thoughts, Ken -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 7

[opensuse-factory] Atheros wifi not working in Tumbleweed
by Pat 09 Apr '11

09 Apr '11

Acer 5100 with Atheros chipset not working in Tumbleweed -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Fwd: [opensuse-project] Versionitis - Results (Or: The next openSUSE release is openSUSE 12.1)
by Andreas Jaeger 07 Apr '11

07 Apr '11

For those that don't read the project mailing list or news.o.o, I'm forwarding what I just send to opensuse-project, Andreas ---------- Forwarded Message ---------- Subject: [opensuse-project] Versionitis - Results (Or: The next openSUSE release is openSUSE 12.1) Date: Wednesday, April 06, 2011, 10:06:30 From: Andreas Jaeger <aj(a)novell.com> To: opensuse-project(a)opensuse.org The voting on how to do the versioning is over and the "old school" has won by 55 per cent (of 98 participants). Thanks to all that participated in the two votes and the discussion around the topic. As Coolo said in http://lists.opensuse.org/opensuse-project/2011-03/msg00516.html, we'd like to make a small change to the numbering: We will not have a .0 release but only .1, .2, .3 release. Since we have releases in three months, the November release is always the .1 release, the July release the .2 and the March release the .3. So, the plan is that the next release will be called openSUSE 12.1 and launched on the 10th of November, 2011! Two years later - on the 14th of November, 2013 - we will then have the openSUSE 13.1 release. So, the next four releases are: * November 2011: openSUSE 12.1 * July 2012: openSUSE 12.2 * March 2013: openSUSE 12.3 * November 2013: openSUSE 13.1 Detailed results for logged-in openSUSE members are available at the connect poll page and I have reproduced them here as well: * A: "old school": Like currently but only counting the right number until 3: 55% (54 votes) * B: "Fedora style": Just integers: 29 % (28 votes) * C: "Ubuntu style": YY.MM: 16 % (16 votes) This is also consistent with the results of thefirst public voting (see http://lizards.opensuse.org/2011/03/28/opensuse-release-versioning-poll-on- last-three-options/ ). Note that openSUSE does not have a major and minor numbering, even if it seems so. There is right now no difference in any way between what we would do for openSUSE 11.4 or 12.0 or 12.1 – and no sense to speak about openSUSE 11 or openSUSE 11 family. We also had in the past no process on how to name the next release (when to increase which parts of the number). I think this new versioning is still consistent with the old one but also an improvement since it's now clear that we change the first digit every two year. The first poll showed that half of our users prefer a date based versioning and the other a consecutive numbering. So, depending on your point of view, you can see this as a mixture of both or as consecutive numbering ;) So, time now to make openSUSE 12.1 a great release! Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org ----------------------------------------- -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] Expired Kernel: repos certificates
by Jiri Slaby 06 Apr '11

06 Apr '11

Hi, one czech opensuse user wrote me that certificates used for our kernel:* repos are expired. I checked and that's indeed true: pub 1024D/A29F6635 2008-04-09 [expired: 2010-06-18] uid Kernel OBS Project <Kernel(a)build.opensuse.org> Who manages the certificates? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1