Alain,
I'm trying to help, and I'm sorry that you feel that I'm snubbing users.
I'm happy to take feedback on what I should be doing instead. Please can
you explain how you think I've snubbed users here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Same problem here.
Works fine with 1.9.0+svn250-3
Broken with 1.9.0+svn250-5 (Package for vivid, installed on a trusty)
Btw, Robie, if you snub one user, in reality you also snub hundreds of others
who find his bug report by googling for the same symptoms, so please be a bit
more helpful. It
Found it.
Actually it was due to both a pecularity in the proxy server I wanted to
get through, and a bug in how proxytunnel sets SNI.
It seems that our proxy server ignores SNI in SSLv3, but considers it in
TLSv1.
And proxytunnel sets the wrong SNI.
proxytunnel ---> proxy1 (the one I want to
** Branch linked: lp:ubuntu/vivid-proposed/juju-core
--
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/1497087
Title:
updates from trusty to vivid will fail when juju-core is
** Branch linked: lp:ubuntu/vivid-proposed/juju-core
--
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/1500916
Title:
[needs-packaging] 1.24.6 is not packaged in Vivid
To manage
@brian-murray, it appears this was not released into trusty-updates as
mentioned above:
root@myserver:~$ apt-cache policy python-txtftp
python-txtftp:
Installed: 0.1~bzr38-0ubuntu4~14.04.1
Candidate: 0.1~bzr38-0ubuntu4~14.04.1
Version table:
*** 0.1~bzr38-0ubuntu4~14.04.1 0
500
** Changed in: bind9 (Ubuntu)
Importance: Undecided => Medium
--
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/1500683
Title:
By default DNSSEC is enabled with automatic keys
To
** Summary changed:
- update to 5.6.20 for security fixes
+ update to 5.6.20 or above for security fixes
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1500684
Title:
update to
** Changed in: libapache2-mod-perl2 (Debian)
Status: Unknown => 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/898124
Title:
Missing Files for Apache2::SizeLimit
Public bug reported:
Hello!
I would like to update my BIND configuration from the command line, but I just
get the error:
/usr/bin/nsupdate -k /etc/bind/Kupdate_key.+157+10019.private
> update add new.domain 300 A 1.2.3.4
> send
; TSIG error with server: expected a TSIG or SIG(0)
update failed:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is a fair point. But the problem is effectively fixed in the latest
release of Ubuntu where only mysql 5.6 is available. I don't expect
we'll be doing a release with two versions concurrently again. I also
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Public bug reported:
Use-case: You are just starting with Charm Layers, made some layers
locally (in JUJU_REPOSITORY/layers) referenced them with layer:mylayer
and generate the Charm. COMPOSER_PATH is unset
What I expect: Charm compose throws an error saying "I couldn't find the
layer remotely
You have been subscribed to a public bug by Robie Basak (racb):
If I am running snmpd (which I was) and I install snmp (which I did), it
kills snmpd due to a pre-install step of the snmp package that calls a
'killall -u snmp' :(
Found the pre-install step here:
user@host3:~$ cat
Public bug reported:
Use-case: You have a "normal" Charm and you start porting it to
composer. You copy the charm from /trusty/mycharm to /layers/mycharm.
You start splitting the charm in layers and run `charm generate mycharm`
Expected result: You get an error explaining that the Charm
** Changed in: net-snmp (Ubuntu)
Status: Confirmed => Triaged
** Changed in: net-snmp (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=103401
Importance: Unknown
Status: Unknown
** Summary changed:
- cups: 127.0.0.1:631 - Address already in use.
+ rpcbind grabs ports used by other daemons such as cupsd
--
You received this bug notification
hey. saw this in my inbox, and very happy! thank you for working on
this.
one note, in update-notifier-3.164/data/update-motd-updates-available
+trap cleanup EXIT
+tmpfile=$(mktemp)
if tmpfile was set in the environment prior to this program running, and
you exited for some reason
** Changed in: tomcat7 (Ubuntu)
Assignee: (unassigned) => Alex Kiss (sysrex)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1400517
Title:
Please update Tomcat7 in
Public bug reported:
Incomplete shutdown
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: psmisc 22.21-2build1
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Wed Oct 7 19:24:29
the package built and passes the tests on all architectures.
** 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 python-greenlet in Ubuntu.
** Changed in: net-snmp (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
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/1245604
Title:
"killall -u snmp" in a
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
While there is a newer libecap in -proposed (1.0), the current squid3
version is under the 3.3 series, which can only be build with libecap
0.20.
In order to use the libecap in version available in proposed we would
need to update squid to 3.5, so while that does not happen it would be
good to
* GCC5 transition (LP: #1504200)
- d/control: rename libecap2 to libecap2v5
- d/rules: call dh_clean to remove *.debhelper.log files
- d/libecap2v5.symbols: update symbols
** Patch added: "libecap_0.2.0-1ubuntu6.debdiff"
Public bug reported:
Currently libecap2 FTBFS on a rebuild with a few symbol changes due to
gcc5 transition.
rebuild FTBFS: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test
/test-rebuild-20151001-wily.html#ubuntu-server
Log from
After applying the patch there are still test failures. The first two
(in tests/test_41_response.py) can be fixed by:
https://github.com/rohe/pysaml2/commit/ee3d828f80ff18082f89e219e0b48faf0dab45ca
The final failure needs to be fixed manually. The test_eptid_mongo_db
test from
2.4.7-1ubuntu4.7 fixes my problem.
--
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/1445914
Title:
Secure web socket proxy does not work in Apache 2.4.7
To manage notifications about
Ok, prepared a debdiff fixing all FTBFS issues. Almost all the fixes
that are part of distro patches in this version are cherry-picked from
upstream (will contact them about certain aspects of the testing suite).
Debian seems to prepare for switching to a newer python-pysaml2 (3.0.0
in
Public bug reported:
* Built on 14.04 via debuild
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I/target/./src -I..
-I../gnulib/lib -I/target/./gnulib/lib -I../include -I/target/./include
-I/target/./src/util -DIN_LIBVIRT -I/target/./src/conf -I/target/./src/xenxs
-export-dynamic
** Also affects: maas
Importance: Undecided
Status: New
** No longer affects: maas (Ubuntu)
** Changed in: maas
Milestone: None => 1.9.0
** Changed in: maas
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team,
libecap3 has been deleted from -proposed, it is now ok to apply this
fix.
--
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/1504200
Title:
libecap2 FTBFS due to gcc5 transition
To
libecap3 was been deleted. I have created LP: #1504200 to handle the
gcc5 transition. After it gets sponsored it should be ok to apply this
fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
libecap3 was been deleted. I have created LP: #1504200 to handle the
gcc5 transition. After it gets sponsored it should be ok to apply the
squid debdiff.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
Public bug reported:
Attempted to upgrade Trusty from 1.5 to 1.9.
Please see the output below.
jenkins@juju-qa-maas-server-1:~$ sudo apt-get upgrade maas
[sudo] password for jenkins:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating
There's a typo in the changelog. It's "d/control" not "d/rules". I'll
fix that when I sponsor. Other than that, the debdiff looks great and
a local build succeeds. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:~ubuntu-branches/ubuntu/wily/python-pysaml2/wily-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pysaml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1503698
Title:
FTBFS due to broken unit tests
Hello Mike, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
This patch also fixes LP: #1501566 and LP: #1496924.
** Patch added: "squid3_3.3.8-1ubuntu16.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4489239/+files/squid3_3.3.8-1ubuntu16.debdiff
** Patch removed: "fixes for this bug as well as LP: #1501566 and LP:
Hello bugproxy, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Public bug reported:
qemu-slof stage1 crashes when linked with wily's binutils 2.25.1.
stage2.c's TOC string references end up pointing to the wrong place and
it branches to invalid memory.
The breaking bfd change is a27e685 "Align .TOC. for PowerPC64". Aligning
the TOC to 256 bytes rather than
The attachment "debdiff containing the upstream patch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
** Changed in: nova (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1490361
Title:
IncompatibleObjectVersion: Version 1.2 of
Public bug reported:
A bug in the Apache2 HTTP server results in invalid memory references
in the ap_server_config_defines array after a graceful restart. This
can result in server config variables defined by means of the Define
directive appearing to be undefined after a graceful restart. This
** Patch added: "debdiff containing the upstream patch"
https://bugs.launchpad.net/apache2/+bug/1504354/+attachment/4489268/+files/server_config_defines.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Launchpad has imported 4 comments from the remote bug at
https://bz.apache.org/bugzilla/show_bug.cgi?id=57328.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
[Expired for python-oslo.messaging (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: python-oslo.messaging (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug was fixed in the package python-pysaml2 - 2.4.0-0ubuntu2
---
python-pysaml2 (2.4.0-0ubuntu2) wily; urgency=medium
* debian/control:
- Depend on python-pymongo versions 3.0 and higher
* debian/patches/fix-build-against-new-pymongo.patch:
- Cherry-pick fix pysaml2
** Branch linked: lp:ubuntu/wily-proposed/squid3
--
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/1496223
Title:
squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
To
** Branch linked: lp:ubuntu/wily-proposed/squid3
--
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/1496924
Title:
squid3 FTBFS due to bad libecap3 dependency and logical-not-
** Branch linked: lp:~ubuntu-branches/ubuntu/wily/freeipmi/wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838
Title:
ipmi-locate causes synchronous external
54 matches
Mail list logo
