Just as an FYI, I'm uploading the SRU of 7.0.18 to all three release
today, it will need some help testing from proposed once it's landed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674892
Title:
** Changed in: php7.0 (Ubuntu)
Status: New => Fix Released
--
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/1686237
Title:
[SRU] microrelease exception for src:php7.0 (7.0.18)
** Changed in: php7.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686237
Title:
[SRU] microrelease exception for src:php7.0 (7.0.18)
To manage
** Also affects: php7.0 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: php7.0 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: php7.0 (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification
** Also affects: php7.0 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: php7.0 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: php7.0 (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: php7.0 (Ubuntu Artful)
Status: Fix Committed => Fix Released
** Changed in: php7.0 (Ubuntu Artful)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: php7.0 (Ubuntu Zesty)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: php7.
** Changed in: php7.0 (Ubuntu Artful)
Status: Fix Committed => Fix Released
** Changed in: php7.0 (Ubuntu Artful)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: php7.0 (Ubuntu Zesty)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: php7.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667834
Title:
Defer php7.1 to Artful
To manage notifications about this bug go to:
7.0.18-2ubuntu1 has landed in 17.10.
** Description changed:
There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the merge in Zesty). As we
have re-merged again in Artful, it feels appropriate to provide another
MRE update
7.0.18-2ubuntu1 has landed in 17.10.
** Description changed:
There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the merge in Zesty). As we
have re-merged again in Artful, it feels appropriate to provide another
MRE update
I just uploaded 7.0.18 to artful. I will SRU this back next to the
various releases.
** Changed in: php7.0 (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just uploaded 7.0.18 to artful. I will SRU this back next to the
various releases.
** Changed in: php7.0 (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.0 in Ubuntu.
** Summary changed:
- [FFe] Please remove php7.1 from zesty
+ Defer php7.1 to Artful
** Changed in: php7.1 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the merge in Zesty). As we
have re-merged again in Artful, it feels appropriate to provide another
MRE update to php7.0. A number of critical security and
Public bug reported:
There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the merge in Zesty). As we
have re-merged again in Artful, it feels appropriate to provide another
MRE update to php7.0. A number of critical security and
.
-- Nishanth Aravamudan <nish.aravamu...@canonical.com> Wed, 08 Feb 2017
17:06:48 -0800
** Affects: php7.0 (Ubuntu)
Importance: Undecided
Assignee: Nish Aravamudan (nacc)
Status: New
** Changed in: php7.0 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
.
-- Nishanth Aravamudan <nish.aravamu...@canonical.com> Wed, 08 Feb 2017
17:06:48 -0800
** Affects: php7.0 (Ubuntu)
Importance: Undecided
Assignee: Nish Aravamudan (nacc)
Status: New
** Changed in: php7.0 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
: Confirmed => Invalid
** Changed in: php7.0 (Ubuntu)
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/1677578
Title:
ph
: Confirmed => Invalid
** Changed in: php7.0 (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677578
Title:
php-fcgi: max_executio
If you are dropped to an emergency shell on failure to boot, does name
resolution period work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never
Almost certainly the issue is that login.service is not waiting for
networking before starting, when ldap is configured.
In the screenshot, I see "Failed to start Login Service" and then later
"Started to raise network interfaces".
--
You received this bug notification because you are a member
Finally, is this reproducible with 17.04? Note that 16.10 goes eol in
about 3 months so there is some non-zero cost to trying to fix it there,
if it's already fixed in 16.10.
** Changed in: libpam-ldap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
I would subscribe ~ubuntu-archive to this and ask for some AA help if
there is going to need to be done in a side PPA.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ldap-auth-client in Ubuntu.
https://bugs.launchpad.net/bugs/1646954
For what it's worth, the same version of libpam-ldap has been present in
Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-
ldap.
When the login service fails, did you obtain the logs for it to see why
it failed?
More than likely this is a systemd change, but it's unclear yet.
Almost certainly the issue is that login.service is not waiting for
networking before starting, when ldap is configured.
In the screenshot, I see "Failed to start Login Service" and then later
"Started to raise network interfaces".
--
You received this bug notification because you are a member
If you are dropped to an emergency shell on failure to boot, does name
resolution period work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap
Finally, is this reproducible with 17.04? Note that 16.10 goes eol in
about 3 months so there is some non-zero cost to trying to fix it there,
if it's already fixed in 16.10.
** Changed in: libpam-ldap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
I would subscribe ~ubuntu-archive to this and ask for some AA help if
there is going to need to be done in a side PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646954
Title:
Sync to Debian
For what it's worth, the same version of libpam-ldap has been present in
Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-
ldap.
When the login service fails, did you obtain the logs for it to see why
it failed?
More than likely this is a systemd change, but it's unclear yet.
I followed the same path and dist-upgraded all the way to yakkety and
saw no errors with the package in proposed. I'm not sure, though, if
that really qualifies as a v-d-y, given that I didn't reproduce the
original issue in that path.
# apt policy libsane libsane-common
libsane:
Installed:
I setup a Trusty LXD, installed libsane and libsane-common and then
manually updated source.list with the xenial repositories, including
xenial-proposed. I then did `sudo apt-get update; sudo apt-get dist-
upgrade` and the upgrade completed successfully (no error) with the
following versions of
# ebtables-restore < txt1.txt
Bad table name 'filter'.
# ebtables -t filter -L
Bridge table: filter
Bridge chain: INPUT, entries: 0, policy: ACCEPT
Bridge chain: FORWARD, entries: 0, policy: ACCEPT
Bridge chain: OUTPUT, entries: 0, policy: ACCEPT
So i think this is a bug, probably upstream?
# ebtables-restore < txt1.txt
Bad table name 'filter'.
# ebtables -t filter -L
Bridge table: filter
Bridge chain: INPUT, entries: 0, policy: ACCEPT
Bridge chain: FORWARD, entries: 0, policy: ACCEPT
Bridge chain: OUTPUT, entries: 0, policy: ACCEPT
So i think this is a bug, probably upstream?
** Also affects: ebtables (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ebtables (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: ebtables (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug
** Also affects: ebtables (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ebtables (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: ebtables (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug
Lukas, thank you for the detailed information. However
On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while
Lukas, thank you for the detailed information. However
On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while
@Paul, because I didn't think of that at the time :) Sorry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662027
Title:
cacti vs PHP 7 vs split
To manage notifications about this bug go to:
Hi Clayton, sorry for the long delay on my part!
I think at this point, we need to ask upstream open-iscsi
(https://github.com/open-iscsi/open-iscsi/issues) about possible bugs in
their code.
They probably will ask you be running directly from github's sources
(rather than the package) -- are
Hi Clayton, sorry for the long delay on my part!
I think at this point, we need to ask upstream open-iscsi
(https://github.com/open-iscsi/open-iscsi/issues) about possible bugs in
their code.
They probably will ask you be running directly from github's sources
(rather than the package) -- are
https://anonscm.debian.org/cgit/resolvconf/resolvconf.git/commit/?id=05a25d1d831ebe3955fb9641a3ba708bca68d35a
1.80 isn't out yet, so we should probably just backport the fix to the
affected releases.
** Also affects: resolvconf (Ubuntu Zesty)
Importance: High
Status: Confirmed
** Also
I'm uploading the fix for x, y and z now. We can sync in aa once it's
open.
** Description changed:
+ [Impact]
+
+ * If the administrator configures cacti to poll data at a higher frequency
+ than the cron job that runs the poller, a fatal error is emitted.
+
+ * As the highest cron
ies)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662027
Title:
cacti vs PHP 7 vs split
To manage notifications about this bug go to:
) => Nish Aravamudan (nacc)
** Changed in: cacti (Ubuntu Yakkety)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: cacti (Ubuntu Zesty)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I will upload the same fix to Ubuntu tonight or tomorrow. Thanks Paul!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662027
Title:
cacti vs PHP 7 vs split
To manage notifications about this bug
On Wed, Apr 12, 2017 at 12:49 PM, Brian Murray wrote:
> Part of the problem may be that linux-headers is installed after linux-
> image so there are no headers when the dkms kernel postinst script is
> run. From /var/log/dist-upgrade/apt-term.log:
But shouldn't the last line:
@Paul: I was asking mostly because the upstream changes don't
necessarily apply cleanly (the whole commit) because there seems to have
been a global move to microtime() in the source. Is that something I
should look at SRUing with this change? Or is it sufficient, in your
opinion, to just backport
Is it possible to get the logs from when you do run `apt install
--reinstall nvidia-375` ? I'm trying to figure out what is missing from
the logs of the upgrade / why it behaves differently on reinstall.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Robie, I would suggest this testcase, but it's so contrived, I'm
not sure it's going to be reasonable to test:
Run Munin; get into a situaation where the rrd data is older than the
graph period in Munin (e.g., some communication error to the Munin node)
and Munin will throw an error.
But
Thanks Robie, I would suggest this testcase, but it's so contrived, I'm
not sure it's going to be reasonable to test:
Run Munin; get into a situaation where the rrd data is older than the
graph period in Munin (e.g., some communication error to the Munin node)
and Munin will throw an error.
But
** Also affects: postfixadmin (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: postfixadmin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: postfixadmin (Ubuntu)
Status: In Progress => Fix Released
** Changed in: postfixadmin (Ubuntu
Great Michael! If you need any help, feel free to ping me on IRC -- I
can also help sponsor your fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321955
Title:
postfixadmin dependencies not
As to mariadb, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794
is the Debian bug, and was fixed in 2.93-1, which is in 16.10 and on.
I would suggest, I think, for clarity's sake (and to make the SRU easier
to verify) that a second bug be opened which will have tasks for 14.04
and 16.04
Specifically, 2.3.7-1ubuntu1 on 16.04 has:
Recommends: postfix-mysql | postfix-pgsql, mysql-server | postgresql,
Or are you fixing the mariadb part specifically?
** Bug watch added: Debian Bug tracker #778794
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778794
--
You received this bug
I'm a bit confused. But this appears to be fixed in Xenial and onwards
via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699602.
** Bug watch added: Debian Bug tracker #699602
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699602
** Also affects: postfixadmin (Ubuntu Trusty)
@Paul,
I do see at least 6b5931130770cdfa5baa68c43a913dcabf1c3970 upstream that
fixes the split() calls in question. Is it suitable to just make those
changes in the versions in Ubuntu. Specifically:
--- cacti-0.8.8f+ds1.orig/poller.php
+++ cacti-0.8.8f+ds1/poller.php
@@ -451,11 +451,9 @@ while
** Also affects: cacti (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cacti (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cacti (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because
Hi Paul,
https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.
It takes at least 7 days in -proposed before the SRU team will release
it.
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Hi Paul,
https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.
It takes at least 7 days in -proposed before the SRU team will release
it.
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Alberto,
why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.
** Changed in: samba (Ubuntu)
@Alberto,
why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.
** Changed in: samba (Ubuntu)
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680956
Title:
Fail to launch an OpenStack Instance with hugepages on top
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
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/1680956
Title:
Fail to launch an OpenStack Instance with
*** This bug is a duplicate of bug 1646739 ***
https://bugs.launchpad.net/bugs/1646739
Hello and thank you for filing this bug report.
For now, please use the command-line (`apt update; apt full-upgrade`) as
a workaround. This is an issue with update-manager across many packages
but is not
*** This bug is a duplicate of bug 1646739 ***
https://bugs.launchpad.net/bugs/1646739
Hello and thank you for filing this bug report.
For now, please use the command-line (`apt update; apt full-upgrade`) as
a workaround. This is an issue with update-manager across many packages
but is not
FWIW, this bug is never going to be fixed in Wily, afaict, I'm deleting
the task.
** No longer affects: libvirt (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1524737
FWIW, this bug is never going to be fixed in Wily, afaict, I'm deleting
the task.
** No longer affects: libvirt (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524737
Title:
systemd
Vasya,
Given Christian's great testing, this might be something we need to
inform upstream PHP about. Could you file a bug? It seems like it has
been fixed/worked around in 7.1.x, but not in 7.0.x -- could be
something they backport if we notify them it's an issue.
-Nish
--
You received this
Vasya,
Given Christian's great testing, this might be something we need to
inform upstream PHP about. Could you file a bug? It seems like it has
been fixed/worked around in 7.1.x, but not in 7.0.x -- could be
something they backport if we notify them it's an issue.
-Nish
--
You received this
Hello Simon,
Please don't just change the flag values, but provide some indication
of what version was tested and what the test was.
2) of https://lists.ubuntu.com/archives/ubuntu-
devel/2017-March/039745.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: network-manager-strongswan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: network-manager-strongswan (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Haw,
I have sponsored the uploads for SRU, with the following change:
Xenial => 1.2.6p12-1ubuntu0.1 -> 1.2.16p12-1ubuntu0.16.04.1
and uploaded the same for Yakkety:
Yakkety => 1.2.6p12-1ubuntu0.1 -> 1.2.16p12-1ubuntu0.16.10.1
--
You received this bug notification because you are a member of
** Changed in: check-mk (Ubuntu Zesty)
Assignee: Haw Loeung (hloeung) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372284
Title:
nagios3 + livestatus: SIGSEGV everyday at
** Changed in: check-mk (Ubuntu Trusty)
Status: New => Triaged
** Changed in: check-mk (Ubuntu Xenial)
Status: New => Triaged
** Changed in: check-mk (Ubuntu Yakkety)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: check-mk (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: check-mk (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: check-mk (Ubuntu Zesty)
Importance: Medium
Assignee: Haw Loeung (hloeung)
Status: In
Thanks for that fix. However, can you please provide debdiffs in this
bug as well for sponsoring purposes? Couple of other nits:
I took a look at the PPA's generated debdiffs and saw that (at least)
the xenial one incorrectly indicates in debian/changelog that 1.2.6p12-1
is from xenial, when it
Haw,
1.2.6p12-1haw1
1.2.2p3-1haw1
are not appropriate versions for the archive. Please follow the
versioning recommendations at:
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
-Nish
On Fri, Mar 31, 2017 at 8:46 PM, Haw Loeung <1372...@bugs.launchpad.net> wrote:
>
On Mon, Apr 3, 2017 at 5:03 AM, Jörg Hänsel <1671...@bugs.launchpad.net> wrote:
> Can I do anything else to help to get the fixed package released?
As of right now, no. It's sitting in the unapproved queue waiting for
an SRU team member to process it:
On Mon, Apr 3, 2017 at 5:03 AM, Jörg Hänsel <1671...@bugs.launchpad.net> wrote:
> Can I do anything else to help to get the fixed package released?
As of right now, no. It's sitting in the unapproved queue waiting for
an SRU team member to process it:
On Fri, Mar 31, 2017 at 1:17 PM, Matt Schulte
<1615...@bugs.launchpad.net> wrote:
> Wait I'm confused, build what in a PPA? Didn't you just want us to run
> Debian and test what the version of open-iscsi it comes with?
Oh, you're a power user :) I assumed it would be easier for me to
build an
On Fri, Mar 31, 2017 at 1:17 PM, Matt Schulte
<1615...@bugs.launchpad.net> wrote:
> Wait I'm confused, build what in a PPA? Didn't you just want us to run
> Debian and test what the version of open-iscsi it comes with?
Oh, you're a power user :) I assumed it would be easier for me to
build an
Hi Matt,
I'll build it for you in a PPA.
-Nish
On Fri, Mar 31, 2017 at 10:45 AM, Matt Schulte
<1615...@bugs.launchpad.net> wrote:
> Sure, we can give Debian a shot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
Hi Matt,
I'll build it for you in a PPA.
-Nish
On Fri, Mar 31, 2017 at 10:45 AM, Matt Schulte
<1615...@bugs.launchpad.net> wrote:
> Sure, we can give Debian a shot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
** Tags removed: verification-needed yakkety
** Tags added: verification-done-yakkety verification-needed-xenial
--
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/1639776
Title:
dnsmasq
** Tags removed: verification-needed yakkety
** Tags added: verification-done-yakkety verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send
On 31.03.2017 [12:27:03 -], Franco Runza wrote:
> Nish : This machine runs exclusively Ubuntu 16,04 LTS , I have another one
> with ubuntu ( a former version of 13,04, which doesn't update any more )
> and Windows 7 Home premium . Please remember I am *not* a bit carver . If
> you want me to
On 31.03.2017 [12:27:03 -], Franco Runza wrote:
> Nish : This machine runs exclusively Ubuntu 16,04 LTS , I have another one
> with ubuntu ( a former version of 13,04, which doesn't update any more )
> and Windows 7 Home premium . Please remember I am *not* a bit carver . If
> you want me to
Note that even with this fix, end users if they use their own image based off
an instance that used a cloud image to start will probably trigger:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1677726.
I am thinking we should revisit the overall design a bit and ensure that
behavior
I have sponsored the change, although it needed some retooling to be
DEP3 compliant. I am attaching the debdiff I generated.
** Patch added: "asterisk.debdiff"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1671767/+attachment/4850924/+files/asterisk.debdiff
** Changed in: asterisk
I have sponsored the change, although it needed some retooling to be
DEP3 compliant. I am attaching the debdiff I generated.
** Patch added: "asterisk.debdiff"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1671767/+attachment/4850924/+files/asterisk.debdiff
** Changed in: asterisk
** Changed in: asterisk (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/1671767
Title:
asterisk crashes dialing h264 video sip device
** Changed in: asterisk (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671767
Title:
asterisk crashes dialing h264 video sip device
To manage
Public bug reported:
After fixing LP: #1444992, smoser pointed out that there is still a gap
if a cloud-image is booted and then the once-run instance is used as a
template for future instances, as the iSCSI initiator name has been
generated.
>From IRC:
11:35 < smoser> nacc, there is
** Also affects: asterisk (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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/1671767
Title:
asterisk crashes dialing h264 video
** Also affects: asterisk (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671767
Title:
asterisk crashes dialing h264 video sip device
To
On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish. My thoughts:
>
> 1.a sounds good
Ack.
> 1.b i'd like another way to do that, but not sure what a better way would
> be.
Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:
On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish. My thoughts:
>
> 1.a sounds good
Ack.
> 1.b i'd like another way to do that, but not sure what a better way would
> be.
Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:
I'm unsubscribing sponsors for now, as the patch attachment does not
have a valid version for uploading to the archive and seems to also be
needed for Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
901 - 1000 of 3522 matches
Mail list logo