Re: Re: Re: A reminder: you cannot just "revert" package version bumps

2024-02-01 Thread Kevin Fenzi
On Thu, Feb 01, 2024 at 02:51:54AM +0100, Kevin Kofler via devel wrote: > kevin wrote: > > distro-sync is nice and all, but it's not a silver bullet. > > In cases of simple packages a downgrade may not break anything, but in > > cases where other things already built upon it, where the new one > >

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-02-01 Thread Gary Buhrmaster
On Thu, Feb 1, 2024 at 3:11 AM Kevin Kofler via devel wrote: > > If the distro-sync (which should be the default way to do updates > at least on Rawhide, if not everywhere) mentions a package being downgraded, > that is much more likely to be noticed. > I look forward to your formal change propos

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-01-31 Thread Kevin Kofler via devel
Gary Buhrmaster wrote: > While I don't like epochs, there is nothing intrinsically > wrong with an epoch bump when a packager > determines that they need to downgrade because > the testing for the upgrade was insufficient or > inadequately performed and the packager found > that there was no way fo

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-01-31 Thread Gary Buhrmaster
On Thu, Feb 1, 2024 at 1:53 AM Kevin Kofler via devel wrote: > And the proposed "solution" of bumping Epoch fixes none of that. It just > introduces an Epoch that we will be stuck with forever. It will not > magically make the downgrade safe in any of the 3 situations you describe. While I don't

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-01-31 Thread Kevin Kofler via devel
kevin wrote: > distro-sync is nice and all, but it's not a silver bullet. > In cases of simple packages a downgrade may not break anything, but in > cases where other things already built upon it, where the new one > changed conguration or interface, or even where the upgrade changed > data, it can

Re: Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

2024-01-31 Thread Alessandro Astone
The "personal attack" is a consideration on the proposed maintainer of these packages. > every effort in order to not to break things must be made. Then I cannot support these packages being added. It is putting additional effort on the KDE-SIG up to once per every week; especially since we're

Re: Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

2024-01-31 Thread Mattia Verga via devel
Messaggio originale 31/01/24 22:27, Alessandro Astone ha scritto: > I can support that. > > But am I supposed to ignore the fact that kkofler is already bullying the > KDE SIG into not breaking that one other package they maintain that > occasionally breaks on kde update

Re: Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

2024-01-31 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Jan 30, 2024 at 01:48:08PM -0800, kevin wrote: > If Adam's summary is understood by all the involved parties, then I > don't think there would be a problem allowing the packages in. > Everyone involved should just try and not place undue burdens on others. > If there's a flood of reports or

Re: Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

2024-01-30 Thread kevin
I've very sorry if anyone was upset by fesco wanting to not allow the new packages in while this was discussed. I'm the one who suggested that, but as noted upthread, the idea was simply to allow time for discussion before doing things. There's actually a slightly similar case from long long ago

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-01-30 Thread kevin
On Tue, Jan 30, 2024 at 08:08:54AM +, Daniel P. Berrangé wrote: > On Mon, Jan 29, 2024 at 03:43:39PM -0800, Adam Williamson wrote: > > nirik ran a script that checks for versioning issues in Rawhide today, and > > it found several: https://pagure.io/releng/issue/11922#comment-893797 > > > > So

Re: Re: A reminder: you cannot just "revert" package version bumps

2024-01-30 Thread kevin
On Tue, Jan 30, 2024 at 01:19:18AM +0100, Kevin Kofler via devel wrote: > Sérgio Basto wrote: > > yes rawhide user should use dnf distro-sync not dnf upgrade > > +1. Rawhide EVRs should be allowed to go backwards, that is an integral part > of being a development branch. distro-sync is nice and

Re: Re: Fedora 40 mass rebuild has begun

2024-01-21 Thread kevin
On Sun, Jan 21, 2024 at 06:13:21PM +, Sérgio Basto wrote: > On Fri, 2024-01-19 at 15:50 +0530, Samyak Jain wrote: > > Hi all, > > > > Per the Fedora Linux f40 schedule [1] we started a mass rebuild on > > 2024-01-17 for Fedora f40 but due to various reasons such as dnf > > issues, and other si

Re: Re: Mass rebuild: git push --no-verify

2024-01-18 Thread kevin
On Thu, Jan 18, 2024 at 08:24:38PM +0100, Björn Persson wrote: > > If, hypothetically, a defect in the mass-rebuild script would corrupt > thousands of spec files, how easy would it be to write a mass-revert > script to repair the damage? The mass-revert script shouldn't just > revert the latest c

Re: Re: Mass rebuild: git push --no-verify

2024-01-18 Thread kevin
On Thu, Jan 18, 2024 at 09:15:18AM -0700, Jerry James wrote: > On Thu, Jan 18, 2024 at 4:50 AM Tomas Hrcka wrote: > > This is not a good idea. Because of a few packages that are not rebuilding > > we would disable the hook for every push the script does. > > My thinking is that the hook is not u

Re: Re: Mock Configs v39.3 released - DNF5 used for F40+ builds

2024-01-16 Thread Chuck Anderson
On Tue, Jan 16, 2024 at 08:02:28PM +0100, Pavel Raiskup wrote: > I just want to bump this thread; @kevin updated Fedora Koji today > - the Fedora 40+ (current Rawhide) builds are already handled with DNF5. > > Happy (faster) building! And should you face any issue, please report. > Pavel In case

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-10 Thread Milan Crha
On Tue, 2024-01-09 at 19:01 +0100, Kalev Lember wrote: > The gnome-shell update just landed in rawhide, so it needs a few > minutes before the build roots are regenerated. If you can do 'koji > wait-repo f40-build-side-80962 --build mutter-46~alpha-2.fc40' first > to make sure new mutter is availab

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-09 Thread Kalev Lember
On Tue, Jan 9, 2024 at 6:42 PM Milan Crha wrote: > On Tue, 2024-01-09 at 18:36 +0100, Kalev Lember wrote: > > Looks like this has a bit of a mid air collision with gnome-shell > > 46.alpha that's in a different bodhi update: > > https://bodhi.fedoraproject.org/updates/FEDORA-2024-d7b40ac758 > >

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-09 Thread Milan Crha
On Tue, 2024-01-09 at 18:36 +0100, Kalev Lember wrote: > Looks like this has a bit of a mid air collision with gnome-shell > 46.alpha that's in a different bodhi update: > https://bodhi.fedoraproject.org/updates/FEDORA-2024-d7b40ac758 Hi, that's a pita. Let me know if I can help with anyth

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-09 Thread Kalev Lember
On Tue, Jan 9, 2024 at 6:25 PM Milan Crha wrote: > On Mon, 2024-01-08 at 18:40 -0800, kevin wrote: > > On Mon, Jan 08, 2024 at 11:05:33AM +0100, Milan Crha wrote: > > >elementary-calendar > > >evolution-chime (which is part of pidgin-chime) > > >gnome-panel > > >phosh > > >

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-09 Thread Milan Crha
On Mon, 2024-01-08 at 18:40 -0800, kevin wrote: > On Mon, Jan 08, 2024 at 11:05:33AM +0100, Milan Crha wrote: > >    elementary-calendar > >    evolution-chime (which is part of pidgin-chime) > >    gnome-panel > >    phosh Hi, thank you all for the promptly rebuild of the left dependenci

Re: Re: [heads-up] evolution-data-server libecal-2.0 soname version bump in rawhide

2024-01-08 Thread kevin
On Mon, Jan 08, 2024 at 11:05:33AM +0100, Milan Crha wrote: > On Mon, 2024-01-08 at 10:34 +0100, Milan Crha wrote: > > I'll handle those I've commit rights for, which is most of them. > > > > ... > > > >fedpkg build --target=f40-build-side-80962 > > > Hi, > the leftover packages to be d

Re: Re: Are package-owner mail addresses working?

2024-01-03 Thread Kevin Fenzi
On Wed, Jan 03, 2024 at 09:59:23AM -0500, Stephen Gallagher wrote: > On Wed, Jan 3, 2024 at 8:15 AM Sergio Pascual wrote: > > > > El lun, 1 ene 2024 a las 13:49, Mamoru TASAKA > > () escribió: > > > > > > Sergio Pascual wrote on 2024/01/01 21:36: > > > > Hello and happy new year. > > > > > > > > A

Re: Re-triggering fedora CI tests

2023-10-17 Thread Adam Williamson
On Tue, 2023-10-17 at 11:41 +, Martin Cermak wrote: > Hello folks, > > based on my end user experience, users are only allowed to re-trigger Fedora > CI tests in case they are committers for the component in question. Would it > be possible to open it a little bit for certain other users?

Re: Re: shotcut compilation fails with "error: ‘hasPro’ was not declared in this scope"

2023-09-24 Thread Fabio Valentini
On Sun, Sep 24, 2023 at 1:36 PM Sam Varshavchik wrote: > > Martin Gansser writes: > > > I have copied the virtual machine from a Windows computer to my Fedora 38 > > computer and shotcut can no longer be compiled here, but it can on the > > Windows computer. > > Do I have to repair the file system

Re: Re: shotcut compilation fails with "error: ‘hasPro’ was not declared in this scope"

2023-09-24 Thread Sam Varshavchik
Martin Gansser writes: I have copied the virtual machine from a Windows computer to my Fedora 38 computer and shotcut can no longer be compiled here, but it can on the Windows computer. Do I have to repair the file system on the Linux computer or do anything else? You snipped out the rele

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-07 Thread Chris Murphy
On Thu, Apr 7, 2022 at 2:36 PM Chris Murphy wrote: > The Windows Hardware Certification Program is a marketing program. If > you want to say things like "made for windows 8" in your product, you > have to comply with their requirements. And the requirements differ by > years for Windows and Windo

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-07 Thread Chris Murphy
On Thu, Apr 7, 2022 at 10:04 AM Jared Dominguez wrote: > > Microsoft has required since Windows 8 (released in 2012) that any systems > that are certified with Windows must ship with UEFI by default The Windows Hardware Certification Program is a marketing program. If you want to say things like

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-07 Thread Jared Dominguez
On Thu, Apr 7, 2022 at 11:09 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Wed, Apr 06, 2022 at 10:47:30AM -0400, Robbie Harwood wrote: > > majid hussain writes: > > > > > hi, > > > could someone kindly tell me if my toshiba l750 machine has EFI > support? > > > i'm blind and ef

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-07 Thread Chris Adams
Once upon a time, Zbigniew Jędrzejewski-Szmek said: > Changing UEFI setting in the firmware is a big problem. We know that > a) it can only be done by tweaking settings in the firmware interface > which looks different on every machine, b) users find it very hard in > general, and c) for blind use

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-07 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Apr 06, 2022 at 10:47:30AM -0400, Robbie Harwood wrote: > majid hussain writes: > > > hi, > > could someone kindly tell me if my toshiba l750 machine has EFI support? > > i'm blind and efi/bios screens are in accessible. Based on a web query, it most likely has EFI support, but it also s

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-06 Thread Robbie Harwood
majid hussain writes: > hi, > could someone kindly tell me if my toshiba l750 machine has EFI support? > i'm blind and efi/bios screens are in accessible. Easiest is probably to do: ls /sys/firmware/efi This tells you whether the machine booted using UEFI. anaconda will set up a UEFI-capable

Re: Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

2022-04-05 Thread majid hussain
hi, could someone kindly tell me if my toshiba l750 machine has EFI support? i'm blind and efi/bios screens are in accessible. Majid > Sent: Wednesday, April 06, 2022 at 6:03 am > From: "Gary Buhrmaster" > To: "Development discussions related to Fedora" > > Subject: Re: F37 Change: Deprecat

Re: Re-Launching the Java SIG

2021-09-15 Thread Jhordy Caceres
Excellent! This is what I needed, I was thinking of starting as a Java packager, specially for the apache-rat package. I'd like to know your opinion on the package or some (other) recommendation. ___ devel mailing list -- devel@lists.fedoraproject.org

Re: Re-Launching the Java SIG

2021-09-15 Thread Jhordy Caceres
Very Thank You! Of course, You can count on me for anything. I'll try to help where I can. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.f

Re: Re-Launching the Java SIG

2021-09-15 Thread Didik Supriadi
On 9/13/21 8:41 PM, Jhordy M. Caceres Guerra wrote: Hello! Hi! I'm new here, but I would like to be part of this group, I have a little knowledge of Java and I think I can be helpful for the group's goals. That would be very helpful considering the states of java (packages) in Fedora! I'

Re: Re-Launching the Java SIG

2021-09-15 Thread Peter Boy
> Am 13.09.2021 um 15:41 schrieb Jhordy M. Caceres Guerra > : > > Hello! > > I'm new here, but I would like to be part of this group, I have a little > knowledge of Java and I think I can be helpful for the group's goals. > > Note: I know this thread is old, but I didn't know how to join thi

Re: Re-Launching the Java SIG

2021-09-13 Thread Jhordy M. Caceres Guerra
Hello! I'm new here, but I would like to be part of this group, I have a little knowledge of Java and I think I can be helpful for the group's goals. Note: I know this thread is old, but I didn't know how to join this group, because this group has no sponsors. __

Re: (Re)orphaning jakarta-commons-httpclient

2021-08-25 Thread Orion Poplawski
On 8/20/21 12:09 PM, Jerry James wrote: I picked up jakarta-commons-httpclient in an attempt to keep ant-contrib building. That proved impossible, so I removed all dependencies on ant-contrib from packages I maintain instead. That means I don't need jakarta-commons-httpclient, so I am orphaning

Re: (Re)orphaning jakarta-commons-httpclient

2021-08-22 Thread Mat Booth
On Fri, 20 Aug 2021 at 19:10, Jerry James wrote: > > I picked up jakarta-commons-httpclient in an attempt to keep > ant-contrib building. That proved impossible, so I removed all > dependencies on ant-contrib from packages I maintain instead. That > means I don't need jakarta-commons-httpclient,

Re: Re-launch of the OCaml devel list

2021-04-16 Thread Jerry James
On Fri, Apr 16, 2021 at 1:39 AM Richard W.M. Jones wrote: > I'm getting emails saying I need to visit: > > https://lists.fedoraproject.org/admin/lists/ocaml-devel.lists.fedoraproject.org/held_messages > > to approve messages, but when I go there (after logging in) I only see: > > 403 Forbidden Th

Re: Re-launch of the OCaml devel list

2021-04-16 Thread Richard W.M. Jones
On Thu, Apr 15, 2021 at 10:27:58PM +0200, Dan Čermák wrote: > Dear OCaml devs & packagers, > > thanks to the work of smoodge and the infra team, I am proud to announce > the resurrection of the ocaml-devel list! > > It should be now available again for subscription in hyperkitty [1] I'm getting

Re: Re-launch of the OCaml devel list

2021-04-15 Thread Michel Alexandre Salim
Huzzah! On Thu, 2021-04-15 at 22:27 +0200, Dan Čermák wrote: > Dear OCaml devs & packagers, > > thanks to the work of smoodge and the infra team, I am proud to > announce > the resurrection of the ocaml-devel list! > > It should be now available again for subscription in hyperkitty [1] > Thanks

Re: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

2020-06-05 Thread Jeff Law
On Fri, 2020-06-05 at 07:33 +, devel-requ...@lists.fedoraproject.org wrote: > -- > > Date: Fri, 5 Jun 2020 09:16:21 +0200 > From: Frantisek Zatloukal > Subject: Re: Fedora 33 System-Wide Change proposal: CompilerPolicy >

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

2020-05-19 Thread Fabio Valentini
On Tue, May 19, 2020 at 11:19 AM Ankur Sinha wrote: > > On Tue, May 19, 2020 10:44:05 +0200, Fabio Valentini wrote: > > > > > > Good Morning! > > > > We were planning to discuss this from the Stewardship SIG point of > > view during today's meeting, and I didn't want to announce any plans > > bef

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

2020-05-19 Thread Ankur Sinha
On Tue, May 19, 2020 10:44:05 +0200, Fabio Valentini wrote: > > > Good Morning! > > We were planning to discuss this from the Stewardship SIG point of > view during today's meeting, and I didn't want to announce any plans > before that. > > However, my suggestion would be to do the following th

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

2020-05-19 Thread Fabio Valentini
On Tue, May 19, 2020 at 10:13 AM Ankur Sinha wrote: > > On Tue, May 12, 2020 18:45:12 +0200, Fabio Valentini wrote: > > 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 th

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

2020-05-19 Thread Ankur Sinha
On Tue, May 12, 2020 18:45:12 +0200, Fabio Valentini wrote: > 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 c

Re: Re-Launching the Java SIG

2020-05-18 Thread Samuel Sieb
On 5/18/20 5:54 PM, Ty Young wrote: I'm not advocating for in-kernel drivers. AMD with their drivers has proven proven what a bad idea that is. I, for the most part, like where I'm at and the way Nvidia does things. If I'm against it, I don't see why I would be the one to do it. This comment

Re: Re-Launching the Java SIG

2020-05-18 Thread Solomon Peachy
On Mon, May 18, 2020 at 07:54:42PM -0500, Ty Young wrote: > Surely it is the responsibility of those who want such a change to > make sure that everything that existed before can continue to exist? I > realize this requires that such arguments are being made in good faith > and consider the pers

Re: Re-Launching the Java SIG

2020-05-18 Thread Neal Gompa
On Mon, May 18, 2020 at 10:18 PM Ty Young wrote: > > > On 5/18/20 8:24 PM, Michael Catanzaro wrote: > > > > Dude, chill out. We're not going to go back to running X as root. The > > Nvidia overclocking tool is just not important at all (seriously, who > > cares?). If you're upset their proprietary

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 8:24 PM, Michael Catanzaro wrote: Dude, chill out. We're not going to go back to running X as root. The Nvidia overclocking tool is just not important at all (seriously, who cares?). If you're upset their proprietary software doesn't work anymore, you can ask them nicely to fix it

Re: Re-Launching the Java SIG

2020-05-18 Thread John M. Harris Jr
On Monday, May 18, 2020 4:03:16 PM MST Ty Young wrote: > On 5/18/20 2:51 PM, Samuel Sieb wrote: > > > On 5/18/20 7:27 AM, Ty Young wrote: > > > >> The application was an Nvidia GPU overclocking utility written in > >> Java. When Fedora decided to disable running X. Org as root, it > >> resulted

Re: Re-Launching the Java SIG

2020-05-18 Thread Michael Catanzaro
On Mon, May 18, 2020 at 8:24 pm, Michael Catanzaro wrote: Dude, chill out. We're not going to go back to running X as root. Ugh, I just noticed the subject of this thread is Java SIG. Amazing how thoroughly this conversation has been derailed

Re: Re-Launching the Java SIG

2020-05-18 Thread Michael Catanzaro
Dude, chill out. We're not going to go back to running X as root. The Nvidia overclocking tool is just not important at all (seriously, who cares?). If you're upset their proprietary software doesn't work anymore, you can ask them nicely to fix it please... or ask for the source code, and see

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 7:08 PM, Solomon Peachy wrote: On Mon, May 18, 2020 at 06:03:16PM -0500, Ty Young wrote: Willing to bet you or anyone else here won't. FYI, this applies to you as well. You just proved my point: >If it was Open Source and we were having this discussion, people like yourself wo

Re: Re-Launching the Java SIG

2020-05-18 Thread Gerald Henriksen
On Mon, 18 May 2020 18:03:16 -0500, you wrote: >X. Org as root is **STILL** the standard and Fedora broke it. This is >why no one wants to support Linux: you constantly break your own >platform and then cry wolf when people who don't care about your >ideological nonsense refuse to fix their sof

Re: Re-Launching the Java SIG

2020-05-18 Thread Solomon Peachy
On Mon, May 18, 2020 at 06:03:16PM -0500, Ty Young wrote: > Willing to bet you or anyone else here won't. FYI, this applies to you as well. - Solomon -- Solomon Peachypizza at shaftnet dot org (email&xmpp) @pizza:shaftnet dot org (

Re: Re-Launching the Java SIG

2020-05-18 Thread Nico Kadel-Garcia
On Mon, May 18, 2020 at 9:34 AM Ty Young wrote: > The "toolchain" isn't broken, other than Gradle developers not caring > about backwards compatibility but... It works for them, just as A toolchain with broken links scattered through it is not toolchain. Building up the .jar files as a hierarchy

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 2:51 PM, Samuel Sieb wrote: On 5/18/20 7:27 AM, Ty Young wrote: The application was an Nvidia GPU overclocking utility written in Java. When Fedora decided to disable running X. Org as root, it resulted in the application no longer being able to adjust GPU/Memory clocks, among poss

Re: Re-Launching the Java SIG

2020-05-18 Thread Samuel Sieb
On 5/18/20 7:27 AM, Ty Young wrote: The application was an Nvidia GPU overclocking utility written in Java. When Fedora decided to disable running X. Org as root, it resulted in the application no longer being able to adjust GPU/Memory clocks, among possible other things. The software worked pe

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 9:14 AM, Fabio Valentini wrote: On Mon, May 18, 2020 at 3:34 PM Ty Young wrote: On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote: My software didn't magically break just for Fedora because of some bug in my software. It broke because Fedora decided they wanted to do something nea

Re: Re-Launching the Java SIG

2020-05-18 Thread Fabio Valentini
On Mon, May 18, 2020 at 3:34 PM Ty Young wrote: > On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote: > My software didn't magically break just for Fedora because of some bug > in my software. It broke because Fedora decided they wanted to do > something nearly no Linux distro does... something t

Re: Re-Launching the Java SIG

2020-05-18 Thread Nicolas Mailhot via devel
Le lundi 18 mai 2020 à 08:34 -0500, Ty Young a écrit : > > The "toolchain" isn't broken, other than Gradle developers not > caring about backwards compatibility but... It works for them, just > as constantly breaking internal kernel APIs works for the Linux > kernel The difference, is that you c

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 8:34 AM, Ty Young wrote: ...and there are plenty of Open Source projects that don't have packages yet people contribute to them. This isn't the early 2000 when barely anyone has internet and sites like Github didn't exist. Sure, a distro package increases visibility still, but it

Re: Re-Launching the Java SIG

2020-05-18 Thread Ty Young
On 5/18/20 7:35 AM, Nicolas Mailhot via devel wrote: Le lundi 18 mai 2020 à 14:12 +0200, Michal Srb a écrit : Hello, On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel < devel@lists.fedoraproject.org> wrote: Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit : On Fri, 15 M

Re: Re-Launching the Java SIG

2020-05-18 Thread Nicolas Mailhot via devel
Le lundi 18 mai 2020 à 14:12 +0200, Michal Srb a écrit : > Hello, > > On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel < > devel@lists.fedoraproject.org> wrote: > > Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit : > > > On Fri, 15 May 2020 08:02:34 +0200 > > > Michal Srb

Re: Re-Launching the Java SIG

2020-05-18 Thread Michal Srb
Hello, On Sat, May 16, 2020 at 11:24 AM Nicolas Mailhot via devel < devel@lists.fedoraproject.org> wrote: > Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit : > > On Fri, 15 May 2020 08:02:34 +0200 > > Michal Srb wrote: > > > > An aside, just to clarify for myself. That means that

Re: Re-Launching the Java SIG

2020-05-16 Thread stan via devel
On Sat, 16 May 2020 11:23:03 +0200 Nicolas Mailhot wrote: > Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit : > > On Fri, 15 May 2020 08:02:34 +0200 > > Michal Srb wrote: > > > > An aside, just to clarify for myself. That means that all Java apps > > are > > the equivalent of sta

Re: Re-Launching the Java SIG

2020-05-16 Thread Nicolas Mailhot via devel
Le vendredi 15 mai 2020 à 08:30 -0700, stan via devel a écrit : > On Fri, 15 May 2020 08:02:34 +0200 > Michal Srb wrote: > > An aside, just to clarify for myself. That means that all Java apps > are > the equivalent of statically linked, right? And are related to > things > like flatpaks and mo

Re: Re-Launching the Java SIG

2020-05-15 Thread Gerald Henriksen
On Thu, 14 May 2020 06:33:47 -0500, you wrote: >* Game developers largely refuse to support Linux, and the some of the >few that have have or are currently pulling support citing >fragmentation(support) issues. Game developers refuse to support Linux because there is no userbase - even Steam, w

Re: Re-Launching the Java SIG

2020-05-15 Thread Gerald Henriksen
On Thu, 14 May 2020 06:59:47 -0500, you wrote: >What i'm saying is: Distros like Fedora actively hurt the very people >who are directly or indirectly helping them. There are single-person run >projects, like mine, out there that can't possibly do all the work >needed to have a dozen packages fo

Re: Re-Launching the Java SIG

2020-05-15 Thread stan via devel
On Fri, 15 May 2020 08:02:34 +0200 Michal Srb wrote: > > I realize that this is technically possible to achieve, but that is > > not how people use it. If you want to distribute your Java app, you > > just bundle it with all its dependencies into a beefy tarball and > > ship it. And if Java apps

Re: Re-Launching the Java SIG

2020-05-14 Thread Michal Srb
On Thu, May 14, 2020 at 2:42 PM Vít Ondruch wrote: > > Dne 14. 05. 20 v 11:53 Michal Srb napsal(a): > > Hello, > > On Tue, May 12, 2020 at 12:57 PM 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 >

Re: Why distributions package software (was: Re: Re-Launching the Java SIG)

2020-05-14 Thread Jerry James
On Thu, May 14, 2020 at 6:38 AM Igor Raits wrote: > On Thu, 2020-05-14 at 06:33 -0500, Ty Young wrote: > > Nonsense spewing with no proof. > > Well, you have started this. Can you provide some statistics how many > bugs were introduced by distributions versus upstream bugs. My experience has been

Re: Re-Launching the Java SIG

2020-05-14 Thread Mamoru TASAKA
Well, as just I saw "xscreensaver" word here: Ty Young wrote on 2020/05/14 20:33: On 5/13/20 4:58 PM, Solomon Peachy wrote: On Wed, May 13, 2020 at 04:04:50PM -0500, Ty Young wrote: Anyway, I'm just asking that Fedora not repeat what Debian did. While I find it to be a bit paranoid, I underst

Re: Re-Launching the Java SIG

2020-05-14 Thread Vít Ondruch
Dne 14. 05. 20 v 11:53 Michal Srb napsal(a): > Hello, > > On Tue, May 12, 2020 at 12:57 PM Felix Schwarz > mailto:fschw...@fedoraproject.org>> 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 > > sho

Why distributions package software (was: Re: Re-Launching the Java SIG)

2020-05-14 Thread Igor Raits
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I wanted to avoid replying to this thread, but this message forced me to do so since it is spreading misinformation. On Thu, 2020-05-14 at 06:33 -0500, Ty Young wrote: > On 5/13/20 4:58 PM, Solomon Peachy wrote: > > On Wed, May 13, 2020 at 04:0

Re: Re-Launching the Java SIG

2020-05-14 Thread Ty Young
On 5/14/20 6:42 AM, Solomon Peachy wrote: On Thu, May 14, 2020 at 06:33:47AM -0500, Ty Young wrote: Whichever you choose. Large projects like Gnome and Fedora refer to themselves as one large organization one minute and then as individuals the next. It reminds me of how everyone says "Linux" is

Re: Re-Launching the Java SIG

2020-05-14 Thread Nicolas Mailhot via devel
Le jeudi 14 mai 2020 à 06:33 -0500, Ty Young a écrit : > > I could literally go on and on. The "my-shit-don't-stink" attitude is > so terrible it's borderline sad. And years of terminally broken build practices Java-side have finally resulted in complete capture of all the Java big data code the

Re: Re-Launching the Java SIG

2020-05-14 Thread Solomon Peachy
On Thu, May 14, 2020 at 06:33:47AM -0500, Ty Young wrote: > Whichever you choose. Large projects like Gnome and Fedora refer to > themselves as one large organization one minute and then as individuals the > next. It reminds me of how everyone says "Linux" is less resource hungry > then Windows but

Re: Re-Launching the Java SIG

2020-05-14 Thread Ty Young
On 5/13/20 4:58 PM, Solomon Peachy wrote: On Wed, May 13, 2020 at 04:04:50PM -0500, Ty Young wrote: Anyway, I'm just asking that Fedora not repeat what Debian did. While I find it to be a bit paranoid, I understand the concerns regarding someone sneaking in malware into pre-build binaries. I'm

Re: Re-Launching the Java SIG

2020-05-14 Thread Nicolas Mailhot via devel
Le jeudi 14 mai 2020 à 11:53 +0200, Michal Srb a écrit : > > Since there is no standard place for shared Java libraries on your > laptop, Of course there is one /usr/share/java, which has been defined and used by Linux distributions since jpackage times (circa ~2000). Java is not special from a

Re: Re-Launching the Java SIG

2020-05-14 Thread Ty Young
On 5/14/20 4:53 AM, Michal Srb wrote: Hello, On Tue, May 12, 2020 at 12:57 PM Felix Schwarz mailto:fschw...@fedoraproject.org>> 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 c

Re: Re-Launching the Java SIG

2020-05-14 Thread Aleksandar Kurtakov
On Thu, May 14, 2020 at 12:55 PM Michal Srb wrote: > Hello, > > On Tue, May 12, 2020 at 12:57 PM 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 f

Re: Re-Launching the Java SIG

2020-05-14 Thread Michal Srb
Hello, On Tue, May 12, 2020 at 12:57 PM 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 whol

Re: Re-Launching the Java SIG

2020-05-13 Thread Fabio Valentini
On Tue, May 12, 2020 at 10:59 PM Ty Young 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. I find it kind of ironic that this is exactly what happened, but you seem not to be aw

Re: Re-Launching the Java SIG

2020-05-13 Thread Fabio Valentini
On Wed, May 13, 2020 at 10:38 PM Jerry James wrote: > > On Mon, May 11, 2020 at 1:46 PM Fabio Valentini wrote: > > So, if you're interested, please consider joining this group effort. > > I'll get new members set up with the FAS group / pagure project / mailing > > list. > > Like some others who

Re: Re-Launching the Java SIG

2020-05-13 Thread Ty Young
On 5/13/20 4:16 PM, James Cassell wrote: On Wed, May 13, 2020, at 5:04 PM, Ty Young wrote: On 5/13/20 12:04 PM, Robbie Harwood wrote: Ty Young writes: 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

Re: Re-Launching the Java SIG

2020-05-13 Thread Solomon Peachy
On Wed, May 13, 2020 at 04:04:50PM -0500, Ty Young wrote: > Anyway, I'm just asking that Fedora not repeat what Debian did. While > I find it to be a bit paranoid, I understand the concerns regarding > someone sneaking in malware into pre-build binaries. I'm just asking > Fedora not package the

Re: Re-Launching the Java SIG

2020-05-13 Thread James Cassell
On Wed, May 13, 2020, at 5:04 PM, Ty Young wrote: > > On 5/13/20 12:04 PM, Robbie Harwood wrote: > > Ty Young writes: > > > >> 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 >

Re: Re-Launching the Java SIG

2020-05-13 Thread Ty Young
On 5/13/20 12:04 PM, Robbie Harwood wrote: Ty Young writes: 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

Re: Re-Launching the Java SIG

2020-05-13 Thread Jerry James
On Mon, May 11, 2020 at 1:46 PM Fabio Valentini wrote: > So, if you're interested, please consider joining this group effort. > I'll get new members set up with the FAS group / pagure project / mailing > list. Like some others who have responded, I probably won't be much help due to lack of time

Re: Re-Launching the Java SIG

2020-05-13 Thread Robbie Harwood
Ty Young writes: > 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

Re: Re-Launching the Java SIG

2020-05-13 Thread Christopher Engelhard
On 13.05.20 14:55, Solomon Peachy wrote: > On Tue, May 12, 2020 at 10:57:43PM -0400, Gerald Henriksen wrote: >> The only way to make sure that the stuff included with Fedora is open >> source is to build it from source - simply grabbing a binary provided >> by an upstream means upstream could slip

Re: Re-Launching the Java SIG

2020-05-13 Thread Solomon Peachy
On Tue, May 12, 2020 at 10:57:43PM -0400, Gerald Henriksen wrote: > The only way to make sure that the stuff included with Fedora is open > source is to build it from source - simply grabbing a binary provided > by an upstream means upstream could slip in some closed source > portions or have such

Re: Re-Launching the Java SIG

2020-05-13 Thread Kevin Kofler
Gerald Henriksen wrote: > The only way to make sure that the stuff included with Fedora is open > source is to build it from source - simply grabbing a binary provided > by an upstream means upstream could slip in some closed source > portions or have such a complex and undocumented build system th

Re: Re-Launching the Java SIG

2020-05-12 Thread Gerald Henriksen
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

Re: Re-Launching the Java SIG

2020-05-12 Thread Philip Rhoades
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

Re: Re-Launching the Java SIG

2020-05-12 Thread Ty Young
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: Re-Launching the Java SIG

2020-05-12 Thread John W. Himpel
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

  1   2   3   4   >