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

Bug#924345: marked as done (xastir-data should be Arch: all)

Your message dated Fri, 28 Jun 2019 14:59:12 +0000
with message-id <E1hgsLI-0002XU-1V@fasolo.debian.org>
and subject line Bug#924345: fixed in xastir 2.1.2-1
has caused the Debian Bug report #924345,
regarding xastir-data should be Arch: all
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.)


-- 
924345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924345
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xastir-data
Version: 2.1.0-3
Severity: normal

The multiarch hinter suggests that xastir-data should actually be
"Architecture: all" rather than "any".

Looking at the control file, most of xastir-data's package stanza
looks like it was copied from xastir, but never updated. Same
Description, Depends, Recommends, Suggests. Looks like WIP and never
finalized.

Christoph

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: xastir
Source-Version: 2.1.2-1

We believe that the bug you reported is fixed in the latest version of
xastir, 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 924345@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated xastir 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: SHA256

Format: 1.8
Date: Fri, 28 Jun 2019 15:12:43 +0200
Source: xastir
Architecture: source
Version: 2.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 902096 924345
Changes:
 xastir (2.1.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version with better GNSS support. (Closes: #902096)
   * Convert xastir-data to Arch: all. (Closes: #924345)
   * Drop "reproducible patch", implemented upstream.
   * Drop gdal support, gone upstream.
Checksums-Sha1:
 ed4bad429cdc5f1e3daba0daa1774a0e9a5abac7 2338 xastir_2.1.2-1.dsc
 e8b3594b8fa49a93d6efc9f3d36742f7b5f346f5 2724737 xastir_2.1.2.orig.tar.gz
 d7ad1e064afef3d7dec8eb086225cab2edf4fb7b 20596 xastir_2.1.2-1.debian.tar.xz
 2b53352f4492a24f84dbdb158eb3738480f95c40 9756 xastir_2.1.2-1_source.buildinfo
Checksums-Sha256:
 6e55a329e36506bcec4eba15c6cd9786034bca06e77b82ee2f0ba2776a71e6fe 2338 xastir_2.1.2-1.dsc
 0c77e67eb318b483ffd51786de5e7c05b8b2e77342fb803895896a4de9f24f03 2724737 xastir_2.1.2.orig.tar.gz
 d157460780e4dd87032c73156e413032af30d40dfc4bdfb6183e3d02ac69895d 20596 xastir_2.1.2-1.debian.tar.xz
 8bfef5b8d4df751395f8add0f91d0df53d4c281164bca2d4bd2d9fb7ec7e7566 9756 xastir_2.1.2-1_source.buildinfo
Files:
 df825ff5b28790f730cb877463f48cfa 2338 hamradio optional xastir_2.1.2-1.dsc
 fe5a957a6a7ef679283bb18115b39391 2724737 hamradio optional xastir_2.1.2.orig.tar.gz
 42e388348404f28bf930fdd383b411ee 20596 hamradio optional xastir_2.1.2-1.debian.tar.xz
 6427f39cb36618ce1568925f280bcd2b 9756 hamradio optional xastir_2.1.2-1_source.buildinfo

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

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl0WGsgACgkQTFprqxLS
p65kmQ/+MFsh9Smy0Wu+PV7Gl3OfS42M/MpDbGYVKzsEcRDCPjuCe9XfBzJSfyD8
0+8zTcarSYGp5vV6jVo3qcsAF+uJOCH8ATe5bruqQHgzkCpgiTkA2+PqWah9JLGp
TqFtr/Z/BOJpe8ySRCzVkKzEbmU2NJPQqcT+B+/pwQApYT5RTJRgvn8eGykdRe1Y
Qh526VrjSh9sA6DvElxUljXrzuHtIab9wA1UikUCrl38qngTZ4VsfvdPgLXcC4+u
Y5OHxp/ILJEWXRzpWwBt8hfpY6TBaw7jMezjHHZUmV/5wjvTpONiOcv+K6R/fU9G
UzIeNsDz6TK7uJBNFabDV6sId5TbU/Rb2IgG4TFJaxzY1ZTowOJmE+gYnQ9miTrp
Wpo6nvyY8vZ0xjucTdn9ONbyxkuYe2wkwUNMCMw3va5KDAdlLPlWoySZb07BY0Ii
/1p2fjnEMy8a3Yko8/sXfHopEwwfafwHbhHBEZHGLDHYtl7Nxxdnwx745WnxDK0k
0ppGwIHJXHveIGB374eyiI/Ut0LPOg7lqZIFYVNQsaUOShTBbosNNXByNSPVlBw/
+ayDD9qzew8AgR+sgxUuSxGU/EH8i3zRy1TJWr1NbwKJM0GBre3LXMxxMttp7168
UM7JgFsaB79pB9Pw2LtSl1htUsIIoPTqP8l4gdXWqRDTWtwDjnc=
=dLrZ
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: