Dne 18.1.2016 v 15:28 Miroslav Suchý napsal(a):
>
> Planned Outage: Copr upgrade - 2016-01-19 20:00 UTC
>
> There will be an outage starting at 2016-01-19 20:00 UTC, which will last
> approximately 1 hours.
>
> During the outage backend will stop processing new task and they will be
> queued i
On Mon, Jan 18, 2016 at 3:51 AM, Florian Weimer wrote:
> On 01/18/2016 11:02 AM, Nikos Mavrogiannopoulos wrote:
>
>> As Florian suggested it makes more sense to compartmentalize chrony so
>> that only a small controlled part of it needs to run with seccomp. My
>> recommendation, if you want to use
Thanks for telling me,
And efl is rebuilt accordingly.
- Original Message -
> Hi,
>
> I plan on building bullet-2.83 in rawhide this weekend. Bullet uses a
> soversion that's equal to the package version, so each bullet version
> bump requires a rebuild of all dependent packages.
>
> A
On Tuesday, 19 January 2016 at 18:06, Kevin Fenzi wrote:
> On Tue, 19 Jan 2016 15:20:33 +
> Richard Fearn wrote:
>
> > Hi
> >
> > > The same thing happened to me with mozilla-noscript updates that
> > > were submitted to stable and obsoleted by another set of updates
> > > I submitted to tes
On Tue, 2016-01-19 at 16:43 +, Fedora compose checker wrote:
> Missing expected images:
>
> Kde disk raw armhfp
> Kde live i386
> Kde live x86_64
>
> No images in this compose but not Rawhide 20160118
>
> Images in Rawhide 20160118 but not this:
>
> Kde live i386
> Scientific_kde live x86_6
On Tue, 2016-01-19 at 09:18 +, Petr Pisar wrote:
> This is doomed even without seccomp because malloc(3) is not
> async-signal-safe ;)
It sems to work reliably for us, but yeah, to do it safely, we need
to preallocate all the memory.
--
devel mailing list
devel@lists.fedoraproject.org
http
On Tue, 2016-01-19 at 10:16 +0100, Nikos Mavrogiannopoulos wrote:
> The issue is that blacklists are terrible from a security standpoint.
> That means that every new obscure system call added to the kernel
> will
> be available by default in your program.
Yes. This implies that seccomp should not
On Tue, 2016-01-19 at 08:08 -0800, Andrew Lutomirski wrote:
> One of these days I need to tidy up Sandstorm's seccomp policy and
> factor
> it into its own library. It's made a good showing for itself over
> the last
> year or so, and it's highly compatible.
I would be quite interested in this!
On Seg, 2016-01-18 at 07:37 -0500, Neal Gompa wrote:
> On Mon, Jan 18, 2016 at 7:27 AM, Jonathan Wakely
> wrote:
> > On 18/01/16 07:05 -0500, Honza Šilhan wrote:
> > >
> > > yes, autoremoval issue could be either caused by bad packaging
> > > [1] or when
> > > you are
> > > installing packages vi
On Tue, 19 Jan 2016 15:20:33 +
Richard Fearn wrote:
> Hi
>
> > The same thing happened to me with mozilla-noscript updates that
> > were submitted to stable and obsoleted by another set of updates
> > I submitted to testing today.
>
> Glad to hear it's not just me :)
>
> > It's not diffe
Missing expected images:
Kde disk raw armhfp
Kde live i386
Kde live x86_64
No images in this compose but not Rawhide 20160118
Images in Rawhide 20160118 but not this:
Kde live i386
Scientific_kde live x86_64
Cloud_atomic vagrant virtualbox x86_64
Scientific_kde live i386
Cloud_atomic vagrant li
On Tue, Jan 19, 2016, at 11:08 AM, Andrew Lutomirski wrote:
>
>
On Jan 19, 2016 7:41 AM, "Colin Walters" wrote:
>
>
>
>
>
>
>
> On Tue, Jan 19, 2016, at 04:16 AM, Nikos Mavrogiannopoulos wrote:
>
>
>
> > The issue is that blacklists are terrible from a security
> > standpoint.
>
> > That means tha
On Thu, 2015-12-24 at 15:01 -0600, Jason L Tibbitts III wrote:
> ardour4 (nphilipp)
> gegl (deji, nphilipp)
> gimp-data-extras (nphilipp)
> gimp-help (nphilipp)
> glade2 (nphilipp, alexl, caillon, caolanm, johnp, mbarnes, rhughes, rstrode,
> ssp, group::gnome-sig)
> python-augeas (xaeth, nphilipp)
On Jan 19, 2016 7:41 AM, "Colin Walters" wrote:
>
>
>
> On Tue, Jan 19, 2016, at 04:16 AM, Nikos Mavrogiannopoulos wrote:
>
> > The issue is that blacklists are terrible from a security standpoint.
> > That means that every new obscure system call added to the kernel will
> > be available by defau
On Tue, Jan 19, 2016, at 04:16 AM, Nikos Mavrogiannopoulos wrote:
> The issue is that blacklists are terrible from a security standpoint.
> That means that every new obscure system call added to the kernel will
> be available by default in your program.
https://github.com/seccomp/libseccomp/iss
Am Montag, den 18.01.2016, 07:05 -0500 schrieb Honza Šilhan:
> > From: "James Hogarth"
> > The autoremove reference might be the well known issue with
> > packagekit, not
> > dnf, that is not marking packages as installed rather than
> > dependencies.
> >
> > The default dnf configuration is auto
Am 18.01.2016 um 13:39 schrieb Heiko Adams:
Am Montag, den 18.01.2016, 12:27 + schrieb Jonathan Wakely:
On 18/01/16 07:05 -0500, Honza Šilhan wrote:
yes, autoremoval issue could be either caused by bad packaging [1]
or when you are
installing packages via yum or packagekit [2]. We are wor
Am 18.01.2016 um 13:16 schrieb Jonathan Wakely:
And the fact that /var/log/dnf.rpm.log doesn't show updates done by PK
is just annoying. Isn't there a single log file I can look at to see
what was updated, and when?
currently no because dnf, PK and yum-deprecated using different logging
inst
Hi
> The same thing happened to me with mozilla-noscript updates that
> were submitted to stable and obsoleted by another set of updates
> I submitted to testing today.
Glad to hear it's not just me :)
> It's not different. Both F23 and F22 updates are affected in the same
> way.
My 6.4.3 F22 u
Hi everyone!
Fedora 24 Changes submission deadline [1] is coming in one week on
January, the 26th.
Alpha release is currently planned on March, the 15th.
Please, submit your System Wide Changes by this deadline, earlier
better. As the deadline mainly applies for System Wide Changes it is
always g
On Mon, Jan 18, 2016 at 7:27 AM, Jonathan Wakely
wrote:
> On 18/01/16 07:05 -0500, Honza Šilhan wrote:
>>
>> yes, autoremoval issue could be either caused by bad packaging [1] or when
>> you are
>> installing packages via yum or packagekit [2]. We are working on better
>> integration
>> between DN
On Mon, Jan 18, 2016 at 11:02:44AM +0100, Nikos Mavrogiannopoulos wrote:
> As Florian suggested it makes more sense to compartmentalize chrony so
> that only a small controlled part of it needs to run with seccomp. My
> recommendation, if you want to use libraries in the filtered code, make
> their
On 01/19/2016 07:32 AM, Jiri Eischmann wrote:
> Hi,
> I'm writing an article on 6 most popular email clients in Fedora for
> Fedora Magazine. For each client I'd like to have a quote from a Fedora
> contributor why he/she is using that particular client.
> I'm missing representatives of Alpine and
Hi,
I'm writing an article on 6 most popular email clients in Fedora for
Fedora Magazine. For each client I'd like to have a quote from a Fedora
contributor why he/she is using that particular client.
I'm missing representatives of Alpine and Claws Mail. If you happen to
use them, can you please se
On Tue, Jan 12, 2016 at 3:02 PM, Josh Boyer wrote:
> On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga wrote:
>>> Please note there seem to be a btrfs regression in since 4.3:
>>> namely fstrim could discard beginning of the disk, removing the
>>> bootloader. This commit fixes the issue:
>>>
>>>
>
On 19/01/16 08:05 -0500, Nico Kadel-Garcia wrote:
This has never worked. Please re-read the manual page for "mock" The
"-r config" option finds "/etc/mock/config.cfg".
The man page says:
"Optionally if CONFIG ends in '.cfg', it is interpreted as full path
to config file."
And it works fine l
On Tue, Jan 19, 2016 at 4:48 AM, Miroslav Suchy wrote:
> Dne 19.1.2016 v 06:51 Dmitrij S. Kryzhevich napsal(a):
>> Like any others. Provide information about repo to /etc/mock/YOURCONFIG.cfg
>> In most cases in would be: /etc/mock/default.cfg
>>
>> You could find details for your particular copr r
Compose started at Tue Jan 19 05:15:02 UTC 2016
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0
On 19/01/16 11:36, Jonathan Wakely wrote:
On 19/01/16 11:10 +, Tom Hughes wrote:
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to te
On 19/01/16 12:32 +0100, Jakub Filak wrote:
On 01/19/2016 11:55 AM, Jonathan Wakely wrote:
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredu
Am 19.01.2016 um 12:36 schrieb Tom Hughes:
On 19/01/16 11:32, Jakub Filak wrote:
I cannot tell how it works in coredumpctl but ABRT C/C++ plugin can
be configured to ignore any path (this feature will be available in ABRT
2.8 [1]).
Right now, you can configure ABRT to drop core files of cert
On 19/01/16 11:10 +, Tom Hughes wrote:
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to terminate. I don't want hundreds
of them clog
On 19/01/16 11:32, Jakub Filak wrote:
I cannot tell how it works in coredumpctl but ABRT C/C++ plugin can
be configured to ignore any path (this feature will be available in ABRT
2.8 [1]).
Right now, you can configure ABRT to drop core files of certain programs
by adding program path to the Bla
On 01/19/2016 11:55 AM, Jonathan Wakely wrote:
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and ena
On Monday, 18 January 2016 at 20:03, Richard Fearn wrote:
> Hi,
[...]
> Later I realised that the F23 6.4.3 update had obsoleted the F23 6.4.0
> update - hence why it had inherited the 6.4.0 bug and notes.
>
> I was surprised that this happened :)
The same thing happened to me with mozilla-noscri
On 19/01/16 10:55, Jonathan Wakely wrote:
Is there a way to tell it to ignore certain core files?
I run parts of the GCC testsuite several times a day, and many of the
tests are expected to call abort() to terminate. I don't want hundreds
of them clogging up my journal, or being stored in ABRT.
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthe
On 01/14/2016 07:37 AM, Roman Tsisyk wrote:
Hi,
Fedora enables hardened builds [1] by default.
This implies -fomit-frame-pointer -fstack-protector and -fPIE.
[1]: https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
How it is supposed to be debugged by upstream developers?
It would be n
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthedocs.org/en/latest/examples.html#getting-core
Dne 19.1.2016 v 06:51 Dmitrij S. Kryzhevich napsal(a):
> Like any others. Provide information about repo to /etc/mock/YOURCONFIG.cfg
> In most cases in would be: /etc/mock/default.cfg
>
> You could find details for your particular copr repo in file with
> corresponding name in /etc/yum.repos.d dir
On 2016-01-18, Michael Catanzaro wrote:
> This all goes awry if, in the web process's signal handler, malloc
> decides to call open(),
This is doomed even without seccomp because malloc(3) is not
async-signal-safe ;)
-- Petr
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedora
On Mon, 2016-01-18 at 09:51 -0600, Michael Catanzaro wrote:
> > I appreciate what you are trying to do, but those seccomp filters
> > totally break encapsulation. I have no idea how to support this
> > properly, in a sustainable way. It appears very difficult to do
> > this
> > for independently
42 matches
Mail list logo
