On Sun, 2020-08-02 at 00:36 +0200, Sandro Mani wrote:
> Hi
>
> postgis seems another one suffering from LTO related failures.
>
> LTO (results in test failures):
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48393090
>
> LTO disabled (tests pass):
> https://koji.fedoraproject.org/koji/
On Sun, 2020-08-02 at 00:36 +0200, Sandro Mani wrote:
> Hi
>
> postgis seems another one suffering from LTO related failures.
>
> LTO (results in test failures):
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48393090
>
> LTO disabled (tests pass):
> https://koji.fedoraproject.org/koji/
On Sat, 2020-08-01 at 15:26 -0700, Kevin Fenzi wrote:
> On Sat, Aug 01, 2020 at 02:03:40PM -0600, Jeff Law wrote:
> > On Sat, 2020-08-01 at 12:12 +0200, Kevin Kofler wrote:
> > > Hi,
> > >
> > > seeing the amount of fallout from LTO, I really think that this feature
> > > ought to be dropped from
Gary Buhrmaster wrote:
> On Sat, Aug 1, 2020 at 9:23 PM Kevin Kofler
> wrote:
>> Especially the CMake one was completely pointless.
>
> The goal was not pointless, but I will assert that the
> implementation was flawed in practice.
The goal was to make more packages do out-of-source builds, whic
Hi
postgis seems another one suffering from LTO related failures.
LTO (results in test failures):
https://koji.fedoraproject.org/koji/taskinfo?taskID=48393090
LTO disabled (tests pass):
https://koji.fedoraproject.org/koji/taskinfo?taskID=48394173
Thanks
Sandro
_
Hi
postgis seems another one suffering from LTO related failures.
LTO (results in test failures):
https://koji.fedoraproject.org/koji/taskinfo?taskID=48393090
LTO disabled (tests pass):
https://koji.fedoraproject.org/koji/taskinfo?taskID=48394173
Thanks
Sandro
_
On Sat, Aug 01, 2020 at 02:03:40PM -0600, Jeff Law wrote:
> On Sat, 2020-08-01 at 12:12 +0200, Kevin Kofler wrote:
> > Hi,
> >
> > seeing the amount of fallout from LTO, I really think that this feature
> > ought to be dropped from F33, and evaluated carefully for F34 (i.e., can it
> > be done w
On Fri, Jul 31, 2020 at 04:05:20PM +0200, Jun Aruga wrote:
> Hi,
> Sometimes once per a few times, I faced the following weird build
> error when building Ruby modules.
> Did you see it? Known issue?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48194471
> BuildrootError: could not init
On Sat, Aug 1, 2020 at 9:23 PM Kevin Kofler wrote:
> Especially the CMake one was completely pointless.
The goal was not pointless, but I will assert that the
implementation was flawed in practice.
I would suggest that a lesson to be learned is that changes
that are expected to require updates t
Hi folks! I'm proposing we cancel the QA meeting for Monday. I don't
have anything urgent this week, and it's a vacation day in Canada.
If you're aware of anything important we have to discuss this week,
please do reply to this mail, but someone else will need to run the
meeting :)
I can't run a
On Sat, 2020-08-01 at 13:18 -0500, Richard Shaw wrote:
> On Sat, Aug 1, 2020 at 1:10 PM Adam Williamson
> wrote:
>
> > On Sat, 2020-08-01 at 12:00 -0500, Richard Shaw wrote:
> > > So I wanted to document a ham radio related howto, so I decided that I
> > > would make it an extension of the Amateu
Michael J Gruber wrote:
> I think we should test build with changes like cmake or LTO in isolation
> from the typical mass rebuild which exposes many other problems.
I think we should just not do this kind of changes that mass-break packages
at all. Especially the CMake one was completely pointle
Neal Gompa wrote:
> Then there'd be the problem of where we'd have the build capacity. We
> barely have enough for what we do now...
To be honest, I would just ignore the modules and do the side tag rebuilds
only for the non-modular Rawhide, and only once a month or so.
Kevin Kofler
On Sat, 2020-08-01 at 21:00 +0100, Richard W.M. Jones wrote:
> On Sat, Aug 01, 2020 at 01:28:09PM -0600, Jeff Law wrote:
> > On Sat, 2020-08-01 at 12:34 +0100, Richard W.M. Jones wrote:
> > > On Fri, Jul 31, 2020 at 05:32:34PM -0600, Jeff Law wrote:
> > > > On Fri, 2020-07-31 at 19:26 +0100, Richar
On Sat, 2020-08-01 at 12:12 +0200, Kevin Kofler wrote:
> Hi,
>
> seeing the amount of fallout from LTO, I really think that this feature
> ought to be dropped from F33, and evaluated carefully for F34 (i.e., can it
> be done without breaking the build of or miscompiling a large part of the
> di
On Sat, Aug 1, 2020 at 6:43 AM Artem Tim wrote:
>
> @Chris, thanks, i did some tests and now we have some numbers. tl;rd the
> results is pretty satisfying me, even if there no speedup in my case, but
> there is a lot disk space could be saved and reduce writes. Probably not
> worth file a bug,
On Sat, Aug 01, 2020 at 01:28:09PM -0600, Jeff Law wrote:
> On Sat, 2020-08-01 at 12:34 +0100, Richard W.M. Jones wrote:
> > On Fri, Jul 31, 2020 at 05:32:34PM -0600, Jeff Law wrote:
> > > On Fri, 2020-07-31 at 19:26 +0100, Richard W.M. Jones wrote:
> > > > On Fri, Jul 31, 2020 at 12:02:22PM -0600,
On Sat, 2020-08-01 at 12:34 +0100, Richard W.M. Jones wrote:
> On Fri, Jul 31, 2020 at 05:32:34PM -0600, Jeff Law wrote:
> > On Fri, 2020-07-31 at 19:26 +0100, Richard W.M. Jones wrote:
> > > On Fri, Jul 31, 2020 at 12:02:22PM -0600, Jeff Law wrote:
> > > > Looks like it's in the buildroots now. L
On Sat, Aug 1, 2020 at 1:10 PM Adam Williamson
wrote:
> On Sat, 2020-08-01 at 12:00 -0500, Richard Shaw wrote:
> > So I wanted to document a ham radio related howto, so I decided that I
> > would make it an extension of the Amateur Radio SIG wiki, and I've got an
> > incomplete version created:
>
On Sat, Aug 01, 2020 at 06:35:30PM +0100, Richard W.M. Jones wrote:
> On Sat, Aug 01, 2020 at 03:13:50PM +0200, Fabio Valentini wrote:
> > On Sat, Aug 1, 2020 at 2:44 PM Richard W.M. Jones wrote:
> > >
> > > On Sat, Aug 01, 2020 at 03:25:48AM -0400, Elliott Sales de Andrade wrote:
> > > > libcroco
On Sat, Aug 01, 2020 at 03:13:50PM +0200, Fabio Valentini wrote:
> On Sat, Aug 1, 2020 at 2:44 PM Richard W.M. Jones wrote:
> >
> > On Sat, Aug 01, 2020 at 03:25:48AM -0400, Elliott Sales de Andrade wrote:
> > > libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it
> > > provides
Hello,
I was using my desktop system when I got logged out. After logging back in, I
found this message in my logs:
Aug 1 13:08:22 x2 journal[1751]: UID 1000 exceeded its 'bytes' quota on UID
1000.
which was then followed by:
Aug 1 13:08:22 x2 dbus-broker[1751]: Peer :1.200 is being disconn
On Sat, 2020-08-01 at 12:00 -0500, Richard Shaw wrote:
> So I wanted to document a ham radio related howto, so I decided that I
> would make it an extension of the Amateur Radio SIG wiki, and I've got an
> incomplete version created:
>
> https://fedoraproject.org/wiki/AmateurRadio/Howto/Pat
>
> H
On Sat, Aug 1, 2020 at 12:05 PM Tom Hughes wrote:
> On 01/08/2020 18:00, Richard Shaw wrote:
> > So I wanted to document a ham radio related howto, so I decided that I
> > would make it an extension of the Amateur Radio SIG wiki, and I've got
> > an incomplete version created:
> >
> > https://fed
On 01/08/2020 18:00, Richard Shaw wrote:
So I wanted to document a ham radio related howto, so I decided that I
would make it an extension of the Amateur Radio SIG wiki, and I've got
an incomplete version created:
https://fedoraproject.org/wiki/AmateurRadio/Howto/Pat
How can a wiki not have s
So I wanted to document a ham radio related howto, so I decided that I
would make it an extension of the Amateur Radio SIG wiki, and I've got an
incomplete version created:
https://fedoraproject.org/wiki/AmateurRadio/Howto/Pat
How can a wiki not have some kind of tag?
Most other systems in Fedo
On Saturday, 1 August 2020 05:07:52 CEST Qiyu Yan wrote:
> Jerry James 于 2020年8月1日周六 上午5:24写道：
>
> > I need two packages reviewed to enable some optional functionality in
> > the normaliz package. The second depends on the first:
> >
> > antic: https://bugzilla.redhat.com/show_bug.cgi?id=186261
On Sat, Aug 01, 2020 at 03:37:37PM -, Michael J Gruber wrote:
> It is tagged as
>
> f33-rebuild
> f33-updates-candidate
>
> now but not as
>
> f33
>
> and bodhi does not know about it either. Is it possible/advisable to tag it
> as f33 directly to get the other rebuilds going again?
You c
On Sat, Aug 01, 2020 at 03:15:59PM +0200, Fabio Valentini wrote:
> On Sat, Aug 1, 2020 at 3:12 PM Michael J Gruber
> wrote:
> >
> > Well, that second mass rebuild made things worse for me.
> > The time between the two was really short - we do need time to fix things
> > (see below).
> > The sec
I've created a review request to unretire rgbds:
https://bugzilla.redhat.com/show_bug.cgi?id=1862705
-ben
signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
It is tagged as
f33-rebuild
f33-updates-candidate
now but not as
f33
and bodhi does not know about it either. Is it possible/advisable to tag it as
f33 directly to get the other rebuilds going again?
___
devel mailing list -- devel@lists.fedoraprojec
On Sat, Aug 1, 2020 at 8:30 am, Michael Catanzaro
wrote:
I don't think there's anything else that needs to be done now.
OK, I see Fabio's mail that it isn't tagged yet:
Can we get gettext-0.20.2-4.fc33 tagged into the f33? I'd do it
myself, if I was sure not to break anything ... would "ko
I got permission from the package owner (Dodji) before retiring it.
I'll check with you first next time, sorry.
I don't think there's anything else that needs to be done now. First we
have to wait for the mass rebuild script to finish. Then we see what
all failed
__
Sorry, this is my fault.
On Sat, Aug 1, 2020 at 3:25 am, Elliott Sales de Andrade
wrote:
gettext is used by many many things. Please unretire libcroco, or
rebuild gettext without it.
It was successfully rebuilt last night by releng, I assume by the mass
rebuild script. We were trying to reb
On Sat, Aug 1, 2020 at 3:12 PM Michael J Gruber wrote:
>
> Well, that second mass rebuild made things worse for me. The time between the
> two was really short - we do need time to fix things (see below). The second
> rebuild not only forced us to rebase changes which were in QA (and rewrite
>
On Sat, Aug 1, 2020 at 2:44 PM Richard W.M. Jones wrote:
>
> On Sat, Aug 01, 2020 at 03:25:48AM -0400, Elliott Sales de Andrade wrote:
> > libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it
> > provides is used by libtextstyle.so.0, part of gettext.
> >
> > gettext is used by m
@Chris, thanks, i did some tests and now we have some numbers. tl;rd the
results is pretty satisfying me, even if there no speedup in my case, but there
is a lot disk space could be saved and reduce writes. Probably not worth file a
bug, but a little bit weird that with zstd:1 still a little bit
I see that this ticket is still NEW.
I've update with my experience that the suggested fix works.
It would be good to get this fix in for F33.
Is there more testing I can do to help?
Barry
___
devel mailing list -- devel@lists.fedoraproject.org
To uns
On 8/1/20 09:25, Elliott Sales de Andrade wrote:
libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it
provides is used by libtextstyle.so.0, part of gettext.
gettext is used by many many things. Please unretire libcroco, or
rebuild gettext without it.
This is unfortunate.
Mi
> On Wed, 2020-07-29 at 14:13 +0100, sergio(a)serjux.com wrote:
> In general I want to have a very good
> indicator the issue is LTO related before I
> disable. THe build you referenced doesn't have any good indicators that LTO
> is
> the problem.
>
> For ppc64le is that the build was done with
Well, that second mass rebuild made things worse for me. The time between the
two was really short - we do need time to fix things (see below). The second
rebuild not only forced us to rebase changes which were in QA (and rewrite the
changelog because of date order stubbornness) but - what's wor
On Sat, Aug 01, 2020 at 03:25:48AM -0400, Elliott Sales de Andrade wrote:
> libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it
> provides is used by libtextstyle.so.0, part of gettext.
>
> gettext is used by many many things. Please unretire libcroco, or
> rebuild gettext witho
On Fri, Jul 31, 2020 at 05:32:34PM -0600, Jeff Law wrote:
> On Fri, 2020-07-31 at 19:26 +0100, Richard W.M. Jones wrote:
> > On Fri, Jul 31, 2020 at 12:02:22PM -0600, Jeff Law wrote:
> > > Looks like it's in the buildroots now. Let me know if that doesn't fix
> > > the
> > > problem.
> >
> > Loo
On Sat, Aug 1, 2020 at 7:17 AM Kevin Kofler wrote:
>
> Neal Gompa wrote:
> > I think it does have value, however I think the Red Hat compiler team
> > drastically underestimated how much breakage we're willing to tolerate
> > for it.
>
> I think you mean "overestimated" there, not "underestimated"
Neal Gompa wrote:
> I think it does have value, however I think the Red Hat compiler team
> drastically underestimated how much breakage we're willing to tolerate
> for it.
I think you mean "overestimated" there, not "underestimated", don't you?
> That's not true. Since Koji 1.18, it's been possi
Hi,
seeing the amount of fallout from LTO, I really think that this feature
ought to be dropped from F33, and evaluated carefully for F34 (i.e., can it
be done without breaking the build of or miscompiling a large part of the
distribution, once the bugs such as the ld bug discussed in this thre
libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it
provides is used by libtextstyle.so.0, part of gettext.
gettext is used by many many things. Please unretire libcroco, or
rebuild gettext without it.
--
Elliott
___
devel mailing li
47 matches
Mail list logo
