From unknown Mon Apr 27 21:32:28 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#1543: [X2Go-Dev] Bug#1543: report spam - link is broken
Reply-To: Mihai Moldovan <ionic@ionic.de>, 1543@bugs.x2go.org
Resent-From: Mihai Moldovan <ionic@ionic.de>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: x2go-dev@lists.x2go.org
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 04 May 2021 10:45:01 +0000
Resent-Message-ID: <handler.1543.B1543.162012492522397@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1543
X-X2Go-PR-Package: wiki.x2go.org
X-X2Go-PR-Keywords: 
References: <e5c3f816-d582-7ebe-b113-10d88572b14d@freenet.de> <e5c3f816-d582-7ebe-b113-10d88572b14d@freenet.de>
Received: via spool by 1543-submit@bugs.x2go.org id=B1543.162012492522397
          (code B ref 1543); Tue, 04 May 2021 10:45:01 +0000
Received: (at 1543) by bugs.x2go.org; 4 May 2021 10:42:05 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,NICE_REPLY_A,SPF_HELO_NONE,URIBL_BLOCKED
	autolearn=ham autolearn_force=no version=3.4.2
Received: from mail.ionic.de (ionic.de [IPv6:2001:41d0:700:3394:1::2])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id EA1355DB22
	for <1543@bugs.x2go.org>; Tue,  4 May 2021 11:45:39 +0200 (CEST)
Authentication-Results: root24.eu; spf=softfail (domain owner 
   discourages use of this host) smtp.mailfrom=ionic.de 
   (client-ip=217.92.117.31; helo=home.ionic.de; 
   envelope-from=ionic@ionic.de; receiver=<UNKNOWN>)
Received: from [192.168.0.46] (home.ionic.de [217.92.117.31])
	by mail.ionic.de (Postfix) with ESMTPSA id 783711487488
	for <1543@bugs.x2go.org>; Tue,  4 May 2021 09:45:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ionic.de; s=default;
	t=1620121539; bh=T0/o6Q1P4s1krQhtG3byW/PwisF8N41hWIGq4rI630k=;
	h=To:References:From:Subject:Date:In-Reply-To:From;
	b=pkNIdFePUqV88LZCUia7e320S4g51WfQafCeOVa5gpNHkfDRb53mgN2cJHF/zJ4xk
	 3wUhRrN1iYxsaH7lsyHh4KBIyM8qp3fYGs+iYlyw8aPt72mnqoK0uPnSi3KGqNJpAf
	 O4SBAGGwme5j62a5ts4WgZktrbBbqNIfTl9qSbY0=
To: 1543@bugs.x2go.org
From: Mihai Moldovan <ionic@ionic.de>
Message-ID: <ae911a9a-8977-9ad7-ab32-e6ad533f0fa0@ionic.de>
Date: Tue, 4 May 2021 11:45:38 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <e5c3f816-d582-7ebe-b113-10d88572b14d@freenet.de>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="WhpCGCm9E6U9ktquDqm2qsm42WiMC9EaE"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--WhpCGCm9E6U9ktquDqm2qsm42WiMC9EaE
Content-Type: multipart/mixed; boundary="LYaAwbDQfUWW1t5aZ0zXDXxtKI0U6RnB2";
 protected-headers="v1"
From: Mihai Moldovan <ionic@ionic.de>
To: 1543@bugs.x2go.org
Message-ID: <ae911a9a-8977-9ad7-ab32-e6ad533f0fa0@ionic.de>
Subject: Re: [X2Go-Dev] Bug#1543: report spam - link is broken
References: <e5c3f816-d582-7ebe-b113-10d88572b14d@freenet.de>
In-Reply-To: <e5c3f816-d582-7ebe-b113-10d88572b14d@freenet.de>

--LYaAwbDQfUWW1t5aZ0zXDXxtKI0U6RnB2
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Control: close -1

* On 5/2/21 11:03 PM, Ren=C3=A9 Genz wrote:
> Package: wiki.x2go.org
>=20
> On the website:
> https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=3D937
> at the bottom you can read "Send a report that this bug log contains sp=
am." The part "this bug log contains spam" links to:
> https://bugs.x2go.org/cgi-bin/bugs.x2go.org/cgi-bin/bugspam.cgi?bug=3D9=
37
> which results in a 404 error. The correct URL is:
> https://bugs.x2go.org/cgi-bin/bugspam.cgi?bug=3D937

Remind me to never try to update to the 3.0.0 alpha version of debbugs ag=
ain.
I've wasted 10 hours on that only to realize that the packaging and code =
are
currently broken beyond (easy) repair.

I've upgraded to the currently unreleased 2.6.1 version and backported a =
few
fixes that went missing from our version.

I also modified the configuration to always include the https:// protocol=

specifier, which should fix the issue you've been seeing (and, hopefully,=
 not
cause other links to have double protocol specifiers).


Mihai


--LYaAwbDQfUWW1t5aZ0zXDXxtKI0U6RnB2--

--WhpCGCm9E6U9ktquDqm2qsm42WiMC9EaE
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEbhHQj3UzgcdE8cg8H9Yu2W4lOocFAmCRF8IFAwAAAAAACgkQH9Yu2W4lOoco
iQ/+JqX5UmPME0LQgqeBhRuR9QVaIlrcUs6Lsa/lvS/RqkHsbCU4xeQiaFJJoKeaL49ulQnuxL1l
+X3YY5labcBOpi4k0l5MYrM6AWxUXLNxlKxOVIx4SZUixnDMi3jrfkeJYFEksapYbt3Ne10GVKH2
8t919FFGT4CAkYOiPTfwmRXdCJg/8qYn30uwiQSxcdtgcIQGftGVc/xgJe4FYKva2wUlBITQmLJL
y6NHMsucIG+B4Sy0thpKkUTXZIR5LfrTrv3Li5fW4ZChf6HU6c0Cu4G2emtV80itLMgSQTdUgWi5
TLhmNPCjHnqHeiuYWvwClNkHhxEHotGluhXSb7C4lib3Qp2ROenj3HOkosKfpKCAHvG3HQbafJF8
O7UGW5HwwUqD8/PliEouqGXqJq+cF0C2an3GtoUKMk7c6FQvqzwsI1ixwLzY6fWKrpV7Jox13JBH
HPFUr8TBn12q5RNgagCMk7TjDX2D41+Cna7v/bthbnh5HSk05U8nE5X2ycB2ypkvgPdtSAb3Rnec
zsCMLSvHtabv2yCMOiVV8bz7P7Z6pczZ/FepUj60D1s7jpyb1Vlj/R0rrwSfK/m826vgGV/Ex3+J
JCC9AlyRUKzPcr/w+YiARcG8Qs7Q1ZI79IDZsSCwbGYgYPCmLCxjKuMSnJZIkLAjknFjzF6r3Z3n
1ys=
=lRvR
-----END PGP SIGNATURE-----

--WhpCGCm9E6U9ktquDqm2qsm42WiMC9EaE--
