Bug#855541: purple-matrix: Not ready for release yet
On Tue, Nov 09, 2021 at 09:22:36PM +0100, Alberto Garcia wrote: > FYI I decided to give this package for adoption. I'll request its > removal from the archive if there are no volunteers to take over its > maintenance after some time. > > https://bugs.debian.org/998660 I just requested its removal: https://bugs.debian.org/1018077 Berto
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Sep 28, 2020 at 07:03:45PM +0200, Alberto Garcia wrote: > I think that this project is essentially dead, there has never been > a release and as you say there hasn't been changes in almost a year. > > I have stopped using it myself and the reason why I didn't ask for > its removal from Debian is that it's a very small package with a > very low manteinance burden (and because popcon shows that it has > some users). FYI I decided to give this package for adoption. I'll request its removal from the archive if there are no volunteers to take over its maintenance after some time. https://bugs.debian.org/998660 Berto
Bug#855541: purple-matrix: Not ready for release yet
On Tue, Sep 22, 2020 at 09:51:14PM +0200, Alex ARNAUD wrote: > > I think this version shouldn't be shipped with the next > > release. Like the description says, it's "somewhat alpha". > > > > It works some times, but then stops working, it crashes, > > and so on. > > I've used the package purple-matrix on Debian 10 since at least 6 > months through Pidgin. It's not a perfect tool, have issues but in > my opinion it is usable. Sometimes purple-matrix is disconnected > or makes Pidgin to crash but it's quite rare. It's sufficient to > restart Pidgin to make it working again. > > I have two points why I think we should have it into next stable: > > * This is very difficult for a stable user to use purple-matrix. In my >case, I have had to rebuilt the package due to dependencies and it's >clearly something not easy for all. > * As a visual-impaired person, purple-matrix through Pidgin is the >most accessible Matrix client I've used. > > There are still reasons why we would like to keep it in unstable: > > * There are no commits in 2020 > * The project doesn't publish new release and "just" push commits Hi, I think that this project is essentially dead, there has never been a release and as you say there hasn't been changes in almost a year. I have stopped using it myself and the reason why I didn't ask for its removal from Debian is that it's a very small package with a very low manteinance burden (and because popcon shows that it has some users). But it seems that there are other alternatives nowadays. The official Matrix website no longer lists purple-matrix, but there are however other text-based clients such as weechat-matrix and gomuks. I cannot evaluate how accessible they are, though. Berto
Bug#855541: purple-matrix: Not ready for release yet
On Mon, 20 Feb 2017 00:12:35 +0100 Kurt Roeckx wrote: > Package: purple-matrix > Version: 0.0.0+git20170105-1 > Severity: serious > > Hi, > > I think this version shouldn't be shipped with the next > release. Like the description says, it's "somewhat alpha". > > It works some times, but then stops working, it crashes, > and so on. I've used the package purple-matrix on Debian 10 since at least 6 months through Pidgin. It's not a perfect tool, have issues but in my opinion it is usable. Sometimes purple-matrix is disconnected or makes Pidgin to crash but it's quite rare. It's sufficient to restart Pidgin to make it working again. I have two points why I think we should have it into next stable: * This is very difficult for a stable user to use purple-matrix. In my case, I have had to rebuilt the package due to dependencies and it's clearly something not easy for all. * As a visual-impaired person, purple-matrix through Pidgin is the most accessible Matrix client I've used. There are still reasons why we would like to keep it in unstable: * There are no commits in 2020 * The project doesn't publish new release and "just" push commits In my humble opinion, the drawbacks of keeping it to unstable are more important. @Kurt: I let you decide if you prefer to keep close or not but since the creation of this issue in 2017 many commits come to the project. Thanks in advance.
Bug#855541: purple-matrix: Not ready for release yet
Package: purple-matrix Version: 0.0.0+git20191228-1 Followup-For: Bug #855541 Hi, What server do you use to have this package working? Here on two servers I get: Failed to create e2e db table (step) So this package seems unusable now. Regards Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages purple-matrix depends on: ii libc6 2.29-10 ii libgcrypt20 1.8.5-3 ii libglib2.0-02.62.4-2 ii libhttp-parser2.9 2.9.2-2 ii libjson-glib-1.0-0 1.4.4-2 ii libolm3 3.1.3+dfsg-2 ii libpurple0 2.13.0-2.2+b1 ii libsqlite3-03.31.1-2 purple-matrix recommends no packages. purple-matrix suggests no packages. -- debconf-show failed
Bug#855541: purple-matrix: Not ready for release yet
On Thu, Feb 23, 2017 at 12:09:37AM +0100, Kurt Roeckx wrote: > > > > Maybe I'm missing something, what is the scenario that you are > > > > worried about? > > > > > > So some of my worries: > > > - It crashes for me a few times a week. > > > - There seem to be various issues that don't make it behave > > > properly. > > > - Maybe next year some of those issues have been fixed in > > > purple-matrix, it's recommended to use it for the desktop, > > > but then people install the version from Debian stable and > > > get a crappy version. > > > > But how is that scenario better if there's no version at all in > > Debian stable? > > That they try to find it in a different place, like backports. > > An other thing I'm concerned about is that I don't see any activity > upstream. Well, it's certainly not a very active project but there are pull requests once a while and they are reviewed and merged when they are ready. I don't know, I see your concerns but I also see that this package -even with missing features- covers a valid use case (I use it myself after all). I don't have a strong opinion about this, to be honest. Berto
Bug#855541: purple-matrix: Not ready for release yet
On Wed, Feb 22, 2017 at 11:21:57PM +0100, Alberto Garcia wrote: > On Wed, Feb 22, 2017 at 10:59:08PM +0100, Kurt Roeckx wrote: > > > > I don't know, I think I would understand you better if I had a > > > list of specific problems that make this software unsuitable for > > > release. > > > > I currently have a connection to my homeserver on 2 devices, and > > pidgin isn't receive any messages, but riot is. I have this problem > > every few days. And like I said, it's not clear where the problem > > is. It looks I can actually send things when in that state, and > > other people receive it, I just don't receive anything back. And > > people generally blame purple-matrix for that if I tell I'm using > > that. > > Ok, interesting. > > > > > Like I said, if you think that you can support this version for > > > > the next 3 years, I have no problem with it. But I wouldn't add > > > > it to a stable release yet in it's current state. > > > > > > I plan to keep using this plugin for the foreseeable time. > > > > But do you think you'll still use this version, or will you upgrade > > the version you're running when there is a new upstream version? > > Well, I'll upgrade it of course, and if there's any critical fix I'll > try to backport it. > > > > Maybe I'm missing something, what is the scenario that you are > > > worried about? > > > > So some of my worries: > > - It crashes for me a few times a week. > > - There seem to be various issues that don't make it behave > > properly. > > - Maybe next year some of those issues have been fixed in > > purple-matrix, it's recommended to use it for the desktop, > > but then people install the version from Debian stable and > > get a crappy version. > > But how is that scenario better if there's no version at all in Debian > stable? That they try to find it in a different place, like backports. An other thing I'm concerned about is that I don't see any activity upstream. Kurt
Bug#855541: purple-matrix: Not ready for release yet
On Wed, Feb 22, 2017 at 10:59:08PM +0100, Kurt Roeckx wrote: > > I don't know, I think I would understand you better if I had a > > list of specific problems that make this software unsuitable for > > release. > > I currently have a connection to my homeserver on 2 devices, and > pidgin isn't receive any messages, but riot is. I have this problem > every few days. And like I said, it's not clear where the problem > is. It looks I can actually send things when in that state, and > other people receive it, I just don't receive anything back. And > people generally blame purple-matrix for that if I tell I'm using > that. Ok, interesting. > > > Like I said, if you think that you can support this version for > > > the next 3 years, I have no problem with it. But I wouldn't add > > > it to a stable release yet in it's current state. > > > > I plan to keep using this plugin for the foreseeable time. > > But do you think you'll still use this version, or will you upgrade > the version you're running when there is a new upstream version? Well, I'll upgrade it of course, and if there's any critical fix I'll try to backport it. > > Maybe I'm missing something, what is the scenario that you are > > worried about? > > So some of my worries: > - It crashes for me a few times a week. > - There seem to be various issues that don't make it behave > properly. > - Maybe next year some of those issues have been fixed in > purple-matrix, it's recommended to use it for the desktop, > but then people install the version from Debian stable and > get a crappy version. But how is that scenario better if there's no version at all in Debian stable? > - I don't know if it's still going to be compatible next year. As far as I'm aware the client-server protocol is stable, well documented and doesn't just break from one version to the next. https://matrix.org/docs/spec/ Berto
Bug#855541: purple-matrix: Not ready for release yet
On Wed, Feb 22, 2017 at 01:56:31PM +0100, Alberto Garcia wrote: > On Mon, Feb 20, 2017 at 06:52:58PM +0100, Kurt Roeckx wrote: > > > It's just that each time I mention I'm using this, people tell me > > taht it's experimental, and probably a bug in purple-matrix. But > > it's at least not always clear to me where the bugs are, and there > > seem to be various problems with the homeserver (synapse) too. > > I don't know, I think I would understand you better if I had a list of > specific problems that make this software unsuitable for release. > > I've been using it daily for months as my primary Matrix client on > my desktop computer, and the only issues I found are occasional > disconnects (and I'm not even sure that it's not a server problem). I currently have a connection to my homeserver on 2 devices, and pidgin isn't receive any messages, but riot is. I have this problem every few days. And like I said, it's not clear where the problem is. It looks I can actually send things when in that state, and other people receive it, I just don't receive anything back. And people generally blame purple-matrix for that if I tell I'm using that. Sometimes the connection really breaks, and then it reconnects and works (or crashes). > > Like I said, if you think that you can support this version for the > > next 3 years, I have no problem with it. But I wouldn't add it to a > > stable release yet in it's current state. > > I plan to keep using this plugin for the foreseeable time. But do you think you'll still use this version, or will you upgrade the version you're running when there is a new upstream version? > If this goes to stretch then it will be a simple Matrix client with > few dependencies and limited functionality, but otherwise stable > enough for everyday use. > > Maybe I'm missing something, what is the scenario that you are worried > about? So some of my worries: - It crashes for me a few times a week. - There seem to be various issues that don't make it behave properly. - Maybe next year some of those issues have been fixed in purple-matrix, it's recommended to use it for the desktop, but then people install the version from Debian stable and get a crappy version. - I don't know if it's still going to be compatible next year. Kurt
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Feb 20, 2017 at 06:52:58PM +0100, Kurt Roeckx wrote: > It's just that each time I mention I'm using this, people tell me > taht it's experimental, and probably a bug in purple-matrix. But > it's at least not always clear to me where the bugs are, and there > seem to be various problems with the homeserver (synapse) too. I don't know, I think I would understand you better if I had a list of specific problems that make this software unsuitable for release. I've been using it daily for months as my primary Matrix client on my desktop computer, and the only issues I found are occasional disconnects (and I'm not even sure that it's not a server problem). > There are more problems with purple-matrix then that. For instance > from the description of the package itself: > The following are not yet supported: > * Creating new rooms (and one-to-one chats) > * Joining existing rooms by alias instead of room_id Those are clear missing features, and yes, you need a different client to join a room. For some people that's probably an essential feature, that's why it's clearly indicated in the package description. In my case I only follow a limited number of rooms, I don't need to join or create new ones, so this keeps me from having yet another chat client open all the time. > Like I said, if you think that you can support this version for the > next 3 years, I have no problem with it. But I wouldn't add it to a > stable release yet in it's current state. I plan to keep using this plugin for the foreseeable time. If this goes to stretch then it will be a simple Matrix client with few dependencies and limited functionality, but otherwise stable enough for everyday use. Maybe I'm missing something, what is the scenario that you are worried about? Berto
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Feb 20, 2017 at 11:21:50AM +0100, Alberto Garcia wrote: > On Mon, Feb 20, 2017 at 09:33:55AM +0100, Kurt Roeckx wrote: > > > > Could you be a bit more specific about the problems? In my > > > experience it disconnects (infrequently) and it lacks some > > > features, but other than that it's perfectly usable. > > > > See for instance: > > https://github.com/matrix-org/purple-matrix/issues/34 > > Well, that looks like a legitimate bug, but I wouldn't say that it > makes the package unusable. I cannot even reproduce it myself. > > > Anyway, if you disagree with the severity, feel free to close this > > bug. > > I can rename this bug and make it about that tab completion crash that > you reported upstream, but I don't see it as a generic "purple-matrix > is not ready yet". It's just that each time I mention I'm using this, people tell me taht it's experimental, and probably a bug in purple-matrix. But it's at least not always clear to me where the bugs are, and there seem to be various problems with the homeserver (synapse) too. There are more problems with purple-matrix then that. For instance from the description of the package itself: The following are not yet supported: * Creating new rooms (and one-to-one chats) * Joining existing rooms by alias instead of room_id This is clearly lacking functionality that I expect. I now need to use a different client to join a room. Like I said, if you think that you can support this version for the next 3 years, I have no problem with it. But I wouldn't add it to a stable release yet in it's current state. Kurt
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Feb 20, 2017 at 09:33:55AM +0100, Kurt Roeckx wrote: > > Could you be a bit more specific about the problems? In my > > experience it disconnects (infrequently) and it lacks some > > features, but other than that it's perfectly usable. > > See for instance: > https://github.com/matrix-org/purple-matrix/issues/34 Well, that looks like a legitimate bug, but I wouldn't say that it makes the package unusable. I cannot even reproduce it myself. > Anyway, if you disagree with the severity, feel free to close this > bug. I can rename this bug and make it about that tab completion crash that you reported upstream, but I don't see it as a generic "purple-matrix is not ready yet". Berto
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Feb 20, 2017 at 08:57:55AM +0100, Alberto Garcia wrote: > On Mon, Feb 20, 2017 at 12:12:35AM +0100, Kurt Roeckx wrote: > > > I think this version shouldn't be shipped with the next > > release. Like the description says, it's "somewhat alpha". > > > > It works some times, but then stops working, it crashes, > > and so on. > > I've been using it daily for several months with very few issues and > zero crashes. > > Could you be a bit more specific about the problems? In my experience > it disconnects (infrequently) and it lacks some features, but other > than that it's perfectly usable. See for instance: https://github.com/matrix-org/purple-matrix/issues/34 Anyway, if you disagree with the severity, feel free to close this bug. Kurt
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Feb 20, 2017 at 12:12:35AM +0100, Kurt Roeckx wrote: > I think this version shouldn't be shipped with the next > release. Like the description says, it's "somewhat alpha". > > It works some times, but then stops working, it crashes, > and so on. I've been using it daily for several months with very few issues and zero crashes. Could you be a bit more specific about the problems? In my experience it disconnects (infrequently) and it lacks some features, but other than that it's perfectly usable. Berto
Bug#855541: purple-matrix: Not ready for release yet
Package: purple-matrix Version: 0.0.0+git20170105-1 Severity: serious Hi, I think this version shouldn't be shipped with the next release. Like the description says, it's "somewhat alpha". It works some times, but then stops working, it crashes, and so on. Kurt
