December 2013 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] python issue I don't understand
by Dmitriy Perlow 28 Dec '13

28 Dec '13

Hi. There are no Internet access from build machine. Your package' postin shouldn't use it. ______________ Dmitriy Perlow via SE J10i

1 0

[opensuse-packaging] factory openssl and ec
by Matwey V. Kornilov 21 Dec '13

21 Dec '13

Hi, Why has elliptic curve cryptography been disabled in factory openssl? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] 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-packaging] 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-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] keep services enabled during upgrade
by Olaf Hering 18 Dec '13

18 Dec '13

What is the best way to keep an already enabled sysv runlevel script enabled when the package moves from sysv init scripts to .service files? To me it looks like having the service file listed in the preset-branding files is not enough when doing rpm -Fvh X.rpm. The result is a disabled service if the previous version of X.rpm had an active /etc/init.d/X and the current version has a X.service. I'm forced to run 'systemctrl start X.service' after every reboot. Would at least a "zypper dup" allow that because it sets YAST_IS_RUNNING? Olaf -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] New OBS notification mails
by Adrian Schröter 17 Dec '13

17 Dec '13

Hi, coolo and Christopher Hofmann created an initial implementation of notification support in OBS. In the long run we want to obsolete hermes.o.o with that approach in the hope that we can offer * improved email content * in the right situations * and way better direct integration in OBS, without the need to change interfaces. For a smooth migration, we want to enable the emails in OBS next week, while we will also de-register the notifications in hermes at the same point of time. There is also already a very-very first interface in build.opensuse.org where you can configure your notifications already (but it will have no effect until we enable the mail delivery): https://build.opensuse.org/user/notifications We know that the interface is not yet designed under usability aspects, the functionality was our first goal. But an improved interface and more optoins will come for sure. thanks adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 15

[opensuse-packaging] EXE-File of mono application is not included in OBS generated package
by Dirk Brünig 15 Dec '13

15 Dec '13

Hello I try to packaging the mono application Tracer2Server for openSUSE. https://build.opensuse.org/package/show/home:dBruenig:Tracer2Server/Tracer2… But I still have some issues I don't understand. 1. EXE-File of mono application is not included The generation of i586 package ends with succeeded. But in the RPM file the tracer2server.exe is not included. I don't know way this happens. Because the compilation succeeded (13 warnings). 2. Package generation for x86_64 failed While the generation for i586 succeeded. The generation for x86_64 failed. So where are the difference between these too. I am a newbie in Linux, so please help me to get this working. Regards Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8

[opensuse-packaging] OBS storage system problems, home:* areas currently disabled.
by Adrian Schröter 14 Dec '13

14 Dec '13

Hi, due to storage system problem, I am unable to solve atm, I have disabled access to home:* projects binary area. This make the entire system working again at least, but it means you have currently no access to build results of home:* projects. we will fix that asap ... have a nice weekend and grab a Glühwein instead :) adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] factory-repo-checker and noarch packages
by Jean Delvare 13 Dec '13

13 Dec '13

Hi all, hi Stephan, I am trying to submit quilt to openSUSE:Factory. It gets rejected by factory-repo-checker with the reason: quilt is disabled or does not build against factory. Please fix and resubmit Quilt is enabled against openSUSE_Factory in devel:tools:scm, but only for x86_64. It is a noarch package so I see no reason to waste build resources to build it on more than one architecture. I suspect this is the reason for the reject above. Can we please fix factory-repo-checker so that it is happy with noarch packages as long as they are enabled on at least one architecture and do not fail to build on any architecture? Thanks, -- Jean Delvare Suse L3 Support -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] not dissolubles dependences - oS 13.1 RC 1 - Updates
by Jens 13 Dec '13

13 Dec '13

hi all Hoping you are my right address I send you "conflicts.txt" for 13.1 RC1 (down) Please look too for acroread -> ask for libidn.so11 it is on the DVD and installed if wanted -> syslog-ng -> ask for libevtlog.so. -> libnet.so1 I tell you, libevtlog is only in eventlog from feodora There is also a Problem with amarok-Update (?) sorry for my english Thank you Regards Jens conflicts: #### YaST2 conflicts list - generated 2013-10-21 09:31:20 #### libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von digikam-3.4.0-2.1.4.x86_64 [ ] veraltetes digikam-3.4.0-2.1.4.x86_64 behalten libkdecore.so.5, benötigt von kipi-plugins-3.5.0-2.4.2.i586, wird von keinem Repository angeboten [ ] veraltetes kipi-plugins-3.4.0-2.1.4.x86_64 behalten [ ] kipi-plugins-3.5.0-2.4.2.i586 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von kipi-plugins-3.4.0-2.1.4.x86_64 libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] veraltetes kipi-plugins-acquireimage-3.4.0-2.1.4.x86_64 behalten [ ] Deinstallation von kipi-plugins-acquireimage-3.4.0-2.1.4.x86_64 libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von kipi-plugins-geolocation-3.4.0-2.1.4.x86_64 [ ] veraltetes kipi-plugins-geolocation-3.4.0-2.1.4.x86_64 behalten #### YaST2 conflicts list END ### conflicts.txt #### YaST2 conflicts list - generated 2013-10-21 09:31:20 #### libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von digikam-3.4.0-2.1.4.x86_64 [ ] veraltetes digikam-3.4.0-2.1.4.x86_64 behalten libkdecore.so.5, benötigt von kipi-plugins-3.5.0-2.4.2.i586, wird von keinem Repository angeboten [ ] veraltetes kipi-plugins-3.4.0-2.1.4.x86_64 behalten [ ] kipi-plugins-3.5.0-2.4.2.i586 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von kipi-plugins-3.4.0-2.1.4.x86_64 libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] veraltetes kipi-plugins-acquireimage-3.4.0-2.1.4.x86_64 behalten [ ] Deinstallation von kipi-plugins-acquireimage-3.4.0-2.1.4.x86_64 libQtGStreamer-0.10.so.0()(64bit), benötigt von kipi-plugins-3.5.0-2.4.2.x86_64, wird von keinem Repository angeboten [ ] kipi-plugins-3.5.0-2.4.2.x86_64 beschädigen durch Ignorieren einiger Abhängigkeiten [ ] Deinstallation von kipi-plugins-geolocation-3.4.0-2.1.4.x86_64 [ ] veraltetes kipi-plugins-geolocation-3.4.0-2.1.4.x86_64 behalten #### YaST2 conflicts list END ### -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 9