2018-02-22 21:47 GMT+01:00 Josh Boyer :
> On Thu, Feb 22, 2018 at 12:49 PM, Marek Polacek wrote:
>> As many of you know, every year we (the GCC team) rebuild all the Fedora
>> packages with the upcoming GCC, so as to reveal as many bugs as possible
>> before
>> we release the new version. As in
On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
>> Hi!
>>
>> During the last days there have been concerns raised regarding
>> what is an appropriate content for the tests namespace. [1] My
>> original idea was to enable shar
On Thursday, February 22, 2018 3:50:38 PM CET Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> > When, for a particular package, it is the most efficient way to
> > maintain tests in a separate repo why should we discourage from
> > this approach? There a
Kevin, Langdon,
thanks guys! I'll keep an eye on this so we won't miss this feature.
Cheers,
milan
pá 23. 2. 2018 v 2:21 odesílatel Langdon White napsal:
> On Thu, Feb 22, 2018 at 4:51 PM Kevin Fenzi wrote:
>
>> On 02/22/2018 10:33 AM, milanisko k wrote:
>> > Folks,
>> >
>> >
>> > I've just
Nicolas Chauvet wrote:
> Hi,
>
> I plan to update cryptopp to 6.1.0 release for f28+ later today.
...
> The good news, is that upstream accepted my patch to freeze the ABI
> with .6, with this lts version. So for more safety, there is a need to
> rebuild the few packages using this library:
>
>
On 22/02/18 16:47 +0100, Rafal Luzynski wrote:
15.02.2018 12:02 Rafal Luzynski wrote:
9.02.2018 11:34 Rafal Luzynski wrote:
> [...]
> Please:
> - backport the solution to F26 and F27 as well, this should be much
> easier than in F28 (my pull requests may be helpful),
> - mark my pull request
On Thu, Feb 22, 2018 at 01:34:00PM -0800, John Reiser wrote:
> Looking at the code:
> = gcc/libgcc/unwind.inc
> _Unwind_ForcedUnwind_Phase2 (struct _Unwind_Exception *exc,
> struct _Unwind_Context *context,
> unsigned long *frames_p)
On 02/18/2018 06:09 PM, Igor Gnatenko wrote:
The grep output is located here:
https://ignatenkobrain.fedorapeople.org/gcc-removal.txt
fbset should be taken care of because I had to touch the package anyway,
and it has seen few actual changes over the years.
Thanks,
Florian
__
On Sun, Feb 18, 2018 at 06:09:40PM +0100, Igor Gnatenko wrote:
>
> List of packages and respective maintainers:
> https://ignatenkobrain.fedorapeople.org/gcc-removal-pkgs.txt
>
> adeltonmod_auth_openidc mod_authnz_pam mod_intercept_form_submit
> mod_lookup_identity perl-Cache-Mmap perl-Crypt
Is it possible, and if so, how do I package a gnome-shell-extension that is
defaulted to on for all users?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On 23/02/18 13:16, Jakub Jelinek wrote:
On Thu, Feb 22, 2018 at 01:34:00PM -0800, John Reiser wrote:
Looking at the code:
= gcc/libgcc/unwind.inc
_Unwind_ForcedUnwind_Phase2 (struct _Unwind_Exception *exc,
struct _Unwind_Context *context,
On Thu, 22 Feb 2018 18:49:02 +0100
Marek Polacek wrote:
> proftpd: timeouts in tests, but in koji it's fine
I get this too. If I build with mock --old-chroot then it works fine.
Paul.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsub
Hi folks,
I'm going to update cfitsio to new version 3.420 this weekend on F28+, this
includes a library version bump to 5. As there were no API changes, everything
should rebuild fine, I made some test builds so far. I'll take care of the
required rebuilds.
Affected packages (many of these my
On 23/02/18 14:33, Paul Howarth wrote:
On Thu, 22 Feb 2018 18:49:02 +0100
Marek Polacek wrote:
proftpd: timeouts in tests, but in koji it's fine
I get this too. If I build with mock --old-chroot then it works fine.
So the obvious difference is that mock with --old-chroot has networking
Tom Hughes wrote:
> On 23/02/18 14:33, Paul Howarth wrote:
>> On Thu, 22 Feb 2018 18:49:02 +0100
>> Marek Polacek wrote:
>>> proftpd: timeouts in tests, but in koji it's fine
>>
>> I get this too. If I build with mock --old-chroot then it works fine.
>
> So the obvious difference is that mo
I've seen a fair amount of LDFLAGS injection failures related to
libtool. For the most part,
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld is dropped, leading to a
lack of BIND_NOW in the resulting binary.
Is there a way we can fix this in libtool or the auto* tools? I'm also
considering mo
===
#fedora-meeting: FESCO (2018-02-23)
===
Meeting started by nirik at 15:08:16 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2018-02-23/fesco.2018-02-23-15.08.log.html
.
Meeting summary
---
On Thu, Feb 22, 2018 at 06:49:02PM +0100, Marek Polacek wrote:
> libguestfs-1.37.35-2.fc28.src.rpm
> I'm not sure about these failures, but they don't seem to be GCC bugs.
Is there a log file?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my pro
The bind now issue is a real problem for some packages. I have interacted with
upstream countlesstimes on it and simply lost the fight. Please, whatever you
do, leave some route to disable bind now.
On Friday, February 23, 2018 10:55 AM, Florian Weimer
wrote:
I've seen a fair amount
Hi,
If anyone knows how to contact Conrad Meyer / konradm, please do so.
Today one package owned by konradm, xchat-ruby, was retired as a result
of a FESCo ticket [1]. The remaining ones will be orphaned in two weeks
if there is no response.
[1] https://pagure.io/fesco/issue/1847
Zbyszek
__
On 02/23/2018 05:16 PM, Philip Kovacs wrote:
The bind now issue is a real problem for some packages. I have interacted with
upstream countlesstimes on it and simply lost the fight. Please, whatever you
do, leave some route to disable bind now.
Disable it for what?
The vast majority of miss
On Fri, Feb 23, 2018 at 8:16 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> If anyone knows how to contact Conrad Meyer / konradm, please do so.
>
> Today one package owned by konradm, xchat-ruby, was retired as a result
> of a FESCo ticket [1]. The remaining ones will be orphaned in two weeks
> if ther
On Fri, Feb 23, 2018 at 08:34:34AM -0800, Conrad Meyer wrote:
> On Fri, Feb 23, 2018 at 8:16 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > If anyone knows how to contact Conrad Meyer / konradm, please do so.
> >
> > Today one package owned by konradm, xchat-ruby, was retired as a result
> > of a FE
> "JJ" == Jakub Jelinek writes:
JJ> Can I get detailed info on how to reproduce this (most importantly,
JJ> which src.rpm you are trying to build)?
Sorry, that was all in the original message.
The package is cyrus-imapd; all you have to do is check it out and do
fedpkg mockbuild (on the raw
Greetings gcc maintainers!
A FESCo issue[0] has been filed due to the dropping of 389-ds-base and
freeipa on 32 bit arches for Fedora 28. This was done without a change
request being filed, so FESCo is trying to decide how best to handle it.
It seems there are some concerns about whether the C to
My particular concern is not "missing" bind now flags in the elf objects. I am
concerned aboutmaking sure bind now is omitted because the package cannot
operate with that flag.
On Friday, February 23, 2018 11:35 AM, Florian Weimer
wrote:
On 02/23/2018 05:16 PM, Philip Kovacs wrote:
>
On 02/23/2018 09:58 AM, Randy Barlow wrote:
> Greetings gcc maintainers!
>
> A FESCo issue[0] has been filed due to the dropping of 389-ds-base and
> freeipa on 32 bit arches for Fedora 28. This was done without a change
> request being filed, so FESCo is trying to decide how best to handle it.
>
On Fri, Feb 23, 2018 at 10:56:47AM -0600, Jason L Tibbitts III wrote:
> > "JJ" == Jakub Jelinek writes:
>
> JJ> Can I get detailed info on how to reproduce this (most importantly,
> JJ> which src.rpm you are trying to build)?
>
> Sorry, that was all in the original message.
>
> The package
Philip Kovacs wrote:
My particular concern is not "missing" bind now flags in the elf objects. I am
concerned about
making sure bind now is omitted because the package cannot operate with that
flag.
Please tell us the name of the packages, and some indication of why
the package does not work
On pe, 23 helmi 2018, Jeff Law wrote:
On 02/23/2018 09:58 AM, Randy Barlow wrote:
Greetings gcc maintainers!
A FESCo issue[0] has been filed due to the dropping of 389-ds-base and
freeipa on 32 bit arches for Fedora 28. This was done without a change
request being filed, so FESCo is trying to d
On 02/23/2018 10:29 AM, Alexander Bokovoy wrote:
> On pe, 23 helmi 2018, Jeff Law wrote:
>> On 02/23/2018 09:58 AM, Randy Barlow wrote:
>>> Greetings gcc maintainers!
>>>
>>> A FESCo issue[0] has been filed due to the dropping of 389-ds-base and
>>> freeipa on 32 bit arches for Fedora 28. This was
On Fri, Feb 23, 2018 at 04:09:26PM +, Richard W.M. Jones wrote:
> On Thu, Feb 22, 2018 at 06:49:02PM +0100, Marek Polacek wrote:
> > libguestfs-1.37.35-2.fc28.src.rpm
> > I'm not sure about these failures, but they don't seem to be GCC bugs.
>
> Is there a log file?
The one I have says
li
The package is slurm and the issue is their plugins. It's a deep architectural
problem unfortunately,To summarize the issue briefly: When designing a plugin
system, the services a plugin providesought not depend on the environment that
loads it. That is not the case for slurm. Their plugins
> "JJ" == Jakub Jelinek writes:
JJ> Haven't managed to reproduce it, while there are some testsuite
JJ> failures, they are due to timeouts and e.g. dmesg doesn't show any
JJ> segvs nor traps.
Of course I can reproduce this easily and it also happens in the
buildsystem. The first failure aft
On Fri, Feb 23, 2018 at 11:54:28AM -0600, Jason L Tibbitts III wrote:
> > "JJ" == Jakub Jelinek writes:
>
> JJ> Haven't managed to reproduce it, while there are some testsuite
> JJ> failures, they are due to timeouts and e.g. dmesg doesn't show any
> JJ> segvs nor traps.
>
> Of course I can
On Fri, Feb 16, 2018 at 12:13:15PM +0100, Jan Kurik wrote:
> Proposed System Wide Change: Enable dbus-broker
> https://fedoraproject.org/wiki/Changes/EnableDbusBroker
What about renaming this to DbusBrokerAsTheDefaultDbusImplementation?
"Enable" correctly describes the technical operation (system
> "JJ" == Jakub Jelinek writes:
JJ> Well, I'm seeing
[...]
So that's the first of the two test suites, which I've seen fail before
but I haven't invested any time into debugging it. It's completely
unrelated to any of the failures I'm talking about.
You can just remove or comment the line
On Fri, Feb 23, 2018 at 02:17:34PM -0600, Jason L Tibbitts III wrote:
> > "JJ" == Jakub Jelinek writes:
>
> JJ> Well, I'm seeing
> [...]
>
> So that's the first of the two test suites, which I've seen fail before
> but I haven't invested any time into debugging it. It's completely
> unrelat
Some more information:
I looked through the Koschei logs for this package and it seemed it
actually started failing before gcc8 went in. Specifically, the first
failed build was on January 22, and the changes for that run were:
mariadb-devel 3:10.2.12-2.fc28 -> 3:10.2.12-3.fc28
bi
On Mon, Feb 19, 2018 at 2:35 AM, Pierre-Yves Chibon
wrote:
>
> Maybe I could help you in the mean time, feel free to ask.
Thanks for the offer but I emailed one of the admins and got myself removed.
Thanks,
Richard
___
devel mailing list -- devel@lis
> "JJ" == Jakub Jelinek writes:
JJ> Strangely, --enable-network to mock was really needed so that the
JJ> first testsuite passes.
That's absolutely bizarre.
JJ> I can now get the coredumps, but I'm afraid I really need a way to
JJ> reproduce it under gdb, from the core dump there isn't suff
I'm sorry, for the first time in decades I actually hit the send
key sequence (Ctrl-C Ctrl-C) accidentally.
> "JJ" == Jakub Jelinek writes:
JJ> Strangely, --enable-network to mock was really needed so that the
JJ> first testsuite passes.
That's absolutely bizarre.
JJ> I can now get the cor
I'm sorry, for the first time in decades I actually hit the send
key sequence (Ctrl-C Ctrl-C) accidentally.
> "JJ" == Jakub Jelinek writes:
JJ> Strangely, --enable-network to mock was really needed so that the
JJ> first testsuite passes.
That's absolutely bizarre.
JJ> I can now get the cor
On Fri, Feb 23, 2018 at 12:32 PM, Jeff Law wrote:
> The fact that the 389-ds code works on other architectures does not
> allow us to draw any conclusions at this point.
>
Can you give any more details on 32-bit ARM in particular -- is it just
i686 that is experiencing issues, or have you seen s
23.02.2018 13:58 Jonathan Wakely wrote:
>
>
> On 22/02/18 16:47 +0100, Rafal Luzynski wrote:
> >15.02.2018 12:02 Rafal Luzynski wrote:
> >>
> >>
> >> 9.02.2018 11:34 Rafal Luzynski wrote:
> >> > [...]
> >> > Please:
> >> > - backport the solution to F26 and F27 as well, this should be much
> >>
45 matches
Mail list logo
