https://bugzilla.redhat.com/show_bug.cgi?id=2105286
Fedora Update System changed:
What|Removed |Added
Fixed In Version||perl-Net-SSH-0.09-39.el8
https://bugzilla.redhat.com/show_bug.cgi?id=2102597
Bug 2102597 depends on bug 2102631, which changed state.
Bug 2102631 Summary: Add perl-Class-C3-Componentised to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2102631
What|Removed |Added
https://bugzilla.redhat.com/show_bug.cgi?id=2102631
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=2105287
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
On Wed, Jul 6, 2022 at 8:13 PM Jerry James wrote:
> The various ANTLR packages will be impacted by
> https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs. The parser
> generators, which are written in Java, will no longer be available on
> i686. If absolutely necessary, we could continue to
Hi,
QtWebEngine is used as the HTML component for many Qt applications,
including large parts of the KDE software universe. It is used by web
browsers such as Falkon, but also, e.g., by KMail/Kontact.
The version that is currently (still) used the most is the Qt 5 version.
There is also a Qt
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #9 from Fedora Update System ---
FEDORA-EPEL-2022-70340b68e5 has been pushed to the Fedora EPEL 7 testing
repository.
You can provide feedback for this update here:
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
--- Comment #9 from Fedora Update System ---
FEDORA-EPEL-2022-70340b68e5 has been pushed to the Fedora EPEL 7 testing
repository.
You can provide feedback for this update here:
The following builds have been pushed to Fedora EPEL 7 updates-testing
chromium-103.0.5060.114-1.el7
elements-6.0.1-1.el7
elements-alexandria-2.25.0-1.el7
perl-Image-ExifTool-12.42-1.el7
sourcextractor++-0.18-1.el7
Details about builds:
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #8 from Fedora Update System ---
FEDORA-EPEL-2022-7c8c127aca has been pushed to the Fedora EPEL 9 testing
repository.
You can provide feedback for this update here:
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
--- Comment #8 from Fedora Update System ---
FEDORA-EPEL-2022-7c8c127aca has been pushed to the Fedora EPEL 9 testing
repository.
You can provide feedback for this update here:
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
--- Comment #7 from Fedora Update System ---
FEDORA-2022-7ae67244f7 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #7 from Fedora Update System ---
FEDORA-2022-7ae67244f7 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #6 from
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #6 from
per a previous thread i took a shot at cleaning up the fence-agents rpm
to only include the missing agents and make a new package. i am having
some issues with the source url and getting it to build. the srpm is ok,
but when i try to rebuild it into a proper rpm i get the following
(output
On Wed, Jul 20 2022 at 12:09:08 AM +0200, Kalev Lember
wrote:
Various bits have switched over to libsoup 3 which also can cause
breakage in consumers: it's not supported to link to both libsoup 2
and libsoup 3 in the same process, so care needs to be taken to only
link to one of them.
Some
On Thu, Jul 14, 2022 at 7:06 AM Jiri Vanek wrote:
> How to find they are absolutely necessary? if-in them back if theirs
> maintainers rise hand?
>
> Because that sounds like the way to go. Seeing the depndece chain, There
> seems to be no pure show stopper.
Yes, since none of the maintainers
On Sun, Jul 10, 2022 at 11:31 PM Mikolaj Izdebski wrote:
> Not sure why your list does not include these, but the following
> packages also build-require antlr-C++:
> * gdl - already has java bcond; BR on antlr would need to be wrapped into
> bcond
> * nco - seems to have ability to be built
OK, I think we are close to the finish line here.
Most of GNOME 43.alpha builds are done and gnome-shell and
evolution-data-server stacks are both nicely switched over from libsoup 2
to libsoup 3. Huge thanks to Milan Crha for all the help with libsoup 3
porting and builds! It was quite an effort
On Di, 19.07.22 21:16, Fedora Development ML (devel@lists.fedoraproject.org)
wrote:
> Would pre-building the initrds mean all users have to use the same
> partition layout. If that happened, than many people dual boot
> setups will not work
No, it dos not mean that.
Lennart
--
Lennart
Would pre-building the initrds mean all users have to use the same partition
layout. If that happened, than many people dual boot setups will not work
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tue, Jul 19, 2022 at 10:11:05PM +0200, Ondrej Mosnacek wrote:
> On Tue, Jul 19, 2022 at 9:21 PM Richard W.M. Jones wrote:
> > On Fri, Jul 15, 2022 at 05:42:35PM -0400, Ben Cotton wrote:
> > > https://fedoraproject.org/wiki/Changes/SELinux_Parallel_Autorelabel
> > >
> > > This document
On Tue, Jul 19, 2022 at 9:21 PM Richard W.M. Jones wrote:
> On Fri, Jul 15, 2022 at 05:42:35PM -0400, Ben Cotton wrote:
> > https://fedoraproject.org/wiki/Changes/SELinux_Parallel_Autorelabel
> >
> > This document represents a proposed Change. As part of the Changes
> > process, proposals are
On Fri, Jul 15, 2022 at 05:42:35PM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/SELinux_Parallel_Autorelabel
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This
On 22/07/17 09:57PM, Maxwell G wrote:
> golang 1.18.4 was released a couple days ago. This release has fixes for
> 9 medium (rated by Red Hat Product Security) CVEs, so I will preform a
> rebuild in `rawhide` and `f36` to mitigate them[^0]. See
>
On 22/07/19 07:00PM, Miro Hrončok wrote:
> I propose that we ship the fix and rebuild all affected packages.
I agree. This issue has the potential to result in confusing, hard to
debug issues for packagers (mainly) but also users.
> + new packages that have not yet reached the either EPEL 8 repo
It's me again with some more schedule reminders
* 2022-07-19 (TODAY!) — F37 Self-Contained Change proposals due
* 2022-07-20 (TOMORROW) — Mass rebuild begins
* 2022-07-26 — Software string freeze
* 2022-08-09 — F37 branches from Rawhide, Change complete (testable) deadline
More schedule details
It's me again with some more schedule reminders
* 2022-07-19 (TODAY!) — F37 Self-Contained Change proposals due
* 2022-07-20 (TOMORROW) — Mass rebuild begins
* 2022-07-26 — Software string freeze
* 2022-08-09 — F37 branches from Rawhide, Change complete (testable) deadline
More schedule details
On Tue, Jul 19, 2022, at 12:24 PM, Lennart Poettering wrote:
>
> by something like this:
>
>
> ExecStart=/usr/bin/systemd-tmpfiles --create -
> StandardInputText=f /run/sysctl.d/01-coreos-printk.conf - - - - kernel.printk
> 4
>
>
> Benefits: no shell, single process forked, no explicit
Hello EPEL people,
apparently, all EPEL 8 Python 3.8 and 3.9 packages that should only provide
python3.8dist(...)/python3.9dist(...) also provide python3dist(...).
That means, any Python 3.6 package that BuildRequires python3dist(...) might
get a Python 3.8/3.9 package instead.
This has
On 30. 06. 22 12:12, Miro Hrončok wrote:
Hello Pythonistas, packagers.
In the context of this change:
https://fedoraproject.org/wiki/Changes/PythonSafePath
Python shebangs will have be:
#! /usr/bin/python3 -sP
In order to remove certain flags, packagers have the following tool:
#
On 11. 05. 22 15:27, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/PythonSafePath
== Summary ==
The [https://docs.python.org/3.11/using/cmdline.html#cmdoption-P `-P`
flag] will be added to the Python shebang macros
(`%{py3_shbang_opts}`, `%{py3_shebang_flags}`, ...). Packages that
On Fr, 15.07.22 10:03, Colin Walters (walt...@verbum.org) wrote:
> We recently did
> https://github.com/coreos/fedora-coreos-config/pull/1840 for Fedora
> CoreOS (more background:
> https://github.com/coreos/fedora-coreos-tracker/issues/1244 ) and
> I'd like to consider applying this to all
Hi Fedora devel people,
I am sending this email, as I think that you might be interested in this topic.
We are going to have a talk session below at an event, Nest with
Fedora on 4-6th August after around 2 weeks.[1] The topic is to give
the community an idea of what Fedora people have done to
On Di, 19.07.22 16:15, Gerd Hoffmann (kra...@redhat.com) wrote:
> > Moreover, this allows us to implemented TPM policies that bind to
> > signatures of PCR hashes, instead of the literal hash values. That
> > makes the measurements a *million* times more useful, since we loose
> > the brittleness
Yes, thank you, this fixed it.
I appreciate tthe comment on the spec. I inherited it as a to-be orphan and I
have continued only fixing the spec file at the margins when things break.
Would be happy to have some help in fixing the spec.
On Tuesday, July 19, 2022 at 10:21:38 AM CDT, Ralf
Am 19.07.22 um 16:45 schrieb Globe Trotter via devel:
Thanks, btw, the command here says unknown command (see below).
Btw, the log is here:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683
The trigger of this breakdown is the sped missing "BuildRequires: gcc"
However, I regret
On Tue, Jul 19, 2022, at 10:15 AM, Gerd Hoffmann wrote:
>
> That is the big if. If you have the initrds.
>
> I've hacked up the kernel rpm to also build a initrd (targeting virtual
> machines for starters) and shipping that as (optional) sub-rpm ...
FWIW, every rpm-ostree based system defaults
V Tue, Jul 19, 2022 at 01:47:12PM +, Globe Trotter via devel napsal(a):
> However, I get the following error in the build log (of koji):
>
>
>
> checking whether the C compiler works... no
> configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
> configure: error: C compiler cannot
Thanks, btw, the command here says unknown command (see below).
Btw, the log is here:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2004683
Thanks!
$ koji save-failed-tree 2004683
Available commands:
admin commands:
add-channel Add a channel
On Tue, Jul 19, 2022 at 7:52 AM Globe Trotter via devel
wrote:
> checking whether the C compiler works... no
> configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
>
>
> Where is the config.log?
Miro Hrončok wrote:
> klamav kkofler
> koffice-kivio kkofler, rdieter
These are fixed now, successfully built in Rawhide, and I have closed the
bugs. So they should disappear from your report next time.
Kevin Kofler
On Mon, Jul 18, 2022 at 05:03:53PM +0200, Lennart Poettering wrote:
> On Mo, 18.07.22 14:52, Gerd Hoffmann (kra...@redhat.com) wrote:
>
> > Problem with measuring the initrd is that we don't have fixed hashes for
> > a given kernel version (due to generating the initrd on the installed
> >
https://bugzilla.redhat.com/show_bug.cgi?id=2031448
Roman Aleksic changed:
What|Removed |Added
CC||roman.alek...@idh.ch
--- Comment #2
On 22/07/19 02:22PM, Vitaly Zaitsev via devel wrote:
> Now it can be easily mitigated by using fmt8-devel.
>
> Rawhide compose will be fixed automatically soon, as fmt8 provides missing
> libfmt.so.8 shared library.
Yes, the *compose*, but those packages will still need to be fixed to
not FTBFS.
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #4 from Fedora Update System ---
FEDORA-EPEL-2022-b0966c6c3e has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b0966c6c3e
--
You are receiving this mail because:
You are
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
--- Comment #3 from Fedora Update System ---
FEDORA-2022-2118b27780 has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-2118b27780
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #2 from Fedora Update System ---
FEDORA-2022-7ae67244f7 has been submitted as an update to Fedora 35.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-7ae67244f7
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
Fedora Update System changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #1 from
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
--- Comment #5 from Fedora Update System ---
FEDORA-EPEL-2022-70340b68e5 has been submitted as an update to Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-70340b68e5
--
You are receiving this mail because:
You are
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #3 from Fedora Update System ---
FEDORA-2022-2118b27780 has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2022-2118b27780
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2103364
--- Comment #5 from Fedora Update System ---
FEDORA-EPEL-2022-70340b68e5 has been submitted as an update to Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-70340b68e5
--
You are receiving this mail because:
You are
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
Fedora Update System changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #1 from
https://bugzilla.redhat.com/show_bug.cgi?id=2096301
Fedora Update System changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #1 from
Never mind, I figured this out. Bad oversight on my part.
However, I get the following error in the build log (of koji):
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
configure: error: C compiler cannot create executables
See
Never mind, I figured this out. Bad oversight on my part.
However, I get the following error in the build log (of koji):
checking whether the C compiler works... no
configure: error: in `/builddir/build/BUILD/osmo-0.4.4':
configure: error: C compiler cannot create executables
See
Hello,
I was trying to fix a minor but severe error in the packging of osmo, and I get
the following error:
$ fedpkg import ~/rpmbuild/SRPMS/osmo-0.4.4-2.fc36.src.rpm
Could not execute import_srpm: (52, 'Empty reply from server')
Where is this error from and how do I get around it?
Thanks
Dear maintainers.
Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August
2022).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages
Done! golang-github-google-dap and golang-starlark added.
Thanks for the script!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Dear maintainers.
Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August
2022).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages
On Tue, Jul 19, 2022 at 2:23 PM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> On 19/07/2022 14:04, Richard Shaw wrote:
> > Unfortunately it's very difficult to "coordinate" things like this with
> > a worldwide community.
>
> True. Nearly impossible without provenpackager
Hello everyone,
Due to several circumstances I am stopping all efforts in maintaining
MariaDB 10.3 & 10.4 series in Fedora.
Just before that, I rebased both series to the latest upstream
versions, so you will get all the security patches released as for
today !
MariaDB 10.3:
On 19/07/2022 14:04, Richard Shaw wrote:
Unfortunately it's very difficult to "coordinate" things like this with
a worldwide community.
True. Nearly impossible without provenpackager rights, I'd say.
In reality, a week really isn't enough time but we can't have stuff like this
going on for
Missing expected images:
Minimal raw-xz armhfp
Compose FAILS proposed Rawhide gating check!
1 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 12/239 (x86_64), 7/167 (aarch64)
New failures (same test not failed
On 19/07/2022 13:53, Mamoru TASAKA wrote:
So far I am doing my best to fix this breakage. Now I've fixed 5 of these.
Thank you.
Currently as far as I am correct 15 pkgs are still broken - I am slowly
looking at these.
We are working on creating fmt8{,-devel} to mitigate all other breakages
On Tue, Jul 19, 2022 at 4:32 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> On 19/07/2022 01:28, Miro Hrončok wrote:
> > I see https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee990d1f61
> was
> > pushed with just a handful of builds, while many others are broken. What
>
Vitaly Zaitsev via devel wrote on 2022/07/19 18:31:
On 19/07/2022 01:28, Miro Hrončok wrote:
I see https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee990d1f61 was pushed
with just a handful of builds, while many others are broken. What happened here?
Maintainers had 1 week to rebuild all
https://bugzilla.redhat.com/show_bug.cgi?id=2108568
Bug ID: 2108568
Summary: perl-Directory-Queue-2.2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Directory-Queue
Keywords: FutureFeature,
On 16/07/2022 06:07, Mamoru TASAKA wrote:
So what should we do? Now the timing is rather critical because
mass rebuild for F37 is planned at 2022-07-20, which will rebuild fmt-9
on rawhide tree anyway, which will cause rawhide tree breakage.
I'm very sorry for this breakage.
I've checked 6/10
Hello, following the non-responsive maintainer policy
(https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/)
it seems that lcts (Christopher Engelhard) and jhogarth (James Hogarth) are
non-responsive maintainers for nextcloud package.
Below the bug reports
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
--- Comment #4 from Petr Pisar ---
It worked without mock because then /tmp is tmpfs.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
Petr Pisar changed:
What|Removed |Added
Summary|perl-Directory-Queue-2.1-3. |perl-Directory-Queue-2.1-3.
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
lionel.c...@cern.ch changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from
On Tue, Jul 19, 2022 at 5:14 AM Marcus Müller wrote:
> Since the pgtk toolkit supports both X and wayland under the hood, I'd
> very much propose
> that we do not only package an emacs-pgtk binary, but also, that it
> becomes what you get
> by default (i.e. when you install and run `emacs`).
On Tue, 19 Jul 2022 at 11:38, Vitaly Zaitsev via devel
wrote:
>
> On 19/07/2022 01:28, Miro Hrončok wrote:
> > I see https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee990d1f61 was
> > pushed with just a handful of builds, while many others are broken. What
> > happened here?
>
> Maintainers
On 19/07/2022 01:28, Miro Hrončok wrote:
I see https://bodhi.fedoraproject.org/updates/FEDORA-2022-ee990d1f61 was
pushed with just a handful of builds, while many others are broken. What
happened here?
Maintainers had 1 week to rebuild all their packages. Most did nothing.
Blame them, not
On Tue, Jul 19, 2022 at 05:17:44PM +0900, Mamoru TASAKA wrote:
Ewoud Kohl van Wijngaarden wrote on 2022/07/19 16:58:
On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:
Dear Ewoud,
Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):
On Tue, Jul 12, 2022 at 01:03:59PM
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
--- Comment #1 from Petr Pisar ---
The underlying file system is BTRFS.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
https://bugzilla.redhat.com/show_bug.cgi?id=2108537
Bug ID: 2108537
Summary: perl-Directory-Queue-2.1-3.fc37 fails tests on pp64le
in mock because number of links to a directory is
always 1
Product: Fedora
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-35-20220718.0):
ID: 1329942 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL:
Ewoud Kohl van Wijngaarden wrote on 2022/07/19 16:58:
On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:
Dear Ewoud,
Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):
On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:
rubygem-bundler_ext
On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:
Dear Ewoud,
Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):
On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:
rubygem-bundler_ext jaruga,
ruby-packagers-sig, vondruch
I have an
Dear Ewoud,
Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):
On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:
Dear maintainers.
Based on the current fail to build from source policy, the following
packages
will be retired from Fedora 37 approximately one week before
Gary Buhrmaster writes:
> On Mon, Jul 18, 2022 at 6:44 AM Petr Lautrbach wrote:
>>
>> Dan Čermák writes:
>> >
>> > Just out of curiosity, how large is the speedup typically?
>> >
>
>>
>> It depends on the number of threads your machine has. But you could get some
>> data for comparison using
85 matches
Mail list logo
