[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-11-22 Thread Ian Weisser
Happy to discuss and help...in the support forums.
This CLOSED bug report is not the appropriate location to help people 
troubleshoot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-11-22 Thread Ian Weisser
Another (complimentary) solution for accumulating kernels in an LVM
environment: http://blog.surgut.co.uk/2016/11/boot-less-lvm-rootfs-in-
zesty.html

The fix to this bug prevents kernels from accumulating. 
That complimentary solution eliminates the tiny /boot partition, eliminating 
the space problem on LVM desktops and laptops...though not on other 
space-constrained devices.

My updated u-u on Ubuntu 16.04 and 16.10 is working just great, and
correctly preventing kernels from accumulating. However, we have seen
similar-looking apt problems in the support forums: A few systems to
continue to run out of /boot space. Upon investigation, these are
usually due to unconfigured/half-configured packages or user confusion
with the settings.

If your unattended-upgrade is not working properly, and your system
continues to run out of /boot space, please seek help in a support forum
before posting permanently to this CLOSED bug report.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1624644] Re: Unable to remove packages that become unused in conjunction with updating by other software

2016-09-17 Thread Ian Weisser
Can you please talk us through exactly how to reproduce the issue?
I have used u-u with a wide variety of other apt frontends in 16.04 without 
seeing that problem yet.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  Unable to remove packages that become unused in conjunction with
  updating by other software

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When using default settings for unattended-upgrades i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  U-U is unable to remove packages that become unused in conjunction with 
updating by other software such as update-manager or apt full-upgrade. This is 
because U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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


Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-11 Thread Ian Weisser
Jarno Suni,

This bug report ran it's course, and 'Fix Released' is another way of
saying 'Closed.' You can discuss it, but no developer is likely to read
it...to them, it's a closed issue. It's fixed, and won't be unfixed.
The patch is released, and won't be reverted. The normal workflow is to
file a new bug, not to reopen or discuss a closed bug.

Bug 1357093 is 'Fix Released' because I duplicated the original
reporter's problems, triaged the bug, and forwarded enough information
to a developer who agreed with my triage and decided to fix it. Upon
testing the fix (repeatedly), my duplication of the original reporter's
problem is really fixed.

If you have a triage-able problem with the unattended-upgrades package,
please open a new bug report and provide enough information so I can
triage it. I cannot generally triage a problem that I cannot duplicate.

If all you know is 'it should work but does not work', then please jump
into a support forum (like Ubuntuforums) and let the experts there help
you figure out how to duplicate or triage it. Similar symptoms may come
from very different causes. Having an unresolved problem is really,
really frustrating. Been there.

I'm quite happy to discuss kernel header dependencies and go into much
greater detail...but doing so in this bug report would be rather
counterproductive. The issue is closed, and most of the questions seem
unrelated to the original bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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


Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-10 Thread Ian Weisser
Jarno Suni,

That possible cause seems irrelevant to Unattended-Upgrades. Any
package installed by any front-end to apt will be upgraded. U-U doesn't
know what packages are installed, nor care. U-U simply tells aptdaemon
to upgrade packages from the repositories authorized by the user. U-U
does not duplicate nor replace Software Updater, and both can safely be
used.

Try running 'apt autoremove' (16.04) or 'apt-get autoremove'
(12.04/14.04).

If those kernels are not removed, then your problem is the apt-marking, 
not U-U. There are several ways to prevent automatically marking kernel
packages as 'auto' - the most common is by installing kernel header
packages.

If those kernels are removed, then check the U-U logs in /var/log to
ensure that U-U is really operating.

A bug report is an awful place to try to troubleshoot in this way. If
you open a thread on UbuntuForums, we may be able help you better.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-09 Thread Ian Weisser
Jarno Suni,

Okay, I stand corrected on that statement.

Please explain how you determined that Unattended Upgrades is the
culprit, instead kernel header packages or user changes to apt-marking
or other possible causes for the symptom you describe.

With the information so far, I cannot duplicate your issue on my test
system. How can I do so?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-08 Thread Ian Weisser
There seems a lot of confusion in this bug report about which pieces of
the system work together to cause this problem, and which pieces should
be responsible for fixing it.

Marking kernels as eligible for autoremoval is done by apt. The apt
package provides /etc/kernel/postinst.d/apt-auto-removal, which sets the
rules for marking kernel packages eligible for autoremoval. If you
discover a system that keeps more than three kernels (and isn't already
broken), run 'apt autoremove' manually. If the system still has more
than three kernels, then see if you can figure out why and then file a
bug against Apt.

But apt only marks. Apt doesn't actually pull the trigger and run an
autoremove.

Compounding the problem is another issue with apt: Apt in 16.04 and
earlier queues autoremoval instead of running it first (or last...or
scheduled). This is what makes broken systems harder to fix. Out-of-
space hits before autoremove.

Unattended-Upgrades prior to 16.04, if the option is enabled, merely
runs 'apt autoremove' via aptdaemon. U-U does not check nor care what
packages need to be removed. U-U does not check nor care if the system
is LVM/Encrypted or has a small separate /boot partition. None of that
is part of U-U's job.

U-U developers in 16.04 addressed this problem (even though it's
arguably not U-U's problem) by checking if packages are already marked
eligible-for-autoremove at the beginning of the run. If so, it
autoremoves them before doing anything else. Again, U-U doesn't care
about which packages happen to be marked, or wheter the system has a
small /boot partition.

In 16.04, the problem is undeniably fixed. The additional functionality
of U-U has prevented stale kernels from accumulating on all my test
systems. However, developers have understandably shown little interest
in backporting that particular fix.

And there are other options to integrate the fix better into apt itself
instead of U-U. For example, aptdaemon does seem to have queue
management tools - it should be possible to move an 'autoremove' to the
head of queue (incidentally making fixes much easier). Or we can add
another kernel hook file to /etc/kernel/postinst.d/ to trigger an
autoremove upon kernel installs (instead of U-U's daily check). Or we
can add a startup/cron.daily service that simply checks for existence of
a small /boot partition and runs autoremove before (or after) the daily
apt update. Or we can have aptdaemon catch out-of-space errors (instead
of simply passing them), run autoremove, and then try the install again.

Almost none of these possible solutions would be implemented in
Unattended Upgrades.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1612301] Re: can't upgrade from 14.04 to 16.04 LTS

2016-08-22 Thread Ian Weisser
Changed package. /usr/lib/python3/dist-packages/apt/progress/text.py is
provided by python3-apt

** Package changed: ubuntu-release-upgrader (Ubuntu) => python-apt
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1612301

Title:
  can't upgrade from 14.04 to 16.04 LTS

Status in python-apt package in Ubuntu:
  New

Bug description:
  I'm trying to do a do-release-upgrade from a 14.04 system to a 16.04
  system, and it tells me can't, because I'd be using on-standard
  package sources. but I'm not. thus I wonder what's wrong

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CrashDB: ubuntu
  Date: Thu Aug 11 17:19:50 2016
  InstallationDate: Installed on 2011-11-09 (1736 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to trusty on 2016-08-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1612301/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-02-11 Thread Ian Weisser
*** This bug is a duplicate of bug 1267059 ***
https://bugs.launchpad.net/bugs/1267059

Fix included in upstream release: unattended-upgrades 0.89 30 JAN 2016
Uploaded to Ubuntu 16.04 on 02 FEB 2016.

   * Add `Unattended-Upgrade::Remove-New-Unused-Dependencies` that
 defaults to "yes". This ensures that older kernel
 get automatically cleaned up and /boot will not overflow.
 LP: #1267059

Marking this bug as a duplicate of LP: #1267059 so it gets closed
automatically when appropriate.

** This bug has been marked a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1323593] Re: Unattended upgrades crash

2016-02-11 Thread Ian Weisser
*** This bug is a duplicate of bug 1267059 ***
https://bugs.launchpad.net/bugs/1267059

** This bug is no longer a duplicate of bug 1357093
   Kernels not autoremoving, causing out of space error on LVM or Encrypted 
installation or on any installation, when /boot partition gets full
** This bug has been marked a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1323593

Title:
  Unattended upgrades crash

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Based this bug report upon https://bugs.launchpad.net/ubuntu/+source
  /unattended-upgrades/+bug/1052360/comments/17

  Installed latest updates on Xubuntu Trusty, immediately during the
  update process the system detected an error, after reboot an error
  report again emerged, hence reporting this bug as suggested above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 27 12:40:58 2014
  InstallationDate: Installed on 2014-05-17 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1323593/+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 1294195] Re: Please consider enabling Unattended-Upgrade::Remove-Unused-Dependencies by default

2016-02-11 Thread Ian Weisser
*** This bug is a duplicate of bug 1267059 ***
https://bugs.launchpad.net/bugs/1267059

** This bug is no longer a duplicate of bug 1357093
   Kernels not autoremoving, causing out of space error on LVM or Encrypted 
installation or on any installation, when /boot partition gets full
** This bug has been marked a duplicate of bug 1267059
   "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1294195

Title:
  Please consider enabling Unattended-Upgrade::Remove-Unused-
  Dependencies by default

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu today with full disk encryption you end up
  with a separate small /boot partition (approx 200Mb).  It doesn't take
  long for this to fill up with old kernels.

  While we mark old kernels for auto-removal nothing (on the default
  system) actually triggers removal of unused packages; a human needs to
  invoke (or arrange to be invoked) 'apt-get autoremove'.

  /etc/apt/apt.conf.d/50unattended-upgrades documents an
  Unattended-Upgrade::Remove-Unused-Dependencies configuration option.
  I'd suggest we consider enabling this option by default on new
  installs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1294195/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-02-11 Thread Ian Weisser
Fix committed upstream https://github.com/mvo5/unattended-
upgrades/commit/d6232a8b904aa2079cc959072a59e12b580252eb


** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Committed

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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


Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install

2016-01-05 Thread Ian Weisser
Please do not spam bug report with "me too!" or "this bug is awful!"
comments.

The bug report is a living document used by the triagers and developers
to share data, many of them volunteers, and noise makes their job
harder.

A fix has has already been made in the upstream git, and is awaiting
merge. See https://github.com/mvo5/unattended-upgrades/pull/19

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted install

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1323593] Re: Unattended upgrades crash

2015-12-23 Thread Ian Weisser
*** This bug is a duplicate of bug 1357093 ***
https://bugs.launchpad.net/bugs/1357093

** This bug has been marked a duplicate of bug 1357093
   Kernels not autoremoving, causing out of space error on LVM or Encrypted 
install

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1323593

Title:
  Unattended upgrades crash

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Based this bug report upon https://bugs.launchpad.net/ubuntu/+source
  /unattended-upgrades/+bug/1052360/comments/17

  Installed latest updates on Xubuntu Trusty, immediately during the
  update process the system detected an error, after reboot an error
  report again emerged, hence reporting this bug as suggested above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 27 12:40:58 2014
  InstallationDate: Installed on 2014-05-17 (10 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1323593/+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 1430119] Re: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2015-12-23 Thread Ian Weisser
*** This bug is a duplicate of bug 1385817 ***
https://bugs.launchpad.net/bugs/1385817

** This bug has been marked a duplicate of bug 1385817
   initscripts package fails to upgrade if there are local init scripts on the 
system with no LSB headers

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1430119

Title:
  package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Nothing

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  Date: Tue Mar 10 08:13:59 2015
  DuplicateSignature: package:unattended-upgrades:0.82.1ubuntu2.1:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2014-08-15 (206 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.82.1ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1430119/+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 1480401] Re: package unattended-upgrades (not installed) failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1

2015-12-23 Thread Ian Weisser
Not an unattended-upgrades issue.

See the DpkgTerminalLog.text file:
> insserv: Starting panasoniclpd-init depends on grub-common and therefore on 
> system facility `$all' which can not be true!

Your file /etc/init.d/panasoniclpd-init , which was not provided by Ubuntu, 
seems to have an inadequate header.
The suggested header corrections in 
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1385817/comments/2 seem 
likely to fix your problem.

Please consider filing a bug wherever you got panasoniclpd from, they
need to fix their file permanently for all users.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1480401

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  il sottoprocesso installato script di post-removal ha restituito lo
  stato di errore 1

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Maybe because of Panasonic KM-MB1900 multifunction unsupported.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Fri Jul 31 19:04:13 2015
  DuplicateSignature: package:unattended-upgrades:(not installed):il 
sottoprocesso installato script di post-removal ha restituito lo stato di 
errore 1
  ErrorMessage: il sottoprocesso installato script di post-removal ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2015-06-12 (49 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
il sottoprocesso installato script di post-removal ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1480401/+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 1470299] Re: package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-12-23 Thread Ian Weisser
This does not seem like an unattended-upgrades issue.
See the DpkgTerminalLog.txt file.

u-a is correctly triggering the package manager (that's what it does).
The error seems to be in update-rc.d, caused by the minidlna package:

insserv: There is a loop between service minidlna and lineakd if stopped
insserv:  loop involving service lineakd at depth 2
insserv:  loop involving service minidlna at depth 1
insserv: Stopping lineakd depends on minidlna and therefore on system facility 
`$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

14.10 is past end-of-life. Does this issue still occur in a newer
release of Ubuntu?

** Package changed: unattended-upgrades (Ubuntu) => minidlna (Ubuntu)

** Changed in: minidlna (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1470299

Title:
  package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in minidlna package in Ubuntu:
  Incomplete

Bug description:
  This occurred as the system was booting up.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: unattended-upgrades 0.82.8ubuntu0.3
  ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.5
  AptOrdering:
   unattended-upgrades: Install
   unattended-upgrades: Configure
  Architecture: amd64
  Date: Mon Jun 29 20:47:30 2015
  DuplicateSignature: package:unattended-upgrades:0.82.8ubuntu0.3:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-03-21 (831 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-05-07 (54 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-07T13:31:12.701689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/minidlna/+bug/1470299/+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 1294195] Re: Please consider enabling Unattended-Upgrade::Remove-Unused-Dependencies by default

2015-12-23 Thread Ian Weisser
*** This bug is a duplicate of bug 1357093 ***
https://bugs.launchpad.net/bugs/1357093

** This bug has been marked a duplicate of bug 1357093
   Kernels not autoremoving, causing out of space error on LVM or Encrypted 
install

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1294195

Title:
  Please consider enabling Unattended-Upgrade::Remove-Unused-
  Dependencies by default

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu today with full disk encryption you end up
  with a separate small /boot partition (approx 200Mb).  It doesn't take
  long for this to fill up with old kernels.

  While we mark old kernels for auto-removal nothing (on the default
  system) actually triggers removal of unused packages; a human needs to
  invoke (or arrange to be invoked) 'apt-get autoremove'.

  /etc/apt/apt.conf.d/50unattended-upgrades documents an
  Unattended-Upgrade::Remove-Unused-Dependencies configuration option.
  I'd suggest we consider enabling this option by default on new
  installs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1294195/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install

2015-12-21 Thread Ian Weisser
Developer of unattended upgrades has submitted a patch:
https://github.com/mvo5/unattended-upgrades/pull/19

** Changed in: apt (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => In Progress

** No longer affects: unattended-upgrades (Ubuntu)

** Package changed: apt (Ubuntu) => unattended-upgrades (Ubuntu)

-- 
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/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted install

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install with small /boot partition

2015-12-17 Thread Ian Weisser
** Summary changed:

- LVM or Encrypted install creates too small /boot partition
+ Kernels not autoremoving, causing out of space error on LVM or Encrypted 
install with small /boot partition

-- 
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/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted install with small /boot partition

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1357093/+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 1357093] Re: LVM or Encrypted install creates too small /boot partition

2015-12-17 Thread Ian Weisser
Ubiquity creates space for enough kernels. The system is not managing
that space later. Not ubiquity's fault.

These two issues together create the problem on a small /boot partition:
apt: apt-get remove/purge/autoremove is blocked by the (always-failing) kernel 
install (not enough space on device)
unattended-upgrade: 'autoremove' is disabled by default.

Adding both packages to the bug report. Removing ubiquity.

Workaround - How users can recover from the problem:
- You can use dpkg to manually remove older kernels until apt has enough space 
to work, or
- You can use dpkg --set selections to un-select the kernel packages for 
install, then run apt-get autoremove

Workaround - How users can prevent recurrence after successful recovery: 
- You can enable autoremoval in /etc/apt/apt.conf.d/50unattended-upgrades , or
- You can mark your wall calendar and manually run apt-get autoremove every few 
months

-- 
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/1357093

Title:
  LVM or Encrypted install creates too small /boot partition

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1357093/+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 1357093] Re: LVM or Encrypted install creates too small /boot partition

2015-12-17 Thread Ian Weisser
apt-get remove/purge/autoremove is blocked by the (always-failing)
kernel install (not enough space on device)


** Package changed: ubiquity (Ubuntu) => apt (Ubuntu)

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1357093

Title:
  LVM or Encrypted install creates too small /boot partition

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1357093/+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 1419839] Re: autoremove does not auto-remove unneeded dependencies

2015-05-20 Thread Ian Weisser
No longer able to reproduce this bug. Unsubscribing.

-- 
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/1419839

Title:
  autoremove does not auto-remove unneeded dependencies

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:

  ### Install 'synaptic'
  $ sudo apt-get install synaptic
  [...]
  The following NEW packages will be installed:
docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
libpango-perl librarian0 rarian-compat sgml-data synaptic

  ### Nothing wrong with apt markings
  $ apt-mark showauto docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  docbook-xml
  libcairo-perl
  libept1.4.12
  libglib-perl
  libgtk2-perl
  libpango-perl
  librarian0
  rarian-compat
  sgml-data

  $ apt-mark showmanual docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  synaptic

  ### Autoremove 'synaptic' - doesn't remove the 9 dependencies.
  $ sudo apt-get autoremove synaptic
  [...]
  The following packages will be REMOVED:
synaptic

  ### Check for unknown dependencies - none found
  $ sudo apt-get remove docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  [...]
  The following packages will be REMOVED:
docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
libpango-perl librarian0 rarian-compat sgml-data synaptic

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apt 1.0.9.2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  9 09:06:19 2015
  InstallationDate: Installed on 2014-12-18 (52 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.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/1419839/+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 1419839] [NEW] autoremove does not auto-remove unneeded dependencies

2015-02-09 Thread Ian Weisser
Public bug reported:

To reproduce:

### Install 'synaptic'
$ sudo apt-get install synaptic
[...]
The following NEW packages will be installed:
  docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
  libpango-perl librarian0 rarian-compat sgml-data synaptic

### Nothing wrong with apt markings
$ apt-mark showauto docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
docbook-xml
libcairo-perl
libept1.4.12
libglib-perl
libgtk2-perl
libpango-perl
librarian0
rarian-compat
sgml-data

$ apt-mark showmanual docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
synaptic

### Autoremove 'synaptic' - doesn't remove the 9 dependencies.
$ sudo apt-get autoremove synaptic
[...]
The following packages will be REMOVED:
  synaptic

### Check for unknown dependencies - none found
$ sudo apt-get remove docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
[...]
The following packages will be REMOVED:
  docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
  libpango-perl librarian0 rarian-compat sgml-data synaptic

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apt 1.0.9.2ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  9 09:06:19 2015
InstallationDate: Installed on 2014-12-18 (52 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

-- 
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/1419839

Title:
  autoremove does not auto-remove unneeded dependencies

Status in apt package in Ubuntu:
  New

Bug description:
  To reproduce:

  ### Install 'synaptic'
  $ sudo apt-get install synaptic
  [...]
  The following NEW packages will be installed:
docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
libpango-perl librarian0 rarian-compat sgml-data synaptic

  ### Nothing wrong with apt markings
  $ apt-mark showauto docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  docbook-xml
  libcairo-perl
  libept1.4.12
  libglib-perl
  libgtk2-perl
  libpango-perl
  librarian0
  rarian-compat
  sgml-data

  $ apt-mark showmanual docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  synaptic

  ### Autoremove 'synaptic' - doesn't remove the 9 dependencies.
  $ sudo apt-get autoremove synaptic
  [...]
  The following packages will be REMOVED:
synaptic

  ### Check for unknown dependencies - none found
  $ sudo apt-get remove docbook-xml libcairo-perl libept1.4.12 libglib-perl 
libgtk2-perl libpango-perl librarian0 rarian-compat sgml-data synaptic
  [...]
  The following packages will be REMOVED:
docbook-xml libcairo-perl libept1.4.12 libglib-perl libgtk2-perl
libpango-perl librarian0 rarian-compat sgml-data synaptic

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: apt 1.0.9.2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  9 09:06:19 2015
  InstallationDate: Installed on 2014-12-18 (52 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.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/1419839/+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