Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-06-10 Thread Chris Hofstaedtler
On Mon, Jun 10, 2024 at 11:59:34AM +0200, Chris Hofstaedtler wrote: > Hi, > > On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote: > > > "Simon" == Simon McVittie writes: [..] > > Simon> However, even with both of those, if the krb5 test suite (or > > Simon> protocol) is

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-06-10 Thread Chris Hofstaedtler
Hi, On Mon, Feb 12, 2024 at 08:43:07AM -0700, Sam Hartman wrote: > > "Simon" == Simon McVittie writes: [..] > Simon> I am unsure whether there is consensus that "the result of > Simon> gethostname() resolves to some address of the local machine" > Simon> is also a reasonable

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-03-11 Thread Antonio Russo
Dear maintainer, This bug is (apparently?) currently preventing the amd64 build of 1.20.1-6. I apologize if this is already understood (by the way, is there somewhere on [1] or elsewhere to see if the build is being retried?). I'm also assuming I am not authorized to "give back" and trigger

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-12 Thread Sam Hartman
> "Simon" == Simon McVittie writes: Simon> It might be relevant that according to #972151, arm-conova-03 Simon> (and perhaps other *-conova-* buildds?) is IPv6-only, with no Simon> IPv4 addresses or routes other than loopback (not even via Simon> NAT). Simon> I believe

Processed: Re: Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-12 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname" in > dh_auto_test Bug #1063648 [src:krb5] krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test Changed Bug title to 'krb5: FTBFS on IPv6-only buildds: "Can't

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-12 Thread Simon McVittie
Control: retitle -1 krb5: FTBFS on IPv6-only buildds: "Can't resolve hostname" in dh_auto_test Control: tags -1 + ipv6 On Sun, 11 Feb 2024 at 23:40:34 +, Simon McVittie wrote: > It might be relevant that according to #972151, arm-conova-03 (and > perhaps other *-conova-* buildds?) is

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-11 Thread Simon McVittie
On Sun, 11 Feb 2024 at 13:53:56 -0800, Benjamin Kaduk wrote: > On Sat, Feb 10, 2024 at 01:33:15PM +0100, Johannes Schauer Marin Rodrigues > wrote: > > there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that > > failed for arm64, armel and ppc64el: > > > >

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-11 Thread Benjamin Kaduk
On Sat, Feb 10, 2024 at 01:33:15PM +0100, Johannes Schauer Marin Rodrigues wrote: > > there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that > failed for arm64, armel and ppc64el: > > https://buildd.debian.org/status/package.php?p=krb5 > > The error logs look very similar: > ***

Bug#1063648: krb5: FTBFS on arm64, armel and ppc64el with "Can't resolve hostname" in dh_auto_test

2024-02-10 Thread Johannes Schauer Marin Rodrigues
Source: krb5 Version: 1.20.1-5+b1 Severity: serious Tags: ftbfs Hi, there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that failed for arm64, armel and ppc64el: https://buildd.debian.org/status/package.php?p=krb5 The error logs look very similar: making check in lib/rpc...