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

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 '/builddir/build/

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 r

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 caug

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

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: https://bugzilla.redhat.com/show_bug.cg

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 mailin

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 some

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 de

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

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 co

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: https://koji.fedoraproject.org/k

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&oldid=528452#Filesystem_Layout still point at the old Filesystem Hierarchy Standard (FHS) site: http://www.pat

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: > > https://bodhi.fedoraproject.or

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 annotat

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 a

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 b

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

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 issu