** Changed in: python-cryptography (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-cryptography in Ubuntu.
https://bugs.launchpad.net/bugs/1555723
Title:
pip is breaking in
This is still incredibly odd because your traceback still flows through
/usr/local, which the apt installed pip would never do. So I think you
have some stuff installed in /usr/local, and possibly a PYTHONPATH, that
is breaking the system installed pip.
Note that on Debian (and derived)
On Jan 26, 2016, at 05:49 PM, Scott Moser wrote:
> mdadm Recommends -> postfix Recommends -> python
Can we bump the latter down to a Suggests?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
We won't be fixing virtualenv in Trusty, there's just too much to
backport. The solution is to use the built-in virtual environment
support in Python 3 for Trusty. Install the `python3.4-venv` package
and use `python3 -m venv `. Then proceed as you normally would
with a virtual environment.
**
On Dec 01, 2015, at 01:38 PM, Marc Deslauriers wrote:
>1- I can't reproduce this by installing the daily live cd in a VM
>2- I can reproduce it successfully by installing the daily live cd on real
>hardware
Confirmed that my working machine is a VM and the busted one is physical
hardware.
--
On Nov 30, 2015, at 08:51 PM, Bryan Quigley wrote:
>@barry.. Maybe do LiveCD tests on both of them to see if it's a
>configuration issue or if it might be hardware related.
I'd be very surprised if it was hardware, but I can try it. I never had this
problem on this machine until this morning's
I just noticed this today. AFAICT, it only affects https to
www.google.com and other Google subdomains (first noticed on
docs.google.com). It does not affect Firefox.
Odder still, I have two fully up-to-date (AFAICT) Xenial machines, both
amd64. One of them connects to https://www.google.com
Probably should be duped with LP: #1513113
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1512498
Title:
gnome-terminal thinks it's Byobu Terminal
To manage notifications about this
I'll do a local test and syncpackage if that passes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007
Title:
Sync 1.0.0-2 from debian testing, fixes FTBFS due to
LGTM, syncing dropping the Ubuntu delta.
** Changed in: python-linecache2 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
This bug was fixed in the package python-linecache2 - 1.0.0-2
---
python-linecache2 (1.0.0-2) unstable; urgency=medium
* Runs unit tests during build, thanks to a patch from James Page
(Closes: #795889).
-- Thomas Goirand Fri, 28 Aug 2015 15:46:28 +
--
Public bug reported:
wily dist-upgrade caused this failure.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: nut-client 2.7.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
% sudo apt-get install --reinstall nut-client
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk
Removing the bogus symlink lets me at least remove nut, nut-client, and
nut-server and reinstall those packages.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1505288
Title:
package
More headscratchers:
% locate nut-client.service | xargs ls -l
lrwxrwxrwx 1 root root 39 Jan 10 2014 /etc/systemd/system/nut-client.service
-> /lib/systemd/system/nut-monitor.service
-rw-r--r-- 1 root root 0 Jan 10 2014
/var/lib/systemd/deb-systemd-helper-enabled/nut-client.service
% ls -l
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
** Changed in: ply (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: ply (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ply in Ubuntu.
https://bugs.launchp
This upstream Python 3.5 change breaks cliff's test suite:
https://bugs.python.org/issue15582
The patch is simple enough, so I'll just attach it here. I plan on
uploading a fix to Ubuntu. We can resync to any new Debian release when
that's available.
** Also affects: python-cliff
** Changed in: genshi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
https://bugs.launchpad.net/bugs/1492359
Title:
genshi FTBFS with Python 3.5 in Wily
To manage
** Tags added: python3.5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ply in Ubuntu.
https://bugs.launchpad.net/bugs/1491620
Title:
ply 3.4-5 ftbfs with Python 3.5
To manage notifications about this bug go to:
been applied upstream yet.
** Affects: genshi (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: New
** Tags: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
https
** Bug watch added: Debian Bug tracker #798030
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798030
** Also affects: genshi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798030
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
A rebuild of python-babel 1.3 would ftbfs, as it does in the Python 3.5
-as-default PPA:
https://launchpadlibrarian.net/210474372/buildlog_ubuntu-wily-amd64
.python-babel_1.3%2Bdfsg.1-5_BUILDING.txt.gz
We should investigate Babel 2.0 which appears to be the latest upstream.
Public bug reported:
Full buildlog from the Python 3.5-as-default PPA:
https://launchpadlibrarian.net/211356336/buildlog_ubuntu-wily-amd64
.python-cliff_1.13.0-0ubuntu1_BUILDING.txt.gz
Should at least investigate whether new upstream 1.14.0 fixes the
problem, or report the bug upstream.
**
** Bug watch added: Debian Bug tracker #797840
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797840
** Also affects: ply (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797840
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Public bug reported:
Even ply 3.7 upstream is incompatible with Python 3.5
https://github.com/dabeaz/ply/issues/76
** Affects: ply (Ubuntu)
Importance: High
Status: New
** Tags: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
On Sep 01, 2015, at 10:57 PM, Colin Watson wrote:
>I thought (from https://github.com/pytest-dev/pytest/issues/744) that
>you were planning to fix this by backporting the pytest fix instead?
I admit I'm thoroughly confused. pytest already has the py35 patch and now
after building a six 1.9.0-5
Public bug reported:
Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast module
API change (ast API is not guaranteed to be stable across Python
releases). This causes six to FTBFS in Wily, where we've enabled Python
3.5 as a supported version.
@slangasek investigated and the neutron failures are unrelated. neutron
has been failing since February, but requests, six, and setuptools
entered trusty-proposed on 2015-03-26.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
wheel from utopic seems to build just fine in a trusty chroot. I then
used that to build six 1.5.2-1ubuntu1 in trusty, and everything looked
fine, including the six wheel.
More to follow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
wheel from utopic seems to build just fine in a trusty chroot. I then
used that to build six 1.5.2-1ubuntu1 in trusty, and everything looked
fine, including the six wheel.
More to follow.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
colorama, urllib3 lgtm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-scripttest in Ubuntu.
https://bugs.launchpad.net/bugs/1433324
Title:
provide whl packages in trusty to enable pyvenv in python3.4
To manage notifications
Okay, all of these trusty backports look good to me. Test built all of
them just fine. Reviewed the diffs against current
trusty{,-backports,-security} version. Tested imports. Tested
virtualenv. AFAICT, these are good to go.
--
You received this bug notification because you are a member of
requests, setuptools, pip lgtm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-scripttest in Ubuntu.
https://bugs.launchpad.net/bugs/1433324
Title:
provide whl packages in trusty to enable pyvenv in python3.4
To manage
chardet lgtm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-scripttest in Ubuntu.
https://bugs.launchpad.net/bugs/1433324
Title:
provide whl packages in trusty to enable pyvenv in python3.4
To manage notifications about
distlib, html5lib lgtm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-scripttest in Ubuntu.
https://bugs.launchpad.net/bugs/1433324
Title:
provide whl packages in trusty to enable pyvenv in python3.4
To manage notifications
When you hit this error, if possible, please attach /var/log/system-
image/client.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to snappy in Ubuntu.
https://bugs.launchpad.net/bugs/1400960
Title:
Problems with a snappy tour
To
** Changed in: requests (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to requests in Ubuntu.
https://bugs.launchpad.net/bugs/1391554
Title:
python3-requests installed, import requests fails
On Oct 17, 2014, at 08:57 AM, Данило Шеган wrote:
Cheers Barry, much appreciated!
No problem!
It seems it's all done and released in main:
http://packages.ubuntu.com/source/utopic/pyparsing
https://launchpad.net/ubuntu/utopic/+source/pyparsing/2.0.3+dfsg1-1
Let me know if I still need to
)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: pyparsing (Ubuntu)
Milestone: None = ubuntu-14.10
** Changed in: pyparsing (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I just uploaded 2.0.3+dfsg1-1 to unstable. As soon as it lands there,
I'll do a sync to utopic. Can you give ubuntu-release a heads up that
this needs to be approved?
** Changed in: pyparsing (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you
Public bug reported:
PEP 466 http://legacy.python.org/dev/peps/pep-0466/ backported Python
3 security enhancements for OpenSSL to Python 2.7.x. As part of the
port, _ssl.sslwrap(). AFAICT, this was never a public API anyway (it
does not appear to be documented), but eventlet was using it, thus
** Changed in: moin (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to moin in Ubuntu.
https://bugs.launchpad.net/bugs/1351331
Title:
Please merge moin 1.9.7-2 (main) from Debian
This bug was fixed in the package ipvsadm - 1:1.26-3
---
ipvsadm (1:1.26-3) unstable; urgency=medium
* [8fe73cf] Move to quilt 3.0
* [9ae82d1] wrap-and-sort
* [d8b7ba7] Move to debhelper compat v9
* [450ce1d] Remove obsolete dpatch patches
* [86caa7e] Remove obsolete
On Mar 11, 2014, at 04:54 AM, Serge Hallyn wrote:
Thanks for filing this bug. I'd like to try to reproduce it but need a
few more details. Can you tell us exactly how you set up the vm, how
you start it, and how you initiate suspend? Is this all done through
virt-manager? You say it is a
% dpkg-query -W qemu-system-arm
qemu-system-arm 2.0~git-20140307.4c288ac-0ubuntu2
--
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/1287443
Title:
qemu crash in armhf sbuild
To manage
Yes, qemu 2.0 still segfaults.
** Attachment added:
ubuntu-download-manager_0.3+14.04.20140224-0ubuntu1_armhf.build
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1287443/+attachment/4017328/+files/ubuntu-download-manager_0.3%2B14.04.20140224-0ubuntu1_armhf.build
--
You received this
On Mar 08, 2014, at 04:59 PM, Martin Pitt wrote:
This is first and foremost a QEMU or linux bug (not sure which), it
should really update its internal time after suspend. But I suppose ntp
could also listen to resume events (perhaps through pm-utils' /usr/lib
/pm-utils/sleep.d/ scripts); although
Public bug reported:
Trying to build lp:~mandel/ubuntu-download-manager/typos-logs-unlock-
not-locked in an armhf schroot on amd64. See attached log file of qemu
crash.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu (not installed)
ProcVersionSignature: Ubuntu 3.13.0-13.33-generic
** Attachment added:
ubuntu-download-manager_0.3+14.04.20140224-0ubuntu1_armhf.build
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1287443/+attachment/4005977/+files/ubuntu-download-manager_0.3%2B14.04.20140224-0ubuntu1_armhf.build
--
You received this bug notification because you are
** Changed in: python-repoze.lru (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-repoze.lru in Ubuntu.
https://bugs.launchpad.net/bugs/1283750
Title:
test failures with
This bug was fixed in the package genshi - 0.7-1
---
genshi (0.7-1) unstable; urgency=low
[ Barry Warsaw ]
* Team upload.
- Closes: #673935
* New upstream release. Closes: #731280
- Closes: #713747 (FTBFS)
- Closes: #673935 (py:match templates patch applied
On Dec 15, 2013, at 04:43 AM, Jackson Doak wrote:
Would you mind syncing this since it's out of NEW?
Oh yes, I planned to. (Didn't expect it to clear NEW so soon. :)
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in
can just
syncpackage -f it. I'm happy to do that.
** Affects: genshi (Ubuntu)
Importance: Medium
Assignee: Barry Warsaw (barry)
Status: Triaged
** Changed in: genshi (Ubuntu)
Importance: Undecided = Medium
** Changed in: genshi (Ubuntu)
Status: New = Triaged
Looks like this has already been done:
% rmadison python-happybase | grep trusty
python-happybase | 0.7-1| trusty | source, all
** Changed in: python-happybase (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server
This bug was fixed in the package python-oauthlib - 0.5.1-1
---
python-oauthlib (0.5.1-1) unstable; urgency=low
* New upstream release
* Switched to pybuild
-- Daniele Tricoli er...@mornie.org Tue, 03 Sep 2013 05:14:53 +0200
python-oauthlib (0.5.0-1) unstable; urgency=low
On Sep 04, 2013, at 09:26 PM, Julian Taylor wrote:
To resolve the issue we have two options:
patch 1.5.7 and 2.0.0, easy but programs that check for version numbers to
avoid the bug will not accept the package. This is the case e.g. with
matplotlib 1.3, I have filed a patch which was accepted
The patch in comment #7 does not apply cleanly against the saucy source
branch:
% patch --dry-run -p1 ../python-webob_1.2.3-2_1.2.3-2ubuntu1.diff
checking file debian/changelog
Hunk #1 FAILED at 1.
Hunk #2 succeeded at 24 with fuzz 2 (offset 5 lines).
1 out of 2 hunks FAILED
checking file
The test_requests.py patch should probably be forwarded to upstream.
Also, I'm keeping Ubuntu's debian/watch file since it points to pypi.
The B-D on quilt silences a lintian error:
Now running lintian...
E: python-webob source: missing-build-dependency quilt
Finished running lintian.
I just
Failure in the package importer.
http://package-import.ubuntu.com/status/mailman.html#2012-07-04
19:09:24.657951
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1184892
Title:
So, I probably just did the stupidest thing ever, but I can't see how it
will make things worse.
I grabbed the out of date version, and the latest .dscs from unstable
and saucy and then imported them:
$ bzr branch ubuntu:mailman saucy
$ chdist apt-get sid source mailman
$ apt-get source mailman
This is an upstream change, as a byproduct of issue #10182
http://bugs.python.org/issue10182
In that bug, a complaint was made that match starts were being truncated
on x64 Windows machines, so the types were changed to longs. I can
reproduce this with hg tip of the 2.7 branch, and the world
Cool, so Benjamin reverted the API change in upstream hg by using PyInt*
instead of PyLong* apis. You'll see this the next time Matthias syncs
to upstream.
** Changed in: python2.7 (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of
.
** Affects: python-tx-tftp (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: In Progress
** Tags: ftbfs rls-q-incoming
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx
Public bug reported:
I'm seeing this now in my 12.04 /var/log/mail.log:
Jun 27 16:25:19 wreckers dovecot: imap(barry): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x380ca) [0x7effc6c080ca] -
/usr/lib/dovecot/libdovecot.so.0(+0x3810e) [0x7effc6c0810e] -
So far, that patch does seem to fix the crashes, and dovecot appears to
be working again on my production 12.04 system. I'll now submit a merge
proposal and SRU request.
** Changed in: dovecot (Ubuntu)
Milestone: None = ubuntu-12.04.1
** Changed in: dovecot (Ubuntu)
Importance: Undecided
** Description changed:
+ SRU information:
+
+ See below for detailed description. tl;dr: Dovecot continuously panics,
+ preventing local delivery. Mail clients cannot connect or read their
+ mail. This is a critical crash which is not fixed by restarting
+ dovecot, rebooting, or anything
Debian testing has 0.58 now, so I merged that, keeping the Ubuntu delta.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/900662
Title:
Please merge etckeeper 0.57 (main) from
Daniel, thanks very much for your contribution to Ubuntu.
I am unable to reproduce this bug because for some reason vm-builder
just hangs for me on both Lucid and Precise. However, from visual
inspection, I think your patch is spot on. Note however that it does
not apply cleanly to Precise.
I've also uploaded the Precise package to my PPA, which you can enable
with:
$ sudo add-apt-repostory ppa:barry/python
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
On further reflection, I think the patch is safe to upload to Precise,
and I will do this. I'm not entirely convinced the bug meets the SRU
guidelines for Lucid
https://wiki.ubuntu.com/StableReleaseUpdates
so I won't prepare an SRU for it. I have however uploaded vm-
Merge proposal for trunk:
https://code.launchpad.net/~barry/vmbuilder/bug-612082/+merge/80615
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/612082
Title:
optparser attribute
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Affects: mailman (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #637398
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637398
** Also affects: mailman (Debian) via
http
** Changed in: mailman (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/826795
Title:
Python dependencies are missing
To manage
@Julian: that changeset appears to be included in lm-sensors 3.3.0,
which is now packaged in Debian. We're carrying a couple of deltas from
Debian which is preventing a sync to the latest version. I've
subscribed Micah and Bryce to get their feedback, but I think at least
two of the deltas can
On Jul 15, 2011, at 07:06 PM, Micah Gersten wrote:
I was planing on merging lm-sensors this wekeend. My and apw's diff are
included in the latest Debian version.
Fantastic! Thanks Micah.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I just tried this on my MBP1,1 running Natty. sensors-detect correctly
found the coretemp module, and prompted me to add it to /etc/modules.
The default is not to install it, but I chose yes. On a reboot,
coretemp was loaded and `sensors` gave me core temperatures.
Now, my MBP1,1 is about 6
** Changed in: lm-sensors (Ubuntu)
Assignee: Barry Warsaw (barry) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/212370
** Changed in: lm-sensors (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) = Barry
Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/212370
Hi Colin. Is it possibly something odd about your build environment?
With your patch it builds fine for me in an Oneiric pbuilder. I'll try
a PPA/sbuild next.
imagestore.tests.test_resources
ResourcesTest
testCancel ... [OK]
Okay, it does fail in my PPA
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to image-store-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/802402
Title:
convert to dh_python2
To manage notifications about this bug go to:
Verified that unchanged 1.0.4-0ubuntu3 also fails in an sbuild.
Assigning to server team.
** Changed in: image-store-proxy (Ubuntu)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
** Changed in: image-store-proxy (Ubuntu)
Status: Incomplete = Confirmed
--
You
BTW, reverting/working around the change was rejected for 2.7.2 so
upstream will need to adjust.
--
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/791221
Title:
Nova's test suite fails
It's almost certainly related to this entry in Misc/NEWS:
- Correct lookup of __dir__ on objects. Among other things, this causes errors
besides AttributeError found on lookup to be propagated.
and this log entry:
changeset: 70312:b2fc6b9f850f
branch: 2.7
parent:
I think this one is even simpler to illustrate the change:
class Foo:
def __dir__(self):
return ['a', 'b', 'c']
class Bar:
def __dir__(self):
return ('a', 'b', 'c')
print dir(Foo())
print dir(Bar())
AFAICT, in Python 2.7.1 you get two lines of ['a', 'b', 'c'] while in
http://bugs.python.org/issue12248
** Bug watch added: Python Roundup #12248
http://bugs.python.org/issue12248
--
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/791221
Title:
Nova's
barry jamespage: http://docs.python.org/dev/whatsnew/3.2.html [11:48]
barry The misleading functions PyEval_AcquireLock() and
PyEval_ReleaseLock() have been officially deprecated. The thread-state
aware APIs (such as PyEval_SaveThread() and PyEval_RestoreThread())
should
I reviewed it and approved it. It's just waiting for someone with
upload rights to commit the change.
--
Please merge cheetah 2.4.2.1-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/663343
You received this bug notification because you are a member of Ubuntu
Server Team,
Now that python-support with 2.7 has landed, I've requested a rebuild of
python-cheetah 2.4.3. The builds look like they are succeeding. Is
there anything else we need to do with this bug?
** Changed in: cheetah (Ubuntu)
Status: In Progress = Fix Released
** Changed in: cheetah
** Changed in: mailman
Status: Fix Committed = Fix Released
--
Mistakes in mailman strings.
https://bugs.launchpad.net/bugs/426979
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.
--
Ubuntu-server-bugs mailing
I guess this still hasn't made it into Lucid yet?
% sudo vmbuilder kvm ubuntu --suite=lucid --flavour=virtual
--libvirt=qemu:///system --arch=amd64 --firstboot=boot.sh
Usage: vmbuilder hypervisor distro [options]
vmbuilder: error: no such option: --firstboot
Any word on that SRU?
--
Here's a branch that merges the current Lucid version with the latest
upstream:
https://code.edge.launchpad.net/~barry/ubuntu/lucid/vm-builder/firstboot
I tried to do a build from branch, but got bug 589454 so I uploaded a
version to my PPA
https://edge.launchpad.net/~barry/+archive/python
I'll throw my weight behind adding mkcert.sh to the package. The
rationale is that if you google for dovecot ssl you'll be presented
with the dovecot.org wiki pages that describe using mkcert.sh. So
naturally you're going to want to try that simple approach and will fail
on Ubuntu.
Simple
93 matches
Mail list logo