April 2017 - 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] reproducible builds test results
by Bernhard M. Wiedemann 02 Oct '17

02 Oct '17

Hi, I did another round of rebuild testing for openSUSE Factory. All resulting build-compare diffs are in http://rb.zq1.de/compare.factory-20170406/ as well as a machine-readable summary http://rb.zq1.de/compare.factory-20170406/rbstats.txt current summary says: total-packages: 10971 build-tried: 10971 build-failed: 118 build-n-a: 114 build-succeeded: 10739 build-official-failed+na: 115 build-compare-failed: 1209 build-compare-succeeded: 9530 bit-by-bit-identical: 8133 not-bit-by-bit-identical: 2599 not-bit-by-bit-identicalcheck: 2606 meaning, 75% of packages already give bit-identical results. And half of the remaining problems are so bad that even build-compare filters do not help and thus trigger unnecessary rebuilds in OBS. and I have details about each of the 10971 packages http://rb.zq1.de/compare.factory-20170406/reproducible.json and a .diff file next to it, comparing it to the previous round The good news is, that nearly all of the packages that build in OBS, could be built locally as well, with 2 of 5 build bugs already fixed * https://bugzilla.opensuse.org/show_bug.cgi?id=1032257 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031548 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031549 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031554 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031556 Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 11

[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] Firefox new upgrades for current Opensuse versions - now sticking to ESR?
by cagsm 25 Jul '17

25 Jul '17

Hello list, in the past Firefox amonst some other select projects or applications kind of got upgrades instead of mere updates. Today or on the updates list I see that Firefox 52 becomes into 52.1.x ESR instead of 53. Is this an intentional change of procedure from the past? How come and where and how has this been discussed and decided. Would like to know and understand more of these kind of things. Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 22

[opensuse-factory] Leap 42.3 status update and roadmap proposal
by Ludwig Nussel 22 Jun '17

22 Jun '17

Hi, As announced in December¹, Leap 42.3 is already open for submissions. We shouldn't expect big updates in 42.3, nevertheless some went in already, like texlive 2016. Also, some packages that we already know SLE will take from Factory also got updated like e.g. YaST. So far the current state looks quite good in openQA² so the adventurous may already zypper dup. What's missing still is a roadmap for the release. SLE12SP3 aims for a release in September. Due to the holiday season in August where many developers are likely unavailable anyways development is expected to be finished before. So my proposal would be to also finish with Leap before and aim for a release at the last Wednesday of July. With regard to the release model I'd like to try something new. Rather than having fixed milestones with fixed submission deadlines every few weeks let's try to adopt a model similar to Tumbleweed's. Ie have snapshots released automatically based on openQA results. Nevertheless the closer we get to the release the stricter the rules for updating packages have to be. cu Ludwig [1] https://lists.opensuse.org/opensuse-factory/2016-12/msg00165.html [2] https://openqa.opensuse.org/group_overview/28 -- (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

10 18

tracker no longer a CPU consumer ? (was: [opensuse-factory] "Automatic" desktop selection)
by Robert Munteanu 25 May '17

25 May '17

Hi, On Thu, Apr 20, 2017 at 4:47 PM, Frederic Crozat <fcrozat(a)suse.com> wrote: >> 1) High CPU consuming applications as for example the gnome-tracker > > First, it is called tracker (it is a fdo project, not a GNOME one) and > it has not been a CPU consumer for years now (it runs only on idle > time). > I have a counter-point for that. tracker has been chewing my CPU over and over again. As we speak, /usr/lib/tracker-miner-fs has 100% CPU usage, and has been that way for some time. $ tracker status Currently indexed: 461158 files, 165743 folders Remaining space on database partition: 88.6 GB (16.51%) Data is still being indexed: Estimated less than one second left $ tracker daemon status Store: 20 Apr 2017, 17:34:56: ✓ Store - Idle Miners: 20 Apr 2017, 17:34:56: ✓ Userguides - Idle 20 Apr 2017, 17:34:56: 1% File System - Crawling recursively directory 'file:///home/robert/Documents' 20 Apr 2017, 17:34:56: ✓ Extractor - Idle 20 Apr 2017, 17:34:56: ✓ Applications - Idle Needless to say, the 'less than one second left' and '1%' progress claims never change. I've tried removing the tracker database, resetting preferences, but I'm still left with a runaway tracker indexer unless I manually stop it. What am I doing wrong? Thanks, Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 24

[opensuse-factory] https://bugzilla.opensuse.org/show_bug.cgi?id=1030936
by Nate Graham 08 May '17

08 May '17

Howdy all, I would like to submit a fix for https://bugzilla.opensuse.org/show_bug.cgi?id=1030936: adding "blacklist pcspkr" to /etc/modprobe.d/<some file>. This will turn off the horrible jarring error beeps in GTK programs systemwide. What would be the correct file/package to make the change in? - /etc/modprobe.d/50-blacklist.conf, from the sysconfig package? - /etc/modprobe.d/99-local.conf, from the suse-module-tools package? - Something else? Nate -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 61

[opensuse-factory] enable source_date_epoch_from_changelog
by Bernhard M. Wiedemann 04 May '17

04 May '17

For https://en.opensuse.org/openSUSE:Reproducible_Builds Now that this upstream RPM patch has landed in Factory https://build.opensuse.org/package/view_file/Base:System/rpm/0001-set-SOURC… I propose to add in the openSUSE:Factory project config under Macros: %source_date_epoch_from_changelog Y %source_date_epoch_from_changelog will set the SOURCE_DATE_EPOCH environment variable to the date of the latest changelog entry and various tools will use that date instead of the 'current' date/time. gcc, cmake, asciidoc and many others. That helps to improve the overall reproducibility of packages. E.g. __DATE__ and __TIME__ preprocessor macros in .c files will then no more create differing binary rpms that trigger superfluous rebuilds of depending packages and waste mirror bandwidth. Also rpm itself will use it to set the "Build Date" field of the resulting package... but the "Signature" field remains as it was. Btw: there are two other macros I have in https://build.opensuse.org/project/prjconf/home:bmwiedemann:reproducible In a later stage, if/when we want to go for bit-identical builds, we can also set %_buildhost SOMECONSTANTSTRING but before, we probably want to add a way to find the actual buildhost in case it created faulty RPM packages. and then later %clamp_mtime_to_source_date_epoch Y which will make sure that packages contain no files with 'current' date. That one is known to have some negative effects on python packages with .pyc files which can be mostly avoided with such a patch https://github.com/python/cpython/pull/296 but it is still uncertain what other formats might be affected in similar ways. Ciao Bernhard M.

2 3

[opensuse-factory] Adding features into zypper...
by Marco Calistri 03 May '17

03 May '17

Hello, I was thinking on how it could be useful to have implemented also into Tumbleweed functions similar as: "apt-get autoclean" "apt-get autoremove", in order to clean the repository cache and get rid of unused installed packages. If such features are already present in some way, please accept my apologies and please point me on how I can use it on openSUSE TW. Another appreciable feature to add IMHO, would be removing an entire pattern, including all the packages belonging to it in just one step: I.E.: "zypper rm Gnome" (obtaining as result the overall remotion of all the gnome related packages, preserving in any case the system dependencies) Cheers, -- TThheerree''ss aann EEcchhoo iinn hheerree.

16 42

[opensuse-factory] Tumbleweed snapshot 20170425 broke X in TW Gnome VirtualBox VM
by Larry Finger 01 May '17

01 May '17

When I rebooted after the "sudo zypper update --no-allow-vendorchange", X failed to start and I get the 1 sec flicker associates with trying to restart it. I have not yet figured out which component is broken, nor have I tried installing that update on my real TW machine. Adding "nomodeset" to the kernel boot line does not help. Of course, I can boot to mode 3. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5