) => Barry Warsaw (barry)
** Also affects: gedit (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-builder (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gtranslator (Ubuntu)
Importance: Undecided
Status: New
** Also affects: life
** Changed in: pytest (Ubuntu)
Status: In Progress => 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/1545586
Title:
regression: python3-pytest doesn't contain pytest module
To
I'm having a difficult time figuring out a good test for
ForceAllowGSMDownload(). I already have DownloadStarted() working and
tested, but the former is giving me some pause.
Is it possible to set UDM into a mode where it thinks it's only on GSM?
What I think I'd like to do is invoke UDM in this
** No longer affects: pytest (Debian)
** Bug watch added: Debian Bug tracker #814834
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814834
** Also affects: pytest (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814834
Importance: Unknown
Status: Unknown
--
You
On Feb 15, 2016, at 05:34 AM, Logan Rosen wrote:
>Looks like the culprit is line 37 of debian/rules, in the
>override_dh_auto_install block:
>rm -rf debian/python3-pytest/usr/lib/python3.5
That line needs to go away... again, and Sebastian needs to find a different
way to fix the problem
** Bug watch added: Debian Bug tracker #814571
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814571
** Also affects: python-pip (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814571
Importance: Unknown
Status: Unknown
--
You received this bug notification
One other thing to remember: we probably want a cli switch to also
override allowGSM, though there we won't need to set that on an existing
group download since si-cli blocks while a download is happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm going to call the signal DownloadStarted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508081
Title:
Fails to receive OTA updates
To manage notifications about this bug go to:
** Changed in: ubuntu-system-image
Status: New => In Progress
** Changed in: ubuntu-system-image
Importance: Undecided => High
** Changed in: ubuntu-system-image
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: ubuntu-system-image
Milestone: None =>
** 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/1508081
Title:
Fails to receive OTA updates
To manage notifications about this bug go to:
So, for the si dbus client we'll:
* Add a Started() signal which just proxies through from UDM.
* Add a ForceAllowGSMDownload() method (no argument), which when called
will forward to UDM's current group download's allowGSMDownload(True).
If there is no download in progress, it will no-op. It
** Changed in: apt-xapian-index (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541407
Title:
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538198
Of course, running sbuild with any chroot spews *tons* of these errors,
so it's fairly annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535416
Title:
Failed to connect to socket
Public bug reported:
Since a recent Xenial dist-upgrade, schroot spews dbus errors, but
doesn't seem to affect operation.
% schroot -u root -c xenial-amd64
Failed opening dbus connection: org.freedesktop.DBus.Error.FileNotFound: Failed
to connect to socket /sys/fs/cgroup/cgmanager/sock: No such
@seb128: Yes, you're right of course. From here on I'll follow up on
the Debian bug. Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440504
Title:
libpeas-1.0-0 depends on both
So maybe this isn't as difficult as I first thought. The basic idea is
that instead of putting both the libpythonloader and libpython3loader
shared libs in the same binary package, I'm creating two new binary
packages libpeas-1.0-0-python2loader and libpeas-1.0-0-python3loader.
Each of this
** Patch added: "lp1440504.diff"
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1440504/+attachment/4549490/+files/lp1440504.diff
** Changed in: libpeas (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
FWIW, instrumenting cython's asyncio_generators.srctree file to show
both events and expected at the failing assertion, we see:
End-to-end asyncio_generators ...
/home/barry/projects/debian/cython/upstream/.tox/py35/bin/python
test_async_def_future.py
Traceback (most recent call last):
File
xnox's posting (still no responses):
https://mail.python.org/pipermail/cython-devel/2015-December/004630.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526613
Title:
ftbfs asyncio test
Since ~foundations-bugs subscribes to pylint, I made that team also
subscribe to lazy-object-proxy. I'll look into the Debian packaging to
see if we can get it to run its tests.
** Changed in: lazy-object-proxy (Ubuntu)
Status: Incomplete => New
** Changed in: lazy-object-proxy (Ubuntu)
The underlying bug has been reported upstream:
http://trac.xapian.org/ticket/703
** Bug watch added: trac.xapian.org/ #703
http://trac.xapian.org/ticket/703
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think it's current unfeasible to run the package's test suite at build
time since at least pytest-benchmark is not yet available in
Debian/Ubuntu. Can we not block this MIR on that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We're seeing crashes in /usr/sbin/update-apt-xapian-index on 32bit
Xenial machines since the switch to Python 3. There's a sizes.py plugin
that tries to record the installed and package size on the document
describing the package. astrometry-data-2mass-00 has an installed
gs in Xapian, which I will report upstream. For
now, in discussion with @cyphermox, it was decided that we'll catch the
exception and treat the values as == -1, which the code already handles
and declines to add the size for.
** Affects: apt-xapian-index (Ubuntu)
Importance: High
Assignee
nce: Undecided => High
** Changed in: xapian1.3-bindings (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527745
Title:
plugin/sizes.py cras
If you run synaptic a second time, or run `sudo /usr/sbin/update-apt-
xapian-index` from the command line, do you still get the exception?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526267
Title:
"spawn_helper"
+ Traceback from update-apt-xapian-index
** Changed in: apt-xapian-index (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Description changed:
- xenial install
-
- get that crash, but apport fails to report it; so i join the crash file
- here to ge
Reproducer:
sudo /usr/sbin/update-apt-xapian-index --force --update
I know what the bug is.
** Changed in: apt-xapian-index (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Dec 16, 2015, at 11:07 AM, Iain Lane wrote:
Thanks for fixing the other binary open. I saw that while I was testing but
forgot to come back to it.
>laney@raleigh> sudo PYTHONDONTWRITEBYTECODE=1
>/usr/sbin/update-apt-xapian-index --force --quiet
>Exception ignored in: >
>Traceback (most
This is gonna be fun. software-center needs some bilingual support even
if it's going away in 16.04 and even though it was once ported to Python
3. :( Stay tuned.
** Changed in: apt-xapian-index (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
This actually isn't caused by a-x-i, so I'm going to remove its bug
task. (It did reveal a minor unrelated bug in a-x-i for which I'll
upload a fix though.)
I have a patch for s-c that I need to do just a little more testing on.
** No longer affects: apt-xapian-index (Ubuntu)
--
You received
rtance: Undecided => High
** Changed in: software-center (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526450
Title:
/usr/sbi
** Branch linked: lp:~barry/software-center/lp1526450
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526450
Title:
/usr/sbin/update-apt-xapian-index:ImportError:/usr/sbin/update-apt-
xapian-
** Changed in: gtimelog (Ubuntu)
Status: In Progress => 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/1309428
Title:
Wrong icon path in desktop file
To manage notifications
@mterry: This was marked Fix Committed, but xapian1.3-bindings is still
in universe, and it's still blocking apt-xapian-index. What more needs
to be done to transition this to main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is a problem with setuptools 18.7 and should be fixed by 18.7.1,
which Doko is in the process of uploading to unstable.
** No longer affects: system-image (Ubuntu)
** Changed in: python-setuptools (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
--
You received this bug
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.
**
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.
**
To be clear `virtualenv ` will create a Python 2.7 virtualenv, and
this works fine.
Use `virtualenv -p python3.4 ` to trigger the described failure,
which I've been able to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's what's going on. Keep in mind, that post-Trusty this was all
sorted out but backporting the fixes to Trusty will not be easy or
quick.
In Trusty, virtualenv vendorizes pip, which vendorizes requests, which
vendorizes urllib3. It's the three-layers down vendored urllib3 that
would need
** Changed in: python-virtualenv (Ubuntu)
Status: In Progress => 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/1522500
Title:
pip in Python 3.4 virtualenvs cannot install using a
I just uploaded 0.10.0-1 to Debian with the fix. Should sync to Ubuntu
and close this bug soon.
** Also affects: gtimelog (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807047
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Changed in: gtimelog (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/983446
Title:
Test suite fails during build
To manage notifications
** Changed in: python-virtualenv (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: python-virtualenv (Ubuntu)
Status: New => In Progress
** Changed in: python-virtualenv (Ubuntu)
Importance: Undecided => High
--
You received this bug notification be
Public bug reported:
dist-upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 228-2ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu1
Architecture: amd64
Date: Thu Dec
Public bug reported:
dist-upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu1
Architecture: amd64
Date: Thu Dec
This isn't a bug in system-image; I've been seeing this traceback in
other contexts but now that this has been reported here I'll have to dig
into it in more detail. FTR, I found it while working on dirtbike, the
test suite of which manipulates packages in a chroot. What I discovered
there is
: New => In Progress
** Changed in: pyyaml (Ubuntu)
Importance: Undecided => High
** Changed in: pyyaml (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Why are you using toolchain-r? Are you sure that's where your getting
your libpython2.7-minimal from for trusty?
https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/test?field.series_filter=trusty
This problem doesn't happen in a clean trusty chroot.
--
You received this bug
** Bug watch added: Debian Bug tracker #806824
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806824
** Also affects: libpeas (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806824
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I'll note that this is less critical now that deja-dup installs
duplicity on demand. Still, it would be nice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440372
Title:
please port duplicity to
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 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
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
It builds for me locally in a Xenial sbuild, and in my PPA:
https://launchpad.net/~barry/+archive/ubuntu/experimental/+packages
Odd that it doesn't build for you. Can you post the build log?
** Changed in: xapian1.3-core (Ubuntu)
Status: Incomplete => New
--
You received this bug
This was fixed in deja-dup 34.1-0ubuntu1, although the dependency
through libpeas (LP: #1440504) keeps a dep to libpython2.7
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
With deja-dup 34.1-0ubuntu1, the tight dependency on Python 2 has been
fixed. deja-dup only recommends duplicity and will install it on
demand. However deja-dup still depends on libpeas-1.0-0 and that pulls
in libpython2.7, so i think that's another package that needs the
libpeas split.
Any
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
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
On Nov 27, 2015, at 01:38 PM, Michael Terry wrote:
>Gotcha. Why not just update the existing xapian packages to 1.3? Does
>1.3 break compatibility?
I think Doko packaged these up separately just to be cautious and allow a
staged migration path.
--
You received this bug notification because
See LP: #1519890
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519887
Title:
[MIR] xapian1.3-bindings
To manage notifications about this bug go to:
Public bug reported:
[Rationale]
See LP: #1519887 - similar considerations apply here. We need to MIR
xapian1.3-core so that xapian1.3-bindings can be MIR'd.
** Affects: xapian1.3-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
[Availability]
xapian1.3-bindings is already in universe.
[Rationale]
python3-xapian1.3 needs to be included in main since the upload of
apt-xapian-index 0.47ubuntu3 because this version switches to Python 3 as part
of the "get Python 2 off the default images" initiative
Oops, I actually did add a bug subscriber but accidentally did a
personal one instead of the team. I've fixed that for
xapian1.3-bindings and xapian1.3-core now.
I don't think Debian will follow us here. The timing should allow
Debian to adopt Xapian 1.4 sometime farther along the Stretch
** Changed in: xapian1.3-bindings (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519887
Title:
[MIR] xapian1.3-bindings
To manage notifications about this
If the log file (or system-image-cli -vv) ends with "Running group
download reactor" it basically means that s-i has told udm to download a
bunch of files, and it's waiting for the D-Bus signals indicating
successful completion or failure. Since we're not seeing either of
those, s-i will just sit
*** This bug is a duplicate of bug 1518023 ***
https://bugs.launchpad.net/bugs/1518023
** This bug has been marked a duplicate of bug 1518023
pip3 installs under python3.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I guess you're asking for a logrotate.d entry for /var/log/system-
image/client.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518955
Title:
System image client log file grows indefinitely
To
** 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/1518955
Title:
System image client log file grows indefinitely
To manage notifications about this bug go to:
ects: python-pip (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: python-pip (Ubuntu Wily)
Status: New => Confirmed
** Changed in: python-pip (Ubuntu Wily)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: python-pip (Ubuntu Wily)
Milestone
Well, that's very interesting. I just built the source package on Wily
and pip3's shebang is /usr/bin/python3. I'll do a bit more testing but
maybe it just needs a no-change rebuild in Wily?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have a fix. Prepping SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518023
Title:
pip3 installs under python3.5
To manage notifications about this bug go to:
The fix is to force `dh_python3 --shebang /usr/bin/python3` in d/rules.
** Also affects: python-pip (Ubuntu Xenial)
Importance: Undecided
Assignee: Barry Warsaw (barry)
Status: Confirmed
** Changed in: python-pip (Ubuntu Xenial)
Milestone: wily-updates => ubuntu-16
Public bug reported:
Even though most people won't ever install system-image from deb, and
even though flashing a device containing system-image will create the
directory, the .deb should ensure that /etc/system-image/config.d
exists.
** Affects: system-image (Ubuntu)
Importance: Undecided
I have two branches which I've submitted to the maintainers. The first
makes a-x-i bilingual so it should be a low-impact branch to apply in
Debian:
http://anonscm.debian.org/cgit/collab-maint/apt-xapian-
index.git/log/?h=bilingual
The second flips the switch to Python 3 so if the above branch
Two things: at the last UOS it was decided that software-center is going
to be dropped from Xenial. We have a TODO in the blueprint but as yet
no one assigned to this:
https://blueprints.launchpad.net/ubuntu/+spec/foundations-x-python3-only
Also, oneconf-common should drop its python-*
is relatively small,
and my second branch does this.
** Affects: apt-xapian-index (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: In Progress
** Tags: python3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: python3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427275
Title:
clean cloud images of python2
To manage notifications about this bug go to:
Oh wow, Launchpad just stopped sending me emails on this issue and I got
side tracked on some changes to system-image that I thought might help
debug the problem. At least it looks like y'all have some good leads on
the root cause though.
--
You received this bug notification because you are a
Just tested with Xenial server, with no additional packages installed.
vim is the last thing keeping libpython2.7 on the server image. Verify
with `apt-get purge python2.7 libpython2.7`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
dist-upgrade from wily to xenial
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
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.2-0ubuntu4
Architecture:
Does the linked branch actually fix the Python 3 bug? I don't see it in
the merge proposal diff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512909
Title:
Port unity to Python 3
To manage
Probably should be duped with LP: #1512498
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513113
Title:
name to icon matching for Terminal broken in xenial
To manage notifications about this bug
Probably should be duped with LP: #1513113
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512498
Title:
gnome-terminal thinks it's Byobu Terminal
To manage notifications about this bug go to:
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
Public bug reported:
Rationale
python{,3}-hypothesis is a new build dependency for python-cryptography,
which is already in main. python-hypothesis has no known violations of
the Main Inclusion Requirements. The source package has no open bugs
in Debian or Ubuntu. Upstream seems to
Also, system-image 3.0.2 is now in both touch and snappy. Do we need
to do anything else for this MIR?
--
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
On Nov 03, 2015, at 05:41 PM, Eduard Bloch wrote:
>I have no idea.
Yeah, I was sitting next to pitti and he was also perplexed! (He also wasn't
able to reproduce it.)
>What's the UID of that user? Maybe something messed up with your passwd
file?
Nope, passwd looks okay. I can't see anything
Subscribed ~foundations-bugs
** Changed in: python-hypothesis (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512758
Title:
[MIR] python-hypothesis
To
Public bug reported:
We're dropping Python 2.7 from the default installs so unity must be
ported to Python 3. It actually might be fairly easy, since I think
/usr/bin/unity might be the only actual Python 2 script and I think it
will run on Python 3. I'm doing a test build now to see if that's
Here's my diff so far. I tried to build this locally but the build
segfaulted, so I'll try in a PPA tomorrow.
** Patch added: "1512909.diff"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1512909/+attachment/4512461/+files/1512909.diff
--
You received this bug notification because
** Description changed:
- Rationale
-
+ [Availability]
+
+ Already available in universe.
+
+ [Rationale]
python{,3}-hypothesis is a new build dependency for python-cryptography,
which is already in main. python-hypothesis has no known violations of
- the Main Inclusion
Public bug reported:
Up-to-date xenial, `apt-get install apt-cacher-ng` produces:
Preparing to unpack .../apt-cacher-ng_0.8.6-1_amd64.deb ...
Unpacking apt-cacher-ng (0.8.6-1) ...
Processing triggers for doc-base (0.10.6) ...
Processing 1 added doc-base file...
Processing triggers for man-db
Fixing the user and group ownership fixes the problem:
% ls -ld /var/log/apt-cacher-ng/
drwxr-sr-x 2 apt-cacher-ng apt-cacher-ng 4096 Nov 3 10:40
/var/log/apt-cacher-ng//
So why did it use usermetrics:systemd-journal ??
apt-cacher-ng has never been installed on this box before.
--
You
Public bug reported:
After dist-upgrading from Wily to Xenial, gnome-terminal has a global
menu bar entry, and switcher icon of Byobu Terminal. This is regardless
of whether I start Terminal via gnome-do, unity (search or sidebar), or
Emacs shell buffer typing 'gnome-terminal'. Other than that,
the exception and continue trying other shortcut handlers.
** Affects: software-properties (Ubuntu)
Importance: High
Assignee: Barry Warsaw (barry)
Status: In Progress
** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-16.04
** Changed in: softw
** Changed in: software-properties (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/1510558
Title:
ppa shortcut handler exception stops shortcut
301 - 400 of 3287 matches
Mail list logo
