[opensuse-factory] New Tumbleweed snapshot 20180709 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=20180709 When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: enblend-enfuse freeipmi (1.5.7 -> 1.6.2) llvm6 python-keyring (10.5.0 -> 13.0.0) squid (4.0.25 -> 4.1) xdg-desktop-portal-kde === Details === ==== enblend-enfuse ==== - Switched to cmake build * Removed patch for autotools: enblend-latex-optional.patch - Added enblend-enfuse-4.2-add-missing-cmakelists.patch - Enabled support for OpenMP - Enabled support for SSE2 - Turn on optimizations again - Info pages are no longer available - Added PDF documentation for enblend and enfuse ==== freeipmi ==== Version update (1.5.7 -> 1.6.2) Subpackages: libfreeipmi17 libipmiconsole2 libipmidetect0 libipmimonitoring6 - Update to 1.6.2 o Fix error in bridging where bridged requests were sent to the wrong LUN. o Fix command parsing bugs in legacy ipmi-config scripts (i.e. bmc-config, ipmi-pef-config, etc.) o Do not output full path of daemons in syslog, output only the daemon name (i.e. output "ipmidetected" instead of "/usr/sbin/ipmidetectd"). o Update channel range from 0-7 to 0-11, per errata IPMI update. - Update to 1.6.1 o Add IPv6 hostname support to FreeIPMI, all of FreeIPMI can now take IPv6 addresses as inputs to "host" parameters, options, or inputs. o Support significant portions of IPMI IPv6 configuration in libfreeipmi. o Add --no-session option in ipmi-raw. o Add SDR cache options to ipmi-config. o Legacy -f short option for --flush-cache and -Q short option for quiet-cache. Backwards compatible for tools that supported it before. o In ipmi-oem, support Gigabyte get-bmc-services and set-bmc-services. o Various performance improvements: - Remove excessive calls to secure_memset to clear memory. - Remove excessive memsets and clears of data. - Remove unnecessary "double input checks". - Remove expensive input checks in libfreeipmi fiid library. Fallout from this may include FIID_ERR_FIELD_NOT_FOUND errors in different fiid functions. - Remove unnecessary input checks in libfreeipmi fiid library. - Add recent 'lookups' of fields in fiid library to internal cache. o Various minor fixes/improvements - Update libfreeipmi core API to use poll() instead of select(), to avoid issues with applications with a high number of threads. - As a side point, while IPv6 networking support has been added, IPv6 configuration in ipmi-config & bmc-config is not supported in this release. ==== llvm6 ==== Subpackages: libLLVM6 libclang6 - llvm6-fix-gdb-index-crash.patch * From upstream, fix lld --gdb-index crash. ==== python-keyring ==== Version update (10.5.0 -> 13.0.0) - Version update to 13.0.0: * #327: In kwallet backend, if the collection or item is locked, a ``KeyringLocked`` exception is raised. Clients expecting a None response from ``get_password`` under this condition will need to catch this exception. Additionally, an ``InitError`` is now raised if the connection cannot be established to the DBus. * #298: In kwallet backend, when checking an existing handle, verify that it is still valid or create a new connection. * Fixed issue in SecretService. Ref #226. * #322: Fix AttributeError when ``escape.__builtins__`` is a dict. * Deprecated ``keyring.util.escape`` module. If you use this module or encounter the warning (on the latest release of your packages), please `file a ticket <https://github.com/jaraco/keyring/issues/new>`_. * Unpin SecretStorage on Python 3.5+. Requires that Setuptools 17.1 be used. Note that the special handling will be unnecessary once Pip 9 can be assumed (as it will exclude SecretStorage 3 in non-viable environments). * #310: Keyring now loads all backends through entry points. * #312: Use ``entrypoints`` instead of pkg_resources to avoid performance hit loading pkg_resources. Adds a dependency on ``entrypoints``. * #294: No longer expose ``keyring.__version__`` (added in 8.1) to avoid performance hit loading pkg_resources. * #299: Keyring exceptions are now derived from a base ``keyring.errors.KeyringError``. * #296: Prevent AttributeError on import when Debian has created broken dbus installs. ==== squid ==== Version update (4.0.25 -> 4.1) - New upstream stable version 4.1: + Fix --with-netfilter-conntrack error message + Supply ALE for force_request_body_continuation ACL ==== xdg-desktop-portal-kde ==== Subpackages: xdg-desktop-portal-kde-lang - Enable screencast support for TW -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version. I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?) So I had to get the wxWidgets-3_0 source package and build it myself :(( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Still no changes. Voted for bug. On 2018-07-12 21:01, Peter Suetterlin wrote:
Hi,
is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version.
I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?)
So I had to get the wxWidgets-3_0 source package and build it myself :(( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 17/07/2018 10:03, Konstantin Voinov ha scritto:
Still no changes. Voted for bug.
On 2018-07-12 21:01, Peter Suetterlin wrote:
Hi,
is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version.
I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?)
So I had to get the wxWidgets-3_0 source package and build it myself :((
I would like to have this resolved as well for wxwidgets in TW. Thanks and regards! Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Il 17/07/2018 11:37, Marco Calistri ha scritto:
Il 17/07/2018 10:03, Konstantin Voinov ha scritto:
Still no changes. Voted for bug.
On 2018-07-12 21:01, Peter Suetterlin wrote:
Hi,
is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version.
I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?)
So I had to get the wxWidgets-3_0 source package and build it myself :((
I would like to have this resolved as well for wxwidgets in TW.
Thanks and regards!
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Suppose that the garbages on my signature are caused by my e-mail client... -- Parts that positively cannot be assembled in improper order will be. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
* Marco Calistri <mcalistri@hotmail.com> [07-17-18 14:00]:
Il 17/07/2018 11:37, Marco Calistri ha scritto:
Il 17/07/2018 10:03, Konstantin Voinov ha scritto:
Still no changes. Voted for bug.
On 2018-07-12 21:01, Peter Suetterlin wrote:
Hi,
is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version.
I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?)
So I had to get the wxWidgets-3_0 source package and build it myself :((
I would like to have this resolved as well for wxwidgets in TW.
Thanks and regards!
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Suppose that the garbages on my signature are caused by my e-mail client... -- Parts that positively cannot be assembled in improper order will be. N?????r??y隊Z)z{.???r?+?맲??r??z?^?ˬz??N?(?֜??^? ޭ隊Z)z{.???r?+??0???????Ǩ
does look a mess, what you quoted, but I don't see it. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Marco Calistri <mcalistri@hotmail.com> [07-17-18 14:00]:
Il 17/07/2018 11:37, Marco Calistri ha scritto:
Il 17/07/2018 10:03, Konstantin Voinov ha scritto:
Still no changes. Voted for bug.
On 2018-07-12 21:01, Peter Suetterlin wrote:
Hi,
is there a way you can trigger a (re)build of the wxwidgets package? The current libs are compiled with the old compiler, so anything you compile yourself on an up-to-date TW system will fail to run with a mismatch in ABI version.
I had filed a bug report (boo#1100497) but there was no reaction to it so far. (is there a way I can check myself what is scheduled for coming TW snapshots?)
So I had to get the wxWidgets-3_0 source package and build it myself :((
I would like to have this resolved as well for wxwidgets in TW.
Thanks and regards!
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Suppose that the garbages on my signature are caused by my e-mail client... -- Parts that positively cannot be assembled in improper order will be. N?????r??y隊Z)z{.???r?+?맲??r??z?^?ˬz??N?(?֜??^? ޭ隊Z)z{.???r?+??0???????Ǩ
does look a mess, what you quoted. but not what I see. why would you not say what email client you are using if you question it's validity? I would guess more a problem of it not being configured correctly, ie: user problem rather than the email client. probably charset? and probably not related to subj: ..wxwidgets libs.. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2018-07-17 19:59, Marco Calistri wrote:
Marco N???????????????r??????y隊Z)z{.?????????r???+???맲??????r??????z???^???ˬz??????N???(???֜??????^??? ޭ隊Z)z{.?????????r???+??????0???????????????Ǩ???
Suppose that the garbages on my signature are caused by my e-mail client...
No, it's caused by the list software which forgets to upconvert the character set of your email so that the (then-edited) email is able to represent both your content and the appended footer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-------- Original Message -------- From: Jan Engelhardt Sent: Tuesday, Jul 17, 2018 4:56 PM SAE To: Marco Calistri Cc: opensuse-factory@opensuse.org Subject: [opensuse-factory] TW: outdated wxwidgets libs
On Tuesday 2018-07-17 19:59, Marco Calistri wrote:
Marco N???????????????r??????y隊Z)z{.?????????r???+???맲??????r??????z???^???ˬz??????N???(???֜??????^??? ޭ隊Z)z{.?????????r???+??????0???????????????Ǩ???
Suppose that the garbages on my signature are caused by my e-mail client...
No, it's caused by the list software which forgets to upconvert the character set of your email so that the (then-edited) email is able to represent both your content and the appended footer.
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one. Cheers, Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
On Tuesday 2018-07-17 21:59, Marco Calistri wrote:
-------- Original Message -------- From: Jan Engelhardt Sent: Tuesday, Jul 17, 2018 4:56 PM SAE To: Marco Calistri Cc: opensuse-factory@opensuse.org Subject: [opensuse-factory] TW: outdated wxwidgets libs
On Tuesday 2018-07-17 19:59, Marco Calistri wrote:
Marco N???????????????r??????y隊Z)z{.?????????r???+???맲??????r??????z???^???ˬz??????N???(???֜??????^??? ޭ隊Z)z{.?????????r???+??????0???????????????Ǩ???
Suppose that the garbages on my signature are caused by my e-mail client...
No, it's caused by the list software which forgets to upconvert the character set of your email so that the (then-edited) email is able to represent both your content and the appended footer.
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one.
[PM Do you know if there is some Thunderbird extension or even settings which could avoid the character-set convertion mispelling by the list software?]
Cheers,
Marco N?????r??y隊Z)z{.???r????????r??z?^?ˬz????(?֜???? ޭ隊Z)z{.???r????0???????Ǩ?
It is the "Content-Transfer-Encoding: base64" in your mail. (This is independent of Content-Type: ..utf-8) Whether it is your MUA or the outlook.com MTA that does this, I cannot tell for sure, and I do not remember any knobs in software to influence this. Either way, it is a opensuse.org list software (-> mlmmj) bug to blindly append the footer whilst ignoring C-T-E. Their tracker is here: http://mlmmj.org/bugs/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/07/18 21:59, Marco Calistri wrote:
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one.
Cheers,
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩrg==
See above. Happens in Thunderbird for Linux, too. :-/ -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 18/07/2018 06:32, Liam Proven ha scritto:
On 17/07/18 21:59, Marco Calistri wrote:
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one.
Cheers,
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩrg==
See above. Happens in Thunderbird for Linux, too. :-/
As promised here I'm replying from my Linux TW system. The difference I see now is that here the Tbird settings default char-set encoding is ISO-8859-1 while on Windows Tbird it is set as UTF-8, so appartently the mlmmj dislike UTF-8 encoding in signature. In other terms when I sent or reply email on opensuse ML by Rbird Linux I put: Content-Type: text/plain; charset="Windows-1252" in my source message while when I sent or reply email on opensuse ML by my Windows Tbird, I put: Content-Type: text/plain; charset="utf-8" Best regards, -- Marco Calistri Build: openSUSE Tumbleweed 20180712 Kernel: 4.17.2-2.gddde22d-default - Cinnamon 3.8.7
* Marco Calistri <mcalistri@hotmail.com> [07-19-18 17:32]:
Il 18/07/2018 06:32, Liam Proven ha scritto:
On 17/07/18 21:59, Marco Calistri wrote:
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one.
Cheers,
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩrg==
See above. Happens in Thunderbird for Linux, too. :-/
As promised here I'm replying from my Linux TW system.
The difference I see now is that here the Tbird settings default char-set encoding is ISO-8859-1 while on Windows Tbird it is set as UTF-8, so appartently the mlmmj dislike UTF-8 encoding in signature.
In other terms when I sent or reply email on opensuse ML by Rbird Linux I put: Content-Type: text/plain; charset="Windows-1252" in my source message while when I sent or reply email on opensuse ML by my Windows Tbird, I put: Content-Type: text/plain; charset="utf-8"
what really has this to do with the development of opensuse factory? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 19/07/2018 20:47, Patrick Shanahan ha scritto:
* Marco Calistri <mcalistri@hotmail.com> [07-19-18 17:32]:
Il 18/07/2018 06:32, Liam Proven ha scritto:
On 17/07/18 21:59, Marco Calistri wrote:
Thanks for your smart response dude. This happens just on my Windows Thunderbird client and not on my Linux TW one.
Cheers,
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩrg==
See above. Happens in Thunderbird for Linux, too. :-/
As promised here I'm replying from my Linux TW system.
The difference I see now is that here the Tbird settings default char-set encoding is ISO-8859-1 while on Windows Tbird it is set as UTF-8, so appartently the mlmmj dislike UTF-8 encoding in signature.
In other terms when I sent or reply email on opensuse ML by Rbird Linux I put: Content-Type: text/plain; charset="Windows-1252" in my source message while when I sent or reply email on opensuse ML by my Windows Tbird, I put: Content-Type: text/plain; charset="utf-8"
what really has this to do with the development of opensuse factory?
Absolutely nothing! Apologize for the "noise". This is the last reply on this topic. But hopefully the mailing list software being updated soon. -- Marco Calistri Opensuse Tumbleweed Lenovo Z470 N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Marco Calistri wrote:
Marco N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Suppose that the garbages on my signature are caused by my e-mail client... The root cause of the garbage is, that the openSUSE mailing list software MLMMJ does not decode Base64 encoded mails before appending the mailing list footer and then re-encode the result back to Base64.
So Base64 encoded mails contain a mixture of Base64 and text after appending the mailing list footer. The mail looks like this in source: Content-Type: text/plain; charset="utf-8" Content-ID: <AF8720025E5E6D48B8BCC1844C1A03EB@eurprd09.prod.outlook.com> Content-Transfer-Encoding: base64 [...] aGF2ZSB0aGlzIHJlc29sdmVkIGFzIHdlbGwgZm9yIHd4d2lkZ2V0cyBpbiBUVy4NCg0KVGhhbmtz IGFuZCByZWdhcmRzIQ0KDQpNYXJjbw0K -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org The bug is only visible, if a sender uses an e-mail client which uses Base64 per default, e.g. Outlook. The problem was already discussed, but until now, nobody tried to fix MLMMJ (for openSUSE). Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
четвер, 12 липня 2018 р. 14:01:46 EEST Peter Suetterlin написано:
So I had to get the wxWidgets-3_0 source package and build it myself :((
Update was accepted [1] at July, 13, but latest snapshot was 0712, so it should be fixed in next snapshot, if I understood it correctly. [1] https://build.opensuse.org/request/show/621874 -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський
participants (9)
-
Bjoern Voigt -
Dominique Leuenberger -
Jan Engelhardt -
Konstantin Voinov -
Liam Proven -
Marco Calistri -
Mykola Krachkovsky -
Patrick Shanahan -
Peter Suetterlin