Your message dated Mon, 07 Apr 2014 01:59:10 +0010
with message-id <[email protected]>
and subject line Mostly fixed
has caused the Debian Bug report #570181,
regarding mono-gac: Installing signature-remapped assemblies fails unless
mono-runtime is configured first
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 [email protected]
immediately.)
--
570181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570181
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mono-gac
Version: 2.4.2.3+dfsg-2
Severity: important
Discovered while investigating why rawang's mono-uia packages failed to install
on the buildds.
09:38 <RAOF> Ok. So, I think rawang's mono-uia problem is interesting from a
policy perspective. The problem is this: mono-uia is delaysigned with the
winfx3 public key. Since mono obviously don't have that private key, the
assemblies get resigned with mono.snk, which works because of a mapping in
machine.config.
09:41 <RAOF> Now, when mono-uia packages are being installed in a chroot, it
goes like this: everything gets unpacked, then mono-gac tries to get
configured. As a part of that, it tries to install libmono-uia3.0 into the
GAC. However, mono-runtime _isn't_ configured, and in particular
machine.config is currently machine.config.dpkg-new, so gacutil can't verify
the strongname, GAC install fails, mono-gac can't be configured, and so
mono-runtime can't be configured.
Everything then ends up nicely wedged.
This could be resolved by using a dpkg trigger to run the GAC install, so that
mono-runtime will be configured before trying to install assemblies into the
GAC.
-- System Information:
Debian Release: squeeze/sid
APT prefers lucid-security
APT policy: (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-999-generic (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mono-gac depends on:
ii mono-2.0-gac 2.4.2.3+dfsg-2 Mono GAC tool (for CLI 2.0)
mono-gac recommends no packages.
mono-gac suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
# 749659 is a failure to GAC a key-remapped assembly
reassign 739659 mono-gac
severity 739659 important
merge 570181 739659
# mono-gac 3.0.6+dfsg2-12 solves almost all of this problem by
# not running gacinstall when clean-installing mono-gac
#
# This was unnecessary, as the library packages would also do a
# gacinstall run in their postinsts
#
# There's a small task remaining, to make cli-common-dev add a
# Depends: on mono-runtime-common when a library package contains
# a key-remapped assembly. Otherwise there's still a chance that
# the gacinstall run can occur before mono-runtime-common is configured
clone 570181 -1
reassign -1 cli-common-dev
retitle -1 dh_clideps: Add a Depends on mono-runtime-common when
GAC-installed assemblies use remapped keys
--- End Message ---
