Bug#993994: vulkan-validationlayers: Requesting VK_LAYER_KHRONOS_validation crash with undefined symbol: _Z14GetEnvironmentB5cxx11PKc
Package: vulkan-validationlayers Version: 1.2.189.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: kienan.stew...@burntworld.ca Dear Maintainer, I am developing an application that uses vulkan, and for debugging includes the validation layer. After a recent upgrade to 1.2.189.0-1, the application began crashing with the following error symbol lookup error: /lib/x86_64-linux-gnu/libVkLayer_khronos_validation.so: undefined symbol: _Z14GetEnvironmentB5cxx11PKc I think the previous working version I had installed was 1.2.162.0-1. I am able to run the application when not requesting the validation layer. I was also able to reproduce this issue by doing the following * Opening qrenderdoc * Selecting a vulkan-based application, eg. /usr/bin/vkcube (from vulkan-tools) * Running the application with the default settings (will work) * Now, check the "Enable API Validation" under the Launch Application capture options * Running the application will cause it to immediately crash /usr/bin/vkcube: symbol lookup error: /lib/x86_64-linux-gnu/libVkLayer_khronos_validation.so: undefined symbol: _Z14GetEnvironmentB5cxx11PKc This appears related to upstream issue https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/2941 where jengelh resolved it in OpenSuse by prefixing the GetEnvironment declaration in layers/vk_layer_config.h with VK_LAYER_EXPORT. Ref: https://build.opensuse.org/package/view_file/openSUSE:Factory/vulkan-validationlayers/ver.diff?expand=1 thanks, kienan -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vulkan-validationlayers depends on: ii libc6 2.32-2 ii libgcc-s1 11.2.0-4 ii libstdc++6 11.2.0-4 vulkan-validationlayers recommends no packages. vulkan-validationlayers suggests no packages. -- no debconf information
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
On Tue, Mar 12, 2019 at 10:22:52AM +0200, Apollon Oikonomopoulos wrote: > Control: tags -1 - moreinfo + patch pending > Control: severity -1 serious > > OK, thanks for confirming this and thanks for the detailed report, it's > very helpful! > > I'm bumping this bug to RC, as I don't think Puppet report storage > should break merely by installing an unrelated Ruby package. > Additionally this is a regression from Puppet 4.x. > > So, here's what's happening: > > - Puppet 5 switched from a custom wire format (PSON) to JSON for >transmitting facts and reports. > - There is no issue when using the ruby-json JSON library to parse >reports. > - Some JSON libraries (Oj and JrJackson) de-serialize floats with many >decimal digits - such as the timing metrics found in a Puppet agent >report - as BigDecimal. > - When BigDecimal's are serialized again to JSON, they are serialized >as Strings (and not floats), causing PuppetDB's schema validation to >fail. > - This path is only triggered when ruby-oj and ruby-multi-json are >installed, enabling Puppet to use Oj via multi-json. (JrJackson is >Jruby-only, and there are provisions upstream handling BigDecimal >conversion in this case). > > Your patch fixes the issue, but it does so right before the report is > transmitted to PuppetDB. I think it's best to instruct Oj to never > deserialize floats as BigDecimals and avoid having to do any conversions > in the first place. Additionally, this will guard all other report > processors (e.g. store) which might want to handle metrics against > similar issues. > > Can you test the attached patch and confirm that it works? > Hi, I applied the patch (reloaded apache2 afterwards) and runs are able to store reports now. (I did confirm before the patch was applied that the reports were not being stored). Thanks for the great explanation, your effort and time, and the patch! Thanks, Kienan > Regards, > Apollon signature.asc Description: PGP signature
Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)
user debian-rele...@lists.debian.org usertag 919737 + bsp-2019-01-ca-montreal tags 919737 + unreproducible moreinfo thank you Hi, I tried building this package (underscore-1.8.3~dfsg) in a clean buster chroot (with sbuild) and a clean unstable chroot (also with sbuild), and it worked in both cases. Thanks, Kienan signature.asc Description: PGP signature
Bug#904657: update
user debian-rele...@lists.debian.org usertags 904657 + bsp-2019-01-ca-montreal tags 904657 + patch thank you Hi, I tested a proposed patch from the upstream github repository which allows the package to build and run : https://github.com/snare/voltron/pull/243 I'm not sure if there are other side-effects to the patch, since the async (now asynchronous) variable is not directly used but could be referred to elsewhere. Thanks, Kienan
Bug#890689: ruby-rgen FTBFS with ruby 2.5
Hi,
These errors happen in ruby >= 2.4 since Fixnum and Bignum were merged into
Integer.
The following upstream commit fixes the issue:
https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf
Attached is a patch to the debian source from
https://salsa.debian.org/ruby-team/ruby-rgen which applies the above commit.
Thanks,
Kienan
diff --git a/debian/patches/fix-test-for-ruby-2.4 b/debian/patches/fix-test-for-ruby-2.4
new file mode 100644
index 000..bb94b79
--- /dev/null
+++ b/debian/patches/fix-test-for-ruby-2.4
@@ -0,0 +1,52 @@
+Description: Fix tests for ruby 2.4
+ This applies commit 1124f4303db52973967e78d93512a1c1b64f23cf which
+ lets the tests pass. In ruby 2.4 Fixnum and Bignum were merged into
+ Integer
+ .
+ ruby-rgen (0.8.0-1) unstable; urgency=medium
+ .
+ [ Cédric Boutillier ]
+ * Bump debhelper compatibility level to 9
+ * Remove version in the gem2deb build-dependency
+ * Use https:// in Vcs-* fields
+ * Bump Standards-Version to 3.9.7 (no changes needed)
+ * Run wrap-and-sort on packaging files
+ .
+ [ Stig Sandbeck Mathisen ]
+ * Declare compliance with Debian policy 3.9.8
+ * Imported upstream release 0.8.0
+Author: Stig Sandbeck Mathisen
+
+Origin: https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf
+Bug-Debian: https://bugs.debian.org/890689
+Last-Update: 2019-01-19
+
+--- ruby-rgen-0.8.0.orig/test/metamodel_builder_test.rb
ruby-rgen-0.8.0/test/metamodel_builder_test.rb
+@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise StandardError do
+ sc.name = 5
+ end
+-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+ assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
+
+ assert_equal "xtest", sc.stringWithDefault
+@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+ o.addLiterals(1)
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+
+ assert_equal [], o.literals
+ o.addLiterals("a")
+@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+ o.literals = 1
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
+
+ o.bools = [true, false, true, false]
+ assert_equal [true, false, true, false], o.bools
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..ae45377
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fix-test-for-ruby-2.4
diff --git a/test/metamodel_builder_test.rb b/test/metamodel_builder_test.rb
index 4567a86..2ce7d2f 100644
--- a/test/metamodel_builder_test.rb
+++ b/test/metamodel_builder_test.rb
@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise StandardError do
sc.name = 5
end
-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
assert_equal "xtest", sc.stringWithDefault
@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise(StandardError) do
o.addLiterals(1)
end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
assert_equal [], o.literals
o.addLiterals("a")
@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise(StandardError) do
o.literals = 1
end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
o.bools = [true, false, true, false]
assert_equal [true, false, true, false], o.bools
Bug#859539: filezilla: Filezilla crashes at startup
Hi, I was unable to reproduce this bug on a clean install (QEMU VM), or on my laptop which had been upgraded from Jessie to Stretch some time ago. I followed the test proposed by John earlier. Perhaps there are some details in the config file or the bookmark path that may be pertinent to provoking this bug? What is the "Language Code" setting in filezilla.xml? filezilla: Installed: 3.24.0-1 Thanks, Kienan signature.asc Description: PGP signature
