No missing expected images.
Passed openQA tests: 1/1 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
On Thu, Mar 5, 2020 at 8:30 AM Daniel Mach wrote:
>
>
>
> Dne 04. 03. 20 v 23:01 Neal Gompa napsal(a):
> > On Wed, Mar 4, 2020 at 4:37 PM Zbigniew Jędrzejewski-Szmek
> > wrote:
> >> Are you going to use sd-bus for the dbus library?
> >>
> >
> > I'd hope not, given that we have cross-distro usage
No missing expected images.
Compose FAILS proposed Rawhide gating check!
17 of 43 required tests failed, 9 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 78/171 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedo
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2020-03-12 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. uitime):
= Day: Thursday ==
2020-03-12 09:00 PDT US/Pacific
2020-03-12
Missing expected images:
Iot dvd aarch64
Iot dvd x86_64
Soft failed openQA tests: 2/8 (x86_64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-IoT-32-20200310.0):
ID: 542281 Test: x86_64 IoT-dvd_ostree-iso install_default_upload
No missing expected images.
Compose FAILS proposed Rawhide gating check!
1 of 43 required tests failed, 1 result missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 17/171 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora
OLD: Fedora-Rawhide-20200309.n.1
NEW: Fedora-Rawhide-20200311.n.0
= SUMMARY =
Added images:0
Dropped images: 13
Added packages: 34
Dropped packages:2
Upgraded packages: 261
Downgraded packages: 2
Size of added packages: 303.16 MiB
Size of dropped packages
No missing expected images.
Failed openQA tests: 9/171 (x86_64), 1/2 (arm)
Old failures (same test failed in Fedora-32-20200309.n.0):
ID: 538025 Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/538025
ID: 538051 Test: x86_64 Workstation-live-iso
This is your final reminder. The Fedora 32 Beta Go/No-Go meeting is
less than 24 hours away!
On Thu, Mar 5, 2020 at 11:40 AM Ben Cotton wrote:
>
> The Go/No-Go meeting for the Fedora 32 Beta release will be held on
> Thursday, 2020-03-12 at 17:00 UTC in #fedora-meeting-1. For more
> information,
Hello nils!
On Wed, 11 Mar 2020 at 16:07, Nils Philippsen wrote:
>
> On Wed, 2020-03-11 at 12:21 +0100, clime wrote:
> > rpmbuild needs to get a preprocessed spec already.
>
> Hmm, what do you mean with that?
I mean, in this proposal, rpmbuild would need to get an already
preprocessed spec file
On Wed, Mar 11, 2020 at 12:38 PM Chris Murphy wrote:
>
> On Wed, Mar 11, 2020 at 10:26 AM Adam Williamson
> wrote:
> >
> > On Tue, 2020-03-10 at 13:21 -0600, Chris Murphy wrote:
> > > Retrying while simplifying...
> > >
> > > The spec file contains these two lines:
> > >
> > > %triggerpostun -- f
On Wed, Mar 11, 2020 at 10:26 AM Adam Williamson
wrote:
>
> On Tue, 2020-03-10 at 13:21 -0600, Chris Murphy wrote:
> > Retrying while simplifying...
> >
> > The spec file contains these two lines:
> >
> > %triggerpostun -- fedora-release < 32
> > %systemd_post fstrim.timer
> >
> > I don't know the
Hi,
On Wed, Mar 11, 2020 at 6:14 PM Sudhir D wrote:
>
>
> On 3/11/20 7:14 PM, Aleksandra Fedorova wrote:
> > Hi, all.
> >
> > Here is the summary of CI-related work happening in Fedora.
> >
> > If you have questions or topics to discuss you can also join Fedora CI
> > SIG bi-weekly meeting. Next
On 3/11/20 7:14 PM, Aleksandra Fedorova wrote:
Hi, all.
Here is the summary of CI-related work happening in Fedora.
If you have questions or topics to discuss you can also join Fedora CI
SIG bi-weekly meeting. Next session is today in #fedora-ci IRC channel
at 15:30 UTC
https://apps.fedorapro
On Tue, 2020-03-10 at 13:21 -0600, Chris Murphy wrote:
> Retrying while simplifying...
>
> The spec file contains these two lines:
>
> %triggerpostun -- fedora-release < 32
> %systemd_post fstrim.timer
>
> I don't know the proper terminology, but I think 'fedora-release' is a
> meta package? Sin
I have upgraded to Fedora 32 today and after a while I have noticed that
`repoquery --whatrequires` yields incomplete results.
From Fedora 31:
$ dnf --refresh repoquery --repo=rawhide{,-source} --whatrequires python3-flaky
pipenv-0:2018.11.26-13.fc32.src
python-ipykernel-0:5.1.4-1.fc33.src
Fr
On Wed, 2020-03-11 at 12:21 +0100, clime wrote:
> rpmbuild needs to get a preprocessed spec already.
Hmm, what do you mean with that? The spec files we currently have in
dist-git can be built directly with rpmbuild, you just need to tell
rpmbuild that the sources are in the same directory, e.g.:
Hi,
So, I went ahead and actually did the upgrade on three different
systems: two workstation installs and a server install. I'm happy to
report that the upgrade went through without any issues.
On F32, I seem to be hitting a qt-webengine bug, though. Abrt reported
it here:
https://bugzilla.redha
Hi, all.
Here is the summary of CI-related work happening in Fedora.
If you have questions or topics to discuss you can also join Fedora CI
SIG bi-weekly meeting. Next session is today in #fedora-ci IRC channel
at 15:30 UTC
https://apps.fedoraproject.org/calendar/SIGs/#m9618
===
On Wed, Mar 11, 2020 at 2:17 PM Igor Gnatenko
wrote:
>
> We could if somebody will commit on maintaining those packages in stable
> releases, keep them always updated, insert proper Obsoletes and create compat
> packages all the time.
I volunteered to work on stable-release rust packages, and t
No. All dependencies and such are in Fedora Build System and kept there as
any other package.
On Wed, Mar 11, 2020, 14:10 Peter Robinson wrote:
> On Wed, Mar 11, 2020 at 12:58 PM Randy Barlow
> wrote:
> >
> > On 3/9/20 11:53 AM, Fabio Valentini wrote:
> > > Source-only rust packages (those only
We could if somebody will commit on maintaining those packages in stable
releases, keep them always updated, insert proper Obsoletes and create
compat packages all the time.
The good news are that Koji maintainers implemented necessary configuration
and when new version will be released and deploy
On 3/10/20 12:17 PM, Ron Olson wrote:
is there a way to pass the body.template.last file to ‘fedpkg update’ so
I don’t have to fill it out for every single release, or fill it out
again when I get a timeout and have to rerun fedpkg update?
See the --file flag on bodhi updates new. It's not exa
On Wed, Mar 11, 2020 at 12:58 PM Randy Barlow
wrote:
>
> On 3/9/20 11:53 AM, Fabio Valentini wrote:
> > Source-only rust packages (those only shipping noarch -devel
> > subpackages) have been untagged from f32 on purpose by Igor. For
> > reasons I disagree with:)
>
> I too wish that we kept the Ru
On 3/9/20 11:53 AM, Fabio Valentini wrote:
Source-only rust packages (those only shipping noarch -devel
subpackages) have been untagged from f32 on purpose by Igor. For
reasons I disagree with:)
I too wish that we kept the Rust devel packages in stable releases. I am
unable to build updates fo
On Wed, 11 Mar 2020 at 11:24, Richard W.M. Jones wrote:
>
> On Mon, Mar 09, 2020 at 11:36:33PM +0100, clime wrote:
> > On Mon, 9 Mar 2020 at 22:45, Richard W.M. Jones wrote:
> > >
> > >
> > > This would break processing with ‘rpmspec’?
> >
> > With just rpmspec, yes. The preproc-rpmspec tool can
On Mon, Mar 09, 2020 at 11:36:33PM +0100, clime wrote:
> On Mon, 9 Mar 2020 at 22:45, Richard W.M. Jones wrote:
> >
> >
> > This would break processing with ‘rpmspec’?
>
> With just rpmspec, yes. The preproc-rpmspec tool can become a wrapper
> around rpmspec aliased prerpmspec essentially doing t
Dne 11. 03. 20 v 1:12 Sam Varshavchik napsal(a):
> Kevin Fenzi writes:
>
>> On Sat, Mar 07, 2020 at 09:47:03AM -0500, Sam Varshavchik wrote:
>> > Trying to follow the direction for a bug report against kernel, and
>> install
>> > the latest kernel from rawhide.
>> >
>> > The Bugzilla template says
Hey all, I'm pleased to announce that a new bugfix release of mock tool,
A 'simple' chroot build environment manager for building RPMs, is out.
There are several bugfixes, mostly for issues caused by rather big previous
release (v2.0, cca month ago).
See the release notes here:
https://githu
On Wed, 11 Mar 2020 at 07:58, Zbigniew Jędrzejewski-Szmek
wrote:
> Hi,
>
> I have two updates [1, 2] for which I got email notifications yesterday:
> > This update's test gating status has been changed to 'greenwave_failed'.
>
It means that Greenwave failed to answer to the request sent by Bodhi
30 matches
Mail list logo
