Re: Re-Launching the Java SIG

On Mon, May 11, 2020 at 09:45:15PM +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 d

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

On Mon, 11 May 2020 at 18:59, Ken Dreyer wrote: > > On Sun, May 10, 2020 at 11:51 PM Petr Pisar wrote: > > How do you backport fixes? Do apply the fixes directly to dist-git? Or do > > you > > apply the fixes to a corresponding patches branch that you occur to have > > around till needed (e.g. t

Re: Re-Launching the Java SIG

On Tue, May 12, 2020 at 9:33 AM Zbigniew Jędrzejewski-Szmek wrote: > The wiki is not that bad actually. The links to guidelines and package > lists are still useful. Even the packaging wishlist is mostly up to > date since we didn't manage to touch most of the items ;) > So maybe just nuke the out

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. :) --

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 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 me

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 v

[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 CC|ppi...@redhat.

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

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 > > elem

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 Feli

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 devel-le...@lists.fedoraproject.or

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 will

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 c

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 encount

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 gras

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 existed

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 indi-gpho

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 figure

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: https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-pack

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 packag

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 -- de

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: 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 f

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 dis

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: 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 is

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 when

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

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], gather

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 lo

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: 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 time:

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 luck

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: 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 libcgroup

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 thing.

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&product=3DFedora&query_fo

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 ma

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: 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 m

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 figur

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 with

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: 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: 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 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: 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&product

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 :-) > > *Us*

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: 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) >> > https://fedoraproject

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 a

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, with

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? Thank

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: 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... to

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 abo

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 way

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: > https://fedora

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: 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 focuse

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 issue

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. Gre

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 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 when

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: 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 bu

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 devel-

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 br

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? >> If

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: > ‐‐‐ O

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 is

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

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 u

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 > […] > 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” U

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 cli

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: 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 orph

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 packag

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: 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 thou

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 progress

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 a

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 this

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