Re: wxWidgets GTK+ 3 build available
On Sun, Nov 25, 2018 at 03:26:36PM +, Simon McVittie wrote:
> On Sat, 24 Nov 2018 at 20:31:03 -0500, Scott Talbert wrote:
> > 2) If your package uses wxGLCanvas, it won't work under Wayland. This is
> > due to wxGLCanvas (currently) requiring X11 to function. This can be worked
> > around by forcing the GDK backend to X11. Here's one example of how this
> > has been done: [1]
>
> If there's already a wrapper shell script or something,
> setting GDK_BACKEND=x11 is OK; but I think the
> preferred way to force the use of X11 even in a Wayland
> environment is to make the C/C++/Python/etc. code call
> gdk_set_allowed_backends("x11"), available since GTK+ 3.10 (for example
> https://github.com/vim/vim/commit/f80663f17b2f2499b45eb4467088704c8298c385
> does this).
That's sensible for gvim since it's using the GTK+ and GDK libraries
directly.
However applications using wxWidgets don't usually link to the GDK
library directly, and so patching them to call
gdk_set_allowed_backends("x11") would need wider changes than using
setenv() does.
Patching wxWidgets itself to call gdk_set_allowed_backends("x11") seems
undesirable because we'd have to do it unconditionally because we can't
tell if wxGLCanvas will be used or not at the point where we need to set
it if it is. In other words, we'd have to force all wxWidgets-using
applications to use the x11 backend.
(There is a wxGLApp class which it might be possible to hook this up to,
but it's not covered in the wxWidgets API docs and so almost nothing
actually uses it).
> In particular please note that setenv() and g_setenv() are not safe
> to call from multi-threaded code[1] so any calls to [g_]setenv() must
> usually happen as early as possible in main(), before calling into
> libraries that might create another thread.
Applications using wxWidgets don't usually link to glib either, so
setenv() >> g_setenv() for this purpose.
You'd want to set this as early as possible anyway since it needs to
happen before any wxWidgets GUI initialisation happens.
Cheers,
Olly
Bug#906715: ITP: lloconv -- command line document converter using libreofficekit
Package: wnpp Severity: wishlist Owner: Olly Betts * Package name: lloconv Version : 6.1.0 Upstream Author : Olly Betts * URL : https://gitlab.com/ojwb/lloconv * License : MPL-2.0 Programming Lang: C++ Description : command line document converter using LibreOfficeKit A command line document format converter which uses LibreOffice (via its LibreOfficeKit API) to do all the hard work. It should support the same formats which LibreOffice does. LibreOfficeKit was formerly known as liblibreoffice, hence the name "lloconv".
Bug#734799: ITP: wxpython3.0 -- wxWidgets Cross-platform C++ GUI toolkit (wxPython binding)
Package: wnpp Severity: wishlist Owner: Olly Betts * Package name: wxpython3.0 Version : 3.0.0.0 Upstream Author : Robert Roebling et al * URL : http://wxpython.org/ * License : wxWindows Licence; wxWindows Free Documentation Licence, Version 3 Programming Lang: C++, Python Description : wxWidgets Cross-platform C++ GUI toolkit (wxPython binding) wxWidgets (formerly known as wxWindows) is a class library for C++ providing GUI components and other facilities on several popular platforms. This package provides a Python binding to the wxGTK library and the wxPython runtime support libraries. [To pre-answer the "isn't this already packaged" questions, we used to build wxpython out of the wxwidgets2.8 source package (which actually contained wxpython sources with an embedded copy of wxwidgets!) The wxwidgets3.0 source package is just the wxwidgets source, and we're packaging wxpython 3.0 from a separate source package.] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140109220943.19654.17524.reportbug@gemse.localnet
Re: wxwidgets 3.0
[A Cc on list replies would be appreciated.] On Wed, Nov 13, 2013 at 03:43:49PM +, Olly Betts wrote: > A few days ago wxwidgets 3.0.0 was officially released. I've already > uploaded a package of it aimed at unstable, which is currently in NEW. The package has cleared NEW (thanks paultag). > https://wiki.debian.org/Teams/WxWidgets/Transition2.8to3.0 There's now a table there (thanks to sre), plus a paste of the whodepends output for packages not yet in the table. If you're planning to take care of a particular package, or if you maintain a package but are happy for others to deal with it, please note it in the table. Cheers, Olly -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131114123701.ga7...@survex.com
wxwidgets 3.0
[A Cc on list replies would be appreciated.] A few days ago wxwidgets 3.0.0 was officially released. I've already uploaded a package of it aimed at unstable, which is currently in NEW. Meanwhile you can download source and amd64 binaries from here: http://survex.com/~olly/wx3-debs/ My hope is that we can remove wxwidgets2.8 before the jessie freeze by either migrating packages to use 3.0, or removing them from Debian (during the wx 2.6 to 2.8 transition, I noticed a number of packages which appeared to have no maintainer either upstream or in Debian - for any where that's still the case, I think removal should be seriously considered). I'll be at the mini-debcamp in Cambridge, UK at the end of this week (14th and 15th November) and plan to make a start checking packages with the new release. I'd welcome local and/or remote assistance. I'll track progress here: https://wiki.debian.org/Teams/WxWidgets/Transition2.8to3.0 Some important notes: * The wxwidgets2.8 source package was actually based on wxPython (which includes an embedded copy of the C++ wxWidgets library sources), but the wxwidgets3.0 source package is just the C++ library. There hasn't been an update of wxPython for 3.0 yet, and while I have managed to patch wxPython 2.9.5.0 to work, it turned out to be quite a complex change and at this point waiting for wxPython 3.0.0.0 and then packaging that as a separate source package seems better. (I've sent upstream my patches in case they're useful). * Upstream now enables their debug checks by default. One consequence of this is that in 2.8, the -dbg packages were a version built with these checks on, and debug info, but in 3.0, the -dbg packages are just detached debug symbols. The other is that code which misuses the wx API will now pop up warning dialogs, while previously the code would have quietly muddled through. Overall sorting out such issues is good, but these dialogs are intrusive for users. I suspect checking rebuilt packages and fixing such issues might be the biggest job in transitioning packages. * You should be able to co-install wx 2.8 and 3.0, so applications can switch independently of one another. The only wrinkle is that currently the -i18n packages attempt to install the same files - I need to look at how we handled that for 2.6 and 2.8. * The -doc package is temporarily gone in the 3.0 packages (upstream now release the docs as a separate download). Cheers, Olly -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131113154349.ga31...@survex.com
Re: Getting rid of wxwidgets2.6
At Paul Wise's suggestion, here is dd-list output for the packages affected by this change (excluding those whose maintainers have already responded). This list includes four packages I missed before - three because they build-depend on libwxgtk2.8-dev|libwxgtk2.6-dev (I only looked at run-time dependencies before and the buildds will always build these against 2.8), and xaralx which is non-free (I only looked at main before). Cheers, Olly Sylvain Beucler freedink-dfarc (U) Kęstutis Biliūnas opendict Joachim Breitner xaralx Carl Chenet pyro (U) Peter Collingbourne p9m4 Cameron Dale bittornado Debian Games Team freedink-dfarc jugglemaster londonlaw Debian Python Modules Team pyenchant (U) pyke pyro pyscard (U) python-avc (U) python-dsv Free Ekanayaka twisted (U) Luke Faraone chipw Helmut Grohne jugglemaster (U) Michael Janssen bittorrent Kaido Kert esteidutil Georges Khaznadar wxglade Bruno "Fuddl" Kleinert londonlaw (U) Matthias Klose pyserial twisted wxglade (U) Thomas Knott gtkwhiteboard Ana Beatriz Guerrero Lopez cycle Pierre Machard cryptonit Daniel Martin pyrite-publisher Ignace Mouzannar kiki Piotr Ożarowski pyenchant Fabrizio Pollastri python-avc Python Applications Packaging Team boa-constructor cycle (U) djvusmooth (U) p9m4 (U) pykaraoke Ludovic Rousseau pyscard Miriam Ruiz cycle (U) pykaraoke (U) Charlie Smotherman boa-constructor (U) Daniel Stender djvusmooth James Stone tunapie Daniele Tricoli pyke (U) Aaron M. Ucko python-dsv (U) Bernd Zeimetz pyro (U) Enrico Zini dballe Michal Čihař wammu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20111019t080146...@post.gmane.org
Re: Getting rid of wxwidgets2.6
I wrote: > Currently we have wxwidgets2.6 and wxwidgets2.8 in the archive. We've > had wxwidgets2.8 since lenny and it's now much more widely used than > 2.6 in the archive. Upstream 2.6 no longer really gets any attention > (the last release was in 2007), while 2.8 had a point release about 6 > months ago. > > So I believe it's time to migrate the remaining wxwidgets2.6-dependent > packages to wxwidgets2.8 and get rid of wxwidgets2.6. We've made good progress already with 6 packages fixed and uploaded and a couple more pending uploads. Thanks to everyone who's helped things along. I get the feeling this migration is pushing on an open door, and it's looking like it could realistically be done before the end of 2011. I'm going to have to be less active on this for a while, but we've reached the point where all the packages which need changing to be able remove wxwidgets2.6 now have a bug filed, so it's mostly a matter of waiting for these to get attention, then addressing what remains with NMUs. There are also 13 packages which will need to drop an alternative dependency on python-wxgtk2.6 at some point, but which don't have bugs filed yet. I'll file wishlist bugs for these if I get a chance, but please just go ahead and remove the alternative dependency on python-wxgtk2.6 next time you upload. If python-wxgtk2.8 is installed these packages will all currently use it in preference (unless the user has changed the wx.pth alternative) so they'll all already be running with 2.8 for most users. If you want to check the status, see the wiki page: http://wiki.debian.org/Teams/WxWidgets/Transition2.6to2.8 I've also user-tagged the bugs, and there's a link to that on there. 2.8.12.1-2 is now in unstable. I'd intended to target experimental (as I had with 2.8.12.1-1), but slipped up. However since putting it in experimental was mostly just being cautious, so I'm intending to let it stay in unstable, and deal with any issues there. We'll uncover them sooner at least. Once 2.6 is gone, I'll try to get 2.9.x packaged and into experimental (if I've not lost all enthusiasm by then) so that at least the various new packages which require it can also go into experimental, and we can be more prepared for when 3.0 finally emerges. Cheers, Olly -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20111019t061307-...@post.gmane.org
Getting rid of wxwidgets2.6
Currently we have wxwidgets2.6 and wxwidgets2.8 in the archive. We've had wxwidgets2.8 since lenny and it's now much more widely used than 2.6 in the archive. Upstream 2.6 no longer really gets any attention (the last release was in 2007), while 2.8 had a point release about 6 months ago. So I believe it's time to migrate the remaining wxwidgets2.6-dependent packages to wxwidgets2.8 and get rid of wxwidgets2.6. If you maintain a package which depends on one of the wxwidgets2.6 packages, please at least scan through the rest of this mail. Further Reasons to do this now == It seems wxwidgets3.0 is approaching (an upstream dev says "beginning of the next year" in a fairly recent blog post at http://wxwidgets.blogspot.com/2011/07/292-and-plans-for-future.html though they're also apparently still merging substantial new pieces of code). We can't realistically support three major versions of wx at once, and there are a number of newer applications which already need a newer wx than 2.8, so there's going to be a strong demand for wx 3.0 to be packaged when it finally gets released. There are 6 Zack-months (that's about 8 in human months) to the proposed freeze date for wheezy, so if we start now there's a realistic possibility of having this done in time for wheezy. Action so far = I migrated survex-aven (the wx-dependent package I co-maintain) to 2.8 before the squeeze release, so I'm at least practising what I preach! I've been getting wxwidgets2.8 back into shape over the past few days - there's an updated version of 2.8.10 in unstable with the RC bugs fixed and low hanging fruit plucked - it's built successfully for all supported architectures and is now just waiting to age enough to transition. I've also updated the packaging to the latest upstream release (2.8.12) and picked the slightly more elevated fruit. I'll be uploading this to experimental shortly - although it's nominally a minor version bump, Torsten Landschoff noted in #586129 that: However, there are also API changes at least in wxPython (some flags are now passed differently for example) so I am not sure if one would want to upload a new package right away. (Torsten: Can you recall the details?) This suggests caution is wise, as does the size of the diff between 2.8.10 and 2.8.12: 2029 files changed, 117347 insertions(+), 69829 deletions(-) Quite a lot of that seems to be in generated files, but still... The Plan I've gone through all the reverse dependencies of the 2.6 packages and put the information on the wiki: http://wiki.debian.org/Teams/WxWidgets/Transition2.6to2.8 I'm going to start working through the list, but it's hard to test applications I don't actually use, especially for the Python ones where use of a removed or changed API won't get spotted until the code path it is in is used. So please help out by testing any applications you maintain or have a particular interest in. If you are looking at a package, please just note your name and the date in brackets after it to avoid duplication of effort. Cheers, Olly -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111012044517.gg28...@survex.com
Re: [Soc-coordination] Removing Spam from the Listarchives (was: Debian mailing lists archives as mbox
On Thu, Aug 04, 2011 at 11:01:22AM +, Cord Beermann wrote: > [we should seperate the GSoC-project from the ListArchiveSpam efforts] Indeed, I've dropped soc-coordination. > as i wrote the review-stuff explained in > http://wiki.debian.org/Teams/ListMaster/ListArchiveSpam#new_web-based_effort_to_flag_spam. > I'm always interested in better methods to recognize spam. If it would be useful, I can probably provide a list of message-ids for the messages from debian lists on Gmane which have been flagged as spam and approved as such (by the team of volunteer spam report handlers). Feel free to mail me privately to sort out details if you'd like this data. Gmane just regards vacation messages, unsubscribe and other list commands sent to the list itself, spam backscatter, etc as "spam", rather than having a separate flag state for those, but the reports have been reviewed by a human, so should be higher quality than the unfiltered reports from clicks on the "Spam" buttons. Cheers, Olly -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110805020438.ga13...@survex.com
Bug#602462: ITP: apache-mod-ntlm-winbind -- apache2 module for NTLM authentication against Winbind
Package: wnpp Severity: wishlist Owner: Olly Betts * Package name: apache-mod-ntlm-winbind Version : 0.0.0+svn801 Upstream Author : Andreas Gal , Sverre H. Huseby , Tim Potter , Andrew Bartlett , Waider * URL : http://adldap.sourceforge.net/wiki/doku.php?id=mod_auth_ntlm_winbind * License : Apache 2.0 Programming Lang: C Description : apache2 module for NTLM authentication against Winbind The mod_auth_ntlm_winbind module provides authentication and authorisation over the web against a Microsoft Windows NT/2000/XP or Samba Domain Controller using Samba's winbind daemon running on the same machine Apache is running on. -- Upstream SVN has some Debian packaging work by Jelmer Vernooij, which I've updated. I talked to Jelmer on IRC about the module, and he said this is lacking an upstream maintainer within Samba currently; however the module seems to work well and be quite widely used. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101105021134.13794.8255.report...@eisluft
Re: Possible mass bug filing: missing shared library dependencies
On 2008-01-17, Niko Tyni <[EMAIL PROTECTED]> wrote: > Olly Betts <[EMAIL PROTECTED]> >xapian-examples Now fixed in SVN. In practice, the missing dependencies will be pulled in by the dependency of libxapian15-dev, so I don't see much practical benefit in uploading for just this change. Cheers, Olly -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
