openSUSE Factory November 2020

factory@lists.opensuse.org

98 participants
83 discussions

[opensuse-factory] Can we assume that /bin/sh is bash?

by Martin Wilck

Hi Jan, all, I'd like to carry our OBS dicussion to a wider audience (https://build.opensuse.org/request/show/672510). The question is whether we can assume that "/bin/sh" links to bash, in particular whether rpm scriptlets without explicit -p interpreter can be assumed to interpreted by bash. I'm aware that, in principle, /bin/sh is supposed to be the Bourne shell on Unix systems. But as a matter of fact, on current openSUSE, it is not. Unless it's tampered with, /bin/sh is a symlink to /bin/bash. bash is not started in full POSIX mode if invoked as /bin/sh, and even if it's in POSIX mode, it supports some extensions over the POSIX shell spec (e.g. the [[ ]] construct), which makes it behave differently than another shell not supporting [[ ]] would (*). Problably there are more differences, I can't claim to know them all. Here are some arguments why I think it'd be reasonable to assume that /bin/sh is bash on openSUSE: 1. patterns-base-minimal_base depends on bash, and the /bin/sh symlink is a non-configurable part of the "bash" package. 2. we could handle /bin/sh via /etc/alternatives, but we don't. 3. our Wiki suggests testing failing scriplets using "bash -xv" (https://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets) 4. /bin/sh has pointed to bash for a long time (not sure how long exactly). FTR, Fedora basically guarantees (sh == bash) for the purpose of rpm scriptlets (https://fedoraproject.org/wiki/Packaging:Scriptlets). So Fedora <-> openSUSE portability may also be an issue to consider. If we can't assume that /bin/sh is bash, what else can we assume? I recall from earlier work that writing really 100% compatible shell code for all kinds of environments is really hard. E.g., "[" isn't 100% portable either, even though it's part of the POSIX "test" standard (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html). We should have clear rules which syntax expressions can be used in rpm scriptlets, and which can't. IMO we should define one of the various existing shells as a reference by saying "if it's supported by this shell, it's valid scriptlet code". That'd be easier (especially for testing compliance) than referring to a spec. That reference shell doesn't have to be bash, of course. Thanks Martin (*) For example: # ln -s /usr/bin/echo '/usr/bin/[[' # ls -l /bin/sh lrwxrwxrwx 1 root root 4 Feb 8 10:38 /bin/sh -> bash # /bin/sh --posix -c '[[ 2 = 1 ]] && echo yes' # dash -c '[[ 2 = 1 ]] && echo yes' 2 -eq 1 ]] yes -- Dr. Martin Wilck <mwilck(a)suse.com>, Tel. +49 (0)911 74053 2107 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

1 month, 3 weeks

[opensuse-factory] openSUSE:Factory git mirror update

by Bernhard M. Wiedemann

Hi, our experimental git mirror of openSUSE:Factory got a new feature: It now makes single commits from most individual updates with some useful info in the commit message. This makes the whole history much nicer to read: https://github.com/bmwiedemann/openSUSE/commits/master In the usual case of SRs it links back to the SR on OBS, because that is where most of the discussion might have happened: https://github.com/bmwiedemann/openSUSE/commit/d1afc9699 but sometimes direct commits happen and they are shown with the commit message and a link to the OBS change https://github.com/bmwiedemann/openSUSE/commit/b2786e5c8 Ideas for future work: In theory we could also track these packages' devel projects on a 'devel' branch In a similar fashion we could also track openSUSE:Leap:15.* on stable/leap15_N branches to allow offline diff We could try to enable osc build to work from such git dirs. Either this uses the OBS server-side logic to resolve dependencies to get the usual .osc/_buildinfo* and .osc/_buildconfig* files or we re-implement or re-use OBS server logic to allow builds when offline. And then (in the foggy far future) it would be possible to make a gateway back from github pull-requests or gitlab merge-requests to submitting SRs in OBS. Or we re-think how OBS handles its source files until then. See https://www.youtube.com/watch?v=iY_ADUQiiQI&t=787 Ciao Bernhard M.

7 months, 2 weeks

[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)

1 year, 1 month

[opensuse-factory] Too many packages to process

by Vojtěch Zeisek

I'm not sure, if this is bug or feature... After few days, update applet (TW, KDE) says there are 6843 new updates (TeX, R, ... ;-). When I click to "Install updates" error "Too many packages to process (6843/5200)" appears. Zypper handles it well. Is it worth of bug report? To b.o.o? Yours, V. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/

1 year, 2 months

[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

1 year, 2 months

[opensuse-factory] New Tumbleweed snapshot 20201024 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: alsa (1.2.3.2 -> 1.2.4) alsa-firmware (1.2.1 -> 1.2.4) alsa-ucm-conf (1.2.3 -> 1.2.4) autoyast2 (4.3.61 -> 4.3.62) bind (9.16.6 -> 9.16.7) ffmpeg-4 liberation-fonts (1.07.4 -> 2.1.1) libnetfilter_conntrack libnfnetlink libnl3 libsolv (0.7.15 -> 0.7.16) mozjs68 ndctl (69 -> 70.1) openblas_pthreads (0.3.10 -> 0.3.11) perl-Mail-DKIM (0.54 -> 1.20200907) postgresql (12.0.1 -> 13) postgresql13 (12.4 -> 13.0) rubygem-css_parser rubygem-hashery setools xfsprogs (5.8.0 -> 5.9.0) === Details === ==== alsa ==== Version update (1.2.3.2 -> 1.2.4) Subpackages: libasound2 libasound2-32bit libatopology2 - Update to alsa-lib 1.2.4: Major updates, including previous patches. Documentation updates, PCM optional lockless, meter and iec958 plugin updates, UCM updates, topology API updates, LTO fixes, etc. See the details in https://www.alsa-project.org/wiki/Changes_v1.2.3.2_v1.2.4 - Drop the superfluous udev rules for HD-audio; it's already handled in the kernel properly - Drop obsoleted patches: 0001-ucm-substitution-remove-duplicate-allow_empty-assign.patch 0002-ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch 0003-ucm-substitute-the-merged-tree-completely.patch 0004-ctl-improve-documentation-for-identifier-of-control-.patch 0005-pcm-dmix-make-lockless-operation-optional.patch 0006-pcm-dmix-Fix-semaphore-usage-with-lockless-operation.patch 0007-pcm-iec958-implement-HDMI-HBR-audio-formatting.patch 0008-pcm-iec958-set-channel-status-bits-according-to-rate.patch 0009-conf-pcm-USB-Added-S-PDIF-fix-for-Asus-Xonar-SE.patch 0010-control-ctlparse-fix-enum-values-in-or.patch 0011-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch 0012-pcm-dmix-fix-access-to-sum-buffer-in-non-interleaved.patch 0014-control-Add-documentation-for-snd_ctl_elem_list_.patch 0015-conf-quote-also-strings-with-and-characters-in-strin.patch 0016-topology-decode-Fix-channel-map-memory-allocation.patch 0017-topology-decode-Fix-infinite-loop-in-decoding-enum-c.patch 0018-topology-decode-Remove-decoding-values-for-enum-cont.patch 0019-topology-decode-Add-enum-control-texts-as-separate-e.patch 0020-topology-decode-Fix-printing-texts-section.patch 0021-topology-decode-Change-declaration-of-enum-decoding-.patch 0022-topology-decode-Fix-decoding-PCM-formats-and-rates.patch 0023-topology-decode-Print-sig_bits-field-in-PCM-capabili.patch 0024-topology-decode-Add-DAI-name-printing.patch 0025-topology-Make-buffer-for-saving-dynamic-size.patch 0026-topology-return-correct-value-in-tplg_save_printf.patch 0027-topology-fix-some-gcc10-warnings-labs-signess.patch 0028-topology-fix-sort_config.patch 0029-topology-fix-the-unaligned-access.patch 0030-topology-improve-the-printf-buffer-management.patch 0031-control-Improve-general-control-interface-documentat.patch 0032-control-Add-documentation-for-snd_ctl_elem_value_.patch ==== alsa-firmware ==== Version update (1.2.1 -> 1.2.4) - Update to alsa-firmware 1.2.4: rework in auto-tools and Makefiles See details in https://alsa-project.org/wiki/Changes_v1.2.3.2_v1.2.4 ==== alsa-ucm-conf ==== Version update (1.2.3 -> 1.2.4) - Update to alsa-ucm-conf 1.2.4: Major version up, most of changes have been already applied via backport patches. See details in https://alsa-project.org/wiki/Changes_v1.2.3.2_v1.2.4 - Drop obsoleted patches: 0001-bytcr-rt5640-Fix-DMIC1-not-working-when-connected-ov.patch 0002-bytcr-rt5651-Fix-high-noise-level-soft-input-on-DMIC.patch 0003-chtrt5645-Add-ASUSTeKCOMPUTERINC.-T101HA-1.0.conf-sy.patch 0004-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch 0005-ucm2-use-Include-Syntax-3.patch 0006-chtrt5645-merge-all-possible-configurations-to-HiFi..patch 0007-cht-bsw-rt5672-merge-all-possible-configurations-to-.patch 0008-chtnau8824-merge-all-possible-configurations-to-HiFi.patch 0009-ucm.conf-add-support-for-the-kernel-module-name-tree.patch 0010-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch 0011-sof-hda-dsp-add-initial-kcontrol-values.patch 0012-sof-hda-dsp-make-the-boot-init-optional-for-all-cont.patch 0013-bdw-rt5677-add-support-for-legacy-and-SOF-drivers.patch 0014-broadwell-rt286-add-SOF-support.patch 0015-sof-soundwire-initial-UCM2-version.patch 0016-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch 0017-sof-soundwire-rewrite-for-syntax-3.patch 0018-sof-hda-dsp-fix-the-device-order-Hdmi-devices.patch 0019-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch 0020-DAISY-I2S-move-to-Samsung-snow-snow.conf.patch 0021-DB410c-move-to-Qualcomm-apq8016-sbc.patch 0022-DB820c-DB845c-move-to-Qualcomm-tree.patch 0023-PAZ00-tegraalc5632-move-to-Tegra-alc5632-tree.patch 0024-VEYRON-I2C-move-to-Rockchip-max98090-tree.patch 0025-Pandaboard-ES-move-to-OMAP-abe-twl6040-tree.patch 0026-GoogleNyan-move-to-Tegra-max98090.patch 0027-SDP4430-Move-to-OMAP-abe-twl6040-SDP4430-tree.patch 0028-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch 0029-cht-bsw-rt5672-Add-Lenovo-Miix-2-10-specific-configu.patch 0030-cht-bsw-rt5672-Add-Lenovo-ThinkPad-10-specific-confi.patch 0031-cht-bsw-rt5672-Boost-ADC-volume-a-bit.patch 0032-chtrt5645-Restore-stereo-sound-output-when-switching.patch 0033-DB820c-Correctly-move-DB820c-to-Qualcomm-apq8096.patch 0034-sof-hda-dsp-fixup-typo-in-Hdmi.conf.patch 0035-sof-hda-dsp-use-sof-hda-dsp-Hdmi.conf.patch 0036-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 0037-update-ucm2-README.md-more-kernel-module-lookup-clar.patch 0038-ucm2-Add-config-for-Rockchip-rk3399-gru-sound.patch 0039-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch 0040-amd-renoir-acp-Add-Syntax-3-in-the-module-lib-Linked.patch 0041-Correct-conflicting-mic-in-max98090.patch 0042-HDA-Intel-HiFi-dual-Fix-the-Rear-Mic-s-Jack-name.patch 0043-USB-Audio-Dell-WD15-Dock-make-input-and-output-volum.patch 0044-Rockchip-rk3399-gru-sound-remove-zero-PCM-subdevice.patch 0045-ucm2-ucm.conf-fix-the-fix-the-sysfs-kernel-module-pa.patch 0046-Revert-amd-renoir-acp-use-the-machine-driver-s-name-.patch 0047-ucm2-module-rename-rk3399-gru-sound.conf-snd_soc_rk3.patch 0048-ucm2-HDA-acp-add-Capture-simple-mixer-element-to-the.patch 0049-HDA-Intel-only-add-the-acp-dmic-to-the-sound-card-wi.patch 0050-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch 0051-ucm2-Qualcomm-sdm845-fixes-HDMI-select-card-and-HiFi.patch ==== autoyast2 ==== Version update (4.3.61 -> 4.3.62) Subpackages: autoyast2-installation - AutoYaST warnings timeout applies to the XML validation error dialog (bsc#1176973). - 4.3.62 ==== bind ==== Version update (9.16.6 -> 9.16.7) Subpackages: bind-chrootenv bind-doc bind-utils libbind9-1600 libirs1601 libisc1606 libisccc1600 libns1604 python3-bind - Upgrade to version 9.16.7 * Fix (non-)publication of CDS and CDNSKEY records. * 'dig +bufsize=0' failed to disable EDNS. * Address a TSAN report by ensuring each rate limiter object holds a reference to its task. * With query minimization enabled, named failed to resolve ip6.arpa. names that had extra labels to the left of the IPv6 part. * Silence the EPROTO syslog message on older systems. * Fix off-by-one error when calculating new hash table size. * Tighten LOC parsing to reject a period (".") and/or "m" as a value. Fix handling of negative altitudes which are not whole meters. * rbtversion->glue_table_size could be read without the appropriate lock being held. * Named erroneously accepted certain invalid resource records that were incorrectly processed after subsequently being written to disk and loaded back, as the wire format differed. Such records include: CERT, IPSECKEY, NSEC3, NSEC3PARAM, NXT, SIG, TLSA, WKS, and X25. * NTA code needed to have a weak reference on its associated view to prevent the latter from being deleted while NTA tests were being performed. * replace an INSIST() (which calls abort()) with a check and an error message. [bsc#1177913, bind-9.16.7.tar.xz] ==== ffmpeg-4 ==== Subpackages: libavcodec58_91 libavdevice58_10 libavfilter7_85 libavformat58_45 libavresample4_0 libavutil56_51 libpostproc55_7 libswresample3_7 libswscale5_7 - Enable VMAF. This can be used to compute VMAF/PSNR/SSIM. - Add vmaf-trim-usr-local.patch . ==== liberation-fonts ==== Version update (1.07.4 -> 2.1.1) - update to 2.1.1: * Fix Liberation Sans renders most Latin combining characters incorrectly * Fix Combining diaerasis below does not work except U * Fix glyph of Cent sign (U+00A2) in Sans and Mono style * Fix U+25D2 and U+25D3 circle with lower / upper half black are backwards * Improving lowercase Cyrillic glyps localized for Macedonian and Serbian * COMBINING LONG SOLIDUS OVERLAY (U+0338) not centred on base character * Added Bitcoin sign * fix for few bugs ==== libnetfilter_conntrack ==== - Modernize specfile constructs. ==== libnfnetlink ==== - Modernize specfile constructs. ==== libnl3 ==== Subpackages: libnl-config libnl3-200 - Modernize specfile constructs. ==== libsolv ==== Version update (0.7.15 -> 0.7.16) Subpackages: libsolv-tools python3-solv ruby-solv - do not ask the namespace callback for splitprovides when writing a testcase - fix add_complex_recommends() selecting conflicted packages in rare cases leading to crashes - improve choicerule generation so that package updates are prefered in more cases - bump version to 0.7.16 ==== mozjs68 ==== - Increase disk constraints to 9G, x86_64 uses ~8.7G currently ==== ndctl ==== Version update (69 -> 70.1) - Update to upstream v70.1 (jsc#SLE-13338). Adds firmware activation support. ==== openblas_pthreads ==== Version update (0.3.10 -> 0.3.11) - Update _constraints to use 12GB RAM on x86_64 - Update to version 0.3.11 common: * Reduced the default BLAS3_MEM_ALLOC_THRESHOLD (used as an upper limit for placing temporary arrays on the stack) to be compatible with a stack size of 1mb (as imposed by the JAVA runtime library) * Added mixed-precision dot function SBDOT and utility functions shstobf16, shdtobf16, sbf16tos and dbf16tod to convert between single or double precision float arrays and bfloat16 arrays * Fixed prototypes of LAPACK_?ggsvp and LAPACK_?ggsvd functions in lapack.h * Fixed underflow and rounding errors in LAPACK SLANV2 and DLANV2 (causing miscalculations in e.g. SHSEQR/DHSEQR, LAPACK issue #263) * Fixed workspace calculation in LAPACK ?GELQ (LAPACK issue #415) * Fixed several bugs in the LAPACK testsuite * Improved performance of TRMM and TRSM for certain problem sizes * Fixed infinite recursions and workspace miscalculations in ReLAPACK * CMAKE builds no longer require pkg-config for creating the .pc file * Makefile builds no longer misread NO_CBLAS=0 or NO_LAPACK=0 as enabling these options * Fixed detection of gfortran when invoked through an mpi wrapper * Improve thread reinitialization performance with OpenMP after a fork * Added support for building only the subset of the library required for a particular precision by specifying BUILD_SINGLE, BUILD_DOUBLE * Optional function name prefixes and suffixes are now correctly reflected in the generated cblas.h * Added CMAKE build support for the LAPACK and multithreading tests power: * Added optimized support for POWER10 * Added support for compiling for POWER8 in 32bit mode * Added support for compilation with LLVM/clang * Added support for compilation with NVIDIA/PGI compilers * Fixed building on big-endian POWER8 * Fixed miscompilation of ZDOTC by gcc10 * Fixed alignment errors in the POWER8 SAXPY kernel * Improved CPU detection on AIX * Supported building with older compilers on POWER9 x86_64: * Added support for Intel Cooperlake * Added autodetection of AMD Renoir/Matisse/Zen3 cpus * Added autodetection of Intel Comet Lake cpus * Reimplemented ?sum, ?dot and daxpy using universal intrinsics * Reset the fpu state before using the fpu on Windows as a workaround for a problem introduced in Windows 10 build 19041 (a.k.a. SDK 2004) * Fixed potentially undefined behaviour in the dot and gemv_t kernels * Fixed a potential segmentation fault in DYNAMIC_ARCH builds * Fixed building for ZEN with PGI/NVIDIA and AMD AOCC compilers armv7: * Fixed cpu detection on BSD-like systems armv8: * Added preliminary support for Apple Vortex cpus * Added support for the Cavium ThunderX3T110 cpu * Fixed cpu detection on BSD-like systems * Fixed compilation in -std=C18 mode IBM Z: * Added support for compiling with the clang compiler * Improved GEMM performance on Z14 - Enable bloat16 support via BUILD_BFLOAT16=1 - Add fix-build.patch to fix build with -Werror=return-type ==== perl-Mail-DKIM ==== Version update (0.54 -> 1.20200907) - updated to 1.20200907 see /usr/share/doc/packages/perl-Mail-DKIM/Changes ==== postgresql ==== Version update (12.0.1 -> 13) Subpackages: postgresql-contrib postgresql-docs postgresql-llvmjit postgresql-server - Bump major and default version to 13. ==== postgresql13 ==== Version update (12.4 -> 13.0) - Initial packaging of PostgreSQL 13: * https://www.postgresql.org/about/news/2077/ * https://www.postgresql.org/docs/13/release-13.html ==== rubygem-css_parser ==== - Add license (MIT) to gem2rpm.yml - Regenerate spec file ==== rubygem-hashery ==== - Add license into gem2rpm.yml ==== setools ==== - Cleanup BuildRequires - Fix setools-gui dependencies, we are using python-qt5 and not tcl/tk ==== xfsprogs ==== Version update (5.8.0 -> 5.9.0) Subpackages: libhandle1 xfsprogs-scrub - update to v5.9.0: * mkfs.xfs: disallow creation of RT files from proto file * mkfs.xfs: fix ASSERT on small device with stripe geom * xfs_repair: more fixes from fuzz-testing * libhandle: fix potential unterminated string problem * libhandle: libfrog: fix a potential null pointer deref * man: install all manpages that redirect to another page * man: fix ioctl_xfs_geometry manpage naming * xfsprogs: various realtime related fixes * xfsprogs: ignore autofs mount table entries * libxfs: make buffers track the per-ag structures * libxfs changes merged from kernel 5.9 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 2 months

[opensuse-factory] Random desktop lockups with kernel 5.9.x

by John Paul Adrian Glaubitz

Hi! Ever since my machine got upgraded to kernel 5.9.x, my Tumbleweed installation is randomly locking up (KDE, X11). Booting into the last 5.8.x kernel fixes the problem, so it's definitely related to the kernel and not anything else. Does anyone else see such lockups? This is on a Dell E7470 laptop with Intel Skylake graphics (Skylake GT2 [HD Graphics 520]), in case it might be related to bugs in the GPU driver. Adrian

1 year, 3 months

[opensuse-factory] Announcement: Run openQA tests with isotovideo in your CI pipelines

by Oliver Kurz

To all users of openQA or anyone interested in running system-level tests in CI jobs, I would like to make you aware of a new approach for running system-level tests using "isotovideo", the main backend of openQA tests, within continuous integration (CI) services, for example github actions, travis CI, gitlab CI, etc. Following an updated section https://github.com/os-autoinst/os-autoinst#getting-started it is possible to run "openQA tests" using a simple, convenient container based on tests that can be provided for example in a git repository. An easy example is described in https://github.com/os-autoinst/os-autoinst-distri-example#local-testing-and… Find the latest example CI run directly following https://github.com/os-autoinst/os-autoinst-distri-example/actions I consider the above approach very suitable if one wants to run system level tests following the "openQA test API" in any project where direct feedback from CI jobs is appreciated but only a limited number of test scenarios are needed, no heavy visual tests are run where the openQA web UI would provide a more convenient interface, or when wanting to test changes to already existing openQA tests but in pull requests before they are merged. For more elaborate examples a complete openQA setup is more suitable. If you want to read more about openQA in general visit http://open.qa/ There is also a single HTML file document http://open.qa/docs/ as well as a PDF version http://open.qa/docs/current.pdf Have fun, Oliver

1 year, 5 months

[opensuse-factory] package to be orphaned soon: firebird

by Michal Kubecek

Hello, the openSUSE firebird package is going to be orphaned soon and anyone willing to maintain it is welcome to take over. Short term, there shouldn't be much trouble with it, except for the fallout of what happens in openSUSE Factory project. The 3.0.7 point release is already in Factory and the next 3.0.x release is expected in about half a year. I don't expect much complications with future 3.0.x point releases. Upgrade to version 4 will be more tricky as the upstream ICU detection code has been reworked and will require some effort to adapt for openSUSE ICU packages versioning and soname tweaks. But firebird is not exactly known for rushing new versions so that there should be enough time to work this out. The background: as I learned on Wednesday, Dominique Leuenberger plans to add more checks for openSUSE Factory packages and two of them would break the build of firebird package. As he insists the build breakage must be resolved in a way I find unacceptable, I decided to step down as the package maintainer once the build is broken. I wanted to go on maintaining the package as long as possible but as Mr. Leuenberger insists that I should announce my stepping down now and he even invited another person who went as far as accusing me of "failure to conduct oneself following the norms of our communities" and "breach of SUSE's Open Source Policy", I changed my mind. I have had enough bad experiences with that person in the past and having to deal with him again is something I would be happy to avoid. Thus I'm sending this announcement now even if there is no technical reason to give up the maintainership yet. Michal Kubecek

1 year, 5 months

[opensuse-factory] UsrMerge preparations

by Ludwig Nussel

Hi, Quite some packages carry around sections like this: #UsrMerge mkdir $RPM_BUILD_ROOT/sbin ln -s %_sbindir/foo $RPM_BUILD_ROOT/sbin/foo #EndUsrMerge That was added years ago as preparation of replacing /bin, /sbin, /lib and /lib64 with a symlink and merging the content into their counterparts in /usr. I'm not sure how that was supposed to work in practice though. To actually get rid of resp disable that code even for testing one would have to modify a hundred packages. So I'd like to replace those comments with a conditional, ie %if !0%{?usrmerged} mkdir %buildroot/sbin ln -s %_sbindir/foo %buildroot/sbin/foo %endif That doesn't yet answer the question when and how we finally do the /usr merge. However at least it would be possible to flip a switch via prjconf to stop building compat symlinks in a branch project then. Factory as of today would keep building the packages the way they are now, so no change in content at this point. Using the macro also paves the way to actually test a usr merged environment in staging in the future. So unless there are better ideas I'd just go ahead and adjust all packages that have those symlinks. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)

1 year, 5 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory November 2020