Hi Marco,
On Thu, Apr 15, 2021 at 02:27:10PM +0200, Marco d'Itri wrote:
> On Apr 14, Paul Gevers wrote:
>
> > The patch looks sensible after reading the discussion in these bugs. Can
> > we have an upload soon to have exposure?
> Unless there are any objections I will do a libxcrypt upload in a
Hi,
On Fri, Mar 19, 2021 at 04:52:57PM +0100, Ivo De Decker wrote:
> > > I wonder if all this might be caused by the breaks from libcrypt1 (against
> > > libc6 (<< 2.29-4)). Is there a way to remove the breaks without causing
> > > issues? Maybe this is som
Hi,
On Fri, Mar 19, 2021 at 03:51:34PM +0100, Aurelien Jarno wrote:
> > However, in all of my tests, between the unpack of the new libc6 and
> > libcrypt1
> > only other unpacks where done, and no dpkg hooks where run. If you have a
> > way
> > to reproduce the upgrade where dpkg ran the hook in
Hi,
On Fri, Nov 20, 2020 at 01:44:50PM +0100, Alois Wohlschlager wrote:
> Am Freitag, den 20.11.2020, 09:13 + schrieb Niko Tyni:
> > I don't think this is related to the recent perl 5.30 -> 5.32
> > transition.
> > The report is about a buster -> bullseye upgrade, and perl in
> > bullseye
> >
Hi,
On Sat, Aug 30, 2014 at 09:20:49PM +0200, Sven Joachim wrote:
> The eglibc source package has been removed from unstable and testing two
> months ago, why are you still trying to build it?
The source is still in unstable (with 'Extra-Source-Only: yes'), because
something in unstable was built
5 matches
Mail list logo