Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update - why not FMV?

2019-07-23 Thread Adrian Sevcenco

On 7/22/19 9:51 PM, Ben Cotton wrote:

https://fedoraproject.org/wiki/Changes/x86-64_micro-architecture_update

Along with AVX2, it makes sense to enable certain other CPU features
which are not strictly implied by AVX2, such as CMPXCHG16B, FMA, and
earlier vector extensions such as SSE 4.2.  Details are still being
worked out.

And why not use FMV?? the gcc/glibc is new enough, FMV could be 
implemented package by package ... using clear linux make-fmv-patch 
recipe one can adapt the code to various capabilities (and of course the 
patches can be contributed upstream, tweaked and customized)


Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


copr mailist?

2018-01-30 Thread Adrian Sevcenco
Hi! I was wondering what would be the best place to ask help about 
problems building packages on copr...


Thank you and sorry for off-topic,
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


f24 x86_64 :: yumex-dnf SIGSEGV

2016-10-26 Thread Adrian Sevcenco
Hi! I have a laptop with fedora 24 and today i encountered a strange thing :
beside various crashes in kde (apps crashing at logout or shutdown, suspend to 
ram not working)
i tried to use yumex-dnf through ssh -XY and i got a stern :
[root@t420 ~]# yumex-dnf
Segmentation fault (core dumped)

trying to debug "python3 /usr/bin/yumex-dnf" i got

(gdb) set args /usr/bin/yumex-dnf
(gdb) run
Starting program: /usr/bin/python3 /usr/bin/yumex-dnf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
37  movdqu  (%rdi), %xmm0

does anyone have any idea about this? is my ram dying?

Thank you!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: f23 :: ksensors :: cleanup errors

2016-09-19 Thread Adrian Sevcenco
On 09/19/2016 03:40 PM, Rex Dieter wrote:
> Adrian Sevcenco wrote:
> 
>> On 09/19/2016 03:19 PM, Rex Dieter wrote:
>>> Adrian Sevcenco wrote:
>>>
>>>> Hi! After updating the ksensors packages i got this errors :
>>>>
>>>> Cleanup : ksensors-0.7.3-30.fc23.x86_64  33/34
>>>> /var/tmp/rpm-tmp.DrghhQ: line 4: syntax error near unexpected token
>>>> `done' /var/tmp/rpm-tmp.DrghhQ: line 4: `done'
>>>> warning: %postun(ksensors-0.7.3-30.fc23.x86_64) scriptlet failed, exit
>>>> status 2 Non-fatal POSTUN scriptlet failure in rpm package ksensors
>>>> Non-fatal POSTUN scriptlet failure in rpm package ksensors
>>>>
>>>> What is the proper procedure for reporting this? Is this important
>>>> enough to fill a bug report?
>>>
>>> Nevermind, it's a bug in an older release, that's already fixed, see
>>> also: http://bugzilla.redhat.com/1187994
>> well, it is present in current fedora 23 in the package that i just
>> updated .. so, from my user point of view, is not fixed...
> 
> It's as fixed as it can get.  the problem occurs when upgrading away from 
> the broken version.  Nothing can be done about that, unfortunately.
yes, of course, sorry about making noise! 

Adrian




smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: f23 :: ksensors :: cleanup errors

2016-09-19 Thread Adrian Sevcenco
On 09/19/2016 03:19 PM, Rex Dieter wrote:
> Adrian Sevcenco wrote:
> 
>> Hi! After updating the ksensors packages i got this errors :
>>
>> Cleanup : ksensors-0.7.3-30.fc23.x86_64  33/34
>> /var/tmp/rpm-tmp.DrghhQ: line 4: syntax error near unexpected token `done'
>> /var/tmp/rpm-tmp.DrghhQ: line 4: `done'
>> warning: %postun(ksensors-0.7.3-30.fc23.x86_64) scriptlet failed, exit
>> status 2 Non-fatal POSTUN scriptlet failure in rpm package ksensors
>> Non-fatal POSTUN scriptlet failure in rpm package ksensors
>>
>> What is the proper procedure for reporting this? Is this important enough
>> to fill a bug report?
> 
> Nevermind, it's a bug in an older release, that's already fixed, see also:
> http://bugzilla.redhat.com/1187994
well, it is present in current fedora 23 in the package that i just updated ..
so, from my user point of view, is not fixed...

should i fill a bug report against fedora 23 version?

Thank you!
Adrian




smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


f23 :: ksensors :: cleanup errors

2016-09-19 Thread Adrian Sevcenco
Hi! After updating the ksensors packages i got this errors :

Cleanup : ksensors-0.7.3-30.fc23.x86_64  33/34 
/var/tmp/rpm-tmp.DrghhQ: line 4: syntax error near unexpected token `done'
/var/tmp/rpm-tmp.DrghhQ: line 4: `done'
warning: %postun(ksensors-0.7.3-30.fc23.x86_64) scriptlet failed, exit status 2
Non-fatal POSTUN scriptlet failure in rpm package ksensors
Non-fatal POSTUN scriptlet failure in rpm package ksensors

What is the proper procedure for reporting this? Is this important enough
to fill a bug report? or just contact the maintainer listed at
https://apps.fedoraproject.org/packages/ksensors/ ?

Thanks!
Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


Re: rpmbuild for cmake project error :: Found 'build_dir' in installed files

2016-09-06 Thread Adrian Sevcenco
On 09/06/2016 02:43 PM, Till Hofmann wrote:
> On 09/06/2016 01:35 PM, Adrian Sevcenco wrote:
>> Hi! I have a head scratching problem with a project (clhep) that i try to 
>> package.
>> It is cmake based and the spec file can be seen here:
>> https://github.com/adriansev/SPECS/blob/master/clhep.spec
>>
>> the error that i get is :
>> Found '/home/adrian/rpmbuild/BUILDROOT/clhep-2.3.3.2-1.x86_64' in installed 
>> files; aborting
>> error: Bad exit status from /var/tmp/rpm-tmp.tOmNW2 (%install)
>>
>> i imagine that it is a problem of setting the buildroot but  have no idea
>> how this translate to cmake settings ..
>>
>> What is the proper way for packaging cmake projects? (and setting prefix)
>>
> 
> Hi Adrian,
Hi!

> you can use the %cmake macro which conveniently sets most (if not all)
> options you need. You can check its content with 'rpm --eval "%cmake"'.
> 
> There is also a Wiki page about packaging with cmake, although it's not
> very elaborate: https://fedoraproject.org/wiki/Packaging:Cmake
Thanks a lot! It worked!!

Adrian



smime.p7s
Description: S/MIME Cryptographic Signature
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


rpmbuild for cmake project error :: Found 'build_dir' in installed files

2016-09-06 Thread Adrian Sevcenco
Hi! I have a head scratching problem with a project (clhep) that i try to 
package.
It is cmake based and the spec file can be seen here:
https://github.com/adriansev/SPECS/blob/master/clhep.spec

the error that i get is :
Found '/home/adrian/rpmbuild/BUILDROOT/clhep-2.3.3.2-1.x86_64' in installed 
files; aborting
error: Bad exit status from /var/tmp/rpm-tmp.tOmNW2 (%install)

i imagine that it is a problem of setting the buildroot but  have no idea
how this translate to cmake settings ..

What is the proper way for packaging cmake projects? (and setting prefix)

Thank you!
Adrian





smime.p7s
Description: S/MIME Cryptographic Signature
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org