On 01/20/2018 11:33 PM, notifications@fedoraproject.org wrote:
From 550dbc37e07290648dfa85a1dbb95bf65891c59e Mon Sep 17 00:00:00 2001 From: Björn Esserbesser82@fedoraproject.org Date: Jan 20 2018 22:06:51 +0000 Subject: Rebuilt for switch to libxcrypt
Why is this necessary?
If rebuilding is required anyway, we should add an explicit
BuildRequires: libcrypt-devel
and drop the dependency in glibc-devel. (I assumed that this was the plan all along.)
Thanks, Florian
On 01/21/2018 10:06 AM, Florian Weimer wrote:
On 01/20/2018 11:33 PM, notifications@fedoraproject.org wrote:
From 550dbc37e07290648dfa85a1dbb95bf65891c59e Mon Sep 17 00:00:00 2001 From: Björn Esserbesser82@fedoraproject.org Date: Jan 20 2018 22:06:51 +0000 Subject: Rebuilt for switch to libxcrypt
Why is this necessary?
If rebuilding is required anyway, we should add an explicit
BuildRequires: libcrypt-devel
and drop the dependency in glibc-devel. (I assumed that this was the plan all along.)
Ping?
The current dependencies prevent upgrading to rawhide:
Error: Problem 1: cannot install both glibc-2.26.9000-46.fc28.x86_64 and glibc-2.26.9000-41.fc28.x86_64 - package libcrypt-2.26.9000-41.fc28.x86_64 requires glibc(x86-64) = 2.26.9000-41.fc28, but none of the providers can be installed - cannot install the best update candidate for package glibc-2.26.9000-41.fc28.x86_64 - problem with installed package libcrypt-2.26.9000-41.fc28.x86_64 Problem 2: package glibc-2.26.9000-41.fc28.x86_64 requires glibc-langpack = 2.26.9000-41.fc28, but none of the providers can be installed - package libcrypt-2.26.9000-41.fc28.x86_64 requires glibc(x86-64) = 2.26.9000-41.fc28, but none of the providers can be installed - cannot install both glibc-all-langpacks-2.26.9000-46.fc28.x86_64 and glibc-all-langpacks-2.26.9000-41.fc28.x86_64 - cannot install the best update candidate for package libcrypt-2.26.9000-41.fc28.x86_64 - cannot install the best update candidate for package glibc-all-langpacks-2.26.9000-41.fc28.x86_64
I think we need fewer Requires: and use Conflicts: instead.
Thanks, Florian
Am Montag, den 22.01.2018, 10:55 +0100 schrieb Florian Weimer:
On 01/21/2018 10:06 AM, Florian Weimer wrote:
On 01/20/2018 11:33 PM, notifications@fedoraproject.org wrote:
From 550dbc37e07290648dfa85a1dbb95bf65891c59e Mon Sep 17 00:00:00 2001 From: Björn Esserbesser82@fedoraproject.org Date: Jan 20 2018 22:06:51 +0000 Subject: Rebuilt for switch to libxcrypt
Why is this necessary?
It was not strictly neccessary for any technical reason, but I wanted to estimate and fixup any possible fallout. It seemed there were some packages (including Python and systemd) failing, because they blindly assume `crypt()` is *always* defined in <unistd.h>. Some others fail because the still use `setkey()` / `encrypt()`. (e.g. claws-mail)
If rebuilding is required anyway, we should add an explicit
BuildRequires: libcrypt-devel
That is the next step I want to do after everything is fixed and there are no other regressions caused by libxcrypt. And of course removing the explicit dependencies from glibc afterwards.
Ping?
The current dependencies prevent upgrading to rawhide:
Error: Problem 1: cannot install both glibc-2.26.9000-46.fc28.x86_64 and glibc-2.26.9000-41.fc28.x86_64
- package libcrypt-2.26.9000-41.fc28.x86_64 requires glibc(x86-64)
= 2.26.9000-41.fc28, but none of the providers can be installed
- cannot install the best update candidate for package
glibc-2.26.9000-41.fc28.x86_64
- problem with installed package libcrypt-2.26.9000-41.fc28.x86_64
Problem 2: package glibc-2.26.9000-41.fc28.x86_64 requires glibc-langpack = 2.26.9000-41.fc28, but none of the providers can be installed
- package libcrypt-2.26.9000-41.fc28.x86_64 requires glibc(x86-64)
= 2.26.9000-41.fc28, but none of the providers can be installed
- cannot install both glibc-all-langpacks-2.26.9000-46.fc28.x86_64
and glibc-all-langpacks-2.26.9000-41.fc28.x86_64
- cannot install the best update candidate for package
libcrypt-2.26.9000-41.fc28.x86_64
- cannot install the best update candidate for package
glibc-all-langpacks-2.26.9000-41.fc28.x86_64
I think we need fewer Requires: and use Conflicts: instead.
That has been fixed in libxcrypt yesterday.
Cheers, Björn
-
Björn 'besser82' Esser -
Florian Weimer