April 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Another 'fun' build failure case in Factory
by Dimstar / Dominique Leuenberger 23 Apr '13

23 Apr '13

Hi all, another fun story you might be running in while looking at build failures. In factory, %{optflags} now contains "-grecord-gcc-switches". A bunch of 'funny' configure and make scripts try to be smart and, if for example built with --disable-build, replace -g in CFLAGS with '' using most stupid sed syntax. The result? gcc -grecord-gcc-switches main.c -o myCoolApp becomes gcc record-gcc-switches main.c -o myCoolApp => and there is (hopefully in call cases) no file called record-gcc-switches, and thus the build fails. In most cases this is visible in the error message (gcc: record-gcc-switches does not exist). In some cases this is a bit deeper burried. Again, I think I hit most cases in Factory and sent proposal SRs to the dev projects.. up to the maintainers to decide if they like the fixes (usually I just removed this mangling... even with --disable-debug, we usually want -g specified so we can get meaningful -debuginfo packages) Happy hacking... and happy chasing bugs! Dominique -- 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] pkg-config 0.28 / minor change (and broken configure checks)
by Dimstar / Dominique Leuenberger 22 Apr '13

22 Apr '13

Hi all, I've been looking at some odd build failures in Factory this evening and could mostly pint it down to very poorly written checks in configure. Look for example at: pkg="openssl" verssl=`(pkg-config --modversion $pkg) 2>/dev/null` if [[ "x$verssl" = "x" ]]; then pkg="libssl" verssl=`(pkg-config --modversion $pkg) 2>/dev/null` fi incssl=`(pkg-config --cflags $pkg) 2>/dev/null` libssl=`(pkg-config --libs $pkg) 2>/dev/null` if [[ "x$incssl" != "x" -a "x$libssl" != "x" ]]; then HAVE_OPENSSL=yes OPENSSL_VER="$verssl" OPENSSL_INC="$incssl" OPENSSL_LIB="$libssl" else verssl="no" fi It's visible that pkg-config --cflags $pkg can very well return empty, in case there are no special flags. the 'difference' between pkg-config 0.27 and 0.28 is that up to 0.27, there used to be a bogus space returned... which was fixed in 0.28; of course, now everybody will claim how bad it is to fix bugs which people rely on; this mail was not meant to start anything like this... merely as a heads-up if you run across similar weird checks... The only way forward is to fix the broken checks... Dominique -- 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] which systemd version is in use by factory?
by Yamaban 22 Apr '13

22 Apr '13

Hello together, when one looks at this page: http://software.opensuse.org/package/systemd and opens the section for "openSUSE Factory" one gets the line: "official release 44 ..." for "openSUSE 12.3" the correct entry is shown: "official update 195 ..." dito for "openSUSE 12.2" "official update 44 ..." My question is where does the version 44 for factory come from? Another question: would it be possible to enable to enable the repository openSUSE_12.3 for systemd in Base:System, atm it's disabled and I'd like to test systemd 202 on OSS 12.3 without opening the can of worms that is Factory on a production system without good cause. (If it's not possible, please say so.) see: https://build.opensuse.org/package/binaries?package=systemd&project=Base%3A… Thank you, Yamaban. -- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 9

[opensuse-factory] How to revoke request for non-existing project?
by Andrey Borzenkov 22 Apr '13

22 Apr '13

bor@opensuse:~> osc rq revoke -f 163452 Log message not specified a)bort, c)ontinue, e)dit: c Server returned an error: HTTP Error 404: Not Found openSUSE:Maintenance:1577 bor@opensuse:~> I do not mind much, but it shows every time I log into OBS, so I'd like to remove it if at all possible. -- 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] Fwd: Issue with BOOST ?
by Raymond Wooninck 22 Apr '13

22 Apr '13

Hi, Since yesterday and today, I got issues with boost. I guess this is due to the published factory on Friday, but at this moment I see a couple of packages (including KDEPIM4) failing with the following error: usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN" Is anybody aware of this error and more importantly can we expect a fix ? 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

4 3

[opensuse-factory] rsyslogd is not stopped on package uninstall
by Marcos Felipe Rasia de Mello 22 Apr '13

22 Apr '13

Using openSUSE 12.3 here. When I replace rsyslog with systemd's journal $ sudo zypper -v in systemd-logger -rsyslog -syslog-service the rsyslogd daemon keeps running after the package uninstall. Is this right? Should not RPM %service_del_preun macro run "systemctl stop" on it? Zypper output: Verbosity: 1 Non-option program arguments: 'systemd-logger' '-rsyslog' '-syslog-service' Initializing Target Checking whether to refresh metadata for openSUSE-12.3-Non-Oss Checking whether to refresh metadata for openSUSE-12.3-Oss Checking whether to refresh metadata for openSUSE-12.3-Update Checking whether to refresh metadata for openSUSE-12.3-Update-Non-Oss Loading repository data... Reading installed packages... Force resolution: No Selecting 'systemd-logger-195-13.18.1.x86_64' from repository 'openSUSE-12.3-Update' for installation. Selecting 'rsyslog-7.2.5-2.2.1.x86_64' for removal. Selecting 'syslog-service-2.0-768.2.1.noarch' for removal. Resolving package dependencies... Force resolution: No The following NEW package is going to be installed: systemd-logger 195-13.18.1 The following packages are going to be REMOVED: rsyslog 7.2.5-2.2.1 syslog-service 2.0-768.2.1 1 new package to install, 2 to remove. Overall download size: 90.7 KiB. After the operation, 1.8 MiB will be freed. Continue? [y/n/?] (y): committing Retrieving package systemd-logger-195-13.18.1.x86_64 (1/1), 90.7 KiB ( 1.6 KiB unpacked) Retrieving: systemd-logger-195-13.18.1.x86_64.rpm [.done] (1/3) Installing: systemd-logger-195-13.18.1 [......done] (2/3) Removing rsyslog-7.2.5-2.2.1 [....done] (3/3) Removing syslog-service-2.0-768.2.1 [....done] committingCommitResult (total 3, done 3, error 0, skipped 0, updateMessages 0) Checking for running processes using deleted libraries... There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. $ sudo zypper ps The following running processes use deleted files: PID | PPID | UID | Login | Command | Service | Files -----+------+-----+-------+---------+---------+------------------------------- 1522 | 0 | 0 | root | rs:main | | /usr/lib64/rsyslog/lmnet.so | | | | | | /usr/lib64/rsyslog/immark.so | | | | | | /usr/lib64/rsyslog/imuxsock.so | | | | | | /usr/lib64/rsyslog/imklog.so | | | | | | /usr/sbin/rsyslogd (deleted) You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 13

[opensuse-factory] Issue with Boost ?
by Raymond Wooninck 21 Apr '13

21 Apr '13

Hi, Since yesterday and today, I got issues with boost. I guess this is due to the published factory on Friday, but at this moment I see a couple of packages (including KDEPIM4) failing with the following error: usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN" Is anybody aware of this error and more importantly can we expect a fix ? 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

1 0

[opensuse-factory] no publish for > 10 days ?
by Cristian Rodríguez 20 Apr '13

20 Apr '13

Hi: Last factory update was on April 8.. is this intended or there is some hardware/software problem in the OBS ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] codelite, new proposal for Factory
by Mariusz Fik 19 Apr '13

19 Apr '13

Hi, I maintain codelite package[1] in devel:tools:ide for some time. Now I'd like to push package to Factory. But I hit some wall because devel:tool:ide is not Factory devel project. What steps are necessary to move forward? [1] - https://build.opensuse.org/package/show?package=codelite&project=devel%3Ato… -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

3 5

[opensuse-factory] GSOC 2013 - call for mentors: external boot selection for Grub2
by okordy 19 Apr '13

19 Apr '13

Hi, I want to take part in GSOC working for opensuse, so I have posted my ideas here: http://lists.opensuse.org/opensuse-project/2013-04/msg00057.html Someone answered me, that I should discuss it here and call for mentors. My idea: external boot selection sources for Grub2 (windows; serial port) This is rather cross-distribution topic, but may require creating distribution-specific tools (which could be incorporated to grub project, if they wants to). Problem scenario #1: I'm working (at the moment) on Windows, installed an system update and want to reboot. So, I click "reboot" and go to the kitchen to make a cup of tea. When I come back, linux is started, because it was default selection and grub booted into it. Problem scenario #2: My PC is shut down and I want to boot into Windows. I press "power" and wait for system to boot. BIOS takes some time to check the hardware, grub waits 3 seconds for OS selection and... I'm late for selecting Windows, because I was disturbed for a moment by something else. Problem scenario #3: I want to boot my PC remotely to Windows, using Ethernet card boot feature. I have to boot into default system (linux) first, then reboot into Windows. Common problem: I have to stare at monitor during boot process, to not overlook Grub menu - if I miss it, I waste lots of time to wait for reboot to correct OS. Suggested solution: I wanted to implement simple-to-use tools to make it possible to: - select "reboot to" OS directly from Windows (like it's currently done in opensuse) - this would include preparing configuration tool for linux (to setup grub, or windows app, if needed), patching grub itself (also, if needed) and implementing Windows application, which would let select next boot-once OS for Grub and reboot PC. Such Windows tool would be splitted into at least two components: pure command-line tool just to set boot-once setting and GUI app to easily use it. - (optional) make it possible to control grub via physical device (connected, for example, via serial port). It would make it possible for user to build a simple-as-possible switch, which would let him select OS *before* powering on or rebooting PC - (optional, I'm not sure if it's possible to do it during GSoC, or won't require too much dependencies) make it possible to select OS when booting from Ethernet card Is there anyone interested in mentoring this idea? Any comments? Thanks, okordy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1