Mohan,
Could you please check the script filling out the FTBFS tickets is doing
the right thing?
There was reported this ticket against Ruby:
https://bugzilla.redhat.com/show_bug.cgi?id=1865667
But I have rebuild Ruby already on Friday 31st:
On Mon, Aug 3, 2020 at 7:04 PM Nicolas Chauvet wrote:
>
> Le lun. 3 août 2020 à 23:18, Neal Gompa a écrit :
> >
> > On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote:
> > >
> > > Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit :
> > > >
> > > > On Mon, Aug 3, 2020 at 12:32 PM Gary
Le lun. 3 août 2020 à 23:18, Neal Gompa a écrit :
>
> On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote:
> >
> > Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit :
> > >
> > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> > > wrote:
> > > >
> > > > On Mon, Aug 3, 2020 at 3:15 PM Richard
On Mon, Aug 3, 2020 at 10:32 AM Jaroslav Skarvada wrote:
>
>
>
> - Original Message -
> > On 8/3/2020 9:42 AM, Neal Gompa wrote:
> > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> > > wrote:
> > >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes
> > >> wrote:
> > >>
> > >>> Most of
On 03/08/2020 22:32, Alexander Ploumistos wrote:
Thanks, going for %define felt like trying to postpone adjusting to
the new guidelines.
What about any "make target1 target2" between the %cmake* macros? Do
they remain as they are?
A "make target" can be replaced with "%cmake_build --target
On Tue, Aug 4, 2020 at 12:20 AM Neal Gompa wrote:
>
> On Mon, Aug 3, 2020 at 4:21 PM Alexander Ploumistos
> wrote:
> >
> > Hi Neal,
> >
> > On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote:
> > >
> > > CMake macros are documented in the packaging guidelines:
> > >
On Mon, 2020-08-03 at 15:39 -0400, Neal Gompa wrote:
> On Mon, Aug 3, 2020 at 3:32 PM Peter Robinson
> wrote:
> > > > > Most of those are the libcroco->gettext breakage, no?
> > > >
> > > > From a very cursory scan (not at all scientific),
> > > > some percentage are the cmake macro changes.
> >
On Mon, Aug 3, 2020 at 4:22 PM Miro Hrončok wrote:
>
> On 03. 08. 20 22:19, Neal Gompa wrote:
> > If you don't care whether it's in-source or out-of-source build, then
> > you only need to concern yourself with %cmake, %cmake_build, and
> > %cmake_install (for EPEL7, %cmake3 is the prefix instead
On Mon, Aug 3, 2020 at 4:21 PM Alexander Ploumistos
wrote:
>
> Hi Neal,
>
> On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote:
> >
> > CMake macros are documented in the packaging guidelines:
> > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/
>
> So if a spec file is supposed to
On 03. 08. 20 22:19, Neal Gompa wrote:
If you don't care whether it's in-source or out-of-source build, then
you only need to concern yourself with %cmake, %cmake_build, and
%cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake).
Neal, can I safely use this on EPEL7 and Fedora?
On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote:
>
> Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit :
> >
> > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> > wrote:
> > >
> > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
> > >
> > > > Most of those are the libcroco->gettext
On Mon, Aug 3, 2020 at 7:32 PM Peter Robinson wrote:
> The changes should have landed _BEFORE_ mass rebuild, if the change
> owner didn't have the permissions they should have done PRs for all
> the packages rather than having zero direct comms to affected package
> owners and having them find
On Mon, Aug 3, 2020 at 3:32 PM Peter Robinson wrote:
>
> > > > Most of those are the libcroco->gettext breakage, no?
> > >
> > > From a very cursory scan (not at all scientific),
> > > some percentage are the cmake macro changes.
> >
> > CMake macros are documented in the packaging guidelines:
>
On 03. 08. 20 21:02, Nicolas Chauvet wrote:
Can you show an example that work across all maintained releases ?
(aka inclusing epel7).
https://src.fedoraproject.org/rpms/lib3mf/c/69ac5cb696456d7f5478f47bf2bcf234ab77ba56?branch=master
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Hi Neal,
On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote:
>
> CMake macros are documented in the packaging guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/
So if a spec file is supposed to work on F31 to F33, "%undefine
__cmake_in_source_build" is all that's
Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit :
>
> On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> wrote:
> >
> > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
> >
> > > Most of those are the libcroco->gettext breakage, no?
> >
> > From a very cursory scan (not at all scientific),
>
> > > Most of those are the libcroco->gettext breakage, no?
> >
> > From a very cursory scan (not at all scientific),
> > some percentage are the cmake macro changes.
>
> CMake macros are documented in the packaging guidelines:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/
>
>
- Original Message -
> On Mon, Aug 03, 2020 at 01:30:56PM -0400, Jaroslav Skarvada wrote:
> >
> > Most of my FTBFSs are in form:
> > BuildrootError: Requested repo (1785390) is DELETED
> >
> > Wtf?
> >
> > E.g.:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1863168
> >
On Mon, Aug 03, 2020 at 01:30:56PM -0400, Jaroslav Skarvada wrote:
>
> Most of my FTBFSs are in form:
> BuildrootError: Requested repo (1785390) is DELETED
>
> Wtf?
>
> E.g.:
> https://bugzilla.redhat.com/show_bug.cgi?id=1863168
> https://bugzilla.redhat.com/show_bug.cgi?id=1863196
>
- Original Message -
> On 8/3/2020 9:42 AM, Neal Gompa wrote:
> > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> > wrote:
> >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
> >>
> >>> Most of those are the libcroco->gettext breakage, no?
> >> From a very cursory scan (not at
On 8/3/2020 9:42 AM, Neal Gompa wrote:
> On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> wrote:
>> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
>>
>>> Most of those are the libcroco->gettext breakage, no?
>> From a very cursory scan (not at all scientific),
>> some percentage are the
On 8/3/2020 9:38 AM, Gary Buhrmaster wrote:
> On Mon, Aug 3, 2020 at 4:24 PM Peter Robinson wrote:
>
>> There's also a bunch of CMake related ones and I'm not even sure how
>> to deal with that.
> The proposal owners stated that:
>
> Existing packages can (and most likely will) become FTBFS,
On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
wrote:
>
> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
>
> > Most of those are the libcroco->gettext breakage, no?
>
> From a very cursory scan (not at all scientific),
> some percentage are the cmake macro changes.
CMake macros are
On Mon, Aug 3, 2020 at 4:24 PM Peter Robinson wrote:
> There's also a bunch of CMake related ones and I'm not even sure how
> to deal with that.
The proposal owners stated that:
Existing packages can (and most likely will) become FTBFS, but
proposal owners will fix as many Fedora
On Mon, Aug 3, 2020 at 5:15 PM Richard Hughes wrote:
>
> On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote:
> > Failures can be seen
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
>
> Most of those are the libcroco->gettext breakage, no? We're not going
> to be rebuilding all
On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
> Most of those are the libcroco->gettext breakage, no?
From a very cursory scan (not at all scientific),
some percentage are the cmake macro changes.
___
devel mailing list --
On Mon, Aug 3, 2020 at 4:15 PM Richard Hughes wrote:
>
> On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote:
> > Failures can be seen
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
>
> Most of those are the libcroco->gettext breakage, no? We're not going
> to be rebuilding all
Many of this are cmake change breakage.
пн, 3 авг. 2020 г., 18:15 Richard Hughes :
> On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote:
> > Failures can be seen
> > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
>
> Most of those are the libcroco->gettext breakage, no? We're not
On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote:
> Failures can be seen
> https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html
Most of those are the libcroco->gettext breakage, no? We're not going
to be rebuilding all affected packages manually are we?!
Richard./
Hi all,
Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33
on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in:
https://pagure.io/releng/issue/9616
Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33.
Failures can be seen
Hi all,
Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33
on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in:
https://pagure.io/releng/issue/9616
Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33.
Failures can be seen
Hi all,
The mass rebuild is postponed to next Monday 27th July 2020 since a
couple of changes haven't landed yet.
For more information, please look at https://pagure.io/fesco/issue/2451
We will keep you posted if anything changes.
Thanks.
On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote:
>
Hi all,
The mass rebuild is postponed to next Monday 27th July 2020 since a
couple of changes haven't landed yet.
For more information, please look at https://pagure.io/fesco/issue/2451
We will keep you posted if anything changes.
Thanks.
On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote:
>
Mohan Boddu
4:32 PM (1 hour ago)
to devel-announce
Hi all,
Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33
on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the
changes listed in:
https://pagure.io/releng/issues?status=Open=mass+rebuild
Mass rebuild will
Mohan Boddu
4:32 PM (1 hour ago)
to devel-announce
Hi all,
Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33
on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the
changes listed in:
https://pagure.io/releng/issues?status=Open=mass+rebuild
Mass rebuild will
35 matches
Mail list logo
