Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #239891 > unrolled thread

Looking for guidance on reporting a bug on the roundcube package

Back to article view | Back to linux.debian.user

Contents

  Looking for guidance on reporting a bug on the roundcube package Steve Dondley <s@dondley.com> - 2021-09-12 04:50 +0200
    Re: Looking for guidance on reporting a bug on the roundcube package Brian <ad44@cityscape.co.uk> - 2021-09-12 13:10 +0200
      Re: Looking for guidance on reporting a bug on the roundcube package Steve Dondley <s@dondley.com> - 2021-09-12 14:10 +0200
    Re: Looking for guidance on reporting a bug on the roundcube package Andrei POPESCU <andreimpopescu@gmail.com> - 2021-09-12 13:10 +0200
      Re: Looking for guidance on reporting a bug on the roundcube package Steve Dondley <s@dondley.com> - 2021-09-12 14:00 +0200
        Re: Looking for guidance on reporting a bug on the roundcube package Andrei POPESCU <andreimpopescu@gmail.com> - 2021-09-12 16:10 +0200

#239891 — Looking for guidance on reporting a bug on the roundcube package

First, thanks to everyone here and the Debian community, an amazing 
project.

Running bullseye with package roundcube. I believe I have found a bug 
that I'd like to report.

I am using reportbug to report it. When doing so, I got this message:

Your version (1.4.11+dfsg.1-4) of roundcube appears to be out of date.
The following newer release(s) are available in the Debian archive:
   experimental: 1.5~rc+dfsg.1-1
Please try to verify if the bug you are about to report is already 
addressed by these releases.  Do you still want to file a report 
[y|N|q|?]? n
Newer released version; stopping.

I don't want to install an experimental package on a production machine 
to verify the bug and I really don't have the time to set up a debian 
installation and install roundcube to test this.

So it's unclear to me if I should bother reporting this bug or if they 
are only interested in hearing about bugs from the upcoming release 
candidate. I have reported the bug to roundcube's github page already. 
I'm not even entirely sure if this is a bug with the package or 
roundcube itself. I'm going to assume it's a debian package issue 
because my issue on github was closed without comment: 
https://github.com/roundcube/roundcubemail/issues/8198

I've always been confused by whether and how debian patches relatively 
bugs like this. I think only security patches were issued and minor 
usability fixes don't get release until the next version of debian. But 
I may be totally wrong on this.

So would I just be wasting my time and everyone else's by reporting 
this?

[toc] | [next] | [standalone]

#239916

On Sat 11 Sep 2021 at 22:40:32 -0400, Steve Dondley wrote:

> First, thanks to everyone here and the Debian community, an amazing project.
> 
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
> 
> I am using reportbug to report it. When doing so, I got this message:
> 
> Your version (1.4.11+dfsg.1-4) of roundcube appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 1.5~rc+dfsg.1-1
> Please try to verify if the bug you are about to report is already addressed
> by these releases.  Do you still want to file a report [y|N|q|?]? n
> Newer released version; stopping.

Technically, the first part of the message is correct. However, your
version of roundcube and unstable's version are the same. Submit the
report.

Even if unstable's version was higher, I would still send the report.
The Project needs users to participate.
 
> I don't want to install an experimental package on a production machine to
> verify the bug and I really don't have the time to set up a debian
> installation and install roundcube to test this.

Not unreasonable. I expect the scary notice on this archive's webpage
is also demotivating.

> So it's unclear to me if I should bother reporting this bug or if they are
> only interested in hearing about bugs from the upcoming release candidate. I
> have reported the bug to roundcube's github page already. I'm not even
> entirely sure if this is a bug with the package or roundcube itself. I'm
> going to assume it's a debian package issue because my issue on github was
> closed without comment:
> https://github.com/roundcube/roundcubemail/issues/8198

Debian is interested in *all* issues affecting a user. The triager will
help sort it out.

> I've always been confused by whether and how debian patches relatively bugs
> like this. I think only security patches were issued and minor usability
> fixes don't get release until the next version of debian. But I may be
> totally wrong on this.

If it is a Debian bug, the fix woudld be applied in unstable and work
its way through the system. The same happens with an upstream fix.

> So would I just be wasting my time and everyone else's by reporting this?

No! Please submit the report.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#239923

> Debian is interested in *all* issues affecting a user. The triager will
> help sort it out.
> 
> If it is a Debian bug, the fix woudld be applied in unstable and work
> its way through the system. The same happens with an upstream fix.
> 
>> So would I just be wasting my time and everyone else's by reporting 
>> this?
> 
> No! Please submit the report.

OK, thanks for the clarification and assurance on this. I didn't want to 
irritate anybody with reports they might consider useless. I'll submit 
the report.

[toc] | [prev] | [next] | [standalone]

#239917

[Multipart message — attachments visible in raw view] — view raw

On Sb, 11 sep 21, 22:40:32, Steve Dondley wrote:
> First, thanks to everyone here and the Debian community, an amazing project.
> 
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
> 
> I am using reportbug to report it. When doing so, I got this message:
> 
> Your version (1.4.11+dfsg.1-4) of roundcube appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 1.5~rc+dfsg.1-1
> Please try to verify if the bug you are about to report is already addressed
> by these releases.  Do you still want to file a report [y|N|q|?]? n
> Newer released version; stopping.
> 
> I don't want to install an experimental package on a production machine to
> verify the bug and I really don't have the time to set up a debian
> installation and install roundcube to test this.

Using free(dom) software sometimes require you invest resources in some 
other way, depending on the particular issue and how important it is to 
you ;)
 
> So it's unclear to me if I should bother reporting this bug or if they are
> only interested in hearing about bugs from the upcoming release 
> candidate.

In general a report is better than no report. The Maintainer might be 
able to easily do the test instead.

Alternatively, it seems you know your way around the source code, so 
maybe you can confirm it is still unchanged.

> I have reported the bug to roundcube's github page already. I'm not 
> even entirely sure if this is a bug with the package or roundcube 
> itself. I'm going to assume it's a debian package issue because my 
> issue on github was closed without comment:
> https://github.com/roundcube/roundcubemail/issues/8198

If you're unsure it is best to report the issue to Debian first.

If the problem is upstream the Debian Maintainer might ask you to open 
an issue upstream (or do that themselves).

Depending on the relation with Debian some upstreams will just close 
bugs instantly at just a mention of Debian. Sometimes this is even 
justified (e.g. in case Debian patches the software heavily and/or is 
using ancient versions that are not supported anymore).

Closing bugs without *any* kind of explanation is still annoying (to say 
the least) :(

> I've always been confused by whether and how debian patches relatively bugs
> like this. I think only security patches were issued and minor usability
> fixes don't get release until the next version of debian. But I may be
> totally wrong on this.

As a general rule stable (and oldstable for one year after the stable 
release) only receive fixes for security and major issues. The next 
stable release should get new upstream versions instead (that may or may 
not fix your issue).

> So would I just be wasting my time and everyone else's by reporting this?

Just documenting an issues is still helpful, as it might help other 
Roundcube users (on Debian) save time, e.g. by not redoing your 
investigation.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#239921

> Using free(dom) software sometimes require you invest resources in some
> other way, depending on the particular issue and how important it is to
> you ;)

Agreed. But the package manager will have a much easier time than me at 
nailing down the problem and do it in much less time. I've already spent 
time investigating and isolating the problem so I consider that to be my 
contribution to the issue.


> Just documenting an issues is still helpful, as it might help other
> Roundcube users (on Debian) save time, e.g. by not redoing your
> investigation.

Yes, good point. I'll submit the report. Thanks.

[toc] | [prev] | [next] | [standalone]

#239925

[Multipart message — attachments visible in raw view] — view raw

On Du, 12 sep 21, 07:54:32, Steve Dondley wrote:
> 
> > Using free(dom) software sometimes require you invest resources in some
> > other way, depending on the particular issue and how important it is to
> > you ;)
> 
> Agreed. But the package manager will have a much easier time than me at
> nailing down the problem and do it in much less time. I've already spent
> time investigating and isolating the problem so I consider that to be my
> contribution to the issue.

Every contribution is (or at least should be) appreciated.

Even if it takes you longer, the Maintainer could be doing other stuff 
in that time, that might benefit you as well, e.g. provide a backport of 
a newer version (which might also incidentally fix issues like yours, 
that do not qualify for a stable update).

Time is limited for everybody ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web