October 2013 - 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

[opensuse-factory] New Package - libhal1-flash (re-enabling Flash-Player DRM content on Linux)
by Christopher Horler 13 Sep '14

13 Sep '14

Good afternoon! I've written and packaged a compatibility library for flash to enable playback of DRM content (this removes the dependency on the HAL package). I'd like to know what steps I can take to have the package considered for inclusion in openSUSE 12.3 and 13.1. Can I submit the package to devel:openSUSE:Factory, or is there another action I should be taking? Details of the bug and links to upstream are here (please briefly review): https://bugzilla.novell.com/show_bug.cgi?id=768562#c19 OBS location: https://build.opensuse.org/package/show?package=hal-flash&project=home%3Ach… I will maintain the package until such time that HTML5 Video content is a viable alternative or the Flash plugin is completely withdrawn. RPMs, debs... are all available on the build service. Three noteworthy points: - package naming (libhal1-flash) doesn't 100% align with the Shared Library Policy (I've suffixed -flash to make clear this is not a fully functional HAL layer and also to avoid naming conflicts as some distros seem to have a shared library package already named libhal1). - The packages depends on dbus and udisks. It seems to work find when udisks is launched on demand (as for openSUSE 12.3) - The flash-player package could have some kind of RPM dependency on this package to assist the user when looking in YaST (Install / Remove Software) / Package Manager. Chris -- 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] source_validator error: signature does not validate
by Kyrill Detinov 25 Aug '14

25 Aug '14

Hello. I can't build a package. Service source_validator failed. % osc build Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpVbBhay Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector.keyring gpg: enabled debug flags: memstat gpg: keyring `/tmp/check_if_valid_source_dir-NL8Ezs/.checkifvalidsourcedir-gpg-keyring' created gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: key 015475F5: public key "Jakub Wilk <jwilk(a)jwilk.net>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks gpg: enabled debug flags: memstat gpg: Signature made Mon Jun 24 22:36:51 2013 MSK using RSA key ID 015475F5 gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: Good signature from "Jakub Wilk <jwilk(a)jwilk.net>" gpg: aka "Jakub Wilk <jwilk(a)debian.org>" gpg: aka "Jakub Wilk <ubanus(a)users.sf.net>" random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks (E) signature /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector-0.11.1.tar.gz.asc does not validate Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i Source service run failed! As far as I can see, the signature is good. This also happens with another package (graphics/icoutils). What is the problem? -- WBR Kyrill

2 5

[opensuse-factory] what happened to fbset?
by Felix Miata 04 Aug '14

04 Aug '14

in 11.4: # fbset -i mode "1152x864" geometry 1152 864 1152 864 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : radeondrmfb Address : 0xd80c0000 Size : 3981312 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 4608 Accelerator : No In 13.1B1: # fbset -l if 'fbset' is not a typo, You can use... # zypper se -s fbset ... No packages found. # command-not-found fbset fbset: command not found -- "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 To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 18

[opensuse-factory] libav and multimedia idea
by Tomáš Chvátal 14 May '14

14 May '14

Hello guys, I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute. Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^. The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies. Let me know what you think about this plan and what would you use as base devel project for this. Cheers Tom [1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv

8 11

[opensuse-factory] Btrfs under heavy write makes system sluggish-er than ext
by Claudio Freire 06 Feb '14

06 Feb '14

So, the subject says it all. I've been testing a huge database on 13.1 RC1, well actually factory, with a btrfs partition (not the system partition, just a dedicated partition), and under heavy write it chokes the system much more than ext4 does. It also seems to have lower thoughput on what should be mostly parallel sequential access (ie: multiple sequential threads), but I'll have to perform more accurate benchmarks to be sure. It may be an fsync issue. It's not a critical issue, of course, but I'm in a position to assist with tests, benchmarks and diagnostics... so... what do I need to do to provide useful info here? -- 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] YaST2 "install/remove" doesn't display solver diagram
by Kyrill Detinov 13 Jan '14

13 Jan '14

Hello. There is a regression in YaST2 *Qt* "install/remove software" module. It doesn't show solver diagram. First, no dependencies on libqdialogsolver. Second, installed libqdialogsolver doesn't help. Reported ages ago. And confirmed. All the info is provided. https://bugzilla.novell.com/show_bug.cgi?id=785431 WBR Kyrill

3 3

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] New packages submission to factory - rubygem-rspec, rubygem-packaging_rake_tasks and rubygem-yast-rake
by Josef Reidinger 09 Dec '13

09 Dec '13

Hi, I'd like to introduce a few new packages that I would like to have in factory ( not 13.1 ). All is related to changes in YaST development and conversion to ruby. rubygem-rspec[1]: Very famous testing frame-work for ruby. It is quite stable now and it is widely used in various projects for testing. Inclusion allows YaST to runs its new tests written in rspec during rpm build to help with early bugs detection ( Yast use CI, but check in during rpm helps with problem detection if dependency change and obs trigger rebuild ). I am willing to maintain it in factory and fix related bugs. rubygem-packaging_rake_tasks[2]: The gem is set of tasks for ruby build tool rake contains helpers for checking code quality, easy submit to Build Service or run local build. Project is around 2 years old and I maintain it myself. It is used in few projects to make submitting ruby projects to build service easier. It reaches version 1.0.0 where API of tasks is stable. I am author and I am willing to maintain it. rubygem-yast-rake[3]: The gem is rake configuration for yast projects. It is very young project and started few weeks ago, but it is needed for new yast CI. It uses packaging rake tasks. It provides to them configuration for yast projects ( like default devel project, default target project, etc. ) and add tasks specific for yast development. It is not much stable now, but yast is only project which depend on it and now it is not needed to build, so there is no risk, it just make yast developer life easier. I am author and I am willing to maintain it. If you have any question, complain or you are interested in such packages, do not hesitate to contact me. Josef [1] http://rspec.info/ [2] https://github.com/openSUSE/packaging_tasks/ [3] https://github.com/yast/yast-rake -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] Thunderbird and Firefox not working, Dolphin and stopping via KDE-menu very slow
by Jogchum Reitsma 24 Nov '13

24 Nov '13

Hi, After a fresh install of RC1 (and emptying .kde and .kde4) firefox and thunderbird are not working. Both show (process:4432): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed when started from the command line. There are several posts (also very recent ones) on various ml's about this error message for FF and TB, but none on opensuse (and none with a solution which works for me). After first start of FF, the FF-window appears, with the entries on the main menu, but without the corresponding icons. Starting it a second - or third, fourth etc.) the icons appear also, and a subwindow which lists the sessions that could not be opened (which is all sessions). No input is taken from mouse or keyboard, and also closing the window does not work (intil KDE kicks in). Also - but maybe not related - some applications are very, very slow starting up. For example to start dolphin it takes 75 secs. To restart or shutdown from the KDE menu it takes 2 minutes for the little stop-menu to appear, and another 75 secs before the real shutdown is started after choosing restart or shutdown. Shutdown as root from a terminal has it's normal speed. What can be going on here? regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 22

[opensuse-factory] running zypper from crontab
by doiggl＠velocitynet.com.au 23 Nov '13

23 Nov '13

Hello, Questions: 1. What command switches allow 'zypper -v up' to run from crontab ? 2. What command switches allow zypper to download the packages/rpm ? Thanks Glenn # zypper --help Usage: zypper [--global-options] <command> [--command-options] [arguments] Global Options: --help, -h Help. --version, -V Output the version number. --promptids Output a list of zypper's user prompts. --config, -c <file> Use specified config file instead of the default. --userdata <string> User defined transaction id used in history and plugins. --quiet, -q Suppress normal output, print only error messages. --verbose, -v Increase verbosity. --no-abbrev, -A Do not abbreviate text in tables. --table-style, -s Table style (integer). --rug-compatible, -r Turn on rug compatibility. --non-interactive, -n Do not ask anything, use default answers automatically. --non-interactive-include-reboot-patches Do not treat patches as interactive, which have the rebootSuggested-flag set. --xmlout, -x Switch to XML output. --ignore-unknown, -i Ignore unknown packages. --reposd-dir, -D <dir> Use alternative repository definition file directory. --cache-dir, -C <dir> Use alternative directory for all caches. --raw-cache-dir <dir> Use alternative raw meta-data cache directory. --solv-cache-dir <dir> Use alternative solv file cache directory. --pkg-cache-dir <dir> Use alternative package cache directory. Repository Options: --no-gpg-checks Ignore GPG check failures and continue. --gpg-auto-import-keys Automatically trust and import new repository signing keys. --plus-repo, -p <URI> Use an additional repository. --disable-repositories Do not read meta-data from repositories. --no-refresh Do not refresh the repositories. --no-cd Ignore CD/DVD repositories. --no-remote Ignore remote repositories. Target Options: --root, -R <dir> Operate on a different root directory. --disable-system-resolvables Do not read installed packages. Commands: help, ? Print help. shell, sh Accept multiple commands at once. Repository Management: repos, lr List all defined repositories. addrepo, ar Add a new repository. removerepo, rr Remove specified repository. renamerepo, nr Rename specified repository. modifyrepo, mr Modify specified repository. refresh, ref Refresh all repositories. clean Clean local caches. Service Management: services, ls List all defined services. addservice, as Add a new service. modifyservice, ms Modify specified service. removeservice, rs Remove specified service. refresh-services, refs Refresh all services. Software Management: install, in Install packages. remove, rm Remove packages. verify, ve Verify integrity of package dependencies. source-install, si Install source packages and their build dependencies. install-new-recommends, inr Install newly added packages recommended by installed packages. Update Management: update, up Update installed packages with newer versions. list-updates, lu List available updates. patch Install needed patches. list-patches, lp List needed patches. dist-upgrade, dup Perform a distribution upgrade. patch-check, pchk Check for patches. Querying: search, se Search for packages matching a pattern. info, if Show full information for specified packages. patch-info Show full information for specified patches. pattern-info Show full information for specified patterns. product-info Show full information for specified products. patches, pch List all available patches. packages, pa List all available packages. patterns, pt List all available patterns. products, pd List all available products. what-provides, wp List packages providing specified capability. Package Locks: addlock, al Add a package lock. removelock, rl Remove a package lock. locks, ll List current package locks. cleanlocks, cl Remove unused locks. Other Commands: versioncmp, vcmp Compare two version strings. targetos, tos Print the target operating system ID string. licenses Print report about licenses and EULAs of installed packages. source-download Download source rpms for all installed packages to a local directory. -- 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] Extended Chromium builds for openSUSE !
by Raymond Wooninck 22 Nov '13

22 Nov '13

Dear list mates, Based on the official chromium tarballs, the process of building Chromium for openSUSE has become a lot easier. This allowed me to extend the Chromium offering for openSUSE users and the following is now available: openSUSE releases and Factory will follow the stable channel updates. I believe this is the right way where a stable Chromium is provided with a stable openSUSE release The OBS repository network:chromium, will provide besides the chromium package (stable channel), also the following packages: chromium-beta (This is based on the beta channel releases) chromium-dev (This is based on the dev channel releases). Please be aware that these packages are mutual exclusive and it is ONLY possible to install one of them. This to prevent issues with the chromium config files for the user. The Packman OBS has been updated to build the corresponding ffmpeg packages for each build to prevent issues. 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 4

[opensuse-factory] Syncing fixes between mkinitrd and dracut
by Michal Vyskocil 14 Nov '13

14 Nov '13

Hi, there is a new request [1] for mkinitrd fixing few bugs for openSUSE Factory. However there was a big effort to replace dracut as a default initrd tool, which seems to be turned on in Factory (see This will replace mkinitrd with dracut as the default initrd generator. in dracut.changes). So I would expect all development and fixing effort should go into dracut instead of mkinitrd (which is hard as even 13.1 won't have it as a default, so most reports are for mkinitrd). So atm the best we can do is to port mkinitrd fixes to dracut (and vice-versa?). Are all interested people aware about the intended switch and is there a process to forward bugs/feature requests from one group to an another? CCying people found in last .changes for both as not sure, who is subscribed here [1] https://build.opensuse.org/request/show/203579 BTW: there is no bugowner for dracut in Base:System/dracut Regards Michal Vyskocil

11 33

[opensuse-factory] Ancient hardware support statement
by Sascha Peilicke 13 Nov '13

13 Nov '13

Hi guys, without checking any mail archives, our forums or wikis for prior art, I would like to know if we have any general hardware support statements. I'm currently staring at a maintenance update that disables SSE2 support on certain software because the CPU doesn't support it. The manufacturing of that CPU stopped in 2004, so I'm not really sure what to think of it. Any thoughts? -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)

8 16

[opensuse-factory] RFC: new package: wemux
by Adam Spiers 08 Nov '13

08 Nov '13

Hi all, I've just packaged wemux: https://build.opensuse.org/package/show/home:aspiers/wemux and would like to find a suitable develproject to be its home. Suggestions gratefully received! Thanks, Adam -- 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] Plain text restriction [Was: Testing many small file write on several filesystems]
by Archie Cobbs 07 Nov '13

07 Nov '13

Jan Engelhardt <jengelh(a)inai.de> wrote: > 14:42 ares07:~ > xfs_info . > meta-data=/dev/md7 isize=256 agcount=32, agsize=22891675 blks > = sectsz=512 attr=2 > data = bsize=4096 blocks=732533583, imaxpct=5 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 ascii-ci=0 > log =internal bsize=4096 blocks=357682, version=2 > = sectsz=512 sunit=0 blks, lazy-count=1 > realtime =none extsz=4096 blocks=0, rtextents=0 Sorry for the following rant, I just can't stand to be silent anymore... This filesystem performance discussion is very interesting! Unfortunately, I can't read any of the reported statistics. Why are they unreadable? Because all of the emails are plain text, but rendered in Gmail in a non-fixed width font, so the columns don't line up. Why are all of the emails plain text? Because all openSUSE mailing lists require this. Why do all openSUSE mailing lists require plain text? HECK IF I KNOW!?! This is 2013. Is anyone out there still reading email using /usr/bin/mail? It sure would be nice if people could send HTML email, like the rest of the world (and every other open source project I'm involved in) has been doing for the past 15 years, so that, say, a fixed-width font could be specified for stuff that needs a fixed-width font. We could even require HTML emails to be "multipart/alternative" for those remaining 17 /usr/bin/mail users. What am I missing? -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 60

[opensuse-factory] Going forward with Plymouth (based on dracut changes)
by Raymond Wooninck 07 Nov '13

07 Nov '13

Hi, Based on the recent changes for Dracut and making it replace mkinitrd, also has some consequences for Plymouth. Using Dracut at the moment would generate a smaller initrd file, then utilizing mkinitrd. Main reason for this is not that Dracut is so much smarter, but more that only partial Plymouth support is provided. The initrd that Dracut generated does not include the Pango libraries/modules and Font that is required to present the user with a question or comments during the boot process. In most cases this is never used, but for those users that utilize encrypted disks, this would be a major issue. This particular combination has been always a hot topic in the past and I would like to resolve it in the best way possible. As far as I can see, we have the following possibilities: 1) Drop the ask-for-password stuff from Plymouth, which would allow us to drop the additional library requirements. This would mean that the password for encrypted disks is validated before plymouth starts (all within the initrd) 2) Drop plymouth from initrd and start plymouth from disk after password, etc have been required. This would then be the task for systemd, which already has this support. 3) Try to establish a checking mechanism that implements option 2 for particular kernels/encrypted root/swap disks. For the other users there is no change. Option 2 would be easy to implement. For the others I don't know and I might have to rely on others to support me. However I would like to have your opinion on the right way forward. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 21

[opensuse-factory] [13.1 RC1] - upgrade test: no network device
by Carlos E. R. 07 Nov '13

07 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm testing the offline upgrade method (DVD) from 12.3 to 13.1, in a vmplayer machine. I've hit a strange problem: no network. Aparently there is a conflict between the old network name, eth0, and the new, ens33. I had a look at yast network module (yast says the name is eth0), then rebooted. This is what the service status says now: +++······························· network.service - LSB: Configure network interfaces and set up routing Loaded: loaded (/usr/lib/systemd/system/network.service; enabled) Active: failed (Result: exit-code) since Tue 2013-10-29 00:37:31 CET; 1h 11min ago Process: 902 ExecStart=/etc/init.d/network start (code=exited, status=7) Oct 29 00:37:01 eleanor3 network[902]: Setting up network interfaces: Oct 29 00:37:01 eleanor3 network[902]: lo Oct 29 00:37:01 eleanor3 ifup[1186]: lo Oct 29 00:37:01 eleanor3 ifup[1230]: lo Oct 29 00:37:01 eleanor3 ifup[1233]: IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 network[902]: lo IP address: 127.0.0.1/8 Oct 29 00:37:01 eleanor3 ifup[1235]: Oct 29 00:37:01 eleanor3 network[902]: ..done ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 ifup[1301]: ens33 Startmode is 'manual' -> skipping Oct 29 00:37:01 eleanor3 network[902]: ..skippedWaiting for mandatory devices: eth0 Oct 29 00:37:31 eleanor3 network[902]: 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 6 5 4 3 2 1 0 Oct 29 00:37:31 eleanor3 network[902]: eth0 No interface found Oct 29 00:37:31 eleanor3 network[902]: ..failedSetting up service network . . . . . . . . . . . . ...failed Oct 29 00:37:31 eleanor3 systemd[1]: network.service: control process exited, code=exited status=7 Oct 29 00:37:31 eleanor3 systemd[1]: Failed to start LSB: Configure network interfaces and set up routing. Oct 29 00:37:31 eleanor3 systemd[1]: Unit network.service entered failed state. ·······························++- How should this be handled? If I try to delete the interface in YaST, and then add a new interface, it still says the name is eth0. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJvCJsACgkQtTMYHG2NR9UDdQCeIehd/YSBlnAFRXZok2+1UREr PM4An12cMm7q93fAsas1PrgqC3et14qJ =CY5N -----END PGP SIGNATURE-----

5 9

[opensuse-factory] Fwd: mozilla-nspr: declined by factory-auto
by Wolfgang Rosenauer 06 Nov '13

06 Nov '13

Hi, is there any way to avoid that check to fail? I know I can remove the full URL but this is a temporary thing. That file is not yet available since upstream is very slow in publishing tarballs for releases and many times we cannot/don't want to wait until they appear. So do I need to remove the full path? Wolfgang -------- Original-Nachricht -------- State of submit-request #201261 was changed by factory-auto: review -> declined Comment: Output of check script: ERROR: Failed to download ftp://ftp.mozilla.org/pub/nspr/releases/v4.10.1/src/nspr-4.10.1.tar.bz2 Source URLs are not valid. Try "osc service localrun download_files" -- 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] release notes 13.1 review
by Ludwig Nussel 06 Nov '13

06 Nov '13

Hi, I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed: 2.2. No Network after Installation 2.3. The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices 3.1. openSUSE Documentation 3.4. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode 3.5. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment 3.6. Crypted LVM in UEFI Mode Needs /boot Partition 4.1. systemd: Activating NetworkManager with a network.service Alias Link The following items still apply 3.3. UEFI—Unified Extensible Firmware Interface 4.2. SYSLOG_DAEMON Variable Removed 5.2. Configuring Postfix I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove? 5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection -> someone from the gnome team may be able to comment here cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 34

Re: [opensuse-factory] SOLVED: postfix does not run
by Christian Boltz 06 Nov '13

06 Nov '13

Hello, Am Freitag, 22. März 2013 schrieb Patrick Shanahan: > /etc/postfix/main.cf had @_some-parameter_@ setting for every > "xxxxxxx_directory =" line. > > After correcting "xxxxxxxx_directory =" settings per my Tumbleweed > machine, postfix appears working correctly. > > This mess probably occurred on installing/upgrading postfix: > postfix-2.9.6-2.1.x86_64 Sun Mar 10 11:14:39 2013 > but the rpm main.cf does not contain "@.............@". This sounds like https://bugzilla.novell.com/show_bug.cgi?id=796162 which should be fixed since some time. I'd guess some older postfix package broke your main.cf. Nevertheless, if you want to be really sure, uninstall postfix, move away /etc/postfix and re-install the postfix package. Regards, Christian Boltz -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- 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] [opensuse-packaging] Re: Some Python questions (Was: Re: devel:language:python3)
by Yamaban 06 Nov '13

06 Nov '13

On Mon, 28 Oct 2013 09:17, Sascha Peilicke <speilicke@...> wrote: > On Thursday 24 October 2013 15:07:49 Adam Spiers wrote: >> Sascha Peilicke (speilicke(a)suse.com) wrote: >>> On Saturday 12 October 2013 14:19:57 you wrote: >>>> Hi Sascha ! >>>> >>>> Is there any possibility we (all python maintainers) discuss our goals >>>> both python2 and python3 ? >>> >>> sure, since Juergen joined recently too, I CC'ed everyone. I dunno how you >>> guys prefer it, we could have an IRC meeting at some point but I guess >>> it's >>> easier to stay with mails just now. Therefore I added opensuse-packaging@ >>> because that's really where we should discuss things. >>> >>>> We receive requests sometimes update and/or >>>> new packages which are Python3 compatible. >>> [snip] >>> In the long run, py3k will gradually replace py2k in openSUSE, that means >>> if the critical mass is reached and most upstreams moved on, py2k pkgs >>> will slowly fade from Factory. Meanwhile, some pkg upstreams already >>> stopped caring for py2k, so their pkgs simply stay with the last working >>> version. Currently it's more manual work, I agree. >> >> Just saw this interesting data-point - Fedora is going to switch to >> Python 3 by default: >> >> http://lwn.net/Articles/571528/ > > Jupp. I guess it's more obvious for Fedora than us since they always want to > be bleeding edge. But what does that mean in reality? They're not likely going > to ditch py2 any time soon. there's just far too much software out there that > needs it. Since RH did a wise choice in standardizing on Python for most of > their tooling, I'd bet they would have to port a whole lot of stuff first. So > in the end it boils down to what /usr/bin/python points too. On openSUSE, it's > the same as /usr/bin/python-2.7. I thought about changing this and we > discussed this in length. Finally, we decided against it [0]. Others than > that, py3k is in very good shape inside 13.1 and will get more packages during > the next dev cycle. > > [0] http://lists.opensuse.org/opensuse-packaging/2013-08/msg00089.html IMHO, we need the first step: separate - the (very) Good (python ver does not matter) - the nice (need either py2 or py3 and be honest about) - the bad (work only with one special python version) - the ugly (need either py2 or py3 and tell not, or lie about) The Good is what we want to prefere, they can point to /usr/bin/python . The nice need to point to either /usr/bin/python2 or /usr/bin/python3 . The bad will have to point to a more specific version, e.g. /usr/bin/python2.7 and need to have a special cared for spec file. Goal would be to get them to the nice point. The ugly, well they will need work, no matter what. The more cleanly defined the needs of a package are the easier it will be to handle it in the long run. We will need a time with a (peacefull) coexistence of python 2 and 3 . Having the programs point to either python2 or python3 is a step in the right direction, and helps to keep the hassle down. Some packages (e.g. calibre) will need special care, no matter what. Our goal should be raising sensitivity upstream. Having them in the know and care about this lowers the problem for all distros. The trouble will be getting some of upstream to care about this. Thats my 2ct on this. - Yamaban. -- 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] user@.service was unmasked after zypper dup
by Andrey Borzenkov 04 Nov '13

04 Nov '13

I masked user@.service after update to RC1 because it was reliably causing long delay on shutdown (https://bugzilla.novell.com/show_bug.cgi?id=841544) After zypper dup recently I observed the same delay and was surprised to see user(a)0.service running again. Is not "systemctl mask" presumed to be persistent? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1