Hi all,
JFYI, for https://bugzilla.redhat.com/1405433 purpose, we're moving
'/bin/msghack' script into 'msghack' package (and most probably, it is going to
be dropped in future). In case anybody used '/bin/msghack' for anything, we'd
like to hear from you (adding explicit (Build)Requires is fine
Missing expected images:
Workstation live i386
Kde live x86_64
Xfce raw-xz armhfp
Minimal raw-xz armhfp
Workstation live x86_64
Kde live i386
Failed openQA tests: 18/80 (x86_64), 5/15 (i386)
New failures (same test did not fail in Rawhide-20161215.n.0):
ID: 51431 Test: x86_64 Server-dvd-i
Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have
anything much on the agenda, and a lot of folks are already winding
down for the holidays.
If you think there is something we need to discuss, please do reply to
this mail and we can go ahead and schedule the meeting! Thanks.
On Mon, 2016-12-19 at 00:25 +, Tom Hughes wrote:
> Maybe systemd is reading the limit itself and applying it to the data
> it
> receives through the pipe?
Yes.
I'm not sure that systemd actually uses the ulimit for more than the
binary decision of whether or not to generate the core, though.
On Sun, 2016-12-18 at 18:08 -0500, Matthew Miller wrote:
> I have ulimit -c returning 0 in shells on my system — have I done
> some
> configuration I don't remember? That's the default, isn't it? Should
> it
> stay that way with this change?
No, the default is supposed to be unlimited. systemd set
On 19/12/16 00:17, Matthew Miller wrote:
On Mon, Dec 19, 2016 at 12:07:06AM +, Tom Hughes wrote:
I have ulimit -c returning 0 in shells on my system — have I done some
configuration I don't remember? That's the default, isn't it? Should it
stay that way with this change?
The ulimit on core
On Mon, Dec 19, 2016 at 12:07:06AM +, Tom Hughes wrote:
> >I have ulimit -c returning 0 in shells on my system — have I done some
> >configuration I don't remember? That's the default, isn't it? Should it
> >stay that way with this change?
> The ulimit on core dump size is (mostly) ignored if s
perl-ZeroMQ has broken dependencies in the rawhide tree:
On x86_64:
perl-ZeroMQ-0.23-13.fc25.x86_64 requires libzmq.so.1()(64bit)
On armhfp:
perl-ZeroMQ-0.23-13.fc25.armv7hl requires libzmq.so.1
On ppc64le:
perl-ZeroMQ-0.23-13.fc25.ppc64le requires libzmq.so.1()(64bit)
On
perl-Alien-ROOT has broken dependencies in the rawhide tree:
On aarch64:
perl-Alien-ROOT-5.34.36.1-2.fc26.noarch requires root-core
On ppc64:
perl-Alien-ROOT-5.34.36.1-2.fc26.noarch requires root-core
On ppc64le:
perl-Alien-ROOT-5.34.36.1-2.fc26.noarch requires root-core
P
On 18/12/16 23:08, Matthew Miller wrote:
On Sun, Dec 18, 2016 at 01:00:37PM -0600, Michael Catanzaro wrote:
How do I get f25 to create cores, these days?
Some more details here:
https://fedoraproject.org/wiki/Changes/coredumpctl
I have ulimit -c returning 0 in shells on my system — have I don
Announcing the creation of a new nightly release validation test event
for Fedora 26 Rawhide 20161218.n.1. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On Sun, Dec 18, 2016 at 01:00:37PM -0600, Michael Catanzaro wrote:
> > How do I get f25 to create cores, these days?
> Some more details here:
> https://fedoraproject.org/wiki/Changes/coredumpctl
I have ulimit -c returning 0 in shells on my system — have I done some
configuration I don't remember?
On Sun, 2016-12-18 at 11:26 -0500, Steve Dickson wrote:
> Hello,
>
> How do I get f25 to create cores, these days?
Some more details here:
https://fedoraproject.org/wiki/Changes/coredumpctl
Michael
___
devel mailing list -- devel@lists.fedoraproject.o
On Sun, Dec 18, 2016 at 12:24:09PM -0500, Matthew Miller wrote:
> On Sun, Dec 18, 2016 at 05:56:04PM +0100, Jan Kratochvil wrote:
> > On Sun, 18 Dec 2016 17:26:40 +0100, Steve Dickson wrote:
> > > How do I get f25 to create cores, these days?
> > echo >/etc/sysctl.d/foo.conf "kernel.core_pattern=co
On Sun, Dec 18, 2016 at 05:56:04PM +0100, Jan Kratochvil wrote:
> On Sun, 18 Dec 2016 17:26:40 +0100, Steve Dickson wrote:
> > How do I get f25 to create cores, these days?
> echo >/etc/sysctl.d/foo.conf "kernel.core_pattern=core"; reboot
> It gets broken by:
> /usr/lib/sysctl.d/50-coredump.c
On Sun, 18 Dec 2016 17:26:40 +0100, Steve Dickson wrote:
> How do I get f25 to create cores, these days?
echo >/etc/sysctl.d/foo.conf "kernel.core_pattern=core"; reboot
It gets broken by:
/usr/lib/sysctl.d/50-coredump.conf
$ rpm -qf /usr/lib/sysctl.d/50-coredump.conf
systemd-231-10.fc25.
Hello,
How do I get f25 to create cores, these days?
I'm getting the segfault
[55108.290610] rpc.gssd[13264]: segfault at 0 ip 55dc90af9dde sp
7f9fb73cb7c0 error 4 in rpc.gssd[55dc90af3000+14000]
but no core so those address are meaningless.
Everything in the kernel is set:
f25# s
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 y
On Sun, Dec 18, 2016 at 3:27 PM, Alexander Bokovoy wrote:
> On su, 18 joulu 2016, Igor Gnatenko wrote:
>>
>> Unfortunately we stuck with very old (1.32.5, somewhere from 2012)
>> version of xmlrpc-c. I've rebased it to newer version (1.47.1, from
>> this month). It doesn't anymore use cmake (it wa
On su, 18 joulu 2016, Igor Gnatenko wrote:
Unfortunately we stuck with very old (1.32.5, somewhere from 2012)
version of xmlrpc-c. I've rebased it to newer version (1.47.1, from
this month). It doesn't anymore use cmake (it was port from one of our
contributors, official buildsys is autoconf+gnum
Unfortunately we stuck with very old (1.32.5, somewhere from 2012)
version of xmlrpc-c. I've rebased it to newer version (1.47.1, from
this month). It doesn't anymore use cmake (it was port from one of our
contributors, official buildsys is autoconf+gnumake) for building, now
it uses meson (you can
21 matches
Mail list logo
