| Summary: | rpm-build install error | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpm | CVE: | |
| Status comment: | |||
|
Description
Georges Eckenschwiller
2019-05-02 16:58:04 CEST
For mga6, python3-pkg-resources: the source package is the python-setuptools urpmi-debuginfo-install: the source package is the gdb Here are some details about the error. The problem lies in the version of the packages. The packages exist in repositories, but not in the version requested when installing rpm-build python3-pkg-resources: request=41.0.0-1.mga7, existing=36.2.4-4.mga7 urpmi-debuginfo-install: request=8.2-7.mga7, existing=8.0.1-1 and 8.0.1-2 Severity:
normal =>
critical As we build every pkg with rpm-build, the build system should be broken also if rpm-build isn't installable. Have you tried other mirrors? What's the exact error? Are you using urpmi or dnf? thank you Jani, I think this is effectively a mirror problem. I use distrib-coffee which is usually well synchronized. I just checked with Sophie's website: urpmi-debuginfo-install is there with the version 8.2 I just checked distrib-coffee. The version is now 8.2 I try again, after syncing my own mirror. In fact, it's my synchronization with rsync that is kidding. I redid using ftp. Now it's OK. thanks again Status:
NEW =>
UNCONFIRMED (In reply to Georges Eckenschwiller from comment #4) > thank you Jani, > I think this is effectively a mirror problem. > > I use distrib-coffee which is usually well synchronized. > I just checked with Sophie's website: urpmi-debuginfo-install is there with > the version 8.2 > > I just checked distrib-coffee. The version is now 8.2 > > I try again, after syncing my own mirror. (In reply to Georges Eckenschwiller from comment #5) > In fact, it's my synchronization with rsync that is kidding. > I redid using ftp. Now it's OK. > thanks again Thanks for the feedback :-) So there wasn't a bug Status:
UNCONFIRMED =>
RESOLVED |