Re: FreeCAD required updates (PySide2 & Coin4)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2019-10-08 at 10:07 -0500, Richard Shaw wrote:
> On Tue, Oct 8, 2019 at 1:35 AM Ralf Corsepius <rc040203@xxxxxxxxxx> wrote:
> 
> > On 10/8/19 8:03 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Mon, Oct 07, 2019 at 04:34:28PM -0400, Scott Talbert wrote:
> > > > On Mon, 7 Oct 2019, Richard Shaw wrote:
> > > > 
> > > > > I am in the midst of updating the freecad package in two major ways:
> > > > > Qt4 -> Qt5 (via PySide -> PySide2, which also facilitates moving from
> > 
> > Python
> > > > > 2 to 3)
> > > > > and
> > > > > Coin3 -> Coin4 (Which requires several other packages move to Coin4)
> > > > > 
> > > > > I have been working with the Coin2/3, SoQt, & SIMVoleon maintainer
> > 
> > Ralf but
> > > > > I stopped getting responses. The last response by email being September
> > > > > 13th.
> > > > > 
> > > > > I have even submitted pull requests so my requested changes can be
> > 
> > easily
> > > > > evaluated.
> > > > > 
> > > > > https://src.fedoraproject.org/rpms/SoQt/pull-request/2
> > > > > https://src.fedoraproject.org/rpms/OpenSceneGraph/pull-request/2
> > > > > https://src.fedoraproject.org/rpms/SIMVoleon/pull-request/1
> > > > > 
> > > > > Updating to Coin4 is required to take care of a longstanding bug[1]
> > > > > 
> > > > > So I'm trying to be nice but I don't think it's doing any good to wait
> > 
> > for a
> > > > > reply that may never come meanwhile the users could easily get the
> > 
> > idea that
> > > > > I (or Fedora) don't care about fixing bugs.
> > > 
> > > Those are fairly substantial changes, but time is of essence here.
> > 
> > I could not disagree more. Quality and stability is of more essence, here.
> > 
> 
> Very few of us (packagers) are computer scientists or the like or paid like
> RHEL to evaluate every possible problem that could arise with adopting new
> releases of software. Nor can we all be expected to backport fixes in every
> case. If you want that, run RHEL/CentOS instead. In the case of Coin4 is
> addresses a REAL issue with FreeCAD and Coin3. I built test packages of the
> whole stack and even went so far as to create a COPR to test the result and
> moving to Coin4 does indeed fix the problem with importing SVG images as
> geometry.
> 
> So what do you suggest I do instead? Fedora tends to run the latest
> versions of packages on purpose.
> 
> 
> > I reviewed all three PRs, and they look fine. (One needs a rebase).
> > > I think you should just push and build all packages.
> > 
> > You don't want to know what I think of this.
> > 
> 
> I knew you probably wouldn't like the changes which is why I bent over
> backwards to be nice about it including submitting pull requests and
> communicating with you over email.
> 
> I even implemented the alternatives for Coin4 that you have on Coin2/3 just
> so they would be compatible instead of just conflicting with Coin2 (which
> is a leaf package in Fedora and Coin3 which will be a leaf package after
> moving the dependencies over).
> 
> I appreciate all the work you did maintaining the Coin3D stack over the
> years in Fedora but at the end of the day we are package maintainers not
> owners, a clarification that was referenced a few years ago.
> 
> Unfortunately I had to resort to posting here on the mailing list to
> provoke a response because 3 emails and almost a month later you couldn't
> even reply just to say "I'm really busy but I will review your changes."
> 
> So again I ask, what was I supposed to do? Ignore a REAL issue because you
> don't like people touching your packages? Wait indefinitely?
> 
> How long would you wait if you were in my position? What should I have done
> differently?
> 
> FreeCAD has been in a terrible state in Fedora for years and after a crap
> ton of work with getting PySIde2 into Fedora, updating the Coin stack I
> would like to be able to ship FUNCTIONAL packages.
> 
> Thanks,
> Richard

Richard I use FreeCAD in Fedora and I want to tahnk you for your work,
it is really appreciated, I think you did the right thing given the
circumstances.

If a maintainer wants to have a say, they have to do the work, or be
completely responsive at least, otherwise they need to let go and let
the ones that care do the work have their way.

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc



_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux