Um... actually, you shouldn't have done that, yerenkov-scott. This is a
debdiff, and a patch, and it needs Ubuntu Sponsors to look at it,
especially for SRU. You also need to get this bug into the SRU format.
Read https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
** Tags added: patch
--
Y
tus: New => Triaged
** 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/1480513
Title:
nginx-common should not depend
Public bug reported:
This is a request for BLACKLISTING and REMOVAL of the Electrum Bitcoin
Wallet program from the repositories.
This request comes with the following considerations:
(1) The Electrum Wallet upstream latest release is 2.4. The version in all our
repositories are at least one ye
@Tim (darkxst) ACK on that. Note that he *did* have to backport the
patches and adjust them, as they didn't cleanly apply apparently, from
what he told me in other chats, so I'm not sure the git headers would
survive that process. "The Unknown" also has said that he's also unsure
of regression p
Debian's solution to the problem appears to have been to make the
package depends as follows:
mysql-client | virtual-mysql-client
This would potentially be enough to fix it. A debdiff for this would be
a one-liner if we take Debian's solution. This might be SRUable...
--
You received this bu
This is already fixed in later releases. I'll add a Series Nomination
for Trusty shortly.
** Description changed:
+ [Impact]
+
+ * automysqlbackup doesn't work with MariaDB. This is mainly due to the
+ depends line depending on mysql-client and not including virtual-mysql-
+ client as an OR i
This is a debdiff for this. This needs review by the SRU team, and the
Sponsors, since I don't have upload rights for this.
** Summary changed:
- Package can't build with mariadb-client
+ Package won't work with mariadb-client
** Patch added: "Trusty Debdiff for #1483942 (v1)"
https://bugs.
Simon:
Please reread comment #4 here -
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1315426/comments/4
The decision on SRU stands because of the reasons stated there, with
agreement from the Server and Security teams to that effect. We will
not be SRUing these changes, because the agreem
Additional discussion with infinity (Adam Conrad) has led to the point
that we should probably dummy-out the prior versions for a similar
reason we did the `bitcoin` source package.
Note that I intend to do that as an SRU, but I have other priorities on
my list for now.
--
You received this bug
An update:
The better reason, now, after discussion with Adam Conrad is, that "This
program, similar to the Bitcoin package, will have changes which break
reverse compatibility with older versions. While they do not have
changes as frequently as Bitcoin which would break reverse
functionality, th
Attached here is a debdiff for retroactive 'nullification' of the
package for electrum, for Trusty. Precedent for this exists because of
the removal of the 'bitcoin' package which was a similar situation of
new versions breaking reverse compatibility, and as the network evolves
older software vers
This is not a bug. The configuration file that you are using (which is
not the same as the one in the package itself) has an invalid
configuration setup.
>From the attached debug file
https://launchpadlibrarian.net/216173830/SystemctlStatusFull_Nginx.txt.txt:
Sep 02 10:52:59 Easy-Main1 systemd[1
There is no information in here that suggests there was a failure. The
only information I can see is that you have two warnings indicating that
you have duplicate servernames and listen statements. However, warnings
are not bugs, and I don't see anything in the information here that
suggests a bu
Hello.
Can you check in /var/crash/ to see if there is an entry for nginx-core
or similar, and run apport-bug on that crash file please, so that debug
information is attached to this bug?
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
** Tags added: arm64 wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491978
Title:
[wily] nginx fails to install on ARM64
To manage notifications about this bug go to:
https://bugs.launchpad.ne
This isn't a bug, nor a problem with the package.
Something else is listening on port 80, and therefore you can't start
nginx. (It by default binds to port 80).
Whatever the other process is (possibly Apache), you should shut it off,
run the installation (or apt-get install -f), and then mess wi
Tested in Precise and it removes the error output and problems as well
for Precise.
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hello, and thanks for filing this! However, this is not really a bug,
and more a conflict of port binding.
Judging from your DpkgHistoryLog, you installed Apache some time before
installing nginx. You cannot run Apache in a default configuration and
Nginx in a default configuration simultaneousl
Thank you for filing this bug.
We have replaced the 1.6.2-5ubuntu3 package with 1.6.2-5ubuntu3.1, which
contains configuration in order to make additional debug data available
in the bug.
Given that, and given that it is impossible to determine from this bug
what is actually breaking, I am markin
Thank you for filing this bug.
We have replaced the 1.6.2-5ubuntu3 package with 1.6.2-5ubuntu3.1, which
contains configuration in order to make additional debug data available
in the bug.
Given that, and given that it is impossible to determine from this bug
what is actually breaking, I am markin
Thank you for filing this bug.
We have replaced the 1.6.2-5ubuntu3 package with 1.6.2-5ubuntu3.1, which
contains configuration in order to make additional debug data available
in the bug.
Given that, and given that it is impossible to determine from this bug
what is actually breaking as the Origi
Thank you for filing this bug.
We have replaced the 1.6.2-5ubuntu3 package with 1.6.2-5ubuntu3.1, which
contains configuration in order to make additional debug data available
in the bug.
Given that, and given that it is impossible to determine from this bug
what is actually breaking as the Origi
Note we also have an updated package in Wily, as well, so if this issue
is replicated in Wily, we will get usable debug data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447294
Title:
package ngi
.
There is a lot of discussion related to what will be done for X-series,
but the plan of action for X-series requires a merge of 1.9.3 from
Debian into Ubuntu for Wily, with future merges likely.
** Affects: nginx (Ubuntu)
Importance: Medium
Assignee: Thomas Ward (teward)
Status
Potential DebDiff here. Will not be merged until spot-checked for
sanity.
** Patch added: "Initial DebDiff for Merge of 1.9.3-1 into Ubuntu Wily"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432211/+files/wily_merge_1.6.2-5ubuntu4_1.9.3-1ubuntu1.lp1476811.debdiff
The 'sanity check' between Debian 1.9.3-1 and the proposed
1.9.3-1ubuntu1 package.
** Patch added: "'Sanity Check' - DebDiff between Debian 1.9.3-1 and proposed
1.9.3-1ubuntu1 merge"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432213/+files/wily_merge_1.9.3-1_1.9
Sanity check from comment #2 failed, due to missing changelog data.
Additional debdiffs to be uploaded here shortly.
Thanks to Dave Walker of the Ubuntu Release Team (and coincidentally the
SRU team) for a cursory sanity-check. :)
** Patch removed: "'Sanity Check' - DebDiff between Debian 1.9.3-
Full Merge DebDiff, Round #2.
** Patch added: "Full DebDiff for Merge of 1.9.3-1 into Ubuntu Wily (Rev. 2)"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432214/+files/wily_merge_1.6.2-5ubuntu4_1.9.3-1ubuntu1.lp1476811.debdiff
--
You received this bug notification
'Sanity check' round #2 between Debian 1.9.3-1 and the proposed
1.9.3-1ubuntu1 package.
** Patch added: "'Sanity Check' (rev. 2) - DebDiff between Debian 1.9.3-1 and
proposed 1.9.3-1ubuntu1 merge"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432215/+files/wily_mer
** Summary changed:
- Please merge nginx 1.9.3-1 (main) from Debian unstable (main)
+ Merge nginx 1.9.3-1 (main) from Debian unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476811
Titl
Final 'Sanity Check' between Debian and the merge in Ubuntu
** Patch added: "'Sanity Check' (rev. 3) - DebDiff between Debian 1.9.3-1 and
proposed 1.9.3-1ubuntu1 merge"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432610/+files/wily_merge_1.9.3-1_1.9.3-1ubuntu1.de
Final Full DebDiff for Merge
** Patch added: "Full DebDiff for Merge of 1.9.3-1 into Ubuntu Wily (Rev. 3)"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1476811/+attachment/4432612/+files/wily_merge_1.6.2-5ubuntu4_1.9.3-1ubuntu1.debdiff
** Patch removed: "'Sanity Check' (rev. 2) - DebD
This isn't "fixed" - it's marked Fix Released in Debian only because of
Debian considering this "Won't Fix".
There's a reason that we say that certain spaces on the file system
aren't for users and this is one of them - this is why I said in my last
post on this even that you should NOT be using t
Ubuntu Utopic has gone End of Life as of today. As such, this bug is
being marked Won't Fix against the Utopic package.
Refer to: https://lists.ubuntu.com/archives/ubuntu-
announce/2015-July/000198.html
** Changed in: nginx (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this b
Ubuntu Utopic has gone End of Life as of today. As such, this bug is
being marked Won't Fix against the Utopic package.
Refer to: https://lists.ubuntu.com/archives/ubuntu-
announce/2015-July/000198.html
** Changed in: nginx (Ubuntu Utopic)
Status: Confirmed => Won't Fix
--
You received
Ubuntu Utopic has gone End of Life as of today. As such, this bug is
being marked Won't Fix against the Utopic package.
Refer to: https://lists.ubuntu.com/archives/ubuntu-
announce/2015-July/000198.html
** Changed in: nginx (Ubuntu Utopic)
Status: Confirmed => Won't Fix
--
You received
This is the diff on this which Debian uses, and we'll likely use that
here:
http://anonscm.debian.org/cgit/collab-maint/nginx.git/commit/debian
/nginx-common.nginx.init?id=b4d1fd4a4ed56f487776adefcc843a031b2a7fbd
** Also affects: nginx (Ubuntu Trusty)
Importance: Undecided
Status: New
This was hit by someone today in the nginx support chat room on
Freenode. I found that diff in Debian to fix this, and will likely poke
at this today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131
This was fixed in later releases after Trusty.
** Changed in: nginx (Ubuntu)
Status: Triaged => 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/1314740
Title:
init script pid pars
Additional changes were made in my testing to verbosify the init
scripts. I can CONFIRM that this does happen, and will get this in the
SRU format.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131474
d to trusty on 2014-04-25 (4 days ago)
** Changed in: nginx (Ubuntu Trusty)
Status: New => In Progress
** Changed in: nginx (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: nginx (Ubuntu Trusty)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received t
This attachment is the DebDiff for this.
** Summary changed:
- init script pid parsing has failure cases
+ [SRU] init script pid parsing has failure cases
** Patch added: "DebDiff for LP#1314740 in Trusty"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1314740/+attachment/4434043/+file
** Package changed: ubuntu => libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478994
Title:
Libreoffice is no longer printing duplex pages
To manage notifications about this bug
*** This bug is a duplicate of bug 1479093 ***
https://bugs.launchpad.net/bugs/1479093
Everyone: This bug has been identified as a duplicate of a mass of
other bugs on this problem - please refer to the bug this is marked as a
duplicate of.
--
You received this bug notification because you
Your apt history shows the following:
Start-Date: 2015-07-19 20:43:33
Commandline: /usr/sbin/synaptic
Install: ... nginx- core:amd64 (1.6.2-5ubuntu3, automatic), ...
nginx-common:amd64 (1.6.2-5ubuntu3, automatic), nginx:amd64 (1.6.2-5ubuntu3),
...
Upgrade: tzdata:amd64 (2015c-1, 2015d-0ubuntu0.
If you wish to replace everything with a default install, do the
following commands. ***Make sure that you back up anything you want to
keep from /etc/nginx or /usr/share/nginx/html***:
sudo apt-get purge nginx nginx-light nginx-full nginx-extras nginx-common
sudo apt-get install nginx nginx-ligh
** Patch removed: "DebDiff for LP#1314740 in Trusty"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1314740/+attachment/4434043/+files/lp1314740.trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Updated debdiff after SRU team feedback.
** Patch added: "lp1314740.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1314740/+attachment/4435967/+files/lp1314740.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified that the bug has been fixed with the upload on Trusty.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314740
Title:
[S
This is not something we can fix, nor is it really a bug in the nginx
package.
When Apache is running, it's bound to port 80. In order to run nginx's
default-installed configuration, you need to either stop or remove
Apache so that port 80 is not bound to, such that nginx can then bind to
it. Th
reports of the Package class currently that could allude to why the postinst
scripts failed.
** Affects: nginx (Ubuntu)
Importance: Medium
Assignee: Thomas Ward (teward)
Status: Triaged
** Affects: nginx (Ubuntu Vivid)
Importance: Medium
Assignee: Thomas Ward (teward)
** Summary changed:
- Nginx bug reports for 'package' problem type are not providing useful data
+ Nginx bug reports for Vivid and later not really returning useful data
** Description changed:
This is against the 'nginx' package because apport hooks need added here
for Vivid and Wily.
** Description changed:
This is against the 'nginx' package because apport hooks need added here
for Vivid and Wily.
Currently, systemd and stderr and Apport do not pull in enough
information for bug triage and handling to be done.
We have several Vivid bugs now which show this - t
Xkeeper:
deadmantfa:
Donald:
There's no evidence YOUR issues are actually the same as the OP of
*this* bug. You need to make your own bugs with your own set of
information. Currently, the state of the package is such that there is
no useful debug data. If you are getting the same "Job for
nginx
** Changed in: nginx (Ubuntu Wily)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472683
Title:
Nginx bug reports for 'package' problem type are not providing u
Public bug reported:
Hello.
I've installed today from the Ubuntu Server Daily ISO. During the
installer process, we get the system identifying network interfaces with
the traditional unpredictable naming algorithms of eth##. After
installation, the system uses systemd to identify network interf
** No longer affects: ubiquity (Ubuntu)
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Importance: Undecided => High
** Description changed:
Hello.
I've installed today from the Ubuntu Server Daily ISO. During the
install
** Changed in: nginx (Ubuntu Wily)
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/1472683
Title:
Nginx bug reports for 'package' problem type are not providing u
** Description changed:
+ [Impact]
+
+ This issue makes it impossible to reliably determine the cause of a
+ postinstallation failure bug during the installation or upgrade attempt
+ of an nginx binary package. A large number of the bugs have tied back
+ to "Postinstall exited with error code" i
** Changed in: nginx (Ubuntu Vivid)
Assignee: Thomas Ward (teward) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472683
Title:
Nginx bug reports for 'package' pro
** Changed in: nginx (Ubuntu Vivid)
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/1472683
Title:
Nginx bug reports for 'package' pro
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472683
Title:
Nginx bug reports for 'package' problem type are not providing usef
t (probably fresh install)
** Affects: nginx (Ubuntu)
Importance: Low
Assignee: Thomas Ward (teward)
Status: Invalid
** Tags: amd64 apport-package need-duplicate-check package-from-proposed vivid
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this
Ran this in a Vivid environment under the test case. When running
apport-bug on the generated crash report, we get the output from the
files which were included as per the apport hooks.
A test bug exists from the -proposed package. See
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1474039
** Changed in: znc (Ubuntu)
Status: New => Confirmed
** Changed in: znc (Ubuntu Vivid)
Status: New => Triaged
** Changed in: znc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: znc (Ubuntu Vivid)
Importance: Undecided => Medium
** Changed in: znc (Ubuntu)
Importa
There is a potential workaround for this issue. Try the following
steps:
sudo apt-get remove nginx
sudo apt-get install nginx-common nginx-full
If it still fails attach the terminal and command output to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
When upgrading nginx packages or booting with nginx configurations that
use `listen` statements or other types of bind locations such as these,
nginx sometimes fails to start because it cannot resolve the hostname:
upstream {
server http://someserver;
}
server {
list
Unfortunately, this is a (common) race condition between nginx at boot
and the system. It is also a common condition even when the system is
running. There are cases where nginx fails to resolve hostnames where
DNS resolvers don't know the information. It has been witnessed in the
past but there
Karmic is past end of life by several years, and therefore I am marking
this as "Won't Fix" against the Karmic task.
** Changed in: ecryptfs-utils (Ubuntu Karmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Not a bug.
This is a case of two web servers both fighting to bind to *:80.
We've seen this race condition for binding before but it's not something
fixable in the package.
You can run two web servers but you would achieve it by binding to
different IPs for each (rather than any IP). This howev
You could also achieve this by having the web servers listen on
different ports, or have one reverse proxy to the other on the differing
port.
In either case this remains not-a-bug and a networking fundamentals
problem of two things binding to the same IP/port combo.
--
You received this bug not
Francis,
This is a known issue. In the nginx community, we actually list the use
of any type of hostname, including localhost, a pitfall, as nginx might
not be able to resolve the hostname at a service restart or at boot
time. Below is the content of this documentation (which I had a hand in
wri
In addition to this being a known issue, there is also currently no
known way to resolve this issue.
** Summary changed:
- package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
+ package nginx-full 1.6.2-5ubuntu3 f
What the docs use and what are actually used are different.
Francis: Also in the future, file a bug with your own information, I
believe. Since i have no information from the OP of *this* bug, and
you've posted something that might not be related, I have to treat
everything as separate. Note tha
This bug will remain at "Incomplete" until the original bug poster,
Lucas Benninger, provides requested information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447294
Title:
package nginx-full 1
mpchlets:
That'd be a different bug, but that type of bug does not qualify for an
SRU or any updates in stable releases. It's likely this can be changed
later in Debian or elsewhere, if it hasn't already been changed, however
it will not get an update in stable releases due to the fact that minor
I've replaced the topic, and the description a little, to match the
'issue' per comment #2. I've also updated the bug status to "Won't Fix"
since this doesn't qualify for any SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
@mpchlets
I don't make SRU policy I only follow it. This is one minor package
listing that is incorrect - ultimately it affects a very very limited
portion of the package and there isn't really a bug needing fixing here.
The policy is that it actually has to fix a substantial bug. In the
past I
Confirmed comment #7. this slipped my radar. Marking vivid fixed as a
result.
** Changed in: znc (Ubuntu Vivid)
Status: Confirmed => 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
Hello.
I do not see any particular need for Ubuntu Bug Control to be subscribed
to this bug, other than that this is an SRU bug. Therefore, I am
unsubscribing Bug Control. Bug Control does not control SRUs, we merely
have some control over bug triage (to an extent). We do not
specifically handl
Samuel Messner and everyone:
This has not actually been fixed based on the bug. The reason this is
'Fix Released' in Debian here is because Launchpad has the incorrect
logic for the Debian bug. (See
https://bugs.launchpad.net/launchpad/+bug/1413304 for details on the
logic breakage).
>From the
Thanks to Brian Murray for the ping on IRC (in #ubuntu-bugs). This is
not an nginx PPA problem.
There have been no NGINX package updates in that repository since
February 10, 2015. The NGINX PPA also has ***zero dependencies,
recommends, or suggests*** on php5-fpm or any other PHP or Apache
comp
I've also done some testing in a system with nginx and php5-fpm
installed - nginx from the (stable) PPA, and php5-fpm from the
repositories, on a Trusty system. This is in a production environment,
on a VPS from RamNode, and the php5-fpm and nginx haven't been updated
in a while (at least three mo
NOTE: I do not have the `php5` metapackage installed on this server - I
explicitly installed php5-fpm WITHOUT the `php5` metapackage. I only
have the `php5-fpm` package (and related dependencies) installed. Is it
at all possible that the `php5` metapackage ignored the dependencies
list and theref
Can anyone confirm whether this happens with the `php5` metapackage
actually in the 'installed' state prior to the update, or whether this
happened with only `php5-fpm` installed?
We also need more steps to reproduce this before we can more thoroughly
start examining and testing.
--
You received
Vivid uses systemd by default now, instead of upstart. Is this on a
non-standard system configuration?
** Changed in: upstart (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
s qualifies for an SRU right now.
** Also affects: nginx (Ubuntu Vivid)
Importance: Undecided
Assignee: Thomas Ward (teward)
Status: Triaged
** Also affects: nginx (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Utopic)
Importance: Un
** Changed in: nginx (Ubuntu Precise)
Importance: Undecided => Wishlist
** Changed in: nginx (Ubuntu Trusty)
Importance: Undecided => Wishlist
** Changed in: nginx (Ubuntu Utopic)
Importance: Undecided => Wishlist
** Changed in: nginx (Ubuntu Vivid)
Importance: Undecided => Wishlist
After additional discussion with the server team and members of the
security team, we do not believe that this qualifies as an SRU. It does
not provide any significant benefit other than hardening, and does not
qualify for SRU.
As such, I am setting "Won't Fix" in Precise through Utopic, but leav
** Changed in: nginx (Ubuntu Vivid)
Importance: Wishlist => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315426
Title:
nginx not built as position independent
To manage notifications about
Sindhudweep: We were not comparing Apache and NGINX speeds. With PIE,
on a 32bit platform there si at least a 15% performance decrease (based
on general observation between platforms with PIE enabled/disabled).
We're working on this for Vivid right now, have patience.
--
You received this bug n
** Changed in: nginx (Ubuntu Vivid)
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/1315426
Title:
nginx not built as position independent
To manage notificati
Additional related bugs in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781703 - nginx not using
BIND_NOW security feature
Immediate binding as well as Position Independent building are both enabled
with the fix that is committed right now. (Bug summary expanded to include the
** Changed in: sponc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: sponc (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/1409879
Title:
sponc c
** Changed in: mttroff (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mttroff (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/1409877
Title:
mtt
*** This bug is a security vulnerability ***
Public security bug reported:
There are 6 new CVEs which impact Wireshark in Utopic. (Three of these
also affect Trusty)
--
CVE-2015-2187: (Utopic)
The dissect_atn_cpdlc_heur function in
asn1/atn-cpdlc/packet-atn-cpdlc-template.c in the ATN-CPD
Marking Fix Released against the devel release as this is already fixed
there.
** Changed in: wireshark (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: wireshark (Ubuntu Utopic)
Status: New => Confirmed
** Changed in: wireshark (Ubuntu Trusty)
Importance: Undecided => Cr
Attached is a debdiff for Utopic to address this bug and the 6 CVEs.
The included patches were taken from the auto-synced Vivid package, but
had their patch names renamed in order to keep the sequential numbering
in Utopic, as only security fixes were included, and there is an extra
patch in Vivid
Corrections needed. For upstream nginx, 1.7.x is mainline; 1.6.x is
stable. 1.7.x has newer features than Stable does, but may not be as
stable.
--
(If this seems like a lot to read, and you don't want to read the lots
of information I put here for background and explanation, skip down to
t
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440363
Title:
package nginx (not installed) (from nginx.org upstream repository)
failed to install/upgrade: tryin
801 - 900 of 1967 matches
Mail list logo
