From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <aris@altlinux.org>
Message-ID: <3137c85ebfe6e33866e56fefee15d463649c3d65.camel@altlinux.org>
From: Yuri Sedunov <aris@altlinux.org>
To: devel@lists.altlinux.org
Date: Tue, 22 Dec 2020 12:41:51 +0300
In-Reply-To: <236b5a67-8b82-3d92-a762-9b79bf44744f@basealt.ru>
References: <girar.task.263623.1.1@gyle.mskdc.altlinux.org>
 <girar.task.263623.2.3@gyle.mskdc.altlinux.org>
 <20201218153847.GB531956@glebfm.cloud.tilaa.com>
 <CA+qzenn_owkA3aE+CpastOp32k70T6evPzip8W5c67wnNcc0Bw@mail.gmail.com>
 <20201221113408.GA8443@altlinux.org>
 <b7b6d17f-3afb-551a-97e4-839bb54f2bbe@basealt.ru>
 <176897aad18.2846.7fa2a2f3bb6a924ec61a71903b1e5144@gmail.com>
 <CAPQ_kbK-aYV46GHo0renA8XRLmUZ3TwQaaN2qEgW5KfhGwJ3UQ@mail.gmail.com>
 <236b5a67-8b82-3d92-a762-9b79bf44744f@basealt.ru>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.2-alt1 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [devel] I: glibc 2.32 && sisyphus snapshot publication skip
X-BeenThere: devel@lists.altlinux.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ALT Linux Team development discussions <devel@lists.altlinux.org>
List-Id: ALT Linux Team development discussions <devel.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/options/devel>,
 <mailto:devel-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/devel>
List-Post: <mailto:devel@lists.altlinux.org>
List-Help: <mailto:devel-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/devel>,
 <mailto:devel-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Dec 2020 09:41:52 -0000
Archived-At: <http://lore.altlinux.org/devel/3137c85ebfe6e33866e56fefee15d463649c3d65.camel@altlinux.org/>
List-Archive: <http://lore.altlinux.org/devel/>
List-Post: <mailto:devel@altlinux.org>

В Вт, 22/12/2020 в 12:10 +0300, Anton Farygin пишет:
> 
> Патчи всё-таки лучше фиксировать в bugzilla, как и ошибки.
> 
> Если это было нужно сделать в libcap, то отправьте изменение,
> пожалуйста.

Проблема появилась в этой libcap-ng:

* Mon Nov 23 2020 Anton Farygin <rider@altlinux.ru> 0.8.1-alt1
- 0.8.1

С ней отвалился gnome-keyring. Благо, апстрим уже к тому времени
выпустил исправление.

commit ebc7bc9efacc17049e54da8d96a4a29943621113
Author: Steve Grubb <sgrubb@redhat.com>
Date:   Fri Nov 20 11:52:14 2020 -0500

    Update libcap-ng capability handling
    
There is a change in libcap-ng-0.8.1 that causes gnome-keyring to not
work correctly. The capng_apply function now returns an error if it
cannot change the bounding set. Previously this was ignored. Which
means now gnome-keyring exits when it shouldn't.
    
The new patch adds troubleshooting info to the error messages. And it
checks to see if we have CAP_SETPCAP. If we do not, then we cannot
change the bounding set and just set capabilities. On the setuid side,
it now drops the bounding set and clears any supplemental groups that
may be left over as an accident.


-- 
Yuri N. Sedunov