Skip to content

Add new package citus for work item 47499297 #13653

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

Open
wants to merge 14 commits into
base: 3.0-dev
Choose a base branch
from

Conversation

cyberbandya007
Copy link
Contributor

@cyberbandya007 cyberbandya007 commented May 1, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

Adds new package citus for work item 47499297

Change Log
  • citus
Does this affect the toolchain?

NO

Test Methodology

@cyberbandya007 cyberbandya007 requested a review from a team as a code owner May 1, 2025 14:03
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels May 1, 2025
@cyberbandya007 cyberbandya007 force-pushed the skarambelkar/citus-addition-1 branch from 07293b3 to d93e23d Compare May 1, 2025 15:20
Copy link
Contributor

@kgodara912 kgodara912 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time="2025-05-02T07:38:08Z" level=debug msg="# 1 of 185 tests failed."
Still your one test is failing. Also, please check warnings in rpm build logs in your local or buddy build and see if they can be resolved?

Patch0: disable_unwanted_tests.patch
%endif
URL: https://github.com/citusdata/%{name}
BuildRequires: postgresql-devel
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many spec files put make and gcc in BuildRequires, do we need to put here explicitly for some environments to make this spec file work in those environments?


%build
currentgccver="$(gcc -dumpversion)"
requiredgccver="4.8.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we put it as requiredmingccver for better communication?

%install
%make_install
# Install documentation with a better name:
%{__mkdir} -p %{buildroot}%{_docdir}/postgresql/extension
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any difference between this and below mkdir? If not, then we can make them uniform.

%doc %{_docdir}/postgresql/extension/NOTICE-%{name}

%changelog
* Mon Apr 29 2025 Sandeep Karambelkar <skarambelkar@microsoft.com> - 13.0.3-1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was Tue

@@ -0,0 +1,86 @@
Summary: PostgreSQL-based distributed RDBMS
Name: citus
Conflicts: %{name}
Copy link
Contributor

@kgodara912 kgodara912 May 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check if we can put version number (something like < %{Version}) if the package conflicts with itself..

@@ -0,0 +1,86 @@
Summary: PostgreSQL-based distributed RDBMS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we didn't start with the .spec available upstream?

https://github.com/citusdata/packaging/blob/all-citus/citus.spec

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We did use the same spec and fixed it for azure linux.

@LeoMar4 LeoMar4 changed the title Add new package citus for work item 47499297 Linkedin Add new package citus for work item 47499297 May 8, 2025
Copy link
Collaborator

@jslobodzian jslobodzian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blocking PR until we get clarity on the AGPL license

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants