Bug 1223333 - kubernetes1.30-client-1.30.0-1.1.x86_64 requires kubernetes1.30-client-common
Summary: kubernetes1.30-client-1.30.0-1.1.x86_64 requires kubernetes1.30-client-common
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-24 05:56 UTC by Felix Niederwanger
Modified: 2024-04-24 08:54 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Niederwanger 2024-04-24 05:56:58 UTC
When updating TW 20240419 to 20240421: 

> Problem: 1: the to be installed kubernetes1.30-client-1.30.0-1.1.x86_64 requires 'kubernetes1.30-client-common', but this requirement cannot be provided
> not installable providers: kubernetes1.30-client-common-1.30.0-1.1.x86_64[download.opensuse.org-oss]
> 
>  Solution 1: deinstallation of kubernetes-client-1.29.3-40.1.x86_64
>  Solution 2: deinstallation of kubernetes1.29-client-common-1.29.3-1.1.x86_64
>  Solution 3: keep obsolete kubernetes-client-1.29.3-40.1.x86_64
>  Solution 4: break kubernetes1.30-client-1.30.0-1.1.x86_64 by ignoring some of its dependencies

Solution 3 requires some follow-ups.
Comment 1 hui 2024-04-24 07:07:32 UTC
Solution 2. Look at the version numbers…
Comment 2 hui 2024-04-24 07:12:18 UTC
kubernetes1.30-client-1.30.0-1.1.x86_64 And kubernetes1.30-client-common-1.30.0-1.1.x86_64 are available in the Tumbleweed OSS repository.

You maybe have hit a not properly synced mirror…
Comment 3 Felix Niederwanger 2024-04-24 07:13:16 UTC
(In reply to hui from comment #2)
> kubernetes1.30-client-1.30.0-1.1.x86_64 And
> kubernetes1.30-client-common-1.30.0-1.1.x86_64 are available in the
> Tumbleweed OSS repository.
> 
> You maybe have hit a not properly synced mirror…

Ah yes, that would explain. Will try again later and report back.
Comment 4 Felix Niederwanger 2024-04-24 08:54:25 UTC
Yep, issue resolved.