[opensuse-factory] New Tumbleweed snapshot 20191110 released!
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&version=Tumbleweed&build=20191110 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: Mesa (19.2.2 -> 19.2.3) Mesa-drivers (19.2.2 -> 19.2.3) adwaita-icon-theme (3.34.0+13 -> 3.34.1) apache2 c-ares (1.15.0 -> 1.15.0~20191108) djvulibre evince gconf2 gegl (0.4.16 -> 0.4.18) gimp (2.10.12 -> 2.10.14) glib2 gtk3 libgnomekbd libqmi (1.22.6 -> 1.24.0) librsvg libtommath (1.0 -> 1.2.0) pipewire (0.2.6 -> 0.2.7) procmail salt spamassassin webkit2gtk3 (2.26.1 -> 2.26.2) === Details === ==== Mesa ==== Version update (19.2.2 -> 19.2.3) Subpackages: Mesa-dri-devel Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 libgbm1 - Update to version 19.2.3 In this release: iris, meson, radv, anv, turnip, 965, svga, utils, core mesa, glsl, etanviv, and gallium/rbug - This Mesa release includes support for latest GPUs including Intel (jsc#SLE-7962, jsc#SLE-8024, jsc#SLE-8022, jsc#SLE-10182, jsc#SLE-4983, bsc#1137515) and fixes for boo#1127672, bsc#1117365 ==== Mesa-drivers ==== Version update (19.2.2 -> 19.2.3) Subpackages: Mesa-dri Mesa-dri-nouveau Mesa-gallium Mesa-libva libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvulkan_intel libvulkan_radeon libxatracker2 - Update to version 19.2.3 In this release: iris, meson, radv, anv, turnip, 965, svga, utils, core mesa, glsl, etanviv, and gallium/rbug - This Mesa release includes support for latest GPUs including Intel (jsc#SLE-7962, jsc#SLE-8024, jsc#SLE-8022, jsc#SLE-10182, jsc#SLE-4983, bsc#1137515) and fixes for boo#1127672, bsc#1117365 - Dont conflict with vulkan-devel anymore as there is no file conflict ==== adwaita-icon-theme ==== Version update (3.34.0+13 -> 3.34.1) - Update to version 3.34.1: + Symbolic: - propegate the checkmark refinements. - slightly smaller media-eject. - centre alignment for go-next/previous. - add ! to battery level 0. - missing classes for battery icons. ==== apache2 ==== Subpackages: apache2-devel apache2-doc apache2-example-pages apache2-prefork apache2-utils - use %license [bsc#1156171] ==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108) - Update to upstream snapshot 20191108 * getaddrinfo - avoid infinite loop in case of NXDOMAIN * ares_getenv - return NULL in all cases * implement ares_getaddrinfo - onion-crash.patch: removed, upstreamed. - removed upstream patches that are part of the snapshot: 0001-Add-initial-implementation-for-ares_getaddrinfo-112.patch 0002-Remaining-queries-counter-fix-additional-unit-tests-.patch 0003-Bugfix-for-ares_getaddrinfo-and-additional-unit-test.patch 0004-Add-ares__sortaddrinfo-to-support-getaddrinfo-sorted.patch 0005-getaddrinfo-avoid-infinite-loop-in-case-of-NXDOMAIN-.patch 0006-getaddrinfo-callback-must-be-called-on-bad-domain-24.patch 0007-getaddrinfo-enhancements-257.patch 0008-Add-missing-limits.h-include-from-ares_getaddrinfo.c.patch 0009-Increase-portability-of-ares-test-mock-ai.cc-235.patch 0010-Disable-failing-test.patch - disable-live-tests.patch - updated ==== djvulibre ==== Subpackages: libdjvulibre21 - security update - added patches CVE-2019-18804 [bsc#1156188] + djvulibre-CVE-2019-18804.patch ==== evince ==== Subpackages: evince-lang evince-plugin-comicsdocument evince-plugin-djvudocument evince-plugin-dvidocument evince-plugin-pdfdocument evince-plugin-tiffdocument evince-plugin-xpsdocument libevdocument3-4 libevview3-3 nautilus-evince typelib-1_0-EvinceDocument-3_0 typelib-1_0-EvinceView-3_0 - Add patches to reverse the upstream requirement of at least synctex 1.19 since that requires texlive 2019 and we have 2017 in SLE 15. The patches are only applied when building evince with synctex < 1.19: * 0001-reversed-synctex-Move-_GNU_SOURCE-to-the-top-of-the-source-code.patch * 0002-reversed-synctex-Remove-unused-labels.patch * 0003-reversed-synctex-Silence-error-when-no-synctex-file-is-present.patch * 0004-reversed-synctex-Annotate-functions-that-wrap-vfprintf.patch * 0005-reversed-synctex-Fix-compilation.patch * 0006-reversed-synctex-Update-from-version-1.18-to-1.21.patch ==== gconf2 ==== Subpackages: gconf-polkit gconf2-lang - Drop gtk3 BuildRequires, only used by gconf-sanity-check, removed in version 3.2.6. - Only Require python3-base for gsettings-schema-convert, which provides xml/etree. - Remove huge Changelog (commit log), the NEWS file is sufficient. ==== gegl ==== Version update (0.4.16 -> 0.4.18) Subpackages: gegl-0_4 gegl-0_4-lang libgegl-0_4-0 - Add BuildRequires: pkgconfig(libavutil) >= 55.92.100 - Drop unneeded libtool BuildRequires. - Drop optional cmake BuildRequires. - Add pkgconfig(pygobject-3.0) BuildRequires: Build python-gobject bindings support. - Update to version 0.4.18 + Build - Drop autotools, GEGL is now using meson, most things are working again now - documentation/website build is a work in progress, many issues have been fixed, more a sure to surface with this first meson only release following the babl one. + Core - Support ui labels and descriptions for aux pads of ops. - Guard against uint32_t overflows in memory computations, improved memory usage stat on FreeBSD. - Added support for hygon dhyana architecture. - Added gegl_try_malloc and use it to allocate storage for tiles. - gegl-stats gained active- and assigned-threads members. + Buffer - New API for aligning to regular tile grid, gegl_rectangle_align[_to_buffer] - added gegl_rectangle_xor - gegl_buffer_create_sub_bufer now always returns a new object. - Improved tile compression, more accurate accounting and avoidiance when it is determinetal. - gegl_buffer_save : store BablSpace - take into consideration concurrent use of different tile sizes in gegl_tile_alloc - Fast path for gegl_buffer_copy is entirely in abyss. - Improved api misuse handling in gegl_buffer_set|get - Improved consistency of results when doing COW of abyss. - Improved Gobject Intospection annotations. - Use a binary tree for tile swap, improving tile removal speed. - Avoid gegl_buffer_set avoid set_pixel fast path if level>0 + Operations - Dynamic computation of per-operation thread cost, making GEGL fully use available cores on more operations. - new operations: bayer-matrix, linear-sinusoid, color-assimilation-grid, normal-map. - new operations in workshop: boxblur, alpha-inpaint - pass-through for infinite planes for: apply-lens, polar-coordinates, whirl-pinch, convolution-matrix, maze, cartoon, waterpixels, tile, distance-transform, spherize, tile-paper, dither, mantiuk06, reinhard05, fattal02, fractal-trace, motion-blur-zoom, motion-blur-circular, wind, little-planet, mirrors, cubism and long-shdow. - improved property ranges/meta-data or copyright for: motion-blur-zoom, edge-neon, cartoon, photocopy, softglow, oilify, bump-map, remap, - convolution: fix source-buffer offsets of filtered-out components, avoiding excessive shifting. - jpg-save: force grayscale if incoming buffer is grayscale - sdl-display: port to SDL2 - gamma: handle negative input values - apply-lens; enable auto threading - matting-global: disable auto threading, allocate less temporay memory. - maze: reimplemented without recursion - newsprint: added black pullout and per colorant pattern and period parameters, enable threading. - saturation: add a colormodel property which permits operating in RGB instead of CIE Lab, enabling hue preserving saturation changes. - exr-load/exr-save: only use associated alpha with EXR files - ff-load: fix audio track decoding for pure audio files - c2g: fixed initialization data race and out of bounds array access when threaded. - color-enhance: fixed a buffer leak - perlin-noise: fix initialization race - domain-transform: faster nop for edge-preservation=1.0, support BablSpace - oilify: support specifying mask-radius with aux buffer - linear-gradient, readial-gradient: use colors in correct order. - pixelize: avoid potential glitches - weighted-blend: harmonize opencl implementation with C - edge-neon: performane improvements + GEGL UI - gcut video editor ui has been removed, all its functionality is latent in the new media browser/manipulator/viewer UI. - Permit start/end times for playlist items, enabling use of folder as EDL. - Add ability loop currently shown media element. - Nearest neighbor decoding; for realtime playback of HD video content. - Frame-cache for rendered video frames (with associated PCM data) - Drag and drop from file-managers to collection view. - switch to meson based build - add buildrequires for tools to build documentation: asciidocs, gtk-doc, ruby - switch from lua to luajit - no lua support anymore on ppc64 due to missing luajit - enable workshop modules - new BuildRequires pkgconfig(lensfun) - added gegl-0.4.18_allow_unknown_arch.patch: the old code in the configure.ac also did fallthrough. restore that behavior. - drop patches no longer needed: 0001-Extend-configure-checks-with-checks-for-SDL2.patch 0002-Port-sdl-display-to-SDL2.patch 0003-Port-sdl-draw-example-to-SDL2.patch fix_doc_installation.patch ==== gimp ==== Version update (2.10.12 -> 2.10.14) Subpackages: gimp-lang gimp-plugin-aa gimp-plugins-python libgimp-2_0-0 libgimpui-2_0-0 - bump babl and gegl deps to match configure script - Update to version 2.10.14: https://www.gimp.org/news/2019/10/31/gimp-2-10-14-released/ + Core: - New "Selected areas continue outside the image" toggle option to the "Feather Selection" dialog. - New "Allow editing on non-visible layers" setting in Preferences to allow painting, transforming, and selecting on layers with toggled off visibility. - XCF loading a bit more resilient to corruption: it doesn't stop any more at the first layer or channel error; instead it tries to load more layers/channels to salvage as much data as possible from a corrupted XCF file. - In gimp:gradient, fix dithering to correspond to how we actually round float values to 8-bit. In particular, this avoids introducing noise when a component is fixed at 0 or 1 along a segment. - New "Show All" view mode allowing to show pixels outside the canvas boundary. - New "Show Canvas Boundary" option to render a dotted line around the canvas boundary. - New "Keep Padding in "Show All" Mode" option, also available as a default option via Preferences, to preserve the padding color instead of displaying the checkerboard. - Several features updated to react as expected when run out-of-canvas: color-picking, canvas grid, transform tools, bucket fill, and more. - Loaded images' pixel density will now default to 72 PPI when no explicit resolution information was stored in the imported file. Newly created images' default pixel density will continue to be based on the default image template (with value 300 PPI if it has not be changed), yet not loaded images anymore. 72 PPI is the common default in most software (and in standards such as Exif) so it makes sense we stick to it, only for loaded images. + Tools: - Free Select tool: fast copy|cut-paste modifiers (Alt + Ctrl|Shift) are now working even when the selection is not committed. Starting a fast copy|cut-paste will automatically close the polygon and commit the selection, accelerating fast usage of free selections. - Foreground Select tool: new "Grayscale" Preview Mode. Also, a color selector for "Color" preview (original preview mode) now available, to select any color and opacity for the preview. - Add a new "Image" transform type to the transform tools, in addition to the existing "Layer", "Selection", and "Path" transform types. The "Image" mode transforms the entire image, rather than a single item. In tools with a preview, the preview shows the transformed image projection. The clipping mode controls how the canvas is clipped during the transform; in particular, the ADJUST clipping mode resizes the canvas to fit its transformed size. - In GimpFilterTool, add a new "clipping" option, which can be either Adjust or Clip. This option is controllable for layers, when there's no selection mask. When set to Adjust, which is used by default, the filter's output may extent past the drawable's boundary, and the drawable will be resized to match the output when committed. - Gradient tool: offest support in shaped gradients + Plug-ins: - Simple 8-bit port of filters to GEGL: nl-filter, film, fractal-explorer, flame, blinds, jigsaw, gradient-flare, checkerboard, tile-small, curve-bend, sample-colorize, map-object, lighting, grid, despeckle, sphere-designer, contrast-retinex, hot, sparkle, cml-explorer, destripe, twain, animation-optimize, depth-merge, warp, imagemap, gimpressionist - Port of filters to GEGL with float support: van-gogh-lic. - Add color profile support for HEIF (only when libheif 1.4.0 is available). - TIFF import will now ask (in interactive mode) how to process unspecified TIFF channels: non-premultiplied (used to be the default) alpha, premultiplied alpha, or just import as generic channel. - HEIF export now improved with same profile logics as JPEG or WebP (it can actually export higher bit-depth data, so profile logics should be the one as in PNG, but we only support 8 bpc HEIF for the time being). - HEIF export dialog now has a "Save color profile" checkbox allowing to not export with a profile when needed (needs libheif 1.4.0 or higher). - PDF exporting: text layers in layer groups are now exported as proper text. - Cleaned up the file-dds GUI, removed the "Advanced" expander. - gimptool external tool now install plug-ins into subfolders (this is not mandatory in GIMP 2.10 yet, unlike future GIMP 3, but is already the recommended folder structure for plug-ins). - 3 procedures ("color-decode-ycocg", "color-decode-ycocg-scaled" and "color-decode-alpha-exp") removed from file-dds plug-in because they are hacks which should stay internal to the plug-in and are semantically wrong because colors in drawables are never in such formats. + Filters: - New "Normal Map" filter to generate normal maps from height maps in the Generic section. - Replace old filters with GEGL operation counterparts: edge-neon (gegl:edge-neon), contrast-normalize (gegl:stretch-contrast), oilify (gegl:oilify) - Add gegl:bayer-matrix and gegl:linear-sinusoid to Filters -> Render -> Pattern. - Add gegl:newsprint to Filters -> Distorts. - Add gegl:mean-curvature-blur to Filters -> Blur. + Performance: - Add an active-thread variable to the dashboard's misc group, showing the number of active worker threads. - Reduce time complexity of layer-group translation. When translating a layer group, avoid separately updating the original area of the child layers before translating them (as per the fix to issue #3484), as this results in quadratic time complexity w.r.t. to the maximal subgroup nesting level. Instead, simply defer the updating of the group's offset until *after* translating the child layers, so that their original area isn't clipped by the parent, while their new area is still properly updated even if the parent's size changes. + User interface: - Many mnemonics added in various dialogs. - Add a gimp-rotate-image-arbitrary action, and a corresponding "Image -> Transform -> Arbitrary Rotation..." menu entry, which activates the rotate tool in image mode (similarly to the corresponding action for layers). - On Windows, minimized GIMP window is now deiconified when GIMP is run again (clicking its shortcut or otherwise). + Preferences: - New "Swap compression" option: explicit control over the tile-swap compression algorithm in GEGL. "Best performance" is used by default, "Balanced", "Best compression", and "None" (disables compression) are available. + Devel docs: - Update the libgimpconfig and libgimpbase docs. - Update docs with missing symbols and types. - New docs for structs and enums. + Debugging: - New mnemonic-clashes tool to help looking for mnemonic clashes. + Updated translations. ==== glib2 ==== Subpackages: glib2-lang glib2-tools libgio-2_0-0 libgio-2_0-0-32bit libglib-2_0-0 libglib-2_0-0-32bit libgmodule-2_0-0 libgmodule-2_0-0-32bit libgobject-2_0-0 libgobject-2_0-0-32bit libgthread-2_0-0 - Re-enable systemtap, and require systemtap-headers and systemtap-dtrace, rather than systemtap-sdt-devel, to avoid build cycle (boo#1145438). - Own /usr/share/systemtap{|tapset} directories, since we no longer have systemtap-sdt-devel in BuildRequires. - Disable lto if systemtap is enabled: build fails otherwise. ==== gtk3 ==== Subpackages: gtk3-data gtk3-immodule-amharic gtk3-immodule-inuktitut gtk3-immodule-thai gtk3-immodule-tigrigna gtk3-immodule-vietnamese gtk3-immodule-xim gtk3-lang gtk3-schema gtk3-tools libgtk-3-0 typelib-1_0-Gtk-3_0 - Don't recommend -lang subpackage ==== libgnomekbd ==== Subpackages: gnomekbd-tools libgnomekbd-lang libgnomekbd8 - Add explicit conflicts in typelib-1_0-Gkbd-3_0 and gnomekbd-tools against libgnomekbd < 3.26.1, before package split was done. ==== libqmi ==== Version update (1.22.6 -> 1.24.0) Subpackages: libqmi-glib5 libqmi-tools - Update to version 1.24.0: + Various new services, requests and firmware update support added. ==== librsvg ==== Subpackages: gdk-pixbuf-loader-rsvg librsvg-2-2 librsvg-lang rsvg-thumbnailer typelib-1_0-Rsvg-2_0 - Add patches to fix coloring of symbolic icons (glgo#GNOME/librsvg#525): * 0001-croco.rs-Add-struct-definition-for-CRSimpleSel.patch * 0002-Compute-the-specificity-of-CSS-selectors.patch * 0003-525-Consider-specificity-when-applying-CSS-selector-.patch - Remove BuildRequires rust-std. The replacement rust-std-static is already required by rust. ==== libtommath ==== Version update (1.0 -> 1.2.0) - update License tag in specfile (project relicensed to Unlicense in upstream v1.1.0-rc1) - upgrade to version 1.2.0 * API refactoring, some functions marked as deprecated * functions returning a value marked with "warn on unused result" * FIPS 186.4 complient prime checking * two's complement functions and mp_{set,get}_double() * mp_rand() has multiple native random provider implementations * add mp_decr(), mp_incr() and mp_log_u32() * various improvements * provide pkgconfig file - adjust build and install section to match upstream changes ==== pipewire ==== Version update (0.2.6 -> 0.2.7) Subpackages: libpipewire-0_2-1 pipewire-modules pipewire-spa-plugins pipewire-spa-tools pipewire-tools - Update to version 0.2.7: + Add support for alsa-lib 1.1.9 which changed the include path + Improve error checking and reporting in the protocol + deviceprovider: fix probing without starting + add sentinel to some functions + compiler fixes for musl + Revert object tree permission checks that broke things, this is probably not a good idea (and the tree of objects is going to be removed later) ==== procmail ==== - Add latest patch sets from Debian: * patch set 27 replaces procmail-3.22-CVE-2014-3618.patch * patch set 28 does fix off-by-one error that makes procmail to segfault on certain .procmailrc files * patch set 29 does fix formail memory corruption * patch set 30 replaces procmail-formisc.c.patch for CVE-2017-16844 - Remove obsolate patches * procmail-3.22-CVE-2014-3618.patch * procmail-formisc.c.patch ==== salt ==== Subpackages: python3-salt salt-master salt-minion - Remove virt.pool_delete fast parameter (U#54474) - Added: * remove-virt.pool_delete-fast-parameter-178.patch - Remove unnecessary yield causing BadYieldError (bsc#1154620) - Added: * remove-unnecessary-yield-causing-badyielderror-bsc-1.patch - Prevent 'Already reading' continuous exception message (bsc#1137642) - Added: * prevent-already-reading-continuous-exception-message.patch ==== spamassassin ==== Subpackages: perl-Mail-SpamAssassin - update spampd to 2.53 * Fix LMTP delivery with multiple recipients * Fix Warning for "Use of uninitialized value in string" update spampd to 2.52 * Override Net::Server's HUP handling, just restart children * Add --version option to print information about SpamPD, Net::Server, SpamAssassin, and Perl. * Add warnings about using deprecated options. * Documentation updates and code cosmetics. - Update download links (add for spampd and iXhash2 sources) - Add source verification (add spamassassin.keyring) - Add %{perl_requires} for perl-Mail-SpamAssassin - Fix "PIDFile= references a path below legacy directory /var/run/" (change /var/run/ -> /run/) - Don't package README.SuSE which documents an init script that was never bundled ==== webkit2gtk3 ==== Version update (2.26.1 -> 2.26.2) 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.26.2: + Improve performance of querying system fallback fonts. + Don't use prgname in dbus-proxy socket path. + Fix thread-safety issues in image decoders. + Fix the build with WebDriver disabled. + Disable accelerated compositing when we fail to initialize the EGL dispaly under Wayland. + Fill the objects category in emoji picker. + Fix several crashes and rendering issues. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12. 11. 19, 8:16, Andrei Borzenkov wrote:
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108 thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/12/19 6:00 PM, Jiri Slaby wrote:
On 12. 11. 19, 8:16, Andrei Borzenkov wrote:
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108
thanks,
For what its worth 1.15.0 is older then 1.15.0-alpha1, which is why in most of my packages I swapped to using 1.15.0~alpha1 for my occasional pre releases. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 12. 11. 19, 9:00, Simon Lees wrote:
On 11/12/19 6:00 PM, Jiri Slaby wrote:
On 12. 11. 19, 8:16, Andrei Borzenkov wrote:
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108
thanks,
For what its worth 1.15.0 is older then 1.15.0-alpha1, which is why in most of my packages I swapped to using 1.15.0~alpha1 for my occasional pre releases.
Sure, I meant "in the above case we use"... Of course, you need the opposite in your example. -- js suse labs
On Tuesday, 12 November 2019 9:00 Simon Lees wrote:
For what its worth 1.15.0 is older then 1.15.0-alpha1, which is why in most of my packages I swapped to using 1.15.0~alpha1 for my occasional pre releases.
Using "-" is also confusing as it makes the boundary between version and release less obvious, I would suggest to avoid it if possible. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Nov 12 2019, Michal Kubecek wrote:
Using "-" is also confusing as it makes the boundary between version and release less obvious, I would suggest to avoid it if possible.
You cannot use `-' in a Version: tag in RPM anyway. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2019-11-12 09:18, Michal Kubecek wrote:
On Tuesday, 12 November 2019 9:00 Simon Lees wrote:
For what its worth 1.15.0 is older then 1.15.0-alpha1, which is why in most of my packages I swapped to using 1.15.0~alpha1 for my occasional pre releases.
Using "-" is also confusing as it makes the boundary between version and release less obvious, I would suggest to avoid it if possible.
RPM does not allow '-' there anyway because that is already the separator for version and release. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Nov 12, 2019 at 08:30:40AM +0100, Jiri Slaby wrote:
On 12. 11. 19, 8:16, Andrei Borzenkov wrote:
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108
Exactly. And I thought that the standard way of versioning software built from unreleased git snapshoits is %PARENT_TAG%+git.%cd. Or eventually just %cd if the project does not have any tags and releases. But it seems that we don't always stick to it and IMO we should. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 12 November 2019 12:25 Michal Rostecki wrote:
Exactly. And I thought that the standard way of versioning software built from unreleased git snapshoits is %PARENT_TAG%+git.%cd. Or eventually just %cd if the project does not have any tags and releases. But it seems that we don't always stick to it and IMO we should.
Some projects update their internal version identifier right after a release while others do it right before or at the time of the release. In either case, I believe, it's preferrable to make package version consistent with what the software says about itself so both "~" and "+" options have their use. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2019-11-12 12:25, Michal Rostecki wrote:
On Tue, Nov 12, 2019 at 08:30:40AM +0100, Jiri Slaby wrote:
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108
Exactly. And I thought that the standard way of versioning software built from unreleased git snapshoits is %PARENT_TAG%+git.%cd. Or eventually just %cd if the project does not have any tags and releases.
Worry not, even that case is covered: use 0~%cd. This practically sorts before anything else. (The only way upstream could break it is by making a really nondescript release number like 0~0 itself. But if they are smart, they will use 0~beta1/0~rc1 at the very least and all is well.) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/12/19 11:13 PM, Jan Engelhardt wrote:
On Tuesday 2019-11-12 12:25, Michal Rostecki wrote:
On Tue, Nov 12, 2019 at 08:30:40AM +0100, Jiri Slaby wrote:
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Right, that's why we use dot or plus: $ zypper versioncmp 1.15.0 1.15.0~20191108 1.15.0 is newer than 1.15.0~20191108 $ zypper versioncmp 1.15.0 1.15.0.20191108 1.15.0 is older than 1.15.0.20191108 $ zypper versioncmp 1.15.0 1.15.0+20191108 1.15.0 is older than 1.15.0+20191108
Exactly. And I thought that the standard way of versioning software built from unreleased git snapshoits is %PARENT_TAG%+git.%cd. Or eventually just %cd if the project does not have any tags and releases.
Worry not, even that case is covered: use 0~%cd. This practically sorts before anything else. (The only way upstream could break it is by making a really nondescript release number like 0~0 itself. But if they are smart, they will use 0~beta1/0~rc1 at the very least and all is well.)
Yeah I have upstreams who tag there pre releases with 1.15.0-alpha1 so you end up with 1.14.99 -> 1.15.0-alpha1 -> 1.15.0 which makes it impossible to use tags, so I have to change that part manually every release. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 12/11/2019 09:16, Andrei Borzenkov wrote:
On Tue, Nov 12, 2019 at 9:00 AM ASSI <Stromeko@nexgo.de> wrote:
==== c-ares ==== Version update (1.15.0 -> 1.15.0~20191108)
Zypper instead considers this a downgrade?
Actually it is. The "~" convention originates in Debian and is used to denote pre-releases. So you can have v1.4 and during development v1.5~rc1, v1.5~rc2 etc which are newer than v1.4 but will be considered older when v1.5 final is released.
Thanks, I normally use 1.4.99 for prerelease 1.5.0-alpha, I can now use ~ Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2019-11-12 05:01, Dominique Leuenberger rašė:
Packages changed: Mesa (19.2.2 -> 19.2.3) Mesa-drivers (19.2.2 -> 19.2.3)
Please don't use Mesa 19.2.3 which causes incomplete rendering on all mesa drivers! Either stick to earlier version or update to Mesa 19.2.4. Update to version Mesa 19.2.4 is available in X11:XOrg repository. Mesa 19.2.4 is an emergency release, to fix a critical bug found in the 19.2.3 release. This release contains a single patch to fix that bug. -- Regards, Mindaugas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/16/19 1:34 AM, opensuse.lietuviu.kalba wrote:
2019-11-12 05:01, Dominique Leuenberger rašė:
Packages changed: Mesa (19.2.2 -> 19.2.3) Mesa-drivers (19.2.2 -> 19.2.3)
Please don't use Mesa 19.2.3 which causes incomplete rendering on all mesa drivers! Either stick to earlier version or update to Mesa 19.2.4. Update to version Mesa 19.2.4 is available in X11:XOrg repository. Mesa 19.2.4 is an emergency release, to fix a critical bug found in the 19.2.3 release. This release contains a single patch to fix that bug. Thanks Mindaugas....I had to change vendors though.......thanks again!!
-- Regards, Mindaugas
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (12)
-
Andreas Schwab
-
Andrei Borzenkov
-
ASSI
-
Dave Plater
-
Dominique Leuenberger
-
Jan Engelhardt
-
Jiri Slaby
-
Michal Kubecek
-
Michal Rostecki
-
mike
-
opensuse.lietuviu.kalba
-
Simon Lees