.. -*- coding: utf-8 -*- Version 0.14.0 -------------- :publication date: 2009/04/27 :expected date: n/a Ticket #7875 [vcslib] no more Debian stable compatible ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.200 :state: resolved See FIXME we check version 1.X cos it's doesn't work for previous versions I commited a dirty workaround but some methods will not be available (log_info, current_short_changeset) :: + # FIXME we check version 1.X cos it's doesn't work for previous versions + if get_version().split('.')[0] == "1": .... Comments :: On 2009/03/04 09:27 - sthenault wrote : which version are you talking about? Mercurial ? It's not in lenny ? > On 2009/03/04 09:31 - Unknown author wrote : > Yep! the fix should not be necessary anymore. I set a minimal load to drop the > code and make some tests. Ticket #7858 check the chroot image availability ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.200 :state: resolved or returns a more explicit error message. Comments :: On 2009/02/27 11:31 - Unknown author wrote : the 'all' value for distrib parameter MUST detect all available pbuilder images. Ticket #6747 /dev/null not writable for some hosts ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.000 :state: deprecated The problem comes from the ownership of /dev/null in the chrooted system: # ls -l /dev/null -rw-r--r-- 1 root root 0 Nov 28 14:38 /dev/null Trying to create with cdebootstrap:: dh_installdirs sh: /dev/null: Permission denied dh_installdirs: dpkg-architecture failed make: *** [install] Error 1 dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2 pbuilder: Failed autobuilding of package and with debootstrap:: # lgp setup -c create -d unstable * Have you already set your pbuilder variables in /etc/lgp/pbuilderrc ? [Y/n] * Creating images now... It will take a while. W: /root/.pbuilderrc does not exist Distribution is unstable. Building the build environment -> running debootstrap /usr/sbin/debootstrap mknod: `/var/cache/pbuilder/build/11065/./test-dev-null': Operation not permitted E: Cannot install into target '/var/cache/pbuilder/build/11065/.' mounted with noexec or nodev pbuilder: debootstrap failed -> Aborting with an error Found some discussions by googling but not clean solution for now: - http://www.mail-archive.com/debian-mentors@lists.debian.org/msg58960.html - http://groups.google.com/group/linux.debian.devel.mentors/browse_thread/thread/c06aa3c4dc045e04 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316135 - http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#nodev Ticket #2884 [hg] changelog attribute of httprepository ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.500 :state: resolved Pour récupérer le détails des changesets 'incoming' ou 'outgoing' dans HGAgent, on passe par l'attribut changelog de l'objet repository. Or cet attribut n'est pas disponible sur la classe httprepository. Il faudrait trouver une manière de gérer correctement le problème. Ticket #9046 traceback on openning repo? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.100 :state: resolved mercurial 1.2 ? tb :: Traceback (most recent call last): File "/usr/bin/apycotclient", line 3, in client.run() File "/usr/lib/python2.5/site-packages/apycotbot/client.py", line 263, in run %s""") File "/usr/lib/pymodules/python2.5/logilab/common/clcommands.py", line 136, in main_run cmd_run(arg, *args) File "/usr/lib/pymodules/python2.5/logilab/common/clcommands.py", line 119, in cmd_run command.run(args) File "/usr/lib/python2.5/site-packages/apycotbot/client.py", line 184, in run repo = pac.repository() File "/usr/lib/pymodules/python2.5/logilab/common/decorators.py", line 27, in cache_wrapper1 value = callableobj(self, *args) File "/usr/share/cubicweb/cubes/apycot/entities.py", line 160, in repository from apycotbot.repositories import get_repository File "/usr/lib/python2.5/site-packages/apycotbot/repositories.py", line 16, in from logilab.devtools.vcslib.hg import HGAgent File "/usr/lib/pymodules/python2.5/logilab/devtools/vcslib/hg.py", line 38, in from mercurial.repo import RepoError ImportError: cannot import name RepoError Ticket #8803 use python-support instead of python-central ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: enhancement :state: resolved We want to unify the Debian python build dependancies i.e. replace python-central with python-support. Ticket #9015 clumsy behaviour of the --orig-tarball option ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :type: bug :load: 0.100 :state: resolved :: E:build: the provided tarball (logilab-mtconverter_0.6.0.orig.tar.gz) has not the expected filename (logilab-mtconverter-0.6.0.tar.gz) Comments :: On 2009/04/14 09:06 - Unknown author wrote : If I recall correctly, this is because what we really want to use is the tarball publicly available from Logilab's FTP. This tarball is internally generated from the orig.tar.gz created by lgp by www-sync.sh. Now, if we accept a .orig.tar.gz tarball, we can't be sure that it is not another tarball, and if that tarball doesn't have the same checksum as the one in the repository, it will cause problems, such as apt-get source refusing to work. I'm not sure how this should be handled. > On 2009/04/14 09:23 - nchauvat wrote : > it is actually ~logilab/www/update-ftp.py that is called by www-synch and > reuses .orig.tar.gz > On 2009/04/14 09:29 - anon wrote : > juj: for our internal needs, we could use the .hg_archival.txt file to > disambiguate the situation ? On 2009/04/14 09:24 - anon wrote : juj: I think about a buggy version of lgc here. 0.13.6 (mercurial) should resolve this. The rule should to permit the both filenames (logilab-mtconverter_0.6.0.orig.tar.gz, logilab-mtconverter-0.6.0.tar.gz) with a preference for the former (add a warning message).