Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
- debian/helpers/goenv.sh - this had previously been dropped from the Ubuntu
packaging (superseded by the changes to debian/rules), but is readded in your
version.
- debian/control: Debian's golang package has dependencies on
golang-{doc,go,src} (= ${source:Version}); Debian has
On 15 December 2015 at 14:41, Steve Langasek
wrote:
> - debian/helpers/goenv.sh - this had previously been dropped from the Ubuntu
> packaging (superseded by the changes to debian/rules), but is readded in your
> version.
I think m-o-m is confusing you. The file
Please disable HTTP/2 / SPDY for initial inclusion into Xenial; the
security team would really prefer this code have some more real-world
exposure and fuzzing before we turn it on. We can always turn it on
after release via an SRU later.
Thanks
--
You received this bug notification because you
ACK on Security Team Request.
Notes:
* SPDY is dead as of HTTP/2 module being released - SPDY support is dead as of
1.9.x (so there's no SPDY to disable).
Further discussion on HTTP/2 enablement will need to be done closer to
16.04 release in the Sec Team and otherwise, to discuss when/if
Public bug reported:
As lb and lb listener db entry is deleted before the driver.listener.delete is
completed.
When listener_delete and loadbalancer_delete is triggered repeatedly,
before update_port triggered by listener_delete is finished,
loadbalancer_delete triggers delete_port. And when
The debdiff shows some changes that are not part of the existing diff
between Ubuntu and Debian, e.g. in the 0ubuntu1->4ubuntu1 debdiff:
-Build-Depends: debhelper (>= 7.4.10), bison, ed, mawk | awk, perl, netbase,
- golang (>= 1:1.4~) | gccgo-5
-Build-Depends-Indep: po-debconf
Turns out this isn't quite so simple, but luckily IBM have done the work
for us (see https://github.com/linux-on-ibm-z/docs/wiki/Building-
MongoDB-2.4-and-2.6). Attaching debdiff.
** Patch added: "juju-mongodb_2.4.10-0ubuntu4_2.4.10-0ubuntu5.diff"
I've built an only trivially different version of the package in a ppa:
https://launchpad.net/~mwhudson/+archive/ubuntu/juju-mongodb-
s390x/+packages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
Thanks Robie. I think you may have misunderstood what the bug is. The
quote you reference is not really relevant in this case, because what I
am reporting isn't that something goes wrong when a port is not
specified.
The important line from the documentation is this, which I provided
On 15 December 2015 at 14:29, Steve Langasek
wrote:
> The debdiff shows some changes that are not part of the existing diff
> between Ubuntu and Debian, e.g. in the 0ubuntu1->4ubuntu1 debdiff:
>
> -Build-Depends: debhelper (>= 7.4.10), bison, ed, mawk | awk, perl,
I got this same error on Ubuntu 14.04:
➜ ~ siege -i -f siege-urls.txt -l siege-log.txt
** SIEGE 3.0.5
** Preparing 15 concurrent users for battle.
The server is now under siege...[error] descriptor table full sock.c:119: Too
many open files
[error] descriptor table full sock.c:119: Too many
** Changed in: juju-mongodb (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1506990
Title:
please drop architecture list in
I fixed this by downloading the latest source version (at time of
writing, 3.1.0) from https://www.joedog.org/siege-home/ and installing
it using the instructions in the INSTALL file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: "systemctl status -l docker-service"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1525361/+attachment/4534538/+files/systemctl-status-docker-service.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Extreme delay due to Internet issues (thank you Comcast), and issues
with `libuuid1` in my local builders, which prevented things from
building. Working on the merge today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in
Blueprint changed by Robie Basak:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: TODO
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): INPROGRESS
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
Taged commit with fix v0.73
https://github.com/slact/nchan/commit/142b637e514e28be8e337b5d31547595d16cb477
--
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/1517865
Title:
nginx-extras
Ok. I've reproduced this, and collected some info here.
First, the following is a bit simpler user data to reproduce:
#!/bin/bash
exec >/run/docker.install.out 2>&1 http://squid.internal:3128
export DEBIAN_FRONTEND=noninteractive
apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80
** Attachment added: "journalctl -xe"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1525361/+attachment/4534539/+files/journal-xe.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Attachment added: "docker.install.out"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1525361/+attachment/4534537/+files/docker.install.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Oh and one final comment and I'll shut up for today: Debian is in the
process of uploading 1.5.2. If they actually do that soon, I'll redo the
merge on top of that (which would be nice, because I can drop two
patches).
--
You received this bug notification because you are a member of Ubuntu
** Changed in: dlm (Ubuntu)
Assignee: (unassigned) => Billy Olsen (billy-olsen)
--
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/1394237
Title:
The dlm package is not installable
>> - debian/control: Debian's golang package has dependencies on
>> golang-{doc,go,src} (= ${source:Version}); Debian has golang-{doc,go,src} (=
>> ${binary:Version}). This difference is not explained in the Ubuntu
>> changelog. I believe the delta should be dropped. It happens that both
>>
Here are the changes from Debian. Looking reasonably tidy to me.
** Patch added: "changes from debian"
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+attachment/4534865/+files/golang_1.5.1-4_1.5.1-4ubuntu1.diff
--
You received this bug notification because you are a member
New debdiff (against ubuntu)
** Patch added: "proposed changes from 0ubuntu4"
https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1524165/+attachment/4534864/+files/golang_1.5.1-0ubuntu4_1.5.1-4ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Server
I appreciate the problems you're facing, but unfortunately I can't help
you through the bug tracker. Pointers to community support can be found
at http://www.ubuntu.com/support/community
I suggest continuing to try to get help on ubuntuforums.org and perhaps
askubuntu.com for your specific
Public bug reported:
In case of e reboot, poweroff or "service corosync stop" corosync stops
before pacemacer this leads to an inconsistent state. As a communication
between the nodes is only possible as long as corosync is running.
My current work around is:
# fix order of corosync/pacemaker
You have been subscribed to a public bug by Robie Basak (racb):
Please merge tgt 1.0.61-1 (main) from Debian unstable (main)
** Affects: tgt (Ubuntu)
Importance: Wishlist
Status: Incomplete
** Tags: patch
--
Please merge tgt 1.0.61-1 (main) from Debian unstable (main)
The start order in the init scripts is not taken into account.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1525911
Title:
wrong stop order of corosync and pacemacer
To manage
** Changed in: golang (Ubuntu)
Status: New => Triaged
** Changed in: golang (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1524071
** Changed in: haproxy (Ubuntu)
Importance: Undecided => Medium
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1524635
Title:
haproxy syslog
** Package changed: mysql-5.6 (Ubuntu) => mysql-workbench (Ubuntu)
--
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/1525566
Title:
Não consigo fazer a conexão entre netbeans e
>From log:
Ställer in mysql-server-5.6 (5.6.27-0ubuntu0.15.04.1) ...
/var/lib/dpkg/info/mysql-server-5.6.postinst: rad 95:
/usr/share/mysql-common/configure-symlinks: Filen eller katalogen finns inte
dpkg: fel vid hantering av paketet mysql-server-5.6 (--configure):
underprocessen installerade
** Changed in: quagga (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quagga in Ubuntu.
https://bugs.launchpad.net/bugs/1525432
Title:
package quagga 0.99.22.4-3ubuntu1 failed to
Thank you for the update.
On looking again I noticed this from the documentation you quoted in
your original report:
"If port is not specified, sshd will listen on the address and all prior
Port options specified."
I'm sorry I didn't notice this the first time round. Given the word
"prior" in
Thank you for your report.
>From your report: "ERROR: There's not enough space in /var/lib/mysql/".
So this looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This looks like an issue with smfpd (Google suggests something to do
with Samsung printer drivers?) breaking your system init system, rather
than a problem with Docker.
You can find pointers to get help for this
You have been subscribed to a public bug by Robie Basak (racb):
The current rsyslogd configuration as provided by the rsyslogd package
causes double logging to occur.
Steps to Reproduce:
1) Install haproxy via whatever normal means (apt-get etc)
2) Configure it to listen on at least one port,
>From log:
Setting up samba-common (2:4.1.17+dfsg-4ubuntu3) ...
Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm
** Changed in: auto-package-testing
Status: New => Invalid
--
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/1522026
Title:
armhf lxd container does not start on arm64 system
To
thx/Seasons Greetings Robie. For now, I don't know which way to turn except
seeing months down the tubes
1. I acknowledge I'm the who lost a few very valuable work when a bug
crashed my PC, which I can't fix whatever has caused my fluttering greyed
out monitor screen, leading to crash
I wonder if you can work around this by using policy-rc.d to ask for the
docker service not to be started at install time, and instead when you
manually try to start it (as you're reporting that doing it a bit later
is working?)
That doesn't solve the actual problem though of course. I'd like to
** Changed in: dovecot (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1524526
Title:
Crashes with undefined symbol
To manage
You have been subscribed to a public bug by Robie Basak (racb):
?
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: quagga 0.99.22.4-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
Uname: Linux 3.13.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
>From log:
Setting up postfix (2.11.0-1ubuntu1) ...
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).
After modifying main.cf, be sure to run '/etc/init.d/postfix
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration
You have been subscribed to a public bug by Robie Basak (racb):
After searching the web, there's evidence to suggest that dovecot 2.2.9
in Ubuntu 14.04.3 LTS can have a segmentation fault at times. In
particular, having a shared mailbox configured can cause the imap daemon
to experience a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since we're on 2.2.18 in Xenial, I'm marking this Fix Released and
adding a bug task to track status on 14.04.
Please see https://wiki.ubuntu.com/StableReleaseUpdates. We can fix this
in 14.04 but only if the
Public bug reported:
amavisd-new -V
amavisd-new-2.7.1 (20120429)
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
with the current pattern amavisd is not able to scan with bitdefender
pattern:
### http://www.bitdefender.com/
['BitDefender', 'bdscan', # new version
@Sergey
Right now, this is more of an error report than a bug. It is perfectly
valid as an error report and may be a bug, but there isn't enough
information for a developer to work on it as a bug, therefore it is
Incomplete. Please read "How to report bugs effectively"
You have been subscribed to a public bug by Robie Basak (racb):
dovecot-lucene in wily (and xenial) crashes immediately when enabled due
to a bug in the buildsystem which enables use of the Snowball analyser
when textcat is available but the code is only built when libstemmer is
available.
Ryan, please could you take a look at this? I've taken a brief look at
the patches and I follow what they're achieving and why, but I'm not
confident that I follow all possible edge cases introduced by these
patches.
If you're satisfied then please could you prepare an SRU? Thanks!
** Changed
You have been subscribed to a public bug by Robie Basak (racb):
The following upstream patches are needed in order to avoid failures
when binding a netlink socket:
1f734a8f892a lib/socket: randomize the generated local port
http://git.infradead.org/users/tgr/libnl.git/commitdiff/1f734a8f892a
Year after year I am astonished that squid has been kept back in Ubuntu, when
all other distros update this important and hugely popular software with every
release.
Squid 3.3 became DEPRECATED in 2013 !!!
http://wiki.squid-cache.org/Squid-3.3
Please read the note from the squid page:
Initial look at the patches results in the following assessment:
The first 2 patches apply fine to the version included in Ubuntu Trusty
027157898708 lib/socket: don't fail if no more local ports can be assigned in
nl_socket_alloc
I fixed this by downloading the latest source version (at time of
writing, 3.1.0) from https://www.joedog.org/siege-home/ and installing
it using the instructions in the INSTALL file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Hello Folks,
I hate to beat an already "terribly beaten horse" but I'd like to say
that I would like the null cipher option to be available. The reason
being is that working for a WAN optimization company, the need to "see"
the unencrypted traffic is paramount in order to reduce SSH's network
Public bug reported:
I don't know
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libnss3-1d:amd64 2:3.19.2.1-0ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Dec 14
Btw, I'd prefer for bug 1524165 to be fixed first, then I'll redo 1.5.2
again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1524071
Title:
update to 1.5.2 release
To manage
I reproduced this bug with 2 different setups while doing a system upgrade
from Ubuntu 14.04.3 LTS.
1) In software & updates - Updates - Notify me of a new Ubuntu version - For
any new version
2) run software updater, select upgrade
systemd-sysv and init fails to install, broken dependency
** Patch removed: "Hidden. Workers for the kingdom of God . Thru Christ .and
every other is up to pinkie ."
https://bugs.launchpad.net/ubuntu/+source/siege/+bug/1317812/+attachment/4314607/+files/2015-02-07%2021.17.07.jpg
** Patch removed: "Gangsta"
63 matches
Mail list logo