Skip to content
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

debian/ in master and nest-3 branches #1321

Closed
alexmyczko opened this issue Oct 22, 2019 · 8 comments
Closed

debian/ in master and nest-3 branches #1321

alexmyczko opened this issue Oct 22, 2019 · 8 comments
Assignees
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome

Comments

@alexmyczko
Copy link
Contributor

let me suggest to drop all debian/ completely and make it the packagers work instead of shipping a heavily outdated/no more working version.

@terhorstd terhorstd added ZC: Infrastructure DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) ZP: Pending DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome labels Oct 28, 2019
@jougs
Copy link
Contributor

jougs commented Nov 11, 2019

@alexmyczko: does your suggestion imply your willingness to take over maintainership of the package in debian?

We think that it would be good if you could join one of the next Open NEST Developer Video Conferences in order to have a proper discussion about this.

@alexmyczko
Copy link
Contributor Author

@jougs more like, one can't take over maintainership of a package, if it's not even there yet?

following links give me empty results
https://packages.debian.org/search?keywords=nest
https://packages.debian.org/search?keywords=nest-simulator

however i've seen some other people provide binaries:
https://repology.org/project/nest/versions (not debian based)

i might be interested, since i have a building package:
http://phd-sid.ethz.ch/debian/nest/

thanks for the tip on video conference, do you also use irc (internet relay chat) for development/users?

@jougs
Copy link
Contributor

jougs commented Nov 11, 2019

I meant of course if you would be willing to be the maintainer, once a package exists. We will discuss this topic internally next Monday and the VC might be a good forum to get things going further.

We don't currently have an IRC channel or such. Most discussions happen either here on GitHub, during our open VC, or on the public mailing list.

@alexmyczko
Copy link
Contributor Author

what was the outcome of the discussion?

@jougs
Copy link
Contributor

jougs commented Feb 25, 2020

Our current take on it is that since we provide the PPA for Ubuntu, there is not a lot of pressure to also get it into Debian. If someone is willing to do that and maintain it, we're not against that.

@jougs
Copy link
Contributor

jougs commented Feb 26, 2020

I'm closing this now. Feel free to come back in case you want to become the maintainer of an official nest package in Debian.

@heplesser heplesser removed ZC: Infrastructure DO NOT USE THIS LABEL ZP: Pending DO NOT USE THIS LABEL labels Apr 7, 2020
@steffengraber
Copy link
Contributor

@jougs Didn't you want to close the issue?

@jougs
Copy link
Contributor

jougs commented Apr 14, 2020

@steffengraber: Yes. Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome
Projects
Development

No branches or pull requests

5 participants