[Bug 1384495] perl-CPAN-Perl-Releases-2.96 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384495



--- Comment #3 from Fedora Update System  ---
perl-CPAN-Perl-Releases-2.96-1.fc25 has been pushed to the Fedora 25 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-b4fe6750de

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384501] perl-Net-SSH2-0.63 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384501

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-Net-SSH2-0.63-1.fc25 has been pushed to the Fedora 25 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-627b9c5391

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384495] perl-CPAN-Perl-Releases-2.96 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384495

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-CPAN-Perl-Releases-2.96-1.fc24 has been pushed to the Fedora 24 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2016-b6aa760e76

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: OpenImageIO: i686 builds failing

[Richard Shaw]

On Thu, Oct 13, 2016 at 6:15 PM, Samuel Sieb  wrote:

> On 10/13/2016 12:04 PM, Richard Shaw wrote:
>
>> The following workaround was suggested by upstream and seemed to do the
>> trick but upstream doesn't want to perform needless initialization on
>> platforms/arches that don't require it.
>>
>> Why would it be arch-dependent whether or not a variable needs to be
> initialized?


No clue, that's why I'm asking :)

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Adam Williamson]

On Fri, 2016-10-14 at 11:26 +1000, Jeff Fearn wrote:
> 
> Not that I think either of those fields are good for marking something
> as a blocker for the distribution, a blocker flag would be more useful
> for that IMO.

None of this is about the blocker process, we already have one of those
and it works fine (it doesn't use flags, though that would work just as
well as what we have).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Jeff Fearn]

On 14/10/2016 11:07 AM, Adam Williamson wrote:
> On Thu, 2016-10-13 at 19:33 +1000, Jeff Fearn wrote:
>>> That's not the intent of the fields as I understand them. 'severity' is
>>> supposed to represent how bad the bug is, whereas 'priority' is
>>> supposed to represent how important it is to get it fixed compared to
>>> other bugs in the same component. They're obviously related, but not
>>> the same, and it's not "severity is the reporter's opinion, priority is
>>> the maintainers' opinion", no.
>> My understanding is based on ye olde services plan:
>>
>> "Bugzilla Severity and Priority
>>
>> When filing a new bug report, or actioning an existing bug, it is
>> important to bear in mind that, while both the 'Severity' and 'Priority'
>> fields are required; 'Priority' is an internal weighting and 'Severity'
>> is customer weighting. This distinction can cause confusion if not
>> consistant."
>>
>> This is only significant in that it may have impacted the way they are
>> coded on BRC.
>>
>>> I think you might be right that we allow the bug reporter to set
>>> 'severity', though.
>> BRC carries a custom patch to restrict priority to a group besides
>> editbugs group (the setpriority group), AFAICT there is no code that
>> allows similar restriction of the severity field.
> Ah, interesting. I don't really have any particular source for my
> understanding of them, it's just something I've been carrying around
> for a while, I guess. However, Fedora definitely does not handle bugs
> the same as RHEL, so we're not necessarily *bound* by that
> definition...but we could use it if we liked.

Hell no, but if a restriction on who can set severity was wanted we'd
have to add a patch for that. Whereas for priority all you'd need is
another BZ group and just switch the group inheritance.

Not that I think either of those fields are good for marking something
as a blocker for the distribution, a blocker flag would be more useful
for that IMO.

Cheers, Jeff.




signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Adam Williamson]

On Thu, 2016-10-13 at 19:33 +1000, Jeff Fearn wrote:
> 
> > That's not the intent of the fields as I understand them. 'severity' is
> > supposed to represent how bad the bug is, whereas 'priority' is
> > supposed to represent how important it is to get it fixed compared to
> > other bugs in the same component. They're obviously related, but not
> > the same, and it's not "severity is the reporter's opinion, priority is
> > the maintainers' opinion", no.
> 
> My understanding is based on ye olde services plan:
> 
> "Bugzilla Severity and Priority
> 
> When filing a new bug report, or actioning an existing bug, it is
> important to bear in mind that, while both the 'Severity' and 'Priority'
> fields are required; 'Priority' is an internal weighting and 'Severity'
> is customer weighting. This distinction can cause confusion if not
> consistant."
> 
> This is only significant in that it may have impacted the way they are
> coded on BRC.
> 
> > I think you might be right that we allow the bug reporter to set
> > 'severity', though.
> 
> BRC carries a custom patch to restrict priority to a group besides
> editbugs group (the setpriority group), AFAICT there is no code that
> allows similar restriction of the severity field.

Ah, interesting. I don't really have any particular source for my
understanding of them, it's just something I've been carrying around
for a while, I guess. However, Fedora definitely does not handle bugs
the same as RHEL, so we're not necessarily *bound* by that
definition...but we could use it if we liked.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: OpenImageIO: i686 builds failing

[Samuel Sieb]

On 10/13/2016 12:04 PM, Richard Shaw wrote:

The following workaround was suggested by upstream and seemed to do the
trick but upstream doesn't want to perform needless initialization on
platforms/arches that don't require it.

Why would it be arch-dependent whether or not a variable needs to be 
initialized?

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Fedora Rawhide-20161013.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Workstation live i386
Workstation live x86_64

Failed openQA tests: 2/91 (x86_64), 1/16 (i386), 1/2 (arm)

ID: 40971   Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/40971
ID: 41034   Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/41034
ID: 41059   Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/41059
ID: 41070   Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/41070

Passed openQA tests: 89/91 (x86_64), 15/16 (i386)

Skipped openQA tests: 1 of 109
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

OpenImageIO: i686 builds failing

[Richard Shaw]

I could use some help figuring out the best fix for the following problem
where only the i686 builds fail:

cd /builddir/build/BUILD/oiio-Release-1.7.7/build/linux/src/libutil &&
/usr/bin/cmake -E cmake_link_script CMakeFiles/fmath_test.dir/link.txt
--verbose=1
/usr/bin/c++   -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4 -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 -mtune=atom
-fasynchronous-unwind-tables  -O2 -g -DNDEBUG   -Wl,-z,relro
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
CMakeFiles/fmath_test.dir/fmath_test.cpp.o  -o fmath_test -rdynamic
libOpenImageIO_Util.so.1.7.7 -lboost_filesystem -lboost_regex
-lboost_system -lboost_thread -lboost_chrono -lboost_date_time
-lboost_atomic -lrt -ldl -lImath -lIex -lHalf -lIlmThread -lpthread
-Wl,-rpath,/builddir/build/BUILD/oiio-Release-1.7.7/build/linux/src/libutil
make[2]: Leaving directory
'/builddir/build/BUILD/oiio-Release-1.7.7/build/linux'
[ 72%] Built target fmath_test
In file included from
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/fmath.h:64:0,
 from
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/hash.h:50,
 from
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/strutil.h:54,
 from
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/ustring.h:137,
 from
/builddir/build/BUILD/oiio-Release-1.7.7/src/libtexture/texturesys.cpp:44:
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/simd.h: In
member function 'bool
OpenImageIO::v1_7::pvt::TextureSystemImpl::sample_bicubic(int, const
float*, const float*, int,
OpenImageIO::v1_7::pvt::TextureSystemImpl::TextureFile&,
OpenImageIO::v1_7::pvt::TextureSystemImpl::PerThreadInfo*,
OpenImageIO::v1_7::TextureOpt&, int, int, const float*,
OpenImageIO::v1_7::simd::float4*, OpenImageIO::v1_7::simd::float4*,
OpenImageIO::v1_7::simd::float4*)':
/builddir/build/BUILD/oiio-Release-1.7.7/src/include/OpenImageIO/simd.h:308:71:
error: '*((void*)& dwy +12)' may be used uninitialized in this function
[-Werror=maybe-uninitialized]
 #define SIMD_CONSTRUCT(x) for (int i = 0; i < elements; ++i) m_val[i] = (x)
   ^
/builddir/build/BUILD/oiio-Release-1.7.7/src/libtexture/texturesys.cpp:2473:20:
note: '*((void*)& dwy +12)' was declared here
 float4 wy, dwy;

Full build logs here:
https://kojipkgs.fedoraproject.org//work/tasks/2540/15912540/build.log

Upstream does not test or use 32bit builds in production...

The following workaround was suggested by upstream and seemed to do the
trick but upstream doesn't want to perform needless initialization on
platforms/arches that don't require it.

Ok, in texturesys.cpp, circa line 2472, please add the following two lines
(bold):

float4 wx, dwx;
float4 wy, dwy;
if (daccumds_) {
evalBSplineWeights_and_derivs (, sfrac, );
evalBSplineWeights_and_derivs (, tfrac, );
} else {
wx = evalBSplineWeights (float4(sfrac));
wy = evalBSplineWeights (float4(tfrac));
*dwx = float4::Zero();*
*dwy = float4::Zero();*
}

Any suggestions?

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[389-devel] Build failed in Jenkins: 389-DS-COMMIT #117

[Jenkins]

7705.fc24
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 
4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) 
<= 4.0-1
Requires: /usr/bin/python /usr/bin/python2
Processing files: 389-ds-base-debuginfo-1.3.6.0-20161013git83a7705.fc24.x86_64
Provides: 389-ds-base-debuginfo = 1.3.6.0-20161013git83a7705.fc24 
389-ds-base-debuginfo(x86-64) = 1.3.6.0-20161013git83a7705.fc24
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 
4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Checking for unpackaged file(s): /usr/lib/rpm/check-files 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/BUILDROOT/389-ds-base-1.3.6.0-20161013git83a7705.fc24.x86_64>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/SRPMS/389-ds-base-1.3.6.0-20161013git83a7705.fc24.src.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/x86_64/389-ds-base-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/x86_64/389-ds-base-libs-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/x86_64/389-ds-base-devel-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/x86_64/389-ds-base-snmp-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/noarch/389-ds-base-tests-1.3.6.0-20161013git83a7705.fc24.noarch.rpm>
Wrote: 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/x86_64/389-ds-base-debuginfo-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm>
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.aFumvv
+ umask 022
+ cd 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/BUILD>
+ cd 389-ds-base-1.3.6.0.20161013git83a7705
+ rm -rf 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/BUILDROOT/389-ds-base-1.3.6.0-20161013git83a7705.fc24.x86_64>
+ exit 0
cp 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/*/389-ds-base-1.3.6.0-20161013git83a7705*.rpm>
 dist/rpms/
cp 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/RPMS/*/389-ds-base-*-1.3.6.0*.rpm>
 dist/rpms/
cp 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild/SRPMS/389-ds-base-1.3.6.0-20161013git83a7705*.src.rpm>
 dist/srpms/
rm -rf 
<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/ds/rpmbuild>
+ cd dist/rpms/
+ sudo rpm -iUvh 389-ds-base-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm 
389-ds-base-libs-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm 
389-ds-base-debuginfo-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm 
389-ds-base-devel-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm 
389-ds-base-snmp-1.3.6.0-20161013git83a7705.fc24.x86_64.rpm
Preparing...  
Updating / installing...
389-ds-base-libs-1.3.6.0-20161013git83
389-ds-base-1.3.6.0-20161013git83a7705
389-ds-base-snmp-1.3.6.0-20161013git83
389-ds-base-devel-1.3.6.0-20161013git8
389-ds-base-debuginfo-1.3.6.0-20161013
Cleaning up / removing...
389-ds-base-devel-1.3.5.13-1.fc24 
389-ds-base-1.3.5.13-1.fc24   
389-ds-base-libs-1.3.5.13-1.fc24  
+ '[' 0 -ne 0 ']'
+ sudo sysctl -w fs.suid_dumpable=1
fs.suid_dumpable = 1
+ sudo chmod 777 /etc/sysconfig/dirsrv.systemd
+ sudo echo LimitCORE=infinity
+ sudo systemctl daemon-reload
+ echo Run the lib389 tests...
Run the lib389 tests...
+ cd ../../dirsrvtests/tests
++ date
+ DATE='Thu Oct 13 20:35:54 CEST 2016'
++ sudo 
PYTHONPATH=/usr/lib64/python2.7:/usr/lib64/python2.7/plat-linux2:/usr/lib64/python2.7/site-packages:/usr/lib/python2.7/site-packages:<http://vm-058-081.abc.idm.lab.eng.brq.redhat.com:8080/job/389-DS-COMMIT/ws/source/lib389/>
 PREFIX=/ py.test -v -x suites/basic/basic_test.py
+ RESULT='= test session starts 
==
platform linux2 -- Python 2.7.12, pytest-2.9.2, py-1.4.31, pluggy-0.3.1 --

Broken dependencies: perl-DBD-Firebird

[buildsys]

perl-DBD-Firebird has broken dependencies in the rawhide tree:
On aarch64:
perl-DBD-Firebird-1.22-2.fc25.aarch64 requires 
libfbembed.so.2.5()(64bit)
On x86_64:
perl-DBD-Firebird-1.22-2.fc25.x86_64 requires libfbembed.so.2.5()(64bit)
On i386:
perl-DBD-Firebird-1.22-2.fc25.i686 requires libfbembed.so.2.5
On armhfp:
perl-DBD-Firebird-1.22-2.fc25.armv7hl requires libfbembed.so.2.5
Please resolve this as soon as possible.

___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Broken dependencies: perl-Alien-ROOT

[buildsys]

perl-Alien-ROOT has broken dependencies in the rawhide tree:
On aarch64:
perl-Alien-ROOT-5.34.36.1-1.fc26.noarch requires root-core
Please resolve this as soon as possible.

___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Broken dependencies: perl-Data-Alias

[buildsys]

perl-Data-Alias has broken dependencies in the rawhide tree:
On aarch64:
perl-Data-Alias-1.20-2.fc24.aarch64 requires libperl.so.5.22()(64bit)
perl-Data-Alias-1.20-2.fc24.aarch64 requires perl(:MODULE_COMPAT_5.22.1)
On x86_64:
perl-Data-Alias-1.20-2.fc24.x86_64 requires libperl.so.5.22()(64bit)
perl-Data-Alias-1.20-2.fc24.x86_64 requires perl(:MODULE_COMPAT_5.22.1)
On i386:
perl-Data-Alias-1.20-2.fc24.i686 requires libperl.so.5.22
perl-Data-Alias-1.20-2.fc24.i686 requires perl(:MODULE_COMPAT_5.22.1)
On armhfp:
perl-Data-Alias-1.20-2.fc24.armv7hl requires libperl.so.5.22
perl-Data-Alias-1.20-2.fc24.armv7hl requires perl(:MODULE_COMPAT_5.22.1)
Please resolve this as soon as possible.

___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Test-Announce] Fedora 25 Branched 20161013.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 25 Branched 20161013.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
lorax - 1.1: lorax-25.15-1.fc25.src, 20161013.n.0: lorax-25.16-1.fc25.src

Test coverage information for the current release can be seen at:
https://www.happyassassin.net/testcase_stats/25

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161013.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relval: https://www.happyassassin.net/relval/
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1383650] perl-Crypt-OpenSSL-RSA-0.28-15.fc26 FTBFS: dereferencing pointer to incomplete type 'RSA {aka struct rsa_st}'

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1383650



--- Comment #1 from Petr Pisar  ---
I developed a fix and posted it to the upstream bug report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-Crypt-OpenSSL-Random (master). "Rebuild against OpenSSL 1.1.0"

[notifications]

From 843a08308f299c3f1e45a45965803d8cd8270f9e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 18:24:54 +0200
Subject: Rebuild against OpenSSL 1.1.0

---
 perl-Crypt-OpenSSL-Random.spec | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/perl-Crypt-OpenSSL-Random.spec b/perl-Crypt-OpenSSL-Random.spec
index d016bf6..79dcf83 100644
--- a/perl-Crypt-OpenSSL-Random.spec
+++ b/perl-Crypt-OpenSSL-Random.spec
@@ -1,6 +1,6 @@
 Name:   perl-Crypt-OpenSSL-Random
 Version:0.11
-Release:3%{?dist}
+Release:4%{?dist}
 Summary:OpenSSL/LibreSSL pseudo-random number generator access
 License:GPL+ or Artistic 
 Group:  Development/Libraries
@@ -64,6 +64,9 @@ rm -rf %{buildroot}
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 0.11-4
+- Rebuild against OpenSSL 1.1.0
+
 * Sat May 14 2016 Jitka Plesnikova  - 0.11-3
 - Perl 5.24 rebuild
 
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Crypt-OpenSSL-Random.git/commit/?h=master=843a08308f299c3f1e45a45965803d8cd8270f9e
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Fedora 25-20161013.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 6/102 (x86_64), 3/17 (i386), 1/2 (arm)

ID: 40820   Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/40820
ID: 40827   Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/40827
ID: 40828   Test: x86_64 Atomic-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/40828
ID: 40838   Test: x86_64 KDE-live-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/40838
ID: 40841   Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/40841
ID: 40888   Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/40888
ID: 40921   Test: i386 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/40921
ID: 40929   Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/40929
ID: 40948   Test: x86_64 universal install_btrfs
URL: https://openqa.fedoraproject.org/tests/40948
ID: 40951   Test: x86_64 Server-dvd-iso server_cockpit_basic
URL: https://openqa.fedoraproject.org/tests/40951

Passed openQA tests: 96/102 (x86_64), 14/17 (i386)

Skipped openQA tests: 1 of 121
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-1b40911266

[notifications]

dist.depcheck PASSED for FEDORA-2016-1b40911266

https://taskotron.fedoraproject.org/artifacts/all/b773e8b8-915f-11e6-be50-525400120b80/task_output/FEDORA-2016-1b40911266.x86_64.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-bc3dce7a84

[notifications]

dist.depcheck PASSED for FEDORA-2016-bc3dce7a84

https://taskotron.fedoraproject.org/artifacts/all/b74e23b2-915f-11e6-b011-525400120b80/task_output/FEDORA-2016-bc3dce7a84.x86_64.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-bc3dce7a84

[notifications]

dist.depcheck PASSED for FEDORA-2016-bc3dce7a84

https://taskotron.fedoraproject.org/artifacts/all/b74e23b2-915f-11e6-b011-525400120b80/task_output/FEDORA-2016-bc3dce7a84.i386.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-1b40911266

[notifications]

dist.depcheck PASSED for FEDORA-2016-1b40911266

https://taskotron.fedoraproject.org/artifacts/all/b773e8b8-915f-11e6-be50-525400120b80/task_output/FEDORA-2016-1b40911266.i386.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-54cc18c642

[notifications]

dist.depcheck PASSED for FEDORA-2016-54cc18c642

https://taskotron.fedoraproject.org/artifacts/all/9ed97f22-915d-11e6-be50-525400120b80/task_output/FEDORA-2016-54cc18c642.i386.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

dist.depcheck PASSED for FEDORA-2016-54cc18c642

[notifications]

dist.depcheck PASSED for FEDORA-2016-54cc18c642

https://taskotron.fedoraproject.org/artifacts/all/9ed97f22-915d-11e6-be50-525400120b80/task_output/FEDORA-2016-54cc18c642.x86_64.log
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: redhat-rpm-config config.sub/guess are old

[Richard W.M. Jones]

On Thu, Oct 13, 2016 at 06:23:24PM +0300, Panu Matilainen wrote:
> On 10/13/2016 04:57 PM, Richard W.M. Jones wrote:
> >
> >The versions of config.sub and config.guess in redhat-rpm-config are
> >3+ years old.  I'd like to update these to the very latest versions,
> >primarily because the upstream versions support riscv64.
> >
> >Is there a reason not to do that?  I don't want to break something
> >unexpectedly.
> 
> Just go ahead. The reason they were updated three years ago was
> exactly the same: support for new hardware. There hasn't been any
> demand for updating since then I guess :)

Thanks Panu.

I updated this package.

Also automake which carries config.sub and config.guess around too.
Perhaps these should be combined?!

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: redhat-rpm-config config.sub/guess are old

[Pavel Raiskup]

On Thursday, October 13, 2016 6:23:24 PM CEST Panu Matilainen wrote:
> On 10/13/2016 04:57 PM, Richard W.M. Jones wrote:
> >
> > The versions of config.sub and config.guess in redhat-rpm-config are
> > 3+ years old.  I'd like to update these to the very latest versions,
> > primarily because the upstream versions support riscv64.
> >
> > Is there a reason not to do that?  I don't want to break something
> > unexpectedly.
> 
> Just go ahead. The reason they were updated three years ago was exactly 
> the same: support for new hardware. There hasn't been any demand for 
> updating since then I guess :)

I'll do the same for automake.  Thanks.

Pavel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f23). "Mandatory Perl build-requires added "

[notifications]

From cffe5f45e9c952ae028d99153ef544bcc99c7b5d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Fri, 24 Jun 2016 09:39:53 +0200
Subject: Mandatory Perl build-requires added
 

---
 abi-compliance-checker.spec | 1 +
 1 file changed, 1 insertion(+)

diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 6672a7f..45551c8 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -9,6 +9,7 @@ Source0:
https://github.com/lvc/%{name}/archive/%{version}/%{name}-%{vers
 
 BuildArch:  noarch
 
+BuildRequires:  perl-generators
 BuildRequires:  perl(Getopt::Long)
 Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f23=cffe5f45e9c952ae028d99153ef544bcc99c7b5d
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f23). "Update to latest upstream release."

[notifications]

From 402c5140e84b8b02d17846e174bff0f032a95819 Mon Sep 17 00:00:00 2001
From: "Richard M. Shaw" 
Date: Thu, 13 Oct 2016 10:36:30 -0500
Subject: Update to latest upstream release.

---
 .gitignore  |  1 +
 ChangeLog   | 47 -
 abi-compliance-checker.spec |  9 ++---
 sources |  2 +-
 4 files changed, 8 insertions(+), 51 deletions(-)
 delete mode 100644 ChangeLog

diff --git a/.gitignore b/.gitignore
index 9572ba3..68f26b0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,3 +24,4 @@
 /abi-compliance-checker-1.99.13.tar.gz
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
+/abi-compliance-checker-1.99.25.tar.gz
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index de0037a..000
--- a/ChangeLog
+++ /dev/null
@@ -1,47 +0,0 @@
-Version 1.99.19 (April 18, 2016)
-Improvements
-
-Support for GCC 5.1
-Misc
-Separated LICENSE file
-Removed obsolete descriptors from the package
-Updated docs
-
-Version 1.99.18 (April 03, 2016)
-Bug Fixes
-Fixed comparison of qualifiers in parameter data types
-Fixed problem descriptions in the report
-Reduced size of the report
-Fixed console output
-
-Version 1.99.17 (March 12, 2016)
-Improvements
-Added a check for changes in parameters of function pointers
-Bug Fixes
-Fixed comparison of virtual table entries
-Do not show time stamp in the report
-Fixed -skip-symbols option
-Fixed detection of the GCC version number
-
-Version 1.99.16 (January 28, 2016)
-Improvements
-Do not check private part of the ABI when comparing ABI dumps created by the
-ABI Dumper tool with use of the -public-headers option
-New Options
--check-private-abi: enable check of the private ABI
-Bug Fixes
-Fixed counting of checked data types
-
-Version 1.99.15 (December 11, 2015)
-Bug Fixes
-Fixed hang on some template instances
-Fixed support for old ABI dumps (formatting of data types)
-Fixed false positives in the report if input ABI dumps contain __unknown__
-types
-
-Version 1.99.14 (November 01, 2015)
-New Options
--skip-types: set list of types that should not be checked
-Bug Fixes
-Fixed formatting of symbol signatures
-Fixed checks of template types
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 45551c8..a6ef6fa 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.20
+Version:1.99.25
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -15,7 +15,8 @@ Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
 Requires:   binutils
 Requires:   ctags >= 5.8
-Requires:   ccache > 3.1.2
+Requires:   ccache >= 3.1.2
+Requires:   abi-dumper >= 0.99.15
 
 %{?perl_default_filter}
 
@@ -39,7 +40,6 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %files
-%{!?_licensedir:%global license %doc}
 %license LICENSE GPL-2.0 LGPL-2.0
 %doc README doc/*
 %{_bindir}/%{name}
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
+- Update to latest upstream release.
+
 * Mon May 16 2016 Richard Shaw  - 1.99.20-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index b8138e9..f428a52 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-151147f75e999f6e0a3974ce32d23932  abi-compliance-checker-1.99.20.tar.gz
+cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f23=402c5140e84b8b02d17846e174bff0f032a95819
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f24). "Mandatory Perl build-requires added "

[notifications]

From cffe5f45e9c952ae028d99153ef544bcc99c7b5d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Fri, 24 Jun 2016 09:39:53 +0200
Subject: Mandatory Perl build-requires added
 

---
 abi-compliance-checker.spec | 1 +
 1 file changed, 1 insertion(+)

diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 6672a7f..45551c8 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -9,6 +9,7 @@ Source0:
https://github.com/lvc/%{name}/archive/%{version}/%{name}-%{vers
 
 BuildArch:  noarch
 
+BuildRequires:  perl-generators
 BuildRequires:  perl(Getopt::Long)
 Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f24=cffe5f45e9c952ae028d99153ef544bcc99c7b5d
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f24). "Update to latest upstream release."

[notifications]

From 402c5140e84b8b02d17846e174bff0f032a95819 Mon Sep 17 00:00:00 2001
From: "Richard M. Shaw" 
Date: Thu, 13 Oct 2016 10:36:30 -0500
Subject: Update to latest upstream release.

---
 .gitignore  |  1 +
 ChangeLog   | 47 -
 abi-compliance-checker.spec |  9 ++---
 sources |  2 +-
 4 files changed, 8 insertions(+), 51 deletions(-)
 delete mode 100644 ChangeLog

diff --git a/.gitignore b/.gitignore
index 9572ba3..68f26b0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,3 +24,4 @@
 /abi-compliance-checker-1.99.13.tar.gz
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
+/abi-compliance-checker-1.99.25.tar.gz
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index de0037a..000
--- a/ChangeLog
+++ /dev/null
@@ -1,47 +0,0 @@
-Version 1.99.19 (April 18, 2016)
-Improvements
-
-Support for GCC 5.1
-Misc
-Separated LICENSE file
-Removed obsolete descriptors from the package
-Updated docs
-
-Version 1.99.18 (April 03, 2016)
-Bug Fixes
-Fixed comparison of qualifiers in parameter data types
-Fixed problem descriptions in the report
-Reduced size of the report
-Fixed console output
-
-Version 1.99.17 (March 12, 2016)
-Improvements
-Added a check for changes in parameters of function pointers
-Bug Fixes
-Fixed comparison of virtual table entries
-Do not show time stamp in the report
-Fixed -skip-symbols option
-Fixed detection of the GCC version number
-
-Version 1.99.16 (January 28, 2016)
-Improvements
-Do not check private part of the ABI when comparing ABI dumps created by the
-ABI Dumper tool with use of the -public-headers option
-New Options
--check-private-abi: enable check of the private ABI
-Bug Fixes
-Fixed counting of checked data types
-
-Version 1.99.15 (December 11, 2015)
-Bug Fixes
-Fixed hang on some template instances
-Fixed support for old ABI dumps (formatting of data types)
-Fixed false positives in the report if input ABI dumps contain __unknown__
-types
-
-Version 1.99.14 (November 01, 2015)
-New Options
--skip-types: set list of types that should not be checked
-Bug Fixes
-Fixed formatting of symbol signatures
-Fixed checks of template types
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 45551c8..a6ef6fa 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.20
+Version:1.99.25
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -15,7 +15,8 @@ Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
 Requires:   binutils
 Requires:   ctags >= 5.8
-Requires:   ccache > 3.1.2
+Requires:   ccache >= 3.1.2
+Requires:   abi-dumper >= 0.99.15
 
 %{?perl_default_filter}
 
@@ -39,7 +40,6 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %files
-%{!?_licensedir:%global license %doc}
 %license LICENSE GPL-2.0 LGPL-2.0
 %doc README doc/*
 %{_bindir}/%{name}
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
+- Update to latest upstream release.
+
 * Mon May 16 2016 Richard Shaw  - 1.99.20-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index b8138e9..f428a52 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-151147f75e999f6e0a3974ce32d23932  abi-compliance-checker-1.99.20.tar.gz
+cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f24=402c5140e84b8b02d17846e174bff0f032a95819
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (f25). "Update to latest upstream release."

[notifications]

From 402c5140e84b8b02d17846e174bff0f032a95819 Mon Sep 17 00:00:00 2001
From: "Richard M. Shaw" 
Date: Thu, 13 Oct 2016 10:36:30 -0500
Subject: Update to latest upstream release.

---
 .gitignore  |  1 +
 ChangeLog   | 47 -
 abi-compliance-checker.spec |  9 ++---
 sources |  2 +-
 4 files changed, 8 insertions(+), 51 deletions(-)
 delete mode 100644 ChangeLog

diff --git a/.gitignore b/.gitignore
index 9572ba3..68f26b0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,3 +24,4 @@
 /abi-compliance-checker-1.99.13.tar.gz
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
+/abi-compliance-checker-1.99.25.tar.gz
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index de0037a..000
--- a/ChangeLog
+++ /dev/null
@@ -1,47 +0,0 @@
-Version 1.99.19 (April 18, 2016)
-Improvements
-
-Support for GCC 5.1
-Misc
-Separated LICENSE file
-Removed obsolete descriptors from the package
-Updated docs
-
-Version 1.99.18 (April 03, 2016)
-Bug Fixes
-Fixed comparison of qualifiers in parameter data types
-Fixed problem descriptions in the report
-Reduced size of the report
-Fixed console output
-
-Version 1.99.17 (March 12, 2016)
-Improvements
-Added a check for changes in parameters of function pointers
-Bug Fixes
-Fixed comparison of virtual table entries
-Do not show time stamp in the report
-Fixed -skip-symbols option
-Fixed detection of the GCC version number
-
-Version 1.99.16 (January 28, 2016)
-Improvements
-Do not check private part of the ABI when comparing ABI dumps created by the
-ABI Dumper tool with use of the -public-headers option
-New Options
--check-private-abi: enable check of the private ABI
-Bug Fixes
-Fixed counting of checked data types
-
-Version 1.99.15 (December 11, 2015)
-Bug Fixes
-Fixed hang on some template instances
-Fixed support for old ABI dumps (formatting of data types)
-Fixed false positives in the report if input ABI dumps contain __unknown__
-types
-
-Version 1.99.14 (November 01, 2015)
-New Options
--skip-types: set list of types that should not be checked
-Bug Fixes
-Fixed formatting of symbol signatures
-Fixed checks of template types
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 45551c8..a6ef6fa 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.20
+Version:1.99.25
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -15,7 +15,8 @@ Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
 Requires:   binutils
 Requires:   ctags >= 5.8
-Requires:   ccache > 3.1.2
+Requires:   ccache >= 3.1.2
+Requires:   abi-dumper >= 0.99.15
 
 %{?perl_default_filter}
 
@@ -39,7 +40,6 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %files
-%{!?_licensedir:%global license %doc}
 %license LICENSE GPL-2.0 LGPL-2.0
 %doc README doc/*
 %{_bindir}/%{name}
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
+- Update to latest upstream release.
+
 * Mon May 16 2016 Richard Shaw  - 1.99.20-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index b8138e9..f428a52 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-151147f75e999f6e0a3974ce32d23932  abi-compliance-checker-1.99.20.tar.gz
+cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=f25=402c5140e84b8b02d17846e174bff0f032a95819
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 pushed to abi-compliance-checker (master). "Update to latest upstream release."

[notifications]

From 402c5140e84b8b02d17846e174bff0f032a95819 Mon Sep 17 00:00:00 2001
From: "Richard M. Shaw" 
Date: Thu, 13 Oct 2016 10:36:30 -0500
Subject: Update to latest upstream release.

---
 .gitignore  |  1 +
 ChangeLog   | 47 -
 abi-compliance-checker.spec |  9 ++---
 sources |  2 +-
 4 files changed, 8 insertions(+), 51 deletions(-)
 delete mode 100644 ChangeLog

diff --git a/.gitignore b/.gitignore
index 9572ba3..68f26b0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,3 +24,4 @@
 /abi-compliance-checker-1.99.13.tar.gz
 /abi-compliance-checker-1.99.19.tar.gz
 /abi-compliance-checker-1.99.20.tar.gz
+/abi-compliance-checker-1.99.25.tar.gz
diff --git a/ChangeLog b/ChangeLog
deleted file mode 100644
index de0037a..000
--- a/ChangeLog
+++ /dev/null
@@ -1,47 +0,0 @@
-Version 1.99.19 (April 18, 2016)
-Improvements
-
-Support for GCC 5.1
-Misc
-Separated LICENSE file
-Removed obsolete descriptors from the package
-Updated docs
-
-Version 1.99.18 (April 03, 2016)
-Bug Fixes
-Fixed comparison of qualifiers in parameter data types
-Fixed problem descriptions in the report
-Reduced size of the report
-Fixed console output
-
-Version 1.99.17 (March 12, 2016)
-Improvements
-Added a check for changes in parameters of function pointers
-Bug Fixes
-Fixed comparison of virtual table entries
-Do not show time stamp in the report
-Fixed -skip-symbols option
-Fixed detection of the GCC version number
-
-Version 1.99.16 (January 28, 2016)
-Improvements
-Do not check private part of the ABI when comparing ABI dumps created by the
-ABI Dumper tool with use of the -public-headers option
-New Options
--check-private-abi: enable check of the private ABI
-Bug Fixes
-Fixed counting of checked data types
-
-Version 1.99.15 (December 11, 2015)
-Bug Fixes
-Fixed hang on some template instances
-Fixed support for old ABI dumps (formatting of data types)
-Fixed false positives in the report if input ABI dumps contain __unknown__
-types
-
-Version 1.99.14 (November 01, 2015)
-New Options
--skip-types: set list of types that should not be checked
-Bug Fixes
-Fixed formatting of symbol signatures
-Fixed checks of template types
diff --git a/abi-compliance-checker.spec b/abi-compliance-checker.spec
index 45551c8..a6ef6fa 100644
--- a/abi-compliance-checker.spec
+++ b/abi-compliance-checker.spec
@@ -1,5 +1,5 @@
 Name:   abi-compliance-checker
-Version:1.99.20
+Version:1.99.25
 Release:1%{?dist}
 Summary:An ABI Compliance Checker
 
@@ -15,7 +15,8 @@ Requires:   gcc >= 4.5
 Requires:   gcc-c++ >= 4.5
 Requires:   binutils
 Requires:   ctags >= 5.8
-Requires:   ccache > 3.1.2
+Requires:   ccache >= 3.1.2
+Requires:   abi-dumper >= 0.99.15
 
 %{?perl_default_filter}
 
@@ -39,7 +40,6 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %files
-%{!?_licensedir:%global license %doc}
 %license LICENSE GPL-2.0 LGPL-2.0
 %doc README doc/*
 %{_bindir}/%{name}
@@ -47,6 +47,9 @@ perl Makefile.pl -install --prefix=%{_prefix} 
--destdir=%{buildroot}
 
 
 %changelog
+* Thu Oct 13 2016 Richard Shaw  - 1.99.25-1
+- Update to latest upstream release.
+
 * Mon May 16 2016 Richard Shaw  - 1.99.20-1
 - Update to latest upstream release.
 
diff --git a/sources b/sources
index b8138e9..f428a52 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-151147f75e999f6e0a3974ce32d23932  abi-compliance-checker-1.99.20.tar.gz
+cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/abi-compliance-checker.git/commit/?h=master=402c5140e84b8b02d17846e174bff0f032a95819
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

hobbes1069 uploaded abi-compliance-checker-1.99.25.tar.gz for abi-compliance-checker

[notifications]

cc4f8e5351c895d325e8010c83931aa4  abi-compliance-checker-1.99.25.tar.gz

http://pkgs.fedoraproject.org/lookaside/pkgs/abi-compliance-checker/abi-compliance-checker-1.99.25.tar.gz/md5/cc4f8e5351c895d325e8010c83931aa4/abi-compliance-checker-1.99.25.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: redhat-rpm-config config.sub/guess are old

[Panu Matilainen]

On 10/13/2016 04:57 PM, Richard W.M. Jones wrote:


The versions of config.sub and config.guess in redhat-rpm-config are
3+ years old.  I'd like to update these to the very latest versions,
primarily because the upstream versions support riscv64.

Is there a reason not to do that?  I don't want to break something
unexpectedly.


Just go ahead. The reason they were updated three years ago was exactly 
the same: support for new hardware. There hasn't been any demand for 
updating since then I guess :)


- Panu -


Rich.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

pghmcfc pushed to perl-Cpanel-JSON-XS (perl-Cpanel-JSON-XS-3.0218-1.fc25). "Update to 3.0218 (..more)"

[notifications]

From 66f88a4a476b70dcd5bb796b544926573bd35c9c Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Thu, 13 Oct 2016 15:18:04 +0100
Subject: Update to 3.0218

- New upstream release 3.0218
  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
negative nan unified to "nan"
  - Use faster strEQc macros from cperl with constant strings
  - Prefer memEQ for systems without memcmp, to use bcmp there
  - Add more expect_false() to inf/nan branches
  - expect_false() macro fix for MSVC
  - Fix av and hv length types: protect from security sensitive overflows, add
HVMAX_T and RITER_T
  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
errors
  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
  - Fix and document wrong strEQc usage in new() (GH#70)
  - Fix t/gh70-asan.t for older perls < 5.14
  - Fix DPPP_dummy_PL_parser warnings
---
 perl-Cpanel-JSON-XS.spec | 26 +++---
 sources  |  2 +-
 2 files changed, 24 insertions(+), 4 deletions(-)

diff --git a/perl-Cpanel-JSON-XS.spec b/perl-Cpanel-JSON-XS.spec
index d7e4645..b85f606 100644
--- a/perl-Cpanel-JSON-XS.spec
+++ b/perl-Cpanel-JSON-XS.spec
@@ -1,6 +1,6 @@
 Name:  perl-Cpanel-JSON-XS
 Summary:   JSON::XS for Cpanel, fast and correct serializing
-Version:   3.0217
+Version:   3.0218
 Release:   1%{?dist}
 License:   GPL+ or Artistic
 URL:   http://search.cpan.org/dist/Cpanel-JSON-XS/
@@ -44,11 +44,12 @@ BuildRequires:  perl(lib)
 BuildRequires: perl(strict)
 BuildRequires: perl(Test)
 BuildRequires: perl(Test::More) >= 0.88
+BuildRequires: perl(Test::Simple)
 BuildRequires: perl(Tie::Array)
 BuildRequires: perl(Tie::Hash)
 BuildRequires: perl(utf8)
 BuildRequires: perl(warnings)
-%if !%{defined perl_bootstrap}
+# Optional Tests
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-LeakTrace → perl-Module-Install
 # → perl-YAML-Tiny → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Perl-MinimumVersion → perl-PPI
@@ -58,7 +59,7 @@ BuildRequires:perl(warnings)
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-Kwalitee → perl-Module-CPANTS-Analyse
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
-# Optional Tests
+%if !%{defined perl_bootstrap}
 BuildRequires: perl(common::sense) >= 3.5
 BuildRequires: perl(Hash::Util)
 BuildRequires: perl(JSON)
@@ -155,6 +156,25 @@ make test %{!?perl_bootstrap:AUTHOR_TESTING=1}
 %{_mandir}/man3/Cpanel::JSON::XS::Boolean.3*
 
 %changelog
+* Thu Oct 13 2016 Paul Howarth  - 3.0218-1
+- Update to 3.0218
+  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
+  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
+"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
+negative nan unified to "nan"
+  - Use faster strEQc macros from cperl with constant strings
+  - Prefer memEQ for systems without memcmp, to use bcmp there
+  - Add more expect_false() to inf/nan branches
+  - expect_false() macro fix for MSVC
+  - Fix av and hv length types: protect from security sensitive overflows, add
+HVMAX_T and RITER_T
+  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
+errors
+  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
+  - Fix and document wrong strEQc usage in new() (GH#70)
+  - Fix t/gh70-asan.t for older perls < 5.14
+  - Fix DPPP_dummy_PL_parser warnings
+
 * Sat Jun 18 2016 Paul Howarth  - 3.0217-1
 - Update to 3.0217
   - Improve test t/20_unknown.t for older JSON::PP
diff --git a/sources b/sources
index 4efb69f..bbb57ce 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-747672f925ce479d3da2ff316e47cf23  Cpanel-JSON-XS-3.0217.tar.gz
+818af1a8354341646d839ca1a14b780c  Cpanel-JSON-XS-3.0218.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Cpanel-JSON-XS.git/commit/?h=perl-Cpanel-JSON-XS-3.0218-1.fc25=66f88a4a476b70dcd5bb796b544926573bd35c9c
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

pghmcfc pushed to perl-Cpanel-JSON-XS (perl-Cpanel-JSON-XS-3.0218-1.fc26). "Update to 3.0218 (..more)"

[notifications]

This commit already existed in another branch.

http://pkgs.fedoraproject.org/cgit/perl-Cpanel-JSON-XS.git/commit/?h=perl-Cpanel-JSON-XS-3.0218-1.fc26=66f88a4a476b70dcd5bb796b544926573bd35c9c
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

pghmcfc pushed to perl-Cpanel-JSON-XS (f25). "Update to 3.0218 (..more)"

[notifications]

From 66f88a4a476b70dcd5bb796b544926573bd35c9c Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Thu, 13 Oct 2016 15:18:04 +0100
Subject: Update to 3.0218

- New upstream release 3.0218
  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
negative nan unified to "nan"
  - Use faster strEQc macros from cperl with constant strings
  - Prefer memEQ for systems without memcmp, to use bcmp there
  - Add more expect_false() to inf/nan branches
  - expect_false() macro fix for MSVC
  - Fix av and hv length types: protect from security sensitive overflows, add
HVMAX_T and RITER_T
  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
errors
  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
  - Fix and document wrong strEQc usage in new() (GH#70)
  - Fix t/gh70-asan.t for older perls < 5.14
  - Fix DPPP_dummy_PL_parser warnings
---
 perl-Cpanel-JSON-XS.spec | 26 +++---
 sources  |  2 +-
 2 files changed, 24 insertions(+), 4 deletions(-)

diff --git a/perl-Cpanel-JSON-XS.spec b/perl-Cpanel-JSON-XS.spec
index d7e4645..b85f606 100644
--- a/perl-Cpanel-JSON-XS.spec
+++ b/perl-Cpanel-JSON-XS.spec
@@ -1,6 +1,6 @@
 Name:  perl-Cpanel-JSON-XS
 Summary:   JSON::XS for Cpanel, fast and correct serializing
-Version:   3.0217
+Version:   3.0218
 Release:   1%{?dist}
 License:   GPL+ or Artistic
 URL:   http://search.cpan.org/dist/Cpanel-JSON-XS/
@@ -44,11 +44,12 @@ BuildRequires:  perl(lib)
 BuildRequires: perl(strict)
 BuildRequires: perl(Test)
 BuildRequires: perl(Test::More) >= 0.88
+BuildRequires: perl(Test::Simple)
 BuildRequires: perl(Tie::Array)
 BuildRequires: perl(Tie::Hash)
 BuildRequires: perl(utf8)
 BuildRequires: perl(warnings)
-%if !%{defined perl_bootstrap}
+# Optional Tests
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-LeakTrace → perl-Module-Install
 # → perl-YAML-Tiny → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Perl-MinimumVersion → perl-PPI
@@ -58,7 +59,7 @@ BuildRequires:perl(warnings)
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-Kwalitee → perl-Module-CPANTS-Analyse
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
-# Optional Tests
+%if !%{defined perl_bootstrap}
 BuildRequires: perl(common::sense) >= 3.5
 BuildRequires: perl(Hash::Util)
 BuildRequires: perl(JSON)
@@ -155,6 +156,25 @@ make test %{!?perl_bootstrap:AUTHOR_TESTING=1}
 %{_mandir}/man3/Cpanel::JSON::XS::Boolean.3*
 
 %changelog
+* Thu Oct 13 2016 Paul Howarth  - 3.0218-1
+- Update to 3.0218
+  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
+  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
+"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
+negative nan unified to "nan"
+  - Use faster strEQc macros from cperl with constant strings
+  - Prefer memEQ for systems without memcmp, to use bcmp there
+  - Add more expect_false() to inf/nan branches
+  - expect_false() macro fix for MSVC
+  - Fix av and hv length types: protect from security sensitive overflows, add
+HVMAX_T and RITER_T
+  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
+errors
+  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
+  - Fix and document wrong strEQc usage in new() (GH#70)
+  - Fix t/gh70-asan.t for older perls < 5.14
+  - Fix DPPP_dummy_PL_parser warnings
+
 * Sat Jun 18 2016 Paul Howarth  - 3.0217-1
 - Update to 3.0217
   - Improve test t/20_unknown.t for older JSON::PP
diff --git a/sources b/sources
index 4efb69f..bbb57ce 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-747672f925ce479d3da2ff316e47cf23  Cpanel-JSON-XS-3.0217.tar.gz
+818af1a8354341646d839ca1a14b780c  Cpanel-JSON-XS-3.0218.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Cpanel-JSON-XS.git/commit/?h=f25=66f88a4a476b70dcd5bb796b544926573bd35c9c
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: libbson soname alias removal

[Tomas Mraz]

On Čt, 2016-10-13 at 14:32 +, Petr Pisar wrote:
> On 2016-10-13, Tom Hughes  wrote:
> > 
> > 
> > In other words, does the soname need to change?
> > 
> The soname did not change. But packages built against older library
> linked to versioned symbols. Thus they had to be rebuild.
> 
> I'm not very verse in version symboling. If you think the removal
> requires bumping soname (technically probably yes because you simply
> cannot run the old executable against the new library), you can try
> to
> explain it to the upstream. At the and it's only a release candidate.
> But be prepared they are quite obstinate about this packaging stuff.

I do not think it is worth it. Effectively rpm dependencies detect this
breakage anyway so there is no need to change the soname.

-- 
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
  Turkish proverb
(You'll never know whether the road is wrong though.)


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: libbson soname alias removal

[Petr Pisar]

On 2016-10-13, Tom Hughes  wrote:
> On 13/10/16 14:05, Tom Hughes wrote:
>> On 13/10/16 13:50, Petr Pisar wrote:
>>
>>> libbson-1.5.0-0.1.rc2.fc26 removes soname aliases visiable on RPM level
>>> as "libbson-1.0.so.0(LIBBSON_*)(64bit)" provides and keeps
>>> "libbson-1.0.so.0()(64bit)" only.
>>
>> That's not an "soname alias" it's a symbol versioning provide.
>>
>> So are you saying that this library has stopped using symbol versioning?
>
> I think https://jira.mongodb.org/browse/CDRIVER-1347 is likely the root 
> cause although I don't see where the code they removed was actually 
> setting the specific versions.
>
> So it seems they changed how they export the symbols and hide private 
> symbols, but the question is whether the new ABI can really be described 
> as unchanged if there used to be five different ABIs supported in the 
> same library and now there is only one!
>
Technically, the versioned symbols disappeared. The unversioned symbols
remained. The reality was that the symbol versioning in the libbson was
never properly used and updated.

> In other words, does the soname need to change?
>
The soname did not change. But packages built against older library
linked to versioned symbols. Thus they had to be rebuild.

I'm not very verse in version symboling. If you think the removal
requires bumping soname (technically probably yes because you simply
cannot run the old executable against the new library), you can try to
explain it to the upstream. At the and it's only a release candidate.
But be prepared they are quite obstinate about this packaging stuff.

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

pghmcfc pushed to perl-Cpanel-JSON-XS (master). "Update to 3.0218 (..more)"

[notifications]

From 66f88a4a476b70dcd5bb796b544926573bd35c9c Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Thu, 13 Oct 2016 15:18:04 +0100
Subject: Update to 3.0218

- New upstream release 3.0218
  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
negative nan unified to "nan"
  - Use faster strEQc macros from cperl with constant strings
  - Prefer memEQ for systems without memcmp, to use bcmp there
  - Add more expect_false() to inf/nan branches
  - expect_false() macro fix for MSVC
  - Fix av and hv length types: protect from security sensitive overflows, add
HVMAX_T and RITER_T
  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
errors
  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
  - Fix and document wrong strEQc usage in new() (GH#70)
  - Fix t/gh70-asan.t for older perls < 5.14
  - Fix DPPP_dummy_PL_parser warnings
---
 perl-Cpanel-JSON-XS.spec | 26 +++---
 sources  |  2 +-
 2 files changed, 24 insertions(+), 4 deletions(-)

diff --git a/perl-Cpanel-JSON-XS.spec b/perl-Cpanel-JSON-XS.spec
index d7e4645..b85f606 100644
--- a/perl-Cpanel-JSON-XS.spec
+++ b/perl-Cpanel-JSON-XS.spec
@@ -1,6 +1,6 @@
 Name:  perl-Cpanel-JSON-XS
 Summary:   JSON::XS for Cpanel, fast and correct serializing
-Version:   3.0217
+Version:   3.0218
 Release:   1%{?dist}
 License:   GPL+ or Artistic
 URL:   http://search.cpan.org/dist/Cpanel-JSON-XS/
@@ -44,11 +44,12 @@ BuildRequires:  perl(lib)
 BuildRequires: perl(strict)
 BuildRequires: perl(Test)
 BuildRequires: perl(Test::More) >= 0.88
+BuildRequires: perl(Test::Simple)
 BuildRequires: perl(Tie::Array)
 BuildRequires: perl(Tie::Hash)
 BuildRequires: perl(utf8)
 BuildRequires: perl(warnings)
-%if !%{defined perl_bootstrap}
+# Optional Tests
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-LeakTrace → perl-Module-Install
 # → perl-YAML-Tiny → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Perl-MinimumVersion → perl-PPI
@@ -58,7 +59,7 @@ BuildRequires:perl(warnings)
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
 # Cycle: perl-Cpanel-JSON-XS → perl-Test-Kwalitee → perl-Module-CPANTS-Analyse
 # → perl-JSON-MaybeXS → perl-Cpanel-JSON-XS
-# Optional Tests
+%if !%{defined perl_bootstrap}
 BuildRequires: perl(common::sense) >= 3.5
 BuildRequires: perl(Hash::Util)
 BuildRequires: perl(JSON)
@@ -155,6 +156,25 @@ make test %{!?perl_bootstrap:AUTHOR_TESTING=1}
 %{_mandir}/man3/Cpanel::JSON::XS::Boolean.3*
 
 %changelog
+* Thu Oct 13 2016 Paul Howarth  - 3.0218-1
+- Update to 3.0218
+  - Detect INF/NAN: ?/++/-?/--- on HP-UX (GH#56)
+  - New stringify_infnan(3) infnan_mode; easy to detect platform-independent
+"inf", "-inf" or "nan" strings with double quotes, with qnan, snan or
+negative nan unified to "nan"
+  - Use faster strEQc macros from cperl with constant strings
+  - Prefer memEQ for systems without memcmp, to use bcmp there
+  - Add more expect_false() to inf/nan branches
+  - expect_false() macro fix for MSVC
+  - Fix av and hv length types: protect from security sensitive overflows, add
+HVMAX_T and RITER_T
+  - Add new "Hash key too large" error; perl5 silently truncates it, we prefer
+errors
+  - Fix broken 5.8.1 SvPOK_only, i.e. assert_not_ROK
+  - Fix and document wrong strEQc usage in new() (GH#70)
+  - Fix t/gh70-asan.t for older perls < 5.14
+  - Fix DPPP_dummy_PL_parser warnings
+
 * Sat Jun 18 2016 Paul Howarth  - 3.0217-1
 - Update to 3.0217
   - Improve test t/20_unknown.t for older JSON::PP
diff --git a/sources b/sources
index 4efb69f..bbb57ce 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-747672f925ce479d3da2ff316e47cf23  Cpanel-JSON-XS-3.0217.tar.gz
+818af1a8354341646d839ca1a14b780c  Cpanel-JSON-XS-3.0218.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Cpanel-JSON-XS.git/commit/?h=master=66f88a4a476b70dcd5bb796b544926573bd35c9c
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

pghmcfc uploaded Cpanel-JSON-XS-3.0218.tar.gz for perl-Cpanel-JSON-XS

[notifications]

818af1a8354341646d839ca1a14b780c  Cpanel-JSON-XS-3.0218.tar.gz

http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Cpanel-JSON-XS/Cpanel-JSON-XS-3.0218.tar.gz/md5/818af1a8354341646d839ca1a14b780c/Cpanel-JSON-XS-3.0218.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-Net-SSH2 (f25). "0.63 bump"

[notifications]

From 4f799b0a1fcfd413c20f9f8854609c8117daa778 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 16:01:18 +0200
Subject: 0.63 bump

---
 .gitignore | 1 +
 perl-Net-SSH2.spec | 5 -
 sources| 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 9165df8..17b6e87 100644
--- a/.gitignore
+++ b/.gitignore
@@ -18,3 +18,4 @@ Net-SSH2-0.28.tar.gz
 /Net-SSH2-0.60.tar.gz
 /Net-SSH2-0.61.tar.gz
 /Net-SSH2-0.62.tar.gz
+/Net-SSH2-0.63.tar.gz
diff --git a/perl-Net-SSH2.spec b/perl-Net-SSH2.spec
index 7372cde..0ea9bc4 100644
--- a/perl-Net-SSH2.spec
+++ b/perl-Net-SSH2.spec
@@ -1,5 +1,5 @@
 Name:   perl-Net-SSH2
-Version:0.62
+Version:0.63
 Release:1%{?dist}
 Summary:Support for the SSH 2 protocol via libSSH2
 License:GPL+ or Artistic
@@ -89,6 +89,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 0.63-1
+- 0.63 bump
+
 * Thu Jun 09 2016 Jitka Plesnikova  - 0.62-1
 - 0.62 bump
 
diff --git a/sources b/sources
index dd4ad18..a762469 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-2e0d20f25967d66cf2fc8c0304349b47  Net-SSH2-0.62.tar.gz
+bcac41475b9f8f20a791bcc410fee912  Net-SSH2-0.63.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Net-SSH2.git/commit/?h=f25=4f799b0a1fcfd413c20f9f8854609c8117daa778
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384501] perl-Net-SSH2-0.63 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384501

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Net-SSH2-0.63-1.fc26



--- Comment #1 from Petr Pisar  ---
A bug fix release suitable for F ≥ 25.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-Net-SSH2 (master). "0.63 bump"

[notifications]

From 4f799b0a1fcfd413c20f9f8854609c8117daa778 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 16:01:18 +0200
Subject: 0.63 bump

---
 .gitignore | 1 +
 perl-Net-SSH2.spec | 5 -
 sources| 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 9165df8..17b6e87 100644
--- a/.gitignore
+++ b/.gitignore
@@ -18,3 +18,4 @@ Net-SSH2-0.28.tar.gz
 /Net-SSH2-0.60.tar.gz
 /Net-SSH2-0.61.tar.gz
 /Net-SSH2-0.62.tar.gz
+/Net-SSH2-0.63.tar.gz
diff --git a/perl-Net-SSH2.spec b/perl-Net-SSH2.spec
index 7372cde..0ea9bc4 100644
--- a/perl-Net-SSH2.spec
+++ b/perl-Net-SSH2.spec
@@ -1,5 +1,5 @@
 Name:   perl-Net-SSH2
-Version:0.62
+Version:0.63
 Release:1%{?dist}
 Summary:Support for the SSH 2 protocol via libSSH2
 License:GPL+ or Artistic
@@ -89,6 +89,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 0.63-1
+- 0.63 bump
+
 * Thu Jun 09 2016 Jitka Plesnikova  - 0.62-1
 - 0.62 bump
 
diff --git a/sources b/sources
index dd4ad18..a762469 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-2e0d20f25967d66cf2fc8c0304349b47  Net-SSH2-0.62.tar.gz
+bcac41475b9f8f20a791bcc410fee912  Net-SSH2-0.63.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-Net-SSH2.git/commit/?h=master=4f799b0a1fcfd413c20f9f8854609c8117daa778
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar uploaded Net-SSH2-0.63.tar.gz for perl-Net-SSH2

[notifications]

bcac41475b9f8f20a791bcc410fee912  Net-SSH2-0.63.tar.gz

http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Net-SSH2/Net-SSH2-0.63.tar.gz/md5/bcac41475b9f8f20a791bcc410fee912/Net-SSH2-0.63.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

redhat-rpm-config config.sub/guess are old

[Richard W.M. Jones]

The versions of config.sub and config.guess in redhat-rpm-config are
3+ years old.  I'd like to update these to the very latest versions,
primarily because the upstream versions support riscv64.

Is there a reason not to do that?  I don't want to break something
unexpectedly.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1384501] perl-Net-SSH2-0.63 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384501

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com |ppi...@redhat.com
   Assignee|jples...@redhat.com |ppi...@redhat.com



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-CPAN-Perl-Releases (f24). "2.96 bump"

[notifications]

From 6e885bbaa093f0b584bdcad78f92e9ec64604c26 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 15:37:27 +0200
Subject: 2.96 bump

---
 .gitignore   | 1 +
 perl-CPAN-Perl-Releases.spec | 5 -
 sources  | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 42690f9..d141479 100644
--- a/.gitignore
+++ b/.gitignore
@@ -55,3 +55,4 @@
 /CPAN-Perl-Releases-2.90.tar.gz
 /CPAN-Perl-Releases-2.92.tar.gz
 /CPAN-Perl-Releases-2.94.tar.gz
+/CPAN-Perl-Releases-2.96.tar.gz
diff --git a/perl-CPAN-Perl-Releases.spec b/perl-CPAN-Perl-Releases.spec
index 7d01577..8c30cd1 100644
--- a/perl-CPAN-Perl-Releases.spec
+++ b/perl-CPAN-Perl-Releases.spec
@@ -1,5 +1,5 @@
 Name:   perl-CPAN-Perl-Releases
-Version:2.94
+Version:2.96
 Release:1%{?dist}
 Summary:Mapping Perl releases on CPAN to the location of the tarballs
 License:GPL+ or Artistic
@@ -53,6 +53,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 2.96-1
+- 2.96 bump
+
 * Thu Sep 29 2016 Jitka Plesnikova  - 2.94-1
 - 2.94 bump
 
diff --git a/sources b/sources
index 9cc01eb..698bdc4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-e3792ce53817fa31fd90fa894c68c645  CPAN-Perl-Releases-2.94.tar.gz
+6a6799d04ab52472446c40a4a3a2  CPAN-Perl-Releases-2.96.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-CPAN-Perl-Releases.git/commit/?h=f24=6e885bbaa093f0b584bdcad78f92e9ec64604c26
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-CPAN-Perl-Releases (f25). "2.96 bump"

[notifications]

From 33c9079ac24ff785710be280c46234a00a7ba464 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 15:37:27 +0200
Subject: 2.96 bump

---
 .gitignore   | 1 +
 perl-CPAN-Perl-Releases.spec | 5 -
 sources  | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 42690f9..d141479 100644
--- a/.gitignore
+++ b/.gitignore
@@ -55,3 +55,4 @@
 /CPAN-Perl-Releases-2.90.tar.gz
 /CPAN-Perl-Releases-2.92.tar.gz
 /CPAN-Perl-Releases-2.94.tar.gz
+/CPAN-Perl-Releases-2.96.tar.gz
diff --git a/perl-CPAN-Perl-Releases.spec b/perl-CPAN-Perl-Releases.spec
index 5070b48..3adc19f 100644
--- a/perl-CPAN-Perl-Releases.spec
+++ b/perl-CPAN-Perl-Releases.spec
@@ -1,5 +1,5 @@
 Name:   perl-CPAN-Perl-Releases
-Version:2.94
+Version:2.96
 Release:1%{?dist}
 Summary:Mapping Perl releases on CPAN to the location of the tarballs
 License:GPL+ or Artistic
@@ -53,6 +53,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 2.96-1
+- 2.96 bump
+
 * Thu Sep 29 2016 Jitka Plesnikova  - 2.94-1
 - 2.94 bump
 
diff --git a/sources b/sources
index 9cc01eb..698bdc4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-e3792ce53817fa31fd90fa894c68c645  CPAN-Perl-Releases-2.94.tar.gz
+6a6799d04ab52472446c40a4a3a2  CPAN-Perl-Releases-2.96.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-CPAN-Perl-Releases.git/commit/?h=f25=33c9079ac24ff785710be280c46234a00a7ba464
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384495] perl-CPAN-Perl-Releases-2.96 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384495

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-CPAN-Perl-Releases-2.9
   ||6-1.fc26



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for F ≥ 24.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar pushed to perl-CPAN-Perl-Releases (master). "2.96 bump"

[notifications]

From dc31ce5a9c7fb4021f7f6e98a39b170893d6102e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 15:37:27 +0200
Subject: 2.96 bump

---
 .gitignore   | 1 +
 perl-CPAN-Perl-Releases.spec | 5 -
 sources  | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index 42690f9..d141479 100644
--- a/.gitignore
+++ b/.gitignore
@@ -55,3 +55,4 @@
 /CPAN-Perl-Releases-2.90.tar.gz
 /CPAN-Perl-Releases-2.92.tar.gz
 /CPAN-Perl-Releases-2.94.tar.gz
+/CPAN-Perl-Releases-2.96.tar.gz
diff --git a/perl-CPAN-Perl-Releases.spec b/perl-CPAN-Perl-Releases.spec
index 5070b48..3adc19f 100644
--- a/perl-CPAN-Perl-Releases.spec
+++ b/perl-CPAN-Perl-Releases.spec
@@ -1,5 +1,5 @@
 Name:   perl-CPAN-Perl-Releases
-Version:2.94
+Version:2.96
 Release:1%{?dist}
 Summary:Mapping Perl releases on CPAN to the location of the tarballs
 License:GPL+ or Artistic
@@ -53,6 +53,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 2.96-1
+- 2.96 bump
+
 * Thu Sep 29 2016 Jitka Plesnikova  - 2.94-1
 - 2.94 bump
 
diff --git a/sources b/sources
index 9cc01eb..698bdc4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-e3792ce53817fa31fd90fa894c68c645  CPAN-Perl-Releases-2.94.tar.gz
+6a6799d04ab52472446c40a4a3a2  CPAN-Perl-Releases-2.96.tar.gz
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-CPAN-Perl-Releases.git/commit/?h=master=dc31ce5a9c7fb4021f7f6e98a39b170893d6102e
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

ppisar uploaded CPAN-Perl-Releases-2.96.tar.gz for perl-CPAN-Perl-Releases

[notifications]

6a6799d04ab52472446c40a4a3a2  CPAN-Perl-Releases-2.96.tar.gz

http://pkgs.fedoraproject.org/lookaside/pkgs/perl-CPAN-Perl-Releases/CPAN-Perl-Releases-2.96.tar.gz/md5/6a6799d04ab52472446c40a4a3a2/CPAN-Perl-Releases-2.96.tar.gz
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384495] perl-CPAN-Perl-Releases-2.96 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384495

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|jples...@redhat.com |ppi...@redhat.com
   Assignee|jples...@redhat.com |ppi...@redhat.com



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: libbson soname alias removal

[Tom Hughes]

On 13/10/16 14:05, Tom Hughes wrote:

On 13/10/16 13:50, Petr Pisar wrote:


libbson-1.5.0-0.1.rc2.fc26 removes soname aliases visiable on RPM level
as "libbson-1.0.so.0(LIBBSON_*)(64bit)" provides and keeps
"libbson-1.0.so.0()(64bit)" only.


That's not an "soname alias" it's a symbol versioning provide.

So are you saying that this library has stopped using symbol versioning?


I think https://jira.mongodb.org/browse/CDRIVER-1347 is likely the root 
cause although I don't see where the code they removed was actually 
setting the specific versions.


So it seems they changed how they export the symbols and hide private 
symbols, but the question is whether the new ABI can really be described 
as unchanged if there used to be five different ABIs supported in the 
same library and now there is only one!


In other words, does the soname need to change?

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

ppisar pushed to perl-MongoDB (master). "Rebuild against libbson-1.5.0-rc2"

[notifications]

From 5ec3e08c90b6135f82e5ebc02477bd7ff517889a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Thu, 13 Oct 2016 14:54:32 +0200
Subject: Rebuild against libbson-1.5.0-rc2

---
 perl-MongoDB.spec | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/perl-MongoDB.spec b/perl-MongoDB.spec
index ac95493..e48f22e 100644
--- a/perl-MongoDB.spec
+++ b/perl-MongoDB.spec
@@ -1,6 +1,6 @@
 Name:   perl-MongoDB
 Version:1.4.5
-Release:1%{?dist}
+Release:2%{?dist}
 Summary:A MongoDB Driver for Perl
 ## Installed:
 # lib/MongoDB/_Link.pm: ASL 2.0 and (GPL+ or Artistic)
@@ -184,6 +184,9 @@ exit $test_rc
 %{_mandir}/man3/*
 
 %changelog
+* Thu Oct 13 2016 Petr Pisar  - 1.4.5-2
+- Rebuild against libbson-1.5.0-rc2 (bug #1380063)
+
 * Fri Sep 02 2016 Petr Pisar  - 1.4.5-1
 - 1.4.5 bump
 
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-MongoDB.git/commit/?h=master=5ec3e08c90b6135f82e5ebc02477bd7ff517889a
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: libbson soname alias removal

[Tom Hughes]

On 13/10/16 13:50, Petr Pisar wrote:


libbson-1.5.0-0.1.rc2.fc26 removes soname aliases visiable on RPM level
as "libbson-1.0.so.0(LIBBSON_*)(64bit)" provides and keeps
"libbson-1.0.so.0()(64bit)" only.


That's not an "soname alias" it's a symbol versioning provide.

So are you saying that this library has stopped using symbol versioning?

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

libbson soname alias removal

[Petr Pisar]

libbson-1.5.0-0.1.rc2.fc26 removes soname aliases visiable on RPM level
as "libbson-1.0.so.0(LIBBSON_*)(64bit)" provides and keeps
"libbson-1.0.so.0()(64bit)" only.

The 1.5.0-rc2 will be pushed into rawhide only and I will rebuild the
three affected packages there:

mongo-c-driver-1.3.5-6.fc26.src.rpm
perl-MongoDB-1.4.5-1.fc26.src.rpm
php-pecl-mongodb-1.1.8-4.fc26.src.rpm

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1384501] New: perl-Net-SSH2-0.63 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384501

Bug ID: 1384501
   Summary: perl-Net-SSH2-0.63 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Net-SSH2
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 0.63
Current version/release in rawhide: 0.62-1.fc25
URL: http://search.cpan.org/dist/Net-SSH2/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/3163/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

[Bug 1384495] New: perl-CPAN-Perl-Releases-2.96 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384495

Bug ID: 1384495
   Summary: perl-CPAN-Perl-Releases-2.96 is available
   Product: Fedora
   Version: rawhide
 Component: perl-CPAN-Perl-Releases
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org



Latest upstream release: 2.96
Current version/release in rawhide: 2.94-1.fc26
URL: http://search.cpan.org/dist/CPAN-Perl-Releases/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.

Based on the information from anitya: 
https://release-monitoring.org/project/5881/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Jan Kurik]

On Thu, Oct 13, 2016 at 1:22 PM, Josh Boyer  wrote:
> On Thu, Oct 13, 2016 at 12:02 AM, Adam Williamson
>  wrote:
>> On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote:
>>> On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson
>>>  wrote:
>>> > On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote:
>>> > > All of the extra app stuff could be avoided if we disallowed reporters
>>> > > (or random people) to change the Severity and Priority fields.
>>> >
>>> > Mmm, I don't really think so. Presumably it would be maintainers who
>>> > got to set those fields, right? But they are doing so in relation to
>>>
>>> No, why would you presume that?
>>
>> I dunno, just seemed logical. That's how they're intended to be used at
>> present. Bug reporters aren't supposed to set them and don't have the
>> privilege purely by rights of having an account...but because we grant
>> 'editbugs' to all packagers and all QA team members, in practice a lot
>> of the people who actually report bugs do have the power to set it.
>>
>> If you're suggesting we restrict access to those fields such that even
>> the packagers can't use them...well, it's a possibility, but I think at
>> least *some* teams do actually use those fields at present, and would
>> be inconvenienced by not being able to any more because we'd decided to
>> take them over for distribution purposes.
>>
>>> Right.  Which speaks to Matt's "very restricted" list of people.
>>> Which would essentially be the same group that is going to do the
>>> categorizing anyway.  Which means that since the fields are useless
>>> today (as in, completely) restricting them to useful to avoid another
>>> process or tool could be a possibility.
>>
>> Well sure, but on the other hand, if all you want to propose is 'do it
>> all in Bugzilla', you don't really need to use those fields; just a
>
> No.  My main goal is "stop building one-off tools because existing
> tools (or usage of them) suck".  If people want to enhance blockerbugs
> since it already exists, that's totally fine with me.  Basically, I
> want us to stop wasting effort and creating more technical debt.

I am fine with using just Bugzilla for this purpose. It does not have
fancy UI, but the capabilities for this job are sufficient. So, lets
start with Bugzilla and we will see whether there will be a need for
something more specific as we go.

I was also exploring a way how we can ensure the priority/severity
fields will not be changed once the bug is tracked as "Important" by
someone "non-authorized". My proposal is to use "PM Score" field
instead. This is a hidden field, every bug has attached, and is not
currently used for bugs in Fedora. The original purpose of this field
is to prioritize bugs from the perspective of Product Management, so
it in fact reflects what we are trying to achieve. The value of this
field is numerical and is visible as a comment any time someone sets
or changes its value. It is accessible via XML/RPC only.

Bugzilla has also a built-in tool called BRE (Bugzilla Rule Engine)
which allow us to react on a change of a field and do some actions. So
we might then enforce value of bug's priority according to the value
sets in the PM Score field, if this will be useful.

Regards,
Jan

> josh
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

ppisar pushed to perl-CPAN (master). "Fix CVE-2016-1238 properly"

[notifications]

From df7a613c62b790af8062a933e4561badee2394e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
Date: Wed, 12 Oct 2016 17:10:18 +0200
Subject: Fix CVE-2016-1238 properly

---
 CPAN-2.14-Fix-CVE-2016-1238-properly.patch | 45 ++
 perl-CPAN.spec |  8 +-
 2 files changed, 52 insertions(+), 1 deletion(-)
 create mode 100644 CPAN-2.14-Fix-CVE-2016-1238-properly.patch

diff --git a/CPAN-2.14-Fix-CVE-2016-1238-properly.patch 
b/CPAN-2.14-Fix-CVE-2016-1238-properly.patch
new file mode 100644
index 000..bc5100c
--- /dev/null
+++ b/CPAN-2.14-Fix-CVE-2016-1238-properly.patch
@@ -0,0 +1,45 @@
+From 9b0b275d923418306cb3c45bb380bd9dcc71476c Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= 
+Date: Wed, 12 Oct 2016 16:56:41 +0200
+Subject: [PATCH] Fix CVE-2016-1238 properly
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Removing "." from @INC does not work because CPAN module translates
+all relative paths into absolute paths. Check for $INC[-1] eq '.'
+sooner.
+
+Signed-off-by: Petr Písař 
+---
+ lib/App/Cpan.pm | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/lib/App/Cpan.pm b/lib/App/Cpan.pm
+index c654c2c..ce7afe5 100644
+--- a/lib/App/Cpan.pm
 b/lib/App/Cpan.pm
+@@ -1,5 +1,11 @@
+ package App::Cpan;
+ 
++# CPAN module translantes @INC, CPAN RT#116507
++my $last_inc_is_dot;
++BEGIN {
++$last_inc_is_dot = $INC[-1] eq '.';
++}
++
+ use strict;
+ use warnings;
+ use vars qw($VERSION);
+@@ -555,7 +561,7 @@ sub _safe_load_module {
+ my $name = shift;
+ 
+ local @INC = @INC;
+-pop @INC if $INC[-1] eq '.';
++pop @INC if $last_inc_is_dot;
+ 
+ eval "require $name; 1";
+ }
+-- 
+2.7.4
+
diff --git a/perl-CPAN.spec b/perl-CPAN.spec
index 6724388..05cc4a7 100644
--- a/perl-CPAN.spec
+++ b/perl-CPAN.spec
@@ -1,6 +1,6 @@
 Name:   perl-CPAN
 Version:2.14
-Release:1%{?dist}
+Release:2%{?dist}
 Summary:Query, download and build perl modules from CPAN sites
 License:GPL+ or Artistic
 Group:  Development/Libraries
@@ -26,6 +26,8 @@ Patch6: 
CPAN-2.14-CVE-2016-1238-don-t-load-optional-modules-from-defau.p
 Patch7: 
CPAN-2.14-Bugfix-47934-version-requirement-with-was-ignored.patch
 # Cope with non-digit version strings, fixed after 2.14
 Patch8: CPAN-2.14-accepts_module-must-be-protected-with-an-eval.patch
+# Fix CVE-2016-1238 properly, CPAN RT#116507
+Patch9: CPAN-2.14-Fix-CVE-2016-1238-properly.patch
 BuildArch:  noarch
 BuildRequires:  coreutils
 BuildRequires:  findutils
@@ -210,6 +212,7 @@ external download clients to fetch distributions from the 
net.
 %patch6 -p1
 %patch7 -p1
 %patch8 -p1
+%patch9 -p1
 # Change configuration name
 find -type f -exec sed -i -e 's/XCPANCONFIGNAMEX/cpan/g' {} \;
 # Remove bundled modules
@@ -236,6 +239,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Wed Oct 12 2016 Petr Pisar  - 2.14-2
+- Fix CVE-2016-1238 properly (CPAN RT#116507)
+
 * Mon Jun 27 2016 Petr Pisar  - 2.14-1
 - 2.14 bump
 - Fix installation from a working directory (CPAN RT#115734)
-- 
cgit v0.12



http://pkgs.fedoraproject.org/cgit/perl-CPAN.git/commit/?h=master=df7a613c62b790af8062a933e4561badee2394e5
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: rawhide vs koji f26 builds

[Dan Horák]

On Thu, 13 Oct 2016 11:26:55 + (UTC)
Petr Pisar  wrote:

> On 2016-10-12, Kaleb S. KEITHLEY  wrote:
> >
> > Sure, but I just installed a rawhide box from 
> > Fedora-Server-netinst-x86_64-Rawhide-20161010.n.0.iso and it still
> > has openssl-1.0.2j-1.fc26.x86_64 and a `dnf update openssl` is not
> > giving me anything newer.
> >
> Because rawhide repositories are subject of mirroring as any other
> repository for F25, F25-updates, F25-updates-testing etc. It takes at
> least a day to reach end-user public mirrors.
> 
> When building in koji, one uses f26-build repository. This is not
> mirrored anywhere. It's regenerated any time a new build finishes.
> This is not "rawhide" repository. It even has different comps groups.
> 
> > I guess I can go get 
> > Fedora-Server-netinst-x86_64-Rawhide-20161011.n.0.iso or install
> > the rpms from
> > http://koji.fedoraproject.org/koji/buildinfo?buildID=809049.
> >
> You can access f26-build repository from
> .

for local mock builds adding "--enablerepo=local" option enables the
koji build repo


Dan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: rawhide vs koji f26 builds

[Petr Pisar]

On 2016-10-12, Kaleb S. KEITHLEY  wrote:
>
> Sure, but I just installed a rawhide box from 
> Fedora-Server-netinst-x86_64-Rawhide-20161010.n.0.iso and it still has 
> openssl-1.0.2j-1.fc26.x86_64 and a `dnf update openssl` is not giving me 
> anything newer.
>
Because rawhide repositories are subject of mirroring as any other
repository for F25, F25-updates, F25-updates-testing etc. It takes at
least a day to reach end-user public mirrors.

When building in koji, one uses f26-build repository. This is not
mirrored anywhere. It's regenerated any time a new build finishes. This
is not "rawhide" repository. It even has different comps groups.

> I guess I can go get 
> Fedora-Server-netinst-x86_64-Rawhide-20161011.n.0.iso or install the 
> rpms from http://koji.fedoraproject.org/koji/buildinfo?buildID=809049.
>
You can access f26-build repository from
.

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Josh Boyer]

On Thu, Oct 13, 2016 at 12:02 AM, Adam Williamson
 wrote:
> On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote:
>> On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson
>>  wrote:
>> > On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote:
>> > > All of the extra app stuff could be avoided if we disallowed reporters
>> > > (or random people) to change the Severity and Priority fields.
>> >
>> > Mmm, I don't really think so. Presumably it would be maintainers who
>> > got to set those fields, right? But they are doing so in relation to
>>
>> No, why would you presume that?
>
> I dunno, just seemed logical. That's how they're intended to be used at
> present. Bug reporters aren't supposed to set them and don't have the
> privilege purely by rights of having an account...but because we grant
> 'editbugs' to all packagers and all QA team members, in practice a lot
> of the people who actually report bugs do have the power to set it.
>
> If you're suggesting we restrict access to those fields such that even
> the packagers can't use them...well, it's a possibility, but I think at
> least *some* teams do actually use those fields at present, and would
> be inconvenienced by not being able to any more because we'd decided to
> take them over for distribution purposes.
>
>> Right.  Which speaks to Matt's "very restricted" list of people.
>> Which would essentially be the same group that is going to do the
>> categorizing anyway.  Which means that since the fields are useless
>> today (as in, completely) restricting them to useful to avoid another
>> process or tool could be a possibility.
>
> Well sure, but on the other hand, if all you want to propose is 'do it
> all in Bugzilla', you don't really need to use those fields; just a

No.  My main goal is "stop building one-off tools because existing
tools (or usage of them) suck".  If people want to enhance blockerbugs
since it already exists, that's totally fine with me.  Basically, I
want us to stop wasting effort and creating more technical debt.

josh
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[Bug 1384434] New: perl-Audio-Beep build is interactive

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1384434

Bug ID: 1384434
   Summary: perl-Audio-Beep build is interactive
   Product: Fedora
   Version: rawhide
 Component: perl-Audio-Beep
  Assignee: jan.kle...@gmail.com
  Reporter: rjo...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jan.kle...@gmail.com,
perl-devel@lists.fedoraproject.org



Description of problem:

The perl-Audio-Beep package fails to build from source unless
stdin is /dev/null.  This is because the build interactively
asks questions:

$ fedpkg local
Downloading Audio-Beep-0.11.tar.gz
 100.0% 


Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DDaXlx
+ umask 022
+ cd /home/rjones/d/fedora/perl-Audio-Beep/master
+ cd /home/rjones/d/fedora/perl-Audio-Beep/master
+ rm -rf Audio-Beep-0.11
+ /usr/bin/gzip -dc
/home/rjones/d/fedora/perl-Audio-Beep/master/Audio-Beep-0.11.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Audio-Beep-0.11
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ chmod -x music/beep_player.pl
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.1IrEhL
+ umask 022
+ cd /home/rjones/d/fedora/perl-Audio-Beep/master
+ cd Audio-Beep-0.11
+ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor 'OPTIMIZE=-O2 -g -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic'
Would you like to install Japanese documentation?
If you enter 'y' then i will try to install Japanese docs alongside
English ones. On platforms using 'man' manpages (typically on UN*X)
Japanese documentation will be available transparently to users whose
locale language is set to Japanese.
On other platforms the documentation will be available as Audio::Beep_jp
Default is to not install Japanese docs. [N/y]

(At this point the build hangs)


Version-Release number of selected component (if applicable):

perl-Audio-Beep-0.11-17.fc26

How reproducible:

100%

Steps to Reproduce:
1. Run 'fedpkg local', 'rpmbuild' etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Jeff Fearn]

On 13/10/2016 4:56 PM, Adam Williamson wrote:
> On Thu, 2016-10-13 at 14:40 +1000, Jeff Fearn wrote:
>> On 13/10/16 14:02, Adam Williamson wrote:
>>> On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote:
 On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson
  wrote:
> On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote:
>> All of the extra app stuff could be avoided if we disallowed reporters
>> (or random people) to change the Severity and Priority fields.
> Mmm, I don't really think so. Presumably it would be maintainers who
> got to set those fields, right? But they are doing so in relation to
 No, why would you presume that?
>>> I dunno, just seemed logical. That's how they're intended to be used at
>>> present. Bug reporters aren't supposed to set them and don't have the
>>> privilege purely by rights of having an account
>> This is true for priority but not true for severity. Severity is the
>> external, i.e. reporters, weighting
>> of the bug and you do not need to be in editbugs to set it.
> That's not the intent of the fields as I understand them. 'severity' is
> supposed to represent how bad the bug is, whereas 'priority' is
> supposed to represent how important it is to get it fixed compared to
> other bugs in the same component. They're obviously related, but not
> the same, and it's not "severity is the reporter's opinion, priority is
> the maintainers' opinion", no.
My understanding is based on ye olde services plan:

"Bugzilla Severity and Priority

When filing a new bug report, or actioning an existing bug, it is
important to bear in mind that, while both the 'Severity' and 'Priority'
fields are required; 'Priority' is an internal weighting and 'Severity'
is customer weighting. This distinction can cause confusion if not
consistant."

This is only significant in that it may have impacted the way they are
coded on BRC.

> I think you might be right that we allow the bug reporter to set
> 'severity', though.

BRC carries a custom patch to restrict priority to a group besides
editbugs group (the setpriority group), AFAICT there is no code that
allows similar restriction of the severity field.

Cheers, Jeff.



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RISC-V struggle (for GMP porting)

[Richard W.M. Jones]

On Tue, Oct 11, 2016 at 08:29:59AM +0100, Richard W.M. Jones wrote:
> > Furthermore, stage4-disk.img.xz is a strange beast; it contains a
> > compiler but no include files and no 'as' command.
> 
> Our rather hacked-up GCC is missing dependencies on glibc-headers &
> binutils.  We're going to fix this, but compiling GCC is an extremely
> slow and iterative process.  So temporarily you will need to:
> 
>   # dnf install binutils glibc-headers
> 
> inside the VM.

FYI with the stage4 disk image just uploaded, GCC is fixed
properly and the above is no longer necessary.

https://fedorapeople.org/groups/risc-v/disk-images/

(Thanks to Stefan O'Rear for fixing this lot.)

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Sudhir Dharanendraiah]

- Original Message -
| From: "Adam Williamson" 
| To: "Development discussions related to Fedora" 

| Sent: Thursday, October 13, 2016 12:26:10 PM
| Subject: Re: PROPOSAL: Blocking the release is our only "big hammer" — let's 
add a softer one.
| 
| On Thu, 2016-10-13 at 14:40 +1000, Jeff Fearn wrote:
| > On 13/10/16 14:02, Adam Williamson wrote:
| > > On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote:
| > > > On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson
| > > >  wrote:
| > > > > On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote:
| > > > > > All of the extra app stuff could be avoided if we disallowed
| > > > > > reporters
| > > > > > (or random people) to change the Severity and Priority fields.
| > > > > 
| > > > > Mmm, I don't really think so. Presumably it would be maintainers who
| > > > > got to set those fields, right? But they are doing so in relation to
| > > > 
| > > > No, why would you presume that?
| > > 
| > > I dunno, just seemed logical. That's how they're intended to be used at
| > > present. Bug reporters aren't supposed to set them and don't have the
| > > privilege purely by rights of having an account
| > 
| > This is true for priority but not true for severity. Severity is the
| > external, i.e. reporters, weighting
| > of the bug and you do not need to be in editbugs to set it.
| 
| That's not the intent of the fields as I understand them. 'severity' is
| supposed to represent how bad the bug is, whereas 'priority' is
| supposed to represent how important it is to get it fixed compared to
| other bugs in the same component. They're obviously related, but not
| the same, and it's not "severity is the reporter's opinion, priority is
| the maintainers' opinion", no.
| 
| I think you might be right that we allow the bug reporter to set
| 'severity', though.

There is no direct relation between these fields.
Many projects interpret in different ways, but the most common way is,
'severity' is what user thinks of the issue, how much of an issue it is for him 
('user' is a QE engineer/consumer or a developer of other component). This is 
usually set to get the attention of the developer/owner of component over other 
bugs in same component. 
'priority' is what the developer/owner of the component (owner of the bug) 
thinks its severity is. It can also be a consensus from all stake holders.

It is not uncommon to see high severity bugs getting triaged first. It is also 
a good practice to keep priority and severity at comparable, if not same level 
once triaged (i.e., it would not logically seem correct to see high severity 
with low priority or vice-versa after triage).

Regards,
Sudhir

| --
| Adam Williamson
| Fedora QA Community Monkey
| IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
| http://www.happyassassin.net
| ___
| devel mailing list -- devel@lists.fedoraproject.org
| To unsubscribe send an email to devel-le...@lists.fedoraproject.org
|
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Copr && Rawhide -- no "rolling updates" workflow

[Vít Ondruch]

Dne 13.10.2016 v 09:37 Neal Gompa napsal(a):
> On Thu, Oct 13, 2016 at 3:11 AM, Michal Novotny  wrote:
>> The description of Kevin is very precise. I am additionally thinking about
>> implementing
>> user option to rebuild all project packages for a new target when added. So
>> when f27 is added, user could click one button to launch rebuild of all his
>> packages
>> for this target.
>>
>> Basically, this allows us to be one-step ahead and serve better as a system
>> for rapid
>> development. Instead of reacting to branching from rawhide to stable, we
>> just consider
>> everything immediately stable. That's because COPR is a collection of
>> relatively small
>> development projects. Projects that currently don't need the same kind of
>> release system
>> as Fedora has.
>>
>> I hope, I am explaining this correctly cause these "high-level" explanations
>> are always
>> a bit fuzzy. For me, the great advantage is that this upgrade alleviates us
>> from launching
>> rawhide_to_release script, which takes all user projects and copies
>> everything from the
>> rawhide targets into the newly branched targets. For me, the alternative of
>> user-invoked
>> explicit rebuilding into a new target when added is much cleaner solution
>> that I can
>> imagine to work well even for projects that do not even have rawhide targets
>> enabled.
>>
> (Sorry about the Mageia spillover, but as I work in both distros and
> this affects both of them...)
>
> I can see the advantages of this, but the COPR plugin for DNF will
> need to be adjusted for this case. It currently treats systems
> detected as "Fedora Rawhide" or "Mageia Cauldron" as a special case
> where it will check for fedora-rawhide-* or mageia-cauldron-* chroots,
> respectively.
>
> If you change it to always be release versions, then this will
> completely break, as there will be no more "rawhide" or "cauldron"
> targets. Instead, we'd have Fedora 26 and Mageia 7 (assuming Cauldron
> has become Mageia 7, which it hasn't yet).
>
> At least from the Fedora point of view, such a change might be
> somewhat painless, since right after branching, we increment the
> release version.

Historically Copr lagged behind after Fedora branching (e.g. after F26
was branched, it too several days until the F25 was enabled in Copr
unless I am mistaken), that would mean that during the mean time, my
Rawhide updates will get broken, since my Fedora will release will be
bumped to 27, but there won't be repositories for F27 on Copr ...

Unless this is handled somehow automatically by infrastructure during
Fedora branching, I don't like this proposal.

Vít

> So the COPR plugin would merely need to have the
> conditional removed and the COPR backend will need to have fake Fedora
> 26 targets that link to the current Rawhide ones.
>

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Copr && Rawhide -- no "rolling updates" workflow

[Neal Gompa]

On Thu, Oct 13, 2016 at 3:11 AM, Michal Novotny  wrote:
> The description of Kevin is very precise. I am additionally thinking about
> implementing
> user option to rebuild all project packages for a new target when added. So
> when f27 is added, user could click one button to launch rebuild of all his
> packages
> for this target.
>
> Basically, this allows us to be one-step ahead and serve better as a system
> for rapid
> development. Instead of reacting to branching from rawhide to stable, we
> just consider
> everything immediately stable. That's because COPR is a collection of
> relatively small
> development projects. Projects that currently don't need the same kind of
> release system
> as Fedora has.
>
> I hope, I am explaining this correctly cause these "high-level" explanations
> are always
> a bit fuzzy. For me, the great advantage is that this upgrade alleviates us
> from launching
> rawhide_to_release script, which takes all user projects and copies
> everything from the
> rawhide targets into the newly branched targets. For me, the alternative of
> user-invoked
> explicit rebuilding into a new target when added is much cleaner solution
> that I can
> imagine to work well even for projects that do not even have rawhide targets
> enabled.
>

(Sorry about the Mageia spillover, but as I work in both distros and
this affects both of them...)

I can see the advantages of this, but the COPR plugin for DNF will
need to be adjusted for this case. It currently treats systems
detected as "Fedora Rawhide" or "Mageia Cauldron" as a special case
where it will check for fedora-rawhide-* or mageia-cauldron-* chroots,
respectively.

If you change it to always be release versions, then this will
completely break, as there will be no more "rawhide" or "cauldron"
targets. Instead, we'd have Fedora 26 and Mageia 7 (assuming Cauldron
has become Mageia 7, which it hasn't yet).

At least from the Fedora point of view, such a change might be
somewhat painless, since right after branching, we increment the
release version. So the COPR plugin would merely need to have the
conditional removed and the COPR backend will need to have fake Fedora
26 targets that link to the current Rawhide ones.

From the Mageia perspective, this is a problem. At this time, the
workflow is to increment the release version for Cauldron only *after*
release, because SVN makes things a bit annoying for juggling more
than one release with a package. A move to Git is in the cards after
Mageia 6 is released, and I suspect after that, we can more-or-less
adopt Fedora's dist-git workflow, which would make such a change less
painful. Thus, right now, Cauldron and Mageia 6 are identical, but
after Mageia 6 releases, that won't be true.

-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: where is /1 coming from?

[Jaroslav Nahorny]

Hi,

Matthew Miller  writes:

> Someone on Reddit noted that there's a zero-length file named `1` in /
> on their F25 system. I just looked on mine, and I have one too. It's
> not owned by any RPM. And I checked on an F24 box, and it's got that
> too. Anyone know where this is coming from?

I see it's fixed now, and it's great. However, funny thing is, I
remember this file being created in root's $HOME (/root/1) around RHEL3
or RHEL4 (not sure if Fedora at that time had it too).

Sorry for off-topic :/

best regards,
-- 
jaroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 6 updates-testing report

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
 462  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031   
python-virtualenv-12.0.7-1.el6
 456  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168   
rubygem-crack-0.3.2-2.el6
 388  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8156   
nagios-4.0.8-1.el6
 346  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb   
mcollective-2.8.4-1.el6
 318  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9   
thttpd-2.25b-24.el6
 204  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-30a8346813   
vtun-3.0.1-10.el6
  63  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-a1450d7fe0   
knot-1.6.8-1.el6
  48  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8594ed3a53   
chicken-4.11.0-3.el6
  21  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-edda50420f   
mongodb-2.4.14-4.el6
  21  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-25e30f6dc3   
jansson-2.9-1.el6
  19  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e8602185c5   
links-2.13-1.el6
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-efb0141e9c   
php-ZendFramework-1.12.20-1.el6
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-63189174a4   
nsd-4.1.13-1.el6
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3428efd3c   
php-symfony-2.3.42-1.el6
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c4b3ba1af6   
nodejs-0.10.47-2.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

keepassx2-2.0.3-1.el6
python-ansible-tower-cli-3.0.1-1.el6
python3-coverage-4.0.3-3.el6
rear-1.19-1.el6
youtube-dl-2016.10.12-1.el6

Details about builds:



 keepassx2-2.0.3-1.el6 (FEDORA-EPEL-2016-5efcdd42c1)
 Cross-platform password manager

Update Information:

2.0.3. https://www.keepassx.org/news/2016/10/609




 python-ansible-tower-cli-3.0.1-1.el6 (FEDORA-EPEL-2016-097c79ae7d)
 A CLI tool for Ansible Tower

Update Information:

New package :)

References:

  [ 1 ] Bug #1370239 - None
https://bugzilla.redhat.com/show_bug.cgi?id=1370239




 python3-coverage-4.0.3-3.el6 (FEDORA-EPEL-2016-1e54b92dfe)
 Code coverage testing module for Python 3

Update Information:

Initial import from epel7 branch




 rear-1.19-1.el6 (FEDORA-EPEL-2016-9fb2383249)
 Relax-and-Recover is a Linux disaster recovery and system migration tool

Update Information:

For a changelog see the rear-release-notes.txt file.




 youtube-dl-2016.10.12-1.el6 (FEDORA-EPEL-2016-506e8c9d15)
 A small command-line program to download online videos

Update Information:

Update to the latest upstream release.

References:

  [ 1 ] Bug #1377102 - None
https://bugzilla.redhat.com/show_bug.cgi?id=1377102

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: Copr && Rawhide -- no "rolling updates" workflow

[Michal Novotny]

The description of Kevin is very precise. I am additionally thinking about
implementing
user option to rebuild all project packages for a new target when added. So
when f27 is added, user could click one button to launch rebuild of all his
packages
for this target.

Basically, this allows us to be one-step ahead and serve better as a system
for rapid
development. Instead of reacting to branching from rawhide to stable, we
just consider
everything immediately stable. That's because COPR is a collection of
relatively small
development projects. Projects that currently don't need the same kind of
release system
as Fedora has.

I hope, I am explaining this correctly cause these "high-level"
explanations are always
a bit fuzzy. For me, the great advantage is that this upgrade alleviates us
from launching
rawhide_to_release script, which takes all user projects and copies
everything from the
rawhide targets into the newly branched targets. For me, the alternative of
user-invoked
explicit rebuilding into a new target when added is much cleaner solution
that I can
imagine to work well even for projects that do not even have rawhide
targets enabled.

clime

On Wed, Oct 12, 2016 at 9:11 PM, Kevin Fenzi  wrote:

> On Tue, 11 Oct 2016 19:14:34 +0200
> Pavel Raiskup  wrote:
>
> > FYI:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1381790
> >
> > Seems like the `fedora-rawhide-x86_64` chroot is not going to exist
> > from now, which is IMO unnecessary change ... but what could be other
> > than those "obvious" consequences for both Copr repo maintainers and
> > users? Does this sound like acceptable change?
>
> Well, its a bit confusing actually, but if I understand it right I
> guess it should be ok.
>
> My understanding is that there will no longer be a 'rawhide'
> target/repos. Instead right now they will all become 'f26' ones. Then,
> when we branch f26, those will follow the branch and new f27 ones will
> appear.
>
> Whats not at all clear is when/if there's going to be any mass adding
> the new branch and rebuilding on it, or if that is up to the user?
>
> Personally, I would say we shouldn't do any mass rebuilding.
> If a project gets to the point where it has no builds for any active
> targets we could move it to a 'archive' or just delete it as it would
> indicate no one is driving/caring for the software.
>
> kevin
>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[EPEL-devel] Fedora EPEL 5 updates-testing report

[updates]

The following Fedora EPEL 5 Security updates need testing:
 Age  URL
 854  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626   
puppet-2.7.26-1.el5
 703  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849   
sblim-sfcb-1.3.8-2.el5
 346  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-edbea40516   
mcollective-2.8.4-1.el5
 318  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-582c8075e6   
thttpd-2.25b-24.el5
  14  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-803d3bfa1a   
openssl101e-1.0.1e-9.el5
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c9c041384d   
c-ares-1.12.0-1.el5
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b78def3304   
perl-Image-Info-1.38-6.el5


The following builds have been pushed to Fedora EPEL 5 updates-testing

rear-1.19-1.el5

Details about builds:



 rear-1.19-1.el5 (FEDORA-EPEL-2016-81c74f4660)
 Relax-and-Recover is a Linux disaster recovery and system migration tool

Update Information:

For a changelog see the rear-release-notes.txt file.

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

[Adam Williamson]

On Thu, 2016-10-13 at 14:40 +1000, Jeff Fearn wrote:
> On 13/10/16 14:02, Adam Williamson wrote:
> > On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote:
> > > On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson
> > >  wrote:
> > > > On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote:
> > > > > All of the extra app stuff could be avoided if we disallowed reporters
> > > > > (or random people) to change the Severity and Priority fields.
> > > > 
> > > > Mmm, I don't really think so. Presumably it would be maintainers who
> > > > got to set those fields, right? But they are doing so in relation to
> > > 
> > > No, why would you presume that?
> > 
> > I dunno, just seemed logical. That's how they're intended to be used at
> > present. Bug reporters aren't supposed to set them and don't have the
> > privilege purely by rights of having an account
> 
> This is true for priority but not true for severity. Severity is the
> external, i.e. reporters, weighting
> of the bug and you do not need to be in editbugs to set it.

That's not the intent of the fields as I understand them. 'severity' is
supposed to represent how bad the bug is, whereas 'priority' is
supposed to represent how important it is to get it fixed compared to
other bugs in the same component. They're obviously related, but not
the same, and it's not "severity is the reporter's opinion, priority is
the maintainers' opinion", no.

I think you might be right that we allow the bug reporter to set
'severity', though.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Where is /null coming from [was Re: where is /1 coming from?]

[Ralf Corsepius]

On 10/13/2016 01:03 AM, Matthew Miller wrote:

On Wed, Oct 12, 2016 at 04:39:18PM +0200, Björn Esser wrote:

Additionally I see a file called /null with zero length!

Same finding (/null) for me, too.


Yup. Okay, let's try this again. :)



FWIW: It seems to be created at each boot.

Ralf
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org