Your message dated Sun, 15 Nov 2009 21:17:56 +0000
with message-id <e1n9mts-0007ib...@ries.debian.org>
and subject line Bug#556212: fixed in dynagen 0.11.0-4
has caused the Debian Bug report #556212,
regarding FTBFS: chmod: cannot access 
`debian/dynagen/usr/share/python-support/dynagen/dynamips_lib.py': 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.)


-- 
556212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dynagen
Version: 0.11.0-3
Severity: serious
Justification: no longer builds from source

Your package failed to build from source in a clean sid chroot:

[...]
dh_installdeb -pdynagen dh_perl -pdynagen dh_shlibdeps -pdynagen rm -rf debian/dynagen/usr/share/doc/dynagen/examples/sample_labs/.DS_Store.gz
chmod 755 debian/dynagen/usr/share/python-support/dynagen/dynamips_lib.py
chmod: cannot access 
`debian/dynagen/usr/share/python-support/dynagen/dynamips_lib.py': No such file 
or directory

--
Jakub Wilk



--- End Message ---
--- Begin Message ---
Source: dynagen
Source-Version: 0.11.0-4

We believe that the bug you reported is fixed in the latest version of
dynagen, which is due to be installed in the Debian FTP archive:

dynagen_0.11.0-4.diff.gz
  to contrib/d/dynagen/dynagen_0.11.0-4.diff.gz
dynagen_0.11.0-4.dsc
  to contrib/d/dynagen/dynagen_0.11.0-4.dsc
dynagen_0.11.0-4_all.deb
  to contrib/d/dynagen/dynagen_0.11.0-4_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 556...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Erik Wenzel <e...@debian.org> (supplier of updated dynagen 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, 15 Nov 2009 21:04:58 +0100
Source: dynagen
Binary: dynagen
Architecture: source all
Version: 0.11.0-4
Distribution: unstable
Urgency: low
Maintainer: Erik Wenzel <e...@debian.org>
Changed-By: Erik Wenzel <e...@debian.org>
Description: 
 dynagen    - Cisco 7200 Router Emulator Command Line Interface
Closes: 556212
Changes: 
 dynagen (0.11.0-4) unstable; urgency=low
 .
   * [d7e67068] [rules] fixed unnessesary chmod, which triggered a ftbfs
     caused by change in (Closes: 556212) - thanks to Kumar Appaiah and
     Jakub Wilk
   * [ed788f81] [control] bumped standards version; nothing changed
Checksums-Sha1: 
 d54865e32fcbfeee81c129f475791e3720cf34e8 1156 dynagen_0.11.0-4.dsc
 b004a4c8f6a3b9a613c61357ef58f586356dcdca 7693 dynagen_0.11.0-4.diff.gz
 d3754a15b9242df875c0938330d719254f19fc47 821012 dynagen_0.11.0-4_all.deb
Checksums-Sha256: 
 c1cfbdb6390ce8155cdf056ca1365de37dc7e99bbc4258f004af51002d394441 1156 
dynagen_0.11.0-4.dsc
 03f8a421699b062c23192945f55272d000d586929669d1afb43c690569742fee 7693 
dynagen_0.11.0-4.diff.gz
 edc6b2115f940bdb55f4bce7c48b21ec9f8765fd3736a937259981dbb05d70eb 821012 
dynagen_0.11.0-4_all.deb
Files: 
 aec9c99555cb149c061ca609320faa94 1156 contrib/net optional dynagen_0.11.0-4.dsc
 f6086d947baab7b691e73cd2353ccec9 7693 contrib/net optional 
dynagen_0.11.0-4.diff.gz
 d6d09f9a489e505e91c2bc122126cc79 821012 contrib/net optional 
dynagen_0.11.0-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAksAX6YACgkQmMmei9uJhBDiFACfb7YMa0BqoAeLliHNk7WAXK6L
Xx0AniFXIwr+AYa06C5+yfmKrEh+oL5R
=Bpko
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to