Re: pprocess packaging SVN
On Thu, 12 Dec 2013, Dmitry Shachnev wrote: > On Thu, Dec 12, 2013 at 6:34 PM, Yaroslav Halchenko > wrote: > > declared svn repository at > > svn://svn.debian.org/python-modules/packages/pprocess/trunk/ > > svn co svn://svn.debian.org/python-modules/packages/pprocess/trunk/ > > pprocess ... > > svn: URL 'svn://svn.debian.org/python-modules/packages/pprocess/trunk' > > doesn't exist > > checkout failed (the command above returned a non-zero exit code) > You may want to restore those paths from r17893 instead of creating > them again, so that history is kept. > See: > http://anonscm.debian.org/viewvc/python-modules?view=revision&revision=17894 Ah right... mighty SVN -- forgotten about your pros ;) Thank you Dmitry. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20131212163140.gr6...@onerussian.com
Re: pprocess packaging SVN
On Thu, Dec 12, 2013 at 6:34 PM, Yaroslav Halchenko wrote: > declared svn repository at > svn://svn.debian.org/python-modules/packages/pprocess/trunk/ > svn co svn://svn.debian.org/python-modules/packages/pprocess/trunk/ pprocess > ... > svn: URL 'svn://svn.debian.org/python-modules/packages/pprocess/trunk' > doesn't exist > checkout failed (the command above returned a non-zero exit code) You may want to restore those paths from r17893 instead of creating them again, so that history is kept. See: http://anonscm.debian.org/viewvc/python-modules?view=revision&revision=17894 -- Dmitry Shachnev -- 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/cakimphwnd6pzbd_hfb1defwoxv98j+kt_mrrsiael2tca4r...@mail.gmail.com
pprocess packaging SVN
Hi Sandro, It is unfortunate that I 1. have forgotten to add pprocess to pymvpa* packages' Recommends 2. have missed the pprocess RM bug I would like to reincarnate the package, may be at least for NeuroDebian unless someone needs it in stock Debian, since we still use it in NeuroDebian and it needs a slight bugfix (amazing how well it served us without a hassle for years). But original SVN is gone and I can't find it on the servers -- is it anywhere or should I just recreate it from the snapshots? $> debcheckout pprocess declared svn repository at svn://svn.debian.org/python-modules/packages/pprocess/trunk/ svn co svn://svn.debian.org/python-modules/packages/pprocess/trunk/ pprocess ... svn: URL 'svn://svn.debian.org/python-modules/packages/pprocess/trunk' doesn't exist checkout failed (the command above returned a non-zero exit code) On Tue, 19 Jul 2011, Debian FTP Masters wrote: > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: > pprocess | 0.5-1 | source > python-pprocess | 0.5-1 | all > --- Reason --- > ROM; unused > -- > Note that the package(s) have simply been removed from the tag > database and may (or may not) still be in the pool; this is not a bug. > The package(s) will be physically removed automatically when no suite > references them (and in the case of source, when no binary references > it). Please also remember that the changes have been done on the > master archive (ftp-master.debian.org) and will not propagate to any > mirrors (ftp.debian.org included) until the next cron.daily run at the > earliest. > Packages are usually not removed from testing by hand. Testing tracks > unstable and will automatically remove packages which were removed > from unstable when removing them from testing causes no dependency > problems. The release team can force a removal from testing if it is > really needed, please contact them if this should be the case. > We try to close Bugs which have been reported against this package > automatically. But please check all old bugs, if they where closed > correctly or should have been re-assign to another package. > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 634...@bugs.debian.org. > The full log for this bug can be viewed at http://bugs.debian.org/634189 > This message was generated automatically; if you believe that there is > a problem with it please contact the archive administrators by mailing > ftpmas...@debian.org. > Debian distribution maintenance software > pp. > Alexander Reichle-Schmehl (the ftpmaster behind the curtain) > ___ > Python-modules-team mailing list > python-modules-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20131212143431.ga8...@onerussian.com
Upgrading html5lib to 0.99 (in order to add support for Python3)
Hi. I'm interested in upgrading html5lib to 0.99 (currently at 0.95 in Debian), in order to bring Python 3 compatibility (see #729155). This would help making sure that RDFLib will also be available for Python 3, for whose package I'm working too (see #655039 and #702300). Bernd, I'm not sure if you're interested and/or have investigated changes brought by this upgrade already. As I'm new to the team, I though I'd ask before doing much work that could be redundant (who knows...). I've already committed to SVN the basic changes needed, but as usptream code has evolved quite a lot I think there's a need for more work (reviewing changes, updating copyright, adding doc generation, maybe passing upstream tests if possible, etc.). Thus I'll probably work on this during the next days. In case you're interested, please let me know... and anybody else interested in helping or willing to review the package, please, let me know too. Also, I'm not exactly sure how to proceed with reverse dependencies on the library, and whether maintainers of these packages should be notified somehow... Feel free to educate me in case I'm missing some procedures on how to contribute to a packaging that was previously handled by someone else, in the frame of DPMT. Thanks in advance. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- 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/87mwk6xx88@inf-8660.int-evry.fr
