[Touch-packages] [Bug 1645815] Re: apt install of local debs does not tab-complete
** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-needed-yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1645815 Title: apt install of local debs does not tab-complete Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: [Impact] Previously apt's bash completion was such that, given $ mkdir xyzzz $ touch xyzzy.deb xyzzx.two.deb you'd get $ apt install xyzz xyzzx.two.deb xyzzz/ $ apt install /tmp/foo/xyzz xyzzx.two.deb xyzzz/ this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but worse than that it offered things that apt would not actually recognise as candidates for install: $ sudo apt install xyzzx.two.deb Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package xyzzx.two.deb E: Couldn't find any package by glob 'xyzzx.two.deb' E: Couldn't find any package by regex 'xyzzx.two.deb' [Test case] With this small (trival, really) change, apt's bash completion should only offer things apt understands, and won't recquire an aditional period in the filename to offer it: $ apt install xyzz^C $ # (no completions!) $ apt install ./xyzz xyzzx.two.deb xyzzy.deb xyzzz/ $ apt install /tmp/foo/xyzz xyzzx.two.deb xyzzy.deb xyzzz/ [Regression potential] Only the expansion of filenames in the completion is affected: -_filedir "*.deb" +if [[ "$cur" == ./* || "$cur" == /* ]]; then +_filedir "deb" +fi so it's unlikely to introduce any regression. [Original bug report] this fails: $ touch xyzzy.deb $ apt install xyzzy because the completion support for install is using _filedir wrong. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.15 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 29 17:51:57 2016 InstallationDate: Installed on 2016-07-05 (147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1645815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-needed-yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1657567 Title: "Content-Range: */" on non-416 responses considered invalid Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: APT only allows Content-Range: */ to be specified on a 416 response. Sourceforge sometimes replies with that in a 302 redirect. We should probably just accept and silently ignore that content-range field for other values. [Impact] Issue breaks and other services that respond with a Content-Range header in a 302 redirect, or any non 416 one. [Test Case] Run /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1 http://www.jak-software.de/lp1657567 ubuntu.iso Before: E: Failed to fetch http://www.jak-software.de/lp1657567 The HTTP server sent an invalid Content-Range header Bad header data After: Redirect is followed successfully and a zesty live image is being downloaded. [Regression Potential] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1657440 Title: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: # apt --version apt 1.2.18 (amd64) xenial I got myself into a situation where a repository has a Release and a Release.gpg file, but apt is just ignoring the gpg one and won't download it via apt update for some reason: The repository in question is http://ubuntu- cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See how locally I have just the Release file: root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release* -rw-r--r-- 1 root root 100K Jan 15 18:03 archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease -rw-r--r-- 1 root root 242K Apr 21 2016 archive.ubuntu.com_ubuntu_dists_xenial_InRelease -rw-r--r-- 1 root root 100K Jan 18 11:42 archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease -rw-r--r-- 1 root root 100K Jan 18 11:42 security.ubuntu.com_ubuntu_dists_xenial-security_InRelease -rw-r--r-- 1 root root 7.7K Jan 18 11:45 ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a "Get:": root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton InRelease Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton Release Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton Release.gpg [543 B] Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease Fetched 205 kB in 0s (395 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 8 packages can be upgraded. Run 'apt list --upgradable' to see them. And I can't install packages: root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: python3-setuptools The following packages will be upgraded: dh-python dnsmasq-base python-pkg-resources python-setuptools python3-cryptography python3-pkg-resources python3-requests python3-urllib3 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,193 kB of archives. After this operation, 808 kB of additional disk space will be used. Do you want to continue? [Y/n] WARNING: The following packages cannot be authenticated! dh-python dnsmasq-base python-setuptools python-pkg-resources python3-pkg-resources python3-setuptools python3-cryptography python3-requests python3-urllib3 Install these packages without verification? [y/N] n E: Some packages could not be authenticated root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# Somehow apt is thinking it has the Release.gpg file, but it doesn't? This server is behind a squid proxy. [Impact] An apt update of an apt repository that does not use InRelease during the time it is being updated can cause the gpg file to not be downloaded and updated. This makes the packages from the repository be unable to be authenticated. The Ubuntu Cloud Archive is one of the archives that meets this criteria. The impact to downstream automation deployment code is that if they are adding the UCA repo to a system and calling apt update during the time the UCA is being updated by Canonical, the repo can get into a state where the Release.gpg file is not there and all package installs will fail due to "unauthenticated packages" error. [Test Case] A detailed python script was attached. To reproduce this outside that script you would want to: 1. Add the UCA repo 2. Do the following in a loop starting at 43 minutes after the hour and run it until 55 minutes after the hour: 2.1 Remove these files to simulate the UCA repo being added the first time. /var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release /var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg /var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_main_binary*Packages 2.2 apt-get update 3. Check the state of the 3 files you deleted. If you have the _Release file
[Touch-packages] [Bug 1427764] Re: When OpenStack sends the command “ip link set p4p1 vf 1 state enable”, it fails.
Apologies for their not being any response to your bug thus far. Unfortunately, there's not near enough information for anyone to look much deeper into your issue as have not provided detailed instructions on how to recreate your bug. By the error surfaced, I'm guessing that the kernel you are running either does not support, or is not configured for whatever iproute needs to make this functionality work. Unfortunately, I don't know off the top of my head what that might be. If you'd like further help, you'll need to provide some detailed recreation (preferably without openstack) so that a developer might have a chance to look at the issue themselves. As my guess is that this is a kernel support/configuration issue ultimately, you may want to just try installing a HWE kernel (HardWare Enablement) and see if that is enough to enable what you need as its significantly newer than the 3.13.0-* kernel you are on right now. Instructions on enabling the HWE kernel for Trusty Tahr (14.04) can be seen here. https://wiki.ubuntu.com/Kernel/LTSEnablementStack ** Changed in: iproute2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1427764 Title: When OpenStack sends the command “ip link set p4p1 vf 1 state enable”, it fails. Status in iproute2 package in Ubuntu: Incomplete Bug description: When OpenStack sends the command “ip link set p4p1 vf 1 state enable”, it fails. The Error returned is : RTNETLINK answers: Operation not supported The ip set is part of iproute2 package. I have iproute2-3.12.0, igb 5.2.9.4, Ubuntu 14.04, kernel 3.13.0-43-generic. The Ubuntu 14.04 LTS comes with iproute2-3.12.0, I can’t upgrade it to a newer version. Thanks, Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1427764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
Hi there Brian, Yeah,I said as much ('nice to fix'). My only
justifications are really that its low-risk/easy fix cherry-picked from
upstream, on an LTS with lots of life left, and had a kindly user
generated bug reporter; always nice to show some love to users willing
to write a reasonable bug report. If the SRU team wants to nix that is
their call ultimately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1668813
Title:
The tc man page references tc-index man page but tc-index man page
does not exist
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
In Progress
Status in iproute2 source package in Yakkety:
In Progress
Bug description:
[Impact]
* The man pages for tc make reference to a non-existent tc-index man
page. Purely a typo that should have been tc-tcindex.
* Purely a documentation fix, but nice to fix for an LTS release
that has many years left to it.
[Test Case]
* To see this issue, fire up a 16,04 image (I did so via lxd) and
type:
root@xi386# man tc | grep tc-index
Filter packets based on traffic control index. See
tc-index(8).
, HOWEVER:
root@xi386:~# man tc-index
No manual entry for tc-index
* on a fixed system you should only see refereces to tc-tcindex, not tc-index:
root@x1:~# man tc | grep tc-index
root@x1:~# man tc | grep tc-tcindex
Filter packets based on traffic control index. See
tc-tcindex(8).
red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8),
tc-tcindex(8), tc-u32(8),
[Regression Potential]
* This is only a change to man pages, so any regression would be non-
functional, but this fix is trivial to fix and verify, and the fix is
exactly from the upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
** Description changed: - The tc man page references tc-index man page but tc-index man page does - not exist. + [Impact] - The tc-index man page is incorrectly named tcindex. + * The man pages for tc make reference to a non-existent tc-index man + page. Purely a typo that should have been tc-tcindex. - This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 + * Purely a documentation fix, but nice to fix for an LTS release that + has many years left to it. + + + [Test Case] + + * To see this issue, fire up a 16,04 image (I did so via lxd) and type: + +root@xi386# man tc | grep tc-index + Filter packets based on traffic control index. See tc-index(8). + + , HOWEVER: + +root@xi386:~# man tc-index +No manual entry for tc-index + + + * on a fixed system you should only see refereces to tc-tcindex, not tc-index: + +root@x1:~# man tc | grep tc-index +root@x1:~# man tc | grep tc-tcindex + Filter packets based on traffic control index. See tc-tcindex(8). + red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), tc-tcindex(8), tc-u32(8), + + + + [Regression Potential] + + * This is only a change to man pages, so any regression would be non- + functional, but this fix is trivial to fix and verify, and the fix is + exactly from the upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Status in iproute2 source package in Yakkety: In Progress Bug description: [Impact] * The man pages for tc make reference to a non-existent tc-index man page. Purely a typo that should have been tc-tcindex. * Purely a documentation fix, but nice to fix for an LTS release that has many years left to it. [Test Case] * To see this issue, fire up a 16,04 image (I did so via lxd) and type: root@xi386# man tc | grep tc-index Filter packets based on traffic control index. See tc-index(8). , HOWEVER: root@xi386:~# man tc-index No manual entry for tc-index * on a fixed system you should only see refereces to tc-tcindex, not tc-index: root@x1:~# man tc | grep tc-index root@x1:~# man tc | grep tc-tcindex Filter packets based on traffic control index. See tc-tcindex(8). red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), tc-tcindex(8), tc-u32(8), [Regression Potential] * This is only a change to man pages, so any regression would be non- functional, but this fix is trivial to fix and verify, and the fix is exactly from the upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces
While I can visually confirm that the fix in comment #10 is now in the zesty source code (and the fix is not in the xenial/yakkety source code), I'm unable to actually recreate the experience of a valgrind failure on xenial (I've attempted with both i386 and amd64 xenial containers). I additionally rebuilt the amd64 source with -O0 -g but that did not affect the valgrind run as well. Reporter, can you trigger this bug on the Ubuntu Xenial (16.04)? To get this accepted through the SRU approval process we should really have some testcase that actually triggers the issue. root@x2:~# ip -V ip utility, iproute2-ss151103 root@x2:~# valgrind ip netns add black2 ==916== Memcheck, a memory error detector ==916== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==916== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==916== Command: ip netns add black2 ==916== ==916== ==916== HEAP SUMMARY: ==916== in use at exit: 0 bytes in 0 blocks ==916== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==916== ==916== All heap blocks were freed -- no leaks are possible ==916== ==916== For counts of detected and suppressed errors, rerun with: -v ==916== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) root@x2:~# So where this sits: 1) Appears fixed in zesty 2) Needs a testcase/recreate scenario if desired fixed in Yakkety/Xenial ** Changed in: iproute2 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1615209 Title: ip crashes after a few times adding and removing network namespaces Status in iproute2 package in Ubuntu: Incomplete Bug description: # which ip /sbin/ip # valgrind ip netns add black2 ==22804== Memcheck, a memory error detector ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==22804== Command: ip netns add black2 ==22804== ==22804== Invalid write of size 1 ==22804==at 0x4031F43: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C83: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Address 0x4227094 is 0 bytes after a block of size 28 alloc'd ==22804==at 0x402D17C: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C5E: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Cannot create namespace file "/var/run/netns/black2": File exists ==22804== ==22804== HEAP SUMMARY: ==22804== in use at exit: 28 bytes in 1 blocks ==22804== total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated ==22804== ==22804== LEAK SUMMARY: ==22804==definitely lost: 0 bytes in 0 blocks ==22804==indirectly lost: 0 bytes in 0 blocks ==22804== possibly lost: 0 bytes in 0 blocks ==22804==still reachable: 28 bytes in 1 blocks ==22804== suppressed: 0 bytes in 0 blocks ==22804== Rerun with --leak-check=full to see details of leaked memory ==22804== ==22804== For counts of detected and suppressed errors, rerun with: -v ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1615209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces
I'll take a look at this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1615209 Title: ip crashes after a few times adding and removing network namespaces Status in iproute2 package in Ubuntu: Triaged Bug description: # which ip /sbin/ip # valgrind ip netns add black2 ==22804== Memcheck, a memory error detector ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==22804== Command: ip netns add black2 ==22804== ==22804== Invalid write of size 1 ==22804==at 0x4031F43: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C83: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Address 0x4227094 is 0 bytes after a block of size 28 alloc'd ==22804==at 0x402D17C: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C5E: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Cannot create namespace file "/var/run/netns/black2": File exists ==22804== ==22804== HEAP SUMMARY: ==22804== in use at exit: 28 bytes in 1 blocks ==22804== total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated ==22804== ==22804== LEAK SUMMARY: ==22804==definitely lost: 0 bytes in 0 blocks ==22804==indirectly lost: 0 bytes in 0 blocks ==22804== possibly lost: 0 bytes in 0 blocks ==22804==still reachable: 28 bytes in 1 blocks ==22804== suppressed: 0 bytes in 0 blocks ==22804== Rerun with --leak-check=full to see details of leaked memory ==22804== ==22804== For counts of detected and suppressed errors, rerun with: -v ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1615209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
Schooled in https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging and redid versions yet again. ** Patch removed: "xenial debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4835659/+files/iproute2_4.3.0-1ubuntu3.1.debdiff ** Patch added: "xenial debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4835669/+files/iproute2_4.3.0-1ubuntu3.16.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Status in iproute2 source package in Yakkety: In Progress Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
** Patch added: "yakkety debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4835670/+files/iproute2_4.3.0-1ubuntu3.16.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Status in iproute2 source package in Yakkety: In Progress Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
Fixing version for xenial. Redid changelog with dep3changlog. ** Changed in: iproute2 (Ubuntu Yakkety) Status: Won't Fix => In Progress ** Patch added: "xenial debdiff" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4835659/+files/iproute2_4.3.0-1ubuntu3.1.debdiff ** Patch removed: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4834701/+files/iproute2_4.3.0-1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Status in iproute2 source package in Yakkety: In Progress Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
** Changed in: iproute2 (Ubuntu Xenial) Status: New => In Progress ** Changed in: iproute2 (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: iproute2 (Ubuntu Yakkety) Status: New => Won't Fix ** Changed in: iproute2 (Ubuntu Yakkety) Importance: Undecided => Low ** Changed in: iproute2 (Ubuntu Yakkety) Assignee: (unassigned) => Jon Grimm (jgrimm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: In Progress Status in iproute2 source package in Yakkety: Won't Fix Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
cherrypicking for xenial SRU. As mentioned, zesty fixed already. I don't plan on fixing yakkety at this stage of its lifecycle and this is a really minor issue. tc(8) manapage now reads: .. tcindex Filter packets based on traffic control index. See tc-tcindex(8). .. ** Patch added: "debdiff for xenial" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+attachment/4834701/+files/iproute2_4.3.0-1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: New Status in iproute2 source package in Yakkety: New Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
Added sponsors for upload assistance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: New Status in iproute2 source package in Yakkety: New Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
>From upstream: https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=b08b5ff128874f94a1bc9dd8e178fa0e57c11c61 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: New Status in iproute2 source package in Yakkety: New Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
Low hanging fruit, I can probably get to this week; but feel free to poke me if anyone else wants it. ** Changed in: iproute2 (Ubuntu Xenial) Assignee: (unassigned) => Jon Grimm (jgrimm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: New Status in iproute2 source package in Yakkety: New Bug description: The tc man page references tc-index man page but tc-index man page does not exist. The tc-index man page is incorrectly named tcindex. This is on Xenial, using package version 4.3.0-1ubuntu3 of iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659039] Re: iproute2 catch up with upstream
** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Jon Grimm (jgrimm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1659039 Title: iproute2 catch up with upstream Status in iproute2 package in Ubuntu: New Bug description: https://answers.launchpad.net/ubuntu/+source/iproute2/+question/445831 also tons of bugfixes: http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/log/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1659039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384503] Re: rsync fails on large files with compression
** Changed in: rsync (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: rsync (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Trusty: Triaged Bug description: [Status] This issue is currently Incomplete. We're currently blocked on obtaining access to a reliable, and publicly available dataset that can be shared to reproduce the issue. The test is critical to being able to evaluate the impact of the change on other users when assessing if the fix can be SRU'ed to trusty. If you are affected by this bug and can reliably reproduce the issue with a specific dataset that you are willing and permitted to share please comment and specify the dataset location, and how you reproduce the issue. [Original Description] Copying large (>10GB) files with rsync -z (compression) leads to a long hang and eventual error after transferring part of the file. The error is consistent. The file copies at normal speed until it reaches its maximum size (1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another). Then nothing happens for a while (many minutes). Finally, there is an error: [] jh/.VirtualBox/win7/win7.vbox jh/.VirtualBox/win7/win7.vbox-prev jh/.VirtualBox/win7/win7.vdi rsync: [sender] write error: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0] In this case, 6.9 GB of 29 GB transferred. Without -z, it works. See the following upstream report, with a comment at the end from the rsync maintainer: https://bugzilla.samba.org/show_bug.cgi?id=10372 According to this report, version 3.1.0 (included in 14.04) uses a different compression package from prior versions. Prior versions did not have this problem for me using the same command on the same systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04 now, in each case with all updates applied, Intel hardware. Network connection between them is gigabit ethernet through one switch. A shell ssh between them in a terminal works and stays up during the failure, so it is not a network issue. There are no relevant entries in syslog on either machine. There is sufficient capacity on the receiving disk. All filesystems are ext4. rsync command: /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found --exclude=.gvfs --exclude=/nonlaptop /home/ backup.host.edu:/bu/host/home/ (yes, I changed the machine names) Current release (both hosts): Description: Ubuntu 14.04.1 LTS Release: 14.04 Current package (both hosts): rsync: Installed: 3.1.0-2ubuntu0.1 Candidate: 3.1.0-2ubuntu0.1 Version table: *** 3.1.0-2ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.0-2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Thanks, --jh-- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1285850] Re: interuppting lxc-clone can destroy source container
Marked Vivid and Wily as Won't Fix as EOL releases. ** Changed in: lxc (Ubuntu Vivid) Status: Confirmed => Won't Fix ** Changed in: lxc (Ubuntu Wily) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1285850 Title: interuppting lxc-clone can destroy source container Status in lxc package in Ubuntu: Incomplete Status in lxc source package in Vivid: Won't Fix Status in lxc source package in Wily: Won't Fix Status in lxc source package in Xenial: Confirmed Bug description: ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen containers on demand, but if i ctrl-c interuppt the operation, i've seen a few cases where it will destroy the source container (using snapshots and btrfs) $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub ctrl-c the source container's rootfs directory goes missing, and only a rootfs.hold file remains in place. btrfs subvolume list shows nothing for the missing container rootfs as well. lxc-version -> 1.0.0.alpha1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1285850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605260] Re: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04
Discussed with rbasak, with conclusion that this isn't high enough priority to SRU; risky to change unless this is causing real production issues. I'll attach my debdiff in case needing to resurrect at a later time. ** Patch added: "libnl3_3.2.21-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+attachment/4730906/+files/libnl3_3.2.21-1ubuntu4.debdiff ** Changed in: libnl3 (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: libnl3 (Ubuntu) Status: Triaged => Fix Released ** Changed in: libnl3 (Ubuntu Trusty) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1605260 Title: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04 Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Won't Fix Bug description: There is a memory leak in libnl 3.2.21 fixed by upstream here: http://lists.infradead.org/pipermail/libnl/2013-April/000985.html and released as part of libnl-3.2.22 (git commit rev df66b0f267af636848d7f0301d3f5863c58fb313). However, this fix doesn't make it into Ubuntu 14.04LTS. Please, apply. $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy libnl-3-200 libnl-3-200: Installed: 3.2.21-1ubuntu3 Candidate: 3.2.21-1ubuntu3 Version table: *** 3.2.21-1ubuntu3 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.2.21-1 0 500 http://ua.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462936] Re: package python-decorator 3.4.0-2build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Relevant lines from DpkgHistoryLog.txt: File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' This error is seen most often when someone has modified /usr/bin/python to point to python3. Apt depends on this being python2.7. Marking as invalid, but please reopen if this turns out not to be the case. ** Changed in: python-decorator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1462936 Title: package python-decorator 3.4.0-2build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-decorator package in Ubuntu: Incomplete Bug description: .. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-decorator 3.4.0-2build1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sat Jun 6 18:52:09 2015 DuplicateSignature: package:python-decorator:3.4.0-2build1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-20 (79 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: python-decorator Title: package python-decorator 3.4.0-2build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1462936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478746] Re: package python-decorator 3.4.0-2build1 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回了错误号 1
Relevant fro DpkTerminalLog.txt: Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' This error is seen most often when someone has modified /usr/bin/python to point to python3. Apt depends on this being python2.7. Marking as Incomplete, but please move back to New, if this turns out not to be the case. ** Changed in: python-decorator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1478746 Title: package python-decorator 3.4.0-2build1 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回了错误号 1 Status in python-decorator package in Ubuntu: Incomplete Bug description: root@z-Lenovo:/home/z# apt-get dist-upgrade 正在读取软件包列表... 完成 正在分析软件包的依赖关系树 正在读取状态信息... 完成 正在对升级进行计算... 完成 升级了 0 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。 有 3 个软件包没有被完全安装或卸载。 解压缩后会消耗掉 0 B 的额外空间。 您希望继续执行吗？ [Y/n] y 正在设置 apt-xapian-index (0.45ubuntu4) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: 处理软件包 apt-xapian-index (--configure)时出错： 子进程 已安装 post-installation 脚本 返回了错误号 1 正在设置 python-decorator (3.4.0-2build1) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: 处理软件包 python-decorator (--configure)时出错： 子进程 已安装 post-installation 脚本 返回了错误号 1 正在设置 python-simplegeneric (0.8.1-1) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: 处理软件包 python-simplegeneric (--configure)时出错： 子进程 已安装 post-installation 脚本 返回了错误号 1 在处理时有错误发生： apt-xapian-index python-decorator python-simplegeneric E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-decorator 3.4.0-2build1 ProcVersionSignature: Ubuntu 3.16.0-44.59~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 Date: Tue Jul 28 09:03:02 2015 DuplicateSignature: package:python-decorator:3.4.0-2build1:子进程 已安装 pre-removal 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 pre-removal 脚本 返回了错误号 1 InstallationDate: Installed on 2015-06-23 (34 days ago) InstallationMedia: Ubuntu-Kylin 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) PackageArchitecture: all SourcePackage: python-decorator Title: package python-decorator 3.4.0-2build1 failed to install/upgrade: 子进程 已安装 pre-removal 脚本 返回了错误号 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-decorator/+bug/1478746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 684522] Re: format error in man page for dotlockfile
Doing a bit of launchpad cleanup. This was opened in maverick timeframe. I tried to unsuccessfully reproduce on xenial and precise, so I'm going to assume that its been fixed somewhere along the line. Thank you for taking the time to file this bug even though it has languished without response for a long while. Please reopen if you feel you can reproduce this on a release that is currently in support. Thanks! ** Changed in: liblockfile (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblockfile in Ubuntu. https://bugs.launchpad.net/bugs/684522 Title: format error in man page for dotlockfile Status in liblockfile package in Ubuntu: Incomplete Bug description: Binary package hint: liblockfile1 # mandb -c Processing manual pages under /usr/share/man... ... mandb: warning: /usr/share/man/man1/dotlockfile.1.gz: whatis parse for dotlockfile(1) failed dpkg-query -S dotlockfile.1.gz liblockfile1: /usr/share/man/man1/dotlockfile.1.gz So Error in the man file formatting/parsing for the page provided by liblockfile1 apt-cache policy liblockfile1 liblockfile1: Installed: 1.08-4 Candidate: 1.08-4 Version table: *** 1.08-4 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status lsb_release -idrc Distributor ID: Ubuntu Description: Ubuntu 10.10 Release: 10.10 Codename: maverick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblockfile/+bug/684522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508225] Re: tipc tool isn't built in iproute2
** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1508225 Title: tipc tool isn't built in iproute2 Status in iproute2 package in Ubuntu: Triaged Status in iproute2 package in Debian: New Bug description: A new tool "tipc" was added to iproute2 v 4.1.1, needed for managing the TIPC kernel module. Despite being present in the source code, it has not been built in the current iproute2 package that comes with 15.10, something forcing all users to check out the code and build it manually. The reason for the buld failure is that it has a dependency to libmnl-dev, although this is not listed in the dependency list. Stephen Hemminger has confirmed that that using libmnl in iproute2 is ok, but unfortunately the dependency has been made optional, meaning that the build will just silently bypass TIPC is libmnl-dev is not found. If you just add libmnl-dev to the dependency list and make sure it is available when iproute2 is built the problem should be solved. On our side we will try to have the optionality removed from iproute2. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: iproute2 4.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 20 17:56:42 2015 InstallationDate: Installed on 2015-10-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019) SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1508225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522371] Re: iproute2: seg fault with 'ip link type gre ...' commands
** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1522371 Title: iproute2: seg fault with 'ip link type gre ...' commands Status in iproute2 package in Ubuntu: Triaged Status in iproute2 package in Debian: New Bug description: This upstream patch needs to be backported: bde5baa5476c gre: raising the size of the buffer holding nl messages. https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=bde5baa5476c Example: root@ubuntu1404:~# ip link add dummy1 type dummy root@ubuntu1404:~# ip a a 10.200.0.1/24 dev dummy1 root@ubuntu1404:~# ip link add gre2 type gre local 10.200.0.1 remote 10.200.0.2 dev dummy1 root@ubuntu1404:~# ip link set gre2 type gre ttl 32 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 *** stack smashing detected ***: ip terminated Aborted root@ubuntu1404:~# uname -a Linux ubuntu1404 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu1404:~# ip -V ip utility, iproute2-ss131122 root@ubuntu1404:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1522371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546358] Re: policycoreutils (in universe) is installed by default by isc-dhcp-server as it is a Recommends
** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1546358 Title: policycoreutils (in universe) is installed by default by isc-dhcp- server as it is a Recommends Status in isc-dhcp package in Ubuntu: New Bug description: Policycoreutils is being installed by default because the package is listed as a Recommends. This package, however, is in universe and seems to be pulling selinux. This should not be a recommends but rather, it should be a Suggests. It seems that the postinst requires a binary being shipped in policycoreutils: debian/isc-dhcp-server.postinst:test ! -x /sbin/restorecon || /sbin/restorecon /var/lib/dhcp/dhcpd.leases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1546358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24
** Changed in: lxc (Ubuntu Wily) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1510108 Title: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24 Status in lxc package in Ubuntu: Triaged Status in lxc source package in Wily: Triaged Status in lxc source package in Xenial: Triaged Bug description: Bug 1509414 describes fallout of inclusion of lxc in cloud images. The initial inclusion caused 2 issues: a.) containers created by 'lxc -t ubuntu-cloud' and 'lxd import-images ubuntu wily' had completely broken networking b.) all cloud images would have lost access to 10.0.3.0/24 networks. The fix that went in fixes 'a' above. By default, containers created for lxd and lxc will now work as expected. This bug is opened to address the much less severe 'b'. Now, on first boot lxc-net selects a network in the 10.0.X.0/24 to give to the lxcbr0 bridge. It selects the network by simply looking for the first available N where there . That code can be seen prior to fix in debian/lxc.preinst [1] and after fix in config/init/common /lxc-net.in [2]. Generally speaking it looks for local ip addresses on the targeted network. That code is fairly simplistic. There are definitely cases where it can pick a network that would be used by this system. The result is that traffic destined for that network will be sent to the lxcbr0 rather than out of the system to wherever it should go. The suggested fix would be to make that code run on 'lxc' or 'lxd' usage rather than on instance boot. By doing so, we reduce the set of users possibly affected from all cloud-image users to all users of lxc or lxd. Note, all users of lxd and lxc have been affected by this bug since at least 14.04. -- [1] https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-wily/debian/lxc.preinst#L55 [2] https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-wily/config/init/common/lxc-net.in Related bugs: * bug 1509414: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512980] Re: Please enable PPS in the Ubuntu build of ntpd
** Changed in: ntp (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512980 Title: Please enable PPS in the Ubuntu build of ntpd Status in ntp package in Ubuntu: New Bug description: NTPD includes a reference clock driver called "pps" which uses a modern kernel mechanism for pulse-per-second devices for very accurate timekeeping. PPS is particularly useful for anybody building a stratum 0 GPS-disciplined time server. Please could we enable the PPS driver in Ubuntu's build of NTP? http://doc.ntp.org/4.2.6/drivers/driver22.html Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Tested wily-proposed cloud-image running in local kvm. Started wily- proposed container via lxc (using ubuntu-cloud template), verified the container's lxcbr0 looks fine (10.0.4.1), verified networking works (via www.google.com). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers Status in lxc package in Ubuntu: Confirmed Bug description: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the image. When a container is started, it will dhcp on eth0 and get 10.0.3.X as expected. The problem comes when the lxc-net service that is already installed in that container starts and configures *its* lxcbr0 with 10.0.3.X. The networking inside the container is broken at that point. This affects LXC containers, and should affect LXD containers but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release (bug 1509390). The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && sudo service lxc-net stop && sudo service lxc-net start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427076] Re: [Ubuntu 15.10] Add Power LE support to libseccomp
@strosake/gcwilsonanyone: Do you have a link to the (set of) commits this involves? In assumption that this will be cherry picked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1427076 Title: [Ubuntu 15.10] Add Power LE support to libseccomp Status in libseccomp package in Ubuntu: Triaged Bug description: == Comment: #0 - George C. Wilson gcwil...@us.ibm.com - 2015-01-28 10:13:19 == seccomp mode 2 involves the parsing of BPF (Berkeley Packet Filter) configuration files to define system call filtering. Mode 2 is not currently supported on Power; this feature covers the addition of this support, which likely includes updates to the kernel and to libseccomp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1427076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
