Hello,

On antradienis 04 Rugpjūtis 2009 16:18:49 Bernhard R. Link wrote:

> > This way "Architecture: $arch" is never broken and "Architecture: all" is
> > used as a staging area for arch:all packages. I have not tested yet if I
> > could use "Architecture: dummy" rather than "Architecture: all" as such a
> > staging area for arch:all packages, but I believe I can hence the bug is
> > wishlist. However, it would be great if you could implement such
> > inclusion behaviour in reprepro itself. Just let me know if you would
> > like to see my scripts.
>
> I've considered addings something like that (using the 'embargoalls'
> Tracking mode), but that was more complicated than I thought.
> (Especially as I mostly planed it for updates, so that architecture all
> packages are embargoes until they can be used).

Ok, so far as I can see something like this could work:

1) Remove that error denying "Architecture: all" in conf/distributions

2) If there is Architecture: all in conf/distributions and _all.deb is being 
included via includedeb, include etc., it should be included to that 
Architecture: all section as well. IIRC, this was not the case with previous 
reprepro versions as I had to "generate" a pull which would pull from $arch to 
"all" manually. It is useful to have the newest arch:all packages apt-getable  
in central place for buildds. URI for this is like:

deb URL dists/$distro/main/binary-all/

3) When 'embargoalls' (or similar) tracking mode is enabled, include / 
processincoming do not include _all.deb packages to those architectures, which 
are not present in the .changes Architecture field. However, it always adds 
those _all.deb to tracking database. Now whenever another .changes is being 
processed which match Distro/Source/Version in the tracking data, include / 
processincoming should include _all.debs (flagged 'a' as far as I understand) 
from tracking into the target architecture as well.

This behaviour would eliminate the need for my custom scripts completely. 
Maybe I will try to look at the code.

-- 
Modestas Vainius <modes...@vainius.eu>

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to