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

Bug#865632: release-notes: document that 'iscsitarget' was dropped in Stretch

Package: release-notes
Severity: important
X-Debbugs-Cc: debian-release@lists.debian.org

Dear release team & release notes editors,

I recently received a bug report from a person using the 'iscsitarget',
which was dropped in Stretch, as it hasn't seen any update upstream
since 2014 - and the kernel module doesn't compile anymore with recent

See: https://bugs.debian.org/865628

The alternative in Stretch is to use the LIO stack to configure a
software iSCSI target, but there is no automated upgrade path (it's a
completely different piece of software, unrelated to IET), and the
configuration is different.

Unfortunately the release notes don't mention this - so if at all
possible, I would propose to add a section to the release notes of
Stretch that document this.

I propose the following language (feel free to adjust this in any way
you'd want to):

   iSCSI Enterprise Target (IET) no longer part of Stretch

   The iSCSI Enterprise Target (IET), packaged in the 'iscsitarget'
   package in previous Debbian versions, is not part of Debian
   Stretch anymore, as it will not work with recent kernel versions,
   and the project has seen no development activity in recent years.

   Users of IET are encouraged to switch to the LIO stack that is
   fully supported in Debian Stretch. The 'targetcli-fb' provides
   the configuration utility for the LIO iSCSI target.

   As the LIO stack was developed independently of the IET, the
   configuration has to be migrated manually.


-- System Information:
Debian Release: 9.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply to: