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

release-critical parts of community infrastructure #1742

Closed
markus2330 opened this Issue Dec 17, 2017 · 16 comments

Comments

Projects
None yet
3 participants
@markus2330
Contributor

markus2330 commented Dec 17, 2017

Thanks to @BernhardDenner we quickly recovered from the breach at libelektra.org. Unfortunately, some release-critical parts are not yet fixed:

  • git repos for ftp+docu: Before the breach it was possible to directly push the release tarballs and docu to the server. It seems these parts are now plain files and not git repos anymore?
  • stretch debian packages not provided: the stretch build job happily builds debian packages but currently there is no way to download them (No webserver reachable at https://unstable.libelektra.org/elektra-stable/).

And small new wishes for the release notes:

And:

@markus2330 markus2330 added the urgent label Dec 17, 2017

@markus2330 markus2330 added this to the 0.8.21 milestone Dec 17, 2017

@BernhardDenner

This comment has been minimized.

Show comment
Hide comment
@BernhardDenner

BernhardDenner Dec 20, 2017

Contributor

@git for docu: I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol. Maybe it was configured somewhere else I not aware of.

Should this be usable by other users too, e.g. pulling from anonymous? If not, I prefer to use SSH for the transport layer, as this supports key based authentication and works out of the box by just creating a local user.

Contributor

BernhardDenner commented Dec 20, 2017

@git for docu: I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol. Maybe it was configured somewhere else I not aware of.

Should this be usable by other users too, e.g. pulling from anonymous? If not, I prefer to use SSH for the transport layer, as this supports key based authentication and works out of the box by just creating a local user.

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Dec 21, 2017

Contributor

@BernhardDenner Thank you for looking into it!

I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol.

It was done using ssh but the repos were configured in a way that they automatically check out when something is pushed into them.

as this supports key based authentication and works out of the box by just creating a local user.

Yes, I would also prefer that. Can you create a user with correct permissions and add my public key?

Contributor

markus2330 commented Dec 21, 2017

@BernhardDenner Thank you for looking into it!

I do not find any Apache related configuration that allows pulling/pushing to doc.liblektra.org using http protocol.

It was done using ssh but the repos were configured in a way that they automatically check out when something is pushed into them.

as this supports key based authentication and works out of the box by just creating a local user.

Yes, I would also prefer that. Can you create a user with correct permissions and add my public key?

@BernhardDenner

This comment has been minimized.

Show comment
Hide comment
@BernhardDenner

BernhardDenner Dec 21, 2017

Contributor

Git repo for releases/downloads now up2date again. See mail for instructions.

Contributor

BernhardDenner commented Dec 21, 2017

Git repo for releases/downloads now up2date again. See mail for instructions.

@BernhardDenner

This comment has been minimized.

Show comment
Hide comment
@BernhardDenner

BernhardDenner Dec 21, 2017

Contributor

New subdomain redirects added, Letsencrypt setup will be done in right now.
However, you still have to update the liblektra.org domain, because these subdomains are not registered right now

Contributor

BernhardDenner commented Dec 21, 2017

New subdomain redirects added, Letsencrypt setup will be done in right now.
However, you still have to update the liblektra.org domain, because these subdomains are not registered right now

@BernhardDenner

This comment has been minimized.

Show comment
Hide comment
@BernhardDenner

BernhardDenner Dec 21, 2017

Contributor

SSL certificate is now updated too, thus includes the now subdomains.

Contributor

BernhardDenner commented Dec 21, 2017

SSL certificate is now updated too, thus includes the now subdomains.

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Dec 21, 2017

Contributor

Thank you! Subdomains are added.

(I also wrote you an email.)

Contributor

markus2330 commented Dec 21, 2017

Thank you! Subdomains are added.

(I also wrote you an email.)

@markus2330 markus2330 modified the milestones: 0.8.21, 0.8.22 Dec 22, 2017

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Dec 22, 2017

Contributor

Stretch repos are the only missing item. The git repos for ftp/doc work wonderful!

Contributor

markus2330 commented Dec 22, 2017

Stretch repos are the only missing item. The git repos for ftp/doc work wonderful!

@markus2330 markus2330 closed this Dec 22, 2017

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Dec 22, 2017

Contributor

Automatic checkout of doc does not seem to work. Is it a problem if non-git files are lying around? (They are periodically copied from the build server).

Contributor

markus2330 commented Dec 22, 2017

Automatic checkout of doc does not seem to work. Is it a problem if non-git files are lying around? (They are periodically copied from the build server).

@markus2330 markus2330 reopened this Dec 22, 2017

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Feb 6, 2018

Contributor

@BernhardDenner Any update here?

Contributor

markus2330 commented Feb 6, 2018

@BernhardDenner Any update here?

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 Feb 7, 2018

Contributor

Seems like we have an additional problem: The mailman Web interface is broken: I cannot subscribe/unsubscribe (seems to do a redirect to http when submitting form data)

Contributor

markus2330 commented Feb 7, 2018

Seems like we have an additional problem: The mailman Web interface is broken: I cannot subscribe/unsubscribe (seems to do a redirect to http when submitting form data)

@markus2330 markus2330 modified the milestones: 0.8.22, 0.8.23 Feb 24, 2018

@markus2330 markus2330 assigned ingwinlu and unassigned BernhardDenner May 1, 2018

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 May 1, 2018

Contributor

It would be great to have this running for 0.8.23. @ingwinlu what is the current status?

Contributor

markus2330 commented May 1, 2018

It would be great to have this running for 0.8.23. @ingwinlu what is the current status?

@markus2330 markus2330 referenced this issue May 1, 2018

Closed

Stretch Debian Packages #1752

0 of 2 tasks complete
@ingwinlu

This comment has been minimized.

Show comment
Hide comment
@ingwinlu

ingwinlu May 1, 2018

Contributor

I tried to get it to build debian packages in docker containers but did not get very far, mostly because I needed to revamp the current images (we need huge images to build all the debian packages because of all the dependencies).

Additionally the feedback on #1866 kept me busy and all the other 'urgent' stuff that I am assigned to.

Contributor

ingwinlu commented May 1, 2018

I tried to get it to build debian packages in docker containers but did not get very far, mostly because I needed to revamp the current images (we need huge images to build all the debian packages because of all the dependencies).

Additionally the feedback on #1866 kept me busy and all the other 'urgent' stuff that I am assigned to.

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 May 1, 2018

Contributor

Which 'urgent' tasks did I assign?

  • I do not know if #1866 is urgent, I thought it would be good to have it within the release notes.
  • #1901 seems unrealistic for this release anyway.
  • The Debian packages are basically the only thing that are needed by external people.

I renamed 'bounty' to 'urgent' to make more clear which the urgent tasks are.

Contributor

markus2330 commented May 1, 2018

Which 'urgent' tasks did I assign?

  • I do not know if #1866 is urgent, I thought it would be good to have it within the release notes.
  • #1901 seems unrealistic for this release anyway.
  • The Debian packages are basically the only thing that are needed by external people.

I renamed 'bounty' to 'urgent' to make more clear which the urgent tasks are.

@ingwinlu

This comment has been minimized.

Show comment
Hide comment
@ingwinlu

ingwinlu May 3, 2018

Contributor

#1866 in itself might not be urgent. but whenever I need to add something like the homepage build or the debian packaging I have to test it locally. And this takes forever as my pc takes 15min+ to build elektra.

Having it merged would mean I could open new PR's for both of those tasks where we could discuss the problems that occur during them as well as have the ci system display the logs in an easily acceptable manner. This would make my life considerable easier.

Contributor

ingwinlu commented May 3, 2018

#1866 in itself might not be urgent. but whenever I need to add something like the homepage build or the debian packaging I have to test it locally. And this takes forever as my pc takes 15min+ to build elektra.

Having it merged would mean I could open new PR's for both of those tasks where we could discuss the problems that occur during them as well as have the ci system display the logs in an easily acceptable manner. This would make my life considerable easier.

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 May 3, 2018

Contributor

Yes, I am for merging it soon, too.

From my point of view only docu is misssing.

Contributor

markus2330 commented May 3, 2018

Yes, I am for merging it soon, too.

From my point of view only docu is misssing.

@markus2330 markus2330 removed the urgent label May 11, 2018

@markus2330

This comment has been minimized.

Show comment
Hide comment
@markus2330

markus2330 May 11, 2018

Contributor

Closing, because it is a duplicate from #1752. Other issue was migrated.

Contributor

markus2330 commented May 11, 2018

Closing, because it is a duplicate from #1752. Other issue was migrated.

@markus2330 markus2330 closed this May 11, 2018

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