> Both packages have been uploaded at the same time, and I could not
>>>> > forsee that it has still not been built and uploaded on sparc on
>>>> > time. I think to avoid this situation in the future the correct way
>>>> > was to use a versioned "Break
ould not
>>> > forsee that it has still not been built and uploaded on sparc on time.
>>> > I think to avoid this situation in the future the correct way was to
>>> > use a versioned "Breaks" field on nexuiz-data:
>>> >
>>> &
on sparc on time.
>> > I think to avoid this situation in the future the correct way was to
>> > use a versioned "Breaks" field on nexuiz-data:
>> >
>> > Breaks: nexuiz (<< 2.3)
Does the testing script look at this? If not, (AFAIK it do
this situation in the future the correct way was to use
> > a versioned "Breaks" field on nexuiz-data:
> >
> > Breaks: nexuiz (<< 2.3)
>
> I might have completely missed your point, but if you have nexuiz-data
> Depends on nexuiz (2.3), then
>
a versioned "Breaks" field on nexuiz-data:
>
> Breaks: nexuiz (<< 2.3)
I might have completely missed your point, but if you have nexuiz-data
Depends on nexuiz (2.3), then
it wouldn't get installed, would it ? Or is there a problem to have nexuiz
Depends nexuiz
someone who prefers to remain anonymous writes:
> Reinhard Tartler wrote:
>> Sorry? Nexuiz 2.3 is already package by the debian games team, uploaded
>> to unstable and requested to be synced to gutsy by my, and available in
>> both distros. What are you exactly requesting?
&
6 matches
Mail list logo
