Actually, golang-go.crypto needs a bug subscriber. Marking incomplete.
Once that is done, this can be moved back to Fix Committed.
** Changed in: golang-go.crypto (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server
@doko
"I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute for the binary packages. If juju-core doesn't want, or cannot use
dh-golang, that
Based on Steve's comment in 118, I'm marking golang as Fix Committed.
** Changed in: golang (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
@slangasek: I agree on your point regarding juju-mongodb. It is fine for
support and I filed bug 1506989 for perftools and bug 1506990 for
architectures.
Between that, the security team ACK and doko's review, marking as Fix
Committed.
** Changed in: juju-mongodb (Ubuntu)
Status: New =>
Public bug reported:
MIR bug 1267393 discovered:
mterry:
"Its name is wrong [1]. It should be golang-github-juju-loggo and
golang-github-juju-loggo-dev. We should fix in Ubuntu so that if it's ever
packaged in Debian, we'll be aligned.
[1] http://pkg-go.alioth.debian.org/packaging.html
"
I
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this bug go to:
> Having seen these past issues, and issues with another not well
> maintained language stack in main for the last two years (ruby), I'm
> asking for explicit confirmation that the teams who are supposed to
> maintain golang do have the required resources to do so. This will
> not only include the
** Changed in: audit (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
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/1478087
Title:
Add libaudit support
>From a supportability standpoint, it's actually easier to have the same
upstream version in trusty and wily (given that trusty is supported
longer), so security patches apply identically to both.
Are there any arguments for a late-in-the-release update to 3.3.14 other
than "it's newer"?
If not,
Ok, this is a very complicated MIR with so many comments it is difficult
to track. I went through the bug and came up with the following list of
remaining items. If I missed something, please comment. Hopefully, no
one has to look before this comment on if everything is done. :)
* security team
I see this is assigned to the security team. I already gave our ACK.
Based on doko's comments, marking Incomplete.
** Changed in: juju-mongodb (Ubuntu)
Status: New => Incomplete
** Changed in: juju-mongodb (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
Public bug reported:
This came up as part of the MIR review in bug 1267393. In the interest
of time, I am filing it on their behalf.
doko: "the package should be built for the upcoming s390x architecture
as well."
slangasek: "Yes, it should; the architecture list in debian/control
should just
golang-go-dbus only ships a dev package with source code so does not
need Built-Using (I updated the MIRteam wiki page to calrify this).
Based on mterry's comments, golang-go-dbus is ok.
** Changed in: golang-go-dbus (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug
"- debian/control should have Built-Using: ${misc:Built-Using} on the
golang-github-bmizerany-assert-dev package"
This isn't needed for -dev packages. Marking Fix Committed.
** Changed in: golang-github-bmizerany-assert (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this
golang-go.crypto:
- builds fine on wily and pulls in no new MIR dependencies not listed in this
bug
- has a testsuite that is run as part of the build
- Ubuntu does not carry a delta
- no watch file
- update history in Debian is sporadic
- lintian clean (one override that is ok)
- git snapshot
@mterry,
I agree with doko and slangasek that we should block migration if APIs
fail and I particularly like pitti's comment in 99.
Also, you said: "I get that you're saying it's good because we don't
have to waste security-update-time fixing reverse-depends." The upstream
Go community as a
@doko:
"While not required, it is good to see that shared library support is
being worked on, and targeted for the upcoming 1.6. release." It is only not
required for 15.10, it is a condition of this MIR (that the juju and
foundations teams already agreed to) that we gain shared library support
Public bug reported:
This came up as part of the MIR review in bug 1267393. In the interest
of time, I am filing it on their behalf.
doko: "google-perftools is available on all archs. Is there a need to
disable that for some architectures?"
slangasek: "It's not available on arm64 in trusty, so
** Branch linked: lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1506652
Title:
[needs-packaging] Juju 1.24.7 is not in Ubuntu
To
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ wily-1.24.7/ > ./1.24.7-vivid-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x *.bzr
I apparently forogt to actually attach the config fragment that
reproduces the problem.
** Attachment added: "Configuration fragment for test case"
https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1504354/+attachment/4497261/+files/ifdefine-test.conf
--
You received this bug
apache 2 2.4.7-1ubuntu4.8 (in trusty-proposed) both passes the test case
and fixes my original problem.
** 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 the bug
"* security team commitments: develop a process for the list of packages
to notify the juju team on when there is a security update. This is not
a precondition of this MIR, but a request of the juju team"
FYI, we have this list and have the tooling update in our backlog.
--
You received this
Adam,
That's a good point. None of the reported LP bugs are fixed by this
particular update. That said, the list of bug fixes in this update is
quite high.
I would be willing to SRU this for Trusty as well to keep it in sync.
--
You received this bug notification because you are a member of
$ change-override -c main -S golang-check.v1
Override component to main
golang-check.v1 0.0+git20150729.11d3bc7-1 in wily: universe/devel -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily amd64:
universe/devel/extra/100% -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily
golang promoted.
$ change-override -c main -S golang
Override component to main
golang 2:1.5.1-0ubuntu2 in wily: universe/devel -> main
golang 2:1.5.1-0ubuntu2 in wily amd64: universe/devel/optional/100% -> main
golang 2:1.5.1-0ubuntu2 in wily arm64: universe/devel/optional/100% -> main
golang
Correction:
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ vivid-1.24.7/ >
./1.24.7-vivid-backport.diff
only the changelogs differ.
** Attachment removed:
Vivid deployment succeeded with no issues.
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1499869
** Package changed: systemd (Debian) => docker (Debian)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1497420
Title:
systemd 226 (moving pid 1 into /init.scope cgroup) breaks
You have been subscribed to a public bug by Robie Basak (racb):
# php -r 'var_dump(json_decode("\"\xff\""));'
string(1) "�"
Should be:
# php -r 'var_dump(json_decode("\"\xff\""));'
NULL
Since a large (and growing) number of services use JSON for communication, it's
quite bad.
ProblemType:
Still no updated package in the cloud archive
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1502363
Title:
Linux bridge agent should include ebtables package and rootwrap rule
To
** Summary changed:
- ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3
+ Add libaudit support
--
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/1478087
Title:
Public bug reported:
Every time I use apt-get or synaptic appear this error.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libapache2-mod-php5 (not installed)
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: wl
** Changed in: openvswitch (Ubuntu)
Status: Fix Released => In Progress
** Changed in: openvswitch (Ubuntu)
Importance: Medium => High
** Changed in: openvswitch (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
Public bug reported:
Upgrading openstack-dashboard fails.
2015-10-16 10:34:53 INFO config-changed The following packages have unmet
dependencies:
2015-10-16 10:34:53 INFO config-changed openstack-dashboard-ubuntu-theme :
Depends: openstack-dashboard (= 1:2015.1.1-0ubuntu1~cloud2) but
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1506785
Title:
package libapache2-mod-php5 (not installed) failed to install/upgrade:
subprocess
** Branch linked: lp:ubuntu/wily-proposed/neutron-lbaas
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron-lbaas in Ubuntu.
https://bugs.launchpad.net/bugs/1504367
Title:
Missing neutron-lbaasv2-agent executable in
** Tags removed: verification-needed
** Tags added: verification-done-precise verification-done-trusty
--
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/1073478
Title:
[SRU] Update
Looks like $n_jobs is set correctly upstream and in 2.0.25-1 in Wily, so
this is fixed but could be cherry-picked to Trusty.
Upstream still outputs a COUNTER and not a GAUGE (from
https://github.com/munin-
monitoring/munin/blob/devel/plugins/node.d/lpstat). If you think it
should be changed, then
** Bug watch added: Debian Bug tracker #801962
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801962
** Also affects: php-json (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801962
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Further to the patch you proposed there was a subsequent commit "doveadm
backup: Fix to handling mailbox deletions."
(http://hg.dovecot.org/dovecot-2.2/rev/57a490780b1e) which wipes out the
lines changed. And then a further commit "doveadm backup: Another
attempt at fixing assert-crashes when
Also happens on wily when running
$ qemu-system-arm -machine realview-pb-a8
--
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/1062220
Title:
qemu-system-arm crashed with SIGABRT in
This bug was fixed in the package neutron-lbaas - 2:7.0.0-0ubuntu1
---
neutron-lbaas (2:7.0.0-0ubuntu1) wily; urgency=medium
* New upstream release for OpenStack Liberty.
* d/control: Add neutron-lbaasv2-agent binary (LP: #1504367).
* d/neutron-lbaasv2-agent.in*: Added for
This is for pocket desktop support
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Milestone: None => ww46-2015
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => kevin gunn (kgunn72)
--
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
Proposed fix:
https://git.launchpad.net/~ubuntu-server-
dev/ubuntu/+source/horizon/commit/?id=4e575fa1e782a1b92b35db58cbecee4a74503900
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
golang:
The packaging of the golang package looks reasonable well, it is based
on the the Debian packaging. In Ubuntu the package suffered regular
maintenance up to and beyond the 15.04 release (vivid). It's good to
see another attempt to maintain this package.
While not required, it is good
juju-core:
Others already commented on the code, and finally approved with some
comments.
I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute
** Changed in: php-json (Debian)
Status: Unknown => 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/1287726
Title:
Wrong evaluation whether json is valid or not
To manage
The postrm script does not tidy cleanly, causing stuff to be left around
which results in an error when configuring openstack-dashboard-ubuntu-
theme
** Changed in: horizon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server
The problem is that the old postrm is being called with no
conditionality on the actions it takes; its doing a remove/purge all of
the time, when infact its being called with 'upgrade' which then fails
due to the interim state of files on disk.
I think the right fix is to only perform the steps
golang 1.5 is now built on arm64 and ppc64el, however juju-core is built
using gccgo. Is there a reason for it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
@kgunn72,
depends on what you need. I'm happy to answer any questions, but I
don't think i know enough to drive this.
If all you really need is to have a phablet line in the lxc-usernet file
as shipped in the package, then probably best for @stgraber to add it.
--
You received this bug
** Tags added: ubuntu-sponsors
** Patch added: "lp1506257.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/nova/+bug/1506257/+attachment/4496906/+files/lp1506257.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
juju-mongodb:
packaging bits only, the security team will follow-up with a code
review.
- the packaging is a copy of the mongodb package, however it looks
like the packaging itself isn't merged / updated where needed.
This problem is shared with the mongodb package in Ubuntu.
-
#10: if that's your entire command line then that's expected behaviour,
and is saying "we just executed a pile of zeros and fell off the end of
RAM". You need to supply a kernel to run.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Seems every time I start up my Ubuntu 12.04 machine this process continually
generates the following error in the log files (ad infinitum, until it fills up
the disk)
process 20018: arguments to dbus_message_iter_append_basic() were incorrect,
assertion
juju-mongodb has security team ACK so long as the builds use --disable-
scripting in perpetuity.
I verified the wily version is correctly using --disable-scripting in
debian/rules (if I build without '--disable-scripting', I see
src/third_party/v8 being built and build with --disable-scripting, I
Override component to main
dh-golang 1.12 in wily: universe/misc -> main
dh-golang 1.12 in wily amd64: universe/devel/extra/100% -> main
dh-golang 1.12 in wily arm64: universe/devel/extra/100% -> main
dh-golang 1.12 in wily armhf: universe/devel/extra/100% -> main
dh-golang 1.12 in wily i386:
@serge - ok to put your name as you might be able to help us here ? ping
me on irc if you need
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
chris pointed out that this isn't really needed for pd as we're using a custom
chroot not lxc.
but leaving this open as we'll want this eventually.
** Changed in: canonical-devices-system-image
Importance: High => Medium
** Changed in: lxc (Ubuntu)
Importance: High => Medium
--
You
Looks like the proper syntax for the listen-on named config is either
Just tested on MAAS dns service which fails > 75% of the time when brought up
in a vm due to timing issues.
The proposed "listen-on { ! 10.0.3.1; };" cannot be parsed by bind
because ! is supposed to be outside the
hmm, I should've validated this statement above further on deployments.
I am seeing other errors with bind with the above suggestion. I'll debug
more and present results.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
SRUing to trusty would require a pretty comprehensive test plan and a
justification for the massive upstream delta. It's likely not a
reasonable thing to be suggesting in a stable update.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Think I came to the same bug - took me a lot of time to identify
this. because it mainly made no sense.
My error described here.
http://stackoverflow.com/questions/33121809/mantis-soap-error-accessing-mantisconnect-php-eclipse-mylyn-plugin
For me disabling the wsdl-cache helped..
$ change-override -c main -S juju-mongodb -y
Override component to main
juju-mongodb 2.4.10-0ubuntu4 in wily: universe/database -> main
juju-mongodb 2.4.10-0ubuntu4 in wily amd64: universe/database/optional/100% ->
main
juju-mongodb 2.4.10-0ubuntu4 in wily arm64: universe/database/optional/100%
> * golang-go.crypto
> - needs a bug subscriber
Looks like it's ~ubuntu-server now.
> * golang-gocheck
> - can be dropped when bug #1504821 is fixed (comment #82)
> * golang-goyaml
> - can be dropped when bug #1504821 is fixed (comment #82)
To clarify, I am making these changes on master.
Mike, did you install this system using a version of the installer that
includes the multipath-udeb from trusty-proposed? If not this is not a
valid test of the SRU. Your comment does not establish how you
installed the system, it only shows that you have a curtin-created
/etc/multipath/bindings
Mike, did you install this system using a version of the installer that
includes the multipath-udeb from trusty-proposed? If not this is not a
valid test of the SRU. Your comment does not establish how you installed
the system, it only shows that you have a curtin-created
/etc/multipath/bindings
Ok attempt #2.
Looks like the original clause below didn't match any addresses so I was
getting connection refused messages
listen-on { ! 10.0.3.1; };
What I found worked on my end was specifying a secondary address match
list 'any' which we fall through to match any ipv4 address that is
** Changed in: docker (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1497420
Title:
systemd 226 (moving pid 1 into /init.scope cgroup) breaks
Looks like the release packages arrived...
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-
archive/liberty_versions.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1507082
Title:
package nginx-core 1.6.2-5ubuntu3.1 failed to install/upgrade: サブプロセス
インストール済みの
Public bug reported:
invoke-rc.d: initscript nginx, action "start" failed.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nginx-core 1.6.2-5ubuntu3.1
ProcVersionSignature: Ubuntu 3.19.0-30.34-lowlatency 3.19.8-ckt6
Uname: Linux 3.19.0-30-lowlatency x86_64
NonfreeKernelModules: fglrx
golang-x-text FTBFS due to testsuite failure:
=== RUN TestNumericCompare
--- FAIL: TestNumericCompare (0.02s)
collate_test.go:119: Compare("\U00011730", "0") = 1; want 0
FAIL
FAILgolang.org/x/text/collate/colltab 1.473s
--
You received this bug notification because you are a
"golang-juju-loggo needs some fixes:
- It's missing Built-Using: ${misc:Built-Using}"
You can ignore this, but please do fix the package name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
> golang 1.5 is now built on arm64 and ppc64el, however juju-core
> is built using gccgo. Is there a reason for it?
The reason for this is that the package is being backported directly to
trusty, under the juju Stable Release Exception for SRUs. Since there
is not a compatible version of golang
77 matches
Mail list logo
