Your message dated Sun, 27 Jan 2019 10:12:45 +0900
with message-id <[email protected]>
and subject line Re: Bug#837379: mime-support: purge left files on system
has caused the Debian Bug report #837379,
regarding mime-support: purge left files on system
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 [email protected]
immediately.)
--
837379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837379
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mime-support
Version: 3.60
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
by running piuparts for scons I get:
[quote]
0m52.2s DEBUG: Recording chroot state
0m54.7s DEBUG: Modified(user, group, mode, size, target): /var/lib/dpkg/info
/mime-support.list expected(root, root, - 100644, 40, None) != found(root,
root, - 100644, 855, None)
0m54.7s DEBUG: Modified(user, group, mode, size, target): /etc/mime.types
expected(root, root, - 100644, 24241, None) != found(root, root, - 100644,
24301, None)
0m54.8s ERROR: FAIL: Package purging left files on system:
/etc/mailcap not owned
/usr/bin/compose -> run-mailcap owned by: mime-support
/usr/bin/edit -> run-mailcap owned by: mime-support
/usr/bin/print -> run-mailcap owned by: mime-support
/usr/bin/run-mailcap owned by: mime-support
/usr/bin/see -> run-mailcap owned by: mime-support
/usr/lib/mime/debian-view owned by: mime-support
/usr/lib/mime/mailcap owned by: mime-support
/usr/lib/mime/packages/mime-support owned by: mime-support
/usr/sbin/update-mime owned by: mime-support
/usr/share/bug/mime-support/ owned by: mime-support
/usr/share/bug/mime-support/presubj owned by: mime-support
/usr/share/doc/mime-support/ owned by: mime-support
/usr/share/doc/mime-support/changelog.gz owned by: mime-support
/usr/share/doc/mime-support/copyright owned by: mime-support
/usr/share/man/man1/compose.1.gz -> run-mailcap.1.gz owned by: mime-support
/usr/share/man/man1/edit.1.gz -> run-mailcap.1.gz owned by: mime-support
/usr/share/man/man1/print.1.gz -> run-mailcap.1.gz owned by: mime-support
/usr/share/man/man1/run-mailcap.1.gz owned by: mime-support
/usr/share/man/man1/see.1.gz -> run-mailcap.1.gz owned by: mime-support
/usr/share/man/man5/mailcap.5.gz owned by: mime-support
/usr/share/man/man5/mailcap.order.5.gz owned by: mime-support
/usr/share/man/man8/update-mime.8.gz owned by: mime-support
/var/lib/dpkg/info/mime-support.conffiles not owned
/var/lib/dpkg/info/mime-support.md5sums not owned
/var/lib/dpkg/info/mime-support.postinst not owned
/var/lib/dpkg/info/mime-support.prerm not owned
/var/lib/dpkg/info/mime-support.triggers not owned
0m54.8s ERROR: FAIL: After purging files have been modified:
/etc/mime.types owned by: mime-support
/var/lib/dpkg/info/mime-support.list not owned
[/quote]
- -- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
mime-support depends on no packages.
Versions of packages mime-support recommends:
ii bzip2 1.0.6-8
ii file 1:5.28-4
ii xz-utils 5.1.1alpha+20120614-2.1
mime-support suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJX1PouAAoJEAn4nzyModJd2FcQAMu4RJ7oyvGQ8m9PHmCgsusz
qx1uXXALQ23gHR5UR5HsPbvZnGcxQmZvQI3M7On3EyT4j+y88lR++wj7q6rr9du+
ec7WGAI+e89XwpJJyQCjY8eOispITFcTtVPjAGa6EmiQTrrcBjEa8YwYTUlOflVn
AXC/HOXCUhXXtIhsQRVhgolzHUqWgI3vZve1GDTrhGjyeTkMZX1gAkx9tUMfmBxm
m3r5I4ZludGes0I+fVi0UqFk/Pa2M2ISVI9/MNdE/OnLMO6JRer9pbpvuvqGqDCR
6DCtNFxU+H4LXVHh58JGSy11zHXu4qV75oDMvQX54Yl7sNACzqRTMMZmdhfe0jDn
uxzDe0AkeTk6VhQKyCFVKrzB4EUq0lB9cte4qh1Fhsj2QvFG0LLqFwbG63aKnP01
wuJi651empIDOfTxNCD8SH7zi2ymDVELf2+w38wZOtgqjiiLO25DFGXnklK4aS76
Aa+RS6QZ6Xr4zH78PD+FPWVIv1RSJvrozO2YlfAGpm4DRi9ckwC//seHSrEqdfJY
RzNR142HVYB9owKoh/8N8k899/OudreC9ym6PievNNJKJrxerXwjxYzEKaPIyNEy
siPIzocyZUiOxLuoGrwNRANNhcptQbfl29HdLw7Po2AU3w6gH7odwTeO5tkYy9Gi
YK2HBKhWzXHHNhpH4SEc
=1nuN
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
> Am Montag, den 12.12.2016, 21:40 +0900 schrieb Charles Plessy:
> >
> > I am a bit puzzled: the main piuparts checks are running fine.
> >
> > https://piuparts.debian.org/sid/source/p/piuparts.html
> >
> > Are you sure that the problem is with mime-support, or could there be
> > a problem with your piuparts installation ?
Le Tue, Dec 27, 2016 at 09:08:30PM +0100, Jörg Frings-Fürst a écrit :
>
> I don't think. I use piuparts with a daily updated sid and stretch
> chroot.
Hi Jörg,
happy new year 2019, time flies fast !
Since the piuparts checks running on the Debian infrastructure are not
reporting problems, I am closing this bug. Please feel free to reopen
it, but in that case, may I ask you to put the Piuparts developers team
in the loop, so that you can work out with them why our tests are not
reporting an issue ?
Have a nice Sunday,
Charles
--
Charles Plessy
Akano, Uruma, Okinawa, Japan
--- End Message ---
