I think having 2 bugs is fine, it's just that doing so for libseccomp (where 
it's applied to all sru releases) adds both bugs to the pending-srus page:

which is used by some of the ~ubuntu-sru team members to find packages
that are 'ready' to promote to -updates, so this one may have caused
confusion as it was still showing this bug as yellow (i.e. not verified

I think the ~ubuntu-sru team has tooling (probably from ubuntu-archive-
tools project) that automatically updates all listed bugs with
'verification-RELEASE-needed' tags, it might be useful to include
something like that into security tooling to add similar tags based on
the changelog 'LP: #NNNNNN' bug tags.

Anyway, hopefully this can be released to -updates; we have another
libseccomp patch we'd like to upload from bug 1861177.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.

  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  This was reported via the snapcraft forum[1]:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  $ scmp_sys_resolver -a aarch64 getrlimit

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  $ scmp_sys_resolver -a aarch64 getrlimit


To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to