Bug#457279: gnarwl: ISPEnv.schema ISPEnv2.schema LICENSE not GPL compliant
Sure. Just take it. Cheers, Cajus Am 08.11.2009 um 01:26 schrieb Barry deFreese : Cajus, Are you OK with me orphaning gnarwl and hopefully Fancesco can take over maintenance? Thank you, Barry deFreese Debian QA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#552010: still not fixed with 2.10.1-3
Processing commands for cont...@bugs.debian.org:
> reopen 552010
Bug #552010 {Done: Aurelien Jarno } [libc6] libc6: After
upgrade many applications become unusable
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552945 pending Bug #552945 [src:van.pydeb] van.pydeb: FTBFS: mv: cannot stat `debian/python-van.pydeb/usr/lib/python2.4/site-packages/van.pydeb-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552010: still not fixed with 2.10.1-3
reopen 552010 thanks After upgrade from 2.9-25 to 2.10.1-5, name resolution breaks if the 'nameserver' option is not present in /etc/resolv.conf: # ping debian.org ping: unknown host debian.org # cat /etc/resolv.conf options ndots:0 # echo nameserver 127.0.0.1 >> /etc/resolv.conf # ping -c 1 debian.org PING debian.org (194.109.137.218) 56(84) bytes of data. 64 bytes from klecker.debian.org (194.109.137.218): icmp_seq=1 ttl=52 time=37.2 ms --- debian.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 37.289/37.289/37.289/0.000 ms # According to resolv.conf(5), the 'nameserver' option is optional and both configurations should be functionally identical: If no nameserver entries are present, the default is to use the name server on the local machine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#545472: Found upstream; #480001
Related to official bug report https://bugzilla.mozilla.org/show_bug.cgi?id=480001 Regards, Raphael
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552971 pending Bug #552971 [src:zc.buildout] zc.buildout: FTBFS: mv: cannot stat `debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc.buildout-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552944 pending Bug #552944 [src:zope.publisher] zope.publisher: FTBFS: mv: cannot stat `debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope.publisher-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552923 pending Bug #552923 [src:zope.testing] zope.testing: FTBFS: mv: cannot stat `debian/python-zope.testing/usr/lib/python2.4/site-packages/zope.testing-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552973 pending Bug #552973 [src:zope.interface] zope.interface: FTBFS: mv: cannot stat `debian/python-zope.interface/usr/lib/python2.4/site-packages/zope.interface-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552979 pending Bug #552979 [src:zope.browser] zope.browser: FTBFS: mv: cannot stat `debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552684 pending Bug #552684 [src:zdaemon] zdaemon: FTBFS: mv: cannot stat `debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552930 pending Bug #552930 [src:zope.schema] zope.schema: FTBFS: mv: cannot stat `debian/python-zope.schema/usr/lib/python2.4/site-packages/zope.schema-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552925 pending Bug #552925 [src:zope.location] zope.location: FTBFS: mv: cannot stat `debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552940 pending Bug #552940 [src:zope.exceptions] zope.exceptions: FTBFS: mv: cannot stat `debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552682 pending Bug #552682 [src:transaction] transaction: FTBFS: mv: cannot stat `debian/python-transaction/usr/lib/python2.4/site-packages/transaction-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552924 pending Bug #552924 [src:zope.authentication] zope.authentication: FTBFS: mv: cannot stat `debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552936 pending Bug #552936 [src:zodb] zodb: FTBFS: mv: cannot stat `debian/python-zodb/usr/lib/python2.4/site-packages/ZODB3-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552941 pending Bug #552941 [src:zope.dottedname] zope.dottedname: FTBFS: mv: cannot stat `debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552929 pending Bug #552929 [src:zope.cachedescriptors] zope.cachedescriptors: FTBFS: mv: cannot stat `debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552935 pending Bug #552935 [src:zope.testbrowser] zope.testbrowser: FTBFS: mv: cannot stat `debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope.testbrowser-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552683 pending Bug #552683 [src:zope.copy] zope.copy: FTBFS: mv: cannot stat `debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552931 pending Bug #552931 [src:zope.component] zope.component: FTBFS: mv: cannot stat `debian/python-zope.component/usr/lib/python2.4/site-packages/zope.component-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552945: marked as done (van.pydeb: FTBFS: mv: cannot stat `debian/python-van.pydeb/usr/lib/python2.4/site-packages/van.pydeb-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 10:17:38 + with message-id and subject line Bug#552945: fixed in van.pydeb 1.3.0-2 has caused the Debian Bug report #552945, regarding van.pydeb: FTBFS: mv: cannot stat `debian/python-van.pydeb/usr/lib/python2.4/site-packages/van.pydeb-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: van.pydeb Version: 1.3.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-van.pydeb_1.3.0-1-amd64-Hk12QB/van.pydeb-1.3.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-van.pydeb > --install-data=usr/lib/python-van.pydeb > running install > running build > running build_py > running egg_info > writing requirements to van.pydeb.egg-info/requires.txt > writing van.pydeb.egg-info/PKG-INFO > writing namespace_packages to van.pydeb.egg-info/namespace_packages.txt > writing top-level names to van.pydeb.egg-info/top_level.txt > writing dependency_links to van.pydeb.egg-info/dependency_links.txt > writing entry points to van.pydeb.egg-info/entry_points.txt > reading manifest file 'van.pydeb.egg-info/SOURCES.txt' > writing manifest file 'van.pydeb.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/__init__.py > (namespace package) > copying van/pydeb/py_to_src.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb > copying van/pydeb/py_to_bin.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb > copying van/pydeb/__init__.py -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb > copying van/pydeb/tests/version.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests > copying van/pydeb/tests/translations.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests > copying van/pydeb/tests/extras.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests > copying van/pydeb/tests/__init__.py -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests > copying van/pydeb/tests/test_doctest.py -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests > copying van/pydeb/tests/zope.security.egg-info/top_level.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/requires.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/not-zip-safe -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/namespace_packages.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/dependency_links.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/SOURCES.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.security.egg-info/PKG-INFO -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.security.egg-info > copying van/pydeb/tests/zope.component.egg-info/top_level.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.component.egg-info > copying van/pydeb/tests/zope.component.egg-info/requires.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.component.egg-info > copying van/pydeb/tests/zope.component.egg-info/not-zip-safe -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.component.egg-info > copying van/pydeb/tests/zope.component.egg-info/namespace_packages.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/van/pydeb/tests/zope.component.egg-info > copying van/pydeb/tests/zope.component.egg-info/dependency_links.txt -> > debian/python-van.pydeb/usr/lib/python2.4/site-packages/v
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552974 pending Bug #552974 [src:zc.lockfile] zc.lockfile: FTBFS: mv: cannot stat `debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552975 pending Bug #552975 [src:zope.configuration] zope.configuration: FTBFS: mv: cannot stat `debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope.configuration-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552928 pending Bug #552928 [src:zope.security] zope.security: FTBFS: mv: cannot stat `debian/python-zope.security/usr/lib/python2.4/site-packages/zope.security-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552919 pending Bug #552919 [src:zope.i18n] zope.i18n: FTBFS: mv: cannot stat `debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope.i18n-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552969 pending Bug #552969 [src:zope.traversing] zope.traversing: FTBFS: mv: cannot stat `debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope.traversing-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552932 pending Bug #552932 [src:zope.hookable] zope.hookable: FTBFS: mv: cannot stat `debian/python-zope.hookable/usr/lib/python2.4/site-packages/zope.hookable-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552978 pending Bug #552978 [src:zope.proxy] zope.proxy: FTBFS: mv: cannot stat `debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552933 pending Bug #552933 [src:zope.i18nmessageid] zope.i18nmessageid: FTBFS: mv: cannot stat `debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552676 pending Bug #552676 [src:zope.sqlalchemy] zope.sqlalchemy: FTBFS: mv: cannot stat `debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552681 pending Bug #552681 [src:zope.event] zope.event: FTBFS: mv: cannot stat `debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552684 pending Bug #552684 [src:zdaemon] zdaemon: FTBFS: mv: cannot stat `debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info': No such file or directory Ignoring request to alter tags of bug #552684 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 552910 pending Bug #552910 [src:zconfig] zconfig: FTBFS: mv: cannot stat `debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig-*-py2.4.egg-info': No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520384: caudium: seeking sponsor for a upload to fix this bug
Quoting Henrik Andreasson (deb...@han.pp.se): > Package: caudium > Followup-For: Bug #520384 > > Hi I've prepared a new version of the caudium package that closes this bug. > My usual sponsor seems unavailabe at the moment. > http://mentors.debian.net/debian/pool/main/c/caudium/caudium_1.4.12-13.dsc Done. signature.asc Description: Digital signature
Bug#553530: marked as done (caudium: dir-or-file-in-var-www var/www/caudiumimages/01.png and 5 others)
Your message dated Sun, 08 Nov 2009 11:02:30 +
with message-id
and subject line Bug#553530: fixed in caudium 3:1.4.12-13
has caused the Debian Bug report #553530,
regarding caudium: dir-or-file-in-var-www var/www/caudiumimages/01.png and 5
others
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
553530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: caudium
Version: 3:1.4.12-12.1
Severity: serious
User: lintian-ma...@debian.org
Usertags: dir-or-file-in-var-www
Debian packages should not install files under /var/www. This is not
one of the /var directories in the File Hierarchy Standard and is
under the control of the local administrator. Packages should not
assume that it is the document root for a web server; it is very
common for users to change the default document root and packages
should not assume that users will keep any particular setting.
Packages that want to make files available via an installed web server
should instead put instructions for the local administrator in a
README.Debian file and ideally include configuration fragments for
common web servers such as Apache.
As an exception, packages are permitted to create the /var/www
directory due to its past history as the default document root, but
should at most copy over a default file in postinst for a new install.
Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for
details.
One solution that works is to put configuration files into
/etc/, put static content, if any, into
/usr/{share,lib}/, then create /var/lib/
as home for the package, and symlink the files from /etc and /usr/
into the /var/lib/. Then create a simple set of
configuration snippets for popular web servers (for example, files one
may link into /etc/apache2/conf.d) and put them into
/etc/. This way user modifiable files stil live in /etc,
and a simple operation can make the package go live.
Filed as serious, since this is a violation of the FHS (which is part
of policy), and also since a package with these files will currently
get this package rejected. See
http://lists.debian.org/debian-devel-announce/2009/10/msg4.html
for details. This means the package has been deemed too buggy to be in
Debian.
manoj
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages caudium depends on:
pn caudium-modules(no description available)
ii cdebconf [debconf-2.0]0.145 Debian Configuration Management Sy
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
pn pike7.6(no description available)
pn pike7.6-core (no description available)
pn pike7.6-image (no description available)
pn pike7.6-pcre (no description available)
ii ttf-dejavu-core 2.30-1 Vera font family derivate with add
Versions of packages caudium recommends:
pn caudium-pixsl (no description available)
pn caudium-ultralog (no description available)
ii mime-support 3.46-1 MIME files 'mime.types' & 'mailcap
Versions of packages caudium suggests:
ii logrotate 3.7.8-4Log rotation utility
pn roxen-doc (no description available)
--- End Message ---
--- Begin Message ---
Source: caudium
Source-Version: 3:1.4.12-13
We believe that the bug you reported is fixed in the latest version of
caudium, which is due to be installed in the Debian FTP archive:
caudium-dev_1.4.12-13_all.deb
to main/c/caudium/caudium-dev_1.4.12-13_all.deb
caudium-modules_1.4.12-13_i386.deb
to main/c/caudium/caudium-modules_1.4.12-13_i386.deb
caudium-perl_1.4.12-13_all.deb
to main/c/caudium/caudium-perl_1.4.12-13_all.deb
caudium-pixsl_1.4.12-13_i386.deb
to main/c/caudium/caudium-pixsl_1.4.12-13_i386.deb
caudium-ultralog_1.4.12-13_i386.deb
to main/c/caudium/caudium-ultralog_1.4.12-13_i386.deb
caudium_1.4.12-13.diff.gz
to main/c/caudium/caudium_1.4.12-13.diff.gz
caudium_1.4.12-13.dsc
to main/c/caudium/caudium_1.4.12-13.dsc
caudium_1.4.12-13_all.deb
to main/c/caudium/caudium_1.4.12-13_all.deb
A summary of the changes between this v
Bug#520384: marked as done (caudium: contains non-free font)
Your message dated Sun, 08 Nov 2009 11:02:29 + with message-id and subject line Bug#520384: fixed in caudium 3:1.4.12-13 has caused the Debian Bug report #520384, regarding caudium: contains non-free font to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 520384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: caudium Version: 3:1.4.12-1 Severity: serious User: pkg-fonts-de...@lists.alioth.debian.org Usertags: non-free X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org Your package contains a non-free font: http://pkg-fonts.alioth.debian.org/review/fnt-20c89e0b1e1aaa6668b1e121d224d4da.html This looks to be from here: http://www.reflectingarea.com/styling/fonts/creators/UtopiaFonts.htm http://www.reflectingarea.com/styling/fonts/creators/UtopiaFonts/FontRedSuit.zip From the zip file: / [utopiafonts] 1998 free font this font is provided free for personal or commercial use, it can be redistributed however it may not be sold. ... \ This licence does not clearly allow all the DFSG-required freedoms: http://www.debian.org/social_contract#guidelines Please contact the font author and ask them to licence the font under a DFSG-compliant font licence such as the OFL: http://scripts.sil.org/OFL http://scripts.sil.org/OFL_web http://scripts.sil.org/OFL-FAQ_web If they are not willing to do so or cannot be contacted, please remove the font from the binary package and the source package and depend on another font package or move the package to non-free. Please contact your upstream and ask them to use fontconfig or similar to get fonts for use by the software instead of using a specific font. This message is brought to you by the Debian Fonts Task Force: http://wiki.debian.org/Fonts -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: caudium Source-Version: 3:1.4.12-13 We believe that the bug you reported is fixed in the latest version of caudium, which is due to be installed in the Debian FTP archive: caudium-dev_1.4.12-13_all.deb to main/c/caudium/caudium-dev_1.4.12-13_all.deb caudium-modules_1.4.12-13_i386.deb to main/c/caudium/caudium-modules_1.4.12-13_i386.deb caudium-perl_1.4.12-13_all.deb to main/c/caudium/caudium-perl_1.4.12-13_all.deb caudium-pixsl_1.4.12-13_i386.deb to main/c/caudium/caudium-pixsl_1.4.12-13_i386.deb caudium-ultralog_1.4.12-13_i386.deb to main/c/caudium/caudium-ultralog_1.4.12-13_i386.deb caudium_1.4.12-13.diff.gz to main/c/caudium/caudium_1.4.12-13.diff.gz caudium_1.4.12-13.dsc to main/c/caudium/caudium_1.4.12-13.dsc caudium_1.4.12-13_all.deb to main/c/caudium/caudium_1.4.12-13_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 520...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henrik Andreasson (supplier of updated caudium package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 02 Nov 2009 22:42:25 +0100 Source: caudium Binary: caudium caudium-modules caudium-pixsl caudium-ultralog caudium-dev caudium-perl Architecture: source i386 all Version: 3:1.4.12-13 Distribution: unstable Urgency: low Maintainer: Henrik Andreasson Changed-By: Henrik Andreasson Description: caudium- An extensible WWW server written in Pike caudium-dev - Development files for Caudium caudium-modules - C modules for Caudium caudium-perl - Perl script support for Caudium caudium-pixsl - Pike XSLT module for Caudium caudium-ultralog - Log Parser module for Caudium Closes: 520384 528290 553530 554037 Changes: caudium (3:1.4.12-13) unstable; urgency=low . * rename getline function Closes: #554037 #552857 * Removal of non-free fontrstc Closes: #520384 * move default caudium sample www-root to /usr/share/caudium/www/ Closes: #553530 * fixed the vcs url Closes: #528290 Checksums-Sha1: ce4fd312935a4e84c8c2ab7f416a4e818de958ba 1335 caudium_1.4.12-1
Bug#554037: marked as done ([caudium] FTBFS due to multiple declaration of getline)
Your message dated Sun, 08 Nov 2009 11:02:30 + with message-id and subject line Bug#554037: fixed in caudium 3:1.4.12-13 has caused the Debian Bug report #554037, regarding [caudium] FTBFS due to multiple declaration of getline to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 554037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: caudium Version: 3:1.4.12-12.1 Severity: serious Build in current unstable /home/peter/rebuild/build/caudium/caudium-1.4.12/src/tools/../..//smartlink /home/peter/rebuild/build/caudium/caudium-1.4.12/smartlink x86_64-linux-gnu-gcc -fPIC -s -I./ -I. -o htpasswd ./htpasswd.c - lcrypt In file included from ./htpasswd.c:25: ./htpasswd.h:5: error: conflicting types for 'getline' /usr/include/stdio.h:651: error: previous declaration of 'getline' was here ./htpasswd.c:56: error: conflicting types for 'getline' /usr/include/stdio.h:651: error: previous declaration of 'getline' was here make[3]: [htpasswd] Error 1 (ignored) --- End Message --- --- Begin Message --- Source: caudium Source-Version: 3:1.4.12-13 We believe that the bug you reported is fixed in the latest version of caudium, which is due to be installed in the Debian FTP archive: caudium-dev_1.4.12-13_all.deb to main/c/caudium/caudium-dev_1.4.12-13_all.deb caudium-modules_1.4.12-13_i386.deb to main/c/caudium/caudium-modules_1.4.12-13_i386.deb caudium-perl_1.4.12-13_all.deb to main/c/caudium/caudium-perl_1.4.12-13_all.deb caudium-pixsl_1.4.12-13_i386.deb to main/c/caudium/caudium-pixsl_1.4.12-13_i386.deb caudium-ultralog_1.4.12-13_i386.deb to main/c/caudium/caudium-ultralog_1.4.12-13_i386.deb caudium_1.4.12-13.diff.gz to main/c/caudium/caudium_1.4.12-13.diff.gz caudium_1.4.12-13.dsc to main/c/caudium/caudium_1.4.12-13.dsc caudium_1.4.12-13_all.deb to main/c/caudium/caudium_1.4.12-13_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 554...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henrik Andreasson (supplier of updated caudium package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 02 Nov 2009 22:42:25 +0100 Source: caudium Binary: caudium caudium-modules caudium-pixsl caudium-ultralog caudium-dev caudium-perl Architecture: source i386 all Version: 3:1.4.12-13 Distribution: unstable Urgency: low Maintainer: Henrik Andreasson Changed-By: Henrik Andreasson Description: caudium- An extensible WWW server written in Pike caudium-dev - Development files for Caudium caudium-modules - C modules for Caudium caudium-perl - Perl script support for Caudium caudium-pixsl - Pike XSLT module for Caudium caudium-ultralog - Log Parser module for Caudium Closes: 520384 528290 553530 554037 Changes: caudium (3:1.4.12-13) unstable; urgency=low . * rename getline function Closes: #554037 #552857 * Removal of non-free fontrstc Closes: #520384 * move default caudium sample www-root to /usr/share/caudium/www/ Closes: #553530 * fixed the vcs url Closes: #528290 Checksums-Sha1: ce4fd312935a4e84c8c2ab7f416a4e818de958ba 1335 caudium_1.4.12-13.dsc fcad52c38b2e4f428edf515b251a4f768578d28b 83553 caudium_1.4.12-13.diff.gz c7ecd4d7d4ec190f19475664fce47515f28ce982 226906 caudium-modules_1.4.12-13_i386.deb 429e9ecc6bbe3d8d925571a418f2bf9a2f3fa299 203696 caudium-pixsl_1.4.12-13_i386.deb f4f87fd1b02303e8c5aeff503ec0c2565a9cd714 239088 caudium-ultralog_1.4.12-13_i386.deb 10d3f0e397adde30abc6a2eb74ba17c1d766bf41 2717876 caudium_1.4.12-13_all.deb c92f669c21f969c8bfd4158bc6b7de74d67ef22a 236424 caudium-dev_1.4.12-13_all.deb 25ca03abd0b3e3397eb3d247c17cb3436f2f28da 196614 caudium-perl_1.4.12-13_all.deb Checksums-Sha256: 6f6d7a94d0486f6f47b2ed497060fe26411107ca84c6e2c4dca1f0241aa80428 1335 caudium_1.4.12-13.dsc 8efd1b4a3b2a317d3d933b4039b57d164684c845c09b387654cb417dab218da7 83553 caudium_1.4.12-13.diff.gz 8255e6b06fca4c66428cbd498ad4d322b1b3cc3b3a290edcf2be35d50e7f35d0 226906 caudium-modules_1.4.12-13_i386.deb f5cb5f5ece9bbb81fef7ab956c7c8cd0464710b50c0760892f88b4f546baea36 203696 caudium-pixsl_1.4.12-13_i386.deb 6f53a377e12ab2e4bda287c979ba7be5db9025c01cfe6832a13
Processed (with 1 errors): Re: eclipse: FTBFS - native libraries are not built from source.
Processing commands for cont...@bugs.debian.org:
> forcemerge 553131 553133
Bug#553131: libswt3.4-gtk-jni: missing-dependency-on-libc needed by
./usr/lib/jni/libswt-atk-gtk-3449.so and 7 others but the package
doesn't depend on the C library package. Normally this indicates
that ${shlibs: Depends} was omitted from the Depends line for
this package in debian/control.
Bug#553133: eclipse-rcp: missing-dependency-on-libc needed by
./usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1115.so
but the package doesn't depend on the C library package.
Normally this indicates that ${shlibs: Depends} was omitted from
the Depends line for this package in debian/control.
Mismatch - only Bugs in the same package can be forcibly merged:
Bug 553133 is not in the same package as 553131
> retitle 553131 eclipse: FTBFS - native libraries are not built from source.
Bug #553131 [libswt3.4-gtk-jni] libswt3.4-gtk-jni: missing-dependency-on-libc
needed by ./usr/lib/jni/libswt-atk-gtk-3449.so and 7 others but
the package doesn't depend on the C library package. Normally
this indicates that ${shlibs: Depends} was omitted from the
Depends line for this package in debian/control.
Changed Bug title to 'eclipse: FTBFS - native libraries are not built from
source.' from 'libswt3.4-gtk-jni: missing-dependency-on-libc needed by
./usr/lib/jni/libswt-atk-gtk-3449.so and 7 others but the package
doesn't depend on the C library package. Normally this indicates
that ${shlibs: Depends} was omitted from the Depends line for
this package in debian/control.'
> tags 553131 = confirmed
Bug #553131 [libswt3.4-gtk-jni] eclipse: FTBFS - native libraries are not built
from source.
Added tag(s) confirmed.
> reassign 553131 src:eclipse
Bug #553131 [libswt3.4-gtk-jni] eclipse: FTBFS - native libraries are not built
from source.
Bug reassigned from package 'libswt3.4-gtk-jni' to 'src:eclipse'.
Bug No longer marked as found in versions eclipse/3.4.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553131: eclipse: FTBFS - native libraries are not built from source.
forcemerge 553131 553133 retitle 553131 eclipse: FTBFS - native libraries are not built from source. tags 553131 = confirmed reassign 553131 src:eclipse thanks Hi It turns out (by looking at the build logs) that this is caused by the 3.4.1 build passing a misspelled path to dpkg-shlibdeps. I have tried to rebuild eclipse 3.4.1 with the correct path but it breaks the x86 build because (as the title suggests) these files are apparently not built from source. The libraries appears to have been build on a amd64 and (based on the feed back of users) eclipse have no issue with this. I have not been able to figure out why it fails to rebuilt them in 3.4.1; nevertheless I am more focused on bringing 3.5.1 into Debian which (unlike a fix of 3.4.1) will close all of the currently filed RC bugs[1]. I could upload an eclipse 3.5.1 now to the archive but it would suffer from a "FTBFS/uses convenience sources", which is why I have not done it. To anyone considering to NMU this package - be my guest, but your time is probably better spent on other packages or helping us getting 3.5.1 done. The upstream build system is not exactly "easy" to understand nor work with. Furthermore, as I recall eclipse 3.4.1 does not support xulrunner 1.9.1 so you would have to disable that as well. This is (one of the) reason(s) to #507536 (and its 5-6 duplicates). If you feel that this package is too RC buggy to be in unstable feel free to request an RM from unstable - I would prefer you did not[2], but on the other hand having 5 unique RC bugs is pushing it and therefore I cannot really object to a RM request. ~Niels [1] That being (besides this/these): #507536 - eclipse: fails to start due to xulrunner - workaround; disable welcome screen. #521312 - eclipse: Eclipse fails to start on SPARC64 #552480 - eclipse: GTK dialog stopped working #554584 - eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build The four above plus this/these are already fixed in our VCS: http://git.debian.org/?p=pkg-java/eclipse.git [2] There are some bugs non-RC bugs on the BTS that will not be fixed in the next upload and I would prefer not to have to reopen those and explain what happens to the submitters. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555087: [courier-mta] courier-mta does not install on clean squeeze system
Package: courier-mta Version: 0.59.0-3 Severity: serious --- Please enter the report below this line. --- When performing apt-get install courier-mta on an otherwise clean squeeze system, dpkg fails with an post-install script error in package courier-mta. Installing the lenny package and dist-upgrading to squeeze is however working. The error occurs with either bash or dash as /bin/sh. My system is using legacy init scripts. Please note that the squeeze system is running inside a vserver-environment on a lenny i386 machine. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: forcemerge 553131 and 553133
Processing commands for cont...@bugs.debian.org:
> reassign 553133 src:eclipse
Bug #553133 [eclipse-rcp] eclipse-rcp: missing-dependency-on-libc needed by
./usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1115.so
but the package doesn't depend on the C library package.
Normally this indicates that ${shlibs: Depends} was omitted from
the Depends line for this package in debian/control.
Bug reassigned from package 'eclipse-rcp' to 'src:eclipse'.
Bug No longer marked as found in versions eclipse/3.4.1-1.
> # The order is intentional.
> forcemerge 553131 553133
Bug#553131: eclipse: FTBFS - native libraries are not built from source.
Bug#553133: eclipse-rcp: missing-dependency-on-libc needed by
./usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1115.so
but the package doesn't depend on the C library package.
Normally this indicates that ${shlibs: Depends} was omitted from
the Depends line for this package in debian/control.
Forcibly Merged 553131 553133.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: affects 545600
Processing commands for cont...@bugs.debian.org: > affects 545600 freej Bug #545600 [libcv-dev] freej: FTBFS: cxtypes.h:144: error: conflicting declaration 'typedef long long int int64' Added indication that 545600 affects freej > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): severity of 543546 is serious, merging 543546 545600
Processing commands for cont...@bugs.debian.org: > severity 543546 serious Bug #543546 [libcv-dev] libcv-dev: bad int64 definition makes it impossible to use with mozjs Severity set to 'serious' from 'important' > merge 543546 545600 Bug#543546: libcv-dev: bad int64 definition makes it impossible to use with mozjs Bug#545600: freej: FTBFS: cxtypes.h:144: error: conflicting declaration 'typedef long long int int64' Mismatch - only Bugs in same state can be merged: Values for `affects' don't match: #543546 has `'; #545600 has `freej' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554871: marked as done (ocaml: FTBFS: unit Includecore exported in ocaml-compiler-libs but already exported by ocaml-nox/ocaml-base-nox)
Your message dated Sun, 08 Nov 2009 12:01:40 + with message-id and subject line Bug#554871: fixed in ocaml 3.11.1-4 has caused the Debian Bug report #554871, regarding ocaml: FTBFS: unit Includecore exported in ocaml-compiler-libs but already exported by ocaml-nox/ocaml-base-nox to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 554871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ocaml Version: 3.11.1-3 Severity: serious From my pbuilder build log: ... # Create .md5sums files and compute dependencies. Use # 3.11.1 because we know that OCaml ABI represents # best dependencies for OCaml package. dh_ocaml \ --runtime-map ocaml-nox:ocaml-base-nox,ocaml:ocaml-base,camlp4 \ --checksum 3.11.1 W: camlp4 v3.11.1-3 doesn't resolve dependency on unit Annot W: camlp4 v3.11.1-3 doesn't resolve dependency on unit Mkcamlp4 W: camlp4 v3.11.1-3 doesn't resolve dependency on unit Asttypes ... W: ocaml/ocaml-base v3.11.1-3 doesn't resolve dependency on unit Asttypes W: ocaml/ocaml-base v3.11.1-3 doesn't resolve dependency on unit Parsetree W: camlp4-extra doesn't resolve dependency on unit Annot E: Error: unit Includecore exported in ocaml-compiler-libs but already exported by ocaml-nox/ocaml-base-nox v3.11.1-3 E: Error running /usr/bin/ocaml-md5sums --checksum 3.11.1 --md5sums-dir debian/camlp4//var/lib/ocaml/md5sums --md5sums-dir debian/ocaml-nox//var/lib/ocaml/md5sums --md5sums-dir debian/ocaml//var/lib/ocaml/md5sums -- package ocaml-compiler-libs dep < debian/ocaml-compiler-libs.olist.debhelper at /usr/bin/dh_ocaml line 476. make: *** [binary-stamp] Error 255 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- Source: ocaml Source-Version: 3.11.1-4 We believe that the bug you reported is fixed in the latest version of ocaml, which is due to be installed in the Debian FTP archive: camlp4-extra_3.11.1-4_amd64.deb to main/o/ocaml/camlp4-extra_3.11.1-4_amd64.deb camlp4_3.11.1-4_amd64.deb to main/o/ocaml/camlp4_3.11.1-4_amd64.deb ocaml-base-nox_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-base-nox_3.11.1-4_amd64.deb ocaml-base_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-base_3.11.1-4_amd64.deb ocaml-compiler-libs_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-compiler-libs_3.11.1-4_amd64.deb ocaml-interp_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-interp_3.11.1-4_amd64.deb ocaml-mode_3.11.1-4_all.deb to main/o/ocaml/ocaml-mode_3.11.1-4_all.deb ocaml-native-compilers_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-native-compilers_3.11.1-4_amd64.deb ocaml-nox_3.11.1-4_amd64.deb to main/o/ocaml/ocaml-nox_3.11.1-4_amd64.deb ocaml-source_3.11.1-4_all.deb to main/o/ocaml/ocaml-source_3.11.1-4_all.deb ocaml_3.11.1-4.diff.gz to main/o/ocaml/ocaml_3.11.1-4.diff.gz ocaml_3.11.1-4.dsc to main/o/ocaml/ocaml_3.11.1-4.dsc ocaml_3.11.1-4_amd64.deb to main/o/ocaml/ocaml_3.11.1-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 554...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Nov 2009 02:49:50 +0100 Source: ocaml Binary: ocaml-nox camlp4 camlp4-extra ocaml ocaml-base-nox ocaml-base ocaml-native-compilers ocaml-source ocaml-interp ocaml-compiler-libs ocaml-mode Architecture: source amd64 all Version: 3.11.1-4 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Description: camlp4 - Pre Processor Pretty Printer for OCaml camlp4-extra - Pre Processor Pretty Printer for OCaml - extras ocaml - ML language implementation with a class-based object system ocaml-base - Runtime system for OCaml bytecode executables ocaml-base-nox - Runtime system for OC
Processed: Re: Bug#552480: eclipse: GTK dialog stopped working
Processing commands for cont...@bugs.debian.org: > tags 552480 = confirmed Bug #552480 [eclipse] eclipse: GTK dialog stopped working Added tag(s) confirmed; removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Merge 554584 + 476067 and retitle eclipse: FTBFS: timeout during build (on various archs)
Processing commands for cont...@bugs.debian.org: > reassign 554584 src:eclipse Bug #554584 [eclipse] eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build Bug reassigned from package 'eclipse' to 'src:eclipse'. Bug No longer marked as found in versions eclipse/3.4.1-1. > reassign 476067 src:eclipse Bug #476067 [eclipse] eclipse: FTBFS: build takes a very, very long time (or just blocks?) Bug reassigned from package 'eclipse' to 'src:eclipse'. Bug No longer marked as found in versions eclipse/3.2.2-5. > forcemerge 554584 476067 Bug#554584: eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build Bug#476067: eclipse: FTBFS: build takes a very, very long time (or just blocks?) Forcibly Merged 476067 554584. > found 554584 3.4.1-1,3.2.2-5 Bug #554584 [src:eclipse] eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build Bug #476067 [src:eclipse] eclipse: FTBFS: build takes a very, very long time (or just blocks?) Bug Marked as found in versions eclipse/3.2.2-5 and eclipse/3.4.1-1. Bug Marked as found in versions eclipse/3.2.2-5 and eclipse/3.4.1-1. > retitle 554584 eclipse: FTBFS: timeout during build (on various archs) Bug #554584 [src:eclipse] eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build Bug #476067 [src:eclipse] eclipse: FTBFS: build takes a very, very long time (or just blocks?) Changed Bug title to 'eclipse: FTBFS: timeout during build (on various archs)' from 'eclipse_3.4.1-1(ia64/unstable): FTBFS: timeout during build' Changed Bug title to 'eclipse: FTBFS: timeout during build (on various archs)' from 'eclipse: FTBFS: build takes a very, very long time (or just blocks?)' > tags = 554584 confirmed Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552480: eclipse: GTK dialog stopped working
tags 552480 = confirmed thanks Hi Thanks for testing it - this is a known problem then and we have partly fixed it in our VCS[1] and it will be fixed by upstream in eclipse 3.6 (and possibly also 3.5.2). ~Niels [1] Partly fixed as in our VCS version suffers from fewer of these problems than the upstream version; however we will be using the env variable as a workaround until it is fixed upstream (or we get them all back-ported). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552682: marked as done (transaction: FTBFS: mv: cannot stat `debian/python-transaction/usr/lib/python2.4/site-packages/transaction-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:48:25 + with message-id and subject line Bug#552682: fixed in transaction 1.0.0-3 has caused the Debian Bug report #552682, regarding transaction: FTBFS: mv: cannot stat `debian/python-transaction/usr/lib/python2.4/site-packages/transaction-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: transaction Version: 1.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-transaction_1.0.0-2-amd64-Ga99S7/transaction-1.0.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-transaction > --install-data=usr/lib/python-transaction > running install > running build > running build_py > running egg_info > writing requirements to transaction.egg-info/requires.txt > writing transaction.egg-info/PKG-INFO > writing top-level names to transaction.egg-info/top_level.txt > writing dependency_links to transaction.egg-info/dependency_links.txt > writing entry points to transaction.egg-info/entry_points.txt > reading manifest file 'transaction.egg-info/SOURCES.txt' > writing manifest file 'transaction.egg-info/SOURCES.txt' > running install_lib > creating debian/python-transaction/usr > creating debian/python-transaction/usr/lib > creating debian/python-transaction/usr/lib/python2.4 > creating debian/python-transaction/usr/lib/python2.4/site-packages > creating debian/python-transaction/usr/lib/python2.4/site-packages/transaction > creating > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/savepoint.txt -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/doom.txt -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_savepoint.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_SampleDataManager.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_weakset.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_register_compat.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/sampledm.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/savepointsample.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/warnhook.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_transaction.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/__init__.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/tests/test_SampleResourceManager.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction/tests > copying build/lib/transaction/weakset.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction > copying build/lib/transaction/interfaces.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction > copying build/lib/transaction/_transaction.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction > copying build/lib/transaction/_manager.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction > copying build/lib/transaction/__init__.py -> > debian/python-transaction/usr/lib/python2.4/site-packages/transaction > running install_egg_info > Copying transaction.egg-info to > debian/python-transaction/usr/lib/python2.4/site-packages/transaction-1.0.0.egg-info > running install_scripts > mv > debian/python-transaction/usr/lib/python2.4/site-packages/transaction-*-py2.4.egg-info > \ > > debian/python-transaction/usr/lib/python2.4/site-packages/transaction.egg-info > > mv: cannot stat >
Bug#552931: marked as done (zope.component: FTBFS: mv: cannot stat `debian/python-zope.component/usr/lib/python2.4/site-packages/zope.component-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:49:54 + with message-id and subject line Bug#552931: fixed in zope.component 3.7.1-5 has caused the Debian Bug report #552931, regarding zope.component: FTBFS: mv: cannot stat `debian/python-zope.component/usr/lib/python2.4/site-packages/zope.component-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.component Version: 3.7.1-4 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.component_3.7.1-4-amd64-y0piIs/zope.component-3.7.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.component > --install-data=usr/lib/python-zope.component > running install > running build > running build_py > running egg_info > writing requirements to src/zope.component.egg-info/requires.txt > writing src/zope.component.egg-info/PKG-INFO > writing namespace_packages to > src/zope.component.egg-info/namespace_packages.txt > writing top-level names to src/zope.component.egg-info/top_level.txt > writing dependency_links to src/zope.component.egg-info/dependency_links.txt > reading manifest file 'src/zope.component.egg-info/SOURCES.txt' > writing manifest file 'src/zope.component.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/component/zcml.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/socketexample.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/registry.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/persistentregistry.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/meta.zcml -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/index.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/factory.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/event.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/configure.zcml -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/README.txt -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/_declaration.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/standalonetests.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/_api.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/interface.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/globalregistry.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/persistentregistry.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/nexttesting.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/registry.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/testing.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/interfaces.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/event.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/factory.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/zcml.py -> > debian/python-zope.component/usr/lib/python2.4/site-packages/zope/component > copying zope/component/hookable.py ->
Bug#552979: marked as done (zope.browser: FTBFS: mv: cannot stat `debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:49:34 + with message-id and subject line Bug#552979: fixed in zope.browser 1.2-3 has caused the Debian Bug report #552979, regarding zope.browser: FTBFS: mv: cannot stat `debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.browser Version: 1.2-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.browser_1.2-2-amd64-3LcuRA/zope.browser-1.2' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.browser > --install-data=usr/lib/python-zope.browser > running install > running build > running build_py > running egg_info > writing requirements to src/zope.browser.egg-info/requires.txt > writing src/zope.browser.egg-info/PKG-INFO > writing namespace_packages to src/zope.browser.egg-info/namespace_packages.txt > writing top-level names to src/zope.browser.egg-info/top_level.txt > writing dependency_links to src/zope.browser.egg-info/dependency_links.txt > reading manifest file 'src/zope.browser.egg-info/SOURCES.txt' > writing manifest file 'src/zope.browser.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/browser/README.txt -> > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope/browser > copying zope/browser/__init__.py -> > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope/browser > copying zope/browser/interfaces.py -> > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope/browser > copying zope/browser/tests.py -> > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope/browser > running install_egg_info > Copying src/zope.browser.egg-info to > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-1.2.egg-info > Installing > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-1.2-nspkg.pth > running install_scripts > mv > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-*-py2.4.egg-info > \ > > debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser.egg-info > > mv: cannot stat > `debian/python-zope.browser/usr/lib/python2.4/site-packages/zope.browser-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.browser_1.2-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.browser Source-Version: 1.2-3 We believe that the bug you reported is fixed in the latest version of zope.browser, which is due to be installed in the Debian FTP archive: python-zope.browser_1.2-3_all.deb to main/z/zope.browser/python-zope.browser_1.2-3_all.deb zope.browser_1.2-3.diff.gz to main/z/zope.browser/zope.browser_1.2-3.diff.gz zope.browser_1.2-3.dsc to main/z/zope.browser/zope.browser_1.2-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.browser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Nov 2009 11:21:1
Bug#552929: marked as done (zope.cachedescriptors: FTBFS: mv: cannot stat `debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-*-py2.4.egg-info': No such file or
Your message dated Sun, 08 Nov 2009 12:49:43 + with message-id and subject line Bug#552929: fixed in zope.cachedescriptors 3.5.0-3 has caused the Debian Bug report #552929, regarding zope.cachedescriptors: FTBFS: mv: cannot stat `debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.cachedescriptors Version: 3.5.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.cachedescriptors_3.5.0-2-amd64-b6yN5c/zope.cachedescriptors-3.5.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.cachedescriptors > --install-data=usr/lib/python-zope.cachedescriptors > running install > running build > running build_py > running egg_info > writing requirements to src/zope.cachedescriptors.egg-info/requires.txt > writing src/zope.cachedescriptors.egg-info/PKG-INFO > writing namespace_packages to > src/zope.cachedescriptors.egg-info/namespace_packages.txt > writing top-level names to src/zope.cachedescriptors.egg-info/top_level.txt > writing dependency_links to > src/zope.cachedescriptors.egg-info/dependency_links.txt > reading manifest file 'src/zope.cachedescriptors.egg-info/SOURCES.txt' > writing manifest file 'src/zope.cachedescriptors.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/cachedescriptors/property.txt -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/method.txt -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/README.txt -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/property.py -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/tests.py -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/method.py -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > copying zope/cachedescriptors/__init__.py -> > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope/cachedescriptors > running install_egg_info > Copying src/zope.cachedescriptors.egg-info to > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-3.5.0.egg-info > Installing > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-3.5.0-nspkg.pth > running install_scripts > mv > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-*-py2.4.egg-info > \ > > debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors.egg-info > > mv: cannot stat > `debian/python-zope.cachedescriptors/usr/lib/python2.4/site-packages/zope.cachedescriptors-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.cachedescriptors_3.5.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.cachedescriptors Source-Version: 3.5.0-3 We believe that the bug you reported is fixed in the latest version of zope.cachedescriptors, which is due to be installed in the Debian FTP archive: python-zope.cachedescriptors_3.5.0-3_all.deb to main/z/zope.cachedescriptors/pytho
Bug#552683: marked as done (zope.copy: FTBFS: mv: cannot stat `debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:50:14 + with message-id and subject line Bug#552683: fixed in zope.copy 3.5.0-3 has caused the Debian Bug report #552683, regarding zope.copy: FTBFS: mv: cannot stat `debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.copy Version: 3.5.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.copy_3.5.0-2-amd64-sVG6Lr/zope.copy-3.5.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.copy > --install-data=usr/lib/python-zope.copy > running install > running build > running build_py > running egg_info > writing requirements to src/zope.copy.egg-info/requires.txt > writing src/zope.copy.egg-info/PKG-INFO > writing namespace_packages to src/zope.copy.egg-info/namespace_packages.txt > writing top-level names to src/zope.copy.egg-info/top_level.txt > writing dependency_links to src/zope.copy.egg-info/dependency_links.txt > reading manifest file 'src/zope.copy.egg-info/SOURCES.txt' > writing manifest file 'src/zope.copy.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/copy/README.txt -> > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope/copy > copying zope/copy/tests.py -> > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope/copy > copying zope/copy/interfaces.py -> > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope/copy > copying zope/copy/__init__.py -> > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope/copy > running install_egg_info > Copying src/zope.copy.egg-info to > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-3.5.0.egg-info > Installing > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-3.5.0-nspkg.pth > running install_scripts > mv > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-*-py2.4.egg-info > \ > > debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy.egg-info > mv: cannot stat > `debian/python-zope.copy/usr/lib/python2.4/site-packages/zope.copy-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.copy_3.5.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.copy Source-Version: 3.5.0-3 We believe that the bug you reported is fixed in the latest version of zope.copy, which is due to be installed in the Debian FTP archive: python-zope.copy_3.5.0-3_all.deb to main/z/zope.copy/python-zope.copy_3.5.0-3_all.deb zope.copy_3.5.0-3.diff.gz to main/z/zope.copy/zope.copy_3.5.0-3.diff.gz zope.copy_3.5.0-3.dsc to main/z/zope.copy/zope.copy_3.5.0-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.copy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Nov 2009 11:04:16 +0100 Source: zope.copy Binary: python-zope.copy Architecture: source all Version: 3.5.0-3 Distribution: unstable Urgency: low Mainta
Bug#552930: marked as done (zope.schema: FTBFS: mv: cannot stat `debian/python-zope.schema/usr/lib/python2.4/site-packages/zope.schema-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:00 + with message-id and subject line Bug#552930: fixed in zope.schema 3.5.4-6 has caused the Debian Bug report #552930, regarding zope.schema: FTBFS: mv: cannot stat `debian/python-zope.schema/usr/lib/python2.4/site-packages/zope.schema-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.schema Version: 3.5.4-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.schema_3.5.4-5-amd64-4oYX5E/zope.schema-3.5.4' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.schema > --install-data=usr/lib/python-zope.schema > running install > running build > running build_py > running egg_info > writing requirements to src/zope.schema.egg-info/requires.txt > writing src/zope.schema.egg-info/PKG-INFO > writing namespace_packages to src/zope.schema.egg-info/namespace_packages.txt > writing top-level names to src/zope.schema.egg-info/top_level.txt > writing dependency_links to src/zope.schema.egg-info/dependency_links.txt > reading manifest file 'src/zope.schema.egg-info/SOURCES.txt' > writing manifest file 'src/zope.schema.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/schema/validation.txt -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/sources.txt -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/index.txt -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/fields.txt -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/README.txt -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/__init__.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/_bootstrapfields.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/_bootstrapinterfaces.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/_field.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/_schema.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/accessors.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/fieldproperty.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/interfaces.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/vocabulary.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema > copying zope/schema/tests/__init__.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/states.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_accessors.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_boolfield.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_choice.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_containerfield.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_date.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_datetime.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_decimalfield.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test_dictfield.py -> > debian/python-zope.schema/usr/lib/python2.4/site-packages/zope/schema/tests > copying zope/schema/tests/test
Bug#552681: marked as done (zope.event: FTBFS: mv: cannot stat `debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:50:33 + with message-id and subject line Bug#552681: fixed in zope.event 3.4.1-5 has caused the Debian Bug report #552681, regarding zope.event: FTBFS: mv: cannot stat `debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.event Version: 3.4.1-4 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.event_3.4.1-4-amd64-tPDVNn/zope.event-3.4.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.event > --install-data=usr/lib/python-zope.event > running install > running build > running build_py > running egg_info > writing requirements to src/zope.event.egg-info/requires.txt > writing src/zope.event.egg-info/PKG-INFO > writing namespace_packages to src/zope.event.egg-info/namespace_packages.txt > writing top-level names to src/zope.event.egg-info/top_level.txt > writing dependency_links to src/zope.event.egg-info/dependency_links.txt > reading manifest file 'src/zope.event.egg-info/SOURCES.txt' > writing manifest file 'src/zope.event.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.event/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/event/README.txt -> > debian/python-zope.event/usr/lib/python2.4/site-packages/zope/event > copying zope/event/tests.py -> > debian/python-zope.event/usr/lib/python2.4/site-packages/zope/event > copying zope/event/__init__.py -> > debian/python-zope.event/usr/lib/python2.4/site-packages/zope/event > running install_egg_info > Copying src/zope.event.egg-info to > debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-3.4.1.egg-info > Installing > debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-3.4.1-nspkg.pth > running install_scripts > mv > debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-*-py2.4.egg-info > \ > > debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event.egg-info > mv: cannot stat > `debian/python-zope.event/usr/lib/python2.4/site-packages/zope.event-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.event_3.4.1-4_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.event Source-Version: 3.4.1-5 We believe that the bug you reported is fixed in the latest version of zope.event, which is due to be installed in the Debian FTP archive: python-zope.event_3.4.1-5_all.deb to main/z/zope.event/python-zope.event_3.4.1-5_all.deb zope.event_3.4.1-5.diff.gz to main/z/zope.event/zope.event_3.4.1-5.diff.gz zope.event_3.4.1-5.dsc to main/z/zope.event/zope.event_3.4.1-5.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.event package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Nov 2009 11:25:19 +0100 Source: zope.event Binary: python-zope.event Architecture: source all Version: 3.4.1-5 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team Changed-By: Fabio Tran
Bug#552932: marked as done (zope.hookable: FTBFS: mv: cannot stat `debian/python-zope.hookable/usr/lib/python2.4/site-packages/zope.hookable-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:50:51 + with message-id and subject line Bug#552932: fixed in zope.hookable 3.4.1-4 has caused the Debian Bug report #552932, regarding zope.hookable: FTBFS: mv: cannot stat `debian/python-zope.hookable/usr/lib/python2.4/site-packages/zope.hookable-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.hookable Version: 3.4.1-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.hookable_3.4.1-3-amd64-0_Lc6U/zope.hookable-3.4.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.hookable > --install-data=usr/lib/python-zope.hookable > running install > running build > running build_py > running egg_info > writing requirements to src/zope.hookable.egg-info/requires.txt > writing src/zope.hookable.egg-info/PKG-INFO > writing namespace_packages to > src/zope.hookable.egg-info/namespace_packages.txt > writing top-level names to src/zope.hookable.egg-info/top_level.txt > writing dependency_links to src/zope.hookable.egg-info/dependency_links.txt > mv: cannot stat > `debian/python-zope.hookable/usr/lib/python2.4/site-packages/zope.hookable-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.hookable_3.4.1-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.hookable Source-Version: 3.4.1-4 We believe that the bug you reported is fixed in the latest version of zope.hookable, which is due to be installed in the Debian FTP archive: python-zope.hookable_3.4.1-4_amd64.deb to main/z/zope.hookable/python-zope.hookable_3.4.1-4_amd64.deb zope.hookable_3.4.1-4.diff.gz to main/z/zope.hookable/zope.hookable_3.4.1-4.diff.gz zope.hookable_3.4.1-4.dsc to main/z/zope.hookable/zope.hookable_3.4.1-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.hookable package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Nov 2009 11:24:52 +0100 Source: zope.hookable Binary: python-zope.hookable Architecture: source amd64 Version: 3.4.1-4 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team Changed-By: Fabio Tranchitella Description: python-zope.hookable - Hookable object support Closes: 552932 Changes: zope.hookable (3.4.1-4) unstable; urgency=low . * debian/control: build-depend on pyton-vab.pydeb >= 1.3.0-2. (Closes: #552932) Checksums-Sha1: 898d2f49ed0ffbaa0b32420c2f769e1028a2e229 1322 zope.hookable_3.4.1-4.dsc e291a51c99b5ad9d1ea3bd60054ae228d5345578 2687 zope.hookable_3.4.1-4.diff.gz e0f7218ac5a2f887760be7bfb4d5336af1a91314 10864 python-zope.hookable_3.4.1-4_amd64.deb Checksums-Sha256: f2dddf15bc41a474e564a2e103dbf8bb0450c5f975249a2363e04ee1bbfdeead 1322 zope.hookable_3.4.1-4.dsc 18f74d1cb335bf7000be3c1ac26c93a2dc32cd55d6f84aaceb946dd85479606c 2687 zope.hookable_3.4.1-4.diff.gz cf6df1b0fbfc3fa32cde38c569537e39bec3880cceb6aa593b6dacc664b05a0e 10864 python-zope.hookable_3.4.1-4_amd64.deb Files: 95fa64aee286fb2ab5369430cc90c539 1322 zope extra zope.hookable_3.4.1-4.dsc 865612cf61a213168e938a750e8b623c 2687 zope extr
Bug#552941: marked as done (zope.dottedname: FTBFS: mv: cannot stat `debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:50:23 + with message-id and subject line Bug#552941: fixed in zope.dottedname 3.4.6-2 has caused the Debian Bug report #552941, regarding zope.dottedname: FTBFS: mv: cannot stat `debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.dottedname Version: 3.4.6-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.dottedname_3.4.6-1-amd64-d3MsVA/zope.dottedname-3.4.6' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.dottedname > --install-data=usr/lib/python-zope.dottedname > running install > running build > running build_py > running egg_info > writing requirements to src/zope.dottedname.egg-info/requires.txt > writing src/zope.dottedname.egg-info/PKG-INFO > writing namespace_packages to > src/zope.dottedname.egg-info/namespace_packages.txt > writing top-level names to src/zope.dottedname.egg-info/top_level.txt > writing dependency_links to src/zope.dottedname.egg-info/dependency_links.txt > reading manifest file 'src/zope.dottedname.egg-info/SOURCES.txt' > writing manifest file 'src/zope.dottedname.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/dottedname/__init__.py -> > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope/dottedname > copying zope/dottedname/resolve.py -> > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope/dottedname > copying zope/dottedname/tests.py -> > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope/dottedname > running install_egg_info > Copying src/zope.dottedname.egg-info to > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-3.4.6.egg-info > Installing > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-3.4.6-nspkg.pth > running install_scripts > mv > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-*-py2.4.egg-info > \ > > debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname.egg-info > > mv: cannot stat > `debian/python-zope.dottedname/usr/lib/python2.4/site-packages/zope.dottedname-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.dottedname_3.4.6-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.dottedname Source-Version: 3.4.6-2 We believe that the bug you reported is fixed in the latest version of zope.dottedname, which is due to be installed in the Debian FTP archive: python-zope.dottedname_3.4.6-2_all.deb to main/z/zope.dottedname/python-zope.dottedname_3.4.6-2_all.deb zope.dottedname_3.4.6-2.diff.gz to main/z/zope.dottedname/zope.dottedname_3.4.6-2.diff.gz zope.dottedname_3.4.6-2.dsc to main/z/zope.dottedname/zope.dottedname_3.4.6-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.dottedname package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED M
Bug#552978: marked as done (zope.proxy: FTBFS: mv: cannot stat `debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:51:41 + with message-id and subject line Bug#552978: fixed in zope.proxy 3.5.0-4 has caused the Debian Bug report #552978, regarding zope.proxy: FTBFS: mv: cannot stat `debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.proxy Version: 3.5.0-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.proxy_3.5.0-3-amd64-hXuAxT/zope.proxy-3.5.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.proxy > --install-data=usr/lib/python-zope.proxy > running install > running build > running build_py > running egg_info > writing requirements to src/zope.proxy.egg-info/requires.txt > writing src/zope.proxy.egg-info/PKG-INFO > writing namespace_packages to src/zope.proxy.egg-info/namespace_packages.txt > writing top-level names to src/zope.proxy.egg-info/top_level.txt > writing dependency_links to src/zope.proxy.egg-info/dependency_links.txt > reading manifest file 'src/zope.proxy.egg-info/SOURCES.txt' > writing manifest file 'src/zope.proxy.egg-info/SOURCES.txt' > running build_ext > running install_lib > Skipping installation of > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/proxy/_zope_proxy_proxy.so -> > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/proxy > copying zope/proxy/_zope_proxy_proxy.c -> > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/proxy > copying zope/proxy/__init__.py -> > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/proxy > copying zope/proxy/decorator.py -> > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/proxy > copying zope/proxy/interfaces.py -> > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope/proxy > running install_headers > creating debian/python-zope.proxy/usr/include > creating debian/python-zope.proxy/usr/include/python2.4 > creating debian/python-zope.proxy/usr/include/python2.4/zope.proxy > copying src/zope/proxy/proxy.h -> > debian/python-zope.proxy/usr/include/python2.4/zope.proxy > running install_egg_info > Copying src/zope.proxy.egg-info to > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-3.5.0.egg-info > Installing > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-3.5.0-nspkg.pth > running install_scripts > mv > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-*-py2.4.egg-info > \ > > debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy.egg-info > mv: cannot stat > `debian/python-zope.proxy/usr/lib/python2.4/site-packages/zope.proxy-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.proxy_3.5.0-3_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.proxy Source-Version: 3.5.0-4 We believe that the bug you reported is fixed in the latest version of zope.proxy, which is due to be installed in the Debian FTP archive: python-zope.proxy_3.5.0-4_amd64.deb to main/z/zope.proxy/python-zope.proxy_3.5.0-4_amd64.deb zope.proxy_3.5.0-4.diff.gz to main/z/zope.proxy/zope.proxy_3.5.0-4.diff.gz zope.proxy_3.5.0-4.dsc to main/z/zope.proxy/zope.proxy_3.5.0-4.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian dist
Bug#552676: marked as done (zope.sqlalchemy: FTBFS: mv: cannot stat `debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:19 + with message-id and subject line Bug#552676: fixed in zope.sqlalchemy 0.4-5 has caused the Debian Bug report #552676, regarding zope.sqlalchemy: FTBFS: mv: cannot stat `debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.sqlalchemy Version: 0.4-4 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.sqlalchemy_0.4-4-amd64-oDCH9U/zope.sqlalchemy-0.4' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.sqlalchemy > --install-data=usr/lib/python-zope.sqlalchemy > running install > running build > running build_py > running egg_info > writing requirements to src/zope.sqlalchemy.egg-info/requires.txt > writing src/zope.sqlalchemy.egg-info/PKG-INFO > writing namespace_packages to > src/zope.sqlalchemy.egg-info/namespace_packages.txt > writing top-level names to src/zope.sqlalchemy.egg-info/top_level.txt > writing dependency_links to src/zope.sqlalchemy.egg-info/dependency_links.txt > reading manifest file 'src/zope.sqlalchemy.egg-info/SOURCES.txt' > writing manifest file 'src/zope.sqlalchemy.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/sqlalchemy/README.txt -> > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope/sqlalchemy > copying zope/sqlalchemy/__init__.py -> > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope/sqlalchemy > copying zope/sqlalchemy/datamanager.py -> > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope/sqlalchemy > copying zope/sqlalchemy/tests.py -> > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope/sqlalchemy > running install_egg_info > Copying src/zope.sqlalchemy.egg-info to > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-0.4.egg-info > Installing > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-0.4-nspkg.pth > running install_scripts > mv > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-*-py2.4.egg-info > \ > > debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy.egg-info > > mv: cannot stat > `debian/python-zope.sqlalchemy/usr/lib/python2.4/site-packages/zope.sqlalchemy-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.sqlalchemy_0.4-4_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.sqlalchemy Source-Version: 0.4-5 We believe that the bug you reported is fixed in the latest version of zope.sqlalchemy, which is due to be installed in the Debian FTP archive: python-zope.sqlalchemy_0.4-5_all.deb to main/z/zope.sqlalchemy/python-zope.sqlalchemy_0.4-5_all.deb zope.sqlalchemy_0.4-5.diff.gz to main/z/zope.sqlalchemy/zope.sqlalchemy_0.4-5.diff.gz zope.sqlalchemy_0.4-5.dsc to main/z/zope.sqlalchemy/zope.sqlalchemy_0.4-5.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zope.sqlalchemy package) (This message was generated automatically at their request; if you believe that there is a problem with it ple
Bug#552971: marked as done (zc.buildout: FTBFS: mv: cannot stat `debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc.buildout-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:48:35 + with message-id and subject line Bug#552971: fixed in zc.buildout 1.4.1-2 has caused the Debian Bug report #552971, regarding zc.buildout: FTBFS: mv: cannot stat `debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc.buildout-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zc.buildout Version: 1.4.1-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zc.buildout_1.4.1-1-amd64-xE8SXa/zc.buildout-1.4.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zc.buildout > --install-data=usr/lib/python-zc.buildout > running install > running build > running build_py > running egg_info > writing requirements to src/zc.buildout.egg-info/requires.txt > writing src/zc.buildout.egg-info/PKG-INFO > writing namespace_packages to src/zc.buildout.egg-info/namespace_packages.txt > writing top-level names to src/zc.buildout.egg-info/top_level.txt > writing dependency_links to src/zc.buildout.egg-info/dependency_links.txt > writing entry points to src/zc.buildout.egg-info/entry_points.txt > reading manifest file 'src/zc.buildout.egg-info/SOURCES.txt' > writing manifest file 'src/zc.buildout.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/__init__.py > (namespace package) > copying zc/buildout/windows.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/update.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/unzip.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/testing_bugfix.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/testing.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/setup.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/runsetup.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/repeatable.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/extends-cache.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/easy_install.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/downloadcache.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/download.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/dependencylinks.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/debugging.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/buildout.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/bootstrap.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/allowhosts.txt -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/__init__.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/buildout.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/download.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/easy_install.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/rmtree.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/testing.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/testrecipes.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copying zc/buildout/tests.py -> > debian/python-zc.buildout/usr/lib/python2.4/site-packages/zc/buildout > copy
Bug#552969: marked as done (zope.traversing: FTBFS: mv: cannot stat `debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope.traversing-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:48 + with message-id and subject line Bug#552969: fixed in zope.traversing 3.8.0-2 has caused the Debian Bug report #552969, regarding zope.traversing: FTBFS: mv: cannot stat `debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope.traversing-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.traversing Version: 3.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.traversing_3.8.0-1-amd64-p0Ss0t/zope.traversing-3.8.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.traversing > --install-data=usr/lib/python-zope.traversing > running install > running build > running build_py > running egg_info > writing requirements to src/zope.traversing.egg-info/requires.txt > writing src/zope.traversing.egg-info/PKG-INFO > writing namespace_packages to > src/zope.traversing.egg-info/namespace_packages.txt > writing top-level names to src/zope.traversing.egg-info/top_level.txt > writing dependency_links to src/zope.traversing.egg-info/dependency_links.txt > reading manifest file 'src/zope.traversing.egg-info/SOURCES.txt' > writing manifest file 'src/zope.traversing.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/traversing/configure.zcml -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/testing.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/__init__.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/publicationtraverse.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/interfaces.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/api.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/namespace.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/adapters.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing > copying zope/traversing/browser/configure.zcml -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/browser > copying zope/traversing/browser/absoluteurl.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/browser > copying zope/traversing/browser/__init__.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/browser > copying zope/traversing/browser/interfaces.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/browser > copying zope/traversing/browser/tests.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/browser > copying zope/traversing/tests/ftesting.zcml -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/ftest_zcml_dependencies.zcml -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/test_vh.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/test_etc.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/test_publicationtraverse.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/layer.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/test_traverser.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/tests > copying zope/traversing/tests/test_vhosting.py -> > debian/python-zope.traversing/usr/lib/python2.4/site-packages/zope/traversing/te
Bug#552910: marked as done (zconfig: FTBFS: mv: cannot stat `debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:48:53 + with message-id and subject line Bug#552910: fixed in zconfig 2.7.1-2 has caused the Debian Bug report #552910, regarding zconfig: FTBFS: mv: cannot stat `debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zconfig Version: 2.7.1-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zconfig_2.7.1-1-amd64-eBQfXV/zconfig-2.7.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zconfig > --install-data=usr/lib/python-zconfig > running install > running build > running build_py > running egg_info > writing ZConfig.egg-info/PKG-INFO > writing top-level names to ZConfig.egg-info/top_level.txt > writing dependency_links to ZConfig.egg-info/dependency_links.txt > reading manifest file 'ZConfig.egg-info/SOURCES.txt' > writing manifest file 'ZConfig.egg-info/SOURCES.txt' > running build_scripts > running install_lib > creating debian/python-zconfig/usr > creating debian/python-zconfig/usr/lib > creating debian/python-zconfig/usr/lib/python2.4 > creating debian/python-zconfig/usr/lib/python2.4/site-packages > creating debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig > copying build/lib/ZConfig/schemaless.txt -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig > creating debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests > creating > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource > creating > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo > creating > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo/sample > copying build/lib/ZConfig/tests/zipsource/foo/sample/datatypes.py -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo/sample > copying build/lib/ZConfig/tests/zipsource/foo/sample/component.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo/sample > copying build/lib/ZConfig/tests/zipsource/foo/sample/__init__.py -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo/sample > copying build/lib/ZConfig/tests/zipsource/foo/__init__.py -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource/foo > copying build/lib/ZConfig/tests/zipsource/README.txt -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/zipsource > creating > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/simplesections.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/simplesections.conf -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/simple.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/simple.conf -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/outer.conf -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/logger.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/library.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/inner.conf -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/include.conf -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/base.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/base-keytype2.xml -> > debian/python-zconfig/usr/lib/python2.4/site-packages/ZConfig/tests/input > copying build/lib/ZConfig/tests/input/base-keytype1.xml -> > debian/python-zconfig/usr/lib/python2.4/site
Bug#552944: marked as done (zope.publisher: FTBFS: mv: cannot stat `debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope.publisher-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:51:50 + with message-id and subject line Bug#552944: fixed in zope.publisher 3.9.3-2 has caused the Debian Bug report #552944, regarding zope.publisher: FTBFS: mv: cannot stat `debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope.publisher-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.publisher Version: 3.9.3-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.publisher_3.9.3-1-amd64-ILHfgO/zope.publisher-3.9.3' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.publisher > --install-data=usr/lib/python-zope.publisher > running install > running build > running build_py > running egg_info > writing requirements to src/zope.publisher.egg-info/requires.txt > writing src/zope.publisher.egg-info/PKG-INFO > writing namespace_packages to > src/zope.publisher.egg-info/namespace_packages.txt > writing top-level names to src/zope.publisher.egg-info/top_level.txt > writing dependency_links to src/zope.publisher.egg-info/dependency_links.txt > writing entry points to src/zope.publisher.egg-info/entry_points.txt > reading manifest file 'src/zope.publisher.egg-info/SOURCES.txt' > writing manifest file 'src/zope.publisher.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/publisher/xmlrpc.txt -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/skinnable.txt -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/paste.txt -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/normal.clb -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/meta.zcml -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/httpresults.txt -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/configure.zcml -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/principallogging.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/ftp.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/base.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/xmlrpc.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/paste.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/publish.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/__init__.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/skinnable.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/defaultview.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/zcml.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/browser.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/contenttype.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/http.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher > copying zope/publisher/interfaces/ftp.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher/interfaces > copying zope/publisher/interfaces/xmlrpc.py -> > debian/python-zope.publisher/usr/lib/python2.4/site-packages/zope/publisher/interfaces > copying zope/publisher/interfaces/__init__.py -> > debian/python-zope.publisher/usr/li
Bug#552974: marked as done (zc.lockfile: FTBFS: mv: cannot stat `debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:48:44 + with message-id and subject line Bug#552974: fixed in zc.lockfile 1.0.0-3 has caused the Debian Bug report #552974, regarding zc.lockfile: FTBFS: mv: cannot stat `debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zc.lockfile Version: 1.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zc.lockfile_1.0.0-2-amd64-ThV1dr/zc.lockfile-1.0.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zc.lockfile > --install-data=usr/lib/python-zc.lockfile > running install > running build > running build_py > running egg_info > writing requirements to src/zc.lockfile.egg-info/requires.txt > writing src/zc.lockfile.egg-info/PKG-INFO > writing namespace_packages to src/zc.lockfile.egg-info/namespace_packages.txt > writing top-level names to src/zc.lockfile.egg-info/top_level.txt > writing dependency_links to src/zc.lockfile.egg-info/dependency_links.txt > reading manifest file 'src/zc.lockfile.egg-info/SOURCES.txt' > writing manifest file 'src/zc.lockfile.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc/__init__.py > (namespace package) > copying zc/lockfile/README.txt -> > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc/lockfile > copying zc/lockfile/CHANGES.txt -> > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc/lockfile > copying zc/lockfile/tests.py -> > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc/lockfile > copying zc/lockfile/__init__.py -> > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc/lockfile > running install_egg_info > Copying src/zc.lockfile.egg-info to > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-1.0.0.egg-info > Installing > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-1.0.0-nspkg.pth > running install_scripts > mv > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-*-py2.4.egg-info > \ > > debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile.egg-info > > mv: cannot stat > `debian/python-zc.lockfile/usr/lib/python2.4/site-packages/zc.lockfile-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zc.lockfile_1.0.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zc.lockfile Source-Version: 1.0.0-3 We believe that the bug you reported is fixed in the latest version of zc.lockfile, which is due to be installed in the Debian FTP archive: python-zc.lockfile_1.0.0-3_all.deb to main/z/zc.lockfile/python-zc.lockfile_1.0.0-3_all.deb zc.lockfile_1.0.0-3.diff.gz to main/z/zc.lockfile/zc.lockfile_1.0.0-3.diff.gz zc.lockfile_1.0.0-3.dsc to main/z/zc.lockfile/zc.lockfile_1.0.0-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 552...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabio Tranchitella (supplier of updated zc.lockfile package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Nov 2009 11:19:11 +0100 Source: zc.lockfile Bi
Bug#552923: marked as done (zope.testing: FTBFS: mv: cannot stat `debian/python-zope.testing/usr/lib/python2.4/site-packages/zope.testing-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:38 + with message-id and subject line Bug#552923: fixed in zope.testing 3.8.3-2 has caused the Debian Bug report #552923, regarding zope.testing: FTBFS: mv: cannot stat `debian/python-zope.testing/usr/lib/python2.4/site-packages/zope.testing-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.testing Version: 3.8.3-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.testing_3.8.3-1-amd64-b21xVY/zope.testing-3.8.3' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.testing > --install-data=usr/lib/python-zope.testing > running install > running build > running build_py > running egg_info > writing requirements to src/zope.testing.egg-info/requires.txt > writing src/zope.testing.egg-info/PKG-INFO > writing namespace_packages to src/zope.testing.egg-info/namespace_packages.txt > writing top-level names to src/zope.testing.egg-info/top_level.txt > writing dependency_links to src/zope.testing.egg-info/dependency_links.txt > writing entry points to src/zope.testing.egg-info/entry_points.txt > reading manifest file 'src/zope.testing.egg-info/SOURCES.txt' > writing manifest file 'src/zope.testing.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/testing/setupstack.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/module.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/formparser.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/doctest.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/doctest.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/__init__.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/server.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/renormalizing.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/tests.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/loghandler.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/formparser.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/loggingsupport.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/setupstack.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/cleanup.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/doctestunit.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/module.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing > copying zope/testing/testrunner/tests.py -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner-wo-source.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner-verbose.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner-test-selection.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner-tb-format.txt -> > debian/python-zope.testing/usr/lib/python2.4/site-packages/zope/testing/testrunner > copying zope/testing/testrunner/testrunner-simple.txt -> > debian/python-zope.testing
Bug#552919: marked as done (zope.i18n: FTBFS: mv: cannot stat `debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope.i18n-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:51:01 + with message-id and subject line Bug#552919: fixed in zope.i18n 3.7.0-5 has caused the Debian Bug report #552919, regarding zope.i18n: FTBFS: mv: cannot stat `debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope.i18n-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.i18n Version: 3.7.0-4 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.i18n_3.7.0-4-amd64-FaUUQv/zope.i18n-3.7.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.i18n > --install-data=usr/lib/python-zope.i18n > running install > running build > running build_py > running egg_info > writing requirements to src/zope.i18n.egg-info/requires.txt > writing src/zope.i18n.egg-info/PKG-INFO > writing namespace_packages to src/zope.i18n.egg-info/namespace_packages.txt > writing top-level names to src/zope.i18n.egg-info/top_level.txt > writing dependency_links to src/zope.i18n.egg-info/dependency_links.txt > reading manifest file 'src/zope.i18n.egg-info/SOURCES.txt' > writing manifest file 'src/zope.i18n.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/i18n/gettextmessagecatalog.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/negotiator.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/format.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/testmessagecatalog.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/compile.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/zcml.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/translationdomain.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/testing.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/config.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/simpletranslationdomain.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/__init__.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n > copying zope/i18n/locales/xmlfactory.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales > copying zope/i18n/locales/provider.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales > copying zope/i18n/locales/inheritance.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales > copying zope/i18n/locales/fallbackcollator.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales > copying zope/i18n/locales/__init__.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales > copying zope/i18n/locales/tests/test_locales.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales/tests > copying zope/i18n/locales/tests/test_docstrings.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales/tests > copying zope/i18n/locales/tests/test_xmlfactory.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales/tests > copying zope/i18n/locales/tests/__init__.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales/tests > copying zope/i18n/locales/tests/test_fallbackcollator.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/locales/tests > copying zope/i18n/tests/test_gettextmessagecatalog.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/tests > copying zope/i18n/tests/test_translationdomain.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/tests > copying zope/i18n/tests/test_testmessagecatalog.py -> > debian/python-zope.i18n/usr/lib/python2.4/site-packages/zope/i18n/tests > copying zope/
Bug#552973: marked as done (zope.interface: FTBFS: mv: cannot stat `debian/python-zope.interface/usr/lib/python2.4/site-packages/zope.interface-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:51:22 + with message-id and subject line Bug#552973: fixed in zope.interface 3.5.2-2 has caused the Debian Bug report #552973, regarding zope.interface: FTBFS: mv: cannot stat `debian/python-zope.interface/usr/lib/python2.4/site-packages/zope.interface-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.interface Version: 3.5.2-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.interface_3.5.2-1-amd64-X6WYuN/zope.interface-3.5.2' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.interface > --install-data=usr/lib/python-zope.interface > running install > running build > running build_py > running egg_info > writing requirements to src/zope.interface.egg-info/requires.txt > writing src/zope.interface.egg-info/PKG-INFO > writing namespace_packages to > src/zope.interface.egg-info/namespace_packages.txt > writing top-level names to src/zope.interface.egg-info/top_level.txt > writing dependency_links to src/zope.interface.egg-info/dependency_links.txt > reading manifest file 'src/zope.interface.egg-info/SOURCES.txt' > writing manifest file 'src/zope.interface.egg-info/SOURCES.txt' > running build_ext > running install_lib > Skipping installation of > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/interface/_zope_interface_coptimizations.so -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/verify.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/index.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/human.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/human.ru.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/adapter.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/adapter.ru.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/_zope_interface_coptimizations.c -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/README.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/README.ru.txt -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/__init__.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/_flatten.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/adapter.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/advice.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/declarations.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/document.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/exceptions.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/interface.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/interfaces.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/ro.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/verify.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface > copying zope/interface/tests/unitfixtures.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/zope/interface/tests > copying zope/interface/tests/test_verify.py -> > debian/python-zope.interface/usr/lib/python2.4/site-packages/z
Bug#552935: marked as done (zope.testbrowser: FTBFS: mv: cannot stat `debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope.testbrowser-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:28 + with message-id and subject line Bug#552935: fixed in zope.testbrowser 3.5.1-4 has caused the Debian Bug report #552935, regarding zope.testbrowser: FTBFS: mv: cannot stat `debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope.testbrowser-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.testbrowser Version: 3.5.1-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.testbrowser_3.5.1-3-amd64-8XEDp7/zope.testbrowser-3.5.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.testbrowser > --install-data=usr/lib/python-zope.testbrowser > running install > running build > running build_py > running egg_info > writing requirements to src/zope.testbrowser.egg-info/requires.txt > writing src/zope.testbrowser.egg-info/PKG-INFO > writing namespace_packages to > src/zope.testbrowser.egg-info/namespace_packages.txt > writing top-level names to src/zope.testbrowser.egg-info/top_level.txt > writing dependency_links to src/zope.testbrowser.egg-info/dependency_links.txt > reading manifest file 'src/zope.testbrowser.egg-info/SOURCES.txt' > writing manifest file 'src/zope.testbrowser.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/testbrowser/over_the_wire.txt -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/fixed-bugs.txt -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/README.txt -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/DEPENDENCIES.cfg -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/browser.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/interfaces.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/testing.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/tests.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/__init__.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser > copying zope/testbrowser/ftests/zope3logo.gif -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/simple.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/radio.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/oneform.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/notitle.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/navigate.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/ftesting.zcml -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/fragment.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/forms.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/controls.html -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > copying zope/testbrowser/ftests/__init__.py -> > debian/python-zope.testbrowser/usr/lib/python2.4/site-packages/zope/testbrowser/ftests > running install_egg_info > Copying src/zope.testbrowser.egg-info to > debian/python-zope.testbrows
Bug#552933: marked as done (zope.i18nmessageid: FTBFS: mv: cannot stat `debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-*-py2.4.egg-info': No such file or directory
Your message dated Sun, 08 Nov 2009 12:51:11 + with message-id and subject line Bug#552933: fixed in zope.i18nmessageid 3.5.0-3 has caused the Debian Bug report #552933, regarding zope.i18nmessageid: FTBFS: mv: cannot stat `debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.i18nmessageid Version: 3.5.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.i18nmessageid_3.5.0-2-amd64-MUqQ0C/zope.i18nmessageid-3.5.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.i18nmessageid > --install-data=usr/lib/python-zope.i18nmessageid > running install > running build > running build_py > running egg_info > writing requirements to src/zope.i18nmessageid.egg-info/requires.txt > writing src/zope.i18nmessageid.egg-info/PKG-INFO > writing namespace_packages to > src/zope.i18nmessageid.egg-info/namespace_packages.txt > writing top-level names to src/zope.i18nmessageid.egg-info/top_level.txt > writing dependency_links to > src/zope.i18nmessageid.egg-info/dependency_links.txt > reading manifest file 'src/zope.i18nmessageid.egg-info/SOURCES.txt' > writing manifest file 'src/zope.i18nmessageid.egg-info/SOURCES.txt' > running build_ext > running install_lib > Skipping installation of > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/i18nmessageid/_zope_i18nmessageid_message.so -> > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/i18nmessageid > copying zope/i18nmessageid/_zope_i18nmessageid_message.c -> > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/i18nmessageid > copying zope/i18nmessageid/__init__.py -> > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/i18nmessageid > copying zope/i18nmessageid/message.py -> > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/i18nmessageid > copying zope/i18nmessageid/tests.py -> > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope/i18nmessageid > running install_egg_info > Copying src/zope.i18nmessageid.egg-info to > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-3.5.0.egg-info > Installing > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-3.5.0-nspkg.pth > running install_scripts > mv > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-*-py2.4.egg-info > \ > > debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid.egg-info > > mv: cannot stat > `debian/python-zope.i18nmessageid/usr/lib/python2.4/site-packages/zope.i18nmessageid-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.i18nmessageid_3.5.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.i18nmessageid Source-Version: 3.5.0-3 We believe that the bug you reported is fixed in the latest version of zope.i18nmessageid, which is due to be installed in the Debian FTP archive: python-zope.i18nmessageid_3.5.0-3_amd64.deb to main/z/zope.i18nmessageid/python-zope.i18nmessageid_3.5.0-3_amd64.deb zope.i18nmessageid_3.5.0-3.diff.gz to main/z/zope.i18nmessageid/zope.i18nmessageid_3.5.0-3.diff.gz zope.i18nmessageid_3.5.0-3.dsc to main/z/zope.i18nmessageid/zope.i18nmessageid_3.5.0-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will no
Bug#552928: marked as done (zope.security: FTBFS: mv: cannot stat `debian/python-zope.security/usr/lib/python2.4/site-packages/zope.security-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:52:10 + with message-id and subject line Bug#552928: fixed in zope.security 3.7.1-3 has caused the Debian Bug report #552928, regarding zope.security: FTBFS: mv: cannot stat `debian/python-zope.security/usr/lib/python2.4/site-packages/zope.security-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.security Version: 3.7.1-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.security_3.7.1-2-amd64-M8x5dj/zope.security-3.7.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.security > --install-data=usr/lib/python-zope.security > running install > running build > running build_py > running egg_info > writing requirements to src/zope.security.egg-info/requires.txt > writing src/zope.security.egg-info/PKG-INFO > writing namespace_packages to > src/zope.security.egg-info/namespace_packages.txt > writing top-level names to src/zope.security.egg-info/top_level.txt > writing dependency_links to src/zope.security.egg-info/dependency_links.txt > reading manifest file 'src/zope.security.egg-info/SOURCES.txt' > writing manifest file 'src/zope.security.egg-info/SOURCES.txt' > running build_ext > running install_lib > Skipping installation of > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/security/_zope_security_checker.so -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/_proxy.so -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/untrustedinterpreter.txt -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/permissions.zcml -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/meta.zcml -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/configure.zcml -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/_zope_security_checker.c -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/_proxy.c -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/README.txt -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/simplepolicies.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/management.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/i18n.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/_definitions.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/permission.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/interfaces.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/testing.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/setup.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/protectclass.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/adapter.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/checker.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/proxy.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/zcml.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/decorator.py -> > debian/python-zope.security/usr/lib/python2.4/site-packages/zope/security > copying zope/security/__init__.py -> > debian/python-zope.security/usr/lib/python2.4/site-p
Bug#552975: marked as done (zope.configuration: FTBFS: mv: cannot stat `debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope.configuration-*-py2.4.egg-info': No such file or directory
Your message dated Sun, 08 Nov 2009 12:50:04 + with message-id and subject line Bug#552975: fixed in zope.configuration 3.6.0-4 has caused the Debian Bug report #552975, regarding zope.configuration: FTBFS: mv: cannot stat `debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope.configuration-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.configuration Version: 3.6.0-3 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.configuration_3.6.0-3-amd64-Dc5T0v/zope.configuration-3.6.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.configuration > --install-data=usr/lib/python-zope.configuration > running install > running build > running build_py > running egg_info > writing requirements to src/zope.configuration.egg-info/requires.txt > writing src/zope.configuration.egg-info/PKG-INFO > writing namespace_packages to > src/zope.configuration.egg-info/namespace_packages.txt > writing top-level names to src/zope.configuration.egg-info/top_level.txt > writing dependency_links to > src/zope.configuration.egg-info/dependency_links.txt > reading manifest file 'src/zope.configuration.egg-info/SOURCES.txt' > writing manifest file 'src/zope.configuration.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/configuration/exclude.txt -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/README.txt -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/fields.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/exceptions.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/docutils.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/stxdocs.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/__init__.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/interfaces.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/config.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/zopeconfigure.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/xmlconfig.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/name.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration > copying zope/configuration/tests/simple.zcml -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/schema.zcml -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/sample.zcml -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/conditions.zcml -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/test_conditions.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/test_nested.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/victim.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying zope/configuration/tests/__init__.py -> > debian/python-zope.configuration/usr/lib/python2.4/site-packages/zope/configuration/tests > copying
Bug#552925: marked as done (zope.location: FTBFS: mv: cannot stat `debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:51:31 + with message-id and subject line Bug#552925: fixed in zope.location 3.7.0-2 has caused the Debian Bug report #552925, regarding zope.location: FTBFS: mv: cannot stat `debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.location Version: 3.7.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.location_3.7.0-1-amd64-fWR67N/zope.location-3.7.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.location > --install-data=usr/lib/python-zope.location > running install > running build > running build_py > running egg_info > writing requirements to src/zope.location.egg-info/requires.txt > writing src/zope.location.egg-info/PKG-INFO > writing namespace_packages to > src/zope.location.egg-info/namespace_packages.txt > writing top-level names to src/zope.location.egg-info/top_level.txt > writing dependency_links to src/zope.location.egg-info/dependency_links.txt > reading manifest file 'src/zope.location.egg-info/SOURCES.txt' > writing manifest file 'src/zope.location.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/location/location.txt -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/configure.zcml -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/traversing.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/__init__.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/interfaces.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/pickling.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/location.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > copying zope/location/tests.py -> > debian/python-zope.location/usr/lib/python2.4/site-packages/zope/location > running install_egg_info > Copying src/zope.location.egg-info to > debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-3.7.0.egg-info > Installing > debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-3.7.0-nspkg.pth > running install_scripts > mv > debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-*-py2.4.egg-info > \ > > debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location.egg-info > > mv: cannot stat > `debian/python-zope.location/usr/lib/python2.4/site-packages/zope.location-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.location_3.7.0-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.location Source-Version: 3.7.0-2 We believe that the bug you reported is fixed in the latest version of zope.location, which is due to be installed in the Debian FTP archive: python-zope.location_3.7.0-2_all.deb to main/z/zope.location/python-zope.location_3.7.0-2_all.deb zope.location_3.7.0-2.diff.gz to main/z/zope.location/zope.location_3.7.0-2.diff.gz zope.location_3.7.0-2.dsc to main/z/zope.location/zope.location_3.7.0-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the
Bug#552684: marked as done (zdaemon: FTBFS: mv: cannot stat `debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:49:03 + with message-id and subject line Bug#552684: fixed in zdaemon 2.0.4-2 has caused the Debian Bug report #552684, regarding zdaemon: FTBFS: mv: cannot stat `debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zdaemon Version: 2.0.4-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zdaemon_2.0.4-1-amd64-wLdHf4/zdaemon-2.0.4' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zdaemon > --install-data=usr/lib/python-zdaemon > running install > running build > running build_py > running egg_info > writing requirements to src/zdaemon.egg-info/requires.txt > writing src/zdaemon.egg-info/PKG-INFO > writing top-level names to src/zdaemon.egg-info/top_level.txt > writing dependency_links to src/zdaemon.egg-info/dependency_links.txt > writing entry points to src/zdaemon.egg-info/entry_points.txt > reading manifest file 'src/zdaemon.egg-info/SOURCES.txt' > writing manifest file 'src/zdaemon.egg-info/SOURCES.txt' > running install_lib > creating debian/python-zdaemon/usr > creating debian/python-zdaemon/usr/lib > creating debian/python-zdaemon/usr/lib/python2.4 > creating debian/python-zdaemon/usr/lib/python2.4/site-packages > creating debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/schema.xml -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/sample.conf -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/component.xml -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/README.txt -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > creating debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/__init__.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/nokill.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/parent.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/tests.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/testzdoptions.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/tests/testzdrun.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon/tests > copying build/lib/zdaemon/__init__.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/zdctl.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/zdoptions.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > copying build/lib/zdaemon/zdrun.py -> > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon > running install_egg_info > Copying src/zdaemon.egg-info to > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-2.0.4.egg-info > running install_scripts > Installing zdaemon script to debian/python-zdaemon/usr/bin > mv > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info > \ > > debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon.egg-info > mv: cannot stat > `debian/python-zdaemon/usr/lib/python2.4/site-packages/zdaemon-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zdaemon_2.0.4-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr
Bug#552940: marked as done (zope.exceptions: FTBFS: mv: cannot stat `debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:50:42 + with message-id and subject line Bug#552940: fixed in zope.exceptions 3.5.2-5 has caused the Debian Bug report #552940, regarding zope.exceptions: FTBFS: mv: cannot stat `debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.exceptions Version: 3.5.2-4 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.exceptions_3.5.2-4-amd64-rJQgc7/zope.exceptions-3.5.2' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.exceptions > --install-data=usr/lib/python-zope.exceptions > running install > running build > running build_py > running egg_info > writing requirements to src/zope.exceptions.egg-info/requires.txt > writing src/zope.exceptions.egg-info/PKG-INFO > writing namespace_packages to > src/zope.exceptions.egg-info/namespace_packages.txt > writing top-level names to src/zope.exceptions.egg-info/top_level.txt > writing dependency_links to src/zope.exceptions.egg-info/dependency_links.txt > reading manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' > writing manifest file 'src/zope.exceptions.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/exceptions/__init__.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions > copying zope/exceptions/exceptionformatter.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions > copying zope/exceptions/interfaces.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions > copying zope/exceptions/log.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions > copying zope/exceptions/tests/__init__.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions/tests > copying zope/exceptions/tests/test_exceptionformatter.py -> > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope/exceptions/tests > running install_egg_info > Copying src/zope.exceptions.egg-info to > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-3.5.2.egg-info > Installing > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-3.5.2-nspkg.pth > running install_scripts > mv > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-*-py2.4.egg-info > \ > > debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions.egg-info > > mv: cannot stat > `debian/python-zope.exceptions/usr/lib/python2.4/site-packages/zope.exceptions-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.exceptions_3.5.2-4_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | --- End Message --- --- Begin Message --- Source: zope.exceptions Source-Version: 3.5.2-5 We believe that the bug you reported is fixed in the latest version of zope.exceptions, which is due to be installed in the Debian FTP archive: python-zope.exceptions_3.5.2-5_all.deb to main/z/zope.exceptions/python-zope.exceptions_3.5.2-5_all.deb zope.exceptions_3.5.2-5.diff.gz to main/z/zope.exceptions/zope.exceptions_3.5.2-5.diff.gz zope.exceptions_3.5.2-5.dsc to main/z/zope.exceptions/zope.exceptions_3.5.2-5.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address
Bug#552936: marked as done (zodb: FTBFS: mv: cannot stat `debian/python-zodb/usr/lib/python2.4/site-packages/ZODB3-*-py2.4.egg-info': No such file or directory)
Your message dated Sun, 08 Nov 2009 12:49:15 + with message-id and subject line Bug#552936: fixed in zodb 1:3.9.1-2 has caused the Debian Bug report #552936, regarding zodb: FTBFS: mv: cannot stat `debian/python-zodb/usr/lib/python2.4/site-packages/ZODB3-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zodb Version: 1:3.9.1-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/build/user-zodb_3.9.1-1-amd64-q4l2Kn/zodb-3.9.1' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zodb > --install-data=usr/lib/python-zodb > running install > running build > running build_py > running egg_info > writing requirements to src/ZODB3.egg-info/requires.txt > writing src/ZODB3.egg-info/PKG-INFO > writing top-level names to src/ZODB3.egg-info/top_level.txt > writing dependency_links to src/ZODB3.egg-info/dependency_links.txt > writing entry points to src/ZODB3.egg-info/entry_points.txt > reading manifest file 'src/ZODB3.egg-info/SOURCES.txt' > writing manifest file 'src/ZODB3.egg-info/SOURCES.txt' > running build_ext > running install_lib > creating debian/python-zodb/usr > creating debian/python-zodb/usr/lib > creating debian/python-zodb/usr/lib/python2.4 > creating debian/python-zodb/usr/lib/python2.4/site-packages > creating debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/TimeStamp.so -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/cPickleCache.so -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/cPersistence.so -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/ring.h -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/ring.c -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/py24compat.h -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/cPickleCache.c -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/cPersistence.h -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/cPersistence.c -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/TimeStamp.c -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > copying build/lib.linux-x86_64-2.4/persistent/README.txt -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent > creating debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/persistent.txt -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_pickle.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/__init__.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_mapping.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_persistent.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_PickleCache.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/testPersistent.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_overriding_attrs.py > -> debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_64-2.4/persistent/tests/test_wref.py -> > debian/python-zodb/usr/lib/python2.4/site-packages/persistent/tests > copying build/lib.linux-x86_6
Bug#552924: marked as done (zope.authentication: FTBFS: mv: cannot stat `debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-*-py2.4.egg-info': No such file or direc
Your message dated Sun, 08 Nov 2009 12:49:24 + with message-id and subject line Bug#552924: fixed in zope.authentication 3.7.0-3 has caused the Debian Bug report #552924, regarding zope.authentication: FTBFS: mv: cannot stat `debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-*-py2.4.egg-info': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 552924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zope.authentication Version: 3.7.0-2 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory > `/build/user-zope.authentication_3.7.0-2-amd64-n8xrpI/zope.authentication-3.7.0' > python2.4 setup.py install --no-compile --single-version-externally-managed > --install-layout=deb --root=debian/python-zope.authentication > --install-data=usr/lib/python-zope.authentication > running install > running build > running build_py > running egg_info > writing requirements to src/zope.authentication.egg-info/requires.txt > writing src/zope.authentication.egg-info/PKG-INFO > writing namespace_packages to > src/zope.authentication.egg-info/namespace_packages.txt > writing top-level names to src/zope.authentication.egg-info/top_level.txt > writing dependency_links to > src/zope.authentication.egg-info/dependency_links.txt > reading manifest file 'src/zope.authentication.egg-info/SOURCES.txt' > writing manifest file 'src/zope.authentication.egg-info/SOURCES.txt' > running install_lib > Skipping installation of > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/__init__.py > (namespace package) > copying zope/authentication/principalterms.txt -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/logout.txt -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/configure.zcml -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/principal.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/interfaces.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/loginpassword.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/logout.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/__init__.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication > copying zope/authentication/tests/test_loginpassword.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication/tests > copying zope/authentication/tests/test_logout.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication/tests > copying zope/authentication/tests/test_principal.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication/tests > copying zope/authentication/tests/__init__.py -> > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope/authentication/tests > running install_egg_info > Copying src/zope.authentication.egg-info to > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-3.7.0.egg-info > Installing > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-3.7.0-nspkg.pth > running install_scripts > mv > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-*-py2.4.egg-info > \ > > debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication.egg-info > > mv: cannot stat > `debian/python-zope.authentication/usr/lib/python2.4/site-packages/zope.authentication-*-py2.4.egg-info': > No such file or directory > make[1]: *** [install-python2.4] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/10/28/zope.authentication_3.7.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribut
Processed: Tag eclipse bugs fixed in VCS (round 2)
Processing commands for cont...@bugs.debian.org: > # Missed that one. > tags 521312 + pending Bug #521312 [eclipse] eclipse: Eclipse fails to start on SPARC64 Added tag(s) pending. > # After round 1 I can actually see which bugs we have forgotten to > # mention in debian/changelog. > tags 552480 + pending Bug #552480 [eclipse] eclipse: GTK dialog stopped working Added tag(s) pending. > tags 354601 + pending Bug #354601 [eclipse] eclipse: Project names umlaut (special chars) problem Added tag(s) pending. > tags 491334 + pending Bug #491334 [eclipse] eclipse ignores vmargs in eclipse.ini Added tag(s) pending. > tags 491542 + pending Bug #491542 [eclipse] eclipse: missing dependency for embedded browsing library Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Tagging eclipse bugs fixed in VCS.
Processing commands for cont...@bugs.debian.org:
> #eclipse (3.5.1+repack-1) UNRELEASED; urgency=low
> #
> # * New upstream release. (LP: #123064)
> #- Supports xulrunner-1.9.1 (Closes: #507536)
> #- Fixed "Software Updates" menu. (Closes: #539016)
> # * Converted build system to use eclipse-build. (Closes: #501533)
> #- Fixed broken symlink in swt packages. (Closes: #543318)
> #- Fixed broken plugins/features. (Closes: #493984)
> #- Fixed problem finding native libraries. (Closes: #553131)
> #- Fixed build for various archs.
> #(Closes: #554584, #521312)
> # * Stopped eclipse from unpacking native libraries into ~/.eclipse.
> #(Closes: #351729)
> # * Corrected Depends and Recommends. (Closes: #554677)
> #- eclipse-jdt now only suggests eclipse.
> #- removed strict depedency on openjdk.
> # * Removed obsolete linda overrides.
> # * New maintainers. (Closes: #526489)
> # * Removed the need for Zenity (Closes: #528070)
> # * Added missing "apt" plug-in for eclipse-jdt.
> #(Closes: #403655, LP: #120610)
> # * Added conflicts on the old eclipse-*-nls packages.
> #(Closes: #538869)
> # * Removed "builtin browser not supported"-warning; it did not work.
> #(Closes: #402340)
> # * Removed dependency on libtomcat5.5-java and liblucene-java-doc.
> #(Closes: #530722, #537605)
> # * Stopped using special hacks and work arounds to find JVMs.
> #(Closes: #353360)
> #- This removes the need for ~/.eclipse/eclipserc (Closes: #402077)
> # * Moved the executable to eclipse-platform from eclipse.
> #(Closes: #358594)
> # * Put the osgi jar-files into its own separate package. (LP: #102717)
> #
> # -- Benjamin Drung Wed, 14 Oct 2009 01:42:49 +0200
> tags 507536 + pending
Bug #507536 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Bug #511713 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Bug #515747 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Bug #526225 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Bug #538871 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Bug #554423 [eclipse] eclipse: fails to start due to xulrunner - workaround;
disable welcome screen.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 539016 + pending
Bug #539016 [eclipse] eclipse: Software Updates do not work in 3.4
Added tag(s) pending.
> tags 501533 + pending
Bug #501533 [eclipse] eclipse: [ia64] native compilation ICEs seem to no longer
occur
Ignoring request to alter tags of bug #501533 to the same tags previously set
> tags 543318 + pending
Bug #543318 [libswt3.4-gtk-java] libswt3.4-gtk-java: all the symlinks in
/usr/lib/java broken
Ignoring request to alter tags of bug #543318 to the same tags previously set
> tags 493984 + pending
Bug #493984 [eclipse] eclipse: plugins/features are missing/wrong version
Bug #497549 [eclipse] [eclipse] plugins not working
Ignoring request to alter tags of bug #493984 to the same tags previously set
Ignoring request to alter tags of bug #497549 to the same tags previously set
> tags 553131 + pending
Bug #553131 [src:eclipse] eclipse: FTBFS - native libraries are not built from
source.
Bug #553133 [src:eclipse] eclipse-rcp: missing-dependency-on-libc needed by
./usr/lib/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1115.so
but the package doesn't depend on the C library package.
Normally this indicates that ${shlibs: Depends} was omitted from
the Depends line for this package in debian/control.
Added tag(s) pending.
Added tag(s) pending.
> tags 554584 + pending
Bug #554584 [src:eclipse] eclipse: FTBFS: timeout during build (on various
archs)
Bug #476067 [src:eclipse] eclipse: FTBFS: timeout during build (on various
archs)
Added tag(s) pending.
Added tag(s) pending.
> tags 351729 + pending
Bug #351729 [libswt3.2-gtk-jni] libswt-pi-gtk-3139.so cannot be mapped and
refuses Eclipse to start
Added tag(s) pending.
> tags 554677 + pending
Bug #554677 [eclipse] wishlist: correct depends / recommends for packages
Ignoring request to alter tags of bug #554677 to the same tags previously set
> tags 526489 + pending
Bug #526489 [wnpp] ITA: eclipse -- Extensible Tool platform and java IDE
Added tag(s) pending.
> tags 528070 + pending
Bug #528070 [eclipse] eclipse: Zenity doesn't be imposed as a dependence
Ignoring request to alter tags of bug #528070 to the same tags previously set
> tags 403655 + pending
Bug #403655 [eclipse-jdt] eclipse-jdt misses core plugin:
org.eclipse.jdt.apt.core
Ignoring request to alter tags of bug #403655 to the same tags previously set
> tags 538869 + pending
Bug #538869 [eclipse] eclipse should conflict with eclipse-*-n
Bug#552456: (no subject)
Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 555093 is serious
Processing commands for cont...@bugs.debian.org: > severity 555093 serious Bug #555093 [linux-2.6] Missing kernel-img.conf makes a debian kernel not installable Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534032: Being stuck
Hi! I have the packages now building fine again and being mostly lintian clean and nice, however some files are no longer correctly installed. I once solved that for ksimus-boolean but can't work out how I did it. The current status of these packages are at [0] so if anyone wants to continue on it (s)he can take it there. Regards Christoph [0] http://alioth.debian.org/~christoph-guest -- /"\ ASCII Ribbon : GPG-Key ID: 0xD49AE731 \ /Campaign : CaCert Assurer X against HTML : Debian Maintainer / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Processed: tagging 552010
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 552010 + pending Bug #552010 [libc6] libc6: After upgrade many applications become unusable Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#457279: gnarwl: ISPEnv.schema ISPEnv2.schema LICENSE not GPL compliant
Cajus Pollmeier wrote: > Sure. Just take it. > > Cheers, > Cajus > > > > Am 08.11.2009 um 01:26 schrieb Barry deFreese : > >> Cajus, >> >> Are you OK with me orphaning gnarwl and hopefully Fancesco can take over >> maintenance? >> >> Thank you, >> >> Barry deFreese >> Debian QA >> >> >> > Cajus, OK, it is orphaned. Thanks for the quick response! Barry deFreese Debian QA -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#554718: xulrunner, poppler, gnome and gupnp transitions
The webkit #554718 currently on kfreebsd-amd64 blocks building of seed, yelp, gir-repository, gstreamer0.10 (via gir-repository), devhelp, kazehakase, ... For details see http://lists.debian.org/debian-devel/2009/11/msg00289.html Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555087: [courier-mta] courier-mta does not install on clean squeeze system
Heiner Markert wrote: Package: courier-mta Version: 0.59.0-3 Severity: serious --- Please enter the report below this line. --- When performing apt-get install courier-mta on an otherwise clean squeeze system, dpkg fails with an post-install script error in package courier-mta. Installing the lenny package and dist-upgrading to squeeze is however working. The error occurs with either bash or dash as /bin/sh. My system is using legacy init scripts. Please note that the squeeze system is running inside a vserver-environment on a lenny i386 machine. How does the error message looks like. Intstalling courier-mta in my sid chroot results in the following error: Starting Courier mail server: done. Starting Courier mail filter:invoke-rc.d: initscript courier-mta, action "start" failed. dpkg: error processing courier-mta (--configure): subprocess installed post-installation script returned error exit status 255 Do you see the same error message? Regards Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: affects 543546, merging 543546 545600
Processing commands for cont...@bugs.debian.org: > affects 543546 freej Bug #543546 [libcv-dev] libcv-dev: bad int64 definition makes it impossible to use with mozjs Added indication that 543546 affects freej > merge 543546 545600 Bug#543546: libcv-dev: bad int64 definition makes it impossible to use with mozjs Bug#545600: freej: FTBFS: cxtypes.h:144: error: conflicting declaration 'typedef long long int int64' Merged 543546 545600. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 551970 in testing
Processing commands for cont...@bugs.debian.org: > found 551970 0.10.6-1 Bug #551970 [poppler] poppler: 0.12.1 Poppler bug fix and security release There is no source info for the package 'poppler' at version '0.10.6-1' with architecture '' Unable to make a source version for version '0.10.6-1' Bug Marked as found in versions 0.10.6-1. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555120: aptitude-gtk doesn't start
Package: aptitude Version: 0.6.0.1-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As shown below. I tried to read README/README.Debian provided with package but it doesn't provide help about gtk frondend startup etc 20:02:24-kar...@olive:~$ aptitude-gtk GThread-ERROR **: GThread system may only be initialized once. aborting... Aborted Thanks. Let me know if you want 'moreinfo'. - -- Package-specific info: aptitude 0.6.0.1 compiled at Oct 25 2009 22:49:53 Compiler: g++ 4.3.4 Compiled against: apt version 4.8.1 NCurses version 5.7 libsigc++ version: 2.0.18 Ept support enabled. Gtk+ version 2.18.3 Gtk-- version 2.18.2 Current library versions: NCurses version: ncurses 5.7.20090803 cwidget version: 0.5.13 Apt version: 4.8.1 linux-vdso.so.1 => (0x7fffe09ff000) libapt-pkg-libc6.9-6.so.4.8 => /usr/lib/libapt-pkg-libc6.9-6.so.4.8 (0x7f08854f8000) libncursesw.so.5 => /lib/libncursesw.so.5 (0x7f08852a7000) liblog4cxx.so.10 => /usr/lib/liblog4cxx.so.10 (0x7f0884eb4000) libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x7f0884caf000) libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x7f08849de000) libept.so.0 => /usr/lib/libept.so.0 (0x7f0884765000) libxapian.so.15 => /usr/lib/libxapian.so.15 (0x7f088440f000) libz.so.1 => /usr/lib/libz.so.1 (0x7f08841f8000) libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x7f0883f6b000) libboost_iostreams.so.1.40.0 => /usr/lib/libboost_iostreams.so.1.40.0 (0x7f0883d6) libglibmm-2.4.so.1 => /usr/lib/libglibmm-2.4.so.1 (0x7f0883b04000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x7f08838bf000) libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x7f08835fa000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x7f08833f6000) librt.so.1 => /lib/librt.so.1 (0x7f08831ee000) libgtkmm-2.4.so.1 => /usr/lib/libgtkmm-2.4.so.1 (0x7f0882b98000) libatkmm-1.6.so.1 => /usr/lib/libatkmm-1.6.so.1 (0x7f088294a000) libgdkmm-2.4.so.1 => /usr/lib/libgdkmm-2.4.so.1 (0x7f08826fd000) libgiomm-2.4.so.1 => /usr/lib/libgiomm-2.4.so.1 (0x7f088247c000) libpangomm-1.4.so.1 => /usr/lib/libpangomm-1.4.so.1 (0x7f088224d000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x7f0881c41000) libcairomm-1.0.so.1 => /usr/lib/libcairomm-1.0.so.1 (0x7f0881a2) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x7f0881774000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x7f0881554000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x7f088132b000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x7f088111) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x7f0880f04000) libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x7f0880c5b000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0x7f08809da000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x7f088078f000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x7f0880508000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x7f08802d7000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x7f08800d4000) libglademm-2.4.so.1 => /usr/lib/libglademm-2.4.so.1 (0x7f087feca000) libglade-2.0.so.0 => /usr/lib/libglade-2.0.so.0 (0x7f087fcb1000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0x7f087f956000) libm.so.6 => /lib/libm.so.6 (0x7f087f6d4000) libvte.so.9 => /usr/lib/libvte.so.9 (0x7f087f438000) libpthread.so.0 => /lib/libpthread.so.0 (0x7f087f21c000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f087ef0c000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x7f087ecf6000) libc.so.6 => /lib/libc.so.6 (0x7f087e9a3000) libutil.so.1 => /lib/libutil.so.1 (0x7f087e7a) libdl.so.2 => /lib/libdl.so.2 (0x7f087e59c000) libaprutil-1.so.0 => /usr/lib/libaprutil-1.so.0 (0x7f087e379000) libapr-1.so.0 => /usr/lib/libapr-1.so.0 (0x7f087e144000) libuuid.so.1 => /lib/libuuid.so.1 (0x7f087df4) libcrypt.so.1 => /lib/libcrypt.so.1 (0x7f087dd09000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x7f087daf9000) libpcre.so.3 => /lib/libpcre.so.3 (0x7f087d8ca000) /lib64/ld-linux-x86-64.so.2 (0x7f08857c) libpng12.so.0 => /usr/lib/libpng12.so.0 (0x7f087d6a5000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x7f087d49c000) libX11.so.6 => /usr/lib/libX11.so.6 (0x7f087d162000) libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x7f087cf6) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x7f087cd5e000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x7f08858a2000)
Processed: Non-free IETF RFC still here in 3.4.3
Processing commands for cont...@bugs.debian.org: > found 538034 2:3.4.3-1 Bug #538034 [samba] Source package contains non-free IETF RFC/I-D Bug Marked as found in versions samba/2:3.4.3-1. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#538034: Non-free IETF RFC still here in 3.4.3
found 538034 2:3.4.3-1 thanks Jelmer, you mentioned in your last contribution to #538034 that you would take care to have the offending remaining two files removed in upstream releases. However, these files are still here in 3.4.3. I wanted to reported this as an upstream bug but it seems that bugzilla.s.o is down. -- signature.asc Description: Digital signature
Bug#551970: found 551970 in testing
found 551970 0.10.6-1 thanks There is no reason for this bug to block migration to testing. Security bugs are present in previous releases anyway. And bugfixes in new upstream release are not worth RC severity. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#553904: [Pkg-samba-maint] Bug#553904: samba: Lost accounts on upgrade.
Quoting David Anselmi (anse...@anselmi.us): > Package: samba > Version: 2:3.4.2-1 > Severity: normal > > When upgrading a domain controller from 2:3.3.4-1 -> 2:3.4.2-1 my domain > became > unusable because the user/machine accounts were lost. > > Running pdbedit -L showed none of my Windows accounts (just the accounts from > the Linux server). > > Fortunately /etc/samba/smbpasswd still contained the accounts so: > > sudo pdbedit -i smbpasswd:/etc/samba/smbpasswd -e > tdbsam:/var/lib/samba/passdb.tdb > > seems to have recovered. > > Running: > > testparm -s --parameter-name "passdb backend" 2>/dev/null > > shows tdbsam but there has been no change to smb.conf to cause that to be > different now. The default setting of "passdb backend" changed from "smbpasswd" to "tdbsam" in samba 3.4.0 The default configuration file we provide in Debian has an explicit definition of "passdb backend = tdbsam" since the Lenny release cycle. So, people who use our default configuration will not be harmed by this default setting change. Only people who have *no* setting ofr "passdb backend" will suffer from the same problem you had. Steve, as you upgraded this bug to RC, I guess you somehow mean that we should do something. Last (and only time) we talked about this (June 25th), the conclusion was to mention something in NEWS.Debian. A stronger solution would be running a test to check whether "passdbbackend" is defined in smb.conf and warn the local admin if it is not (and if this is an upgrade from a pre-3.4.0 version). Comments? signature.asc Description: Digital signature
Processed: Re: Bug#550977: Re: Bug#550977: libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500
Processing commands for cont...@bugs.debian.org: > reassign 550977 linux-2.6 2.6.30-8 Bug #550977 [libgl1-mesa-dri] libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500 Bug reassigned from package 'libgl1-mesa-dri' to 'linux-2.6'. Bug No longer marked as found in versions mesa/7.6-1. Bug #550977 [linux-2.6] libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500 There is no source info for the package 'linux-2.6' at version '2.6.30-8' with architecture '' Unable to make a source version for version '2.6.30-8' Bug Marked as found in versions 2.6.30-8. > retitle 550977 filesystem corruption (drm related?) on thinkpad t40 Bug #550977 [linux-2.6] libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500 Changed Bug title to 'filesystem corruption (drm related?) on thinkpad t40' from 'libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500' > kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550977: Re: Bug#550977: libgl1-mesa-dri: direct rendering crashes the whole system on Thinkpad T40 with Radeon Mobility 7500
reassign 550977 linux-2.6 2.6.30-8 retitle 550977 filesystem corruption (drm related?) on thinkpad t40 kthxbye On Sat, Nov 7, 2009 at 22:25:46 +0100, ender wrote: > > > Did this filesystem corruption happen only once, or more than that? > > It did happen every time I tried, with one exception. > > > > > Is just X crashing, or is the system completely unresponsive > > (including over the network)? If the former, do you have > > corresponding X and kernel logs? > > It's not like a freeze of X. For example I'm able to switch to a > serial terminal but I can't login. The response is: > > /bin/login: error while loading shared libraris: > /lib/libpam_misc.so.0: invalid ELF header > > Ext3-fs error (device hda6): ext3_lookup: deletet inode referenced: > > > On the other hand some tools like pwd might still work. However the > system is unusable after a crash because it's impossible to start > basic programs or even login and I guess it won't work over the > network either. I didn't try that but samba didn't work anymore. > > > Anyway I'm going to add kernel and Xorg logs. Maybe you'll find > something interesting in there. > > One Crash happened Nov 7. approx 13:00 that one is in the kern.log > filesystem corruption is likely to be a kernel bug, so reassigning this bug over there. As another data point, does this also happen after a fresh boot, or only after a suspend/resume cycle? Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521473: getcontext missing on some architectures, what to do with wvstreams and wvdial?
Hello Release Team, I'd like to have some guidance on how to manage bug #521473, which affects wvstreams and wvdial because they rely on getcontext and setcontext, not available in armel and kfreebsd* implementations of eglibc (and this feature won't probably be implemented soon). I was thinking about the possibility to limit architectures to the ones getcontext/setcontext are available and functional, mangling Arch field or by adjusting P-A-S, and asking removal for armel and kfreebsd* binaries afterwards. Do you agree with this approach, or have better advices? -- .''`. : :' : Luca Falavigna `. `' `- signature.asc Description: PGP signature
Bug#520384: closed by Henrik Andreasson (Bug#520384: fixed in caudium 3:1.4.12-13)
reopen 520384 found 520384 3:1.4.12-13 thanks On Sun, 2009-11-08 at 11:07 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the caudium package: > > #520384: caudium: contains non-free font > > It has been closed by Henrik Andreasson . ... > >* Removal of non-free fontrstc Closes: #520384 You need to remove the font from the source package too: caudium-1.4.12/server/fonts/ttf/fontrstc.ttf Please ask upstream to do that and release a new version, then you can package the new version so this issue gets fixed in Debian. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#520384 closed by Henrik Andreasson (Bug#520384: fixed in caudium 3:1.4.12-13)
Processing commands for cont...@bugs.debian.org:
> reopen 520384
Bug #520384 {Done: Henrik Andreasson } [caudium] caudium:
contains non-free font
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
> found 520384 3:1.4.12-13
Bug #520384 [caudium] caudium: contains non-free font
Bug Marked as found in versions caudium/3:1.4.12-13.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555129: (no subject)
Subject: apache2-suexec: Should not set document root to /var/www - violates the FHS Package: apache2-suexec Version: 2.2.14-2 Justification: Policy 9.1.1 Severity: serious Hi, apache2-suexec is built with the following configure option: --with-suexec-docroot=/var/www This is not one of the /var directories in the File Hierarchy Standard and is under the control of the local administrator. Packages should not assume that it is the document root for a web server; it is very common for users to change the default document root and packages should not assume that users will keep any particular setting. Even http://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-web-appl, which suggests /var/www should be used if **unavoidable**, states that this place can be a symlink to the location where the system administrator has put the real document root. If I am right, suexec doesn't allow symlinks for security reasons. Please also see the discussion at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553498 which explains why I open this bug. Cheers, Julien -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: block 553498 with 555129
Processing commands for cont...@bugs.debian.org: > block 553498 with 555129 Bug #553498 [dspam-webfrontend] dspam-webfrontend: dir-or-file-in-var-www /var/www/dspam/admin.cgi and 6 others Was not blocked by any bugs. Added blocking bug(s) of 553498: 555129 > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
