Upstream merged the patch for python3. Could someone give some love to
the package of pdf-stapler?
Otherwise, we'd run into danger to see this package get retired due to
lack of python3 support.
Thanks.
___
devel mailing list -- devel@lists.fedoraproje
Hello Kevin,
That would help us out greatly and I filed the following ticket at this
weblink with an additional request for x86_64 machine along with aarch64:
https://pagure.io/fedora-infrastructure/issue/8406
In request we are dropping support for armv7, as our application is geared
mainly for
On Fri, Nov 22, 2019 at 02:03:47PM -0800, Brian C. Lane wrote:
> I'm doing a new build of courier-unicode and maildrop this afternoon.
> Only cone depends on it, and it is currently broken - rhbz#1574797
> I'll submit a pr to update cone to 1.0 as well (I'm not sure if I can
> still build it since
I'm doing a new build of courier-unicode and maildrop this afternoon.
Only cone depends on it, and it is currently broken - rhbz#1574797
I'll submit a pr to update cone to 1.0 as well (I'm not sure if I can
still build it since I'm no longer maintainer).
--
Brian C. Lane (PST8PDT) - weldr.io - l
Happy Friday everyone!
Welcome to the CPE team weekly project update mail!
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases,
On Fri, Nov 22, 2019 at 8:19 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> Hi,
>
> a new systemd has been sent to rawhide. I don't expect any major
> trouble, but please report any issues.
>
> Quoting %changelog:
> Biggest items: cgroups v2 cpuset controller, fido_id builtin in ud
Hi,
a new systemd has been sent to rawhide. I don't expect any major
trouble, but please report any issues.
Quoting %changelog:
Biggest items: cgroups v2 cpuset controller, fido_id builtin in udev,
systemd-networkd does not create a default route for link local addressing,
systemd-networkd
Awhile back, polymake upstream started shipping two new components in
the polymake tarball: JuPyMake (a python interface to polymake) and
jupyter-polymake (a Jupyter kernel for polymake). Even though they
are all shipped in the same tarball, they have different version
numbers. This has made the
No missing expected images.
Compose FAILS proposed Rawhide gating check!
2 of 45 required tests failed, 3 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
FAILED: compose.clo
OLD: Fedora-Rawhide-20191119.n.2
NEW: Fedora-Rawhide-20191122.n.0
= SUMMARY =
Added images:1
Dropped images: 1
Added packages: 7
Dropped packages:11
Upgraded packages: 240
Downgraded packages: 0
Size of added packages: 8.34 MiB
Size of dropped packages
Is it needed to build any packages in the main Fedora repo? If not, then
why not just make a COPR for it instead of putting it in the mainline repos.
-Ian
On Fri, Nov 22, 2019 at 1:42 PM Frantisek Zatloukal
wrote:
> On Fri, Nov 22, 2019 at 12:47 PM Leigh Scott
> wrote:
>
>> > Please don't revi
On Fri, Nov 22, 2019 at 12:47 PM Leigh Scott
wrote:
> > Please don't revive ancient, unmaintained, security-critical libraries
> > for use with proprietary software not distributed by Fedora
> Old gstreamer is used by a couple of ancient apps in fedora (banshee)
>
Banshee in Fedora is using
On 2019-11-20, John M. Harris Jr wrote:
> On Tuesday, November 19, 2019 3:52:27 AM MST Petr Pisar wrote:
>> If you start fidling with things in PATH, you have the problem of SCL. And
>> as you wrote, SCL is terrible. And that was the reason why we have
>> modularity: We do not want to relocate cod
Announcing the creation of a new nightly release validation test event
for Fedora 32 Rawhide 20191122.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
> Please don't revive ancient, unmaintained, security-critical libraries
> for use with proprietary software not distributed by Fedora
Old gstreamer is used by a couple of ancient apps in fedora (banshee) and
isn't installed by default so I fail to see how you class it as
'security-critical
On Thursday, 21 November 2019 at 17:17, Michael Catanzaro wrote:
>
> Please don't revive ancient, unmaintained, security-critical libraries for
> use with proprietary software not distributed by Fedora
Well, it's useful at least for two other people and I don't see any CVE
bugs open against t
test
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.
No missing expected images.
Soft failed openQA tests: 1/1 (x86_64)
(Tests completed, but using a workaround for a known bug)
New soft failures (same test not soft failed in Fedora-Cloud-29-20191121.0):
ID: 487276 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedora
18 matches
Mail list logo
