[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#887308: marked as done (mark kpackagetool5 Multi-Arch: foreign)

Your message dated Mon, 19 Oct 2020 21:55:01 +0000
with message-id <E1kUd7N-0002k3-U2@fasolo.debian.org>
and subject line Bug#887308: fixed in kpackage 5.74.0-2
has caused the Debian Bug report #887308,
regarding mark kpackagetool5 Multi-Arch: foreign
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
887308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887308
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kpackagetool5
Version: 5.37.0-2
Tags: patch
User: helmutg@debian.org
Usertags: rebootstrap
Control: affects -1 + src:kate

kate fails to cross build from source, because running kpackagetool5
fails:

| CMake Warning at /usr/lib/mips-linux-gnu/cmake/KF5Package/KF5PackageMacros.cmake:58 (message):
|   couldn't generate metainfo for org.kde.plasma.katesessions:
|   /usr/bin/kpackagetool5: 1: /usr/bin/kpackagetool5: Syntax error: "("
|   unexpected

Some shell is trying to run the foreign ELF binary as a shell script and
fails. Unfortunately, it doesn't give the more useful "Exec format
error". Also cmake doesn't trap this error (which arguably is a policy
4.6 violation), so you don't notice the failure until the end of the
build when some file is missing (or you don't notice it at all).

If kpackagetool5 needs to be run, it needs to be installed for the build
architecture. The easy way of doing so is marking it "Multi-Arch:
foreign". The major remaining question is: Is such a marking correct?

That's difficult to answer unless you know what kpackagetool5 does. I
don't know what it does and the manual page is not very ... descriptive.
I looked around and as far as I can see, it deals with text formats such
as xml and json, but not with binary formats. If it was dealing with
binary formats, the question would be whether such formats are
architecture-dependent (e.g. endianess). I hope my cursory look is
sufficient here and ask you to review it. If it is, the attached patch
likely makes kate (and a pile more packages) cross build. If in doubt,
don't just apply my patch but help me better understand kpackagetool5.

Helmut

diff --minimal -Nru kpackage-5.37.0/debian/changelog kpackage-5.37.0/debian/changelog
--- kpackage-5.37.0/debian/changelog	2017-09-03 09:58:36.000000000 +0200
+++ kpackage-5.37.0/debian/changelog	2018-01-14 20:54:34.000000000 +0100
@@ -1,3 +1,11 @@
+kpackage (5.37.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Mark kpackagetool5 Multi-Arch: foreign. (Closes: #-1)
+  * Mark libkf5package-dev Multi-Arch: same.
+
+ -- Helmut Grohne <helmut@subdivi.de>  Sun, 14 Jan 2018 20:54:34 +0100
+
 kpackage (5.37.0-2) sid; urgency=medium
 
   * New revision
diff --minimal -Nru kpackage-5.37.0/debian/control kpackage-5.37.0/debian/control
--- kpackage-5.37.0/debian/control	2017-09-03 09:58:36.000000000 +0200
+++ kpackage-5.37.0/debian/control	2018-01-14 20:54:32.000000000 +0100
@@ -25,6 +25,7 @@
 Package: kpackagetool5
 Section: kde
 Architecture: any
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Breaks: kpackagelauncherqml (<< 5.37),
         libkf5declarative5 (<< 5.37),
@@ -57,6 +58,7 @@
 Package: libkf5package-dev
 Section: libdevel
 Architecture: any
+Multi-Arch: same
 Depends: kpackagetool5 (= ${binary:Version}),
          libkf5coreaddons-dev (>= 5.37.0~),
          libkf5package5 (= ${binary:Version}),

--- End Message ---
--- Begin Message --- 
Source: kpackage
Source-Version: 5.74.0-2
Done: =?utf-8?q?Sandro_Knau=C3=9F?= <hefee@debian.org>

We believe that the bug you reported is fixed in the latest version of
kpackage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887308@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Knauß <hefee@debian.org> (supplier of updated kpackage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2020 23:16:47 +0200
Source: kpackage
Architecture: source
Version: 5.74.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Sandro Knauß <hefee@debian.org>
Closes: 887308
Changes:
 kpackage (5.74.0-2) unstable; urgency=medium
 .
   * Team upload to unstable.
 .
   [ Helmut Grohne ]
   * Mark kpackagetool5 Multi-Arch: foreign. (Closes: #887308)
   * Mark libkf5package-dev Multi-Arch: same.
Checksums-Sha1:
 299358bde448b4ffe506d6b4c80164ff4184942d 2896 kpackage_5.74.0-2.dsc
 f3ac32613237d83bfcce5744386bdcdc369de16f 11600 kpackage_5.74.0-2.debian.tar.xz
 a9586752af723bd18afada5a49ca036bcfd7a1df 14868 kpackage_5.74.0-2_source.buildinfo
Checksums-Sha256:
 63e643844cc3b9fdbd68bc9675ad43d4ba16565dc3c55e7914c272eadc44359b 2896 kpackage_5.74.0-2.dsc
 ee3191d1adb007c71d859b739ad83871d6cd1ed86567033c45658de6490b00e8 11600 kpackage_5.74.0-2.debian.tar.xz
 aeffe8cf2167931d98896b4404933654c76bf3b348f3432b8c40353ba5eaf59b 14868 kpackage_5.74.0-2_source.buildinfo
Files:
 e4346b5ee14bb32471f8e138dd1a0906 2896 libs optional kpackage_5.74.0-2.dsc
 aea63f94de431d90228ef6b65f82a77b 11600 libs optional kpackage_5.74.0-2.debian.tar.xz
 ec3cccd38f2ddb6a37610a164035980d 14868 libs optional kpackage_5.74.0-2_source.buildinfo

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

iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAl+OA5URHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjbvjRAAhYDRR10eI6gqSMeKw3qv9CcP4ZPgN6xU
+q3+/XB16IDVEN3jVg5N8ybMuKMr1SGuQjblpS9hHTG/i9X2IPDjLpL8G0GLPtto
cA17rJEKGW6OKd8E6lCnh2Ar1n4sLEbHTYu3QwqS8i3E7f2w+zcjv6ZShd3jcH8T
QUWIHniG0JR3R+UJobNUMDqC3PyiuBNAydO9od171eM9+Nx9HurSmcDLumy+J3RW
HkSfbwYyORljPJKQkmYqlZOUI30Ayan4J84iIwfKuZl9UtLMDio8onts/+D1Cq3M
YzBcv9BwUOwSS7a0AO31oH/uhlRRBcGI/2kxe6KE4yZ5l0L/B7GXRN0pz5Ks1lFf
wqBmY7W3XZ3frwTY6/DG1kUzH3dtblzY6XIioPTanxvZkBG/SNkNnEPSr2Aylc/Y
QQSKamwo8leMCUpGg8bG5QkHBWzi/i6Ex0qljiHImpJvqboL44Gx673osP0omT7u
e5q4A4WdjoBSyK0r8Knuqw+5ZGLTylZ2UaUkz3OKll0srWOe827k5uf/hD7jaw7w
TRCALAOylMkSsFx8Z/Bqbbd6q+5jKQLzYa8nQSKYBbRM2eonXosu6szc22iOS01A
8x8hEYg6MKqkAZZpb8uWhViLP1A7KADZR9P2kGoO+Lnn2n0PDgwh3kY+iAB5CIzI
aKp8UoAq3fU=
=xUWv
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: