3
5
Fork
You've already forked xut
3

Search results appear twice if they are in unofficial package #38

Closed
opened 2025年10月22日 18:19:14 +02:00 by mobinmob · 9 comments
(~>) Info: Searching for <tixati> ... 
(~>) Info: Found in abyss-packages: 
 (*) tixati
(~>) Info: Found in void-packages: 
 (*) tixati

It should only appear in the origin repo (abyss-packages).

``` (~>) Info: Searching for <tixati> ... (~>) Info: Found in abyss-packages: (*) tixati (~>) Info: Found in void-packages: (*) tixati ``` It should only appear in the origin repo (abyss-packages).
Contributor
Copy link

that is intended behaviour
to see if packages is in more repos

that is intended behaviour to see if packages is in more repos
Author
Owner
Copy link

tixati is not in any other repo.
The bug is that it appears in void-packages.

tixati is not in any other repo. The bug is that it appears in void-packages.
Contributor
Copy link

yes
void-packages list came from already merged repo now, not from void-packages only

I am aware of that

Looking for easiest way to track what is in origin not merged repo

yes void-packages list came from already merged repo now, not from void-packages only I am aware of that Looking for easiest way to track what is in origin not merged repo
Author
Owner
Copy link

@zenobit wrote in #38 (comment):

yes void-packages list came from already merged repo now, not from void-packages only

Current way of presenting results makes the distinction between origin repos meaningless and I will fix it or stop searching entirelly in void-packages (except for restricted packages ofc). The user can find the packages that build in their system directly using xbps...

@zenobit wrote in https://codeberg.org/mobinmob/xut/issues/38#issuecomment-7860500: > yes void-packages list came from already merged repo now, not from void-packages only > Current way of presenting results makes the distinction between origin repos meaningless and I will fix it or stop searching entirelly in void-packages (except for restricted packages ofc). The user can find the packages that build in their system directly using xbps...
Contributor
Copy link

solution is move updating lists after sync and before merging repos

solution is move updating lists after sync and before merging repos
Author
Owner
Copy link

@zenobit wrote in #38 (comment):

solution is move updating lists after sync and before merging repos

Yep 👍
I plan to move the list creation logic to a small separate function and call it when there is a change inside the sync or retrieve functions (including the removal of stale lists - nice btw ;) ).

@zenobit wrote in https://codeberg.org/mobinmob/xut/issues/38#issuecomment-7863632: > solution is move updating lists after sync and before merging repos Yep 👍 I plan to move the list creation logic to a small separate function and call it when there is a change inside the sync or retrieve functions (including the removal of stale lists - nice btw ;) ).
Author
Owner
Copy link

After much consideration...
The current way we are creating template lists works, but the creation/update is all over the place.
I will try to centralize the logic as follows:
Have the repo creation commands in create_template_list_for_repo(). Call the function when a repo is cloned or synced.
Create the restricted templates list when the default_repo is cloned or synced.

After much consideration... The current way we are creating template lists works, but the creation/update is all over the place. I will try to centralize the logic as follows: Have the repo creation commands in `create_template_list_for_repo()`. Call the function when a repo is cloned or synced. Create the restricted templates list when the default_repo is cloned or synced.
Contributor
Copy link

First I want use custom branch for repos
(need bit more testing)
And I will create MR

then...
I will look at template_lists again

First I want use custom branch for repos (need bit more testing) And I will create MR then... I will look at template_lists again
Author
Owner
Copy link

Solved in #55.

Solved in https://codeberg.org/mobinmob/xut/pulls/55.
Sign in to join this conversation.
No Branch/Tag specified
master
template_list_cache
find_repodir_caching
unique_repodir_names
mobinmob-patch-1
yet_another_touch
mdocs
moar_fixes
seperate_build_preparation
root_check
ls_to_list_dirs
CONF_WORKDIR.override
safety_portability_fixes
fix_updates
fixes_and_find
get_key_from_template
v.0.3
v.0.2
dev
manyrepos
v.0.4.2
0.4.1
v.0.3.1
v.0.3
v.0.2.1
v.0.2
v.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mobinmob/xut#38
Reference in a new issue
mobinmob/xut
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?