This is perfectly reproducible on a pristine zesty cloud image in a VM
after installing and configuring lxd first, then juju-2.0.
I also tried on a pristine xenial cloud VM, and I don't even get that
far:
$ juju-2.0 bootstrap lxd localhost
Creating Juju controller "lxd" on localhost/localhost
Bo
As a data point, I was doing the same last week in zesty, and it worked
perfectly. Also juju-core itself did not change since then (it's the
same version as in yakkety), so something underneath it broke.
I confirmed this bug with 2.0 final in zesty-proposed, same behaviour.
** Also affects: juju-
Public bug reported:
In current zesty, "juju-2.0 bootstrap lxd localhost" does:
Creating Juju controller "lxd" on localhost/localhost
Looking for packaged Juju agent version 2.0-rc3 for amd64
Launching controller instance(s) on localhost/localhost...
- juju-5fc6db-0
Fetching Juju GUI 2.2.3
Waiti
I suppose you want this for yakkety too, so backported:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-yakkety&id=648c659e9
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as ne
Xenial fixes:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=aeff48d716
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=310753a6
** Changed in: systemd (Ubuntu Xenial)
Status: Triaged => In Progress
--
You recei
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as networking is not yet
available when cloud-init.service runs.
cloud-init service unit deps look like this:
[Unit]
Description=Initial cloud-
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as networking is not yet
available when cloud-init.service runs.
cloud-init service unit deps look like this:
[Unit]
Description=Initial cloud-
Thanks Po-Hsu. This is clearly a bug within test-snapd-tools, possibly
fixed by bug 1641243. Is there a simpler "hello world" type snap that
has a service that can be used to verify this without running into the
apparmor profile issue?
Steps 7 to 9 can be done independently.
--
You received this
I just landed the last PR (https://github.com/systemd/systemd/pull/4710)
in upstreamd master that fully fixes networkd for early boot. The
complete set is too intrusive to backport, but we don't need to in
xenial: Transient (DHCP-acquired) hostname and timezone have never
worked in xenial, and it s
** Description changed:
- Hello,
+ The current packaged systemd for Yakkety does not have the Mellanox
+ netdev udev naming set for systemd patch installed
+ (https://github.com/systemd/systemd/commit/4887b656c22). The current
+ version for zesty does. I installed the ppa for this on to my Yakkety
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Will, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help us
Hello Rafael, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Kyle, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help us
Can you please add a test case? I. e. how does the naming currently
look, and how is it supposed to look with the patch?
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd
Not much that we can do about the conffile prompt indeed. However, I
disagree with the actual patch. This should include
abstractions/nameservice instead, which allows these files plus a lot
more for other name service methods. We really want to avoid having to
SRU a conffile change twice, and this
How can we ensure that this does not break existing 16.04 installs (with
or without HWE)? Please add a test plan that covers at least the most
widespread hardware (Intel, Nvidia, fglrx, free/proprietary drivers) and
an overview of the regression potential based on the changes in the new
libdrm vers
Hello Su, or anyone else affected,
Accepted gcin into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gcin/2.8.4+dfsg1-1ubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Mathieu, or anyone else affected,
Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Martin, or anyone else affected,
Accepted util-linux into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.20.1-5.1ubuntu20.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
+except OSError as e:
+if e.errno == 5:
+pass
This check makes little sense -- if errno is 5 or something else, the
exception is ignored in both cases. So just
except OSError:
pass
is sufficient IMHO --
@Eric: Right, that's what I meant. It should be mitigated by that recent
cloud-init reorganization, but even if snapd.boot-ok.service now stopped
failing on upgrade I still think it does not make sense to run this on
package upgrade, only on boot.
--
You received this bug notification because you
https://cgit.freedesktop.org/udisks/commit/?id=e168e59f
https://cgit.freedesktop.org/udisks/commit/?id=554daa4b
I tried this with an USB stick; I do get the wipefs failure pretty
consistently, and with this creating the partition and FS seems to work
reliably. I think we ought to SRU this into xen
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460602
Title:
Erasing disk failed: Error wiping newly created partition
To manage notifications a
Massaged a bit and pushed to trusty packaging branch:
https://git.launchpad.net/~ubuntu-core-dev/+git/systemd-
trusty/commit/?id=9577cf48
** Changed in: systemd (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562344
Title:
Not working hotkeys for brightness in HP ProBook 640
Comitted to trusty packaging git: https://git.launchpad.net/~ubuntu-
core-dev/+git/systemd-trusty/commit/?id=482827
Note that there is a current SRU in trusty which blocks this. But this
being "wishlist" it's not that urgent anyway, and my gut feeling is that
it's okay to wait a bit until we get s
Applied to xenial packaging branch, with similar small noise:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial&id=71a4b81ffc
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of
snapd-glib accepted into xenial. Please upload the corresponding gnome-
software SRU.
** Changed in: snapd-glib (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Applied to yakkety packaging branch, with some reformatting (gbp pq and
using gbp dch): :https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-yakkety&id=9b4f59ff766d36
** Changed in: systemd (Ubuntu Yakkety)
Importance: Undecided => Wishlist
** Changed in: systemd (Ubuntu
> [Regression Potential]
> None.
This is a vast underestimate -- touching udev rules can lead to an
unbootable system in the worst case :-) I'll adjust the description.
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/1636912
Title:
systemd-networkd runs too late for cloud-init.service (net)
To man
** Changed in: lightdm (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/1637758
Title:
lightdm greeter session not properly shut down at login
To m
The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
The version of apt-btrfs-snapshot in the proposed pocket of Xenial that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Status: Fix
The version of apt-btrfs-snapshot in the proposed pocket of Xenial that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
--
You received this bug notification because you are a member of Ub
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for pulseaudio has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
The version of apt-btrfs-snapshot in the proposed pocket of Xenial that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Status: Fix
The version of apt-btrfs-snapshot in the proposed pocket of Xenial that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
--
You received this bug notification because you are a member of Ub
The version of apt-btrfs-snapshot in the proposed pocket of Xenial that
was purported to fix this bug report has been removed because the bugs
that were to be fixed by the upload were not verified in a timely (105
days) fashion.
--
You received this bug notification because you are a member of Ub
The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubunt
The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: indicator-power (Ubuntu Xenial)
Status: Fix Commit
** Changed in: pulseaudio (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/1574324
Title:
pulseaudio crashes when connecting to bluetooth headphones
The verification of the Stable Release Update for pulseaudio has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
Comment #123 provided verification in yakkety.
** Tags removed: verification-done-xenial verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574324
Tit
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: libvirt (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: bcmwl (Ubuntu Precise)
Status: New => Won't Fix
--
You re
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs
The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs
The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: lvm2 (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The version of duplicity in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: duplicity (Ubuntu Trusty)
Status: Fix Committed => Won't
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The version of lvm2 in the proposed pocket of Trusty that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: libvirt (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This SRU got removed due to the failed verification of bug 1536008, and
is generally stalled. At this point 14.04 is old enough that actual
users who encounter this will either have learned how to live with this
or moved to 16.04 LTS. Thus "wontfix".
** Changed in: multipath-tools (Ubuntu Trusty)
The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: bcmwl (Ubuntu Precise)
Status: Fix Committed => Won't Fix
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Tags removed: verification-needed
--
You received this bug notification bec
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: libvirt (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Also affects: bcmwl (Ubuntu Precise)
Importance: Undecided
Status: N
The version of libvirt in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member of
The version of walinuxagent in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
B
The version of parted in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
The version of apache2 in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: apache2 (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
The version of apache2 in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member of
The version of parted in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: parted (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member of
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member of
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member of
The version of virtuoso-opensource in the proposed pocket of Precise
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
** Changed in: virtuoso-opensource (Ubuntu Precise)
Status:
The version of librarian-puppet-simple in the proposed pocket of Xenial
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
--
You received this bug notification because you are a member
The version of walinuxagent in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: walinuxagent (Ubuntu Trusty)
Status: Fix Committed =>
The version of librarian-puppet-simple in the proposed pocket of Xenial
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.
** Changed in: librarian-puppet-simple (Ubuntu Xenial)
St
The version of golang-1.6 in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bug
The version of golang-1.6 in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Bug
The version of fusionforge in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: fusionforge (Ubuntu Xenial)
Status: Fix Committed => W
The version of golang-1.6 in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: golang-1.6 (Ubuntu Trusty)
Status: Fix Committed => Won
The version of fusionforge in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Tags removed: verification-needed
--
You received this bug notification
The python-virtualenv test regression is bug 1626201, thus unrelated to
this update. Releasing SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626258
Title:
[SRU] AttributeError: 'Requirement' o
> http://kernel.ubuntu.com/~jsalisbury/lp1626436/yakkety-proposed-
patched
This is a GOOD kernel as well -- booting is almost as fast as with 4.4,
and the load doesn't explode under sbuild either.
I'm a bit confused now, I thought we already tried the two patches in
isolation -- but I think *only
Uploaded and forwarded to Debian. I CC'ed you, but your email address in
the patch is wrong, so it bounced. I fixed the typo in the actual Ubuntu
upload, though. Thanks!
** Bug watch added: Debian Bug tracker #844720
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844720
** Also affects: xfce
Hello Su, or anyone else affected,
Accepted gcin into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gcin/2.8.4+dfsg1-9build1~1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Chuck, or anyone else affected,
Accepted nova-lxd into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/nova-
lxd/14.0.1-0ubuntu0.16.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello Lutz, or anyone else affected,
Accepted ark into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ark/4:16.04.3a-
0ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Mathieu, or anyone else affected,
Accepted livecd-rootfs into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.435.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Thanks for the patch! I forwarded it to the Debian maintainer and linked
the Debian bug here. Please understand that it's too costly to apply
such "minor" patches in Ubuntu as that would introduce a delta to the
package which then blocks automatic updates from Debian. So I won't
upload this to Ubun
Sponsored, thanks!
** Changed in: liblouisutdml (Ubuntu)
Status: New => 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/1639105
Title:
Rebuild for liblouis transition
To manage
I don't see anythign left to sponsor here, so unsubscribing sponsors
now. Please re-subscribe when you upload further patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
Mouse curs
bug 1633479 actually was released to -updates now, so is there still
actually some observable behaviour difference that can be used to both
justify and verify this update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Closing for now as there hasn't been a response in several months.
Please reopen if you still want to go ahead with this as an SRU, and
then please add a test case and a regression potential analysis.
** Changed in: upstart (Ubuntu Trusty)
Status: Incomplete => Won't Fix
--
You received t
I actually can't see it anywhere in the New, Unapproved, or Rejected
queues.
** Changed in: ubuntu
Status: Fix Committed => 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/1607546
Ti
401 - 500 of 52613 matches
Mail list logo
