Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Noise crashes initiating call, Signal does not #605
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Mar 10, 2017
Contributor
We don't make any changes to Signal, so it doesn't make sense to report issues here. Noise is simply a rebranded build and is explicitly not going to carry any patches to the code anymore. That means no upstream issues are going to be fixed even if it would only require changing one line of code. This is also the issue tracker for CopperheadOS and Noise isn't part of CopperheadOS.
|
We don't make any changes to Signal, so it doesn't make sense to report issues here. Noise is simply a rebranded build and is explicitly not going to carry any patches to the code anymore. That means no upstream issues are going to be fixed even if it would only require changing one line of code. This is also the issue tracker for CopperheadOS and Noise isn't part of CopperheadOS. |
thestinger
closed this
Mar 10, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vvug
Mar 10, 2017
@thestinger I know, but as Noise always crashes when starting a call, while Signal never crashes, and the source is the same, then the problem is clearly with your build process.
If you don't want to see these bugs reported here just open the issue tracker for Noise. Where do you expect people reporting them?
vvug
commented
Mar 10, 2017
|
@thestinger I know, but as Noise always crashes when starting a call, while Signal never crashes, and the source is the same, then the problem is clearly with your build process. If you don't want to see these bugs reported here just open the issue tracker for Noise. Where do you expect people reporting them? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Mar 10, 2017
Contributor
It's not my code, so I don't really want to receive bug reports for it. I disabled the issue tracker once having a fork with changes was no longer necessary.
then the problem is clearly with your build process.
It's not my build process. It's the standard build process they provide. You said yourself that you run into the problem with your own builds of Signal.
If Noise is going to create maintenance / support work, I can just stop providing it and have people download the Signal web site builds that update themselves and require unknown sources enabled. I am only providing a more convenient option under the condition that it's not taking much time.
|
It's not my code, so I don't really want to receive bug reports for it. I disabled the issue tracker once having a fork with changes was no longer necessary.
It's not my build process. It's the standard build process they provide. You said yourself that you run into the problem with your own builds of Signal. If Noise is going to create maintenance / support work, I can just stop providing it and have people download the Signal web site builds that update themselves and require unknown sources enabled. I am only providing a more convenient option under the condition that it's not taking much time. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Mar 10, 2017
Contributor
I would rather just redistribute their Play builds via our F-Droid repository if it was permitted...
|
I would rather just redistribute their Play builds via our F-Droid repository if it was permitted... |
vvug commentedMar 10, 2017
Cable is affected by this bug, affecting self-compiled versions of Signal:
WhisperSystems/Signal-Android#6355
The bug does not affect the official Signal builds.