[389-devel] 389 DS nightly 2019-06-08 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2019/06/08/report-389-ds-base-1.4.1.3-20190607git3ca307d.fc30.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

[Bug 1710585] Not validating valid IPv6 CIDR addresses

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version||perl-Net-CIDR-0.20-1.el7
 Resolution|--- |ERRATA
Last Closed||2019-06-08 01:20:05



--- Comment #3 from Fedora Update System  ---
perl-Net-CIDR-0.20-1.el7 has been pushed to the Fedora EPEL 7 stable
repository. If problems still persist, please make note of it in this bug
report.

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

[Bug 1718093] perl-Graphics-ColorNames-3.5.0 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Graphics-ColorNames-3.5.0-1.fc30 has been pushed to the Fedora 30 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-2019-b93226a64e

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

[389-devel] please review: PR 50432 - Fix latest coverity warnings

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/50432
___
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

Re: Qt 5.12.3 coming to rawhide

[Richard Shaw]

On Tue, Jun 4, 2019 at 6:30 AM Jan Grulich  wrote:

> Hi,
>
> I started update process in rawhide to update all Qt modules to 5.12.3 and
> later I will rebuild all packages depending on Qt private stuff. You may
> experience build failures until the whole update process is done, which
> should
> be hopefully tomorrow.
>

What's the current status of the rebuild? I just got PySide2 approved
(still waiting on repo generation) and will need to update from 5.12.1 to
5.12.3.

Thanks,
Richard
___
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

build failure using boost-python3 on ppc64le

[Carl Byington via devel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I am trying a scratch build of libpst, and I don't understand the
error.

http://koji.fedoraproject.org/koji/taskinfo?taskID=35373272

This package uses boost-python3. On x86, the build log contains:

  make[2]: Entering directory
  '/builddir/build/BUILD/libpst-0.6.72/python'
  /bin/sh ../libtool  --tag=CXX   --mode=link g++  -O2 -g -pipe -Wall
  -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
  -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong
  -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
  -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
  -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
  -module  -avoid-version -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -o _libpst.la -rpath
  /usr/lib64/python3.7/site-packages python-libpst.lo -lboost_python37
  ../src/libpst.la -lpthread
  libtool: link: g++  -fPIC -DPIC -shared -nostdlib
  /usr/lib/gcc/x86_64-redhat-linux/9/../../../../lib64/crti.o
  /usr/lib/gcc/x86_64-redhat-linux/9/crtbeginS.o  .libs/python-libpst.o
  -Wl,-rpath -Wl,/builddir/build/BUILD/libpst-0.6.72/src/.libs
  -lboost_python37 ../src/.libs/libpst.so -lpthread
  -L/usr/lib/gcc/x86_64-redhat-linux/9
  -L/usr/lib/gcc/x86_64-redhat-linux/9/../../../../lib64
  -L/lib/../lib64
  -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/9/../../..
  -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-redhat-linux/9/crtendS.o
  /usr/lib/gcc/x86_64-redhat-linux/9/../../../../lib64/crtn.o
  -Wl,-z,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -g
  -fstack-protector-strong -grecord-gcc-switches
  -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
  -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
  -Wl,-z -Wl,relro -Wl,--as-needed -Wl,-z -Wl,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld   -Wl,-soname
  -Wl,_libpst.so -o .libs/_libpst.so


which works. On ppc, the build log contains:


  make[2]: Entering directory
  '/builddir/build/BUILD/libpst-0.6.72/python'
  /bin/sh ../libtool  --tag=CXX   --mode=link g++  -O2 -g -pipe -Wall
  -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
  -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong
  -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
  -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8
  -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection
  -module  -avoid-version -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -o _libpst.la -rpath
  /usr/lib64/python3.7/site-packages python-libpst.lo -l
  ../src/libpst.la
  -lpthread
  libtool: link: g++  -fPIC -DPIC -shared -nostdlib
  /usr/lib/gcc/ppc64le-redhat-linux/9/../../../../lib64/crti.o
  /usr/lib/gcc/ppc64le-redhat-linux/9/crtbeginS.o
  .libs/python-libpst.o
   -Wl,-rpath -Wl,/builddir/build/BUILD/libpst-0.6.72/src/.libs -l
  ../src/.libs/libpst.so -lpthread
  -L/usr/lib/gcc/ppc64le-redhat-linux/9
  -L/usr/lib/gcc/ppc64le-redhat-linux/9/../../../../lib64
  -L/lib/../lib64
  -L/usr/lib/../lib64 -L/usr/lib/gcc/ppc64le-redhat-linux/9/../../..
  -lstdc++ -lm -lc -lgcc_s
  /usr/lib/gcc/ppc64le-redhat-linux/9/crtendS.o
  /usr/lib/gcc/ppc64le-redhat-linux/9/../../../../lib64/crtn.o
  -Wl,-z,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -g
  -fstack-protector-strong -grecord-gcc-switches
  -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
  -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8
  -mtune=power8 -Wl,-z -Wl,relro -Wl,--as-needed -Wl,-z -Wl,now
  -specs=/usr/lib/rpm/redhat/redhat-hardened-ld   -Wl,-soname
  -Wl,_libpst.so -o .libs/_libpst.so


which fails. Notice that on x86, we have

BUILD/libpst-0.6.72/src/.libs
- -lboost_python37 ../src/.libs/libpst.so -lpthread

but on ppc, we have

BUILD/libpst-0.6.72/src/.libs -l
../src/.libs/libpst.so -lpthread


The -lboost_python37 turns into a plain -l, so the next token
../src/.libs/libpst.so is taken as a library name which fails.




-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAlz6qS0ACgkQL6j7milTFsGulgCfUhXGs70fysofV8NRlI9LgUlP
mCEAnRmIz6burXpZFkwCpB+7LbIyH4uu
=coL1
-END PGP 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

Re: HEADS UP: libgit 0.28

[Igor Gnatenko]

Except that it doesn't scale with multiple people working with different
side tags.

On Fri, Jun 7, 2019, 18:51 Miro Hrončok  wrote:

> On 07. 06. 19 17:57, Adam Williamson wrote:
> > On Wed, 2019-06-05 at 18:27 +0200, Igor Gnatenko wrote:
> >> Hello,
> >>
> >> I'm going to build libgit 0.28.x in rawhide and rebuild all affected
> >> packages somewhere this week.
> >
> > Unfortunately your rebuild of kf5-ktexteditor failed, and that broke
> > today's Rawhide compose:
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=35366912
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=35366363
> >
> > We really need a better system for doing these. :(
>
> I only we could do this in an isolated Koji tag and merge it only when it
> goes
> well. Oh wait.
>
> --
> 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
>
___
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

Re: Rawhide bugs => F30?

[Ben Cotton]

On Fri, Jun 7, 2019 at 1:28 PM Vít Ondruch  wrote:

> Interesting. I was specifically referring to this bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1675902
>
> So may be the FTBFS mass filling missed the deadline? Or was there some
> exception?
>
Well it looks like it should have been caught. It was filed on
2019-02-11 and the rawhide->F30 branch happened on 2019-02-19. I don't
see any obvious reason it would have been excluded, so it may have
been a transient issue in Bugzilla as the mass-editing was underway.
This is usually done via the bugzilla web interface, not the Perl
scripts handed down from PgM to PgM since time immemorial, so it may
have errored without an obvious indication. I'll make a note to myself
to do a second pass the next time to catch any stragglers.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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

Re: Rawhide bugs => F30?

[Adam Williamson]

On Fri, 2019-06-07 at 13:16 -0400, Ben Cotton wrote:
> Vit,
> 
> Rawhide bugs are moved during the development cycle of the next
> stable. So bugs filed against rawhide will become F31 bugs on
> 2019-08-13.

Ah, yeah, to clarify my message - the Rawhide -> F*30* transition (as
given in Subject) happened already. As Ben says, Rawhide -> F*31*
doesn't happen for a while.
-- 
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

Re: Rawhide bugs => F30?

[Vít Ondruch]

Dne 07. 06. 19 v 19:16 Ben Cotton napsal(a):
> Vit,
>
> Rawhide bugs are moved during the development cycle of the next
> stable. So bugs filed against rawhide will become F31 bugs on
> 2019-08-13.
>
>

Interesting. I was specifically referring to this bug:

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

So may be the FTBFS mass filling missed the deadline? Or was there some
exception?


Vít
___
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

Re: Rawhide bugs => F30?

[Ben Cotton]

Vit,

Rawhide bugs are moved during the development cycle of the next
stable. So bugs filed against rawhide will become F31 bugs on
2019-08-13.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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

Re: Rawhide bugs => F30?

[Adam Williamson]

On Fri, 2019-06-07 at 18:50 +0200, Vít Ondruch wrote:
> Hi everybody,
> 
> At release of stable version, the Rawhide bugs used to be moved to the
> stable version. Does this going to happen? It is a bit late already 

It already did happen. If your bug wasn't moved then it was excepted
for some reason, there are a few rules for *not* moving bugs.
-- 
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

Re: HEADS UP: libgit 0.28

[Adam Williamson]

On Fri, 2019-06-07 at 18:04 +0200, Miro Hrončok wrote:
> On 07. 06. 19 17:57, Adam Williamson wrote:
> > On Wed, 2019-06-05 at 18:27 +0200, Igor Gnatenko wrote:
> > > Hello,
> > > 
> > > I'm going to build libgit 0.28.x in rawhide and rebuild all affected
> > > packages somewhere this week.
> > 
> > Unfortunately your rebuild of kf5-ktexteditor failed, and that broke
> > today's Rawhide compose:
> > 
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=35366912
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=35366363
> > 
> > We really need a better system for doing these. :(
> 
> I only we could do this in an isolated Koji tag and merge it only when it 
> goes 
> well. Oh wait.

Well yes, but that process is pretty awkward at present. It needs to be
much easier.
-- 
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

Rawhide bugs => F30?

[Vít Ondruch]

Hi everybody,

At release of stable version, the Rawhide bugs used to be moved to the
stable version. Does this going to happen? It is a bit late already 


Vít
___
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

Summary/Minutes from today's FESCo Meeting (2019-06-07)

[Zbigniew Jędrzejewski-Szmek]

Meeting summary
---
* init process  (zbyszek, 15:02:03)

* #2063 F31 Change: Ibus-typing-booster default for Indian languages
  (zbyszek, 15:03:54)
  * LINK: https://pagure.io/fesco/issue/2063   (zbyszek, 15:03:59)
  * AGREED: This change is rejected due to lack of response. Change
owner is free to resubmit it again. (+5, 0, 0)  (zbyszek, 15:05:48)

* #2140 F31 System-Wide Change: RPM 4.15  (zbyszek, 15:05:58)
  * LINK: https://pagure.io/fesco/issue/2140   (zbyszek, 15:05:58)
  * AGREED: Change is accepted (+6, 1, -0)  (zbyszek, 15:23:51)
  * ACTION: mhroncok to put a I've told you so note in the top drawer
(mhroncok, 15:24:21)

* #2139 F30: change default stream for avocado module  (zbyszek,
  15:24:44)
  * LINK: https://pagure.io/fesco/issue/2139   (zbyszek, 15:24:44)
  * the request has already been withdrawn  (zbyszek, 15:28:17)

* #2135 set default module stream for cri-o  (zbyszek, 15:28:22)
  * LINK: https://pagure.io/fesco/issue/2135   (zbyszek, 15:28:23)

* #2136 F32 Self-Contained Change: Track Changes in Taiga  (zbyszek,
  15:35:46)
  * LINK: https://pagure.io/fesco/issue/2136   (zbyszek, 15:35:47)
  * LINK:
https://teams.fedoraproject.org/project/bcotton-test-changes-tracker/issue/3
(bcotton, 15:53:04)
  * LINK:

https://teams.fedoraproject.org/project/bcotton-test-changes-tracker/us/1?kanban-status=29
(bcotton, 15:54:07)
  * ACTION: bcotton to test the issue filing process with mhroncok and
vondruch.  (zbyszek, 16:06:21)
  * We'll revisit next week.  (zbyszek, 16:06:43)

* Next week's chair  (zbyszek, 16:06:53)
  * ACTION: contyk will chair next meeting  (zbyszek, 16:07:22)

* Open Floor  (zbyszek, 16:07:36)
  * LINK: http://elections.fedoraproject.org/   (bcotton, 16:08:50)
  * Voting closes in 13 days  (zbyszek, 16:09:04)

Meeting ended at 16:10:09 UTC.


Action Items

* mhroncok to put a I've told you so note in the top drawer
* bcotton to test the issue filing process with mhroncok and vondruch.
* contyk will chair next meeting

Minutes: 
https://meetbot.fedoraproject.org/fedora-meeting/2019-06-07/fesco.2019-06-07-15.02.html
Minutes (text): 
https://meetbot.fedoraproject.org/fedora-meeting/2019-06-07/fesco.2019-06-07-15.02.txt
Log: 
https://meetbot.fedoraproject.org/fedora-meeting/2019-06-07/fesco.2019-06-07-15.02.log.html
___
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

Re: The Fedora Packaging Guidelines point at the old FHS site

[Chris Murphy]

On Fri, Jun 7, 2019 at 8:31 AM David Howells  wrote:
>
> The FHS is now maintained by the Linux Foundation:
>
> https://wiki.linuxfoundation.org/lsb/fhs

That page is also stale.

"Our goal is to release FHS 3.0 by July 1 if possible. "
lsb/fhs.txt · Last modified: 2016/07/19 01:23 (external edit)

FHS 3.0 was released in June 2015.

Maybe this is the better reference:
https://wiki.linuxfoundation.org/lsb/start
or
https://wiki.linuxfoundation.org/lsb/fhs-30




-- 
Chris Murphy
___
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

Re: HEADS UP: libgit 0.28

[Miro Hrončok]

On 07. 06. 19 17:57, Adam Williamson wrote:

On Wed, 2019-06-05 at 18:27 +0200, Igor Gnatenko wrote:

Hello,

I'm going to build libgit 0.28.x in rawhide and rebuild all affected
packages somewhere this week.


Unfortunately your rebuild of kf5-ktexteditor failed, and that broke
today's Rawhide compose:

https://koji.fedoraproject.org/koji/taskinfo?taskID=35366912
https://koji.fedoraproject.org/koji/taskinfo?taskID=35366363

We really need a better system for doing these. :(


I only we could do this in an isolated Koji tag and merge it only when it goes 
well. Oh wait.


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

Re: HEADS UP: libgit 0.28

[Adam Williamson]

On Wed, 2019-06-05 at 18:27 +0200, Igor Gnatenko wrote:
> Hello,
> 
> I'm going to build libgit 0.28.x in rawhide and rebuild all affected
> packages somewhere this week.

Unfortunately your rebuild of kf5-ktexteditor failed, and that broke
today's Rawhide compose:

https://koji.fedoraproject.org/koji/taskinfo?taskID=35366912
https://koji.fedoraproject.org/koji/taskinfo?taskID=35366363

We really need a better system for doing these. :(
-- 
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

The Fedora Packaging Guidelines point at the old FHS site

[David Howells]

Hi,

The packaging guidelines pages:

https://docs.fedoraproject.org/en-US/packaging-guidelines/

https://fedoraproject.org/w/index.php?title=Packaging:Guidelines=528452#Filesystem_Layout

still point at the old Filesystem Hierarchy Standard (FHS) site:

http://www.pathname.com/fhs/

This hasn't been updated since something like 2004.

The FHS is now maintained by the Linux Foundation:

https://wiki.linuxfoundation.org/lsb/fhs

David
___
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

[389-devel] please review: PR 50430 - nsSSL3Ciphers is limited to 1024 characters

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/50430
___
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

Re: Another ceph build stuck in pending testing, four days

[Kaleb Keithley]

Thanks for opening the ticket, but the update is still stuck, now going on
nine days.

Would someone with the necessary privs please kick it.

Thanks


On Mon, Jun 3, 2019 at 1:52 PM Randy Barlow 
wrote:

> On Sun, 2019-06-02 at 18:03 -0400, Kaleb Keithley wrote:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2019-60ba61b5ab
> >
> > Why does this happen every time?
> >
> > Would someone please kick it? Thanks
>
> I filed an issue about this for you:
>
> https://pagure.io/fedora-infrastructure/issue/7871
> ___
> 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
>
___
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

Re: Tagging commit hashes of Koji builds in dist-git

[Neal Gompa]

On Fri, Jun 7, 2019 at 8:09 AM clime  wrote:
>
> On Thu, 6 Jun 2019 at 13:53, Florian Weimer  wrote:
> >
> > Is there a reason why we do not tag dist-git commits, using a name which
> > is derived from the NEVR from a Koji build?
>
> Interesting idea. I am soon coming with a proposal of the annotated tags
> being created by packagers and storing changelog automatically in them.
>
> These tags would have name derived automatically from Name-Version-Release
> put in the spec file and constitute a basically a package release
> record in DistGit.
>
> The information in Koji would then be derivative of it. I guess this is 
> another
> way how to go around things.
>

This is very similar to what Igor and I had been thinking of doing, too.



-- 
真実はいつも一つ！/ 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

Re: Tagging commit hashes of Koji builds in dist-git

[clime]

On Thu, 6 Jun 2019 at 13:53, Florian Weimer  wrote:
>
> Is there a reason why we do not tag dist-git commits, using a name which
> is derived from the NEVR from a Koji build?

Interesting idea. I am soon coming with a proposal of the annotated tags
being created by packagers and storing changelog automatically in them.

These tags would have name derived automatically from Name-Version-Release
put in the spec file and constitute a basically a package release
record in DistGit.

The information in Koji would then be derivative of it. I guess this is another
way how to go around things.

clime

>
> How well does Git scale with thousands of tags?
>
> Thanks,
> Florian
> ___
> 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
___
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

[EPEL-devel] Re: What version of gcc is available in EPEL-7?

[José Abílio Matos]

On Friday, 7 June 2019 10.22.14 WEST Dominik 'Rathann' Mierzejewski wrote:
> Yes. Please check the mkvtoolnix package, for example. In short:
> 
> BuildRequires: devtoolset-7-gcc-c++
> ...
> %build
> . /opt/rh/devtoolset-7/enable
> 
> Should be enough. I haven't tried devtoolset-8 yet. I'll try it when I
> do the next mkvtoolnix update.
> 
> Regards,
> Dominik

Right.

Thank you very much to Florian and Dominik for the quick answer. :-)

Best regards,
-- 
José Abílio

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: What version of gcc is available in EPEL-7?

[Dominik 'Rathann' Mierzejewski]

On Friday, 07 June 2019 at 11:01, José Abílio Matos wrote:
> On Friday, 7 June 2019 09.50.08 WEST Florian Weimer wrote:
> > There are publicly available builds of GCC 8 for CentOS:
> > 
> >   
> > 
> > It still uses the old C++ ABI.   and many other things will work,
> > though.
> > 
> > Thanks,
> > Florian
> 
> Can we use those packages as BR (build requirements) when building for epel-7?
> 
> That is my main concern. I would like to make lyx-2.4 available also for 
> epel-7.

Yes. Please check the mkvtoolnix package, for example. In short:

BuildRequires: devtoolset-7-gcc-c++
...
%build
. /opt/rh/devtoolset-7/enable

Should be enough. I haven't tried devtoolset-8 yet. I'll try it when I
do the next mkvtoolnix update.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  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
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org

[389-devel] Re: How to create a user with certificate with lib389

[William Brown]

I haven't read the link but maybe there is some confusion about TLS binding 
here. You do the create_rsa_user and that only set's up the certificates.

> On 4 Jun 2019, at 17:51, Anuj Borah  wrote:
> 
> @William Brown
>  
> Thanks , I am doing the same . Trying to follow it . (i have make this script 
> 99% pass)
>  
> But its way too old . It uses some like :
> 
> standalone.nss_ssl.create_rsa_user('testuser')    not valid 
> (NssSsl(standalone).create_rsa_user('testuser'))
> 
> standalone.nss_ssl.get_rsa_user('testuser')   -- not valid 
> (NssSsl(standalone).get_rsa_user('testuser'))

IIRC this syntax is valid, but maybe the linking type was removed. 

> 
> standalone.openConnection ---  I dont know what is it . May be bind.

Yes, i think this is bind now. If you grep for create_rsa_user in the tests you 
may find another example. 

> 
> And Most importantly, after i have make this script 99% pass . I am not able 
> to see the usercertificate field in the test user that was created during the 
> test . while i do _unsafe_raw_entry()

Because you don't need it. The certificate's cn is mapped to the cn in the 
directory, and then because the certificate was issued be the ca, it "confirms" 
the users identity. No userCertificate attribute required.

There is a configuration that DOES require the certificate to not only be 
signed, but also in userCertificate for binary matching, but this is a 
configuration option, not the default. I seem to recall helping document all 
this with Marc, so it should be in the latest RHDS documentation. Generally 
though, the userCertificate attribute today would be used to allow a client 
like SSSD to read the userCertificate to allow smartCard authentication to a 
workstation. 

Does that help a bit? 

> 
> Also mind changing the lib389 doc 
> https://spichugi.fedorapeople.org/html/guidelines.html#setting-up-ssl-tls . 
> Its the same test case given there , which is not relevant now .
> 
> Regards
> Anuj Borah
> 
> 
> 
> 
> 
> 
> 
> On Tue, Jun 4, 2019 at 9:08 PM William Brown  wrote:
> I'm currently traveling at the moment, but I can have a look later to update 
> this to work on latest lib389 etc.
> 
> You can read it and use it as an example though, even if it doesn't pass ... 
> 
> 
> 
> 
> > On 4 Jun 2019, at 16:32, Anuj Borah  wrote:
> > 
> > @William Brown
> >  
> > This test script does not pass . Its too old .
> > 
> > Regards
> > Anuj Borah
> > 
> > On Tue, Jun 4, 2019 at 8:00 PM William Brown  wrote:
> > Have a look at this test case if you want to do usercertificate generation 
> > and authentication :) 
> > 
> > https://pagure.io/389-ds-base/blob/master/f/src/lib389/lib389/tests/tls_external_test.py
> > 
> > > On 4 Jun 2019, at 14:31, Anuj Borah  wrote:
> > > 
> > > Hi all,
> > > 
> > > Let say i want to create a user with userCertificate fileld. My user will 
> > > look like bellow.
> > > 
> > > users_people = UserAccounts(topo.standalone, DEFAULT_SUFFIX)
> > > users_people.create(properties={
> > > 'uid': 'certUser2',
> > > 'cn': 'CUser2',
> > > 'sn': 'CertificateUser2',
> > > 'givenName': 'CU2',
> > > 'description': "This is certUser2's description",
> > > 'mail': 'certus...@example.com',
> > > 'userPassword': PW_DM,
> > > 'userCertificate': 'some_cert_+++NUhz+Rigq7xT5g0Jqo1gXq1jJFdCw==',
> > > 'manager': f'uid=certUser2,ou=People,{DEFAULT_SUFFIX}',
> > > 'homeDirectory': '/home/' + 'certUser2',
> > > 'uidNumber': '1000',
> > > 'gidNumber': '2000'
> > > })
> > > 
> > > Here i have put userCertificate field manually (which i dont want to do). 
> > > But how can i achieve this without putting userCertificate field manually 
> > > . Like create a user and userCertificate field will be auto field with 
> > > auto generated certificates .  
> > > 
> > > Regards
> > > Anuj Borah
> > > ___
> > > 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
> > 
> > —
> > Sincerely,
> > 
> > William Brown
> > 
> > Senior Software Engineer, 389 Directory Server
> > SUSE Labs
> > ___
> > 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
> 
> —
> Sincerely,
> 
> William Brown
> 
> Senior Software Engineer, 389 

[EPEL-devel] Re: What version of gcc is available in EPEL-7?

[José Abílio Matos]

On Friday, 7 June 2019 09.50.08 WEST Florian Weimer wrote:
> There are publicly available builds of GCC 8 for CentOS:
> 
>   
> 
> It still uses the old C++ ABI.   and many other things will work,
> though.
> 
> Thanks,
> Florian

Can we use those packages as BR (build requirements) when building for epel-7?

That is my main concern. I would like to make lyx-2.4 available also for 
epel-7.

Thank you, :-)
-- 
José Abílio

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: What version of gcc is available in EPEL-7?

[Florian Weimer]

* José Abílio Matos:

>   what versions, other than 4.8.5, of gcc are avaialble for EPEL-7?
>
> My question is due to LyX that is starting the release procedure for 2.4 and 
> there is a consideration for the minimum supported gcc supported.
>
> The interest in gcc (actually g++) is due to the fact that the regex library 
> in 4.8 has problems.

There are publicly available builds of GCC 8 for CentOS:

  

It still uses the old C++ ABI.   and many other things will work,
though.

Thanks,
Florian
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org

Re: Tagging commit hashes of Koji builds in dist-git

[Florian Weimer]

* Bruno Wolff, III:

> On Fri, Jun 07, 2019 at 08:37:57 -,
>  Petr Pisar  wrote:
>>On 2019-06-06, Stephen Gallagher  wrote:
>>> Might be worth asking if there's a reason to need this offline. If the
>>> exact commit ID is stored in Koji and is authoritative, also tagging
>>> it into git might be convenient for offline purposes. The fact that
>>> it's not immutable is probably not an issue as long as the
>>> authoritative site *is*. (e.g. The same script that gets the hash from
>>> Koji could also detect if someone manually changed it in git, which
>>> would probably qualify as suspicious behavior.)
>>
>>If tags in dist-git could disagree with Koji, people could not rely on
>>them and would use Koji instead rendering tags in dist-tag useless.
>
> Would having signed tags help?

No, the tags must recide in a namespace, and dist-git (i.e.,
src.fedoraproject.org) must restrict who can push into that namespace.

Thanks,
Florian
___
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

Re: Tagging commit hashes of Koji builds in dist-git

[Bruno Wolff III]

On Fri, Jun 07, 2019 at 08:37:57 -,
 Petr Pisar  wrote:

On 2019-06-06, Stephen Gallagher  wrote:

Might be worth asking if there's a reason to need this offline. If the
exact commit ID is stored in Koji and is authoritative, also tagging
it into git might be convenient for offline purposes. The fact that
it's not immutable is probably not an issue as long as the
authoritative site *is*. (e.g. The same script that gets the hash from
Koji could also detect if someone manually changed it in git, which
would probably qualify as suspicious behavior.)


If tags in dist-git could disagree with Koji, people could not rely on
them and would use Koji instead rendering tags in dist-tag useless.


Would having signed tags help?
___
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

Re: Tagging commit hashes of Koji builds in dist-git

[Petr Pisar]

On 2019-06-06, Stephen Gallagher  wrote:
> Might be worth asking if there's a reason to need this offline. If the
> exact commit ID is stored in Koji and is authoritative, also tagging
> it into git might be convenient for offline purposes. The fact that
> it's not immutable is probably not an issue as long as the
> authoritative site *is*. (e.g. The same script that gets the hash from
> Koji could also detect if someone manually changed it in git, which
> would probably qualify as suspicious behavior.)

If tags in dist-git could disagree with Koji, people could not rely on
them and would use Koji instead rendering tags in dist-tag useless.

-- Petr
___
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

[Bug 1718093] perl-Graphics-ColorNames-3.5.0 is available

[bugzilla]

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



--- Comment #2 from Fedora Update System  ---
FEDORA-2019-b93226a64e has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-b93226a64e

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

[Bug 1718093] perl-Graphics-ColorNames-3.5.0 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Graphics-ColorNames-3.
   ||5.0-1.fc31



--- Comment #1 from Petr Pisar  ---
A bug-fix release suitable for Fedora ≥ 30.

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

[Bug 1718093] perl-Graphics-ColorNames-3.5.0 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

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



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

[EPEL-devel] What version of gcc is available in EPEL-7?

[José Abílio Matos]

Hi,
what versions, other than 4.8.5, of gcc are avaialble for EPEL-7?

My question is due to LyX that is starting the release procedure for 2.4 and 
there is a consideration for the minimum supported gcc supported.

The interest in gcc (actually g++) is due to the fact that the regex library 
in 4.8 has problems.

Regards,
-- 
José Abílio

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org