You have another service listening on port 80. Figure out what it is
and either stop it or uninstall it and then attempt to run/install
nginx.
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: nginx (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062058
Title:
Add a UFW firewall config to support QUIC
To manage notifications
*** This bug is a duplicate of bug 277 ***
https://bugs.launchpad.net/bugs/277
The 404 issues are tracked in 277.
GPG keys updates were already uploaded, however they may be stuck in
Proposed still pending a fix for the 404 issues.
Due to how versions of software are updated in
*** This bug is a duplicate of bug 277 ***
https://bugs.launchpad.net/bugs/277
** This bug has been marked a duplicate of bug 277
Download URLs are broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your configuration is bad. Refer to the error log output in journalctl:
mar 10 19:00:41 wojciech-To-be-filled-by-O-E-M nginx[1323]: nginx:
[emerg] cannot load certificate "/etc/diaspora/ssl/localhost-
bundle.pem": BIO_new_file() failed (SSL: error:02001002:system
library:fopen:No such file or
torbrowser-launcher is only a tool to help download and update (and run)
Tor Browser. It is not actually Tor Browser.
If you are having issues with Tor Browser, I suggest you enlist the help
of the Tor community as issues with Tor Browser itself are not related
to the Launcher tool.
** Changed
Something with the debdiff broke the translations components, so the
debdiff is rejected.
However, the components provided here work, so uploaded. Both are in
building/pending state.
** Changed in: golang-github-openprinting-goipp (Ubuntu)
Status: New => In Progress
--
You received
Note ipp-usb applies cleanly, so that's "in progress", while goipp is
"Incomplete"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055346
Title:
Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for
Rejection on goipp 1.1.0.
Fails to apply cleanly. Please address the differences from upstream
that are returned by dpkg-buildpackage.
---
$ debuild -S -sa -d
dpkg-buildpackage -us -uc -ui -S -sa -d
dpkg-buildpackage: info: source package golang-github-openprinting-goipp
dpkg-buildpackage:
** Changed in: ipp-usb (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055346
Title:
Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble
To manage
** Changed in: golang-github-openprinting-goipp (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: ipp-usb (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
"failed to install/upgrade" also means that a package failed to
configure. If as Simon says the packages were left unconfigured, then
that means the package is "Installed but failed to restart on upgrade"
which is an action the postinst scripts execute. So it may not be an
'installer' failure
Looks like during your upgrade a certificate went awry, but this isn't
an NGINX issue, it's the maintenance of your system on your end.
From the journalctl data:
Jun 04 14:21:05 heliopolis-aws nginx[44002]: nginx: [emerg] cannot load
certificate "/etc/ssl/certs/heliosd.crt": BIO_new_file()
NACK as is. (negative acknowledgement aka "Debdiff Rejected")
You are attempting to submit a new upstream version not in the Ubuntu
repositories. Unlike Debian, an Ubuntu backport requires a little more
work to push this in.
Jammy has 03.00.00.0423-1. Your debdiff is for 03.00.00.0429 which is
If you can give me an extra day or two (I'm suffering from COVID right
now), I can sponsor this. I'll let the other backporters handle
approval, etc. but uploading the package is something that only takes a
few minutes on my part. (Just need the patience - COVID is evil)
--
You received this
If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.
Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark
*** This bug is a duplicate of bug 1967572 ***
https://bugs.launchpad.net/bugs/1967572
Duplicate of #1967572 due to same traceback on failure.
** This bug has been marked a duplicate of bug 1967572
torbrowser-launcher crashed with move(self, int, int) in main(): argument
1 has
Note that your Debian source target will be NGINX 1.20.2-1 once it
lands, this was uploaded to ftp-master by myself today after I was given
access to upload by Ondrej Novy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You have a symlink in /etc/nginx/sites-enabled that points to a
nonexistent config file:
nginx[1326]: nginx: [emerg] open() "/etc/nginx/sites-
enabled/frappe.conf" failed (2: No such file or directory) in
/etc/nginx/nginx.conf:62
This is not an NGINX package bug but a local config issue.
**
*** This bug is a duplicate of bug 1969752 ***
https://bugs.launchpad.net/bugs/1969752
** This bug has been marked a duplicate of bug 1969752
oss4-dkms '-mfloat-abi=hard' build failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
FYI #1969145 has been closed as a duplicate of this bug, and sponsors
unsubscribed from that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752
Title:
oss4-dkms '-mfloat-abi=hard' build
YOu're welcome, that's the workaround for these cases.
Note that this exact issue was 'discussed' back in 2015 by the upstream
Debian team and they rejected changing it because IPv6 being disabled is
"non-standard", and a user/admin level decision at the endpoints of
things, so when anything
This is a pretty old issue but in Debian they made a decision to not
accomodate this back in 2015 for when IPv6 is disabled on systems on the
basis of "not only is it non-standard but it's nonsensical":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779825#97
The workaround for this is when
CentOS uses completely different packaging than Debian. The problem
here is that the Debian and Ubuntu developers of NGINX decided to
support "the most common setups" - the Debian and thus Ubuntu default
configurations ship both IPv4 and IPv6 support. You can fix this by
changing the
How are you launching the launcher? So we can have a 'minimal
reprocudible example' to test with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967572
Title:
torbrowser-launcher crashed with
Tested similar BTRFS root partition layout here, and it exploded as
stated here. I was testing in a VM with a fresh ZSync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966774
Title:
btrfs
Everyone posting 'installation failure' cases, please open separate
bugs. The underlying issue that *this* bug was referring to is fixed,
and the new failures are due to other problems, so please open different
bugs.
** Summary changed:
- Ubiquity crashes Kubuntu Jammy after selecting "install
** Changed in: lubuntu-meta (Ubuntu)
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831220
Title:
Add hexchat by default on all ubuntu flavours
To manage
Like Studio, Lubuntu ships quassel. We have no intention on the Lubuntu
Team to ship hexchat instead at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831220
Title:
Add hexchat by
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831220
Title:
Add hexchat by default on all ubuntu flavours
To manage
archive admins dont think i386ing the RPM source is a good idea based on
my brief discussiom in #ubuntu-release
debugedit has splitsource in later versions, perhaps a split-source is
needed here. However I would suggest we defer to archive admins for
best approach here
--
You received this bug
[ubuntu/jammy-proposed] openssl 3.0.2-0ubuntu1 (Accepted)
Uploaded to proposed, it has to go through the usual process of passing
autopkgtests and such. It shouldn't need any additional package
rebuilds because of no ABI changes but expect autopkgtests to run hot a
while
** Changed in: openssl
I've got some extra cycles later today, so I'll happily help the
Security team out and get this uploaded later today (Eastern US time for
clarity sake when I say "later today")
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: op
Then this should be trivial to backport, if you need it backported
waveform and you don't want to handle the actual backport uploads, I'll
take this on, I have some spare cycles today this afternoon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
waveform: Paride: given this bug, wouldn't this be more suited for full
SRU and rebuilds? I'm wondering whether this is truly a backportable
case because this requires rebuild of all affected packages, and if
anyone builds with debhelper in backports (which is NOT available in
standard build envs
Whoops looks like we had some collission in terms of assignments.
Reassigning to waveform.
Once this is looked at and looks OK at the Canonical level, then the
Backports Team will take over backporting this. Keep in mind that since
the original Backports process is mostly scrapped, the Backports
Not a bug, you just have bad config.
From your logs:
> Mar 20 13:32:34 spark nginx[68287]: nginx: [emerg] a duplicate default
server for 0.0.0.0:80 in /etc/nginx/sites-enabled/embracehealth.io:209
So you need to figure out where else you've defined default_server and
remove it from the other
I agree with mapreri. Backports is not how to get bug fixes for crashes
and such into older releases.
Please follow the procedure for SRU, not Backports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565880/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565878/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565879/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
apport information
** Attachment added: "Casper.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565874/+files/Casper.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963697
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565877/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565876/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1963697/+attachment/5565875/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: KDE
DistroRelease: Ubuntu 22.04
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed
maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu
I offered to test and assist too, this is the Python TraceBack from the
crash I currently see/get:
Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 668, in
main(oem_config)
File "/usr/lib/ubiquity/bin/ubiquity", line 652, in main
install(args[0],
This was fixed in 2.4.0-2 from Debian which was synced down with the
OpenSSL 3.0 patches.
** Changed in: xca (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm an evil person so I poked and prodded upstream to make sure they
address this. OpenSSL 3.0 compat is in a branch here -
https://github.com/chris2511/xca/compare/xca-240-ossl3 - which succeeded
passing the build tests in my 'junk drawer' PPA which is used for build
tests on all archs with
Sponsoring alone doesnt approve it for Backports, the Backports team has
to review and approve. I'll take a look later, in the middle of my FT
job right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nginx (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544607
Title:
nginx dav module doesn't return directories with space in names in
Unsubscribing sponsors for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946161
Title:
Add GTK4 support
To manage notifications about this bug go to:
** Summary changed:
- [BPO] Backport 5.6.0 from Jammy
+ [BPO] Backport opencpn 5.6.0 from Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956004
Title:
[BPO] Backport opencpn 5.6.0 from Jammy
** Bug watch added: Debian Bug tracker #1001498
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001498
** Also affects: xca (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001498
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: xca (Ubuntu)
Status: New => Confirmed
** Changed in: xca (Ubuntu)
Importance: Undecided => Critical
** Description changed:
- It looks like XCA does not support OpenSSL 3.0 yet.
+ It looks like XCA does not support OpenSSL 3.0 yet. As such, it cannot
+ be included or
Public bug reported:
It looks like XCA does not support OpenSSL 3.0 yet.
I've submitted this as an upstream bug
https://github.com/chris2511/xca/issues/320
** Affects: xca (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
kskb: What Debian has done is 'patch' it to use the lua mod that is the
version *before* requiring Resty Core. However, Ubuntu is not Debian
and whether Debian uses Lua module or not still is not bearing on the
Server Team's decision to not include or ship the Lua module in future
releases of
** Also affects: lxqt-policykit (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: lxqt-policykit (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Won't Fix for later releases, dropped in later versions of NGINX
packaging in Repositories (21.04 at least)
** Also affects: nginx (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: nginx (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: nginx (Ubuntu)
The Lua module has been dropped in Ubuntu since 21.04 due to many more
library requirements to keep it up to date and functional. As such, we
are not shipping Lua module anymore and do not need the Lua
dependencies.
Are you looking for this for a specific Ubuntu release, or for the
future, as
so is the goal here to wait for a sync from Debian for this? If so, I'm
going to unsubscribe Sponsors at the moment since there's no task for
Sponsors to do here right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943840
Title:
[FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
To manage notifications about this bug go to:
*TECHNICALLY* you aren't wrong. However, let's consider that I"ve been
around since 2009 in the Ubuntu world (2012 when I started deep diving
into it technically) and NVIDIA has *never* provided any drivers binary
or otherwise that work on non-x86 infras. I don't see any time yet that
NVIDIA is
Why is this required?
Currently, there are **no** binary drivers for NVIDIA which nvidia-
settings would work with in RISCv, based on my research, meaning that
from my POV there's no justification for making nvidia-settings work in
RISCv.
** Changed in: nvidia-settings (Ubuntu)
Status:
** Changed in: tachyon (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943253
Title:
Enable riscv64 build of all the packages
To manage
$ dput tachyon_0.99~b6+dsx-9ubuntu1_source.changes
Trying to upload package to ubuntu
Uploading to ubuntu (via sftp to upload.ubuntu.com):
Uploading tachyon_0.99~b6+dsx-9ubuntu1.dsc: done.
Uploading tachyon_0.99~b6+dsx.orig.tar.xz: done.
Uploading
Blah keyboard failure. In the future, make sure that you include the
Launchpad bug numbers to the changelog so the bugs get closed
automatically when the packages are accepted in and processed.
I'll "Fix Released" this bug once it builds and is in the release and
not in proposed.
--
You
For the future, though, make sure to include the Launchpad bug numbers
so that they get closed automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943253
Title:
Enable riscv64 build of
** Changed in: tachyon (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943253
Title:
Enable riscv64 build of all the packages
To man
Per Steve, I'm unsubscribing sponsors on this for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943152
Title:
riscv64 packages are not published for impish
To manage notifications about this
I checked with Foundations team on this. The binaries for sasmodels
were removed by doko due to FTBFS. I've handed this off to Steve
Langasek (i.e. back to Foundations Team) for acting on this or not,
because of the FTBFS binaries being removed.
I"m leaving Sponsors subscribed, pending me
Foundations has their own sponsors and as this is currently assigned to
the Foundations team, I"m going to suggest you discuss with the
Foundations team first. If they need someone else to sponsor it, I'll
be happy to.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: sbsigntool (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941888
Title:
FFe: sbsigntools 0.9.4
To manage notifications about this
Build was successful against Impish Proposed, uploading with the changes
I mentioned - the correct version string and the full path to the
sbkeysync patch in the changelog. Also adjusted the bug number to point
to this FFe bug, which as stated in the dupe I've defined as the
'master' tracker for
Diff in bug 1938438 (duplicate of this bug) is okay...ish. It has some
things that're incorrect or incomplete and need addressed for future
uploads and merges.
(1) Version string should be -2ubuntu1 - this is the FIRST package
revision that is Ubuntu specific based on 0.9.4-2 from Debian. Refer
: (unassigned) => Thomas Ward (teward)
** Changed in: sbsigntool (Ubuntu)
Status: New => In Progress
** This bug has been marked a duplicate of bug 1941888
FFe: sbsigntools 0.9.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: sbsigntool (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941888
Title:
FFe: sbsigntools 0.9.4
To manage notificati
NGINX does not include, and technically does not support, the Passenger
extensions.
This is a problem with your configuration per the error output from
`systemctl -l status nginx` which was attached when you filed the bug:
Aug 25 16:11:32 thinkpad nginx[69358]: nginx: [emerg] unknown directive
** Changed in: pastebinit (Ubuntu)
Status: New => Confirmed
** Also affects: pastebinit (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: pastebinit (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: pastebinit (Ubuntu Focal)
** Changed in: torbrowser-launcher (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933886
Title:
tor browser not launching in impish (flavors;
** Summary changed:
- multiple urls not opening on commandline
+ URLs not opening in Tor Browser when passed as command line arguments
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754431
Title:
In 0.3.2, we know that the torbrowser-launcher does not actually launch
the URLs.
When executed on the command line directly we see this on a Focal
system:
$ torbrowser-launcher https://cnn.com
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.3.2
** Also affects: libmaxminddb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: libmaxminddb (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: libmaxminddb (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are
Unsubscribing sponsors as I've sponsored this. Server Team: do me a
solid and keep an eye out for any autopkgtest failures in case I miss
them - I have a lot of mail so sometimes I don't see the failure notices
:P
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Uploaded to impish-proposed. Should be building, and provided no
autopkgtests fail it should migrate to impish repos on its own.
** Changed in: squid (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: squid (Ubuntu)
Status: Triaged => In Progress
** Changed in: squid (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934891
Title:
hanged in: squid (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: squid (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
** Changed in: mongodb (Ubuntu Focal)
Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)
** Changed in: mongodb (Ubuntu Impish)
Assignee: Heather Lemon (hypothetical-lemon) => (unassigned)
** Changed in: mongodb (Ubuntu Impish)
Importance: High => Undecided
** Changed in:
Confirmed, removed from Groovy onwards, see
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1879494
Removing the hirsute+ tasks because of license incompatibility blocks.
** Changed in: mongodb (Ubuntu Groovy)
Status: New => Won't Fix
** Changed in: mongodb (Ubuntu Hirsute)
Also verify whether Hirsute and later are also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933378
Title:
Unable to build from source mongodb-server-core - focal
To manage
Does mongodb still need the requests library, but in Python 3? If so
the removal here without inclusion of the python3 requests library will
break things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Viktor:
No, not all buggy modules are going to get removed, especially if
there's patches. However, to *fix* the issue with the Lua module, and
because it has **future** requisite dependencies on OpenResty Core, the
Lua module was removed.
This also was not removed in *older* releases, it was
I did some testing with the adjusted X abstractions, and porting the
torbrowser-launcher apparmor rules back as part of testing. With the X
abstractions added, and the adjusted X abstractions working, all looks
good there.
The other component of the SRU is a tests fix, that will only show in
the
** Changed in: torbrowser-launcher (Ubuntu)
Status: Confirmed => In Progress
** Changed in: torbrowser-launcher (Ubuntu)
Importance: Undecided => Medium
** Changed in: torbrowser-launcher (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received
** Changed in: apparmor
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932331
Title:
ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish
To
** Changed in: apparmor (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Hirsute)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: apparmor (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932331
Title:
ubuntu_qrt_apparmor: i18n test fails on arm64
Thanks for the confirm, Steve. However, these may be 'upstream' but
aren't yet in Ubuntu, so. The two issues on my radar are the one I
discovered needs fixed for something to properly WORK for torbrowser-
launcher, and the other is this one Seth poked at me to include on any
SRU for HIrsute.
Seth Arnold has affirmed the patch is going to fix things, so it's been
reviewed by Seth.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932331
Title:
ubuntu_qrt_apparmor: i18n test fails on arm64
SRU template applied because this'll need SRU'd as well, after this
lands in Impish.
** Description changed:
+ [Impact]
+ Any application that requires access to X11 sockets for the Display may want
to include abstractions/X in the AppArmor rules, which usually will include
rules that we would
1 - 100 of 2326 matches
Mail list logo
