jplesnik pushed to perl-Ref-Util-XS (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-29 05:57:03 UTC

From 374319de2ac26b6fac512dc6c56eef8af2dce237 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 29 2018 05:56:58 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Ref-Util-XS.spec b/perl-Ref-Util-XS.spec
index 2c92e86..17e201a 100644
--- a/perl-Ref-Util-XS.spec
+++ b/perl-Ref-Util-XS.spec
@@ -7,7 +7,7 @@
 
 Name:  perl-Ref-Util-XS
 Version:   0.117
-Release:   2%{?dist}
+Release:   3%{?dist}
 Summary:   Utility functions for checking references
 License:   MIT
 URL:   https://metacpan.org/release/Ref-Util-XS
@@ -70,6 +70,9 @@ make test
 %{_mandir}/man3/Ref::Util::XS.3*
 
 %changelog
+* Fri Jun 29 2018 Jitka Plesnikova  - 0.117-3
+- Perl 5.28 rebuild
+
 * Fri Feb 09 2018 Fedora Release Engineering  - 
0.117-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Ref-Util-XS/c/374319de2ac26b6fac512dc6c56eef8af2dce237?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/EUK6FFO5V2LFXMA76NQKY4IPNMO34NQF/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Tomasz Torcz 
On Thu, Jun 28, 2018 at 05:49:39PM -0400, Matthew Miller wrote:
> On Thu, Jun 28, 2018 at 02:37:07PM -0700, Gerald B. Cox wrote:
> > If we're keeping both commands, I don't really care - but to make
> > sure I'm understanding this, we're proposing to eliminate the yum
> > code, create a symlink for yum pointing to dnf and then change our
> > documentation to no longer reference dnf - only reference yum?
> 
> That's my suggestion, although "no longer reference dnf" is a bit
> strong. We'd use `yum` as the standard command in documentation about
> package management, but detailed documentation would talk about "yum
> powered by dnf".

  After half a decade of using dnf? It's aready ingrained in my muscle
memory and some of my ansible scripts.  Flipping the name of most
important command every few years is really counter-productive, yum→dnf
transition was painful enough. I'm against inflicting such self-harm
again.

-- 
Tomasz TorczThere exists no separation between gods and men:
xmpp: zdzich...@chrome.pl   one blends softly casual into the other.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZK5U46K7N5SBG45YW4ZQ4JZLWZLIVZGO/

jplesnik pushed to perl-Cookie-Baker (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-29 05:33:06 UTC

From a429c934fc6670374c289d159d32c0e83eee5f48 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 29 2018 05:33:03 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Cookie-Baker.spec b/perl-Cookie-Baker.spec
index 0436c84..5aa8615 100644
--- a/perl-Cookie-Baker.spec
+++ b/perl-Cookie-Baker.spec
@@ -1,6 +1,6 @@
 Name:   perl-Cookie-Baker
 Version:0.09
-Release:1%{?dist}
+Release:2%{?dist}
 Summary:Cookie string generator / parser
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Cookie-Baker
@@ -50,6 +50,9 @@ Cookie::Baker provides simple cookie string generator and 
parser.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Jun 29 2018 Jitka Plesnikova  - 0.09-2
+- Perl 5.28 rebuild
+
 * Sun Mar 04 2018 Ralf Corsépius  - 0.09-1
 - Update to 0.09.
 - Spec file cosmetics.



https://src.fedoraproject.org/rpms/perl-Cookie-Baker/c/a429c934fc6670374c289d159d32c0e83eee5f48?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/2FCLYHGLLJY6TBLKP5DBUU5KYCMNO35P/

[389-devel] 389 DS nightly 2018-06-29 - 73% PASS

2018-06-28 Thread vashirov 
https://fedorapeople.org/groups/389ds/ci/nightly/2018/06/29/report-389-ds-base-1.4.0.11-20180628git08b2d88.fc28.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org/message/KSZZXKPTLQABQSHRGENIQJNVOKDN26MA/

Re: new package built, now what?

2018-06-28 Thread Alois Mahdal 


On 06/28/2018 11:43 PM, Alois Mahdal wrote:
> Hi,
> 
> so I'm following "Join the package collection maintainers", I'm at the
> late phase when I've submitted new package, ran `fedpkg build` from
> master, koji is happy, etc.
> 
> 
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Import.2C_commit.2C_and_build_your_package
> 
> Now I tried to just follow with "Update Your Branches (if desired)", but
> that fails, because F27 and F28 branches don't exist -- OTOH I don't
> expect them to spawn from nowhere; both versions are already released,
> so I wonder if it's even possible to add new ones.
> 
> So what should I do?  Just forget about F27/F28 and wait for F29?  Do
> [something] to have the F27/28 branches created?

Thanks for all the replies.  My newpkg updates are already in bodhi! :-)


> And should the guide be updated?  (It seems that this will happen to
> every new package)

Seems like it should.  Filed as BZ#1596438.

aL.

-- 
Alois Mahdal 
Platform QE Engineer at Red Hat, Inc.
#brno, #daemons, #preupgrade
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ND74BZHQDCI2XOQLHZVLZEE6LEY6RVQB/

Re: Semi-orphaning pysvn

2018-06-28 Thread Jonathan Wakely 

On 28/06/18 14:09 -0600, Jerry James wrote:

On Thu, Jun 28, 2018 at 1:25 PM Stephen Gallagher  wrote:

I've been keeping the lights on in this package for years since the maintainer 
(ravenoak) vanished from Fedora. However, it doesn't build against Python 3.7 
(works fine with 3.6) and I don't have the cycles to dig into it.

If someone steps up to fix the FTBFS, I'm willing to hang on as a comaintainer, 
but if no one does, I'm going to orphan it completely in about a week.


The bug is not in pysvn.  It is in python-pycxx.  From the build log:

/usr/src/CXX/IndirectPythonInterface.cxx: In function 'char*
Py::__Py_PackageContext()':
/usr/src/CXX/IndirectPythonInterface.cxx:471:50: error: invalid
conversion from 'const char*' to 'char*' [-fpermissive]
char *__Py_PackageContext() { return _Py_PackageContext; }
 ^~
make: *** [Makefile:170: IndirectPythonInterface.o] Error 1


That declaration should be:

const char *__Py_PackageContext() { return _Py_PackageContext; }


I think Boost.Python needed a similar change to build with Python 3.7


Either patch python-pycxx to add the missing "const" or build pysvn
with -fpermissive.


Please fix the code, don't use -fpermissive (it turns off loads of
rules in the C++ compiler, so is a sledgehammer to crack a nut).


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/S33D3FSQRX6QQZLNRCLPO6FEQ6TQRPES/

[Bug 1596422] New: perl-Carton-v1.0.34 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1596422

Bug ID: 1596422
   Summary: perl-Carton-v1.0.34 is available
   Product: Fedora
   Version: rawhide
 Component: perl-Carton
  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: v1.0.34
Current version/release in rawhide: 1.0.33-1.fc29
URL: http://search.cpan.org/dist/Carton/

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/8357/

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/TATYYJSDJKNAV3XWOYSTODJAQ3B3H7B7/

Re: Your package doesn't build with Python 3.7

2018-06-28 Thread Sérgio Basto 
On Thu, 2018-06-28 at 20:41 +0200, Miro Hrončok wrote:
> sergiomb   opencv

/builddir/build/BUILD/opencv-3.4.1/modules/python/src2/cv2.cpp:889:34:
error: invalid conversion from 'const char*' to 'char*' [-fpermissive]
 char* str = PyString_AsString(obj);

This problem is not about new gcc flags ? or about python rebuild ? now
that I'm reading if I just add const to the code [1] will fix this
build error ?
original code here [2]

[1]
const char* str = PyString_AsString(obj); 

 
[2] 
https://github.com/opencv/opencv/blob/master/modules/python/src2/cv2.cp
p#L919

Thanks,
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SCRTZW2ERRXTBK7M3LTKRYXRQ5DFSGBS/

jplesnik pushed to perl-Test2-Plugin-NoWarnings (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 22:26:37 UTC

From 9421dcb48ec50d9546c084c5894dcdde6a853e97 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 22:26:35 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Test2-Plugin-NoWarnings.spec 
b/perl-Test2-Plugin-NoWarnings.spec
index 024e6cc..bb11c87 100644
--- a/perl-Test2-Plugin-NoWarnings.spec
+++ b/perl-Test2-Plugin-NoWarnings.spec
@@ -1,6 +1,6 @@
 Name:  perl-Test2-Plugin-NoWarnings
 Version:   0.06
-Release:   3%{?dist}
+Release:   4%{?dist}
 Summary:   Fail if tests warn
 License:   Artistic 2.0
 URL:   https://metacpan.org/release/Test2-Plugin-NoWarnings
@@ -62,6 +62,9 @@ make test
 %{_mandir}/man3/Test2::Plugin::NoWarnings.3*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.06-4
+- Perl 5.28 rebuild
+
 * Fri Feb 09 2018 Fedora Release Engineering  - 
0.06-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Test2-Plugin-NoWarnings/c/9421dcb48ec50d9546c084c5894dcdde6a853e97?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/VGOQ2NW745WZDTQEVSQMEVEHVMYIA6Y4/

jplesnik pushed to perl-List-MoreUtils-XS (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 22:09:59 UTC

From 5a25c830016459458aa04ac7d2a7de029c23009e Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 22:09:57 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-List-MoreUtils-XS.spec b/perl-List-MoreUtils-XS.spec
index 07c14ed..8d4cad7 100644
--- a/perl-List-MoreUtils-XS.spec
+++ b/perl-List-MoreUtils-XS.spec
@@ -1,6 +1,6 @@
 Name:  perl-List-MoreUtils-XS
 Version:   0.428
-Release:   2%{?dist}
+Release:   3%{?dist}
 Summary:   Provide compiled List::MoreUtils functions
 # Code from List-MoreUtils < 0.417 is GPL+ or Artistic
 # Anything after that is ASL 2.0
@@ -78,6 +78,9 @@ make test
 %{_mandir}/man3/List::MoreUtils::XS.3*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.428-3
+- Perl 5.28 rebuild
+
 * Thu Feb 08 2018 Fedora Release Engineering  - 
0.428-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-List-MoreUtils-XS/c/5a25c830016459458aa04ac7d2a7de029c23009e?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/6P2GUCKY6EX4CTJMKJRWP6T5SAB5UJZM/

Re: new package built, now what?

2018-06-28 Thread Adam Williamson 
On Thu, 2018-06-28 at 18:13 -0400, Matthew Miller wrote:
> On Thu, Jun 28, 2018 at 05:58:55PM -0400, Christopher wrote:
> > Maybe run the following? Not sure. Hard to find docs on this.
> > fedpkg request-branch f28
> 
> Documented here:
> 
> https://fedoraproject.org/wiki/Changes/fedrepo-req-to-fedpkg

No it isn't. A Change page is not documentation. It's essentially a
transient thing that documents the Change itself for the purpose of the
Change process.

If this is a permanent step in a permanent packager process it should
be documented in the actual documentation of that packager process.
-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JGBIFE72TEZPSOH4VZXLU2D4MK34ASTH/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok 



On 28.6.2018 15:42, Miro Hrončok wrote:

The Python 3.7 rebuild in the f29-python side tag is currently:

  - 2168 built
  - ~170 FTBFS
  - ~120 blocked by dependencies that FTBFS

Ideally, this would all get fixed before the merge, but that's 
unrealistic, there are packages that are FTBFS for unrelated reasons, etc.


What is the criterion to merge the side tag?


OK. I'll ask releng to merge on Monday.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org/message/PPAFZORSNKSKNBCQ4RLRFKOJPDEK5ZQM/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok 



On 28.6.2018 15:42, Miro Hrončok wrote:

The Python 3.7 rebuild in the f29-python side tag is currently:

  - 2168 built
  - ~170 FTBFS
  - ~120 blocked by dependencies that FTBFS

Ideally, this would all get fixed before the merge, but that's 
unrealistic, there are packages that are FTBFS for unrelated reasons, etc.


What is the criterion to merge the side tag?


OK. I'll ask releng to merge on Monday.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PPAFZORSNKSKNBCQ4RLRFKOJPDEK5ZQM/

Re: new package built, now what?

2018-06-28 Thread Matthew Miller 
On Thu, Jun 28, 2018 at 05:58:55PM -0400, Christopher wrote:
> Maybe run the following? Not sure. Hard to find docs on this.
> fedpkg request-branch f28

Documented here:

https://fedoraproject.org/wiki/Changes/fedrepo-req-to-fedpkg


-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PEVQHKOIMII5IONSGSLPEV6DD6B3Q4IQ/

dbxtool service errors (was: Re: F29 System Wide Change: Hide the grub menu)

2018-06-28 Thread Dominik 'Rathann' Mierzejewski 
Hello, Gerald.
Sorry for late reply, I managed to catch up with this thread only now.

On Wednesday, 20 June 2018 at 18:01, Gerald B. Cox wrote:
> On Wed, Jun 20, 2018 at 4:56 AM, Dominik 'Rathann' Mierzejewski <
> domi...@greysector.net> wrote:
> > On Wednesday, 20 June 2018 at 07:54, Gerald B. Cox wrote:
> > [...]
> > > The dbxtool.service message is associated with rhbz#1508808
> >
> > Thanks to this, I checked my machine and filed:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1593258
> > because I'm seeing a different variation of yours.
> 
> Actually, that is the error I am receiving... is your SecureBoot enabled or
> disabled?
> 
> You can check by:  mokutil --sb-state

It's enabled and mokutil confirms it:
$ mokutil --sb-state
SecureBoot enabled

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPMFusion   http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/J5NKNIZNY5Z7RAW24UGIHKIG3574YQM7/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Kalev Lember 

On 06/28/2018 03:42 PM, Miro Hrončok wrote:

The Python 3.7 rebuild in the f29-python side tag is currently:

  - 2168 built
  - ~170 FTBFS
  - ~120 blocked by dependencies that FTBFS

Ideally, this would all get fixed before the merge, but that's 
unrealistic, there are packages that are FTBFS for unrelated reasons, etc.


What is the criterion to merge the side tag?

The critpath installs fine (except stuff that cannot be installed due to 
yum-deprecated vs yum collisions and gnome-software that has some broken 
dependency on PackageKit).


Stuff that doesn't build and sounds important:

  - ceph (also FTBFS in regular rawhide)
  - libreoffice (also FTBFS in regular rawhide)
  - orca (blocked by pyatspi, looking at it ATM)
  - kernel-tools


I think it's fine to merge this with some broken dependencies remaining.
I would concentrate on getting those builds fixed that are in the
default install (Server, Workstation), with the goal being to keep
nightly composes working.

After that, I'd merge it immediately and continue the rebuilds in
rawhide proper.

Side tags that have a lot of packages start quickly diverging from
rawhide when people do regular rawhide updates and I think it's least
painful to aggressively merge this back to rawhide once it's good enough
(doesn't break default install composes).

Kalev
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K7RFXAIUY7WN32PUSUL4SOE4MJMH3NNQ/

Re: new package built, now what?

2018-06-28 Thread Robert-André Mauchin 
On jeudi 28 juin 2018 23:43:09 CEST Alois Mahdal wrote:
> Hi,
> 
> so I'm following "Join the package collection maintainers", I'm at the
> late phase when I've submitted new package, ran `fedpkg build` from
> master, koji is happy, etc.
> 
> 
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=Pa
> ckageMaintainers/Join#Import.2C_commit.2C_and_build_your_package
 
> Now I tried to just follow with "Update Your Branches (if desired)", but
> that fails, because F27 and F28 branches don't exist -- OTOH I don't
> expect them to spawn from nowhere; both versions are already released,
> so I wonder if it's even possible to add new ones.
> 
> So what should I do?  Just forget about F27/F28 and wait for F29?  Do
> [something] to have the F27/28 branches created?
> 
> And should the guide be updated?  (It seems that this will happen to
> every new package)
> 
> 
> Thanks,
> aL.
> 
> PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
> "jump through these hoops", I'm asking because I want to notify upstream
> yet I kinda don't know what can I tell them. :D
> 
> 
You can request new branches just after requesting your repo:

fedpkg --module-name ydiff request-branch f28
fedpkg --module-name ydiff request-branch f27

fedpkg --module-name slop request-branch f28
fedpkg --module-name slop request-branch f27

(You can omit --module-name if you running the command from within the already 
created GIT repo).

Then wait for Gwyn to do her magic.

Afterwards you can:

 1. git pull to get the new branches
 2. fedpkg switch-branch f28
 3. git merge master
 4. fedpkg push
 5. fedpkg build
 6. fedpkg update

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/F7FISMPJ4C2GFTXE34BJEUZLEUVOHNGR/

Re: new package built, now what?

2018-06-28 Thread Christopher 
Maybe run the following? Not sure. Hard to find docs on this.
fedpkg request-branch f28


On Thu, Jun 28, 2018 at 5:51 PM Alois Mahdal  wrote:

> Hi,
>
> so I'm following "Join the package collection maintainers", I'm at the
> late phase when I've submitted new package, ran `fedpkg build` from
> master, koji is happy, etc.
>
>
>
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Import.2C_commit.2C_and_build_your_package
>
> Now I tried to just follow with "Update Your Branches (if desired)", but
> that fails, because F27 and F28 branches don't exist -- OTOH I don't
> expect them to spawn from nowhere; both versions are already released,
> so I wonder if it's even possible to add new ones.
>
> So what should I do?  Just forget about F27/F28 and wait for F29?  Do
> [something] to have the F27/28 branches created?
>
> And should the guide be updated?  (It seems that this will happen to
> every new package)
>
>
> Thanks,
> aL.
>
> PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
> "jump through these hoops", I'm asking because I want to notify upstream
> yet I kinda don't know what can I tell them. :D
>
>
> --
> Alois Mahdal 
> Platform QE Engineer at Red Hat, Inc.
> #brno, #daemons, #preupgrade
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/I6A2VMIUPT2VVS3VAENF5MYOUYYXLE54/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/76TYAEGHE5GFYTICPHUT6RSEMQO5FW6A/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Matthew Miller 
On Thu, Jun 28, 2018 at 02:37:07PM -0700, Gerald B. Cox wrote:
> If we're keeping both commands, I don't really care - but to make
> sure I'm understanding this, we're proposing to eliminate the yum
> code, create a symlink for yum pointing to dnf and then change our
> documentation to no longer reference dnf - only reference yum?

That's my suggestion, although "no longer reference dnf" is a bit
strong. We'd use `yum` as the standard command in documentation about
package management, but detailed documentation would talk about "yum
powered by dnf".





-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/P5HCL3L2C7ACWXUFD27THEKJ6WLUTRY5/

new package built, now what?

2018-06-28 Thread Alois Mahdal 
Hi,

so I'm following "Join the package collection maintainers", I'm at the
late phase when I've submitted new package, ran `fedpkg build` from
master, koji is happy, etc.


https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join#Import.2C_commit.2C_and_build_your_package

Now I tried to just follow with "Update Your Branches (if desired)", but
that fails, because F27 and F28 branches don't exist -- OTOH I don't
expect them to spawn from nowhere; both versions are already released,
so I wonder if it's even possible to add new ones.

So what should I do?  Just forget about F27/F28 and wait for F29?  Do
[something] to have the F27/28 branches created?

And should the guide be updated?  (It seems that this will happen to
every new package)


Thanks,
aL.

PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
"jump through these hoops", I'm asking because I want to notify upstream
yet I kinda don't know what can I tell them. :D


-- 
Alois Mahdal 
Platform QE Engineer at Red Hat, Inc.
#brno, #daemons, #preupgrade
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/I6A2VMIUPT2VVS3VAENF5MYOUYYXLE54/

jplesnik pushed to perl-Net-LDAP-Server-Test (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 20:50:41 UTC

From 53ca6ae67fa002a601d1b5813506e20a3ab0da9c Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 20:50:35 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Net-LDAP-Server-Test.spec b/perl-Net-LDAP-Server-Test.spec
index 6c8df88..1e97b08 100644
--- a/perl-Net-LDAP-Server-Test.spec
+++ b/perl-Net-LDAP-Server-Test.spec
@@ -1,6 +1,6 @@
 Name:   perl-Net-LDAP-Server-Test
 Version:0.22
-Release:5%{?dist}
+Release:6%{?dist}
 Summary:Test Net::LDAP code
 License:GPL+ or Artistic
 Group:  Development/Libraries
@@ -69,6 +69,9 @@ Test your Net::LDAP code without having a real LDAP server 
available.
 %{_mandir}/man3/*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.22-6
+- Perl 5.28 rebuild
+
 * Thu Feb 08 2018 Fedora Release Engineering  - 
0.22-5
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Net-LDAP-Server-Test/c/53ca6ae67fa002a601d1b5813506e20a3ab0da9c?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/7EB72UQIAYR3FYT4ZIG6HSY4AWO3475G/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Gerald B. Cox 
On Thu, Jun 28, 2018 at 2:17 PM, Matthew Miller 
wrote:

> On Thu, Jun 28, 2018 at 03:45:06PM -0400, Przemek Klosowski wrote:
> > To tie two recent devel list threads, this is a perfect use case for
> > a ~/bin being first in PATH: a ~/bin/yum -> /bin/dnf symlink for
> > those that don't want to rewrite scripts.
>
> As I understand it, regardless of which one we decide to document and
> market as primary, the plan is for the package to include that symlink
> and for both commands to just work identically.
>
> If we're keeping both commands, I don't really care - but to make sure I'm
understanding this,
we're proposing to eliminate the yum code, create a symlink for yum
pointing to dnf and then
change our documentation to no longer reference dnf - only reference yum?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/IDWJKPX636VAUBFJUHZMNGZBDCSWFXPW/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Matthew Miller 
On Thu, Jun 28, 2018 at 03:45:06PM -0400, Przemek Klosowski wrote:
> To tie two recent devel list threads, this is a perfect use case for
> a ~/bin being first in PATH: a ~/bin/yum -> /bin/dnf symlink for
> those that don't want to rewrite scripts.

As I understand it, regardless of which one we decide to document and
market as primary, the plan is for the package to include that symlink
and for both commands to just work identically.

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/B454OYKORMUFY4WBFI4FCSG465F7ZJYX/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Kalev Lember 

On 06/28/2018 08:51 PM, Matthew Miller wrote:

On Wed, Jun 27, 2018 at 01:29:41PM -0700, Adam Williamson wrote:

But in Fedora land, we've spent several years selling the message "yum
is gone and replaced with this new thing called dnf". It would be
rather confusing to suddenly start selling the message "oh hey yum is
back only now it's sort of dnf but sort of not dnf".


When FESCo decided to approve that change to the original plan, this
was noted as a potential risk. I personally think that staying aligned
with the rest of the RH distro ecosystem is worth some inconvenience.
It'll make it easier to share and collaborate on documentation and
other help.


I am no longer on FESCo, but I strongly support Matthew's message here,
for what it's worth.

--
Kalev
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/Q3EC3EAR6MVSZIN236J45RGOBWQRNQS5/

Planned Outage: PHX2 services down/disrupted 2018-07-03 21:00 UTC

2018-06-28 Thread Stephen John Smoogen 
There will be an outage starting at 2018-07-03 21:00UTC, which will
last approximately 6 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto

or run:

date -d '2018-07-03 21:00UTC'

Reason for outage:

There have been a set up of updates for EL7 and Fedora requiring
reboots of infrastructure. We will be rebooting the Build and remote
systems outside of PHX2 on this day.

Affected Services:

Various web services housed in PHX2 may be up or down during the
outage window. This will affect builds and authentication for short
periods of time.

Contact Information:

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7065

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.
-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DFMLJW6R3IFLKGOCXPCZ324QAM2RLFFX/

ICU4J License Change notification

2018-06-28 Thread Mat Booth 
ICU4J is now covered by the Unicode License (with MIT and BSD licensed
contributed parts.)

The Unicode license is very similar to the previous MIT-style ICU license.

-- 
Mat Booth
http://fedoraproject.org/get-fedora
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/message/MITQQDMOAEO7SHSMPOGUSQ7QYLM3B5WK/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MITQQDMOAEO7SHSMPOGUSQ7QYLM3B5WK/

ICU4J License Change notification

2018-06-28 Thread Mat Booth 
ICU4J is now covered by the Unicode License (with MIT and BSD licensed
contributed parts.)

The Unicode license is very similar to the previous MIT-style ICU license.

-- 
Mat Booth
http://fedoraproject.org/get-fedora
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/MITQQDMOAEO7SHSMPOGUSQ7QYLM3B5WK/

Planned Outage: Build, cloud and web proxy service down/disrupted 2018-07-02 21:00 UTC

2018-06-28 Thread Stephen John Smoogen 
There will be an outage starting at 2018-07-02 21:00UTC, which will
last approximately 4 hours.

To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto

or run:

date -d '2018-07-02 21:00UTC'

Reason for outage:

There have been a set up of updates for EL7 and Fedora requiring
reboots of infrastructure. We will be rebooting the Build and remote
systems outside of PHX2 on this day.

Affected Services:

All build and cloud services may be up or down during the outage
window. Various proxies will not be available and fedorapeople will be
down also.

Contact Information:

Ticket Link:

https://pagure.io/fedora-infrastructure/issue/7064

Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.




-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/D2V6JED6H7Y3575ZRP4OCXR5JGRRHNWC/

Re: Heads up: Python 3.7 rebuild in progress

2018-06-28 Thread Robert-André Mauchin 
On jeudi 28 juin 2018 22:05:36 CEST Antonio Trande wrote:
> Does anyone know how to fix 'antimony'?
> https://bugzilla.redhat.com/show_bug.cgi?id=1594496
> 
> Reply from upstream is delayed...
> 
> On 28/06/2018 20:41, Miro Hrončok wrote:
> > This is a reminder that your package FTBFS with Python 3.7. Please fix
> > it. We'd like to merge the side tag soon and your package will likely
> > get broken deps afterwards. Chances are your package blocks others.
> > 
> > If nothing depends on your package and upstream is dead, consider
> > removing it.
> > 
> > Rebuild your package with: fedpkg build --target=f29-python
> > 
> > The list:
> > Maintainers by package:
> > 
> > sagitter   antimony
PyUnicode_AsUTF8 return type was char* in 3.6:
https://docs.python.org/3.6/c-api/unicode.html#c.PyUnicode_AsUTF8

but became const char* in 3.7:
https://docs.python.org/3.7/c-api/unicode.html#c.PyUnicode_AsUTF8

Thus you should probably patch https://github.com/mkeeter/antimony/blob/
master/lib/graph/src/util.cpp#L50 by transforming "char* c" into 
"const char* c"

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/COPKAWVLS5QTEJEL7ZDV7AQU7F3CX7B3/

Re: Heads up: Python 3.7 rebuild in progress

2018-06-28 Thread Jerry James 
On Thu, Jun 28, 2018 at 2:06 PM Antonio Trande  wrote:
> Does anyone know how to fix 'antimony'?
> https://bugzilla.redhat.com/show_bug.cgi?id=1594496

The code has 2 problems.  One is simply a missing "const" keyword,
easy to fix.  The other problem is that the Qt authors apparently
thought it was a good idea to make a common word, "slots", be a macro.
Since there is a structure element in the python headers with the name
slots, bad things happen.  Try the attached patch.  It is slightly
horrible, but should fix the build.  And please slap any developer
near you who tries to #define a short word like that.

(I recently had to help a bunch of upstreams cope with the #define
iszero that the latest revision of the C standard required to be added
to math.h.  Guess what?  People had already used "iszero" as a
function or method name, many times, and not synonymously with the
meaning of the C standard macro, either.)
-- 
Jerry James
http://www.jamezone.org/
--- app/viewport/render/instance.h.orig	2016-11-27 19:16:48.0 -0700
+++ app/viewport/render/instance.h	2018-06-28 14:44:06.985669560 -0600
@@ -1,6 +1,8 @@
 #pragma once
 
+#undef slots
 #include 
+#define slots Q_SLOTS
 #include 
 
 #include "viewport/image.h"
--- lib/graph/src/util.cpp.orig	2016-11-27 19:16:48.0 -0700
+++ lib/graph/src/util.cpp	2018-06-28 14:19:57.332549621 -0600
@@ -47,7 +47,7 @@ std::pair getPyError()
 error_traceback = "";
 for (int i=0; i < PyList_Size(lst); ++i)
 {
-char* c = PyUnicode_AsUTF8(PyList_GetItem(lst, i));
+const char* c = PyUnicode_AsUTF8(PyList_GetItem(lst, i));
 assert(!PyErr_Occurred());
 error_traceback += std::string(c);
 }
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WFFFBMSKMU27FSHJLAKQJZMRJ5VGVPGK/

jplesnik pushed to perl-Net-LDAP-Server (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 20:18:09 UTC

From 3246659a85d9081f4cc0fd4202a216c2da504817 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 20:18:05 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Net-LDAP-Server.spec b/perl-Net-LDAP-Server.spec
index 24f05e1..97b5bf2 100644
--- a/perl-Net-LDAP-Server.spec
+++ b/perl-Net-LDAP-Server.spec
@@ -1,6 +1,6 @@
 Name:   perl-Net-LDAP-Server
 Version:0.43
-Release:6%{?dist}
+Release:7%{?dist}
 Summary:Net::LDAP::Server Perl module
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Net-LDAP-Server
@@ -59,6 +59,9 @@ connection with the client.
 %{_mandir}/man3/*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.43-7
+- Perl 5.28 rebuild
+
 * Thu Feb 08 2018 Fedora Release Engineering  - 
0.43-6
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Net-LDAP-Server/c/3246659a85d9081f4cc0fd4202a216c2da504817?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/RHO4LZIPPZWK2MHJBZO5XBE23O4KBQ5F/

Re: Semi-orphaning pysvn

2018-06-28 Thread Stephen Gallagher 
CCing the maintainers of pyCXX.

On Thu, Jun 28, 2018 at 4:10 PM Jerry James  wrote:

> On Thu, Jun 28, 2018 at 1:25 PM Stephen Gallagher 
> wrote:
> > I've been keeping the lights on in this package for years since the
> maintainer (ravenoak) vanished from Fedora. However, it doesn't build
> against Python 3.7 (works fine with 3.6) and I don't have the cycles to dig
> into it.
> >
> > If someone steps up to fix the FTBFS, I'm willing to hang on as a
> comaintainer, but if no one does, I'm going to orphan it completely in
> about a week.
>
> The bug is not in pysvn.  It is in python-pycxx.  From the build log:
>
> /usr/src/CXX/IndirectPythonInterface.cxx: In function 'char*
> Py::__Py_PackageContext()':
> /usr/src/CXX/IndirectPythonInterface.cxx:471:50: error: invalid
> conversion from 'const char*' to 'char*' [-fpermissive]
>  char *__Py_PackageContext() { return _Py_PackageContext; }
>   ^~
> make: *** [Makefile:170: IndirectPythonInterface.o] Error 1
>
>
> That declaration should be:
>
> const char *__Py_PackageContext() { return _Py_PackageContext;
> }
>
> Either patch python-pycxx to add the missing "const" or build pysvn
> with -fpermissive.
>
> Incidentally, the two sed expressions in %build are wrong.  They don't
> match anything, and therefore don't change anything.  Change them both
> to this:
>
> %{__sed} -i -e 's@-fexceptions -frtti@%{optflags} -frtti@' Makefile
>
> or, if you want to go the -fpermissive route, to this:
>
> %{__sed} -i -e 's@-fexceptions -frtti@%{optflags} -frtti -fpermissive@'
> Makefile
>
> Regards,
> --
> Jerry James
> http://www.jamezone.org/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZALDNFOZO6DLRXOS6J7EA7WFHMGE3UAF/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/IU5BXDLUBTMWM6732PGRHBEGSZU5ISMM/

Re: Semi-orphaning pysvn

2018-06-28 Thread Jerry James 
On Thu, Jun 28, 2018 at 1:25 PM Stephen Gallagher  wrote:
> I've been keeping the lights on in this package for years since the 
> maintainer (ravenoak) vanished from Fedora. However, it doesn't build against 
> Python 3.7 (works fine with 3.6) and I don't have the cycles to dig into it.
>
> If someone steps up to fix the FTBFS, I'm willing to hang on as a 
> comaintainer, but if no one does, I'm going to orphan it completely in about 
> a week.

The bug is not in pysvn.  It is in python-pycxx.  From the build log:

/usr/src/CXX/IndirectPythonInterface.cxx: In function 'char*
Py::__Py_PackageContext()':
/usr/src/CXX/IndirectPythonInterface.cxx:471:50: error: invalid
conversion from 'const char*' to 'char*' [-fpermissive]
 char *__Py_PackageContext() { return _Py_PackageContext; }
  ^~
make: *** [Makefile:170: IndirectPythonInterface.o] Error 1


That declaration should be:

const char *__Py_PackageContext() { return _Py_PackageContext; }

Either patch python-pycxx to add the missing "const" or build pysvn
with -fpermissive.

Incidentally, the two sed expressions in %build are wrong.  They don't
match anything, and therefore don't change anything.  Change them both
to this:

%{__sed} -i -e 's@-fexceptions -frtti@%{optflags} -frtti@' Makefile

or, if you want to go the -fpermissive route, to this:

%{__sed} -i -e 's@-fexceptions -frtti@%{optflags} -frtti -fpermissive@' Makefile

Regards,
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZALDNFOZO6DLRXOS6J7EA7WFHMGE3UAF/

Heads up: Python 3.7 rebuild in progress

2018-06-28 Thread Antonio Trande 
Does anyone know how to fix 'antimony'?
https://bugzilla.redhat.com/show_bug.cgi?id=1594496

Reply from upstream is delayed...

On 28/06/2018 20:41, Miro Hrončok wrote:
> This is a reminder that your package FTBFS with Python 3.7. Please fix
> it. We'd like to merge the side tag soon and your package will likely
> get broken deps afterwards. Chances are your package blocks others.
> 
> If nothing depends on your package and upstream is dead, consider
> removing it.
> 
> Rebuild your package with: fedpkg build --target=f29-python
> 
> The list:
> Maintainers by package:
> 
> sagitter   antimony
>


-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x5E212EE1D35568BE
GPG key server: https://keys.fedoraproject.org/



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/D3XUHQG6KSIZF6GCQYEAIIIO3R4H2KW5/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Przemek Klosowski 

On 06/28/2018 03:34 PM, Josh Boyer wrote:

To answer the ecosystem question... if I were an EL shop that had been
using yum and writing scripts to interact with yum for years, and then
I had to rewrite all of my scripts and retrain my muscle memory to
call a new command that had similar semantics and compatibility, I'd
be pretty annoyed.  Having dnf in CentOS 7 is a way to help users that
use both Fedora and EL avoid that problem, which is good.


To tie two recent devel list threads, this is a perfect use case for a 
~/bin being first in PATH: a ~/bin/yum -> /bin/dnf symlink for those 
that don't want to rewrite scripts.


For the record, I was against introducing dnf as a separate command---I 
thought (and still think) that it should be yum v.3 (or whatever next 
major version was due at that time). Having said that, once the decision 
has been made, I just got on with it, even though I use a mix of Fedora 
and EL/RHEL so I have to remember which is which and use both yum and 
dnf commands.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PRRKRKUKXJ5YHA2KHLZ4R4RQFIRR6I55/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Josh Boyer 
On Thu, Jun 28, 2018 at 3:24 PM Gerald B. Cox  wrote:
>
>
>
> On Thu, Jun 28, 2018 at 11:54 AM, Neal Gompa  wrote:
>>
>> On Thu, Jun 28, 2018 at 2:51 PM Matthew Miller  
>> wrote:
>>
>> > When FESCo decided to approve that change to the original plan, this
>> > was noted as a potential risk. I personally think that staying aligned
>> > with the rest of the RH distro ecosystem is worth some inconvenience.
>> > It'll make it easier to share and collaborate on documentation and
>> > other help.
>> >
>
>
> Aren't we talking about YUM being a symlink to DNF?  If that is the case, I 
> don't believe
> staying "aligned" is going to be easier - since it is indeed DNF and not YUM. 
>   I was under the impression
> this was a rebranding; and that ship has sailed years ago.  Which also begs 
> the question, why isn't
> the rest of the RH distro ecosystem using DNF?

The cool thing about sailing ships on a globe is that it's a sphere
and you can keep going and still wind up back where you started :)

To answer the ecosystem question... if I were an EL shop that had been
using yum and writing scripts to interact with yum for years, and then
I had to rewrite all of my scripts and retrain my muscle memory to
call a new command that had similar semantics and compatibility, I'd
be pretty annoyed.  Having dnf in CentOS 7 is a way to help users that
use both Fedora and EL avoid that problem, which is good.

>> The irony is not lost on me that a big part of the reason DNF has been
>> adopted in other Linux distributions is because it's not called YUM
>> and wasn't attached to the stigma of that name, and after having that
>> happen, there's now people in RH/Fedora who want to rename DNF to YUM.
>>
>
> I'm not aware of that being a big part of the reason, but I am aware of the 
> negative connotation that YUM
> has had in the past... and the rebranding effort helped mitigate that.  I 
> don't understand why people appear
> to have some sort of emotional connection to the name YUM. DNF has been 
> around since 2013... 5 years later
> and we're discussing changing the name?

Yep.  Sometimes we don't consider all angles or get feedback that
negates decisions.  That's what's awesome about open source.  It
allows you to experiment, correct, and adapt, all in the public space.

josh
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WGINJGOLANM7EUOCVYK6FBDJU43CLLTB/

Semi-orphaning pysvn

2018-06-28 Thread Stephen Gallagher 
I've been keeping the lights on in this package for years since the
maintainer (ravenoak) vanished from Fedora. However, it doesn't build
against Python 3.7 (works fine with 3.6) and I don't have the cycles to dig
into it.

If someone steps up to fix the FTBFS, I'm willing to hang on as a
comaintainer, but if no one does, I'm going to orphan it completely in
about a week.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AX5UARVRHHSYPLSXGFZSENDQYGVG2WYE/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Gerald B. Cox 
On Thu, Jun 28, 2018 at 11:54 AM, Neal Gompa  wrote:

> On Thu, Jun 28, 2018 at 2:51 PM Matthew Miller 
> wrote:
>
> > When FESCo decided to approve that change to the original plan, this
> > was noted as a potential risk. I personally think that staying aligned
> > with the rest of the RH distro ecosystem is worth some inconvenience.
> > It'll make it easier to share and collaborate on documentation and
> > other help.
> >
>

Aren't we talking about YUM being a symlink to DNF?  If that is the case, I
don't believe
staying "aligned" is going to be easier - since it is indeed DNF and not
YUM.   I was under the impression
this was a rebranding; and that ship has sailed years ago.  Which also begs
the question, why isn't
the rest of the RH distro ecosystem using DNF?


>
> The irony is not lost on me that a big part of the reason DNF has been
> adopted in other Linux distributions is because it's not called YUM
> and wasn't attached to the stigma of that name, and after having that
> happen, there's now people in RH/Fedora who want to rename DNF to YUM.
>
>
I'm not aware of that being a big part of the reason, but I am aware of the
negative connotation that YUM
has had in the past... and the rebranding effort helped mitigate that.  I
don't understand why people appear
to have some sort of emotional connection to the name YUM. DNF has been
around since 2013... 5 years later
and we're discussing changing the name?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CAMID3UW5KZP3KTPQVOYVGTUTRJDKY57/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Matthew Miller 
On Thu, Jun 28, 2018 at 02:54:05PM -0400, Neal Gompa wrote:
> > When FESCo decided to approve that change to the original plan, this
> > was noted as a potential risk. I personally think that staying aligned
> > with the rest of the RH distro ecosystem is worth some inconvenience.
> > It'll make it easier to share and collaborate on documentation and
> > other help.
> The irony is not lost on me that a big part of the reason DNF has been
> adopted in other Linux distributions is because it's not called YUM
> and wasn't attached to the stigma of that name, and after having that
> happen, there's now people in RH/Fedora who want to rename DNF to YUM.

Well, here, we never had that stigma. :)


-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JHG2ZNE4V65J4NQTC7CM6S7REBFDYP3W/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Neal Gompa 
On Thu, Jun 28, 2018 at 2:51 PM Matthew Miller  wrote:
>
> On Wed, Jun 27, 2018 at 01:29:41PM -0700, Adam Williamson wrote:
> > But in Fedora land, we've spent several years selling the message "yum
> > is gone and replaced with this new thing called dnf". It would be
> > rather confusing to suddenly start selling the message "oh hey yum is
> > back only now it's sort of dnf but sort of not dnf".
>
> When FESCo decided to approve that change to the original plan, this
> was noted as a potential risk. I personally think that staying aligned
> with the rest of the RH distro ecosystem is worth some inconvenience.
> It'll make it easier to share and collaborate on documentation and
> other help.
>

The irony is not lost on me that a big part of the reason DNF has been
adopted in other Linux distributions is because it's not called YUM
and wasn't attached to the stigma of that name, and after having that
happen, there's now people in RH/Fedora who want to rename DNF to YUM.


--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BENZGPKFNOVQGQGIXKWTRY57QYEFKQZJ/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Matthew Miller 
On Wed, Jun 27, 2018 at 01:29:41PM -0700, Adam Williamson wrote:
> But in Fedora land, we've spent several years selling the message "yum
> is gone and replaced with this new thing called dnf". It would be
> rather confusing to suddenly start selling the message "oh hey yum is
> back only now it's sort of dnf but sort of not dnf".

When FESCo decided to approve that change to the original plan, this
was noted as a potential risk. I personally think that staying aligned
with the rest of the RH distro ecosystem is worth some inconvenience.
It'll make it easier to share and collaborate on documentation and
other help.



-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WN23XKJEDEQOSMWS4JJECU4KSF6NRLTA/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Ken Dreyer 
On Thu, Jun 28, 2018 at 7:16 AM, Daniel Mach  wrote:

> DNF shouldn't diverge from YUM just "because we can".
> We're fixing some obvious differences that weren't introduced for any good
> reason.
>
> There will be no special compat layer just a yum -> dnf symlink.
> If the compatibility is preserved to sufficient level, we believe it's a
> better
> option than to have 2 executables with different behavior.

I think this is a great plan. Thank you for explaining it here.

I also like Matt's idea of re-titling the change "Replace Yum 3 with
Yum 4, powered by DNF"? I think it would help bring publicity to
what's going on with Yum in Fedora.

- Ken
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LZ6DAL66VRHQNHLMN76OFTDJIRZSMMEX/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Jason L Tibbitts III 
> "MH" == Miro Hrončok  writes:

MH> What is the criterion to merge the side tag?

I think ultimately that's up to you, but certainly the idea is to
balance disruption (breaking builds or rawhide usability) against
holding back progress (the approved python 3.7 feature).

It would certainly be nice to have less disruption than 170 FTBFS
packages and 120 broken dependencies, but then if some of those packages
are broken already then they shouldn't count against the total unless
somehow they're "more broken" after the tag is merged.

I think setting a deadline for the merge (which would have to be pretty
soon if the mass rebuild is still on July 11) and sending regular broken
package lists and calls for help for help would be the only thing you
can really do besides just hitting the button and merging it.

 - J<
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/7ABC33DGZPKTZSRHD6YAZSSXEYVJEZPI/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Jason L Tibbitts III 
> "MH" == Miro Hrončok  writes:

MH> What is the criterion to merge the side tag?

I think ultimately that's up to you, but certainly the idea is to
balance disruption (breaking builds or rawhide usability) against
holding back progress (the approved python 3.7 feature).

It would certainly be nice to have less disruption than 170 FTBFS
packages and 120 broken dependencies, but then if some of those packages
are broken already then they shouldn't count against the total unless
somehow they're "more broken" after the tag is merged.

I think setting a deadline for the merge (which would have to be pretty
soon if the mass rebuild is still on July 11) and sending regular broken
package lists and calls for help for help would be the only thing you
can really do besides just hitting the button and merging it.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7ABC33DGZPKTZSRHD6YAZSSXEYVJEZPI/

Re: Packages with scriptlets which call ldconfig

2018-06-28 Thread Jason L Tibbitts III 
After modifying the script to strip comments and running it against the
most recent version of rawhide on my local mirror, I found that abrt,
pcsc-cyberjack and slic3r dropped off the list.  But I found that libdnf
actually appeared on the list when it wasn't before..  I checked the
package and that's correct; in commit
a5902b6c02cfe6f5f1338da3744f4c25e029fcde the %ldconfig_scriptlets macro
was removed and replaced with the old incorrect direct ldconfig calls.

https://src.fedoraproject.org/rpms/libdnf/c/a5902b6c02cfe6f5f1338da3744f4c25e029fcde?branch=master

Supposedly this is on purpose, to keep specfile compatibility with
RHEL7, but then the correct way to do that is to conditionalize the
scriptlets by wrapping them in

%if (0%{?rhel} && 0%{?rhel} <= 7)
...
%endif

The macros do of course work in EPEL but I guess EPEL compatibility
isn't the issue.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DXPHCOBSVR2VGFTNLYO2T77BPI3UEJTI/

Re: Packages with scriptlets which call ldconfig

2018-06-28 Thread Jason L Tibbitts III 
> "TH" == Till Hofmann  writes:

TH> Not strictly a script error: I already updated most of my packages
TH> without rebuilding them, so they are all false positives.

That's fine.  I could exclude those but I don't know which they are and
the benefit would be pretty low.

TH> I guess I'm not the only one who updated the Spec without a rebuild,
TH> so I'm not sure checking the source packages is the best approach.

Well, it shows the current state of rawhide.  (And I'm checking the
binary packages, not the srpms.)  Rebuilds in rawhide do not have a
particularly high cost so it doesn't really hurt to do them, but
certainly the mass rebuild in a couple of weeks will take care of them.
I'll rerun the script then.  Certainly if you know you don't have any
issues (which you can't really be sure of if you didn't actually build
and test) then you can ignore the report.

TH> Is it possible to directly check the Spec?

It is, but it's not as reliable or easy and wouldn't actually reflect
what's in rawhide currently.  Some specs can't be parsed without having
the full git checkout, and you have to be careful when parsing specs
because they execute arbitrary code.  You can do it by eye pretty
easily, but there are just too many packages right now for me to do
that.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/IDCFRHK2MIIDH7UKBVTSFB4SKMGFWUAG/

Re: [X86] Fwd: F29 System Wide Change: i686 Is For x86-64

2018-06-28 Thread Jeff Backus 
Thanks for the response and sorry for taking so long to reply.

On Mon, Jun 18, 2018 at 10:05 PM, Kevin Kofler 
wrote:

> Jeff Backus wrote:
> > Hmm.. Yes, we've had discussions within the SIG re: window managers that
> > support i586/i686, and KDE was on the list of WMs that no longer support
> > our target system. Do these patches/hacks only apply to KDE or do they
> > apply to Qt in general?
>
> The absolute worst is QtWebEngine. Chromium dropped support for non-SSE2
> x86
> years ago, so I had to cumulatively revert a whole bunch of commits that
> removed runtime SSE2 detection where it was present and added some more
> unconditional SSE2 optimizations. And now V8 (the JavaScript engine that
> Chromium relies on) dropped the x87 backend (i.e., the one using x87
> rather
> than SSE2 for floating-point operations, hence working on non-SSE2 x86
> machines) for their JIT entirely (and there is no interpreter-only
> fallback), so I am even stuck trying to port the x87 backend to each new
> Qt
> branch (which uses a newer Chromium and thus a newer V8). This is a huge
> effort, and nobody outside of Fedora cares about non-SSE2 anymore. Even
> distros that claim to support non-SSE2 hardware just ship QtWebEngine as
> SSE2 only. I haven't seen any other distro even picking up my patch, let
> alone working on it. The Fedora Chromium, V8 and Node.js packagers also do
> not care.
>

Wow. Yes, that is a heavy lift. Thank you for your efforts! :) It helps to
see how expensive non-SSE2 support is. Thanks.


> I think Google sucks for desupporting hardware that way, but I also do not
> think maintaining the V8 x87 backend on our own is going to scale in the
> long run. My time is limited and I do not currently see anybody else among
> the Fedora Qt maintainers who is at the same time both able and willing to
> maintain it. (This needs somebody with plenty of free time and with some
> experience working on compilers.)
>

Agreed. Is the only reason to maintain the x87 backend for non-SSE2 support?

So the QtWebEngine no-sse2 patch is definitely going to be dropped from
> F29+, given the FESCo decision on this issue. For F27 and F28, I will look
> into it and see what I can do.
>

Thank you.

Cheers,
Jeff


-- 
Jeff Backus
jeff.bac...@gmail.com
http://github.com/jsbackus
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XGXDROC66RS5DGUGQV5NONBJR2TRMRQQ/

Re: What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Laura Abbott 

On 06/28/2018 06:42 AM, Miro Hrončok wrote:

Stuff that doesn't build and sounds important:

  - ceph (also FTBFS in regular rawhide)
  - libreoffice (also FTBFS in regular rawhide)
  - orca (blocked by pyatspi, looking at it ATM)
  - kernel-tools


For kernel-tools, it depends on your definition of "important".
This is mostly a collection of miscellaneous userspace tools
that happen to live in the kernel source tree. The part that
isn't building is perf which is notoriously finicky and
probably needs to be debugged in conjunction with the
upstream maintainer.

Thanks,
Laura

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/F4BK4ZGUFCMOSZBORILBBR3LDTCHYYTY/

When will mock make it into copr?

2018-06-28 Thread Radka Janekova 
Hi, we've got some issues that were resolved[1] and I was wondering if
anyone could give me a bit better idea when would it make into copr?


[1] bz: https://bugzilla.redhat.com/show_bug.cgi?id=1580435
fixed: https://github.com/rpm-software-management/mock/commit/f2282d6

Regards,
Radka

--
*Radka Janeková*
.NET Engineer, Red Hat
*radka.ja...@redhat.com *
IRC: radka | Freenode: Rhea
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FFMK2NS66J64VD45SCIBZXTFNFHEOHPN/

jplesnik pushed to perl-Sub-Infix (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 16:00:38 UTC

From 3f5f44a9cba351bb5ef0cd31fa3c365c6a15fae5 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 16:00:36 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Sub-Infix.spec b/perl-Sub-Infix.spec
index 26163ef..b8b26e0 100644
--- a/perl-Sub-Infix.spec
+++ b/perl-Sub-Infix.spec
@@ -1,6 +1,6 @@
 Name:   perl-Sub-Infix
 Version:0.004
-Release:4%{?dist}
+Release:5%{?dist}
 Summary:Create a fake infix operator
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Sub-Infix
@@ -53,6 +53,9 @@ make test
 %{_mandir}/man3/*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.004-5
+- Perl 5.28 rebuild
+
 * Fri Feb 09 2018 Fedora Release Engineering  - 
0.004-4
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Sub-Infix/c/3f5f44a9cba351bb5ef0cd31fa3c365c6a15fae5?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/JSX5UJDXKAA6CR3U4GVXOCHSJ7SBR5QK/

[Bug 1594473] perl-Module-CoreList-5.20180622 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594473

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #5 from Fedora Update System  ---
perl-Module-CoreList-5.20180626-1.fc28 has been pushed to the Fedora 28 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-2018-9ea0246ee1

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/RD2ZUJICMAKHTFU2QLKLN7Z5MTO4UCCB/

[Bug 1594993] perl-Event-RPC-1.09 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594993



--- Comment #9 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc28 has been pushed to the Fedora 28 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-2018-fb8982959e

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/7WELHPYIQR5YFKQ6QJERCTBMAC7BMXI3/

[Bug 1595972] perl-Event-RPC-1.10 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595972



--- Comment #5 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc28 has been pushed to the Fedora 28 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-2018-fb8982959e

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/KI3HJSFJUOARRJQ2SRUJULQV7MLCASZT/

[Bug 1595716] perl-Module-CoreList-5.20180626 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595716

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Module-CoreList-5.20180626-1.fc28 has been pushed to the Fedora 28 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-2018-9ea0246ee1

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/VQJVRYVDZUO6W7UNXNMWNAOZHCQTSXKD/

[Bug 1593043] perl-CPAN-Perl-Releases-3.64 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1593043



--- Comment #12 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc28 has been pushed to the Fedora 28 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-2018-9d2f8be8d6

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/LTRG2D2ZBQP7OUOTRHLJS36HCNFNVJMA/

[Bug 1592742] perl-CPAN-Perl-Releases-3.62 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1592742



--- Comment #16 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc28 has been pushed to the Fedora 28 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-2018-9d2f8be8d6

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/W4MQDZ4ZQBM6M5MJJWM76JTUTLOXAZHZ/

[Bug 1594468] perl-CPAN-Perl-Releases-3.66 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594468



--- Comment #8 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc28 has been pushed to the Fedora 28 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-2018-9d2f8be8d6

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/6VI5QFAG2TDOR3G7ZJLS4JRJ22S3QMUL/

[Bug 1595713] perl-CPAN-Perl-Releases-3.68 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595713



--- Comment #4 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc28 has been pushed to the Fedora 28 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-2018-9d2f8be8d6

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/PRFY3YTJZYX6ANYPA4VLNOAOBULF4IOX/

[Bug 1594219] ack-2.24 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594219



--- Comment #4 from Fedora Update System  ---
ack-2.24-1.fc28 has been pushed to the Fedora 28 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-2018-c48ee3baff

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/PCK76HAQY7MW2KK5FP2X2A7L73UXR46I/

Re: Packages with scriptlets which call ldconfig

2018-06-28 Thread Jonathan Dieter 
On Wed, 2018-06-27 at 20:30 -0500, Jason L Tibbitts III wrote:
> usbipjdieter

Fixed in git for F28+

Jonathan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ANOVOB3GH26OIF5RH6M2FHVZ27A5MGVT/

Re: Packages with scriptlets which call ldconfig

2018-06-28 Thread Robert-André Mauchin 
On jeudi 28 juin 2018 03:30:34 CEST Jason L Tibbitts III wrote:
> eclipseo   libfilteraudio webkit2-sharp

Done for me on F28+.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/OQMUBQH2S4EHOPAUYEAMNC54M5A6IMG5/

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

2018-06-28 Thread updates 
The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  18  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c   
unrtf-0.21.9-8.el6
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-7948d6772e   
ansible-2.5.5-1.el6
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-98ff28b9d0   
drupal7-backup_migrate-3.5-1.el6


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

ga-5.6.5-1.el6
globus-ftp-control-8.4-1.el6
inxi-3.0.14-1.el6
lynis-2.6.5-1.el6
myproxy-6.1.30-1.el6
pidgin-sipe-1.23.2-2.el6

Details about builds:



 ga-5.6.5-1.el6 (FEDORA-EPEL-2018-6dad7f8714)
 Global Arrays Toolkit

Update Information:

New release 5.6.5

ChangeLog:

* Wed Jun 13 2018 Edoardo Apra  - 5.6.5-1
- New release 5.6.5
- Replaced Atlas with OpenBLAS
- Made compatible with ScaLapack RPM updates
- Added options -with-blas4 to work with NWChem
* Wed Feb  7 2018 Fedora Release Engineering  - 
5.6.1-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Fri Aug 25 2017 Adam Williamson  - 5.6.1-1
- New release 5.6.1
- Minor spec fixups
* Wed Aug  2 2017 Fedora Release Engineering  - 
5.3b-24
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild
* Wed Jul 26 2017 Fedora Release Engineering  - 
5.3b-23
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
* Fri Feb 10 2017 Fedora Release Engineering  - 
5.3b-22
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
* Fri Oct 21 2016 Orion Poplawski  - 5.3b-21
- Rebuild for openmpi 2.0
* Wed Feb  3 2016 Fedora Release Engineering  - 
5.3b-20
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
* Tue Sep 15 2015 Orion Poplawski  - 5.3b-19
- Rebuild for openmpi 1.10.0
* Sun Jul 26 2015 Sandro Mani  - 5.3b-18
- Rebuild for RPM MPI Requires Provides Change
* Wed Jun 17 2015 Fedora Release Engineering  
- 5.3b-17
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
* Sat May  2 2015 Kalev Lember  - 5.3b-16
- Rebuilt for GCC 5 C++11 ABI change
* Fri Mar 20 2015 David Brown  - 5.3b-15
- Rebuild to support new version of mpich
* Wed Nov 19 2014 David Brown  - 5.3b-14
- Fix bug #1150473 to support epel7




 globus-ftp-control-8.4-1.el6 (FEDORA-EPEL-2018-c90c5ee2aa)
 Globus Toolkit - GridFTP Control Library

Update Information:

globus-ftp-control (8.4)  * Check for missing signing policy req flag  myproxy
(6.1.30)  * Remove macro overquoting

ChangeLog:

* Thu Jun 28 2018 Mattias Ellert  - 8.4-1
- GT6 update: Check for missing signing policy req flag




 inxi-3.0.14-1.el6 (FEDORA-EPEL-2018-18f14d5c55)
 A full featured system information script

Update Information:

Update to 3.0.14. Now it uses Perl.

ChangeLog:

* Thu Jun 28 2018 Vasiliy N. Glazov  3.0.14-1
- Update to 3.0.14




 lynis-2.6.5-1.el6 (FEDORA-EPEL-2018-a5767153ca)
 Security and system auditing tool

Update Information:

2.6.5

ChangeLog:

* Wed Jun 27 2018 Gwyn Ciesla  - 2.6.5-1
- 2.6.5

References:

  [ 1 ] Bug #1595476 - lynis-2.6.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1595476




 myproxy-6.1.30-1.el6 (FEDORA-EPEL-2018-c90c5ee2aa)
 Manage X.509 Public Key Infrastructure (PKI) security credentials

Update Information:

globus-ftp-control (8.4)  * Check for missing signing policy req flag  myproxy
(6.1.30)  * Remove macro overquoting

Re: Heads up: Python 3.7 rebuild in progress

2018-06-28 Thread William Moreno 
>
>
> williamjmorenor python-rows
>
>
Done
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ANHVPWIYX4QUAZPDLBMQG4ESLKVTCKI4/

Re: F28's "ImprovedLaptopBatteryLife" causing USB issues?

2018-06-28 Thread Hans de Goede 

Hi,

On 26-06-18 15:19, Radka Janekova wrote:

On Mon, Jun 25, 2018 at 2:29 PM, Hans de Goede mailto:hdego...@redhat.com>>wrote:

Hi,

On 25-06-18 13:26, Radka Janekova wrote:

ref: 
https://fedoraproject.org/wiki/Changes/ImprovedLaptopBatteryLife#Current_status 

  > "Enable USB autosuspend for USB bluetooth receivers by default. If all 
other USB devices on the laptop also have USB auto-suspend enabled (which typically is true) 
this saves aprox. 0.4 Watts of power on an idle laptop."

I believe that this option fails to actually re-enable USB until 
complete reboot of a machine affected. Neither keyboard, nor mouse, nothing, no 
USBs work after switching from power (dock) to battery, even after 
re-connecting power.

The issue is observed since upgrading to F28 (non-gnome)

Is there anything I can look at to find out what is causing it, if it 
is really due to the above mentioned power saving tweaks?


F28 only enables auto-suspend on BlueTooth USB interfaces, all other USB 
devices are
left alone, so this seems unrelated.


Not exactly since it's happening only since the update and I don't know what 
else it could be...
Further I do use a bluetooth keyboard that I am unable to connect anymore (so i 
use it through synergy from windows machine...)


In your original mail you say "no USBs work", that sounds like you've tested 
other USB
devices and they all don't work.

Anyways you can try passing "btusb.enable_autosuspend=0" on the kernel 
commandline,
that disables the USB BT autosuspend which we now do by default in F28.

Regards,

Hans

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FLMW2RA67EHMVJFNTHRK5K46VP2FFSK4/

What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok 

The Python 3.7 rebuild in the f29-python side tag is currently:

 - 2168 built
 - ~170 FTBFS
 - ~120 blocked by dependencies that FTBFS

Ideally, this would all get fixed before the merge, but that's 
unrealistic, there are packages that are FTBFS for unrelated reasons, etc.


What is the criterion to merge the side tag?

The critpath installs fine (except stuff that cannot be installed due to 
yum-deprecated vs yum collisions and gnome-software that has some broken 
dependency on PackageKit).


Stuff that doesn't build and sounds important:

 - ceph (also FTBFS in regular rawhide)
 - libreoffice (also FTBFS in regular rawhide)
 - orca (blocked by pyatspi, looking at it ATM)
 - kernel-tools

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/YVW4WOJGUYL4ZTD32UQHZAEVYX47U7L4/

What is the criterion for Python 3.7 side tag merge?

2018-06-28 Thread Miro Hrončok 

The Python 3.7 rebuild in the f29-python side tag is currently:

 - 2168 built
 - ~170 FTBFS
 - ~120 blocked by dependencies that FTBFS

Ideally, this would all get fixed before the merge, but that's 
unrealistic, there are packages that are FTBFS for unrelated reasons, etc.


What is the criterion to merge the side tag?

The critpath installs fine (except stuff that cannot be installed due to 
yum-deprecated vs yum collisions and gnome-software that has some broken 
dependency on PackageKit).


Stuff that doesn't build and sounds important:

 - ceph (also FTBFS in regular rawhide)
 - libreoffice (also FTBFS in regular rawhide)
 - orca (blocked by pyatspi, looking at it ATM)
 - kernel-tools

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YVW4WOJGUYL4ZTD32UQHZAEVYX47U7L4/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Daniel Mach 
On Thu, Jun 28, 2018 at 1:35 AM, Adam Williamson  wrote:

> On Wed, 2018-06-27 at 18:18 -0400, Josh Boyer wrote:
> > On Wed, Jun 27, 2018 at 4:30 PM Adam Williamson
> >  wrote:
> > >
> > > On Wed, 2018-06-27 at 16:25 -0400, Matthew Miller wrote:
> > > > On Wed, Jun 27, 2018 at 02:54:07PM +0200, Björn Persson wrote:
> > > > > > IMHO deprecate != remove, but rather mark for removal in some
> next release.
> > > > > > Should the change be called differently?
> > > > >
> > > > > Especially since Yum has been called "yum-deprecated" for several
> > > > > releases already.
> > > >
> > > > How about "Replace Yum 3 with Yum 4, powered by DNF"? This would
> bring
> > > > us in line with what's happening in the Enterprise Linux space.
> > > >
> > > > (See
> > > > https://wiki.centos.org/SpecialInterestGroup/
> ConfigManagementSIG/YUM4)
> > >
> > > But in Fedora land, we've spent several years selling the message "yum
> > > is gone and replaced with this new thing called dnf". It would be
> > > rather confusing to suddenly start selling the message "oh hey yum is
> > > back only now it's sort of dnf but sort of not dnf".
> >
> > It's still dnf.  In fact, I believe /usr/bin/dnf would even still
> > exist.  However, dnf has come significantly closer to yum
> > functionality since it was first introduced and reuniting isn't a bad
> > idea.
> >
> > I understand where you're coming from, but I think we should take the
> > opportunity to correct now.  We (and I do mean we as someone that
> > pushed for not calling it yum) had valid reasons to separate it in the
> > past, but those reasons are becoming increasingly invalid.  Sticking
> > with the dnf name is going to become a forced split going forward for
> > little benefit.  I'm happy to eat my own words and say we should
> > probably focus around a single package manager name at this point.
> >
> > > It's different from the EL situation because EL never really had the
> > > "dnf is the new thing" phase. If you're going from EL 7 to The Next EL
> > > you're just going from yum 3 to "yum 4".
> >
> > Yeah, but if you play in both spaces continuing to call it "dnf" in
> > Fedora and "yum4" in EL is forcing a mental break that doesn't really
> > need to be there.
>
> So I may have missed the latest shiny plans here - I thought the plan
> was that dnf would provide a 'yum' CLI command which was as close as
> possible to compatible with yum 3, but *also* provide a 'dnf' CLI
> command which was more like the 'current' dnf CLI in Fedora. Is that
> still the case? Or is there just going to be one true CLI command now?
>
> DNF shouldn't diverge from YUM just "because we can".
We're fixing some obvious differences that weren't introduced for any good
reason.

There will be no special compat layer just a yum -> dnf symlink.
If the compatibility is preserved to sufficient level, we believe it's a
better
option than to have 2 executables with different behavior.

The long-term priority is to make DNF command-line interface and behavior
consistent
and in such cases, DNF must diverge from YUM3 behavior and insisting on 100%
compatibility would block usability improvements and evolution in general.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BLKXTF4K3WZPM2ZHHDAWTBKJIMMUXXG3/

[Bug 1591449] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1591449

Petr Pisar  changed:

   What|Removed |Added

External Bug ID||Github
   ||redhotpenguin/perl-Archive-
   ||Zip/pull/33



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-de...@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-de...@lists.fedoraproject.org/message/TDS3W43NG4476ZR6EJJTNBNRDKHTWSBC/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Daniel Mach 
On Wed, Jun 27, 2018 at 2:23 PM, Sam Varshavchik 
wrote:

> Jan Kurik writes:
>
> = Proposed Self Contained Change: Deprecate YUM 3 =
>> https://fedoraproject.org/wiki/Changes/Deprecate_YUM_3
>>
>>
>> Owner(s):
>>   * Daniel Mach 
>>
>>
>> Remove yum (v3) and all related packages from Fedora.
>>
>>
>> == Detailed description ==
>> Remove packages from the distribution:
>> * createrepo
>>
>
> We should have createrepo_c install a symlink, and have an "Obsoletes:
> createrepo" so that this gets taken care of by a normal upgrade.
>
> Yes, we'll provide compat Provides and symlinks to createrepo_c and yum so
many command line users won't see any big difference.
I've updated the document with the 'Compatibility' section.
Thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NMLNEFKAJKPCER5KDS45SORDFYF4V2AT/

Re: change in -fpic handling?

2018-06-28 Thread Nick Clifton 
Hi Dave, Hi Florian,

  Right - there is a new annobin rpm available - annobin-8.0-1.el8 - which
  has these changes:

* Weak symbols are not generated by the annobin plugin
  when compiling with -ffunction-sections.

  There was no point really.  Linker garbage collection will not
  discard sections if they have annobin notes against them, since
  the code section and the note section are not in a section group.
  
  Really this is a gcc problem.  If it created a section group for
  sections created by the -ffunction-sections option, then annobin
  could add the notes into this group and linker garbage collection
  would discard the lot.

  Note - annobin does still generate weak symbols for linkonce
  sections, since these can and will be discarded by the linker.
  The symbols still get into the dynamic symbol table, but they
  are hidden.  Not sure if this makes much difference however.


* The annobin plugin will now only reference symbols that it 
  creates, and all of these symbols now have a ".annobin_" prefix 
  in order to avoid potential collisions with symbols defined
  elsewhere in the executable.


  I hope that these changes address the immediate issue of libxsmm not 
  compiling.

  Longer term I need to work with the gcc maintainers to get section
  groups generated for function sections.

Cheers
  Nick
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GTDIIJ7S6YYV55EQFJ4FRI57VWT7HJES/

[Bug 1595972] perl-Event-RPC-1.10 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595972

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc27 has been pushed to the Fedora 27 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-2018-1e3a1eca9d

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/6MJXI7S6MJ3BIA7J4KGVPO4AVKEP4CE6/

[Bug 1594993] perl-Event-RPC-1.09 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594993

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #8 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc27 has been pushed to the Fedora 27 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-2018-1e3a1eca9d

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/EPPLSBI67RF6KN5KD66SBPZQH5M4WSB7/

[Bug 1593043] perl-CPAN-Perl-Releases-3.64 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1593043

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #11 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc27 has been pushed to the Fedora 27 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-2018-239130efc9

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/A7VNWDUQSYZGSIA4DWXFLGW424NYAHT3/

[Bug 1595713] perl-CPAN-Perl-Releases-3.68 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595713

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc27 has been pushed to the Fedora 27 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-2018-239130efc9

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/ILQREYJ2VMZ2MCN7WKGHF7XRR4A5N36L/

[Bug 1594468] perl-CPAN-Perl-Releases-3.66 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594468



--- Comment #7 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc27 has been pushed to the Fedora 27 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-2018-239130efc9

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/HVKI2BIJI2HEISS3S76CAYHOSCMVH4CZ/

[Bug 1592742] perl-CPAN-Perl-Releases-3.62 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1592742

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #15 from Fedora Update System  ---
perl-CPAN-Perl-Releases-3.68-1.fc27 has been pushed to the Fedora 27 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-2018-239130efc9

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/V6H4ZXDTY6RMSUEYDOVFTHEHTT57ISLN/

[Bug 1594219] ack-2.24 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594219

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
ack-2.24-1.fc27 has been pushed to the Fedora 27 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-2018-39d8aeec8b

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/Q2KLO6DUCZZGCMDVXZKD76QWFOITZOPU/

jplesnik pushed to perl-Sub-Exporter-Lexical (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 12:00:53 UTC

From 3dd861045793ce0629efd54dc71f1db7617cfbcf Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 12:00:51 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Sub-Exporter-Lexical.spec b/perl-Sub-Exporter-Lexical.spec
index 442d17d..6dd9def 100644
--- a/perl-Sub-Exporter-Lexical.spec
+++ b/perl-Sub-Exporter-Lexical.spec
@@ -1,6 +1,6 @@
 Name:   perl-Sub-Exporter-Lexical
 Version:0.092292
-Release:5%{?dist}
+Release:6%{?dist}
 Summary:Export lexically-available subs with Sub::Exporter
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Sub-Exporter-Lexical
@@ -54,6 +54,9 @@ rm $RPM_BUILD_ROOT%{perl_vendorlib}/Sub/Exporter/snippet.pl
 %{_mandir}/man3/*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 0.092292-6
+- Perl 5.28 rebuild
+
 * Fri Feb 09 2018 Fedora Release Engineering  - 
0.092292-5
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Sub-Exporter-Lexical/c/3dd861045793ce0629efd54dc71f1db7617cfbcf?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/TH46P2T4H4YM6W6AXXCO7KOUVQDM6QNS/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Miroslav Suchý 
Dne 27.6.2018 v 13:44 Vít Ondruch napsal(a):
> So is it actually possible to use DNF to prepare bootstrap buildroot
> containing YUM from RHEL and then the buildroot itself being managed by
> YUM? Last time I tried to come up with setup like this I failed
> (rhbz#1467314) ...

Right. Still not possible. I thought that with the config option bootstrap_* we 
are done, but I just tested it and I
still get en error. :(

Miroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SQLQEHCGXN44PEZUZFGW3M3LUVRXF3Q2/

Re: F29 Self Contained Change: Deprecate YUM 3

2018-06-28 Thread Miroslav Suchý 
Dne 28.6.2018 v 02:00 Kevin Kofler napsal(a):
> How about changing the default config to use DNF instead? Last I checked, 
> the tenor was that it should work and that you just prefer using YUM 3 to 
> ensure the results are the same as when running mock on an EL machine, but 
> if YUM 3 is not available anymore, wouldn't using DNF work?

This is definitely possible. Just add
  config_opts['package_manager'] = 'dnf'
And it will work. Kind of. If you are ok with using different depsolver.

E.g., if you have in spec
  BuildRequires: webserver
And yum always picked httpd, dnf can pick nginx. Or vice versa. The code is 
different.

Miroslav
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UCDMPGXJHICZFU3T4QPVBPIAGCT6OQKT/

Re: streamlining fedora-release (again)

2018-06-28 Thread Zbigniew Jędrzejewski-Szmek 
On Thu, Jun 28, 2018 at 06:28:53AM -0400, Stephen Gallagher wrote:
> On Wed, Jun 27, 2018 at 9:19 PM Dennis Gilmore  wrote:
> 
> > El mié, 27-06-2018 a las 11:58 +, Zbigniew Jędrzejewski-Szmek
> > escribió:
> > > Hi,
> > >
> > > I'd like to pick up the process of converting fedora-release from a
> > > split "upstream"/"downstream" model into a single repo in src.fp.o.
> > >
> > > For previous discussions see
> > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje
> > > ct.org/thread/CIKK4WEF5ACVWZ6EWBKNHSKKKCDTV27C/#CIKK4WEF5ACVWZ6EWBKNH
> > > SKKKCDTV27C
> > > https://pagure.io/fedora-release/pull-request/119
> > > https://pagure.io/releng/issue/7293
> > >
> > > I made the changes requested by Dennis Gilmore
> > > (an exploded repo, no tarball) and they are available in
> > > https://src.fedoraproject.org/fork/zbyszek/rpms/fedora-release/branch
> > > /drop-upstream-split .
> > >
> > > "Tests" were requested — I tested using rpmdiff and diffoscope that
> > > the changes only introduce timestamp differences, and then the
> > > subsequent cleanup commits only introduce expected differences
> > > (Group tag becomes "Unspecified", the description is updated,
> > > whitespace changes in scriptlets). If additional testing is required
> > > let me know what.
> > >
> > > As stated previously, I'm requesting co-maintainership of
> > > fedora-release to merge presets requests in reasonable time
> > > and to implement the changes described above.
> > >
> > > Let me know if you need anything else from me now.
> > > (I'll revisit the outstanding PRs against fedora-release once
> > > the new repo is established, I hope that happens quickly.)
> > >
> > > Zbyszek
> > fedora-release is no longer in my scope of influence, however the
> > testing requested was to make sure that any updates do not break the
> > package, the reluctance to simplify the process is due to the number of
> > times simple patches were submitted that broke things in unintended
> > ways.
> >
> >
> 
> In the recent past, we've had situations where the artificial split itself
> resulted in errors because the person merging from upstream to downstream
> didn't know that certain packages had to be updated outside the tarball due
> to RPM limitations. Having a single repository would have avoided this.
> 
> When you say "the reluctance to simplify the process is due to the number of
> times simple patches were submitted that broke things in unintended
> ways", it sounds like you're saying "we implemented the separation so we
> could prevent this from happening, but in reality it didn't help at all
> because the changes still got merged and built downstream". (And yes, I'm
> aware that I was responsible for a non-trivial number of those).
> 
> I think that eliminating the redundancy here is an improvement on its own.
> I don't believe that adding new testing needs to be a pre-requisite for
> this. It can (and should) be done, but we shouldn't block a positive change
> waiting for a "perfect" one.

Yes, that's my thinking too — we know that the simplified version
results in identical packages. If you think some more checks should be
added, that's OK, I'd be happy to do that, but a) please be more
precise in what exactly those checks should be, b) they would apply to
the old setup too in the same way, so this shouldn't block the change.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/SGXKSNFUFPSOH4GZ2Y6ZJCFXWRKSDCMG/

Fedora Rawhide-20180627.n.0 compose check report

2018-06-28 Thread Fedora compose checker 
No missing expected images.

Failed openQA tests: 15/138 (x86_64), 23/24 (i386), 1/2 (arm)

New failures (same test did not fail in Rawhide-20180625.n.0):

ID: 253004  Test: x86_64 Server-dvd-iso base_update_cli
URL: https://openqa.fedoraproject.org/tests/253004
ID: 253013  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/253013
ID: 253014  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/253014
ID: 253017  Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/253017
ID: 253024  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/253024
ID: 253033  Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/253033
ID: 253034  Test: i386 Workstation-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/253034
ID: 253035  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/253035
ID: 253036  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/253036
ID: 253050  Test: i386 KDE-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/253050
ID: 253056  Test: x86_64 AtomicWorkstation-dvd_ostree-iso 
install_default@uefi
URL: https://openqa.fedoraproject.org/tests/253056
ID: 253067  Test: x86_64 universal install_repository_http_variation
URL: https://openqa.fedoraproject.org/tests/253067
ID: 253068  Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/253068
ID: 253069  Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/253069
ID: 253092  Test: x86_64 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/253092
ID: 253101  Test: x86_64 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/253101
ID: 253110  Test: x86_64 universal install_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/253110
ID: 253123  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/253123
ID: 253127  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/253127
ID: 253129  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/253129
ID: 253130  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/253130
ID: 253131  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/253131
ID: 253137  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/253137
ID: 253139  Test: i386 universal upgrade_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/253139
ID: 253140  Test: i386 universal install_blivet_lvmthin
URL: https://openqa.fedoraproject.org/tests/253140
ID: 253141  Test: i386 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/253141
ID: 253142  Test: i386 universal install_blivet_xfs
URL: https://openqa.fedoraproject.org/tests/253142
ID: 253143  Test: i386 universal install_blivet_no_swap
URL: https://openqa.fedoraproject.org/tests/253143
ID: 253144  Test: i386 universal install_blivet_btrfs
URL: https://openqa.fedoraproject.org/tests/253144
ID: 253145  Test: i386 universal install_blivet_ext3
URL: https://openqa.fedoraproject.org/tests/253145
ID: 253146  Test: i386 universal install_lvmthin
URL: https://openqa.fedoraproject.org/tests/253146
ID: 253147  Test: i386 universal install_ext3
URL: https://openqa.fedoraproject.org/tests/253147
ID: 253148  Test: i386 universal install_btrfs
URL: https://openqa.fedoraproject.org/tests/253148
ID: 253149  Test: i386 universal install_software_raid
URL: https://openqa.fedoraproject.org/tests/253149
ID: 253150  Test: i386 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/253150
ID: 253151  Test: i386 universal install_scsi_updates_img
URL: https://openqa.fedoraproject.org/tests/253151
ID: 253152  Test: i386 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/253152
ID: 253153  Test: i386 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/253153

Old failures (same test failed in Rawhide-20180625.n.0):

ID: 253051  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/253051

Soft failed openQA tests: 6/138 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test did not soft fail in Rawhide-20180625.n.0):

ID: 253019  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/253019
ID: 253040  Test: x86_64 KDE-live-iso

[Bug 1596132] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip [fedora-all]

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1596132

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/OMRLBHWJXGROD6IMK4TFBXZ37DT7TRA4/

jplesnik pushed to perl-Encode-IMAPUTF7 (master). "Perl 5.28 rebuild"

2018-06-28 Thread notifications 
Notification time stamped 2018-06-28 10:29:29 UTC

From e8b13c9ec0f81b403793e064c5e21294bf9ffd15 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova 
Date: Jun 28 2018 10:29:25 +
Subject: Perl 5.28 rebuild


---

diff --git a/perl-Encode-IMAPUTF7.spec b/perl-Encode-IMAPUTF7.spec
index bed6b4b..4b1392a 100644
--- a/perl-Encode-IMAPUTF7.spec
+++ b/perl-Encode-IMAPUTF7.spec
@@ -2,7 +2,7 @@
 
 Name:   perl-Encode-IMAPUTF7
 Version:1.05
-Release:6%{?dist}
+Release:7%{?dist}
 Summary:Process the special UTF-7 variant required by IMAP
 License:GPL+ or Artistic
 URL:https://metacpan.org/release/Encode-IMAPUTF7
@@ -42,6 +42,9 @@ make test
 %_mandir/man3/*
 
 %changelog
+* Thu Jun 28 2018 Jitka Plesnikova  - 1.05-7
+- Perl 5.28 rebuild
+
 * Thu Feb 08 2018 Fedora Release Engineering  - 
1.05-6
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
 



https://src.fedoraproject.org/rpms/perl-Encode-IMAPUTF7/c/e8b13c9ec0f81b403793e064c5e21294bf9ffd15?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/X3L5FDCSRGHHIULC2NZKFKPPCYUVHC54/

Re: streamlining fedora-release (again)

2018-06-28 Thread Stephen Gallagher 
On Wed, Jun 27, 2018 at 9:19 PM Dennis Gilmore  wrote:

> El mié, 27-06-2018 a las 11:58 +, Zbigniew Jędrzejewski-Szmek
> escribió:
> > Hi,
> >
> > I'd like to pick up the process of converting fedora-release from a
> > split "upstream"/"downstream" model into a single repo in src.fp.o.
> >
> > For previous discussions see
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje
> > ct.org/thread/CIKK4WEF5ACVWZ6EWBKNHSKKKCDTV27C/#CIKK4WEF5ACVWZ6EWBKNH
> > SKKKCDTV27C
> > https://pagure.io/fedora-release/pull-request/119
> > https://pagure.io/releng/issue/7293
> >
> > I made the changes requested by Dennis Gilmore
> > (an exploded repo, no tarball) and they are available in
> > https://src.fedoraproject.org/fork/zbyszek/rpms/fedora-release/branch
> > /drop-upstream-split .
> >
> > "Tests" were requested — I tested using rpmdiff and diffoscope that
> > the changes only introduce timestamp differences, and then the
> > subsequent cleanup commits only introduce expected differences
> > (Group tag becomes "Unspecified", the description is updated,
> > whitespace changes in scriptlets). If additional testing is required
> > let me know what.
> >
> > As stated previously, I'm requesting co-maintainership of
> > fedora-release to merge presets requests in reasonable time
> > and to implement the changes described above.
> >
> > Let me know if you need anything else from me now.
> > (I'll revisit the outstanding PRs against fedora-release once
> > the new repo is established, I hope that happens quickly.)
> >
> > Zbyszek
> fedora-release is no longer in my scope of influence, however the
> testing requested was to make sure that any updates do not break the
> package, the reluctance to simplify the process is due to the number of
> times simple patches were submitted that broke things in unintended
> ways.
>
>

In the recent past, we've had situations where the artificial split itself
resulted in errors because the person merging from upstream to downstream
didn't know that certain packages had to be updated outside the tarball due
to RPM limitations. Having a single repository would have avoided this.

When you say "the reluctance to simplify the process is due to the number of
times simple patches were submitted that broke things in unintended
ways", it sounds like you're saying "we implemented the separation so we
could prevent this from happening, but in reality it didn't help at all
because the changes still got merged and built downstream". (And yes, I'm
aware that I was responsible for a non-trivial number of those).

I think that eliminating the redundancy here is an improvement on its own.
I don't believe that adding new testing needs to be a pre-requisite for
this. It can (and should) be done, but we shouldn't block a positive change
waiting for a "perfect" one.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EHLXZBF6OVXQ4FD66GVXGMKHETQWFUCK/

Re: F29 System Wide Change: Make BootLoaderSpec the default

2018-06-28 Thread Javier Martinez Canillas 
On Thu, Jun 28, 2018 at 3:34 AM, Dennis Gilmore  wrote:
> El jue, 14-06-2018 a las 12:06 +0200, Jan Kurik escribió:
>> = Proposed System Wide Change: Make BootLoaderSpec the default =
>> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

[snip]

>> Fedora already has a lot of infrastructure in place to not require
>> modifying bootloader configuration files for boot menu entries. The
>> BootLoaderSpec and drop-in BLS fragments can be used instead, and the
>> kernel-install script can do any additional task that is currently
>> done by grubby. The kernel-install script has a pluggable design that
>> uses a drop-in directory for scripts to extend its functionality. So
>> if needed, any bootloader specific logic can be implemented as
>> kernel-install scripts.
>> With this setup the bootloader configuration could be static and not
>> modified after installation.
>> The missing piece was the lack of BLS support on all the supported
>> bootloaders, but all of them have support to parse BLS fragments now.
>> So we can default to install BLS files on kernel installation and
>> drop
>> grubby.
>
> There is no BLS support in u-boot, how is it planned to support ARM
> systems? it is not an issue for aarch64 systems using u-boot as they
> use the efi implementation and load grub2, that is not true on 32 bit
> arm at all.
>

I talked with Peter Robinson (on cc) and the plan is to do the same
for ARMv7 in Fedora 29.

> Dennis
>

Best regards,
Javier
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UA6DK5Q23H3MVPM5F526DL5RPFT3M3CT/

[Bug 1591449] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1591449

Cedric Buissart  changed:

   What|Removed |Added

 Depends On||1596133, 1596135, 1596134



-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/IZD5SPUPOG2GKJG4KEL33UTISCWKZM5X/

[Bug 1596132] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip [fedora-all]

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1596132

Cedric Buissart  changed:

   What|Removed |Added

 Blocks||1591449 (CVE-2018-10860)




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1591449
[Bug 1591449] CVE-2018-10860 perl-Archive-Zip: Directory traversal in
Archive::Zip
-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/RFDLCMMNXIAWSUOLFGVEEVAT2FPCPAYY/

[Bug 1591449] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1591449

Cedric Buissart  changed:

   What|Removed |Added

 Depends On||1596131, 1596132



--- Comment #7 from Cedric Buissart  ---
Created perl-Archive-Zip tracking bugs for this issue:

Affects: fedora-all [bug 1596132]


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1596132
[Bug 1596132] CVE-2018-10860 perl-Archive-Zip: Directory traversal in
Archive::Zip [fedora-all]
-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/6RPWA75BVKYJPBGVF2A736JETSXFD23Y/

[Bug 1596132] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip [fedora-all]

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1596132



--- Comment #1 from Cedric Buissart  ---
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1591449,1596132

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

==

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/KBMZKPQ4J4LWSDCBM26L46YHK4ZGVCPM/

[Bug 1591449] CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1591449

Cedric Buissart  changed:

   What|Removed |Added

  Group|security, qe_staff  |
 CC||al...@redhat.com,
   ||caillon+fedoraproject@gmail
   ||.com,
   ||john.j5l...@gmail.com,
   ||jples...@redhat.com,
   ||ka...@ucw.cz,
   ||mbar...@fastmail.com,
   ||perl-devel@lists.fedoraproj
   ||ect.org,
   ||perl-maint-l...@redhat.com,
   ||rhug...@redhat.com,
   ||rstr...@redhat.com,
   ||sandm...@redhat.com,
   ||st...@silug.org
Summary|EMBARGOED CVE-2018-10860|CVE-2018-10860
   |perl-Archive-Zip: Directory |perl-Archive-Zip: Directory
   |traversal in Archive::Zip   |traversal in Archive::Zip
 Whiteboard|impact=moderate,reported=20 |impact=moderate,public=2018
   |180614,source=redhat,cvss3= |0628,reported=20180614,sour
   |5.4/CVSS:3.0/AV:N/AC:L/PR:N |ce=redhat,cvss3=5.4/CVSS:3.
   |/UI:R/S:U/C:N/I:L/A:L,cwe=C |0/AV:N/AC:L/PR:N/UI:R/S:U/C
   |WE-22,rhel-5/perl-Archive-Z |:N/I:L/A:L,cwe=CWE-22,rhel-
   |ip=wontfix,rhel-6/perl-Arch |5/perl-Archive-Zip=wontfix,
   |ive-Zip=wontfix,rhel-7/perl |rhel-6/perl-Archive-Zip=won
   |-Archive-Zip=affected,rhel- |tfix,rhel-7/perl-Archive-Zi
   |8/perl-Archive-Zip=affected |p=affected,rhel-8/perl-Arch
   |,fedora-all/perl-Archive-Zi |ive-Zip=affected,fedora-all
   |p=affected,rhscl-3/rh-perl5 |/perl-Archive-Zip=affected,
   |26-perl-Archive-Tar=affecte |rhscl-3/rh-perl526-perl-Arc
   |d,rhscl-3/rh-perl524-perl-A |hive-Tar=affected,rhscl-3/r
   |rchive-Tar=affected,rhscl-3 |h-perl524-perl-Archive-Tar=
   |/rh-perl520-perl-Archive-Ta |affected,rhscl-3/rh-perl520
   |r=wontfix   |-perl-Archive-Tar=wontfix



-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/WXVBPSBHP4LZNG4C3OUUOEE5E4SEYAJL/

[Bug 1596132] New: CVE-2018-10860 perl-Archive-Zip: Directory traversal in Archive::Zip [fedora-all]

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1596132

Bug ID: 1596132
   Summary: CVE-2018-10860 perl-Archive-Zip: Directory traversal
in Archive::Zip [fedora-all]
   Product: Fedora
   Version: 28
 Component: perl-Archive-Zip
  Keywords: Security, SecurityTracking
  Severity: medium
  Priority: medium
  Assignee: jples...@redhat.com
  Reporter: cbuis...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: al...@redhat.com, caillon+fedoraproj...@gmail.com,
john.j5l...@gmail.com, jples...@redhat.com,
ka...@ucw.cz, mbar...@fastmail.com,
perl-devel@lists.fedoraproject.org,
rhug...@redhat.com, rstr...@redhat.com,
sandm...@redhat.com, st...@silug.org



-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org/message/ECOBT36U2WPWOZVYOQ6SQUJXZLIEQAKS/

Re: Heads up: Python 3.7 rebuild in progress

2018-06-28 Thread Alfredo Moralejo Alonso 
On Mon, Jun 25, 2018 at 3:45 PM, Miro Hrončok  wrote:

> On 19.6.2018 11:27, Miro Hrončok wrote:
>
>> On 13.6.2018 15:14, Miro Hrončok wrote:
>>
>>> I've just started to build the bootstrap sequence in a side tag
>>> (f29-python).
>>>
>>>
>> I'm now mass rebuilding everything. Will do a couple of rounds before I
>> will look at the logs. If you see you package failing for a
>> non-dependencies related reason, please try to fix it and rebuild it with:
>>
>>  fedpkg build --target=f29-python
>>
>> Feel free to open bugs, make sure to block PYTHON37 [1].
>>
>> [1] http://bugzilla.redhat.com/show_bug.cgi?id=PYTHON37
>>
>
> Hi.
>
> We have 170 packages with blocked dependencies.
> We also have 176 packages that fail to build from source (+ ~10 more that
> are being handled).
>
> I need your help, I cannot possibly fix 178 packages.
>
> I've opened bugzillas for some, but let me ask you via e-mail before I go
> file 176 of them.
>
> Common problems:
>
>  * RuntimeError: generator raised StopIteration
>https://www.python.org/dev/peps/pep-0479/
>Solution: return instead (works with 2.7 as well)
>
>  * Syntax Error: async, await
>Those are reserved keywords now
>https://www.python.org/dev/peps/pep-0492/
>Solution: Rename. Add a wrapper if it's part of an API.
>
>
> If you fix your package, please build it in the side tag (fedpkg build
> --target=f29-python) and check what buildrequires it and maybe needs a
> rebuild as well (feel free to ping me for that part).
>
>
> The list of packages that FTBFS for non dependency reasons:
>
> Maintainers by package:
>
> python-kubernetesamoralej - affected by Syntax Error: async, await -
> just reported upstream in
> https://github.com/kubernetes-client/python/issues/558
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/KC3HT5CQB7UZVEBUFSKVKIY46HSX5RGI/

Re: Packages with scriptlets which call ldconfig

2018-06-28 Thread Till Hofmann 


On 06/28/2018 03:30 AM, Jason L Tibbitts III wrote:
> In Fedora 28 and newer, it is no longer necessary for most packages
> which install shared libraries to have scriptlets which call ldconfig:
> https://fedoraproject.org/wiki/Packaging:Scriptlets#Shared_Libraries
> 
> For your convenience, I ran the find-ldconfig-calls script from
> https://pagure.io/fedora-misc-package-utilities to find all source
> packages in rawhide which produce binary packages with scriptlets that
> call ldconfig.  I found 2239 packages.  Due to the length of this list,
> I only did spot checks for correctness, so please accept my apologies if
> some packages are misidentified (but let me know so that I can correct
> the script).

Not strictly a script error: I already updated most of my packages
without rebuilding them, so they are all false positives. I guess I'm
not the only one who updated the Spec without a rebuild, so I'm not sure
checking the source packages is the best approach. Is it possible to
directly check the Spec?

Kind regards
Till
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/7NEVZG7PXTBAOUYJ72R7LJIGMIYVZXQ2/

Fedora rawhide compose report: 20180627.n.0 changes

2018-06-28 Thread Fedora Rawhide Report 
OLD: Fedora-Rawhide-20180625.n.0
NEW: Fedora-Rawhide-20180627.n.0

= SUMMARY =
Added images:18
Dropped images:  0
Added packages:  17
Dropped packages:1
Upgraded packages:   189
Downgraded packages: 0

Size of added packages:  66.71 MiB
Size of dropped packages:216.43 KiB
Size of upgraded packages:   9.02 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   63.65 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Xfce live i386
Path: Spins/i386/iso/Fedora-Xfce-Live-i386-Rawhide-20180627.n.0.iso
Image: Scientific_KDE live i386
Path: Labs/i386/iso/Fedora-Scientific_KDE-Live-i386-Rawhide-20180627.n.0.iso
Image: SoaS live i386
Path: Spins/i386/iso/Fedora-SoaS-Live-i386-Rawhide-20180627.n.0.iso
Image: Robotics live i386
Path: Labs/i386/iso/Fedora-Robotics-Live-i386-Rawhide-20180627.n.0.iso
Image: Design_suite live i386
Path: Labs/i386/iso/Fedora-Design_suite-Live-i386-Rawhide-20180627.n.0.iso
Image: LXQt live i386
Path: Spins/i386/iso/Fedora-LXQt-Live-i386-Rawhide-20180627.n.0.iso
Image: Server boot i386
Path: Server/i386/iso/Fedora-Server-netinst-i386-Rawhide-20180627.n.0.iso
Image: Workstation boot i386
Path: 
Workstation/i386/iso/Fedora-Workstation-netinst-i386-Rawhide-20180627.n.0.iso
Image: Everything boot i386
Path: 
Everything/i386/iso/Fedora-Everything-netinst-i386-Rawhide-20180627.n.0.iso
Image: Jam_KDE live i386
Path: Labs/i386/iso/Fedora-Jam_KDE-Live-i386-Rawhide-20180627.n.0.iso
Image: Container_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Base-Rawhide-20180627.n.0.s390x.tar.xz
Image: LXDE live i386
Path: Spins/i386/iso/Fedora-LXDE-Live-i386-Rawhide-20180627.n.0.iso
Image: Workstation live i386
Path: Workstation/i386/iso/Fedora-Workstation-Live-i386-Rawhide-20180627.n.0.iso
Image: Server dvd i386
Path: Server/i386/iso/Fedora-Server-dvd-i386-Rawhide-20180627.n.0.iso
Image: Cinnamon live i386
Path: Spins/i386/iso/Fedora-Cinnamon-Live-i386-Rawhide-20180627.n.0.iso
Image: KDE live i386
Path: Spins/i386/iso/Fedora-KDE-Live-i386-Rawhide-20180627.n.0.iso
Image: Python_Classroom live i386
Path: Labs/i386/iso/Fedora-Python-Classroom-Live-i386-Rawhide-20180627.n.0.iso
Image: Security live i386
Path: Labs/i386/iso/Fedora-Security-Live-i386-Rawhide-20180627.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: R-foreach-1.4.4-1.fc29
Summary: Provides Foreach Looping Construct for R
RPMs:R-foreach
Size:412.48 KiB

Package: R-itertools-0.1.3-1.fc29
Summary: Iterator Tools
RPMs:R-itertools
Size:125.00 KiB

Package: aom-1.0.0-1.fc29
Summary: Royalty-free next-generation video format
RPMs:aom aom-devel
Size:11.08 MiB

Package: freight-container-0-0.3.20180613gitd1d03af.fc29
Summary: RPM macro set and commands for creating containers using rpm-build/mock
RPMs:freight-container
Size:26.06 KiB

Package: ignition-0.26.0-0.2.git7610725.fc29
Summary: First boot installer and configuration tool
RPMs:ignition ignition-dracut
Size:28.26 MiB

Package: newsboat-2.12-1.fc29
Summary: RSS/Atom feed reader for the text console
RPMs:newsboat
Size:5.86 MiB

Package: perl-UUID-URandom-0.001-1.fc29
Summary: UUIDs based on /dev/urandom
RPMs:perl-UUID-URandom
Size:17.62 KiB

Package: rust-peg-0.5.4-1.fc29
Summary: Simple Parsing Expression Grammar (PEG) parser generator
RPMs:rust-peg rust-peg-devel
Size:1.34 MiB

Package: rust-unix_socket-0.5.0-1.fc29
Summary: Unix domain socket bindings
RPMs:rust-unix_socket-devel
Size:20.46 KiB

Package: rust-varlink-1.1.0-1.fc29
Summary: Client and server support for the varlink protocol
RPMs:rust-varlink rust-varlink-devel
Size:1.54 MiB

Package: rust-varlink-cli-1.0.3-1.fc29
Summary: Varlink command line tool
RPMs:varlink-cli
Size:3.75 MiB

Package: rust-varlink_parser-1.1.0-1.fc29
Summary: Crate for parsing varlink interface definition files
RPMs:rust-varlink_parser-devel
Size:26.60 KiB

Package: tiny-dnn-1.0.0-0.a3.3.fc29
Summary: Header only, dependency-free deep learning framework in C++14
RPMs:tiny-dnn-devel
Size:1.78 MiB

Package: vulkan-headers-1.1.77.0-1.fc29
Summary: Vulkan Header files and API registry
RPMs:vulkan-headers
Size:377.23 KiB

Package: vulkan-loader-1.1.77.0-4.fc29
Summary: Vulkan ICD desktop loader
RPMs:vulkan-loader vulkan-loader-devel
Size:847.00 KiB

Package: vulkan-tools-1.1.77.0-1.fc29
Summary: Vulkan tools
RPMs:vulkan-tools
Size:655.74 KiB

Package: vulkan-validation-layers-1.1.77.0-3.fc29
Summary: Vulkan validation layers
RPMs:vulkan-validation-layers
Size:10.65 MiB


= DROPPED PACKAGES =
Package: python-docker-py-1:1.10.6-8.fc29
Summary: An API client for docker written in Python
RPMs:python2-docker-py python3-docker-py
Size:216.43 KiB


= UPGRADED PACKAGES =
Package:  OpenStego-0.7.3-1.fc29
Old package:  OpenStego-0.7.2-1.fc28
Summary:  Free Steganography solution
RPMs:

F29 System Wide Change: CJK Default Fonts To Noto

2018-06-28 Thread Jan Kurik 
= Proposed System Wide Change: CJK Default Fonts To Noto =
https://fedoraproject.org/wiki/Changes/CJKDefaultFontsToNoto


Owner(s):
  * Akira TAGOH 
  * Peng Wu 


Changes the default fonts for Chinese, Japanese, and Korean (CJK)
languages to Google Noto.


== Detailed description ==
This proposal is to change the default fonts for CJK languages to
Google Noto and adopts OpenType Collection format to suppress disk
space increase as far as possible. Typefaces mapping will change as
described on the Change Proposal wiki page (Change wrangler note: the
description contains tables which are not easily convertible to text,
so please follow this link to check it:
https://fedoraproject.org/wiki/Changes/CJKDefaultFontsToNoto#Detailed_Description
):


== Scope ==
* Proposal owners:
** Update CJK fonts packages with the proper priority of fontconfig config files
** Update fonts group in comps [done]

* Other developers:
** For application package maintainers:
*** Any GUI applications that don't support TTC or OTC, would need to be fixed.

* Release engineering:
#7592 [https://pagure.io/releng/issue/7592]

** List of deliverables:
All of the installable images should be affected

* Policies and guidelines:
N/A

* Trademark approval:
N/A
-- 
Jan Kuřík
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/4HOZ5PUZXMNRACCM5QHAO5P2QTN2L2TS/

F29 System Wide Change: CJK Default Fonts To Noto

2018-06-28 Thread Jan Kurik 
= Proposed System Wide Change: CJK Default Fonts To Noto =
https://fedoraproject.org/wiki/Changes/CJKDefaultFontsToNoto


Owner(s):
  * Akira TAGOH 
  * Peng Wu 


Changes the default fonts for Chinese, Japanese, and Korean (CJK)
languages to Google Noto.


== Detailed description ==
This proposal is to change the default fonts for CJK languages to
Google Noto and adopts OpenType Collection format to suppress disk
space increase as far as possible. Typefaces mapping will change as
described on the Change Proposal wiki page (Change wrangler note: the
description contains tables which are not easily convertible to text,
so please follow this link to check it:
https://fedoraproject.org/wiki/Changes/CJKDefaultFontsToNoto#Detailed_Description
):


== Scope ==
* Proposal owners:
** Update CJK fonts packages with the proper priority of fontconfig config files
** Update fonts group in comps [done]

* Other developers:
** For application package maintainers:
*** Any GUI applications that don't support TTC or OTC, would need to be fixed.

* Release engineering:
#7592 [https://pagure.io/releng/issue/7592]

** List of deliverables:
All of the installable images should be affected

* Policies and guidelines:
N/A

* Trademark approval:
N/A
-- 
Jan Kuřík
JBoss EAP 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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/4HOZ5PUZXMNRACCM5QHAO5P2QTN2L2TS/

[Bug 1594993] perl-Event-RPC-1.09 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1594993



--- Comment #6 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb8982959e

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: ${hyperkitty_url}

[Bug 1595972] perl-Event-RPC-1.10 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595972



--- Comment #3 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc27 has been submitted as an update to Fedora 27.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-1e3a1eca9d

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: ${hyperkitty_url}

[Bug 1595972] perl-Event-RPC-1.10 is available

2018-06-28 Thread bugzilla 
https://bugzilla.redhat.com/show_bug.cgi?id=1595972



--- Comment #2 from Fedora Update System  ---
perl-Event-RPC-1.10-1.fc28 has been submitted as an update to Fedora 28.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fb8982959e

-- 
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
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: ${hyperkitty_url}

  1   2   >