Your message dated Thu, 25 Nov 2010 23:02:26 +0000
with message-id <e1plkpe-0001rk...@franck.debian.org>
and subject line Bug#604206: fixed in mod-mono 2.6.3-4
has caused the Debian Bug report #604206,
regarding libapache2-mod-mono: installation fails
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.)
--
604206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-mono
Version: 2.6.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: instest-20101120 instest
Hi,
While testing the installation of all packages in unstable, I ran
into the following problem:
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Starting
> Starting 2
> Done
> The following NEW packages will be installed:
> libapache2-mod-mono
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 51.5 kB of archives.
> After this operation, 201 kB of additional disk space will be used.
> Get:1 http://localhost/debian/ squeeze/main libapache2-mod-mono amd64 2.6.3-3
> [51.5 kB]
> Preconfiguring packages ...
> Using mono-apache-server2...
> Fetched 51.5 kB in 0s (177 kB/s)
> Selecting previously deselected package libapache2-mod-mono.
> (Reading database ... 17523 files and directories currently installed.)
> Unpacking libapache2-mod-mono (from
> .../libapache2-mod-mono_2.6.3-3_amd64.deb) ...
> Setting up libapache2-mod-mono (2.6.3-3) ...
>
> Configuration file `/etc/apache2/mods-available/mod_mono.conf'
> ==> File on system created by you or by a script.
> ==> File also in package provided by package maintainer.
> What would you like to do about it ? Your options are:
> Y or I : install the package maintainer's version
> N or O : keep your currently-installed version
> D : show the differences between the versions
> Z : start a shell to examine the situation
> The default action is to keep your current version.
> *** mod_mono.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing
> libapache2-mod-mono (--configure):
> EOF on stdin at conffile prompt
> configured to not write apport reports
> Errors were encountered while processing:
> libapache2-mod-mono
> E: Sub-process /usr/bin/dpkg returned an error code (1)
The full build log is available from:
http://people.debian.org/~lucas/logs/2010/11/20/libapache2-mod-mono.log
It is reproducible by installing your package in a clean chroot, using
the debconf Noninteractive frontend, and priority: critical.
This test was carried out using about 50 AMD64 nodes of the Grid'5000
platform. Internet was not accessible from the nodes.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Source: mod-mono
Source-Version: 2.6.3-4
We believe that the bug you reported is fixed in the latest version of
mod-mono, which is due to be installed in the Debian FTP archive:
libapache2-mod-mono_2.6.3-4_amd64.deb
to main/m/mod-mono/libapache2-mod-mono_2.6.3-4_amd64.deb
mod-mono_2.6.3-4.diff.gz
to main/m/mod-mono/mod-mono_2.6.3-4.diff.gz
mod-mono_2.6.3-4.dsc
to main/m/mod-mono/mod-mono_2.6.3-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 604...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jo Shields <direct...@apebox.org> (supplier of updated mod-mono 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: Thu, 25 Nov 2010 09:13:34 +0000
Source: mod-mono
Binary: libapache2-mod-mono
Architecture: source amd64
Version: 2.6.3-4
Distribution: unstable
Urgency: low
Maintainer: Debian Mono Group <pkg-mono-gr...@lists.alioth.debian.org>
Changed-By: Jo Shields <direct...@apebox.org>
Description:
libapache2-mod-mono - Apache module for running ASP.NET applications on Mono
Closes: 604206
Changes:
mod-mono (2.6.3-4) unstable; urgency=low
.
* [8b34845] Remove obsolete gbp.conf
* [07a4ab2] As it turns out, the change in 2.0-1 to prevent postinst
failure has an unwanted side effect - it is possible that
mod_mono.conf will be created (via touch) before dpkg handles the
conffiles - meaning it will prompt users about replacing the empty
file. Instead, just exit without an error when the config file is
missing (Closes: #604206)
Checksums-Sha1:
2e7772050e9c7612b4c5610df5f6bf1026fdcc4d 1644 mod-mono_2.6.3-4.dsc
27785ea3df1d0e64eec56e7365c6922b7de07220 15868 mod-mono_2.6.3-4.diff.gz
750dfb3cc113bf68c26ce2f23f21568594d2bc37 51694
libapache2-mod-mono_2.6.3-4_amd64.deb
Checksums-Sha256:
c555d03e6df35f4526c3ea1ad110ffe8c8e7c223797b68a10843f6cb7aba0bf1 1644
mod-mono_2.6.3-4.dsc
2b8978ac7d6335e93a4fa7306ab6cd44270e7ba724725ba29ce1663a3674dcf9 15868
mod-mono_2.6.3-4.diff.gz
4989a4e720c33859ce59e8e8e914d24680eda5df851df6c2ca6e4fd4aeb51602 51694
libapache2-mod-mono_2.6.3-4_amd64.deb
Files:
d2ad1fb5562e21d8946a08c8982cb1a7 1644 web optional mod-mono_2.6.3-4.dsc
4de2a56350e3a19a45f04f34709c5560 15868 web optional mod-mono_2.6.3-4.diff.gz
eac45d63568513bc57126c2b8232546e 51694 web optional
libapache2-mod-mono_2.6.3-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJM7upEAAoJEMkPnLkOH60ML0YH/0goMwPhrESbm9cmJrgP5aMS
mMyA8qjmKPyQ4qKhh80ygrCqVrzhCWJsZi25iPx0Ov/MAu5sZxzCOdOa2MwpvOzc
L0eianZuUUXPIfFHizLS1bwniBftbrKfSqtXl6xBawVER2REbEo6rPavri8fdF/P
hiAMTTlNfKgz1l1r1FULrMW8XJIUGVdo0XKC3578MjnpiUNKT9mLb/P7fkRq7+4+
ZqprL2joMfJgMdUvrTl/pWB5xeTqaNCwoeZ3CqnmduX+sLqcKX+j02eA825Qvp/3
lvr+4HMJV4gamMol36lTVzxpHu9mVi5s9pAMEIoLPl0yY274cmsljIFPPd2nMkg=
=GUDA
-----END PGP SIGNATURE-----
--- End Message ---
