* Cameron Dale <[EMAIL PROTECTED]> [070905 00:49]:
> I recently added a new architecture to my conf/distributions file. After
> that I did a "reprepro export" to get the new index files created, which
> worked fine (I thought). Looking back now, I see that the architecture:all
> packages in my archive are not in the new architecture's Packages files.
> Subsequently adding new-arch-specific packages did not add the arch:all
> packages to the new arch either.
This is (consequence of) intended behaviour. You can have different
versions (including no version) of an arch:all package within different
architectures (so one can have working binary packages of different
versions in different architectures depending on arch:all packages
of the same version and thinks still work).
The downsize is that reprepro thus stores arch:all packages just as
it handles binary packages, which just share the same file for the
different architectures.
As reprepro does not realize that there was a new architecture added,
it cannot special case that. And even if it could, and there would be
multiple other architectures yet, where should it copy them from, and
if the versions of their arch:all packages differ, which should it
choose?
> To get them added I had to manually
> traverse my pool and do "reprepro includedeb package.deb" for all the
> arch:all binary packages.
An easier way is to use the pull command. Add a pull rule like the
following into conf/pulls:
Name: copyarchall
From: <your codename>
Architectures: i386>powerpc
FilterFormula: Architecture (== all)
and add
Pull: copyarchall
to your distribtion in conf/distributions
Then call reprepro's pull command.
(Perhaps I should allow From: * for pull rules just as for update rules.
This way one could have one pull rule like that for all
distributions...)
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
