I am not sure how packages.ubuntu.com generates its list but they were
published for all architectures on launchpad:
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.20.04.2
Also the debs are present on ports.ubuntu.com: http://ports.ubuntu.com
/ubuntu-ports/pool/main/libs/libseccomp
I don't see the updated applied to the ARM architecture. The versions of
arm64 and armhf at https://packages.ubuntu.com/focal/libseccomp-dev
still show 2.4.3-1ubuntu1. What's the story on that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This bug was fixed in the package libseccomp - 2.4.3-1ubuntu3.20.04.2
---
libseccomp (2.4.3-1ubuntu3.20.04.2) focal; urgency=medium
* Updated to new upstream 2.4.3 version for updated syscalls support
and test-suite robustness
- d/p/add-5.4-local-syscall-headers.patch: Add l
@ddstreet - is there anything I can / still need to do to get this into
-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and 2.
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:
https://people.canonical.com/~ubuntu-archive/pending-sru.html
which is used by some of the ~ubuntu-sru team members to find packages
that are 're
Ah thanks Dan! - I realise now that perhaps I should have had just the 1
bug report for both issues to make things simpler as having two seems to
have complicated things too much.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
since the libseccomp uploads to b/e/x-proposed also have this bug marked
in their changelog, it's showing up in the pending srus page as not
verified yet for the x/b/e libseccomp uploads. As mentioned in the
description, the initial problem only occurred in focal, but just for
verification purposes
Verified on focal using the following procedure - full log attached as
well:
# install seccomp
$ apt install seccomp
# try resolving getrlimit for aarch64
$ scmp_sys_resolver -a aarch64 getrlimit
-10180
# on the current focal version this fails to resolve correctly and
returns -10180
# enable -
FYI, I reran the bionic and eoan autopkgtests and there are now no
regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and 2.4.
Sorry, I reran bionic and *focal* autopkgtests and there are now no
regressions. Running eoan again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libse
FYI, I reran the xenial autopkgtests and they now pass.
** Tags removed: verification-done-focal
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.laun
FYI, I copied xenial-focal from the security-proposed ppa to -proposed.
Borrowing from the ubuntu-sru team's SRU verification text:
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback wil
** Changed in: libseccomp (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and 2.4
This bug was fixed in the package libseccomp - 2.4.3-1ubuntu2
---
libseccomp (2.4.3-1ubuntu2) groovy; urgency=medium
* Add missing syscalls for aarch64 (LP: #1877633)
- fix-aarch64-syscalls.patch: Backport of pending PR #235 from
upstream
-- Alex Murray Tue, 12 May 202
Thanks for the debdiff Alex. Uploaded to groovy-proposed.
** Changed in: libseccomp (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.
The attachment "libseccomp_2.4.3-1ubuntu2.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patc
@jdstrand would you be willing to sponsor that for me to groovy and then
I'll update this bug for SRU of this back to focal (and will add this
change also for the existing libseccomp SRU for eoan/bionic/xenial in LP
#1876055)
--
You received this bug notification because you are a member of Ubunt
Tested on an up-to-date groovy install:
amurray@sec-groovy-amd64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
Codename: groovy
amurray@sec-groovy-amd64:~$ dpkg -l seccomp
Desired=Unknow
** Patch added: "libseccomp_2.4.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+attachment/5370131/+files/libseccomp_2.4.3-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
See attached for a debdiff to fix this in groovy - this backports the PR
mentioned above to add these missing syscalls for aarch64.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.n
When generating the list of systems calls for aarch64, libseccomp uses
the generic kernel API headers rather than the architecture specific
ones - and so misses the definitions of getrlimit, setrlimit and clone3
for aarch64 - if this is changed to use arch-specific headers then we
can regenerate th
** Description changed:
- This was reported via the snapcraft forum:
+ 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
getrlimit
$ scmp_sys_resolv
22 matches
Mail list logo