New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate usage of packagecloud.io for Debian/Ubuntu repositories #663

Closed
untitaker opened this Issue Aug 24, 2017 · 10 comments

Comments

Projects
None yet
3 participants
@untitaker
Member

untitaker commented Aug 24, 2017

Debian has policies that prevent users from using the latest vdirsyncer version. We should make it possible for users to add a repository that contains the latest version while still using their native package manager for updates.

The two options for this are:

An ideal solution would automatically generate apt packages from the PyPI releases.

@hobarrera investigated this sometime ago, however it's unclear what the conclusions/results were. We should try this out again and perhaps contact packagecloud's support about our usecase. We should also clearly document what we found out.

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 24, 2017

By the way, I would consider it unproblematic to bundle all dependencies of vdirsyncer in the same package, as long as it doesn't conflict with the system-site-packages. In fact we probably should also choose a name for our packages that doesn't conflict with the one packaged by debian (compare with the repositories for mongodb, slack, docker)

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 24, 2017

17:23 "blocker". I'd actually done it. :P
17:23 Can you see the packages if you log into packagecloud? https://packagecloud.io/pimutils/todoman

I can see the packages python-atomicwrites and python-pyxdg without logging in.

@WhyNotHugo

This comment has been minimized.

Member

WhyNotHugo commented Aug 24, 2017

Looks like package generation was the actual issue: pimutils/todoman#84

packagecloud merely provides repositories, not packaging itself.

CI integration seems pretty simple: https://packagecloud.io/hobarrera/todoman/ci#travis

@geier

This comment has been minimized.

Member

geier commented Aug 24, 2017

@WhyNotHugo

This comment has been minimized.

Member

WhyNotHugo commented Aug 24, 2017

The issue I mentioned above has been reported:

jordansissel/fpm#1106

However, there's an extra issue with fpm; ideally, both khal and todoman aren't pure-python, since we provide custom entry point to avoid setuptools' overhead.

@geier There's a public instance here: https://build.opensuse.org/

@geier

This comment has been minimized.

Member

geier commented Aug 24, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 24, 2017

This also looks very interesting: https://github.com/spotify/dh-virtualenv

@WhyNotHugo

This comment has been minimized.

Member

WhyNotHugo commented Aug 24, 2017

dh-virtualenv looks promising. I think the idea of having a virtualenv makes sense it that we don't have to deal with outdated dependencies (and I don't want to have to package the whole dependency tree for debian).

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 25, 2017

FWIW I have had great success with dh-virtualenv. The initial setup is quite laborious and you have to write your own docker/docker-compose files to build packages for all distros, but once you have that releases are completely automatic (although resource intensive).

@untitaker untitaker removed the in progress label Aug 30, 2017

untitaker added a commit that referenced this issue Aug 31, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Sep 2, 2017

Btw I now replaced dh-virtualenv with fpm. It turns out fpm has a virtualenv source.

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