Public bug reported:
pyparsing 2.0.0 and 1.5.7 have a serious bug breaking any forward grammar:
http://sourceforge.net/p/pyparsing/bugs/67/
this is fixed in 2.0.1 with a very small patch, but it is complicated
due to a split into two source packages which happened in 2.0.0 and
1.5.7, the python3
Public bug reported:
python3-pyparsing in raring does not contain pyparsing.py:
$ dpkg -L python3-pyparsing
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python3-pyparsing
/usr/share/doc/python3-pyparsing/changelog.Debian.gz
/usr/share/doc/python3-pyparsing/copyright
/usr/lib
** Branch linked: lp:~jtaylor/ubuntu/raring/pyparsing/fix-py3-package
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pyparsing in Ubuntu.
https://bugs.launchpad.net/bugs/1170107
Title:
python3-pyparsing is an empty package
To
*** This bug is a duplicate of bug 1103111 ***
https://bugs.launchpad.net/bugs/1103111
** This bug has been marked a duplicate of bug 1103111
Upgrade failure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
*** This bug is a duplicate of bug 1103111 ***
https://bugs.launchpad.net/bugs/1103111
** This bug has been marked a duplicate of bug 1103111
Upgrade failure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
*** This bug is a duplicate of bug 1103111 ***
https://bugs.launchpad.net/bugs/1103111
** This bug has been marked a duplicate of bug 1103111
Upgrade failure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
turns out using buildflags is not so good as it lacks the extra logic to handle
pie and pic clashes which hardening wrapper has.
sorry for the wrong request.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
instead of using the old hardening wrapper we should use the new
dpkg-buildflags interface:
export DEB_BUILD_MAINT_OPTIONS=hardening=+pie,+bindnow
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
I don't see pie or bindnow in the old buildlogs, the current version doesn't
even build with pie (some library/executable code mixup)
so its not a regression.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
scratch that, the old hardening wrapper does not show the stuff in the
buildlog.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1039542
Title:
Please re-enable PIE and BIND_NOW
** Also affects: asterisk (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1022360
Title:
(CVE-2012-3812) CVE-2012-3812
** Also affects: mod-proxy-html (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/988819
Title:
[SRU] wrong path to libxml2.so.2
** Changed in: mod-proxy-html (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/988819
Title:
[SRU] wrong path to libxml2.so.2 in
** Package changed: python-defaults (Ubuntu) = juju (Ubuntu)
** Changed in: juju (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1003138
Title:
this was probably fixed in 1:1.8.10.1~dfsg-1ubuntu1
** Changed in: asterisk (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/517144
for precise it might be better to instead sync the version from debian
which has the fix. It looks like its a bugfix only update so it could be
synced without an exception.
for oneiric can the bug description please be updated for an SRU:
see https://wiki.ubuntu.com/StableReleaseUpdates
--
You
can you give some details on the regressions. Where they fixed in .10 or still
open?
there have been several CVE's fixed in those versions which should then be
backported.
e.g. CVE-2011-4598, CVE-2011-4063
also precise is supported 5 years, so getting a newer version will ease
backporting
I have also uploaded the fix to oneiric-proposed please test it when it
has been accepted.
note that the version number for SRU in this case is ubuntu1.1
see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
for general stable version number advice
thanks for the
This is due to a toolchain change in oneiric.
Now by default the linker flag --as-needed is used, which requires you to place
the libraries behind objects needing their symbols.
See: https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition
A fix should be to simply do this:
g++ $(mysql_config
*** This bug is a duplicate of bug 629005 ***
https://bugs.launchpad.net/bugs/629005
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 629005, so it is being marked as such. Please look
20 matches
Mail list logo
