December 2011 - 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

[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] KDE menus and gitorious
by Cristian Morales Vega 06 Nov '12

06 Nov '12

I created a merge request for desktop-data three weeks ago. It's just a minor patch that doesn't really fix anything but a warning from kbuildsycoca4. I'm not sure about how Gitorious works, maintainers are supposed to notice the "1" in the merge requests section or they receive an email notifying it? And since I'm on it. Since I updated my 11.3 system to KDE to 4.5 the "inline" part of the menu is not honored... Expected behavior? Known problem? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 6

[opensuse-factory] [RFC DRAFT] Phasing out sysvinit
by Cristian Rodríguez 08 Feb '12

08 Feb '12

Hi: Supporting 2 different init systems comes with a large increase of possible usecases and scenarios that are very difficult to support correctly, specially in the long term. This RFC proposes steps to permanently phase out sysvinit from future openSUSE releases. Phase 0 - Fix all *currently* outstanding bugs of systemd if any, note that this step only deals with problems in systemd itself, not in service files installed by other packages, udev, kernel, networkmanager or whatever other thing. - Determine which services currently lack of native systemd units. - Add an rpmlint error with moderate badness for the start,complaining about the lack of unit files. Phase 1: - Delete sysvinit scripts that deal purely with hardware things,like only loading kernel modules, making udev to handle them or simple dropping a foobar.conf with the needed modules in /usr/lib/modules-load.d/ whichever is more adequate or doable. - Add missing systemd units for the packages where rpmlint warns. - Add rpmlint with badness complaining about logrotate, or other shell scripts calling files in /etc/init.d ... Phase 3: - Turn rpmlint warnings about the lack of systemd units on packages including traditional sysvinit scripts a fatal error. - fix logrotate or shell scripts that are calling sysvint scripts and make the rpmlint warning a fatal error. - tell RPM to %exclude files in /etc/init.d from packages, do not forc packagers to exclude these files themselves. - make all macros relevant to traditional init scripts a no-op, do not force packagers to remove those lines or add extra hacks to the already horrendous hackery in spec files. - test, test, test. - remove sysvinit and all the relevant bootloader options and from the documentation. -- ????? -- Profit. :-) This is just a quick brain dump, I am certainly missing something else. Have fun. Cristian. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

53 224

[opensuse-factory] Lilypond won't work with guile 2.0, What can I do to prevent it being dropped? Do we really want guile 2.0 yet?
by Dave Plater 31 Jan '12

31 Jan '12

OpenSUSE has jumped way ahead of all the other major distributions by pushing guile-2.0 to factory, this may cause problems for packages such as gnucash if it uses guile to the extent that lilypond does. Lilypond uses guile extensively and are working on porting lily to guile 2.0 but this is their timeline quoted from one of my emails from Graham Percival to the devel list please note that lilypond 2.16.0 may not be released before openSUSE 12.1 and I'm working on 2.14.2 atm the current release : There is absolutely zero chance of lilypond 2.16 using guile 2.0. There is maybe a 10% chance that any version of lilypond will support guile 2.0 in 2011. Total guesswork for future predictions: 50% chance of supporting guile 2.0 before July 2012, 80% chance of support guile 2.0 before the end of 2012. What that means for opensuse is up to you. If you particularly want guile 2.0, then by all means jump in; the more people working on it, the higher the chances are that it'll get done sooner. But based on the amount of work that currently goes into guile 2.0, those are my estimates. Cheers, - Graham and I think this is also relevant, another lily developers reply from the same message: Given that the upcoming ubuntu oneiric apparently does not include guile 2.0, I also don't see a switch to guile 2.0 in the near future. I suppose that we should ask the ubuntu people when they'll finally package guile 2.0. Cheers, Reinhold I've looked at parallel installation of guile 1.8.8 (we jumped from 1.8.7 to 2.0.1) and it doesn't look easy otherwise I would have submitted guile1 but I'm still working on it although I'm not that familiar with the autoconf/automake build system at this level. What this means for openSUSE, lilypond is a very popular musical notation type setting program, the developers pride themselves in the accuracy of the notation positions, it is also used, for musical notation by rosegarden, a popular music and midi composition program. Both of these applications have no substitutes in the open source world and only have costly equivalents in the ms windows world, neither being available for ms windows although there are requests to port for both this won't happen in the immediate future. Rosegarden can work without lilypond as it is only bound to lilyponds notation fonts but the sheet music it exports will be useless so it will lose major functionality. Lilypond won't even be able to be installed via tarball on openSUSE 12.1 without the user removing guile 2.0 completely and installing guile 1.8 via tarball, as a result these users of lilypond and rosegarden will drop openSUSE. I started as a community maintainer by saving both lilypond and rosegarden from being dropped, I'm now very active in maintaining multimedia apps and libs and losing these programs will mean losing a large section of professionals in music related professions that have migrated from the windows world including the people that I've converted from ms windows just by showing them rosegarden although ms's change from xp to vista also helped. For the other packages that directly depend on guile : guile aisleriot gnucash autogen and slib, the change back to guile-1.8.8 won't AFAICS have any negative effects, all of these packages simply have patches for guile 2.0 and after looking at the patches, will most probably build with the patches still in place. I don't know what the situation is with guile users but it is an app for use by apps and not a direct users app. Guile-1.8.7 builds for factory, guile-1.8.7 doesn't build for 11.4. What are we going to do? Drop lilypond, I will keep it alive in home:plater:lilypond with guile-1.8.8 to replace guile-2.0.2 or revert to guile-1.8.8 in line with the other linux distributions? Thanks Dave Plater -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 5

[opensuse-factory] proper way to link packages in openSUSE:Tumbleweed
by Greg KH 12 Jan '12

12 Jan '12

Hi Adrian, We talked at brainshare about the "correct" way to link packages in Tumbleweed, and unfortunatly, I forgot one of the steps as I can't get it to work now. Here's what I remember: - look up the xsrcmd5 from the "root" package. For example, in the X11:xfce midori package I would do something like: osc api /source/X11:xfce/midori | grep linkinfo | pick out xsrcmd5 (where 'pick out' is a regex) - then run 'osc setlinkrev' with that md5 in the Tumbleweed repo. It's that last step that I can't seem to get correct, what is the exact command for it? I tried something like: $ osc setlinkrev -r bc383278250a5673d3799c2b31c9e6ef openSUSE:Tumbleweed filesystem setting revision to bc383278250a5673d3799c2b31c9e6ef for package filesystem Server returned an error: HTTP Error 400: Base System/filesystem/bc383278250a5673d3799c2b31c9e6ef not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Base:System/filesystem/bc383278250a5673d3799c2b31c9e6ef: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Any hints would be appreciated. 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

3 7

[opensuse-factory] [12.1] massive data loss in /var/tmp/
by Melchior FRANZ 09 Jan '12

09 Jan '12

Apparently, 12.1 has added /var/tmp/ to TMP_DIRS_TO_CLEAR in /etc/sysconfig/cron. I was quite surprised when I found out today that I've lost a few GB of data, which used to be safe there. Needless to say that I'm not pleased. No backups, because it wasn't *that* important, but I find such changes without warning suboptimal, to put it politely. m. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

44 244

[opensuse-factory] Planned submission of glib 2.31 and resulting package failures
by Dimstar / Dominique Leuenberger 05 Jan '12

05 Jan '12

Hello everybody! This is as a heads up for all of you having packages depending (directly or indirectly) on glib. We're like to start pushing parts of GNOME 3.3.2 to Factory in the not too distant future. A 'critical' part will be glib, which gets updated to version 2.31, and, in turn, get's very strict on its header inclusion. With the exception of very few headers (see end), only glib.h can be #include'd now; all the others trigger an error: error: "Only <glib.h> can be included directly." Generally, the code needs fixing and changing the includes to only contain #include <glib.h> Most of the other glib headers are indirectly implicit included. So far I know of those that still need to be manually included: glib/gstdio.h glib/gi18n.h glib/i18n-lib.h I'll be trying to setup a repo like coolo does for the various fallouts he produces (libtool/automake) and try to get a bunch of packages fixed beforehand (I fixed most of GNOME:Factory/GNOME:Apps by now), but of course I'll gladly accept any help of other volunteers checking their packages. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Proposal for 12.2, move all binaries under /usr
by Greg KH 04 Jan '12

04 Jan '12

Hi all, As a proposal for 12.2, I would like to implement the move of all binaries to /usr/ like is being done at the moment in Fedora. Here's the details as to why this is a good thing to do, and what is involved in it: https://fedoraproject.org/wiki/Features/UsrMove The first packages implementing this have already started to land in Fedora's version of Factory. Before you get worried, there will be symlinks back to /bin and /sbin for those scripts expecting things to be in those locations. We can use the Fedora patches for almost all of this, they are all published at: http://harald.fedorapeople.org/downloads/usrmove/ and a number of upstream projects are already moving their releases over to this as well, which will make things easier. If there are no major objections, I'll start working on Base:system in December. thanks, greg k-h p.s. Please, before you respond, read the link above and all of the discussion about it and don't repeat the same questions that the link already answers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

27 57

[opensuse-factory] RFC: Integrating Plymouth
by Cristian Rodríguez 03 Jan '12

03 Jan '12

Hi: Today I looked into Plymouth and got it somehow working quickly, I want to propose the inclusion of this replacement of bootsplash, under the following constrains: - It will be only supported when running in conjunction with systemd. (it has native integration with it) - Users are free to package or create their own themes, but we provide only ONE theme, consistent "looking" between desktops whatever the openSUSE artwork theme decides. Steps: - enable building of systemd-plymouth package, actually changing %build_plymouth variable in systemd.spec - Take a look to the initrd related code, as well as "cryptsetup" integration that looks somewhat strange currently. - Install "bootsplash" only with legacy sysvinit. That's all for now. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 32

[opensuse-factory] kernel-desktop and kernel-desktop-base
by Kyrill Detinov 02 Jan '12

02 Jan '12

Hello. kernel-desktop-base-3.2.rc6 conflicts with kernel-desktop-3.2.rc6. Does it mean that I don't need kernel-desktop-base anymore and it is safe to remove version 3.1.0? x86_64 -- WBR Kyrill -- 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] glibc 2.15 coming to Base:System and later Factory
by Andreas Jaeger 02 Jan '12

02 Jan '12

FYI, I've put glibc 2.15 in Base:System and will push in a couple of days to Factory if I don't see any problems. I'm appending the announcement, there's nothing in it that should break stuff so please speak up if you notice something! Dirk, could you check what needs to be done for Arm, please? thanks, Andreas -------- Original Message -------- Subject: glibc 2.15 Date: Mon, 26 Dec 2011 05:31:04 -0500 From: Ulrich Drepper <drepper(a)gmail.com> To: libc-alpha <libc-alpha(a)sourceware.org> I have tagged the tree for the 2.15 release. This release saw some changes in additional functionality but mainly optimizations: Version 2.15 * The following bugs are resolved with this release: 6779, 6783, 9696, 10103, 10709, 11589, 12403, 12786, 12840, 12847, 12868, 12852, 12874, 12885, 12892, 12906, 12907, 12922, 12935, 12962, 13007, 13021, 13061, 13062, 13067, 13068, 13085, 13088, 13090, 13092, 13096, 13114, 13118, 13123, 13134, 13138, 13147, 13150, 13166, 13179, 13185, 13189, 13192, 13268, 13276, 13282, 13291, 13305, 13328, 13335, 13337, 13344, 13358, 13367, 13413, 13416, 13423, 13439, 13446, 13472, 13484, 13506, 13515, 13523, 13524, 13538, 13540 * New program pldd to list loaded object of a process Implemented by Ulrich Drepper. * Add nss_db support back to glibc. No more dependency on Berkeley db and support for initgroups lookups. Implemented by Ulrich Drepper. * Optimized strcpy, strncpy, stpcpy, stpncpy for SSE2 and SSSE3 on x86-32. Contributed by HJ Lu. * Improved strcpy, strncpy, stpcpy, stpncpy for SSE2 and SSSE3 on x86-64. Contributed by HJ Lu. * Optimized strcat, strncat on x86-64 and optimized wcscmp, wcslen, strnlen on x86-32 and x86-64. Contributed by Liubov Dmitrieva. * Optimized strchr and strrchr for SSE on x86-32. Contributed by Liubov Dmitrieva. * Optimized memchr, memrchr, rawmemchr, memcmp, wmemcmp, wcschr, wcscpy for x86-64 and x86-32. Contributed by Liubov Dmitrieva. * New interfaces: scandirat, scandirat64 Implemented by Ulrich Drepper. * Checking versions of FD_SET, FD_CLR, and FD_ISSET added. Implemented by Ulrich Drepper. * nscd now also caches the netgroup database. Implemented by Ulrich Drepper. * Integrate libm with gcc's -ffinite-math-only option. Implemented by Ulrich Drepper. * Lots of generic, 64-bit, and x86-64-specific performance optimizations to math functions. Implemented by Ulrich Drepper. * Optimized strcasecmp and strncasecmp for AVX on x86-64. Implemented by Ulrich Drepper. * New Linux interfaces: process_vm_readv, process_vm_writev * Optimized strcasecmp and strncasecmp for SSSE3 and SSE4.2 on x86-32. Implemented by Ulrich Drepper. * Optimized nearbyint and strcasecmp for PPC. Implemented by Adhemerval Zanella. * New locales: bho_IN, unm_US, es_CU, ta_LK I'll branch the tree for 2.15 in the next few days after which the development for 2.16 will start. Expect the next release in 6 month-ish. Thanks to everyone who helped with the release, especially Adhemerval Zanella Andreas Jaeger Andreas Krebbel Andreas Schwab David S. Miller H.J. Lu Jakub Jelinek Jiri Olsa Joseph Myers Liubov Dmitrieva Marek Polacek Paul Pluzhnikov Roland McGrath Samuel Thibault Will Schmidt -- 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

3 8

[opensuse-factory] Help with dir setup in /media
by Robert Schweikert 01 Jan '12

01 Jan '12

With 12.1 /media is now mounted as tmpfs. As I used to have a number of directories in /media (used as mount points for ISO images), I created the following script in /etc/tmpdirs.d to get the directories I want in /media -> cat /etc/tmpdirs.d/02_media mediaDirs=( os11332 os11364 os11432 os11464 os12132 os12164 sle10sp432sdk \ sle10sp464sdk sle11sp132sdk sle11sp164sdk sled1032 sled1064 \ sled10sp432 sled10sp464 sled11sp132 sled11sp164 sles1032 \ sles1064 sles10sp432 sles10sp464 sles11sp132 sles11sp164) for medDir in ${mediaDirs[@]};do test -d /media/$medDir || mkdir /media/$medDir done However, upon reboot the /media directory is empty, what am I missing? I am aware of the discussion of dropping /etc/tmpdirs.d (http://lists.opensuse.org/opensuse-packaging/2011-11/msg00057.html) However, the manpage for tmpdirs.d states /etc/tmpdirs.d supersedes /usr/lib/tmpfiles.d, also I think my custom files should go into /etc and not /usr/lib. Anyway, what is the best, and somewhat future proof, approach to this? As a side note, with the mounting of /media as tmpfs "umount /media" followed by the TAB key no longer auto-completes to any mounted filesystems/devices/loops etc :( . Is there a way to get the old behavior back? Thanks, 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

2 2

[opensuse-factory] [devel-editors] new package "nested"
by Izaac Zavaleta 31 Dec '11

31 Dec '11

Hello gents, I'd like to introduce you nested editor (nested) which is an specialized editor focused on structured documents you can read more about it in the project's about page: http://nestededitor.sourceforge.net/about.html it is basically a python-gtk/python-webkitgtk editor using txt2tags as markup language written in python, and according to upstream/vendor it needs python > 2.6 and also textlive to export or publish documents in tex/pdf and is also capable of export them as html, also the website is made with it. As you may notice it is focused to aid users not familiar with markup languages or tex tools to publish documents with advanced formatting. You can also check the complete list of features in the project website. In tech terms is basically written in python and with very few build requirements so it shouldn't be difficult to maintain. I'm in the process to do a submit request shortly to factory from devel-editors. Regards. -- 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] 'xz' (LZMA) support by default on our build environments...
by Nelson Marques 31 Dec '11

31 Dec '11

Dear people, The GNOME Project, one of the biggest projects in openSUSE is throwing out the source code in .xz (LZMA). This is quite fun and there's obvious benefits on it, the problem that rises from this is the following: * Our build environments doesn't support .xz sources; * We're required to add "BuildRequires: xz" to the spec files; * Some projects require us to add comments to the "BR xz" entries refering to bnc#697467; * Some projects require us to add the same stuff in the changelog entries; In the last times I've seen a growing demonstration of attitudes in the scope of "We dont give a flying fuck about you or your needs" (that's how I see it). The Project Management is growing arrogant and following a potential hidden agenda and ignoring everything that doesn't sound nice to them. While we move forward (or some at least) into dangerous fields like systemd, btrfs, the proposed changes from Fedora to the filesystem structure and friends... the stuff that we really could use to improve productivity and our work is being left behind. So I bring this tiny issue to your attention, so that any kind soul can provide a technical explanation on why we can have 'xz' supported on our build environments... and why we're required to insert dumbass comments that no one can explain. If the Project Leadership is unable to answer with a technical explanation for this, you should seriously consider resigning and opening your spot to someone who has some balls to change things up and at least provide a reasonable explanation for this.... at the risk of loosing every independent contributor that still donates some of their free time to openSUSE. NM PS: If you don't like the tone, live with it, I return in double whatever is granted to me. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 17

[opensuse-factory] factory publishing
by Christoph Walzer 31 Dec '11

31 Dec '11

Hi, tex is broken: texlive-2011-75.1.noarch requires texlive-bin = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-2011-75.1.i586[Factory_Publishing] texlive-latex-2011-75.1.noarch requires texlive-bin-latex = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-latex-2011-75.1.i586[Factory_Publishing] texlive-metapost-2011-75.1.noarch requires texlive-bin-metapost = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin- metapost-2011-75.1.i586[Factory_Publishing texlive-musictex-2011-75.1.noarch requires texlive-bin-musictex = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin- musictex-2011-75.1.i586[Factory_Publishing] texlive-tools-2011-75.1.noarch requires texlive-bin-tools = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-tools-2011-75.1.i586[Factory_Publishing] Seems the x86_64 versions are somehow missing. Regards, C. -- 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] factory publishing
by Christoph Walzer 30 Dec '11

30 Dec '11

Hi, tex is broken: texlive-2011-75.1.noarch requires texlive-bin = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-2011-75.1.i586[Factory_Publishing] texlive-latex-2011-75.1.noarch requires texlive-bin-latex = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-latex-2011-75.1.i586[Factory_Publishing] texlive-metapost-2011-75.1.noarch requires texlive-bin-metapost = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin- metapost-2011-75.1.i586[Factory_Publishing texlive-musictex-2011-75.1.noarch requires texlive-bin-musictex = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin- musictex-2011-75.1.i586[Factory_Publishing] texlive-tools-2011-75.1.noarch requires texlive-bin-tools = 2011-75.1, but this requirement cannot be provided uninstallable providers: texlive-bin-tools-2011-75.1.i586[Factory_Publishing] Seems the x86_64 versions are somehow missing. Regards, C. -- 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] RFC: Integrating Plymouth
by Anders Johansson 29 Dec '11

29 Dec '11

On Wednesday 28 December 2011 22:56:27 David Hall wrote: > On Wed, Dec 28, 2011 at 10:35 PM, Anders Johansson <ajh(a)nitio.de> wrote: > > Secondly, I'm not sure which part of this you think is a very requested > > feature. > > Look at: > https://features.opensuse.org/ > Second most voted for feature > > No matter your opinion of openFATE, it is where the community has agreed to > post features and vote on them. Well, reading the comments, the feature actually requested is for a flicker- free boot sequence, and that is something I can agree with, I certainly don't have a problem with that. I just think we may be leaving regular users behind for ideological reasons when we say that users of the only properly working nvidia driver can forget support, they'll have to take what they get. I think it should be possible to detect when there is a kms capable driver, and use plymouth then, and fall back to bootsplash/splashy/whatever to provide a nice graphical boot sequence for everyone. I don't object to plymouth, I object to dropping the standard bootsplash by default Anders -- 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] [12.1-update] German release notes as an update - Would that be possible?
by Kim Leyendecker 28 Dec '11

28 Dec '11

Howdy all, The German translation of the release notes will be ready soon. So, I want to ask you if it would be possible to ship them as an update. thanks, -- Kim Leyendecker, openSUSE Wiki Team GPG Key: 664265369547B825 | leyendecker(a)opensuse.org http://www.opensuse.org - Linux for open minds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Tarballs absent in upstream is not a packaging bug
by Cristian Rodríguez 27 Dec '11

27 Dec '11

Hi: Currently, some bots are mass refusing submit requests due to missing tarballs in the Source field of the spec file. With all due respect, this is non-sense, specially since machine made resolutions cannot be successfully challenged, reopening the request causes the same damned bot to decline the request for the same reason,over and over again. Try for example getting reliable tarballs from kernel.org..since the intrusion on their systems they are sometimes there, sometimes not. Also it considers FTP connection failures as a packaging bug ! even changing the Source line causes the same declined request, as do omitting the url and just using %{name}-%{version}.tar.bz2. I understand that the purpose of the check is to verify the authenticity of the file, however failing servers or under-recovery sites are none of our business. Thanks for taking a look at this :-P -- 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] cyrus-sasl, the package that rules them all?
by Gerald Pfeifer 23 Dec '11

23 Dec '11

So, one of these days I figured I'd make the installation on one of my systems a bit slimmer, and I really don't need an IMAP server on that machine. tomonaga# rpm -qa | grep cyrus-sasl cyrus-sasl-gssapi-2.1.25-17.2.x86_64 cyrus-sasl-plain-2.1.25-17.2.x86_64 cyrus-sasl-saslauthd-2.1.25-17.2.x86_64 cyrus-sasl-crammd5-2.1.25-17.2.x86_64 cyrus-sasl-2.1.25-17.2.x86_64 cyrus-sasl-32bit-2.1.25-17.2.x86_64 cyrus-sasl-digestmd5-2.1.25-17.2.x86_64 Alas, when removing cyrus-sasl, zypper is inclined to remove quite a bit more including the kernel, Firefox, and a load of others? Something is overly aggressive in terms of dependencies it seems? Or am I missing something? tomonaga# rpm -qa | grep cyrus-sasl | xargs zypper rm Loading repository data... Reading installed packages... Resolving package dependencies... The following packages are going to be REMOVED: ConsoleKit ConsoleKit-x11 DirectFB-Mesa Mesa ModemManager MozillaFirefox MozillaFirefox-branding-openSUSE NetworkManager NetworkManager-gnome NetworkManager-openvpn NetworkManager-openvpn-gnome OpenPrintingPPDs-ghostscript OpenPrintingPPDs-hpijs OpenPrintingPPDs-postscript PackageKit PackageKit-branding-openSUSE PackageKit-browser-plugin PackageKit-gstreamer-plugin PolicyKit SuSEfirewall2 a2ps aaa_base aaa_base-extras accountsservice acpid alpine alsa-plugins-pulse amarok at at-spi2-core audit autofs autoyast2-installation biosdevname bluez bootsplash bootsplash-branding-openSUSE brltty-driver-at-spi2 brltty-driver-espeak bug-buddy cantarell-fonts cdrdao cdrkit-cdrtools-compat cifs-utils cmake colord cron cronie cryptsetup cups cups-backends cups-pk-helper curl cyrus-sasl cyrus-sasl-32bit cyrus-sasl-crammd5 cyrus-sasl-digestmd5 cyrus-sasl-gssapi cyrus-sasl-plain cyrus-sasl-saslauthd dbus-1 dbus-1-glib dbus-1-python dconf dejavu desktop-file-utils device-mapper dhcp dhcp-client dhcpcd digikam dirmngr dmraid dnsmasq dosbox droid-fonts efont-unicode emacs-x11 enblend-enfuse enscript espeak evince evolution-data-server fam fetchmail fifth-leg-font finger flash-player foomatic-filters freeglut gconf-editor gconf-polkit gconf-sanity-check gconf2 gdm gdm-branding-openSUSE ghostscript-fonts-std ghostscript-library ghostscript-x11 gimp gimp-branding-openSUSE gimp-help gjs gnokii gnome-bluetooth gnome-contacts gnome-keyring gnome-packagekit gnome-panel gnome-panel-branding-openSUSE gnome-power-manager gnome-screensaver gnome-session-core gnome-settings-daemon gnome-settings-daemon-polkit-datetime gnome-terminal gnome-vfs2 gpg2 gpsd gsettings-backend-dconf gstreamer-0_10-libnice gstreamer-0_10-plugin-esd gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-good gucharmap gutenprint gvfs gvfs-backend-afc gvfs-backends gvfs-fuse haveged hplip-hpijs hplip-sane icedax ifnteuro intlfnts irqbalance k3b kaffeine kdebase4-runtime kdelibs4 kdelibs4-core kdepimlibs4 kdialog kernel-default kernel-default-base kerneloops kipi-plugins kipi-plugins-acquireimage kipi-plugins-geolocation kpartx kscd ksh libGLEW1_6 libGLEW1_7 libQtWebKit4 libaccountsservice0 libakonadi4 libakonadiprotocolinternals1 libao-plugins4 libao4 libapr-util1 libatasmart0 libatasmart4 libatspi0 libattica0 libavahi-client3 libavahi-gobject0 libbrasero-burn3-1 libbrasero-utils3-1 libcamel-1_2-28 libcamel-1_2-29 libcanberra-gtk0 libcanberra-gtk3-0 libcanberra0 libcheese-gtk20 libcheese1 libclutter-glx-1_0-0 libclutter-gst-1_0-0 libclutter-gtk-1_0-0 libcogl-pango0 libcogl1 libcogl2 libcogl5 libcompizconfig libcryptsetup1 libcryptui0 libcurl4 libdbusmenu-qt2 libdconf0 libdns_sd libebackend-1_2-1 libebook-1_2-11 libebook-1_2-12 libecal-1_2-10 libecal-1_2-9 libedata-book-1_2-10 libedata-book-1_2-11 libedata-cal-1_2-12 libedata-cal-1_2-13 libedataserver-1_2-14 libedataserver-1_2-15 libedataserverui-3_0-1 libepc-1_0-2 liberation-fonts libfolks-eds25 libfolks-libsocialweb25 libfolks-telepathy25 libfolks25 libftgl2 libgconfmm-2_6-1 libgdata13 libgdmgreeter1 libgdu0 libgeoclue0 libgjs0 libgnome-bluetooth8 libgnome-keyring0 libgoa-backend-1_0-0 libgpgme11 libgphoto2 libgpod-tools libgpod4 libgrlnet-0_1-0 libgssdp-1_0-3 libgudev-1_0-0 libgupnp-1_0-4 libgupnp-av-1_0-2 libgupnp-igd-1_0-3 libgvfscommon0 libgvnc-1_0-0 libgweather-3-0 libgweather-data libimobiledevice2 libkcddb4 libkcompactdisc4 libkdcraw20 libkde4 libkdecore4 libkdeedu4-data libkdepimlibs4 libkeduvocdocument4 libkexiv2-10 libkface1 libkgeomap1 libkipi8 libksane0 libksuseinstall1 liblastfm0 liblazy1 libldap-2_4-2 libldap-2_4-2-32bit libldapcpp1 libldb1 liblockdev1 libmarblewidget12 libmission-control-plugins0 libmx-1_0-2 libmygpo-qt1 libnice10 libnm-glib-vpn1 libnm-glib4 libnm-gtk0 libnm-util2 liboauth0 libofx libofx4 libopal3_6_8 libopencv2_3 libpackagekit-glib2-14 libpanel-applet-4-0 libparted0 libphonon4 libpolkit-qt-1-1 libpolkit0 libpq5 libprison0 libproxy1-networkmanager libpt2_6_7 libpulse-mainloop-glib0 libpulse0 libqca2 libqdialogsolver1 libqjson0 libqt4 libqt4-qt3support libqt4-sql libqt4-sql-mysql libqt4-sql-postgresql libqt4-sql-sqlite libqt4-x11 libquvi0 libquvi6 libqzeitgeist0 libraptor2-0 librasqal3 libredland0 libreoffice libreoffice-base libreoffice-base-extensions libreoffice-calc libreoffice-calc-extensions libreoffice-converter libreoffice-draw libreoffice-draw-extensions libreoffice-filters-optional libreoffice-help-en-US libreoffice-impress libreoffice-impress-extensions libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer libreoffice-writer-extensions librest0 libsmbclient0 libsocialweb libsocialweb-branding-openSUSE libsocialweb-client2 libsocialweb0 libsoprano4 libsoup-2_4-1 libspectre1 libstorage3 libstrigi0 libtelepathy-glib0 libtelepathy-logger2 libtotem-plparser-mini17 libtotem-plparser17 libtunepimp libtunepimp5 libudev0 libupower-glib1 libusbmuxd1 libwebkitgtk-3_0-0 libxine1 libxine1-pulse libyelp0 libzypp lirc lockdev logrotate lvm2 marble marble-data mariadb mcelog metacity microcode_ctl mkinitrd moodbar multipath-tools mutter nautilus-evince nautilus-extension-seahorse nautilus-open-terminal nautilus-totem netcfg nfs-client nfsidmap notification-daemon ntp obex-data-server obexd obexd-client openSUSE-build-key openldap2-client openssh openssh-askpass parallel-printer-support parted patterns-openSUSE-base patterns-openSUSE-enhanced_base patterns-openSUSE-games patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-sw_management patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf perl-WWW-Curl phonon-backend-gstreamer-0_10 plotutils pm-utils polkit polkit-gnome postfix pstoedit pulseaudio pulseaudio-esound-compat pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-jack pulseaudio-module-lirc pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils pwdutils python-gnomekeyring python-smbc qt4-qtscript redland rpcbind rsyslog rtkit samba samba-client seahorse seahorse-daemon smartmontools snapper-zypp-plugin soprano soprano-backend-redland soprano-backend-virtuoso sox speech-dispatcher speech-dispatcher-module-espeak splashy splashy-branding-openSUSE strigi subversion subversion-perl sudo suseRegister suspend sysconfig syslog-ng syslog-service system-config-printer system-config-printer-applet system-config-printer-common system-config-printer-dbus-service systemd systemd-presets-branding-openSUSE systemd-sysvinit telepathy-gabble telepathy-idle telepathy-mission-control telepathy-salut telepathy-sofiasip telnet tightvnc tmpwatch totem totem-browser-plugin totem-browser-plugin-gmp totem-plugins transfig transmission transmission-common udev udev-configure-printer udisks update-desktop-files upower usbmuxd vim vim-base vim-data vino virtuoso-server vorbis-tools wine wine-32bit wine-gecko wpa_supplicant xchat xchat-perl xchat-tcl xinetd xkeyboard-config xlockmore xorg-x11 xorg-x11-Xvnc xorg-x11-driver-input xorg-x11-driver-video xorg-x11-driver-video-intel-legacy xorg-x11-driver-video-nouveau xorg-x11-server xorg-x11-server-extra xscreensaver-data xscreensaver-data-extra yast2 yast2-add-on yast2-apparmor yast2-backup yast2-bootloader yast2-control-center yast2-control-center-gnome yast2-control-center-qt yast2-country yast2-dbus-client yast2-drbd yast2-fingerprint-reader yast2-firewall yast2-gtk yast2-inetd yast2-inetd-doc yast2-installation yast2-irda yast2-iscsi-client yast2-iscsi-server yast2-kerberos-client yast2-ldap yast2-ldap-client yast2-mail yast2-metapackage-handler yast2-mouse yast2-ncurses-pkg yast2-network yast2-nfs-client yast2-nis-client yast2-ntp-client yast2-online-update yast2-online-update-frontend yast2-packager yast2-pam yast2-pkg-bindings yast2-printer yast2-qt yast2-qt-pkg yast2-restore yast2-runlevel yast2-samba-client yast2-samba-server yast2-scanner yast2-security yast2-slp yast2-snapper yast2-sound yast2-sshd yast2-storage yast2-sudo yast2-support yast2-sysconfig yast2-transfer yast2-tune yast2-tv yast2-update yast2-users yast2-vm yelp ypbind yudit zypper 548 packages to remove. After the operation, 2.0 GiB will be freed. Continue? [y/n/?] (y): Gerald -- Dr. Gerald Pfeifer <gp(a)suse.com> || SUSE || Director Product Management -- 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] Check in review delay: Vacation Christmas and New Year`s Eve 2011/2012
by Lars Vogdt 20 Dec '11

20 Dec '11

Dear Packagers, during the time from the 24th Dec 2011 until 08th Jan 2012 (Christmas/New Year´s Eve) many teams and departments inside the SUSE Linux Products GmbH will be on vacation or can only offer limited services. This affects also the "autobuild-team" you might know as reviewers for your packages submitted to Factory (and other released distributions). While some of us are still in the office to get the most annoying and security bugs fixed and out to you as our customers, most of us are using this period to spend some time aside of computers and with their friends and families. As result, packages in openSUSE:Factory might stay a bit longer in the "review" state as you can expect in normal times. Please be not so angry with us in this case - just do the same and use this time for regeneration and preparation for the upcoming openSUSE year. We wish you and your families a Merry Christmas and a Happy New Year! Ah: and remember to have a lot of fun! ;-) Lars -- Lars Vogdt <Lars.Vogdt(a)suse.com> - OPS Engineering Services Teamlead - SUSE Linux Products GmbH - GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Maxfeldstraße 5, 90409 Nuernberg, Germany - HRB 16746 (AG Nuernberg) -- 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] Tumbleweed Project is almost empty (only 26 packages being built)
by Dirk Müller 20 Dec '11

20 Dec '11

On Tuesday 13 December 2011, Joerg Mayer wrote: > OK, when *will* Tumbleweed start to be "useable" again? Right now I'm > running 12.1 but with the newer Xorg (Mesa 7.11.1 instead of 7.11) is there a reason for updating to 7.11.1 other than the version number? if so, file a bugreport and NEEDINFO maintenance(a)opensuse.org to see if we can ship this as a regular update. > , KDE > (4.7.4 instead of 4.7.2) same here (note a big swoop of updates have just been released that are related to KDE). > and libreoffice (3.4.4 instead of 3.4.2) repos. this will come pretty soon anyway as an update. Greetings, Dirk -- 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] namespace for system users - tor
by Andreas Stieger 20 Dec '11

20 Dec '11

Hello, I would put Ludwig Nussel's points from -packaging up for discussion. On Thursday 15 Dec 2011 08:30:56 Ludwig Nussel wrote: > There's a request to add a system user 'tor': > https://build.opensuse.org/request/show/96531 > > There is no name space separation between system users and actual > logins. So especially for short names like the above there is a > chance that it could collide with an already existing user name on > some system. Having a system service running with the uid of an > actual user isn't desirable. > So what about mandating an extra prefix or suffix to (new) system > user names like 'daemon' or 'service'? Ie in the above example the > user name would be 'tor-daemon' or 'tor-service' instead of 'tor'. > Other thoughts? The request mentioned above has been merged manually to devel:openSUSE:Factrory:rpmlint / rpmlint by dirkmueller and the change is now pending to be added to openSUSE:Factory - #97074 The packages indirectly involved are network / tor and openSUSE:Factory / tor. Debian uses "debian-tor". The upstream sources specify: "_tor" in a sample spec file, other online examples use tor_d / daemon for the uid/gid. I agree in general that there is potential for conflicts. This, however, is not a new problem with "tor", but also with "amanda" and "jonas" which were already registered and are obviously far more popular. These are legacy and Ludwig proposed guidelines for new packages only. I don't see an immediate packaging issue, but as this is a new package to factory I am willing to update if there is consensus in -factory as to rules for the naming of daemon users for new packages, or at least regarding this particular package. With kind regards, Andreas Stieger -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0