At today's blocker review meeting[0], we ran across a bug[1] that we
believe is bad enough to warrant blocker status, but as the criteria
currently stand, does not violate any particular criterion. The bug in
question has to do with logging out of one user account and logging into
another account t
On Aug 4, 2020 8:31 AM, "John M. Harris Jr" wrote:
>
> That somebody doesn't like something doesn't mean that they don't respect
> those who made it.
Ok. Maybe we are going OT.
But excuse me John: words matter. Saying "it sucks" is not equal to "I don't
like it".
A.
_
On Monday, August 3, 2020 9:39:19 AM MST Robbie Harwood wrote:
> Richard Shaw writes:
> > 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://fedoraproj
Hi,
this is more of a head's up than a bug per se (well, I'm actually not
sure if it's a bug, is it?), but I've had a package fail to build due to
LTO and neon optimisations:
https://kojipkgs.fedoraproject.org//work/tasks/2576/48362576/build.log
Basically what they do is compile different .a with
On 04/08/2020 04:14, Richard Shaw wrote:
I had to rely on the power of Google/Gmail to find Neal's response to
one of my earlier emails to find the answer again...
%{_vpath_builddir}
But that begs the question, now that we have updated %cmake, and new
%cmake_build & %cmake_install, why is it
On Mon, 2020-08-03 at 14:06 -0600, Jerry James wrote:
> On Mon, Aug 3, 2020 at 11:33 AM Tom Stellard wrote:
> > These are all likely caused by the linker running out of memory and
> > getting killed by the OOM killer.
>
> I see. In that case, I'll try resubmitting each build once and see if
> th
On Mon, 2020-08-03 at 18:39 -0500, Richard Shaw wrote:
> On Mon, Aug 3, 2020 at 6:12 PM Kevin Fenzi wrote:
> > On Mon, Aug 03, 2020 at 10:28:03PM +0100, Richard W.M. Jones wrote:
> > > On Mon, Aug 03, 2020 at 04:04:57PM -0500, Richard Shaw wrote:
> > > > I'm up to 21 and climbing. Technically two
On Mon, Aug 3, 2020 at 11:45 PM Richard Shaw wrote:
>
> Sometimes you need to get into the build directory, in my case for
> OpenColorIO I use help2man to generate some of the man pages.
>
> I had to rely on the power of Google/Gmail to find Neal's response to one of
> my earlier emails to find
it's done - Thanks Aleksei!
On Tue, 4 Aug 2020 at 12:02, Bob Hepple wrote:
>
> Hi,
>
> The upstream author of wayvnc (a VNC server for Wayland) has split
> some code out into a separate tiny package (aml) for which I'm waiting
> to get a review request done, since 28th July.
>
> I'm blocked from
Sometimes you need to get into the build directory, in my case for
OpenColorIO I use help2man to generate some of the man pages.
I had to rely on the power of Google/Gmail to find Neal's response to one
of my earlier emails to find the answer again...
%{_vpath_builddir}
But that begs the questio
Hi,
The upstream author of wayvnc (a VNC server for Wayland) has split
some code out into a separate tiny package (aml) for which I'm waiting
to get a review request done, since 28th July.
I'm blocked from packaging the new release wayvnc-0.2.0 until that one
is done and I need to get that new ve
On 8/3/20 6:29 PM, Kevin Fenzi wrote:
ok. I did what I could with the resources we have right now to improve
things on the s390x builders.
I've been watching it for the last hour or so and so far 0 failures that
I can attribute to s390x cache or builder infra.
Hopefully that should make thin
ok. I did what I could with the resources we have right now to improve
things on the s390x builders.
1. I noticed that we had the kvm instances oversubscribed on cpus (the
host has 32, we had 42 used). So, I lowered all the kvm builders to 3
vcpus from 4. (Those are 15-24).
2. I moved the varni
On Mon, Aug 3, 2020 at 6:12 PM Kevin Fenzi wrote:
> On Mon, Aug 03, 2020 at 10:28:03PM +0100, Richard W.M. Jones wrote:
> > On Mon, Aug 03, 2020 at 04:04:57PM -0500, Richard Shaw wrote:
> > > I'm up to 21 and climbing. Technically two are failure to install...
> > >
> > > I'm confused if I should
On Mon, Aug 3, 2020 at 7:08 PM Orion Poplawski wrote:
>
> On 7/7/20 12:09 PM, Neal Gompa wrote:
> > On Tue, Jul 7, 2020 at 1:57 PM Orion Poplawski wrote:
> >>
> >> On 6/15/20 1:47 PM, Ben Cotton wrote:
> >>> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
> >>>
>
> >>> ==
On 7/7/20 12:09 PM, Neal Gompa wrote:
> On Tue, Jul 7, 2020 at 1:57 PM Orion Poplawski wrote:
>>
>> On 6/15/20 1:47 PM, Ben Cotton wrote:
>>> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
>>>
>>> == Upgrade/compatibility impact ==
>>> Existing packages can (and most like
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 Buhrmaster
Hi Fabio,
On Mon, 2020-08-03 at 19:29 +0200, Fabio Valentini wrote:
> On Mon, Aug 3, 2020 at 6:59 PM Hans de Goede
> wrote:
> > Hi,
> >
> > On 8/3/20 5:53 PM, Kevin Fenzi wrote:
> > > On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
> > > > Hi All,
> > > >
> > > >
> > > > I just
On Mon, Aug 03, 2020 at 10:28:03PM +0100, Richard W.M. Jones wrote:
> On Mon, Aug 03, 2020 at 04:04:57PM -0500, Richard Shaw wrote:
> > I'm up to 21 and climbing. Technically two are failure to install...
> >
> > I'm confused if I should even fix these right now due to the various issues
> > I've
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 H
https://bugzilla.redhat.com/show_bug.cgi?id=1865666
links to the latest build, but that's the ELN build (which failed):
https://koji.fedoraproject.org/koji/packageinfo?packageID=8391
The latest F33 build did not fail.
I believe this bug was filed incorrectly and perhaps the script that
files t
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 t
On Mon, Aug 03, 2020 at 10:42:01PM +0100, Richard W.M. Jones wrote:
> I can't reproduce this locally but it happens in Koji reliably enough:
>
> + /usr/lib/rpm/brp-strip /usr/bin/strip
> /usr/bin/strip: unable to copy file
> '/builddir/build/BUILDROOT/ocaml-omake-0.10.3-27.fc33.x86_64/usr/bin/oma
I can't reproduce this locally but it happens in Koji reliably enough:
+ /usr/lib/rpm/brp-strip /usr/bin/strip
/usr/bin/strip: unable to copy file
'/builddir/build/BUILDROOT/ocaml-omake-0.10.3-27.fc33.x86_64/usr/bin/omake';
reason: Permission denied
error: Bad exit status from /var/tmp/rpm-tmp.5
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 tar
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:
> > > https://docs.fedoraproject.org/e
On Mon, Aug 03, 2020 at 04:04:57PM -0500, Richard Shaw wrote:
> I'm up to 21 and climbing. Technically two are failure to install...
>
> I'm confused if I should even fix these right now due to the various issues
> I've seen on the list.
>
> Is it safe to do builds right now?
Everything is block
I created the nanomsg package to support mozilla-iot-gateway.
I have orphaned mozilla-iot-gateway because I have not been able to
give it the attention it needs. I have decided to orphan nanomsg, and
the other supporting packages while I am at it.
Below are the packages I am orphaning:
nanomsg
py
Planned Outage - koji.fedoraproject.org - 2020-08-05 21:00 UTC
There will be an outage starting at 2020-08-05 21:00 UTC
which will last approximately 3 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2020-08-05 21:00
I'm up to 21 and climbing. Technically two are failure to install...
I'm confused if I should even fix these right now due to the various issues
I've seen on the list.
Is it safe to do builds right now?
Most of these are due to the cmake change. I generally agree with it
although I was already
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 w
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?
%u
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 b
On Mon, Aug 3, 2020 at 11:33 AM Tom Stellard wrote:
> These are all likely caused by the linker running out of memory and
> getting killed by the OOM killer.
I see. In that case, I'll try resubmitting each build once and see if
the same thing happens. Thanks, Tom.
--
Jerry James
http://www.jam
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 ou
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 require
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),
>
Hello all,
fst is a VST bridge for Windows VST plugins for wine only for i686 and
hasn't seen a commit since 2011-01-31[1]. With the F33 mass rebuild, the
day finally has come where fst is FTBFS due to bit rot.
Since there are newer solutions now, such as Carla, that do a good job
of bridging, I
Hi,
On 8/3/20 7:29 PM, Fabio Valentini wrote:
On Mon, Aug 3, 2020 at 6:59 PM Hans de Goede wrote:
Hi,
On 8/3/20 5:53 PM, Kevin Fenzi wrote:
On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
Hi All,
I just noticed that a lot my packages got a FTBFS because of
failing to build
Hey list,
How do Fedora rawhide images get respun? Every time filesystem updates,
it causes `dnf update` to fail in a podman container because filesystem
can't be updated in a container. We either need to make sure filesystem
updates cause rawhide containers to be rebuilt, or figure out how to
s
> > > 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/
>
>
I finally ran into another issue and used the vim faq. It was ":set
cindent" that was causing the crazy indentation in spec file %changelogs.
I still consider this a bug as the file doesn't even end in c, cpp, cxx,
c++ etc.
Thanks,
Richard
___
devel mai
- 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
> > https://bugzil
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
> https://bug
On Sun, Aug 2, 2020 at 11:27 AM Jerry James wrote:
> You can point the finger of blame at least partly at me for this.
> Version 0.15.0 of check introduced the use of
> __attribute__((printf)) to check the arguments to some of the
> calls. However, upstream didn't do it right, with the result
On 8/3/20 1:28 PM, Jerry James wrote:
I've been going through mass rebuild failures. Several of these look
like they might be LTO problems that only manifest on one
architecture.
libfplll: arm
https://koji.fedoraproject.org/koji/buildinfo?buildID=1575475
Link step fails:
/usr/bin/ld: error: lto
- 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 a
On Mon, Aug 3, 2020 at 6:59 PM Hans de Goede wrote:
>
> Hi,
>
> On 8/3/20 5:53 PM, Kevin Fenzi wrote:
> > On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
> >> Hi All,
> >>
> >>
> >> I just noticed that a lot my packages got a FTBFS because of
> >> failing to build on s390x. The fir
I've been going through mass rebuild failures. Several of these look
like they might be LTO problems that only manifest on one
architecture.
libfplll: arm
https://koji.fedoraproject.org/koji/buildinfo?buildID=1575475
Link step fails:
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld retu
Hi Elliot, thanks for the heads up:
On Mon, Aug 3, 2020 at 8:12 AM Elliott Sales de Andrade <
quantum.anal...@gmail.com> wrote:
> The build for ghc-cryptonite failed in the mass rebuild [1] and a
> later rebuild by me [2], but only on s390x. The failure appears to be
> LTO related. This doesn't a
On Mon, Aug 3, 2020 at 9:16 AM Qiyu Yan wrote:
> This works, but due to the mass rebuild and the mirrors available for
> me didn't get synced. Preparing the buildroot will take unreasonable
> long time here, maybe letting others interested to continue.
Sure, thank you for the antic review, Qiyu.
On Sun, Aug 02, 2020 at 03:48:41PM -0700, Adam Williamson wrote:
> Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a
> valued member of the QA team for many years, passed away last week. His
> wife contacted me with the news. Thomas was a regular and reassuring
> presence at Q
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 cm
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, b
Steve Grubb writes:
> Hello,
>
> On Saturday, August 1, 2020 1:27:07 PM EDT Steven Grubb wrote:
>> 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
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 docume
On Mon, 2020-08-03 at 17:26 +0100, Daniel P. Berrangé wrote:
> On Mon, Aug 03, 2020 at 05:34:47PM +0200, Hans de Goede wrote:
> > Hi,
> >
> > On 8/3/20 5:27 PM, Daniel P. Berrangé wrote:
> > > On Mon, Aug 03, 2020 at 05:01:18PM +0200, Florian Weimer wrote:
> > > > * Daniel P. Berrangé:
> > > >
>
On Mon, Aug 03, 2020 at 05:40:42PM +0200, Florian Weimer wrote:
> * Daniel P. Berrangé:
>
> > If I run LD_DEBUG=all on a build /with/ LTO, there are no symbol lookups
> > at all for qemuProcessStartManagedPRDaemon. It looks very much like the
> > call was resolved and bound at link time when built
Richard Shaw writes:
> 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 o
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 packag
On Mon, Aug 03, 2020 at 05:34:47PM +0200, Hans de Goede wrote:
> Hi,
>
> On 8/3/20 5:27 PM, Daniel P. Berrangé wrote:
> > On Mon, Aug 03, 2020 at 05:01:18PM +0200, Florian Weimer wrote:
> > > * Daniel P. Berrangé:
> > >
> > > > Disabling LTO in the RPM spec confirms this and makes things pass
> >
On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
> Hi All,
>
>
> I just noticed that a lot my packages got a FTBFS because of
> failing to build on s390x. The first set of rebuilds failed with:
>
> "BuildrootError: Requested repo (1785390) is DELETED"
I have one of those too, but
Addressed in: https://pagure.io/fesco/issue/2460#comment-668868
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/proje
Hi,
On 8/3/20 5:53 PM, Kevin Fenzi wrote:
On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
Hi All,
I just noticed that a lot my packages got a FTBFS because of
failing to build on s390x. The first set of rebuilds failed with:
"BuildrootError: Requested repo (1785390) is DELETED
On Mon, Aug 03, 2020 at 05:21:58PM +0200, Hans de Goede wrote:
> Hi All,
>
>
> I just noticed that a lot my packages got a FTBFS because of
> failing to build on s390x. The first set of rebuilds failed with:
>
> "BuildrootError: Requested repo (1785390) is DELETED"
>
> The second set of rebuild
On Mon, Aug 03, 2020 at 04:47:39PM +0200, Jun Aruga wrote:
...
> So, I suppose previously it tried to build outputed platform (f30).
> The other build id 9294 is f32, 9295 is f31, 9296 is f33.
Ah, that would do it. I finally was shown the command to retire the f30
eol platform and did so... before
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
* Daniel P. Berrangé:
> If I run LD_DEBUG=all on a build /with/ LTO, there are no symbol lookups
> at all for qemuProcessStartManagedPRDaemon. It looks very much like the
> call was resolved and bound at link time when built with LTO.
It's possible that the symbol extraction logic is confused by
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 -- devel@lists.fedoraproj
Hi,
On 8/3/20 5:27 PM, Daniel P. Berrangé wrote:
On Mon, Aug 03, 2020 at 05:01:18PM +0200, Florian Weimer wrote:
* Daniel P. Berrangé:
Disabling LTO in the RPM spec confirms this and makes things pass
again. Hacking the makefiles to remove the -fno-lto option when
building the test suite bina
On Mon, Aug 03, 2020 at 05:01:18PM +0200, Florian Weimer wrote:
> * Daniel P. Berrangé:
>
> > Disabling LTO in the RPM spec confirms this and makes things pass
> > again. Hacking the makefiles to remove the -fno-lto option when
> > building the test suite binaries also fixes things.
> >
> > I don'
On 03/08/20 17:16 +0200, Andrea Musuruane wrote:
Hi guys,
at least one of the packages I maintain was also affected. Fedora
I'm seeing the same error for boost on both s390x and armv7hl.
Release Engineering has opened a bug against the package for this issue.
Can you please avoid that? Mor
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
Hi All,
I just noticed that a lot my packages got a FTBFS because of
failing to build on s390x. The first set of rebuilds failed with:
"BuildrootError: Requested repo (1785390) is DELETED"
The second set of rebuilds failed with:
"rpm.error: error reading package header"
errors.
The last err
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
Hi guys,
at least one of the packages I maintain was also affected. Fedora
Release Engineering has opened a bug against the package for this issue.
Can you please avoid that? Moreover, would my package be orphaned in 8
weeks because it cannot be built for a builder issue on s390x?
https://bugz
On Mon, Aug 03, 2020 at 05:01:18PM +0200, Florian Weimer wrote:
> * Daniel P. Berrangé:
>
> > Disabling LTO in the RPM spec confirms this and makes things pass
> > again. Hacking the makefiles to remove the -fno-lto option when
> > building the test suite binaries also fixes things.
> >
> > I don
* Daniel P. Berrangé:
> Disabling LTO in the RPM spec confirms this and makes things pass
> again. Hacking the makefiles to remove the -fno-lto option when
> building the test suite binaries also fixes things.
>
> I don't see any mention of LD_PRELOAD being impacted by LTO in the
> Fedora feature
> Can you try again now? we fixed a major issue with mbs, which I wouldn't
think was related to this, but who knows..
I tried it, and found the cause of the error now.
> So isn't this the relevant part of root.log which could give a hint?
Yes, possibly it is related to the issue.
> https://koji
I'm trying to understand failures in the libvirt test suite since the
Fedora rawhide mass rebuild.
Our test suite makes extensive use of mocking to replace functions in
the library being tested. We do this either by loading a LD_PRELOAD,
or by having the test program define a symbol with the same
Robert-André Mauchin 于2020年8月2日周日 上午1:47写道：
>
> 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:
> > >
> >
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./
On Mon, Aug 3, 2020 at 12:13 pm, John Doe wrote:
I am willing to help this, I want flatpaks with sandboxing for more
secure desktop with Fedora.
Best person to talk to about helping out with Fedora flatpaks would be
Owen Taylor . I understand that infrastructure
challenges are the main probl
On Sat, Aug 1, 2020 at 8:21 PM Richard Shaw wrote:
>
> On Sat, Aug 1, 2020 at 1:10 PM Adam Williamson
> wrote:
>>
>> If what you're writing falls under the general heading of
>> 'documentation', you might want to write it for docs.fedoraproject.org
>> rather than the wiki. docs.fp.o is built by
OLD: Fedora-Rawhide-20200802.n.0
NEW: Fedora-Rawhide-20200803.n.0
= SUMMARY =
Added images:3
Dropped images: 3
Added packages: 0
Dropped packages:1
Upgraded packages: 271
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:374.16
On Mon, Aug 3, 2020 at 9:55 am, Fabio Valentini
wrote:
FWIW, I've been resubmitting koji builds for all FTBFS packages that
build locally (with mockbuild --enablerepo local) for the past few
days.
Almost 100 packages that failed due to transient buildroot issues
(broken gcc/annobin, broken get
I'm late to the party, but there are factual errors here that deserve
correcting.
On 7/4/20 10:23 AM, Nicolas Mailhot via devel wrote:
Le vendredi 03 juillet 2020 à 11:09 -0700, PGNet Dev a écrit :
%define _build_timestamp %( date +%Y%m%d_%H%M%S )
You’re hitting rpm macro expansion
Hi,
to the best of my knowledge, Sebastian Vahl left Fedora several years ago.
He used to be the maintainer of the Fedora KDE Live image, but at some point
simply stopped doing that (even though he was still listed as the official
maintainer) and the live image was maintained de facto first by
Mhm okay, is there any reason you need such complicated machinery for getting
flatpaks available in Fedora? The point is, for me, the desktop sandboxing
capabilities, and specially when they'll actually be effective after the death
of X11-only applications eco-system wide.
The issue with Flatpa
I do hope you realize that if I'm digging into Koji, I do know how to install a
package with dnf and if I want to use flatpak, I do want to.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
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
https:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If
In support of Kevin's statement:
Out-of-source builds make sense if you want to build from the source multiple
times, or if you want to ensure that the source is immutable (for the build
process).
None of this seems to be the goal of the Change which was motivated solely by
general "you should
Dne 02. 08. 20 v 0:21 Kevin Fenzi napsal(a):
> 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/task
Good Morning Everyone,
I have been trying to contact packagers without a proper bugzilla account
associated with their FAS email for a while now. The first email to
devel-announce
is from June 13th [1].
This is a requirement for packagers which is mentioned at:
https://fedoraproject.org/wiki/Joi
Quite some stuff from the list are "soft" dependencies of rpmbuild, e.g.
the compression algorithms. May be we should have discussion if we
should have BR on the decompression library, or if the BR could be
autogenerated.
Vít
Dne 02. 08. 20 v 22:06 Miroslav Suchý napsal(a):
> As part of
> ht
1 - 100 of 101 matches
Mail list logo
