Public bug reported:

This reproducibly fails in launchpad based builds like:
https://launchpadlibrarian.net/570210505/buildlog_ubuntu-jammy-s390x.parlatype_3.0-1_BUILDING.txt.gz
https://launchpadlibrarian.net/570130462/buildlog_ubuntu-jammy-s390x.parlatype_3.0-1_BUILDING.txt.gz

dpkg-buildpackage: info: source package parlatype
dpkg-buildpackage: info: source version 3.0-1
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture s390x
 debian/rules clean
debian/rules:19: *** missing separator.  Stop.

Repdoducible in local reproducer (LXC) on s390x.

I'm slightly wondering why this isn't breaking on all architectures as it is
all whitespace damage that can be important in Make.
But indeed on x86 it does not fail.

Converted to proper whitespaces it works and that is what I'll propose to Debian
which is also affected.

Reported to Debian as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000388
and fix: https://salsa.debian.org/gkarsay/parlatype/-/merge_requests/2

** Affects: parlatype (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Affects: parlatype (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: update-excuse

** Bug watch added: Debian Bug tracker #1000388
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000388

** Also affects: parlatype (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000388
   Importance: Unknown
       Status: Unknown

** Tags added: update-excuse

** Changed in: parlatype (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951833

Title:
  FTBFS -  missing separator - on s390x only

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parlatype/+bug/1951833/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to