[Tracker-discuss] [issue134] Exception viewing issue with superseder - should superseder be Link or Multilink

[Erik Forsberg]

Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Huss <metatracker at psf.upfronthosting.co.za> writes:

> I do not
> know what the underlying problem is.  

I know :-).

In our schema, 'superseder' on issue is a Link, not a Multilink as in
the default schema. This made the page template code confused, which
caused the traceback. 

In non-roundup-guru speak, this means that you can only have _one_
superseder for an issue, not several.

If this is what we want, then my temporary fix (checked in and
implemented at bugs.python.org) is OK. 

If we do want a superseder to a be a Multilink, we need to change the
schema. And the latter needs to be done after asking some roundup
übergurus if that can be done safely.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGzdEUrJurFAusidkRAlvxAJsFcvu/bEbAAF0rBhryfC4OZagwbwCeMAjI
FximlzgqdXuQ5T/r+0aXKRQ=
=ZIaS
-----END PGP SIGNATURE-----

----------
status: unread -> chatting
title: Exception viewing closed issue -> Exception viewing issue with superseder - should superseder be Link or Multilink

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue134>
_______________________________________________________