The attached patch gets past the compilation problems, but the test
suite still fails:
TEST: test-vala... (pid=6684)
/Unit/ResultsSynchronizer: OK
/Unit/IO/AsyncDesktopFile: OK
Public bug reported:
checkbox fails to build against Python 3.5 in Wily. Here's the PPA
build log for details.
https://launchpadlibrarian.net/211139258/buildlog_ubuntu-wily-
amd64.checkbox_0.18-0ubuntu2_BUILDING.txt.gz
** Affects: checkbox (Ubuntu)
Importance: High
Status: New
** 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
** 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
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
Bugs, which is
End of bug - please close this one. But please consider making it a
Unity wishlist item. No one I was in contact with could repeat the
problem. I downloaded the latest daily-build of Wily, and tried
everything I could in the live session to break Unity.
I conclude that the problem occurred
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
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
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 think I forgot to do that. I'll look at that tomorrow and back out the six
change if it works out. I
See also https://launchpadlibrarian.net/211356903/buildlog_ubuntu-wily-
amd64.six_1.9.0-3_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491162
Title:
FTBFS in Wily
To manage
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.
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.
This is because in Debian/Ubuntu, we've made --user the default. While
this diverges from upstream, it's a sensible default and something that
upstream eventually wants to adopt too.
https://github.com/pypa/pip/issues/1668
You can either put ~/.local/bin on your $PATH or use `sudo pip install
I have now tried setting up another account on the same installation of Wily.
The problem is there as well. I've been trying to get friends to run Wily, and
try the steps that I found caused the problem. So far with little success.
The steps are:
Open an online account with Google, and use
It's been pointed out to me that Wily does not integrate anything Google
by default. Checking back, I set up the Google account in my Online
Accounts, when I installed evolution, so I could import my google
contacts.
Google contacts don't export in a format which the Thunderbird address-
book
Maybe some explanation as to exactly what I did to the Ubuntu Unity settings
might help. In the Online Account settings, it lists access by Ubuntu to the
following Google online accounts for these apps:
Evolution Data Server (if Evolution is installed) for Contacts, for Calendar
and for Gmail.
Public bug reported:
Immediately after removing interaction with all Google accounts
(settings-online accounts), the Unity dash no longer showed any
applications, only files recently accessed. The launcher sidebar is
unaffected, and the dash appears as normal but without access to
applications.
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
On Aug 27, 2015, at 01:22 PM, Muelli wrote:
I think the duplicate status is wrong.
I agree, but then it's not a bug in python-apt. It's really a bug caused by
our old version of pip, which doesn't
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
On Aug 27, 2015, at 02:16 PM, Julian Andres Klode wrote:
If you guys want this to track the pip bug, then please unduplicate it,
and drop the python-apt bug.
There's no need, it's already fixed.
--
You
*** This bug is a duplicate of bug 1445949 ***
https://bugs.launchpad.net/bugs/1445949
On Aug 27, 2015, at 02:55 PM, Muelli wrote:
I confirm that the wily version makes pip freeze work.
Yay!
Will we see a fix in vivid?
Unlikely unless someone provides a patch. I probably won't have time,
On Aug 21, 2015, at 04:07 PM, Alberto Milone wrote:
I can build the same code in a vivid chroot without seeing any failures.
My guess is that something else (python-apt? python-aptdaemon?) changed
in the archive.
Oh yes, they surely have.
python-apt | 0.9.3.11build1 | vivid |
Public bug reported:
This version fails to build from source in wily-proposed, although I
don't understand why. Attached is the full build log.
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Attachment added: ubuntu-drivers-common_0.4.7_amd64.build
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1487223/+attachment/4449886/+files/ubuntu-drivers-common_0.4.7_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm also experiencing the same bug on Linux Mint 17.2 that Kyle C.
reported above. It seems to mostly (if not only) affect the right edge
of the window and there does appear to be a connection with using the
system menu resize just like Kyle noted. Maybe I'll just stop using the
keyboard shortcut
Public bug reported:
The adt-run manpage is unclear whether the results are logged if -o or
-l is not given. I think they should, but the manpage should clarify
whether they are and if so, where the logs are placed by default.
** Affects: autopkgtest (Ubuntu)
Importance: Undecided
Public bug reported:
Very often, it's quite difficult to find all the results in the log
files. If there's a lot of output between runs of separate tests, the
results can be separated by a lot of output. Further, there's no super
great way to search for the results.
Better would be something
On Aug 14, 2015, at 03:19 PM, Martin Pitt wrote:
Indeed the single log often isn't the easiest to consume output. But
every individual test has its own testname-stdout and
testname-stderr artifact, which is also available from
http://autopkgtest.ubuntu.com (artifacts.tar.gz link). stderr and exit
For example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-wily/wily/i386/p/python-pex/20150814_061119@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
python3-distupgrade contains the symlink /usr/lib/python3/dist-
packages/DistUpgrade/NvidiaDetector which symlinks to ../NvidiaDetector.
However /usr/lib/python3/dist-packages/NvidiaDetector is owned by
ubuntu-drivers-common.
This causes a problem with at least the pex DEP-8
If it is a cython issue, I wonder if 0.23 fixes it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478146
Title:
pytables FTBFS with python3.5
To manage notifications about this bug go to:
It's not a cython issue, it's a bug in PyTables. I think I have a fix
so I'll report this upstream and work on a wily package update (and will
send a debdiff to Debian BTS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #795333
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795333
** Also affects: pytables (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795333
Importance: Unknown
Status: Unknown
--
You received this bug notification because
.
[1] https://github.com/PyTables/PyTables/issues/485
** Changed in: pytables (Ubuntu Wily)
Status: Triaged = In Progress
** Changed in: pytables (Ubuntu Wily)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is a low impact change, so if it makes folks lives easier, I'm
happy to apply it. No ETA on that atm, but +1 for making this change to
wily and trusty.
** Changed in: python-virtualenv (Ubuntu)
Status: Opinion = Triaged
** Also affects: python-virtualenv (Ubuntu Wily)
Importance:
** Changed in: python3-defaults (Ubuntu)
Status: New = In Progress
** Changed in: python3-defaults (Ubuntu)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: python3-defaults (Ubuntu)
Importance: Undecided = High
** Changed in: python3-defaults (Ubuntu)
Milestone
Public bug reported:
This is the second step in the Python 3.5 transition, after LP: #1474882
which makes Python 3.5 a supported version. In this bug, we intend to
switch the default Python 3 version to Python 3.5 but we won't need to
rebuild any other packages.
** Affects: python3-defaults
On Jul 15, 2015, at 07:29 AM, Alessio Treglia wrote:
Apparently lives's FTBFS is unrelated. It seems fixed with lives
2.4.0~ds0-1 in Debian unstable, which closed https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=789858
Thanks. I'll look at doing a sync.
--
You received this bug notification
Public bug reported:
This is the third step of the Python 3.5 transition after LP: #1474882
(adding 3.5 as supported) and LP: #1474886 (make 3.5 default).
It's not clear yet whether we will do this for wily or defer it for x
(16.04 LTS).
Note that this bug will require a mass rebuild to drop
Public bug reported:
Add Python 3.5 as a supported Python 3 version for wily, keeping Python
3.4 as the default version.
Note that many packages will need new uploads so that they will be built
for Python 3.5. See the transition PPA for details, including FTBFS.
debdiff for change I plan to upload
** Patch added: lp1474882.diff
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1474882/+attachment/4429412/+files/lp1474882.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
shiboken:
https://launchpadlibrarian.net/210638858/buildlog_ubuntu-wily-
amd64.shiboken_1.2.2-1_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=shibokenfield.status_filter=publishedfield.series_filter=
** Also affects: shiboken
*** This bug is a duplicate of bug 1474539 ***
https://bugs.launchpad.net/bugs/1474539
Public bug reported:
We're in the process of starting the Python 3.5 transition for Wily. As
such, we've identified a number of packages which FTBFS with Python 3.5.
We're also soon starting the transition
Public bug reported:
We're in the process of starting the Python 3.5 transition for Wily. As
such, we've identified a number of packages which FTBFS with Python 3.5.
We're also soon starting the transition to gcc5. These are the packages
that FTBFS in both transitions.
Here is a link to the
blist:
https://launchpadlibrarian.net/210636656/buildlog_ubuntu-wily-
amd64.blist_1.3.6-4_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=blistfield.status_filter=publishedfield.series_filter=
** Also affects: cigi-ccl (Ubuntu)
libguestfs:
https://launchpadlibrarian.net/210638193/buildlog_ubuntu-wily-
amd64.libguestfs_1%3A1.28.6-1ubuntu1_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=libguestfsfield.status_filter=publishedfield.series_filter=
** Also
kubuntu-driver-manager:
https://launchpadlibrarian.net/210637379/buildlog_ubuntu-wily-amd64
.kubuntu-driver-manager_15.04ubuntu3_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=kubuntufield.status_filter=publishedfield.series_filter=
cigi-ccl:
https://launchpadlibrarian.net/210636859/buildlog_ubuntu-wily-amd64
.cigi-ccl_3.3.3a%2Bsvn818-8_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter
=cigi-cclfield.status_filter=publishedfield.series_filter=
** Description
lives:
https://launchpadlibrarian.net/210474052/buildlog_ubuntu-wily-
amd64.lives_2.2.8~ds0-1ubuntu1_BUILDING.txt.gz
https://launchpad.net/~pythoneers/+archive/ubuntu/py35asdefault/+packages?field.name_filter=livesfield.status_filter=publishedfield.series_filter=
--
You received this bug
Hi. Is there anything else I can do to help debug/fix this issue? It's
still a problem with the latest dist-upgrade on wily and it makes my
desktop unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It doesn't come from system-image. Removing that bug task.
** No longer affects: system-image (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359344
Title:
Contradictory and/or incomplete
On Jun 25, 2015, at 11:13 AM, Jonas Thiem wrote:
Who calls pyvenv directly?
I do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To
On Jun 25, 2015, at 04:31 PM, Donald Stufft wrote:
FWIW I think that ``python -m venv`` is the easiest (only?) way to
reliably say that you want to create a virtual environment for *this*
particular Python.
Even though I don't generally use it, I agree with the above.
--
You received this bug
@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
Bugs, which is subscribed to Ubuntu.
@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
Note that in 15.10, at the moment, wine can't be installed at all -
either 1.6x or 1.7x. I'll have to wait a bit longer. Not sure, but I
think with the number of changes, a new version of wine is going to have
to be built and packaged before there is any chance. Maybe this time,
15.10 will
On Jun 18, 2015, at 03:09 PM, Didier Roche wrote:
I disagree that this patch should be dropped. Look at the upstream bug
and people thanking about that change, look at the g+ post and
developers finding sanity in installing things locally.
Sure, but I'm also getting bombarded by comments from
Through a process of disk snapshotting, apt-mark holding certain
packages, and bisecting the dist-upgrade, I've narrowed it down to one
of the following packages. I'm unable to narrow it down any further.
This is the output of `apt-get dist-upgrade --dry-run`
The following packages will be
2.5.1 as a fixed phasing algorithm. system-image-cli also has a couple
of command line switches around phasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465828
Title:
ota-4 image contains
On Jun 17, 2015, at 12:08 PM, Matthias Klose wrote:
+ To validate this SRU, I'm proposing to use the results from the test
+ rebuild, plus evaluating the testsuite results of the python3.4 package
+ itself.
+1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Jun 16, 2015, at 11:37 AM, Jonas Thiem wrote:
Is there any chance this will be made available without a separate
python3-venv package? Since python 3.3 or 3.4 venv is considered as a
core package, so the requirement to install python3-venv is somewhat
non-intuitive.
Would it be good enough if
** Summary changed:
- Please provide a way to get the progress in used from a plugin
+ Expose --progress settings in the global config
** Description changed:
For snappy we use a plugin to apply the upgrade. I.e. we set:
[hooks]
apply: ubuntucoreupgrader.apply.ApplyUpgrade
- We
Public bug reported:
Now that adt-run supports reboots in some test beds, we should add some
tests that verify upgrades through reboot.
Start by looking at the latest lp:ubuntu-tests-cases/touch which was the
result of previous QA work around this topic.
** Affects: system-image (Ubuntu)
1.5.4-1ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324391
Title:
pip 1.5.4 import an invalid dependencies
To manage notifications about this bug go to:
On Jun 16, 2015, at 06:53 PM, Brian Murray wrote:
I've tried seeing if this SRU fixes the issue I encountered in comment
#4 and it does not seem to.
Looks like a versioned binary package dependency got lost. Testing a
fix now.
--
You received this bug notification because you are a member of
** Changed in: ubuntu-system-image
Assignee: Barry Warsaw (barry) = Łukasz Zemczak (sil2100)
** Also affects: system-image (Ubuntu)
Importance: Undecided
Status: New
** Changed in: system-image (Ubuntu)
Assignee: (unassigned) = Łukasz Zemczak (sil2100)
** No longer affects
Public bug reported:
I have a 3440x1440 monitor and after today's full dist-upgrade, most of
the screen real-estate is unusable. I see a small rectangular patch in
the lower left corner, and on this patch I can right-button to bring up
the menu. While the rest of the screen will display the
This appears to be fixed with today's full dist-upgrade.
** Changed in: unity
Status: New = Invalid
** Changed in: unity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This appears to be fixed with today's full dist-upgrade.
** Changed in: xorg-server (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462398
Title:
wily boot is
I understand far better now. What the installer had done was
overwritten the BIOS boot sector on sda with the efi information that it
would have correctly written to a UEFI bootable disk. I have now tried
re-installing with the two internal drives disconnected physically.
This made my spare
Ok. That works fine in the BIOS boot mode - I think there ought to be a
warning though! I didn't expect that kind of behaviour - and was
surprised by it. However, yesterday, I spent a long time experimenting
with EFI install to my spare drive. The components of grub are
installed to sdc, but
I've checked that out. I have a choice on my boot menu and when I
choose EFI boot, I get the grub menu. I'm going to try this later today
and re-install to my spare drive. I hope to collect more information as
to why I can't boot from it. It still leaves the problem that when I do
a BIOS
Public bug reported:
I have a PC which has two internal hard drives. One of them (sda)
currently has an installation of Mint, and the other (sdb) contained an
installation of 15.04 at the time of this problem.
I made a DVD from the testing iso of 15.10 last Wednesday. On booting
from this DVD,
The installation described in detail was made to a removable spare disk
in a caddy, so I ended up with two Ubuntu installaions; the second being
a temporary experiment to try to find out what had happened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
$ sudo apt-get install wine
[sudo] password for barry:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Wine currently cannot be installed: log as follows:
Some packages could not be installed. This may mean that you have
SRU information.
[Impact]
pip installing a package as root into /usr/local is a supported use case. This
bug describes two problems with that in Trusty. First, installing some
packages, such as httpie, can upgrade requests to an incompatible version,
causing a subsequent ImportError when
1.5.4-1ubuntu2 has been uploaded to trusty-proposed and awaits SRU
approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324391
Title:
pip 1.5.4 import an invalid dependencies
To manage
Now that 1.5.6-6ubuntu1 has finally been promoted to wily, I've verified
that the repro recipe bdmurray describes in #4 is fixed, both the import
error and the debsums error.
I'll now be working on backporting the patch to SRU a fix into Trusty.
--
You received this bug notification because you
After bisecting the dist-upgrade, apt-mark holding various packages
until I found the culprit.
It's either xserver-common, xserver-xorg-core, or xvfb (probably not the
latter).
If I unhold the first two and dist-upgrade, I see the freeze.
** Also affects: xorg-server (Ubuntu)
Importance:
Public bug reported:
dist-upgrade today on a wily VM completely freezes boot. I'm reporting
this against lightdm because it's the last message I see in the console
during boot. I haven't bisected the dist-upgrade yet, but I can verify
that I've seen this on two VMs (running in Fusion on OS X,
blocked on new dependencies).
Speak up now or forever hold your peace. :)
** Affects: python-pip (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: New
** Changed in: python-pip (Ubuntu)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug
** Summary changed:
-
/usr/bin/aa-clickhook:ImportError:/usr/bin/aa-clickhook@14:/usr/lib/python3/dist-packages/apparmor/click.py@15:/usr/lib/python3.4/ctypes/__init__.py@7
+ A file with link count 2 doesn't get both links updated
** No longer affects: click-apparmor (Ubuntu)
** No longer
Well, I fixed the import error but haven't figured out the debsums
(removal of .egg-info file) problem yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324391
Title:
pip 1.5.4 import an invalid
More information on comment #9:
slangasek because of bad handling of hardlinks in the delta generator
slangasek a minimal test case would be to generate a delta between two trees
where a file whose link count is 2 has been updated [15:23]
slangasek and verify that both of the link
FWIW, I fixed this in Debian's 1.5.6-5. I'll work on an SRU to trusty-
updates.
** Changed in: python-pip (Ubuntu Trusty)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: python-pip (Ubuntu)
Status: Triaged = In Progress
** Changed in: python-pip (Ubuntu Trusty
There is a hardware platform - it's called Lenovo. It is built to be
totally compatible with Linux, and sold as a Linux machine in many parts
of the world. AFAIK every Lenovo machine works totally out of the box
with Ubuntu. I just upgraded my Lenovo Netbook from 14.04 to 15.04 and
will shortly
** Changed in: python-lockfile (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/596832
Title:
Karmic version is broken and not usable
To manage notifications
I just sponsored python-lockfile 1:0.10.2-1 into unstable. As soon as
it clears NEW (for the Python 3 packages), I'll syncpackage it over to
wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just sponsored python-lockfile 1:0.10.2-1 into unstable. As soon as
it clears NEW (for the Python 3 packages), I'll syncpackage it over to
wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: client
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367028
Title:
[MIR] system-image
To manage notifications about this bug go to:
I'm marking this as won't fix due to the new policy prohibiting internet
access from DEP-8 based pocket promotion tests. It is my opinion that
DEP-8 format should be preserved for defining integration tests with
external services (which include system-image.u.c) but which are not
tied directly to
discussion
mechanism to allow separate integration tests, which might still use
DEP-8 format but be untied from pocket promotion. Just removing the
stanzas from d/t/control is good enough for now.
** Affects: system-image (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status
** Changed in: system-image (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457070
Title:
Disable DEP-8 smoketests
To manage notifications about
** Tags added: client
** Also affects: ubuntu-system-image
Importance: Undecided
Status: New
** No longer affects: system-image (Ubuntu)
** Changed in: ubuntu-system-image
Status: New = Triaged
** Changed in: ubuntu-system-image
Importance: Undecided = Medium
** Changed
Public bug reported:
On wily with latest apt-get update dist-upgrade I noticed a problem
where after logging in via the lightdm greeter, the full desktop would
not come up. The screen blanks and it appears as if I get my normal
desktop solid background, but the global menu bar never comes up,
** Changed in: system-image (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431696
Title:
Please make ubuntu-download-manager a or dependency for
** Changed in: system-image (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377184
Title:
move archive_master file out of /etc to avoid it being
** Changed in: python-pip (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: python-pip (Ubuntu)
Importance: Undecided = High
** Changed in: python-pip (Ubuntu)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug notification because you are a member
** Changed in: system-image (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431696
Title:
Please make ubuntu-download-manager a or dependency for
** Also affects: ubuntu-system-image
Importance: Undecided
Status: New
** Changed in: ubuntu-system-image
Status: New = Triaged
** Changed in: ubuntu-system-image
Importance: Undecided = Medium
** Changed in: ubuntu-system-image
Milestone: None = 3.1
** No longer
901 - 1000 of 5457 matches
Mail list logo
