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

Re: why package Signal in Debian? (was Re: Bug#1113746: ITP: node-noop6 -- No operation as a module using an arrow function)



Hey,

I would love to see signal-desktop in Debian. If upstream is that aggressive 
with old version, than yes the normal Debian stable is not working for signal-
desktop.
But it can be used in unstable/testing and -backports.  If forky release is 
taking place you can use a release-critical bug to make sure that it does not 
end up in stable on purpose, if no netter solution is found until than.
 
> Either way, given the (justified) negative reactions with this ITP, I
> will go back to the drawing board and probably withdraw this upload.

Yes, there are some reactions and a lot of open questions. But please don't 
see them as negative feedback. Several questions need answers, when forky will 
be released, but that is a lot time to find answers.  I would encourage you to 
start packaging signal-desktop and than we can find answers along the way.
A lot of discussion will get easier if signal-desktop is packaged, as than 
everyone can look at the package; sneak into the code etc.

Maybe release-team will accept a solution like for browsers to get new 
versions shipped to stable. But this discussion, about stable updates for 
signal, you should do with release-team via a bug on bts. But this discussion 
is a lot easier, if there is signal-desktop packaged, as than release-team/
security team can look at the code/package and together you'll find a solution.

Regards,

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: