On Tue, Dec 30, 2014 at 06:22:31PM +0530, Ritesh Raj Sarraf wrote: > On 12/30/2014 04:53 PM, Jonathan Wiltshire wrote: > >> > I would like to see the current builds in experimental, be pushed for Jessie. But given the freeze, I want opinion here first. > > This isn't enough information for any of us to give you an opinion; please > > send source debdiffs. It's probably wise to include some explanation of the > > changes, since your changelogs are mostly "new upstream release". > > > That is the core of the problem. LIO is a fairly new stack. The kernel > component was merged, IIRC, around 2 yrs ago. > > For the management stack, the startup organization behind it has been > going rounds. THey have shuffled through licensing, and then Red Hat > forked LIO Management tools. I guess all this has led to slow > development in the past. > > > Recently, me and Jerome (upstream LIO maintainer) met. Based on our > conversation, I uploaded a revised snapshot of LIO. But it had to go > into experimental because of the freeze. > > > As requested, I've attached the debdiff for all the conponenets of LIO, > i.e. configshell, rtslib and targetcli. > > > 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. Please remove the moreinfo tag when you reply, or you may not get a repsonse. -- Jonathan Wiltshire jmw@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Attachment:
signature.asc
Description: Digital signature