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

Add version bounds to all dependencies #119

Open
ivanperez-keera opened this issue Jan 22, 2024 · 3 comments
Open

Add version bounds to all dependencies #119

ivanperez-keera opened this issue Jan 22, 2024 · 3 comments
Assignees
@ivanperez-keera
Labels
CR:Status:Scheduled Admin only: Change requested scheduled CR:Type:Bug Admin only: Change request pertaining to error detected
Milestone
1.6.0

Comments

@ivanperez-keera
Copy link
Member

ivanperez-keera commented Jan 22, 2024 •
edited
Loading

Description

The cabal packages do not currently specify version bounds. This makes hackage complain when we upload packages, and can create stability / installation issues for users.

Type

  • Bug: Cabal files are missing useful information.

Additional context

None.

Requester

  • Ivan Perez.

Method to check presence of bug

It's not possible to check automatically. The check is done by opening the cabal files and checking whether all dependencies of all components specify version bounds.

Expected result

All dependencies of all components specify version bounds.

Desired result

All dependencies of all components specify version bounds.

Proposed solution

Add version bounds to all dependencies of all components of all packages.

Further notes

None.
@ivanperez-keera ivanperez-keera changed the title Add version bounds to all dependencies. Add version bounds to all dependencies Jan 22, 2024
@ivanperez-keera ivanperez-keera added CR:Status:Initiated Admin only: Change request that has been initiated CR:Type:Bug Admin only: Change request pertaining to error detected labels Nov 23, 2024
@ivanperez-keera
Copy link
Member Author

Change Manager: Confirmed that the issue exists.

@ivanperez-keera ivanperez-keera added CR:Status:Confirmed Admin only: Change request that has been acknowledged by the change manager and removed CR:Status:Initiated Admin only: Change request that has been initiated labels Nov 23, 2024
@ivanperez-keera
Copy link
Member Author

Technical Lead: Confirmed that the issue should be addressed.

@ivanperez-keera ivanperez-keera added CR:Status:Accepted Admin only: Change request accepted by technical lead and removed CR:Status:Confirmed Admin only: Change request that has been acknowledged by the change manager labels Nov 23, 2024
@ivanperez-keera
Copy link
Member Author

Technical Lead: Issue scheduled for fixing in Ogma 1.6.0.

Fix assigned to: @ivanperez-keera .

@ivanperez-keera ivanperez-keera added CR:Status:Scheduled Admin only: Change requested scheduled and removed CR:Status:Accepted Admin only: Change request accepted by technical lead labels Nov 25, 2024
@ivanperez-keera ivanperez-keera added this to the 1.6.0 milestone Nov 25, 2024
@ivanperez-keera ivanperez-keera self-assigned this Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ivanperez-keera ivanperez-keera

Labels
CR:Status:Scheduled Admin only: Change requested scheduled CR:Type:Bug Admin only: Change request pertaining to error detected
Projects
None yet
Milestone
1.6.0
Development

No branches or pull requests
1 participant
@ivanperez-keera