Backports Team does not (and is not authorized) to handle bugfix-only
updates, unless the SRU path has no chance. I have not seen this the
case, so as of now, the backports request is rejected. Reopen if SRU
fails.
** Changed in: dapper-backports (upstream)
Status: Confirmed = Rejected
**
I do not see an approval from a backporters member here, so setting back
to needsinfo.
** Changed in: dapper-backports (upstream)
Status: In Progress = Needs Info
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
https://launchpad.net/bugs/73556
--
Closing Feisty task as per comment 5.
** Changed in: suphp (Ubuntu)
Status: Unconfirmed = Fix Released
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
https://launchpad.net/bugs/73556
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
** Changed in: dapper-backports (upstream)
Assignee: (unassigned) = Paul McClure
Status: Needs Info = In Progress
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
https://launchpad.net/bugs/73556
--
ubuntu-backports mailing list
Please attempt this as a SRU first, or have an MOTU reply with a reason
why a SRU is not appropriate.
** Changed in: dapper-backports (upstream)
Status: Unconfirmed = Needs Info
** Changed in: edgy-backports (upstream)
Status: Confirmed = Needs Info
--
suphp 0.6.2 backport
This is a request for a MOTU SRU for the suphp package for both Edgy and
Dapper as per the backporting team's request. This package has already
been updated in Feisty.
Due to the nature of the problem (see bug description), this could
possibly be a serious bug resulting in loss of user data or
b/i/r(id assume dont know how to test)
+1 for edgy using proper patch
** Changed in: edgy-backports (upstream)
Status: Unconfirmed = Confirmed
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
https://launchpad.net/bugs/73556
--
ubuntu-backports mailing
** Changed in: suphp (Debian)
Status: Unknown = Fix Released
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
https://launchpad.net/bugs/73556
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
Modify settings or unsubscribe at:
** Summary changed:
- libapache2-mod-suphp causes double free error in Apache error log when script
is inaccessible
+ suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
** Description changed:
+ Backport request: please backport suphp 0.6.2 to dapper and edgy from
+
Builds OK on edgy using prevu as per the instructions here:
http://ubuntuforums.org/showthread.php?t=268687
Minor tweaks needed in suphp-0.6.2/debian/control file to override dependencies
on apache-2.2. Patch for contol file attached. Apply patch as usual:
patch targetfile patchfile
**
Builds OK on dapper as well (build host is edgy, but target is dapper)
using prevu. The patch I attached with my previous comment also worked
for the dapper build (please refer to my previous comment).
--
suphp 0.6.2 backport request to dapper (0.6.1) and edgy (0.6.1) from feisty
11 matches
Mail list logo
