Good morning,
21/1/19 16:52(e)an, Peter Robinson igorleak idatzi zuen:
On Tue, Jan 19, 2021 at 3:50 PM Matthew Miller wrote:
A large computer vendor with whom we have a friendly relationship would like
to update the image they're shipping on their systems so that 1) new users
don't have quite
The RFE commit have been merged on master:
https://pagure.io/pagure/c/31280551ec2fdf282152abae2ff9d44f20faaf92?branch=master
I'll notify here once we release 5.9 and upgrade pagure.io with it.
19/12/5 10:06(e)an, Kamil Paral igorleak idatzi zuen:
On Thu, Dec 5, 2019 at 9:33 AM Julen
+1 on my side
20/1/9 10:19(e)an, Kamil Paral igorleak idatzi zuen:
On Thu, Jan 9, 2020 at 1:28 AM Adam Williamson
mailto:adamw...@fedoraproject.org>> wrote:
Hi folks! As discussed at the meeting this week, we're sort of missing
a process for people to become QA group sponsors, and an S
seems like a lot of moving parts to
> keep synchronized.
pagure supports third-party themes|plugins , src.fp.o uses both for
custom features (anitya integration for example), we could do something
similar on pagure.io, where we are already using a downstream theme but
not plu
Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
--
Julen Landa Alustiza
___
eing
>kparal's suggestions
>* **UNASSIGNED**
> * (none)
>
>
>
>
>People Present (lines said)
>---
>* adamw (110)
>* cmurf (37)
>* kparal (27)
>* lruzicka (23)
>* tablepc (17)
>* zodbot (15)
>* frantisekz (15)
>* co
>reported, and I've also filed on on our bugzilla for completeness now:
>
>https://bugzilla.redhat.com/show_bug.cgi?id=1753558
>https://gitlab.gnome.org/GNOME/gnome-calendar/issues/455
Julen Landa Alustiza
___
test mailing list --
o deliver a good experience
>to our users if we're trying to trim half a gig from an image before
>Beta than if we're doing it on the Monday before Go/No-Go.
Julen Landa Alustiza
___
test mailing list -- test@lists.fedoraproject.org
To
fit onto a DVD disc. But for
>Beta we
>> can always test it just fine, regardless the size (and no images are
>> release blocking for optical media for Beta).
>
>> Thoughts?
>
>We could consider still enforcing sizes which clearly relate to optica
lated
term "target size" to "maximum size".
+1. I see no downsides to this.
Also +1, dunno why someone picked 'target' in the first place.
--
Julen Landa Alustiza
___
test mailing list -- test@lists.fedoraproject.org
To u
it's needed for Toolbox, which is a vital feature for Silverblue
>but
>also one we want to encourage on general Workstation as well.
>
>Pretty sure it's also required for IoT.
Julen Landa Alustiza
___
test mailing list -- test
e-x86_64-31-20190826.n.0.iso
>
>so i don't know what FINISHED_INCOMPLETE means in the context of what
>appears to be a perfectly complete and working ISO.
>
>rday
Julen Landa Alustiza
___
test mailing list -- test@lists.fedoraproject.o
nd up spending half of of the go/no-go
>meeting trying to reproduce the bug report.
>
>> I dunno, it's hard to be sure what number is right exactly.
>
>Only because there's no right answer. :-) I'm fine with choosing 7
>days a
https://fedoraproject.org/wiki/Releases/30/ReleaseBlocking
Julen Landa Alustiza
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
send an email to test-le...@lists.fedoraproject.org
>Fedora Code of Conduct:
>https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>List Archives:
>https://lists.fedoraproject.org/archives/list/test@lists
>From the live user's perspective I don't see the point on adding it, I
agree with kamil. The unique use case that cames to my mind for fmw on a
livecd session is burning an arm sd, but that does not make too much sense
neither, you can burn a fc31 arm sd from fc29 or whatever without problems,
so
Lukas Ruzicka igorleak hau idatzi zuen (2019 mai. 14,
ar. 14:12):
>
> I am talking about the quorum, if there is a late discovered bug, that
> would normally be considered a blocker, but because
>
> a) it could not be fixed on time, and
> b) it is not as serious as it would prevent people from us
Lukas Ruzicka igorleak hau idatzi zuen (2019 mai. 14,
ar. 12:55):
> Yeah, you can be right, Julen, however the process, as we are having now,
> would allow discarding Blocker Bugs possibly anytime, even if 3 or 4 people
> would be present on a meeting. And I don't think it is correct to let 4
> p
Lukas Ruzicka igorleak hau idatzi zuen (2019 mai. 14,
ar. 10:39):
> I have suggested the quorum, but we can still discuss the exact numbers
> (mine were just examples). Besides, the votes do not have to come from
> people present in one particular IRC meeting, but
>
>- votes could be recorded
On both fc29 and fc30 cycles, nor the later blocker review meetings nor the
go/no-go ones did not have 10 participants, so needing a 80% agremeent with
a minimum of 10 votes would directly block on last minute bugs on those
scenarios.
I don't have a clear opinion on this, but for now I would prefe
> > 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/Ma
Due to the context and actual bugs, and what we see during the argues, the
main idea about "work correctly" is that you should be able to launch a
working desktop where typical use of some tools and specialy the installer
process can be launched and executed with success.
Yeah, with caveats, a sub
Sounds more than reasonable.
Adam Jackson igorleak hau idatzi zuen (2019 mar. 12, ar.
19:11):
> On Wed, 2019-03-06 at 12:46 -0800, Adam Williamson wrote:
> > Hi folks!
> >
> > So there's a current Beta blocker bug:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1683197
> >
> > it is current
The biggest problem would be the machine that can't boot the live iso on
normal mode and hangs on basic video mode too.
How frequent is this? My test boxes can install on normal mode, I did not
found a box that hangs on both modes.
Chris Murphy igorleak hau idatzi zuen (2019 mar.
8, or. 21:38):
t; in F30. My intent was to test modularity as it is available now, in
> upcoming F30. I think that nobody would test for old releases, but I might
> be wrong.
>
> On Fri, Mar 8, 2019 at 7:04 PM Julen Landa Alustiza
> wrote:
>
>> My concern is around the minimum version co
My concern is around the minimum version constraints. >= 29 or clean >= 30,
while we support and block from 28 till 29 and we're testing 30 and an
upgraded box should work like a clean one for blocking purposes. What
happens with the versions that are supported but out of scope of these
testcases?
Will we have a working branched f30 compose with gnome 3.32 for then? :D
Sumantro Mukherjee igorleak hau idatzi zuen (2019
ots. 22, or. 15:18):
> Hola!
>
> Monday, 2019-02-25 will be Fedora 30 Gnome 3.32 Test Day!
>
> As part of this planned Change for Fedora 30, So this is an important Test
> D
Lukas' question made me another one... Server spin has a couple of blockers
on software (freeipa and posgresql at least). Are we going to take them out
from the installer?
Matthew Miller igorleak hau idatzi zuen (2019
ots. 18, al. 17:00):
> On Mon, Feb 18, 2019 at 11:43:46AM +0100, Lukas Ruzicka
+1 here. totally agree with
Stephen Gallagher igorleak hau idatzi zuen (2019 ots.
15, or. 16:49):
> For a long time, the Fedora Server Edition has provided a fairly
> lightweight default installation, but a fairly heavyweight DVD. This
> is because we opted to include a lot of infrastructure-rel
The meeting had been cancelled (subscribe to qa-announce so you don't miss
the meeting cancelling mail next time) and it uses to be on
#fedora-meeting-1
pmkel...@frontier.com I tried to attend the Monday QA meeting, but when ever I typed something
> to the chat screen I got an error something lik
i'm glad to see this revived.
As I mentioned before, my vote goes to B + updates-testing checkbox for
prereleases.
That way we can:
- test the compose as is, even installing from lives
- bypass broken u-t packages
But also:
- install directly with u-t in case that compose is installing but broke
https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-09-24/f29-blocker-review.2018-09-24-16.05.txt
--
Julen Landa Alustiza
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fe
Discussing about Lukas's propossal without you has no sense, we could delat
that point to next meeting
Have a nice team dinner ;)
El lun., 12 nov. 2018 10:17, Kamil Paral escribió:
> On Sun, Nov 11, 2018 at 6:13 PM Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
>> # Fedora Quality Ass
Related to this and server, and remembering that we had a non working cron
issue proposed as blocker but we didn't have a clear criteria that was
violated to accept the blocker bug, but the majority of the meeting
attendees was in favour of blocking because cron was not working on server
edition an
Hi, I'm suffering a very strange behaviour on my wks and I would like to
know if it's a general issue or just my setup before going further.
I upgraded an fc28 wks to fc29 yesterday. fc28 was almost a default wks +
nvidia drivers, I don't have more extra repos nor too much extra packages.
It had u
that will allow us to install a working enviroment if there is something
broken on u-t or if there is something broken on the compose and fixed on
u-t since we will be able to add the repo during install process.
Would be great to have a disabled by default checkbox on additional repos
windows so
I'm agree with stephen & kparal too.
For anaconda, I would prefer always disabled or respect fedora-release
El mié., 31 oct. 2018 15:01, Kamil Paral escribió:
> On Wed, Oct 31, 2018 at 2:48 PM Lukas Ruzicka wrote:
>
>> Hello,
>> I have been assigned to organize a discussion about this issue
>>
ct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
--
Julen Landa Alustiza
gnome-maps --version
(org.gnome.Maps:4284): Gjs-WARNING **: 19:26:11.529: Some
I've been reading all the release criterias after founding the bug and I
don't see any violated criteria.
My concern more than being blocker or not is about being a major version
upgrade during freezing that creates at least one new regression because
it's a version that changes much more than jus
ed in this case. Should I write a comment on fesco issue?
Should we discuss this during today meeting?
Dunno how to proceed :D
Regards,
[1]: https://pagure.io/fesco/issue/2001
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1640235
--
Julen Landa Alustiza
__
I'll try asap.
El mié., 17 oct. 2018 17:37, Geoffrey Marr escribió:
> Julen,
>
> Thanks for testing. If possible, can you try testing on a bare-metal
> install and see if you have the glitch?
>
> Geoff Marr
> IRC: coremodule
>
>
> On Wed, Oct 17, 2018 at 9:
Just tried on a vm with libvirt, I have the glitch
El mié., 17 oct. 2018 4:04, Geoffrey Marr escribió:
> Testers,
>
> One of the current blockers for F29 Final is this bug regarding
> gnome-maps: [0]
>
> Based off the comments in-bug it seems that there is conflicting data
> regarding whether or
I keep an optical driver in a box under the desk, it might be useful
someday.
I haven't used it for years. So yeah, it's time to clean the box
El jue., 20 sept. 2018 20:26, Richard Shaw escribió:
> On Thu, Sep 20, 2018 at 12:49 PM Matthew Miller
> wrote:
>
>> Justification:
>> http://newsthump
Adam said on the last meeting that there was an known issue with
NetworkManager not starting properly somethings.
sudo systemctl start NetworkManager should repair your issue until it's
fixed
El vie., 20 jul. 2018 14:19, Alessio Ciregia escribió:
> Using F29 I've spotted that sometimes (1 time
Some progress updates...
On fc28, after installing libtirpc-devel and applying
https://pagure.io/kernel-tests/pull-request/18 the performance test can
be compiled and it PASS on a fc28 server KVM guest, but committing the
pull-request will break the test suite on fc27 and earlier.
IMHO the
The performance test is not compiling on fc28 due to rpc/rpc.h stuff
El mar., 12 jun. 2018 10:38, Sumantro Mukherjee
escribió:
>
>
> - Original Message -
> > From: pmkel...@frontier.com
> > To: test@lists.fedoraproject.org
> > Sent: Tuesday, June 12, 2018 12:07:29 AM
> > Subject: Re: 201
46 matches
Mail list logo
