[SRU] Include upstream fix for bug 15496

Hello Julian, or anyone else affected,

Accepted into quantal-proposed. The package will build now and be available in a few hours in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package python-django - 1.3.1-4ubuntu1.5

---------------
python-django (1.3.1-4ubuntu1.5) precise-proposed; urgency=low

  [ Julian Edwards ]
  * debian/patches:
    - genericipaddressfield.diff: Backport GenericIPAddressField
      from 1.4 (LP: #1081391)
    - prefetch_related.diff: Backport prefetch_related from 1.4 (LP: #1081388)
    - bug15496-base64-multipart-fix.diff: Include fix for upstream bug #15496
      which makes 'Content-Transfer-Encoding: base64: work for multipart
      messages. (LP: #1081392)
 -- Andres Rodriguez <email address hidden> Tue, 20 Nov 2012 16:00:41 -0500

I've just removed this update from precise-updates. Unfortunately it wasn't until after I copied it over that I noticed that this is not an appropriate change for an SRU and it's not been reviewed by the SRU team.

Since this was not reviewed by the SRU team, I've removed the SRU. Additionally, since feature additions are not permitted in SRUs by the normal policy, a change like this should be discussed in advance, probably with the tech board, before it is resubmitted.

Scott, if you read the bug title and description carefully, you'll see that this is not a feature, it is a bug fix.

OK. Agreed.

Thanks - when can we expect it to hit -updates>

There were (IIRC) three bugs included in the upload. This was only one. The
others were clear feature backports that aren't suitable for an SRU. First
then someone needs to do an upload that fixes just the bug to proposed.

On 11/12/12 13:32, Scott Kitterman wrote:
> There were (IIRC) three bugs included in the upload. This was only one. The
> others were clear feature backports that aren't suitable for an SRU. First
> then someone needs to do an upload that fixes just the bug to proposed.
>

The other bugs are critical SRU uploads too as they allow a new maas
upload which fixes a whole raft of problems and security issues. I
think the security team needs to get involved.

I think it would be better not to write security fixes that depend on features not present in the release.

It's possibly worth mentioning that if it turns out these are approved, I'll go ahead and approve all the backports needed to update owncloud due to it having security issues. If that's enough to waive SRU policy, then stand by for the flood.

On 11/12/12 16:03, Scott Kitterman wrote:
> I think it would be better not to write security fixes that depend on
> features not present in the release.
>

I'd love to have that choice.

Hello Julian, or anyone else affected,

Accepted into quantal-proposed. The package will build now and be available in a few hours in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

As far as I can tell, the new package in precise-proposed hasn't been tested yet. Although a previous upload was tested, we need to test the package that is actually going to be copied into -updates. Please do so, and we can release it to -updates.

This bug was fixed in the package python-django - 1.3.1-4ubuntu1.7

---------------
python-django (1.3.1-4ubuntu1.7) precise-proposed; urgency=low

  [ Julian Edwards ]
  * debian/patches:
    - prefetch_related.diff: Backport prefetch_related from 1.4 (LP: #1081388)
    - bug15496-base64-multipart-fix.diff: Include fix for upstream bug #15496
      which makes 'Content-Transfer-Encoding: base64: work for multipart
      messages. (LP: #1081392)
 -- Andres Rodriguez <email address hidden> Thu, 07 Mar 2013 17:27:06 -0500