Joining the team to maintain pydrive
Hey there, I would like to add pydrive [1] to Debian (I'm currently maintaining it for Ubuntu as a opt-depends of deja-dup to be able to back-up on gdrive). I think it makes sense for it to be under the python team umbrella. I might occasionally contribute to updates or fixes on desktop components maintained by the team. My salsa login is 'seb128' I've read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and agree to comply to the team rules. Cheers, Sebastien Bacher [1] RFP #922076 , using https://github.com/iterative/PyDrive2 which is the maintained version of the project
gnome2 et opengl for python2.2
Hello Does somebody know where I could found debian packages (binary build for libgtk2.0-0png3, or sources) of python2.2-gnome2 and python2.2-opengl ? Thank you Sebastien Bacher
python transition and python-xml
Hi, I need the python-xml package to rebuild some of my packages (python-gtk, python-gtk2, python-gnome2, python-pyorbit, rubrica), but python-xml is away from unstable because of transition. Several packages use python-gtk/gtk2, so I would upload these packages today, but I don't know what's the best way. * NMU python-xml (I've mailed the maintainer yesterday but no response for the moment). * I've made python2.3 package of python-xml on my box, so I can build python-gtk and upload it ... but with missing build-depends autobuilders will fail to build the package ... * change Build-Depends from python-xml to python2.3-xml for the moment. I'd like have some advices about what's the best way to process. Thank you, Sebastien Bacher
Re: python transition and python-xml
> Yesterday was saturday, and I don't read my mail on week ends. The > updated package is in progress (i.e. pbuilder is running right now), > and I have contacted Jerome Marant who's my usual sponstor (I'm not a > DD). I was planning to ask someone on the list to sponsor the upload if > I don't get an answer from him by tomorow, but if people think this is > more urgent, please tell me if you want to sponsor the upload today, and > I'll give you the URL where you can dowload the source package for > python-xml and python-unit. Ok, no problem. If Jerome is away I can make the upload. Cheers, Sebastien Bacher
pygtk transition
Hello, The new pygtk 1.2 packages are available: python-gtk-1.2 python-gnome-1.2 python-glade-1.2 python-gdk-imlib-1.2 Package which have some depends on old packages (python-gtk/gnome/glade/gdk-imlib) have to update them. Don't forget to check that py files have changes to run with pygtk2 as default (look on this list archives for details). Cheers, Sebastien Bacher
Re: pygtk transition
Matthias Klose <[EMAIL PROTECTED]> writes: > Do I need to understand this? Currently I do not ... It's the 3rd mail on this list about this list about this. The package renaming was discuted last week, I've just sent this mail to say that the new packages are available. > If you rename packages and dependent packages, then at least notify > the package maintainers (and the list) what needs to be done on which > packages. Which packages become unbuildable/uninstallabe and have to > be changed? I've filled bug all concerned packages and I'll let some days to maintainer before posting a resume a resume of which package need to be rebuilded. The old packages are not removed yet, so there is no breakage for the moment. Cheers, Sebastien Bacher > > Thanks, Matthias > -- Test signature
Re: pygtk 1.2 transition problem
Joe Drew <[EMAIL PROTECTED]> writes: > I've updated glimmer to build against python 2.3 and the new > python-gtk-1.2 package, but have run into problems running it. I'm > wondering what has changed; is there an easy workaround? (I know some > python but am not, by any means, a python hacker.) > > Fatal Python error: could not import _gtk There is no changes in -1.2 package, just a name change. We've fixed the bug, due to a python part in C sources of glimmer ... > One other question: could someone (Sebastien?) let me know if the new > python-gtk-1.2 (etc) packages are meant for sarge? If not, it'll be > difficult to get any pygtk 1.2 using packages into sarge. The new package are designed for the next stable with python-gtk2 as default. They are only in unstable for the moment but they will hit Sarge before the release ... and hold version are not removed yet from the archive. Cheers, Sebastien Bacher
pygtk transition 1.2 -> 2
Hi,
It seems to be transition time for python packages ;-)
For the moment the default python bindings for gtk/gnome are 1.2
version. It means that an "import gtk" in a .py will load gtk1.2.
It's time to switch gtk/gnome 2 as the default bindings.
So all pygtk/gnome 1.2 programs have to use these two lines before
loading a gtk/gnome part:
import pygtk
pygtk.require('1.2')
I've mailed almost all the maintainers (sorry if I've forgotten some of
them) who have packages depending on python-gtk/gnome about this for
some months. The goal is to have packages which work with pygtk.pth set
to gtk-2.0 before the transition.
I've mailed against in july to re-explain the situation, and patchs (that
should work) were attached to the mails.
Some maintainers have made the changes, but a large number of them
didn't response to the mails for the moment.
I'll fill bug against the packages which don't have any fix for the
transition during the next week, and upload python-gtk2 and
python-gnome2 as default version before the end of the month.
If some of maintainers need NMU, you can ask here.
Cheers,
Sebastien Bacher
Re: pygtk transition 1.2 -> 2
Joe Drew <[EMAIL PROTECTED]> writes:
>> import pygtk
>> pygtk.require('1.2')
>
> Will this also cover using gnome 1 bindings instead of gnome 2?
Yes, these two line specify that you want to use gtk and gnome 1
bindings instead of the gnome 2 ones.
> I assume that just prepending the above two lines to something like the
> following should work?
>
> from gtk import *
> import _gtk
> import _gnome
> import _gnomeui
> from gnome.ui import *
> import gnome.config
Yes ;-)
Cheers,
Sebastien Bacher
pygtk 1.2 -> 2 transition, what's the best way ?
Hello, I'm looking on the best way to do the soon coming python-gtk 1.2 -> 2 transition (for more details about that: http://lists.debian.org/debian-python/2003/debian-python-200308/msg00031.html). The transition will be ok for unstable, but what about the next stable ? A summarize the problem : * An user is running current stable with some python-gtk apps. The gtk1.2 python binding is the default, so woody's apps use "import gtk" to have gtk1.2 (without specify the version). * After the next release he decides to install python-gtk2 (or an app that need python-gtk2) by apt-get install python-gtk2 (or app). => The default binding will be set to 2.0, and brokes all woody's packages that use "import gtk" to have gtk 1.2. So we need to make the install of python-gtk2 upgrading all the packages depending from python-gtk (without that they will be broken). I'm seeing two solutions for that : 1- Make current python-gtk(2) conflict with all old packages depending on python-gtk to force the update. This solution will : - be ok for the upgrade - need no changes for the others packages but: - need to list all the packages concerned (and be carefull not forgotten one) - will not work with non-official packages 2- Make python-gtk2 conflicts with python-gtk, and introduced a python-gtk-compat1.2 package to replace it. Then you just need to build all packages depending on python-gtk (1.2) against the new package (about 20 packages to rebuild, not a lot of work). So a install of python-gtk2 will remove python-gtk, install python-gtk-compat1.2 and upgrade all needed packages. I'm thinking the second one is the best solution, but I prefer asking here for having some advices before starting in that way. I've made some test of the second solution in a chroot, all seems to be ok (install of python-gtk2, of a app depending on python-gtk2, upgrade, ...). If nobody is against that, I think I'll upload the new python-gtk-compat1.2 during the next week. Cheers, Sebastien Bacher
Re: Summary of python transition problems
Colin Watson <[EMAIL PROTECTED]> writes: > * python-gnome2: s390 Due to #212854 on gnome-vfs2 ... I'll probably NMU gnome-vfs2 soon if Takuo KITAME doesn't fix it. Cheers, Sebastien Bacher
