[ic] [interchange-cvs] [SCM] Interchange branch, master, updated. REL_5_7_3-4-g794cd5e

[Stefan Hornburg (Racke)]

Stefan Hornburg wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "Interchange".
> 
> The branch, master has been updated
>        via  794cd5ec1a9f52f3c16d8d806ebe9a26c9c12a50 (commit)
>        via  892af5b79afa4862358cd8510225bd73ad8064ab (commit)
>       from  b75c35f3af2bbe7376b6ded5fb3998263654a160 (commit)
> 
> Those revisions listed above that are new to this repository have
> not appeared on any other notification email; so we list those
> revisions in full, below.
> 
> - Log -----------------------------------------------------------------
> commit 794cd5ec1a9f52f3c16d8d806ebe9a26c9c12a50
> Author: Stefan Hornburg (Racke) <racke at linuxia.de>
> Date:   Fri Nov 6 09:26:49 2009 +0100
> 
>     get rid of CVS tag
> 
> commit 892af5b79afa4862358cd8510225bd73ad8064ab
> Author: Stefan Hornburg (Racke) <racke at linuxia.de>
> Date:   Fri Nov 6 09:18:37 2009 +0100
> 
>     force raw encoding for file uploads (#268)
> 
> -----------------------------------------------------------------------
> 
> Summary of changes and diff:
>  lib/Vend/Data.pm |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/Vend/Data.pm b/lib/Vend/Data.pm
> index 9ba239b..1723d34 100644
> --- a/lib/Vend/Data.pm
> +++ b/lib/Vend/Data.pm
> @@ -1,7 +1,5 @@
>  # Vend::Data - Interchange databases
>  #
> -# $Id: Data.pm,v 2.68 2008-08-12 22:02:57 jon Exp $
> -# 
>  # Copyright (C) 2002-2008 Interchange Development Group
>  # Copyright (C) 1996-2002 Red Hat, Inc.
>  #
> @@ -2069,6 +2067,7 @@ sub update_data {
>  						$nm,
>  						{
>  							outfile => $outfile,
> +							encoding => 'raw',
>  							umask => $::Scratch->{mv_create_umask} || '022',
>  							auto_create_dir => $::Scratch->{mv_auto_create_dir},
>  							yes => '1',
> 
> 
> hooks/post-receive

This patch fixes the image upload. However, it is more of a bandaid right 
now as we hardcode the file encoding.

I suppose that we need to determine the content type of the file in order
to get a real solution for this problem.

Regards
         Racke


-- 
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team