On Sun, Mar 17, 2024 at 06:53:34AM +0100, Emanuele Rocca wrote:
>
> On 2024-03-16 04:21, Emanuele Rocca wrote:
> > With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf
>
> And on armel too. Fixed armhf/armel packages uploaded.
>
> > Fabian: it seems that cargo's build-depend on git
On 2024-03-16 04:21, Emanuele Rocca wrote:
> With libcurl3t64-gnutls cargo can now be rebootstrapped on armhf
And on armel too. Fixed armhf/armel packages uploaded.
> Fabian: it seems that cargo's build-depend on git can be dropped? The
> package builds fine without, tests included.
I haven't
On Sat, 16 Mar 2024 at 14:29, Simon McVittie wrote:
> On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> > For example curl isn't building on armel/armhf now and numerous packages
> > that
> > depend of curl are not building on armel/armhf.
>
> I believe a maintainer upload or NMU
On Sat, 16 Mar 2024 at 15:37:20 +0100, Matthias Klose wrote:
> build gdb without libdebuginfo on the bootstrap archs for a while.
That's likely also good advice, but the cycle involving gdb isn't the
only one involving curl.
smcv
Hi!
On 2024-03-16 02:29, Simon McVittie wrote:
> On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> > For example curl isn't building on armel/armhf now and numerous packages
> > that
> > depend of curl are not building on armel/armhf.
>
> I believe a maintainer upload or NMU of
On 16.03.24 15:29, Simon McVittie wrote:
On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
For example curl isn't building on armel/armhf now and numerous packages that
depend of curl are not building on armel/armhf.
I believe a maintainer upload or NMU of #1066981 and #1066982
On Thu, 14 Mar 2024 at 22:03:57 -0700, Otto Kekäläinen wrote:
> For example curl isn't building on armel/armhf now and numerous packages that
> depend of curl are not building on armel/armhf.
I believe a maintainer upload or NMU of #1066981 and #1066982 would
now be enough to unblock curl, which
On Fri, Mar 15, 2024 at 08:16:40AM -0700, Otto Kekäläinen wrote:
> Hi!
>
> pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler
> kirjoitti:
>
> > On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> > > Hi!
> > >
> > > Is anyone perhaps planning to fix cargo?
> > >
> > > For example
On 2024-03-14 22:03 -0700, Otto Kekäläinen wrote:
> Hi!
>
> Is anyone perhaps planning to fix cargo?
Yes. We have been working on it this week (e.g. ema built cargo for armhf),
but that is not sufficient to unbung the
curl->stunnel4->python->crypography->cargo loop.
I tried building the patched
Hi!
pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler
kirjoitti:
> On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> > Hi!
> >
> > Is anyone perhaps planning to fix cargo?
> >
> > For example curl isn't building on armel/armhf now and numerous packages
> > that depend of curl
On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> Hi!
>
> Is anyone perhaps planning to fix cargo?
>
> For example curl isn't building on armel/armhf now and numerous packages
> that depend of curl are not building on armel/armhf.
>
> Thanks in advance to the person who steps
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages
that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
Andrea Bolognani, le mer. 13 mars 2024 18:03:40 +0100, a ecrit:
> On Wed, Mar 13, 2024 at 12:34:55PM +0100, Samuel Thibault wrote:
> > Simon McVittie, le mer. 13 mars 2024 10:52:35 +, a ecrit:
> > > 2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
> > >because its
On Wed, Mar 13, 2024 at 12:34:55PM +0100, Samuel Thibault wrote:
> Simon McVittie, le mer. 13 mars 2024 10:52:35 +, a ecrit:
> > 2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
> >because its major purpose this decade is running legacy 32-bit binaries,
> >a
Simon McVittie, le mer. 13 mars 2024 10:52:35 +, a ecrit:
> 2. i386 is 32-bit but has been excluded from the 64-bit time_t transition
>because its major purpose this decade is running legacy 32-bit binaries,
>a purpose that would no longer be possible if it broke ABI
>- non-release
On Tue, 12 Mar 2024 at 23:13:30 -0500, Steven Robbins wrote:
> I checked the build logs for cargo and noticed that most architectures have
> been built on the buildds. All release arches except armel & armhf. How is
> it that these two have build dep installability problems but others do not?
On Tuesday, March 12, 2024 1:24:25 A.M. CDT Steve Langasek wrote:
> The quickest fix for this based on what we've done in Ubuntu is:
>
> - unpack cargo and libstd-rust debs to the root via dpkg-deb -x
> - use equivs to mock up packages by these names with no dependencies and
> install those
>
On Mon, Mar 11, 2024 at 09:07:17PM -0500, Steven Robbins wrote:
> Peter convincingly argues (details in bug) that manual intervention is needed
> for package "cargo":
> On Sun, 10 Mar 2024 00:48:32 + Peter Michael Green
> wrote:
> > This will require manual intervention to resolve, either
Peter convincingly argues (details in bug) that manual intervention is needed
for package "cargo":
On Sun, 10 Mar 2024 00:48:32 + Peter Michael Green
wrote:
> This will require manual intervention to resolve, either through
> cross-building or through building manually in a hacked-up
19 matches
Mail list logo
