** Tags removed: bitesize
** Tags removed: server-next
--
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/1275495
Title:
check_radius missing
To manage notifications about this bug go
@unit193: http://people.canonical.com/~ubuntu-archive/component-
mismatches-proposed indicates a MIR is needed for python-future with
this upload.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to parsedatetime in Ubuntu.
@racb, @lars-tangvald:
I think I have set the various tasks correctly now. But I'm not sure if
anyone has verified if the issue is present in Trusty (older versions of
the MySQL packages) or in MariaDB's packaging.
** Also affects: mysql-5.5 (Ubuntu Trusty)
Importance: Undecided
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: New => Invalid
** Changed in: mariadb-10.0 (Ubuntu)
Status: New => Invalid
** Also affects: mariadb-10.1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
I believe the 4 remaining tasks are now confirmed (my check was looking
at the source package to see if the apport hook existed, and if it does
whether it had the same fix as src:mysql-5.7 to filter the logs (they
all filter the conf files already)).
--
You received this bug notification because
mysql-5.5, mysql-5.6, mariadb-5.5 are all not in 16.04.
** No longer affects: mysql-5.6 (Ubuntu Xenial)
** No longer affects: mysql-5.5 (Ubuntu Xenial)
** No longer affects: mariadb-5.5 (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: mariadb-10.0 (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: mariadb-10.1 (Ubuntu)
Status: New => Confirmed
** Changed in: mysql-5.5 (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Status: New => Confirmed
Hello, 15.10 has gone EOL, and src:mysql-5.6 has been replaced with
src:mysql-5.7 in 16.04. Are you able to reproduce this issue with a
current, supported release of Ubuntu?
** Changed in: mysql-5.6 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because
Hello, 15.10 has gone EOL now. mysql-5.6 has also been removed (in
16.04) in favor of mysql-5.7. Are you able to reproduce this with a
current, supported release?
** Changed in: mysql-5.6 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Hello and thank you for filing this bug report. Unfortunately, 15.04 has
gone EOL and src:mysql-5.6 has been replaced src:mysql-5.7 in 16.04. Are
you able to reproduce this with a current release and packages.
** Changed in: mysql-5.6 (Ubuntu)
Status: Confirmed => Incomplete
--
You
I think the issues mentioned by Lars in c#2 are partially fixed.
mysql-5.5 in trusty has the mysqld_get_param function. But the newlines
in the postinst alter statements is still missing (the version of mysql
in 16.04+ does not have these lines).
** Changed in: mysql-5.5 (Ubuntu)
Status:
** Also affects: mysql-5.5 (Ubuntu Trusty)
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/1210380
Title:
package mysql-server-5.5
Hello, Precise is EOL and we are no longer providing bug-fixes to it. It
would appear this particular issue is fixed in Trusty (the only current
release it is present) -- In Bug 1629644, it was determined this version
did not regress Trusty (a different upload did), and it has since
expired due to
Also, I'm not sure what this bug is driving towards -- do you want these
values to be derived automatically?
--
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/1467989
Title:
Boot issues
@mauricfo: is this fix upstream? Where, if so?
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Tags added: upstream-report-needed
--
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/1583705
Title:
unmatched entries for postfix
To manage notifications about this bug go to:
@rackspace.matt: Are you able to test either 16.04.2 or (even better) in
17.04 to see if it also happens there? Just lets us narrow down whether
the bug is already fixed upstream/in the package version there (0.6.4 is
the upstream version).
--
You received this bug notification because you are a
Hello and thank you for reporting this bug! Changing default values is a
scary proposition (to me), because we have to think about every possible
environment.
What are the implications of failback=immediate over failback=manual?
Also, the base configuration for multipath "works" for all cases (I
The upstream fix is
https://anonscm.debian.org/cgit/logcheck/logcheck.git/commit/?id=bacf43b2b706b8f91ffc34d8c983c8d7c4f3efe6
Based upon duping other bugs here, tracking where that might need
backporting.
** Also affects: logcheck (Ubuntu Xenial)
Importance: Undecided
Status: New
**
** Changed in: multipath-tools (Ubuntu)
Status: Triaged => Confirmed
--
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/1627768
Title:
multipath silently crashes with general
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1058760
Title:
unmatched entries for dovecot login
To manage notifications about this bug go
*** This bug is a duplicate of bug 1357880 ***
https://bugs.launchpad.net/bugs/1357880
This was fixed upstream/Debian/Ubuntu via Bug #1357880 -- so I'm duping
this over there and adding tasks there for SRU'ing the fix back.
** This bug has been marked a duplicate of bug 1357880
Thank you everyone for filing bug reports for this issue. Now that 12.04
has gone EOL without a resolution for this, is it possible to re-test
with 14.04 or 16.04 (or ideally 17.10 daily) to see if it still occurs?
This helps us track where it is occurring and decide if it has been
fixed upstream.
As far as I can tell, nothing from couriertls: connect is actually
logwatch'd upstream.
I believe the original bug report's entry is unmatched because it is not
under:
# ESMTP, including all delivery
elsif ( $service =~
** Also affects: celery (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1690688
Title:
kombu in artful-proposed incompatible with
** Also affects: net-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: net-tools (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
** Also affects: samba (Ubuntu Trusty)
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/820679
Title:
nmbd and smbd will not be started again
Hello and thank you for filing this bug report. I believe in this case,
it makes sense to request this of Debian. Can you file a Debian bug?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Hello and thank you for filing this bug report!
As mentioned in the description, it would appear you have deleted two
necessary configuration files from the libapache2-mod-php7.0 package:
/etc/apache2/mods-available/php7.0.conf
/etc/apache2/mods-available/php7.0.load
Public bug reported:
src:nagios3 has been removed from Debian stretch and unstable due to
CVEs and no activity upstream (moved to nagios4, as well).
icinga2 is an alternative that is available and active/current.
There are three reverse-depends of nagios3:
* ganglia-nagios-bridge (for
On Jun 14, 2017 17:22, "Lithi" wrote:
Just a note on how to stop the error messages from occurring every time
the cron script runs:
$ cd /usr/lib/x86_64-linux-gnu/
$ sudo ln -s libzip.so.5.0.0 libzip.so.4
Do not do this. You are telling the loader that your libzip is
On Jun 14, 2017 18:02, "Keen Mouse" <1697...@bugs.launchpad.net> wrote:
$ apt policy libzip4
libzip4:
Installed: 1.2.0-0neon+16.04+xenial+build2
Candidate: 1.2.0-0neon+16.04+xenial+build2
Version table:
*** 1.2.0-0neon+16.04+xenial+build2 500
500
@lithi, so it seems you are also using Neon, which is not Ubuntu. Please
follow up with them on their (rather glaring) mistake.
--
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/1697832
Fixed in celery 4.0.2-0ubuntu1.
** Changed in: kombu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1690688
Title:
kombu in
Fixed in kombu 4.0.2+really4.0.2+dfsg-2ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1690688
Title:
kombu in artful-proposed incompatible with celery in artful
To manage
** Changed in: celery (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
https://bugs.launchpad.net/bugs/1690688
Title:
kombu in artful-proposed incompatible with
billiard and celery are uploaded, but I forgot to mention this bug in
the celery changelog. In any case, the celery tests pass during the
build, and I'm retriggering with kombu & billiard from a-p to see if the
DEP8 tests will also pass (they pass locally).
** No longer affects: sphinx-celery
** Changed in: billiard (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: celery (Ubuntu)
Status: In Progress => Fix Committed
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Hello and thank you for filing this bug report.
On 14.06.2017 [04:14:34 -], Lithi wrote:
> Public bug reported:
>
> $ ldd -v /usr/lib/php/20151012/zip.so
> linux-vdso.so.1 => (0x7fffe33ea000)
> libzip.so.4 => not found
On 16.04, in a fully updated LXD container:
# ldd
On 14.06.2017 [21:27:25 -], Keen Mouse wrote:
> I have this issue on KDE Neon 16.04.
>
> $ ldd -v /usr/lib/php/20151012/zip.so
> linux-vdso.so.1 => (0x7fff225db000)
> libzip.so.4 => not found
>
> $ locate libzip.so.5
> /usr/lib/x86_64-linux-gnu/libzip.so.5
>
@stafox, thank you for confirming. If anyone is able to reproduce this
with actual Ubuntu (not any PPAs, not NEON), please mark this bug as
New.
** Changed in: php7.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
Hello, and thank you for filing this bug report.
Did you make any changes to /etc/default/tomcat8 after installing it on
2017-06-13?
The uninstall path is unable to parse your /etc/default/tomcat8 file at
line 49.
** Changed in: tomcat8 (Ubuntu)
Status: New => Incomplete
--
You
I'm testing a new change locally which doesn't need any changes to
sphinx-celery. (the docs are what use sphinx, and require python3 to
build).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to celery in Ubuntu.
celery debdiff updating to 4.0.2.
** Patch added: "celery_3.1.23-7_4.0.0-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sphinx-celery/+bug/1690688/+attachment/4894892/+files/celery_3.1.23-7_4.0.0-0ubuntu1.debdiff
--
You received this bug notification because you are a member of
Attaching some debdiffs. With these, both billiard and celery build
successfully (which for celery also means passing their tests). But
upstream celery has deprecated a bunch of commands, so I'm holding off
on uploading today.
--
You received this bug notification because you are a member of
Public bug reported:
Availability: src:nghttp2 is in artful/universe and builds binary
packages for all available architectures.
Rationale: In order to enable apache2's support for HTTP/2,
libnghttp2-14 must be in main (libnghttp2-dev is added as a b-d for
src:apache2, but it can remain in
Thanks for the quick response! I will try to spin up a VM and verify
that.
** Changed in: postfix (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
I am uploading the http2-enabled apache2 to a-p, but will need to
process the MIR for nghttp2.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Hello and thank you for filing this bug report!
Did you manually change /var/log from 775 to 755? In a fresh cloud image
(lxd), I see /var/log has 775 permissions:
drwxrwxr-x 6 root syslog 4.0K May 1 16:16 log
Thanks,
Nish
** Changed in: postfix (Ubuntu)
Status: New => Incomplete
--
** Summary changed:
- Merge python-django 1:1.10.3 from Debian unstable
+ Merge python-django 1:1.11-1 from Debian unstable
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
ves of
- source-is-missing.
- * Cleanup debian/copyright for dropped/renamed files.
- * Run tests for all supported Python versions.
-
- -- Raphaël Hertzog <hert...@debian.org> Wed, 25 Nov 2015 16:16:10
- +0100
+ -- Nishanth Aravamudan <nish.aravamu...@canonical.com> Fri
Set up LXD containers of 16.10 and 17.04. Ran the testcase in the
description with the actual and expected results before/after the
upgrade to the proposed versions. Testcase passes with the following
versions:
16.10:
# apt policy php7.0-cli
php7.0-cli:
Installed: 7.0.18-0ubuntu0.16.10.1
Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Ser
On 08.05.2017 [11:25:03 -], Balint Reczey wrote:
> >> 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:
> >
> > 999-cpc-fixes.chroot:
> > ##
Public bug reported:
ocfs2-tools (1.8.4-4ubuntu1) artful; urgency=medium
* Merge with Debian unstable. Remaining changes:
- d/t/basic: do not assume local filesystem blocksize will support
the mkfs.ocfs2 blocksize (e.g., 4k disks will not support a 1k
blocksize).
* Drop:
Tested, as per usual, by installing php in a LXD 17.04 and 16.10
container and then upgrading to the versions in -proposed. Everything
went smoothly:
16.10:
# apt policy php7.0
php7.0:
Installed: 7.0.18-0ubuntu0.16.10.1
Candidate: 7.0.18-0ubuntu0.16.10.1
Version table:
***
Public bug reported:
To be entered
** Affects: openipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1688411
Title:
** Changed in: php7.1 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: php-defaults (Ubuntu)
Status: In Progress => Fix Released
** Changed in: php-defaults (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
** Changed in: php7.1 (Ubuntu)
ffects: unbound (Ubuntu)
Importance: Undecided
Assignee: Nish Aravamudan (nacc)
Status: In Progress
** Changed in: unbound (Ubuntu)
Status: New => In Progress
** Changed in: unbound (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Descrip
** Changed in: php7.0 (Ubuntu)
Status: Confirmed => Won't Fix
** 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.
** Changed in: lvm2 (Ubuntu)
Status: In Progress => Fix Committed
--
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/1576341
Title:
systemd in degraded state on startup in LXD
Hello and thank you for reporting this bug.
Do you still get any errors if you run:
sudo apt update
sudo apt -f install
sudo apt full-upgrade
If you do, can you attach the output to this bug?
'atd' claims:
Setting up at (3.1.18-2ubuntu1) ...
Failed to connect to bus: Connection refused
Failed
Hello and thank you for reporting this bug.
What exactly is the use case / why do you need networking for your
database to start?
The MongoDB service is for the mongodb server, as far as I can tell,
which is for serving databases. By default that is done locally. If you
need to server your
Hello and thank you for reporting this issue!
Vorbereitung zum Entpacken von .../138-php7.1-common_7.1.5-1ubuntu1_amd64.deb
...
/var/lib/dpkg/tmp.ci/preinst: 52: /var/lib/dpkg/tmp.ci/preinst: Cannot fork
dpkg: Fehler beim Bearbeiten des Archivs
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1693944
Title:
package openssh-server 1:7.2p2-4ubuntu2.2 failed to
Hello and thank you for filing this bug report. It appears you installed
a non-ubuntu version of MySQL at some point:
Selezionato il pacchetto mysql-server-5.7 non precedentemente selezionato.
Preparativi per estrarre
.../mysql-server-5.7_5.7.18-0ubuntu0.17.04.1_i386.deb...
Aborting downgrade
Status: New => Triaged
** Tags added: bitesize
** Changed in: imapfilter (Ubuntu Xenial)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: imapfilter (Ubuntu Yakkety)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notifi
** Summary changed:
- mod_http2 is not available under Apache 2.4.23 / Ubuntu 17.04 xenial
+ mod_http2 is not available in Apache
** Summary changed:
- mod_http2 is not available in Apache
+ [FFe] mod_http2 is not available in Apache
** Description changed:
+ Feature Freeze justification
Sponsored.
--
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/1715012
Title:
Installing snapd can hide dpkg prompts and make it look like it's
stuck
To manage
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:
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?
--
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
*** This bug is a duplicate of bug 1662654 ***
https://bugs.launchpad.net/bugs/1662654
If you would like to help fix dogtag upstream, we can let tomcat8 sync.
Debian chose to break those packages instead.
** This bug has been marked a duplicate of bug 1662654
Please remove resteasy
We are in discussions to do this for 18.04 (with a transition to icinga2
everywhere). But it will need MIRs, etc.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
https://bugs.launchpad.net/bugs/1696252
Title:
Andreas, can you document your conclusion from IRC in the bug when
unassigning yourself?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1712179
Title:
Please merge libnss-ldap
** Changed in: python-django (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
https://bugs.launchpad.net/bugs/1605278
Title:
Merge python-django
And
https://github.com/squid-cache/squid/commit/85942de8e7b4f8a449d933657fc4a5324a4c5d58
for 3.5.27 and in the v3.5 branch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1712668
Fixed upstream with:
https://github.com/squid-cache/squid/commit/39cca4e121215f3f994c1e57f7201ad2a2a2d32a
?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1712668
Title:
squid3:
*** This bug is a duplicate of bug 1662654 ***
https://bugs.launchpad.net/bugs/1662654
Hello Ross, thanks for filing this request.
https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1662654
documents the necessary steps to get tomcat8.5 into the archive. Note
it's still irrelevant (and
** 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)
@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:
@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
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,
@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
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
@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.
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
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
@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
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
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
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
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
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
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
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
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
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),
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.
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
401 - 500 of 576 matches
Mail list logo