[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

            Bug ID: 243470
           Summary: devel/mono-addins: deprecate and expire in 90 days
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: [hidden email]
          Reporter: [hidden email]
             Flags: maintainer-feedback?([hidden email])
          Assignee: [hidden email]

Created attachment 210897
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=210897&action=edit
deprecate and expire

After checking with upstream, it has been determined that mono-addins has been
deprecated upstream and will no longer be maintained going forward.

I set the expiry to 90 days as there is one maintained port which added a new
dependency on this on December 19, graphics/pinta. (Will be opening a separate
bug for graphics/pinta.)

This is part of the mono cleanup effort to bring in Mono 6.8+.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

maintainer-feedback requested: [Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
Bugzilla Automation <[hidden email]> has asked freebsd-mono mailing list
<[hidden email]> for maintainer-feedback:
Bug 243470: devel/mono-addins: deprecate and expire in 90 days
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470



--- Description ---
After checking with upstream, it has been determined that mono-addins has been
deprecated upstream and will no longer be maintained going forward.

I set the expiry to 90 days as there is one maintained port which added a new
dependency on this on December 19, graphics/pinta. (Will be opening a separate
bug for graphics/pinta.)

This is part of the mono cleanup effort to bring in Mono 6.8+.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

OlivierW <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olivierw1+bugzilla-freebsd@
                   |                            |hotmail.com

--- Comment #1 from OlivierW <[hidden email]> ---
I have been told mono-addins isn't deprecated, there is just no active feature
development ATM.

Best Regards,
Olivier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

Kubilay Kocak <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.freebsd.org/bu
                   |                            |gzilla/show_bug.cgi?id=2434
                   |                            |71
             Status|New                         |Open
           Keywords|                            |needs-qa

--- Comment #2 from Kubilay Kocak <[hidden email]> ---
Excerpt from bug 243471 comment 6 to clarify comment 1 here:

mono-addins is receiving commits @ GitHub (Latest Nov 22, 2019):
https://github.com/mono/mono-addins/commits

Conversation [1] with Marius Ungureanu (therzok, committer and Senior Software
Engineer @microsoft) on Twitter:

"Hey, mono-addins is not deprecated, it's still largely used in MonoDevelop.
There's no active feature development on it right now, but that's a different
story"

Can you describe the nature if any, of mono-addins preventing or precluding
lang/mono update?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

--- Comment #3 from Kubilay Kocak <[hidden email]> ---
(In reply to Kubilay Kocak from comment #2)

Forgot to include the twitter conversation reference [1]:
https://twitter.com/Therzok/status/1219439705042956288

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

--- Comment #4 from Phillip R. Jaenke <[hidden email]> ---
Interesting! I talked with Alexander Koeplinger (runtime team) on Gitter about
it, so it probably is just a miscommunication between teams there. Mono
internally is a VERY large project.

However, a quick swing through shows that the version in ports does NOT compile
with newer Mono. Which isn't entirely unexpected, as it's a 4 year old release
tarball.

/usr/local/bin/mcs -out:WidgetViewer.exe -r:../../glib/glib-sharp.dll
-r:../../pango/pango-sharp.dll -r:../../atk/atk-sharp.dll
-r:../../gdk/gdk-sharp.dll -r:../../gtk/gtk-sharp.dll ./TestCheckButton.cs
./TestColorSelection.cs ./TestRadioButton.cs ./TestRange.cs ./TestStatusbar.cs
./TestDialog.cs ./TestFlipping.cs ./TestSizeGroup.cs ./TestCombo.cs
./TestComboBox.cs ./WidgetViewer.cs
./TestCombo.cs(17,14): warning CS0612: `Gtk.Combo' is obsolete
./TestRange.cs(35,6): error CS0104: `Range' is an ambiguous reference between
`System.Range' and `Gtk.Range'
/usr/local/lib/mono/4.5/mscorlib.dll (Location of the symbol related to
previous error)
./TestRange.cs(35,13): error CS0030: Cannot convert type `Gtk.HScale' to
`System.Range'
./TestRange.cs(42,6): error CS0104: `Range' is an ambiguous reference between
`System.Range' and `Gtk.Range'
/usr/local/lib/mono/4.5/mscorlib.dll (Location of the symbol related to
previous error)
./TestRange.cs(42,13): error CS0030: Cannot convert type `Gtk.HScrollbar' to
`System.Range'
./TestRange.cs(62,6): error CS0104: `Range' is an ambiguous reference between
`System.Range' and `Gtk.Range'
/usr/local/lib/mono/4.5/mscorlib.dll (Location of the symbol related to
previous error)
./TestRange.cs(62,13): error CS0030: Cannot convert type `Gtk.VScale' to
`System.Range'
./TestCombo.cs(31,20): warning CS0612: `Gtk.Combo' is obsolete
Compilation failed: 6 error(s), 2 warnings

So there's definitely some major cleanup and overhaul needed here. Item one is
probably switching to actually fetching from a GH commit instead of a 4 year
old pseudo-release. There's probably over a thousand bug fix commits between
the release tarball and current commit. Or having upstream do a new release
tarball; either way works.
I've got no problem switching that out and updating the port correspondingly
there. (Just probably won't be able to get to it today.)

However: issue two, this depends on gtk-sharp20, which is another orphan in
need of serious updating. (Or optionally gtk-sharp30, same deal.) I don't know
anywhere near enough about the Gnome infrastructure to know what the correct
answer here is or how the gtk-sharp pieces would impact other gtk pieces at
this point. Is there anyone from gnome@ who would be able to lend me a hand
here?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

[Bug 243470] devel/mono-addins: deprecate and expire in 90 days

bugzilla-noreply
In reply to this post by bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243470

Kubilay Kocak <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needs-qa                    |
                 CC|                            |[hidden email]
           Assignee|[hidden email]            |[hidden email]
             Status|Open                        |Closed
         Resolution|---                         |Not Accepted

--- Comment #5 from Kubilay Kocak <[hidden email]> ---
^Triage: Per bug 243471 comment 6, mono-addins isn't deprecated and the
proposal 'as reported' is not accepted

It appears (per comment 4) that mono-addins needs work, updating &
improvements, and the mono@ team would appreciate any contributions (created in
separate issues) in that regard.

Where there are any other dependencies/other ports that need to be changed,
improved fixed in order to support a better/up-to-date mono-addins port, please
create separate and dependent (Depends On, Blocks fields) issues for those
specific ports and maintainers/teams (gnome, etc) so those can be addressed
independently but in a trackable way

Thank you for your report Phillip.

--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-mono
To unsubscribe, send any mail to "[hidden email]"