Hi, when trying to contact the m68k team via their @buildd.d.o address earlier today, I noticed that there seems to be a problem with the address. See message below (and my original request as well). I thought you might want to know ;)
Best regards Sascha > Begin forwarded message: > > From: Mail Delivery System <mailer-dae...@molnjunk.nocrew.org> > Subject: Mail delivery failed: returning message to sender > Date: 10 January 2016 at 12:13:36 GMT > To: sas...@steinbiss.name > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > pipe to |/var/lib/mailman/mail/mailman post m68k-build > generated by m68k-bu...@nocrew.org > local delivery failed > > The following text was generated during the delivery attempt: > > ------ pipe to |/var/lib/mailman/mail/mailman post m68k-build > generated by m68k-bu...@nocrew.org ------ > > post script, list not found: m68k-build > > ------ This is a copy of the message, including all the headers. ------ > > Return-path: <sas...@steinbiss.name> > Received: from wuiet.debian.org ([5.153.231.18]) > by molnjunk.nocrew.org with esmtp (Exim 4.76) > (envelope-from <sas...@steinbiss.name>) > id 1aIEsK-0002ny-AY > for m68k-bu...@nocrew.org; Sun, 10 Jan 2016 13:13:36 +0100 > Received: from tetrinetsucht.de ([88.80.200.78] ident=Debian-exim) > by wuiet.debian.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) > (Exim 4.84) > (envelope-from <sas...@steinbiss.name>) > id 1aIEs1-0007HA-Dy > for m68k-bu...@nocrew.org; Sun, 10 Jan 2016 12:13:36 +0000 > Received: from XXX ([XXXX] helo=[192.168.1.2]) > by tetrinetsucht.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) > (Exim 4.72) > (envelope-from <sas...@steinbiss.name>) > id 1aIErz-0000zc-6h > for m...@buildd.debian.org; Sun, 10 Jan 2016 13:13:15 +0100 > From: Sascha Steinbiss <sas...@steinbiss.name> > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: quoted-printable > Message-Id: <05350b37-41da-4bdc-bddf-40ef0a3d0...@steinbiss.name> > Date: Sun, 10 Jan 2016 12:13:09 +0000 > To: m68k-bu...@nocrew.org > Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) > X-Mailer: Apple Mail (2.3112) > X-SA-Exim-Connect-IP: 81.101.15.93 > X-SA-Exim-Mail-From: sas...@steinbiss.name > X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tetrinetsucht.de > X-Spam-Level: > X-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 > autolearn=ham version=3.3.2 > Subject: package kmc autobuild > X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000) > X-SA-Exim-Scanned: Yes (on tetrinetsucht.de) > > Hello, > > I have noticed that the kmc package fails to build on m68k with a fairly = > generic message: > > https://buildd.debian.org/status/package.php?p=3Dkmc > > Since this is a C++ package for which compilation can be quite = > resource-intensive and take a long time, it could be that the build = > machine might not be up to it. Maybe you know more about the involved = > machines and whether there might be any chance to get the package built = > on all theoretically possible platforms? > > Many thanks, > Sascha=
