Conan repository revision range & search issue #12695

Open
opened 2025-11-02 10:18:20 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @RobinMaub on GitHub (Mar 21, 2024).

Description

I have been using Conan repository for ages with Gitea, but since 1 or 2 releases, the revision range is not working anymore (Conan 1.xx) so it leads that we can not use them anymore. Also, the conan table search is broken (returns an empty list)

Gitea Version

1.21.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Linux Ubuntu 22.04

How are you running Gitea?

Self hosted gitea in an AWS machine

Database

None

Originally created by @RobinMaub on GitHub (Mar 21, 2024). ### Description I have been using Conan repository for ages with Gitea, but since 1 or 2 releases, the revision range is not working anymore (Conan 1.xx) so it leads that we can not use them anymore. Also, the conan table search is broken (returns an empty list) ### Gitea Version 1.21.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Linux Ubuntu 22.04 ### How are you running Gitea? Self hosted gitea in an AWS machine ### Database None
GiteaMirror added the topic/packagestype/bug labels 2025-11-02 10:18:20 -06:00
Author
Owner

@KN4CK3R commented on GitHub (Mar 21, 2024):

Could you provide some examples or how to reproduce the error? The was no relevant change.

@KN4CK3R commented on GitHub (Mar 21, 2024): Could you provide some examples or how to reproduce the error? The was no relevant change.
Author
Owner

@RobinMaub commented on GitHub (Mar 21, 2024):

Yes sure, Let's create 3 packages A, B, C.
A depends on B with the following dependency B/[~0]@conan/stable
B depends on C with the following dependency C/[~0]@conan/stable

Let's say that B in 0.0.1 has been built with the dependency on C in version 0.0.10
If I build a new version of C (0.0.11), I expect to find in the server a version of B in 0.0.1 able to work with the latest C because revision range is fine.

It was working few releases ago, but not anymore. Now it answers that we don't have a B 0.0.1 fitting the latest C package dependency.

Is it clear ?

@RobinMaub commented on GitHub (Mar 21, 2024): Yes sure, Let's create 3 packages A, B, C. A depends on B with the following dependency B/[~0]@conan/stable B depends on C with the following dependency C/[~0]@conan/stable Let's say that B in 0.0.1 has been built with the dependency on C in version 0.0.10 If I build a new version of C (0.0.11), I expect to find in the server a version of B in 0.0.1 able to work with the latest C because revision range is fine. It was working few releases ago, but not anymore. Now it answers that we don't have a B 0.0.1 fitting the latest C package dependency. Is it clear ?
Author
Owner

@RobinMaub commented on GitHub (Apr 24, 2024):

Hi everyone,

Any update on that topic ?

@RobinMaub commented on GitHub (Apr 24, 2024): Hi everyone, Any update on that topic ?
Author
Owner

@lunny commented on GitHub (Apr 24, 2024):

I will try to reproduce this on my local machine and do some investigation.

@lunny commented on GitHub (Apr 24, 2024): I will try to reproduce this on my local machine and do some investigation.
Author
Owner

@RobinMaub commented on GitHub (Apr 28, 2024):

@lunny Have you found something ? I have tried more on my side and I confirm the issue. Is the package repository fully compatible with the revisions ?

@RobinMaub commented on GitHub (Apr 28, 2024): @lunny Have you found something ? I have tried more on my side and I confirm the issue. Is the package repository fully compatible with the revisions ?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12695