Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)
Version: 0.9-1 * Brian May [Sun, 27 Aug 2006 17:43:24 +1000]: Robert Could you please run 'bzr upgrade' while using bzr Robert 0.9rc1. If my guess at your situation is right this will Robert take a while to run, but correct your performance issues. Did I do something wrong? [EMAIL PROTECTED]:~/bzr/diary-data$ bzr upgrade /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools/__init__.py:21: DeprecationWarning: Modifying DEFAULT_IGNORE was deprecated in version 0.9. Consider using bzrlib.ignores.add_unique_user_ignores o r bzrlib.ignores.add_runtime_ignores /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools/__init__.py:22: DeprecationWarning: Modifying DEFAULT_IGNORE was deprecated in version 0.9. Consider using bzrlib.ignores.add_unique_user_ignores o r bzrlib.ignores.add_runtime_ignores bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format. Adeodato No. You just need to upgrade your bzrtool package to 0.9 Adeodato as well. I had 0.9 installed already when doing this: ii bzrtools0.9.0-1 Collection of tools for bzr Hm. I'd say that you have .pyc files left in: /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools Can you check, please? Also, do you remember having root bzr as root? bzrtools 0.9 does not put files under /usr/lib/python2.4, since it uses python-support; and its maintainer scripts for 0.9 did not bytecompile the modules, so the most plausible explanation for .pyc files in /usr/lib/python2.4 is having run bzr 0.8 as root. To debian-python: this is presumably a bug in bzrtools? So what is going wrong? Anyway, I tried the revert operation again with 0.9-2. Memory usage was still high (205meg at one point), but bounded - much better. The operation successfully completed this time. Adeodato Sounds acceptable to close ##380412, then? Yes, sounds good to me. Done, thanks. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Los Caramelos - Cherry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Adeodato Hm. I'd say that you have .pyc files left in: Adeodato Adeodato /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools Adeodato Can you check, please? Yes, see below. Adeodate Also, do you remember having root Adeodato bzr as root? Huh? Adeodato bzrtools 0.9 does not put files under Adeodato /usr/lib/python2.4, since it uses python-support; and Adeodato its maintainer scripts for 0.9 did not bytecompile the Adeodato modules, so the most plausible explanation for .pyc Adeodato files in /usr/lib/python2.4 is having run bzr 0.8 as Adeodato root. Adeodato To debian-python: this is presumably a bug in bzrtools? [EMAIL PROTECTED]:~$ ls -l /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools total 288 -rw-r--r-- 1 root root 31767 2006-07-16 18:58 baz_import.py.bak -rw-r--r-- 1 root root 29959 2006-08-12 12:08 baz_import.pyc -rw-r--r-- 1 root root 830 2006-08-12 12:08 branches.pyc -rw-r--r-- 1 root root 2198 2006-08-12 12:08 branchhistory.pyc -rw-r--r-- 1 root root 4167 2006-08-12 12:08 branch_mark.pyc -rw-r--r-- 1 root root 13906 2006-08-12 12:08 bzrtools.pyc -rw-r--r-- 1 root root 1232 2006-08-12 12:08 cbranch.pyc -rw-r--r-- 1 root root 4167 2006-08-12 12:08 clean_tree.pyc -rw-r--r-- 1 root root 8687 2006-08-12 12:08 dotgraph.pyc -rw-r--r-- 1 root root 1637 2006-08-12 12:08 errors.pyc -rw-r--r-- 1 root root 4235 2006-08-12 12:08 fai.pyc -rw-r--r-- 1 root root 2275 2006-08-12 12:08 fetch_ghosts.pyc -rw-r--r-- 1 root root 8827 2006-08-12 12:08 graph.pyc -rw-r--r-- 1 root root 5466 2006-08-12 12:08 hunk_selector.pyc -rw-r--r-- 1 root root 16502 2006-07-16 18:52 __init__.py.bak -rw-r--r-- 1 root root 18867 2006-08-12 12:08 __init__.pyc -rw-r--r-- 1 root root 20311 2006-08-12 12:08 patches.pyc -rw-r--r-- 1 root root 7321 2006-08-12 12:08 patch.pyc -rw-r--r-- 1 root root 2573 2006-08-12 12:08 patchsource.pyc -rw-r--r-- 1 root root 1460 2006-08-12 12:08 progress.pyc -rw-r--r-- 1 root root 1545 2006-08-12 12:08 rspush.pyc -rw-r--r-- 1 root root 626 2006-08-12 12:08 setup.pyc -rw-r--r-- 1 root root 9907 2006-08-12 12:08 shelf.pyc -rw-r--r-- 1 root root 10210 2006-08-12 12:08 shell.pyc -rw-r--r-- 1 root root 3846 2006-08-12 12:08 switch.pyc -rw-r--r-- 1 root root 1822 2006-08-12 12:08 terminal.pyc -rw-r--r-- 1 root root 1367 2006-08-12 12:08 test.pyc -rw-r--r-- 1 root root 5083 2006-08-12 12:08 userinteractor.pyc -rw-r--r-- 1 root root 3674 2006-08-12 12:08 zap.pyc [EMAIL PROTECTED]:~$ dpkg -S /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools bzrtools: /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools [EMAIL PROTECTED]:~$ dpkg -L bzrtools /. /usr /usr/lib /usr/lib/python2.4 /usr/lib/python2.4/site-packages /usr/lib/python2.4/site-packages/bzrlib /usr/lib/python2.4/site-packages/bzrlib/plugins /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools /usr/share [...] Not sure what those *.bak files are, but I suspect that was some hackish debugging I did for a previous problem. I would speculate that upgrading the package didn't result in the compiled files being deleted. [EMAIL PROTECTED]:~$ dpkg -l bzrtools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii bzrtools 0.9.0-1 Collection of tools for bzr -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)
* Brian May [Mon, 28 Aug 2006 13:22:55 +1000]: Adeodate Also, do you remember having root Adeodato bzr as root? Huh? Sorry, that should have read: do you remember having *run* bzr as root. It's the most likely cause for those .pyc files to be there, since bzrtools did not. Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org The total accumulated knowledge of all the men that ever walked the Earth on the topic of women can fit in the period at the end of this sentence. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Adeodato Sorry, that should have read: do you remember having Adeodato *run* bzr as root. It's the most likely cause for Adeodato those .pyc files to be there, since bzrtools did not. No - I don't recall running bzr as root, nor have I had any reason to do so. This doesn't mean I didn't do it accidently, but I don't think so. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
