aptly publish multiple component from multiple mono component snapshots #36

Closed
erickeller opened this Issue Apr 17, 2014 · 6 comments

Comments

Projects
None yet
2 participants
@erickeller

Andrey said:

"What I see is that snapshot should be mono-component (it should contain packages from one component only). So most probably mirror should be mono-component. But when publishing aptly should give an option to publish several mono-component snapshots under one prefix/distribution so that published repository is multi-component once again."

@smira smira added this to the v0.6 milestone Apr 17, 2014

@smira smira added the enhancement label May 10, 2014

smira added a commit that referenced this issue Jun 3, 2014

smira added a commit that referenced this issue Jun 3, 2014

Update to new PublishedRepo with multiple components. #36
Multiple component publishing doesn't work yet, but old features are working.

smira added a commit that referenced this issue Jun 4, 2014

smira added a commit that referenced this issue Jun 5, 2014

smira added a commit to aptly-dev/aptly-bash-completion that referenced this issue Jun 5, 2014

smira added a commit that referenced this issue Jun 5, 2014

smira added a commit that referenced this issue Jun 5, 2014

smira added a commit that referenced this issue Jun 7, 2014

smira added a commit that referenced this issue Jun 7, 2014

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Jun 7, 2014

Member

Done in master.

Member

smira commented Jun 7, 2014

Done in master.

@smira smira closed this Jun 7, 2014

smira added a commit to aptly-dev/aptly-dev.github.io that referenced this issue Jun 7, 2014

@erickeller

This comment has been minimized.

Show comment
Hide comment
@erickeller

erickeller Jun 8, 2014

Hi Andrey,

Thanks for implementing this will try it out and give you feedback...

Eric

Hi Andrey,

Thanks for implementing this will try it out and give you feedback...

Eric

@erickeller

This comment has been minimized.

Show comment
Hide comment
@erickeller

erickeller Jun 10, 2014

Hi Andrey I am testing the newly implemented feature on master with multiple component publishing with the following example:

aptly mirror create -with-sources=true -architectures="amd64,i386" debian-wheezy http://ftp.ch.debian.org/debian wheezy main contrib non-free

aptly mirror update debian-wheezy
aptly snapshot create daily from mirror debian-wheezy

aptly publish snapshot -component="main,contrib,non-free" daily
Usage: aptly publish snapshot []

aptly publish snapshot - publish snapshot

Options:
-architectures="": list of architectures to consider during (comma-separated), default to all available
-component="": component name to publish (for multi-component publishing, separate components with commas)
-config="": location of configuration file (default locations are /etc/aptly.conf, ~/.aptly.conf)
-dep-follow-all-variants=false: when processing dependencies, follow a & b if depdency is 'a|b'
-dep-follow-recommends=false: when processing dependencies, follow Recommends
-dep-follow-source=false: when processing dependencies, follow from binary to Source packages
-dep-follow-suggests=false: when processing dependencies, follow Suggests
-distribution="": distribution name to publish
-gpg-key="": GPG key ID to use when signing the release
-keyring=: GPG keyring to use (instead of default)
-label="": label to publish
-origin="": origin name to publish
-secret-keyring="": GPG secret keyring to use (instead of default)
-skip-signing=false: don't sign Release files with GPG
ERROR: unable to parse command

if I remove the -component it only publish main as defined.

by opposition when using -component="contrib" it works publishing contrib

aptly publish snapshot -component="contrib" daily
Loading packages...
Generating metadata files and linking package files...

Snapshot daily has been successfully published.
Please setup your webserver to serve directory '/media/aptly/.aptly/public' with autoindexing.
Now you can add following line to apt sources:
deb http://your-server/ wheezy contrib
Don't forget to add your GPG key to apt with apt-key.

You can also use aptly serve to publish your repositories over HTTP quickly.

do you have some hints?

Hi Andrey I am testing the newly implemented feature on master with multiple component publishing with the following example:

aptly mirror create -with-sources=true -architectures="amd64,i386" debian-wheezy http://ftp.ch.debian.org/debian wheezy main contrib non-free

aptly mirror update debian-wheezy
aptly snapshot create daily from mirror debian-wheezy

aptly publish snapshot -component="main,contrib,non-free" daily
Usage: aptly publish snapshot []

aptly publish snapshot - publish snapshot

Options:
-architectures="": list of architectures to consider during (comma-separated), default to all available
-component="": component name to publish (for multi-component publishing, separate components with commas)
-config="": location of configuration file (default locations are /etc/aptly.conf, ~/.aptly.conf)
-dep-follow-all-variants=false: when processing dependencies, follow a & b if depdency is 'a|b'
-dep-follow-recommends=false: when processing dependencies, follow Recommends
-dep-follow-source=false: when processing dependencies, follow from binary to Source packages
-dep-follow-suggests=false: when processing dependencies, follow Suggests
-distribution="": distribution name to publish
-gpg-key="": GPG key ID to use when signing the release
-keyring=: GPG keyring to use (instead of default)
-label="": label to publish
-origin="": origin name to publish
-secret-keyring="": GPG secret keyring to use (instead of default)
-skip-signing=false: don't sign Release files with GPG
ERROR: unable to parse command

if I remove the -component it only publish main as defined.

by opposition when using -component="contrib" it works publishing contrib

aptly publish snapshot -component="contrib" daily
Loading packages...
Generating metadata files and linking package files...

Snapshot daily has been successfully published.
Please setup your webserver to serve directory '/media/aptly/.aptly/public' with autoindexing.
Now you can add following line to apt sources:
deb http://your-server/ wheezy contrib
Don't forget to add your GPG key to apt with apt-key.

You can also use aptly serve to publish your repositories over HTTP quickly.

do you have some hints?

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Jun 10, 2014

Member

Hi @erickeller!

You need to have three different mirrors (and snapshots, respectively) for each component of Debian wheezy.

Then you need to publish them (three snapshots) as three components.

Example is given in this blog post: http://smira.ru/en/posts/aptly-06.html

Member

smira commented Jun 10, 2014

Hi @erickeller!

You need to have three different mirrors (and snapshots, respectively) for each component of Debian wheezy.

Then you need to publish them (three snapshots) as three components.

Example is given in this blog post: http://smira.ru/en/posts/aptly-06.html

@erickeller

This comment has been minimized.

Show comment
Hide comment
@erickeller

erickeller Dec 1, 2014

Work great thanks for the blog post...

Work great thanks for the blog post...

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Dec 1, 2014

Member

It is available as part of aptly documentation now: http://www.aptly.info/doc/feature/multi-component/

Member

smira commented Dec 1, 2014

It is available as part of aptly documentation now: http://www.aptly.info/doc/feature/multi-component/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment