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

Bug#611364: desktop-base: Please document the reason for the "sync" usage in postinst



Package: desktop-base
Version: 6.0.5
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi

I hear that desktop-base uses "sync" in the postinst and that it has a valid
reason for doing so.  That being said, the postinst does not have any inline
documentation/comments clarifying it.

It might also be prudent document the consequences of (or even emit a
warning if) eatmydata (or similar) is used.

~Niels

- -- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages desktop-base depends on:
ii  librsvg2-common               2.26.3-1   SAX-based renderer library for SVG

desktop-base recommends no packages.

Versions of packages desktop-base suggests:
pn  gnome | kde-standard | xfce4  <none>     (no description available)

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJNQsXUAAoJEAVLu599gGRCpIEP/1Pon2aOKFT8Dz4u3Ofn2Blq
7DWjfFTOALU0ASSeIQmhaP2o7KHnfAw9MJaVJ7LgqdQJmduFIBPT3akP3qBhv3G4
hFaNlyfAfmHV19HY6nQnEUyV9SpwnH0+APZ1lvpA/uFzFCWM0YjgzgV7NgOt1mqU
knBexDSK9j+Zk7qOdkqq1dwyhBjzxnGC66URCCu6FetE/Ck2zXEuTZo6QT1anqbn
fF5GCXlD9uAmfLkBIJUn5cqVZ6uAd30erONcoDf8RAWey9jZmHpTRm+foF9oGC79
txusnL8MKMI/LvoPyXiwXGx8Jy+VCL0cz9QOTk6Ie+GTvQ4a/6N58mAbgNQQKcq6
JkYOAhd28r3XiwGqqn6Qu6DEdP594ghmLOleVs2j7wIjAvQehRIvQFbsenJz0XYs
ckz2VjEtBPb+HeBV+wVp78fhSgZUY1mCZeilq/JFmDuiAyzX6J+ehz/vW9UjzXmb
B9NsQAvXvgf07ZVYRa6pxA19nz5f9XxEVusH7Mc/E6MOAPROM+9//fpECWEleEK7
gyvdig/QbM6nXRFTTXT5FgZL396HH7BKZhhYhZTu56AWbviL10x/pvISeC+pIvpw
pztuX9pVsTj+SZzpMno4dFqQ6H3VQs5IxRT/PoikBg8+1Or1yMlJQxG9nDdRso4a
b6a4/iQUuSaskfOm7Gcm
=ozhn
-----END PGP SIGNATURE-----




Reply to: