20 Nov
2006
20 Nov
'06
20:00
I'd like to inform you about the following two changes to bugzilla:
openSUSE 10.3
=============
We have created a new product and opened it. Some of the bugs that
will not be fixed for 10.2 are moved over to that product.
SUSE Linux 10.0
===============
Our policy is to only fix security bugs for released products and we
fix the occasional critical bugs. Security bugs are reported by the
security team and with 10.1 out and 10.2 nearly finished, we're not
fixing critical bugs anymore so we do not really need a public
bugzilla here. We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
SUSE Linux 10.1 will stay open for now - and openSUSE 10.2 is the
product we're working on,
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
21 Nov
21 Nov
01:10
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
Two questions:
1. What exactly does non-public mean?
a) nobody can report bugs against 10.0 or
b) nobody can view 10.0 bugs - this would be a very bad idea!
2. What makes you sure that nobody abuses 10.1, 10.2 or opensuse.org
then? ;-))
Regards,
Christian Boltz
--
Es ist im Moment recht ruhig, ja. Und das obwohl die ersten 9.3er Pakete
mittlerweile im Umlauf sind. Ob SuSE inzwischen so gut ist, dass die
Leute einfach keine Probleme mehr haben? (je nach eigenen Erfahrungen,
bitte Ironie-Tags setzen, oder eben nicht)
[Manfred Tremmel in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
09:21
Christian Boltz <opensuse(a)cboltz.de> writes:
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
Only the Novell folks and some of our old beta testers can report bugs
against it.
We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
Two questions:
1. What exactly does non-public mean?
a) nobody can report bugs against 10.0 or b) nobody can view 10.0 bugs - this would be a very
bad idea!
I'll check whether this is possible.
2. What makes you sure that nobody abuses 10.1, 10.2
or opensuse.org
then? ;-))
10.0 and 10 are too similar - but yes, I cannot be sure ;-(
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
16:16
Andreas Jaeger <aj(a)suse.de> writes:
Christian Boltz <opensuse(a)cboltz.de> writes:
This is possible - and it's setup this way now. If something is not
working as expected, please tell me.
To clarify: Everybody can still look at bugs reported against 10.0 -
but entering is not possible anymore for the general public,
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hello,
Am Montag, 20. November 2006 20:00 schrieb Andreas Jaeger:
Only the Novell folks and some of our old beta testers can report bugs
against it.
We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
Two questions:
1. What exactly does non-public mean?
a) nobody can report bugs against 10.0 or b) nobody can view 10.0 bugs - this would be a
very bad idea!
I'll check whether this is possible. 
25 Nov
25 Nov
10:15
On 2006-11-20 13:00, Andreas Jaeger wrote:
<snip>
Our policy is to only fix security bugs for released products and we
fix the occasional critical bugs. Security bugs are reported by the
security team and with 10.1 out and 10.2 nearly finished, we're not
fixing critical bugs anymore so we do not really need a public
bugzilla here. We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
Would this be the reason
why I am unable to read the bug report (100692)
concerning opening ports on the external zone in the Yast firewall setup?
--
The best way to accelerate a computer running Windows is at 9.81 m/s²
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
11:24
Darryl Gregorash <raven(a)accesscomm.ca> writes:
On 2006-11-20 13:00, Andreas Jaeger wrote:
No - that bug was reported against SLES10 and is only open to Novell
developers (no change here at all). Marking another as duplicate of
this was a bad idea ;-(
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
<snip>
Our policy is to only fix security bugs for released products and we
fix the occasional critical bugs. Security bugs are reported by the
security team and with 10.1 out and 10.2 nearly finished, we're not
fixing critical bugs anymore so we do not really need a public
bugzilla here. We do see some misuse especially with 10.0 where
people report bugs against different products or ask for general help
and have therefore decided to make it non-public tomorrow.
Would this be the
reason why I am unable to read the bug report (100692)
concerning opening ports on the external zone in the Yast firewall setup?
19:08
On 2006-11-25 04:24, Andreas Jaeger wrote:
Darryl Gregorash <raven(a)accesscomm.ca> writes:
It was present at least in 9.3, and probably before then,
but as I
always used the sysconfig editor to configure firewall ports, I didn't
discover it until someone reported it for 10.1, in suse-linux-e.
Surprising that no one reported it until SLES10.
Does the "no change" remark mean its still not fixed in 10.2? :-(
--
The best way to accelerate a computer running Windows is at 9.81 m/s²
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Would this be the reason why I am unable to read
the bug report (100692)
concerning opening ports on the external zone in the Yast firewall setup?
No - that bug was reported against SLES10 and is only open to Novell
developers (no change here at all). Marking another as duplicate of
this was a bad idea ;-(
26 Nov
26 Nov
07:12
Darryl Gregorash <raven(a)accesscomm.ca> writes:
On 2006-11-25 04:24, Andreas Jaeger wrote:
Yes :-(
Andreas
--
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Darryl Gregorash <raven(a)accesscomm.ca>
writes:
It was present at least in 9.3, and probably before then,
but as I
always used the sysconfig editor to configure firewall ports, I didn't
discover it until someone reported it for 10.1, in suse-linux-e.
Surprising that no one reported it until SLES10.
Does the "no change" remark mean its still not fixed in 10.2? :-( Would this be the reason why I am unable to read
the bug report (100692)
concerning opening ports on the external zone in the Yast firewall setup?
No - that bug was reported against SLES10 and is only open to Novell
developers (no change here at all). Marking another as duplicate of
this was a bad idea ;-(
08:17
On 2006-11-26 00:12, Andreas Jaeger wrote:
Darryl Gregorash <raven(a)accesscomm.ca> writes:
Thanks.
Should I file another bug report? :-)
--
The best way to accelerate a computer running Windows is at 9.81 m/s²
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Does the "no change" remark mean its
still not fixed in 10.2? :-(
Yes :-(
11 Feb
11 Feb
13:51
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger wrote:
I'd like to inform you about the following two
changes to bugzilla:
openSUSE 10.3
=============
Whom do we contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFFzxE1tTMYHG2NR9URAs5sAKCLdDX6p0EJU8pWMlq6VHekLTmTdQCdE59k
GFMTL+IYoN9hNSC+p+0P2nM=
=f1kR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
20:26
On Sunday 11 February 2007 06:51, Carlos E. R. wrote:
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger
wrote:
I have to second your opinion.
The problem is the policy or guys that mark bugs as duplicate.
For me, bug that is reported in restricted zone should not be announced
publicly by marking some public bug as duplicate of restricted one.
If it is really necessary, it would be probably better to do the same in
opposite direction, mark restricted bug as public one.
That way whoever is user of restricted zone can look for a solution, and no
info runs out of restricted zone.
--
Regards, Rajko.
http://en.opensuse.org/Portal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
I'd like to inform you about the following
two changes to bugzilla:
openSUSE 10.3
=============
Whom do we contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted. 
20:34
On Sun, 11 Feb 2007, Rajko M. wrote:
On Sunday 11 February 2007 06:51, Carlos E. R. wrote:
This is really the most annoying issue with bugzilla. There really should
be a policy to create a not restricted bug for any bug marked as a
duplicate of a restriced bug. Reference the restricted bug for those that
have to keep the information such, but all information that may be public
must be made public. That way community memember and other will be able
to follow but bug and not create more bugs that have already been
reported. I always do a search to make sure my bugs are not duplicates.
The only problem is I am not able to verify restricted bugs, this creates
more work for both as we are unable to verify bug and therefore create a
new bug that creates work for Novell to check and then assign bug.
Please create a non-restricted bug and follow up an it in the open. Use
reference bug only for restrited content.
Thanks,
--
Boyd Gerber <gerberb(a)zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
The Monday 2006-11-20 at 20:00 +0100, Andreas
Jaeger wrote:
I have to second your opinion.
The problem is the policy or guys that mark bugs as duplicate.
For me, bug that is reported in restricted zone should not be announced
publicly by marking some public bug as duplicate of restricted one.
If it is really necessary, it would be probably better to do the same in
opposite direction, mark restricted bug as public one.
That way whoever is user of restricted zone can look for a solution, and no
info runs out of restricted zone. I'd like to inform you about the following
two changes to bugzilla:
openSUSE 10.3
=============
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted. 
21:41
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E. R.:
The Monday 2006-11-20 at 20:00 +0100, Andreas Jaeger
wrote:
You can report it for now to this list or to me.
I will try to find some more official place (maybe some screening team can
help out here ... )
I am not sure, if I can open the bug, but I have asked ....
thanks
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian(a)suse.de
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
I'd like to inform you about the following
two changes to bugzilla:
openSUSE 10.3
=============
Whom do we contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted.
12 Feb
12 Feb
00:39
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Ok. What I did (before seeing your email) was forward an email to Q.A.
contact of the bug - I assume that QA means "quality assurance"?
Whom do we
contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted.
You can report it for now to this list or to me. I will try to find some more official place (maybe
some screening team can
help out here ... )
I am not sure, if I can open the bug, but I have asked ....
Thank you!
Perhaps the bugzilla developers could add a feature not allowing to close
a report as duplicate when the other one is restricted; ie, forcing to
keep both open.
You see, I understand the need to keep some reports restricted; what I
object to is to closing the non restricted report for that reason.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFFz6kytTMYHG2NR9URAsvfAKCFFjsR6qGvBhaXp9a6ukmRtegkZgCeOLNB
d4PeWxd207afIvFqt/s+DoI=
=BuCP
-----END PGP SIGNATURE-----
00:59
On Sun, 11 Feb 2007, Adrian Schröter wrote:
I am not sure, if I can open the bug, but I have asked
....
This is just one specific bug. Wrt. the general issue I would like
bugzilla.novell.com to warn whenever someone tries to mark an openSUSE
bug a duplicate of a restricted one.
Thoughts?
Gerald
14:11
Hello,
Am Montag, 12. Februar 2007 schrieb Gerald Pfeifer:
On Sun, 11 Feb 2007, Adrian Schröter wrote:
Such a warning is already in place. If you want to see how it looks
like, have a look at
http://www.cboltz.de/tmp/bugzilla-duplicate-permission-warning.png [1]
IMHO this warning is visible enough - but it seems it is often
ignored :-(
Hmm, maybe it should really be made more visible. My proposal: blinking,
fat, large red text, a chain of 20 "do you really want to do this?"
pages (all captcha-protected if "yes" is selected) and a loud siren
sound in the background so that everyone in the office knows what you
are doing *SCNR*
Sidenote: This discussion is a duplicate of
https://bugzilla.novell.com/show_bug.cgi?id=155846 ;-))
(and I won't complain if someone reopens it)
Regards,
Christian Boltz, BBfH [2]
PS: It's also possible to mark single comments as private/novellonly
(which is also done from time to time - maybe you already found some
bugreports where some comment numbers seem to be missing) - so it
would even be possible to have "open" bugreports with just the
secret parts hidden.
[1] Before you ask: I have access to bugs for older SUSE Linux versions,
but not for "novellonly" or SLE* bugs which are the major problem
nowadays.
[2] Well, I guess you know BOfH - in BBfH, the second B
means "Bugreporter" ;-)
--
Ich brauchte ganz, ganz dringend einen Beweis, das ich zu blöd für
die einfachsten Sachen bin, z.B. Email-Forwarden. Den habe ich ja
nun - Danke für die Mithilfe. BOINK. BOINK. BOINK. BOINK... Die
Passwörter poste ich dann morgen. Gnaaaaa! [Ratti in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
I am not sure, if I can open the bug, but I have
asked ....
This is just one specific bug. Wrt. the general issue I would like
bugzilla.novell.com to warn whenever someone tries to mark an
openSUSE bug a duplicate of a restricted one. 
16:44
On 2007-02-12 07:11, Christian Boltz wrote:
--
Moral indignation is jealousy with a halo. -- HG Wells
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
<snip>
fat, large red text, a chain of 20 "do you really want to do this?"
pages (all captcha-protected if "yes" is selected) and a loud siren
sound in the background so that everyone in the office knows what you
are doing *SCNR*
The 20th page should offer a choice of "no" or "no" :-)
16:41
On 2007-02-11 14:41, Adrian Schröter wrote:
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E.
R.:
Please do the same for my bug report on the Yast firewall allowed
services problem for the external zone,
https://bugzilla.novell.com/show_bug.cgi?id=214855
This bug has been around since 9.3, according to Marcus was first
reported asbug 100692 for SLES 9 (or a version of that vintage), and is
still alive in 10.2. 214855 was marked as a duplicate of 100692.
--
Moral indignation is jealousy with a halo. -- HG Wells
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
<snip>
I am not sure, if I can open the bug, but I have asked ....
23 Mar
23 Mar
21:58
New subject: [opensuse-project] Marking bugs as Duplicate of another one that is Restricted in Bugzilla [Was: Changes in Bugzilla]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Ok. Another one.
Bug 257168
Closed as duplicate of bug 233122. This one is restricted, so I reopen it.
"He" again closes as "RESOLVED INVALID".
!!!!! :-/
Novell, You really have to address this kind of issues, hire an ombudsman,
or something.
- --
Cheers,
Carlos E. R.
Am Sonntag 11 Februar 2007 13:51:00 schrieb Carlos E.
R.:
Whom do we
contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted.
You can report it for now to this list or to me. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGBD9/tTMYHG2NR9URAt7iAJ9cHLvEAwZeWn0IeB1WW5ogEKmvqQCfSF4x
FaYmBGXdHCoC59b9gDLwzcA=
=Eocq
-----END PGP SIGNATURE-----
23:45
New subject: [opensuse-project] Marking bugs as Duplicate of another one that is Restricted in Bugzilla [Was: Changes in Bugzilla]
On Fri, Mar 23, 2007 at 09:58:38PM +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2007-02-11 at 21:41 +0100, Adrian Schröter wrote:
Ok. Another one.
Bug 257168
Closed as duplicate of bug 233122. This one is restricted, so I reopen it.
"He" again closes as "RESOLVED INVALID".
!!!!! :-/
Novell, You really have to address this kind of issues, hire an ombudsman,
or something.
We already told sometime ago that we cannot release -debuginfo packages
due to its excessive sizes... Its just too big.
The 10.2 update repo is already nearing to 4GB, it would be >50GB with debuginfos
(at least, if not more).
The other bug is open now.
Ciao, Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
Am Sonntag 11 Februar 2007 13:51:00 schrieb
Carlos E. R.:
Whom do
we contact when we have problems with Bugzilla, what is the
procedure?
For instance, I reported time ago "bug 225631", which is now marked as
duplicate of bug 188556, and the last one is restricted.
This general issue has been comented somewhere else. Whom do I report the
problem to? I do not want to reopen it myself, but I would like to see the
conclussions of the problem, which are restricted.
You can report it for now to this list or to me.
24 Mar
24 Mar
01:17
New subject: [opensuse-project] Marking bugs as Duplicate of another one that is Restricted in Bugzilla [Was: Changes in Bugzilla]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Friday 2007-03-23 at 23:45 +0100, Marcus Meissner wrote:
We already told sometime ago that we cannot release
-debuginfo packages
due to its excessive sizes... Its just too big.
Didn't know that.
The 10.2 update repo is already nearing to 4GB, it would be >50GB with debuginfos
(at least, if not more).
The other bug is open now.
Thanks! :-)
[...]
Reading it, I understand that to investigate Bug 256363 some one should
supply me with the correct kdelibs3-debuginfo (Comment #8 of Bug 233122).
The thing is that I discovered a big memory hole in kbabel, of 2 GiB size.
I reported this, and was told to use ulimit -m 300000 to force it crash
before it ate all available swap (this does not work, by the way).
In order to get a meaningful backtrace I should first install the
corresponding debuginfo rpms: qt3, kdelibs3 and kdesdk3. But Yast
complained and refused, because kdelibs3 has been updated and there is no
corresponding update for -debuginfo.
So I again reported that, and instead of being told what the problem is,
it was closed as duplicate or a restricted bug!
You can imagine how pissing is to be artificially blocked when trying to
help solve a bug!
So, again, thank you for your help and clarification.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGBG49tTMYHG2NR9URAnA+AKCPATfsP5vh/vTjjR1pXVJB14TgzACfWSOf
aJeyYHXEp9pJjAAAKo/OrNA=
=GK2S
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org
5293
days inactive
5417
days old
20 comments
9 participants
participants (9)
-
Adrian Schröter -
Andreas Jaeger -
Boyd Lynn Gerber -
Carlos E. R. -
Christian Boltz -
Darryl Gregorash -
Gerald Pfeifer -
Marcus Meissner -
Rajko M.