November 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "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

4 3

Re: [opensuse-factory] repository priorities with Tumbleweed
by Thomas Langkamp 16 Jul '15

16 Jul '15

> No, please don't confuse people, if you add more repos than just > Tumbleweed you really had better know what you are doing or bad things > can, and will, happen :) I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " >You do know the legal reasons behind why packman is there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 18

[opensuse-factory] Export broken for KinfoCenter
by Roger Luedecke 30 Jan '15

30 Jan '15

Export button is greyed out no matter what. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] Nothing provides /usr/bin/php5
by Sascha Peilicke 11 Jan '14

11 Jan '14

On 12/01/2011 11:44 AM, Kyrill Detinov wrote: > > Hello. > > We have one package affected in standard repo: leechcraft-eiskaltdcpp. > The program itself doesn't require php5. But the package includes > example scripts with shebang '!/usr/bin/php5'. So the package isn't > installable. > > Also I see the same problem with pgfouine from Contrib (written in > PHP) and eiskaltdcpp from filesharing repo. Maybe more in third-party > repositories. > > Can we have symlink /usr/bin/php -> php5 in php5 package? Or affected > packages should be fixed? > Please file a bug against php5 and assign to Cristian Rodríguez. -- Viele Grüße, Sascha -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Re: What is the purpose of the systemd journal service?
by Linda Walsh 14 May '13

14 May '13

Cristian Rodríguez wrote: > El 15/09/12 11:49, Per Jessen escribió: > >> I do want to log, but I've looked at the journal already and didn't see >> anything that wasn't already in /var/log/messages, /var/log/mail etc. >> Seems like a duplication of effort and a waste of space in >> /var/log/journal. (which afaict can just be deleted). > > It is significantly more powerful than traditional logging: > > For example > > journalctl /usr/bin/foo --> get messages from program foo > > journalctl /dev/sda --> hard-drive problems ? > > journalctl -p error --> only errors > --- I assume the full power of linux's text utilities can be used on them - like grep, sort, awk, perl... vim... Having logs recorded in a non-text binary format tends to make MS logs out-a-sight, out-a-mind, where as I often go and poke around in /var/log and look to see if I notice anything 'new'. If I can't look at the whole stream as a text (messages, warnings, etc), I don't get a field for what is right or wrong behavior and certainly wouldn't be able to pick out an anomaly if I had to query each item separately -- that global view is a good way to look for 'warts'... MS makes it much to painful to do hat -- 1 error / page, everything in 300 separate queries ... ug! > Currently it is not a full replacement for syslog but I suggest you to > check it out. > I tend to use ngsyslog for the filtering benefits. -- really has some powerful filtering in the 2.x line -- had to label ng3x taboo, so it won't overwrite a working config with a non working config... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

27 129

[opensuse-factory] rpmlint: warn if -ansi is used to build packages
by Cristian Rodríguez 19 Mar '13

19 Mar '13

Hi: Will be cool if rpmlint could warn when upstream packages attempt to use the -ansi gcc option because it inhibits usage of gcc builtin functions while optimizing (list here --> http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other-Builtins) most recently it caught my attention that it also disables the new "optimize-strlen" pass in gcc 4.7, in particular this: "for hosted compilations where stpcpy is available in the runtime and headers provide its prototype, e.g. void foo (char *a, const char *b, const char *c, const char *d) { strcpy (a, b); strcat (a, c); strcat (a, d); } can be optimized into: void foo (char *a, const char *b, const char *c, const char *d) { strcpy (stpcpy (stpcpy (a, b), c), d); } " when -ansi is used and (defined(_GNU_SOURCE) || (_XOPEN_SOURCE >= 700 || _POSIX_C_SOURCE >= 200809L)) is false, there is no stpcpy prototype and hence no optimization. Thoughts ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 28

[opensuse-factory] Re: Fontconfig fonts priority
by Lars Müller 19 Feb '13

19 Feb '13

On Wed, Feb 01, 2012 at 12:22:50PM +0100, Mariusz Fik wrote: > Dnia środa, 1 lutego 2012 01:03:13 Sven Burmeister pisze: > > Am Dienstag, 31. Januar 2012, 22:43:11 schrieb Mariusz Fik: > > > > > > current fontconfig configuration[1] sets the highest priority for > > > Microsoft font. If user install them (i.e. Times New Roman, Arial, > > > Consolas) they will be set as _default_ for respectively families > > > (sans-serif, sans, monospace). Why do we promote Microsoft fonts > > > instead support open fonts, shipped with system? > > > > > > I propose[2] to downgrade those fonts. Thanks to this, we keep our > > > default font settings but those MS fonts will be still available for > > > use. > > > > > > Whats Your point of view in this case? > > > > Are you sure that the free fonts have the same quality – even if > > anti-aliasing is disabled? I remember ugly characters with free fonts > > unless I would use bitmap fonts and that's a no-go IMHO. My suggestion is: > > Set the best quality fonts as default. Those that do not want to use MS > > fonts simply do not install them. There was a reason to prefer those fonts > > and AFAIR it was quality or lack thereof regarding the free fonts. > > The goal is: to not set those fonts as _default_ and not to get them rid off . > Why Joe when install i.e. Consolas font should get it set as default monospace > font? Maybe he want's only to use it in a single program? Please continue this thread at opensuse-factory as it was already suggested as part of this thread. Therefore the Reply-To got set. The begin of this thread was here: http://lists.opensuse.org/opensuse/2012-01/msg02101.html Why? Cause it's more likely that you'll get the required attention. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

8 18

[opensuse-factory] Maintainer model clean up
by Robert Schweikert 23 Jan '13

23 Jan '13

Hi, This is also related to the "Coolo needs help thread". During osc12 we had various discussions related to the topic of getting the distribution out the door and how we can get there within the release schedule that we had agreed to a while back. Part of this discussion are the two sessions I had the opportunity to lead, both are available on youtube opensusetv, if you are interested in this topic please go and watch these sessions, as well as Stephan's session, also on youtube. Unfortunately we did not have video equipment in the BoF session. The basic proposal is, and this received general agreement at osc12, that we will move toward changing the model as proposed in the session. This implies the following: - In the web UI one will no longer see inherited project maintainers on the package page, only the "true" package maintainers. (Inherited "maintainers" will be hidden in an expandable tree) - We will collect information about all packages in all devel projects that feed factory. We will generate a list of packages that have no maintainer, and a list of packages that need help, i.e. a package that has fewer than 5 maintainers. In addition we will list packages that have more than 5 maintainers and try to encourage maintainers from those packages (to get the number to 5) to take on packages that need help. - We want to clean up the devel project maintainer list to a ratio of 10/500 packages with a max of 25. ~ In many cases package maintainers in a given project do not care about all the other packages in the project, yet they are on the project maintainer list. ~ Also many people have their Hermes notifications disabled as they get too many messages about packages they do not care, hopefully with the changes more people will re-enable their Hermes notifications (more on this below) - We would like to see a notification on the package page if the package fails to build in factory - Would like to see package build status information on the factory status page about the status of the package in it's devel project. - Having the monitor page and the status page presented in the current form is confusing, we need to somehow merge the information. - It would be really nice if there were some kind of policy engine that could enforce the "no more than 5 per package" and the "no more than 25 project maintainers" policies. ~ now OBS is not just for openSUSE, thus this cannot be hard coded into the OBS code, thus this is potentially a lot of work. - We would like to have some kind of rating system on the devel projects - We will produce guidelines for package and product maintainers outlining what is expected. ~ These guidelines are not hard rules, but provide help to new people stepping in to define the role they are comfortable with. There appears to be a problem that the complete void of guidelines in this area leads to paralysis and people just do not know what to do if they want to help. We have documents how to package, these guidelines will be a hopefully short list of "what is expected". These are the rough outlines of the "plan". Obviously there is work to be done and the OBS team already has plenty to do. It is up to me to document in more detail the requirements/use case before a potential timeline can be developed. I will also start a wiki page attempting to define the various roles in the devel process and then opening that up for discussion once the basics are in place. Now to a couple of counter points. - Yes we will step on some people's toe, sorry. Meaning if you get removed as project maintainer from a devel project and you really really want to be a project maintainer you are probably not going to be happy. Please do not take it personal and get yourself added back to the project. Preferably you would find one of the project maintainers that remained, by chance and chance alone, and get that person to drop of the list. Chances are you will find someone willing to "make space for you" ~ Sorry, but this process has to be somewhat arbitrary due to the large number on the various devel projects. ~ Please be not offended, there is no vicious intent, just the intent to help the project grow and scale better. - Yes, the "rules" are changing, and if you maintain a package that is also in factory there will now be some expectations ~ In the end we all should have the same goal, create a quality distro in the time frame we promise, thus this should really not be a big deal Before I close this rather long e-mail (sorry) I have a kind of survey question. I would like to have the hermes settings of package maintainers reset "automatically" as we move through the house keeping project such that package maintainers get notification of build failures of their packages. I realize many people have these turned off today, but again, this is probably due to the number of notifications due to the project maintainer mails that most people do not care about. OK, before I write another couple of pages about this subject I'll stop here. Thanks for your attention, please no flaming, bitching and moaning. Great ideas and help are welcome. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 12

[opensuse-factory] gtkglext missing from factory
by Josef Reidinger 09 Jan '13

09 Jan '13

Hi, some project in games repository start failing as opensuse:Factory doesn't have gtkglext. Is it intention? I found that it is in 12.2 and cannot find in in opensuse:DROPPED. It is accident or intention? Thanks for answer Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 11 Dec '12

11 Dec '12

Ken Schneider - openSUSE wrote: > On 11/28/2012 07:07 PM, Linda Walsh pecked at the keyboard and wrote: > > Linda, > > You have been ask several times to stop cross posting, so once again > please stop. ---- Um which list does one post questions about current and future development and current releases on? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

[opensuse-factory] Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 11 Dec '12

11 Dec '12

Perhaps someone can explain to me why Windows doesn't need a pre-boot ramdisk in order to boot, while Linux does? I know Windows doesn't have all the drivers for all the hardware linked in with it's kernel -- it's dynamically loaded out of it's "/bin (windows/sytem32)" dir. So why does the linux kernel have this extra complication while windows does not? It's a bit embarrassing, I would think to see the wide range of HW supported by Windows **without** a special 'initrd' for drivers, while linux still doesn't support the range of HW that Windows does (some, but not ALL of that being due to short-sited HW providers who can't provide open specs or drivers). So what is Windows doing 'right', that Linux is unable to do? Maybe this is a kernel question -- maybe OpenSuse can't doing anything about this -- is this the case -- is this some kernel limitation? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 10

[opensuse-factory] Yast Partitioner creates partition overlap of cylinders that's just plain wrong
by Roman Bysh 10 Dec '12

10 Dec '12

Hello List mates, I recently purchased a Western Digital "Black" 500 GB drive with 7200 rpm. When I create partitions during the install using the "optimal" option, the following appears when I select fdisk. fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00033420 Device Boot Start End Blocks Id System /dev/sda1 * 2048 146802687 73400320 83 Linux /dev/sda2 146802688 155187199 4192256 82 Linux swap / Solaris /dev/sda3 155187200 976773119 410792960 f W95 Ext'd (LBA) /dev/sda5 155189248 870322175 357566464 83 Linux /dev/sda6 870324224 976752639 53214208 83 Linux linux-nxcl:~ # fdisk -lu=cylinders Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00033420 Device Boot Start End Blocks Id System /dev/sda1 * 1 9139 73400320 83 Linux /dev/sda2 9139 9660 4192256 82 Linux swap / Solaris /dev/sda3 9660 60802 410792960 f W95 Ext'd (LBA) /dev/sda5 9661 54176 357566464 83 Linux /dev/sda6 54176 60801 53214208 83 Linux Why is 1st partition's last cylinder sharing the same number with the 2nd partition's first cylinder when the gui showed the 2nd partition starting on the next cylinder? When I select the "Cylinder" option under settings I get the following. However, fdisk shows that that the physical partitions are overlapping. Example Device Boot Start End /dev/sda1 * 1 9139 /dev/sda2 9140 9661 /dev/sda3 9662 60802 /dev/sda5 9663 54176 /dev/sda6 54177 60801 Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 17

Re: [opensuse-factory] mkinitrd or dracut ?
by Frederic Crozat 09 Dec '12

09 Dec '12

Le jeudi 01 novembre 2012 à 20:23 +0100, Andreas Jaeger a écrit : > On 11/01/2012 12:03 PM, Raymond Wooninck wrote: > >[...] > > Again based on the current status of mkinitrd (and the fact that the above bug > > somehow seems to take quite some time to be resolved) I really wonder if we > > have to keep the old mkinitrd functionality or that we should go with a newer > > technology which is used by more distributions. Especially as that we are > > already providing working packages for dracut. > > Currently mkinitrd has support for some hardware/boot scenario that > dracut has not, so before we make dracut the default (or drop mkinitrd) > we need to get everything running. Hannes, Frederic, what's exactly is > missing? * dsdt support (skeleton in place) * blogd (not sure it is still needed with systemd) * rtc / zoneinfo (might not be relevant anymore, might be worth asking Werner) * EC2 (but it is just a workaround) * kdump * mtab "migration" * "supported" option for kernel module * netconsole -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 27

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 04 Dec '12

04 Dec '12

Philipp Thomas wrote: > For the umteentht time: STOP the stupid cross posting and make up your > mind as to where to discuss this. ---- You tell me where it belongs. It's about Suse 12.2 and suse 12.3 and beyond. Last person I asked which list I should shut out of the discussion, I got no answer, so what's your answer. > >> Windows doesn't need extra disks / drivers to be pre-loaded >> unless you are booting from a rescue disk/installation disk. > > You have followed the links to the Wikipedia articles describing the > boot mechanisms in various Windows versions that David posted > yesterday? ==== Why should I? I've read the Windows system internal's book written by a Windows "Fellow", that describes the process in considerably more detail in chapter 13. Maybe you should read the book 'Windows System Internals (5th ed). It tells you why -- boot sector loads a basic device aware booter like lilo, that can then boot images off of any of windows devices... None of them require an initrd. Any other questions? I had stopped cross posting the past several posts, but you seemed to be a case-in-point of not getting the fact that if it was NEVER appropriate to cross post, it could be blocked for everyone at the list-reflector. If it is the case that it is appropriate at times -- then what about a cross-topic subject like this isn't appropriate - what would be an example of something that would be if this isn't? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 7

[opensuse-factory] Nvidia now requires devel packages ?!
by Daniele 03 Dec '12

03 Dec '12

Hi, I don't know if this is a packaging bug but: Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW packages are going to be installed: gcc gcc47 glibc-devel kernel-default-devel kernel-devel linux-glibc- devel The following packages are going to be upgraded: nvidia-computeG02 nvidia-gfxG02-kmp-default x11-video-nvidiaG02 3 packages to upgrade, 6 new. Overall download size: 43.3 MiB. After the operation, additional 64.3 MiB will be used. Continue? [y/n/?] (y): n Why gcc and *-devel for binary driver ? bug/change/something for next opensuse ?! -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 49

[opensuse-factory] Kernel:Tools project
by Jiri Slaby 03 Dec '12

03 Dec '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm thinking about creating Kernel:Tools project to maintain packages like this: sparse trinity mmtests systemtap trace-cmd xfstests ksplice in the future module-init-tools and friends (or maybe not, if it would cause dependency problems in Base:System) Ideas, comments? thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQs8VGAAoJEL0lsQQGtHBJ/g8P/2hJrvpZBl0AENPlAmYMT2pO JcAbdQuofuemRczqZA7XXhY7cXEIbrmvoAyJNfaHV19sMT26Gh3CfiWiy7g4fgn5 xFuZ6Pv8G/oFpEa6i6ZDXDBN1/Ype6Nvuiv/y1iFa3mtPCdrlvr1zfP/3s/qISzU lR9T0vTPiQaH2a8t+QzNS/2QYL9vTbLafb/0pti4DYOvCJ3ZXQ/sgXdUehGBmlBH TxpkhEqgYY1wmO8CW0LUmLaeOpZlVDnBb/F7/3hzIFfKoJ81jdjxLvUalmJIiQWc 7ZIGJDXV6mxksR/lcF4SOyOh/DQ+R9MGLHNs8rKsfyisCkuxboV8LBoqSi3qHDjl XUd4xy1qbcISPaC9cYxlsJl8lwxNqxjekeyh693UCoGhZHUK6kCYt+P/likrqjli ++dJ3hjSCKP5juG/8NrkZ/O3LIieWNbR2m4nY/+7xmLq37yAmp04HFV1Gw5RqDUx C6misGUklk8hR0xk7o2Hfgz/V7GfK/bXZNNagdrSZEfI+z2YHDU2jQGT/bfoBkbe FQdX87SrteasumLFK5CAGmOBQ34h5aFsnuCC0dKdsXhXqH0hNv2odmwSigFSI9h4 glevVmGZ6IfGc2ijHHesxxGcrS/8VxH85UNlRjQ185Eu4f9fRHLa0WDCkVdI8YYc uM9F3qevaFlYNF/vH9n2 =k80B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] kwin crashes on logout
by Esztermann, Ansgar 03 Dec '12

03 Dec '12

Hi, on my machine, kwin reliably crashes upon logout. It looks exactly like https://bugs.kde.org/show_bug.cgi?id=252817, but the workaround given in comment 181 does not resolve the problem (and it should not be needed anyway, since UnredirectFullscreen=false has been the default for some time). Anyone else seeing this? Also, (this might or might not be related), when the screen stays locked overnight, the locking window will not disappear upon unlocking -- it is no longer functional, and clicks seem to go right through, but it is still very visible. A. -- Ansgar Esztermann DV-Systemadministration Max-Planck-Institut für biophysikalische Chemie, Abteilung 105

2 2

[opensuse-factory] please trigger a rebuild of "perf"
by Stefan Seyfried 02 Dec '12

02 Dec '12

It looks like "perf" is built against old perl: susi:~ # perf top perf: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory susi:~ # rpm -qi perf Name : perf Version : 3.5.0 Release : 21.6 Architecture: x86_64 Install Date: Fri Nov 30 18:05:58 2012 Group : Development/Tools/Debuggers Size : 1074883 License : GPL-2.0 Signature : RSA/SHA256, Sun Sep 23 22:15:41 2012, Key ID b88b2fd43dbdc284 Source RPM : perf-3.5.0-21.6.src.rpm Build Date : Sun Sep 23 22:15:23 2012 [...] There is no newer version available in Factory, so it looks like the pearl update was not recognized by OBS. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] factory openSUSE-DVD-x86_64 builds broken ?
by doiggl＠velocitynet.com.au 02 Dec '12

02 Dec '12

Hello, Is something broken in the openSUSE-DVD-x86_64 builds as the last published one was the 20-Nov-2012, where the i586 dvd was 25-Nov-2012 [1]. Questions: Which buildlog holds the build failed details ?, can it be fixed ?, had a look at [2] but could not figure out whats busted. Cheers Glenn [1]http://openqa.opensuse.org/opensuse/factory/iso/ openSUSE-DVD-x86_64-Build0204-Media.iso 20-Nov-2012 04:04 4.4G openSUSE-DVD-i586-Build0217-Media.iso 25-Nov-2012 01:01 4.2G [2] https://build.opensuse.org/package/live_build_log?arch=local&package=_produ… https://build.opensuse.org/package/show?package=_product%3AopenSUSE-dvd5-dv… -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 12

Re: [opensuse-factory] Re: commit typo3-cms-4_5 for openSUSE:Factory
by Thomas Worm 30 Nov '12

30 Nov '12

Hello Marcus, > On Wed, 28 Nov 2012 15:41:02 +0100: Marcus Meissner wrote > > Thomas, > > - Multiple versions of Typo3 CMS? Really? Why not just one? As I wrote in the SR theese three versions are the most used versions in the web. Because of incompatibility of some extensions with the newest version TYPO3 CMS users dom't also use the two older versions of TYPO3 CMS. In general you can say: Users want to use the versions down to the latest LTS version (LTS = Long Term Support). Currently this is TYPO3 CMS v4.5 and they want to use it in parallel on one server (depending on the extensions their site needs and with which version this extensions will work). So the user needs some flexibility in choosing the version branch and I think versions 4.5, 5.6, 4.7 will be quite good. Before the next openSUSE release the TYPO3 community will release a typo3 version 6.0. I currently don't know if it'll be good to deliver also this version, but seems to better wait for openSUSE 13.1 to deliver TYPO3 CMS 6.0. > - As these are high-security-turnaround packasges, will you > maintain them for the 18 months longer openSUSE is under > official support? Of couse I will. I've worked with TYPO3 CMS for years I'll also use it in the future, even in business situations. So I'll permanently watch the TYPO3 releases and I'll pack them soon as an security update. Oliver Hader (TYPO3 CMS v4 Core Leader) thinks about an automation when they release a new fix. This will be possible 'cause my spec files are designed to work properly with only changing version and revision in _service file. So it will be possible that the TYPO3 community automatically adapts the _service file and sends the submit request. > Also given the high amount of security issues, we > would appreciate if you can help the security team > there too with actively notifying us :/ I'll do. Greets, Thomas -- Mit freundlichen Grüßen, Thomas Worm ****************************** Thomas Worm Handel & Dienstleistung Postfach 2207 D-90009 Nürnberg Hausanschrift: Hintere Cramergasse 3 D-90478 Nürnberg ****************************** Telefon: +49 1803 030505000* Telefax: +49 1803 030505050* * 9 Ct./Min. aus dem dt. Festnetz, max 42 Ct./Min aus dem dt. Mobilfunknetz, andere Netze abweichend Allgemeiner Kontakt: info(a)thomas-worm.de Buchhaltung: buchhaltung(a)thomas-worm.de ****************************** Geschäftsführer: Thomas Worm thomas.worm(a)thomas-worm.de Kontoverbindung: Inhaber: Thomas Worm H. u. D. Kontonummer: 38 56 38 Bankleitzahl: 760 606 18 Kreditinstitut: Volksbank-Raiffeisenbank Nürnberg eG Steuernummer: 240-290-21429 USt-ID: DE250745940 ISBN-Verlagsnummer: 3-86749 ****************************** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Tumbleweed, calibre broken
by Patrick Shanahan 30 Nov '12

30 Nov '12

calibre-0.8.63-1.1.1.x86_64 python-2.7.3-3.6.1.x86_64 23:24 Crash: ~ > calibre Traceback (most recent call last): File "/usr/bin/calibre", line 20, in <module> sys.exit(main()) File "/usr/lib64/calibre/calibre/gui2/main.py", line 363, in main app, opts, args, actions = init_qt(args) File "/usr/lib64/calibre/calibre/gui2/main.py", line 50, in init_qt from calibre.gui2.ui import Main File "/usr/lib64/calibre/calibre/gui2/ui.py", line 31, in <module> from calibre.gui2.widgets import ProgressIndicator File "/usr/lib64/calibre/calibre/gui2/widgets.py", line 23, in <module> from calibre.gui2.progress_indicator import ProgressIndicator as _ProgressIndicator File "/usr/lib64/calibre/calibre/gui2/progress_indicator/__init__.py", line 15, in <module> pi_error) RuntimeError: Failed to load the Progress Indicator plugin: the sip module implements API v9.0 to v9.1 but the progress_indicator module requires API v8.1 -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 19

[opensuse-factory] GNOME 3.6 is now in openSUSE:Tumbleweed:GNOME
by Greg KH 30 Nov '12

30 Nov '12

Finally, I have it working on my box, but I would like to get some more testers before I push it out to the main Tumbleweed repo. So, if you want to test the latest Gnome, can you add the repo in the $SUBJECT and do a 'zypper dup' to install everything and let me know how it goes? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Finally MySQL client libs under LGPL
by Marcus Rueckert 30 Nov '12

30 Nov '12

http://www.h-online.com/open/news/item/New-open-source-MariaDB-drivers-for-… http://www.skysql.com/downloads/connectors/c -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] ClamAV running on Tumbleweed
by ellanios82 30 Nov '12

30 Nov '12

Hello List - it seems that the command 'freshclam' is not producing fresh virus signatures, and that updating has ceased : ............... main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven) daily.cld is up to date (version: 15662, sigs: 290624, f-level: 63, builder: ccordes) bytecode.cld is up to date (version: 202, sigs: 40, f-level: 63, builder: neo) ........................ is this to be expected, please ?? ...... best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 30 Nov '12

30 Nov '12

Felix Miata wrote: > Likely the registry, if you can call that doing anything right. > > Ever tried moving a Windows HD to another motherboard and booting it. I > don't think it ever works. ---- It almost always works. What doesn't work is *licensing*. Hardware wise -- no problem. I've taken completely different HD images ( 15K SAS in one case, same image copied to SATA-based SDD's.. came up w/o a hitch). > In recent Linux distros, it usually works, at > least as long as the HD controller is in the same class. --- Same image on windows will boot on SSD/SATA/RAID/SAS.... unless you put in something it doesn't know about... but anything that is standards compatibile, will work for booting.. maybe not optimally, but it will work -- and then Win7 will usually update the driver if better settings are needed. But this is ANOTHER deflection of the question. No one is talking about moving disk images around -- we are talking about installing a system, then ... why does linux/suse need initrd and Windows does not? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 9

[opensuse-factory] Latest Tumbleweed kernel 3.6.7-12.2 source missing
by Vahis 30 Nov '12

30 Nov '12

I've been waiting for the source to appear, kernel itself an other stuff have these versions... Perhaps it got stuck somewhere? Vahis -- http://waxborg.servepics.com openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host openSUSE 12.1 (x86_64) 3.1.1-48-desktop Tumbleweed in VirtualBox openSUSE 12.1 (i586) 3.1.0-1.2-desktop in EeePC 900 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 30 Nov '12

30 Nov '12

Cristian Rodríguez wrote: > El 28/11/12 21:07, Linda Walsh escribió: >> Perhaps someone can explain to me why Windows doesn't >> need a pre-boot ramdisk in order to boot, while Linux does? > > Linux does not need an initrd to boot, distributions do need it to > support a wide variety of booting scenarios and not driving developers > insane in the process. ---- That deflects the question. What wide variety of booting scenarios are supported by linux that are not supported on Windows? Windows runs embedded, headless, on rescue disks, servers, desktops...um...where is the need? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Disable automatic debuginfo packages in Factory
by Peter Trommler 29 Nov '12

29 Nov '12

I need to disable debuginfo packages for package ghc as ghc does not produce DWARF output. Even though I disabled debuginfo packages in my spec file using %global debug_packages %{nil} debuginfo packages are still generated and the package build fails for unpackaged files. What is the correct way of fixing this? Note: Package ghc creates several sub-packages that contain shared libraries and rpm generates debuginfo for those too. Thanks, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Where are sources for pm-utils?
by Andrey Borzenkov 29 Nov '12

29 Nov '12

pm-utils.spec points to http://gitorious.org/opensuse/pm-utils-suse, but last commit there is 8 months old and checkout has no relation to sources in package. How can I submit patches to it? TIA -andrey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 16

[opensuse-factory] Debugging systemd-udevd
by Esztermann, Ansgar 29 Nov '12

29 Nov '12

Hi, I have a bunch of /usr/lib/systemd/systemd-udevd in disk sleep. Any ideas how to debug this? Thanks, A. -- Ansgar Esztermann DV-Systemadministration Max-Planck-Institut für biophysikalische Chemie, Abteilung 105

8 12

[opensuse-factory] Can LibreOffice:Stable and factory be updated to version 3.6x from 3.5x
by doiggl＠velocitynet.com.au 29 Nov '12

29 Nov '12

Hello, Can LibreOffice:Stable and factory [2],[3] be updated to version 3.6x from 3.5x After some searching on obs I found a built LibreOffice 3.6x in [1] Some versions successfully built[4] So can a copy be made to LibreOffice Stable and factory to update packages to a later version. Cheers Glenn [1]https://build.opensuse.org/package/show?package=libreoffice&project=Libre… [2]https://build.opensuse.org/package/show?package=libreoffice&project=Libre… [3]https://build.opensuse.org/package/show?package=libreoffice&project=Libre… [4]:results for x86_64, i586 sources https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… https://build.opensuse.org/package/live_build_log?arch=i586&package=libreof… [56611s] build: extracting built packages... [56643s] libreoffice-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-drivers-mysql-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-drivers-mysql-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-drivers-postgresql-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-drivers-postgresql-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-base-extensions-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-calc-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-calc-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-calc-extensions-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-debugsource-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-draw-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-draw-extensions-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-draw-extensions-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-filters-optional-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-filters-optional-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-gnome-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-gnome-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-icon-themes-prebuilt-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-impress-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-impress-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-impress-extensions-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-impress-extensions-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-kde-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-kde-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-kde4-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-kde4-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-l10n-prebuilt-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-mailmerge-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-math-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-math-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-officebean-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-officebean-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-pyuno-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-pyuno-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-sdk-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-sdk-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-sdk-doc-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-writer-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-writer-debuginfo-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-writer-extensions-3.6.3.2.2-2.3.x86_64.rpm [56643s] libreoffice-3.6.3.2.2-2.3.src.rpm [56643s] _statistics [56643s] libreoffice-appdata.xml [56643s] libreoffice-base-appdata.xml [56643s] libreoffice-calc-appdata.xml [56643s] libreoffice-draw-appdata.xml [56643s] libreoffice-impress-appdata.xml [56643s] libreoffice-writer-appdata.xml [56643s] rpmlint.log and [28427s] build: extracting built packages... [28442s] libreoffice-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-drivers-mysql-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-drivers-mysql-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-drivers-postgresql-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-drivers-postgresql-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-base-extensions-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-calc-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-calc-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-calc-extensions-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-debugsource-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-draw-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-draw-extensions-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-draw-extensions-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-filters-optional-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-filters-optional-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-gnome-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-gnome-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-icon-themes-prebuilt-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-impress-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-impress-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-impress-extensions-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-impress-extensions-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-kde-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-kde-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-kde4-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-kde4-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-l10n-prebuilt-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-mailmerge-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-math-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-math-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-officebean-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-officebean-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-pyuno-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-pyuno-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-sdk-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-sdk-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-sdk-doc-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-writer-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-writer-debuginfo-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-writer-extensions-3.6.3.2.2-2.3.i586.rpm [28442s] libreoffice-3.6.3.2.2-2.3.src.rpm [28442s] _statistics [28442s] libreoffice-appdata.xml [28442s] libreoffice-base-appdata.xml [28442s] libreoffice-calc-appdata.xml [28442s] libreoffice-draw-appdata.xml [28442s] libreoffice-impress-appdata.xml [28442s] libreoffice-writer-appdata.xml [28442s] rpmlint.log -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Python 3 - to split or not to split
by todd rme 29 Nov '12

29 Nov '12

Currently python3 provides a python3-base package, which contains the core interpreter and commonly-used modules, python3, which depends on python3-base and contains less-used modules, and a few packages that contain more specialized modules (like tk or ncurses). The problem is that there are a lot of python3 packages that depend on just one of the modules in the python3 package. This currently requires the package to depend on the whole python3 package, which takes additional space, is more difficult to maintain, and devs keep removing it without checking whether the build actually works afterwards. I think it is important to have these packages depend only on the module that they actually need, to make it more clear what is needed. I see two ways to handle this: 1. Make python3 provide the modules it includes (like python3-hashlib and python3-sqlite). This would not be at all intrusive. 2. Split the modules into separate packages and then have the python3 package depend on them. This could cause problems if there are dependencies between the modules I am not aware of. My thinking is that for python 12.1 and 12.2 we release a patch that adds the provides, while for 12.3 we split the packages. Packagers wouldn't need to care, they would just use the buildrequires or requires for the module they need. What does everyone think of this approach? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] Re: Why is initrd needed...
by Linda Walsh 29 Nov '12

29 Nov '12

Philipp Thomas wrote: > The question is, how do I support a maximum > of different devices *without* requiring the user to compile his own > kernel. > >> For those, you *offer* them the option to rebuild the kernel with >> their needed-boot modules and install that to disk to enable direct >> boot. > > The is free software, so why don't you implement something like that > and then offer it to those that do want it? ---- It would have been trivial if the boot system hadn't been modified to be difficult to maintain, unfriendly, error-prone, boot-resistant, fault-intolerant -- the move to systemd with the now claimed false requirement of moving all to /usr/bin, has made things incredibly unstable and unusable for a development platform without severe repair work. If I were to work from 11.4, I could have it as a replacement for 12.3 timeframe for the stuff in there now, but trying systemd, has caused numerous hangs and having to bring it up by hand -- boot 'S' run bootscripts by hand, then run rcdir by hand. initscripts timed out -- and the system came up -- it was resilient. systemd, 1 thing hangs and the system has you locked out and you can't fix it without rebooting to single user -- if that works. I haven't been able to keep track of all the ways systemd is failing when it tries to come up -- and don't ask me to report bugs, as 1) there are too many and I wouldn't know where to start, and 2) no one is willing to fix the underlying problems, but continue to go down hill -- the move /usr isn't necessary, you said it yourself, but it is continue and causing more damage as it moves forward. I couldn't understand why boot processes no longer worked -- "boot.local" was reserved for calling site-local boot needed processes after boot and before single-user. It is no longer called, but worse, trying to add it, I am told: #chkconfig boot.local on insserv: Note: sysvinit service boot.local is shadowed by systemd local.service, Forwarding request to '/bin/systemctl --root / enable local.service'. Operation failed: No such file or directory insserv: Forward service request to systemctl returned error status : 256 insserv: script name boot.local is not valid, skipped! ==== Great -- boot.local isn't valid? Yet it is the same header and format as the rest. It loaded modules and set the font/tty cuz it doesn't get set right by systemd when one does a warm reboot. Now it doesnt' get called at all, and the drivers not loading caused systemd to hang and the sytem not to come up... wonderful! and this is in SuSE 12.1?? I deliberately enabled the break key in 'boot'.... - so if the system hung during boot, I could press break and interrupt boot and fix it. now.. it's locked out. This is Suse inovation??? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] Chromium browser has returned to it's openSUSE uhome location
by Raymond Wooninck 29 Nov '12

29 Nov '12

Dear openSUSE Users, Last week, I send out the message that it was no longer possible to build Chromium on the openSUSE OBS. This due to issues with ffmpeg, etc. Due to the big help of Ludwig Nussel, we resolved the issues and I can now inform you that we are building Chromium again in it's old location and that we will continue shipping Chromium with openSUSE. A new subpackage was introduced (chromium-ffmpegsumo) that builds a restricted form of the multimedia library required by Chromium. This library supports all the opensource codecs. On Packman we continue to build the chromium-ffmpeg package that contains the same multimedia library, but then with support for more proprietary codecs (equal to the ones supported by the official Chrome browser). If you install the chromium-ffmpeg package, then automatically the new chromium-ffmpegsumo package will be deinstalled. This is the correct behavior. I would like to thank Ludwig again for his help in resolving this matter. As a reminder: The Chromium browser is build in the network:chromium repository and from there updates to Factory and maintenance updates for 12.2/12.1 are shipped. I would like to apologize for the inconvienence this might cause due to swapping the repositories. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] New visual theme for KDE
by Raymond Wooninck 28 Nov '12

28 Nov '12

Hello everyone, this mail is meant to present and discuss the work done by a number of openSUSE contributors for a new visual style for KDE. A number of weeks ago, people in the #opensuse-kde channel started hacking on a new theme for KDE, which should have sported the iconic green of the distro. Alin suggested during a discussion to base the work on the Produkt theme[1]. At that point, the openSUSE contributor shumski (as he's known in IRC) started working on that, also taking a look at the icon set needed for the theme. Due to the KDE team's decision of bringing the 4.10 version of the KDE Platform, Applications and Workspaces for 12.3, shumski also made adjustments to handle the slight differences that took place between 4.9 and 4.10 with regards to theming. A very early draft was published in my blog[2] since I wanted to make the process hopefully open and communicate to the community what those people were doing. The overall impressions were positive and work continued. Recently, this theme was also pushed to KDE:Distro:Factory and then to Factory itself as one of the possible candidate themes for 12.3. I also blogged showing the new look[3]. At this point, we felt necessary to gather the feedback of a larger part of the openSUSE contributors, hence this mail. We're interested in how this can be integrated with the ongoing work of the artwork team and in general taking account of all feedback, good or bad. So, give it a spin (it is in KDE:Distro:Factory or Factory itself, the KDF version is however more up to date) and let us know what you think. At the moment this theme is the default opensuse branding theme for KDE (so you will get it with the *-branding-openSUSE KDE packages). P.S.: Apologies for the list cross-posting, but I wanted to gather every stakeholder in tihs. [1] http://kde-look.org/content/show.php/?content=124213 [2] http://www.dennogumi.org/2012/10/whats-cooking-for-kde-in-opensuse-12-3- theming [3] http://www.dennogumi.org/2012/11/new-theme-for-opensuse-12-3-is-now-in -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 ----------------------------------------- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] glibc 2.17 development version packaged
by Andreas Jaeger 28 Nov '12

28 Nov '12

I've packaged current glibc git version (release planned before Christmas) and like to submit it to Factory now - and update it until the release. Looking at the changes, we receive a lot of bugfixes but I'm not aware of any expected breakage due to it. Coolo, do you want to setup a staging project first or shall I submit via Base:System to Factory directly? The package is building in my project home:a_jaeger:devel-glibc right now. Andreas P.S. The NEWS file lists these changes: * Bugfixes * Port to ARM AArch64 contributed by Linaro. * Support for STT_GNU_IFUNC symbols added for s390 and s390x. Optimized versions of memcpy, memset, and memcmp added for System z10 and zEnterprise z196. Implemented by Andreas Krebbel. * The new function secure_getenv allows secure access to the environment, returning NULL if running in a SUID/SGID process. This function replaces the internal function __secure_getenv. * SystemTap static probes have been added into the dynamic linker. Implemented by Gary Benson. * Optimizations of string functions strstr, strcasestr and memmem. Implemented by Maxim Kuvyrkov. * The minimum Linux kernel version that this version of the GNU C Library can be used with is 2.6.16. * Optimizations of string functions memchr, wcschr, wcscpy, and wcsrchr for powerpc POWER7. Implemented by Will Schmidt. * New configure option --disable-nscd builds the C library such that it never attempts to contact the Name Service Caching Daemon (nscd). New configure option --disable-build-nscd avoids building nscd itself; this is the default if --disable-nscd is used. * The ttyname and ttyname_r functions on Linux now fall back to searching for the tty file descriptor in /dev/pts or /dev if /proc is not available. This allows creation of chroots without the procfs mounted on /proc. * The `crypt' function now fails if passed salt bytes that violate the specification for those values. On Linux, the `crypt' function will consult /proc/sys/crypto/fips_enabled to determine if "FIPS mode" is enabled, and fail on encrypted strings using the MD5 or DES algorithm when the mode is enabled. * The `clock_*' suite of functions (declared in <time.h>) is now available directly in the main C library. Previously it was necessary to link with -lrt to use these functions. This change has the effect that a single-threaded program that uses a function such as `clock_gettime' (and is not linked with -lrt) will no longer implicitly load the pthreads library at runtime and so will not suffer the overheads associated with multi-thread support in other code such as the C++ runtime library. -- Andreas Jaeger aj(a){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,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 16

[opensuse-factory] Re: commit typo3-cms-4_5 for openSUSE:Factory
by Marcus Meissner 28 Nov '12

28 Nov '12

Thomas, - Multiple versions of Typo3 CMS? Really? Why not just one? - As these are high-security-turnaround packasges, will you maintain them for the 18 months longer openSUSE is under official support? Also given the high amount of security issues, we would appreciate if you can help the security team there too with actively notifying us :/ Ciao, Marcus On Wed, Nov 28, 2012 at 02:56:16PM +0100, h_root wrote: > Hello community, > > here is the log from the commit of package typo3-cms-4_5 for openSUSE:Factory checked in at 2012-11-28 14:56:13 > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Comparing /work/SRC/openSUSE:Factory/typo3-cms-4_5 (Old) > and /work/SRC/openSUSE:Factory/.typo3-cms-4_5.new (New) > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Package is "typo3-cms-4_5", Maintainer is "" > > Changes: > -------- > New Changes file: > > --- /dev/null 2012-11-26 11:02:30.307549147 +0100 > +++ /work/SRC/openSUSE:Factory/.typo3-cms-4_5.new/typo3-cms-4_5.changes 2012-11-28 14:56:14.000000000 +0100 > @@ -0,0 +1,92 @@ > +------------------------------------------------------------------- > +Tue Nov 13 09:22:55 UTC 2012 - Thomas.Worm(a)DATEV.de > + > +- Raised to version 4.5.22 > + * Raise submodule pointer (TYPO3 Release Team) > + * Raise version numbers of system extensions (Steffen Ritter) > + * bugfix: imagecopyresized: correct invalid parameters (Stefan Neufeind), t3#26660 > + * Fix TYPO3 logos (Helmut Hummel), t3#42850 > + * Raise submodule pointer (TYPO3 Release Team) > + * bugfix: t3#42812 Most checkboxes (like Extended View) are not working (Michael Spä), t3#42812 > + * Set TYPO3 version to 4.5.22-dev (TYPO3 Release Team) > + * security: Fix SQL injection and XSS in record history (Oliver Hader), t3#42696 > + * security: XSS in TCA Tree (Oliver Hader), t3#42774 > + * security: Fix potential XSS in t3lib_BEfunc::getFuncCheck (Helmut Hummel), t3#42776 > + * Raise submodule pointer (TYPO3 Release Team) > + * bugfix: No sorting in TypoScript Object Browser when browsing (Nicole Cordes), t3#39677 > + * bugfix: Translated non-published page in workspace breaks live workspace (Oliver Hader), t3#42281 > + * bugfix: Illegal string offsets in t3lib_stdgraphic (Wouter Wolters), t3#38024 > + * bugfix: PHP 5.4 warning in CLI context in switch back user (Christian Kuhn), t3#37578 > + * bugfix: t3lib_div: adjust substUrlsInPlainText to also work on URLs at end of sentence (Robert Heel), t3#28248 > + * bugfix: Wrong call to TSFE in FrontendEditing (Steffen Ritter), t3#40733 > + * Fix generation of ext_emconf.php (Wouter Wolters), t3#42444 > + * bugfix: t3lib_div::unlink_tempfile does not always work on Windows (Stanislas Rolland), t3#38699 > + * bugfix: TCEForms.Suggest wizard in IRRE records (Nicole Cordes), t3#27020 > + * Fix case of tests folder (Xavier Perseguers) > + * bugfix: Unit test for saltedpasswords fail (Xavier Perseguers) > + * bugfix: RTE: Link to disabled page doesn't show in FE, link icon does (Stanislas Rolland), t3#36087 > + * bugfix: RTE: Words containing umlauts not added to personal dictionary (Stanislas Rolland), t3#29685 > + * bugfix: Extension Import not working with postgresql and DBAL (Ernesto Baschny), t3#38406 > + * Set TYPO3 version to 4.5.21-dev (TYPO3 Release Team) > + > +------------------------------------------------------------------- > +Wed Oct 24 07:10:29 UTC 2012 - Thomas.Worm(a)DATEV.de > + > +- Raised to version 4.5.20 > + * Raise submodule pointer > + * Update md5 sums for 4.5.20 > + * Update backend sprites according to rebranding > + * Introduce "TYPO3 CMS" in EXT: about (t3#41823) > + * Adjust Logos to new style-guide (t3#41704) > + * Prevent saltedpasswords destroying the password (t3#41828) > + * bugfix: RTE: Paste as plain text doesn't work in > + Safari (Mac only) (t3#35356) > + * bugfix: CE with "All languages" doesn't show with every lang (t3#24087) > + * bugfix: CE with "All languages" isn't shown in Page module (t3#24087) > + * bugfix: Proper cursor icon in access module (t3#33230) > + * bugfix: Fix the additional icon check (t3#41463) > + * bugfix: Fix translation moving in workspaces (t3#33592) > + * bugfix: strftime expects parameter 2 to be long, string given (t3#38717) > + * bugfix: RTE: array_flip warning on array of languages (t3#35147) > + * bugfix: Words with special characters not added to personal > + dictionary (t3#38653) > + * bugfix: htmlArea RTE: Cursor jumps to first letter with Chrome 22 (t3#41411) > + * bugfix: Do not save expand state for root node in TCA tree (t3#31978) > + * bugfix: File upload button is collapsed in Chrome 21 (t3#39659) > + * bugfix: Switch to List module on root page leads to blank page (t3#40781) > + * bugfix: Error handler registration accepts way too much PHP error > + types (t3#31827) > + * bugfix: Tree view in admin panel is broken with PHP 5.4 (t3#41213) > + * bugfix: Error handler callback causes fatal error for parse time > + errors (t3#31834) > + * bugfix: Error messages are not shown in 123 installation process (t3#41158) > + * bugfix: Database creating fails due to not allowed characters (t3#41151) > + * bugfix: Set charset property after cloning t3lib_PageRenderer (t3#27957) > + * bugfix: PHP warning when no language pack is available (t3#40108) > + * Set TYPO3 version to 4.5.20-dev > + * dbal: Update md5 sum for 4.5.20 > + * extbase: Update version number to 1.3.4 > + * extbase, bugfix: (Persistence) Make Typo3QuerySettings exchangeable > + * extbase, bugfix: Declare LocalizationUtility::translateFileReference static > + * fluid: Update version number to 1.3.1 > + * fluid, bugfix: Return empty result in pagination if page does not exist > + * linkvalidator: Raise version number for 4.5.20 > + * linkvalidator, bugfix: Field name 'location' is case insensitive (t3#40486) > + * version: Raise version number for 4.5.20 > + * workspaces: Raise version number for 4.5.20 > + * workspaces, feature: set default grid limit to 30 (t3#26287) > +- Renamed package from typo3-4_5 to typo3-cms-4_5 due to name change of > + software product. > + > +------------------------------------------------------------------- > +Fri Sep 7 13:22:51 UTC 2012 - Thomas.Worm(a)DATEV.de > + > +- Changed installation directory from /usr/share/typo3-4.5 to > + /usr/share/typo3-4_5. > +- Added PHP requirements to spec file. > + > +------------------------------------------------------------------- > +Thu Sep 6 14:08:13 UTC 2012 - Thomas.Worm(a)DATEV.de > + > +- Initial package version 4.5.19 > + > > New: > ---- > _service > typo3-4.5.22.tar.bz2 > typo3-cms-4_5.changes > typo3-cms-4_5.spec > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Other differences: > ------------------ > ++++++ typo3-cms-4_5.spec ++++++ > # > # spec file for package typo3-cms-4_5 > # > # Copyright (c) 2012 SUSE LINUX Products GmbH, Nuernberg, Germany. > # Copyright (c) 2012 Thomas Worm <thomas.worm(a)datev.de> > # > # All modifications and additions to the file contributed by third parties > # remain the property of their copyright owners, unless otherwise agreed > # upon. The license for this file, and modifications and additions to the > # file, is the same license as for the pristine package itself (unless the > # license for the pristine package is not an Open Source License, in which > # case the license is the MIT License). An "Open Source License" is a > # license that conforms to the Open Source Definition (Version 1.9) > # published by the Open Source Initiative. > > # Please submit bugfixes or comments via http://bugs.opensuse.org/ > # > > > Name: typo3-cms-4_5 > Summary: Typo3 CMS v4.5 > License: GPL-2.0+ > Group: Productivity/Networking/Web/Frontends > Version: 4.5.22 > Release: 0 > Source0: typo3-%{version}.tar.bz2 > Url: http://www.typo3.org/ > BuildArch: noarch > BuildRoot: %{_tmppath}/%{name}-%{version}-build > BuildRequires: zlib > Requires: apache2 > Requires: php5 >= 5.2 > Requires: php5-iconv > Requires: php5-mbstring > Requires: php5-mysql > Requires: php5-zlib > Requires: typo3-manager > Recommends: php5-gd > Recommends: GraphicsMagick > Provides: typo3-cms-src > > # Renamed with version 4.5.20 from typo3-4_5 to typo3-cms-4_5 > Obsoletes: typo3-4_5 > > %define underscored_version %(echo -n %{version} | sed 's/\\./_/g') > > %description > Enterprise Content Management System, Version %{version} > > > %prep > %setup -q -n typo3-%{version} -c > > %build > > %check > > %install > mkdir -p %{buildroot}%{_datadir}/typo3-cms-%{underscored_version} > cp -pr typo3-%{version}/* %{buildroot}%{_datadir}/typo3-cms-%{underscored_version}/ > ln -s typo3-cms-%{underscored_version} %{buildroot}%{_datadir}/%{name} > > %files > %defattr(644,root,root,755) > %{_datadir}/typo3-cms-%{underscored_version} > %{_datadir}/%{name} > > %changelog > ++++++ _service ++++++ > <services> > <service name="tar_scm" mode="localonly"> > <param name="scm">git</param> > <param name="url">git://git.typo3.org/TYPO3v4/Core.git</param> > <param name="filename">typo3</param> > <param name="version">4.5.22</param> > <param name="revision">TYPO3_4-5-22</param> > </service> > <service name="recompress" mode="localonly"> > <param name="file">*.tar</param> > <param name="compression">bz2</param> > </service> > <service name="set_version" mode="localonly" /> > </services> > -- > To unsubscribe, e-mail: opensuse-commit+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-commit+help(a)opensuse.org > -- Open Linux Security Engineer Position at SUSE: http://bit.ly/Li4RbS -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Re: [opensuse-xorg] Error or as designed? glu-devel not required by Mesa-devel (like before Mesa-libGLU-devel)
by Joop Boonen 28 Nov '12

28 Nov '12

Hi all, The issue will be fixed in X11:XOrg Mesa per a submit request. It's not needed to use a workaround in the spec file. We only have to wait until the fix has ended up in Factory. Regards, Joop. On 2012-11-27 09:13, Joop Boonen wrote: > Hi all, > > I saw quite a few packages fail to build in games for Factory due to > a missing GL/glu.h this is provided by glu-devel. Since recently up > to > and including openSUSE 12.2 Mesa-devel has a requirement for > Mesa-libGLU-devel. This package doesn't exist any more. This > dependency can now be solved by glu-devel. > > I wonder has the dependency been removed accidentally or is it > planned. If it's not planned it no use to fix involved packages. > If it's planned the packages can be fixed by adding this to the spec > file: > > %if 0%{?suse_version} > 1220 > BuildRequires: glu-devel > %endif > > Regards, > > Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] FYI: glibc causes grep test-fwrite test failure
by Andreas Jaeger 28 Nov '12

28 Nov '12

At least grep failed the gnulib test-fwrite test - and this is a regression introduced by glibc. If any of your packages also fails due to test-fwrite of gnulib, ignore the failure for now. I've reported upstream, a fix is currently under review and new glibc will come once upstream fixed this. Details at: http://sourceware.org/ml/libc-alpha/2012-11/msg00701.html Andreas -- Andreas Jaeger aj(a){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,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] How do you allow connections from 127.0.0.1 to apache2
by doiggl＠velocitynet.com.au 28 Nov '12

28 Nov '12

Hello How do you allow connections from 127.0.0.1 to apache2 I get this error [1]. I have these rpms installed [2]and using factory. What else needs to be altered ? Firewall settings ? Its just using defaults. Thanks Glenn [1] Failed to Connect The connection was refused when attempting to contact 127.0.0.1. Though the site seems valid, the browser was unable to establish a connection.Could the site be temporarily unavailable? Try again later.Are you unable to browse other sites? Check the computer's network connection.Is your computer or network protected by a firewall or proxy? Incorrect settings can interfere with Web browsing. [2] # rpm -qa | grep -i apache2| sort apache2-2.2.22-8.4.x86_64 apache2-example-pages-2.2.22-8.4.x86_64 apache2-mod_php5-5.3.17-2.3.x86_64 apache2-prefork-2.2.22-8.4.x86_64 apache2-utils-2.2.22-8.4.x86_64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] udev rules still in /lib/udev
by Alin M Elena 28 Nov '12

28 Nov '12

Hi, After some angst and one night without internet because rules being in the wrong folder /lib/udev/rules.d/ I have decided to add a blame list of packages that still install them in /lib/udev rather that /usr/lib/udev here are mine... rpm -qf /lib/udev/rules.d/*.rules | sort -u hdparm-9.43-1.1.x86_64 libgphoto2-6-2.5.0-5.1.x86_64 libgpod-tools-0.8.2-10.18.x86_64 lirc-0.9.0-3.6.x86_64 NetworkManager-0.9.6.4-2.1.x86_64 please add yours, ModemManager is already fixed... regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

4 6

[opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

Hi, for reason independent on me I did a clean install of factory... net install last iso of 25th of November... and then I have updated all nicely to factory... All to have the surprise of having my usb mobile broadband (snail version) not working,,, from the exterior the blue led of the dongle is blinking... meaning ready for business... but from inside the box the thing does not even exist.. here it is some info dmesg part [ 526.208107] usb 2-4: new high-speed USB device number 10 using ehci_hcd [ 526.325249] usb 2-4: New USB device found, idVendor=12d1, idProduct=1446 [ 526.325255] usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 526.325258] usb 2-4: Product: HUAWEI Mobile [ 526.325261] usb 2-4: Manufacturer: HUAWEI Technology [ 526.327084] scsi20 : usb-storage 2-4:1.0 [ 526.327252] scsi21 : usb-storage 2-4:1.1 [ 527.000571] usb 2-4: USB disconnect, device number 10 [ 535.998075] usb 2-4: new high-speed USB device number 11 using ehci_hcd [ 536.115225] usb 2-4: New USB device found, idVendor=12d1, idProduct=1446 [ 536.115237] usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 [ 536.115244] usb 2-4: Product: HUAWEI Mobile [ 536.115250] usb 2-4: Manufacturer: HUAWEI Technology [ 536.118558] scsi22 : usb-storage 2-4:1.0 [ 536.119476] scsi23 : usb-storage 2-4:1.1 [ 536.776596] usb 2-4: USB disconnect, device number 11 [ 541.023062] usb 2-4: new high-speed USB device number 12 using ehci_hcd [ 541.140092] usb 2-4: New USB device found, idVendor=12d1, idProduct=1436 [ 541.140098] usb 2-4: New USB device strings: Mfr=4, Product=3, SerialNumber=0 [ 541.140102] usb 2-4: Product: HUAWEI Mobile [ 541.140105] usb 2-4: Manufacturer: HUAWEI Technology [ 541.143027] option 2-4:1.0: GSM modem (1-port) converter detected [ 541.143245] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0 [ 541.145156] cdc_ether 2-4:1.1 wwan0: register 'cdc_ether' at usb-0000:00:06.1-4, Mobile Broadband Network Device, 02:50:f3:00:00:00 [ 541.145306] option 2-4:1.3: GSM modem (1-port) converter detected [ 541.145378] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1 [ 541.145724] option 2-4:1.4: GSM modem (1-port) converter detected [ 541.145874] usb 2-4: GSM modem (1-port) converter now attached to ttyUSB2 [ 541.146667] scsi28 : usb-storage 2-4:1.5 [ 541.147142] scsi29 : usb-storage 2-4:1.6 [ 542.152286] scsi 28:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 542.152601] scsi 29:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 [ 542.153469] sd 29:0:0:0: Attached scsi generic sg3 type 0 [ 542.156198] sd 29:0:0:0: [sdc] Attached SCSI removable disk [ 542.157049] sr1: scsi-1 drive [ 542.157154] sr 28:0:0:0: Attached scsi CD-ROM sr1 [ 542.157242] sr 28:0:0:0: Attached scsi generic sg4 type 5 network manager part... nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabled enabled disabled using the mm-test.py wget http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm- test.py ./mm-test.py No modems found zypper se -is modem Retrieving repository 'localRPMs' metadata ............................................................................................................. [done] Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------+---------+--------------------------+--------+--------------------------------------------------------- i | ModemManager | package | 0.6.0.0-1.3 | x86_64 | openSUSE-12.3-Oss i | libQtModemManager0 | package | 0.5.0git.1329528114-88.1 | x86_64 | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory) [root@abbaton:/home/alin]: zypper se -is ppp Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------+---------+-------------+--------+------------------ i | ppp | package | 2.4.5-14.4 | x86_64 | openSUSE-12.3-Oss i | smpppd | package | 1.60.56-4.5 | x86_64 | openSUSE-12.3-Oss Any help is much appreciated. Alin I have also observed that modem-manager still installs his udev rules in /lib/udev/rules.d rather than /usr/lib/udev/rules.d/ -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

4 5

[opensuse-factory] KDE rebuilds in Tumbleweed
by Achim Gratz 27 Nov '12

27 Nov '12

Now that KDE is back in Tumbleweed it seems to rebuild almost daily. Even if that was intended, why does it also rebuild the noarch packages (all the artwork, icons and stuff) that surely never change? And if OBS absolutely must rebuild them, should they be packaged and delivered each time, with presumably the same content (the file sizes always differ by a few bytes, which seems to be logging information) and just a different label? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

this is the log from 12.2 and working modem-manager[23760]: <info> [1354041601.438126] [main.c:167] main(): ModemManager (version 0.5.2.0) starting... modem-manager[23760]: <info> [1354041601.440798] [mm-manager.c:120] load_plugin(): Loaded plugin Novatel modem-manager[23760]: <info> [1354041601.441017] [mm-manager.c:120] load_plugin(): Loaded plugin Option modem-manager[23760]: <info> [1354041601.441179] [mm-manager.c:120] load_plugin(): Loaded plugin Gobi modem-manager[23760]: <info> [1354041601.441338] [mm-manager.c:120] load_plugin(): Loaded plugin SimTech modem-manager[23760]: <info> [1354041601.441495] [mm-manager.c:120] load_plugin(): Loaded plugin Generic modem-manager[23760]: <info> [1354041601.441653] [mm-manager.c:120] load_plugin(): Loaded plugin Longcheer modem-manager[23760]: <info> [1354041601.441817] [mm-manager.c:120] load_plugin(): Loaded plugin Nokia modem-manager[23760]: <info> [1354041601.441978] [mm-manager.c:120] load_plugin(): Loaded plugin Samsung modem-manager[23760]: <info> [1354041601.442139] [mm-manager.c:120] load_plugin(): Loaded plugin Wavecom modem-manager[23760]: <info> [1354041601.442305] [mm-manager.c:120] load_plugin(): Loaded plugin ZTE modem-manager[23760]: <info> [1354041601.442467] [mm-manager.c:120] load_plugin(): Loaded plugin Linktop modem-manager[23760]: <info> [1354041601.442633] [mm-manager.c:120] load_plugin(): Loaded plugin AnyData modem-manager[23760]: <info> [1354041601.442795] [mm-manager.c:120] load_plugin(): Loaded plugin X22X modem-manager[23760]: <info> [1354041601.442961] [mm-manager.c:120] load_plugin(): Loaded plugin Ericsson MBM modem-manager[23760]: <info> [1354041601.443125] [mm-manager.c:120] load_plugin(): Loaded plugin MotoC modem-manager[23760]: <info> [1354041601.443299] [mm-manager.c:120] load_plugin(): Loaded plugin Option High-Speed modem-manager[23760]: <info> [1354041601.443470] [mm-manager.c:120] load_plugin(): Loaded plugin Huawei modem-manager[23760]: <info> [1354041601.443641] [mm-manager.c:120] load_plugin(): Loaded plugin Sierra modem-manager[23760]: <debug> [1354041601.445640] [mm-manager.c:809] device_added(): (tty/ttyS0): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.445792] [mm-manager.c:809] device_added(): (tty/ttyS1): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.445925] [mm-manager.c:809] device_added(): (tty/ttyS2): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446047] [mm-manager.c:809] device_added(): (tty/ttyS3): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446168] [mm-manager.c:809] device_added(): (tty/ttyS4): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446289] [mm-manager.c:809] device_added(): (tty/ttyS5): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.446412] [mm-manager.c:809] device_added(): (tty/ttyS6): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041601.447003] [mm-manager.c:809] device_added(): (tty/ttyS7): port's parent platform driver is not whitelisted modem-manager[23760]: <debug> [1354041637.441873] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB2) deferring support check modem-manager[23760]: <debug> [1354041637.445329] [mm-manager.c:491] try_supports_port(): (Huawei): (ttyUSB1) deferring support check modem-manager[23760]: <info> [1354041637.462561] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB0) opening serial port... modem-manager[23760]: <debug> [1354041637.463613] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 1 (open) modem-manager[23760]: <debug> [1354041637.463675] [mm-plugin-base.c:859] try_open(): (ttyUSB0): probe requested by plugin 'Huawei' modem-manager[23760]: <debug> [1354041637.599075] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GCAP<CR>' modem-manager[23760]: <debug> [1354041638.919454] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'AT+GCAP' modem-manager[23760]: <debug> [1354041638.920492] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041638.920938] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CME ERROR: SIM busy<CR><LF>' modem-manager[23760]: <debug> [1354041638.921017] [mm-serial-parsers.c:438] mm_serial_parser_v1_parse(): Got failure code 14: SIM busy modem-manager[23760]: <debug> [1354041638.921086] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GCAP<CR>' modem-manager[23760]: <debug> [1354041639.621239] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'AT+GCAP' modem-manager[23760]: <debug> [1354041639.622115] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041639.623237] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+GCAP: +CGSM,+DS, +ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.623399] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close) modem-manager[23760]: <info> [1354041639.623418] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port... modem-manager[23760]: <info> [1354041639.624477] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB0) serial port closed modem-manager[23760]: <debug> [1354041639.629922] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB0) type primary claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041639.630077] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB0) opening serial port... modem-manager[23760]: <debug> [1354041639.631124] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 1 (open) modem-manager[23760]: <debug> [1354041639.631198] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 2 (open) modem-manager[23760]: <debug> [1354041639.631221] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 3 (open) modem-manager[23760]: <info> [1354041639.631350] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB0 modem-manager[23760]: <debug> [1354041639.631392] [mm-manager.c:317] add_modem(): Added modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631411] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631524] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041639.631873] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATE0<CR>' modem-manager[23760]: <debug> [1354041639.642239] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- 'ATE' modem-manager[23760]: <debug> [1354041639.642491] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '0' modem-manager[23760]: <debug> [1354041639.650498] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR>' modem-manager[23760]: <debug> [1354041639.650857] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.650921] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMI<CR>' modem-manager[23760]: <debug> [1354041639.968379] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>huawei<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041639.968928] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMM<CR>' modem-manager[23760]: <debug> [1354041640.088869] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>E1752<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.089727] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GMR<CR>' modem-manager[23760]: <debug> [1354041640.132750] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>11.126.08.01.00<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.133270] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMI<CR>' modem-manager[23760]: <debug> [1354041640.174134] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>huawei<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.174286] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMM<CR>' modem-manager[23760]: <debug> [1354041640.241243] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>E1752<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.241312] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGMR<CR>' modem-manager[23760]: <debug> [1354041640.288238] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>11.126.08.01.00<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.288728] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATI<CR>' modem-manager[23760]: <debug> [1354041640.313902] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>Manufacturer: huawei<CR><LF>Model: E1752<CR><LF>Revision: 11.126.08.01.00<CR><LF>IMEI: 353220040853787<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.313988] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATI1<CR>' modem-manager[23760]: <debug> [1354041640.346151] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>Manufacturer: huawei<CR><LF>Model: E1752<CR><LF>Revision: 11.126.08.01.00<CR><LF>IMEI: 353220040853787<CR><LF>+GCAP: +CGSM,+DS,+ES<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.346230] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+GSN<CR>' modem-manager[23760]: <debug> [1354041640.390385] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>353220040853787<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.390525] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CGSN<CR>' modem-manager[23760]: <debug> [1354041640.441748] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>353220040853787<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.442241] [mm-manager.c:457] supports_defer_timeout(): (ttyUSB2): re-checking support... modem-manager[23760]: <info> [1354041640.443073] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB2) opening serial port... modem-manager[23760]: <debug> [1354041640.444879] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB2) device open count is 1 (open) modem-manager[23760]: <debug> [1354041640.445023] [mm-modem-helpers.c:920] mm_create_device_identifier(): Device ID source '000012d100001436Manufacturer:huaweiModel:E1752Revision:11.126.08.01.00IMEI:353220040853787+GCAP: +CGSM,+DS,+ES35322004085378711.126.08.01.00E1752huawei' modem-manager[23760]: <debug> [1354041640.445045] [mm-modem-helpers.c:921] mm_create_device_identifier(): Device ID '9e5fcfd87c7028286423c289c6776ef5f143db5e' modem-manager[23760]: <debug> [1354041640.445085] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 2 (close) modem-manager[23760]: <debug> [1354041640.445111] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'ATE0<CR>' modem-manager[23760]: <debug> [1354041640.451761] [mm-manager.c:457] supports_defer_timeout(): (ttyUSB1): re-checking support... modem-manager[23760]: <info> [1354041640.452261] [mm-serial-port.c:741] mm_serial_port_open(): (ttyUSB1) opening serial port... modem-manager[23760]: <debug> [1354041640.453755] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB1) device open count is 1 (open) modem-manager[23760]: <debug> [1354041640.479242] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.480088] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 1 (close) modem-manager[23760]: <debug> [1354041640.480749] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CMEE=1<CR>' modem-manager[23760]: <debug> [1354041640.543745] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.544286] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CPIN?<CR>' modem-manager[23760]: <debug> [1354041640.600866] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041640.601016] [mm-serial-port.c:810] mm_serial_port_open(): (ttyUSB0) device open count is 2 (open) modem-manager[23760]: <debug> [1354041640.601041] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 1 (close) modem-manager[23760]: <debug> [1354041640.601070] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): --> 'AT+CRSM=176,12258,0,0,10<CR>' modem-manager[23760]: <debug> [1354041641.046263] [mm-at-serial-port.c:333] debug_log(): (ttyUSB0): <-- '<CR><LF>+CRSM: 144,0,"985303120081004340F5"<CR><LF><CR><LF>OK<CR><LF>' modem-manager[23760]: <debug> [1354041641.047080] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB0) device open count is 0 (close) modem-manager[23760]: <info> [1354041641.047125] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB0) closing serial port... modem-manager[23760]: <info> [1354041641.047986] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB0) serial port closed modem-manager[23760]: <debug> [1354041641.048066] [mm-generic-gsm.c:507] get_iccid_done(): SIM ID source '8935302100180034045' modem-manager[23760]: <debug> [1354041641.048082] [mm-generic-gsm.c:508] get_iccid_done(): SIM ID '00f77f4bb96a6dfb449b93a04e9b4d336174e8e5' modem-manager[23760]: <debug> [1354041641.048228] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041642.323343] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^SIMST:1<CR><LF>' modem-manager[23760]: <debug> [1354041642.324389] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^SRVST:2<CR><LF>' modem-manager[23760]: <debug> [1354041643.671363] [mm-at-serial-port.c:333] debug_log(): (ttyUSB2): <-- '<CR><LF>^RSSI:14<CR><LF>' modem-manager[23760]: <debug> [1354041643.671476] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB2) device open count is 0 (close) modem-manager[23760]: <info> [1354041643.671497] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB2) closing serial port... modem-manager[23760]: <info> [1354041643.672492] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB2) serial port closed modem-manager[23760]: <debug> [1354041643.673074] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB2) type secondary claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041643.673306] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB2 modem-manager[23760]: <debug> [1354041643.673367] [mm-manager.c:243] check_export_modem(): (tty/ttyUSB1): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041648.450016] [mm-serial-port.c:844] mm_serial_port_close(): (ttyUSB1) device open count is 0 (close) modem-manager[23760]: <info> [1354041648.450065] [mm-serial-port.c:859] mm_serial_port_close(): (ttyUSB1) closing serial port... modem-manager[23760]: <info> [1354041648.451099] [mm-serial-port.c:880] mm_serial_port_close(): (ttyUSB1) serial port closed modem-manager[23760]: <debug> [1354041648.451599] [mm-modem-base.c:155] mm_modem_base_add_port(): (ttyUSB1) type ignored claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <info> [1354041648.451837] [mm-manager.c:564] do_grab_port(): (Huawei): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 claimed port ttyUSB1 modem-manager[23760]: <debug> [1354041648.451954] [mm-manager.c:265] check_export_modem(): Exported modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 as /org/freedesktop/ModemManager/Modems/0 modem-manager[23760]: <debug> [1354041648.452005] [mm-manager.c:278] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): VID 0x12D1 PID 0x1436 (usb) modem-manager[23760]: <debug> [1354041648.452019] [mm-manager.c:279] check_export_modem(): (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 modem-manager[23760]: <info> [1354041665.939095] [mm-manager.c:862] device_removed(): (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041665.939178] [mm-modem-base.c:185] mm_modem_base_remove_port(): (ttyUSB0) type primary removed from /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 modem-manager[23760]: <debug> [1354041665.939217] [mm-manager.c:204] remove_modem(): Removed modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.3 Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] modem-manager and its daemons part II
by Alin M Elena 27 Nov '12

27 Nov '12

> Please verify udev has created the device nodes. l /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Nov 27 17:17 /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 1 Nov 27 17:17 /dev/ttyUSB1 crw-rw---- 1 root dialout 188, 2 Nov 27 17:17 /dev/ttyUSB2 i this is what you mean by devices. Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Error or as designed? glu-devel not required by Mesa-devel (like before Mesa-libGLU-devel)
by Joop Boonen 27 Nov '12

27 Nov '12

Hi all, I saw quite a few packages fail to build in games for Factory due to a missing GL/glu.h this is provided by glu-devel. Since recently up to and including openSUSE 12.2 Mesa-devel has a requirement for Mesa-libGLU-devel. This package doesn't exist any more. This dependency can now be solved by glu-devel. I wonder has the dependency been removed accidentally or is it planned. If it's not planned it no use to fix involved packages. If it's planned the packages can be fixed by adding this to the spec file: %if 0%{?suse_version} > 1220 BuildRequires: glu-devel %endif Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] 12.3 samba trying to use port 1024?
by Linda Walsh 26 Nov '12

26 Nov '12

i was trying to fix some problems in network connectivity, so I'm not sure 100% if the problem was in samba -- but it appeared to be trying to make use of port 1024 for some ep or com like function (didn't get exact message -- was another boot time error that I saw.. not sure if it was samba trying to use a a port that's already allocated for local use, or some other problem. Only think I saw in the source was 1024-65535 being for user-level usage (vs. root), but didn't see anything that should have been using it. Is there anything in suse's configs that's trying to make use of this port? Is it configurable somewhere? tnx... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] unknown type name 'size_t' in /usr/include/scsi/sg.h
by Ilya Chernykh 26 Nov '12

26 Nov '12

Under latest Factory rebuild: [ 136s] /usr/include/scsi/sg.h:38:3: error: unknown type name 'size_t' I do not know to what package this file belongs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Re: Why is initrd needed - to support moving bin files from root->/usr? That requires extra patches by Suse.
by Linda Walsh 26 Nov '12

26 Nov '12

Brian K. White wrote: > > Custom built kernels are probably a support nightmare. ----- How is a custom built kernel any more of a support nightmare than a custom built initrd? At least with the kernel, you can list out the config and easily see what went into it. Is there a proc interface for listing out the contents of initrd? I call phooey on this FUD... the initrd is more customized than any kernel. The kernel has a common interface for customization across all distros -- but show me the common initrd interface. The initrd interface is worse in this way and every way mentioned so far. > > I don't fault them for using initrd, but I do think it sucks that they > deliberately make it essentially required when it doesn't have to be. ---- At one point, it was an easy way out -- because it JUST contained the modules you needed to build -- it wasn't a custom boot disk. > > Using an initrd is a downgrade in some cases. _Requiring_ it is an even > bigger downgrade in general, as it's a loss in flexibility and in some > cases a loss in efficiency. > > I don't think xfs is a reasonable default fs for a linux distro like > opensuse either. There are special linux distros that target security > and reliability above all else, including at the expense of performance. > I don't think suse was ever one of those. It was a general purpose OS > that now targets desktops. xfs is not the best fs for desktops nor even > for all servers. ---- It is the best for servers, and it was part of a C2-evaluated security distro (Trusted Irix) before linux existed. But it was developed to meet the needs of the media creation industry who needed to write real-time media steams -- no other file system could do that at the time, and no other file system today has it's benefits in handling media files. Where it is weak is in handling tiny bits of info -- and then -- only really on deletion. It tries to be efficient -- to the point that it will store data and/or access information in the inode if the amount is very small you have large enough inodes. But there are some features in NON-unix standard FS's that have potential for being better than XFS -- ZFS and BTRFS... maybe... have to see where they end up.. right now, ZFS is slower due to implementation and BTRFS still is in early development. > > But opensuse isn't all linux itself, it's just opensuse. Every > distribution takes pieces from the world of available code and packages > them up in different ways that serve different needs. > > The targets opensuse serves has shifted from those suse used to serve > very well that's all. It's not a crime it just sucks for us. --- Not a crime, BUT it was a distro that was general purpose and one of the best... there is no other distro that has what Suse had -- or even what suse could have again if it really turned around. My last boss bet me suse would be out of business within a year -- that was back in 2001. I never take bets - but at the time, it was a safe bet, as I knew it had at least 3-6 years more, minimum. now...If the distro doesn't change directions -- it will be gone or a bit player in 3-5 and I don't see another similar one on the horizon with the same stability that OSuse had. > > I don't like that opensuse has veered off from the kind of distro it > used to be, because I was well served by what it used to be and I am not > well served by what it is now, and it means I now have to do a bunch of > work. > > But some of these things you're arguing are not really just. > They should be allowed for but I don't think they are reasonable to > expect as defaults. ---- I'm arguing for not *disallowing* them as default choices. People are saying there is no choice but to do "X", I am pointing out alternatives at every step and every point that belies that fact -- not that I am trying to convert everyone to my choices -- but I will fight to show my choices as solving all of their problems as long as they continue to hold up their problems as unsolvable and needing to kill off my choice as a consequence. What's happening is that they want to make sure there are no alternatives. That's really what is going on. Then they can more easily control the end user just as MS controls most of the afterboot env after win7 and and felt comfortable wiping out the desktop in win8. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] How to reliably check for SUSE distribution?
by Andrey Borzenkov 25 Nov '12

25 Nov '12

DKMS currently is using /etc/SuSEconfig to detect whether it is running on SUSE. As I understand SuSEconfig is scheduled to be removed entirely. What is the proper way to detect distribution? I would use /etc/SuSE-release, but may be there were reasons to use SuSEconfig in the first place. DKMS needs to know distribution to decide e.g. whether it needs to do kernel source preparation or it can skip it. TIA -andrey -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6