December 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] openSUSE:Factory:NonFree repository
by Kyrill Detinov 03 Jul '15

03 Jul '15

Hello. /factory/repo/non-oss/ isn't updated since September 23. -- WBR Kyrill

4 9

[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] Tumbleweed: systemd cannot start privoxy
by Patrick Shanahan 30 Oct '14

30 Oct '14

up to date Tumbleweed (13.1) systemctl start privoxy 18:26 Crash: ~ # systemctl start privoxy Job for privoxy.service failed. See 'systemctl status privoxy.service' and 'journalctl -xn' for details. 18:27 Crash: ~ # systemctl status privoxy privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; disabled) Active: failed (Result: exit-code) since Wed 2013-11-20 18:27:09 EST; 15s ago Process: 9430 ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy /etc/privoxy/config (code=exited, status=1/FAILURE) Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. 18:27 Crash: ~ # journalctl -xn -- Logs begin at Sat 2013-03-30 18:27:22 EDT, end at Wed 2013-11-20 -- 18:27:35 EST. -- Nov 20 18:27:08 Crash systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... -- Subject: Unit privoxy.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit privoxy.service has begun starting up. Nov 20 18:27:09 Crash systemd[1]: privoxy.service: control process exited, code=exited status=1 Nov 20 18:27:09 Crash systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. -- Subject: Unit privoxy.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: -- http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba4… -- -- Unit privoxy.service has failed. -- -- The result is failed. Nov 20 18:27:09 Crash systemd[1]: Unit privoxy.service entered failed state. Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51684 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:15 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=282 TOS=0x00 PREC=0x00 TTL=64 ID=51685 DF PROTO=UDP SPT=631 DPT=631 LEN=262 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51686 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:34 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=247 TOS=0x00 PREC=0x00 TTL=64 ID=51687 DF PROTO=UDP SPT=631 DPT=631 LEN=227 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51688 DF PROTO=UDP SPT=631 DPT=631 LEN=243 Nov 20 18:27:35 Crash kernel: SFW2-INext-ACC-TRUST IN=eth0 OUT= MAC= SRC=192.168.1.10 DST=192.168.1.255 LEN=263 TOS=0x00 PREC=0x00 TTL=64 ID=51689 DF PROTO=UDP SPT=631 DPT=631 LEN=243 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 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

9 20

[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] Your thoughts on dropping pm-utils
by Vojtěch Dziewięcki 13 Jan '14

13 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I maintain pm-utils, and I want to drop them soon, because systemd can handle (sort of) suspend and hibernation and also becouse their upstream is dead and I'm not able to (and don't want to) fix all the bugs all by myself. There is some information and an initial discussion on the topic here: https://bugzilla.novell.com/show_bug.cgi?id=790157 The current state is that pm-utils are sort of "plugged in" to systemd and are called from systemd to perform suspend and hibernate, if they are installed. Doesn't work too well. So I'm interested in other people's opinions on how this should be done and in particular what hooks you would like to see rewritten as systemd units, since I can usually do that. IMO the most important hook is 99Zgrub that prevents to boot another OS if we have hibernated, I've already rewritten that one, if someone wants to look at it or test it (just put it in /usr/lib/systemd/system-sleep, hibernate without pm-utils and see if the grub menu appears when you turn the computer on - it shouldn't) , here's the link: http://bugzillafiles.novell.org/attachment.cgi?id=569356 I just modified it at the end, so it works as a systemd unit, but all the functions are the same as in 99ZGrub from pm-utils. I also think it would be nice to have a "transitional period", when pm-utils won't be used as default, but if someone would be unhappy with using systemd for suspending, pm-utils could be installed. So please share your thoughts on this. I also realize there are people who would like to keep pm-utils, but unfortunately I'm not able to fix those bugs any more, so if someone wants to disagree with dropping pm-utils, that person would have to become the maintainer and fix all the bugs (or find someone else to do it), because I can't and don't want to, thanks for understanding. Wojtek Dziewięcki -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSlhzWAAoJEHrcxBn8c1xjNVMH/2qvaIUSxUz/wtCBPqSmhlv9 nJXyrst1/eM3WMA2cGt6+8DjpeNDq19Fs2j19H/WH4l1MPCyvW6R8b2UKwb++fPt RDJd4T6vKBaK46hzL6DNdigwf7JtSFJB7B69ohN85fNoSNyrzIzVtnQA0Cl5QGU8 SStmp0vy8n67WXKkOerszmpOqdpomUu+GPdy4OCcjbK2Z6VLnwBVGnFw4IcTNw2N Wu2U/Iplyt1e7mpueNOxFCQr3qJePlyqbHLeLRYi3ROshJiJycx/siyD8yB7WGa6 UmKHPj5a+Q2yZ2T9/gzZm5OmQscfum/jgPV+B4Uh53BudnW2wm75xPSuOQOyaQI= =b39f -----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

17 27

[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] Why is esound-daemon automatically installed on opensuse 12.3 when using zypper dup?
by Joop Boonen 04 Jan '14

04 Jan '14

Dear all, Today I did a sudo zypper dup. I saw: sudo zypper dup root's password: Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Retrieving repository 'openSUSE-12.3-Update' metadata ................................................................................[done] Building repository 'openSUSE-12.3-Update' cache .....................................................................................[done] Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW package is going to be installed: esound-daemon The following packages are going to be upgraded: As I wondered why esound-daemon was installed I've checked out what package needs this package: rpm -q --whatrequires esound-daemon no package requires esound-daemon I've deleted this package via: rpm -evh esound-daemon Preparing... ################################# [100%] Cleaning up / removing... 1:esound-daemon-0.2.41-23.1.1 ################################# [100%] without any problems. I wonder why esound-daemon is automatically installed? Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 5

[opensuse-factory] smpppd anyone?
by Ludwig Nussel 02 Jan '14

02 Jan '14

Hi, Is anyone interested in maintaining smpppd? My personal usecase is gone so I have no use for smpppd anymore. If no one steps up I'll request dropping it from Factory. 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

13 24

[opensuse-factory] Possible 3.13-rc nouveau regression with GT 560 Ti
by Sid Boyce 02 Jan '14

02 Jan '14

System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said "nouveau Playlist update failed". Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 10

[opensuse-factory] Cannot fetch build logs from OBS
by Andrey Borzenkov 28 Dec '13

28 Dec '13

I get bor@opensuse:~/obs/home:arvidjaar:grub2-next/grub2> osc rblt home:arvidjaar:grub2-next/grub2 openSUSE_Factory x86_64 Server returned an error: HTTP Error 400: remote error no socket attached remote error: no socket attached for any repository. Also logs are not available post-builds as well. -- 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] Replace laptop-mode-tools with tuned
by denisart benjamin2 22 Dec '13

22 Dec '13

Hello everyone, I don't come back on old reasons of purposing tuned as a laptop-mode-tools replacement. Actually, the maintainer of pm-utils want's to drop pm-utils and laptop-mode-tools requires it to work correctly. That why we need to replace it with tuned https://features.opensuse.org/314309 Regards. Benjamin -- 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] O Factory - Where art Thou?
by Stephan Kulow 20 Dec '13

20 Dec '13

Hi It's Thanksgiving today and we had a great harvest - "Bottle" rocks. But today is also a good time to plant new seeds for even better openSUSE releases. Factory has a healthy growth, but we have to make sure it's growing in the right direction and so the openSUSE team at SUSE had an on-and-off discussion basically since 12.3 on how to improve things. But first let me give you some background, that you might not be aware of: 10.3 had 3334 packages, 11.1 3746, 3605 for 11.2, 3807 for 11.3, 4784 in 12.1, 5710 in 12.2, 6246 in 12.3, 6678 in 13.1, 6800 right now in Factory. If you need a picture, look at http://s.kulow.org/packages Integrating these to make a good distribution is real work. And one of my favourite songs (in that context) goes: No one said it would be easy But no one said it'd be this hard No one said it would be easy No one thought we'd come this far In that song Sheryl Crow sings "It's just a question of eliminating obstacles", so what did we in the openSUSE Team do to help? We focused on getting a grip on testing by improving openqa (http://s.kulow.org/openqa-blog) but we soon found out that it was not good enough to test Factory ISOs. Factory is broken often enough not to produce ISOs at all, ISOs can't be installed and once these problems are sorted out, we found in openqa very basic things to be broken, but it was too late to protect factory users to run into them. One thing I tried was to setup "rings" to help easing the very painful staging projects (with 6800 packages, every staging project as we use them is a monster). That experiment has shown rings to be worthy way to check, but they won't work as I thought with the OBS as it is. We need to think bigger. So we tried to come up with an idea on how to improve the factory development process that includes a more clever way to utilize staging projects and openQA. As this development process is a bit hard to explain in email, Alberto and Ancor prepared an interactive diagram: https://progress.opensuse.org/workflow/factory-proposal.html We basically want to put the pressure on the submitting packager not the user. Using factory should be safe, for this we want to revive a thing that has been lost on the way: Bernhard's factory-tested project. And we want to open another submission path: from staging projects. Consider a situation where recent updates to GNOME and automake 'clash', causing problems when they're installed together. Right now we throw both into Factory, breaking both for our Factory users until we solve the issues. Instead, we think working on these issues in a separate 'staging project' could be the solution. None of us knows how *exactly* it will look alike because we need to get a conversation with the OBS team going. But the basic idea is: - GNOME:Factory stays the devel project of things that relate to GNOME updates - devel:tools stays the devel project of things that relate to automake updates - on automake updates, we open up a new devel project that stages GNOME packages for the new automake. In there, GNOME devs and automake experts work together to fix them and updates in there are submitted either back to GNOME:Factory and are integrated right into Factory. Or if that's not possible, the automake update is "grouped" with various GNOME package updates and these updates end in Factory together. There are several problems with the current "everything through devel project" approach we need to solve. Our ideas are just ideas, but I had several discussions in various places and nobody offered a better idea. So we really would like to start with it and I would like to hear your concerns so they can be part of the final solution. We have more ideas, but we can only achieve that if we get help, so let me finish with another favourite of mine What would you think if I sang out of tune? Would you stand up and walk out on me? Lend me your ears and I'll sing you a song And I'll try not to sing out of key Oh, I get by with a little help from my friends Greetings, Stephan -- Ignorance is when you don't know anything and somebody finds it out. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

32 132

[opensuse-factory] Re: Up coming changes to Enlightenment (e16, e17, e18) + libraries
by Tomas Cech 20 Dec '13

20 Dec '13

Hi, On Thu, Dec 19, 2013 at 12:07:13PM +1030, Simon wrote: > Hi All, > before everyone heads off for Christmas / summer / winter breaks, i'd like > to give a heads up of some changes coming to openSUSE:factory over the > next few weeks we will try to limit breakages however some temporary > issues may be unavoidable. > Firstly the existing enlightenment package will be removed and replaced > with one called e16, this is the only change for e16 users i'll get back > to whats happening with the enlightenment package in a little bit. > > The biggest change will be to the enlightenment foundation libraries (efl) > used by e17, e18 and terminology. As of efl 1.8 all the components of the > efl with the exception of elementary are shipped as one source tar and are > built together as such we have added one new package efl and will be > removing the following packages, eina, eet, evas, eio, emotion, efreet, > e_dbus, embryo, edje and eeze. E_dbus is exception here as it is still needed for e17 to run. But that is OK, because single-source efl doesn't contain it. > As not all the extra modules / themes are available with e18 and because > it requires compositing to be enabled we have had some requests to keep > e17 around. For now we will be keeping e17 pretty much as is but probably > at version 0.17.6 instead of 0.17.3 unless it is found unusable by a > number of people, it will also build from the new efl package rather then > the older split libraries. > > Enlightenment e18 will be built in the enlightenment package, this is > because upstream have indicated they would like to do a new release at > least every year possibly less and i don't want to change the package name > that often. I will try and come up with a way for e17.3 in 13.1 to > automaticlly update to the new enlightenment e18 package that doesn't ask > people who are using e17.6 from 13.2 to update, if someone could help with > that it would be great, i don't know how to do it. > > Previously themes were named e-theme-* and modules e-module-* as themes > and modules need to be built against the right version of enlightenment > the package naming will change to e17-module-* and e17-theme-* for e17 and > enlightenment-module-* and enlightenment-theme-*, e17 users who use > terminology will also need both the e17 and enlightenment theme as e18 and > later themes are used by the libraries as well > > Currently we don't plan to keep e18 around when e19 etc come out like we > have with e16 and e17. > > Summary of changes: > Stage 1 (Basics): > * Add efl > * replace existing enlightenment package with e16) > Stage 2 (core components) > * Update elementary, terminology and e17 to use efl rather then older > libs. > * add new enlightenment package > Stage 3 (everything else) > * replace / add modules, themes and branding > * update other packages i forgot about. > * remove old libraries Thanks for this mail. Until all the changes will be done, EFL and E17 + E18 is expected to be broken. Sleep_Walker

2 1

[opensuse-factory] nVidia repo for 13.1 missing?
by Jim Henderson 19 Dec '13

19 Dec '13

A few days ago, the repository hosted by nVidia for their drivers for oS 13.1 was made available, but the directory seems to have gone missing - anyone know what happened, or who to contact/notify? We've had a couple questions on the forums about this. Thanks. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 31

[opensuse-factory] Upcoming changes to Enlightenment (e16, e17, e18) + libraries, Includes package add remove and rename
by Simon 19 Dec '13

19 Dec '13

Hi All, before everyone heads off for Christmas / summer / winter breaks, i'd like to give a heads up of some changes coming to openSUSE:factory over the next few weeks we will try to limit breakages however some temporary issues may be unavoidable. Firstly the existing enlightenment package will be removed and replaced with one called e16, this is the only change for e16 users i'll get back to whats happening with the enlightenment package in a little bit. The biggest change will be to the enlightenment foundation libraries (efl) used by e17, e18 and terminology. As of efl 1.8 all the components of the efl with the exception of elementary are shipped as one source tar and are built together as such we have added one new package efl and will be removing the following packages, eina, eet, evas, eio, emotion, efreet, e_dbus, embryo, edje and eeze. As not all the extra modules / themes are available with e18 and because it requires compositing to be enabled we have had some requests to keep e17 around. For now we will be keeping e17 pretty much as is but probably at version 0.17.6 instead of 0.17.3 unless it is found unusable by a number of people, it will also build from the new efl package rather then the older split libraries. Enlightenment e18 will be built in the enlightenment package, this is because upstream have indicated they would like to do a new release at least every year possibly less and i don't want to change the package name that often. I will try and come up with a way for e17.3 in 13.1 to automaticlly update to the new enlightenment e18 package that doesn't ask people who are using e17.6 from 13.2 to update, if someone could help with that it would be great, i don't know how to do it. Previously themes were named e-theme-* and modules e-module-* as themes and modules need to be built against the right version of enlightenment the package naming will change to e17-module-* and e17-theme-* for e17 and enlightenment-module-* and enlightenment-theme-*, e17 users who use terminology will also need both the e17 and enlightenment theme as e18 and later themes are used by the libraries as well Currently we don't plan to keep e18 around when e19 etc come out like we have with e16 and e17. Summary of changes: Stage 1 (Basics): * Add efl * replace existing enlightenment package with e16) Stage 2 (core components) * Update elementary, terminology and e17 to use efl rather then older libs. * add new enlightenment package Stage 3 (everything else) * replace / add modules, themes and branding * update other packages i forgot about. * remove old libraries Almost all the changes have already been made in the X11:Enlightenment:Factory Thanks for your time Simon (Simotek) Maintainer for enlightenment on openSUSE -- 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] Playing again with rings
by Stephan Kulow 19 Dec '13

19 Dec '13

Hi, Trying to find more options for the staging workflow, I played again with the ring idea. The rings I have so far are: openSUSE:Factory:Build the minimal bootstrap cycle gcc,binutils, ... (106 packages) openSUSE:Factory:Core packages required for DVD with minimalx installation (976 packages). This DVD is 522 MB at the moment and we have already openQA support for running the minimalx installation on it. openSUSE:Factory:MainDesktops packages required to build GNOME and KDE Live media, this adds to the above alot of the desktop stuff including java and libreoffice (817 packages) The next ring I'd add is a project that builds the x86_64 DVD. This will include quite some packages (at least 1050 are needed to build it right now). So we had ~3000 packages in rings - the 3800 packages in factory not in one of these rings would be in a "nice to have" ring. The idea would be then: - packages in "nice to have" don't get any staging - packages in rings need to build the rings up. If it's a :Build package, it first needs to prove :Build is green, then build :Core's minimal DVD, test it in openqa, then MainDesktop Live CDs, test, then DVD, test -> profit. Every package only has to prove it's greenness for the state it submitted to. For longer running projects we need to rebase, but not in the usual case. The rest of the ideas from Michal's staging concept still apply of course. E.g. we need to find a way to group the packages *before* we create the staging projects. Greetings, Stephan -- 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] OpenSUSE 13.1 on ThinkPad X60s
by Thorolf Godawa 18 Dec '13

18 Dec '13

Hi everybody, it's not "really" factory anymore, but I think it should work, because I don't have the problems with 12.1 and I havn't found any solution right now. I'm trying to install openSUSE 13.1 on a ThinkPad X60s (CoreDuo, Intel 950 graphics, Intel 3945ABG wifi, SanDisk 128GB SSD). The installation went through mostly fine, all hardware was detected correctly but I was not able to establish a wifi-connection during installation (shows SSIDs for available APs, but does not get an IP), so I went for cable to finish the installation including all available updates. On next reboot, it takes quite long (>60s) to go over the Grub showing the boot menu and even worse, the system is not booting into runlevel 5 at all, last message seen is "Started SuSEfirewall2 phase 2". I can change to an other console, after connecting a cable I have working network and I can start XFCE4 manually from there. Now I am also able to connect to my wifi-network, using the NetworkManager. I can get over the "Started SuSEfirewall2 phase 2" if I switch the network from NetworkManager to ipup, but then I'm not able to get a Wifi connection anymore (only SSIDs viewable, but no IP-connection). Any idea what I can check to solve this problem? I'm using 13.1, because it should be a "evergreen" version, while I was a SuSE user for long time, I stopped using it some time ago, because I was not willing to do frequent distribution upgrades, so "evergreen" seems to be a good option for me. -- kind regards, Thorolf -- 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] up zypper/libzypp wants to remove YaST
by Felix Miata 17 Dec '13

17 Dec '13

Is there an ETA on this not happening any more? I don't see a bug opened on it. -- "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

1 0