README.feature-removal-schedule 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118
  1. This is a list of features that are scheduled to be removed from dpkg.
  2. What: fallback of dpkg-source to source format "1.0" without explicit debian/source/format
  3. Status: deprecated
  4. When: 1.17.x
  5. Warning: program and lintian (missing-debian-source-format)
  6. Why:
  7. With the support of multiple source formats, the user should be explicit
  8. about the desired source format. The fallback to "1.0" is there only for
  9. backwards compatiblity but will be removed once all packages have the
  10. debian/source/format file. This is unlikely to happen before 1.17.x.
  11. What: Source-Version (substvar)
  12. Status: obsolete
  13. When: 1.16.x
  14. Warning: lintian (substvar-source-version-is-deprecated)
  15. Why:
  16. The semantics of Source-Version are missleading when applied to binNMUs.
  17. Should switch to use binary:Version or source:Version substvars.
  18. What: Revision, Package-Revision, Package_Revision, Class, Recommended,
  19. Optional (field)
  20. Status: obsolete
  21. When: 1.15.x
  22. Warning: program
  23. Why:
  24. These fields have been superseded by either other fields with better names
  25. or values in other fields.
  26. What: -u, --udeb (dpkg-scanpackages option)
  27. Status: deprecated
  28. When: 1.16.x
  29. Warning: program
  30. Why:
  31. This option has been superseded by -tudeb.
  32. What: support of PGP
  33. Status: deprecated
  34. When: 1.15.x
  35. Warning: program
  36. Why:
  37. PGP is not part of Debian and GnuPG has been the standard tool for digital
  38. signatures for several years already. Supporting only GnuPG enables us to
  39. rely on some of its features.
  40. What: --print-installation-architecture (dpkg option)
  41. Status: obsolete
  42. When: 1.15.x
  43. Warning: program
  44. Why:
  45. Obsoleted long time ago (2005-01-22). Remaining packages should switch to
  46. use 'dpkg --print-architecture'.
  47. What --forget-old-unavail (dpkg option)
  48. Status: obsolete
  49. When: 1.16.x
  50. Warning: program
  51. Why:
  52. Purged packages are properly cleaned up now by dpkg, and old unavailable
  53. leftovers are automatically cleaned up on database parsing. So there's no
  54. need anymore for this manual action.
  55. History of feature removals
  56. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  57. What: cleanup-info (program)
  58. Status: removed
  59. Since: 1.15.0
  60. Why:
  61. This program was needed long time ago to fixup broken info dir files
  62. generated by buggy install-info programs. Should not be needed anymore.
  63. What: --largemem, --smallmem (dpkg option)
  64. Status: removed
  65. When: 1.15.1
  66. Why:
  67. These options have been no-ops for a long time.
  68. What: --force-auto-select (dpkg option)
  69. Status: removed
  70. When: 1.15.1
  71. Why:
  72. This option has been a no-op for so long, that there's no traces on git
  73. history of its usage.
  74. What: recommended, contrib, base (priority)
  75. Status: removed
  76. When: 1.15.1
  77. Why:
  78. These priorities have been superseded by either other fields or values in
  79. other fields.
  80. What: 822-date (program)
  81. Status: removed
  82. When: 1.15.1
  83. Why:
  84. Should switch to use 'date -R'.
  85. What: support of custom changelog parsers understanding only -v
  86. Status: removed
  87. Since: 1.15.5
  88. Why:
  89. The debian changelog parser has been enhanced. It supports new options
  90. that enable more fine-grained retrieval of information. Those new options
  91. will be used by scripts (like dpkg-genchanges).
  92. .
  93. Custom changelog parsers must be updated to support the new API (see
  94. dpkg-parsechangelog(1) and README.api).
  95. What: support for environment variable DPKG_NO_TSTP
  96. Status: removed
  97. Since: 1.15.6
  98. Why:
  99. Having two ways to let the administrator get to a shell on conffile prompt
  100. is confusing, it also difficults setting up a consistent environment to be
  101. used by external programs.