Re: Format for name of .changes file?
...then katie has a bug. It rejected my package because the name of
my packages files was 'not valid'. I don't have the reason file
anymore. I suspect that katie explicitly checks this since there
was a reason file with that excuse.
On Thu, Feb 21, 2002 at 08:02:19PM -0600, Adam Heath wrote:
> On Thu, 21 Feb 2002 firstname.lastname@example.org wrote:
> > I have been using the format
> > <package>_<version>.changes
> > The new archive maintenance program (katie?) doesn't like this. It
> > does appear to like
> > <package>_<version>_<architecture>.changes
> > I don't see a reference to this in the developer's reference or policy
> > manual. What are our options? Can the architecture be 'any'? Can it
> > be 'source'?
> The name of the .changes should not matter at all.
> If it does, than katie has a bug. I have no verified this, however.