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