perl

2016-03-01 Thread Elan Ruusamäe
+ /usr/bin/perl Makefile.PL 
'INSTALLVENDORSCRIPT=/usr/lib/nagios/plugins' 'INSTALLDIRS=vendor'

Generating a Unix-style Makefile
Writing Makefile for App::Monitoring::Plugin::CheckRaid
"\x{00c3}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00a4}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00c3}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00a4}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00c3}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00a4}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00c3}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.
"\x{00a4}" does not map to ascii at 
/usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm line 1182.

Writing MYMETA.yml and MYMETA.json

➔ showline /usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm:1182
==> /usr/share/perl5/5.22.0/ExtUtils/MakeMaker.pm <==
1177:for my $chunk (@{$self->{RESULT}}) {
1178:my $to_write = "$chunk\n";
1179:if (!$CAN_DECODE && $] > 5.008) {
1180:utf8::encode $to_write;
1181:}
1182:print $fh "$chunk\n"
1183:or die "Can't write to MakeMaker.tmp: $!";
1184:}
1186:close $fh
1187:or die "Can't write to MakeMaker.tmp: $!";
1188:_rename("MakeMaker.tmp", $finalname) or

i  think it doesn't like the a uml here:

WriteMakefile(
NAME => 'App::Monitoring::Plugin::CheckRaid',
AUTHOR => 'Elan Ruusamäe ',
EXE_FILES => ['bin/check_raid.pl'],
);


[~/rpm/packages/BUILD.x86_64-linux/nagios-plugin-check_raid-4.0.1(?)] ➔ 
grep AUTHOR Makefile

# AUTHOR => [q[Elan Ruusam\x{00c3}\x{00a4}e ]]
$(NOECHO) $(ECHO) 'Elan Ruusam\x{00c3}\x{00a4}e 
' >> $(DISTNAME).ppd



i wonder what's the way to solve it?

LC_ALL=C.UTF-8? or should encode non-ascii differently?




--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: Fwd: [packages/thefuck] python3.spec hack

2016-03-01 Thread Elan Ruusamäe

On 01.03.2016 14:30, Jacek Konieczny wrote:


It would probably be better to patch thefuck not to require this. The 
requirement is probably defined in setup.py and could be removed with 
one line change.

it's in thefuck setup.py because for python2 there exists as backport

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: Vulkan 3D drivers test request

2016-03-01 Thread Jacek Konieczny

On 2016-03-01 12:32, Łukasz Maśko wrote:

Dnia czwartek, 25 lutego 2016 13:12:31 Jacek Konieczny pisze:

Hi,

I have made the Vulkan packages and would like someone to test those on
a different system and hardware.

To play with Vulkan you need:

1. the Vulkan loader
2. a Vulkan Installable Client Driver (ICD)
3. a Vulkan application


Well... The demos seem to work for me:


With the latest Mesa-vulkan-icd-intel snapshots they work for me too. 
Though The Talos Principle still does not.



VkPhysicalDeviceProperties:
===
apiVersion = 4194306
driverVersion  = 1
vendorID   = 0x8086
deviceID   = 0x1616
deviceType = INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 5500 (Broadwell GT2)


So it is better that mine and the one better supported but the driver.


[...]
(too long to include everything). I have run vulcan-cube and vulcan-tri (looks
a bit strange). I have not tried anything else.


Yes, vulkan-tri is strange… it probably tests something we don't 
understand ;-)


Thanks!

Jacek
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: Fwd: [packages/thefuck] python3.spec hack

2016-03-01 Thread Jacek Konieczny

On 2016-03-01 13:06, Elan Ruusamäe wrote:

On 01.03.2016 13:12, Jacek Konieczny wrote:


You could add egg-info file/directory for pathlib to python3.spec.

so. empty file/dir will do?


No. It should be a proper PKG-INFO file.

Though, I have changed my mind…

As it is now a standard part of Python3 and Python does not include 
those egg-info file, then I think we should no do things different in PLD.


It would probably be better to patch thefuck not to require this. The 
requirement is probably defined in setup.py and could be removed with 
one line change.


Jacek

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: Fwd: [packages/thefuck] python3.spec hack

2016-03-01 Thread Elan Ruusamäe

On 01.03.2016 13:12, Jacek Konieczny wrote:


You could add egg-info file/directory for pathlib to python3.spec. 

so. empty file/dir will do?

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: Vulkan 3D drivers test request

2016-03-01 Thread Łukasz Maśko
Dnia czwartek, 25 lutego 2016 13:12:31 Jacek Konieczny pisze:
> Hi,
> 
> I have made the Vulkan packages and would like someone to test those on
> a different system and hardware.
> 
> To play with Vulkan you need:
> 
> 1. the Vulkan loader
> 2. a Vulkan Installable Client Driver (ICD)
> 3. a Vulkan application

Well... The demos seem to work for me:

$ rpm -qa | grep vulkan
Mesa-vulkan-icd-intel-0.s20160220-4.x86_64
vulkan-loader-1.0.3.0-3.s20160223.5.x86_64
vulkan-sdk-tools-1.0.3.0-3.s20160223.5.x86_64
vulkan-sdk-demos-1.0.3.0-3.s20160223.5.x86_64
$ vulkaninfo
===
VULKAN INFO
===

Vulkan API Version: 1.0.3

INFO: [loader] Code 0 : Found manifest file 
/usr/share/vulkan/explicit_layer.d/VkLayer_vktrace_layer.json, version "1.0.0"
INFO: [loader] Code 0 : Found manifest file /usr/share/vulkan/icd.d/Mesa-
intel_icd.json, version "1.0.0"
Instance Extensions and layers:
===
Instance Extensions count = 4
VK_KHR_surface  : extension revision 25
VK_KHR_xcb_surface  : extension revision  5
VK_KHR_wayland_surface  : extension revision  4
VK_EXT_debug_report : extension revision  1

Instance Layers count = 1
VK_LAYER_LUNARG_vktrace (Vktrace tracing library) Vulkan version 
1.0.3, layer version 1
VK_LAYER_LUNARG_vktrace Extensions  count = 0

Device Extensions and layers:
=
GPU0
VkPhysicalDeviceProperties:
===
apiVersion = 4194306
driverVersion  = 1
vendorID   = 0x8086
deviceID   = 0x1616
deviceType = INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 5500 (Broadwell GT2)
VkPhysicalDeviceLimits:
---
maxImageDimension1D = 0x4000
maxImageDimension2D = 0x4000
maxImageDimension3D = 0x400
maxImageDimensionCube   = 0x4000
maxImageArrayLayers = 0x400
maxTexelBufferElements  = 0x800
maxUniformBufferRange   = 0x
maxStorageBufferRange   = 0x
maxPushConstantsSize= 0x80
maxMemoryAllocationCount= 0x
maxSamplerAllocationCount   = 0x1
bufferImageGranularity  = 0x40
sparseAddressSpaceSize  = 0x0
maxBoundDescriptorSets  = 0x8
maxPerStageDescriptorSamplers   = 0x40
maxPerStageDescriptorUniformBuffers = 0x40
maxPerStageDescriptorStorageBuffers = 0x40
maxPerStageDescriptorSampledImages  = 0x40
maxPerStageDescriptorStorageImages  = 0x40
maxPerStageDescriptorInputAttachments   = 0x40
maxPerStageResources= 0x80
maxDescriptorSetSamplers= 0x100
maxDescriptorSetUniformBuffers  = 0x100
maxDescriptorSetUniformBuffersDynamic   = 0x100
maxDescriptorSetStorageBuffers  = 0x100
maxDescriptorSetStorageBuffersDynamic   = 0x100
maxDescriptorSetSampledImages   = 0x100
maxDescriptorSetStorageImages   = 0x100
maxDescriptorSetInputAttachments= 0x100
maxVertexInputAttributes= 0x20
maxVertexInputBindings  = 0x20
maxVertexInputAttributeOffset   = 0x7ff
maxVertexInputBindingStride = 0x800
maxVertexOutputComponents   = 0x80
maxTessellationGenerationLevel  = 0x0
maxTessellationPatchSize= 0x0
maxTessellationControlPerVertexInputComponents  = 0x0
maxTessellationControlPerVertexOutputComponents = 0x0
maxTessellationControlPerPatchOutputComponents  = 0x0
maxTessellationControlTotalOutputComponents = 0x0
maxTessellationEvaluationInputComponents= 0x0
maxTessellationEvaluationOutputComponents   = 0x0
maxGeometryShaderInvocations= 0x20
maxGeometryInputComponents  = 0x40
maxGeometryOutputComponents = 0x80
maxGeometryOutputVertices   = 0x100
maxGeometryTotalOutputComponents= 0x400
maxFragmentInputComponents  = 0x80
maxFragmentOutputAttachments= 0x8
 

Re: Fwd: [packages/thefuck] python3.spec hack

2016-03-01 Thread Jacek Konieczny

On 2016-03-01 11:11, Elan Ruusamäe wrote:

i wonder where the proper fix would be?

➔ rpm -ql python3-modules|grep -F pathlib
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.opt-1.pyc
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.opt-2.pyc
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.pyc
/usr/lib64/python3.5/pathlib.py


You could add egg-info file/directory for pathlib to python3.spec.

Jacek

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Fwd: [packages/thefuck] python3.spec hack

2016-03-01 Thread Elan Ruusamäe

i wonder where the proper fix would be?

➔ rpm -ql python3-modules|grep -F pathlib
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.opt-1.pyc
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.opt-2.pyc
/usr/lib64/python3.5/__pycache__/pathlib.cpython-35.pyc
/usr/lib64/python3.5/pathlib.py


 Forwarded Message 
Subject:[packages/thefuck] python3.spec hack
Date:   Tue, 01 Mar 2016 09:40:32 +0100
From:   glen 
Reply-To: 	pld-devel-en@lists.pld-linux.org, 
pld-devel...@lists.pld-linux.org

To: pld-cvs-com...@lists.pld-linux.org



commit 08f1b42f9f6cc08b772586574bbce9bd01929d1c
Author: Elan Ruusamäe 
Date:   Tue Mar 1 10:40:25 2016 +0200

python3.spec hack

 thefuck.spec | 3 +++
 1 file changed, 3 insertions(+)
---
diff --git a/thefuck.spec b/thefuck.spec
index 6a76454..1a83e05 100644
--- a/thefuck.spec
+++ b/thefuck.spec
@@ -32,6 +32,9 @@ Requires: python3-six
 BuildArch: noarch
 BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
 
+# provided by python3.spec

+%define_noautoreq_py3egg pathlib
+
 %description
 This application corrects your previous console command.
 



 gitweb:

http://git.pld-linux.org/gitweb.cgi/packages/thefuck.git/commitdiff/08f1b42f9f6cc08b772586574bbce9bd01929d1c

___
pld-cvs-commit mailing list
pld-cvs-com...@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit



___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en