Control: tags -1 pending
On 5/11/24 12:31 PM, Santiago Vila wrote:
--- debian/libnetcdf19t64.symbols (libnetcdf19t64_4.9.2_amd64)
+++ dpkg-gensymbolsbQjlfm 2024-05-08 16:50:08.612637064 +
@@ -2099,7 +2099,7 @@
showopenobjects@Base 4.6.2
simplenodematch@Base 4.3.3
On 2/26/24 7:40 AM, Alastair McKinstry wrote:
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
This transition is blocking many of the remaining packages rebuilt for
64-bit time_t.
The autopkgtest for slurm-wlm on i386 is blocking testing migration of
mpich:
Control: tags -1 upstream
Control: user debian-...@lists.debian.org
Control: usertag -1 hdf-4.3
On 4/25/24 7:35 PM, Bas Couwenberg wrote:
The buildlogs shows many instances of these:
/usr/bin/ld: cannot find -lNGctrans: No such file or directory
/usr/bin/ld: cannot find -lNGras: No such
Control: tags -1 upstream
Control: forwarded -1 https://github.com/patjoly/geo-gpx/issues/6
I've forwarded this issue upstream. Please followup there.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 4/9/24 5:47 PM, Sudip Mukherjee wrote:
dh_pdl fails with the error:
Quite unusual to see dh_pdl used without debhelper installed.
I guess you were just trying the command instead of using it to set the
dependencies for another package?
It will need a runtime dependency on
I've added architecture-is-little-endian to the build dependency in git
to make the lack of big endian support explicit.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 4/8/24 4:55 AM, wuruilong wrote:
gmt compiles incorrectly on loong64 architectures, the attached patch solves
the problem and is verified.
Thanks for the patch and forwarding it upstream, it's applied in git.
Kind Regards,
Bas
--
GPG Key ID:
On 4/6/24 1:29 PM, Aurelien Jarno wrote:
On 2024-04-06 08:01, Sebastiaan Couwenberg wrote:
On 4/5/24 9:51 PM, Aurelien Jarno wrote:
For Bookworm given we can not fix the compiler easily, I propose to just
build icinga2 with -O1 on ppc64el. If you are fine with that option, I
can take care
On 4/5/24 9:51 PM, Aurelien Jarno wrote:
For Bookworm given we can not fix the compiler easily, I propose to just
build icinga2 with -O1 on ppc64el. If you are fine with that option, I
can take care of proposing a patch and submitting it to the stable
release team.
A patch for this is very
Control: tags -1 patch
On 4/4/24 6:22 PM, Sebastiaan Couwenberg wrote:
The FTBFS with HDF 4.3.0 is not fixed in 6.6.2.dfsg.1-5.
You need the attached patch to fix the error with HDF 4.3.0 by including
df.h instead of dfi.h.
The package then still FTBFS but due to dh_install:
dh_install
reopen 1068387
thanks
The FTBFS with HDF 4.3.0 is not fixed in 6.6.2.dfsg.1-5.
On 4/4/24 1:53 PM, Bas Couwenberg wrote:
Your package FTBFS while performing test rebuilds with HDF 4.3.20.
The attached debdiff contains changes to fix FTBFS issues unrelated to HDF
4.3.20.
This patch was
Control: tags -1 pending
On 4/4/24 12:54 PM, Bas Couwenberg wrote:
pyhdf/hdfext_wrap.c:3845:10: fatal error: hdfi.h: No such file or directory
3845 | #include "hdfi.h" /* declares int32, float32, etc */
| ^~~~
This is fixed in git by including hdf.h instead.
Kind
Control: tags -1 confirmed
On 4/4/24 12:59 AM, Bastian Germann wrote:
Please update to the latest upstream version. 4.3.0 has the following
changelog entry, which I would like to see in the Debian package:
That's not available where the other releases are and used by uscan:
Control: tags -1 upstream
Control: forwarded -1 https://github.com/PDLPorters/pdl/issues/469
On 4/1/24 10:47 PM, Sebastian Ramacher wrote:
https://buildd.debian.org/status/fetch.php?pkg=pdl=i386=1%3A2.086-1=1712002199=0
Salsa CI also caught that which triggered the upstream issue.
Kind
Control: tags -1 pending
On 4/1/24 11:19 AM, activityworkshop wrote:
I don't know if this is the best solution, but one way I found to allow access
is to add
a parameter to the launch command:
--add-opens=java.desktop/sun.awt=ALL-UNNAMED
This is implemented in git.
Kind Regards,
Bas
--
Control: merge 1067812 1067813
I already requested this a little earlier.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 3/25/24 10:20 AM, Vladimir Petko wrote:
I've made a small change to the patch: used -D_DEFAULT_SOURCE[1] to
avoid the deprecation warning. I have tested noble and sid build with
the attached patch.
Thanks for you patch improvements. I've managed to test my original
On 3/25/24 9:25 AM, Vladimir Petko wrote:
strlcpy and strlcat were introduced in glibc 2.38[1]. At the moment
Ubuntu noble has 2.39 and Debian unstable - 2.37.
Can you try the attached patch which patches CMakeLists.txt to add the
definition when strlcat/strlcpy are found on Linux?
Kind
On 3/25/24 6:31 AM, Vladimir Petko wrote:
The CMake checks if the function is present in the runtime library
(whether strlcpy() compiles), but the declaration in string.h itself
is guarded by __USE_MISC define.
On armhf in Ubuntu toolchain has -Werror=implicit-function-declaration
flag that
Control: tags -1 upstream moreinfo
On 3/25/24 3:39 AM, Vladimir Petko wrote:
In Ubuntu, the attached patch was applied to achieve the following:
* d/rules: define -D_BSD_SOURCE to ensure that strlcpy/strlcat functions
are declared (LP: #2058864).
That seems wrong.
CMakeLists.txt
Control: tags -1 pending
This is fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 3/19/24 5:04 PM, Sebastiaan Couwenberg wrote:
On 3/19/24 4:52 PM, Benjamin Drung wrote:
mapnik fails to build on Ubuntu with Python 3.12 due to the Scons
version in the package. I applied the attached patch to Ubuntu to use
the scons Debian package.
We moved away
On 3/19/24 4:52 PM, Benjamin Drung wrote:
mapnik fails to build on Ubuntu with Python 3.12 due to the Scons
version in the package. I applied the attached patch to Ubuntu to use
the scons Debian package.
We moved away from the scons package because that was broken (#936017).
Better to patch
Control: tags -1 pending
This is fixed in git with patch that adds the external function definitions.
Youhei, you marked the other patches as forwarded, how did you forward
those patches upstream? There is no upstream metadata or
Upstream-Contact which informs us of where to send patches.
The upstream repo shows no progress for two years,
affected packages should switch to alternatives.
Note that this packages was in the archive in the past:
https://tracker.debian.org/pkg/mercantile
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
reassign 1066727 src:python-pytest-lazy-fixture
found 1066727 python-pytest-lazy-fixture/0.6.3-2
affects 1066727 src:satpy
thanks
On 3/13/24 4:00 PM, Lucas Nussbaum wrote:
/usr/lib/python3/dist-packages/pytest_lazyfixture.py:105: in normalize_call
valtype_keys = set(getattr(callspec,
On 3/13/24 1:03 PM, Lucas Nussbaum wrote:
Preferences/MerkaartorPreferences.h:28:10: fatal error: proxy.h: No such file
or directory
28 | #include
| ^
Looks like libproxy-dev moved the header from /usr/include to
/usr/include/libproxy, we'll need to add that
Control: tags -1 pending
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 3/9/24 2:58 PM, Andrew Chadwick wrote:
I will continue reporting here, since this seems to be a Debian-
specific issue. I don't have much else to add, however. Happy to try
out fixes as they emerge.
Without upstream involvement, this issue will not get resolved.
Upstream doesn't built the
Control: tags -1 upstream
Control: forwarded -1 https://josm.openstreetmap.de/ticket/23540
This is a known issue since the update to 18969, the workaround is to
add the OSM Carto layer first, and then add the Bing layer.
As this is an upstream issue, you're encouraged to report it upstream
Control: tags -1 upstream
Control: forwarded -1 https://github.com/qgis/QGIS/issues/56756
From the build log:
Operation needs translation in
QgsCoordinateReferenceSystemUtils::translateProjection: mod_krovak
This is actually caused by PROJ 9.4.0 which introduced support for the
Modified
Control: tags -1 confirmed
On 3/5/24 4:44 PM, Adrian Bunk wrote:
https://buildd.debian.org/status/logs.php?pkg=qgis=3.34.4%2Bdfsg-3
Nothing we can do about that until the dependency chain has been rebuilt
for the ongoing t64 transition.
The builds prior to the t64 transition succeeded.
On 3/2/24 10:35 AM, Sebastian Ramacher wrote:
Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. Hence, the package was built with an old version of dpkg
not enabling the changes for the time_t
On 3/2/24 10:33 AM, Sebastian Ramacher wrote:
Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. Hence, the package was built with an old version of dpkg
not enabling the changes for the time_t
Control: tags -1 moreinfo
This sounds like the wrong package, because pyshp is maintained by the
Debian GIS team and won't be orphaned.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
Thanks for reporting this issue, it's fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 2/29/24 5:17 AM, Michael Hudson-Doyle wrote:
On Thu, 29 Feb 2024 at 17:11, Sebastiaan Couwenberg
wrote:
On 2/28/24 8:33 PM, Michael Hudson-Doyle wrote:
Hi, thanks for taking the NMU. Unfortunately it looks like you uploaded
just slightly too early and the package was built with 32 bit
On 2/28/24 8:33 PM, Michael Hudson-Doyle wrote:
Hi, thanks for taking the NMU. Unfortunately it looks like you uploaded
just slightly too early and the package was built with 32 bit time_t on ARM
That's odd, because gcc-13 and dpkg were already built & installed on
armel & armhf.
I also
Control: tags -1 pending
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
Thanks for the patch, it's applied in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 2/15/24 1:05 PM, Yuriy M. Kaminskiy wrote:
Trivial patch attached.
Like ogdi it does not apply cleanly as it targets the old version in
bookworm.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D
Control: tags -1 pending
On 2/15/24 1:26 PM, Yuriy M. Kaminskiy wrote:
Patch attached.
It does not apply cleanly as it targets the old version in bookworm
instead of what's in unstable.
Further changes to fix the lintian regressions were also committed in git.
Kind Regards,
Bas
--
GPG
Control: tags -1 pending.
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Keeping an eye on the Release Calendar can help too:
https://release.debian.org/release-calendar.ics
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
On 2/7/24 08:10, Mattias Ellert wrote:
Personally I think it would have made more sense to file these bugs
with minor or normal severity (since they are simply informational at
this stage) and then upgrade them to serious when the transition starts
(at which point they become RC).
I'd
Control: tags -1 upstream
Control: forwarded -1 https://sourceforge.net/p/saga-gis/bugs/317/
On 2/3/24 22:18, Sergio Durigan Junior wrote:
/<>/obj-x86_64-linux-gnu/src/saga_core/saga_api/saga_api_python/CMakeFiles/saga_api_python.dir/saga_apiPYTHON_wrap.cxx:
In function ‘PyObject*
On 1/31/24 13:29, Sebastiaan Couwenberg wrote:
This seems to use the wrong package name:
-Package: libgeos3.12.1
+Package: libgeos3.12.1t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libgeos-c1v5
+Replaces: libgeos3.12.1
+Breaks: libgeos3.12.1 (<< ${source:V
This seems to use the wrong package name:
-Package: libgeos3.12.1
+Package: libgeos3.12.1t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libgeos-c1v5
+Replaces: libgeos3.12.1
+Breaks: libgeos3.12.1 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Section: libs
If I
On 1/30/24 16:32, Lukas Märdian wrote:
Am 30.01.24 um 16:06 schrieb Sebastiaan Couwenberg:
On 1/30/24 15:57, Lukas Märdian wrote:
But please remember that this is meant to only hit experimental for
now, until the dpkg change lands in unstable.
So please don't upload it into unstable just yet
On 1/30/24 15:57, Lukas Märdian wrote:
But please remember that this is meant to only hit experimental for now,
until the dpkg change lands in unstable.
So please don't upload it into unstable just yet.
gdal will need to be rebuilt once fyba moves to unstable, how will these
transitions be
On 1/30/24 14:50, Lukas Märdian wrote:
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your
Control: tags -1 upstream moreinfo
On 1/18/24 12:55, Andre Castro Gonçalves de Oliveira de Castro wrote:
When I attempt to compress a NetCDF file with nccopy in Bookworm, an HDF error
is returned and an empty NetCDF is produced
If the same command + file are invoked by netcdf-bin:1:4.7.4-1
On 1/16/24 20:39, Jens Ritter wrote:
Upstream provides an update for PHP8.2-Errors
(https://www.nagvis.org/downloads/changelog/1.9.36)
That's already in testing & unstable, see:
https://tracker.debian.org/pkg/nagvis
Is there any way possible to include this changes ?
I doubt the
Control: tags -1 pending
The build dependency is dropped in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
plplot got removed from armhf, the severity of this issue could be
lowered to important to not have the package removed from testing.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 patch.
Thanks for the patch, it's applied in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
It turns out that plplot FTBFS on armhf: #1055228
I've requested partial removal of plplot and its rdeps from armhf since
a fix is unlikely in the short term:
- plplot (1059682)
# Broken Depends:
- munipack (1059683)
- psfex (1059684)
# Broken Build-Depends:
- coyote (1059685)
-
On 12/27/23 21:16, Sebastian Ramacher wrote:
On 2023-12-22 16:39:57 +0100, Bas Couwenberg wrote:
Shapelib 1.6.0 bumps the SONAME requiring a transition.
All rdeps built successfully with the new version as summarized below.
Please go ahead.
Thanks. shapelib (1.6.0-1) has been uploaded to
Control: tags -1 pending
On 12/20/23 18:06, Remus-Gabriel Chelu wrote:
Please find attached the Romanian translation of the «icinga2» file.
Add it git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Please also binNMU icinga2 in experimental.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Don't forget to raise the severity of the FTBFS bugreports to serious
now that the new boost-defaults is in unstable.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
This is fixed in the most recent upstream release, which unfortunately
FTBFS with python3.12 due to test failures.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 12/13/23 17:52, Rafael Laboissière wrote:
The bug has been forwarded upstream [1]. The upstream author of
octave-netcdf, John Donoghue, discovered that the problem is not caused
by the netcdf package nor by Octave itself, but is rather a problem
within the netcdf
tags 1056450 ftbfs
reassign 1058121 src:python-flasgger
found 1058121 python-flasgger/0.9.5+dfsg.2-3
affects 1058121 src:pytest-recording
merge 1056450 1058121
thanks
This is a duplicate of #1056450, reassigning to python-flasgger.
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41
Control: block -1 by 1058031
This seems to be fixed upstream:
https://github.com/mcfletch/pyopengl/issues/99
The pyopengl test suite fails because pygame FTBFS with Python 3.12
(#1058031) this likely also affects the autopkgtest.
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182
On 12/11/23 13:08, Francesco P. Lovergine wrote:
On Mon, Dec 11, 2023 at 12:30:24PM +0100, Sebastiaan Couwenberg wrote:
On 12/11/23 12:04, Francesco P. Lovergine wrote:
Unfortunately pyfuse3 is currently not more actively developedi (see
it's github page), I wonder if it makes sense
On 12/11/23 12:04, Francesco P. Lovergine wrote:
Unfortunately pyfuse3 is currently not more actively developedi (see
it's github page), I wonder if it makes sense maintaining it in Debian,
even considering the Python
life cycle which far from being slow and could render the whole thing
On 12/11/23 08:23, Jochen Sprickerhof wrote:
* Sebastiaan Couwenberg [2023-12-10 12:22]:
On Sun, 26 Nov 2023 10:06:32 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable
Control: tags -1 patch
On Sun, 26 Nov 2023 10:07:04 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:07:01 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:58 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:56 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:55 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:54 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:53 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:52 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:50 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:49 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch switches
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:48 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:47 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:46 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:44 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:43 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:42 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:40 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:39 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:35 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch switches
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:33 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:32 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:31 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:28 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:27 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:26 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:25 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:23 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch switches
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:21 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
Control: tags -1 patch
On Sun, 26 Nov 2023 10:06:20 + Matthias Klose wrote:
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
The attached patch
1 - 100 of 2322 matches
Mail list logo
