Antoine Zellmeyer via devel writes:
> Sorry for the late answer, It seems to be working :) I was able to import and
> install packages signed with this certificate.
Thanks for confirming that it works as expected. I've made a new
release of rpm-sequoia, which includes this fix. I expect that
Hi Antoine
Antoine Zellmeyer via devel writes:
> Thanks ! I'll follow this issue.
Great. I posted a fix. It would be helpful if you could test that it
works for your case. Specifically, it would be helpful to hear back
that it:
- imports the certificate, and
- you are able to install
Hi Antoine,
Antoine Zellmeyer via devel writes:
> Following Fedora’s migration to Sequoia PGP, it seems that it isn’t possible
> to import an expired signing key anymore.
>
> rpm --import https://some.domain/public-keys/SOME_EXPIRED_RPM_KEY.public
> error: Certificate :
> The certificate is
Hi all,
I would like to unretire pgRouting. pgRouting was orphaned and retired
because of a problem in the packet requirements specification at the
time [1].
Since I use this PostgreSQL extension at work, I wanted to reintroduce
it in Fedora instead of using docker containers or custom
Hi Pavel,
On Wed, 14 Jun 2023 11:27:35 +0200,
Pavel Raiskup wrote:
> On úterý 13. června 2023 16:57:42 CEST Neal H. Walfield wrote:
> > On Thu, 08 Jun 2023 21:37:09 +0200,
> > Ondřej Budai wrote:
> > > RPM Sequoia's crypto policies can be configured, so you should be able
On Thu, 08 Jun 2023 21:37:09 +0200,
Ondřej Budai wrote:
> RPM Sequoia's crypto policies can be configured, so you should be able to
> re-enable SHA-1. However, this would
> be a global change, not only for EL6... See
>
On Tue, 06 Jun 2023 18:07:04 +0200,
Fabio Valentini wrote:
> On the other hand, the libreoffice flatpak bundles ~80 projects:
> - gpgme (huh?)
This...
> - openldap (huh?)
and perhaps this are probably because it is possible to sign and
encrypt ODF documents using OpenPGP. Some details are
I am also interested in keeping the LO packages in Fedora.
Hussein
On 6/6/23 20:55, Mattia Verga via devel wrote:
I'm forking this proposal off from the other thread, as it got buried
under tons of posts.
Shall we set up a libreoffice-sig to coordinate and ensure that
libreoffice and all
Hi Bob,
On Thu, 27 Apr 2023 19:55:42 +0200,
Robert Relyea wrote:
> A good read indeed.
Thanks, I'm happy you enjoyed it :).
> I do wonder about the error message:
>
> because: SHA1 is not considered secure since 1970-01-01T00:00:00Z
>
> I'm not sure where the date came from, but SHA1 wasn't
Hi all,
A year and a half ago, I began working with Panu on using Sequoia as
RPM's OpenPGP parser. I wrote up our journey from the initial
analysis, to adding the code to RPM, and to getting it into Fedora 38
(yay!) in a blog post. I'm mentioning it here, as I believe it is of
general interest
Hi Zbyszek,
Thanks for the clarifications.
Neal
On Mon, 27 Mar 2023 14:32:58 +0200,
Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Mar 27, 2023 at 01:29:38PM +0200, Neal H. Walfield wrote:
> > On Mon, 27 Mar 2023 13:16:45 +0200,
> > Zbigniew Jędrzejewski-Szmek wrote:
> >
On Mon, 27 Mar 2023 13:16:45 +0200,
Zbigniew Jędrzejewski-Szmek wrote:
> I agree. The scope of the issue is fairly narrow, and the underlying
> issue is an invalid signature made by the anydesk maintainers.
> We also have a simple command that users can use to work around
> the issue.
If you are
Hi Ben,
Thanks for working on this.
On Fri, 24 Mar 2023 19:25:46 +0100,
Ben Cotton wrote:
> Accepted blockers
> -
>
> 1. crypto-policies ― Insecure installed RPMs (like Google Chrome)
> prevent system updates in F38, can't be removed ― ASSIGNED
> ACTION: Maintainers to propose
Hi
I'll build rust-imagequant-sys in rawhide shortly in the side-tag
"f39-build-side-64368", and rebuild dependent packages (with the help of
@smani):
* gd-0:2.3.3-9.fc37.x86_64
* pngquant-0:2.17.0-2.fc37.x86_64
* python3-pillow-0:9.2.0-2.fc37.x86_64
* tuxpaint-1:0.9.28-4.fc37.x86_64
*
Hi Simo,
On Fri, 14 Oct 2022 18:28:01 +0200,
Simo Sorce wrote:
> At this time, as far as I know, there is no OpenPGP work of any kind on
> supporting PQC algorithms. Furthermore the way we use signatures in RPM
> really has no resemblance to the scenarios OpenPGP was built for.
>
> So we should
Hello everyone
This mail should serve as my self introduction to the devel community.
I am a (soon to be) computer science graduate, that has been working
in the Linux / open source world for about 6 years. I first started working
as a python developer in the GIS (geographic information
Hi Simo,
On Fri, 14 Oct 2022 22:36:09 +0200,
Neal H. Walfield wrote:
> On Fri, 14 Oct 2022 18:28:01 +0200,
> Simo Sorce wrote:
> > At this time, as far as I know, there is no OpenPGP work of any kind on
> > supporting PQC algorithms.
>
> The German BSI contracted MTG AG
On Thu, 13 Oct 2022 09:29:27 +0200,
Panu Matilainen wrote:
> >> - Some old, insecure (MD5/SHA1 based) signatures are rejected (this is
> >> in line with the stronger crypto settings proposed elsewhere for F38)
> >
> > Such a hardcoded restriction, without a way for the local administrator to
> >
On Fri, 14 Oct 2022 18:28:01 +0200,
Simo Sorce wrote:
> At this time, as far as I know, there is no OpenPGP work of any kind on
> supporting PQC algorithms.
The German BSI contracted MTG AG to design and implement PQC for
OpenPGP. They presented their work at IETF 113, and at the OpenPGP
email
I've just add --alowerasing for protonvpn...
LANG=C sudo dnf --releasever=37 --setopt=module_platform_id=platform:f37
--enablerepo=updates-testing $(rpm -q fedora-repos-modular >/dev/null && echo
--enablerepo=updates-testing-modular) --assumeno distro-sync --allowerasing;
Installing weak
Hi Dan,
On Mon, 05 Sep 2022 14:18:05 +0200,
Dan Čermák wrote:
> "Neal H. Walfield" writes:
> As Sequoia is written in Rust, what is your RISCV story? Fedora is (at
> least that's my impression) a quite popular choice for RISCV boards, so
> rpm working on RISCV would be
On Mon, 05 Sep 2022 10:12:23 +0200,
Alexander Sosedkin wrote:
> Mind the
> https://docs.fedoraproject.org/en-US/packaging-guidelines/CryptoPolicies
>
> Will we need to introduce a configuration mechanism to limit algorithm
> selection in Sequoia PGP? Or just wait untl it switches to OpenSSL?
Hi Paul,
Thanks for your comments.
On Fri, 02 Sep 2022 20:21:21 +0200,
Paul Wouters wrote:
> On Fri, 2 Sep 2022, Neal H. Walfield wrote:
>
> > Note: Sequoia currently uses Nettle on Fedora, but there is ongoing
> > work to port it to Sequoia to OpenSSL:
>
> I think t
Hi all,
rpm 4.18 is on the horizon and includes a new OpenPGP backend based on
Sequoia PGP.
https://rpm.org/wiki/Releases/4.18.0
https://sequoia-pgp.org/
Thanks to Fabio Valentini (decathorpe) for packaging not only
rpm-sequoia, but all of the Sequoia packages for Fedora.
This is my First time here, so Glad to be here:
Hello., is not precisely my idea but anyone can build a script, which can be
included in fedora live cd image for solving/troubleshoting this issues, at
least for a fedora default instalation, if is a custom install there is nothing
we can do
Error:
Problem 1: libnghttp2-1.41.0-3.fc33.i686 has inferior architecture
- libnghttp2-1.41.0-3.fc33.x86_64 does not belong to a distupgrade repository
- problem with installed package libnghttp2-1.41.0-3.fc33.i686
Problem 2: rdma-core-33.0-2.fc33.i686 has inferior architecture
-
On October 11, 2020 7:57:45 AM EDT, Nicolas Chauvet wrote:
>Le dim. 11 oct. 2020 à 07:47, Christopher Engelhard a
>écrit :
>>
>> Hi,
>> the nextcloud server package is currently stuck at ancient version 10
>> (current is 20) in EPEL7 (It's not (yet) available EPEL8 repos).
>>
>> I'd like to fix
On June 5, 2020 11:21:07 AM EDT, Greg Bailey wrote:
>On 6/5/20 2:21 AM, Menanteau wrote:
>> Hi there,
>>
>> is there a plan to update Mate in EPEL ?
>>
>> There was a demand to update to Mate 1.8 years ago but I didn't see
>> any answer. Mate 1.24 is currently available.
>>
>> Thanks
>
>I run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Aug 26, 2014 at 12:36:47PM +0200, Vít Ondruch wrote:
$ gem fetch power_assert
ERROR: Could not find a valid gem 'power_assert' (= 0), here is why:
Unable to download data from https://rubygems.org/ -
SSL_connect returned=1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Aug 11, 2014 at 03:31:56PM +0200, Karel Volný wrote:
you really haven't wondered for too long, now, in the middle of summer when
folks are on vacations, did you?
Which folks, exactly? These were all orphaned packages so no one was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I just did a query of all the packages in EPEL that are currently orphaned and
contain vulnerabilies. I'm wondering if any of them are still useful or if
they can be removed from the repos. Here's the list:
couchdb - epel-all
ejabberd - epel-5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Some people have already heard about the new Security Team making the rounds on
BZ trying to clean up vulnerabilities that still linger within our OS. Until
today I've not said much as I was waiting to see how successful we'd be at
trying to
Heya !
Welcome here and I'm glad that you finally jumped onboard :)
Feel free to ping me if you're looking for a sponsor.
best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org
had to be this way are really smart and had good reasons.
~m
Well, we may end up lawyered by Legal, but I think it's good we try to
realign ourselves and clear up few misunderstandings.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Apr 22, 2014 at 08:33:55PM +0200, Miloslav Trmač wrote:
I find it difficult to believe that most users [don't have Flash
installed]. AFAIK there is no data to say either way, and anecdotal
evidence from around here isn't supportive.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Apr 21, 2014 at 08:36:55AM -0400, Stephen Gallagher wrote:
...I'd
like to suggest a fifth Foundation, one to ultimately supersede all
the rest: Functional.
I think anytime anyone suggests a new foundation that supersedes all of what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Apr 21, 2014 at 07:04:03PM +0200, Michael Scherer wrote:
Le lundi 21 avril 2014 à 11:56 -0400, Eric H. Christensen a écrit :
On Mon, Apr 21, 2014 at 08:36:55AM -0400, Stephen Gallagher wrote:
Now, let me be further clear on this: I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Apr 21, 2014 at 12:37:57PM -0400, Stephen Gallagher wrote:
On 04/21/2014 11:56 AM, Eric H. Christensen wrote:
i packaging or otherwise making it easier for one to choose
proprietary software. When we start pushing proprietary solutions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Apr 15, 2014 at 11:01:51AM +0200, Jaroslav Reznik wrote:
== Detailed Description ==
The current level of integration into the desktop and applications does not
justify enabling the firewalld service by default. Additionally, the set of
releases named libdb starting F21
best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
+1 Mesos is definitively an asset for the Fedora Cloud Product and
would fit in some of our use cases.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
say that the fault lies with the crazy
updates policy that plague us.
regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Mar 17, 2014 at 02:52:43PM -0700, Adam Williamson wrote:
Well, I guess I'd better go read the docs.
reads docs
That was a clear, short and cogent explanation! I learned something, an
now I can continue!
I clearly didn't write that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 05:05:28AM -0400, Jaroslav Reznik wrote:
- Original Message -
Existing NIST and Red Hat documentation on OpenSCAP says that it's for
enterprise-level Linux infrastructure. Is any Fedora 21 product targeted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 03:00:20PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 09:25:16AM -0400, Eric H. Christensen wrote:
I disagree with this assessment. The workstation is exactly where much of
these hardening needs to take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 12:38:59PM -0400, Jan Lieskovsky wrote:
On Fri, Mar 14, 2014 at 09:25:16AM -0400, Eric H. Christensen wrote:
I disagree with this assessment. The workstation is exactly where much of
these hardening needs to take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 06:59:18PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 02:57:33PM -0400, Steve Grubb wrote:
On Friday, March 14, 2014 06:53:42 PM Matthew Garrett wrote:
Having separate server, workstation and cloud products
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 07:31:55PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 02:39:51PM -0400, Eric H. Christensen wrote:
On Fri, Mar 14, 2014 at 03:00:20PM +, Matthew Garrett wrote:
If there's a default policy that would make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 08:51:08PM +0100, Miloslav Trmač wrote:
2014-03-14 20:47 GMT+01:00 Reindl Harald h.rei...@thelounge.net:
why is only the average user relevant?
how do usesers get advanced?
by notice things which sounds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 07:45:53PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 03:41:30PM -0400, Eric H. Christensen wrote:
On Fri, Mar 14, 2014 at 07:31:55PM +, Matthew Garrett wrote:
How does the average user make an informed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 08:01:53PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 03:56:47PM -0400, Eric H. Christensen wrote:
On Fri, Mar 14, 2014 at 07:45:53PM +, Matthew Garrett wrote:
The failure mode of making the wrong choice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Mar 14, 2014 at 04:25:48PM -0600, Chris Murphy wrote:
On Mar 14, 2014, at 1:06 PM, Eric H. Christensen spa...@fedoraproject.org
wrote:
On Fri, Mar 14, 2014 at 06:59:18PM +, Matthew Garrett wrote:
On Fri, Mar 14, 2014 at 02:57:33PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Mar 13, 2014 at 04:40:01PM -0600, Chris Murphy wrote:
Existing NIST and Red Hat documentation on OpenSCAP says that it's for
enterprise-level Linux infrastructure. Is any Fedora 21 product targeted
mainly for enterprise deployment? Is
, it should be fixed anyway.
my 2 cts,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
out well for you,
Matthias
--
Matthias Runge mru...@matthias-runge.de
Thanks, I appreciate your kindness.
The same goes for all my Fedora Friends who are helping me to go through
these tough days :)
best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https
Use createrepo, its man page should be more than enough.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
to finish packaging
properly a few dependencies.
regards,
H.
2014-02-12 13:52 GMT+01:00 Miro Hrončok mhron...@redhat.com:
Hi,
I've just published a blogpost that summarizes what's going on with Python
3 as default in Fedora.
You can find it here:
http://eng.hroncok.cz/2014/02/12/python3-fedora
it so we may discuss
this based on facts ?
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
to finish packaging
properly a few dependencies.
regards,
H.
2014-02-12 13:52 GMT+01:00 Miro Hrončok mhron...@redhat.com:
Hi,
I've just published a blogpost that summarizes what's going on with Python
3 as default in Fedora.
You can find it here:
http://eng.hroncok.cz/2014/02/12/python3-fedora
(that is to be defined yet).
In a contributor-driven community, it shouldn't be a problem to accept new
products if it is backed appropriately.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org
It's also a negative message to the 1.4 k active contributors in fedora.
Or do you assume that most of them are paid by RH which is unlikely.
Don't forget that fp.o has been founded with two stakeholders: RH and the
community
H.
--
devel mailing list
devel@lists.fedoraproject.org
https
contributors. PERIOD
H.
[1] I think KDE SIG, I'm no user of the K Desktop but kudos guys for making
Fedora a choice distro for KDE users. You did great !
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm trying to figure out how to catalog what packages are using what
cryptographic ciphers within Fedora (specifically RC4). Does anyone know of a
good way of figuring that out?
- -- Eric
- --
.
btw, it wouldn't be wise to define that process while we're still in
Fedora.Next early stages, it'll just had more entropy.
First we should work to release our sample products, then use that
experience to define the process to bring a new product.
H.
--
devel mailing list
devel
infrastructure can handle it (rel-eng, QA, etc.), why should we
prevent them ?
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
it consciously. Think of it as the fast lane to find a
sponsor.
best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Ruby collections ? Did you mean SCL ? At the moment, the cloud WG hadn't
discuss any other options.
We're not the only stakeholders on that matters, these are topics requiring
collaboration with other WG.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Jan 21, 2014 at 04:26:19PM -0500, Dan Scott wrote:
I tried following
https://fedoraproject.org/wiki/Security_Tracking_Bugs?rd=Security/TrackingBugs
but it appears to depend on waiting on a CVE, which upstream did not
yet have... but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Jan 21, 2014 at 04:31:10PM -0500, Eric H. Christensen wrote:
On Tue, Jan 21, 2014 at 04:26:19PM -0500, Dan Scott wrote:
I tried following
https://fedoraproject.org/wiki/Security_Tracking_Bugs?rd=Security/TrackingBugs
but it appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Jan 16, 2014 at 02:03:14PM +0100, Nikos Mavrogiannopoulos wrote:
I am working on a draft common crypto policy for Fedora. The idea is to
be able to set a security level for all TLS/SSL connections in a system
(which will of course allow
/me wants the ability to push force on *private* branches
2014/1/15 Dridi Boukelmoune dridi.boukelmo...@gmail.com
On Wed, Jan 15, 2014 at 2:16 PM, Vít Ondruch vondr...@redhat.com wrote:
Dne 14.1.2014 21:41, Andrew Lutomirski napsal(a):
I have some trivial cleanups I want to make to a
.
Yeah, leveraging containers is a waste of time ... I agree with Nicolas,
containers are still immature at the moment, but that's part of our mission
as fedoraproject.org to make such technologies mature and bring them to
rock-solid.
best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
this and Software Collections)
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
of the major application that prevents us to do so.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
2014/1/14 Daniel P. Berrange berra...@redhat.com
In fact Fedora still ships GTK *1*. If we can't even get rid of GTK1,
then talk of killing GTK2 seems wildly over optimistic.
Regards,
Daniel
I'll quote myself again: at least from base images , not removing it from
repositories.
H
Hi,
there's a draft, i suggest that you start checking it.
http://fedoraproject.org/wiki/PackagingDrafts/Go
Taking a peek at Debian and OpenSuSE Go guidelines might be worthy:
http://pkg-go.alioth.debian.org/packaging.html
http://en.opensuse.org/openSUSE:Packaging_Go
Best regards,
H.
--
devel
My apologies for linking opensuse guidelines, i missed that point in your
mail.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
This discussion has now reached the phoronix point
http://www.phoronix.com/scan.php?page=news_itempx=MTU2MTE
Has anyone filed any tickets so we could move forward or will we continue
wasting time here ?
Best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
https
Congratulations for lowering the level of this discussion even lower than
it already was !
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Welcome in Fedora :)
Out of curiosity, are you only packaging it or also developing it ?
Anyway, it will be a useful library (no trolling about the rdrand
instruction ;))
Best regards,
H.
Le 5 janv. 2014 21:14, Jan Tulak jtu...@redhat.com a écrit :
Hi all
I'm an IT university student
2013/10/28 Jóhann B. Guðmundsson johan...@gmail.com
On 10/27/2013 11:34 AM, Nobrakal wrote:
2013/10/27, Frank Murphyfrankl...@gmail.com:
On Sun, 27 Oct 2013 19:05:37 +0800
Christopher Mengcicku...@gmail.com wrote:
It seems that most of members from the new formed groups are
working
Hi,
Fesco is entitled to delegate their authority to anyone they see fit to
do so.
For instance, FPC members are designated by Fesco and rule packaging
guidelines.
Besides, the final decision was taken by Fesco.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https
be glad to
serve as a liaison officer with both Ambassadors and Marketing groups.
I can't speak on the behalf of cwickert, but as one of the most supportive
member of the
Ambassadors group, I'm confident that he'll do an outstanding job -as
usual- on that matter
best regards,
H.
--
devel mailing
of our products in the open and keep the process
focused.
Either i would have been appointed into the Cloud WG or not, i would have
participated anyway in that effort.
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Oct 18, 2013 at 09:49:29PM +0200, Miloslav Trmač wrote:
On Wed, Oct 16, 2013 at 11:46 PM, Elio Maldonado emald...@redhat.com wrote:
No one in the NSS team was consulted on this. I usually monitor the FESCO
meetings announcements but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FESCo met today to address the NSS BEAST patch that left all software using NSS
vulnerable to the BEAST[0] vulnerability. The decision was made to implement
the patch that fixes this vulnerablity in F19 and F20. There are some programs
that may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sat, Oct 12, 2013 at 02:31:37PM -0500, Bruno Wolff III wrote:
On Sun, Oct 13, 2013 at 03:13:41 +0800,
P J P pj.pan...@yahoo.co.in wrote:
No, it does not. If yum is protecting users from un-installing a package
which could render the
of the
benefits of reducing our scope)
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sat, Sep 28, 2013 at 01:34:48PM +0200, Björn Persson wrote:
Eric H. Christensen wrote:
link-layer encryption like WPA2 won't protect anything anymore
What do you think WPA2 protects against? It has never protected
against anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, Sep 25, 2013 at 08:42:38PM +0200, Björn Persson wrote:
Eric H. Christensen wrote:
Authentication is based on WEP/WPA/WPA2 passphrase, possibly a MAC
address (BSSID), and 802.1 authentication.
There were no protests and no warnings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Sep 20, 2013 at 10:23:27PM +0200, Björn Persson wrote:
Thomas Woerner wrote:
If for
example you are using wifi connections at home, work, .. you can bind
these to the (for you) appropriate zone. For example work for your
work wifi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, Sep 10, 2013 at 03:50:58PM -0500, inode0 wrote:
On Tue, Sep 10, 2013 at 3:38 PM, Matthew Miller
mat...@fedoraproject.org wrote:
On Tue, Sep 10, 2013 at 03:24:28PM -0500, inode0 wrote:
What is under question is that it publishes a
and against the antlr3-C package in Fedora (bug #966973).
Regards,
Norvald H. Ryeng
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Hi,
since Gazpacho hasn't been maintained fro years and it requires an older
version of python-kiwi than currently packaged in F20, i'm retiring.
It has been superseeded by Glade 3 and no other packages should require it.
Best regards,
H.
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, Jul 17, 2013 at 03:14:09PM +0200, Lennart Poettering wrote:
On Wed, 17.07.13 07:57, Chris Adams (li...@cmadams.net) wrote:
That terribly sounds like my way or the high way.
That is Lennart's standard behavior.
And the thread just went ugly.
Not sure what the trigger for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I manage the cqrlog package in Fedora. One of the 'Requires' is
libmysqlclient.so.18. Up until F19 it hasn't been a problem. Now users are
seeing a dependency error that appears to be fulfilled by mariadb-libs.
# rpm -Uvh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Jun 28, 2013 at 11:43:44AM +0200, Tomasz Torcz wrote:
Tinyproxy package has a problem since F16 - because of missing tmpfilesd
snippet,
the program won't start without intervention of admin. Tinyproxy wnats to
store
pidfile in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Greetings, extra-patient friends:
The elections for the Fedora Board, Fedora Engineering Steering
Committee (FESCo), and Fedora Ambassadors Steering Committee (FAmSCo)
have concluded, and the results are shown below.
* * *
FESCo is electing 5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm working on text in the Fedora Security Guide discussing GRUB. There is a
sentence that reads [Fedora] ships with the GRUB boot loader on the x86
platform. and I am curious as to how true that is. Do we not use GRUB on any
other platform?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Jun 03, 2013 at 08:07:41AM -0500, Michael Cronenworth wrote:
Does anyone know how to contact Ian Weller?
He has not responded to his gmail account since I e-mailed him last
week. His last fedora activity seems to be about 6 months ago.
1 - 100 of 185 matches
Mail list logo
