Re: [Proposal] Remove the QA:Testcase_desktop_app_basic - archive manager from matrix

2021-09-21 Thread Kamil Paral
On Tue, Sep 21, 2021 at 1:10 AM Adam Williamson wrote: > Could we perhaps keep the > line and add a footnote that specifies the "archive manager" role on > Workstation is fulfilled by Nautilus/"Files"? > That sounds like a reasonable solution to me.

Re: Changes to Bugzilla query limits

2021-09-17 Thread Kamil Paral
On Fri, Sep 17, 2021 at 2:09 PM Ben Cotton wrote: > I'm passing along a lightly-edited announcement from the Red Hat > Bugzilla admins. You may have noticed this change already. The short > version is that the search API now defaults to returning 20 bugs, but > authenticated calls can request up

Re: Basic criterion proposal: g-i-s shouldn't take 2 minutes to launch

2021-09-17 Thread Kamil Paral
On Thu, Sep 16, 2021 at 7:17 PM Adam Williamson wrote: > On Wed, 2021-08-25 at 11:33 -0400, Ben Cotton wrote: > > On Wed, Aug 25, 2021 at 11:03 AM Kamil Paral wrote: > > > Or if we want to have some exact numbers, what about "it must not add > more than 10 seconds to a

Re: F36 Change: Enable exclude_from_weak_autodetect by default in LIBDNF (System-Wide Change proposal)

2021-09-17 Thread Kamil Paral
On Thu, Sep 16, 2021 at 9:18 PM Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/ExcludeFromWeakAutodetect > > > == Summary == > exclude_from_weak_autodetect enables autodetection of unmet weak > dependencies (Recommends or Supplements) of installed packages and > blocks installation

criterion update proposal: Keyboard layout configuration in the Initial setup

2021-09-14 Thread Kamil Paral
This is related to bug 2003253 [1]. As reported in comment 1, our current "Keyboard layout configuration" criterion [2] specifies where the configured keyboard layout must be honored. It doesn't specify the initial setup utility, which seems like a clear omission, because in that utility you

Re: [Proposal] Remove the QA:Testcase_desktop_app_basic - archive manager from matrix

2021-09-14 Thread Kamil Paral
On Mon, Sep 13, 2021 at 2:55 PM Lukas Ruzicka wrote: > Hello, > > I am proposing to remove the $subj from the Desktop matrix (Workstation > related) cause the archive manager no longer is an installed application > and its functionality has been taken by Nautilus, so it will be tested as > part

Re: Proposed blocker for wrong milestone

2021-09-06 Thread Kamil Paral
On Mon, Sep 6, 2021 at 3:08 AM Brandon Nielsen wrote: > I accidentally proposed bug 2000300[0] as a Beta blocker, I meant to > propose it as a Final blocker as I feel it violates the "SELinux and > crash notifications" criterion[1]. > > What should I do? Also propose it as a Final blocker? Or

Re: Basic criterion proposal: g-i-s shouldn't take 2 minutes to launch

2021-08-25 Thread Kamil Paral
On Wed, Aug 25, 2021 at 2:30 PM Ben Cotton wrote: > On Wed, Aug 25, 2021 at 6:44 AM Kamil Paral wrote: > > > >> > > If a utility for creating user accounts and other configuration is > configured to launch, it must be visible within 10 seconds of the first >

Re: Basic criterion proposal: g-i-s shouldn't take 2 minutes to launch

2021-08-25 Thread Kamil Paral
On Wed, Aug 25, 2021 at 12:00 AM Adam Williamson wrote: > On Sun, 2021-03-14 at 11:13 -0400, Ben Cotton wrote: > > In the wake of the BZ 1924808[1] discussion in Thursday's Go/No-Go > > meeting[2], I am proposing an addition to the Basic Release > > Criteria[3]. This would go into Post-Install

[Test-Announce] BlockerBugs webapp upgraded to 1.4.0

2021-08-23 Thread Kamil Paral
Hello, for those of you who use our BlockerBugs app to track release blockers (e.g. tracked bugs for F35 Beta [1]), there's a new version 1.4.0 deployed to production. The most user-visible change in this release is a new purple anchor icon, which is displayed next to blocker bugs which depend

[Test-Announce] BlockerBugs webapp upgraded to 1.4.0

2021-08-23 Thread Kamil Paral
Hello, for those of you who use our BlockerBugs app to track release blockers (e.g. tracked bugs for F35 Beta [1]), there's a new version 1.4.0 deployed to production. The most user-visible change in this release is a new purple anchor icon, which is displayed next to blocker bugs which depend

Re: PSA: partner-bugzilla to be replaced with bugzilla.stage on July 31st

2021-07-27 Thread Kamil Paral
On Tue, Jul 27, 2021 at 10:39 AM Miro Hrončok wrote: > On 27. 07. 21 10:34, Kamil Paral wrote: > > If any of you uses https://partner-bugzilla.redhat.com > > <https://partner-bugzilla.redhat.com> (e.g. for integration testing, > etc, > > basically as a staging B

PSA: partner-bugzilla to be replaced with bugzilla.stage on July 31st

2021-07-27 Thread Kamil Paral
If any of you uses https://partner-bugzilla.redhat.com (e.g. for integration testing, etc, basically as a staging Bugzilla instance), please note that it says: "This instance of Bugzilla will be shut down permanently on July 31st at 12:30 AM UTC. You should use bugzilla.stage.redhat.com instead"

Re: Attempt to contact "Standard Test Interface" project collaborators

2021-07-02 Thread Kamil Paral
On Wed, Jun 30, 2021 at 3:13 AM Michal Schorm wrote: > Hello, > I tried to contact the people behind "Standard Test interface" CI. > I sent the e-mail about 3 weeks ago. > Then after about 2 weeks (= ~1 week ago) I reacted to the same email > so it would appear in their inboxes again. > > Yet no

Re: Install of rawhide from netinstall without net connection

2021-06-24 Thread Kamil Paral
On Wed, Jun 23, 2021 at 3:41 PM stan via test wrote: > I tried to install the latest netinstall version (20210622) of rawhide > yesterday using optical media. Everything seems to work fine, > except... without a net connection it does not fall back to using the > minimal install on the CD. >

Re: Priority test request: jpegxl (F34)

2021-06-21 Thread Kamil Paral
On Sun, Jun 20, 2021 at 8:44 AM Adam Williamson wrote: > > I suppose the intention here is so that someone who installs the library > for > > this format gets it automatically working in Gimp. Maybe some of the > > new-fangled rich dependencies would be be better than a "Recommends". > > Yeah, I

Re: IRC Announcement

2021-06-01 Thread Kamil Paral
On Mon, May 31, 2021 at 6:55 PM Fabio Valentini wrote: > > If I intend to use Matrix exclusively, do I still need to register on > libera.chat, in order to participate in Fedora rooms? > > I think if you want to show up on the IRC side with your expected IRC > nick (for example, for IRC

Re: IRC Announcement

2021-06-01 Thread Kamil Paral
On Mon, May 31, 2021 at 10:44 PM Fabio Valentini wrote: > > Maybe it helps in Element Web, Settings, Preferences, to deactivate > > "Show join/leave messages (invites/kicks/bans unaffected)" > > Thanks for the suggestion, but I already had that setting turned off for > months. > > Weirdly

Re: IRC Announcement

2021-05-31 Thread Kamil Paral
On Thu, May 27, 2021 at 8:11 PM Nick Bebout wrote: > If you are a Matrix user, we ask for your patience as we get bridges setup > on the new network. If you were joined to rooms via the generic freenode > bridge, you will need to leave them and rejoin the fedora rooms in matrix > (which will be

Re: Disappearing and re-appearing i686 packages in the x86_64 compose

2021-05-10 Thread Kamil Paral
On Fri, May 7, 2021 at 7:59 PM Kevin Fenzi wrote: > No, I don't think it will ever be "fixed". > ... > We have in update pungi config a (IMHO poorly named) > "multilib_whitelist" variable. We can add packages to this and pungi > will pull them in, no matter if something depends on them or not. >

Re: Unretiring and maintaining the Fish Fillets NG game

2021-04-29 Thread Kamil Paral
On Thu, Apr 29, 2021 at 3:59 AM Nikolay Nikolov wrote: > What are the next steps for unretiring these two packages and > maintaining them? > Hey Nikolay, thanks for taking care of Fish Fillets, it's a great game (and also from my country). Here I found the instructions for unretiring a package:

Re: post go upgrades (re)testing

2021-04-29 Thread Kamil Paral
Gmail doesn't display it when you put the quote below your text, let me quote it differently: As for manual testing, what do you think about my previous proposal? "we could extend our upgrade testing matrices with two variants - one would test with stable updates, the other would test with

Re: post go upgrades (re)testing

2021-04-29 Thread Kamil Paral
On Wed, Apr 28, 2021 at 6:56 PM Adam Williamson wrote: > We do sort of have this already, because openQA tests all updates, and > one of the tests it runs on them is an upgrade test. > > Now, the iptables thing is interesting, because the logs of that test > on an F34 update show the issue: > >

Re: post go upgrades (re)testing

2021-04-28 Thread Kamil Paral
I wonder what the best way to improve the situation would be. There are two issues as a I see it: a) Some packages (pipewire.i686) are not in the default installation and therefore our automated checks don't catch it. The manual checks are often done with default installations as well, but someone

Re: [Proposal] The dual monitor set-up criterion (Final Version)

2021-04-26 Thread Kamil Paral
On Thu, Apr 22, 2021 at 2:32 AM Michel Alexandre Salim < mic...@michel-slm.name> wrote: > Do we need to explicitly mention that we do not expect different > monitors to have the same scaling? > I wouldn't complicate it. ___ test mailing list --

Re: [Proposal] The dual monitor set-up criterion (Final Version)

2021-04-26 Thread Kamil Paral
On Wed, Apr 21, 2021 at 10:32 AM Lukas Ruzicka wrote: > Hello friends of Fedora, > > please see the final version of the dual monitor criterion. This is the > last chance for you to suggest anything you would like to see inside (or > remove from it). > > > *"On computers using two monitors (e.g.

Re: [Proposal] The dual monitor set-up criterion (Is "dual head" redrafted)

2021-04-16 Thread Kamil Paral
On Wed, Apr 14, 2021 at 7:42 PM Felix Miata wrote: > Lukas Ruzicka composed on 2021-04-14 18:02 (UTC+0200): > > > *On computers with a possibility to connect an external monitor (e.g. two > > monitors on a desktop and one external monitor on a laptop)... > > "Desktop" to me implies not server,

Re: [Proposal] The dual head set-up criterion

2021-04-06 Thread Kamil Paral
On Thu, Apr 1, 2021 at 9:17 PM Ben Cotton wrote: > On Tue, Mar 30, 2021 at 7:27 AM Lukas Ruzicka wrote: > > > > I would like to propose a new release covering criterion that was > suggested on the yesterday's Blocker Review Meeting. Please let me know, > what you think about it and perhaps

Re: [Proposal] The dual head set-up criterion

2021-03-31 Thread Kamil Paral
On Tue, Mar 30, 2021 at 1:27 PM Lukas Ruzicka wrote: > Hello friends of Fedora, > > I would like to propose a new release covering criterion that was > suggested on the yesterday's Blocker Review Meeting. Please let me know, > what you think about it and perhaps suggest improvements. > > Target:

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-24 Thread Kamil Paral
On Tue, Feb 23, 2021 at 1:12 PM Lukas Ruzicka wrote: > >> You can set up usb passthrough through virt-manager or VirtualBox. After >> you do that, the guest gains complete control of that usb device and it >> should work/behave like it wasn't even in a vm. >> > > I can confirm that you can use

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-02-23 Thread Kamil Paral
On Tue, Feb 23, 2021 at 10:27 AM Lukas Ruzicka wrote: > Hello friends of Fedora, > > The Final Release Criterion that deals with basic sound recording as > proposed in this list has been added to Fedora 34 Final Release Criteria ( >

Re: criterion proposal: prevent services timing out on system shutdown

2021-02-22 Thread Kamil Paral
On Mon, Feb 22, 2021 at 1:45 PM Pat Kelly wrote: > A long delay on a shutdown or restart must be a blocker criterion. It's an > excuse for folks to say "Fedora is slow". The pundits will say it's broken. > Also it's very annoying especially when you're working on software or doing > testing. > >

Re: [Test-Announce] 2021-02-22 @ 17:00 UTC - Fedora 34 Blocker Review Meeting

2021-02-22 Thread Kamil Paral
On Sun, Feb 21, 2021 at 10:18 PM Chris Murphy wrote: > On Sun, Feb 21, 2021 at 12:24 PM Tom Seewald wrote: > > > > If Gnome is still hanging for 2 minutes on reboot [1] then I think we > may want to consider that a blocking bug for F34. I can at least confirm > that this bug is still affecting

Re: [Test-Announce] 2021-02-22 @ 17:00 UTC - Fedora 34 Blocker Review Meeting

2021-02-22 Thread Kamil Paral
On Sun, Feb 21, 2021 at 10:18 PM Chris Murphy wrote: > On Sun, Feb 21, 2021 at 12:24 PM Tom Seewald wrote: > > > > If Gnome is still hanging for 2 minutes on reboot [1] then I think we > may want to consider that a blocking bug for F34. I can at least confirm > that this bug is still affecting

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-19 Thread Kamil Paral
On Thu, Feb 18, 2021 at 8:37 PM Brandon Nielsen wrote: > Mumble supports both local and server loopback. Additionally the initial > setup wizard is probably a good indicator if devices are working > correctly. Unfortunately I don't know of a good publicly available > testing server. > We

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-18 Thread Kamil Paral
On Thu, Feb 18, 2021 at 2:58 PM Lukas Ruzicka wrote: > Overall it looks very good. Note that some time ago I created a special >> category for "test day's test cases", and so let's put all of those in when >> moving them into the final location: >>

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-17 Thread Kamil Paral
On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka wrote: > List of test cases to test that: > >- PipeWire is used by default ( >https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default >) > > s/bare machines/bare-metal machines/ (Also in (all) other testcases) >-

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-15 Thread Kamil Paral
On Mon, Feb 15, 2021 at 11:37 AM Lukas Ruzicka wrote: > On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral wrote: > >> Oh, one more question. Can you please specify which testcases you think >> should be general testcases to be included in our release validation >> matrices,

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-15 Thread Kamil Paral
On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka wrote: > Below, you can find the drafts of the test cases prepared on our Wiki for > you to read and comment. Also, if you have some other audio use cases that > you think should be tested, please let us know. Any suggestions are welcome. > > List

Re: [Proposal] Test Cases for the Fedora Audio Test Day.

2021-02-15 Thread Kamil Paral
On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka wrote: > List of test cases to test that: > >- PipeWire is used by default ( >https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default >) > > "This test case can be performed on both bare machines." doesn't make sense to

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-28 Thread Kamil Paral
On Thu, Jan 28, 2021 at 9:13 PM Kevin Fenzi wrote: > pipewire replaces completely pulseaudio and jack _daemons_ > > ie, now you might have jackd or pulseaudio running, after the switch you > will just have pipewire. All the pulseaudio clients and jack clients > talk to pipewire, and think it's

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-28 Thread Kamil Paral
On Fri, Jan 29, 2021 at 3:45 AM Robbi Nespu wrote: > On Arch wiki mentioned "Firefox (84+) supports this method by default, > while on Chromium (73+) one needs to enable WebRTC PipeWire support by > setting the corresponding (experimental) flag" this is for WebRTC screen > sharing, not sure it

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-28 Thread Kamil Paral
On Thu, Jan 28, 2021 at 12:36 PM Lukas Ruzicka wrote: > I do understand the audio criterion quite differently. I believe that an > application is an application, while an audio framework is an audio > framework. I think that the working sound criterion should apply to audio > as in audio

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-28 Thread Kamil Paral
On Wed, Jan 27, 2021 at 7:35 PM Adam Williamson wrote: > The reason the current criterion specifies "with gstreamer-based > applications" is to avoid being too broad and vague. It really *means* > "sound must basically work", but we're referring to gstreamer on the > basis that: > > 1. It's the

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-28 Thread Kamil Paral
On Wed, Jan 27, 2021 at 7:39 PM Jan K wrote: > It would be nice to have working sound on virtual machines as well. If you > could add instructions or note(s) whether this would be possible at this > stage it would be appreciated. > If it should work, it could be tested as well. > Hi Jan, unless

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-27 Thread Kamil Paral
On Mon, Jan 25, 2021 at 1:59 PM Kamil Paral wrote: > On Thu, Jan 21, 2021 at 2:20 PM Lukas Ruzicka wrote: > >> Hello friends of Fedora, >> >> I have been thinking about a proposal to modify the %subj. >> > > It's good to link to the existing version, s

Re: PackageKit-gtk3-module i686 (x86_32) is missing in Fedora 33 repositories

2021-01-27 Thread Kamil Paral
On Tue, Jan 26, 2021 at 7:06 PM Kevin Fenzi wrote: > > Adding normal packages are requirements for a devel package just to make > it > > multilib feels... unclean? Perhaps I'm misunderstanding something. In > order > > to have the logic self-contained, why don't we add something like > >

Re: i686 packages for x86_64 platform

2021-01-26 Thread Kamil Paral
On Tue, Jan 26, 2021 at 1:49 PM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 26.01.2021 13:24, Honggang LI wrote: > > What is the rule to concurrently select both x86_64 and i686 build > > for Fedora X86_64 platform? > > Fedora ships only i686 packages for multilib

Re: PackageKit-gtk3-module i686 (x86_32) is missing in Fedora 33 repositories

2021-01-26 Thread Kamil Paral
On Mon, Jan 25, 2021 at 11:10 PM Kevin Fenzi wrote: > For rawhide, and branched (prerelease) yes, changes likely would need to > be there. > For updates its the infrastructure ansible repo. > Sigh. So, IMHO, tickets for this should be filed as releng tickets > and folks should note which they

Re: Proposal to modify: Working Sound Beta Release Criterion

2021-01-25 Thread Kamil Paral
On Thu, Jan 21, 2021 at 2:20 PM Lukas Ruzicka wrote: > Hello friends of Fedora, > > I have been thinking about a proposal to modify the %subj. > It's good to link to the existing version, so that people can compare: https://fedoraproject.org/wiki/Fedora_34_Beta_Release_Criteria#Working_sound

Re: PackageKit-gtk3-module i686 (x86_32) is missing in Fedora 33 repositories

2021-01-25 Thread Kamil Paral
On Mon, Jan 25, 2021 at 11:17 AM Graham White wrote: > Hi, > > I'm trying to get to the bottom of bug #1901065 - > https://bugzilla.redhat.com/show_bug.cgi?id=1901065 > > Anyone know why PackageKit-gtk3-module.i686 has been removed from the > Fedora 33 repositories? This package was there for

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-22 Thread Kamil Paral
On Fri, Jan 22, 2021 at 5:21 PM Lukas Ruzicka wrote: > The latest version of the proposal: > > Testcase Audio Recording (change proposal) Description > > This test case tests whether sound can be recorded on Fedora. > Prerequisites > >- Install any sound recording application you're familiar

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-22 Thread Kamil Paral
On Fri, Jan 22, 2021 at 3:33 PM Neal Gompa wrote: > Hmm, that's more fair than I read it as originally. > Alright, the score is 1:1 on misreading each other's comments :-) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-22 Thread Kamil Paral
On Fri, Jan 22, 2021 at 3:01 PM Neal Gompa wrote: > On Fri, Jan 22, 2021 at 2:01 AM Kamil Paral wrote: > > > > On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa wrote: > >> > >> GNOME applications pull in most of the GNOME desktop as dependencies. > >> Pro

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-22 Thread Kamil Paral
On Fri, Jan 22, 2021 at 2:30 PM Lukas Ruzicka wrote: > > As an exercise, imagine the application is not called the GNOME Sound >> Recorder, but a Fred's Sound Recorder instead. I don't think we'd be having >> this conversation at all, in that case. >> > > I have been testing the new respin of

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-21 Thread Kamil Paral
On Fri, Jan 22, 2021 at 8:00 AM Kamil Paral wrote: > Your reaction is the tribalism I was talking about, negatively reacting to > anything that has "GNOME" or "K" in the name. > As an exercise, imagine the application is not called the GNOME Sound Recorder, but a

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-21 Thread Kamil Paral
On Thu, Jan 21, 2021 at 12:30 PM Neal Gompa wrote: > GNOME applications pull in most of the GNOME desktop as dependencies. > Properly developed KDE applications will pull in the KF5 libraries and > occasionally some Plasma libraries. That's just how it goes. It is > also unrealistic to expect

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-21 Thread Kamil Paral
On Thu, Jan 21, 2021 at 11:24 AM Lukas Ruzicka wrote: > > On Thu, Jan 21, 2021 at 10:04 AM Lukas Ruzicka > wrote: > >> Have you tested whether gnome-sound-recorder works well in KDE and >>> optionally also other desktops? If not (or if it pulls too many >>> dependencies), it would be good to

Re: Fedora Audio Test Cases for Test Day (a proposal)

2021-01-20 Thread Kamil Paral
On Wed, Jan 20, 2021 at 5:02 PM Brandon Nielsen wrote: > Would some kind of device switching test case be feasible? In my > experience that's where a lot of weird behavior creeps in. For example, > plugging in a USB interface, using it, and unplugging it. Or switching back > and forth between

Re: Respins for OEM preloads

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 6:44 PM Mark Pearson wrote: > Release cadence is once. We just can't update our preload images that > often - there's a long test cycle, and energy certification that goes > with that image. It's one of the reasons the X1C8 is still shipping with > Fedora32, and P1G3 and

Re: Proposal to Modify: Testcase dualboot with macOS

2021-01-20 Thread Kamil Paral
On Wed, Jan 20, 2021 at 4:45 AM Chris Murphy wrote: > On Tue, Jan 19, 2021 at 12:55 PM Geoffrey Marr wrote: > > > > After reviewing our "dualboot with macOS" testcase [0], I noticed that > the testcase says it's based on a Mac running macOS 10.12 Sierra. At this > point in time, macOS Sierra is

Re: Proposal to Modify: Testcase dualboot with macOS

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 8:56 PM Geoffrey Marr wrote: > Hi all, > > I have spent the last two days experimenting with Fedora 33 on a 2017 12" > Macbook (Macbook10,1). Unlike some previous Macs I have installed Fedora > on, out-of-the box peripheral support is fantastic. I didn't have to > install

Re: Fedora Audio Test Cases for Test Day (a proposal)

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 2:26 PM Lukas Ruzicka wrote: > Hello friends of Fedora, > > the following is a proposal for the test scope of PipeWire audio in > Fedora, which could be tested as part of Fedora Audio Test Days. Please let > me know what you think about it. > Particular test cases have

Re: Testcase Audio Basic - a change proposal

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 12:50 PM Lukas Ruzicka wrote: > Testcase Audio Basic (change proposal) Description > > This test case tests whether sound can be played on Fedora. > Prerequisites > >- Make sure your sound device (hardware) is correctly connected to >your computer, so that you can

Re: Testcase Audio Recording Basic (new test case proposal)

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 1:07 PM Lukas Ruzicka wrote: > Hello friends of Fedora, > > this is the follow up for my previous email which proposes a new test > Desktop test case to cover basic sound recording, because we feel that we > also should test some basic recording, especially in times when

Re: Testcase Audio Basic - a change proposal

2021-01-20 Thread Kamil Paral
On Tue, Jan 19, 2021 at 12:50 PM Lukas Ruzicka wrote: > Hello friends of Fedora, > > with Fedora 34, the current audio server Pulseaudio will be (probably) > replaced by PipeWire which will handle all system audio. Therefore we, at > Fedora QA, believe that some adjustments should be made to how

Re: Software Management (RPM, DNF) 2020 retrospective

2021-01-18 Thread Kamil Paral
On Mon, Jan 18, 2021 at 2:08 PM Marius Schwarz wrote: > Am 18.01.21 um 09:35 schrieb Daniel Mach: > > DNF 5 > > - > > * The goal is to remove redundant code and make sure all tools built > > on top libdnf work the same (DNF currently uses a different code path > > than microdnf and

Re: Software Management (RPM, DNF) 2020 retrospective

2021-01-18 Thread Kamil Paral
On Mon, Jan 18, 2021 at 11:33 AM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 18.01.2021 11:29, Kamil Paral wrote: > > Sounds great. But I don't see those commands neither in F33 nor in > > Rawhide. Am I looking wrong? Thanks. > > You need t

Re: Software Management (RPM, DNF) 2020 retrospective

2021-01-18 Thread Kamil Paral
On Mon, Jan 18, 2021 at 9:36 AM Daniel Mach wrote: > $ dnf offline-upgrade > $ dnf offline-distrosync >* New commands to upgrade your system on reboot > Sounds great. But I don't see those commands neither in F33 nor in Rawhide. Am I looking wrong? Thanks.

Re: proposal: move Data Corruption criterion from Final to Beta

2021-01-14 Thread Kamil Paral
On Mon, Jan 11, 2021 at 1:04 PM Kamil Paral wrote: > Hello, I already sent this proposal (quoted below) to the test list last > week. Please read the existing discussion at: > > https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/thread/BFN427ECEZTGYCDKHJYH

Re: proposal: move Data Corruption criterion from Final to Beta

2021-01-14 Thread Kamil Paral
On Thu, Jan 7, 2021 at 1:44 PM Kamil Paral wrote: > I propose we move the existing Data Corruption criterion from Final to > Beta. The criterion sounds like this: > "All known bugs that can cause corruption of user data must be fixed or > documented at Common F34

proposal: move Data Corruption criterion from Final to Beta

2021-01-11 Thread Kamil Paral
Cotton. I'm forwarding it also here to the devel list, to collect more feedback, if there is any. Thanks, Kamil -- Forwarded message - From: Kamil Paral Date: Thu, Jan 7, 2021 at 1:44 PM Subject: proposal: move Data Corruption criterion from Final to Beta To: test I propose we move

Re: Proposal: gate stable release critical path updates on openQA test results

2021-01-08 Thread Kamil Paral
On Thu, Jan 7, 2021 at 6:26 PM Adam Williamson wrote: > Hey folks! > > So here's an idea I was thinking about over the RH shutdown: I propose > we gate stable release critical path updates on the openQA tests. > +1, awesome I'm glad I'm not going to be that person that everybody pokes when

Re: Proposal: gate stable release critical path updates on openQA test results

2021-01-08 Thread Kamil Paral
On Thu, Jan 7, 2021 at 6:26 PM Adam Williamson wrote: > Hey folks! > > So here's an idea I was thinking about over the RH shutdown: I propose > we gate stable release critical path updates on the openQA tests. > +1, awesome I'm glad I'm not going to be that person that everybody pokes when

Re: proposal: move Data Corruption criterion from Final to Beta

2021-01-08 Thread Kamil Paral
On Fri, Jan 8, 2021 at 5:58 AM Chris Murphy wrote: > On Thu, Jan 7, 2021 at 5:44 AM Kamil Paral wrote: > > > The reason for this proposal is this bugzilla [1] and this blocker > ticket [2] where we discussed whether we should ship an older Firefox on > F33 Beta medi

proposal: move Data Corruption criterion from Final to Beta

2021-01-07 Thread Kamil Paral
I propose we move the existing Data Corruption criterion from Final to Beta. The criterion sounds like this: "All known bugs that can cause corruption of user data must be fixed or documented at Common F34 bugs." https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria#Data_corruption (see

Re: criteria clarification: change HTTP to HTTP(S) and drop FTP in select criteria

2021-01-07 Thread Kamil Paral
On Mon, Jan 4, 2021 at 2:40 PM Kamil Paral wrote: > This has been already discussed before [1], but the discussion died down. > Here's an updated proposal. > > Change the following: > > 1. > https://fedoraproject.org/wiki/Basic_Release_Criteria#Remote_package_source

Re: criteria clarification: change HTTP to HTTP(S) and drop FTP in select criteria

2021-01-05 Thread Kamil Paral
On Mon, Jan 4, 2021 at 5:30 PM Matthew Miller wrote: > On Mon, Jan 04, 2021 at 02:40:58PM +0100, Kamil Paral wrote: > > To: "...must be able to use HTTP(S) repositories as package sources..." > > Let's drop the (S) and make it just HTTPS. With the parenthesis, I'm >

criteria clarification: change HTTP to HTTP(S) and drop FTP in select criteria

2021-01-04 Thread Kamil Paral
This has been already discussed before [1], but the discussion died down. Here's an updated proposal. Change the following: 1. https://fedoraproject.org/wiki/Basic_Release_Criteria#Remote_package_sources From: "When using a release-blocking dedicated installer image, the installer must be able

Re: testcase base update cli

2021-01-04 Thread Kamil Paral
On Mon, Jan 4, 2021 at 12:54 PM pmkel...@frontier.com wrote: > I understand. What I'm saying is that I think that an old version of a > non-essential package was made part of the compose so their would be > something to update in the case of someone running the test on the day > the compose was

Re: testcase base update cli

2021-01-04 Thread Kamil Paral
On Sun, Jan 3, 2021 at 2:58 PM pmkel...@frontier.com wrote: > First!... Happy New Year Everyone. I hope you all had Great holidays. > > While running tests on Fedora 34 Rawhide 20210102.n.0, I saw a problem > that has been present for about a year now. If it's considered a but, I > am at a loss

Re: Fedora 34 Change: Make Fedora CoreOS a Fedora Edition (System-Wide Change)

2020-12-03 Thread Kamil Paral
On Thu, Dec 3, 2020 at 3:27 AM Dusty Mabe wrote: > There are three update streams for Fedora CoreOS. The "stable" stream is > still > on Fedora 32 but has been receiving bi-weekly updates and should be > switched over > to Fedora 33 soon (probably this week). The `next` and `testing` streams >

Re: video meeting to discuss Matrix/Element and IRC

2020-11-30 Thread Kamil Paral
As someone who hates IRC with passion (including the necessity of maintaining a znc instance and dealing with IRC authentication and network issues from time to time) and would love to jump to a more modern solution ASAP, what is the best course of action for me now? - Create an account with some

orphaned python-mongoquery

2020-11-25 Thread Kamil Paral
Hello, the python-mongoquery package is now orphaned, our group doesn't need it anymore. It doesn't seem to be required by any other package. If python-mongoquery is useful to you, feel free to take it: https://src.fedoraproject.org/rpms/python-mongoquery Cheers, Kamil

Re: orphaning Taskotron-related packages

2020-11-25 Thread Kamil Paral
On Wed, Nov 25, 2020 at 2:29 PM Josef Skladanka wrote: > > Orphaning python-mongoquery and retiring everything else makes sense to > > me. > > > > Tim > > +1 > OK, I'll make it happen. ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To

Re: Blockerbugs discussion tickets feedback 

2020-11-20 Thread Kamil Paral
On Thu, Nov 19, 2020 at 6:14 PM Adam Williamson wrote: > On Thu, 2020-11-19 at 14:41 +0100, Kamil Paral wrote: > > > > People often add a hyperlink to the criterion in question (not using > Adam's > > anchors, just ToC links, but that's fine) to a Bugzilla comment. At &g

Re: Blockerbugs discussion tickets feedback 

2020-11-20 Thread Kamil Paral
On Thu, Nov 19, 2020 at 6:08 PM Adam Williamson wrote: > > The only difference seems to be in FE vs FreezeException, and then in > > having "AcceptedBlocker" in the Whiteboard instead of AcceptedBetaBlocker > > and AcceptedFinalBlocker. Perhaps we could fix at least the latter in > > Bugzilla?

Re: Blockerbugs discussion tickets feedback 

2020-11-19 Thread Kamil Paral
On Mon, Nov 16, 2020 at 9:49 PM Kevin Fenzi wrote: > > We could add plumbing to update the mentioned data, but it's a lot of > work > > and I'm concerned about reliability. The envision workflow was that you > > visit the ticket through blockerbugs web app, and so you already know > most > > of

Re: Blockerbugs discussion tickets feedback 

2020-11-19 Thread Kamil Paral
On Thu, Nov 19, 2020 at 1:46 PM Neal Gompa wrote: > On Thu, Nov 12, 2020 at 11:57 AM Adam Williamson < > adamw...@fedoraproject.org> wrote: > >> >> * Using Magic Text for voting and admin is awkward and error-prone. >> Better UI for this would be really helpful. In addition, the state >> isn't

Re: Blockerbugs discussion tickets feedback 

2020-11-19 Thread Kamil Paral
On Tue, Nov 17, 2020 at 2:20 AM Adam Williamson wrote: > On Mon, 2020-11-16 at 20:29 +0100, Kamil Paral wrote: > > > > > > * Using Magic Text for voting and admin is awkward and error-prone. > > > Better UI for this would be really helpful. > > > > >

Re: Blockerbugs discussion tickets feedback 

2020-11-19 Thread Kamil Paral
On Tue, Nov 17, 2020 at 2:00 AM Chris Murphy wrote: > On Mon, Nov 16, 2020 at 12:30 PM Kamil Paral wrote: > > On Thu, Nov 12, 2020 at 9:25 PM Chris Murphy > wrote: > >> > >> I often had to click the 'how to vote' link in a separate tab to > copy/paste the prop

Re: Blockerbugs discussion tickets feedback 

2020-11-19 Thread Kamil Paral
On Mon, Nov 16, 2020 at 8:50 PM Ben Cotton wrote: > On Mon, Nov 16, 2020 at 2:33 PM Kamil Paral wrote: > > > > Alright, that's a similar feedback to Chris'. Could you specify what > exactly did you not remember? The tracker names (FinalBlocker, FinalFE, > etc)? Their C

Re: Blockerbugs discussion tickets feedback 

2020-11-16 Thread Kamil Paral
On Thu, Nov 12, 2020 at 4:15 PM Kamil Paral wrote: > First, a ticket creation should automatically send a comment to Bugzilla, > so that the developer/package maintainer and anyone watching knows about > the discussion and can participate (we're fairly bad about it at the > momen

Re: orphaning Taskotron-related packages

2020-11-16 Thread Kamil Paral
On Mon, Nov 16, 2020 at 8:27 AM František Zatloukal wrote: > The "correct" way to do this is to use orphaning procedure. This way, > anybody interested will have enough time to take over the to-be removed > packages. > "When Fedora maintainers do not want or are not able to maintain a package

Re: orphaning Taskotron-related packages

2020-11-12 Thread Kamil Paral
Note: The email subject should have said "retiring" instead of "orphaning". There is little reason to orphan them, retiring is the right approach here. Perhaps except for mongoquery, somebody else could be interested in maintaining that, so that one should be orphaned instead.

orphaning Taskotron-related packages

2020-11-12 Thread Kamil Paral
Hello, our Taskotron-related repositories (with exceptions like resultsdb) have been marked as EOL and archived more than half a year ago. I believe it's time to also tidy up our rpm packages in Fedora. Looking at our group ownership [1] I have identified the following rpms which could be

Re: Blockerbugs discussion tickets feedback 

2020-11-12 Thread Kamil Paral
On Thu, Nov 12, 2020 at 3:06 PM Kamil Paral wrote: > *I'd like to know how well it worked, in your opinion.* > I have mostly positive experience with the discussion tickets. It definitely increased my participation during this cycle. Previously, I mostly dealt with blockerbugs once pe

Blockerbugs discussion tickets feedback 

2020-11-12 Thread Kamil Paral
Hello, some of you used the Blockerbugs discussion tickets during the F33 cycle. I'd love to have your feedback on that functionality. As a refresher, those discussion tickets are available from the Blockerbugs website [1] after clicking on Vote/Discuss links, which forward you to a ticket

Re: Display sizing - plasma wayland vs gnome wayland

2020-11-05 Thread Kamil Paral
On Thu, Nov 5, 2020 at 1:52 AM Ed Greshko wrote: > I have rawhide installed in a kvm vm. Both plasma and gnome desktops are > installed and sddm is > the DM. > > After logging in to a gnome session the screen will resize to fill > whatever the VM's window is. > No matter if the VM's window is a

Re: current maintainer of lmbench3

2020-11-02 Thread Kamil Paral
On Sun, Nov 1, 2020 at 9:53 PM Ryan Kosta wrote: > Dear QA tool development, > > During this week's kernel testday, I encountered a few interesting > compilation errors with lmbench. Nothing to warrent major concern but > their was a variable or two that had the wrong types, enough to offer a >

<    1   2   3   4   5   6   7   8   9   10   >