Re: [backintime] I'll package the next release
Hey, On Fri, Sep 15, 2023 at 07:48:30AM +, bu...@posteo.de wrote: > Back In Time [1][2] will have a new upstream release [3] in the next days. I > [4] will try to prepare the packaging for Debian this time. The next Debian > release is minimum 2 years away so I have enough time. ;) Thanks for the heads up; I thought you were going to say it had happened and I'd missed it :) Help appreciated as always, although as an existing package you won't find it as exciting as doing something new. I may also get chance while travelling next week. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Re: Bug#798999: transition: python3.5 supported
Control: forwarded -1 https://release.debian.org/transitions/html/python3.5.html On Mon, Sep 14, 2015 at 04:30:16PM -0400, Scott Kitterman wrote: > Here's what I sent to debian-python about this transition: > > """ > It seems very likely that we'll want to release Stretch with python3.5 as the > default and only python3 version. To do that, we'll need three transitions > for python3 extensions (arch all python3 modules don't (with one exception) > need to be touched for these transitions): > > 1. Add python3.5 as a supported python3 version (there is a python3-defaults > in experimental that has this enabled for testing). This involves rebuilding > all extensions that build-dep on python3-all-dev to support python3 3.4 and > 3.5. > > 2. Make python3.5 the default python3 version. Rebuild extensions that > build-dep on python3-dev. > > 3. Drop python3.4 as a supported python3 version. This involved rebuilding > the same packages as the first one. > > For packages that build fine with python3.5, there should be nothing required > from a maintainer point of view. Except pycxx this can all be done with > binNMUs. Ubuntu has already done this transition and has patches for a number > of packages that may be of assistance when working through issues. > > Python3 3.5.0-1 is in unstable. I'm going to ask the release team for > permission to start the first transition once it gets to testing. The only > impact (other than the aforementioned python3.5 specific build issues) will be > transient build-dep uninstallabliity in the higher levels of the transition > stack until the lower levels are rebuilt. > """ > > Here's my attempt at a ben file for the first transition: > > Ben file: > > title = "python3.5 supported"; > is_affected = .build-depends ~ "python3-all-dev"; > is_good = .depends ~ /python3 \(<< 3\.6/; > is_bad = .depends ~ /python3 \(<< 3\.5/; > > I would appreciate it if you would go ahead and publish it and then with your > permission, I'll coordinate binNMUs as I've done in the past for python > transitions. Does https://release.debian.org/transitions/html/python3.5.html look about right? I adjusted the build-depend slightly. There's quite some tangling with g++ stuff at the moment so please hold tight for now. Is it feasible to do rebuild tests in experimental ahead of time? Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#708654: ITP: unittest-xml-reporting -- Python unittest-based test runner with Ant/JUnit like XML reporting
Package: wnpp Severity: wishlist Owner: Jonathan Wiltshire j...@tiger-computing.co.uk * Package name: unittest-xml-reporting Version : 1.4.3 Upstream Author : Daniel Fernandes Martins * URL : https://pypi.python.org/pypi/unittest-xml-reporting * License : GPL-3+ Programming Lang: Python Description : Python unittest-based test runner with Ant/JUnit like XML reporting unittest-xml-reporting is a unittest test runner that can save test results to XML files that can be consumed by a wide range of tools, such as build systems, IDEs and continuous integration servers. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130517141945.18380.82694.report...@jmw.tiger-computing.wbp
Re: SPAMing from my email address
On Wed, Apr 20, 2011 at 03:22:49PM +0430, Sameer Rahmani wrote: I deactivated my gmail account while ago but some one use it for sending SPAM mails, at first i apologize for this. I will delete my Gamil account if i can or deactivate it. so i will not send any email with my Gmail account again and if you get any mail from my account it will be a SPAM for sure. from now on my primary mail address will be lxsameer [AT] GNU.org Well done for publishing your entire address book to a list with public archives. /sarc -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110420164708.go12...@lupin.home.powdarrmonkey.net
Re: RFS: preprocess
On Mon, Apr 04, 2011 at 10:34:07AM +0200, Johannes Ring wrote: P: no-upstream-changelog: upstream changelog is in README.txt You use debhelper, in a round-about way: see 1. dh_installchangelogs(1) 2. http://build-common.alioth.debian.org/cdbs-doc.html#id2540110 -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110404165931.ga31...@lupin.home.powdarrmonkey.net
Re: Bug#605784: nagios-statd-server: stops responding and 100% cpu usage
clone 605784 -1 reassign -1 python2.6 retitle -1 os.waitpid does not take keyword args in Lib/SocketServer.py forwarded -1 http://bugs.python.org/issue5814 tag -1 fixed-upstream upstream severity -1 important This appears to be the root cause of 605784 and it's fixed upstream at http://svn.python.org/view?view=revrevision=73887 On Fri, Dec 03, 2010 at 01:39:12PM +0100, Vladislav Kurz wrote: after upgrade to squeeze, nagios-statd stopped working. Usually works fine for one hour and after that nagios reports connection timeout and top indicates that nagios-statd is using 100% of CPU. (Fortunately uses only one core on muli-core CPU.) I found a recommendation on ubutu bugzilla to use python2.4. See here: https://bugs.launchpad.net/ubuntu/+source/nagios-statd/+bug/463795 -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: PyMT in Debian
Hi, On Mon, Nov 29, 2010 at 11:05:35PM +0100, Johan Euphrosine wrote: Given that: - The package “pymt” 0.5.1-0ubuntu1 is only available in Ubuntu Maverick. - Robert (in Cc) packaged it for Ubuntu. - Maintainer is Ubuntu Desktop Team ubuntu-desk...@lists.ubuntu.com. - I'm a Debian Maintainer (DM not DD), thus I can't sponsor package myself. What would be the proper way to get pymt package into Debian, and synced to upcoming Ubuntu release ? - take the Maverick package as a start - remove the ubuntu parts, and make it conform to Debian policy and Debian Python policy - make the version 0.5.1-1, which is higher than the Maverick version, so it will upgrade it, and find a friendly sponsor (sadly not me) - it will flow through to ubuntu in a sync That's a *broad* summary, all the usual packaging rules will apply. -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Consistent DPMT and PAPT names
On Mon, Nov 15, 2010 at 08:29:30PM +0200, anatoly techtonik wrote: Why not to choose consistent naming scheme for Python groups? Like PMPT and PAPT or DPMT and DPAT? Presently they're not easily confused or mis-typed, which is actually quite useful when you work in both teams. BTW, what are differences in packaging between Application and Module - any FAQ links? Debian Python Policy? Sections 2 and 3 are modules and applications respectively. http://www.debian.org/doc/packaging-manuals/python-policy/ -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Deadline for 10.10 updates?
On Wed, Sep 22, 2010 at 09:21:16PM +0200, Tim Michelsen wrote: When is the last date to submit an updated package? The Version of the Spyder Science IDE to be included in 10.10 is very outdated: http://packages.ubuntu.com/maverick/spyder I couldn't find it on the wiki: https://wiki.ubuntu.com/MaverickReleaseSchedule With a Debian hat on, I think you have the wrong list. This is the list for Python development in Debian. With an Ubuntu hat on, the release is well past Final Freeze and rapidly approaching Release Candidate, so you must have a very, very good reason and convince the release managers so. If you'd like to contribute to spyder in Debian, that's great :-) Your changes will flow through to Ubuntu anyway when their freeze is over and the automatic sync is re-enabled. -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: RFS: python-cloudfiles
On Fri, Apr 02, 2010 at 07:11:55AM -0500, Michael Shuler wrote: I would enjoy some feedback from the python team on this package, if someone has a bit of time to review my work. I can't sponsor your work, but a brief review. There are just a couple of things outstanding from a Python point of view, unless other team members disagree: You need to build-depend on python-support = 0.90 for Python 2.6 support. debian/pycompat is for python-central, please use debian/pyversions. Does the module really work with all 2.x versions, or should it be increased to 2.4-? See /usr/share/python-support/README.gz for debian/pyversions format. The quickest way to get it sponsored, when these are changed, is to inject the package into python-modules svn and add the package to /topic in #debian-python. See http://wiki.debian.org/Teams/PythonModulesTeam -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Bug#524176: AM_PATH_PYTHON should honor python's idea about the site directory
On Tue, Mar 23, 2010 at 11:34:42PM +0100, Matthias Klose wrote: it is fixed upstream in automake 1.11 (and in Debian), so you could use this version; I doubt that it will allow more binNMUs, as autoconf isn't called during the build for many packages. I don't see automake1.11 in the archive. Can you give me a pointer? Thanks. I will take a closer look at the blocked bugs. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Bug#524176: AM_PATH_PYTHON should honor python's idea about the site directory
Hi, Do you have any indication of when this bug will be closed? It's currently holding up the (proper) fixes for several bugs key to the Python 2.6 transition, that we want to get over and done as soon as possible. We can make ugly patches, but fixing this bug would reduce the work needed to merely binNMUing the affected packages, if I have understood it correctly. Thanks, -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Ensuring stable APIs for consumer applications
Hi, It occurs to me that there's very little guarantee of a stable API in Python modules - less so in C modules, because upstream tends to be more aware that this is a library, but in pure Python modules. In lib* libraries, we (usually) have SONAMEs which provide some kind of contract between the .so and the consuming application. Is there an equivalent practice in pure Python modules that is implemented widely enough to be useful? The question came about because the upstream author of RedNotebook ships a number of convenience copies, sometimes heavily modified, because he is nervous about APIs changing suddenly and wasting his work. It's likely that there will be more of these in the near future. Is there anything with which I can reassure him and reduce the amount of duplicated code in this application? Of course I may have missed something very obvious, so please say so if I have. Thanks, -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: RC severity for Python 2.6 related bugs
On Sun, Feb 28, 2010 at 04:46:09PM +0100, Josselin Mouette wrote: Le dimanche 28 février 2010 à 15:29 +0100, Vincent Bernat a écrit : It would be far easier to let Python 2.6 be the default, then file (or upgrade) serious bugs and solve them in a week or two. Yeah sure, let’s knowingly break dozens of packages by switching instead of fixing them before and make it painless for users. I think we need to do both before we end up running out of time. I propose that we upgrade/file bugs as serious so that they get maintainer attention where possible, and allow (let's say) 7 days to react. After this time, Python 2.6 should become default in sid and all such bugs are NMU candidates. If nothing else gets maintainer's attention, this will. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100228161932.ga32...@lupin.powdarrmonkey.net
Bug#563838: RFP: zeitgeist -- user activity logging and collation service
Package: wnpp Severity: wishlist * Package name: zeitgeist Version : 0.3 (0.4 soon) Upstream Author : Zeitgeist Developers zeitge...@lists.launchpad.net * URL : http://zeitgeist-project.com/ * License : LGPL3 (LGPL2.1 planned) Programming Lang: Python Description : user activity logging and collation service Zeitgeist is a service which logs the users's activities and events, anywhere from files opened to websites visited and conversations. . It makes this information readily available for other applications to use. . It is able to establish relationships between items based on similarity and usage patterns. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557288: libkml: manipulates site-packages/ directly, failing with Python 2.6
Package: libkml Version: 1.0.1-3 Severity: important User: debian-python@lists.debian.org Usertags: python2.6 ftbfs Package fails to build from source with python2.6, here's the build log tail: | # removes build-time rpaths | for version in python2.5 python2.4; \ | do \ | chrpath --delete /tmp/buildd/libkml-1.0.1/debian/python-kml/usr/lib/$version/site-packages/*.so ; \ | done | open: No such file or directory | elf_open: Invalid argument | make: *** [binary-install/python-kml] Error 1 (debian-python: caution, this package has large build-dependencies and takes a very long time to build) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557293: polybori: FTBFS without Python 2.4
Package: polybori Version: 0.5~rc1-2 Severity: important User: debian-python@lists.debian.org Usertags: python2.6 ftbfs polybori hardcodes Python version it uses at build time in python-polybori.install, despite have a build-depends on python-all-dev. This means that polybori will fail to build once Python 2.4 is removed from the list of support Python versions. While you're there, you might also migrate from python-central to python-support (this is the advice of the debian-python list): http://wiki.debian.org/DebianPython/central2support -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556364: pycxx: FTBFS with Python 2.6
Package: pycxx Version: 5.5.0-1 Severity: important User: debian-python@lists.debian.org Usertags: python2.6 ftbfs pycxx fails to build from source with python2.6, with this log: | Writing /tmp/buildd/pycxx-5.5.0/debian/python-cxx/usr/local/lib/python2.6/dist-packages/CXX-5.3.egg-info | find debian/python-cxx -name '*.egg-info' | xargs -r rm -f | mkdir -p debian/python-cxx-dev/usr/share/ | mv debian/python-cxx/usr/share/python2.6 \ | debian/python-cxx-dev/usr/share/ | mkdir -p debian/python-cxx-dev/usr/include | mv debian/python-cxx/usr/include/python2.6 debian/python-cxx-dev/usr/include/ | mv: cannot stat `debian/python-cxx/usr/include/python2.6': No such file or directory | make: *** [install-python2.6] Error 1 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#555415: rednotebook: Embedded copy of msgfmt.py script
(debian-python readers, please see paragraph 2) On Tue, Nov 10, 2009 at 04:54:19PM +0100, Jakub Wilk wrote: It seems to me the this module is required only at build time, so it should be safe to remove it from the binary package. (Please correct me if I'm wrong.) This is true, but removing it from the binary package doesn't fix the code duplication, because it still builds with the private copy and not a public module. Should there ever be a serious problem with msgfmt.py, it's still got to be patched in multiple packages. Anyway, I'm increasingly thinking that those example scripts which are of production quality should be turned into binary packages installing as public modules, so that they are more easily recognised. Copying debian-python for a wider view; I'm happy to work on doing this, if it's worth it. If they're not production quality, then the packages using them shouldn't be and we have a different problem (at least with msgfmt.py, which I take it you have filed mass bugs for). Copying the python-examples maintainer: your thoughts please? There are other packages that are actually using a copy of msgfmt.py at runtime so the question if still valid. -- Jakub Wilk -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: MBF: embedded copies of Python modules
On Sun, Nov 08, 2009 at 05:43:20PM +0100, Jakub Wilk wrote: Jonathan Wiltshire deb...@jwiltshire.org.uk rednotebook Because rednotebook embeds a copy of txt2tags presumably? This is because it uses some features in txt2tags's VCS that aren't yet released, and I'm already working closely with upstream to remove the embedded copy (hence my ongoing work on the txt2tags package for sid). -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Debhelper 7, Python package, multiple binary packages
On Sun, Oct 18, 2009 at 10:31:02AM +1100, Ben Finney wrote: Thanks, ‘backintime’ does indeed meet these criteria. The ‘debian/rules’ file is doing some things that I'm confused about: = override_dh_auto_clean: rm -rf locale common/po/*.mo find $(CURDIR) -name *\.py[co] -delete rm -f common/Makefile gnome/Makefile kde4/Makefile = Is it necessary to remove ‘*.py[co]’ files? Wouldn't it be better to call ‘dh_auto_clean’ to do this? They must be removed to keep the .diff.gz clean, but upstream doesn't ship makefiles with clean targets, so dh_auto_clean can't handle it. dh_clean doesn't know about pre-compiled python files. = override_dh_pysupport: dh_pysupport /usr/share/backintime/ = Is this necessary? Why can't ‘dh_pysupport’ do this without being overridden here? dh_pysupport: If your package installs private python modules in non-standard directories, you can make dh_pysupport check those directories by passing their names on the command line. By default, it will check /usr/lib/$PACKAGE, /usr/share/$PACKAGE, /usr/lib/games/$PACKAGE and /usr/share/games/$PACKAGE In my case, the package names are backintime-* but the install directory is always /usr/share/backintime, so dh_pysupport needs a little hint here. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debhelper 7, Python package, multiple binary packages (was: RFS: python-coverage 3.0.1-1)
On Sat, Oct 17, 2009 at 11:40:07PM +1100, Ben Finney wrote: Can someone point me to an existing package that: * uses ‘debhelper’ vversion 7 or later (i.e. uses the implied-sequence ‘dh’ command instead of explicit lists of ‘dh_foo’ commands) * uses ‘python-support’ * creates multiple packages, preferably including a ‘foo-dbg’ package IIRC, backintime does all but the -dbg of these things. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: apps-team, modules-team: pet.cgi gives bad SVN links
On Fri, Aug 21, 2009 at 12:06:25AM +0200, Piotr Ożarowski wrote: fixed thanks to guys from #pet-devel (in pet.conf, we were using wsvn_url which is no longer supported) Much better; please thank them :) -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Getting stuck into apps-team and modules-team
Hi, I've looked at a few packages in the repositories for these teams, but I'm reluctant to start making changes without making sure it's not going to upset anybody :) Where the team is just an uploader, I'm inclined to leave the maintainer to ask for help when s/he needs it. But where packages are fully under the team's scope, is there any protocol for starting work on an oustanding package? Particularly where there are bugs or new upstreams available, is it acceptable to just get stuck in, or is wise to contact the last changer (I found little evidence of this on lists, but I may have been looking in the wrong places)? I'd like to contribute to both teams (so by all means say 'please do this for us') but not at the risk of disrupting their workflow. Thanks for your advice. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Getting stuck into apps-team and modules-team
On Thu, Aug 13, 2009 at 03:00:15PM +0100, Jonathan Wiltshire wrote: I've looked at a few packages in the repositories for these teams, but I'm reluctant to start making changes without making sure it's not going to upset anybody :) And of course, I was bound to forget something. Last question: what is the consensus on deep packaging changes, like (examples) dpatch/quilt, cdbs/debhelper/dh, python-central/python-support and so on? -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
apps-team, modules-team: pet.cgi gives bad SVN links
Hi, by all means tell me where to file a bug :) On both teams' PET scripts, links to the ViewVC pages seem invalid, for example: /wsvn/python-modules/packages/pprocess/debian/changelog/trunk/ should be /wsvn/python-modules/packages/pprocess/trunk/debian/changelog/ It doesn't seem to affect the Perl team's PET, so I guess it's local configuration. Is it something I can fix? Thanks, -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Getting stuck into apps-team and modules-team
On Thu, Aug 13, 2009 at 04:14:30PM +0200, Sandro Tosi wrote: check with the current real guy behind the package, it's the safest way. Of course. like (examples) dpatch/quilt, I'd say dpatch - it's easier to use it in SVN cdbs/debhelper/dh, I strongly encourage to use debhelper, and others do the same Any (team) thoughts on debhelper vs dh's autosequencer? Personally, I like dh in simple cases and with overrides, but it makes backporting trickier because the support hasn't been in a stable release (AFAIK). python-central/python-support and so on? python-support is what we're standardizing on, so feel free to migrate to pysupport is you stumble upon a pycentral package. Right. Ah, a nice communication medium is IRC: if you like, you can find us at #debian-python on irc.debian.org OFTC network. Ok. I'm often not near IRC, but I drop in from time to time. Cheers, -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Getting stuck into apps-team and modules-team
On Thu, Aug 13, 2009 at 04:23:29PM +0200, Piotr Ożarowski wrote: feel free to commit your changes, we can always revert it ;-) (you'll get private replies from those subscribed to -commits if there's something wrong) Just call me cautious :) I'd like to contribute to both teams (so by all means say 'please do this for us') but not at the risk of disrupting their workflow. see this thread: http://lists.debian.org/debian-python/2008/03/msg00014.html my reply (and I still use these rules when I do changes in team packages or when I sponsor team uploads) is here: http://lists.debian.org/debian-python/2008/03/msg00016.html Aha, thanks. -- -=[ Piotr Ożarowski ]=- -=[ http://www.ozarowski.pl ]=- Cheers, -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
RFS: rednotebook
Dear mentors, Piotr is unable to sponsor rednotebook at the moment, so I'm seeking a sponsor for the new version until he's back online. It's a new upstream version only, no packaging changes, and targets unstable. The dsc is on mentors at http://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_0.6.4-1.dsc and is lintian clean. If you're able to review or sponsor, thanks in advance. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: [done] RFS: rednotebook
On Mon, Mar 30, 2009 at 01:13:59PM +0200, Alexander Reichle-Schmehl wrote: Colleagues are busy; uploaded ;) Cheers :) -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: doubt about license
On Tue, Feb 03, 2009 at 09:47:53PM +0100, Pietro Battiston wrote: Googling a little, I couldn't understand if such a migration is legally plausible (I don't think so, but I'm not an expert). But even if it was, what is the reason? The chart in [1] is a useful reference for such a query (and in this case, it's not legal and the package needs re-licensing). [1] http://www.fsf.org/licensing/licenses/quick-guide-gplv3.html -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: RFS: rednotebook (NEW)
On Thu, Jan 29, 2009 at 08:48:59PM +0100, Piotr Ożarowski wrote: [Jonathan Wiltshire, 2009-01-29] * it's Python app. - consider installing it to private directory (f.e. /usr/share/rednotebook) Ok, that makes more sense, done. Also imported a new upstream release, which is based on PyGTK and much nicer, so you will see the dependencies have changed. I also cleared a lintian error about debian/copyright which somehow I missed. The updated dsc is on mentors at http://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_0.5.3-1.dsc TIA -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
RFS: rednotebook (NEW)
(copy to debian-python as this is a python package; still seeking sponsorship) Dear mentors, I am seeking a sponsor for my package rednotebook, a daily journal with calendar, templates and keyword searching. Version:0.4.0 Upstream author:Jendrik Seipp jendrikse...@web.de URL:http://rednotebook.sf.net/ License:GPLv2 Language: Python The full description reads: RedNotebook is a graphical diary and journal to keep track of notes and thoughts throughout the day. It includes a calendar navigation, customisable templates for each day, and a keywork search and cloud. This upload closes ITP bug 507939. I believe the package is in good shape (it is certainly lintian clean) and is not complex, so even if you are unable to upload I would appreciate any comments. It includes a simple man page that I have sent upstream already. The dsc is available on mentors.d.n at: http://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_0.4.0-1.dsc Thanks in advance, -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 Sending of encrypted mail is encouraged signature.asc Description: Digital signature
