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.

Sign up for GitHub

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

Jump to bottom

Packaging 3.16 and beyond #19

Open
mmarquar opened this issue Oct 17, 2018 · 3 comments
Open

Packaging 3.16 and beyond #19

mmarquar opened this issue Oct 17, 2018 · 3 comments

Comments

@mmarquar
Copy link

We (CSIRO ASKAP) are just about to move to 3.16.1 as preparation for 7. Currently, we just create debian binary packages from our build system (3.14.x and 3.16.1)which are not supposed to comply to policies and are single platform. We have been looking at this project and like to move and possibly contribute to this.
Is anyone coming to the collab meeting in Melbourne next month? We could discuss this furher then.
@mark0n
Copy link
Contributor

mark0n commented Oct 18, 2018

Hi @mmarquar, welcome to the epicsdeb project! I'm glad to hear that you are considering to contribute - we can always use some helping hands :-) You can contribute by submitting issue tickets, creating pull requests or by testing new releases.

Unfortunately @mdavidsaver and I will not be able to attend the EPICS meeting in person. I'm not sure about @aderbenev. At FRIB I'm currently working on getting 3.15.6 packaged and deployed. At the same time I'm trying to resolve issues on Debian stretch. Once that's done (maybe by the end of the year) we are planning to start working on packaging EPICS 7. We are intending to skip 3.16 and want to move directly to 7. Base 3.16 and 7 are pretty similar when it comes to the EPICS 3 part and adding the EPICS 4 part doesn't hurt ;-)

When it comes to packaging 3.16 or 7, I would recommend to start with my 3.15.6 branch.

@ralphlange
Copy link
Contributor

+1 for skipping 3.16
3.16.1 has a few really nasty bugs that are fixed in 7.0.
The immanent 3.16.2 release will be the last one in the 3.16 series, which will be dropped.

Try checking out the 7.0 branch without submodules - surprise: it will work, and build exactly the V3 scope.

@aderbenev
Copy link
Member

I concur on all above - with our legacy-ish-ness in places, there would be no real demand to upgrade to and test the 3.16. Plus, we already have EPICS 7 and modules binary bundles (not from Debian packaging) used for AreaDetector IOCs. I won't be attending the meeting alas, but Kunal is coming - he's not involved in packaging much, but can bring your insights to us at NSLS-II.

mark0n added a commit to mark0n/epics-base-package that referenced this issue May 21, 2020
@mark0n
Merge pull request epicsdeb#19 in EPICS/epics-base from uc3 to releas…
0f41255 
…e/fc3

* commit '22302320fde3e949302cfd48ad3dd6d2b7df19c9':
  Release 3.15.6-3
  Start default instance of ioclogserver service
  Improve systemd support, remove legacy init scripts
  Avoid deprecated dh_install --fail-missing
  Remove debug package (nowadays built automatically)
  Add patch for shebang lines of Perl scripts
  Bump up standards version to 4.3.0
  Apply patch that removes cacExitHandler()
  libca: don't set thread local storage handle to zero on cleanup
  Apply patches that add callback queue status functionality
  Release 3.15.6-1+frib3
  Apply patch that removes cacExitHandler()
  libca: don't set thread local storage handle to zero on cleanup
  Release 3.15.6-2
  Add patches for MSI bugs lp:1810946 and lp:1810949
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mmarquar @ralphlange @mark0n @aderbenev