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


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

Bug#1081217: Should fava be removed from unstable?

Started byHelmut Grohne <helmut@subdivi.de>
First post2024-09-09 16:10 +0200
Last post2024-11-12 01:50 +0100
Articles 4 — 3 participants

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


Contents

  Bug#1081217: Should fava be removed from unstable? Helmut Grohne <helmut@subdivi.de> - 2024-09-09 16:10 +0200
    Bug#1081217: Keep this package in unstable "Dr. Tobias Quathamer" <toddy@debian.org> - 2024-10-01 17:00 +0200
      Bug#1081217: Keep this package in unstable Helmut Grohne <helmut@subdivi.de> - 2024-10-02 06:50 +0200
    Bug#1081217: making fava work on bookworm Chris Frey <cdfrey@foursquare.net> - 2024-11-12 01:50 +0100

#1212054 — Bug#1081217: Should fava be removed from unstable?

FromHelmut Grohne <helmut@subdivi.de>
Date2024-09-09 16:10 +0200
SubjectBug#1081217: Should fava be removed from unstable?
Message-ID<JkNfz-b6fa-23@gated-at.bofh.it>
Source: fava
Severity: important
User: helmutg@debian.org
Usertags: sidremove

Dear maintainer,

I suggest removing fava from Debian for the following reasons:
 * It accumulated one RC-bug:
   + #1031724: fava: frontend is not built from source; missing source
     Last modified: 1 year, 6 months

 * It is not part of bookworm or trixie and is not a key package.

This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.

In case the package should be kept in unstable, please evaluate each of the
RC-bugs listed above.
 * If the bug is meant to permanently prevent the package from entering testing
   or a stable release, but this package should stay part of unstable, please
   add a usertag:

       user helmutg@debian.org
       usertags NNN + sidremove-ignore

 * If the bug no longer applies, please close it. If it is closed, check
   whether the fixed version is correct and adjust if necessary.

 * Is the bug really release-critical? If not, please downgrade.

 * If the bug still applies, please send a status update at least once a year.

Once all of the mentioned RC bugs have been acted upon in one way or another,
please close this bug.

In case the package should be removed from unstable, you may reassign this
bug report:

    Control: severity -1 normal
    Control: retitle -1 RM: fava -- RoM; rc-buggy
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:fava

Alternatively, you may wait a month and have it reassigned.

In case you disagree with the above, please add a wontfix tag to this bug.

    Control: tags -1 + wontfix

Doing so will also prevent automatic reassignment.

Kind regards

A tool for automatically removing packages from unstable

This bug report has been automatically filed with little human intervention.
If the filing is unclear or in error, don't hesitate to contact
Helmut Grohne <helmut@subdivi.de> for assistance.

[toc] | [next] | [standalone]


#1214807 — Bug#1081217: Keep this package in unstable

From"Dr. Tobias Quathamer" <toddy@debian.org>
Date2024-10-01 17:00 +0200
SubjectBug#1081217: Keep this package in unstable
Message-ID<JsMw1-ge4Y-1@gated-at.bofh.it>
In reply to#1212054
Control: tags -1 + wontfix

Hi,

thanks for asking about fava. There are currently two RC bugs, but I'd 
like to keep this package in unstable very much. I use it, so I'll try 
to fix the RC bugs.

In the meantime, please don't remove fava from unstable.

Regards,
Tobias

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


#1214854 — Bug#1081217: Keep this package in unstable

FromHelmut Grohne <helmut@subdivi.de>
Date2024-10-02 06:50 +0200
SubjectBug#1081217: Keep this package in unstable
Message-ID<JsZtf-glYn-1@gated-at.bofh.it>
In reply to#1214807
Hi Tobias,

On Tue, Oct 01, 2024 at 04:46:52PM +0200, Dr. Tobias Quathamer wrote:
> thanks for asking about fava. There are currently two RC bugs, but I'd like
> to keep this package in unstable very much. I use it, so I'll try to fix the
> RC bugs.

Thank you for the reply and expressing the intention of keeping fava
alive. Rather than marking this bug wontfix, could you send a brief
status update about your plans on fixing #1031724 indicating partial
progress if any to that bug and then close this bug entirely?

> In the meantime, please don't remove fava from unstable.

I have intentions to remove packages that are being worked on.

Helmut

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


#1219966 — Bug#1081217: making fava work on bookworm

FromChris Frey <cdfrey@foursquare.net>
Date2024-11-12 01:50 +0100
SubjectBug#1081217: making fava work on bookworm
Message-ID<JHNgt-8iJv-1@gated-at.bofh.it>
In reply to#1212054
Coming from the buster and bullseye worlds here, I was sad and surprised
to find that python3-fava is not available in bookworm anymore.

I haven't started working on it yet, but I have every intention of getting
it working somehow since it is a critical part of my beancount flow.
So how can I help?

Should I be starting with 'apt-get source fava' on unstable, or
is there something newer I could test/work on?

Thanks,
- Chris

[toc] | [prev] | [standalone]


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


csiph-web