Your message dated Sun, 24 Nov 2024 21:20:07 +0000
with message-id <e1tfk1x-00fwv9...@fasolo.debian.org>
and subject line Bug#1051323: fixed in libseccomp 2.5.5-2
has caused the Debian Bug report #1051323,
regarding libseccomp: Please add support for loongarch64
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.)


-- 
1051323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libseccomp
Version: 2.5.4-1
Severity: wishlist
Tags: patch ftbfs
User: debian-de...@lists.debian.org
Usertags: loongarch64

   Dear maintainers,

The LoongArch architecture has been supported in libseccomp upstream [1], please see the following link [2]. Please add support for loongarch64 (64-bit LoongArch) in libseccomp source package [3].

We were unable to get information about the loongarch architecture from the libseccomp 2.5.4 source package.
The command line messages are as follows:
root@localhost:/home/buildd/libseccomp# apt source libseccomp
......omit
root@localhost:/home/buildd/libseccomp# cd libseccomp-2.5.4/
root@localhost:/home/buildd/libseccomp/libseccomp-2.5.4# grep "loongarch" -ri .
root@localhost:/home/buildd/libseccomp/libseccomp-2.5.4#

Would it be possible to include the support for LoongArch in the next upload?
Your opinions are welcome.
If you have any questions, you can contact me at any time.

[1]:https://github.com/seccomp/libseccomp
[2]:https://github.com/seccomp/libseccomp/pull/356
[3]:https://packages.debian.org/source/sid/libseccomp


thanks,
Dandan Zhang

--- End Message ---
--- Begin Message ---
Source: libseccomp
Source-Version: 2.5.5-2
Done: Felix Geyer <fge...@debian.org>

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

Debian distribution maintenance software
pp.
Felix Geyer <fge...@debian.org> (supplier of updated libseccomp 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: Sun, 24 Nov 2024 21:54:16 +0100
Source: libseccomp
Architecture: source
Version: 2.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook <k...@debian.org>
Changed-By: Felix Geyer <fge...@debian.org>
Closes: 1051323
Changes:
 libseccomp (2.5.5-2) unstable; urgency=medium
 .
   * Revert: Dynamically skip autopkgtests when the test runner already applies
     seccomp restrictions.
     - Container based backends usually apply a seccomp filter so it's better
       to declare the isolation-machine restriction.
   * Backport support for syscalls up to kernel v6.12-rc5 and loongarch64.
     (Closes: #1051323)
     - syscalls_update_to_Linux_v6.0.patch
     - tests_add_fstatfs_syscall_in_the_06-sim-actions.patch
     - arch_Add_64-bit_LoongArch_support.patch
     - tests_Add_64-bit_LoongArch_support.patch
     - doc_update_README_and_manpage_for_64-bit_LoongArch.patch
     - tests_Fix_wrong_syscall-error_in_test_29.patch
     - tests_only_use_bogus_syscall_numbers_in_test_29.patch
     - arch_unify_handling_of_syscall.tbl_in_arch-syscall-validate.patch
     - arch_adapt_arch-syscall-validate_to_Linux_6.11.patch
     - syscalls_Update_the_syscall_table_for_Linux_v6.12-rc5.patch
Checksums-Sha1:
 7498f9924b0e662b0f1ba77d2babe5830739621e 2708 libseccomp_2.5.5-2.dsc
 a9e4e2262c8a867497098686db11505288cb9c9b 39004 libseccomp_2.5.5-2.debian.tar.xz
Checksums-Sha256:
 e69657cf7b3cf0219d4c6d72c81db1f7f2d9a8e090fd8a983d17a4a80363dcc2 2708 
libseccomp_2.5.5-2.dsc
 82fa4dfbea7c0ce54d18781230b9625c44fc83f495ef4a468beb2a33e98897ef 39004 
libseccomp_2.5.5-2.debian.tar.xz
Files:
 00955fbdeea21c03f30519a0580b1c87 2708 libs optional libseccomp_2.5.5-2.dsc
 fa61fec7cd520deeecd39880e9795b99 39004 libs optional 
libseccomp_2.5.5-2.debian.tar.xz

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

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAmdDlKEACgkQ/iLG/YMT
XUVAWw/7BOEh1o8Br0rT6CKr1FK5TGio5EZChCy4qzr4N2cBQ0wbSI+IaC6SVh0G
CxtYD2KFmZR8V7CjILa7EPkeooN3KY3cH1id+0UPI8L02tG6fWZGi6+J9xwPI2Kw
UtLTA7Ixp112NpEzgZ27Kr5T7NbdaNCregZw8kfaL4eb+uZNMK1NXCXbUozIuK1f
tRY4UvtaflCEh/lzAjKyu9/VW7KssR3xwclmP6JVz9yQYQr+yA6jqmGVeIV85ext
v7ptw7GA36AmtmqJzqj/epGX3E4tX0T6X0VIsnushROo7LPfE+bsCwtvK2Mz3OG3
YFJBOP2JNAmPjMJPi9u3aSy7oJwr63wgXY9+Ec500M+KCDawX7KWtmeoXOgx3yWG
Xp1tb97ewAzeFt9nUNb764RinU2Uo9KGz9y3nbAahDNm6vxXWiic/CaxUyhzxeeQ
5VZ+dsUgBSg01EOmfTVP6IL0N4gExeruDIP9wx4tGdGoZC/Rk+VM/gaTi8391Qbp
VQUEAH+AkpqkxhB5vvgkpQGdayv+Zy8UTDxLJ7detXfv7yUxRHmUdaElSnuytWEt
oX7DAc8Ar17wXutTwj0sq5U9ASYjzlbDWpxLd9jD/MpOcVKM/g1Tjv/2mo4QwEex
HdjH+rT5YGJROSkC38Hi/M2LZQWgmzCzlOh/kJuPKhdp7trVD7U=
=01MD
-----END PGP SIGNATURE-----

Attachment: pgpNOhQk0DlDG.pgp
Description: PGP signature


--- End Message ---

Reply via email to