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

Bug#956353: marked as done (usermode: Please stop using deprecated <selinux/flask.h> and <selinux/av_permissions.h> headers)



Your message dated Fri, 10 Apr 2020 16:54:37 +0000
with message-id <E1jMwvN-000Ek9-VZ@fasolo.debian.org>
and subject line Bug#956353: fixed in usermode 1.113-2
has caused the Debian Bug report #956353,
regarding usermode: Please stop using deprecated <selinux/flask.h> and <selinux/av_permissions.h> headers
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.)


-- 
956353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956353
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: usermode
Version: 1.113-1
Severity: important
Tags: sid bullseye
User: selinux-devel@lists.alioth.debian.org
Usertags: selinux flask-removal

Dear Maintainer,

Your package is using either <selinux/flask.h> and/or
<selinux/av_permissions.h> and hardcoded SELinux security classes or
permissions. This is deprecated for about 5 years and upstream has
now decided to remove these completely in the upcoming 3.1 release.

Your package should be ported to dynamically query the security
classes and permissions instead of relying on the hardcoded ones and
remove these headers.

I will bump the severity of this bug to serious when libselinux 3.1
is finally released as your package will FTBFS.

Don't hesitate to contact me if you have any questions.

Kind regards,

Laurent Bigonville 

--- End Message ---
--- Begin Message ---
Source: usermode
Source-Version: 1.113-2
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated usermode 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: Fri, 10 Apr 2020 12:06:56 -0400
Source: usermode
Architecture: source
Version: 1.113-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 956353
Changes:
 usermode (1.113-2) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/0002: Stop using deprecated selinux headers.
     (Closes: #956353)
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 5a0eea59762d13b66f0956726c78133ada619892 1982 usermode_1.113-2.dsc
 3faa0bb91ab84499b7f7c153f0029e7dd34a841d 6388 usermode_1.113-2.debian.tar.xz
 152d85f1c79456fd788816b29eb623b0be085385 12375 usermode_1.113-2_amd64.buildinfo
Checksums-Sha256:
 e44dbf9cd017f763d6129c2c41c03699e91c85fe582e1f61e2160f25452f1032 1982 usermode_1.113-2.dsc
 cbb8b5f35a2d2a366224fb24aedd771d065cd9433b72e84a7c56096c08b2ffb0 6388 usermode_1.113-2.debian.tar.xz
 83b6912f47bb25e4b70d21ec9dde9538708d7707cb7f1ce0f50ef44f36d2ff43 12375 usermode_1.113-2_amd64.buildinfo
Files:
 c3fc40ec1af73b6e2e0cbce3124916b6 1982 x11 optional usermode_1.113-2.dsc
 5eb063fcb04281538a04112bf2378f1b 6388 x11 optional usermode_1.113-2.debian.tar.xz
 26cdf530306007c951a86aec12e42495 12375 x11 optional usermode_1.113-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl6QnisACgkQwpPntGGC
Ws6qrw/+I6XLvwclHVILQM/Jwtib86pg7K4vH3yj0O+iFIj5w+BeZf3M20qhBXlA
jx7+quaf/4otC2j6rOrcucpXjI4V41UEA+OzwEs7fIYly+zx+paIEyC0u7dk/6K9
IIWLUiQ6luVtyQMFokZ2xEi3SupROSaQRIMr42mqeV+vMjHFv/uc1ljwLtQtqGX9
BoR/1aBZ8fYgSGCYLfzOBp/1vCmsr3z98ja1yAY9IUniZOYRP2xuXnXM4ENcj6VN
J+TBD4EnnZWTS8V9Vq+wW1yGTKj+lpZqJFl8pL29MpA9c50NPVflpWNgENcgwgN1
mdzodYqid6U/MSKBvCSpXabRslIiOln3pyLl6A6L+9RtlAzItSRpUydtIYLzu1a2
FEHVfAKg85WQ+LopOsDaEmKpUlA52+xGUEQ9rLNJzK1oRiRyrB5oeDXtVhykbw2o
FVlACxPqoKR0FIdSD4M8Vpmc1eKUBHyM31qvXAOj2AuVp6R0WWnjsNiKcsMVgoNy
lhg4CpizX5dsoKWa3zVZ7omzkSCE8qxXyFCbWqVt2TvGlryYndQ6q0LEHumTkmlc
xnMAPcxY5suEc6Ce8mR8NjXON9u8HvOv7oeiEX0AO3/glvwiebx1Q1yrHJSQA7kB
Z8VnNZa5I+NkVYGOIWhD3eIbYx5wocNkzEoRfkgNhsrOPB6JoKY=
=jvf5
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: