strigazi added a new comment to an issue you are following:
``
> Or, we could track the latest in Fedora stable and the alpha releases in
> rawhide -- that seems a bit more true to rawhide, and still worthwhile, but I
> can imagine people wanting to run the N-1 version, and we don't have a way
jlebon added a new comment to an issue you are following:
``
> discussions and troubleshooting Fedora build pipeline/releng (bodhi, punji,
> etc.) for Atomic will be on the new channel #fedora-atomic. Content
> discussions which start there will get re-directed to #atomic.
Sorry if I'm missing
===
#fedora-meeting-1: fedora_atomic_wg
===
Meeting started by jberkus at 17:01:42 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-19/fedora_atomic_wg.2017-07-19-17.01.log.html
.
dustymabe added a new comment to an issue you are following:
``
Discussion in the meeting today and votes in the ticket means we are approving
jberkus' proposal. the [mailing
list](https://lists.fedoraproject.org/admin/lists/atomic.lists.fedoraproject.org/)
has been created and the irc channel
The issue: `Disable deltarpms in the Fedora base docker image` of project:
`atomic-wg` has been assigned to `maxamillion` by maxamillion.
https://pagure.io/atomic-wg/issue/297
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send
sinnykumari added a new comment to an issue you are following:
``
+1 to jberkus' proposal.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
jberkus added a new comment to an issue you are following:
``
@jlebon that was suggested, but @dustymabe really wanted a separate channel,
and nobody argued against it.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
roshi added a new comment to an issue you are following:
``
+1 to the @jberkus proposal
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
maxamillion added a new comment to an issue you are following:
``
+1 to jberkus' proposal. :thumbsup:
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/295
___
cloud mailing list --
dustymabe added a new comment to an issue you are following:
``
> Sorry if I'm missing context from the IRC #fedora-cloud convo, but isn't the
> proper place for those discussions in #fedora-releng? Is it worth having a
> separate channel just for FAH releng? If that's really the case, then
sinnykumari added a new comment to an issue you are following:
``
>
> we need to experiment with reqpart and see if it does the right thing for
> atomic - are you able to run imagefactory locally and experiment?
>
> Haven't checked how reqpart works, will look into it.
Yes, we can use reqpart
On Wed, Jul 19, 2017 at 4:28 AM, Dusty Mabe wrote:
> Bug is already filed against the correct component. This is just an FYI.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1472573
You've got the wrong end of the stick, nothing provides
libxenctrl.so.4.8 because xen was
strigazi added a new comment to an issue you are following:
``
> @jchaloup is a hero indeed!
> @strigazi, is the proposal here to eventually get kube 1.7.x into fedora 26?
If FA26 continues to ship kubernetes in it I think it should contain 1.7.x. In
70 days 1.8.x will be out and fedora 26
On 07/19/2017 04:12 AM, Peter Robinson wrote:
> On Wed, Jul 19, 2017 at 4:28 AM, Dusty Mabe wrote:
>> Bug is already filed against the correct component. This is just an FYI.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1472573
>
> You've got the wrong end of the
On 07/18/2017 11:28 PM, Dusty Mabe wrote:
> Bug is already filed against the correct component. This is just an FYI.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1472573
>
This is resolved with last nights ostree compose:
https://koji.fedoraproject.org/koji/taskinfo?taskID=20609382
On 07/19/2017 07:55 AM, Peter Robinson wrote:
>
> You worded it differently to that, it was a known problem, they were
> having issues rebuilding due to the breakage in s390x, so it was
> already in progress.
Can you help explain to me what I did wrong?
AFAIK I found a problem and opened a
They will no longer be sent to the cloud list. Please subscribe to the
atomic list if you wish to receive them:
https://lists.fedoraproject.org/admin/lists/atomic.lists.fedoraproject.org/
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
>> You worded it differently to that, it was a known problem, they were
>> having issues rebuilding due to the breakage in s390x, so it was
>> already in progress.
>
> Can you help explain to me what I did wrong?
>
> AFAIK I found a problem and opened a bug against the correct component.
> I had
On Wed, Jul 19, 2017 at 2:02 PM, Dusty Mabe wrote:
>
>
> On 07/19/2017 08:49 AM, Peter Robinson wrote:
You worded it differently to that, it was a known problem, they were
having issues rebuilding due to the breakage in s390x, so it was
already in progress.
>>>
On 07/19/2017 08:49 AM, Peter Robinson wrote:
>>> You worded it differently to that, it was a known problem, they were
>>> having issues rebuilding due to the breakage in s390x, so it was
>>> already in progress.
>>
>> Can you help explain to me what I did wrong?
>>
>> AFAIK I found a problem
TL;DR There is a new fedora atomic mailing list [1] and IRC channel [2], but
the mailing list
should only be used for automated messages and the IRC channel should be
used only
when something extremely Fedora specific (like releng bits) is being
discussed. Otherwise
please
jasonbrooks added a new comment to an issue you are following:
``
The kubernetes project maintains two releases at a time -- one way we might
approach this is to keep the newer release in rawhide and the N-1 release in
Fedora stable, and swap when a new upstream releases goes GA. As long as we
strigazi added a new comment to an issue you are following:
``
> The kubernetes project maintains two releases at a time -- one way we might
> approach this is to keep the newer release in rawhide and the N-1 release in
> Fedora stable, and swap when a new upstream releases goes GA. As long as
jasonbrooks added a new comment to an issue you are following:
``
Or, we could track the latest in Fedora stable and the alpha releases in
rawhide -- that seems a bit more true to rawhide, and still worthwhile, but I
can imagine people wanting to run the N-1 version, and we don't have a way of
On 07/19/2017 09:10 AM, Peter Robinson wrote:
> On Wed, Jul 19, 2017 at 2:02 PM, Dusty Mabe wrote:
>>
>> I agree maybe I could have done more, but I maintain that I didn't do
>> anything
>> incorrect. It would be great if we actually notified when there are issues
>>
25 matches
Mail list logo