On 3/15/24 07:14, Andreas Tille wrote:
I simply remove all those testing removal warnings in my
mailbox to cope with this and by doing so I'm probably missing real
issues I should rather care about.
I know what you're talking about: anyone that maintains a lot of
packages always receive waves
On 3/15/24 21:52, Paul Gevers wrote:
Hi,
Disclaimer: exception only valid while the time_t transition is ongoing.
On 15-03-2024 6:15 a.m., Steve Langasek wrote:
Migration to testing is largely out of control of the maintainers at this
point, it's very much dependent on folks rebootstrapping ar
Hi,
Disclaimer: exception only valid while the time_t transition is ongoing.
On 15-03-2024 6:15 a.m., Steve Langasek wrote:
Migration to testing is largely out of control of the maintainers at this
point, it's very much dependent on folks rebootstrapping armel and armhf
against the new library
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 c
On Thu, Mar 14, 2024 at 08:42:14PM -0700, Steve Langasek wrote:
> On Thu, Mar 14, 2024 at 10:47:02PM +0100, Micha Lenk wrote:
> > The time_t transition seems to be stalled due to issues on armel/armhf
> > architecture. My understanding is, as long as this transition isn't over,
> > uploaders of af
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 are
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 up
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-momepy
Version : 0.7.0
Upstream Contact: Martin Fleischmann
* URL : https://github.com/pysal/momepy
* License : BSD-3-clause
Programming
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-contextily
Version : 1.5.2
Upstream Contact: Dani Arribas-Bel
* URL : https://github.com/geopandas/contextily
* License : BSD-3-clause
P
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-mercantile
Version : 1.2.1
Upstream Contact: Sean Gillies
* URL : https://github.com/mapbox/mercantile
* License : BSD-3-clause
Programm
Hi Andreas,
* Andreas Tille [2024-03-15 07:31]:
Hi,
thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one
package of the R pkg team is affected by some strange linker issue
#1066409 r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or directory
which boils down to[1]
g++ -st
12 matches
Mail list logo