wrong description of java-openjdk in bugzilla

2019-01-03 Thread jiri vanek
Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1661697 ;

Description of component (here, in BZ) is wrong: OpenJDK Runtime Environment 11 
Should be: OpenJDK rolling package for latest JDK

Can you please manage to fix it?
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: How do we find the source code for our services?

2019-01-03 Thread Brian (bex) Exelbierd
On Thu, Jan 3, 2019 at 8:58 AM Sayan Chowdhury  wrote:

> On Wed, Jan 2, 2019 at 2:56 PM Brian (bex) Exelbierd
>  wrote:
> >
> > I was looking for the source to the badges website/application to fix
> >
> > https://pagure.io/fedora-badges/issue/612
> >
> > How should I find it without asking someone on the infra team?
>
> We did fix and push the change in the source code in the 0.9.2
> release, but the *.rst files rendering the footer were getting pushed
> via a config file (I did not know that) and a lot of times we push the
> config files via our Ansible repository. So, it would be worth
> checking the ansible repository too.
>

I see, I think, that someone fixed the files yesterday in that repo.  That
repo appears to live solely on a backend machine and has a file only
mirror.

I am not going to go on about how this was also undiscoverable without a
human's help, but I do think it would be nice if our ansible playbooks were
more easily findable so we could get PRs, issues, and more importantly show
them off as part of the amazing OS created by Fedora.  They are good models
of infrastructure management.

regards,

bex



>
> --
> Sayan Chowdhury 
> GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>


-- 
Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: New to Fedora

2019-01-03 Thread Clement Verna
On Thu, 3 Jan 2019 at 05:26, Salman Siddiqui
 wrote:
>
> I am a Python Developer and I want to Join this Awesome Open Source
> Community. I Love Fedora and now want to contribute in it for GSOC
> 2019 to Become a Part of this Community.
>

Hi Salman and Welcome :)

Did you take a look at the Python applications we develop and maintain
(https://github.com/fedora-infra) ? Are you interested in something
particular ?

Also you can find me (irc nickname cverna) or others on the
#fedora-apps IRC channel on freenode.

>
>
> Thanks
> Salman Siddiqui
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: How do we find the source code for our services?

2019-01-03 Thread Clement Verna
On Thu, 3 Jan 2019 at 11:31, Brian (bex) Exelbierd  wrote:
>
>
>
> On Thu, Jan 3, 2019 at 8:58 AM Sayan Chowdhury  wrote:
>>
>> On Wed, Jan 2, 2019 at 2:56 PM Brian (bex) Exelbierd
>>  wrote:
>> >
>> > I was looking for the source to the badges website/application to fix
>> >
>> > https://pagure.io/fedora-badges/issue/612
>> >
>> > How should I find it without asking someone on the infra team?
>>
>> We did fix and push the change in the source code in the 0.9.2
>> release, but the *.rst files rendering the footer were getting pushed
>> via a config file (I did not know that) and a lot of times we push the
>> config files via our Ansible repository. So, it would be worth
>> checking the ansible repository too.
>
>
> I see, I think, that someone fixed the files yesterday in that repo.  That 
> repo appears to live solely on a backend machine and has a file only mirror.
>
> I am not going to go on about how this was also undiscoverable without a 
> human's help, but I do think it would be nice if our ansible playbooks were 
> more easily findable so we could get PRs, issues, and more importantly show 
> them off as part of the amazing OS created by Fedora.  They are good models 
> of infrastructure management.

This is currently worked on, and afaik waiting on
https://pagure.io/pagure/pull-request/4054 to be finished before we
can host our ansible repo on pagure.io.

>
> regards,
>
> bex
>
>
>>
>>
>> --
>> Sayan Chowdhury 
>> GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
>> ___
>> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
>> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
>
>
> --
> Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com
> Fedora Community Action & Impact Coordinator
> @bexelbie | http://www.winglemeyer.org
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: wrong description of java-openjdk in bugzilla

2019-01-03 Thread Mikolaj Izdebski
On Thu, Jan 3, 2019 at 9:25 AM jiri vanek  wrote:
>
> Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1661697 ;
>
> Description of component (here, in BZ) is wrong: OpenJDK Runtime Environment 
> 11
> Should be: OpenJDK rolling package for latest JDK
>
> Can you please manage to fix it?

Component description in Bugzilla is taken from summary of SRPM in
rawhide. You can change the summary yourself and it should be
eventually propagated to Bugzilla.

--
Mikolaj
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: New to Fedora

2019-01-03 Thread Salman Siddiqui
Hello. I am really interested in Pagure. I have even started working with
it and want to continue working with it. Its really amazing.

Thanks
Salman Siddiqui

On Thu, 3 Jan 2019, 3:57 pm Clement Verna  On Thu, 3 Jan 2019 at 05:26, Salman Siddiqui
>  wrote:
> >
> > I am a Python Developer and I want to Join this Awesome Open Source
> > Community. I Love Fedora and now want to contribute in it for GSOC
> > 2019 to Become a Part of this Community.
> >
>
> Hi Salman and Welcome :)
>
> Did you take a look at the Python applications we develop and maintain
> (https://github.com/fedora-infra) ? Are you interested in something
> particular ?
>
> Also you can find me (irc nickname cverna) or others on the
> #fedora-apps IRC channel on freenode.
>
> >
> >
> > Thanks
> > Salman Siddiqui
> > ___
> > infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> > To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to
> infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
>
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [EPEL-devel] Re: Fedora project login

2019-01-03 Thread Eduard Lucena
Hi, sorry for the way I'm answering I'm on mobile Gmail app.

El mié., 2 de enero de 2019 16:00, James Cassell <
fedoraproj...@cyberpear.com> escribió:

> On Wed, Jan 2, 2019, at 1:31 PM, Kevin Fenzi wrote:
> > On 1/2/19 12:44 AM, Michael A. Peters wrote:
> > > Hello,
> > >
> > > Extremely BAD experience trying to log in at
> > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-9a4a06731c
> >
> > Sorry to hear it. ;(
> >
> > > First I couldn't remember my username but I could remember my password
> > > and the VERY BROKEN DESIGN does not allow me to request it send me a
> > > reminder of my username.
> > >
> > > Finally figured out my username and it sent me a password reset.
> > >
> > > Reset password, and it would not let me log in.
> > >
> > > Attempted several times.
> > >
> > > Figuring I entered it wrong and did the reset again.
> > >
> > > Tried the password the way it was in my password manager and it said I
> > > couldn't reset it to an old password.
> > >
> > > So regenerated new password - but with that also could not log in.
> >
> > Can you expand on that? What did it do? You got a username/password
> > dialog? It said password incorrect? or any other messages/errors?
> >
>
> Here's my experience:
> Go to https://bodhi.fedoraproject.org
> Click "Login"
> Dialog pops up asking for user/pass
> Click Cancel
> Page comes up for FAS log in
> Put Fedora Account System credentials
> Click "Log In"
> Get redirected back to bodhi, logged in.
>
> Typing my FAS credentials into the first pop up dialog just shows the
> dialog again and does not log me in.
>

I had the same experience for all id.fpo sites when I'm behind my company
proxy, and it works only with Google Chrome, Firefox just said forbidden
when you 'escape' the popup login. It doesn't happen in my home internet
using the same machine and browsers, there I never get the popup login,
just the normal id.fpo login.

Br,
Eduard Lucena
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: Proposal : Use OSBS to build the fedora container base image

2019-01-03 Thread Dennis Gregorovic
Forwarding info I got from Tomas off-line...

"""
oz should be py3-ready according to clancellete (not tested by me). I've
started some work on ImageFactory, but didn't get too far as there were
other priorities. It seemed to be doable (waited on oz in that time), so if
we want to give it some resources (very rough estimation ~1month/man to get
both things running together)

About ImageFactory maintaining - I don't think there is anybody actively
maintaining it, nearest shot is Brendan. Both mailing lists are dead from
2014/2015.

btw, for OSBS it should be no difference while koji builders are still
python2. ImageFactory is running there and needs to be same python version
as kojid (it is used as library, not separate process).
"""


On Wed, Jan 2, 2019 at 2:24 PM Dennis Gregorovic  wrote:

> There has been some progress as Tomas Kopecek added py3 patches to Oz last
> year... https://github.com/clalancette/oz/pull/263
>
> Not sure how much effort is needed to add py3 support to ImageFactory
> itself.  Copying Tomas as Brendan.  Neither of them maintain IF, but they
> have contributed to it in the past and may be able to help.
>
> -- Dennis
>
>
>
> On Mon, Dec 3, 2018 at 2:02 PM Neal Gompa  wrote:
>
>> On Mon, Dec 3, 2018 at 1:39 PM Clement Verna 
>> wrote:
>> >
>> > Hi all,
>> >
>> > I would like to get feedbacks on the following proposal. Use OSBS to
>> > build the fedora container base image, indeed OSBS has the capability
>> > to build a base container image using a kickstart file.
>> > To do this OSBS needs a Dockerfile, a kickstart file and an
>> > image-build.conf file stored in dist-git, then OSBS will trigger an
>> > ImageFactory task in Koji in order to build to base image and then it
>> > will build the base container based on the artifacts built in Koji.
>> >
>>
>> Is anyone actively maintaining ImageFactory? Because it's still Python
>> 2 only and I haven't seen anyone really working on fixing that, much
>> less supporting more images easily...
>>
>>
>> --
>> 真実はいつも一つ!/ Always, there's only one truth!
>> ___
>> devel mailing list -- de...@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org
>>
>
>
> --
> Dennis Gregorovic
> Manager, PnT DevOps
> Red Hat
> dgre...@redhat.comT: +1-978.392.3112M: +1-617.901.9799
>


-- 
Dennis Gregorovic
Manager, PnT DevOps
Red Hat
dgre...@redhat.comT: +1-978.392.3112M: +1-617.901.9799
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


[PATCH] Add CDN testing cloudfront redirect for atomic repo

2019-01-03 Thread Sinny Kumari
Hi,

Currently, we are using two different cloudfront distributions to CDN
content for
/atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we
see
an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this
issue and provide faster delivery of ostree content, we have created a
cloudfront distribution where we CDN /atomic/repo/ .

This patch (available in attachment) adds some redirect rules to use new
cloudfront urls for testing purpose and see how much improvement we get in
content delivery. This patch shouldn't impact existing infra setup.

Thanks,
Sinny

-- 
http://sinny.io/
From e42132ff2f5d5935cd2b0124091201d6a6cf2a9f Mon Sep 17 00:00:00 2001
From: Sinny Kumari 
Date: Thu, 3 Jan 2019 20:57:01 +0530
Subject: [PATCH] Add CDN testing cloudfront redirect for atomic repo

Signed-off-by: Sinny Kumari 
---
 roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf b/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
index 1f39e6c5d..8fa8a3420 100644
--- a/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
+++ b/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
@@ -23,5 +23,9 @@ RedirectMatch 302 ^/atomic/repo/deltas/(.*) https://d14lrfjen188b1.cloudfront.ne
 RedirectMatch 302 ^/atomic/repo/objects/(.*) https://d2os45suu8yck8.cloudfront.net/$1
 RedirectMatch 302 ^/atomic/repo/(.*) https://kojipkgs.fedoraproject.org/atomic/repo/$1
 
+RedirectMatch 302 ^/cdn-testing/atomic/repo/deltas/(.*) http://d1dgksnh07m2j5.cloudfront.net/deltas/$1
+RedirectMatch 302 ^/cdn-testing/atomic/repo/objects/(.*) http://d1dgksnh07m2j5.cloudfront.net/objects/$1
+RedirectMatch 302 ^/cdn-testing/atomic/repo/(.*) https://kojipkgs.fedoraproject.org/atomic/repo/$1
+
 RedirectMatch 302 ^/iot/repo/objects/(.*) https://d35xkejx7yn5rc.cloudfront.net/$1
 RedirectMatch 302 ^/iot/repo/(.*) https://kojipkgs.fedoraproject.org/compose/iot/repo/$1
-- 
2.20.1

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] Add CDN testing cloudfront redirect for atomic repo

2019-01-03 Thread Dusty Mabe


On 1/3/19 10:40 AM, Sinny Kumari wrote:
> Hi,
> 
> Currently, we are using two different cloudfront distributions to CDN content 
> for
> /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we see
> an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this
> issue and provide faster delivery of ostree content, we have created a
> cloudfront distribution where we CDN /atomic/repo/ .
> 
> This patch (available in attachment) adds some redirect rules to use new
> cloudfront urls for testing purpose and see how much improvement we get in
> content delivery. This patch shouldn't impact existing infra setup.
>

I'd like to highlight this is for testing purposes only and should have a short
life. We just wanted to make sure the "redirect penalty" that we experience with
our prod redirects is also reflected in our testing so we can get more accurate
results.

Sinny,

One thing we might want to do is use https for the cloudfron URLs like we are 
for
the prod redirects. Otherwise LGTM. 

Dusty

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: [PATCH] Add CDN testing cloudfront redirect for atomic repo

2019-01-03 Thread Sinny Kumari
On Thu, Jan 3, 2019 at 9:16 PM Dusty Mabe  wrote:

>
>
> On 1/3/19 10:40 AM, Sinny Kumari wrote:
> > Hi,
> >
> > Currently, we are using two different cloudfront distributions to CDN
> content for
> > /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup
> we see
> > an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome
> this
> > issue and provide faster delivery of ostree content, we have created a
> > cloudfront distribution where we CDN /atomic/repo/ .
> >
> > This patch (available in attachment) adds some redirect rules to use new
> > cloudfront urls for testing purpose and see how much improvement we get
> in
> > content delivery. This patch shouldn't impact existing infra setup.
> >
>
> I'd like to highlight this is for testing purposes only and should have a
> short
> life. We just wanted to make sure the "redirect penalty" that we
> experience with
> our prod redirects is also reflected in our testing so we can get more
> accurate
> results.
>
> Sinny,
>
> One thing we might want to do is use https for the cloudfron URLs like we
> are for
> the prod redirects. Otherwise LGTM.
>

Ah yes, nice catch. Updated patch is available in the attachment.
This is the sad part part of doing copy paste :/



> Dusty
>
>
>

-- 
http://sinny.io/
From 420894ee34e7561d134bc3713801c9ec3edde5cd Mon Sep 17 00:00:00 2001
From: Sinny Kumari 
Date: Thu, 3 Jan 2019 20:57:01 +0530
Subject: [PATCH] Add CDN testing cloudfront redirect for atomic repo

Signed-off-by: Sinny Kumari 
---
 roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf b/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
index 1f39e6c5d..63c97568b 100644
--- a/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
+++ b/roles/download/files/httpd/dl.fedoraproject.org/rewrite.conf
@@ -23,5 +23,9 @@ RedirectMatch 302 ^/atomic/repo/deltas/(.*) https://d14lrfjen188b1.cloudfront.ne
 RedirectMatch 302 ^/atomic/repo/objects/(.*) https://d2os45suu8yck8.cloudfront.net/$1
 RedirectMatch 302 ^/atomic/repo/(.*) https://kojipkgs.fedoraproject.org/atomic/repo/$1
 
+RedirectMatch 302 ^/cdn-testing/atomic/repo/deltas/(.*) https://d1dgksnh07m2j5.cloudfront.net/deltas/$1
+RedirectMatch 302 ^/cdn-testing/atomic/repo/objects/(.*) https://d1dgksnh07m2j5.cloudfront.net/objects/$1
+RedirectMatch 302 ^/cdn-testing/atomic/repo/(.*) https://kojipkgs.fedoraproject.org/atomic/repo/$1
+
 RedirectMatch 302 ^/iot/repo/objects/(.*) https://d35xkejx7yn5rc.cloudfront.net/$1
 RedirectMatch 302 ^/iot/repo/(.*) https://kojipkgs.fedoraproject.org/compose/iot/repo/$1
-- 
2.20.1

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: Proposal : Use OSBS to build the fedora container base image

2019-01-03 Thread Neal Gompa
On Thu, Jan 3, 2019 at 9:54 AM Dennis Gregorovic  wrote:
>
> Forwarding info I got from Tomas off-line...
>
> """
> oz should be py3-ready according to clancellete (not tested by me). I've 
> started some work on ImageFactory, but didn't get too far as there were other 
> priorities. It seemed to be doable (waited on oz in that time), so if we want 
> to give it some resources (very rough estimation ~1month/man to get both 
> things running together)
>
> About ImageFactory maintaining - I don't think there is anybody actively 
> maintaining it, nearest shot is Brendan. Both mailing lists are dead from 
> 2014/2015.
>
> btw, for OSBS it should be no difference while koji builders are still 
> python2. ImageFactory is running there and needs to be same python version as 
> kojid (it is used as library, not separate process).
> """
>

The PRs for Koji to move to Python 3 are waiting for their review to
be completed to be merged:

* https://pagure.io/koji/pull-request/1117
* https://pagure.io/koji/pull-request/921
* https://pagure.io/koji/pull-request/891

Basically, as soon as someone gives a crap about it, these can be
finished up, merged, and we can have Koji switched to Python 3.



--
真実はいつも一つ!/ Always, there's only one truth!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


do we use mash any more?

2019-01-03 Thread Ken Dreyer
I was going to update the Mash README at https://pagure.io/mash to
indicate that the Fedora Project no longer uses this software, but I
wanted to be sure that's really true.

- Ken
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: do we use mash any more?

2019-01-03 Thread Neal Gompa
On Thu, Jan 3, 2019 at 1:11 PM Ken Dreyer  wrote:
>
> I was going to update the Mash README at https://pagure.io/mash to
> indicate that the Fedora Project no longer uses this software, but I
> wanted to be sure that's really true.
>

Mash is dead. We killed it a little over a year ago.



-- 
真実はいつも一つ!/ Always, there's only one truth!
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


Re: do we use mash any more?

2019-01-03 Thread Ken Dreyer
On Thu, Jan 3, 2019 at 11:15 AM Neal Gompa  wrote:
>
> On Thu, Jan 3, 2019 at 1:11 PM Ken Dreyer  wrote:
> >
> > I was going to update the Mash README at https://pagure.io/mash to
> > indicate that the Fedora Project no longer uses this software, but I
> > wanted to be sure that's really true.
> >
>
> Mash is dead. We killed it a little over a year ago.

Thank you Neal. I've updated the README in
https://pagure.io/mash/pull-request/17 with this information.
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org