Your message dated Sun, 02 Feb 2025 13:13:26 +0000
with message-id <e1tezmw-009lga...@fasolo.debian.org>
and subject line Bug#1094758: fixed in sep 1.2.1-8
has caused the Debian Bug report #1094758,
regarding sep: FTBFS with numpy 2.x: 'int_t' is not a type identifier
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 ow...@bugs.debian.org
immediately.)


-- 
1094758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sep
Version: 1.2.1-7
Severity: serious
Tags: ftbfs
Control: block 1082237 by -1

https://buildd.debian.org/status/fetch.php?pkg=sep&arch=amd64&ver=1.2.1-7%2Bb2&stamp=1738253327&raw=0

Error compiling Cython file:
------------------------------------------------------------
...
# Source Extraction

# This needs to match the result from extract
cdef packed struct Object:
    np.float64_t thresh
    np.int_t npix
    ^
------------------------------------------------------------

sep.pyx:555:4: 'int_t' is not a type identifier


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.8-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Source: sep
Source-Version: 1.2.1-8
Done: Ole Streicher <oleb...@debian.org>

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

Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated sep 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 31 Jan 2025 14:20:56 +0100
Source: sep
Architecture: source
Version: 1.2.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 
<debian-astro-maintain...@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Closes: 1094758
Changes:
 sep (1.2.1-8) unstable; urgency=medium
 .
   * Numpy 2.2 compatibility (Closes: #1094758)
Checksums-Sha1:
 70540cde902bed2034b1342ce5b186bfeac8e2c2 2241 sep_1.2.1-8.dsc
 00d93fde77147396c9c7838b849aa4de69c609f3 5180 sep_1.2.1-8.debian.tar.xz
Checksums-Sha256:
 8110d1324c9a6d3a0e1585be4b742a94472306336c995baff21c6d80cb4408ec 2241 
sep_1.2.1-8.dsc
 ff00a8846ebc05e989dd9ba00897b53f670ac6e0ba235ac497cf167678393e56 5180 
sep_1.2.1-8.debian.tar.xz
Files:
 582e5d61805dba2209bae5ac7c027935 2241 python optional sep_1.2.1-8.dsc
 85a8c38d88d2ae814a99d707c3fbe330 5180 python optional sep_1.2.1-8.debian.tar.xz

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

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmefaHQACgkQmk9WvbkO
GL35rg//RVsPuY3hvHBFvxej9NUA7MHNaywu0HbE613MuGa27ACSQaaGjTpBUHnX
u6Ou6LmH7Sjmrl5ynf68On+TgGePLO7KfILWWIcyrXDPlGB3+EC9fZ0gTsRF9tlk
A1gA4ZUBQHaJoxOsBM13TdGQIx4/Y3AFKCUrPiuLy3GXRLVWQ709eUZt1VlkKWuz
ZuAJUjuuJeSy//aqNcnT0DVAG858siSdj6mOdZ/o6mC/YJ32sgMu+5J8mr/hH/il
q+jGh9eKMSldQQgWOK+64piPk5IQQjcTW2Vo20KnobwBk1tePgqdby3yzv3Zegmi
sh3lyxCobqBf48RqT4CkIY3CeCDlZjuwXk3hMDcMG7KYcuQ+moqyPDM3RRqF6DF1
kwxdMybl89HxdW6FVItaVE5Tx70Zo8GdaFB1MyXujA+OR6Cs5vFwqUnxGdRIC8We
iqIM18tt2vk1ddOvoPEc04Mn+ipdpRrj96ThhktjyQdxu5L/uBUBs1li7goq1t1Y
vDOT1VldQektzWVLlFbyOIOpO8xQlZt6OECpNZssuXdC/imp9cfWY46lbUN+07js
UGH0WeyfmcRdmGIIJ+Ig/+EBixcb9Naz8LOpRAt/fJP891URb21XTHJSF/eu8d+e
Uh58Rn4KiZ03uf5++Y1oYggXfYS88muP6YQO5R9BZUQ7NLGbX8k=
=cP5A
-----END PGP SIGNATURE-----

Attachment: pgpSwx1IoMItE.pgp
Description: PGP signature


--- End Message ---

Reply via email to