[Bug 1782956] Re: Sync sql-ledger 3.2.6-1 (main) from Debian sid (main)

Jeremy Bicha (jbicha) wrote: > sql-ledger was removed from Ubuntu and added to the sync blacklist. > See LP: #1598308 for more details. I reviewed that as well, as I was unaware of it because I was not the package maintainer in Debian back then. Jeremy Bicha (jbicha) wrote: > I believe the

[Bug 1782956] [NEW] Sync sql-ledger 3.2.6-1 (main) from Debian sid (main)

Public bug reported: Please sync sql-ledger 3.2.6-1 (main) from Debian sid (main) Package backports to Cosmic and builds cleanly. Reference: sql-ledger - 3.2.6-1~ubuntu18.10.1 at https://launchpad.net/~sql-ledger/+archive/ubuntu/ppa/+packages The updated package closed three bugs in Debian

[Bug 1092835] Re: missing translation entries not appearing in the "all" file

** Changed in: sql-ledger (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092835 Title: missing translation entries not appearing in the "all" file To

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

Bbackports for sql-ledger in Ubuntu are now available for bionic, artful, xenial, & trusty at: https://launchpad.net/~sql-ledger/+archive/ubuntu/ppa ** Changed in: sql-ledger (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

Apologies; note that my gmail email address is rjc...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537461 Title: Version 3.2 of SQL Ledger now available To manage notifications about

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

Apologies; note that my gmail email address is rjc...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281329 Title: Sync up 14.04 release with latest avaiable version from project To

[Bug 1092835] Re: missing translation entries not appearing in the "all" file

Apologies; note that my gmail email address is rjc...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092835 Title: missing translation entries not appearing in the "all" file To manage

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

** Changed in: sql-ledger (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537461 Title: Version 3.2 of SQL Ledger now available To manage

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

will be looking into backporting that version as necessary. Robert James Clay rc...@gmail.com j...@rocasa.us ** Changed in: sql-ledger (Ubuntu) Assignee: (unassigned) => RJ Clay (rjclay) ** Changed in: sql-ledger (Ubuntu) Status: New => Confirmed -- You received this bug notifi

[Bug 1092835] Re: missing translation entries not appearing in the "all" file

if this issue of the "missing translation entries not appearing in the 'all' file" is still present. Robert James Clay rc...@gmail.com j...@rocasa.us ** Changed in: sql-ledger (Ubuntu) Assignee: (unassigned) => RJ Clay (rjclay) -- You received this bug notification because you

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

Note that version 3.2.6-1 of the sql-ledger package was uploaded to Debian unstable on 6 July 2018, at which point I also became the maintainer. Barring any issues, I anticipate the new version of the package to transition to Ubuntu on or after Wednesday, 11 July 2018. Robert James Clay

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

** Changed in: sql-ledger (Ubuntu) Assignee: (unassigned) => RJ Clay (rjclay) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537461 Title: Version 3.2 of SQL Ledger now available To man

[Bug 1184226] Re: package multimail (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/bin/mm', que também está no pacote mountmanager 0.2.6-0ubuntu5

The package MountManager is no longer in any current Ubuntu distribution and so is no longer present to interfere with the existing (since 1999) package multimail or the path /usr/bin/mm. This bug should therefore be closed as not valid. ** Changed in: multimail (Ubuntu) Status: New =>

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

Indeed and I agree but the bug when running on Perl v5.26 will need to be resolved first, by either a patch in the package or (preferably) a new upstream version that can handle running on that version of Perl. See also Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869994 Also;

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

On Mon, 02 Oct 2017 11:44:41 -0400 "Maik Wagner" wrote: > I am very glad that somebody is looking at maintaining this package. > Are you looking to primarily support Ubuntu or Debian. I'm primaraly a packager for Debian but keep in mind that is traditionally via Debian

[Bug 795625] Re: package citadel-server 7.84-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 141

This bug should be closed as invalid because it is over 6 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received

[Bug 863596] Re: package citadel-server 7.84-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

This bug is somewhat of a duplicate of Ubuntu bug #795625 and in case should be closed as invalid because it is almost 6 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in:

[Bug 496102] Re: E:dpkg was interrputed

This bug should now be closed as invalid because it is over 5 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received

[Bug 682532] Re: package citadel-server 7.51-1 failed to install/upgrade: subprocess installed post-installation script killed by signal (Interrupt)

This bug should be closed as invalid because it is almost 6 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received

[Bug 704464] Re: install returns export: 106: 007: bad variable name

This bug should be closed as invalid because it is over 6 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received

[Bug 387155] Re: package citadel-server 7.38-1 failed to install/upgrade: subprocess post-installation script returned error exit status 2

This bug should be closed as invalid because it is almost 7 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: Confirmed => Invalid -- You

[Bug 355391] Re: citadel-server down

This bug should be closed as invalid because it is almost 8 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) ** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received

[Bug 302249] Re: package citadel-common 7.37-5 failed to install/upgrade: sous-processus post-installation script tu? par le signal (Interrupt)

This bug should be closed as invalid because it is almost 8 years old and the version of Citadel it was reported against has not been in Ubuntu for years. (The oldest version is currently 7.86, which is in Precise.) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 302249] Re: package citadel-common 7.37-5 failed to install/upgrade: sous-processus post-installation script tu? par le signal (Interrupt)

** Changed in: citadel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/302249 Title: package citadel-common 7.37-5 failed to install/upgrade: sous- processus

[Bug 1281329] Re: Sync up 14.04 release with latest avaiable version from project

Note that while it didn't make tt into trusty (14.04 LTS), version v3.0.8 of SQL-Ledger did make it into xenial (16.04 LTS). Also, there have already been open bugs in both Debian[1] and Ubuntu[2] requesting that the most current version (currently v3.2.5) be packaged. [1]

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

This package was orphaned in Debian and I am looking at adopting it. As part of that, I have attempted to update the packaging to be for upstream v3.2.5, which resulted in the following new issues: 1) The existing latex-cmdline-option patch did not apply as is to the new upstream. That will

[Bug 1537461] Re: Version 3.2 of SQL Ledger now available

** Changed in: sql-ledger (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537461 Title: Version 3.2 of SQL Ledger now available To manage notifications

[Bug 1637247] Re: Doesn't work properly after installation (and fix)

This was resolved with the upload to Debian of 1.3.47-1 a year ago and subsequent migration to Ubuntu. That 1.3.x series version has since been replaced by the 1.4.x series; for instance, 1.4.32+ds-1 which is in Ubuntu 16.10 (Yakkety). The most recent version of that series in Ubuntu is

[Bug 1637240] Re: installation should enable mod_rewrite

This was resolved with the upload to Debian of 1.3.47-1 a year ago and subsequent migration to Ubuntu. That 1.3.x series version has since been replaced by the 1.4.x series; for instance, 1.4.32+ds-1 which is in Ubuntu 16.10 (Yakkety). The most recent version of that series in Ubuntu is

[Bug 1637247] Re: Doesn't work properly after installation (and fix)

** Changed in: ledgersmb (Ubuntu) Assignee: (unassigned) => RJ Clay (rjclay) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637247 Title: Doesn't work properly after installation (and

[Bug 1637240] Re: installation should enable mod_rewrite

** Changed in: ledgersmb (Ubuntu) Assignee: (unassigned) => RJ Clay (rjclay) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637240 Title: installation should enable mod_rewrite To man

[Bug 1513691] Re: package ledgersmb 1.3.46-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

** Changed in: ledgersmb (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513691 Title: package ledgersmb 1.3.46-1 failed to install/upgrade:

[Bug 1513691] Re: package ledgersmb 1.3.46-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

** Changed in: ledgersmb (Ubuntu) Assignee: (unassigned) => Ubuntu LedgerSMB (ledgersmb) ** Changed in: ledgersmb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1513691] Re: package ledgersmb 1.3.46-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

As noted in DpkgTerminalLog.txt, this looks to be associated with the following error: apache2_reload: Your configuration is broken. Not reloading Apache 2 apache2_reload: AH00526: Syntax error on line 9 of /etc/apache2/conf-enabled/ledgersmb.conf: apache2_reload: Invalid command

[Bug 1473318] Re: package ledgersmb 1.3.40-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

** Changed in: ledgersmb (Ubuntu) Assignee: (unassigned) = RJ Clay (rjclay) ** Changed in: ledgersmb (Ubuntu) Assignee: RJ Clay (rjclay) = (unassigned) ** Changed in: ledgersmb (Ubuntu) Assignee: (unassigned) = Ubuntu LedgerSMB (ledgersmb) -- You received this bug notification

[Bug 1078817] Re: After installation it doesn't work

Version with fix, ledgersmb 1.3.46-1, is in Ubuntu ('Wily') ** Changed in: ledgersmb (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078817 Title:

[Bug 1473318] Re: package ledgersmb 1.3.40-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

The version with a fix for this issue, ledgersmb 1.3.46-1, is in Ubuntu ('Wily'). ** Changed in: ledgersmb (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1473318] Re: package ledgersmb 1.3.40-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

As per Google Translate, that bug title and ErrorMessage comes up as: Subprocess installed post-installation script returned error exit status 1. Is that all there is to the reported issue? If that is the case, then to my knowledge, this issue was resolved with ledgersmb 1.3.46-1, which is