Question: path for exported files

[ftoledo]

Hi all, I run appstream-dep11 into my own repo and the tree structure for data was:

$suite/$component/Components $suite/$component/icons

Should it be $suite/$component/dep11/Component* ?? Maybe are missing the "dep11" directory? thanks!

data/
├── sud
│   ├── contrib
│   │   ├── Components-amd64.yml.gz
│   │   └── Components-i386.yml.gz
│   ├── main
│   │   ├── Components-amd64.yml.gz
│   │   ├── Components-i386.yml.gz
│   │   ├── icons-128x128.tar.gz
│   │   └── icons-64x64.tar.gz
│   └── non-free
│       ├── Components-amd64.yml.gz
│       ├── Components-i386.yml.gz
│       ├── icons-128x128.tar.gz
│       └── icons-64x64.tar.gz
├── sud-updates
│   ├── main
│   │   ├── Components-amd64.yml.gz
│   │   ├── Components-i386.yml.gz
│   │   ├── icons-128x128.tar.gz
│   │   └── icons-64x64.tar.gz
│   └── non-free
│       ├── Components-amd64.yml.gz
│       └── Components-i386.yml.gz
├── torbellino
│   └── main
│       ├── Components-amd64.yml.gz
│       ├── Components-i386.yml.gz
│       ├── icons-128x128.tar.gz
│       └── icons-64x64.tar.gz
└── zonda
    ├── main
    │   ├── Components-amd64.yml.gz
    │   ├── Components-i386.yml.gz
    │   ├── icons-128x128.tar.gz
    │   └── icons-64x64.tar.gz
    └── non-free
        ├── Components-amd64.yml.gz
        ├── Components-i386.yml.gz
        ├── icons-128x128.tar.gz
        └── icons-64x64.tar.gz

[ximion]

@ftoledo You, or your archive management software, are supposed to move those files to the appropriate location.

Please also note that appstream-dep11 is an old and discontinued project, and we recommend using appstream-generator now, which is not only much more up to date, but also a bit easier to use and much, much faster. If you have issues with asgen, we could continue the discussion over there.

Cheers, Matthias

[ftoledo]

Thanks @ximion for your reply. If have these dir i can just cp -r data/* to root/dist of reprepro repository. instead of scripting the copy for each suite/component. But dont worry. Is just for vagrancy. =) I start first with appstream-dep11 due to unmet dependencies on debian stretch (that are my actual repo) but i will migrate ASAP. Thanks

[ximion]

If have these dir i can just cp -r data/* to root/dist of reprepro repository.

In theory that's how it should work (rsync might be the better tool than cp though), but I remember reprepro having issues with correctly handling DEP-11 data in the past - those bugs might be resolved by now though. The appstream-generator tool is able to output to arbitrary directories if the right configuration option is set, by the way ;-) (I would not recommend to output data to the dists/ directory directly though, the ideal workflow is to have the metadata extracted on a separate machine and the machine holding the real archive pull fresh data from the generator machine. The generator does nasty stuff like rendering SVG images and downloading random images from the web, which can be security sensitive in case there are any exploitable bugs in the image or font processing functions. It's a highly unlikely case, but it's better to be safe.)