Hi, folks! I thought this might be about the appropriate time to throw
this out there.
There hasn't been a big news press on this, but some of you may know
that releng is fairly close to switching over to Pungi 4 for composes.
For those of you who don't know:
releng is fairly close to switching o
> https://fedoraproject.org/wiki/Template:Installation_test_matrix
>
> quite a lot of the tables have 'i386' and 'x86_64' as environments.
> Especially with the Milestone column, listing i386 alongside x86_64 is
> a bit misleading if i386 is no longer blocking. I can see a few
> options:
>
> 1) j
> Since people seemed to be on board with this approach, I've done the
> drafts. Here they are:
>
> https://fedoraproject.org/wiki/User:Adamwill/Draft_Alpha_Criteria_Postinstall
> https://fedoraproject.org/wiki/User:Adamwill/Draft_Beta_Criteria_Postinstall
> https://fedoraproject.org/wiki/User:Ada
> I have tweaked the release criteria 'preamble' text slightly to mention
> this explicitly, and also to link to the canonical list of release-
> blocking images that the program manager is maintaining now (the F24
> list is
> https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking
> If we have automated, more-than-nightly composes that look much like a
> regular release compose would, there's no clear case for having TCs at
> all. We could simply stop building them and extend the "nightly"
> validation process. I think the way to do that would be to keep
> 'nominating' night
On Friday, January 29, 2016 02:25:49 PM Richard W.M. Jones wrote:
> On Fri, Jan 29, 2016 at 03:03:33PM +0100, Stanislav Ochotnicky wrote:
> > On Fri 29 Jan 2016 02:51:31 PM CET Richard W.M. Jones wrote:
> > > On Fri, Jan 29, 2016 at 04:33:19AM -0800, Adam Williamson wrote:
> > >> Hi, folks! I thoug
Missing expected images:
Kde disk raw armhfp
Cloud_atomic disk raw x86_64
Images in this compose but not Rawhide 20160128:
Cloud disk raw i386
Games live x86_64
Design_suite live x86_64
Generic boot x86_64
Cloud disk qcow x86_64
Soas live x86_64
Xfce live x86_64
Cloud vagrant libvirt x86_64
Clou
On Fri, 2016-01-29 at 09:26 -0500, Kamil Paral wrote:
> Here's a question. Are we going to "nominate" only those composes in
> which a substantial component changed (i.e. anaconda or systemd),
> similarly to what we do now in rawhide, or are we going to nominate
> each new compose (i.e. one or mor
On Fri, 2016-01-29 at 08:09 -0500, Kamil Paral wrote:
> But if we want to still test i686 in OpenQA (at least on a best-
> effort basis), we somewhat rely on the wiki pages for reporting. (Or
> do you think that having it in OpenQA frontend is good enough?).
Well, there's one other venue where we
On Fri, 2016-01-29 at 08:46 -0500, Kamil Paral wrote:
> > Since people seemed to be on board with this approach, I've done the
> > drafts. Here they are:
> >
> > https://fedoraproject.org/wiki/User:Adamwill/Draft_Alpha_Criteria_Postinstall
> > https://fedoraproject.org/wiki/User:Adamwill/Draft_Bet
On Fri, 2016-01-29 at 08:55 -0500, Kamil Paral wrote:
> > I have tweaked the release criteria 'preamble' text slightly to mention
> > this explicitly, and also to link to the canonical list of release-
> > blocking images that the program manager is maintaining now (the F24
> > list is
> > https://
On Fri, Jan 29, 2016 at 10:07:14AM -0600, Dennis Gilmore wrote:
> > > > https://fedorahosted.org/rel-eng/ticket/5805
[...]
> We have none of that info and its not yet on our radar.
> https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline is
> the list of things we have coming up. I th
On Fri, 29 Jan 2016 10:49:06 -0800
Adam Williamson wrote:
> i.e. they're actually marked 'i386' and are in a directory called
> 'i386'.
>
> CCing Jan and nirik (who's shown as creating the page in the edit
> log).
Yeah, just missed/typo/mistake.
I have changed them to the i386 path and marked
Hi,
I posted a variation of this question on users@ and it looks like no
one there has hit this. Basically I can ssh, and reach Cockpit, via
IPv6. But I can't reach Anaconda over VNC via IPv6.
This says it ought to work.
https://fedoraproject.org/wiki/Anaconda/Features/Ipv6OnlyInstallation
The p
On 01/29/2016 03:42 PM, Chris Murphy wrote:
The problem I'm running into next is that non-lives don't have either
netstat or ss, so I can see if xvnc is actually listening on an ipv6
port or not.
Can you install using some other method?
If so ... do the installation, boot the installation medi
On Fri, Jan 29, 2016 at 3:39 PM, Ian Pilcher wrote:
> On 01/29/2016 03:42 PM, Chris Murphy wrote:
>>
>> The problem I'm running into next is that non-lives don't have either
>> netstat or ss, so I can see if xvnc is actually listening on an ipv6
>> port or not.
>
>
> Can you install using some oth
On Fri, Jan 29, 2016 at 3:39 PM, Ian Pilcher wrote:
> On 01/29/2016 03:42 PM, Chris Murphy wrote:
>>
>> The problem I'm running into next is that non-lives don't have either
>> netstat or ss, so I can see if xvnc is actually listening on an ipv6
>> port or not.
>
>
> Can you install using some oth
Firefox, to find Cockpit running on Fedora server wants the IPv6
address in the form:
http://[2601:282:702:b65c:a871:6172:b20f:3a0b]:9090
And then ssh wants it in the form
ssh chris@2601:282:702:b65c:a871:6172:b20f:3a0b
But I don't actually know what form TigerVNC wants it in.
I just tried nma
2016-01-29 20:44 GMT+02:00 Adam Williamson :
> On Fri, 2016-01-29 at 08:46 -0500, Kamil Paral wrote:
>
> > I'm not completely happy about the wording of:
> > " This criterion does apply to live environments. However, a stricter
> > standard of judgement may be applied to conditional violations in
19 matches
Mail list logo
