We just checked with cjwatson and vorlon, it looks like this might be a
stuck sync and mirror process. They're killing that and manually
syncing it now, so the mismatch might go away in the next ISO build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Discussed via IRC, but libmaxminddb is a dependency that needs to be in
Main if we're going to get this third-party module (shipped inside
src:nginx) binary-included in Main.
The module is still actively reviewed by the third party developer but
has not had any code changes to the underlying C mod
Public bug reported:
The pastebin.com fallback (in the event the distro can't be determined
by `distro` module) does not function. While this does not block any
functionality for distro-specific pastebins such as paste.u.c or
Debian's paste, it DOES break pastebin.com functionality, making
pasteb
This issue was resolved by cjwatson and vorlon addressing the
mismatching versions between what's in the repos and what was being put
on the ISO (caused by a desync in the local ftp mirror the builder was
using).
This is not a Cala bug nor a Grub bug, this was an ISO builder issue.
** Changed in:
Your configuration is pointing to a nonexistent certificate somewhere in
the configuration.
This is the relevant section in your logs:
mei 27 10:26:01 Kernoitje2 nginx[12175]: nginx: [emerg] cannot load
certificate "/etc/ssl/meet.jit.si.crt": BIO_new_file() failed (SSL:
error:02001002:system libr
That is something you have to discuss with NGINX and their developers
upstream. And is not something that we can do at the Ubuntu level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929878
Title:
** Changed in: jack-rack (Ubuntu)
Assignee: Ubuntu Studio Development (ubuntustudio-dev) => (unassigned)
** Changed in: jack-rack (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
ERR:NOREPRO
Test environment: Ubuntu 21.10, fresh install. Wayland is the
environment (because Wayland is default)
** Changed in: torbrowser-launcher (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Okay, so, I did some heavy hardcore digging.
The core execution string at the deepest level is something like this:
`$HOME/.local/share/torbrowser/tbb/x86_64/tor-browser_en-
US/Browser/firefox --class "Tor Browser" -profile
$HOME/.local/share/torbrowser/tbb/x86_64/tor-browser_en-
US/Browser/TorBr
More development chaos:
I downloaded Tor Browser from upstream directly. This issue is not
reproducible on Upstream Tor Browser, which doesn't use a launcher
mechanism like torbrowser-launcher does.
More digging for me, now...
** Changed in: torbrowser-launcher (Ubuntu)
Status: Incomplet
** Attachment added: "Crash stderr output."
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1933886/+attachment/5507948/+files/torbrowser-crash-error.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Did some more tracing. Narrowed this down to some kind of AppArmor
issue in the Lubuntu environment possibly, but more importantly, this
error shows up:
" Gtk-WARNING **: 01:33:02.634: cannot open display: :0"
This suggests that apparmor might be blocking things?
** Attachment added: "apparmor
Core problem traced back to what LOOKS to be a regression in AppArmor
owned by the Security team.
For all intents and purposes, `/etc/apparmor.d/abstractions/X` should
give read-write to the display sockets. HOWEVER, this has changed in
AppArmor. Even if we include the abstractions if they exist
Public bug reported:
In Focal, abstractions/X has the following section in it:
# the unix socket to use to connect to the display
/tmp/.X11-unix/* rw,
unix (connect, receive, send)
type=stream
peer=(addr="@/tmp/.X11-unix/X[0-9]*"),
unix (connect, receive, send)
type=s
Related Security Team bug for the apparmor regression:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1934005
Related Upstream bug because there'll need to be some abstractions included in
the apparmor rules:
https://github.com/micahflee/torbrowser-launcher/issues/588
** Bug watch ad
NOTE: The AppArmor profiles are **brand new** in Impish, and as such are
incomplete. This plus the X abstractions regression explains why this
is broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
So, fixed upstream, but not present in Hirsute or Impish... guess its
patching time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934005
Title:
abstractions/X: Possible regression of X session fun
** Changed in: apparmor (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/1934005
Title:
abstractions/X: Possible regression of X sess
** Changed in: apparmor (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/1932331
Title:
ubuntu_qrt_apparmor: i18n test fails on ar
Has the fidelity of the patch attached here been vetted by anyone?
(Seth Arnold asked me to take a look @ this while I'm pushing hard for
1934005 to fix some major chaos so this gets in with that update / SRU)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Also affects: apparmor (Ubuntu Impish)
Importance: High
Assignee: Thomas Ward (teward)
Status: New
** Also affects: apparmor (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Hirsute)
Importance: Undecided => High
** Changed
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
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 H
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. (Or
** 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 Hirs
** 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.
** 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 man
** 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
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
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 on
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.
https://bugs.launchpad.net/bugs
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 notifications
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)
** 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:
ned)
** Changed 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.n
** 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:
squid
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 subs
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, whi
** 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
This is not a bug in Ubuntu, in fact this should instead be submitted to
the mirrors team as a ticket at r...@ubuntu.com and *not* via the Ubuntu
bug system.
Closing as "invalid" as it's not a bug in Ubuntu, rather a separate
issue not related to a bug in Ubuntu.
** Changed in: ubuntu
Stat
** Changed in: ubuntu
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918137
Title:
Ubuntu 21.04 Hirsute: i386 package cleaning process
To manage notifications ab
Public bug reported:
`fwupd` has an internal logging mechanism, and during firmware updates
attempts to rebuild TPM PCRs based off event logs. Unfortunately, this
has known bugs in versions before 1.3.12, 1.4.7, 1.5.0.
Per their wiki on this (https://github.com/fwupd/fwupd/wiki/TPM-PCR0
-differs
** Attachment added: "Example logs with TPM PCR0 failures."
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1926311/+attachment/5492799/+files/fwupd_logs_focal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1883568 is related,
but 1.3.11 does NOT properly fix the TPM PCR0 calculation, per fwupd
upstream.
** Summary changed:
- "TPM PCR0 differs from reconstruction" for device firmware
+ "TPM PCR0 differs from reconstruction" for device firmware err
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
https://github.com/micahflee/torbro
** 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:
U
** 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; l/x
** Changed in: nginx (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/1893753
Title:
libnginx-mod-http-lua 0.10.11 not compatible w
You need to verify the rdepends as well. This will not move until this
gets the rdeps tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905613
Title:
Please backport v4l2loopback 0.12.5-1 (uni
I misread - Reverse-Suggests don't need tested, they're listed for
completeness sake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905613
Title:
Please backport v4l2loopback 0.12.5-1 (universe) fr
>From your logs, something else is already listening on Port 80. Find
that process and shut it down, then attempt installation and
configuration of NGINX again.
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
B
Upload in progress, it should land in the queue shortly. Thanks,
Lukasz.
** Changed in: nginx (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/1790149
T
Tested and confirmed working in Bionic.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
Adding --with-compat would allow for those compiling dynamic modules
separately to include them in the NGINX packages.
This should be considered for Ubuntu and Debian as well.
** Affects: nginx
Importance: Wishlist
Assignee: Thomas Ward (teward)
Status
Note that for Ubuntu, this will not be done for Cosmic - we are too late
in the dev cycle to do this for Cosmic, so any changes to this which
would add this to the Ubuntu packages will be for D-series (whatever it
is named). This needs discussed first, however, before it gets included
in the Ubunt
I realized in IRC I failed to explain properly what happens here.
Related:
https://forum.nginx.org/read.php?29,270210,270213#msg-270213 and
http://mailman.nginx.org/pipermail/nginx-devel/2018-May/09.html
IN a nut-shell, what --with-compat does is allow people who build NGINX dynamic
modules
We are too close to Cosmic release to get this into Cosmic (Won't Fix'd
for Cosmic). This will be included in the D-series cycle for Ubuntu.
** Changed in: nginx (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Also affects: nginx (Ubuntu Dd-series)
Importan
Mainline PPA packages are building with --with-compat in the staging
PPA, if all goes well I'll copy it over to the actual Mainline PPA.
Stable PPA is in progress but more slowly due to other work
requirements.
** Changed in: nginx (Ubuntu Dd-series)
Assignee: (unassigned) => Tho
Stable PPA packages are now building with --with-compat in the staging
PPA, they'll be copied over if all goes well to the main Stable PPA as
well.
Ubuntu changes are on hold until D-series cycle opens.
** Changed in: nginx/stable
Status: In Progress => Fix Committed
--
You received this
PPAs now have --with-compat enabled. Updated packages are copying in
from the staging PPAs now.
** Changed in: nginx/mainline
Status: Fix Committed => Fix Released
** Changed in: nginx/stable
Status: Fix Committed => Fix Released
** Changed in: nginx
Status: In Progress =>
** Bug watch added: Debian Bug tracker #897926
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897926
** Also affects: nginx (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897926
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Public bug reported:
[Reason for SRU]
Ubuntu Cosmic 18.10 ships with OpenSSL 1.1.1, which has TLS 1.3 support.
It was intended to enable TLS 1.3 in the default nginx.conf so that TLS
v1.3 support would be "enabled by default" if you enabled SSL, however
it did not get included due to my own sched
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
** Changed in: nginx (Ubuntu)
Status: Incomplete => In Progress
** Description changed:
[Reason for SRU]
Ubuntu Cosmic 18.10 ships with OpenSSL 1.1.1, which has TLS 1.3 support.
It was intended to enable TLS 1.3 in th
** Changed in: nginx (Ubuntu Disco)
Status: Triaged => 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/1797897
Title:
Add --with-compat to NGINX packages
To manage notifications ab
upload and should
be OK under the current freeze of the archives.
** Affects: nginx (Ubuntu)
Importance: Medium
Assignee: Thomas Ward (teward)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Build tests are underway in
https://launchpad.net/~teward/+archive/ubuntu/cosmic-
buildtests/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795690
Title:
Update NGINX in Cosmic go 1.15.5 f
As Steve Beattie indicated, something else is already listening on port
80, so NGINX can't bind to the port.
This is not a package bug. Check to see if you have any other processes
listening in Port 80 and disable them before attempting to start NGINX.
** Changed in: nginx (Ubuntu)
Status
** Changed in: nginx (Ubuntu)
Status: In Progress => Fix Committed
** Summary changed:
- Update NGINX in Cosmic go 1.15.5 for segfault bugfixes
+ SSL worker process bugfixes in 1.15.5, please put into Cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Note also bug reports are not for support requests, please use another
medium to get help with your issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803590
Title:
package nginx-core 1.14.0-0ub
Per the request of Logan Rosen on #ubuntu-devel on IRC, I was able to
follow the test case as written and confirmed the proposed SRU fix does
in fact solve this issue.
It was noted by Logan however on IRC that another issue had been
identified while looking at the source code, but it is not an SRU
Confirmed in testing with a Cosmic container that this enables TLS 1.3
as well as 1.2, 1.1, and 1.0 in the default configuration change.
TESTERS:
(0) Start with the NGINX in main, not in proposed, for this test.
(`sudo apt install nginx-core nginx`)
(1) In /etc/nginx/sites-available/default, unc
*** This bug is a security vulnerability ***
Public security bug reported:
The following was put out in a security advisory notice over nginx-
announce's mailing list today:
http://mailman.nginx.org/pipermail/nginx-announce/2018/000220.html
Hello!
Two security issues were identified in nginx H
ubuntu1, 1.10.3-0ubuntu0.16.04.2)
* Bionic (1.14.0-0ubuntu1, 1.14.0-0ubuntu1.1)
* Cosmic (1.15.0-0ubuntu1, 1.15.0-0ubuntu2)
* Disco (1.15.0-0ubuntu1, 1.15.0-0ubuntu3)
** Affects: nginx (Ubuntu)
Importance: Medium
Assignee: Thomas Ward (teward)
Status: Confirmed
** Affects: nginx
ic)
Importance: Undecided => Medium
** Changed in: nginx (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: nginx (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: nginx (Ubuntu Disco)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604434
Title:
NGINX 1.10.x Fail to Build in OpenSSL 1.1.0, switch to Mainline for
Looks like Adam Conrad included the SRU within Disco's no change rebuild
for perl, marking as Fix Committed for Disco as that hasn't landed out
of proposed yet.
** Also affects: nginx (Ubuntu Disco)
Importance: Wishlist
Status: In Progress
** Changed in: nginx (Ubuntu Disco)
Stat
Additional testing was completed by myself and I haven't seen any TLS
related regressions (running this on two production sites currently for
my business and my personal).
I'm marking this as verification-done.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verific
** Changed in: nginx (Ubuntu Trusty)
Status: Confirmed => Fix Released
** Changed in: nginx (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: nginx (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: nginx (Ubuntu Cosmic)
Status: Confirmed
** Changed in: nginx (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: nginx (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: nginx (Ubuntu Cosmic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a membe
Released by the security team while handing USN-3812-1 and three CVEs
into Cosmic. Marking "Fix Released" for Cosmic as this is now in the
repositories.
** Changed in: nginx (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a memb
Public bug reported:
Partclone is capable of working with images that're fragmented into tiny
bits, and then reconstructing them and cloning partitions.
However, with extremely large disks, the version of partclone in Xenial
has a major flaw: it wants you to have memory equal to the 'disk size'.
** Changed in: partclone (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: partclone (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802330
Title
Correction, the backported version was using Disco as a base, however in
this case the actual versions of partclone are still the same, the only
difference is the version string (as the changes in Bionic, COsmic, and
Disco are just no-change rebuilds as far as I can tell)
--
You received this bug
Note that I was able to successfully backport the Bionic 0.3.11 version
into Xenial with one change to the build dependencies (a very minor
change) in a PPA, and this works without issues (and is not affected by
this bug).
The PPA is available at
https://launchpad.net/~teward/+archive/ubuntu/partc
** Changed in: nginx (Ubuntu Disco)
Status: Confirmed => 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/1801982
Title:
Security Advisory - Nov. 6, 2018 - CVE-2018-16843, CVE-2018
** Changed in: nginx (Ubuntu Disco)
Status: Confirmed => 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/1801983
Title:
Security Advisory - Nov. 6, 2018 - CVE-2018-16845
To manag
A packaging change containing the --with-compat change has been
committed to disco-proposed, along with security patch fixes via the
newer nginx version for bugs #1801982 and #1801983.
** Changed in: nginx (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notifi
** Description changed:
demotion of pcre3 in favor of pcre2. These packages need analysis what
needs to be done for the demotion of pcre3:
Packages which are ready to build with pcre2 should be marked as
'Triaged', packages which are not ready should be marked as
'Incomplete'.
ai
Nginx properly builds with pcre2
** Changed in: nginx (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in favor of pcre2
To man
1.14.0-0ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782226
Title:
[SRU] Allow NGINX to install but not start during postinst if another
process is bound to port 80
To manage notific
Nice find, I looked in trac but must have missed that...
Sent from my Sprint Samsung Galaxy S9+.
Original message From: Anders Kaseorg Date:
9/18/18 06:22 (GMT-05:00) To: tew...@thomas-ward.net Subject: [Bug 1792544]
Re: demotion of pcre3 in favor of pcre2
Likewise, nginx d
NGINX has technically said this is won't fix:
>From a response to my inquiry: http://mailman.nginx.org/pipermail/nginx-
devel/2018-September/011448.html
--
Hello!
On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote:
> Downstream in Ubuntu, it has been proposed to demot
Sep 21 09:41:43 ajax nginx[4764]: nginx: [emerg]
BIO_new_file("/etc/letsencrypt/live/w9qbj.duckdns.org/fullchain.pem")
failed (SSL: error:02001002:system library:fopen:No such file or
directory:fopen('/etc/letsencrypt/live/w9qbj.duckdns.org/fullchain.pem','r')
error:2006D080:BIO routines:BIO_new_fi
That's beyond the scope of the bug. NGINX can't read or see the file,
why that is the case is beyond the scope of this bug. (You may wish to
seek support for this problem from Let's Encrypt or some other support
mechanism, as bugs are not a support method for solving issues).
--
You received th
Public bug reported:
NGINX Upstream recently released 1.15.4.
This is the following from its changelog:
Changes with nginx 1.15.425 Sep
2018
*) Feature: now the "ssl_early_data" directive can be used with
OpenSSL.
*) Bugfix: in the ngx_http_uwsgi
PPA builds uploaded, location will be at
https://launchpad.net/~teward/+archive/ubuntu/nginx-1794321
Once it builds, I'll run the upgrade sanity tests.
(Thanks for the quick response, sil2100!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just realized I didn't enable all the archs on the PPA. WIll reupload
to the PPA if necessary to regenerate the other archs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794321
Title:
[FFe Needed
All other arch builds beyond amd64 and i386 have been spun and are in
progress on the PPA - thanks to cjwatson for showing me the sneaky way
to build the other archs. (Builds in progress, once amd64 finishes and
shows up I'll do testing)
--
You received this bug notification because you are a me
Basic upgrade and installation tests were completed in a Cosmic
container.
Both upgrading to 1.15.4 from 1.15.3 which is currently in the repos and
clean-installing 1.15.4 work without issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Uploaded and awaiting approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794321
Title:
[FFe Needed] Update NGINX in Cosmic to 1.15.4 for bugfixes
To manage notifications about this bug go to:
1 - 100 of 1936 matches
Mail list logo
