[Group.of.nepali.translators] [Bug 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine
** Changed in: snapd (Ubuntu Xenial) Status: Fix Released => Confirmed ** Changed in: snapd (Ubuntu Zesty) Status: Fix Released => Confirmed ** Changed in: dpkg (Ubuntu Trusty) Status: Fix Released => Confirmed ** Changed in: dpkg (Ubuntu Xenial) Status: Fix Released => Confirmed ** Changed in: dpkg (Ubuntu Zesty) Status: Fix Released => Confirmed ** Changed in: snapd (Ubuntu Yakkety) Status: Fix Released => Invalid ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Michael Vogt (mvo) ** Changed in: dpkg (Ubuntu Yakkety) Status: Fix Released => Invalid ** Changed in: snapd (Ubuntu) Status: Fix Released => In Progress ** Changed in: dpkg (Ubuntu) Status: Fix Released => In Progress ** Changed in: snapd (Ubuntu Trusty) Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1673247 Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 Status in snapd: Won't Fix Status in dpkg package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in dpkg source package in Trusty: Confirmed Status in snapd source package in Trusty: In Progress Status in dpkg source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Status in dpkg source package in Yakkety: Invalid Status in snapd source package in Yakkety: Invalid Status in dpkg source package in Zesty: Confirmed Status in snapd source package in Zesty: Confirmed Bug description: When the ubuntu installer runs it has an option to download updates during the install. When this happens snapd/snap-confine 2.22.6 are installed on /target. The upgrade brings in snapd/snap-confine 2.23.1 which has a conffile in /etc/apparmor.d/usr.lib.snapd.snap-confine. The snapd packages declares a breaks/replaces: snapd-confine (<< 2.23) which works correctly on regular upgrades. However it does fail on upgrades with the "--root=/target" that is used by ubiquity. After a bit of debugging it turns out the reason is that src/archives.c:tarobject() has a check for obsolete conffiles in the block around "Is the file an obsolete conffile ...". There is a stat() here that checks that the conff->name and the fnamevb are the same file. This check fails to take the instdir into account and therefore the loop does not continue but falls through to the "does_replace()" checks. Snap 2.23.1 fails to upgrade from 2.21. Known facts: - reporters (and apport) indicate it fails during the install via the live-cd - not reproducible so far on an already installed system - breaks/replaces of snapd are correct - When adding "xenial-proposed" to apt-setup in ubiquity and installing Cause: - when ubiquity runs it uses "dpkg --root=/target --unpack ..." - however when doing the conffile checking dpkg does not handle the "--root" parameter correctly and checks something against "/" instead of "/target". - I really don't know what else to add... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: snapd 2.23.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Wed Mar 15 16:03:33 2017 DuplicateSignature: package:snapd:2.23.1 Unpacking snapd (2.23.1) over (2.21) ... dpkg: error processing archive /target/var/cache/apt/archives/snapd_2.23.1_amd64.deb (--unpack): trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 ErrorMessage: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: snapd Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1673247/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Changed in: compiz (Ubuntu) Status: Fix Released => Confirmed ** Changed in: compiz-plugins-main (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Fix Released Status in Compiz Main Plugins: Fix Released Status in Compiz Desktop Wall Plugin: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in compiz package in Ubuntu: Confirmed Status in compiz-plugins-main package in Ubuntu: Confirmed Status in compiz source package in Xenial: Won't Fix Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1844504] [NEW] xenial buildd chroots shouldn't have makedev
Public bug reported: xenial mir builds recently started failing as follows: https://launchpadlibrarian.net/442878565/buildlog_ubuntu-xenial- amd64.mir_1.4.0+dev83-g939ca20348-0ubuntu16.04_BUILDING.txt.gz ERROR:src/umockdev.c:4991:umockdev_testbed_create_node_for_device: assertion failed: (Linux.openpty (out ptym, out ptys, ptyname_array, null, null) == 0) I'm fairly sure that this is because the new livecd-rootfs-built xenial buildd base images include makedev, which was Priority: required in xenial (but not in later releases) but not in the historical buildd chroots. The best approach is likely to be to just take makedev out again. [Test Case] Run a buildd image build and make sure that makedev is gone from the resulting images. If possible, run a mir build and test that it works now, though this is likely to be arduous; we probably don't need to put too much effort into this given that reverting buildd base image upgrades is now a quick operation. (We can't upgrade the base images until this is in -updates.) [Regression Potential] This is mostly a reversion to a previous known- working state, so I'm not too worried, but we need to make sure that buildd images are still buildable and keep a close eye on builds immediately after upgrading to new images. ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: High Assignee: Colin Watson (cjwatson) Status: Fix Committed ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Xenial) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Colin Watson (cjwatson) ** No longer affects: livecd-rootfs (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1844504 Title: xenial buildd chroots shouldn't have makedev Status in livecd-rootfs source package in Xenial: Fix Committed Bug description: xenial mir builds recently started failing as follows: https://launchpadlibrarian.net/442878565/buildlog_ubuntu-xenial- amd64.mir_1.4.0+dev83-g939ca20348-0ubuntu16.04_BUILDING.txt.gz ERROR:src/umockdev.c:4991:umockdev_testbed_create_node_for_device: assertion failed: (Linux.openpty (out ptym, out ptys, ptyname_array, null, null) == 0) I'm fairly sure that this is because the new livecd-rootfs-built xenial buildd base images include makedev, which was Priority: required in xenial (but not in later releases) but not in the historical buildd chroots. The best approach is likely to be to just take makedev out again. [Test Case] Run a buildd image build and make sure that makedev is gone from the resulting images. If possible, run a mir build and test that it works now, though this is likely to be arduous; we probably don't need to put too much effort into this given that reverting buildd base image upgrades is now a quick operation. (We can't upgrade the base images until this is in -updates.) [Regression Potential] This is mostly a reversion to a previous known- working state, so I'm not too worried, but we need to make sure that buildd images are still buildable and keep a close eye on builds immediately after upgrading to new images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/xenial/+source/livecd-rootfs/+bug/1844504/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1841573] Re: buildd images contain broken update-initramfs script
Actually, now that I look more closely it doesn't affect xenial or bionic after all. The regression was introduced in commit 283871573db33af8bb1a77d452d17ac6e18ef9e2 which was part of livecd-rootfs 2.559, which is newer than bionic. If we ever plan to use the new-style base images for disco then this would be a problem there, but we probably don't. ** No longer affects: livecd-rootfs (Ubuntu Xenial) ** No longer affects: livecd-rootfs (Ubuntu Bionic) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1841573 Title: buildd images contain broken update-initramfs script Status in livecd-rootfs package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/439022047/buildlog_ubuntu-eoan- amd64.diffoscope_121_BUILDING.txt.gz fails with: Setting up linux-firmware (1.181) ... /usr/sbin/update-initramfs: 3: exec: update-initramfs.REAL: not found dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 This is a bug in the buildd images: they don't contain initramfs-tools at all, so while the chroot configuration stage creates an update- initramfs diversion, the deconfiguration stage sees that update- initramfs.REAL doesn't exist and so never removes the diversion or the temporary replacement script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1841573/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831942] Re: support u-boot Flat Image Tree (FIT) signing support
** Changed in: launchpad Status: Fix Committed => Fix Released ** Summary changed: - support u-boot Flat Image Tree (FIT) signing support + u-boot Flat Image Tree (FIT) signing support -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831942 Title: u-boot Flat Image Tree (FIT) signing support Status in Launchpad itself: Fix Released Status in u-boot package in Ubuntu: Fix Released Status in u-boot source package in Xenial: Fix Released Status in u-boot source package in Bionic: Fix Released Status in u-boot source package in Cosmic: Fix Released Status in u-boot source package in Disco: Fix Released Status in u-boot source package in Eoan: Fix Released Bug description: [Impact] the existing mkimage/dumpimage tools are unable to make or dump out the contents of a u-boot FIT image. [Test Case] run mkimage with no arguments, note that FIT images and signing are shown as disabled. Install the updated version and note that FIT images and signing are now shown as enabled. Run the attached TEST-FIT script which will put together a sample image, generate some keys, and sign the resulting image contents. You will see "kernel.img: Device Tree Blob version 17,..." if the image is created and you will see dumpimage output showing it is not yet signed (Sign value: unavailable). The signatures will then be applied and the image redumped and you will see it is now signed (Sign value: ). [Regression Potential] though this changes the u-boot boot loader package, only the build of the u-boot-utils package contents is modified. This primarily enabled FIT_SIGNATURE support in the configuration before building those tools. The majority of the tools we ship do not have configuration support even and so should not be affected. mkimage et al are not normally used during a kernel/bootloader update and so the risk to a pre-installed system should be low. There is slightly higher risk in the xenial changes as the enablement has enabled some additional tool builds, but none of those are shipped in the resulting binaries. === We need a mechanism for securely signing Flat Image Tree binaries. This will be performed in a similar manner to UEFI signing support via a custom binary upload to launchpad. We will also need a u-boot update to enable image creation and signing support in mkimage. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1831942/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1659801] Re: apparmor rules block ejabberdctl
** Also affects: ejabberd (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1659801
Title:
apparmor rules block ejabberdctl
Status in ejabberd package in Ubuntu:
Fix Released
Status in ejabberd source package in Xenial:
New
Status in ejabberd package in Debian:
Fix Released
Bug description:
Hi,
I am just trying to install ejabberd in a fresh Ubuntu 16.04 LXD
container running on a 16.10 host.
I found that I cannot run ejabberdctl directly as root:
# ejabberdctl
/usr/sbin/ejabberdctl: line 428: 2886 Segmentation fault $EXEC_CMD
"$CMD"
strace reveals what happens:
2861 execve("/bin/su", ["su", "ejabberd", "-c", "/usr/bin/erl -sname
ctl-2841-ejabberd -noinput -hidden -s ejabberd_ctl -extra
ejabberd"], [/* 23 vars */]) = -1 EACCES (Permission denied)
2861 --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
2861 +++ killed by SIGSEGV +++
It is not allowed to execute su to become ejabberd, because apparmor does not
allow this:
[ 7827.594020] audit: type=1400 audit(1485515038.865:156): apparmor="DENIED"
operation="file_mmap" namespace="root//lxd-ansitest_"
profile="/usr/sbin/ejabberdctl//su" name="/bin/su" pid=12861 comm="su"
requested_mask="m" denied_mask="m" fsuid=165536 ouid=165536
But if I do it the other way round (i.e. su outside of ejabberdctl),
it works:
su ejabberd -c ejabberdctl
since then the su is not covered by the apparmor profile of ejabberdctl.
Is that behaviour intended?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1659801/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted
** Also affects: parted (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: parted (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: parted (Ubuntu Xenial) Importance: Undecided => High ** Changed in: parted (Ubuntu Bionic) Importance: Undecided => High ** Changed in: parted (Ubuntu Xenial) Status: New => Triaged ** Changed in: parted (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641308 Title: Partitions display wrong in gnome -disks - ok in gparted Status in parted package in Ubuntu: Fix Released Status in parted source package in Xenial: Triaged Status in parted source package in Bionic: Triaged Bug description: The partitions displayed by gnome-disk-utility are wrong. When i use gparted the partitions displayed are correct. The display became wrong after i deleted 1 partition from the disk using gnome-disk-utility. Here is a screenshot of the 2 tools vision of the same disk: http://pasteboard.co/PjWpqeNzi.png Here is the fdisk: hippo@hippo-camp:~$ sudo fdisk -l [sudo] password for hippo: Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1c0966b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 63 758587953 758587891 361,7G 7 HPFS/NTFS/exFAT /dev/sdc3 758589438 903041023 144451586 68,9G 5 Extended /dev/sdc5 758589440 903041023 144451584 68,9G 83 Linux hippo@hippo-camp:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 gnome-disk-utility: Installed: 3.18.3.1-1ubuntu1 Candidate: 3.18.3.1-1ubuntu1 Version table: *** 3.18.3.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status gparted: Installed: 0.25.0-1 Candidate: 0.25.0-1 Version table: *** 0.25.0-1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I get *very nervous* when tools that have write access to partitions can't display them properly. Good hunt Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 12:16:39 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2016-10-11 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1641308/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815251] [NEW] Build buildd images
Public bug reported: I've been working for some time on having livecd-rootfs be able to build buildd chroots. This has a few immediate advantages: it makes the process of building those chroots more transparent and reproducible, reduces the pressure on the single person currently responsible for managing chroots across all architectures, and allows for a less frustrating chroot update process since I added a facility to Launchpad last year for updating chroots from a livefs build which will be a fast API operation rather than something requiring uploading several hundred megabytes to Launchpad and frequently timing out. I expect that in the future it can also allow us to have separate chroots for e.g. -updates at relatively low cost, which will make builds for stable series substantially faster as they won't need to apply a large and growing set of upgrades at the start of nearly every build. We also have a more recent requirement to build LXD images in order that we can converge with the images used by snapcraft, and so that we can use them directly in Launchpad livefs and snap builds rather than having to convert chroots on the fly. Fortunately it's quite easy to convert buildd chroots into images usable by LXD, and for now I've simply translated the approach currently used in launchpad-buildd to do the conversion on the fly. Particularly in order to assist with snapcraft convergence but also so that we can improve build performance for the heavily-used LTS series, I'd like to backport this support to xenial and bionic. Most of it has been in disco for a while now, with some recent tweaks. [Test Case] We'll want to run livefs builds in Launchpad with appropriate configuration, similar to https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/disco/buildd, and probably then test on dogfood or similar before unleashing them on production. [Regression Potential] The patch is substantially just adding another subproject type so I'm not too concerned, but of course we should check that a couple of other build types still work. ** Affects: livecd-rootfs (Ubuntu) Importance: High Assignee: Colin Watson (cjwatson) Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: High Assignee: Colin Watson (cjwatson) Status: In Progress ** Affects: livecd-rootfs (Ubuntu Bionic) Importance: High Assignee: Colin Watson (cjwatson) Status: In Progress ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Xenial) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Colin Watson (cjwatson) ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Bionic) Importance: Undecided => High ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815251 Title: Build buildd images Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Status in livecd-rootfs source package in Bionic: In Progress Bug description: I've been working for some time on having livecd-rootfs be able to build buildd chroots. This has a few immediate advantages: it makes the process of building those chroots more transparent and reproducible, reduces the pressure on the single person currently responsible for managing chroots across all architectures, and allows for a less frustrating chroot update process since I added a facility to Launchpad last year for updating chroots from a livefs build which will be a fast API operation rather than something requiring uploading several hundred megabytes to Launchpad and frequently timing out. I expect that in the future it can also allow us to have separate chroots for e.g. -updates at relatively low cost, which will make builds for stable series substantially faster as they won't need to apply a large and growing set of upgrades at the start of nearly every build. We also have a more recent requirement to build LXD images in order that we can converge with the images used by snapcraft, and so that we can use them directly in Launchpad livefs and snap
[Group.of.nepali.translators] [Bug 1734040] Re: openssh: The concurrency of settimeofday and ssh connect would lead to coredump
This was fixed upstream a while back in response to you reporting it directly to them (https://anongit.mindrot.org/openssh.git/commit/?id=5db6fbf1438b108e5df3e79a1b4de544373bc2d4); that fix was in OpenSSH 7.7p1 and is thus in cosmic. It might not be a bad idea to backport this fix to xenial and bionic, so I've opened bug tasks for that. ** Also affects: openssh (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1734040 Title: openssh: The concurrency of settimeofday and ssh connect would lead to coredump Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: New Status in openssh source package in Bionic: New Bug description: Hi, pals: we found a coredump when we do ssh connection. the basic information as follow: the stack trace in coredump: (gdb) bt #0 0x20007510 in raise () from /lib/libc.so.6 #1 0x2000c718 in abort () from /lib/libc.so.6 #2 0x2053d42c in __mulvsi3 (a=, b=) at /home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159 #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871 #4 0x204d2568 in ssh_exchange_identification (timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580 #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, timeout_ms=5000) at sshconnect.c:1346 #6 0x204c433c in main (ac=, av=) at ssh.c:1326 the direct cause of the coredump, is that the function __mulvsi3 in gcc checked the plus operation is overflow, then this gcc function abort(). the reason of the overflow is cause by the time-setting operation when do ssh connect. in function ms_subtract_diff . the timeoutp get a very big value because of the time-change. So could we add a limitation for the differ of the 2 values get from gettimeofday ? if it's too big, would lead to overflow, we set a default value and report a warning log. thanks for you attention and expect your reply. B.R. Le Wang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1734040/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1729754] Re: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad
1.3.3 (2018-07-20) == - Drop support for Python < 2.6. - Add tox testing support. - Implement a subset of MIME multipart/form-data encoding locally rather than using the standard library's email module, which doesn't have good handling of binary parts and corrupts bytes in them that look like line endings in various ways depending on the Python version. [bug=1729754] ** Changed in: wadllib Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1729754 Title: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad Status in wadllib: Fix Released Status in python-wadllib package in Ubuntu: New Status in python-wadllib source package in Xenial: New Status in python-wadllib source package in Bionic: New Bug description: Tested on 16.04 and 17.10 python-launchpadlib (1.10.5-1 on 17.10) python3-launchpadlib (1.10.5-1 on 17.10) While working on porting a utility using launchpadlib from Python2 to Python3, I noticed the binary attachments were becoming unreadable. I wrote a little proof of concept that uploads a given binary attachment to a launchpad issue (see attachment). To use it on staging launchpad: APPORT_STAGING=1 ./poc.py When using the exact same script with python2 (basically, replacing `python3` with `python` in the shebang line), the binary file is properly attached. That's why I think it's a bug with python3-launchpadlib. I've tried uploading .jpg files, .tgz files, .tar.xz files, they all fail to open properly. P.S.: When a fix is available, can it be ported to Xenial? We need this for our tools running on devices using Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/1729754/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775641] Re: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu
** No longer affects: ibm-java80 (Ubuntu) ** No longer affects: ibm-java80 (Ubuntu Xenial) ** No longer affects: ibm-java80 (Ubuntu Bionic) ** Changed in: ibm-java71 (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: ibm-java71 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775641 Title: [Comm] IBM JDK 8.0.5.16 integration into Ubuntu Status in Ubuntu on IBM z Systems: In Progress Status in ibm-java71 package in Ubuntu: New Status in ibm-java71 source package in Xenial: Fix Committed Status in ibm-java71 source package in Bionic: New Bug description: foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp16_20180524_01_ocdc.tar.gz local: 80sr5fp16_20180524_01_ocdc.tar.gz remote: 80sr5fp16_20180524_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp16_20180524_01_ocdc.tar.gz 226 Transfer successful. 651496332 bytes sent in 377.03 secs (1687.5 kB/s) ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775641/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in intel-microcode source package in Xenial: New Status in linux source package in Xenial: New Status in intel-microcode source package in Artful: Confirmed Status in linux source package in Artful: Confirmed Bug description: I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1685962] Re: keyring file-backend reports backtrace with oauth
Fixed in launchpadlib 1.10.6.
** Changed in: launchpadlib
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1685962
Title:
keyring file-backend reports backtrace with oauth
Status in launchpadlib :
Fix Released
Status in python-launchpadlib package in Ubuntu:
Confirmed
Status in python-launchpadlib source package in Xenial:
Confirmed
Status in python-launchpadlib source package in Artful:
Confirmed
Status in python-launchpadlib source package in Bionic:
Confirmed
Bug description:
When bringing the importer back up, I ran into the following:
The authorization page:
()
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
Traceback (most recent call last):
File "./bin/usd", line 17, in
main()
File "/home/ubuntu/usd-importer/usd/__main__.py", line 172, in main
args.func(args)
File "/home/ubuntu/usd-importer/usd/importer.py", line 1230, in main
lp = launchpad_login_auth()
File "/home/ubuntu/usd-importer/usd/source_information.py", line 47, in
launchpad_login_auth
version=_lp_api_version)
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 544,
in login_with
credential_save_failed, version)
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 351,
in _authorize_token_and_login
credentials = authorization_engine(credentials, credential_store)
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line
552, in __call__
credential_store.save(credentials, self.unique_consumer_id)
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line
307, in save
raise e
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line
302, in save
self.do_save(credentials, unique_consumer_id)
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line
384, in do_save
'launchpadlib', unique_key, serialized)
File "/usr/lib/python3/dist-packages/keyring/core.py", line 48, in
set_password
_keyring_backend.set_password(service_name, username, password)
File "/usr/lib/python3/dist-packages/keyring/backends/file.py", line 87, in
set_password
password_encrypted = self.encrypt(password.encode('utf-8'))
AttributeError: 'bytes' object has no attribute 'encode'
cjwatson on IRC suggested this is probably a simple change in
launchpadlib:
=== modified file 'src/launchpadlib/credentials.py'
--- src/launchpadlib/credentials.py 2016-08-15 10:32:44 +
+++ src/launchpadlib/credentials.py 2017-04-24 16:28:46 +
@@ -380,7 +380,7 @@ class KeyringCredentialStore(CredentialS
# this problem by base 64 encoding the serialized value.
serialized = self.B64MARKER + b64encode(serialized)
keyring.set_password(
-'launchpadlib', unique_key, serialized)
+'launchpadlib', unique_key, serialized.decode('utf8'))
def do_load(self, unique_key):
"""Retrieve credentials from the keyring."""
which ensures unicode is always passed down, but it needs further
testing. It does fix the issue in my particular case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/1685962/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1736454] Re: pylxd cannot start containers with LXD 2.0.11
;alias": "xenial"}}, wait=True)
+ >>> container.start(wait=True) # should produce no warnings or exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server and
the Python client code, so anything around there could in principle go
wrong. I think running launchpad-buildd against it ought to exercise it
fairly well.
** Also affects: python-pylxd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: python-pylxd (Ubuntu Xenial)
Status: New => In Progress
** Changed in: python-pylxd (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: python-pylxd (Ubuntu Xenial)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: python-pylxd (Ubuntu)
Status: In Progress => Fix Released
** Changed in: python-pylxd (Ubuntu)
Importance: Critical => Undecided
** Changed in: python-pylxd (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Patch added: "python-pylxd_2.0.5-0ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1736454/+attachment/5018816/+files/python-pylxd_2.0.5-0ubuntu1.2.debdiff
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736454
Title:
pylxd cannot start containers with LXD 2.0.11
Status in python-pylxd package in Ubuntu:
Fix Released
Status in python-pylxd source package in Xenial:
In Progress
Bug description:
The LXD 2.0.11 SRU in xenial broke pylxd and hence broke Launchpad
builds, as visible here:
https://launchpadlibrarian.net/348160479/buildlog_snap_ubuntu_xenial_arm64_core_BUILDING.txt.gz
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted
to set unknown attribute "used_by" on instance of "Profile"
key, self.__class__.__name__
/usr/lib/python2.7/dist-packages/pylxd/model.py:113: UserWarning: Attempted
to set unknown attribute "description" on instance of "Container"
key, self.__class__.__name__
Traceback (most recent call last):
File "/usr/share/launchpad-buildd/slavebin/in-target", line 27, in
sys.exit(main())
File "/usr/share/launchpad-buildd/slavebin/in-target", line 23, in main
return args.operation.run()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lifecycle.py",
line 40, in run
self.backend.start()
File "/usr/lib/python2.7/dist-packages/lpbuildd/target/lxd.py", line 380,
in start
container.start(wait=True)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 163, in
start
wait=wait)
File "/usr/lib/python2.7/dist-packages/pylxd/container.py", line 151, in
_set_state
self.sync()
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 154, in sync
setattr(self, key, val)
File "/usr/lib/python2.7/dist-packages/pylxd/model.py", line 135, in
__setattr__
return super(Model, self).__setattr__(name, value)
AttributeError: 'Container' object has no attribute 'description'
I initially thought this would require reverting LXD, but on
inspection it's just adding some new attributes and it's really not
its fault that pylxd is unnecessarily strict. This was fixed in pylxd
upstream a while ago (https://github.com/lxc/pylxd/pull/234), and the
fix is in 2.2.4 so >=artful is already fixed. zesty in principle
requires the fix but I can't actually reproduce the bug there, so it's
probably best to leave it alone for the time being. However, xenial's
pylxd is currently broken.
[Test Case]
>>> from pylxd import Client
>>> client = Client()
>>> container = client.containers.create({"name": "test", "architecture":
"x86_64", "profiles": ["default"], "source": {"type": "image", "mode": "pull",
"server": "https://cloud-images.ubuntu.com/releases;, "protocol":
"simplestreams", "alias": "xenial"}}, wait=True)
>>> container.start(wait=True) # should produce no warnings or exceptions
[Regression Potential]
The fix is to the code that marshals objects between the LXD server
and the Python client code, so anything around there could in
principle go wrong. I think running launchpad-buildd against it ought
to exercise it fairly well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1736454/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1668093] Re: ssh-keygen -H corrupts already hashed entries
Thanks - I'll cherry-pick that into Debian, so zesty will get the fix. I'd appreciate somebody else handling SRUs, though. ** Bug watch added: Debian Bug tracker #851734 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851734 ** Changed in: openssh (Debian) Importance: Undecided => Unknown ** Changed in: openssh (Debian) Status: New => Unknown ** Changed in: openssh (Debian) Remote watch: None => Debian Bug tracker #851734 ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Importance: Medium => High ** Changed in: openssh (Ubuntu Xenial) Status: New => Triaged ** Changed in: openssh (Ubuntu Xenial) Importance: Undecided => High ** Changed in: openssh (Ubuntu Yakkety) Status: New => Triaged ** Changed in: openssh (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668093 Title: ssh-keygen -H corrupts already hashed entries Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Xenial: Triaged Status in openssh source package in Yakkety: Triaged Status in openssh package in Debian: Unknown Bug description: xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @ 1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested any other ssh versions. The following should reproduce the issue: #ssh-keyscan > ~/.ssh/known_hosts # ssh root@X Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@XX Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@X The authenticity of host 'XX' can't be established. RSA key fingerprint is XX. Are you sure you want to continue connecting (yes/no)? # diff known_hosts.old known_hosts 1c1 < |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X --- > |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1471927] Re: AccessToken.from_string() crashes on python3
Fixed in launchpadlib 1.10.5. ** Changed in: launchpadlib Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1471927 Title: AccessToken.from_string() crashes on python3 Status in launchpadlib : Fix Released Status in python-launchpadlib package in Ubuntu: Fix Released Status in python-launchpadlib source package in Xenial: Fix Committed Bug description: [Impact] * Unable to renew/relogin with a new oauth token, using python3 scripts * python2 APIs work (because python2 does not care about str vs bytes) [Test Case] * Attempt login_with() using python3 and an expired/invalid existing token * Relogin should be successful, without crashing scripts [Regression Potential] * No change in behaviour on python2 (which is what used by reverse dependencies) * this is a backport to fix python3 behaviour, for all the newly ported maintainance scripts in python3 that prefer to run on "stable" systems [Other Info] * Well tested in later releases, and with users running from trunk. * I believe this still is not published in the cheeseshop. [Original bug report] Trying to use Launchpad.login_with() on python3, after fixing the earlier bug yields this issue: Traceback (most recent call last): File "./foo.py", line 31, in lb = launchpad.projects[project] File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 1001, in __getitem__ shim_resource._ensure_representation() File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 382, in _ensure_representation representation = self._root._browser.get(self._wadl_resource) File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 436, in get response, content = self._request(url, extra_headers=headers) File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 387, in _request str(url), method=method, body=data, headers=headers) File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 357, in _request_and_retry url, method=method, body=body, headers=headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1291, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 132, in _request return self.retry_on_bad_token(response, content, *args) File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 144, in retry_on_bad_token self.launchpad.credentials, self.launchpad.credential_store) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 545, in __call__ self.make_end_user_authorize_token(credentials, request_token_string) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 658, in make_end_user_authorize_token self.web_root) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 233, in exchange_request_token_for_access_token self.access_token = AccessToken.from_string(content) File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 251, in from_string key = params['oauth_token'] KeyError: 'oauth_token' The problem is that params has b'oauth_token', not 'oauth_token', which matters on python3 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpadlib/+bug/1471927/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1606203] Re: Failed to build of snappy package on Launchpad: Invalid header value 'Basic U05BUEJVSUxELTE4NzAtMTQ2OTQyNjE0ODpjOTJkYzVjOWQ0OTg0ZGE5OWZlNGY1ZjI3ODRhMWJk
** Also affects: bzr (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1606203 Title: Failed to build of snappy package on Launchpad: Invalid header value 'Basic U05BUEJVSUxELTE4NzAtMTQ2OTQyNjE0ODpjOTJkYzVjOWQ0OTg0ZGE5OWZlNGY1ZjI3ODRhMWJk\nOA==' Status in Bazaar: In Progress Status in Snapcraft: Invalid Status in bzr package in Ubuntu: New Status in bzr source package in Xenial: New Bug description: Snappy package of KiCad: https://code.launchpad.net/~eldar/+snap/kicad-snappy Log amd64: https://launchpadlibrarian.net/274916496/buildlog_snap_ubuntu_xenial_amd64_kicad-snappy_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/1606203/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1539157] Re: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img
** Also affects: live-build (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: Some architectures get "link_in_boot = yes" added to /etc/kernel- img.conf by lb_chroot_linux-image; it appears that cloud images built for these architectures (I have checked s390x and arm64) end up with an LZMA-compressed empty regular file at /boot/initrd.img (instead of the expected symlink to /boot/initrd.img-...). In terms of time-of-introduction, I have confirmed that an s390x image built against proposed on the 12th of January was good, whereas an s390x image built against the main archive on the 25th was not. (I suspect that this is actually an issue in something in the archive, but as I don't really know _what_, I have filed this against live-build for now.) Related bugs: * bug 1539157: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img * bug 1536810 kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory + + For SRU purposes, we can confirm a fix by making sure that cloud images + of a couple of architectures built with this fix still boot, and that + initrd.img is a symlink rather than a (small) regular file. -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1539157 Title: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img Status in live-build package in Ubuntu: New Status in live-build source package in Xenial: New Bug description: Some architectures get "link_in_boot = yes" added to /etc/kernel- img.conf by lb_chroot_linux-image; it appears that cloud images built for these architectures (I have checked s390x and arm64) end up with an LZMA-compressed empty regular file at /boot/initrd.img (instead of the expected symlink to /boot/initrd.img-...). In terms of time-of-introduction, I have confirmed that an s390x image built against proposed on the 12th of January was good, whereas an s390x image built against the main archive on the 25th was not. (I suspect that this is actually an issue in something in the archive, but as I don't really know _what_, I have filed this against live- build for now.) Related bugs: * bug 1539157: Images built with "link_in_boot = yes" in /etc/kernel-img.conf end up with a broken /boot/initrd.img * bug 1536810 kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory For SRU purposes, we can confirm a fix by making sure that cloud images of a couple of architectures built with this fix still boot, and that initrd.img is a symlink rather than a (small) regular file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1539157/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1587667] Re: Import from Debian fails for source packages with included tarball .asc
In order to fix this, we'll need to cherry-pick the patches to allow extraction (but not building!) of such source packages back to precise/trusty/xenial dpkg. ** Description changed: https://launchpad.net/debian/+source/vlc/ is missing Debian branches for sid and stretch. This then also breaks auto-sync of some of Debian's packages to Ubuntu's development branch. This is apparently what broke the auto-import: - pkg-source: error: unrecognized file for a v2.0 source package: + dpkg-source: error: unrecognized file for a v2.0 source package: vlc_2.2.3.orig.tar.xz.asc See this discussion about including .asc files in Debian source packages which requires dpkg to be updated: https://lists.debian.org/debian-dpkg/2016/05/msg00041.html Initial discussion: http://irclogs.ubuntu.com/2016/05/31/%23ubuntu-devel.html#t22:44 ** Changed in: launchpad Status: New => Triaged ** Changed in: launchpad Importance: Undecided => High ** Tags added: lp-soyuz ** Tags added: gina ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: dpkg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1587667 Title: Import from Debian fails for source packages with included tarball .asc Status in Launchpad itself: Triaged Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Precise: New Status in dpkg source package in Trusty: New Status in dpkg source package in Xenial: New Bug description: https://launchpad.net/debian/+source/vlc/ is missing Debian branches for sid and stretch. This then also breaks auto-sync of some of Debian's packages to Ubuntu's development branch. This is apparently what broke the auto-import: dpkg-source: error: unrecognized file for a v2.0 source package: vlc_2.2.3.orig.tar.xz.asc See this discussion about including .asc files in Debian source packages which requires dpkg to be updated: https://lists.debian.org/debian-dpkg/2016/05/msg00041.html Initial discussion: http://irclogs.ubuntu.com/2016/05/31/%23ubuntu-devel.html#t22:44 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1587667/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1586770] [NEW] Add pymacaroons to xenial
Public bug reported: In order to be able to authenticate properly to myapps.developer.ubuntu.com for such things as uploading snaps, snapcraft is going to need the "pymacaroons" library. (This is because it needs to be able to get a macaroon-format authentication token from myapps, then go to SSO to get a "discharge macaroon" that confirms that it actually has permission from the user in question to act on their behalf, then bind these two tokens together; it's that last step that requires pymacaroons.) pymacaroons in turn also requires python- libnacl. I hope that we're generally agreed that it would be better for snapcraft not to need to embed its own copies of these libraries. I've packaged both of these in Debian unstable and they're therefore also in yakkety, but we need them in xenial-updates as well. ** Affects: pymacaroons (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-libnacl (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: pymacaroons (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: python-libnacl (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-libnacl (Ubuntu) Importance: Undecided Status: New ** Also affects: python-libnacl (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pymacaroons (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-libnacl (Ubuntu) Status: New => Fix Released ** Changed in: pymacaroons (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1586770 Title: Add pymacaroons to xenial Status in pymacaroons package in Ubuntu: Fix Released Status in python-libnacl package in Ubuntu: Fix Released Status in pymacaroons source package in Xenial: New Status in python-libnacl source package in Xenial: New Bug description: In order to be able to authenticate properly to myapps.developer.ubuntu.com for such things as uploading snaps, snapcraft is going to need the "pymacaroons" library. (This is because it needs to be able to get a macaroon-format authentication token from myapps, then go to SSO to get a "discharge macaroon" that confirms that it actually has permission from the user in question to act on their behalf, then bind these two tokens together; it's that last step that requires pymacaroons.) pymacaroons in turn also requires python-libnacl. I hope that we're generally agreed that it would be better for snapcraft not to need to embed its own copies of these libraries. I've packaged both of these in Debian unstable and they're therefore also in yakkety, but we need them in xenial-updates as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pymacaroons/+bug/1586770/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1512347] Re: invalid sources.list generated from reading apt-setup/local0/repository
** Also affects: base-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: base-installer (Ubuntu Xenial) Status: New => Triaged ** Changed in: base-installer (Ubuntu Xenial) Importance: Undecided => High ** Changed in: base-installer (Ubuntu Xenial) Milestone: None => ubuntu-16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1512347 Title: invalid sources.list generated from reading apt- setup/local0/repository Status in base-installer package in Ubuntu: Fix Released Status in base-installer source package in Xenial: Triaged Bug description: hi, it looks like configure_apt from library.sh will add the contents of apt-setup/local0/repository verbatim to the sources file. This works only if the repository is prefixed with "deb ", which for apt-setup is optional. Not using a repository prefixed with "deb" will result in an invalid sources.list file. See also https://phabricator.wikimedia.org/T94177 and https://gerrit.wikimedia.org/r/250380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1575961] Re: OpenSSH Client Certificate Auth Regression
** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => High ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) ** Also affects: openssh (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: openssh (Ubuntu Trusty) ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Xenial) Status: New => Triaged ** Changed in: openssh (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1575961 Title: OpenSSH Client Certificate Auth Regression Status in openssh package in Ubuntu: Triaged Status in openssh source package in Xenial: Triaged Bug description: OpenSSH Client Certificates worked in Ubuntu 15.10 and 14.04 LTS -- but not 16.04. OpenSSH 7.2.p2 includes a bug in how it loads keys & certificates, and basically will never find the correct private key for an OpenSSH Client Certificate. This is the upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2550 Fix was committed on March 14: https://github.com/openssh/openssh- portable/commit/c38905ba391434834da86abfc988a2b8b9b62477 I've tested with the attached patch, and it allows Client Certificate auth to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1575961/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1513589] Re: linux-firmware-nonfree should be removed from Xenial
Removing packages from xenial: linux-firmware-nonfree 1.16 in xenial linux-firmware-nonfree 1.16 in xenial amd64 linux-firmware-nonfree 1.16 in xenial arm64 linux-firmware-nonfree 1.16 in xenial armhf linux-firmware-nonfree 1.16 in xenial i386 linux-firmware-nonfree 1.16 in xenial powerpc linux-firmware-nonfree 1.16 in xenial ppc64el linux-firmware-nonfree 1.16 in xenial s390x Comment: requested by ~timg-tpi; "beyond questionable" provenance and licensing; LP: #1513589 Remove [y|N]? y 1 package successfully removed. ** Changed in: linux-firmware-nonfree (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1513589 Title: linux-firmware-nonfree should be removed from Xenial Status in linux-firmware-nonfree package in Ubuntu: Fix Released Status in linux-firmware-nonfree source package in Xenial: Fix Released Bug description: Provenance and licensing for the firmware files included in this package are beyond questionable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/1513589/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
