bug when trying to update a media object with a new file

I can create and publish a media file without any problem
(this is a new
10.2 installation we're working on).  Then, when I check it
out again and
try and replace the image file with a new one, and then
check in and
publish, I get this error:

An error occurred while processing your request:

Unable to execute SQL statement

DBD::Pg::st execute failed: ERROR:  duplicate key violates
unique
constraint "pk_job__resource"
 [for Statement "
            INSERT INTO job__resource (job__id,
resource__id)
            VALUES (?, ?)
        " with ParamValues: 1='4034', 2='1670'] at
/usr/local/bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1187> line
1215.

 Please report this error to your administrator.

Looks like the same error as in
http://
bugs.bricolage.cc/show_bug.cgi?id=1266

On Mon, 18 Jun 2007, John Durkin wrote:
> I can create and publish a media file without any
problem (this is a new
> 10.2 installation we're working on).  Then, when I
check it out again and
> try and replace the image file with a new one, and then
check in and
> publish, I get this error:
>
> An error occurred while processing your request:
>
> Unable to execute SQL statement
>
> DBD::Pg::st execute failed: ERROR:  duplicate key
violates unique
> constraint "pk_job__resource"
> [for Statement "
>           INSERT INTO job__resource (job__id,
resource__id)
>           VALUES (?, ?)
>       " with ParamValues: 1='4034', 2='1670'] at
> /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1187> line
> 1215.
>
> Please report this error to your administrator.

On Jun 19, 2007, at 03:43, Scott Lanning wrote:

> Looks like the same error as in
> http://
bugs.bricolage.cc/show_bug.cgi?id=1266

Although I could swear that I fixed it a while back…

Yep, it's in changes:

> Publishing media documents that have had new files
uploaded to them  
> no longer
> causes a publish failure. Reported by Christian Niles
and numerous  
> others.

So let me see, where is the commit?…Here it is:

   http://viewsvn.bricolage.cc/bricolage/branches/
rev_1_10/lib/Bric/ 
Dist/Resource.pm?r1=7760&r2=7759&pathrev=7760&vi
ew=patch

Best,

David

On Tue, 19 Jun 2007, David E. Wheeler wrote:
> On Jun 19, 2007, at 03:43, Scott Lanning wrote:
>> Looks like the same error as in
>> http://
bugs.bricolage.cc/show_bug.cgi?id=1266
>
> Although I could swear that I fixed it a while back?
>
> Yep, it's in changes:
>
>> Publishing media documents that have had new files
uploaded to them no 
>> longer
>> causes a publish failure. Reported by Christian
Niles and numerous others.
>
> So let me see, where is the commit??Here it is:
>
> http://viewsvn.bricolage.cc/bricolage/b
ranches/rev_1_10/lib/Bric/Dist/Resource.pm?r1=7760&r2=77
59&pathrev=7760&view=patch

The patch says it's from August 9, 2006,
which was after the June 22, 2006 release date of version
1.10.2.
I noted your patch in bug 1266.

i searched through the list archives and find this has
popped up a few
times.  bug 1227 as well.  i'm a little confused.  we
started out with
version 1.10.2 - is it possible that somehow this bug crept
back in?

also - when i create an image media object on-the-fly as a
relation to
another object, and then I try to publish that object, the
related images
will not publish because they "are not on a publish
desk."  anyone know a
fix for this behaviour?  it is undesirable 

jd


On 6/19/07, Scott Lanning <lanningswho.int> wrote:
>
> On Tue, 19 Jun 2007, David E. Wheeler wrote:
> > On Jun 19, 2007, at 03:43, Scott Lanning wrote:
> >> Looks like the same error as in
> >> http://
bugs.bricolage.cc/show_bug.cgi?id=1266
> >
> > Although I could swear that I fixed it a while
back?
> >
> > Yep, it's in changes:
> >
> >> Publishing media documents that have had new
files uploaded to them no
> >> longer
> >> causes a publish failure. Reported by
Christian Niles and numerous
> others.
> >
> > So let me see, where is the commit??Here it is:
> >
> >
> http://viewsvn.bricolage.cc/bricolage/b
ranches/rev_1_10/lib/Bric/Dist/Resource.pm?r1=7760&r2=77
59&pathrev=7760&view=patch
>
> The patch says it's from August 9, 2006,
> which was after the June 22, 2006 release date of
version 1.10.2.
> I noted your patch in bug 1266.
>

ok - so i checked our version 1.10.2 installation file
Resource.pm, and if
this patch should have been committed in the release it
appears that it
wasn't:

http://viewsvn.bricolage.cc/bricolage/b
ranches/rev_1_10/lib/Bric/Dist/Resource.pm?r1=7760&r2=77
59&pathrev=7760&view=patch

my Resource.pm file appears unpatched.  I'm going to try the
patch and
restart and see if I still get the error.

Best,
John D.

On 6/19/07, John Durkin <john.durkingmail.com> wrote:
>
> i searched through the list archives and find this has
popped up a few
> times.  bug 1227 as well.  i'm a little confused.  we
started out with
> version 1.10.2 - is it possible that somehow this bug
crept back in?
>
> also - when i create an image media object on-the-fly
as a relation to
> another object, and then I try to publish that object,
the related images
> will not publish because they "are not on a
publish desk."  anyone know a
> fix for this behaviour?  it is undesirable 
>
> jd
>
>
> On 6/19/07, Scott Lanning <lanningswho.int> wrote:
> >
> > On Tue, 19 Jun 2007, David E. Wheeler wrote:
> > > On Jun 19, 2007, at 03:43, Scott Lanning
wrote:
> > >> Looks like the same error as in
> > >> http://
bugs.bricolage.cc/show_bug.cgi?id=1266
> > >
> > > Although I could swear that I fixed it a
while back?
> > >
> > > Yep, it's in changes:
> > >
> > >> Publishing media documents that have had
new files uploaded to them
> > no
> > >> longer
> > >> causes a publish failure. Reported by
Christian Niles and numerous
> > others.
> > >
> > > So let me see, where is the commit??Here it
is:
> > >
> > >
> > http://viewsvn.bricolage.cc/bricolage/b
ranches/rev_1_10/lib/Bric/Dist/Resource.pm?r1=7760&r2=77
59&pathrev=7760&view=patch
> >
> > The patch says it's from August 9, 2006,
> > which was after the June 22, 2006 release date of
version 1.10.2.
> > I noted your patch in bug 1266.
> >
>
>

On Jun 19, 2007, at 14:44, John Durkin wrote:

> my Resource.pm file appears unpatched.  I'm going to
try the patch and
> restart and see if I still get the error.

It has been fixed since the release of 1.10.2. It is not in
a public  
release, but will be in 1.10.3.

Best,

David