RE: Bug triage report for 2024-01-08 (Monday triage)

[Thomas Ward]

Robie,

Regarding that discourse nginx post I'll give it a thorough overview.  First 
glance is the raised question is legitimate that theres an issue in the 
documentation written by Bryce, but I'll go over it today and make comments (or 
edits) accordingly.

Thomas



Sent from my Galaxy



 Original message 
From: Robie Basak 
Date: 1/8/24 09:34 (GMT-05:00)
To: ubuntu-server@lists.ubuntu.com
Subject: Bug triage report for 2024-01-08 (Monday triage)

> LP: #2020260 || D   | Expired   | samba   | Samba 
> seems to panic after enabling and connecting to ZFS b… |

This is an additional report from someone using samba in Debian. I
commented to try and set the expectation that we probably won't make any
progress without a reproducer or a deeper technical analysis. I also
added this to our long term backlog since a crash is generally a valid
bug that we would work on if we had infinite time (but the severity
related to a rare crash doesn't warrant prioritising it).

> LP: #2041751 || D   | Fix Released  | pptpd   |   
>  RM: Remove dangerously insecure MPPE PPTP from Ubuntu |

I add a ubuntu-release-notes task as I think this should be release
noted. No other action was needed.

> LP: #2048068 || D   | New   | exim4   | 
> exim4-daemon-heavy: investigate enabling experimental ARC s… |

Mitchell had added this for discussion. I also added it to our long term
backlog since I think that we would investigate this in principle if we
had infinite time regardless of its priority.

> LP: #2048419 || D   | New   | apache2 |   
> ubuntu-logo.png missing in icons directory |

Marked for immediate attention. I haven't verified this but it seems
clear enough.

> LP: #2048436 || D   | New   | sssd|   
>four Dependency failed for SSSD |

It isn't clear that this is a bug at all. Commented and marked
Incomplete.

Reviewing older bugs:

> LP: #2042824 |  + | DJ  | Triaged   | freeradius  |   
>   smbencrypt segfaults when run with any parameter |

This seems like a legitimate if low priority issue, so I added it to the
backlog (it wasn't previously).

> LP: #1852994 || DFI | New   | samba   | samba 
> creates temporary files in /tmp, but never deletes th… |

This is already in the backlog and fixed in Jammy onwards, so only an
SRU remains for Focal. I don't think prioritisation is appropriate, so I
left it as-is.

For Discourse triage,
https://discourse.ubuntu.com/t/how-to-configure-nginx/39680/2 seems
legit and needs further investigation, but I'm not sure how to add it to
a backlog somewhere. Advice appreciated!

Robie
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Bug triage report for 2021-01-11 (Tuesday triage)

[Thomas Ward]

We had further discussions and had determined in IRC discussions that 
this was an 'edge case' and 'odd configuration'.


If we want to have a discussion on this, you may need to loop me in on 
this - it's an issue that we have in the juggling between "should we fix 
this" and "this is a non-standard end system configuration that we don't 
out of the box support".



Thomas


On 1/12/21 9:56 AM, Lucas Kanashiro wrote:

Bugs last updated on 2021-01-11 (Monday)
Date range identified as: "Tuesday triage"
Found 22 bugs

Most of bugs are taken care by other people, the only one I want to 
mention is this one:


https://pad.lv/1743592  - (Won't Fix)     
 [nginx]          - NGINX fails to start/install/upgrade if IPv6 is 
completely disabled.


There was a discussion on this bug to change the Nginx behavior for 
Focal but it did not happen. A user replied saying that it is not 
installable if IPV6 is disabled, and they are asking if we could make 
it at least installable but the service would not start. I am not sure 
what is the best course of action here, so I tagged the bug with 
server-triage-discuss and I'd like input from others (specially people 
previously involved in this discussion).


Lucas Kanashiro.

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday bug triage duty - 12th October 2020

[Thomas Ward]

Christian,

On 10/12/20 10:58 AM, Christian Ehrhardt wrote:
> 1899164 nginx
> A rather detailed report about build time options, I subscribed the team.
> But lacking the background details I also subscribed teward (who knows
> much
> better) and asked him to comment.

No need to sub me as I'm already subbed to all NGINX bugs, just poke me.

Regarding the bug, though, this is Won't Fix.  The compile time prefixes
are set by Debian, and NGINX Upstream does something similar with their
prebuilt packages.  All the prefixes the bug poster indicated are
erroring on can be overridden with the proper nginx.conf options - so
the original poster needs to dig into the nginx documentation and with
their CUSTOMIZED nginx.conf override the prefixes with the proper
configuration arguments.  That applies to almost all nginx options that
have a precoded, compile-time prefix path.  Easily overridden with the
proper configuration arguments.

So, I finished the triage on that bug - it's been Won't Fix'd by me
because we're not going to remove those compile time prefix options.  To
remove them would introduce breakages to things that aren't set by
default, and I can't begin to determine the scope of the breakage.  It'd
also add another substantial divergence from Debian, and since NGINX
upstream does similar configuration prefix setting at compile time in
their repositories, it's not going to be 'removed' when the person in
question can just override those prefixes with custom configuration
arguments in their (sparse) nginx.conf.


Thomas

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Monday Bug Triage - 2020-04-24 (Friday) and 2020-04-26 (Sunday)

[Thomas Ward]

On 4/27/20 10:12 PM, Rafael David Tinoco wrote:
> Bugs last updated between 2020-04-24 (Friday) and 2020-04-26 (Sunday)
> inclusive
> Date range identified as: "Monday triage"
>
> SEVERAL bugs opened because of 20.04 release. A bunch of those were
> opened by apport because of installation issues.
>
> The ones I had triaged were:
>
> ...
>
> libnginx-mod-nchan distributes old/incompatible module
> https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831
>> opened bug upstream (debian) asking for nchan upgrade
>> if debian/module upgraded, likely need to be SRUed to focal
>> triaged

Just to make a note, this is on my radar to be updated in Gorilla.  SRU
for this needs analyzed to see if there's any 'new features' that need
additional scrutiny.

This said, I'm working on some major packaging shifts to make the
configuration more pluggable and to split out some bits into separate
configuration files (similar to how Dovecot splits out core
configuration bits).  This will effectively make us extremely diverged
from Debian, but I haven't seen much movement on their front lately. 
I'm going to open a separate discussion on those proposed changes and
updates to the nginx packaging and layout of conf.d inclusions later. 
I'm not ready to share my prototype yet, but I had preliminarily
discussed this with Seth Arnold and he thought it was a good idea to
make things more 'pluggable' from a config perspective and to split some
config bits out into conf.d inclusions.


Thomas

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

NGINX (again) and 20.04 Development Cycle

[Thomas Ward]

Whenever we approach an April release, we have to always be considering 
NGINX and the fact that around the same time we release a new stable 
version is cut from Mainline.


What this means is, as NGINX decides to release a Stable version they 
use the NGINX Mainline branch to do more active feature development, 
feature implementations, etc. and then once it's cut 'no longer support 
the older versions of NGINX' before it.


Currently, we have been tracking NGINX 1.16.x which in April will become 
the "No Longer Supported" branch and at this point will be over a year 
old.  NGINX Mainline is currently at 1.17.5 and has bugfixes, feature 
changes/revisions/updates, etc. and will eventually become NGINX 1.18.x 
around when we release 20.04 LTS.


In the past around the LTS releases we've switched from tracking NGINX 
Stable to NGINX Mainline in anticipation of a right-before-release or 
shortly-after-release upload to change the version string from 1.17.x to 
1.18.0 to coincide with NGINX upstream releases.  I'm not fond of 
keeping 1.16.x in the repos for 20.04 LTS if I can avoid it, since it's 
technically no longer supported once NGINX releases upstream. around 
when we release 20.04.


Do we want to pursue this approach of tracking Mainline again with the 
intention of FFes and MREs during the dev cycle up until the 1.18.x 
release after which we SRU that version string change that in?


The other alternative is to keep 1.16.x in the repositories and then 
forcibly jump to 1.18.0 later but that's a more major version bump with 
a lot of feature changes.  (I'd like at least for 20.04 to get on the 
latest NGINX Mainline branch with the intention of keeping it updated 
with FFes during dev and then a final version string change either just 
before or just after release to get us tracking 1.18.x as the version 
number.)



I'd be happy to file any relevant requests to the Release Team ahead of 
time to get any of the devel cycle headaches handled.



Thomas

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: How do I update bug 1708870

[Thomas Ward]

I would take that URL and put it into another system's web browser, and
then login to LP and use the link.  The URL needs to know who's
submitting the data to tie it to a Launchpad account, if that login part
didn't work in Lynx for you then you need to take that URL to a normal
browser on another computer.  (Which is fine, I do this for my remote
servers all the time, open the URL locally on my laptop if I'm SSH'd in
or such).

This is just a quirk unfortunately I think with Lynx.  (None of my
servers are GUI devices, yet I still apport-collect on them and such
fine by opening their URLs locally on my system rather than on the
non-GUI environment itself).

If you open that URL in your local browser rather than directly on the
non-GUI device, it should work.



Thomas


On 1/7/19 9:12 AM, Leroy Tennison wrote:
> Thanks for your reply, I appreciate it.  apport-collect does open a URL but, 
> because it's on a non-GUI device, Lynx is what I tried using.  I guessed my 
> way through that interface but got to a point where it appeared I had gotten 
> into a circular loop.
>
> BTW, I was able to download the latest Intel driver source and compile it.  
> Initial (limited) testing indicates that it works even though the process 
> produced error messages.  My concern with that is "What happens if there is 
> an upgrade?".
>
> I could possibly use Ubuntu 18.04 but then I have to deal with the bug 
> regarding netplan and keepalived (which I have to get back to submitting a 
> bug for).
>
>
>
> Leroy Tennison
> Network Information/Cyber Security Specialist
> E: le...@datavoiceint.com
> 2220 Bush Dr
> McKinney, Texas
> 75070
> www.datavoiceint.com
> TThis message has been sent on behalf
> of a company that is part of the Harris Operating Group of
> Constellation Software Inc. These companies are listed
> here
> .
> If you prefer not to be contacted by Harris
> Operating Group
> please notify us
> .
> This message is intended exclusively for the
> individual or entity to which it is addressed. This communication
> may contain information that is proprietary, privileged or
> confidential or otherwise legally exempt from disclosure. If you are
> not the named addressee, you are not authorized to read, print,
> retain, copy or disseminate this message or any part of it. If you
> have received this message in error, please notify the sender
> immediately by e-mail and delete all copies of the
> message.
>
> -Original Message-
> From: Andreas Hasenack 
> Sent: Monday, January 7, 2019 7:50 AM
> To: Leroy Tennison 
> Cc: ubuntu-server@lists.ubuntu.com
> Subject: [EXTERNAL] Re: How do I update bug 1708870
>
>
>
> On Thu, Dec 27, 2018 at 7:45 PM Leroy Tennison   > wrote:
>
>
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708870) I didn’t 
> submit the original bug but a comment asks to run “apport-collect 1708870” 
> and change the status to confirmed.  Since the person submitting the bug 
> apparently didn’t do so I tried to (on a server with no GUI, answering the 
> prompts in Lynx was “interesting” to say the least) but couldn’t discern what 
> needed to be done to submit the apport information.  Is there a way I can do 
> this?  I have hardware that is unusable until this is resolved.  Thanks for 
> your help.
>
>
>
>
> Thanks for your interest in helping
>
> What happens after you run the apport-collect command? It should give you an 
> url that you can open from your desktop, it doesn't have to be opened from 
> that same machine where you ran the command.
>
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Inquiry: NGINX branch to track in "Interim" Non-LTS Releases

[Thomas Ward]

Hi, all.


On 08/08/2018 10:00 AM, Thomas Ward wrote:
>
>
>
> On 08/08/2018 01:22 AM, Christian Ehrhardt wrote:
>>
>>
>> On Tue, Aug 7, 2018 at 7:14 PM Thomas Ward > <mailto:tew...@ubuntu.com>> wrote:
>>
>> 
>>
>> Hi Thomas,
>> yeah I'd prefer to track Mainline in non-LTS releases as well.
>>
>> To the sole exception of being very careful toward the next LTS to
>> not being forced to decide to "go back" or "stay on mainline" for the
>> next Ubuntu LTS.
>> For example if NGINX 1.17 mainline would be in Ubuntu 19.10 (as we
>> track mainline in non-LTS releases), but then there would not be a
>> NGINX 1.18 stable available in time for Ubuntu 20.04 to pick up.
>> I don't know about the NGINX release schedule too much (is it regular
>> and reliable?), maybe this is not an issue at all, but I have seen
>> similar issues for other packages so I wanted to mention it.
>>
>
> We do have that type of issue though.  We need not look further than
> the 16.04 cycle for an example of this.  NGINX Stable was cut from
> NGINX Mainline the same day as we released 16.04, but we had tracked
> mainline right up to that point so there was a version strong only
> change SRU'd in the day after release.
>
> For 18.04, NGINX Stable was cut from mainline the same day as final
> freeze, but I managed to get that uploaded right before FinalFreeze
> went into effect.
>
> NGINX stable versions tend to be cut from mainline right about the
> time we are either releasing or are entering final freeze, based on
> the past experiences of their release cycles.  Generally speaking
> however, even if they cut stable from mainline right after we release,
> the changes between Mainline and stable at that point are typically
> just version string changes as we saw in the 16.04 cycle.  Maybe a
> bugfix or two but usually not new features.
>
> NGINX however doesn't follow a fixed-date release cycle
> unfortunately.  Which has contributed to things like the 16.04 cycle
> had or a last minute upload before freeze like 18.04 had.  They do,
> however, tend to cut the releases within 1 week of our release date
> (Ubuntu Release Week +/- 1 week), and by that point the likelihood
> they add any new features to the release prior to cutting Stable from
> that mainline branch is very very low based on the historical trends
> (based on watching upstream changelogs since 2014).
>
> While I can't say with *certainty* there won't be a case where they
> release Stable maybe a week after our release, it's so far only been a
> version-string-only change, and there's precedent already in place
> from 16.04 where we can put a version-string-only change into -updates
> without disrupting anything.  Consistently, the 'release' of Stable
> has been in April around the time we release an LTS version.  And so
> far, the only case we've had where NGINX releases Stable when we're in
> a final frozen state for LTS when Stable comes out has been the 16.04
> cycle and it was a version-string-only change, of which that
> version-string change was able to be done as a post-release SRU as it
> doesn't change any features and just updates the version string. 
> (Otherwise it's been in the FeatureFreeze states, and we've been able
> to get it approved, or *right* before FinalFreeze where the Release
> team said "Upload it now before we freeze" and it got in).
>
>
>>
>> ---
>> Thomas Ward
>> Ubuntu Server Team Member
>>
>> -- 
>>     ubuntu-server mailing list
>> ubuntu-server@lists.ubuntu.com
>> <mailto:ubuntu-server@lists.ubuntu.com>
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
>> More info: https://wiki.ubuntu.com/ServerTeam
>>
>>
>>
>> -- 
>> Christian Ehrhardt
>> Software Engineer, Ubuntu Server
>> Canonical Ltd
>
> --
> Thomas Ward
> Ubuntu Server Team Member

In follow up to my response to Christian, I ended up discussing this
briefly with Seth Arnold over IRC yesterday.

I agree that up to LTS we need to make sure we don't have to have any
type of version reverts, so I have come up with the following
idea/proposal: For 18.10 and 19.04, both interim releases, we can track
Mainline.  This way we can at least get the 'newer features' read for
19.04 or 19.10 getting NGINX 1.16.x as its stable version, and as we
approach 20.04 LTS we can determine if we should focus on getting the
next Stable into an LTS.

This way we don't have to worry between now and the next LTS about the
version reverts.

This also gets my want of newer features to be tested in the interim
releases (at least the next two), without impinging upon LTS.

Thoughts?


--
Thomas Ward
Ubuntu Server Team Member
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Inquiry: NGINX branch to track in "Interim" Non-LTS Releases

[Thomas Ward]

On 08/08/2018 01:22 AM, Christian Ehrhardt wrote:
>
>
> On Tue, Aug 7, 2018 at 7:14 PM Thomas Ward  <mailto:tew...@ubuntu.com>> wrote:
>
> 
>
> Hi Thomas,
> yeah I'd prefer to track Mainline in non-LTS releases as well.
>
> To the sole exception of being very careful toward the next LTS to not
> being forced to decide to "go back" or "stay on mainline" for the next
> Ubuntu LTS.
> For example if NGINX 1.17 mainline would be in Ubuntu 19.10 (as we
> track mainline in non-LTS releases), but then there would not be a
> NGINX 1.18 stable available in time for Ubuntu 20.04 to pick up.
> I don't know about the NGINX release schedule too much (is it regular
> and reliable?), maybe this is not an issue at all, but I have seen
> similar issues for other packages so I wanted to mention it.
>

We do have that type of issue though.  We need not look further than the
16.04 cycle for an example of this.  NGINX Stable was cut from NGINX
Mainline the same day as we released 16.04, but we had tracked mainline
right up to that point so there was a version strong only change SRU'd
in the day after release.

For 18.04, NGINX Stable was cut from mainline the same day as final
freeze, but I managed to get that uploaded right before FinalFreeze went
into effect.

NGINX stable versions tend to be cut from mainline right about the time
we are either releasing or are entering final freeze, based on the past
experiences of their release cycles.  Generally speaking however, even
if they cut stable from mainline right after we release, the changes
between Mainline and stable at that point are typically just version
string changes as we saw in the 16.04 cycle.  Maybe a bugfix or two but
usually not new features.

NGINX however doesn't follow a fixed-date release cycle unfortunately. 
Which has contributed to things like the 16.04 cycle had or a last
minute upload before freeze like 18.04 had.  They do, however, tend to
cut the releases within 1 week of our release date (Ubuntu Release Week
+/- 1 week), and by that point the likelihood they add any new features
to the release prior to cutting Stable from that mainline branch is very
very low based on the historical trends (based on watching upstream
changelogs since 2014).

While I can't say with *certainty* there won't be a case where they
release Stable maybe a week after our release, it's so far only been a
version-string-only change, and there's precedent already in place from
16.04 where we can put a version-string-only change into -updates
without disrupting anything.  Consistently, the 'release' of Stable has
been in April around the time we release an LTS version.  And so far,
the only case we've had where NGINX releases Stable when we're in a
final frozen state for LTS when Stable comes out has been the 16.04
cycle and it was a version-string-only change, of which that
version-string change was able to be done as a post-release SRU as it
doesn't change any features and just updates the version string. 
(Otherwise it's been in the FeatureFreeze states, and we've been able to
get it approved, or *right* before FinalFreeze where the Release team
said "Upload it now before we freeze" and it got in).


>
> ---
> Thomas Ward
> Ubuntu Server Team Member
>
> -- 
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com <mailto:ubuntu-server@lists.ubuntu.com>
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>
>
>
> -- 
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd

--
Thomas Ward
Ubuntu Server Team Member
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Inquiry: NGINX branch to track in "Interim" Non-LTS Releases

[Thomas Ward]

Currently, all LTS versions of Ubuntu that are currently supported have
a version of the NGINX Stable branch in the repositories.  This was done
initially so that we can provide a 'stable' and 'released without new
features' type of branch we would be able to track.  In the cycle before
release, we kept it in line with NGINX Mainline because once NGINX
Stable was cut from that Mainline branch, they'd have newer features
that would otherwise have been unavailable if we had tracked Stable.

My assumption is we want to still do this type of behavior (that is,
track Mainline branch) in interim releases.  This lets the interim
releases of Ubuntu work with newer features that NGINX introduces,
allowing us to file bugs upstream as necessary with the Mainline builds
or to debug issues as they arise in the packaging.  However, because I
am not sure if this is what we wish to do, I thought I'd reach out to
the rest of the Server Team for your input.

What do you think would be best, tracking NGINX Stable, or tracking
NGINX Mainline, for the interim non-LTS releases?  I'm leaning towards
tracking Mainline in the interim releases, if there's no objection -
it'll let users who want more cutting edge NGINX features to use those
in the interim releases without having to force them to use the PPAs.


---
Thomas Ward
Ubuntu Server Team Member

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: AU server tags [was Re: ]

[Thomas Ward]

Nish,

The problem with Ask Ubuntu is that tags need to be specific and useful
to identify a question.  The rules of a StackExchange site don't
necessarily match what the Ubuntu triage rules are.

We already have a tag for "Server" -
https://askubuntu.com/questions/tagged/server - which would be regarding
a server.  The other problem is, almost every issue reported under the
'server' tag isn't necessarily server-specific, and many server-related
questions don't have that tag on them even though they'd be server related.

A second consideration is this question: "Are we going to actively
review questions as part of Server Team duties, both hired (read:
Canonical) and volunteer?"  I'm fairly certain I know the answer to the
first one of these, and the second one of these is a "If you are going
to volunteer, then just read the site."

Bugs filed on Ask Ubuntu get squished by me and the community as "File
an actual bug".


So I'm going to need clarification on the thoughts behind this idea,
before I can give a better answer.



Thomas


On 10/11/2017 03:32 PM, Nish Aravamudan wrote:
> Hi Thomas,
>
> On Tue, Oct 10, 2017 at 3:11 PM, Nish Aravamudan
>  wrote:
> 
>> === askubuntu.com questions (teward) - Better communication with community. 
>> ===
>> The discussion about "askubuntu.com questions (teward) - Better
>> communication with community." started at 16:21.
> In the meeting this week, the above topic was brought up although you
> weren't available.
>
> Specifically, the question is if it makes sense to add a tag
> ('server'?') to AU questions specific to server.
>
> I see some followon discussion on IRC, but it probably deserves to be on the 
> ML.
>
> Thanks,
> Nish
>
> P.S. I've removed the agenda item for now.

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Server Team Meeting Minutes, 2017-08-22

[Thomas Ward]

== Meeting information ==
 * #ubuntu-meeting: ubuntu-server-team, 22 Aug at 16:01  16:37 UTC
 * Full logs at 
[[http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-08-22-16.01.log.html]]



== Meeting summary ==

=== Review ACTION points from previous meeting ===
The discussion about "Review ACTION points from previous meeting" started at 
16:01.

  * ''ACTION:'' nacc to write a release notes entry on ipv6 netboot (carried 
over)
  * ''ACTION:'' nacc to write a server guide entry on ipv6 netboot (carried 
over)
  * ''ACTION:'' 
  * ''ACTION:'' rbasak to add maintainership info to mysql triage page (carried 
over)

=== Artful Development ===
The discussion about "Artful Development" started at 16:03.

  * ''LINK:'' https://wiki.ubuntu.com/ArtfulAardvark/ReleaseSchedule 
  * Feature Freeze is on the 24th, so try and get things in by 23rd if you need 
to upload and add new features.
  * Server Team working on several extra merges that may end up as FFEs
  * ''LINK:'' 
https://bugs.launchpad.net/~ubuntu-release/+bugs?orderby=-date_last_updated=0
 
 * '''Current Work''' (16:08)
  * ''LINK:'' https://trello.com/b/U9HhWyT0/daily-ubuntu-server 
 * '''Release Bugs''' (16:10)
  * ''LINK:'' 
http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-aa-tracking-bug-tasks.html#ubuntu-server
 
  * ''ACTION:'' dpb1 to check with stgraber for 'zfs clone' performance 
degredation in lxd.
  * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1567557 

=== Server & Cloud Bugs & SRU/Pending Uploads (slashd, ddstreet) ===
The discussion about "Server & Cloud Bugs & SRU/Pending Uploads (slashd, 
ddstreet)" started at 16:19.

  * pcp MIR being worked on was NACK'd by Security Team; pcp upstream is 
looking at security note and seeing what they can do to satisfy requirements 
and needs for the security note
  * ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1700827 
  * ''LINK:'' 
http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-z-tracking-bug-tasks.html#ubuntu-server
 
  * ''LINK:'' 
http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-x-tracking-bug-tasks.html#ubuntu-server
 

=== Weekly Updates & Questions for the QA Team (powersj) ===
The discussion about "Weekly Updates & Questions for the QA Team (powersj)" 
started at 16:24.

  * ''LINK:'' https://jenkins.ubuntu.com/server/ 

=== Weekly Updates & Questions for the Kernel Team (smb, sforshee) ===
The discussion about "Weekly Updates & Questions for the Kernel Team (smb, 
sforshee)" started at 16:26.


=== Upcoming Call For Papers ===
The discussion about "Upcoming Call For Papers" started at 16:27.

  * ''LINK:'' https://lwn.net/Calendar/Monthly/cfp/ 
  * ''LINK:'' http://www.open-zfs.org/wiki/OpenZFS_Developer_Summit 

=== Ubuntu Server Team Events ===
The discussion about "Ubuntu Server Team Events" started at 16:29.

  * A few of the canonical-server team will be sprinting Thursday/Friday this 
week, FYI.
  * teward to attend Harrisburg, PA local FOSS event focusing on open-source 
systems, software, and server implementations.

=== Open Discussion ===
The discussion about "Open Discussion" started at 16:34.


=== Announce next meeting date, time and chair ===
The discussion about "Announce next meeting date, time and chair" started at 
16:36.

  * Next meeting Tuesday, 2017-08-29 at 1600 UTC, chair will be rbasak



== Vote results ==




== Action items, by person ==

 * dpb1
  * dpb1 to check with stgraber for 'zfs clone' performance degredation in lxd.
 * nacc
  * nacc to write a release notes entry on ipv6 netboot (carried over)
  * nacc to write a server guide entry on ipv6 netboot (carried over)
 * stgraber
  * dpb1 to check with stgraber for 'zfs clone' performance degredation in lxd.
 * **UNASSIGNED**
  * 
  * rbasak to add maintainership info to mysql triage page (carried over)



== Done items ==

 * (none)



== People present (lines said) ==

 * teward (93)
 * dpb1 (23)
 * cpaelzer (11)
 * meetingology (8)
 * ahasenack (6)
 * nacc (5)
 * powersj (5)
 * stgraber (3)
 * ubottu (2)
 * smb (1)
 * ddstreet (1)



== Full Log ==


 16:01  #startmeeting ubuntu-server-team

 16:01  Meeting started Tue Aug 22 16:01:11 2017 UTC.  The chair 
is teward. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 16:01  

 16:01  Available commands: action commands idea info link nick

 16:01  #topic Review ACTION points from previous meeting

 16:01  * nacc to write a release notes entry on ipv6 netboot (carried 
over)

 16:02  * nacc to write a server guide entry on ipv6 netboot (carried 
over)

 16:02  nacc: any progress on these, or should we carry these over to 
next meeting?

 16:02  * rbasak to add maintainership info to mysql triage page 
(carried over)

 16:02  teward: please carry over

 16:02  I think rbasak is absent, as I got put in as the chair today, 
so I'll carry that to next meeting.

 16:02  carry over rbasak too

 16:02  teward: rbasak is also not attending

 16:02  yep

 16:03  thanks

 16:03  

Re: Ubuntu Server Bug Squashing Day (monthly)

[Thomas Ward]

Just want to make sure everyone is on the same page though - there are a few 
packages that have special handling rules so make sure you're up to date with 
the bug triage rules and regulations.

Totally unrelated I will be drifting around during bug days but not always 
alive - if you are squishing a bug that I should probably know about (read: 
nginx), drop me a line.  Though I think all the ubuntu-next ones are squished 
already...


Thomas
LP: ~teward



*Sent from my iPhone.  Please excuse any typos, as they are likely to happen by 
accident.*

> On Mar 20, 2017, at 13:55, Nish Aravamudan  
> wrote:
> 
> On Fri, Mar 17, 2017 at 3:08 PM, Nish Aravamudan
>  wrote:
>> On 15.03.2017 [12:22:54 +0100], Christian Ehrhardt wrote:
>>> Would you think e.g. creating an etherpad or such and announce it in this
>>> thread (as well as on IRC at the day) would help?
>> 
>> My plan is to set that all up on Monday so we have a few days to
>> coordinate/plan.
> 
> http://pad.ubuntu.com/U5GLIMwc2u
> 
> Is the Etherpad, and 2) is where folks can enter their IRC nicks and
> bugs they would like to work on.
> 
> -Nish
> 
> -- 
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: Call for Testing: NGINX 1.10.3 with Dynamic Modules

[Thomas Ward]

On 02/15/2017 03:05 AM, Christian Ehrhardt wrote:
>
> On Wed, Feb 15, 2017 at 1:47 AM, Thomas Ward <tew...@ubuntu.com
> <mailto:tew...@ubuntu.com>> wrote:
>
> I've been working on the merge of nginx from Debian for the Zesty
> cycle
> for some time.  We're technically ahead of Debian so it's a little bit
> more evil of a merge, but I think we have something that we can
> finally
> start testing with for Zesty.
>
>  
> [...]
>
>
> My deadline here is FeatureFreeze, but if we can't get tests done
> by FF,
> then I'll file for an FF, though tests should still be completed.
>
>
> If the server team could help me out with these tests, that'd be
> great.  :)
>
>
>
> Thanks for your work Thomas,
> I was giving it a shot pretending to be a normal user and
> following 
> https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-in-ubuntu-16-04.
> I did so with the new ppa and without it.
> With that I was
> - comparing the results/bheavior of old/new version.
> - running httperf against it checking that there is no degradation and
> no errors in the log when stressing it a bit.
> - installing the nginx extra packages and reran the above
> - eventually upgrading the one without the ppa and checked that
> everything works still.
>
> Comments/Changes what I realized being a simulated normal user of
> nginx due to the upgrade:
> I realized the default config for php fpm changed in the
> conf /etc/nginx/sites-available/default
> from /var/run/php/php7.0-fpm.sock to /run/php/php7.0-fpm.sock
> But both exist and work, so it might be fine.
> In general the default config got a lot of noisy updates (e.g. help
> URLs changed, order of entries changed, comments changed), but not a
> lot functional ones.
> TL;DR - I did not hit an issue on the upgrade due to this at least -
> so that should be ok.
>
> The systemd service now lists a man page - well that is a good change?
>
> The new packaging (as you announced) has more libnginx-mod-* packages
> for the extra features now.
> I did not explicitly use any of the extra features yet, but they
> install correctly.
> There is a warning about dependency issues is posted, but that is on
> the nginx-core that is about to be removed.
> Also this warning is the same prior to the update - juts with more
> packages now so it seems "more conflicts" at first sight.
>
> Overall all went fine - maybe not the best test possible, but I hope
> that gives you some confidence!

Can you provide me a copy of the 'dependency issues' warning, if you
still have it?  Maybe it's just a minor issue that can be fixed.

That said, thank you for your testing, and thank you also for helping to
test, if it all looks good, then great!  Most of the evils of things
missing were 'leftovers' from the older packaging; we ended up having to
do non-merge updates because of other issues and such, but now we've got
those ironed out to make this buildable.

If there are no other objections to this, I'll push the package (minus
the +test3 part of the string) to the Repositories, and it'll be in
*just* before Feature Freeze.


--
Thomas Ward
Ubuntu Server Team Member
LP: ~teward
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Call for Testing: NGINX 1.10.3 with Dynamic Modules

[Thomas Ward]

Hi, all!

I've been working on the merge of nginx from Debian for the Zesty cycle
for some time.  We're technically ahead of Debian so it's a little bit
more evil of a merge, but I think we have something that we can finally
start testing with for Zesty.

The current potential candidate NGINX packaging for merging is located
in a PPA currently [1], with a version string of "+test#" at the end,
indicating it's a test build but also a specific # of test builds.  When
uploaded to the main repository, it won't have that.

I'd like some help testing some important parts.  Basically, there's
three sets of tests I currently need to worry about:

(1) Fresh install in Zesty.  That is, a Zesty system that doesn't have
any nginx or prior configs on it, and fresh installations of nginx-core,
nginx-light, nginx-extras, or nginx-full, and the dependencies.

(2) Upgrade Installation - Zesty 1.10.3-0ubuntu1 -> Zesty
1.10.3-0ubuntu2+test3 (the current test build).  That is, install the
nginx that's already in Zesty, then install this updated version.  Same
flavor tests as in test case 1.

My deadline here is FeatureFreeze, but if we can't get tests done by FF,
then I'll file for an FF, though tests should still be completed.


If the server team could help me out with these tests, that'd be great.  :)


--
Thomas Ward
Ubuntu Server Team Member
LP: ~teward

[1]: https://launchpad.net/~teward/+archive/ubuntu/nginx-merge-zesty



-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: NGINX in Ubuntu

[Thomas Ward]

Well, it's been about a week since I looked at this, and I had a little
bit of an explosion on my computer.  Turns out, upgrading 14.04 to 16.04
when you have more than one GCC in place breaks things.  So I have been
restoring data from my backup since Tuesday.

Getting 1.10.x into Xenial, but I'd probably prod the SRU / Release
teams for their opinions before I do anything in terms of uploading. 
I'm also rebuilding my sbuild schroots, but I do know that NGINX 1.10.2
*does* build for Xenial, and does run efficiently on Xenial.  It
wouldn't be too hard to backport that from Zesty to Xenial, though I'm
not going to put dynamic modules into Xenial or Yakkety.

I'm still working on the merge from Debian to Zesty, which includes the
dynamic module stuff, but that's going to take a lot more time. 
Probably not until after the new year, unfortunately.


Thomas


On 12/17/2016 10:14 AM, Thomas Ward wrote:
>
> Jon,
>
> Thanks for your reply.
>
> I think it is reasonable to attempt to include the code as well.  I
> will work on diffs, and then ping the SRU team to look at it once my
> own build tests and update/upgrade testing is confirmed to not break
> anything.
>
> That said, there's a huge snow/ice storm that just rolled through, so
> power is spotty at my location - won't be able to get to this until
> the electricity stabilizes (it's got some periods of being out while
> mostly being on).
>
>
> Thomas
>
>
> On 12/15/2016 04:12 PM, Jon Grimm wrote:
>> Hi Thomas,
>>
>> As 16.04 is an LTS with a whole lot of life yet to it, I think its
>> reasonable to consider bringing it back to Xenial.   
>>
>> As you have a lot more experience with nginx you can help assess
>> whether it meets the SRU micro-release exception even:
>>
>> https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
>>
>>
>> Obviously, we want to be very cautious with the LTS in not regressing
>> anyone, but looking through your changelog it seems reasonable to
>> attempt it.   
>>
>> Thank you for your looking after diligent looking after of nginx; I
>> greatly appreciate it!
>>
>>
>> On Thu, Dec 15, 2016 at 11:27 AM, Thomas Ward <tew...@ubuntu.com
>> <mailto:tew...@ubuntu.com>> wrote:
>>
>> Hello to all on the Server Team!
>>
>> Just to put this out of the way: The nginx merge from Debian is
>> currently giving build errors, so I am going to upload a 1.10.2
>> directly to Zesty, the same as we did during the Yakkety and
>> Xenial cycles.  That way, we get nginx 1.10.2 available for Zesty.
>>
>> However, it was initially requested via a bug on Launchpad to
>> update the version of nginx in Xenial (and by extension, Yakkety)
>> to 1.10.2 as well.  [1]  For now, I've marked those tasks as
>> "Won't Fix" because I wanted to touch base with the Server Team
>> first on this.
>>
>> This request to update to 1.10.2 would include the following
>> changes from Upstream:
>>
>> Changes with nginx 1.10.218 Oct 
>> 2016
>>
>> *) Change: the "421 Misdirected Request" response now used when
>>rejecting requests to a virtual server different from one 
>> negotiated
>>during an SSL handshake; this improves interoperability with some
>>HTTP/2 clients when using client certificates.
>>
>> *) Change: HTTP/2 clients can now start sending request body
>>immediately; the "http2_body_preread_size" directive controls 
>> size of
>>the buffer used before nginx will start reading client request 
>> body.
>>
>> *) Bugfix: a segmentation fault might occur in a worker process when
>>using HTTP/2 and the "proxy_request_buffering" directive.
>>
>> *) Bugfix: the "Content-Length" request header line was always added 
>> to
>>requests passed to backends, including requests without body, when
>>using HTTP/2.
>>
>> *) Bugfix: "http request count is zero" alerts might appear in logs 
>> when
>>using HTTP/2.
>>
>> *) Bugfix: unnecessary buffering might occur when using the 
>> "sub_filter"
>>directive; the issue had appeared in 1.9.4.
>>
>> *) Bugfix: socket leak when using HTTP/2.
>>
>> *) Bugfix: an incorrect response might be returned when using the 
>> "aio
>>threads" and "sendfile" 

Re: NGINX in Ubuntu

[Thomas Ward]

On 12/15/2016 01:43 PM, Jonathon Fernyhough wrote:
> On 15/12/16 17:27, Thomas Ward wrote:
>> Hello to all on the Server Team!
>>
>> Just to put this out of the way: The nginx merge from Debian is
>> currently giving build errors, 
> Where are the builds being done? I just kicked off a PPA build for
> nginx=1.10.2-2 from sid and it built correctly for trusty onwards (for
> amd64 and i386 at least, using `backportpackage`, no-change).
I'm running them locally on my own sbuild systems.  The issue appears to
be in the Ubuntu specific changes that we applied in Trusty (the
addition of the `nginx-core` flavor for Main as part of the MIR), so I
have to debug those.  That's why the merge is not available anywhere
yet.  There'll be a separate call for testing of a potential merge
candidate sent to the list once I have a non-failing build.

The other issue with the merge is that I have to basically 'redo' the
`nginx-core` changes.  The existing delta and the new dynamic-modules
builds don't merge cleanly with each other, so I'd have to redo the
nginx-core variation and the Ubuntu delta by hand to account for these
changes.  Which isn't hard, just time consuming.

>
>> I am not 100% sure whether we should be updating Xenial to 1.10.2. 
>> Apart from the fact it is more than just a 'bug fix' release, I'm not so
>> sure whether we need all of these bug fixes in Xenial.  Because I am
>> unsure, I'd like Server Team member input on how we should proceed.
> (Not server team) IMHO if it's got bugfixes, and it's in main, it should
> be updated. (Policy-dependant, it would probably also be easier than
> cherry-picking certain patches and having to maintain a diverging codebase)
Hence the call out to the Mailing List, and the Server Team, for input
on how we should proceed.

--
Thomas Ward
Ubuntu Server Team Member
LP: https://launchpad.net/~teward

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

NGINX in Ubuntu

[Thomas Ward]

Hello to all on the Server Team!

Just to put this out of the way: The nginx merge from Debian is
currently giving build errors, so I am going to upload a 1.10.2 directly
to Zesty, the same as we did during the Yakkety and Xenial cycles.  That
way, we get nginx 1.10.2 available for Zesty.

However, it was initially requested via a bug on Launchpad to update the
version of nginx in Xenial (and by extension, Yakkety) to 1.10.2 as
well.  [1]  For now, I've marked those tasks as "Won't Fix" because I
wanted to touch base with the Server Team first on this.

This request to update to 1.10.2 would include the following changes
from Upstream:


Changes with nginx 1.10.218 Oct 2016

*) Change: the "421 Misdirected Request" response now used when
   rejecting requests to a virtual server different from one negotiated
   during an SSL handshake; this improves interoperability with some
   HTTP/2 clients when using client certificates.

*) Change: HTTP/2 clients can now start sending request body
   immediately; the "http2_body_preread_size" directive controls size of
   the buffer used before nginx will start reading client request body.

*) Bugfix: a segmentation fault might occur in a worker process when
   using HTTP/2 and the "proxy_request_buffering" directive.

*) Bugfix: the "Content-Length" request header line was always added to
   requests passed to backends, including requests without body, when
   using HTTP/2.

*) Bugfix: "http request count is zero" alerts might appear in logs when
   using HTTP/2.

*) Bugfix: unnecessary buffering might occur when using the "sub_filter"
   directive; the issue had appeared in 1.9.4.

*) Bugfix: socket leak when using HTTP/2.

*) Bugfix: an incorrect response might be returned when using the "aio
   threads" and "sendfile" directives; the bug had appeared in 1.9.13.

*) Workaround: OpenSSL 1.1.0 compatibility.


Note that the CVE update from 1.10.1 is already applied in Ubuntu
releases.  I coordinated with the Security team to make sure that got
pushed out in a timely manner.  1.10.1 introduces a few changes, a lot
of bugfixes, and a workaround for OpenSSL 1.1.0 compatibility.

I am not 100% sure whether we should be updating Xenial to 1.10.2. 
Apart from the fact it is more than just a 'bug fix' release, I'm not so
sure whether we need all of these bug fixes in Xenial.  Because I am
unsure, I'd like Server Team member input on how we should proceed.

Namely, should we consider updating nginx 1.10.2 in both Xenial and
Yakkety to get these bugfixes in?  And if we think we should, we'll need
SRU team approval.


Thomas Ward
Ubuntu Server Team Member
LP: https://launchpad.net/~teward

[1]: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1636593

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Re: nginx package signature guarantees with Xenial?

[Thomas Ward]

Jeff,

Sorry for not replying sooner. Along with the rest of the Server Team, I
help to maintain the nginx packaging in Ubuntu.

Robie's points have all been points he and I discussed on IRC or are
points I would make myself.  I'm not changing those points, as they are
spot-on accurate.

That said, if you're unsure of whether there is an nginx update in the
pipeline for Ubuntu or not, chances are I'm in the loop for any pending
updates, and you can drop me a message, or email the Server list where
I'll see it anyways, and I'll let you know generally if there's any
updates in the works.  (I can tell you there's one in the works now that
I intend to land in Yakkety (16.10) "soon" and am happy to share some
specifics off-list, though there'll be a message landing soon on the
lists for a call for testing of this, detailing the changes, anyways.)




Thomas



On 07/01/2016 07:10 AM, Robie Basak wrote:
> Hi Jeff,
>
> Sorry, I just remembered this thread and that I hadn't replied.
>
> On Fri, Jun 24, 2016 at 03:06:13PM -0400, Jeff Kaufman wrote:
>>> Have you considered adding your module to Ubuntu's repositories? Is
>>> there any reason you couldn't maintain them in xenial-backports for the
>>> benefit of Xenial users, for example?
> Note that the usual route to adding packages to Ubuntu is via Debian.
> Though then you'd have to deal with the rebuilds in collaboration with
> the Debian nginx maintainers too, as well as the rebuilds in stable
> Ubuntu releases and backports[2] which would have to be done
> independently.
>
>> That's possible.  I don't have a great sense of what that would
>> entail.  For example, if the nginx package maintainer updated nginx,
>> the package for ngx_pagespeed would need to be rebuilt.  Is there a
>> good way to handle this?
> If there's a particular reason you don't want to do that then Ubuntu
> does accept Ubuntu-specific (not from Debian) packages too.
>
> Unfortunately, we don't really have a good way right now. However, in
> Ubuntu, we work in teams rather than owning specific maintainerships
> like Debian. If we know that ngx_pagespeed needs to be rebuilt, I expect
> that we'll JFDI. For example, we already do this with pinba-engine-mysql
> as needed.
>
> In the development release, an update can't land in the release pocket
> if it causes other packages to become uninstallable[1], so we should
> also notice. This assumes that the dependencies are set up correctly.
>
> In a stable release, I don't think we currently track this because it is
> quite an unusual case (I only know of pinba-engine-mysql and now this).
> But I'm sure the SRU team[3] would be open to some additional CI to
> prevent accidents if you're interested in driving this.
>
> We do expect that those interested in the package (in this case, you)
> are available to fix any issues though, for example if it fails to
> build, or otherwise blocks a new nginx release going in. We usually use
> IRC but this mailing list is fine to make contact too.
>
>>> Note that it's 16.04, not just 16. 16 will be ambiguous when a
>>> subsequent 16.10 is released.
>> But "16 LTS" isn't ambiguous, right?
> I guess not. You can call it what you like of course, though I don't
> think the Ubuntu release team or any Ubuntu developers call it that :)
>
> Sorry again for my delay in responding.
>
> Robie
>
> [1] https://wiki.ubuntu.com/ProposedMigration
> [2] https://wiki.ubuntu.com/UbuntuBackports
> [3] https://wiki.ubuntu.com/StableReleaseUpdates
>


-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

[Bug 1565043] [NEW] Please enable HTTP/2 in NGINX for Xenial

[Thomas Ward]

Public bug reported:

The Security team has recently given the OK to enable HTTP/2 in NGINX
for Xenial.

Please activate it for nginx-core, nginx-extras, nginx-full, and nginx-
light.


Upstream, in Debian, it is being enabled for all versions as part of the 
dynamic modules changes; even though dynamic modules are not being enabled 
here, it would be good to ahve this enabled for all flavors.  Debian anonscm 
git commit for this is 
http://anonscm.debian.org/cgit/collab-maint/nginx.git/tree/debian/rules?h=dyn#n53,
 with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816095 being the Debian 
bug that has a 'pending' change.

** Affects: nginx (Ubuntu)
 Importance: Wishlist
 Assignee: Thomas Ward (teward)
 Status: Triaged


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1565043

Title:
  Please enable HTTP/2 in NGINX for Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1565043/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1565043] Re: Please enable HTTP/2 in NGINX

[Thomas Ward]

Before I enable HTTP/2 in nginx-light, I will discuss with the Server
team.  Debian does, indeed, have it enabled in nginx-full and nginx-
extras, and nginx-core will have it as it closely mirrors nginx-full.

This will be considered for the next upload, otherwise.

** Summary changed:

- Please enable HTTP/2 in NGINX
+ Please enable HTTP/2 in NGINX for Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1565043

Title:
  Please enable HTTP/2 in NGINX for Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1565043/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FreezeException Needed] Update nginx to 1.9.13.

[Thomas Ward]

** Changed in: nginx (Ubuntu)
   Status: Confirmed => Fix Committed

** Summary changed:

- [FreezeException Needed] Update nginx to 1.9.13.
+ [FFe] Update nginx to 1.9.13.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522890] Re: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thomas Ward]

zarej, refer to Bug 1512344 - this is a known problem but it's not
something that's able to be fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1522890

Title:
  package nginx-core (not installed) failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1522890/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522890] Re: package nginx-core (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thomas Ward]

This is not a bug in `nginx`.  You have to shut off any other web server
running on port 80 in order to install NGINX and get it to run
automatically during setup.  You run into the same issues installing
Apache when there's another thing running on Port 80.

Marking Invalid.

** Changed in: nginx (Ubuntu)
   Status: Expired => Won't Fix

** Changed in: nginx (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: nginx (Ubuntu)
   Status: Invalid => Won't Fix

** Changed in: nginx (Ubuntu)
   Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1522890

Title:
  package nginx-core (not installed) failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1522890/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FreezeException Needed] Update nginx to 1.9.13.

[Thomas Ward]

** Summary changed:

- [FFe Needed] Update nginx to 1.9.13.
+ [FreezeException Needed] Update nginx to 1.9.13.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FreezeException Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

Upgrading from the 1.9.12 packages to the 1.9.13 packages works without
any issues.  There are no failures to update.

Adding install/history logs shortly for each version, and a screenshot
done through nginx-core to show that the defaults work and the
application runs.  It also includes a picture of the VMware Workstation
window to the VM running Xenial to show its IP, and that nginx-core's
nginx executable is running.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

Runtime screenshot - shows the 'default' landing page of nginx-core,
done via VM, and the IP data for the VM, the pidof output to show nginx
is running, and the default landing page via web browser to that VM's IP
address.

** Attachment added: "Screenshot - Xenial VM IP, Xenial pidof output showing 
nginx is running, and default landing page (via 14.04 Host) on Chrome to show 
running."
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617288/+files/Screenshot_nginx-core_running.png

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

This is the nginx-core installation and apt logs.

** Attachment added: "nginx-core apt logs"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617282/+files/install_logs_nginx-core.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

DebDiff between 1.9.12-0ubuntu1 and 1.9.13-0ubuntu1.

** Patch added: "Debdiff, nginx 1.9.12-0ubuntu1 to 1.9.13-0ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617290/+files/nginx_xenial_1.9.12_1.9.13.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

This needs to be examined for freeze exception.  We are past
FinalBetaFreeze, so this needs review before I even upload it to the
repositories.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

This is the nginx-extras installation and apt logs.

** Attachment added: "nginx-extras apt logs"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617286/+files/install_logs_nginx-extras.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

This is the nginx-light installation and apt logs.

** Attachment added: "nginx-light apt logs"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617283/+files/install_logs_nginx-light.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

This is the nginx-full installation and apt logs.

** Attachment added: "nginx-full apt logs"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4617284/+files/install_logs_nginx-full.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] php7.0 for Xenial (in main now, still removing php5): INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: MIR for pps-tools: DONE
  [arges] libvirt merge (bug 1533003) : DONE
  [arges] libvirt-python: DONE
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): DONE
  [smoser] openiscsi merge: DONE
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7: DONE
  [racb] squid3 merge (=4days): INPROGRESS
  [racb] libecap (squid3 dependency): INPROGRESS
  [nacc] logwatch cleanup: DONE
  [nacc] Tomcat updates and cleanup: DONE
  [nacc] Java-related work: DONE
  [nacc] puppet merge and cleanup: DONE
  [rharper] docker.io 1.10 or greater: DONE
  [louis-bouchard] clamav merge: DONE
  [jamespage] crmsh and pacemaker: DONE
  [teward] Update nginx to 1.9.11 (bug 1543624): DONE
  [kick-d] Amavisd-new update: DONE
  [kick-d] moin merge: DONE
  [kick-d] urlgrabber merge: DONE
  
  Work items for ubuntu-16.04:
- [teward] Update nginx to 1.9.13 (bug 1563393): TODO
+ [teward] Update nginx to 1.9.13 (bug 1563393): INPROGRESS
  [paelzer] DPDK MIR: DONE
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: DONE
  [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): DONE
  [kick-d] Get postfix migrated: DONE

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

Additional build tests available in my Xenial build testing PPA -
https://launchpad.net/~teward/+archive/ubuntu/xenial-
buildtests/+packages - this is to permit armhf, arm64, and ppc64el
builds in addition to i386 and amd64.

If there are no build errors, this PPA will be used for the install
tests on a clean Xenial VM.

I've already tested upgrading nginx-core and nginx dependencies to
1.9.13 from the sbuild-built packages.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

amd64 sbuild logs (plus Lintian checks)

** Attachment added: "amd64 sbuild logs (+ Lintian)"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4616444/+files/nginx_1.9.13-0ubuntu1_amd64.build

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] Re: [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

i386 sbuild logs (plus Lintian checks)

** Attachment added: "i386 sbuild logs (+ Lintian)"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+attachment/4616443/+files/nginx_1.9.13-0ubuntu1_i386.build

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563393] [NEW] [FFe Needed] Update nginx to 1.9.13.

[Thomas Ward]

Public bug reported:

NGINX has recently uploaded 1.9.13.  There are included in this upload
multiple bug fixes, but also changes to include support for other
features in the modules.

--
--

The upstream changelog is as follows:
(http://nginx.org/en/CHANGES)

Changes with nginx 1.9.1329 Mar
2016

*) Change: non-idempotent requests (POST, LOCK, PATCH) are no longer
   passed to the next server by default if a request has been sent to a
   backend; the "non_idempotent" parameter of the "proxy_next_upstream"
   directive explicitly allows retrying such requests.

*) Feature: the ngx_http_perl_module can be built dynamically.

*) Feature: UDP support in the stream module.

*) Feature: the "aio_write" directive.

*) Feature: now cache manager monitors number of elements in caches and
   tries to avoid cache keys zone overflows.

*) Bugfix: "task already active" and "second aio post" alerts might
   appear in logs when using the "sendfile" and "aio" directives with
   subrequests.

*) Bugfix: "zero size buf in output" alerts might appear in logs if
   caching was used and a client closed a connection prematurely.

*) Bugfix: connections with clients might be closed needlessly if
   caching was used.
   Thanks to Justin Li.

*) Bugfix: nginx might hog CPU if the "sendfile" directive was used on
   Linux or Solaris and a file being sent was changed during sending.

*) Bugfix: connections might hang when using the "sendfile" and "aio
   threads" directives.

*) Bugfix: in the "proxy_pass", "fastcgi_pass", "scgi_pass", and
   "uwsgi_pass" directives when using variables.
   Thanks to Piotr Sikora.

*) Bugfix: in the ngx_http_sub_filter_module.

*) Bugfix: if an error occurred in a cached backend connection, the
   request was passed to the next server regardless of the
   proxy_next_upstream directive.

*) Bugfix: "CreateFile() failed" errors when creating temporary files on
   Windows.

--
--

Rationale for Update:

A longer term goal of the Server Team is to have NGINX 1.10.x (the next
stable release of NGINX) in Ubuntu Xenial, either as a post-Xenial-
release SRU, or right before we release, depending on when NGINX
releases the 1.10.x branch (which is based off the 1.9.x branch).

To reduce the delta between merges, and to reduce the amount of work
necessary to switch from 1.9.x to 1.10.x in the future of Xenial, it is
more preferable to have the latest 1.9.x available as close to 1.10.x
release as possible; this makes it much more easier to deal with build
failures, or to troubleshoot issues between versions, as there is less
of an upstream delta.

There are new features, however they do not affect the default
configuration, and some feature additions are not yet implemented
(dynamic modules are available, but not user-friendly nor are they
incorporated into the packaging at this time).

We have other bugfixes, as well, for other functions in the system,
which should all be included.

--
--

Security Considerations:

HTTP/2
--
* HTTP/2 is disabled in the NGINX builds currently. This is at the request of 
the Security Team. There is no security concern of HTTP/2 in this release.

--
--

Files to be uploaded (Pending creation) for FFe Consideration:

* Debdiff between 1.9.12-0ubuntu1 and 1.9.13-0ubuntu1 (direct upload)
* Local sbuild logs (amd64, i386), including 'lintian' checks
* Installation log (Xenial amd64 VM)

** Affects: nginx (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1563393

Title:
  [FFe Needed] Update nginx to 1.9.13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1563393/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] php7.0 for Xenial (in main now, still removing php5): INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: MIR for pps-tools: DONE
  [arges] libvirt merge (bug 1533003) : DONE
  [arges] libvirt-python: DONE
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): DONE
  [smoser] openiscsi merge: DONE
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7: DONE
  [racb] squid3 merge (=4days): INPROGRESS
  [racb] libecap (squid3 dependency): INPROGRESS
  [nacc] logwatch cleanup: DONE
  [nacc] Tomcat updates and cleanup: DONE
  [nacc] Java-related work: DONE
  [nacc] puppet merge and cleanup: DONE
  [rharper] docker.io 1.10 or greater: DONE
  [louis-bouchard] clamav merge: DONE
  [jamespage] crmsh and pacemaker: DONE
  [teward] Update nginx to 1.9.11 (bug 1543624): DONE
  [kick-d] Amavisd-new update: DONE
  [kick-d] moin merge: DONE
  [kick-d] urlgrabber merge: DONE
  
  Work items for ubuntu-16.04:
+ [teward] Update nginx to 1.9.13 (bug 1563393): TODO
  [paelzer] DPDK MIR: DONE
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: DONE
  [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): DONE
  [kick-d] Get postfix migrated: DONE

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1559571] Re: package nginx-extras (not installed) failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Thomas Ward]

*** This bug is a duplicate of bug 1521786 ***
https://bugs.launchpad.net/bugs/1521786

You still have a broken install, like you did in Bug 1521786.  I am
marking this a duplicate of that, as the issue remains the same.

Please follow my diagnostic instructions as I posted in the other bug
(Bug 1521786).  This is not a bug in the package.

** Changed in: nginx (Ubuntu)
   Status: Incomplete => Invalid

** This bug has been marked a duplicate of bug 1521786
   package nginx-core 1.9.3-1ubuntu1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1559571

Title:
  package nginx-extras (not installed) failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1559571/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1559571] Re: package nginx-extras (not installed) failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Thomas Ward]

Dead process with changes to your nginx.service file is bad, because it
looks like your systemd has changes to the nginx service, perhaps run
these:

sudo systemctl daemon-reload
sudo apt-get install -f


and see if anything fails.  If it still fails, run this command again, and add 
the output for it here:

systemctl -l status nginx.service

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1559571

Title:
  package nginx-extras (not installed) failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1559571/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1559571] Re: package nginx-extras (not installed) failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Thomas Ward]

Due to some issue in apt and apport hooks, can you provide the output of
the following command please?

systemctl -l status nginx.service


** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1559571

Title:
  package nginx-extras (not installed) failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1559571/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1299972] Re: Default site config is ambiguous in PHP block (precise)

[Thomas Ward]

This appears to have been resolved since this was originally filed.

** Changed in: nginx (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: nginx (Ubuntu Precise)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1299972

Title:
  Default site config is ambiguous in PHP block (precise)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1299972/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: [FFe] Please update nginx to 1.9.12

[Thomas Ward]

** Changed in: nginx (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nginx (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  [FFe] Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: [FFe] Please update nginx to 1.9.12

[Thomas Ward]

** Summary changed:

- [FFe Requested] Please update nginx to 1.9.12
+ [FFe] Please update nginx to 1.9.12

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  [FFe] Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1553321] Re: package nginx 1.9.3-1ubuntu1.1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

[Thomas Ward]

** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1553321

Title:
  package nginx 1.9.3-1ubuntu1.1 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1553321/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1552949] Re: the "http2" parameter requires ngx_http_v2_module

[Thomas Ward]

We will have a section in the release notes regarding HTTP/2 support for
nginx not being available at release time, most likely.  We will address
that bit closer to Xenial release, however.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1552949

Title:
  the "http2" parameter requires ngx_http_v2_module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1552949/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1552949] Re: the "http2" parameter requires ngx_http_v2_module

[Thomas Ward]

Marking as won't fix for now.

Refer to
https://answers.launchpad.net/ubuntu/+source/nginx/+question/280708

** Changed in: nginx (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1552949

Title:
  the "http2" parameter requires ngx_http_v2_module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1552949/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1352617] Re: php5-fpm UNIX sockets in Precise do not listen as www-data:www-data by default, and causes 502s with webservers trying to use socket

[Thomas Ward]

Note that "UNIX Sockets" applies only when configured to use them -
default is to use a TCP listener.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1352617

Title:
  php5-fpm UNIX sockets in Precise do not listen as www-data:www-data by
  default, and causes 502s with webservers trying to use socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1352617/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1552181] Re: Nginx service should restart on the fly, without downtime

[Thomas Ward]

It supports it but it does not close the old workers which can then
restart later if they are needed.

This is all great, but that means you get a lot of leftover nginx
processes and old processes which hog resources when you do it this way.

I am not going to change the existing implementation of upgrading - we
don't need extra processes left over hogging resources on upgrades.

** Changed in: nginx (Ubuntu)
   Status: New => Won't Fix

** Changed in: nginx (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1552181

Title:
  Nginx service should restart on the fly, without downtime

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1552181/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: [FFe Requested] Please update nginx to 1.9.12

[Thomas Ward]

** Summary changed:

- Please update nginx to 1.9.12
+ [FFe Requested] Please update nginx to 1.9.12

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  [FFe Requested] Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: Please update nginx to 1.9.12

[Thomas Ward]

** Summary changed:

- New nginx upstream release - 1.9.12
+ Please update nginx to 1.9.12

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

I do not have logs here, but I can confirm that all flavors (-core,
-light, -full, -extras) can be upgraded to the version in the debdiff
without issues and without any failures, outside of configuration
failures by users (that is, not Package-specific issues)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

NGINX install logs from apt for nginx-extras

** Attachment added: "NGINX_InstallLog_Extras.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580165/+files/NGINX_InstallLog_Extras.txt

** Patch removed: "Debdiff for NGINX, version 1.9.11-0ubuntu2 to 
1.9.12-0ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580089/+files/nginx_1.9.11-nginx_1.9.12_xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

NGINX install logs from apt for nginx-core

** Attachment added: "NGINX_InstallLog_Core.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580162/+files/NGINX_InstallLog_Core.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

Updated debdiff because I accidentally left the bug number off this.


This is ready for review for a FeatureFreeze Exception.

** Patch added: "Debdiff for NGINX, version 1.9.11-0ubuntu2 to 1.9.12-0ubuntu1  
(Version 2)"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580166/+files/nginx_1.9.11-0ubuntu2_to_nginx_1.9.12-0ubuntu1.debdiff

** Changed in: nginx (Ubuntu)
 Assignee: Thomas Ward (teward) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

NGINX install logs from apt for nginx-full

** Attachment added: "NGINX_InstallLog_Full.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580164/+files/NGINX_InstallLog_Full.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

NGINX install logs from apt for nginx-light

** Attachment added: "NGINX_InstallLog_Light.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580163/+files/NGINX_InstallLog_Light.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

Screenshot #1: Image of the VM - Shows "netstat -tulpn | grep :80"
output, which will indicate that nginx is indeed running.  Obtained
right after installation.

** Attachment added: "Screenshot #1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580159/+files/ConfirmNGINXListener_Xenial.png

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

Screenshot #2: IP address of VM, and Default Landing Page (screenshot
from Host system, includes VM console)

** Attachment added: "Screenshot #2"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580160/+files/NGINX_VM_DefaultPage.png

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

Additional build logs and tests available in
https://launchpad.net/~teward/+archive/ubuntu/xenial-
buildtests/+packages for package `nginx 1.9.12-0ubuntu1` for other
architectures

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

** Patch added: "Debdiff for NGINX, version 1.9.11-0ubuntu2 to 1.9.12-0ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580089/+files/nginx_1.9.11-nginx_1.9.12_xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

amd64 sbuild logs (plus Lintian checks)

** Attachment added: "amd64 sbuild logs (+ Lintian) - nginx_1.9.12-0ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580086/+files/nginx_1.9.12-0ubuntu1_amd64.build

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

i386 sbuild logs (plus Lintian checks)

** Attachment added: "i386 sbuild logs (+ Lintian) - nginx_1.9.12-0ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+attachment/4580087/+files/nginx_1.9.12-0ubuntu1_i386.build

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] Re: New nginx upstream release - 1.9.12

[Thomas Ward]

** Summary changed:

- New upstream release - 1.9.12
+ New nginx upstream release - 1.9.12

** Description changed:

  NGINX has recently uploaded version 1.9.12.  This contains bugfixes and
  feature changes to core functionality in nginx, as well as introduces
  workarounds due to some issues with OpenSSL.
  
  --
  --
  
  The upstream changelog is as follows.  Comments of mine will be added
  with hashtags (#):
  
+ Changes with nginx 1.9.1224 Feb
+ 2016
  
- Changes with nginx 1.9.1224 Feb 2016
+ *) Feature: Huffman encoding of response headers in HTTP/2.
+    Thanks to Vlad Krasnov.
  
- *) Feature: Huffman encoding of response headers in HTTP/2.
-Thanks to Vlad Krasnov.
+ *) Feature: the "worker_cpu_affinity" directive now supports more than
+    64 CPUs.
  
- *) Feature: the "worker_cpu_affinity" directive now supports more than
-64 CPUs.
+ *) Bugfix: compatibility with 3rd party C++ modules; the bug had
+    appeared in 1.9.11.
+    Thanks to Piotr Sikora.
  
- *) Bugfix: compatibility with 3rd party C++ modules; the bug had
-appeared in 1.9.11.
-Thanks to Piotr Sikora.
+ *) Bugfix: nginx could not be built statically with OpenSSL on Linux;
+    the bug had appeared in 1.9.11.
  
- *) Bugfix: nginx could not be built statically with OpenSSL on Linux;
-the bug had appeared in 1.9.11.
+ *) Bugfix: the "add_header ... always" directive with an empty value did
+    not delete "Last-Modified" and "ETag" header lines from error
+    responses.
  
- *) Bugfix: the "add_header ... always" directive with an empty value did
-not delete "Last-Modified" and "ETag" header lines from error
-responses.
+ *) Workaround: "called a function you should not call" and "shutdown
+    while in init" messages might appear in logs when using OpenSSL
+    1.0.2f.
  
- *) Workaround: "called a function you should not call" and "shutdown
-while in init" messages might appear in logs when using OpenSSL
-1.0.2f.
+ *) Bugfix: invalid headers might be logged incorrectly.
  
- *) Bugfix: invalid headers might be logged incorrectly.
+ *) Bugfix: socket leak when using HTTP/2.
  
- *) Bugfix: socket leak when using HTTP/2.
- 
- *) Bugfix: in the ngx_http_v2_module.
+ *) Bugfix: in the ngx_http_v2_module.
  
  --
  --
  
  Rationale for Update:
  
  A longer term goal of the Server Team is to have NGINX 1.10.x (the next
  stable release of NGINX) in Ubuntu Xenial, either as a post-Xenial-
  release SRU, or right before we release, depending on when NGINX
  releases the 1.10.x branch (which is based off the 1.9.x branch).
  
  To reduce the delta between merges, and to reduce the amount of work
  necessary to switch from 1.9.x to 1.10.x in the future of Xenial, it is
  more preferable to have the latest 1.9.x available as close to 1.10.x
  release as possible; this makes it much more easier to deal with build
  failures, or to troubleshoot issues between versions, as there is less
  of an upstream delta.
  
  We do not enable HTTP/2, therefore the only feature change we should be
  worried about here is the ability of the `worker_cpu_affinity` directive
  being able to support more than 64 CPUs.  This does not affect other
  functionality.
  
  We have other bugfixes, as well, for other functions in the system,
  including 'add_header' directives, and incorrect logging of invalid
  headers.  These do not affect any of the other features in Ubuntu, nor
  does this appear to affect the feature-set of NGINX.
  
- 
  --
  --
  
  Security Considerations:
  
  HTTP/2
  --
  * HTTP/2 is disabled in the NGINX builds currently.  This is at the request 
of the Security Team.  There is no security concern of HTTP/2 in this release.
  
- 
  --
  --
  
  Files to be uploaded (Pending creation)
  
  * Debdiff between 1.9.11-0ubuntu2 and 1.9.12-0ubuntu1 (direct upload)
- * Local sbuild logs (amd64, i386)
+ * Local sbuild logs (amd64, i386), including 'lintian' checks
  * Installation log (Xenial amd64 VM)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New nginx upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1549347] [NEW] New upstream release - 1.9.12

[Thomas Ward]

Public bug reported:

NGINX has recently uploaded version 1.9.12.  This contains bugfixes and
feature changes to core functionality in nginx, as well as introduces
workarounds due to some issues with OpenSSL.

--
--

The upstream changelog is as follows.  Comments of mine will be added
with hashtags (#):


Changes with nginx 1.9.1224 Feb 2016

*) Feature: Huffman encoding of response headers in HTTP/2.
   Thanks to Vlad Krasnov.

*) Feature: the "worker_cpu_affinity" directive now supports more than
   64 CPUs.

*) Bugfix: compatibility with 3rd party C++ modules; the bug had
   appeared in 1.9.11.
   Thanks to Piotr Sikora.

*) Bugfix: nginx could not be built statically with OpenSSL on Linux;
   the bug had appeared in 1.9.11.

*) Bugfix: the "add_header ... always" directive with an empty value did
   not delete "Last-Modified" and "ETag" header lines from error
   responses.

*) Workaround: "called a function you should not call" and "shutdown
   while in init" messages might appear in logs when using OpenSSL
   1.0.2f.

*) Bugfix: invalid headers might be logged incorrectly.

*) Bugfix: socket leak when using HTTP/2.

*) Bugfix: in the ngx_http_v2_module.

--
--

Rationale for Update:

A longer term goal of the Server Team is to have NGINX 1.10.x (the next
stable release of NGINX) in Ubuntu Xenial, either as a post-Xenial-
release SRU, or right before we release, depending on when NGINX
releases the 1.10.x branch (which is based off the 1.9.x branch).

To reduce the delta between merges, and to reduce the amount of work
necessary to switch from 1.9.x to 1.10.x in the future of Xenial, it is
more preferable to have the latest 1.9.x available as close to 1.10.x
release as possible; this makes it much more easier to deal with build
failures, or to troubleshoot issues between versions, as there is less
of an upstream delta.

We do not enable HTTP/2, therefore the only feature change we should be
worried about here is the ability of the `worker_cpu_affinity` directive
being able to support more than 64 CPUs.  This does not affect other
functionality.

We have other bugfixes, as well, for other functions in the system,
including 'add_header' directives, and incorrect logging of invalid
headers.  These do not affect any of the other features in Ubuntu, nor
does this appear to affect the feature-set of NGINX.


--
--

Security Considerations:

HTTP/2
--
* HTTP/2 is disabled in the NGINX builds currently.  This is at the request of 
the Security Team.  There is no security concern of HTTP/2 in this release.


--
--

Files to be uploaded (Pending creation)

* Debdiff between 1.9.11-0ubuntu2 and 1.9.12-0ubuntu1 (direct upload)
* Local sbuild logs (amd64, i386)
* Installation log (Xenial amd64 VM)

** Affects: nginx (Ubuntu)
 Importance: Undecided
 Assignee: Thomas Ward (teward)
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1549347

Title:
  New upstream release - 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547070] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to nginx error: /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file: No such

[Thomas Ward]

This line in your nginx.conf will no longer work under OpenSSL 1.0.2:
ssl_engine rsax;

The rsax engine does not exist in OpenSSL 1.0.2.  You will need to
choose another SSL engine, or just remove that and use the defaults.

This is not a bug in the nginx package, nor is this a bug in the OpenSSL
package.

** Changed in: nginx (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547070

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to
  nginx error: /usr/lib/x86_64-linux-
  gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547070/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547642] Re: Xenial default configuration refers to PHP5, not PHP7; uses incorrect default php-fpm socket path as well

[Thomas Ward]

** Changed in: nginx (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547642

Title:
  Xenial default configuration refers to PHP5, not PHP7; uses incorrect
  default php-fpm socket path as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547642] Re: Xenial default configuration refers to PHP5, not PHP7; uses incorrect default php-fpm socket path as well

[Thomas Ward]

This is a bugfix only upload; it does not modify any existing
functionality nor does it bring any new features.  It simply updates the
configuration with regards to php7.0 existing and php5 not existing.

This did not make it in before FeatureFreeze due to my own mistake, and
some timing delays which delayed 1.9.11 entering Ubuntu in the first
place

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547642

Title:
  Xenial default configuration refers to PHP5, not PHP7; uses incorrect
  default php-fpm socket path as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547642] Re: Xenial default configuration refers to PHP5, not PHP7; uses incorrect default php-fpm socket path as well

[Thomas Ward]

Debdiff for the fix.

** Patch added: "Fix for the config issue"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+attachment/4575909/+files/lp1547642.debdiff

** Patch removed: "Fix for the default configuration"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+attachment/4575909/+files/lp1547642.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547642

Title:
  Xenial default configuration refers to PHP5, not PHP7; uses incorrect
  default php-fpm socket path as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547642] Re: Xenial default configuration refers to PHP5, not PHP7; uses incorrect default php-fpm socket path as well

[Thomas Ward]

** Patch added: "Debdiff / Fix for the default configuration"
   
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+attachment/4575910/+files/lp1547642.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547642

Title:
  Xenial default configuration refers to PHP5, not PHP7; uses incorrect
  default php-fpm socket path as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547642] [NEW] Xenial default configuration refers to PHP5, not PHP7; uses incorrect default php-fpm socket path as well

[Thomas Ward]

Public bug reported:

Given that we now are having php7.0 in Xenial, the default configuration
for NGINX needs updated to match.

While not enabled by default, the default configurations have 'preset'
items to make it easier to just 'enable' PHP support; this includes
pointing to the socket file path for php5-fpm.  Given we don't have
php5-fpm anymore, we need to update this to match php7.0-fpm's defaults
instead.

This does NOT add any new functionality, nor does it change any default
configuration of feature-enablement; it is to address cases where users
use the default configuration examples instead of setting site
configurations up themselves, so that we don't have any bugs filed for
'PHP FPM settings in defaults are not valid!' issues.

** Affects: nginx (Ubuntu)
 Importance: Medium
 Assignee: Thomas Ward (teward)
 Status: In Progress


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547642

Title:
  Xenial default configuration refers to PHP5, not PHP7; uses incorrect
  default php-fpm socket path as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547642/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545676] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

This is a non-deterministic failure error in the installation attempts
on the package.  According to everything, nginx is currently running.

The only thing I can suggest is that you try and stop nginx first, then
try and load it again, and see if that resolves the issue... because it
appears that everything is actually 'running'...

sudo service nginx stop
sudo service nginx start

** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1545676

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1545676/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543624] Re: Please update nginx in Xenial to 1.9.11

[Thomas Ward]

This was uploaded approximately two hours ago, and is now available in
the repositories.

The following is the changelog entry for the upload that has now marked
this as 'fix released':

nginx (1.9.11-0ubuntu1) xenial; urgency=low

  * New upstream release (1.9.11) - see http://nginx.org/en/CHANGES for
full changelog.
  * Ubuntu-specific changes from the 1.9.10 merge remain included here.
  * Additional changes:
- debian/modules/nginx-lua: Apply upstream patch to fix FTBFS issue

 -- Thomas Ward <tew...@ubuntu.com>  Tue, 09 Feb 2016 10:33:14 -0500

** Changed in: nginx (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543624

Title:
  Please update nginx in Xenial to 1.9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543624/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: MIR for pps-tools: DONE
  [arges] libvirt merge (bug 1533003) : DONE
  [arges] libvirt-python: DONE
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): DONE
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (rbasak will file FFE): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): INPROGRESS
  [nacc] Java-related work (=10days): INPROGRESS
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: DONE
  [jamespage] crmsh and pacemaker: DONE
- [teward] Update nginx to 1.9.11 (bug 1543624): INPROGRESS
+ [teward] Update nginx to 1.9.11 (bug 1543624): DONE
  [kick-d] Amavisd-new update: INPROGRESS
  [kick-d] moin merge: INPROGRESS
  [kick-d] urlgrabber merge: INPROGRESS
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  [kick-d] Get postfix migrated: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547070] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to nginx error: /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file: No such

[Thomas Ward]

Looking into this further (thanks to Marc on the Security Team), it
looks like your system is trying to use the rsax OpenSSL engine, which
is not shipped in Ubuntu.

Can you provide all your nginx configurations, please, so we can see
whether this is the case or not?

** Changed in: nginx (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547070

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to
  nginx error: /usr/lib/x86_64-linux-
  gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547070/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547070] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to nginx error: /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file: No such

[Thomas Ward]

I will look into this a bit further, but it looks like, for some reason,
your system is trying to depend on OpenSSL 1.0.0 libraries, instead of
OpenSSL 1.0.2 libraries.  It is possible you have a broken system,
because other package upgrades in your apt history log appeared to fail
as well.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547070

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to
  nginx error: /usr/lib/x86_64-linux-
  gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547070/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547070] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to nginx error: /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file: No such

[Thomas Ward]

Extracted from the error logs:

Feb 18 08:35:25 Parke.dynu.com nginx[24872]: nginx: [warn]
ENGINE_by_id("rsax") failed (SSL: error:25066067:DSO support
routines:DLFCN_LOAD:could not load the shared
library:filename(/usr/lib/x86_64-linux-
gnu/openssl-1.0.0/engines/librsax.so): /usr/lib/x86_64-linux-
gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file: No
such file or directory error:25070067:DSO support
routines:DSO_load:could not load the shared library
error:260B6084:engine routines:DYNAMIC_LOAD:dso not found
error:2606A074:engine routines:ENGINE_by_id:no such engine:id=rsax)

** Summary changed:

- package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to nginx 
error: /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax.so: cannot open 
shared object file: No such file or directory

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1547070

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade due to
  nginx error: /usr/lib/x86_64-linux-
  gnu/openssl-1.0.0/engines/librsax.so: cannot open shared object file:
  No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1547070/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545186] Re: package nginx-full 1.9.3-1ubuntu1.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1

[Thomas Ward]

*** This bug is a duplicate of bug 1543741 ***
https://bugs.launchpad.net/bugs/1543741

This was marked as a duplicate because the core issue with the
installation failing is observed to be identical to that of another bug.
This is also confirmed by the fact the authors of the two bugs are the
same person.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1545186

Title:
  package nginx-full 1.9.3-1ubuntu1.1 failed to install/upgrade:
  subprocesso script post-installation instalado retornou erro do status
  de saída 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1545186/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1545186] Re: package nginx-full 1.9.3-1ubuntu1.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1

[Thomas Ward]

*** This bug is a duplicate of bug 1543741 ***
https://bugs.launchpad.net/bugs/1543741

This is a duplicate of another bug.  ***DO NOT*** file duplicate bugs,
and please read all comments on the other bug, to try and determine why
it may have been closed.

** This bug has been marked a duplicate of bug 1543741
   package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade: subprocesso 
script post-installation instalado retornou erro do status de saída 1

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1545186

Title:
  package nginx-full 1.9.3-1ubuntu1.1 failed to install/upgrade:
  subprocesso script post-installation instalado retornou erro do status
  de saída 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1545186/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1512344] Re: [Master Bug] Package nginx-* failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (due to "Address in Use" issue)

[Thomas Ward]

@Sardinoux

That needs its own bug, with its own set of debug information - I tested
yesterday usin  a fresh Xenial copy and nginx installed without issue
(using nginx as the package name).  What you stated is NOT related to
this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1512344

Title:
  [Master Bug] Package nginx-* failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1 (due
  to "Address in Use" issue)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1512344/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: INPROGRESS
  [jamespage] crmsh and pacemaker: DONE
- [teward] Update nginx to 1.9.11 (bug 1543624): BLOCKED
+ [teward] Update nginx to 1.9.11 (bug 1543624): INPROGRESS
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543624] Re: Please update nginx in Xenial to 1.9.11

[Thomas Ward]

nginx 1.9.11-0ubuntu1.1~ppa0 in the PPA includes the following upstream
code patch for the nginx-lua module from OpenResty:

https://github.com/openresty/lua-nginx-
module/commit/64866bcf4d3c1d9f5990bb43507118d50904cc52.patch

This addresses the FTBFS introduced by the changes to NGINX 1.9.11
involving the udp connection item inside of NGINX.

--

This successfully builds on all arches available to my build tests PPA
(amd64 i386 arm64 armhf ppc64el), and correctly operates.

All other Ubuntu specific changes from the merge remain in place.  I am
planning to upload 1.9.11-0ubuntu1, with an updated changelog to include
the upstream patch from OpenResty to fix the FTBFS, within the next
several hours, unless Debian provides an upload that can be merged here,
first.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543624

Title:
  Please update nginx in Xenial to 1.9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543624/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1538165] Re: Security Issues Impacting NGINX: 1.8.x, 1.9.x

[Thomas Ward]

** Bug watch added: Debian Bug tracker #812806
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812806

** Also affects: nginx (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812806
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1538165

Title:
  Security Issues Impacting NGINX: 1.8.x, 1.9.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1538165/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543741] Re: package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1

[Thomas Ward]

This isn't really a bug.

Fev 09 19:04:59 jaime-A6JC nginx[3077]: nginx: [emerg]
BIO_new_file("/etc/diaspora/ssl/localhost-bundle.pem") failed (SSL:
error:02001002:system library:fopen:No such file or
directory:fopen('/etc/diaspora/ssl/localhost-bundle.pem','r')
error:2006D080:BIO routines:BIO_new_file:no such file)


This error, extracted from the error output in `systemctl -l status nginx`, 
indicates that it is attempting to open a certificate in .pem format in 
`/etc/diaspora/ssl/localhost-bundle.pem'.  This file does not exist, or NGINX 
does not have the access to reach it.  Therefore, this is a configuration error 
on the system in which your install/upgrade failed.  Please go back and verify 
the configuration options you use which specify paths to certificates and such 
actually exist on your system.

** Changed in: nginx (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543741

Title:
  package nginx-core 1.9.3-1ubuntu1.1 failed to install/upgrade:
  subprocesso script post-installation instalado retornou erro do status
  de saída 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543741/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: TODO
  [jamespage] crmsh and pacemaker: DONE
+ [teward] Update nginx to 1.9.11 (waiting on Deian for coordinated release 
discussion): TODO
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: TODO
  [jamespage] crmsh and pacemaker: DONE
- [teward] Update nginx to 1.9.11 (waiting on Deian for coordinated release 
discussion): TODO
+ [teward] Update nginx to 1.9.11: TODO
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: TODO
  [jamespage] crmsh and pacemaker: DONE
- [teward] Update nginx to 1.9.11: TODO
+ [teward] Update nginx to 1.9.11 (bug 1543624): TODO
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543624] [NEW] Please update nginx in Xenial to 1.9.11

[Thomas Ward]

Public bug reported:

NGINX 1.9.11 was released on February 9, 2016. Specifics of note are
bugfixes in HTTP/2 (which remains disabled in Ubuntu), TCP support in
the resolver functions, and the first of the dynamic modules
functionality.

--

This is the upstream changelog:

Changes with nginx 1.9.1109 Feb
2016

*) Feature: TCP support in resolver.

*) Feature: dynamic modules.

*) Bugfix: the $request_length variable did not include size of request
   headers when using HTTP/2.

*) Bugfix: in the ngx_http_v2_module.

--

Coordination for the dynamic modules inclusion will be done with Debian,
as they should likely be the first to produce dynamic-module-based
packaging; once it's in Debian we may wish to consider it for inclusion
later, with the release team's approval to do so.  Such dynamic module
inclusion will very likely result in an increase in the number of built
binary packages, but this will be determined at a later time.

For updating nginx in Xenial to 1.9.11, there should be no major
packaging changes - as I would rather Debian come up with the module-
specific-packages first, so it can then be merged and included into
Xenial.

I am currently touching base with Debian to determine if we want to do a
coordinated release; if I don't hear from them, then nginx 1.9.11 will
likely get its own upload with the -0ubuntu1 version suffix.  (All
changes from the prior merges will remain in place).

** Affects: nginx (Ubuntu)
 Importance: Wishlist
 Assignee: Thomas Ward (teward)
 Status: In Progress


** Tags: xenial

** Description changed:

  NGINX 1.9.11 was released on February 9, 2016. Specifics of note are
  bugfixes in HTTP/2 (which remains disabled in Ubuntu), TCP support in
  the resolver functions, and the first of the dynamic modules
  functionality.
  
  --
  
  This is the upstream changelog:
  
+ Changes with nginx 1.9.1109 Feb
+ 2016
  
- Changes with nginx 1.9.1109 Feb 2016
+ *) Feature: TCP support in resolver.
  
- *) Feature: TCP support in resolver.
+ *) Feature: dynamic modules.
  
- *) Feature: dynamic modules.
+ *) Bugfix: the $request_length variable did not include size of request
+    headers when using HTTP/2.
  
- *) Bugfix: the $request_length variable did not include size of request
-headers when using HTTP/2.
- 
- *) Bugfix: in the ngx_http_v2_module.
+ *) Bugfix: in the ngx_http_v2_module.
  
  --
  
  Coordination for the dynamic modules inclusion will be done with Debian,
  as they should likely be the first to produce dynamic-module-based
  packaging; once it's in Debian we may wish to consider it for inclusion
  later, with the release team's approval to do so.  Such dynamic module
  inclusion will very likely result in an increase in the number of built
  binary packages, but this will be determined at a later time.
  
- For updating nginx in Xenial to 1.9.11, there will be no packaging
- changes - as I would rather Debian come up with the module-specific-
- packages first, so it can then be merged and included into Xenial.
+ For updating nginx in Xenial to 1.9.11, there should be no major
+ packaging changes - as I would rather Debian come up with the module-
+ specific-packages first, so it can then be merged and included into
+ Xenial.
  
  I am currently touching base with Debian to determine if we want to do a
  coordinated release; if I don't hear from them, then nginx 1.9.11 will
  likely get its own upload with the -0ubuntu1 version suffix.  (All
  changes from the prior merges will remain in place).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543624

Title:
  Please update nginx in Xenial to 1.9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543624/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: TODO
  [jamespage] crmsh and pacemaker: DONE
  [teward] Update nginx to 1.9.11 (bug 1543624): TODO
  
- Work items for ubuntu-16.03:
- [teward] Update nginx to 1.10.x after upstream release: BLOCKED
- 
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
+ [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
  [louis-bouchard] clamav merge: INPROGRESS
  [jamespage] crmsh and pacemaker: DONE
- [teward] Update nginx to 1.9.11 (bug 1543624): TODO
+ [teward] Update nginx to 1.9.11 (bug 1543624): BLOCKED
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543624] Re: Please update nginx in Xenial to 1.9.11

[Thomas Ward]

We are not rolling Dynamic Module support at this time, though it's
available in core.  To build dynamic modules, one must build the module
alongside nginx, at compile time, but it will produce .so shared library
objects that can be individually packaged.

There is an FTBFS in the nginx-extras flavor, with the Lua module.  This
is blocking uploading NGINX 1.9.11 to Ubuntu.

Ongoing tracking of the incompatibility can be found at these upstream links 
for the Lua module:
https://github.com/openresty/lua-nginx-module/issues/668
https://github.com/openresty/lua-nginx-module/pull/669

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543624

Title:
  Please update nginx in Xenial to 1.9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543624/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1543624] Re: Please update nginx in Xenial to 1.9.11

[Thomas Ward]

As previously with uploads/merges to Xenial, this is being build-tested
in https://launchpad.net/~teward/+archive/ubuntu/xenial-buildtests.
Subsequent versions of the package in this PPA will get +b1, +b2, etc.
appended to the end for build testing purposes.

Depending on whether Debian gets a solution for this sooner than I do, this 
will be versioned for Ubuntu as one of the following:
Direct Upload: 1.9.11-0ubuntu1
Merge from Debian: 1.9.11-1ubuntu1

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1543624

Title:
  Please update nginx in Xenial to 1.9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1543624/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1538165] Re: Security Issues Impacting NGINX: 1.8.x, 1.9.x

[Thomas Ward]

As Vivid reaches End of Life tomorrow, and that provides insufficient
time for a fix to be produced for that version of the package, we are
marking this as "Won't Fix" on Vivid.

** Changed in: nginx (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1538165

Title:
  Security Issues Impacting NGINX: 1.8.x, 1.9.x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1538165/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

** Changed in: nginx (Ubuntu)
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

Digging around further in your Dpkg History that was attached here, it
looks like you have Apache installed.  Nginx won't start if port 80 is
bound to, but without the additional bug information I can't determine
if that's the issue (though it's likely one of the main culprits)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

There is nothing in your bug here that indicates any type of bug in the
NGINX package.

Without further debugging information, there is nothing here to suggest
any type of bug in the NGINX package, or in others.  Therefore, without
any additional debugging information, and since you said you no longer
need it, I am going to leave this bug as Incomplete until such time
there's sufficient debugging information to determine whether this is or
is not a bug.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Thomas Ward]

Blueprint changed by Thomas Ward:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [nacc] logwatch merge and cleanup: INPROGRESS
  [smoser] openiscsi merge: TODO
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
- [teward] Merge nginx 1.9.10 (extra Debian changes not already included): 
INPROGRESS
+ [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  
  Work items for ubuntu-16.02:
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
  [rharper] Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [racb] squid3 merge (=4days): TODO
  [louis-bouchard] nut merge: DONE
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

Also, please refresh your apt information with `apt-get update`; there
was a recent upload of nginx 1.9.10-1ubuntu1 which addresses security
issues as well as other fixes, and it is necessary to test that version
rather than the older 1.9.9-1ubuntu1 which you are attempting to
install.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

Missing some information here for diagnosis - specifically the terminal
output of the dpkg commands and such which are executed.  Can you copy
the complete terminal output you get when you try and install nginx
please?

** Changed in: nginx (Ubuntu)
   Status: New => Confirmed

** Changed in: nginx (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1539316] Re: package nginx-core (not installed) failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

[Thomas Ward]

We are missing information still for debugging this.  There also appears
to be a different issue as well with apport hooks.

I need you to include the output of the following command, please, as
either a comment on your bug or as an attachment:

systemctl -l nginx.service status


This will likely contain additional information, because it failed to
start after configuring the package, which suggests something else is at
play, and the error message was not obtained here.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1539316

Title:
  package nginx-core (not installed) failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1539316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs