Hi All,
Please note that mod_security_crs (Core Rule Set, now from OWASP) has
been updated to 3.0.0 in rawhide, the update should be smooth for most
standard setup.
Copr repo athmane/mod_security[1] has been updated as well, note that
EL7 is broken atm due to RHBZ #1444652 [2]
[1] https://copr.
Missing expected images:
Xfce raw-xz armhfp
Failed openQA tests: 19/111 (x86_64), 6/18 (i386), 1/2 (arm)
New failures (same test did not fail in 26-20170421.n.0):
ID: 85556 Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/85556
ID: 85558
Am Sun, 23 Apr 2017 17:14:50 + (UTC)
schrieb Globe Trotter :
> From: Ralf Corsepius
> To: devel@lists.fedoraproject.org
> Sent: Sunday, April 23, 2017 12:03 PM
> Subject: Re: how to handle source code from github
>
> On 04/23/2017 06:40 PM, Globe Trotter wrote:
> > Thanks!
> >
You can set the name of the file via the GitHub API when you download it.
For jQuery (packaged as js-jquery), I use:
https://github.com/jquery/jquery/archive/%{version}/jquery-%{version}.tar.gz
This will work for any GitHub project which tags released versions:
https://github.com///archive//.tar.
From: Ralf Corsepius
To: devel@lists.fedoraproject.org
Sent: Sunday, April 23, 2017 12:03 PM
Subject: Re: how to handle source code from github
On 04/23/2017 06:40 PM, Globe Trotter wrote:
> Thanks!
>
> Would you know how to make upstream provide the tarball? Is it something
> a
On 04/23/2017 06:40 PM, Globe Trotter wrote:
Thanks!
Would you know how to make upstream provide the tarball? Is it something
as simple as creating a tarball and dumping it to git?
github creates them on demand.
Ralf
___
devel mailing list -- devel
Thanks!
Would you know how to make upstream provide the tarball? Is it something as
simple as creating a tarball and dumping it to git?
I have four packages on Fedora. I would like to put in another four for review
and adoption.
THanks again!
From: Florian Lehner
To: Globe Trotter ; Dev
Missing expected images:
Cloud_base qcow2 x86_64
Atomic qcow2 x86_64
Cloud_base raw-xz x86_64
Xfce raw-xz armhfp
Atomic raw-xz x86_64
Minimal raw-xz armhfp
Failed openQA tests: 67/109 (x86_64), 17/18 (i386)
Old failures (same test failed in Rawhide-20170422.n.0):
ID: 85372 Test: x86_64 Se
Hi Luya,
On Tue, Apr 11, 2017 at 8:19 AM, Luya Tshimbalanga
wrote:
> I am looking for swaping review with swatchbooker:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1441046
> An odd issue is the startup of the application with the correct path
> within the binary leaving baffled. Improvemen
I am trying to package the following from github for fedora. (Actually, I have
been using my own RPM for years so it is hopefully not a major task).
https://github.com/maitra/thaali
Anyway, I wanted to ask how I should put the Source code from there
The source is at:
https://github.com/maitra/
Thanks! I had all the packages installed (updated versions). But removing
~/.koji/config seems to have done the trick.
Thanks again!Best wishes.
From: Sérgio Basto
To: Globe Trotter ; Development discussions related to
Fedora
Sent: Sunday, April 23, 2017 10:02 AM
Subject: Re: Quest
From: https://fedoraproject.org/wiki/ReleaseEngineering/FlagDay2016
Question: I get an error "SSL: CERTIFICATE_VERIFY_FAILED" when trying
to use koji
Answer: This means you have an outdated configuration file. Please make
sure first that you have the package versions as described in the l
From: Jens Lody
To: devel@lists.fedoraproject.org
Sent: Sunday, April 23, 2017 9:49 AM
Subject: Re: Question on koji error: SSLError: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)
Am Sun, 23 Apr 2017 13:29:30 + (UTC)
schrieb Globe Trotter :
>
> $ op
Am Sun, 23 Apr 2017 13:29:30 + (UTC)
schrieb Globe Trotter :
>
> $ openssl s_client -showcerts -connect koji.fedoraproject.org:443
>
> gives no errors but
> $ /usr/lib64/nss/unsupported-tools/tstclnt -CCC -D -b -h
> koji.fedoraproject.org -p 443tstclnt: error setting SSL/TLS version
> range
From: Peter Robinson
To: Development discussions related to Fedora
Cc: Globe Trotter
Sent: Sunday, April 23, 2017 6:31 AM
Subject: Re: Question on koji error: SSLError: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)
On Sun, Apr 23, 2017 at 11:28 AM, Kai
On Sun, Apr 23, 2017 at 11:28 AM, Kai Engert wrote:
> On Sun, 2017-04-23 at 01:05 +, Globe Trotter wrote:
>> Hi,
>> I am trying to build a package on koji using:
>> koji build --scratch f25 thaali-0.4.2-1.fc25.src.rpm
>>
>> and I get:
>> SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate
On Sun, 2017-04-23 at 01:05 +, Globe Trotter wrote:
> Hi,
> I am trying to build a package on koji using:
> koji build --scratch f25 thaali-0.4.2-1.fc25.src.rpm
>
> and I get:
> SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
> (_ssl.c:661)
>
> What does this mean? I ha
Hello,
last bugfix release of DevAssisatnt [1] happened in September 2016, last
"major" release happened in April 2015. The project has not active
contributors, only me as a (very) low prio maintainer.
Users are experiencing problems with the assistants, as they are not
compatible with curre
Hey.
I'm orphaning Estonian ID card packages. I can not guarantee stable
update and maintenance of those packages, because of lack of time. So
I'm looking a person or persons who can take it over.
List of packages:
rpms/esteidcerts -- Estonian ID-card certificates ( master f26 f25
f24 )
19 matches
Mail list logo
