openSUSE Factory September 2020

factory@lists.opensuse.org

81 participants
79 discussions

[opensuse-factory] Convert from classic to transactional server?

by seroton10＠gmail.com

Hi, When installing openSUSE (any flavour), the installer offers a choice between the "server" and "transactional server" roles, among others. If I choose to install using the "server" role, is there a (supported) procedure by which I can later convert it into a "transactional server"? (Assume using btrfs for /, and having snapshots.) I tried to do this conversion on a test system running openSUSE Leap 15.2 as follows: * run "zypper install patterns-base-transactional_base" * edit /etc/fstab to make root read-only * reboot This appears to work: The system self-updates, and reboots when needed; /etc has been turned into an overlay filesystem; and zypper up tells me to use the transactional-update tool. However, one of the packages installed during the conversion is "read- only-root-fs", and its description contains a rather stern warning: Files, scripts and directories to run the system with a read-only root filesystem with /etc writeable via overlayfs. This package should never be installed in an already running system! It should only be selected by a system role for a read-only root filesystem with transactional updates. The package will create / modify entries for mounting /etc and /var. Those entries are used by dracut to mount the overlay file systems during the early boot phase. After reading this, I ask myself, was it just dumb luck that the test system wasn't destroyed during the conversion? What can/does go wrong if read-only-root-fs is installed in an already running system, against the advice given? Any clarification on this would be much appreciated. Regards, Olav -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 days, 16 hours

[opensuse-factory] openSUSE reproducible builds status 2020-08

by Bernhard M. Wiedemann

Hi, last month's status: https://lists.opensuse.org/opensuse-factory/2020-07/msg00417.html Last months' reproducible builds project updates (including my work): https://reproducible-builds.org/reports/2020-07/ I uploaded https://rb.zq1.de/compare.factory-20200830/ today and rbstats are: total-packages: 13244 (+111) build-tried: 13236 (+110) build-failed: 66 (+28) build-n-a: 125 (-1) build-succeeded: 13045 (+83) build-official-failed+na: 323 (+72) build-compare-failed: 431 (-3) build-compare-succeeded: 12614 (+86) verify-failed: 519 (+28) verified-semi-reproducible: 12362 (+258) verified-bit-identical: 0 (+0) bit-by-bit-identical: 12488 (+106) not-bit-by-bit-identical: 558 (-23) https://rb.zq1.de/compare.factory-20200830/graph.png shows the change over time https://rb.zq1.de/compare.factory-20200830/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 2 were in ring0 45 were in ring1 That makes it 47/3268 => 1.44 % which is below the overall average of 431/13045 => 3.30 % 558/13045 => 4.28 % of packages are not perfectly reproducible Build workers were upgraded to Leap-15.2 to have a rpm that understands zstd. Several small packages seem to build faster now, possibly because the setup of the build environment is faster with zstd. E.g. "hub" went from 181+139s to 87+64s for -j1 and -j4 builds and "xinit" went from 64+63s to 46+51s Notable unreproducible core packages: cargo-c: parallelism? + filesys in rust libgit2-sys installation-images: ordering issues and plenty other issues xen: PE timestamps in .efi files Ciao Bernhard M.

3 months, 1 week

[opensuse-factory] [RFC] OpenSUSE Distribution Tiers Policy

by Dirk Müller

Hi all, I would like to get your input and start a discussion around : https://en.opensuse.org/openSUSE:OpenSUSE_Distribution_Tiers_Policy This is a draft aiming to define what a Premium Tier openSUSE Distribution architecture is. Currently this is mostly x86_64 as it stands today out of historic reasons, and rather than letting historic reasons define the future, I'd like to make it a bit more transparent on why that is and what quality standards an openSUSE distribution has to offer for other architectures to be considered also a main / premium Tier openSUSE Distribution. Please be aware that this does not silently introduce aarch64 as a premium tier, however it is aimed to define the rules that any architecture port including aarch64 would have to meet in order to be considered a premium tier. So once we agree on the terms and scope, AArch64 would be requested to be evaluated against this. For the interest of tracking, please refrain from editing the main page, and use either the mailing list discussion here or the Talk page for comments/questions/considerations/feedback. Thanks! Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 months, 2 weeks

[opensuse-factory] Thunderbird 78 and encryption status

by Wolfgang Rosenauer

Hi, since there have been multiple threads on different lists about availability of Thunderbird 78 for openSUSE please let me share the latest news. Upstream released Thunderbird 78.2.2 last week. Upstream did not enable automatic updates to 78 from 68 and also recommended to distros to not upgrade until now. It's likely that this changes with 78.2.2 being released now. The main reason is that there was no finished PGP support in TB 78. Previously it was provided by enigmail but as TB 78 does only allow webextensions enigmail cannot work anymore to provide PGP support. Therefore upstream implemented their own OpenPGP support natively in Thunderbird 78 which has been finally enabled by default in recent versions. You can find the upstream FAQ here and if you are using Thunderbird with enigmal today you really should read it carefully: https://support.mozilla.org/en-US/kb/openpgp-thunderbird-howto-and-faq So what about the current status for openSUSE: The "mozilla" OBS repository (which is for ages the official project you get current versions as backports to supported openSUSE distros) currently contains Thunderbird 78.2.2 enigmail 2.2.2 (which requires 78.2.2) (please find its purpose in the FAQ above) how those will soon be submitted to Tumbleweed. When this "soon" will be depends a bit on your feedback if there are still major issues found during the next days. So please feel free to provide feedback on the list, in bugzilla, or directly to me. After Tumbleweed I'm quite sure that the SUSE guys will also move along putting the version into supported Leap versions. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 months

[opensuse-factory] [CtLG] questioning usage of qemu/SDL2 in openSUSE Leap

by Lubos Kocman

Hello team, Virtualization team for SUSE Linux Enterprise is in favor of not brining back SDL2 support for qemu as it was previously dropped in favor of GTK. This means that openSUSE jump will not have qemu-ui-sdl unless we fork and rebuild the package. Are you aware of any usecases, that would justify additional maintenance of qemu-ui-sdl in Leap so we could bring it back to the project? Please let me know by end of the week. Thank you -- Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

4 months, 3 weeks

[opensuse-factory] xauth and now gone ~/.Xauthority

by Hans-Peter Jansen

Hi, what's the canonical way to run scripts (eg. from crontab), that want to access the X session, (eg. xprop, wmctrl), now that xauth is a random file in /run/user/$UID? Before the switch, it was possible to run such scripts from crontab, using the pattern: XAUTHORITY=~/.Xauthority DISPLAY=:0 ~/bin/script Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 months

[opensuse-factory] /etc/sysconfig vs. /etc/default

by Thorsten Kukuk

Hi, Currently we have two directories with similar usage: - /etc/default, seems to come from Debian, mainly used by upstream projects on openSUSE - /etc/sysconfig, mainly based on Red Hat, mainly used for start scripts written by us. I will ignore the subdirectories here. Both have files with in a KEY=VALUE format which can be sources by a shell. /etc/default is controlled by RPM, so changes in the config files lead to *.rpmsave or *.rpmnew files. /etc/sysconfig is controlled by fillup. Adding new variables is easy, changing defaults or removing variables is next to impossible in most cases. Why do I write this? No, I don't want to get rid of /etc/sysconfig, but bring up an idea how to solve quite some of the problems with updating sysconfig files. Many bug reports about sysconfig files get closed as "Wontfix", since changing defaults is really difficult, as we don't want to overwrite user made changes, and adjusting comments is next to impossible. As result, an user may have many sysconfig files with outdated comments and content after a longer time after installation. This can be very irritating or lead to not working configurations and frustrations as following this steps does not lead to success. Hey, we still have comments which tells the user that he has now to run SuSEconfig because of this! To run and manage our openSUSE containers via podman and systemd, we started with as example for the bind container: /etc/sysconfig/container-bind container-bind.service, which did contain: EnvironmentFile=/etc/sysconfig/container-bind and we run immeaditly into problems as there were typos in it which we couldn't fix in an easy way on already installed systems. But we have now /usr/etc and /usr/etc/default :) So /usr/etc/default/container-bind contains now the system default (fillup doesn't make sense here, as this file is RPM controlled and should not be changed by an user), and the user can override single variables by creating a file /etc/default/container-bind with just this modified variables. The container-bind.service looks now like: EnvironmentFile=/usr/etc/default/container-bind EnvironmentFile=-/etc/default/container-bind All update problems solved without the need to find out, if a variable is modified by an user or not. This is not a proposal to change now all sysconfig files, but I think many packages could benefit from such a change, especially if they are really old and the sysconfig template gets often changed. The packaging change is trivial: install the sysconfig template in /usr/etc/default/, adjust your docu and remove the fillup call. And you need to think about, if you want to rename the old sysconfig file to *.rpmsave or move it to /etc/default. Is this something we should propose as "best practise", or are there reasons not to do so we haven't found yet? Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, 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

5 months

[opensuse-factory] new package: irqstat

by Dario Faggioli

Hello everyone, There's a new package in server:monitoring called `irqstat`, which I'd like to get into Factory: https://build.opensuse.org/package/show/server:monitoring/irqstat It's a rather simple, but yet quite effective, python script for both online monitoring and offline parsing of the content of the special file /proc/interrupts. In fact, especially on large servers, where that file may have something like 550 lines and 224 columns (this is a real example, I'm not making numbers up :-) ), it may be very annoying to tell, e.g., how many IRQs a particular source is sending toward which CPUs using only the usual tools. And this is exactly where irqstat helps. There is more that can be done, and in fact, I'm also involved with upstream development (yes, for the ones that I've seen the other thread, I eventually did manage to get in touch with the maintainer!) and have some plans. E.g., improving the documentation is quite high in my TODO list for the project. I'd be interested in any feedback, comment, question, whatever. :-) Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)

5 months, 1 week

[opensuse-factory] New Tumbleweed snapshot 20200928 released!

by Dominique Leuenberger

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: dracut (050+suse.226.gb86d9bcf -> 050+suse.227.g7a9b782d) emacs-apel fcitx-zhuyin ghostscript-fonts-grops python-pygraphviz (1.5 -> 1.6) rubygem-diffy (3.3.0 -> 3.4.0) rubygem-fog-core (2.2.0 -> 2.2.3) timezone timezone-java transactional-update (2.24.1 -> 2.26) webkit2gtk3 (2.30.0 -> 2.30.1) xreader (2.2.2 -> 2.6.4) === Details === ==== dracut ==== Version update (050+suse.226.gb86d9bcf -> 050+suse.227.g7a9b782d) - Update to version 050+suse.227.g7a9b782d: * Revert "install: also install post weak dependencies of kernel modules" (boo#1177016) ==== emacs-apel ==== - add emacs-apel-fix-old-backquote.patch - fix TW build ==== fcitx-zhuyin ==== - Add fcitx-zhuyin-libpinyin.patch * libzhuyin has merged into libpinyin ==== ghostscript-fonts-grops ==== - ghostscript gs >= 9.50 needs "-dNOSAFER" to operate on files but pfbtopfa doesn't have that param ==== python-pygraphviz ==== Version update (1.5 -> 1.6) - update to 1.6: - Add Python 3.8 support - Drop Python 2.7 support - Update to SWIG 4.0.1 ==== rubygem-diffy ==== Version update (3.3.0 -> 3.4.0) updated to version 3.4.0 see installed CHANGELOG ==== rubygem-fog-core ==== Version update (2.2.0 -> 2.2.3) updated to version 2.2.3 see installed changelog.md 2.2.3 09/16/2020 ========================================================== Fix provider lookup to properly symbolize newly underscored names 2.2.2 09/15/2020 ========================================================== Fix #underscore name to be class method (instead of instance method) 2.2.1 09/15/2020 ========================================================== - Change to verify_host_key never in ssh/scp if supported - Allow either downcased and underscored provider names for broader compatability ==== timezone ==== - Fixup tzdata-china.diff: zone.tab and zone1970.tab MUST be tab delimited (boo#1176927). - modify tzdata-china.diff * systemd now reads zone1970.tab * link Asia/Shanghai to Asia/Beijing is enough and more precise ==== timezone-java ==== - modify tzdata-china.diff * systemd now reads zone1970.tab * link Asia/Shanghai to Asia/Beijing is enough and more precise ==== transactional-update ==== Version update (2.24.1 -> 2.26) Subpackages: transactional-update-zypp-config - Version 2.26 - Fix broken sync for second snapshot [boo#1176989] - Add new options to allow separate cleanup of snapshots and overlays - Check for existence of inotifywait before using it - Check that mount options don't exceed maximum length - Version 2.25.1 - Fix inotify watcher setup - Use log_{info,error} for more messages to avoid messing up Salt logs - Version 2.25 - Reduce number of overlays: Instead of using transparent overlays for all previous layers only add the previous snapshot's overlay; this will greatly reduce the number of overlays while still making sure that /etc changes in the running system will be visible in the next snapshot - When using --drop-if-no-change synchronize potential /etc changes with running system - Exclude all non-root-fs mounts from inotify watcher ==== webkit2gtk3 ==== Version update (2.30.0 -> 2.30.1) Subpackages: libjavascriptcoregtk-4_0-18 libwebkit2gtk-4_0-37 libwebkit2gtk3-lang typelib-1_0-JavaScriptCore-4_0 typelib-1_0-WebKit2-4_0 webkit2gtk-4_0-injected-bundles - Update to version 2.30.1: + Bring back the environment variable to force single process mode when PSON is disabled. + Fix downloads started by an ephemeral web context. + Updated translations. ==== xreader ==== Version update (2.2.2 -> 2.6.4) Subpackages: libxreaderdocument3 libxreaderview3 xreader-lang xreader-plugin-epubdocument xreader-plugin-pdfdocument xreader-plugin-psdocument xreader-plugin-tiffdocument xreader-plugin-xpsdocument - Update to version 2.6.4. * Fix app version. - Update since 2.2.2. * l10n: Update translations * Fix compile warnings (#317) * Fix build: Fail on implicit function declarations (#321) * preview window/printing: Remove build conditionals for gtk+-unix-print-3.0 * Fix segfault on empty navMap (#334) * meson: Dependency fixes (#335) * EVINCE BACKPORTS: * backends: backends: Don't ask for bug report in known issues. Fixes #695165 * pdf: Create highlight annotations for existing annotations in document * libdocument: adding class EvAnnotationTextMarkup * libdocument: adding annotation highlight * shell: Show highlight annotations in the sidebar * libdocument: Use a common annotation type for text markup annotations * Add support for reading strike out text markup annotations * Add support for reading underline text markup annotations * Add support for changing the type of a text markup annotation * pdf: Fix memory leak when adding new text annotations * libdocument: Added can-have-popup property to EvAnnotationMarkups. * pdf: Set can-have-popup property to markup annotations when created * ev-view: Create an EvAnnotationWindow for EvAnnotationMarkups allowing this * pdf: Added support to save popup rectangles to pdf backend * pdf: Use poppler_annot_markup_set_popup_rectangle() if available * pdf: Force text annotations to have a fixed size 24x24 * libview: Take border into account when converting view points to doc points * view: preparing for interactive annotations * libdocument: adding annotation squiggly. * pdf: adding annotation squiggly. * shell: adding annotation squiggly. * pdf: Fixed wrong type-check in copy_poppler_annot. * libdocument: Add area property to EvAnnotation * libview: Set the area of the annotations created by the user * pdf: Deprecate the rectangle passed to ev_document_annotations_add_annotation * libdocument: Add EV_ANNOTATIONS_SAVE_AREA flag * pdf: Add support for saving the annotation area * libview: Update the annot area while moved when it's being added * pdf: support for adding and saving highlight annotations * shell, view: adding highlight annotation * pdf: Ensure we always create text markup annots with at least one quadrilateral * Add a toolbar for adding annotations * page-cache: Add flags parameter to ev_page_cache_mark_dirty() * pdf: Mark document as modified when inserting annotations * libview: Do not create annotation window twice. * libview: Ignore right clicks while in annotation add mode. * view: use a hashtable to map annots to their popups. * ev-view: don't show tooltips for empty annotations * Fix add_annotation() to update area based on bounding box * Remove deprecated/unused code and fix warnings * libview: Hide annotation windows on key-press * l10n: Update POT * Meson: Formatting fix in the options file * Thumbnailer: Do not try to create an unsupported epub thumbnail * Thumbnailer: Remove MATE label from context * Add meson scripts for compiling gschemas and updating the icon cache * meson: Fix build configuration - dbus support was partly broken. * Shell: Run thumbnail jobs for epubs not as threads (#353) * meson: fix detection of t1lib * Created test for the Xreader Help menu. * Created test cases for File and Edit menus. * Remove use of deprecated g_type_class_add_private function * ev-window.c: Refactor action visibility. * ev-window.c: Hide the toolbar in recent document mode, there's nothing that can be used on it anyhow. * Created more tests for Xreader menu. * Tests: use build target rather than executable name for dependency * Build: change the conditions for handling tests * tests: Some adjustments and improvements * testEditMenu.py and testFileMenu.py: open file with arg to prevent error * Tests: extend the timeout from 30 seconds to 2 minutes * Updated old tests * meson: simplify version comparison * Updated python version to python3 * ev-window.c: Don't use g_type_class_peek. * Added checks to stop error messages from overtaking the terminal and possibly causing a segfault. * Add Print button to toolbar * Added logic to keep the find bar visible until keyboard shortcut is pressed. * Added back hot keys * Fix Segmentation fault when opening a PDF file #339 * Add UTF8 support for filename in recent view * Zoom by Control+scroll is too sensitive * [Feature request] Please provide "Save" option * Use new annotations icons (#397) * Fix xreader crash on epub search * Copy metadata when a file is copied * Thumbnailer: add application/vnd.comicbook-rar - Add patch fix_ev-window.c_error.patch to fix error: control reaches end of non-void function. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 months, 1 week

[opensuse-factory] Highlights of development sprint 109

by Ancor Gonzalez Sosa

The YaST Team continues focusing on improving both AutoYaST and the management of storage devices. Let's take a quick glance at some of the results. - New YaST test client to check AutoYaST dynamic profiles. - Improved detection of which YaST package is needed to process each section of the profile, relying on RPM’s supplement information. - First steps to annotate the documentation of AutoYaST with better information about the corresponding version for each feature. - Final design of the new Partitioner user interface. - Improved automatic submission of translations to Leap and SLE. Check the whole report at https://yast.opensuse.org/blog/2020-09-29/sprint-109 Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 months, 1 week

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory September 2020