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

2019-06-07 Thread 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

[Bug 1710585] Not validating valid IPv6 CIDR addresses

2019-06-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1710585 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|

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

2019-06-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1718093 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

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

2019-06-07 Thread 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

Re: Qt 5.12.3 coming to rawhide

2019-06-07 Thread 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 >

build failure using boost-python3 on ppc64le

2019-06-07 Thread 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

Re: HEADS UP: libgit 0.28

2019-06-07 Thread 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

Re: Rawhide bugs => F30?

2019-06-07 Thread 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

Re: Rawhide bugs => F30?

2019-06-07 Thread 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)

Re: Rawhide bugs => F30?

2019-06-07 Thread 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:

Re: Rawhide bugs => F30?

2019-06-07 Thread 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

Re: Rawhide bugs => F30?

2019-06-07 Thread 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

Re: HEADS UP: libgit 0.28

2019-06-07 Thread 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. > > >

Rawhide bugs => F30?

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

Re: HEADS UP: libgit 0.28

2019-06-07 Thread 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

Re: HEADS UP: libgit 0.28

2019-06-07 Thread 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:

The Fedora Packaging Guidelines point at the old FHS site

2019-06-07 Thread 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:

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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: > >

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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.

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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.

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

2019-06-07 Thread 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

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

2019-06-07 Thread 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

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

2019-06-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1718093 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version|

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

2019-06-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1718093 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED

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

2019-06-07 Thread 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