group.of.nepali.translators team mailing list archive

[Tyler Hicks <tyhicks@xxxxxxxxxxxxx>]

** Also affects: apparmor (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Low
     Assignee: Tyler Hicks (tyhicks)
       Status: In Progress

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: apparmor (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: apparmor (Ubuntu Xenial)
     Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Description changed:

+ [Impact]
+ Confusing output from a diff command executed during the apparmor update process leaves users concerned about the state of their system.
+ 
+ [Test Case]
+ 1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is installed
+ 
+ 2. Update to the apparmor package in -proposed
+ 
+ 3. Look at the output during the update process to verify that the
+ following message is *not* printed:
+ 
+   Files /var/lib/dpkg/info/apparmor.md5sums and
+ /var/lib/apparmor/profiles/.apparmor.md5sums differ
+ 
+ [Regression Potential]
+ Considered to be extremely low. The change is a one-liner that pipes the stdout of diff command to /dev/null (the -q option of diff is not sufficient).
+ 
+ [Original description]
+ 
  Upon applying the latest Ubuntu routine-update, I observed these
  messages:
  
  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ...
  update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ
  
  "The reason why I am filing a bug report" is the LAST line.  I presume
  that if md5sums do not agree, something was probably done improperly in
  preparing this particular software-update blast.
  
  However, in-passing, I would also point out line #3, about "start and
  stop actions no longer supported." That seems to me to be something (of
  much less importance, obviously) that might have been overlooked.  (I've
  seen =that= message for some time now.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug 17 14:22:55 2016
  InstallationDate: Installed on 2016-03-02 (168 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro
  SourcePackage: apparmor
  Syslog:
-  Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled
-  Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled
-  Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled
-  Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled
+  Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled
+  Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled
+  Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled
+  Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614215

Title:
  "md5sums differ" message seems to indicate an install problem

Status in AppArmor:
  Invalid
Status in Ubuntu GNOME:
  Invalid
Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Xenial:
  In Progress
Status in apparmor source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  Confusing output from a diff command executed during the apparmor update process leaves users concerned about the state of their system.

  [Test Case]
  1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is installed

  2. Update to the apparmor package in -proposed

  3. Look at the output during the update process to verify that the
  following message is *not* printed:

    Files /var/lib/dpkg/info/apparmor.md5sums and
  /var/lib/apparmor/profiles/.apparmor.md5sums differ

  [Regression Potential]
  Considered to be extremely low. The change is a one-liner that pipes the stdout of diff command to /dev/null (the -q option of diff is not sufficient).

  [Original description]

  Upon applying the latest Ubuntu routine-update, I observed these
  messages:

  Setting up apparmor (2.10.95-0ubuntu2.2) ...
  Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ...
  update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ

  "The reason why I am filing a bug report" is the LAST line.  I presume
  that if md5sums do not agree, something was probably done improperly
  in preparing this particular software-update blast.

  However, in-passing, I would also point out line #3, about "start and
  stop actions no longer supported." That seems to me to be something
  (of much less importance, obviously) that might have been overlooked.
  (I've seen =that= message for some time now.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug 17 14:22:55 2016
  InstallationDate: Installed on 2016-03-02 (168 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro
  SourcePackage: apparmor
  Syslog:
   Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled
   Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled
   Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled
   Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1614215/+subscriptions