Your message dated Sat, 3 Jan 2015 18:49:03 +0000 with message-id <20150103184903.GF10587@lupin.home.powdarrmonkey.net> and subject line Re: Bug#774206: release.debian.org: broken/buggy linux-target stack in Jessie has caused the Debian Bug report #774206, regarding unblock (pre-approval): linux-target stack 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.) -- 774206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774206 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release.debian.org: broken/buggy linux-target stack in Jessie
- From: Ritesh Raj Sarraf <rrs@debian.org>
- Date: Tue, 30 Dec 2014 14:53:47 +0530
- Message-id: <20141230092347.6551.7624.reportbug@learner.researchut.com>
Package: release.debian.org Severity: important The linux-target stack in Jessie is broken. It has many issues. After talking with the upstream maintainers, I put up a newer version in experimental. This build, though not bug free, is much better than what is currently slated for Jessie. I would like to see the current builds in experimental, be pushed for Jessie. But given the freeze, I want opinion here first. http://packages.qa.debian.org/targetcli http://packages.qa.debian.org/rtslib http://packages.qa.debian.org/configshell Please be aware that Linux Target mgmg tools, targetcli, has gone major changes from 2.x to 3.x. And there has been no backward compatibility or settings migration. Users are expected to manually migrate their settings to the new environment -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
- To: rrs@debian.org, 774206-done@bugs.debian.org
- Subject: Re: Bug#774206: release.debian.org: broken/buggy linux-target stack in Jessie
- From: Jonathan Wiltshire <jmw@debian.org>
- Date: Sat, 3 Jan 2015 18:49:03 +0000
- Message-id: <20150103184903.GF10587@lupin.home.powdarrmonkey.net>
- In-reply-to: <[🔎] 54A81F39.4070100@debian.org>
- References: <20141230092347.6551.7624.reportbug@learner.researchut.com> <20141230112325.GL15483@lupin.home.powdarrmonkey.net> <54A2A00F.3060009@debian.org> <[🔎] 20150103122121.GC10587@lupin.home.powdarrmonkey.net> <[🔎] 54A81F39.4070100@debian.org>
Control: tag -1 - moreinfo On Sat, Jan 03, 2015 at 10:26:25PM +0530, Ritesh Raj Sarraf wrote: > Contro: tag -1 -moreinfo > > On 01/03/2015 05:51 PM, Jonathan Wiltshire wrote: > >> I know this request is not in line with freeze policy. But we already > >> > have an RC bug against targetcli. So, if we cannot accommodate this > >> > exception, I'd rather prefer to see LIO removed for Jessie. > > Well, your diff for configshell does nothing, so that's a no. Does the new > > targetcli package actually fix the RC bug or not? It's not closed in the > > changelog. > > > > The RC issue is about upgrade path from 2.x to 3.x. No. That bug is not > fixed. And won't be fixed. I don't have the resource to fix it at this > point. > > > BTW, targetcli got removed from testing because of that RC bug, yesterday. Removal hints added. -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51Attachment: signature.asc
Description: Digital signature
--- End Message ---