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
Hi,
because life isn't hard enough as it is: When /bin is a symlink to
usr/bin, and I install two packages, where one installs /bin/foo and the
other installs /usr/bin/foo, then, if both are installed in the same
dpkg invocation, the contents of the first package end up being
installed, while
Package: wnpp
Severity: wishlist
Owner: Bernhard Dick
X-Debbugs-Cc: debian-devel@lists.debian.org, bernh...@bdick.de
* Package name: vaultwarden
Version : 1.30.5
Upstream Contact: Daniel García
* URL : https://github.com/dani-garcia/vaultwarden
* License : AG
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-observabilityclient
Version : 0.1.1
Upstream Contact: OpenStack Foundation
* URL : https://infrawatch.github.io/documentation/
* License :
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 of
On 16.03.24 18:41, Steven Robbins wrote:
This recent transition has really illuminated how little I know of the dark
corners of Debian infrastructure...
Some packages (e.g. libcdk5/experimental) aren't buildable on the armel/armhf
because the build-deps don't install, and in particular:
The fol
This recent transition has really illuminated how little I know of the dark
corners of Debian infrastructure...
Some packages (e.g. libcdk5/experimental) aren't buildable on the armel/armhf
because the build-deps don't install, and in particular:
The following packages have unmet dependencies:
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 #10
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 wou
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 w
Hi zigo,
On 16-03-2024 12:31 a.m., Thomas Goirand wrote:
But when the AUTORM period was announced as reduced, I thought
like it was probably a bad call, and that the previous AUTORM was
aggressive enough.
I'm not aware that we reduced autoremoval times in recent history. Are
you maybe confus
12 matches
Mail list logo
