On Wed, Dec 11, 2019 at 7:27 PM Chris Murphy
wrote:
> I'd also drop all the preconditions like using defaults. Pretty much
> any possible installer allowed configuration that trips up this test
> case is an eyeball opener and should be tracked down.
>
+1
>
> > >
>
On Wed, Dec 11, 2019 at 5:14 PM Adam Williamson
wrote:
> > What's the point of running the checks from Live image as well? The local
> > filesystems will likely get wiped and re-created anyway. Extra failures
> in
> > the log might just confuse us when reading the bug report.
>
> That was in
On Mon, Dec 9, 2019 at 7:05 PM Adam Williamson
wrote:
> On Sat, 2019-12-07 at 09:45 -0500, pmkel...@frontier.com wrote:
> > I think I have it close to what you want. Please let me know.
> >
> > Here's the link:
> >
> > https://fedoraproject.org/wiki/User:Tablepc/Draft_testcase_reboot
> >
> >
On Sat, Dec 7, 2019 at 2:46 AM Adam Williamson
wrote:
> # Fedora Quality Assurance Meeting
> # Date: 2019-12-09
> # Time: 16:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location: #fedora-meeting on irc.freenode.net
>
> Greetings testers!
>
> We have a couple of active
On Thu, Dec 5, 2019 at 8:07 PM pmkel...@frontier.com
wrote:
>
> On 12/5/19 03:56, Kamil Paral wrote:
>
> >
> > Here's the email I had in mind, containing the important journal
> messages:
> >
> https://lists.fedoraproject.org/archives/list/tes
On Thu, Dec 5, 2019 at 9:33 AM Julen Landa Alustiza <
jla...@fedoraproject.org> wrote:
>
> 19/12/4 15:34(e)an, Kamil Paral igorleak idatzi zuen:
>
> On Tue, Dec 3, 2019 at 10:22 PM Tim Flink wrote:
>
>> Has anyone poked at scoping out the work required for either the
On Tue, Dec 3, 2019 at 3:29 PM pmkel...@frontier.com
wrote:
> On 12/3/19 06:27, Kamil Paral wrote:
> > On Mon, Dec 2, 2019 at 7:43 PM pmkel...@frontier.com <
> pmkel...@frontier.com>
> > wrote:
> >
> >> I have the update ready. I think I interpolated the
On Wed, Dec 4, 2019 at 6:23 PM Ben Cotton wrote:
> Hi team,
>
> If you have some spare time and a ThinkPad (particularly the T490),
> can you please see if you can replicate the behavior reported in:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1773879
>
> In today's Prioritized Bugs meeting,
On Tue, Dec 3, 2019 at 5:15 PM Geoffrey Marr wrote:
> Kamil,
>
> I wasn't intending the time we would get together each week for voting,
> instead for time spent discussing and clarifying any discrepancies we may
> have with the bugs. By the time we would have this 30 or so minute
>
On Tue, Dec 3, 2019 at 10:22 PM Tim Flink wrote:
> Has anyone poked at scoping out the work required for either the bot or
> the enhancements we would need for pagure?
>
Lukáš Brabec looked into it, and creating a new Pagure ticket is a matter
of a few lines of code (already written). Extending
On Tue, Dec 3, 2019 at 8:29 PM Kevin Fenzi wrote:
> I pretty much agree with all the points you made on the various systems.
> That said, I think this is kinda a bad time to be doing this change.
> There's a lot of... (grumblings? rumors? idle converstations?) about the
> various
On Tue, Dec 3, 2019 at 1:18 PM Lukas Ruzicka wrote:
>
> Abstain is useful if there are conflicts of interest, or to indicate no
>> preference either way, or as a result of confusion. I chock up more than
>> one abstain vote as an indicator the proposal isn't persuasive enough.
>> Indeed if
On Mon, Dec 2, 2019 at 11:47 PM Geoffrey Marr wrote:
> Kamil,
>
> Thanks for working on this. I am glad we are considering something
> different here, as the current process is not perfect.
>
> Personally, of the suggested options, I think that using Pagure is my
> preferred option. I think of
On Mon, Dec 2, 2019 at 4:19 PM pmkel...@frontier.com
wrote:
>
>
> On 12/2/19 07:03, Kamil Paral wrote:
>
> >
> > I'm not familiar with kanban/taiga. What is the benefit over using
> standard
> > (Pagure) tickets?
> >
> >
>
> The kanban/taiga i
On Mon, Dec 2, 2019 at 4:02 PM Ben Cotton wrote:
> I want to speak up in defense of synchronous meetings. I acknowledge
> that the timing is rather convenient for me personally (it's 12–3pm my
> time), which makes it easier for me to see the upsides.
>
> The big benefit is the high bandwidth
On Mon, Dec 2, 2019 at 7:43 PM pmkel...@frontier.com
wrote:
> I have the update ready. I think I interpolated the discussion
> correctly, but probably leaned toward the "keep it simple for now" case.
> Please let me know if there are further changes needed. Here's the link:
>
>
On Sat, Nov 30, 2019 at 10:40 PM Chris Murphy
wrote:
> On Thu, Nov 28, 2019 at 5:30 AM Kamil Paral wrote:
> >
> > Pagure
> > ***
> >
> > This is very similar to the Bugzilla description. For each proposed
> blocker, we (auto-)create a ticket in a "fe
On Fri, Nov 29, 2019 at 7:30 PM Chris Murphy
wrote:
> On Fri, Nov 29, 2019 at 5:10 AM Kamil Paral wrote:
> >
> > Sounds reasonable to test both LiveOS and the installed system. Does it
> make sense to test both installed system's reboot and poweroff, though? Are
>
On Thu, Nov 28, 2019 at 8:29 PM Chris Murphy
wrote:
> FAT, ext4, and XFS all have a kind of "dirty bit" set upon mount. It's
> removed when cleanly unmounted. Therefore if the file system isn't
> mounted, but the "dirty bit" is set, it can be assumed it was not
> cleanly unmounted. Both kernel
On Fri, Nov 29, 2019 at 9:46 AM Lukas Brabec wrote:
> > 2. Blocker Bugs App (BBA) detects the new blocker and creates a new
> ticket in Pagure in the "fedora-blockers" project, then updates the bug to
> link to this ticket (a new comment, a Links entry). It shows both the bug
> and the
On Thu, Nov 28, 2019 at 11:29 PM Frantisek Zatloukal
wrote:
>
>
> On Thu, Nov 28, 2019 at 1:31 PM Kamil Paral wrote:
>
>>
>> 5. Once some kind of understanding of the issue is formed, a privileged
>> member (e.g. a member of @fedora-qa FAS group) can start the
On Thu, Nov 28, 2019 at 5:59 PM Lukas Ruzicka wrote:
>
> 7. People vote by submitting comments containing VOTE +1/0/-1 on a
>> separate line (and including any justification or feedback they wish in the
>> comment as well; the command has to simply be on its own line so that we
>> can detect it
On Thu, Nov 28, 2019 at 5:14 PM Adam Williamson
wrote:
> So overall I agree with a lot of what you wrote. It does cause me to
> wonder if writing some kind of plugin/extension for Pagure, or just
> writing the functionality into the blockerbugs app, might possibly be
> *less* work than writing
We've talked about replacing blocker bug review meetings with something
else for a long time. The meeting has an upside of a higher communication
bandwidth, but also a downside of requiring participants to be available at
the same time (throughout the world), often being extremely long, and being
On Wed, Nov 27, 2019 at 9:17 PM Chris Murphy
wrote:
> On Wed, Nov 27, 2019 at 10:35 AM pmkel...@frontier.com
> wrote:
>
> > https://fedoraproject.org/wiki/User:Tablepc/Draft_testcase_reboot
>
> Why does it need to happen on baremetal only? Any problem discovered
> by this test case is sure to
On Tue, Nov 26, 2019 at 9:16 PM Adam Williamson
wrote:
> On Tue, 2019-11-26 at 13:59 -0500, pmkel...@frontier.com wrote:
> >
> > I assure you that I wasn't being lazy when I created the web draft test
> > case. It wasn't copied from e'mail, but from my original LibriWriter
> > file where I
On Tue, Nov 26, 2019 at 7:59 PM pmkel...@frontier.com
wrote:
> Kamil,
>
> I have received your input. Thank you; I appreciate your help.
>
> With the holiday this week, I will start on the updates next week and
> send a note when it is done.
>
Sure, no rush. Pat, one more thing, can you please
On Mon, Nov 25, 2019 at 1:39 PM pmkel...@frontier.com
wrote:
> Here is a link to the List discussion on the subject item:
>
>
> https://lists.fedoraproject.org/archives/search?q=drive+dismount+test+case=1=test%40lists.fedoraproject.org=date-asc
>
> I don't have a current example of this
On Mon, Nov 25, 2019 at 10:27 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/DisallowEmptyPasswordsByDefault
>
> == Summary ==
> Remove ''nullok'' parameter from pam_unix module in default PAM
> configuration in order to disallow authentication with empty password.
>
> == Owner ==
On Sun, Nov 3, 2019 at 1:02 AM ToddAndMargo via test <
test@lists.fedoraproject.org> wrote:
> Hi All,
>
> Fedora 30, attempting to upgrade to Fedora 31
>
> # dnf system-upgrade download --refresh --releasever=31 --allowerasing
> --best --skip-broken
>
> Error:
> Problem: cannot install the best
On Mon, Oct 28, 2019 at 4:34 PM Ben Cotton wrote:
> On Wed, Oct 9, 2019 at 7:11 AM Kamil Paral wrote:
>
> > I guess the proposed criterion should get adjusted per our latest
> discussion in blocker review meeting, i.e. this one:
> >
> > 16:28:24 #agreed 1755898 - Ac
On Mon, Oct 7, 2019 at 5:47 PM Adam Williamson
wrote:
> On Mon, 2019-09-30 at 15:19 -0400, Ben Cotton wrote:
> > As we discussed in today's blocker review meeting[1], I am presenting
> > a draft proposal for the toggle keys. I am proposing this as a *final*
> > criterion, but would not object to
On Fri, Oct 4, 2019 at 3:37 PM Pavel Raiskup wrote:
> Hello,
>
> today (on Oct 4, 2019), new Copr release landed production.
>
> This was mostly a bugfix release, with some optimization/reliability
> patches interesting for copr administrators. But there were few exciting
> changes for the
On Fri, Oct 4, 2019 at 3:37 PM Pavel Raiskup wrote:
> Hello,
>
> today (on Oct 4, 2019), new Copr release landed production.
>
> This was mostly a bugfix release, with some optimization/reliability
> patches interesting for copr administrators. But there were few exciting
> changes for the
On Fri, Oct 4, 2019 at 12:50 PM Lukas Ruzicka wrote:
>
>
> Both have been rejected as blockers due to being too "edge case". But
>> pasting into QT applications seems sufficiently broad to be considering as
>> blocking, I think. So if your problems are not related to those two issues
>> (e.g.
On Thu, Oct 3, 2019 at 3:30 PM Ankur Sinha wrote:
> Hello,
>
> I ran into an issues with copy/pasting on F31 with the new Gnome 3.34.
> Are these known, or are they expected and if not where should one file
> bugs please?
>
> gnome-shell-3.34.0-3.fc31.x86_64
>
>
> --- Issue 1
>
> X
On Mon, Sep 30, 2019 at 9:19 PM Ben Cotton wrote:
> As we discussed in today's blocker review meeting[1], I am presenting
> a draft proposal for the toggle keys. I am proposing this as a *final*
> criterion, but would not object to adding it as a beta criterion.
>
> == Keyboard toggle keys ==
>
I'm happy we have some automation in place now, but I feel this whole
discussion went somewhat off-topic from the proposal. It seems I haven't
gained any support for simply moving the criterion to Final, and I don't
really want to make such a trivial check more complex (in terms of release
On Tue, Sep 17, 2019 at 10:35 PM Ben Cotton wrote:
> On Tue, Sep 17, 2019 at 9:55 AM Kamil Paral wrote:
> >
> > Considering this, I believe it makes sense to move the current criterion
> from Beta to Final.
> >
> I'd be okay with letting the responsible team specify
On Tue, Sep 17, 2019 at 8:38 PM Adam Williamson
wrote:
> We could consider still enforcing sizes which clearly relate to optical
> media (so, basically, 700MB and 4.7GB sizes).
>
But we enforce them, for Final. And for Beta, we don't block on optical
media anyway. That was one of my arguments
On Tue, Sep 17, 2019 at 7:34 PM Chris Murphy
wrote:
> On Tue, Sep 17, 2019 at 7:55 AM Kamil Paral wrote:
> >
> > We currently have the following Beta criterion:
> > "The release-blocking images must meet current size requirements." [1]
> >
> > The lat
We currently have the following Beta criterion:
"The release-blocking images must meet current size requirements." [1]
The latest "Workstation image is oversized" bug [2] showed that we don't
consider this requirement to be that critical. People mostly agreed that
having a slightly oversized
On Mon, Sep 16, 2019 at 5:06 PM Adam Williamson
wrote:
> I still consider automatic blockers to be about obviousness (not
> criticality), but I'm open to different resolutions here anyway, if we
> want to come up with something really clear.
>
For the record, we talked about this yesterday in
On Fri, Sep 13, 2019 at 6:44 PM Adam Williamson
wrote:
> On Fri, 2019-09-13 at 13:53 +0200, Kamil Paral wrote:
> > As I feel it (and would like to have it), "automatic blockers" imply they
> > are such core and basic issues that they are non-questionable and
> >
On Fri, Sep 13, 2019 at 5:42 PM Adam Williamson
wrote:
> On Fri, 2019-09-13 at 08:44 -0400, Ben Cotton wrote:
> > On Fri, Sep 13, 2019 at 8:09 AM Kamil Paral wrote:
> > > Related to Workstation image oversize bug [1] and the related
> > > Go/NoGo meeting, I'd like to
Related to Workstation image oversize bug [1] and the related Go/NoGo
meeting, I'd like to propose to rename the image-related term "target size"
to "maximum size". The rename would affect the following pages:
https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking
On Fri, Aug 30, 2019 at 3:11 AM Adam Williamson
wrote:
> On Fri, 2019-08-09 at 19:04 -0700, Adam Williamson wrote:
> > On Fri, 2019-08-09 at 18:26 -0700, Adam Williamson wrote:
> > > On Wed, 2019-07-24 at 10:04 -0400, pmkel...@frontier.com wrote:
> > > > I got feedback from Adam and Ben today;
On Wed, Sep 11, 2019 at 2:46 PM Kamil Paral wrote:
> On Tue, Sep 10, 2019 at 5:59 PM wrote:
>
>> F31 Workstation fully updated.
>> Strange behaviour after I create a user in addition to the one created
>> during initial setup.
>>
>> So, create a new us
On Tue, Sep 10, 2019 at 5:59 PM wrote:
> F31 Workstation fully updated.
> Strange behaviour after I create a user in addition to the one created
> during initial setup.
>
> So, create a new user.
> Lock the current user session.
> Click on "Log in as another user".
> Click on the other user.
On Thu, Sep 5, 2019 at 8:59 PM Adam Williamson
wrote:
> Hey folks! So, it was suggested at the blocker review meeting on Monday
> that violations of the Basic desktop background criterion:
>
> "The default desktop background must be different from that of the last
> two stable releases."
>
>
On Wed, Sep 4, 2019 at 2:29 PM Dominik Turecek wrote:
> Hello.
>
> Today, we have released a new version of Copr.
> Main highlights from the release was the addition
> of discussion panels in Copr projects and speed
> optimization of front page.
>
The discussion page is a neat idea. For some
On Tue, Sep 3, 2019 at 11:52 AM wrote:
> On F31 with latest updates, in GNOME Settings I enabled Sharing then
> Screen Sharing.
> I use Remmina to connect via VNC, and it works.
> But when the system, after the default 5 minutes of inactivity blanks
> the screen and locks the user session, VNC
On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe wrote:
> I don't know the formal process for proposal but here is a shot at a bare
> minimum
> start for trying to add containers to the existing release criteria. This
> is a suggestion
> after we found podman can't pull containers from a registry in
On Wed, Aug 28, 2019 at 1:24 PM Pierre-Yves Chibon
wrote:
> Is the issue about updates lingering in -testing?
>
I imagine this could cause some issues for e.g. generic tests that test
everything in -testing in one go, instead of just one particular NVR, for
performance reasons (like
On Mon, Aug 26, 2019 at 2:42 PM Justin Forbes wrote:
> From my standpoint, ext4 and xfs are the primary supported root
> filesystems. I don't think that anything else should be release
> blocking.
If this is the case, we can explicitly list the supported file systems in
criteria. The list
On Mon, Aug 26, 2019 at 2:42 PM Justin Forbes wrote:
> From my standpoint, ext4 and xfs are the primary supported root
> filesystems. I don't think that anything else should be release
> blocking.
If this is the case, we can explicitly list the supported file systems in
criteria. The list
On Fri, Aug 23, 2019 at 10:39 AM Vít Ondruch wrote:
>
> Dne 22. 08. 19 v 18:57 Kevin Fenzi napsal(a):
>
> On 8/21/19 3:24 AM, Vít Ondruch wrote:
>
>
> That is not completely true. The only possible way is to update the
> `fedora-gpg-keys` first without anything else and that was the reason
> for
On Mon, Aug 12, 2019 at 11:40 PM Adam Williamson
wrote:
> On Mon, 2019-08-12 at 22:39 +0200, Kamil Paral wrote:
> > On Sat, Aug 10, 2019 at 4:04 AM Adam Williamson <
> adamw...@fedoraproject.org>
> > wrote:
> >
> > >
> > > +++ DRAFT STA
On Fri, Aug 9, 2019 at 5:16 PM Adam Williamson
wrote:
> In case folks didn't see it on devel@, I wanted to flag this up here.
> Infra is talking about no longer maintaining fedocal. We do use it for
> some purposes, the most notable I can think of is the Test Day calendar
> - we used to keep the
On Sat, Aug 10, 2019 at 4:04 AM Adam Williamson
wrote:
>
>
> +++ DRAFT START +++
>
> === Exceptional cases ===
>
> Generally speaking, any bug that is agreed to be a violation of the
> [[Fedora Release Criteria|release criteria]] should be accepted as a
> blocker bug for the next
On Tue, Jul 30, 2019 at 10:41 AM Pierre-Yves Chibon
wrote:
> On Tue, Jul 30, 2019 at 10:11:07AM +0200, Fabio Valentini wrote:
> > On Thu, Jul 25, 2019 at 5:25 PM Pierre-Yves Chibon
> wrote:
> > >
> > > Good Morning Everyone,
> > >
> > > I just wanted to let everyone know that this is now live.
On Wed, Jul 24, 2019 at 2:33 PM Josh Boyer
wrote:
> On Wed, Jul 24, 2019 at 8:02 AM Miro Hrončok wrote:
> >
> > On 24. 07. 19 10:24, Tom Hughes wrote:
> > > That said, having to go round adding a mega ugly config file
> > > to every package that looks an awful lot like an internal braindump
> >
On Tue, Jul 23, 2019 at 7:44 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Anaconda_Reclaim_Disk_Space
>
> The Manual Partitioning screen supports all actions of the Resize Disk
> Space dialog, so it doesn't make sense to have two user interfaces
> with the same functionality.
>
On Mon, Jul 22, 2019 at 8:52 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/x86-64_micro-architecture_update
>
> = Detailed Description ==
>
> After preliminary discussions with CPU vendors, we propose AVX2 as the
> new baseline. AVX2 support was introduced into CPUs from 2013 to
On Mon, Jul 8, 2019 at 6:12 PM Adam Williamson
wrote:
> On Tue, 2019-05-21 at 11:14 -0700, Adam Williamson wrote:
> > > > > > "The release must boot successfully as Xen DomU with releases
> providing
> > > > > > a functional, supported Xen Dom0 and widely used cloud providers
> > > > > >
On Mon, Jul 8, 2019 at 6:12 PM Adam Williamson
wrote:
> On Tue, 2019-05-21 at 11:14 -0700, Adam Williamson wrote:
> > > > > > "The release must boot successfully as Xen DomU with releases
> providing
> > > > > > a functional, supported Xen Dom0 and widely used cloud providers
> > > > > >
Hello,
anyone using fedora-easy-karma to submit feedback to proposed Bodhi updates
might be interested to know that we've fixed some issues that appeared
recently after Bodhi updated to version 4. F-e-k no longer crashes and can
list all your karma-able updates. However, due to a bodhi bug [1] it
On Fri, Jun 28, 2019 at 11:12 AM Miroslav Suchý wrote:
> Dne 27. 06. 19 v 23:56 Zbigniew Jędrzejewski-Szmek napsal(a):
> > (try to add '--allowerasing' to command line to replace conflicting
> packages or '--skip-broken' to skip uninstallable packages)
>
> This is message for people who are
On Tue, Jun 4, 2019 at 3:29 PM Jan Pazdziora wrote:
>
> Hello,
>
> I have run fedora-rawhide-build-pipeline
>
>
> https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-build-pipeline/detail/fedora-rawhide-build-pipeline/4426/pipeline/
>
> that failed in
On Wed, May 29, 2019 at 10:20 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Switch_RPMs_to_zstd_compression
>
> = Switch RPMs to zstd compression =
>
> == Summary ==
> Binary RPMs are currently compressed with xz level 2.
> Switching to zstd would increase decompression speed
On Mon, May 20, 2019 at 7:45 PM Lars Kurth wrote:
> @Adam and Fedora Testing & QA:
> any views on my proposal?
> Regards
> Lars
>
Hi Lars,
thanks for your reply. Adam was on a long vacation and he's probably the
most qualified person to reply to you, sorry for not telling you sooner.
Adam is
On Mon, May 20, 2019 at 7:45 PM Lars Kurth wrote:
> @Adam and Fedora Testing & QA:
> any views on my proposal?
> Regards
> Lars
>
Hi Lars,
thanks for your reply. Adam was on a long vacation and he's probably the
most qualified person to reply to you, sorry for not telling you sooner.
Adam is
On Tue, May 14, 2019 at 12:56 PM pmkel...@frontier.com <
pmkel...@frontier.com> wrote:
> Lukas,
>
> When a system is installed to hard disk from Workstation Live, Media
> Writer is not part of that install. The thinking is that people use
> Media Writer as the main way they create install media;
On Thu, May 2, 2019 at 6:19 PM Adam Jackson wrote:
> On Thu, 2019-05-02 at 17:05 +0200, Kamil Paral wrote:
> > Hello,
> >
> > I wonder whether it's expected that vsync doesn't work in VMs. I've
> > tested Fedora 28/29/30 Workstation and Fedora 30 KDE guests on Fedora
&
Hello,
I wonder whether it's expected that vsync doesn't work in VMs. I've tested
Fedora 28/29/30 Workstation and Fedora 30 KDE guests on Fedora 30 host,
with virtio GPU (3D acceleration on and off) or QXL GPU, and in all cases,
I'm seeing hundreds or thousands of FPS in glxgears, implying that
On Wed, Apr 24, 2019 at 9:20 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
>
> Last time I used tracer, it had several issues. It was breaking
> dist-upgrades and hogged the CPU for tens of seconds after the dnf
> transaction was done. needs-restarting can be run after
On Tue, Apr 16, 2019 at 4:56 PM Bojan Smojver wrote:
> I'm guessing most of you here probably observed this behaviour with dnf
> when FF is upgraded. Even after FF restarted, dnf needs-restarting reports
> that it needs restarting. Does that sound like a bug or is this somehow
> intentional?
>
>
On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral wrote:
> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
> because CSM off or even SecureBoot on make the image unbootable (I'll
> report a separate bug about that).
>
https://bugzilla.redhat.com/show_bug.cg
On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral wrote:
> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
> because CSM off or even SecureBoot on make the image unbootable (I'll
> report a separate bug about that).
>
https://bugzilla.redhat.com/show_bug.cg
On Tue, Apr 9, 2019 at 3:03 AM Adam Williamson
wrote:
> Hi folks!
>
> A few weeks back we asked for testing of 'basic graphics mode' /
> nomodeset booting - the feedback from that was very helpful in
> establishing that we had a generic issue which dated back to Fedora 29,
> thanks a lot. We
On Tue, Apr 9, 2019 at 3:03 AM Adam Williamson
wrote:
> Hi folks!
>
> A few weeks back we asked for testing of 'basic graphics mode' /
> nomodeset booting - the feedback from that was very helpful in
> establishing that we had a generic issue which dated back to Fedora 29,
> thanks a lot. We
On Mon, Apr 8, 2019 at 7:34 PM Karsten Andreas Artz
wrote:
> Hi guys,
>
> my name is Andi, 29 and I'm from Germany. I'm using Fedora almost 2 years
> (Fedora 26). My programming skills are on Python, Java/Java Script, and
> C/C++. But acutally I prefer mostly Python hacking. I studied B.A. of
On Tue, Apr 9, 2019 at 8:21 PM Lennart Poettering
wrote:
> Hmm, but the installed OS is not 100% the same as the livesys, or is
> it? If not, it should be possible to add a "systemctl disable
> dmraid.service --root=/path/to/os" somewhere, no?
>
AFAIK, they are 100% same. There's a hack, check
On Wed, Apr 10, 2019 at 2:35 AM Chris Murphy
wrote:
> > 1. multipathd.
>
> I'm pretty sure it gets dragged in by the installer
Nope, multipath seems to be present because libblockdev and udisks (and
perhaps some more), which is in turn required by GNOME:
$ rpm -q --whatrequires
On Mon, Apr 1, 2019 at 9:04 PM Adam Williamson
wrote:
> "The boot menu for all release-blocking installer and live images
> should include an entry which causes both installation and the
> installed system to use a generic, highly compatible video driver (such
> as 'vesa')."
>
Maybe change
On Mon, Apr 1, 2019 at 9:04 PM Adam Williamson
wrote:
> "The boot menu for all release-blocking installer and live images
> should include an entry which causes both installation and the
> installed system to use a generic, highly compatible video driver (such
> as 'vesa')."
>
Maybe change
Workstation netinst and package tree will be removed from F31 onward:
https://pagure.io/fedora-workstation/issue/45
https://pagure.io/releng/issue/7403
It seems regular netinst will be used to install Workstation over the
network.
We'll need to adjust our test matrices/test cases and automated
On Tue, Mar 26, 2019 at 9:31 PM Chris Murphy
wrote:
> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell,
On Tue, Mar 26, 2019 at 9:31 PM Chris Murphy
wrote:
> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell,
On Fri, Mar 8, 2019 at 8:46 PM Chris Murphy wrote:
> There's a new feature in Fedora 29, hide the grub menu, that can make
> it difficult to troubleshoot system upgrades if you run into a
> problem. Here's what you can do to get more information for a one time
> boot without obliterating the
On Fri, Mar 8, 2019 at 3:21 PM Lukas Ruzicka wrote:
> Hello,
>
> I have updated the modularity test cases according to what we discussed in
> a meeting with @Stephen Gallagher , @Petr Sabata
> , @Adam Samalik , @Mohan Boddu
> . Currently, we have the following test cases defined
> to cover
On Mon, Feb 18, 2019 at 7:34 PM Matthew Miller
wrote:
> On Mon, Feb 18, 2019 at 05:48:15PM +0100, Lukas Ruzicka wrote:
> > > servers also need security and bug fixes.
> > If so and local repository is always needed ... why keep a server spin
> > then? Why not install from Everything netinst?
>
>
On Fri, Feb 15, 2019 at 4:50 PM Stephen Gallagher
wrote:
> 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-related content
> on the disk, such as BIND,
On Wed, Jan 9, 2019 at 7:01 PM Randy Barlow
wrote:
> Greetings again!
>
> In my quest to kill Bodhi features so I can have a smaller codebase to
> maintain, I am considering getting rid of the fedmsg integration in the
> web interface:
>
> https://github.com/fedora-infra/bodhi/issues/2913
>
> I
On Tue, Nov 27, 2018 at 4:39 PM Owen Taylor wrote:
> And if we did do updates like that, would we consider respinning media
> and making a "F30.1"?
>
What's the difference between re-spinning install media and doing a proper
F31 release? At least from QA point of view, I see very little
On Tue, Nov 27, 2018 at 5:12 PM Adam Williamson
wrote:
> On Tue, 2018-11-27 at 12:48 +0100, Kamil Paral wrote:
> > Hi Adam,
> >
> > I and Lukas are in the process of drafting an email to Desktop SIGs
> > regarding basic functionality criteria for all apps availab
Hi Adam,
I and Lukas are in the process of drafting an email to Desktop SIGs
regarding basic functionality criteria for all apps available on blocking
desktops (as discussed recently in the QA meeting), and I need to clarify
the purpose of the "workstation core applications" testcase [1]. You
On Mon, Nov 26, 2018 at 6:20 PM Adam Williamson
wrote:
> On Mon, 2018-11-26 at 15:41 +0100, Kamil Paral wrote:
> >
> > > > * Into Additional Repositories section, add updates-testing repo
> item,
> > > > disabled by default, and only visible in pre-re
On Fri, Nov 23, 2018 at 5:47 PM Adam Williamson
wrote:
> On Fri, 2018-11-23 at 10:02 +0100, Kamil Paral wrote:
> > On Thu, Nov 22, 2018 at 6:22 PM Adam Williamson <
> adamw...@fedoraproject.org>
> > wrote:
> >
> > > Here's a bit of background:
> > >
On Thu, Nov 22, 2018 at 6:22 PM Adam Williamson
wrote:
> Here's a bit of background:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=962522
>
> The key point there is that if we implement your b), the checkbox would
> effectively do nothing in the pre-release phase at all, because there
> are no
501 - 600 of 2019 matches
Mail list logo
