May 2016 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] receiving files via bluetooth fails
by Olaf Hering 24 Sep '17

24 Sep '17

Some months ago it was possible to receive files via bluetooth with TW. But since some weeks that fails for me. I waited for GNOME 3.20 and the new bluez in the hope it will fix itself, but the failure remains: Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff) Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0x0) Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), (null)(0xffffffff) Apr 05 18:01:32 probook obexd[3042]: open(/home/olaf/.cache/obexd/GSIBFY): No such file or directory (2) Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), NOT_FOUND(0x44) Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff) Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20) Apr 05 18:01:32 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Apr 05 18:01:32 probook obexd[3042]: disconnected: Transport got disconnected Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0x0) Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: open(/home/olaf/.cache/obexd/1OLQFY): Operation not permitted (1) Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), FORBIDDEN(0x43) Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20) Apr 05 18:02:42 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Apr 05 18:02:42 probook obexd[3042]: disconnected: Transport got disconnected First I tried to remove /home/olaf/.cache/obexd, but nothing seems to feel responsible to create this dir as seen with the first error. Then I created it with mkdir -m07777, and that just gives the EPERM error as before. strace shows that it gets some "forbidden" from dbus. Is receiving files working for anyone else? Also the rfkill thing does not work reliable. NetworkManager finds the device according to syslog, but the GNOME bluetooth thing finds nothing. Something softblocks it: root@probook:~ # hciconfig -a hci0 reset Can't init device hci0: Operation not possible due to RF-kill (132) root@probook:~ # rfkill list all 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: yes Hard blocked: no Need to run 'rfkill unblock 4' manually to get it going. Once that it done its appearently possible to use the UMTS, and sending a file works as well. Olaf -- 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] How can calibre be allowed access through YaST firewall?
by Chan Ju Ping 24 Sep '16

24 Sep '16

Unlike rsync, or KDE Connect, there is no option to automatically allow the Calibre ebook manager to open ports so external devices can connect to it. So far, my solution has been to disable the firewall before connecting my device to Calibre via the Calibre Companion app on Android. For those unfamiliar with the process, Calibre Companion can sync ebooks from the desktop's library to the Android device's library, thus eliminating the need for wires and further organization of books. If I know I am using port 9090 for Calibre, is there a way to allow this connection in the Firewall? Has anyone else attempted this setup? Running netstat shows this additional parameter enabled when my tablet is connected to the computer. tcp 0 0 10.42.0.1%2457529:39858 10.42.0.250%328:sesi-lm ESTABLISHED

3 8

[opensuse-factory] Gstreamer*0.10* for sale!
by Bjørn Lie 07 Sep '16

07 Sep '16

More than 3 years ago upstream said enough is enough and pulled the plug on gst-0_10 branch, and ever since then we the gnome-maintainers have been carrying around the abandoned packages, both because we care and at the time of upstreams kill-off point we had a lot of packages depending on them. Since then we have quietly been porting the ones we care about or dropping them from Tumbleweed. We have however now reached a point where we can not in good conscious say that we care for gst-0_10 at all anymore, and would as a result offer up maintainership of said packages for those that still depend on them / want them to stay in Tumbleweed. Currently osc whatdependson openSUSE:Factory gstreamer-0_10 standard x86_64 gives this list [see end of email] of depending packages. If you as a maintainer are affected, please consider stepping up and requesting maintainer via obs or email. The above said, maintenance burden is not very high currently, so don't fear taking responsibility, it mainly consists of tweaking packages to ensure their continued build. As a maintainer though I'd prefer that we could drop gst-0_10 from TW all the way, but acknowledge that this is not currently possible, but if everyone who have packages still depend on gst-0_10* do a real push to port or drop packages still dependent we could perhaps take the easy route out and just drop gstreamer-0_10. //Bjørn - on behalf of openSUSE GNOME maintainers. LIST: osc whatdependson openSUSE:Factory gstreamer-0_10 standard x86_64 gstreamer-0_10 : aegisub audacity boinc-client codelite e17 e_dbus echievements elementary elemines emotion-generic-players enlightenment eperiodique epymc erlang espeakedit etrophy evas-generic-loaders filezilla fityk flamerobin freqtweak gcompris gnuplot gnuradio gstreamer-0_10-plugin-crystalhd gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-base gstreamer-0_10-plugins-gl gstreamer-0_10-plugins-good gstreamer-0_10-plugins-ugly hugin ignuit kde3-amarok kde3-kaffeine kdemultimedia3 kicad lekha libucil mathgl meson moodbar morituri perl-Alien-wxWidgets perl-Wx pgadmin3 plplot poedit presage psi+-plugins-psimediaplugin python-efl python-gstreamer-0_10 python-matplotlib python-wxWidgets python-wxWidgets-3_0 rage sffview shellementary terminology tintii urbanlightscape usbprog wammu wxGTK3-3_0 wxMaxima wxWidgets wxWidgets-3_0 wxWidgets-ansi wxWidgets-wxcontainer wxWidgets-wxcontainer24c wxhexeditor xchm xfce4-mixer xfce4-volumed xylib -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 11

[opensuse-factory] Transitioning to GCC 6
by Richard Biener 25 Jul '16

25 Jul '16

You may have noticed that GCC 6 packages appeared in Factory (but gcc used for building packages still points to GCC 5). Somewhen in January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used to build packages. The status of that is that it depends on the glibc update pending in Staging:B and it still requires fixing a few packages, mostly -Werror related. There was a point in time where openQA was green for x86_64 (and Minimal-X). Once Staging:B has been accepted I'll formally submit an update to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6. That staging can nevertheless be used to look at the current FAILs which are build failed cluster-glue failed elfutils failed espeak failed gdb failed jack failed libyui failed llvm failed mozilla-nss failed pesign failed python3-base failed xen failed and can also be caused by the glibc update which I pulled into Staging:Gcc6. Any help is appreciated. Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 21

[opensuse-factory] Unable to boot from latest Tumbleweed-iso
by Jogchum Reitsma 22 Jul '16

22 Jul '16

-- 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] New package proposal: jgrep
by Dmitriy Perlow 20 Jun '16

20 Jun '16

Hello to all! I'd like to open a submit request with jgrep package to openSUSE Factory. It is a command-line grep-like utility written in Java. It supports Java regular expressions, RE2J, POSIX options (excluding -E and -G), most GNU grep(1) options, options -O, -2 and -8. However packaging is a bit tricky. 1) jgrep normally requires maven at build time but there are no maven at openSUSE Factory. 2) Maven requires about *teen plugins for jgrep and no one is packaged at all. That is why upstream and I decided to let maintainer make jar file and invoke it at %prep stage. Is *.jar bundling allowed at OBS? openSUSE Factory? [0] https://github.com/cheusov/jgrep [1] http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/textproc/jgrep # NetBSD package [2] https://build.opensuse.org/package/show/home:DarkSS:branches:devel:tools:bu… -- Best regards, Dmitriy Perlow R&D chemical engineer Lekpharm JLLC -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] Planned release schedule for Leap 42.2
by Ludwig Nussel 20 Jun '16

20 Jun '16

Hi, Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top. My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd. cu Ludwig [1] https://en.opensuse.org/Portal:42.1 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (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

9 17

[opensuse-factory] Leap 42.2 ARM: Ring 0 status
by Matwey V. Kornilov 06 Jun '16

06 Jun '16

Hello, Leap 42.2 Ring0 rebuilt for ARM is here: https://build.opensuse.org/project/monitor/home:matwey:experimental:Leap:42… The following changes have to be introduced: build: 1) apply https://github.com/openSUSE/obs-build/commit/2caf24a52292b0e23725d1821d48c4… to fix build on armv7 (this is common issue also for Factory) gcc5: 1) drop _constraints, they are never satisfied at armv7 libunwind: 1) apply c90a2e02b3c1b03362a549a05261a4d0513d6026 from upstream 2) apply 0bed10aa217157b287e036fba1e48ad2c6a3356e from upstream (fixed package is probably already in SLE queue) post-build-checks: 1) apply https://github.com/openSUSE/post-build-checks/commit/c6e35c3b68457630fa7379… What should I do with this changes? Should I submit them directly to Leap:42.2? Leap 42.2 Ring1 is being built here: https://build.opensuse.org/project/monitor/home:matwey:experimental:Leap:42… You are welcome to reuse my work or participate into fixing `failed' packages in Ring1. -- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 13

[opensuse-factory] [TW] mutt-1.6.1 unusable when built with --enable-sidebar
by Manfred Hollstein 02 Jun '16

02 Jun '16

Hi there, something in advance: I'm a long time mutt user. Therefore I'm used to shuffle through the list of folders containing new/unread messages using the 'c' followed by 'space' key sequence. This doesn't work anymore in current Tumbleweed snapshots. I narrowed it down to the configure option "--enable-sidebar", which enables some pseudo graphical functionality for - I guess - mutt newbies. Rebuilding the otherwise unchanged package with "--disable-sidebar" produces a normally working mutt again. I strongly recommend to disable this code until it gets fixed. <https://bugzilla.opensuse.org/show_bug.cgi?id=982129> Hope this helps some otherwise potentially frustrated mutt users ;) Thx, cheers. l8er manfred

5 16