[Tonight I did a yum upgrade on a slightly newer intel gfx system, i915G, and
did not have this problem, so...]
Stephen John Smoogen composed on 2015-01-09 09:15 (UTC-0700):
> Felix Miata wrote:
>> P4 2.8G, no hyperthreading, with i865G video.
>> F20 and F21 work normally.
>> Kernel 3.19.0-0.r
It has happened again. :-/
| This message is a notice that Fedora 19 is now at end of life. Fedora
| has stopped maintaining and issuing updates for Fedora 19. It is
| Fedora's policy to close all bug reports from releases that are no
| longer maintained.
|
| [...]
As I found it odd, that agai
On Sat, Jan 10, 2015 at 12:37 PM, Michael Schwendt wrote:
> It has happened again. :-/
>
> | This message is a notice that Fedora 19 is now at end of life. Fedora
> | has stopped maintaining and issuing updates for Fedora 19. It is
> | Fedora's policy to close all bug reports from releases that ar
Big *sigh*.
Guys, this is not funny anymore. Almost as if some people at Fedora try to
test how long one can keep one's temper. Well, this is embarrasing and not
casting a positive light on the Fedora Project package collection:
https://bugzilla.redhat.com/460557
Package and software are in a
On Fri, Jan 09, 2015 at 10:18:54AM -0700, Orion Poplawski wrote:
> On 01/09/2015 09:57 AM, Nathaniel McCallum wrote:
> > On Fedora 21, OpenSSL doesn't appear to support NIST p224r1, but *does*
> > support other NIST curves. I presume this was intentional, but I'm not
> > sure why. Can someone enlig
On Sat, 10 Jan 2015 00:27:15 -0600, Bruno Wolff III wrote:
> While working on a spec file to cause build failure if new fonts showed
> up in a package, I noticed two oddities with the checking for unpackaged
> files.
>
> An unpackaged empty directory will not trigger a build failure.
That's an
Compose started at Sat Jan 10 05:15:03 UTC 2015
Broken deps for i386
--
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[aeskulap]
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6
aesku
On Sat, Jan 10, 2015 at 12:54:27PM +0100, Michael Schwendt wrote:
> Big *sigh*.
>
> Guys, this is not funny anymore. Almost as if some people at Fedora try to
> test how long one can keep one's temper. Well, this is embarrasing and not
> casting a positive light on the Fedora Project package colle
Announcing the creation of a new nightly release validation test event
for Fedora 22 Rawhide 20150110. 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 2015-01-10, 11:54 GMT, Michael Schwendt wrote:
> Guys, this is not funny anymore. Almost as if some people at
> Fedora try to
> test how long one can keep one's temper. Well, this is embarrasing and not
> casting a positive light on the Fedora Project package collection:
I would just go ahead
On Sat, 10 Jan 2015 14:44:39 +0100, Matěj Cepl wrote:
> I would just go ahead with
> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
As much sense as this procedure may make in _some_ cases, it has been a
failure for other packagers before. They emerge only to end the
> On Thu, 2015-01-08 at 08:47 -0500, Paul Wouters wrote:
>> On Thu, 8 Jan 2015, Dhiru Kholia wrote:
>>
>> >> | Your package accepts/processes untrusted input.
>> >>
>> >> This seems to be about every package that I use, because I most if not
>> >> all tools process untrusted data from the Inter
On Fri, Jan 9, 2015 at 3:10 AM, Jan Synacek wrote:
> Jan Staněk writes:
>> Hi guys,
>> as the new BerkeleyDB 6.x has a more restrictive license than the
>> previous versions (AGPLv3 vs. LGPLv2), and due to that many projects
>> cannot use it, perhaps it is time to get rid of it from Fedora for go
On Sat, Jan 10, 2015 at 12:58:07 +0100,
Tomasz Torcz wrote:
Kinda affects Tor, too: https://bugzilla.redhat.com/show_bug.cgi?id=1164210
I surprised that tor supports any of the NIST curves given questions about
how they were developed and that 25519 is available as an alternative.
--
dev
On Sat, Jan 10, 2015 at 13:04:27 +0100,
Michael Schwendt wrote:
On Sat, 10 Jan 2015 00:27:15 -0600, Bruno Wolff III wrote:
If a file is covered by %exclude in the main package, but is not included
in any subpackage, it will not trigger a build failure.
%exclude is global per spec file, or e
Hi,
I've been testing in advance to make mass rebuilds changing macros and the
results are pretty good (I mean x86_64 f20, f21 + grsecurity custom
kernels). It is clear that we will find regressions, we just have to start
and test it.. It is an important and necessary change.
If anyone is interes
> On Saturday, 10 January 2015 1:34 AM, Mike Pinkerton wrote:
> Even if you want to do key-based authentication rather than password,
> you still need to use password initially to get the key onto the
> remote box.
True!
---
Regards
-Prasad
http://feedmug.com
--
devel mailing list
devel@lis
On Sat, 10 Jan 2015 09:51:19 -0600, Bruno Wolff III wrote:
> My guess would have
> been that %excludes would have been developed specifically for making it
> convenient to exclude a directory in the main package that needs to be owned
> by a subpackage.
Rather: a quick way to not package a fil
On Sat, Jan 10, 2015 at 18:33:14 +0100,
Michael Schwendt wrote:
Deleting files in %install is considered cleaner by many, because it
ensures that a file is not found inside the %buildroot anymore and cannot
be included accidentally either. The drawback is obvious: There ought to
be a comment e
Will F22 introduce plasma5 when it rolls out?
--
Mike Chambers
Madisonville, KY
"Best little town on Earth!"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Sat, 10 Jan 2015 12:06:10 -0600, Bruno Wolff III wrote:
> In this particular case some stuff gets added depending on whether or
> not the build process finds all of the fonts that are needed. I wanted
> this to fail during build if any were not found,
%check
[ -f %{buildroot}%{_datadir}/font
- Original Message -
> I surprised that tor supports any of the NIST curves given questions about
> how they were developed and that 25519 is available as an alternative.
It was never an alternative to the NIST curves because it was never part
of any standard, and doesn't support key excha
On Sat, Jan 10, 2015 at 03:19:28PM +, Peter Robinson wrote:
> > On Thu, 2015-01-08 at 08:47 -0500, Paul Wouters wrote:
> >> On Thu, 8 Jan 2015, Dhiru Kholia wrote:
> >>
> >> >> | Your package accepts/processes untrusted input.
> >> >>
> >> >> This seems to be about every package that I use,
Does this proposal apply to native non-C/C++ programs?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings fro
24 matches
Mail list logo
