[Bug 1761899] [NEW] [FFe] Please merge with 1.13.10-1 from Debian unstable

Public bug reported: Feature Freeze exception: Much like 16.04, we want to get nginx in 18.04 as close to a LTS release as possible. Future updates to get the actual upstream LTS release will come from bionic-updates. Features between 1.13.6 and 1.13.10: https://nginx.org/en/CHANGES **

[Bug 1761370] Re: package libapache2-mod-php7.0 7.0.28-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thank you for filing this bug report. Per the output: modified.conffile..etc.apache2.mods-available.php7.0.conf: [deleted] modified.conffile..etc.apache2.mods-available.php7.0.load: [deleted] You have deleted the apache2 configuration for the php7.0 module. If your goal was to disable PHP

[Bug 1757344] Re: package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to php7.1 in Ubuntu. https://bugs.launchpad.net/bugs/1757344 Title: package php7.1-sqlite3

[Bug 1638957] Re: [MIR] http-parser, dependency of sssd

Given the security team ack, and the package generally, fine to MIR I believe the only package that needs promotion (other than the source): libhttp-parser2.7.1 ** Changed in: http-parser (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are

[Bug 1757344] Re: package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

Hello and thank you for filing this bug! Was your update performed from a terminal (e.g., using apt or apt-get) or from a GUI (e.g. update-manager)? If the latter, which GUI? The segmentation fault reported is actually in the package manager itself (the frontend of it), not with PHP. A

[Bug 1638957] Re: [MIR] http-parser, dependency of sssd

** Changed in: http-parser (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1638957 Title: [MIR] http-parser, depende

[Bug 1753018] Re: Please merge strongswan 5.6.2-1 from Debian

FYI, the CVE was already fixed in 5.6.1-2ubuntu4. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1753018 Title: Please merge strongswan 5.6.2-1 from Debian To manage notifications

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

** Attachment added: "php7.1_7.1.15-0ubuntu0.17.10.1.dsc" https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079883/+files/php7.1_7.1.15-0ubuntu0.17.10.1.dsc -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to php7.1

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

@Marc: php7.0/7.1 is ready to sponsor into xenial-security (and -updates). You should only need to do some changelog mangling to match the security team's format, and a `uscan` to grab the orig tarball from upstream. ** Changed in: php7.0 (Ubuntu Xenial) Assignee: Nish Aravamudan (nacc

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

** Attachment added: "php7.1_7.1.15-0ubuntu0.17.10.1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079884/+files/php7.1_7.1.15-0ubuntu0.17.10.1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Server, which is

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

** Attachment added: "php7.0_7.0.28-0ubuntu0.16.04.1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079866/+files/php7.0_7.0.28-0ubuntu0.16.04.1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Server, which is

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

** Attachment added: "php7.0_7.0.28-0ubuntu0.16.04.1.dsc" https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079867/+files/php7.0_7.0.28-0ubuntu0.16.04.1.dsc -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to php7.1

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

** Changed in: php7.2 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to php7.1 in Ubuntu. https://bugs.launchpad.net/bugs/1744148 Title: [MRE] Please update to latest upstream release

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

) ** Changed in: php7.1 (Ubuntu) Status: New => Invalid ** Changed in: php7.1 (Ubuntu Artful) Status: New => In Progress ** Changed in: php7.1 (Ubuntu Artful) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Also affects: php7.2 (Ubuntu) Importance: Undecided St

[Bug 1596474] Re: openipmi adding to autoload fail

** Changed in: openipmi (Ubuntu Xenial) Assignee: Nish Aravamudan (nacc) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1596474 Title: openipmi adding to autol

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Based upon discussion, we will not be fixing this in Trusty. Updating the SysV scripts to be more error-proof is itself error-prone. Additionally, corosync on Trusty has not received significant updates, and this update itself would lead to at least an additional outage (in order to put the fix

[Bug 1744072] Re: [MIR] Chrony in 18.04

I reviewed chrony; it's fine to MIR (and has security team approval). MIR ACKed. ** Changed in: chrony (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu.

[Bug 1749745] [NEW] php7.2 has removed the mcrypt module

Public bug reported: http://php.net/manual/en/migration71.deprecated.php There are a number of affected packages. ** Affects: cakephp (Ubuntu) Importance: Undecided Status: New ** Affects: gosa (Ubuntu) Importance: Undecided Status: New ** Affects: php-crypt-chap

[Bug 1744072] Re: [MIR] Chrony in 18.04

** Changed in: chrony (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: chrony (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu.

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

I have uploaded the fixes today to Bionic. I will update the bug once they are migrated, but the SRUs should be startable now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1740892

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

I did some cursory testing yesterday (I still need to think about how to do a X -> B upgrade w/ a PPA) of B -> B updates. pacemaker stays running as expected. I am checking (via the MP, a comment recently) if it's possible to minimize our changes even more in 18.04. -- You received this bug

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Sorry for the long delay on my end! I have pushed up MPs for the correct resolution (I think) for Bionic (incl. appropriate comments of what can be dropped after B+1 opens). I am building them in my PPA (pacemaker 1.1.18~rc4-1ubuntu1~ppa1 and corosync 2.4.2-3ubuntu1~ppa1) now and will test the

[Bug 1621386] Re: [MIR] libsodium

** Changed in: libsodium (Ubuntu) Status: Fix Released => Won't Fix ** Changed in: libsodium (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libsodium in Ubuntu.

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.27

** Changed in: php7.0 (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1744148 Title: [MRE] Please update to latest upstream

[Bug 1743904] Re: Please merge with Debian unstable 57

** Description changed: php-defaults (57ubuntu1) bionic; urgency=medium - - * Merge with Debian unstable (LP: #1743904). Remaining changes: - - d/control, d/rules: bump to php7.1 as the default. - + Update text of d/control to refer to Ubuntu and 7.1 as well. - + d/control

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

On Xenial: corosync2.3.5-3ubuntu2.1~ppa3 pacemaker 1.1.14-2ubuntu1.4~ppa3 The same 3 test cases as in c#39 alll passed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu.

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

4) a case I am not sure what to do with yet (in Trusty or Xenial): stopping pacemaker and then installing the PPA packages. I'm not sure how to handle this, really, for 16.04, as the deb-helper scripts don't seem to have status wrappers and calling systemctl directly does not apparently work. The

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

After hitting some corner cases with my Trusty packages (and Xenial), I uploaded new versions: corosync - 2.3.3-1ubuntu4.1~ppa7 pacemaker - 1.1.10+git20130802-1ubuntu2.5~ppa4 And ran the following tests: 1) install corosync and pacemaker, but do not enable either Upgrade to the PPA packages No

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Xenial MPs updated and packages uploaded to PPA: corosync - 2.3.5-3ubuntu2.1~ppa2 pacemaker - 1.1.14-2ubuntu1.4~ppa2 Bionic will have to wait til tomorrow. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu.

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

I tested the versions mentioned in the last comment (with one syntax fix) and the upgrade path successfully worked! I need to test more corner-cases and would appreciate help with that (e.g., corosync only installed, installing pacemaker separately, etc) The MPs have been updated and I'm building

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

Filed: https://bugs.launchpad.net/debian/+source/php-sabre- vobject-3/+bug/1744166 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

The only legitimate bug is php-sabre-vobject-3, which is unrelated to this upload. I will fix it independently. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337 ** Bug watch added: Debian Bug tracker #880337 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337 -- You received

[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.27

* Changed in: php7.0 (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: php7.0 (Ubuntu Xenial) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 i

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Big thanks to Robie Basak for providing some feedback and discussion on IRC and in the MP. We came up with the following, which I'm currently testing, to try and resolve this issue: In addition to all the changes currently in the MP(s), modify: corosync to Breaks: on older pacemaker versions

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

I should say, retrigger the lot, once we are allowed to again :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest upstream release 7.0.25

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

So far everyting I've seen is false negatives due to infra issues. I'm retriggering the lot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to

[Bug 1743904] [NEW] Please merge with Debian unstable 57

by `./debian/rules debian/control` -- Nishanth Aravamudan <nish.aravamu...@canonical.com> Wed, 17 Jan 2018 15:55:22 -0800 ** Affects: php-defaults (Ubuntu) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Changed in: php-defaults (Ubuntu) As

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

** Bug watch added: Debian Bug tracker #887563 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 ** Also affects: corosync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Testing on Trusty: # apt-get install corosync pacemaker # Make corosync start at boot # sed -i 's/no/yes/' /etc/default/corosync # Make pacemaker start at boot # update-rc.d pacemaker defaults # reboot # service corosync status; service pacemaker status * corosync is running pacemakerd (pid

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Ok, I've put up MPs for Trusty (just corosync) and Xenial (corosync and pacemaker). I think that's correct, and the underlying bug here (package upgrade of corosync does not lead to pacemaker restarting) should be resolved in both cases [1) in c#33]. Additionally, case 2) in c#33 is resolved in

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

8) On Xenial and on, where we have systemd .service files for both corosync and pacemaker, this is my current understanding (after looking at the .service files and thinking about the Trusty case, as well; some of this is repeats of others' observations): 8a) corosync can be installed configured

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

My findings from today: 1) This situation has always existed on Trusty, afaict. Removing the regression related tag. 2) There are 24 possible combinations to consider (some are by definition green already, but I'm including them for completeness; and some are not achievable) for each release:

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage notifications

[Bug 1743059] Re: Please merge with Debian unstable 1.1.18~rc4-1

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336063 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1743059 Title:

[Bug 1743059] [NEW] Please merge with Debian unstable 1.1.18~rc4-1

14.04. -- Nishanth Aravamudan <nish.aravamu...@canonical.com> Fri, 12 Jan 2018 16:30:04 -0800 ** Affects: pacemaker (Ubuntu) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Changed in: pacemaker (Ubuntu) Status: New => In

[Bug 1742319] Re: Please merge with Debian unstable 3.1.20-3.1

** Changed in: at (Ubuntu) Status: New => In Progress ** Changed in: at (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to at in Ubuntu. https://bugs.launchp

[Bug 1597315] Re: package libapache2-mod-php7.0 7.0.4-7ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: php7.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1597315 Title: package libapache2-mod-php7.0 7.0.4-7ubuntu2.1

[Bug 1742319] [NEW] Please merge with Debian unstable 3.1.20-3.1

Public bug reported: TBD ** Affects: at (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to at in Ubuntu. https://bugs.launchpad.net/bugs/1742319 Title: Please merge with Debian

[Bug 1566519] Re: Please add native systemd units

This was fixed in Debian in 2.4.23-5, which is in Zesty+. ** Changed in: apache2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1566519

Re: [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote: > As mentioned by Mario @ #10, stopping corosync while pacemaker runs > throws the same error as the upgrade. Syslog from Xenial + > corosync=2.3.5-3ubuntu1: > > Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping

Re: [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

On Mon, Jan 8, 2018 at 10:04 AM, Nish Aravamudan <nish.aravamu...@canonical.com> wrote: > On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan > <nish.aravamu...@canonical.com> wrote: >> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia <victor.ta...@canonical.com> >> wr

Re: [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan <nish.aravamu...@canonical.com> wrote: > On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia <victor.ta...@canonical.com> > wrote: >> As mentioned by Mario @ #10, stopping corosync while pacemaker runs >> throws the same err

Re: [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote: > As mentioned by Mario @ #10, stopping corosync while pacemaker runs > throws the same error as the upgrade. Syslog from Xenial + > corosync=2.3.5-3ubuntu1: > > Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping

Re: [Bug 1658469] Re: [FFe] mod_http2 is not available in Apache

On Wed, Nov 22, 2017 at 5:20 AM, Mathias <1658...@bugs.launchpad.net> wrote: > Bionic includes the /etc/apache2/mods-available/proxy_http2.load file, > but the module mod_proxy_http2.so has been removed. > > Is it a mistake? > > Suite: Ubuntu 18.04 (bionic) >

[Bug 1658469] Re: [FFe] mod_http2 is not available in Apache

This is now enabled in bionic. ** Changed in: apache2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1658469 Title: [FFe] mod_http2 is

[Bug 1740160] Re: Please consider removing tickcount from Ubuntu

@kirkland: accumulated justifications: 1) no python3 support (not possible? per c#1) -- which implies we'd remove it eventually anyways 2) no reverse-depends (no consumers) 3) not in Debian, so it's purely technical debt? I haven't looked to see if there have been many/any bugs over the years,

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

@afreiberger, thank you for the extra info! Reading the upstream patch referred to in Bug 1739033, I see this change: struct main_cp_cb_data { - enum main_cp_cb_data_state state; - int ringnumber; char *bindnetaddr; char *mcastaddr; Now, that is a struct size

[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

Hello, Being relatively new to pacemaker/corosync -- what is the actual error condition here? That when corosync is stopped (as part of the package upgrade), pacemakerd stops and does not restart? Thanks, Nish -- You received this bug notification because you are a member of Ubuntu Server

Re: [Bug 1734967] Re: tzdata info for WGT/WGST broken

Does the Ubuntu php build use the bundled tzdata? A lot of stuff comes from the system not the source (e.g, pcre iirc) On Dec 1, 2017 18:40, "Eric Desrochers" wrote: > Same thing with new php pkg release in debian/unstable (php - 7.1.12-1). > It still displays

Re: [Bug 1734967] Re: tzdata info for WGT/WGST broken

Is this already fixed in proposed (MRE to latest upstream php 7.0 and 7.1)? On Dec 1, 2017 03:48, "Bug Watch Updater" <1734...@bugs.launchpad.net> wrote: > ** Changed in: php7.0 (Debian) >Status: Unknown => New > > -- > You received this bug notification because you are subscribed to

[Bug 1734967] Re: tzdata info for WGT/WGST broken

Just to be clear, this isn't a bug based upon comment 1 but new tasks were opened in comment 2? If it's purely an SRU regression in tzdata that should be figured out. Im guessing this is an upstream php issue. Has it been fixed there? -- You received this bug notification because you are a

[Bug 1732918] Re: iscsitarget-dkms 1.4.20.3+svn502-2ubuntu4.4 doesn't build for Xenial hwe (4.10) kernel

You dont' need iscsitarget-dkms on any new kernel. https://bugs.launchpad.net/bugs/1668808 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to iscsitarget in Ubuntu. https://bugs.launchpad.net/bugs/1732918 Title: iscsitarget-dkms

[Bug 1729036] Re: [MRE] Please update to latest upstream release 7.1.11

Performed my normal LXD verification by upgrade php7.1 in a 17.10 container. # apt policy php7.1 php7.1: Installed: 7.1.11-0ubuntu0.17.10.1 Candidate: 7.1.11-0ubuntu0.17.10.1 Version table: *** 7.1.11-0ubuntu0.17.10.1 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

Brian, was there any problem with the 16.04 upload, or were you letting 17.04 shake out any issues first? ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

Performed my normal LXD verification for an upgrade in 17.04 from 7.0.22-0ubuntu0.17.04.1 to 7.0.25-0ubuntu0.17.04.1. root@fluent-grouse:~# apt policy php7.0 php7.0: Installed: 7.0.25-0ubuntu0.17.04.1 Candidate: 7.0.25-0ubuntu0.17.04.1 Version table: *** 7.0.25-0ubuntu0.17.04.1 500

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

I'm guessing this might be a quirk of the armhf runners: test_tree_garbage (__main__.ChrootRunner) copied source tree contains only expected files ... : Operation not permitted cp: cannot create special file ‘/tmp/tmp36ee0r77/chroot//dev/null’: Operation not permitted cp: cannot create special

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

If someone is interested in the proper upstream fixes, please file a new bug and we will need to fix bionic and prepare a distinct SRU for the existing releases. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report.

[Bug 1712441] Re: pacemaker 1.1.17-1ubuntu1 FTBFS

I just uploaded https://launchpad.net/ubuntu/+source/pacemaker/1.1.18~rc3-1ubuntu1 which has the fix from Debian for the corresponding bug (I'm not sure why the Debian bug hasn't been closed). I'm not sure if it's worth SRU'ing it or not. I suppose to artful- proposed, at least, it is, since

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

** Description changed: There have been a number of microreleases of PHP 7.0 upstream since the last update to Xenial (which corresponded to the last update in Zesty). As it has been a few months, it feels appropriate to provide another MRE update to php7.0. A number of critical security

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

** Also affects: php7.0 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: php7.0 (Ubuntu Zesty) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: php7.0 (Ubuntu Zesty) Status: New => In Progress -- You received this bug notification becau

[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25

** Summary changed: - [MRE] Please update to latest upstream release 7.0.24 + [MRE] Please update to latest upstream release 7.0.25 ** No longer affects: php7.0 (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0

Re: [Bug 1729064] Re: package bacula-director-pgsql 7.0.5+dfsg-4ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

On Wed, Nov 1, 2017 at 7:26 AM, Andreas Hasenack wrote: > It worked out of the box in artful, so the fix is somewhere in between > xenial and artful. I would check the changes in 7.4.1~dfsg-1 or 7.4.2+dfsg-1 or 7.4.3+dfsg-1. Also, iirc (only vaguely possibly true),

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote: > @arges > > Hi, would you need any more testing from us? Nope, your part is done. All SRUs have to bake for 7 days in -proposed to shake out regressions. -- You received this bug notification because you are a

[Bug 1729036] [NEW] [MRE] Please update to latest upstream release 7.1.11

would result in 7.2.0. We already had an MRE for php7.0 in X and Y, and this is the corresponding source package in AA. ** Affects: php7.1 (Ubuntu) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Affects: php7.1 (Ubuntu Artful) Importance

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

** No longer affects: php7.1 (Ubuntu Artful) ** Summary changed: - [MRE] Please update to latest upstream release 7.1.10 + Please update to latest upstream release 7.1.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.1 in

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

Thanks for letting me know. I'll do an update to 7.1.11 shortly for bionic and then work with the security team to replace the update in artful. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1283 -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

Are you referring to: PCRE: Fixed bug #75207 (applied upstream patch for CVE-2016-1283). ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.1 in Ubuntu. https://bugs.launchpad.net/bugs/1724902 Title: [MRE] Please update to

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

I asked Steve Langasek to reject the unapproved upload of php7.1 so that I can do a proper SRU version, now that Bionic is open. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.1 in Ubuntu. https://bugs.launchpad.net/bugs/1724902

[Bug 1721607] Re: please update to latest upstream release 7.0.24

Just an FYI that I have uploaded an update to php7.0 for x and z and php7.1 for aa (which should get copied to bb, but bb will end up with 7.2 before release), but not as a security update. It will go through the normal SRU process before being available. -- You received this bug notification

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote: > On 20.10.2017 [07:18:15 -], Jan Gutter wrote: > > I had a look at the two proposals and could not spot any obvious > > mistakes: > > > > - the correct upstream git commit has been cherry-picked > &

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

On 20.10.2017 [07:18:15 -], Jan Gutter wrote: > I had a look at the two proposals and could not spot any obvious > mistakes: > > - the correct upstream git commit has been cherry-picked > - I don't have any objections to attribution or log messages > > Thanks again for shepherding this one

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

On 20.10.2017 [07:09:00 -], Jan Gutter wrote: > I concur with option 2), unnecessary deviation will just cause > confusion. Thank you for confirming that! > Regarding the other buffer sizes, the last time I looked they were > mostly OK. The issue reared its head in this particular case

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

I have set up two MPs with the adjustments (it looks like Monique's latest debdiffs followed path 2) from my previous comment already) to the DEP3 headers that I think make the most sense. Please take a look at them and if you approve the changes I will upload them. I note also there are a number

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

** Description changed: There have been a number of microreleases of PHP 7.1 upstream since the last update to Artful. As it has been a few months, it feels appropriate to provide a MRE update to php7.1. A number of critical security and bug-fixes are present in each 7.1.x. Rather than

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

I will probably SRU this ahead of BB opening, which will imply we'll need a copy-forward for BB. ** Changed in: php7.1 (Ubuntu Bb-series) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.1 in

[Bug 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

** Changed in: php7.1 (Ubuntu Artful) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: php7.1 (Ubuntu Bb-series) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: php7.1 (Ubuntu Bb-series) Status: New => In Progress ** Changed in: php7.

[Bug 1724902] [NEW] [MRE] Please update to latest upstream release 7.1.10

would result in 7.2.0. ** Affects: php7.1 (Ubuntu) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Affects: php7.1 (Ubuntu Artful) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Affects: php7.1

[Bug 1724896] [NEW] [MRE] Please update to latest upstream release 7.0.24

: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Affects: php7.0 (Ubuntu Xenial) Importance: Undecided Assignee: Nish Aravamudan (nacc) Status: In Progress ** Also affects: php7.0 (Ubuntu Trusty) Importance: Undecided Status: New ** Also

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

@mvandenberg, Couple of nits in your debdiffs. 1) changelogs are targetting UNRELEASED, please update to xenial and trusty respectively. 2) Is there a reason your fix is different than the fix upstream/Debian? Does Debian need your version instead? 3) Please use appropriate DEP3 headers

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

On 17.10.2017 [08:56:17 -], Jan Gutter wrote: > @nacc I built from source to verify that the one-liner is directly > responsible for fixing and breaking the issue (inherent paranoia). I did > test with the binaries and they worked. Ah ok, yeah -- I guess that's reasonable, and is a good

[Bug 1720029] Re: Backport "Re-enable SSL support by default. Compatibility with older versions has been fixed." to zesty.

Hello and thank you again for the report. I am looking at the fix, and the NEWS and changelog files say: + The bug that caused the SSL support between NRPE 2.x and 3.x not + to work has been fixed. What bug? Where was it fixed? Will updating just nagios-nrpe break existing 17.04 installs? --

[Bug 1721607] Re: please update to latest upstream release 7.0.24

Thank Tyler :) Steven, a) The patched version from Ondrej's repo is not an official, nor supported version, it's irrelevant to this discussion. b) If you can provide the CVEs that Tyler asked for, then a security update will occur. c) We do have an MRE for PHP7.0 (probably also for PHP7.1 by

[Bug 1721468] Re: Free invalid pointer crash in vnc

@berrange, if so, can @peter-sabaini verify that it is fixed in 17.04 (2.8 based) and Artful (2.10 based). ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu.

[Bug 1719671] Re: [SRU][xenial] include fips enablement into ubuntu-advantage

After chatting on IRC, this was fixed in Artful in LP: #1718291. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Fix Released ** Also affects: ubuntu-advantage-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

@jangutter: I'm not sure why you built from source? I assume you actually tested the version in 17.04 and it worked. The proper solution is to backport the Debian change to xenial and trusty, most likely. A git repository that can be used with `git-ubuntu` (sudo snap install --classic

[Bug 1721546] Re: max open files limit prevents max_connections over 214 on systemd

Should this be fixed in Debian? Or at least reported there? So that it does not add to the delta? And is the underlying proposed fix to add the Service LimitNOFILE change to the default mysql service file? -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 1719671] Re: [SRU][xenial] include fips enablement into ubuntu-advantage

@j-latten: It's unclear to me if this is actually intended for all releases (based upon the nominated tasks by Manoj and Andreas) or just Xenial (based upon the bug description). Can you clarify? -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

** Also affects: iproute2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: iproute2 (Ubuntu Xenial)

[Bug 1722808] Re: update to 2.10.1 point release

@paelzer, should this be assigned to you? Not sure if there is an explicit request here for someone else to pick this up? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1722808 Title:

[Bug 1718291] Re: [FFe]: Include FIPS into the ubuntu-advantage tool

Sponsored. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1718291 Title:

  1   2   3   4   5   6   >