[Bug 1828234] perl-Date-Holidays-DE-2.05 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1828234 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Date-Holidays-DE-2.05- |perl-Date-Holidays-DE-2.05-

[Bug 1834480] perl-FFI-CheckLib-0.27 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1834480 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[389-devel] 389 DS nightly 2020-05-13 - 93% PASS

https://fedorapeople.org/groups/389ds/ci/nightly/2020/05/13/report-389-ds-base-1.4.4.2-20200512gitd45d8bd.fc31.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Re-Launching the Java SIG

On Tue, 12 May 2020 15:58:39 -0500, you wrote: >As someone who has been burned due to Fedora's goody little two shoes >policies, I'd kindly ask that Fedora take a hike and not package the >software at all. The only way to make sure that the stuff included with Fedora is open source is to build

[Bug 1835063] New: perl-Mail-DKIM-1.20200513.1 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1835063 Bug ID: 1835063 Summary: perl-Mail-DKIM-1.20200513.1 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Mail-DKIM Keywords: FutureFeature, Triaged

4.4+ squashfs-tools in rawhide

I finally built 4.4 for rawhide. We already had back-ported zstd, but this gives us reproducible builds and a few other things. I'm noting this here, because squashfs-tools is used for some important stuff and in the case it breaks something I wanted people to know that it might be due to

Re: Re-Launching the Java SIG

Ty, On 2020-05-13 06:58, Ty Young wrote: On 5/12/20 5:55 AM, Felix Schwarz wrote: Am 12.05.20 um 12:32 schrieb Ty Young: Right, I figured it was some Fedora policy and not up to you. I suppose I should have been more clear there. Sorry for any confusion, it was aimed at the Fedora project

Re: CPE Weekly: 2020-05-11

On Tue, 12 May 2020 at 16:28, Clement Verna wrote: > > On Mon, 11 May 2020 at 12:55, Clement Verna wrote: >> >> >> >> On Mon, 11 May 2020 at 11:03, Fabio Valentini wrote: >>> >>> On Mon, May 11, 2020 at 10:42 AM Aoife Moloney wrote: >>> > ## GitForge Updates >>> > * We are tracking our

Re: Is dist-git a good place for work?

On Fri, 8 May 2020 at 21:13, David Cantrell wrote: > > On Mon, May 04, 2020 at 05:05:02PM +0200, Tomas Tomecek wrote: > >Let’s talk about dist-git, as a place where we work. For us, > >packagers, it’s a well-known place. Yet for newcomers, it may take a > >while to learn all the details. Even

Re: Is dist-git a good place for work?

On Tue, 12 May 2020 at 23:06, Ken Dreyer wrote: > > On Tue, May 12, 2020 at 1:45 AM clime wrote: > > > > Ken, would it be, please, possible to provide links to the patch > > branches and mentioned dist-git repos. I would like to have a closer > > look. > > Sure. I can't share the links to the RH

Re: Retired packages with maintainers

On Tue, May 12, 2020 at 03:13:42PM +0200, Pierre-Yves Chibon wrote: > On Tue, May 12, 2020 at 02:51:03PM +0200, Miro Hrončok wrote: > > On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: > > > Finally, does everyone agree about the original request: "remove all > > > maintainers > > > of retired

Re: Orphaned packages looking for new maintainers

On Mon, May 11, 2020 at 09:55:45PM +0200, Dominique Martinet wrote: > Hi, > > Miro Hrončok wrote on Mon, May 11, 2020 at 07:42:09PM +0200: > > Request package ownership via the *Take* button in he left column on > > https://src.fedoraproject.org/rpms/ > > > > waypipe

Re: New set of questions for FESCo candidates?

Zbigniew Jędrzejewski-Szmek writes: > On Mon, May 11, 2020 at 04:55:03PM -0400, Ben Cotton wrote: >> On Mon, May 11, 2020 at 4:39 PM Kevin Fenzi wrote: >> >> > If we just make it an essay with suggestions of what to include, I think >> > it might be more engaging than just a sentence or two on

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

[…] This is getting out of hand, so I logged straight into the web client. > Ok, I understand what's happening. Your email client doesn't recognize > the in-reply-to option from the url. Exactly; I will enquire and send a bug report. > Why are replying from there instead of using your email

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> From: Samuel Sieb > […] > Are you actually using the Pandora email client? It's still being = > developed? Unfortunately, it appears to not create any of the proper = > headers. No, I am not using that. The thing is, any post at lists.fedoraproject.org/archives/… has a clickable “⤣ Reply”

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On 5/12/20 3:01 PM, virgo wrote: From: Samuel Sieb […] Please fix your email client. Every reply you send starts a new thread. I saw that, my apologies. Are you actually using the Pandora email client? It's still being = developed? Unfortunately, it appears to not create any of the proper

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> From: Samuel Sieb > […] > Please fix your email client. Every reply you send starts a new thread. I saw that, my apologies. > Are you actually using the Pandora email client? It's still being = > developed? Unfortunately, it appears to not create any of the proper = > headers. No, I am not

Re: Is dist-git a good place for work?

On Tue, May 12, 2020 at 1:45 AM clime wrote: > > Ken, would it be, please, possible to provide links to the patch > branches and mentioned dist-git repos. I would like to have a closer > look. Sure. I can't share the links to the RH Ceph Storage dist-git repos, so I will give one example where I

[Bug 1823526] bugzilla fails to build with Sphinx 3.0.0

https://bugzilla.redhat.com/show_bug.cgi?id=1823526 Emmanuel Seyman changed: What|Removed |Added Status|NEW |ASSIGNED

Re: Re-Launching the Java SIG

On 5/12/20 5:55 AM, Felix Schwarz wrote: Am 12.05.20 um 12:32 schrieb Ty Young: Right, I figured it was some Fedora policy and not up to you. I suppose I should have been more clear there. Sorry for any confusion, it was aimed at the Fedora project as a whole as this is a Fedora issue. This

[Bug 1834997] New: perl-Test-Smoke-1.76 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1834997 Bug ID: 1834997 Summary: perl-Test-Smoke-1.76 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Test-Smoke Keywords: FutureFeature, Triaged

Re: LibRaw 0.20 Beta; soname bump

--  Gwyn Ciesla she/her/hers   in your fear, seek only peace  in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Tuesday, May 12, 2020 8:24 AM, Gwyn Ciesla via devel wrote: > ‐‐‐

Re: Retired packages with maintainers

Dne 12. 05. 20 v 20:26 Vít Ondruch napsal(a): > Dne 12. 05. 20 v 14:51 Miro Hrončok napsal(a): >> On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: >>> Finally, does everyone agree about the original request: "remove all >>> maintainers >>> of retired packages"? Or should we bring this to FESCo? >>

[389-devel] please review: PR 51095 - remove more unnecessary slapi entry dups

https://pagure.io/389-ds-base/pull-request/51085 -- 389 Directory Server Development Team ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: Retired packages with maintainers

Dne 12. 05. 20 v 14:51 Miro Hrončok napsal(a): > On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: >> Finally, does everyone agree about the original request: "remove all >> maintainers >> of retired packages"? Or should we bring this to FESCo? > > If the procedure is "remove all maintainers if all

Orphaning rubygem-echoe

Hi, I am orphaning rubygem-echoe. The upstream project is dead, some of its dependencies upstreams are dead and it's past time to let it go. Regards, Athos ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Non-responsive maintainer: pcpa

On Sat, May 09, 2020 at 09:57:18PM -0400, Neal Gompa wrote: Hello all, Hi Neal, I've been trying to get python-flask-babel[0] updated to v1.0.0 via PR[1]. Unfortunately, pcpa hasn't been responding to pings in the PR or emails. I've also filed the requisite non-responsive maintainer check

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

Please fix your email client. Every reply you send starts a new thread. Are you actually using the Pandora email client? It's still being developed? Unfortunately, it appears to not create any of the proper headers. On 5/12/20 7:09 AM, virgo wrote:

Re: Re-Launching the Java SIG

On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not focused or organized right > now. > > What we did

Re: [fedora-java] Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 6:17 PM Igor Raits wrote: > Count me in! I don't think I can help much, but at least can give some > suggestions. > > > Let's make this happen. > > Good luck, Fabio! Thanks! Every bit of help counts. You should now be all set with FAS group / pagure project / mailing list

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 5:43 PM Markku Korkeala wrote: > Great, really appreciate your work. Thank you! > Count me in! I'm relatively new to fedora and rpm packaging, but got ~20 > years of working with Java and my packages depends on the Java > ecosystem. FAS account: korkeala. > > Markku.

Re: Re-Launching the Java SIG

On 5/12/20 11:55 AM, Felix Schwarz wrote: > > Am 12.05.20 um 12:32 schrieb Ty Young: >> Right, I figured it was some Fedora policy and not up to you. I suppose I >> should have been more clear there. Sorry for any confusion, it was aimed at >> the Fedora project as a whole as this is a Fedora

Re: Re-Launching the Java SIG

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not

Re: Re-Launching the Java SIG

On 5/11/20 10:45 PM, Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not focused or organized right > now Great, really appreciate your work.

Re: Orphaned packages looking for new maintainers

On Mon, 2020-05-11 at 19:42 +0200, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know > for sure > that the package should be retired, please do so now with a proper > reason: >

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 10:53:32AM -0400, Omair Majid wrote: > Hi, > > A bit of a tangential question: > > Zbigniew Jędrzejewski-Szmek writes: > > > So maybe just nuke the outdated parts (member lists, "state of affairs" > > content), and keep the rest? > > My wiki-foo sucks. Is there some

Re: New set of questions for FESCo candidates?

On Mon, May 11, 2020 at 04:55:03PM -0400, Ben Cotton wrote: > On Mon, May 11, 2020 at 4:39 PM Kevin Fenzi wrote: > > > If we just make it an essay with suggestions of what to include, I think > > it might be more engaging than just a sentence or two on specific > > questions. > > > > Thinking

Re: Summary/Minutes from today's FESCo Meeting (2020-05-11)

On Mon, May 11, 2020 at 09:11:32PM -0500, Chris Adams wrote: > Once upon a time, Zbigniew Jędrzejewski-Szmek said: > > Yep. There's also /run/systemd/resolve/resolv.conf, where systemd-resolved > > always exposes a list (with the limitations described above). > > I wasn't aware of that file...

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> > On 12/05/2020 15:06, virgo wrote: > > > > ... > > > > Let’s say I want to compile `pandoc` with modifications of my own and > > > > many non- > > > > default compiler options. At the same time, on the same machine, I still > > want > > to do other stuff. `cgexec` et al. helped a lot to

Re: Re-Launching the Java SIG

Hi, A bit of a tangential question: Zbigniew Jędrzejewski-Szmek writes: > So maybe just nuke the outdated parts (member lists, "state of affairs" > content), and keep the rest? My wiki-foo sucks. Is there some way to automatically generate a list of members on the wiki from a FAS group?

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On 12/05/2020 15:06, virgo wrote: Let’s say I want to compile `pandoc` with modifications of my own and many non- default compiler options. At the same time, on the same machine, I still want to do other stuff. `cgexec` et al. helped a lot to cap the memory and CPU usage of tasks like that,

Re: Is dist-git a good place for work?

On Tue, 12 May 2020 at 09:47, Tomas Tomecek wrote: > > I haven't responded here for a few days - that doesn't mean I stopped > caring, quite the opposite, I've read every single response but the > thread grew so big that I wasn't able to keep up replying. > > Given all your valuable feedback, we

Re: CPE Weekly: 2020-05-11

On Mon, 11 May 2020 at 12:55, Clement Verna wrote: > > > On Mon, 11 May 2020 at 11:03, Fabio Valentini > wrote: > >> On Mon, May 11, 2020 at 10:42 AM Aoife Moloney >> wrote: >> > ## GitForge Updates >> > * We are tracking our progress here (nothing new added yet, fyi) >> >

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> On Di, 12.05.20 14:21, Fedora Development ML > (devel(a)lists.fedoraproject.org) wrote: > > ... > > cgroupsv2 is built around a single-writer scheme. That means any > section of the tree shall only have a singler writer, i.e. one > subsystem 'owning' it. On systemd systems the root of the tree

Re: Re-Launching the Java SIG

- Original Message - > From: "Fabio Valentini" > To: "Development discussions related to Fedora" > > Sent: Tuesday, May 12, 2020 9:44:33 AM > Subject: Re: Re-Launching the Java SIG > > On Tue, May 12, 2020 at 3:34 PM Alex Scheel wrote: > > > > Obviously count us in, Fabio :-) > >

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> On Tue, May 12, 2020 at 12:47:51PM +, virgo wrote: > ... > > > I recommend you to ask the question about v2 support on Fedora > > Bugzilla for= > > > the > > > > libcgroup package > > >

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> On 12/05/2020 14:13, Petr Pisar wrote: > ... > > On Tue, May 12, 2020 at 12:47:51PM +, virgo wrote: > >> I recommend you to ask the question about v2 support on Fedora Bugzilla > >> for= > >> > >> the > >> > >> libcgroup package > >

Re: Orphaned packages looking for new maintainers

On Monday, 11 May 2020 19.31.39 WEST Miro Hrončok wrote: > Any code contribution to make the output work better is appreciated, but > unfortunately, I am not available to work on this, sorry Where is the code? I search for it without success. :-) -- José Abílio

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On Di, 12.05.20 14:21, Fedora Development ML (devel@lists.fedoraproject.org) wrote: > > > By the way, what would you and (and others) recommend as a replacement for > > > libcgroup-tools?[fn:2] > > > > No idea. I don't use cgroups for anything on purpose. As far as I know, > > cgroups membership

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 3:34 PM Alex Scheel wrote: > > Obviously count us in, Fabio :-) *Us* means the three guys from the Dogtag PKI team? :) > Do we need a two-step bootstrap process? A first (offline) step where we run > gradle-wrapper and fetch all the resources, put all online dependencies

Re: Is dist-git a good place for work?

I haven't responded here for a few days - that doesn't mean I stopped caring, quite the opposite, I've read every single response but the thread grew so big that I wasn't able to keep up replying. Given all your valuable feedback, we are aiming to come with a plan, how to provide repositories

Re: Re-Launching the Java SIG

Obviously count us in, Fabio :-) - Original Message - > From: "Fabio Valentini" > To: "Development discussions related to Fedora" > > Sent: Tuesday, May 12, 2020 6:39:04 AM > Subject: Re: Re-Launching the Java SIG > > On Tue, May 12, 2020 at 12:34 PM Ty Young wrote: > > Right, I

Re: LibRaw 0.20 Beta; soname bump

‐‐‐ Original Message ‐‐‐ On Tuesday, May 12, 2020 5:14 AM, Miro Hrončok wrote: > On 12. 05. 20 0:12, Miro Hrončok wrote: > > > On 11. 05. 20 22:33, Gwyn Ciesla via devel wrote: > > > > > I'm building LibRaw 0.20 Beta 1 for rawhide, along with all direct > > > consumers, > > > in a

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On 12/05/2020 14:13, Petr Pisar wrote: On Tue, May 12, 2020 at 12:47:51PM +, virgo wrote: I recommend you to ask the question about v2 support on Fedora Bugzilla for= the libcgroup package

Re: Retired packages with maintainers

On Tue, May 12, 2020 at 02:51:03PM +0200, Miro Hrončok wrote: > On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: > > Finally, does everyone agree about the original request: "remove all > > maintainers > > of retired packages"? Or should we bring this to FESCo? > > If the procedure is "remove all

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On Tue, May 12, 2020 at 12:47:51PM +, virgo wrote: > > I recommend you to ask the question about v2 support on Fedora Bugzilla for= > > > > the > > > > libcgroup package > > > =3Dlibcgroup=3DFedora_format=3Dadvanced>. >

Re: Retired packages with maintainers

On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: Finally, does everyone agree about the original request: "remove all maintainers of retired packages"? Or should we bring this to FESCo? If the procedure is "remove all maintainers if all branches are retired or EOL" than yes, this is a good

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

> Date: Tue, 12 May 2020 13:00:13 +0200 > From: Petr Pisar > Subject: Re: Transitioning scripts relying on libcgroup-tools to the > cgroup’s unified hierarchy (v2) > […] > cgcreate tool comes from libcgroup-tools-0:0.42.2-1.fc32 package that comes > from libcgroup project sources, and

Re: Retired packages with maintainers

On Tue, May 12, 2020 at 02:08:12PM +0200, Igor Raits wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On Tue, 2020-05-12 at 08:49 +0200, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > > > A little while ago we have received the request on the infra issue > > tracker to >

Re: [fedora-java] Re-Launching the Java SIG

On Tue, May 12, 2020 at 1:02 PM Aleksandar Kurtakov wrote: > Good luck with that! As someone that has been part of the Java SIG since day > 0 I wish you make Fedora even better workstation for Java developer than we > ever managed. Thank you! You're welcome to (re-)join the effort, we'd be

Re: Proposal: Revise FESCo voting policy

Hi, On Tue, May 12, 2020 at 10:19 AM Vít Ondruch wrote: > > > Dne 11. 05. 20 v 19:40 Aleksandra Fedorova napsal(a): > > Hi, > > > > On Mon, May 11, 2020 at 5:52 PM Stephen Gallagher > > wrote: > >> During today's FESCo meeting, we encountered an unusual voting > >> situation for the first

[Bug 1820714] perl-WWW-Search-2.519 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1820714 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED CC|

Re: Is dist-git a good place for work?

On Thu, May 7, 2020 at 3:54 PM clime wrote: > > > > In the rare occasion that I need to make downstream-only changes with > > patches, I usually just explode the upstream tarball, run "git init", > > then "git add .", "git commit -m import", apply my changes, and then > > do "git diff --patch >

Re: Retired packages with maintainers

On Tue, May 12, 2020 at 2:03 PM Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > A little while ago we have received the request on the infra issue tracker to > remove all maintainers of retired packages [1]. > > So today I decided to look at what this would look like and wrote a script

Re: Retired packages with maintainers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Tue, 2020-05-12 at 08:49 +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > A little while ago we have received the request on the infra issue > tracker to > remove all maintainers of retired packages [1]. > > So today I decided to

Retired packages with maintainers

Good Morning Everyone, A little while ago we have received the request on the infra issue tracker to remove all maintainers of retired packages [1]. So today I decided to look at what this would look like and wrote a script that queries PDC for the list of all branches on all projects [2],

Retired packages with maintainers

Good Morning Everyone, A little while ago we have received the request on the infra issue tracker to remove all maintainers of retired packages [1]. So today I decided to look at what this would look like and wrote a script that queries PDC for the list of all branches on all projects [2],

Re: Pinging spin or labs maintainers in failed composes tickets

On 11. 05. 20 20:03, Miro Hrončok wrote: On 11. 05. 20 19:53, Mohan Boddu wrote: Sorry for the late reply, compose-tracker uses the toml file https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151 And the PR is merged and it should work. Thanks for confirmation. It

[Bug 1829906] Upgrade perl-Net-OpenSSH to 0.79

https://bugzilla.redhat.com/show_bug.cgi?id=1829906 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

Re: Re-Launching the Java SIG

On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not focused or organized right > now. > > What we did

Re: Re-Launching the Java SIG

On 5/12/20 5:39 AM, Fabio Valentini wrote: On Tue, May 12, 2020 at 12:34 PM Ty Young wrote: Right, I figured it was some Fedora policy and not up to you. I suppose I should have been more clear there. Sorry for any confusion, it was aimed at the Fedora project as a whole as this is a Fedora

Re: [fedora-java] Re-Launching the Java SIG

On Mon, May 11, 2020 at 10:46 PM Fabio Valentini wrote: > This past weekend I finally decided to jump off the cliff and attempt > to re-launch the Java SIG. It seems there's some interest in keeping > the Java stack maintained, it's just not focused or organized right > now. > > What we did when

Re: LibRaw 0.20 Beta; soname bump

On Tue, May 12, 2020 at 12:21 PM Aleksandra Fedorova wrote: > > Hi, > > On Tue, May 12, 2020 at 12:05 PM Miro Hrončok wrote: > > > > On 12. 05. 20 10:46, Daniel P. Berrangé wrote: > > > Are we ever going to get gating on rawhide, so that soname bumps are > > > blocked > > > from entering the

Re: Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

On Tue, May 12, 2020 at 09:03:22AM +, virgo wrote: > The issue is that I upgraded my computer to Fedora 32 from version 30, and > broke some scripts in the process; they were relying on cgroup v1. [...] > how to use the `cgcreate` command and the like under libcgroup v2? cgcreate tool comes

Re: Re-Launching the Java SIG

Am 12.05.20 um 12:32 schrieb Ty Young: > Right, I figured it was some Fedora policy and not up to you. I suppose I > should have been more clear there. Sorry for any confusion, it was aimed at > the Fedora project as a whole as this is a Fedora issue. This is not a Fedora issue but a consequence

Re: Re-Launching the Java SIG

On 12.05.2020 10:35, Ty Young wrote: > JUST PACKAGE THE PRE-COMPILED BUILDS!!! No. Please read Fedora packaging guidelines. All packages **must** be built from sources. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list --

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 12:34 PM Ty Young wrote: > Right, I figured it was some Fedora policy and not up to you. I suppose > I should have been more clear there. Sorry for any confusion, it was > aimed at the Fedora project as a whole as this is a Fedora issue. I am aware that Arch is just

Re: Re-Launching the Java SIG

On 5/12/20 3:48 AM, Felix Schwarz wrote: Am 12.05.20 um 10:35 schrieb Ty Young: JUST PACKAGE THE PRE-COMPILED BUILDS!!! Don't take me as rude but this is not possible. This is documented in Fedora's packaging policies:

[Bug 1834195] perl-Set-Crontab missing from epel8 repository metadata

https://bugzilla.redhat.com/show_bug.cgi?id=1834195 --- Comment #4 from Petr Pisar --- I checked http://mirror.xnet.co.nz/pub/epel/8/Everything/x86_64/ and it works for me: # dnf --disableexcludes=all --disablerepo=\* --repofrompath=0,http://mirror.xnet.co.nz/pub/epel/8/Everything/x86_64/

[Bug 1832203] Upgrade perl-Type-Tiny to 1.010002

https://bugzilla.redhat.com/show_bug.cgi?id=1832203 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

Re: LibRaw 0.20 Beta; soname bump

Hi, On Tue, May 12, 2020 at 12:05 PM Miro Hrončok wrote: > > On 12. 05. 20 10:46, Daniel P. Berrangé wrote: > > Are we ever going to get gating on rawhide, so that soname bumps are blocked > > from entering the dist until rebuilds of deps are ready ? > > We wanted to, Taskotron was able to

Re: LibRaw 0.20 Beta; soname bump

On 12. 05. 20 0:12, Miro Hrončok wrote: On 11. 05. 20 22:33, Gwyn Ciesla via devel wrote: I'm building LibRaw 0.20 Beta 1 for rawhide, along with all direct consumers, in a multi-stage chain build, today, including the following: deepin-image-viewer elementary-photos freeimage gthumb

Re: LibRaw 0.20 Beta; soname bump

On 12. 05. 20 10:46, Daniel P. Berrangé wrote: Are we ever going to get gating on rawhide, so that soname bumps are blocked from entering the dist until rebuilds of deps are ready ? We wanted to, Taskotron was able to figure this out, but was recently EOLed, before a viable alternative

Re: Proposal: Revise FESCo voting policy

On 12. 05. 20 10:27, Vít Ondruch wrote: Actually, it should be also useful if position of each abstaining FESCo member was explained. Because for myself, I can interpret 5 people abstaining just as a lack of understanding of the issue and nothing else. For me, it was that. I wasn't able to

pghmcfc pushed to perl-MCE-Shared (master). "Update to 1.869 (..more)"

Notification time stamped 2020-05-12 09:47:49 UTC From a7a5a6881425f233e91b4c6ba70b125f564d13da Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: May 12 2020 09:46:59 + Subject: Update to 1.869 - New upstream release 1.869 - Disabled unicode testing for MCE::Shared::Cache on Perl 5.10.1;

[389-devel] Please review: PR #51075 - Issue 50610 - memory leak in dbscan and changelog encryption

Hi team, please, check my memory leaks fix: https://pagure.io/389-ds-base/pull-request/51075 Thanks, Simon signature.asc Description: PGP signature ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Proposal: Revise FESCo voting policy

On Tue, May 12, 2020 at 10:27:26AM +0200, Vít Ondruch wrote: > > Dne 12. 05. 20 v 10:18 Vít Ondruch napsal(a): > > Dne 11. 05. 20 v 19:40 Aleksandra Fedorova napsal(a): > >> Hi, > >> > >> On Mon, May 11, 2020 at 5:52 PM Stephen Gallagher > >> wrote: > >>> During today's FESCo meeting, we

Transitioning scripts relying on libcgroup-tools to the cgroup’s unified hierarchy (v2)

Greetings, I am very aware this is not the place for user questions. This is also where the likelihood of an answer /at all/ are the highest. So, please bear with me; at the bottom[fn:1] are all the other places where I tried to find hints before posting here. The issue is that I upgraded my

[Bug 1834195] perl-Set-Crontab missing from epel8 repository metadata

https://bugzilla.redhat.com/show_bug.cgi?id=1834195 --- Comment #3 from Peter Ajamian --- I'm using http://mirror.xnet.co.nz/pub/epel/8/Everything/x86_64/. I also checked with http://ucmirror.canterbury.ac.nz/linux/fedora/fedora-epel/8/Everything/x86_64/ and

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 03:35:55 -0500, Ty Young wrote: > > On 5/12/20 2:50 AM, Fabio Valentini wrote: > > > What about packaging gradle instead? (In the cases I looked into, > > > porting from gradle to maven would be rewriting the build system from > > > scratch. Assuming that we have tens and

Re: Re-Launching the Java SIG

Hey Fabio, thank you very much for your work. I can't take on more Fedora work but still wanted to express my gratitude :-) Felix ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Re-Launching the Java SIG

Am 12.05.20 um 10:35 schrieb Ty Young: > JUST PACKAGE THE PRE-COMPILED BUILDS!!! Don't take me as rude but this is not possible. This is documented in Fedora's packaging policies: https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packaged/#prebuilt-binaries-or-libraries

Re: LibRaw 0.20 Beta; soname bump

On Tue, May 12, 2020 at 12:12:01AM +0200, Miro Hrončok wrote: > On 11. 05. 20 22:33, Gwyn Ciesla via devel wrote: > > I'm building LibRaw 0.20 Beta 1 for rawhide, along with all direct > > consumers, in a multi-stage chain build, today, including the following: > > > > deepin-image-viewer > >

Re: Re-Launching the Java SIG

On 5/12/20 2:50 AM, Fabio Valentini wrote: What about packaging gradle instead? (In the cases I looked into, porting from gradle to maven would be rewriting the build system from scratch. Assuming that we have tens and will have hundreds of packages with gradle, in the long term it seems better

[Bug 1834480] perl-FFI-CheckLib-0.27 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1834480 --- Comment #2 from Fedora Update System --- FEDORA-2020-12cd8fc8b8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-12cd8fc8b8 -- You are receiving this mail because: You are on the CC list

[Bug 1834480] perl-FFI-CheckLib-0.27 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1834480 Petr Pisar changed: What|Removed |Added Status|NEW |MODIFIED

Re: Proposal: Revise FESCo voting policy

Dne 12. 05. 20 v 10:18 Vít Ondruch napsal(a): > Dne 11. 05. 20 v 19:40 Aleksandra Fedorova napsal(a): >> Hi, >> >> On Mon, May 11, 2020 at 5:52 PM Stephen Gallagher >> wrote: >>> During today's FESCo meeting, we encountered an unusual voting >>> situation for the first time: Four FESCo members

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 10:15 AM Ankur Sinha wrote: > > On Tue, May 12, 2020 09:50:30 +0200, Fabio Valentini wrote: > > > > > > Yep, count me in. > > > > Thanks. I'll get your memberships set up. :) > > Thank you for starting this off, and thank you for taking care of the > Java packages in the

Re: Proposal: Revise FESCo voting policy

Dne 11. 05. 20 v 19:40 Aleksandra Fedorova napsal(a): > Hi, > > On Mon, May 11, 2020 at 5:52 PM Stephen Gallagher wrote: >> During today's FESCo meeting, we encountered an unusual voting >> situation for the first time: Four FESCo members voted in favor (+1) >> of a measure and five FESCo

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 09:50:30 +0200, Fabio Valentini wrote: > > > > Yep, count me in. > > Thanks. I'll get your memberships set up. :) Thank you for starting this off, and thank you for taking care of the Java packages in the meantime too. We really appreciate it. Please count me in also. :)

  1   2   >