Your message dated Sun, 17 Jun 2018 20:23:10 +0100 with message-id <1529263390.2082.41.camel@adam-barratt.org.uk> and subject line Re: Bug#821239: jessie-pu: package ledgersmb/1.3.40-1~deb8u1 has caused the Debian Bug report #821239, regarding jessie-pu: package ledgersmb/1.3.40-1+deb8u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 821239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821239 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: jessie-pu: package ledgersmb/1.3.47-1~deb8u1
- From: Robert James Clay <jame@rocasa.us>
- Date: Sat, 16 Apr 2016 18:52:45 -0400
- Message-id: <1694103.tAgUpsjuys@rjcdev>
- Reply-to: jame@rocasa.us
Package: release.debian.org Severity: normal Tags: jessie User: release.debian.org@packages.debian.org Usertags: pu Dear release managers, Please accept ledgersmb_1.3.47-1~deb8u1 for the next Jessie point release. It resolves the issues with the current version of ledgersmb in 'jessie' (1.3.40-1) of the package failing to complete an install without errors. Please see the attached debdiff.txt.gz for the debdiff between the existing version ledgersmb/1.3.40-1 in jessie and the proposed update package version 1.3.47-1~deb8u1. Regards, Robert Jame Clay, DM jame@rocasa.usAttachment: debdiff.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
- To: 821239-done@bugs.debian.org, jame@rocasa.us, Julien Cristau <jcristau@debian.org>
- Cc: Jonathan Wiltshire <jmw@debian.org>
- Subject: Re: Bug#821239: jessie-pu: package ledgersmb/1.3.40-1~deb8u1
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sun, 17 Jun 2018 20:23:10 +0100
- Message-id: <1529263390.2082.41.camel@adam-barratt.org.uk>
- In-reply-to: <[🔎] 1528920457.2806.66.camel@adam-barratt.org.uk>
- References: <1694103.tAgUpsjuys@rjcdev> <2342184.GVIxC6GxQN@rjcdev> <20160515135806.GE2718@betterave.cristau.org> <1877728.qc4R6lbfh0@rjcdev> <1694103.tAgUpsjuys@rjcdev> <[🔎] 1528920457.2806.66.camel@adam-barratt.org.uk>
Control: tags -1 + wontfix On Wed, 2018-06-13 at 21:07 +0100, Adam D. Barratt wrote: > On Sun, 2016-05-15 at 17:37 -0400, Robert James Clay wrote: > > Control: retitle -1 jessie-pu: package ledgersmb/1.3.40-1~deb8u1 > > > > On Sunday, May 15, 2016 09:58:06 AM Julien Cristau wrote: > > > The usual sequence is *not* unstable -> testing -> jessie- > > > pu. The > > > usual > > > sequence is to fix the bugs in unstable/testing, and then > > > separately > > > cherry-pick the fixes that warrant the stable update to the > > > stable > > > version of the package, > > > > Thank you for clarifying that. (My mistake; I was going too much > > by the > > last time I did something like this, which was an upstream issue > > and > > not a > > packaging issue...) > > > > > > > so in this case that would mean preparing a ledgersmb 1.3.40- > > > 1+deb8u1 with > > > the fixes you want to see in stable, and not the unrelated > > > upstream > > > bits. > > > > I'll take care of that and then update the bug again. > > That was two years ago, and there's been no further activity. > > The window for getting fixes into jessie before it becomes LTS closes > during this weekend. Is there still any interest here? Unfortunately there was no reply to the above query, and the window for getting fixes in to the final point release for jessie (before it moves to LTS support) has now closed. Regards, Adam
--- End Message ---