[Pkg-sql-ledger-discussion] Bug#682274: new upstream version available (1.3.20)
Robert James Clay
jame at rocasa.us
Sat Jul 21 00:16:24 UTC 2012
owner 682274 !
tags 682274 + confirmed
thanks
On Fri, 2012-07-20 at 17:40 -0400, Antoine Beaupré wrote:
> Package: ledgersmb
> Severity: wishlist
>
> Upstream has two new releases after what is in sid, we should upgrade,
Oh, I quite agree and I posted regarding my plans on getting there
earlier today to the package & ledgersmb-develop mailing lists:
On Fri, 2012-07-20 at 08:58 -0400, Robert James Clay wrote:
On Fri, 2012-06-29 at 10:28 -0400, Robert James Clay wrote:
>> I did get a start on packaging 1.3.19 (which has both upstream &
>> debian related fixes) but ran into an issue with packaging for an
>> upstream change that I haven't had time to resolve.
>
> That change is the one for the new (with v1.3.19) css file system
> configuration variable ("$fs_cssdir"), which I could not get to work.
> (I also had some issues with my test systems, though, that I've since
> resolved.) Now that I've merged the 1.3.18-2 Debian package changes,
> I'll get back to working on that issue again. Once that's been
> resolved, I'll go on to work on packaging v1.3.20 and it'll be at
> least that version (along with v1.3.19) that will in the next
> Debian upload.
On Fri, 2012-07-20 at 17:40 -0400, Antoine Beaupré wrote:
> and I think we should consider asking for a freeze exception, as
> apparently (according to the release notes), 1.3.20 is more stable.
I'd already been thinking about using such reasoning for 1.3.19;
I'll check into that for 1.3.20 as well. There's also a fix & update
for one of the LedgerSMB locale/po files in v1.3.20 (Debian #678281),
which also may help.
RJ Clay
jame at rocasa.us
More information about the Pkg-sql-ledger-discussion
mailing list