[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#789917: marked as done (gfortran-<triplet>: leaves alternatives after purge: /usr/bin/<triplet>-f{77, 95})

Your message dated Tue, 8 Dec 2015 15:33:06 +0100
with message-id <5666EA22.9050505@debian.org>
and subject line Re: gfortran-<triplet>: leaves alternatives after purge: /usr/bin/<triplet>-f{77, 95}
has caused the Debian Bug report #789917,
regarding gfortran-<triplet>: leaves alternatives after purge: /usr/bin/<triplet>-f{77, 95}
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
789917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789917
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gfortran-aarch64-linux-gnu,gfortran-arm-linux-gnueabi,gfortran-arm-linux-gnueabihf,gfortran-mips-linux-gnu
Version: 4.9.2-10.1
Severity: important
User: debian-qa@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

The leftover files are actually alternatives that were installed by the
package but have not been properly removed.

While there is ongoing discussion how to remove alternatives correctly
(see https://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).

Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove <name> <path>'.

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

>From the attached log (scroll to the bottom...):

0m56.0s ERROR: WARN: Broken symlinks:
  /usr/bin/aarch64-linux-gnu-f95 -> /etc/alternatives/aarch64-linux-gnu-f95
  /usr/bin/aarch64-linux-gnu-f77 -> /etc/alternatives/aarch64-linux-gnu-f77
  /etc/alternatives/aarch64-linux-gnu-f95 -> /usr/bin/aarch64-linux-gnu-gfortran
  /etc/alternatives/aarch64-linux-gnu-f77 -> /usr/bin/aarch64-linux-gnu-gfortran

0m59.1s ERROR: FAIL: Package purging left files on system:
  /etc/alternatives/aarch64-linux-gnu-f77 -> /usr/bin/aarch64-linux-gnu-gfortran	 not owned
  /etc/alternatives/aarch64-linux-gnu-f95 -> /usr/bin/aarch64-linux-gnu-gfortran	 not owned
  /usr/bin/aarch64-linux-gnu-f77 -> /etc/alternatives/aarch64-linux-gnu-f77	 not owned
  /usr/bin/aarch64-linux-gnu-f95 -> /etc/alternatives/aarch64-linux-gnu-f95	 not owned


cheers,

Andreas

Attachment: gfortran-aarch64-linux-gnu_4.9.2-10.1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Version: 4:5.2.1-5

now built from the gcc-defaults source package. not installed at all.

--- End Message ---
Reply to: