No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproj
No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproj
On Wed, 2020-01-08 at 09:39 -0500, pmkel...@frontier.com wrote:
> > > https://fedoraproject.org/wiki/User:Adamwill/Draft_testcase_reboot
> >
> > Hey Pat, thanks for your edits. I've made some further changes to the same
> > page (you can see them in history). I think the test case is good to go an
Hey folks!
Just wanted to point up a neat project Fabio Valentini has been working
on. It's called fedora-update-feedback:
https://github.com/ironthree/fedora-update-feedback
it's an alternative to fedora-easy-karma, written in Rust. He says it
should be pretty much working at this point, and he
On Mon, Jan 20, 2020, 15:42 Adam Williamson
wrote:
> Hey folks!
>
> Just wanted to point up a neat project Fabio Valentini has been working
> on. It's called fedora-update-feedback:
>
> https://github.com/ironthree/fedora-update-feedback
>
> it's an alternative to fedora-easy-karma, written in Ru
On Mon, 2020-01-20 at 15:59 +0100, Fabio Valentini wrote:
> - download and extract tarball of the latest fedora-update-feedback
> release (or use git master, at your peril)
> - "dnf install cargo" (for the rust compiler and build system)
And also "dnf install openssl-devel", right?
Ciao,
A.
_
On Mon, Jan 20, 2020 at 4:33 PM Alessio wrote:
>
> On Mon, 2020-01-20 at 15:59 +0100, Fabio Valentini wrote:
> > - download and extract tarball of the latest fedora-update-feedback
> > release (or use git master, at your peril)
> > - "dnf install cargo" (for the rust compiler and build system)
(s
The topic came up in our meeting today that seemed to be a problem with
Japanese jeyboards (kana kanji) working in F32. I think I must have
initially misunderstood the issue. Apparently the observed problem was
that when in the GCC under Region & Language the Japanese keyboard
option "Kana Kanj
