January 2019 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] gpl-2 vs. bsd-4-claus
by Peter Czanik 07 Jan '19

07 Jan '19

Hi, Recently my syslog-ng update in Factory was rejected: https://build.opensuse.org/request/show/660707 The reasoning was: "@babelworx declined the legal report with the following comment: GPL-2.0 incompatible BSD-4-Clause: syslog-ng-3.19.1/lib/compat/strcasestr.c" Two questions: - Does this patch correctly resolve this problem: https://github.com/balabit/syslog-ng/pull/2482/commits/a240d0f48202c41eaac6… - Is licensdigger clever enough to check the patched sources instead of the original? If both answers are "yes", I'll resubmit syslog-ng 3.19 with the above patch. If only the first is yes, I can also roll out a patched release tgz. Bye, CzP Peter Czanik (CzP) <peter.czanik(a)balabit.com <mailto:peter.czanik@balabit.com>> Balabit (a OneIdentity company) / syslog-ng upstream https://syslog-ng.com/community/ <https://syslog-ng.com/community/> https://twitter.com/PCzanik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] openSUSE reproducible builds status 2018-10
by Bernhard M. Wiedemann 07 Jan '19

07 Jan '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I uploaded http://rb.zq1.de/compare.factory-20181023/ today and rbstats are: total-packages: 11105 build-tried: 11103 build-failed: 50 build-n-a: 103 build-succeeded: 10950 build-official-failed+na: 95 build-compare-failed: 271 build-compare-succeeded: 10679 bit-by-bit-identical: 10378 not-bit-by-bit-identical: 571 Over the past weeks, I had get rid of several build failures at the expense of having fewer patches to remove sources of indeterminism. Of the 271 packages with major issues, there are 4 in Ring0 and 53 in Ring1: - --- ring0 --- acl gcc7 gcc8 grep - --- ring1 --- MozillaFirefox MozillaThunderbird breeze5-icons colord dolphin dom4j ecj emacs evolution firebird gconf2-branding-openSUSE gdb gimp gnome-builder gnome-documents go1.10 go1.11 groff-full hamcrest hsqldb infinipath-psm java-10-openjdk java-11-openjdk java-1_8_0-openjdk javassist kdoctools kernel-default kernel-vanilla libkolabxml libreoffice mono-core mozilla-nss mysql-connector-java open-iscsi pcp php7 plasma5-desktop python-base python3-base qpid-proton release-notes-openSUSE rubygem-gem2rpm rust syntax-highlighting thai-fonts tigervnc tomcat transfig virtualbox wireshark xalan-j2 xen xmlbeans If you are interested in why they vary: acl: date+time in /usr/share/locale/en(a)boldquot/LC_MESSAGES/acl.mo - -PO-Revision-Date: 2018-10-23 01:45+0000 +PO-Revision-Date: 2033-11-24 15:01+0000 gcc7 gcc8 grep: indeterminism from PGO. See also https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/pgo MozillaFirefox MozillaThunderbird: date+time, other /usr/lib64/firefox/libxul.so varies maybe from https://github.com/rust-lang/rust/issues/50556 .../browser/extensions/langpack-ca(a)firefox.mozilla.org/manifest.json - - "version": "20181009013946" + "version": "20331110172641" breeze5-icons dolphin wireshark syntax-highlighting: Qt rcc/qrc fix pending / requires discussion https://build.opensuse.org/request/show/643992 colord some randomness in .icc files from cd-create-profile plus an uncommitted date/time fix in lib/colord/cd-it8.c: priv->enable_created = FALSE dom4j hsqldb javassist tomcat: date + mtime in .jar + javadoc html ecj ASLR /usr/share/maven-metadata/ecj.xml has alias entries in random order emacs unknown variations in /usr/bin/emacs-* evolution parallelism (-j1 vs -j4) influences content of /usr/share/gtk-doc/html/evolution-mail-composer/evolution-mail-composer-EMsgComposer.html firebird: ships unreproducible database http://tracker.firebirdsql.org/browse/CORE-5548 gconf2-branding-openSUSE embeds mtime values in /etc/gconf/gconf.xml.vendor/%gconf-tree.xml gdb contains testresults https://bugzilla.opensuse.org/show_bug.cgi?id=1110708 gimp ASLR 12 byte differ in bKGD header from gegl GEGL_USE_OPENCL=no GEGL_SWAP=ram /usr/bin/gegl ../../icons/Symbolic/64/gimp-texture.png -o 64/gimp-texture.png -- gegl:invert-gamma gnome-builder solved: https://build.opensuse.org/request/show/644025 gnome-documents gnome-documents-getting-started.pdf from inkscape go1.10 go1.11: variations in /usr/lib64/go/1.10/pkg/obj/go-build/*/*-a groff-full unknown reason .ps files vary hamcrest java .class files vary from build/temp/hamcrest-core/generated-code /org/hamcrest/CoreMatchers.java written by ant javadoc html varies infinipath-psm: date ; orphaned upstream https://github.com/intel/psm/pull/16 was incomplete solved by https://build.opensuse.org/request/show/644077 java-1_8_0-openjdk java-10-openjdk java-11-openjdk various .jar .zip .html .jmod ordering in /usr/lib64/jvm/java-10-openjdk-10/lib/classlist kdoctools open parallelism-race bug https://bugs.kde.org/show_bug.cgi?id=398263 kernel-default kernel-vanilla date+time ; random keys? "Build time autogenerated kernel key0 ..181009012108Z..21180915012108Z0.1,0" libkolabxml ASLR from build/kolabformat-xcal-schema.cxx from compiled/xsdbin.cxx libreoffice various .jar .so .dat/.bau (.zip) javadoc_log.txt mono-core date+time ; other mozilla-nss DSA random temp-key from shlibsign https://bugzilla.opensuse.org/show_bug.cgi?id=1081723 mysql-connector-java xalan-j2: turned out to only be a minor diff with https://github.com/openSUSE/build-compare/pull/29 open-iscsi date in man solved with https://build.opensuse.org/request/show/644084 pcp /var/lib/pcp/testsuite/perfevent/perfevent_coverage has random diffs from gcov / .gcno files causing diff in .o ? php7 date / EPOCH timestamps e.g. in /usr/share/php7/PEAR/.channels/__uri.reg plasma5-desktop parallelism makes kcolorschemeeditor vary kcolorschemeeditor_autogen/mocs_compilation.cpp.o differ workaround: make -C kcms/colors/ python-base python3-base: PGO varies .o files that go into /usr/lib64/libpython3.6m.so.1.0 qpid-proton filesys readdir order solved with https://build.opensuse.org/request/show/644081 release-notes-openSUSE date+time in .pdf random id values in .html rubygem-gem2rpm mtime ? /usr/lib64/ruby/gems/2.5.0/cache/checksums.yaml varies rust unknown asm diffs in rustc and others thai-fonts maybe fixed by fontforge patch tigervnc date+time in /usr/share/vnc/classes/META-INF/TIGERVNC.RSA varies transfig date+time in sample-presentation.pdf /CreationDate /ModDate from Ghostscript virtualbox tar ; random xen date in hvmloader something in .efi files xmlbeans index.xsb varies Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRk4KvQEtfG32NHprVJNgs7HfuhZAUCW8+K0gAKCRBJNgs7Hfuh ZIzAAKD0pHgj4kdnsXGHL4GbVWX6Y6AgMgCg6yb8neslLRd003FVCFOTXPDT07U= =FZJA -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 14

Re: [opensuse-factory] Exploring a better way to notify users about upgrades
by hellcp＠opensuse.org 07 Jan '19

07 Jan '19

On Mon, Jan 7, 2019 at 1:54 PM, Neal Gompa <ngompa13(a)gmail.com> wrote: > On Mon, Jan 7, 2019 at 3:18 AM <hellcp(a)opensuse.org> wrote: >> >> Hi, >> >> Since 2007 ZYpp has a backend for PackageKit, during openSUSE 11 >> discussions >> specification regrading notifying user about new upgrades was >> created. >> Instead >> of relying on existing tooling, developers decided to opt for newly >> created >> PackageKit to do it instead. That's how we got function that checks >> for >> upgrades >> based on product definition in /etc/product.d/. Obviously that's >> not a >> great >> system, considering the history of openSUSE, with switch to Leap, we >> can't >> expect ourselves to know what the next openSUSE will be early >> enough to >> put the >> correct definition of upgrades a year prior to next version coming >> out. >> After >> all, it's not just Leap that is an option during upgrades, there is >> also >> Tumbleweed which Leap can upgrade to. >> >> Old specification: >> https://old-en.opensuse.org/Product_management/Code11/Upgrade >> Current code regarding upgrade checks in PackageKit ZYpp backend: >> >> https://github.com/hughsie/PackageKit/blob/master/backends/zypp/pk-backend-zypp.cpp#L2273-L2322 >> >> Now that Ludwig has been looking into using releasever in openSUSE >> repositories >> (at last, that has been supported by ZYpp for a very long time), we >> can >> have >> nice things, like easy upgrades, and much easier specifications >> regarding new >> versions of openSUSE consumable by third party applications, like >> ZYpp >> backend >> for PackageKit. Also wagon has been dead for a long time, would be >> nice >> to make >> it easier for users to upgrade easily (although `zypper dup >> --releasever 15.2` >> is quite easy, not UI enough for me). >> >> ZYpp specification regarding repo variables: >> https://doc.opensuse.org/projects/libzypp/HEAD/zypp-repovars.html >> >> There are at least 2 ways to approach that obviously, both very >> similar >> though. >> Let's call them Fedora way and old-modified for the sake of this >> mail. >> >> Fedora uses their own plugin to Gnome Software to check for >> "collections" (read >> upgrades) in a spec they host on their server. That spec specifies >> what >> release >> is currently maintained, active, EOL, unstable, etc. When Gnome >> Software daemon >> is run, it checks that file for information regarding updates, >> downloads artwork >> for next release and displays nice banner in Gnome Software (or any >> app >> store >> using the same backend). This solution is visually stunning, but >> requires a >> bunch of software, which is not desirable. I think we could use that >> style of >> showing upgrades for users that do have Gnome Software based >> applications >> installed, but shouldn't be necessary to get notified about the next >> upgrade. >> >> Fedora's spec: >> https://admin.fedoraproject.org/pkgdb/api/collections/ >> Gnome Software Fedora Collections code: >> >> https://gitlab.gnome.org/GNOME/gnome-software/tree/master/plugins/fedora-pkgdb-collections >> > > It is not necessarily true that "a bunch of software" is required for > this. From GNOME Software's point of view, it's just requesting a blob > to process. That can be static or dynamic. While Fedora's is dynamic, > Mageia's is static and edited by humans. (Yes, Mageia doesn't have a > g-s plugin yet, I'm working on it!) > > The advantage of this approach is that if the availability of an > upgrade needs to be disabled for whatever reason, you can kill it > immediately. Also, you can have more than GNOME Software leverage > that. Anything that could want to "listen" for openSUSE upgrades and > either notify or trigger them can use the same end point. Still much more software uses PK over GS ;) I understand the advantages, but this is the kind of design that should work pretty much everywhere, with the software that already exists (this is what being lazy is like :P). >> Old-modified however would specify url of the same kind of file >> that is >> used for >> Fedora upgrades, but thanks to it being specified in >> /etc/product.d/, >> it would >> be usable by ZYpp backend for PackageKit, which would fetch >> whatever we >> decide >> to put into the file on the server. Similar file already exists in >> software-o-o, >> but for the purposes of generating different output in html >> resulting in >> distributions part of the site. >> >> software-o-o definition: >> >> https://github.com/openSUSE/software-o-o/blob/master/config/releases.yml >> >> So product.d definition that would have looked like this in the >> past: >> >> ```xml >> <?xml version="1.0" encoding="UTF-8"?> >> <product schemeversion="0.0"> >> <vendor>Novell</vendor> >> <name>openSUSE</name> >> <version>11.0</version> >> ... >> <upgrades> >> <upgrade> >> <name>openSUSE_11.1</name> >> <summary>openSUSE 11.1</summary> >> <repository> >> http://download.opensuse.org/distribution/openSUSE/11.1 >> </repository> >> <notify>true</notify> >> <status>stable</status> >> </upgrade> >> <upgrade> >> <name>openSUSE_Factory</name> >> <summary>openSUSE Factory</summary> >> <repository> >> >> http://download.opensuse.org/distribution/openSUSE/Factory >> </repository> >> <notify>false</notify> >> <status>unstable</status> >> </upgrade> >> </upgrades> >> ... >> </product> >> ``` >> >> would instead be: >> >> ```xml >> <?xml version="1.0" encoding="UTF-8"?> >> <product schemeversion="0.0"> >> <vendor>openSUSE Project</vendor> >> <name>openSUSE Leap</name> >> <version>16.0</version> >> ... >> <upgradespec> >> https://software.opensuse.org/distributions/productdef >> </upgradespec> >> ... >> </product> >> ``` >> (just an example, not a real url) >> >> And the spec would be written in the same manner as Fedora's >> collections (but >> specify url for Tumbleweed repository, because it's not easily >> changable with >> current way we have $basename specified, that should be improved too >> most >> likely). >> > > The problem with this approach is that a package has to be updated > first before you'll get notified of a distribution upgrade. This is > problematic for a number of reasons, because people sometimes only do > distribution upgrades and don't frequently do regular updates. Or > maybe they missed *that one update* that provided the definition. > > Ideally, with either approach, you'd ship the repo files for the > distribution in a package so that the content is static and set up > with $releasever. In Fedora and Mageia, we have a system-repos package > (Fedora's is fedora-repos, Mageia's is mageia-repos). These ship all > the default repos for the distribution with their correct states > (enabled, disabled, correct priorities, correct base paths, repo vars, > etc.). Additional repos can be added as normal, but zypper/yast can be > configured to make them somewhat differently from base repos (for > example, a different default priority or something). > > This eliminates all the current fiddling people have to do for doing > system upgrades, and makes it as easy as "zypper dup > --releasever=16.0", just as "dnf --releasever=29 distro-sync" would > work on Fedora. In a perfect world `zypper dup --basename tumbleweed --releasever ''` would be a valid command to upgrade to Tumbleweed from Leap :P Good ideas aside, obviously the best approach is static repos, the fact that priorities for all the repos are flat is certainly not a great design :P However I don't think that standard updates should be necessary in the whole process, but I get your point. The best way to approach updates like 42.3 -> 15.0 as it already happened would be to add relations between the distributions. In that case even if one day openSUSE Project splits Leap into two new distributions, release manager would have to take preference for default upgrade for users, but it's a small price to pay for flexability of that approach (even for other potential vendors). > >> A new specification of this kind will obviously requre some >> discussion, >> which >> I invite you to do. After some discussion I will consider the input >> and >> implement whatever comes out of it. Now I should get back to >> Artwork, >> where I belong. >> > > I like you doing code things too. :) I think just you, quality of code overall goes down immidiately ;) >> Ah, and btw, PackageKit will soon be able to do dup for Tumbleweed: >> https://github.com/hughsie/PackageKit/pull/305 >> I expect that to be tested by openQA, it will make Tumbleweed >> easier to >> use >> for newbs :D >> > > Yeah, it's nice to see the zypp backend get some love. > >> There are some other items that have to be considered for backend, >> it >> still >> takes over Zypper and YaST way more than it should, which dnf fixed >> by >> starting out lock for duration of PackageKit function, instead of >> duration of >> life of PackageKit process (it slows down PackageKit by a bit, but >> makes other >> tools collaborate with PackageKit better). > > Honestly, I'm surprised no one thought of this before it was done for > the dnf backend. It's kind of obvious... > >> Also backend doesn't refresh >> AppStream, which makes Gnome Software empty, that should be fixed >> using >> more >> of a repo approach than ZYpp backend (because ZYpp doesn't expose >> AppStream >> urls, so using librepo with as-glib would probably be a better >> idea). >> > > It's a good plan, since that lets you freely fetch additional metadata > from rpm-md however you like. LCP [Stasiek] https://lcp.world -- 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] Exploring a better way to notify users about upgrades
by hellcp＠opensuse.org 07 Jan '19

07 Jan '19

Hi, Since 2007 ZYpp has a backend for PackageKit, during openSUSE 11 discussions specification regrading notifying user about new upgrades was created. Instead of relying on existing tooling, developers decided to opt for newly created PackageKit to do it instead. That's how we got function that checks for upgrades based on product definition in /etc/product.d/. Obviously that's not a great system, considering the history of openSUSE, with switch to Leap, we can't expect ourselves to know what the next openSUSE will be early enough to put the correct definition of upgrades a year prior to next version coming out. After all, it's not just Leap that is an option during upgrades, there is also Tumbleweed which Leap can upgrade to. Old specification: https://old-en.opensuse.org/Product_management/Code11/Upgrade Current code regarding upgrade checks in PackageKit ZYpp backend: https://github.com/hughsie/PackageKit/blob/master/backends/zypp/pk-backend-… Now that Ludwig has been looking into using releasever in openSUSE repositories (at last, that has been supported by ZYpp for a very long time), we can have nice things, like easy upgrades, and much easier specifications regarding new versions of openSUSE consumable by third party applications, like ZYpp backend for PackageKit. Also wagon has been dead for a long time, would be nice to make it easier for users to upgrade easily (although `zypper dup --releasever 15.2` is quite easy, not UI enough for me). ZYpp specification regarding repo variables: https://doc.opensuse.org/projects/libzypp/HEAD/zypp-repovars.html There are at least 2 ways to approach that obviously, both very similar though. Let's call them Fedora way and old-modified for the sake of this mail. Fedora uses their own plugin to Gnome Software to check for "collections" (read upgrades) in a spec they host on their server. That spec specifies what release is currently maintained, active, EOL, unstable, etc. When Gnome Software daemon is run, it checks that file for information regarding updates, downloads artwork for next release and displays nice banner in Gnome Software (or any app store using the same backend). This solution is visually stunning, but requires a bunch of software, which is not desirable. I think we could use that style of showing upgrades for users that do have Gnome Software based applications installed, but shouldn't be necessary to get notified about the next upgrade. Fedora's spec: https://admin.fedoraproject.org/pkgdb/api/collections/ Gnome Software Fedora Collections code: https://gitlab.gnome.org/GNOME/gnome-software/tree/master/plugins/fedora-pk… Old-modified however would specify url of the same kind of file that is used for Fedora upgrades, but thanks to it being specified in /etc/product.d/, it would be usable by ZYpp backend for PackageKit, which would fetch whatever we decide to put into the file on the server. Similar file already exists in software-o-o, but for the purposes of generating different output in html resulting in distributions part of the site. software-o-o definition: https://github.com/openSUSE/software-o-o/blob/master/config/releases.yml So product.d definition that would have looked like this in the past: ```xml <?xml version="1.0" encoding="UTF-8"?> <product schemeversion="0.0"> <vendor>Novell</vendor> <name>openSUSE</name> <version>11.0</version> ... <upgrades> <upgrade> <name>openSUSE_11.1</name> <summary>openSUSE 11.1</summary> <repository> http://download.opensuse.org/distribution/openSUSE/11.1 </repository> <notify>true</notify> <status>stable</status> </upgrade> <upgrade> <name>openSUSE_Factory</name> <summary>openSUSE Factory</summary> <repository> http://download.opensuse.org/distribution/openSUSE/Factory </repository> <notify>false</notify> <status>unstable</status> </upgrade> </upgrades> ... </product> ``` would instead be: ```xml <?xml version="1.0" encoding="UTF-8"?> <product schemeversion="0.0"> <vendor>openSUSE Project</vendor> <name>openSUSE Leap</name> <version>16.0</version> ... <upgradespec> https://software.opensuse.org/distributions/productdef </upgradespec> ... </product> ``` (just an example, not a real url) And the spec would be written in the same manner as Fedora's collections (but specify url for Tumbleweed repository, because it's not easily changable with current way we have $basename specified, that should be improved too most likely). A new specification of this kind will obviously requre some discussion, which I invite you to do. After some discussion I will consider the input and implement whatever comes out of it. Now I should get back to Artwork, where I belong. Ah, and btw, PackageKit will soon be able to do dup for Tumbleweed: https://github.com/hughsie/PackageKit/pull/305 I expect that to be tested by openQA, it will make Tumbleweed easier to use for newbs :D There are some other items that have to be considered for backend, it still takes over Zypper and YaST way more than it should, which dnf fixed by starting out lock for duration of PackageKit function, instead of duration of life of PackageKit process (it slows down PackageKit by a bit, but makes other tools collaborate with PackageKit better). Also backend doesn't refresh AppStream, which makes Gnome Software empty, that should be fixed using more of a repo approach than ZYpp backend (because ZYpp doesn't expose AppStream urls, so using librepo with as-glib would probably be a better idea). LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] New Tumbleweed snapshot 20181204 released!
by Dominique Leuenberger 06 Jan '19

06 Jan '19

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: cyrus-imapd frogr (1.4 -> 1.5) goffice (0.10.43 -> 0.10.44) ibus-libpinyin mlocate nodejs10 obs-service-set_version (0.5.10 -> 0.5.11) python-boto python-boto3 (1.9.38 -> 1.9.57) python-botocore (1.12.38 -> 1.12.57) rubygem-pathutil (0.16.1 -> 0.16.2) rubygem-pry (0.11.3 -> 0.12.2) rubygem-pry-doc (0.13.4 -> 0.13.5) rubygem-rack-1_6 (1.6.10 -> 1.6.11) rubygem-rack-oauth2 (1.9.2 -> 1.9.3) rubygem-rack-protection (2.0.3 -> 2.0.4) rubygem-rouge (3.2.1 -> 3.3.0) rubygem-sass (3.6.0 -> 3.7.2) rubygem-serverengine (2.0.7 -> 2.1.0) squid vdr virt-manager xfce4-branding-openSUSE xfce4-dict (0.8.1 -> 0.8.2) === Details === ==== cyrus-imapd ==== Subpackages: cyradm perl-Cyrus-IMAP perl-Cyrus-SIEVE-managesieve - Fixed startup of cyrus-imapd when using native systemd service by setting RuntimeDirectory=cyrus-imapd in the service file - cyrus-imapd: migrate from cron to systemd timers (bsc#1115438) Created script service and timer replacing cron daily script - Please convert SysV init scripts by cyrus-imapd into native systemd services (bsc#1115999) Fixed using the with_systemd macro ==== frogr ==== Version update (1.4 -> 1.5) Subpackages: frogr-lang - Update to version 1.5: + Introduced "empty" initial state for when no pictures have been loaded yet. + Fixed issues with the content and installation of the AppData file. + Stopped installing frogr as a MIME handler for text/plain and text/html. + Stopped using gtk_widget_show_all(), use gtk_widget_show only instead. + Removed the application menu, moved functionality to hamburger menu. + Updated translations. - Drop obsolete conditional handling of desktop_database_post(un) and icon_theme_cache_post(un) in post(un). ==== goffice ==== Version update (0.10.43 -> 0.10.44) Subpackages: goffice-lang libgoffice-0_10-10 - Update to version 0.10.44: + No changes, version bump only. ==== ibus-libpinyin ==== - Update ibus-libpinyin.spec: To adapt to tumbleweed's update to python3. ==== mlocate ==== Subpackages: mlocate-lang - Reduce amount of emitted %service_* boilerplate. ==== nodejs10 ==== Subpackages: nodejs10-devel npm10 - flaky_test_rerun.patch: Rerun failing tests in case of flakiness ==== obs-service-set_version ==== Version update (0.5.10 -> 0.5.11) - for now obs_scm_testsuite only for > 1315, needed python stuff not available otherwise - Update to version 0.5.11: * fix code to pass flake8 tests for python3 * fix zipfile crash also for python2.7 * avoid error with latest flake8 about unused variable * allow running tests with python3 * second place where zip file handling can crash * avoid crashes due to false is_zipfile() response * Add python-flake8 to test suite package list * Fix indentation of condition * Fix basename to match documentation (#54) ==== python-boto ==== - Undo previous change, name confustion between boto and boto3 - Fix build for openSUSE Leap 42.3 + urllib3 needs the ssl module, which in Leap 42.3 is delivered by python and not python-base. Set explicit build dependency on python ==== python-boto3 ==== Version update (1.9.38 -> 1.9.57) - Version update to 1.9.57 (bsc#1118021, bsc#1118027) * bugfix:s3: [``botocore``] Add md5 header injection to new operations that require it * api-change:``s3``: [``botocore``] Update s3 client to latest version - from version 1.9.56 * api-change:``elbv2``: [``botocore``] Update elbv2 client to latest version * api-change:``stepfunctions``: [``botocore``] Update stepfunctions client to latest version * api-change:``xray``: [``botocore``] Update xray client to latest version * api-change:``lambda``: [``botocore``] Update lambda client to latest version * api-change:``events``: [``botocore``] Update events client to latest version * api-change:``serverlessrepo``: [``botocore``] Update serverlessrepo client to latest version * api-change:``kafka``: [``botocore``] Update kafka client to latest version * api-change:``s3``: [``botocore``] Update s3 client to latest version - Update Requires in spec file from setup.py - Version update to 1.9.55 * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``appmesh``: [``botocore``] Update appmesh client to latest version * api-change:``license-manager``: [``botocore``] Update license-manager client to latest version * api-change:``servicediscovery``: [``botocore``] Update servicediscovery client to latest version * api-change:``sagemaker``: [``botocore``] Update sagemaker client to latest version * api-change:``lightsail``: [``botocore``] Update lightsail client to latest version - from version 1.9.54 * api-change:``securityhub``: [``botocore``] Update securityhub client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version * api-change:``fsx``: [``botocore``] Update fsx client to latest version * api-change:``dynamodb``: [``botocore``] Update dynamodb client to latest version - from version 1.9.53 * api-change:``meteringmarketplace``: [``botocore``] Update meteringmarketplace client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``codedeploy``: [``botocore``] Update codedeploy client to latest version * api-change:``translate``: [``botocore``] Update translate client to latest version * api-change:``logs``: [``botocore``] Update logs client to latest version * api-change:``kinesisanalytics``: [``botocore``] Update kinesisanalytics client to latest version * api-change:``comprehendmedical``: [``botocore``] Update comprehendmedical client to latest version * api-change:``mediaconnect``: [``botocore``] Update mediaconnect client to latest version * api-change:``kinesisanalyticsv2``: [``botocore``] Update kinesisanalyticsv2 client to latest version * api-change:``ecs``: [``botocore``] Update ecs client to latest version - from version 1.9.52 * api-change:``iot``: [``botocore``] Update iot client to latest version * api-change:``sms``: [``botocore``] Update sms client to latest version * api-change:``s3``: [``botocore``] Update s3 client to latest version * api-change:``iotanalytics``: [``botocore``] Update iotanalytics client to latest version * api-change:``greengrass``: [``botocore``] Update greengrass client to latest version * api-change:``kms``: [``botocore``] Update kms client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``globalaccelerator``: [``botocore``] Update globalaccelerator client to latest version - from version 1.9.51 * api-change:``amplify``: [``botocore``] Update amplify client to latest version * api-change:``transfer``: [``botocore``] Update transfer client to latest version * api-change:``snowball``: [``botocore``] Update snowball client to latest version * api-change:``robomaker``: [``botocore``] Update robomaker client to latest version * api-change:``s3``: [``botocore``] Update s3 client to latest version * api-change:``datasync``: [``botocore``] Update datasync client to latest version - from version 1.9.50 * api-change:``rekognition``: [``botocore``] Update rekognition client to latest version - from version 1.9.49 * api-change:``autoscaling-plans``: [``botocore``] Update autoscaling-plans client to latest version * api-change:``xray``: [``botocore``] Update xray client to latest version * api-change:``devicefarm``: [``botocore``] Update devicefarm client to latest version * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``medialive``: [``botocore``] Update medialive client to latest version * api-change:``redshift``: [``botocore``] Update redshift client to latest version * api-change:``rds-data``: [``botocore``] Update rds-data client to latest version * api-change:``appsync``: [``botocore``] Update appsync client to latest version * api-change:``cloudwatch``: [``botocore``] Update cloudwatch client to latest version * api-change:``quicksight``: [``botocore``] Update quicksight client to latest version * api-change:``cloudfront``: [``botocore``] Update cloudfront client to latest version - from version 1.9.48 * api-change:``lightsail``: [``botocore``] Update lightsail client to latest version * api-change:``workspaces``: [``botocore``] Update workspaces client to latest version * api-change:``workdocs``: [``botocore``] Update workdocs client to latest version * api-change:``batch``: [``botocore``] Update batch client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``devicefarm``: [``botocore``] Update devicefarm client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version * api-change:``cloudformation``: [``botocore``] Update cloudformation client to latest version * api-change:``lambda``: [``botocore``] Update lambda client to latest version * api-change:``config``: [``botocore``] Update config client to latest version * api-change:``cloudtrail``: [``botocore``] Update cloudtrail client to latest version * api-change:``mediaconvert``: [``botocore``] Update mediaconvert client to latest version * api-change:``iot``: [``botocore``] Update iot client to latest version - from version 1.9.47 * api-change:``ssm``: [``botocore``] Update ssm client to latest version * api-change:``comprehend``: [``botocore``] Update comprehend client to latest version * api-change:``workspaces``: [``botocore``] Update workspaces client to latest version * api-change:``ce``: [``botocore``] Update ce client to latest version * api-change:``ecs``: [``botocore``] Update ecs client to latest version - from version 1.9.46 * api-change:``s3``: [``botocore``] Update s3 client to latest version * api-change:``sms-voice``: [``botocore``] Update sms-voice client to latest version * api-change:``redshift``: [``botocore``] Update redshift client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version * api-change:``dms``: [``botocore``] Update dms client to latest version * api-change:``codebuild``: [``botocore``] Update codebuild client to latest version * api-change:``s3control``: [``botocore``] Update s3control client to latest version * api-change:``directconnect``: [``botocore``] Update directconnect client to latest version * api-change:``ram``: [``botocore``] Update ram client to latest version * api-change:``pinpoint``: [``botocore``] Update pinpoint client to latest version * api-change:``route53resolver``: [``botocore``] Update route53resolver client to latest version * api-change:``comprehend``: [``botocore``] Update comprehend client to latest version * api-change:``transcribe``: [``botocore``] Update transcribe client to latest version * api-change:``ecs``: [``botocore``] Update ecs client to latest version * api-change:``iam``: [``botocore``] Update iam client to latest version - from version 1.9.45 * api-change:``resource-groups``: [``botocore``] Update resource-groups client to latest version * api-change:``autoscaling``: [``botocore``] Update autoscaling client to latest version * api-change:``mediatailor``: [``botocore``] Update mediatailor client to latest version * api-change:``sns``: [``botocore``] Update sns client to latest version * api-change:``sagemaker``: [``botocore``] Update sagemaker client to latest version * api-change:``servicecatalog``: [``botocore``] Update servicecatalog client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version - from version 1.9.44 * api-change:``chime``: [``botocore``] Update chime client to latest version * api-change:``budgets``: [``botocore``] Update budgets client to latest version * api-change:``redshift``: [``botocore``] Update redshift client to latest version - from version 1.9.43 * api-change:``polly``: [``botocore``] Update polly client to latest version * api-change:``batch``: [``botocore``] Update batch client to latest version * api-change:``firehose``: [``botocore``] Update firehose client to latest version * api-change:``cloudformation``: [``botocore``] Update cloudformation client to latest version * api-change:``budgets``: [``botocore``] Update budgets client to latest version * api-change:``codepipeline``: [``botocore``] Update codepipeline client to latest version * api-change:``rds``: [``botocore``] Update rds client to latest version - from version 1.9.42 * api-change:``mediapackage``: [``botocore``] Update mediapackage client to latest version - from version 1.9.41 * api-change:``medialive``: [``botocore``] Update medialive client to latest version * api-change:``dlm``: [``botocore``] Update dlm client to latest version * api-change:``events``: [``botocore``] Update events client to latest version - from version 1.9.40 * api-change:``dms``: [``botocore``] Update dms client to latest version * api-change:``ce``: [``botocore``] Update ce client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version - from version 1.9.39 * api-change:``codebuild``: [``botocore``] Update codebuild client to latest version * api-change:``pinpoint``: [``botocore``] Update pinpoint client to latest version * api-change:``ec2``: [``botocore``] Update ec2 client to latest version * api-change:``pinpoint-email``: [``botocore``] Update pinpoint-email client to latest version * api-change:``apigateway``: [``botocore``] Update apigateway client to latest version * api-change:``waf-regional``: [``botocore``] Update waf-regional client to latest version * bugfix:session config: [``botocore``] Added the default session configuration tuples back to session.session_vars_map. - Update Requires in spec file from setup.py ==== python-botocore ==== Version update (1.12.38 -> 1.12.57) - Version update to 1.12.57 (bsc#1118021, bsc#1118027) * bugfix:s3: Add md5 header injection to new operations that require it * api-change:``s3``: Update s3 client to latest version - from version 1.12.56 * api-change:``elbv2``: Update elbv2 client to latest version * api-change:``stepfunctions``: Update stepfunctions client to latest version * api-change:``xray``: Update xray client to latest version * api-change:``lambda``: Update lambda client to latest version * api-change:``events``: Update events client to latest version * api-change:``serverlessrepo``: Update serverlessrepo client to latest version * api-change:``kafka``: Update kafka client to latest version * api-change:``s3``: Update s3 client to latest version - from version 1.12.55 * api-change:``ec2``: Update ec2 client to latest version * api-change:``appmesh``: Update appmesh client to latest version * api-change:``license-manager``: Update license-manager client to latest version * api-change:``servicediscovery``: Update servicediscovery client to latest version * api-change:``sagemaker``: Update sagemaker client to latest version * api-change:``lightsail``: Update lightsail client to latest version - from version 1.12.54 * api-change:``securityhub``: Update securityhub client to latest version * api-change:``rds``: Update rds client to latest version * api-change:``fsx``: Update fsx client to latest version * api-change:``dynamodb``: Update dynamodb client to latest version - from version 1.12.53 * api-change:``meteringmarketplace``: Update meteringmarketplace client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``codedeploy``: Update codedeploy client to latest version * api-change:``translate``: Update translate client to latest version * api-change:``logs``: Update logs client to latest version * api-change:``kinesisanalytics``: Update kinesisanalytics client to latest version * api-change:``comprehendmedical``: Update comprehendmedical client to latest version * api-change:``mediaconnect``: Update mediaconnect client to latest version * api-change:``kinesisanalyticsv2``: Update kinesisanalyticsv2 client to latest version * api-change:``ecs``: Update ecs client to latest version - from version 1.12.52 * api-change:``iot``: Update iot client to latest version * api-change:``sms``: Update sms client to latest version * api-change:``s3``: Update s3 client to latest version * api-change:``iotanalytics``: Update iotanalytics client to latest version * api-change:``greengrass``: Update greengrass client to latest version * api-change:``kms``: Update kms client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``globalaccelerator``: Update globalaccelerator client to latest version - from version 1.12.51 * api-change:``amplify``: Update amplify client to latest version * api-change:``transfer``: Update transfer client to latest version * api-change:``snowball``: Update snowball client to latest version * api-change:``robomaker``: Update robomaker client to latest version * api-change:``s3``: Update s3 client to latest version * api-change:``datasync``: Update datasync client to latest version - from version 1.12.50 * api-change:``rekognition``: Update rekognition client to latest version - from version 1.12.49 * api-change:``autoscaling-plans``: Update autoscaling-plans client to latest version * api-change:``xray``: Update xray client to latest version * api-change:``devicefarm``: Update devicefarm client to latest version * api-change:``ssm``: Update ssm client to latest version * api-change:``medialive``: Update medialive client to latest version * api-change:``redshift``: Update redshift client to latest version * api-change:``rds-data``: Update rds-data client to latest version * api-change:``appsync``: Update appsync client to latest version * api-change:``cloudwatch``: Update cloudwatch client to latest version * api-change:``quicksight``: Update quicksight client to latest version * api-change:``cloudfront``: Update cloudfront client to latest version - from version 1.12.48 * api-change:``lightsail``: Update lightsail client to latest version * api-change:``workspaces``: Update workspaces client to latest version * api-change:``workdocs``: Update workdocs client to latest version * api-change:``batch``: Update batch client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``devicefarm``: Update devicefarm client to latest version * api-change:``rds``: Update rds client to latest version * api-change:``cloudformation``: Update cloudformation client to latest version * api-change:``lambda``: Update lambda client to latest version * api-change:``config``: Update config client to latest version * api-change:``cloudtrail``: Update cloudtrail client to latest version * api-change:``mediaconvert``: Update mediaconvert client to latest version * api-change:``iot``: Update iot client to latest version - from version 1.12.47 * api-change:``ssm``: Update ssm client to latest version * api-change:``comprehend``: Update comprehend client to latest version * api-change:``workspaces``: Update workspaces client to latest version * api-change:``ce``: Update ce client to latest version * api-change:``ecs``: Update ecs client to latest version - from version 1.12.46 * api-change:``s3``: Update s3 client to latest version * api-change:``sms-voice``: Update sms-voice client to latest version * api-change:``redshift``: Update redshift client to latest version * api-change:``rds``: Update rds client to latest version * api-change:``dms``: Update dms client to latest version * api-change:``codebuild``: Update codebuild client to latest version * api-change:``s3control``: Update s3control client to latest version * api-change:``directconnect``: Update directconnect client to latest version * api-change:``ram``: Update ram client to latest version * api-change:``pinpoint``: Update pinpoint client to latest version * api-change:``route53resolver``: Update route53resolver client to latest version * api-change:``comprehend``: Update comprehend client to latest version * api-change:``transcribe``: Update transcribe client to latest version * api-change:``ecs``: Update ecs client to latest version * api-change:``iam``: Update iam client to latest version - from version 1.12.45 * api-change:``resource-groups``: Update resource-groups client to latest version * api-change:``autoscaling``: Update autoscaling client to latest version * api-change:``mediatailor``: Update mediatailor client to latest version * api-change:``sns``: Update sns client to latest version * api-change:``sagemaker``: Update sagemaker client to latest version * api-change:``servicecatalog``: Update servicecatalog client to latest version * api-change:``ec2``: Update ec2 client to latest version - from version 1.12.44 * api-change:``chime``: Update chime client to latest version * api-change:``budgets``: Update budgets client to latest version * api-change:``redshift``: Update redshift client to latest version - from version 1.12.43 * api-change:``polly``: Update polly client to latest version * api-change:``batch``: Update batch client to latest version * api-change:``firehose``: Update firehose client to latest version * api-change:``cloudformation``: Update cloudformation client to latest version * api-change:``budgets``: Update budgets client to latest version * api-change:``codepipeline``: Update codepipeline client to latest version * api-change:``rds``: Update rds client to latest version - from version 1.12.42 * api-change:``mediapackage``: Update mediapackage client to latest version - from version 1.12.41 * api-change:``medialive``: Update medialive client to latest version * api-change:``dlm``: Update dlm client to latest version * api-change:``events``: Update events client to latest version - from version 1.12.40 * api-change:``dms``: Update dms client to latest version * api-change:``ce``: Update ce client to latest version * api-change:``ec2``: Update ec2 client to latest version - from version 1.12.39 * api-change:``codebuild``: Update codebuild client to latest version * api-change:``pinpoint``: Update pinpoint client to latest version * api-change:``ec2``: Update ec2 client to latest version * api-change:``pinpoint-email``: Update pinpoint-email client to latest version * api-change:``apigateway``: Update apigateway client to latest version * api-change:``waf-regional``: Update waf-regional client to latest version * bugfix:session config: Added the default session configuration tuples back to session.session_vars_map. ==== rubygem-pathutil ==== Version update (0.16.1 -> 0.16.2) - updated to version 0.16.2 no changelog found ==== rubygem-pry ==== Version update (0.11.3 -> 0.12.2) - updated to version 0.12.2 see installed CHANGELOG.md [#]## [v0.12.2][v0.12.2] (November 12, 2018) [#]### Bug fixes * Restore removed deprecations, which were removed by accident due to a bad rebase. [#]## [v0.12.1][v0.12.1] (November 12, 2018) [#]### Bug fixes * Stopped creating a new hash each time `Pry::Prompt#[]` is invoked ([#1855](https://github.com/pry/pry/pull/1855)) * Fixed `less` pager not working when it's available ([#1861](https://github.com/pry/pry/pull/1861)) [#]## [v0.12.0][v0.12.0] (November 5, 2018) [#]### Major changes * Dropped support for Rubinius ([#1785](https://github.com/pry/pry/pull/1785)) ==== rubygem-pry-doc ==== Version update (0.13.4 -> 0.13.5) - updated to version 0.13.5 see installed CHANGELOG.md [#]## [v0.13.5][v0.13.5] (November 8, 2018) * Fixed deprecation warnings emitted by Pry v0.12.0 ([#87](https://github.com/pry/pry-doc/pull/87)) * Fixed MRI 2.0 regression ([#88](https://github.com/pry/pry-doc/pull/88)) ==== rubygem-rack-1_6 ==== Version update (1.6.10 -> 1.6.11) - updated to version 1.6.11 see installed HISTORY.md ==== rubygem-rack-oauth2 ==== Version update (1.9.2 -> 1.9.3) - updated to version 1.9.3 no changelog found ==== rubygem-rack-protection ==== Version update (2.0.3 -> 2.0.4) - updated to version 2.0.4 no changelog found ==== rubygem-rouge ==== Version update (3.2.1 -> 3.3.0) - updated to version 3.3.0 no changelog found ==== rubygem-sass ==== Version update (3.6.0 -> 3.7.2) - updated to version 3.7.2 no changelog found ==== rubygem-serverengine ==== Version update (2.0.7 -> 2.1.0) - updated to version 2.1.0 see installed Changelog 2018-11-14 version 2.1.0: * Improve socket manager security ==== squid ==== - Fix permissions of installed file to tmpfilesdir ==== vdr ==== Subpackages: vdr-lang - remove dvbhddevice plugin for Factory (kernel 4.19+), the needed drivers/APIs are no longer available - add "-pie -fPIE" compiler options to make rpmlint happier - use %license for COPYING file ==== virt-manager ==== Subpackages: virt-install virt-manager-common - Change icons to those provided by package (yast2-theme doesn't provide some icons anymore) ==== xfce4-branding-openSUSE ==== Subpackages: exo-branding-openSUSE libgarcon-branding-openSUSE libxfce4ui-branding-openSUSE openSUSE-xfce-icon-theme thunar-volman-branding-openSUSE xfce4-notifyd-branding-openSUSE xfce4-panel-branding-openSUSE xfce4-power-manager-branding-openSUSE xfce4-session-branding-openSUSE xfce4-settings-branding-openSUSE xfdesktop-branding-openSUSE xfwm4-branding-openSUSE - removed midori branding ==== xfce4-dict ==== Version update (0.8.1 -> 0.8.2) Subpackages: xfce4-dict-lang xfce4-panel-plugin-dict - update to version 0.8.2 - Avoid segfaults (bxo#14786) - Only show web search link if we have a valid URL/dict mode - Escape link tooltip - Minor visual improvements - Translation updates -- 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] [TW] cpan shell is broken w/ perl-5.28.1
by Achim Gratz 06 Jan '19

06 Jan '19

As follows: --8<---------------cut here---------------start------------->8--- # perl -MCPAN -e 'CPAN::shell' There seems to be running another CPAN process (pid 7816). Contacting... Other job not responding. Shall I overwrite the lockfile '/root/.cpan/.lock'? (Y/n) [y] y cpan shell -- CPAN exploration and modules installation (v2.20) Enter 'h' for help. *** buffer overflow detected ***: perl terminated Aborted (core dumped) --8<---------------cut here---------------end--------------->8--- Installing modules from the command line seems to work, though. Some collision via readline maybe? I get this from an strace: --8<---------------cut here---------------start------------->8--- ioctl(-1, TIOCGWINSZ, 0x7ffd2c180250) = -1 EBADF (Bad file descriptor) ioctl(-1, TCGETS, 0x7ffd2c180220) = -1 EBADF (Bad file descriptor) --8<---------------cut here---------------end--------------->8--- So somehow it doesn't really like the terminal (konsole), although setting the TERM=dumb doesn't seem to help. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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] PHP-FPM and PHP 7.3.0
by Bjoern Voigt 05 Jan '19

05 Jan '19

Is someone successfully using PHP-FPM and PHP 7.3.0 on Tumbleweed? None of my PHP applications worked after upgrading PHP-PHP and PHP, even simple phpinfo-scripts. I use the latest Apache2, PHP and PHP-FPM packages. At the beginning I used the old configuration from PHP 7.2, later I updated the configuration from *.rpmnew files. It did not help. Even the status check does not work: /etc/php7/fpm/php-fpm.d/www.conf: [...] pm.status_path = /status [...] myusername@mybox:~> SCRIPT_NAME=/status \ > SCRIPT_FILENAME=/status \ > QUERY_STRING=full \ > REQUEST_METHOD=GET \ > cgi-fcgi -bind -connect 127.0.0.1:9000 Primary script unknownStatus: 404 Not Found X-Powered-By: PHP/7.3.0 Content-type: text/html; charset=UTF-8 File not found. Unfortunately I didn't get useful logs from PHP-FPM, e.g. the "cgi-fcgi" script does not product logs for PHP-FPM. I gave up and returned to MOD_PHP7 (apache2-mod_php7). MOD_PHP7 works. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] Non-building packages in Science and Education to be removed
by Todd Rme 04 Jan '19

04 Jan '19

Currently there are a large number of unmaintained packages that fail to build in the Science and Education repositories. They haven't been updated in years and fail to build on at least Tumbleweed, and in many cases other releases as well. There was recently a request to remove these. I will deny the requests in order to give people a chance to fix the packages. Anyone interested in any of these packages please fix them in the next 4 weeks. Any packages that are still not working on Monday, January 7 will be removed. Here is a list of failing packages: Education / HeeksART Education / HeeksCAD Education / HeeksCNC Education / MultiplicationStation Education / TuxMathScrabble Education / VUE Education / chemtool Education / fet Education / fpc-cross-i386-linux Education / freeon Education / fzclips Education / galib Education / gnome-chemistry-utils Education / graphthing Education / gtkextra2 Education / italc Education / itext Education / jMemorize Education / k3dsurf Education / kdeedu3 Education / kiwi-config-openSUSE-Edu Education / klogic Education / klogoturtle Education / koctave Education / krecipes Education / kseg Education / ksociograma Education / lenmus Education / lomse Education / moodle3_2 Education / mpqc Education / nanoxml Education / noteedit Education / open-axiom Education / opensuse-education-release Education / php5-pear-xml_parser Education / piklab Education / planets Education / plutimikation Education / release-notes-edu Education / score-reading-trainer Education / skelcd-education-desktop Education / sonic-pi Education / squidguard-blacklists Education / tablix Education / tagainijisho Education / xaralx Education / xlogo science / ASL science / CGM science / OpenVSP science / UGENE science / alberta science / arrayfire science / babel science / boxshade science / clipper science / code_saturne science / coot science / dolfin science / emboss-explorer science / engrid science / forge science / gbench science / glemon science / gnome-chemistry-utils science / ised science / keepnote science / libadjoint science / libmesh science / moab science / molekel science / mshr science / openms science / openvibe science / prank science / pyqpcr science / silo science / slepc science / superlu_dist science / tao science / taucs science / treeviewx science / vrpn science / xdrawchem science / zoltan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Tumbleweed - Review of the week 2018/52
by Dominique Leuenberger / DimStar 04 Jan '19

04 Jan '19

Dear Tumbleweed users and hackers, Today, I am cheating by writing/publishing the review of week52 of 2018 and having a look at the last snapshots that were published with versions 2018*. The pace has been quite a bit lower and thus only 5 more snapshots had been published in 2018 that had not yet been covered in earlier reviews: 1213, 1214, 1218, 1219 and 1224. After that, OBS decided to force us on a break and not produce new snapshots. Anyway, the few things that got published with those 5 snapshots were: * Mesa 18.3.1 (updated from 18.1.x) * Qt 5.12.0 * Linux kernel 4.19.8 & 4.19.11 * Mozilla Firefox 64.0 * KDE Applications 18.12.0 * KDE Frameworks 5.53.0 * Switch to LLVM 7 * Perl 5.28.0 Slow speed, but quite some impact. Nice to see so many larger stacks could be updated/submitted/tested/published before the year ended. But, as you are certainly used to, openSUSE Tumbleweed would not be called stable rolling distribution if there were not many more things already piled up. And stable means we are not publishing snapshots until the openQA tests have passed. So, there are major updates happening in the coming days/weeks: * Installer redesign: the sidebar is coming back, showing where in the installation workflow one is currently. This is already checked in to Factory and will take a bit of work to get all the needles right for openQA. This is also the main reason for no new snapshots at the moment * glibc 2.28, Python 3.7, openssl 1.1.1: The staging is still far from ready though, as Python 3.7 is known to be incompatible to Salt. Additionally, some build cycles in Factory make it close to impossible to update python to 3.7. * Linux kernel 4.20 * tcl 8.6.9, currently breaks sqlite3’s test suite Cheers, Dominique

1 0

[opensuse-factory] Taking that next step:
by election-officials＠opensuse.org 04 Jan '19

04 Jan '19

MPORTANT: DO NOT REPLY ON THIS LIST!!! IMPORTANT: DO NOT REPLY ON THIS LIST!!! Replies or comments should be made on the openSUSE Project Mailing List. Private replies or comments can be made to the Elections Committee through the address election-officials(a)opensuse.org ******** Hello, openSUSE Contributors: It seems that several of our best Contributors in the openSUSE Project do not have their openSUSE Membership, and in fact think that it is not important or even that it is a "bother". However, we would like to point out to those of you who do not have your Membership, and who make other such important Contributions to openSUSE, that a Healthy Project is only as Healthy as its Members. And, especially important, Membership is required in order to vote for the openSUSE Board. We on the Elections Committee think that the people who should *most* be taking part in the Voting process are the hard-lifters, such as the Heroes, the Developers, the Maintainers, the Packagers, the project's Coders, and all the Heavy Lifters. Therefore, we appeal to those of you who do NOT have their Membership to please apply: Get your openSUSE Membership, it is important for a Healthy Project. <url>https://en.opensuse.org/openSUSE:Members#How_to_become_a_Member</url> <url>https://en.opensuse.org/openSUSE:Members</url> We know you are tremendously busy, but if any of you think you can spare the time, we also would like you to consider running as a Candidate in the 2018-2019 Board Elections. <url>https://en.opensuse.org/openSUSE:Board_election</url> We really would prefer not to see this: <url>https://news.opensuse.org/2019/01/04/no-candidates-board-might-be-forced-to…</url> Thank You, -- from: The Elections Committee: M. Edwin Zakaria Ish Sookun Gerry Makaro -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0