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

Groups > linux.debian.bugs.dist > #1214827 > unrolled thread

Bug#932927: questions

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#932927: questions Hefee <hefee@debian.org> - 2024-10-01 22:20 +0200
    Bug#932927: questions Aurelien Jarno <aurel32@debian.org> - 2024-10-01 22:30 +0200
      Bug#932927: [Pkg-privacy-maintainers] Bug#932927: questions Hefee <hefee@debian.org> - 2024-10-02 13:40 +0200

#1214827 — Bug#932927: questions

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

Control: tags -1 +moreinfo

Hey Aurelien,

Can you please explain, why you see value in keeping this bug open for more 
than two years? I see no action item; aka nothing to do at the moment, just 
wait or do I miss something?

So far I understood, that this bug may come again in future - okay - but every 
bug could come in future again, that in it self is not a reason to keep the 
bug open. Why not close this bug now and open it, if you see it again.

And the other reason that the riscv porter team needs this bug, you declined 
and actually removed it from there table.

Regards,

hefee

[toc] | [next] | [standalone]

#1214830

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

Hi,

On 2024-10-01 22:10, Hefee wrote:
> Control: tags -1 +moreinfo
> 
> Hey Aurelien,
> 
> Can you please explain, why you see value in keeping this bug open for more 
> than two years? I see no action item; aka nothing to do at the moment, just 
> wait or do I miss something?

There is a patch in the BTS to fix the issue. I am waiting for this bug
to be fixed either by applying the patch, or by an alternative solution.

> So far I understood, that this bug may come again in future - okay - but every 
> bug could come in future again, that in it self is not a reason to keep the 
> bug open. Why not close this bug now and open it, if you see it again.

Uninitialized variables can come back even without changing the source
code, it depends for instance on how the compiler generate code and
place variables in memory. That's actually very likely how the testsuite
started to pass on riscv64.

In short the bug is still there, just it is not visible anymore... for
now...

> And the other reason that the riscv porter team needs this bug, you declined 
> and actually removed it from there table.

Yes, given the testsuite now passes on riscv64, it does not block the
port anymore. But the bug is still there.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

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

#1214887 — Bug#932927: [Pkg-privacy-maintainers] Bug#932927: questions

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

Control: tags -1 -moreinfo

Hey,

Thanks for your explanation. I missed the part, that the patch was added 
already. That makes sense to keep the bug open.

regards,

hefee

--
On Dienstag, 1. Oktober 2024 22:20:47 CEST Aurelien Jarno wrote:
> Hi,
> 
> On 2024-10-01 22:10, Hefee wrote:
> > Control: tags -1 +moreinfo
> > 
> > Hey Aurelien,
> > 
> > Can you please explain, why you see value in keeping this bug open for
> > more
> > than two years? I see no action item; aka nothing to do at the moment,
> > just
> > wait or do I miss something?
> 
> There is a patch in the BTS to fix the issue. I am waiting for this bug
> to be fixed either by applying the patch, or by an alternative solution.
> 
> > So far I understood, that this bug may come again in future - okay - but
> > every bug could come in future again, that in it self is not a reason to
> > keep the bug open. Why not close this bug now and open it, if you see it
> > again.
> Uninitialized variables can come back even without changing the source
> code, it depends for instance on how the compiler generate code and
> place variables in memory. That's actually very likely how the testsuite
> started to pass on riscv64.
> 
> In short the bug is still there, just it is not visible anymore... for
> now...
> 
> > And the other reason that the riscv porter team needs this bug, you
> > declined and actually removed it from there table.
> 
> Yes, given the testsuite now passes on riscv64, it does not block the
> port anymore. But the bug is still there.
> 
> Regards
> Aurelien

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web