** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
Filed bug 1644787 to upgrade initrd package to xenial one. Need some
hacks in initrd touch script.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1641561
Title:
** Merge proposal linked:
https://code.launchpad.net/~vicamo/repowerd/+git/repowerd/+merge/311694
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Vicamo Yang (vicamo)
** Changed in: lxc-android-config (Ubuntu)
Status: New => In Progress
** Changed in: repowerd (
)
Assignee: (unassigned) => Vicamo Yang (vicamo)
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Vicamo Yang (vicamo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
** Branch linked: lp:~vicamo/ubuntu-touch-session/bug-165-depends-
on-android-target
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/165
Title:
avila
** Patch added: "0001-misc-create-var-lib-udisks2-in-post-install.patch"
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1643459/+attachment/4782317/+files/0001-misc-create-var-lib-udisks2-in-post-install.patch
--
You received this bug notification because you are a member of Ubuntu
=> In Progress
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Vicamo Yang (vicamo)
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Public bug reported:
We found devices will take about 80 seconds to show the ubuntu flash UI, and
after about 60 seconds to show the login UI.
So it will take more than 2 minutes to boot up the system.
[[1. on xenial+systemd/arm64]]:
Second boot time:
Without flight mode: 25s to ubuntu splash,
Public bug reported:
/var/tmp: rtkit systemd service uses PrivateTmp
/var/lib/udisks2: udisks2
/var/lib/dhcp: isc-dhcp-server leases files
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: lxc-android-config (Ubuntu)
Importance:
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Vicamo Yang (vicamo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1642535
Ti
It turns out we also need /var/snap for lxd snap, which writes some
global data.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~vicamo/lxc-android-config/lxd-snap-writable-path
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Filed follow-up bug 1642535.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
Status in Canonical System Image:
All known issues in comment 8 addressed, so I think that's all we need
for lxd porting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate
Confirmed installed in ubuntu-touch version 1.264xenial19, or system-
image rev 84. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1638204
Title:
** Also affects: urfkill (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android
Update prebuilt boot.img with current kernel changes in
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
** Attachment added: "boot.img"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4778450/+files/boot.img
--
You received this
audit namespace issue fixed in upstream
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9441639e6319f0c0e12bd63fa2f58990af0a9d2
and
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=33faba7fa7f2288d2f8aaea95958b2c97bf9ebfb
. Already included in
** Branch linked: lp:~vicamo/lxc-android-config/lxd-migration
** Branch unlinked: lp:~vicamo/lxc-android-config/lxd-writable-path
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
AppArmor is not functioning this way Hmmm
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
Status in
Add audit=0 to kernel command line and logd ceases to try kernel audit,
and the rest of the system (lxd/snap) doesn't seem to be affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
Another issue seems to relate to the kernel version again. In logcat
messages I found logd restarts over and over again due to failure when
sending audit netlink messages. It seems lxd fails to setup some
cgroups: cgroups controllers for blkio/memory/network/pids/... not
found.
With some hacking with systemd, now lxd image boots and GUI is
available. Some refinements are needed. Known issues:
1. lxc tries to write client.srt to /root/.config/lxc, which should be
read-only by default. Add --force-local to every lxc command invoked
fixes this issue.
2. Currently I'm
Script to generate android lxd image from /android/system/boot/android-
ramdisk.img
** Attachment removed: "lxd-image-create.sh"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh
** Attachment added: "lxd-image-create.sh"
Current status: with following three lines added to the profile, ueventd
processes devices as usual. But I can't still found any daemon process
with executable located in /system running. /proc/$(pidof init)/mounts
shows /system and all other partitions have been correctly mounted.
** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
Script to generate android lxd image from /android/system/boot/android-
ramdisk.img
** Attachment added: "lxd-image-create.sh"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh
--
You received this bug notification
** Branch linked: lp:~vicamo/lxc-android-config/lxd-writable-path
** Description changed:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc
Prebuilt boot image with
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
applied.
** Merge proposal linked:
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
** Description changed:
Several things to do here:
* include lxd, lxd-client in
Again, the fundermental reason init dies is a critical core service
healthd dies, so it's not really about background/foreground here. And
healthd dies because it fails to open /dev/binder. It follows in lxd,
ueventd is not correctly running yet.
--
You received this bug notification because you
With comment #1 fixed with a patched kernel, it seems we bumped into bug
1625916 again. Need to run lxc in the background.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
Again, avila's kernel is pretty outdated, and its user namespace support
is so poor that it's actually mis-behave on a certain security related
operations.
In security/commoncap.c, function cap_prctl_drop, it should check
`ns_capable(...)`, not just `capable(...)`. See
http://bazaar.launchpad.net/~timo-jyrinki/+junk/uitk-
gallery/view/head:/snapcraft.yaml reference for snappy content
interface.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
With bug 1641549, we're also trying to migrate current lxc-based android
container to lxd image. Snap interface to access lxd is in bug 1634880.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
Public bug reported:
With snapd running in current Ubuntu Touch Xenial port, we'd like to
package whole android container as a snap for the final all-snap target.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: lxc-android-config (Ubuntu)
Public bug reported:
Several things to do here:
* include lxd, lxd-client in default installation,
* writable path for lxd: lxd resides at /var/lib/lxd and it takes write
permission to fully function,
* migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles,
etc.,
* migrate
With the two patches, one may test adbd emergency shell manually by
replacing ExecStart command with `/bin/false` in either lxc-android-
config or lightdm systemd service.
** Branch linked: lp:~vicamo/lxc-android-config/adbd-emergency-shell
** Changed in: android-tools (Ubuntu)
Status:
Patch for source package android-tools to add a systemd ExecStopPost
hook /usr/lib/android-tools-adbd/start-emergency-shell for other
packages.
** Patch added: "0001-Add-adbd-emergency-shell-systemd-support.patch"
: Undecided
Assignee: Vicamo Yang (vicamo)
Status: New
** Affects: lxc-android-config (Ubuntu)
Importance: Undecided
Assignee: Vicamo Yang (vicamo)
Status: New
** Tags: systemd
** Tags added: systemd
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
There is no more work to do for systemd bring up.
For snappy bring up, bug 1632272 and bug 1633367 are still open/waiting
for review.
** Changed in: upstart (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Confirmed included in version 0.230+16.04.20161011-0ubuntu1, rootfs
rev59.
** Changed in: lxc-android-config (Ubuntu)
Status: New => Fix Released
** Changed in: canonical-devices-system-image
Status: New => Fix Released
--
You received this bug notification because you are a
All necessary changes merged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632602
Title:
no adb access under xenial+systemd user build
Status in Canonical
Temp work-arounds have been proposed. Please keep this bug open even if
they're merged later.
** Changed in: android-tools (Ubuntu)
Status: New => In Progress
** Changed in: android-tools (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need
** Tags added: snappy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
Status in Canonical System Image:
After some discussion, we can also enable "ro.debuggable=1" in user
builds temporarily and revert it when all is ready.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
However, like what we've have for eng build, one may simply hook
android-tools-adbd service to another valid property under user build,
e.g. "ro.build.type=user".
device# cd /ubuntu/etc/systemd/system
device# mkdir android-contai...@ro.build.type\\x3duser.target.wants
device# cd
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
Public bug reported:
It seems there is still some problems in the systemd/upstart mix
environment. So far running upstart-local-bridge in foreground mode
stablize this a lot.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects:
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila. Following steps are based on rootfs rev
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
- working xenial+upstart avila.
+ working xenial+upstart avila.
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila.
2. Install systemd-sysv rather
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila.
2. Install systemd-sysv rather
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila.
2. Install systemd-sysv rather
** Attachment removed:
"android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb
** Description changed:
** Attachment added: "ubuntu-touch_1.264xenial17+systemd_arm64.deb"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4751598/+files/ubuntu-touch_1.264xenial17+systemd_arm64.deb
** Attachment removed: "ubuntu-touch_1.264xenial13+systemd_arm64.deb"
Add prebuilt lxc-android-config package with mp
https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-
bridge, https://code.launchpad.net/~vicamo/lxc-android-config/disable-
systemd-alsa-restore/+merge/306587, https://code.launchpad.net/~vicamo
Add prebuilt package with
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001
-install-systemd-service-files.patch applied.
** Attachment added:
"android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb"
Prebuilt package with https://code.launchpad.net/~vicamo/upstart/xenial-
escape-systemd-strings applied.
** Attachment added: "upstart_1.13.2-0ubuntu21.1_arm64.deb"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751437/+files/upstart_1.13.2-0ubuntu21.1_arm64.deb
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila.
2. Install systemd-sysv rather
Prebuilt upstart-local-bridge binary from version 1.13.2-0ubuntu21.1
** Attachment added: "upstart-local-bridge"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750793/+files/upstart-local-bridge
--
You received this bug notification because you are a member of
** Patch added: "0001-install-systemd-service-files.patch"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working xenial+upstart avila.
2. Install systemd-sysv rather
Patch for android-tools to enable adbd in eng build at boot.
** Branch linked: lp:~vicamo/lxc-android-config/add-upstart-local-bridge
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
** Branch linked: lp:~vicamo/upstart/xenial-escape-systemd-strings
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1627613
Title:
enable android adbd properly
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1627613
Title:
enable android adbd
** Description changed:
Currently android adbd has no systemd service file and the mechanism for
related parts like usb state and mtp is void.
+
+ TODO: document
+
https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty
--
You received this bug
Filed bug 1627613 to track adbd stuff separately.
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1]. This should gives a
working
"upstart-local-bridge[930]: Unit name
android-contai...@persist.sys.usb.config\x3d,adb.target is not valid."
So from systemd source, the allowed unit name is:
#define VALID_CHARS DIGITS LETTERS ":-_.\\"
upstart-local-bridge translates the event (name,value) pair to a unit
name that doesn't
Public bug reported:
Currently android adbd has no systemd service file and the mechanism for
related parts like usb state and mtp is void.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: android-tools (Ubuntu)
Importance: Undecided
Prebuilt lxc-android-config that integrates
https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-
paths/+merge/306184 for bug 1625445, https://code.launchpad.net/~vicamo
/lxc-android-config/fix-systemd-service-startup/+merge/306435 for bug
1625916, and
** Attachment removed:
"lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb"
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb
--
You received this bug notification because you
** Branch linked: lp:~vicamo/lxc-android-config/disable-systemd-alsa-
restore
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc-android-config (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
- 1. flash images built from xenial branch [1] (need manually checkout
- xenial branch in kernel-3.10/ before
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
1. flash images built from xenial branch [1] (need manually checkout
xenial branch in kernel-3.10/ before
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1625023
Title:
switch to
** Changed in: lxc-android-config (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1625916
Title:
android init exits
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
[steps to construct systemd-based avila]
- 1. flash images built from xenial branch [1] . This should gives a
- working xenial+upstart avila.
+ 1. flash images built from xenial
** Description changed:
Snappy heavily rely on systemd system session and xenial has systemd by
default.
+
+ [steps to construct systemd-based avila]
+
+ 1. flash images built from xenial branch [1] . This should gives a
+ working xenial+upstart avila.
+
+ 2. Install systemd-sysv rather
Patch used to compile android-tools with systemd support. Note this is
currently a dirty hack to enable adbd unconditionally at boot.
** Patch added: "force-adbd.patch"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch
--
You
Prebuilt lxc-android-config deb that contains
https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-
service-startup/+merge/306435 for bug 1625916, and
https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-
paths/+merge/306184 for bug 1625445.
** Attachment added:
** Branch linked: lp:~vicamo/lxc-android-config/fix-systemd-service-
startup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1625916
Title:
android init exits
** Also affects: android-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: android-tools (Ubuntu)
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Kernel changes in
https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/306307
, maybe we need another branch for xenial+systemd?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
Prebuilt adbd package that installs systemd service and starts up at
early boot stage.
** Attachment added:
"android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb"
It seems there is no repository to land changes for ubuntu-touch-mate
package, so here is the patch for manual landing.
** Patch added: "ubuntu-touch-meta.patch"
** Also affects: android-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1625023
Title:
switch to
Differences between list of packages install upstart and/or systemd
service files:
# diff -Nu /tmp/upstart-packages.list /tmp/systemd-packages.
--- /tmp/upstart-packages.list 2016-09-19 05:55:03.849426548 +
+++ /tmp/systemd-packages.list 2016-09-19 05:56:15.139426552 +
@@ -1,80 +1,40 @@
Append debian build version so that it doesn't confuse dpkg.
** Attachment added: "ubuntu-touch_1.264xenial13+systemd_arm64.deb"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743481/+files/ubuntu-touch_1.264xenial13+systemd_arm64.deb
** Attachment
Prebuilt ubuntu-touch meta package that depends on systemd-sysv instead.
** Attachment added: "ubuntu-touch_1.264xenial13_arm64.deb"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743479/+files/ubuntu-touch_1.264xenial13_arm64.deb
--
You received this
BTW, I have location-service rebuilt for bug 1618412. The GPS works on
avila. No crash found then. I think it suggests there might be some ABI
change in libdbus-cpp recently, so packages linked to libdbus-cpp might
need a rebuild then.
--
You received this bug notification because you are a
mtp-server rebuilt against latest libdbus-cpp. Verified on GNOME*, no
mtp-server crash, file operations work just fine.
[1]: there seems to be some unresolved issue in kio-mtp:
https://bugs.kde.org/show_bug.cgi?id=318980
** Attachment added: "mtp-server_0.0.4+16.04.20160413-0ubuntu2_arm64.deb"
libmtpserver1 rebuilt against latest libdbus-cpp.
** Attachment added: "libmtpserver1_0.0.4+16.04.20160413-0ubuntu2_arm64.deb"
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1618390/+attachment/4732672/+files/libmtpserver1_0.0.4+16.04.20160413-0ubuntu2_arm64.deb
** Bug watch
Hi, for the mtp-server crash, I found the mtp-server binary package
(version 0.0.4+16.04.20160413-0ubuntu2) was built against an previous
libdbus-cpp version, and a no-change rebuild against current libdbus-cpp
(version 5.0.0+16.04.20160809-0ubuntu1) then mtp-server crash happens no
more.
--
You
1 - 100 of 111 matches
Mail list logo
