[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-05-01 Thread Colomban Wendling via Github-comments
Closed #1340. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#event-12673653995 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-05-01 Thread Colomban Wendling via Github-comments
Yeah I agree, better stick with libsoup then, although relying on an existing component was an interesting idea. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2088925494 You are receiving this because you are subscribed to

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-05-01 Thread Jiří Techet via Github-comments
Regarding macOS, the way gio behaves I expect it will never work so better to use libsoup (2 or 3, both are provided by gtk-osx). I can try again if I manage to get tls work with libsoup - to be honest, I didn't try too hard last time because I don't use neither of the plugins. -- Reply to

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-05-01 Thread Enrico Tröger via Github-comments
> So it probably works provided one uses an up to date operating system. If > anyone has access to a Windows 10/11 system, the artifacts of the CI build > https://github.com/geany/geany-plugins/actions/runs/8850165013 contain the > Geany and G-P installers for easy testing. I was about to ask

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Jiří Techet via Github-comments
> To confirm, the first is Windows? The second macOS? Both with GIO? Only speaking for the macOS part - yes, the second message is on macOS with GIO. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2081536322 You are receiving

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread xiota via Github-comments
> `GET request failed: WinHttp error: SECURE_CHANNEL_ERROR` > > `Unable to perform version check: Operation not supported` To confirm, the first is Windows? The second macOS? Both with GIO? -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Jiří Techet via Github-comments
So I get ``` 17:47:11.712578: Updatechecker MESSAGE : Checking for updates (querying URL "https://geany.org/service/version/;) 17:47:14.085164: Updatechecker WARNING : Unable to perform version check: Operation not supported ``` in debug messages and also the corresponding popup error :-(. --

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Jiří Techet via Github-comments
> What do you mean, with GIO, with libsoup, with anything? If it doesn't work > neither on macos not Windows, it starts to feel like nobody is gonna be using > it  Yeah, it was with libsoup which, when using gtk-osx for building dependencies, depends on gnutls:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread elextr via Github-comments
@techee you don't want to be shipping TLS, that should be using a system library, the last thing you need is to be constantly updating as CVEs are fixed against it. If it doesn't use a system library then it shouldn't be available. > nobody is gonna be using it  Its wrong on Linux, doesn't

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Enrico Tröger via Github-comments
> > I "think" it will work. > > In detail this is, when querying https://geany.org/ I get an error: `GET > > request failed: WinHttp error: SECURE_CHANNEL_ERROR`. […] > > If I change the URL to query to https://httpbin.org/anything/version, the > > HTTP request works fine and I get the expected

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Colomban Wendling via Github-comments
> I "think" it will work. > In detail this is, when querying https://geany.org/ I get an error: `GET > request failed: WinHttp error: SECURE_CHANNEL_ERROR`. […] > > If I change the URL to query to https://httpbin.org/anything/version, the > HTTP request works fine and I get the expected

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Enrico Tröger via Github-comments
> Guys, be a bit patient :D. I'll test this on Windows/MSYS2 later or in the > next days. I "think" it will work. In detail this is, when querying https://geany.org I get an error: `GET request failed: WinHttp error: SECURE_CHANNEL_ERROR`. But I guess this is not related to the changes but

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Jiří Techet via Github-comments
> @techee any chance you could check whether gvfs works with HTTP(S) under > macos? The thing is that I didn't even manage to get tls running correctly (it compiled but https didn't work afterwards, probably some configuration issue) so the updatechecker plugin isn't part of the macOS release.

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread elextr via Github-comments
> you never know what the future of the web holds Yeah, its just a fad :grin: > A new feature maybe, but well. But the G* guys would never break API without a new major version Anyway as you say, there are prototypes for all four plugins available, so if we are not gonna kill any off

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-28 Thread Colomban Wendling via Github-comments
@elextr you never know what the future of the web holds, but I highly doubt a security issue would ruin the current API. A new feature maybe, but well. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2081379570 You are

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread elextr via Github-comments
@b4n: > Yet, does it currently matter? Well if you are willing to maintain them in sync its fine. But who knows if a security alert will require them to change libsoup3.1 API, its a web library after all! @xiota: > You're too far ahead. Takes a while to catch up. Just around longer, but

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread Colomban Wendling via Github-comments
> Yeah, but then its back to four plugins to synchronise on > libsoup3/webkit2gtk-4.1. Yet, does it currently matter? I mean, the code is ready (but for more testing maybe) for all four now, porting isn't what is holding back anymore. Sure the question might arise again for a future libsoup4

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread xiota via Github-comments
> has again pointed out the point I made a while back about this I realized later that you'd already said it. You're too far ahead. Takes a while to catch up. > four plugins to synchronise This number could be reduced... -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread elextr via Github-comments
> just keep using the libsoup implementation Yeah, but then its back to four plugins to synchronise on libsoup3/webkit2gtk-4.1. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2080645295 You are receiving this because you

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread Colomban Wendling via Github-comments
@elextr hence checking if it does :) But if it's a concern, just keep using the libsoup implementation, it *ought* to work with HTTP as that's the whole point of that library :smiley: -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread elextr via Github-comments
@xiota: > (win/mac – the platforms most likely to need update checkers). has again pointed out the point I made a while back about this, its useful for Windows and Macos, but for Linux it lies, just because the project releases a new Geany does not put it in the distro they are using. And for

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-27 Thread Colomban Wendling via Github-comments
@techee any chance you could check whether gvfs works with HTTP(S) under macos? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2080478237 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-26 Thread Colomban Wendling via Github-comments
@xiota I don't think we need to explore a *different* additional HTTP library; either we only use what's already part of the general GTK stack, or using libsoup which is also a direct or indirect dependency of 3 other plugins is fine. -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-26 Thread Enrico Tröger via Github-comments
Guys, be a bit patient :D. I'll test this on Windows/MSYS2 later or in the next days. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2079741003 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany-plugins] updatechecker: Port to GIO and small other fixes (PR #1340)

2024-04-26 Thread xiota via Github-comments
I think a problem with gio method is depends on gvfs (gnome) and not available on msys2 and brew (win/mac). Wondering now about libcurl vs libsoup. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1340#issuecomment-2079619971 You are receiving