On 6/9/24 9:56 AM, Antonio Valentino wrote:
If it is OK for you to have bpack in Debian GIS I kindly ask to create
the git repository and sponsor the initial upload.
Yes, that's fine.
Repo: https://salsa.debian.org/debian-gis-team/bpack
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4A
On 6/14/24 8:00 PM, Thorsten Alteholz wrote:
according to policy (5.2) the source package stanza should not have a
Description:
Policy doesn't specify that Source stanza cannot have a Description.
dpkg supports this since 1.19.0 as documented in deb-substvars(5).
See: https://bugs.debian.org
Control: fixed -1 mapnik/4.0.0~rc1+ds-1~exp1
On 6/16/24 2:48 PM, Lucas Nussbaum wrote:
c++ -o src/json/mapnik_json_feature_collection_grammar.o -c -std=c++14
-DU_USING_ICU_NAMESPACE=0 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-secur
Don't forget to push you tags.
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mail
On 6/16/24 11:39 PM, Thorsten Alteholz wrote:
On Fri, 14 Jun 2024, Sebastiaan Couwenberg wrote:
On 6/14/24 8:00 PM, Thorsten Alteholz wrote:
according to policy (5.2) the source package stanza should not have a
Description:
Policy doesn't specify that Source stanza cannot have a Descri
The netcd4-python autopkgtest jobs are failing because /tmp is not writable:
==
ERROR: runTest (test_unlimdim.UnlimdimTestCase.runTest)
testing unlimited dimensions
Control: tags -1 pending
On 6/18/24 11:39 AM, Helmut Grohne wrote:
* dh_installsystemd and dh_installudev revert to the aliased location.
This is already 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 6/20/24 6:51 PM, Jeremy Bícha wrote:
libsoup3 was released in late 2021. This is a major API bump from libsoup2.4.
This is already fixed in git:
https://salsa.debian.org/debian-gis-team/osm-gps-map/-/commit/d2224755698c9f57c18273601fe6239a0d290684
Kind Regards,
Repo: https://salsa.debian.org/debian-gis-team/pyogrio
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists
Testing migration is blocked by autopkgtest on s390x:
https://qa.debian.org/excuses.php?package=bpack
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mail
On 6/27/24 7:21 AM, Antonio Valentino wrote:
bpack cannot be installed on s390x because of missing dependencies.
Specifically python3-bitstruct is not available on that platform.
We may need to exclude s390x in the autopkgtest-pkg-pybuild.conf, i.e.:
architecture=!s390x
What is not clear to
Control: tags -1 upstream
Control: forwarded -1 https://gitlab.com/sfcgal/SFCGAL/-/issues/267
The issue has been forwarded upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
On 7/1/24 8:44 AM, Antonio Valentino wrote:
pysolid has changed build system so scikit-build-core + cmake and it is
now fully compatible with Python 3.12 (see #1069217).
Unfortunately now the reproducibility test fails because of the lintian
error tagged "file-references-package-build-path".
I've pushed a few commits the fix the formatting of the control and
copyright file to be consistent with our other packages.
The .dirs files are useless, you should remove them.
The upstream metadata is still the example template.
The watch file is not consistent with our other packages.
The
reopen 1069130
tags 1069130 - patch
tags 1069130 + trixie sid
tags 1074660 + upstream
merge 1069130 1074660
thanks
On 7/2/24 2:51 PM, Lucas Nussbaum wrote:
FileNotFoundError: [Errno 2] No such file or directory: 'mapnik-config'
The CMake build of Mapnik 4.0 no longer provides mapnik-config, only
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
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://
Control: tags -1 upstream
Control: forwarded -1 https://github.com/mapnik/mapnik/issues/4467
The issue has been forwarded upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
On 7/3/24 2:39 PM, Matthias Klose wrote:
In file included from /<>/src/command_export.hpp:34,
from /<>/src/commands.cpp:12:
/<>/include/rapidjson/document.h: In member function
‘rapidjson::GenericStringRef& rapidjson::GenericStringRef::operator=(const
Control: tags -1 upstream
Control: forwarded -1 https://github.com/shapely/shapely/issues/2081
The issue has been forwarded upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
__
Control: tags -1 pending
On 7/3/24 7:28 PM, Sebastiaan Couwenberg wrote:
The issue has been forwarded upstream.
This is now fixed in git thanks to a patch from Fedora linked in the
upstream issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D
Control: tags -1 upstream
Youhei,
Can you look into fixing these incompatible-pointer-types errors?
See: https://gcc.gnu.org/gcc-14/porting_to.html#incompatible-pointer-types
These are not covered by the existing gcc-14.patch which only addresses
the implicit-function-declaration issues.
Ki
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
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://
On 7/8/24 9:38 AM, Gianfranco Costamagna wrote:
Hello, the bug seems to have regressed due to new gcc/boost.
Mapnik 4.0.0-rc2 switched from boost:optional to std:optional which
broke the python-mapnik git snapshot in experimental which worked
correctly with Mapnik 4.0.0-rc1.
I crafted a new
On 7/11/24 8:29 AM, Matthias Klose wrote:
On 11.07.24 08:15, Sebastiaan Couwenberg wrote:
Version: 8.4.0~rc1-1~exp1
On 7/11/24 8:07 AM, Matthias Klose wrote:
there are (build-)dependency on the now removed python3-distutils.
Already fixed via #1065869.
please consider fixing it in
On 7/11/24 8:53 AM, Matthias Klose wrote:
On 11.07.24 08:43, Sebastiaan Couwenberg wrote:
On 7/11/24 8:29 AM, Matthias Klose wrote:
On 11.07.24 08:15, Sebastiaan Couwenberg wrote:
Version: 8.4.0~rc1-1~exp1
On 7/11/24 8:07 AM, Matthias Klose wrote:
there are (build-)dependency on the now
On 7/13/24 8:33 PM, Christian Fuchs wrote:
I would like to understand why PDAL was removed in Debian Bookworm:
* Was it lack of time to keep it supported, or for technical reasons,
or for other reasons?
https://tracker.debian.org/pkg/pdal; read the REMOVED from testing news
item https:/
The qgis build for unstable is stuck in maybe-succesful status, which
cannot be given-back. Can you resolve this?
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-
fixed 1077357 fiona/1.10~b2-1~exp1
close 1077357
tags 1074959 ftbfs
severity 1074959 serious
merge 1077357 1074959
thanks
This is a duplicate of #1074959.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_
If you intended for this to be rebuilt for GRASS 8.4.0 you forgot the
relevant changes for that.
See:
https://salsa.debian.org/debian-gis-team/qgis/-/commit/c907382ab8badbce79b709af2456e1cb53e48299
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 614
Control: severity -1 normal
Control: tags -1 moreinfo unreproducible
On 7/30/24 10:03 AM, Ceppo wrote:
I went through the log from `josm --debug --reset-preferences --skip-plugins`
but couldn't find anything useful. I attach it anyway, surely it is more
meaningful to you than to me.
That show
On 7/31/24 5:47 PM, Ceppo wrote:
I run josm from both JRE 17 and 21 as you asked, and had the same issue. I
couldn't find any significant difference in the respective logs (attached).
I installed and successfully run josm in a virtual machine with a fresh
unstable install, but I couldn't underst
On 7/31/24 11:47 PM, Ceppo wrote:
On Wed, Jul 31, 2024 at 08:07:49PM GMT, Sebastiaan Couwenberg wrote:
Compare the output of `josm --status-report` on both.
The only differences are:
1. the VM uses Gnome and my physical machine doesn't,
That's where you should looks for t
Control: tags -1 pending
On 8/2/24 12:17 AM, Alexandre Detiste wrote:
python3-six usage has been removed completely since 8.4.0-1
Fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_
On 8/3/24 12:06 PM, Antonio Valentino (@antonio.valentino) wrote:
=
debian/source/lintian-overrides
=
@@ -0,0 +1,2 @@
+# False positive: "cryptography" is imported instead.
+uses-deprecated-python-stdlib crypt (deprecated in
On 8/4/24 5:16 PM, Antonio Valentino wrote:
I think that the lintian rule has bee improved so hopefully we will not
need overrides for this kind of issues.
Yes, the recent commit [0] looks promising. Hopefully we won't have to
wait many months until the next lintian upload with the change incl
On 8/6/24 3:39 AM, wuruilong wrote:
Now, gmt still compiles incorrectly on loongarch, and the debian repositories
don't merge this patch. please merge the patch!
As mentioned before, it's merged in git:
https://salsa.debian.org/debian-gis-team/gmt/-/commit/d484ca01c0d6dca1afcbc28fda4aca0bdee3
Repo: https://salsa.debian.org/debian-gis-team/pygeofilter
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-l
Repo: https://salsa.debian.org/debian-gis-team/stream-zip
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-li
Control: fixed -1 netcdf/1:4.9.3~rc1-1~exp1
Hello, netcdf started FTBFS probably due to gcc-14 on armhf
This seems to be fixed in the new upstream release in experimental.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF
On 8/8/24 1:04 PM, Antonio Valentino wrote:
Il 06/08/24 20:23, Sebastiaan Couwenberg ha scritto:
Repo: https://salsa.debian.org/debian-gis-team/pygeofilter
Thanks a lot for creating the repository.
The package is now ready for review and upload.
Would you like to do it?
Yes, I'll have
On 8/8/24 1:04 PM, Antonio Valentino wrote:
The package is now ready for review and upload.
Why is 0001-Fix-compatibility-with-i386.patch not forwarded?
Your approach seems better than hardcoding the amd64 multiarch path as a
fallback, that's broken by design.
I've added an override for thi
On 8/9/24 9:27 AM, Antonio Valentino wrote:
The package is now ready in git.
Please feel free to review and upload when you have time.
Also added py3dist-overrides before sponsoring the upload.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50
Testing migration is blocked by autopkgtest failure on i386:
https://qa.debian.org/excuses.php?package=stream-zip
You may need to exclude i386 and possibly other 32-bit architectures if
those aren't supported. If the tests also fail on armel and armhf, you
can add architecture-is-64-bit to th
Control: tags -1 upstream pending
On 8/15/24 10:46 AM, Petter Reinholdtsen wrote:
Here is a patch to add Appstream metainfo XML announcing the hardware
handled by this package.
Thanks for the patch, it's applied in git and forwarded upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10A
On 8/31/24 11:04 AM, Paolo Greppi wrote:
Hi! I have rebuilt a few packages:
https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.12.0+ds-1-partial
with the upcoming doxygen 1.12.0+ds-1 I am preparing here:
You should upload the new doxygen to experimental, we can't easily reproduce
t
Control: tags -1 upstream
Control: forwarded -1 https://github.com/libgeos/geos/issues/1153
Control: severity -1 important
Thanks for reporting this issue, I've forwarded it upstream.
On 8/31/24 11:04 AM, Paolo Greppi wrote:
P.S. since just a handful of packages break, I plan to upload the newe
Control: tags -1 pending
On 9/5/24 4:57 PM, stefa...@debian.org wrote:
Please add a Build-Depends on python3-setuptools to your package, or migrate
the package's build system away from setuptools/distutils.
This is already the case in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88
Control: tags -1 upstream
Control: forwarded -1 https://github.com/pytroll/aggdraw/issues/101
Thanks for reporting this issue, I've forwarded it upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_
Control: tags -1 pending
Fix in git by adding openjfx to Depends like for the regular josm package.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing
Control: tags -1 fixed-upstream pending
This issue is already fixed upstream, the changes have been cherry-picked.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass
Control: tags -1 pending
As reported in the upstream issue, the
test_area_def_geocentric_resolution failure is not actually caused by
Shapely 2.0, but by PROJ 9.1.1.
A patch has been added to tune the tolerances to make the test succeed
with PROJ 9.1.1 too.
Kind Regards,
Bas
--
GPG Key
Control: tags -1 pending
Thanks for the patch, it's applied in git and forwarded upstream.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-
Antonio,
Upstream has release tags now, consider switching from PyPI tarballs to
GitHub tags.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing lis
On 12/17/22 17:43, Antonio Valentino wrote:
Il 17/12/22 15:30, Sebastiaan Couwenberg ha scritto:
Upstream has release tags now, consider switching from PyPI tarballs
to GitHub tags.
yes, I think that it is a good idea.
I have just update the d/watch file.
That makes d/source/options obsolete
On 12/22/22 09:19, Antonio Valentino wrote:
Il 20/12/22 20:40, Bas Couwenberg ha scritto:
Please remove satpy from s390x where it FTBFS due to test failures and
autopkgtest failures negatively other packages.
not sure to understand why you made this request.
Probably I'm missing something, s39
Why in /usr/bin/mintpy not installed anywhere?
dh_missing: warning: usr/bin/mintpy exists in debian/tmp but is not
installed to anywhere
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Testing migration is blocked by autopkgtest failure:
=== python3.10 ===
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.ftv99a1d/downtmp/build.iMG/src/tests/asc_desc2horz_vert.py",
line 12, in
from mintpy.asc_desc2horz_vert import asc_desc2horz_vert
File "/usr/lib/python
On 12/23/22 09:54, Antonio Valentino wrote:
It is strange because python3-h5py is indeed a dependency of mintpy but
in the autopkgtest log it is only listed as a suggested package.
The problem could be related to #1025575 [1], but I'm not 100% sure.
By the way I will workaround by adding python
Testing migration is still blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=mintpy
pyfftw is not available on all (release) achitectures:
https://buildd.debian.org/status/package.php?p=pyfftw
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 81
On 12/29/22 23:43, Antonio Valentino (@antonio.valentino) wrote:
- - - - -
fd81b17f by Antonio Valentino at 2022-12-29T21:45:46+00:00
New pylibtiff package for command line utilities
- - - - -
[...]
- - - - -
f8c5bd23 by Antonio Valentino at 2022-12-29T22:40:46+00:00
Set distribution to unstabl
On 12/30/22 09:28, Antonio Valentino wrote:
Il 30/12/22 07:01, Sebastiaan Couwenberg ha scritto:
On 12/29/22 23:43, Antonio Valentino (@antonio.valentino) wrote:
- - - - -
fd81b17f by Antonio Valentino at 2022-12-29T21:45:46+00:00
New pylibtiff package for command line utilities
Testing migration is blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=pylibtiff
Possibly caused by autodep8-python3 changes.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
__
Testing migration is blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=satpy
autodep8-python3 fails here too.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
__
On 1/2/23 19:33, Sebastiaan Couwenberg wrote:
Testing migration is blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=satpy
autodep8-python3 fails here too.
Correction, it's not autodep8-python3 which fails here, its the python3
test:
ModuleNotFoundErro
On 1/2/23 19:32, Sebastiaan Couwenberg wrote:
Testing migration is blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=pylibtiff
Possibly caused by autodep8-python3 changes.
I've pushed a fix to generate version.py with setuptools_scm.
Please consider enabling
On 1/2/23 19:35, Sebastiaan Couwenberg wrote:
On 1/2/23 19:33, Sebastiaan Couwenberg wrote:
Testing migration is blocked by autopkgtest failures:
https://qa.debian.org/excuses.php?package=satpy
autodep8-python3 fails here too.
Correction, it's not autodep8-python3 which fails here
On 1/3/23 10:10, Antonio Valentino wrote:
I'm fine with enabling CI but I cannot do it myself, I have no access to
the project settings on salsa.
In few minutes I will upload the new version of the package.
You don't need to change the repo config, CI/CD is enabled already you
only need to ad
Why did you not enable Salsa CI for this package with autopkgtests?
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-list
The testsuite fails on i386:
https://salsa.debian.org/debian-gis-team/flox/-/jobs/3765665
This is not a huge issue as arch:all packages are built on amd64, but it
may be something upstream wants to fix.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 40
Like flox, the testsuite fails on i386
https://salsa.debian.org/debian-gis-team/sarsen/-/jobs/3765793
This is not a huge issue as arch:all packages are built on amd64, but it
may be something upstream wants to fix.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182
On 1/8/23 18:31, Antonio Valentino wrote:
Il 08/01/23 18:21, Antonio Valentino ha scritto:
Il 08/01/23 16:51, Sebastiaan Couwenberg ha scritto:
The testsuite fails on i386:
https://salsa.debian.org/debian-gis-team/flox/-/jobs/3765665
This is not a huge issue as arch:all packages are built
On 1/9/23 23:02, Antonio Valentino (@antonio.valentino) wrote:
=
debian/tests/python3
=
@@ -1,6 +1,15 @@
#!/bin/sh
set -efu
+# Skip tests on problematic architectures
+ARCH="$(dpkg-architecture -qDEB_BUILD_ARCH)"
+
+i
On 1/14/23 13:57, Lucas Nussbaum wrote:
=== FAILURES ===
_ TestSuite.test_32bit _
self =
def test_32bit(self):
"""
SCENARIO: The sample format is 32bi
FYI: dask is installable in unstable again.
CI job has been retried and is looking good.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-g
Don't forget to push the tags.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.deb
On 1/18/23 07:40, Antonio Valentino wrote:
I plan to upload a new version of flox soon.
The v0.6.7 upstream release I presume?
Is it OK for you?
That's fine, flox (0.6.5-3) and sarsen (0.9.3+ds-2) have finally
migrated to testing.
Just be aware of the ongoing python3.11-default, numpy, a
Angelos,
You need to move the VCS elsewhere, e.g. the debian namespace on Salsa
if you intend to reintroduce the package in Debian, or your personal
namespace if you only intend to maintain it for OSGeoLive/UbuntuGIS.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 818
On 2/9/23 09:11, Paul Gevers wrote:
Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build
On 2/16/23 15:05, Paul Cochrane wrote:
On Thu, Feb 16, 2023 at 02:44:36PM +0100, Sebastiaan Couwenberg wrote:
I'm not sure if it's worth the effort to fix this issue in bullseye with a
stable update. Since you've already done the work to patch package in
bullseye, can you pre
On 2/17/23 23:08, Yuri Astrakhan wrote:
As reported at OSGeo/PROJ-data [1] and also found on stackexchange 5 years
ago [2], it seems it is not possible to install libproj9 in a
cross-compilation scenario:
[1] https://github.com/OSGeo/PROJ-data/issues/94
[2]
https://askubuntu.com/questions/997277
On 3/9/23 16:32, ǝɹʇʇɐʃǝ◖ xıʃǝɟ (@pantierra) wrote:
Added linitian override for long lines in provided source files.
very-long-line-length-in-source-file is a pedantic issue, only severity
info and higher need to be addressed. It's bad practice to add override
for pedantic and extra severity is
On 12/8/22 14:34, zhangdandan wrote:
I have added support for loongarch64 in libhdf4 source package.
The results of test-units(make check) all passed.
Please consider applying the attached patch.
HDF4 4.2.16 no longer has the architecture conditionals, this made your
loongarch.patch and simila
Control: tags -1 pending
On 4/11/23 09:37, bi...@debian.org wrote:
As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to
tags 1035235 wontfix
thanks
On 4/30/23 02:07, Sandro Tosi wrote:
Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages
Control: tags -1 moreinfo
On 5/8/23 02:07, Vagrant Cascadian wrote:
The attached patch fixes this by not touching these files during the
build process.
From shar(1):
"
-m, --no-timestamp
do not restore modification times.
Avoid generating 'touch' commands to restore the f
On 5/8/23 22:43, Vagrant Cascadian wrote:
On 2023-05-08, Sebastiaan Couwenberg wrote:
On 5/8/23 02:07, Vagrant Cascadian wrote:
The attached patch fixes this by not touching these files during the
build process.
From shar(1):
"
-m, --no-timestamp
do not restore modific
On 5/9/23 05:47, Sebastiaan Couwenberg wrote:
On 5/8/23 22:43, Vagrant Cascadian wrote:
On 2023-05-08, Sebastiaan Couwenberg wrote:
On 5/8/23 02:07, Vagrant Cascadian wrote:
The attached patch fixes this by not touching these files during the
build process.
From shar(1):
"
-m,
Hi Stephan,
Your bugreport came in just as I submitted #1035922 on your behalf. The
two bugreports have been merged.
As noted in #1035922, two more upstream commits are required to resolve
the regression, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035922#5
The next bullseye p
On 5/11/23 10:52, Sebastiaan Couwenberg wrote:
The next bullseye point release should include this fix, in the mean
your can downgrade to 3.1.1+dfsg-1.
The bullseye-pu bugreport: #1035924
The changes are available in git:
https://salsa.debian.org/debian-gis-team/postgis/-/commits/bullseye
Control: tags -1 pending
On 5/23/23 01:13, Andreas Beckmann wrote:
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m55.9s ERROR: FAIL: Broken symlinks:
/usr/share/man/man1/x-grass.1.gz -> grass.1.gz (grass-core)
The manpages seem to have moved to gr
Control: tags -1 pending
Thanks for reporting this issue, it's fixed in git by dropping the symlink.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
___
Pkg-grass-devel mailing
On 5/28/23 23:38, Vagrant Cascadian wrote:
On 2023-05-08, Vagrant Cascadian wrote:
On 2023-05-09, Sebastiaan Couwenberg wrote:
On 5/9/23 05:47, Sebastiaan Couwenberg wrote:
On 5/8/23 22:43, Vagrant Cascadian wrote:
On 2023-05-08, Sebastiaan Couwenberg wrote:
On 5/8/23 02:07, Vagrant
On 5/29/23 06:13, Vagrant Cascadian wrote:
On 2023-05-29, Sebastiaan Couwenberg wrote:
On 5/28/23 23:38, Vagrant Cascadian wrote:
That said, I think it really is the touch commands in debian/datumgrids*
as touch's timestamp modification is timezone dependent in many cases...
The att
Control: tags -1 - moreinfo + pending
On 5/30/23 00:35, Vagrant Cascadian wrote:
On 2023-05-29, Sebastiaan Couwenberg wrote:
On 5/29/23 06:13, Vagrant Cascadian wrote:
On 2023-05-29, Sebastiaan Couwenberg wrote:
Does TZ=UTC also work when set in the environment? If so, that could be
passed
Control: tags -1 pending
On 5/30/23 02:57, Vagrant Cascadian wrote:
The RPATH contains the build path resulting in different buildid and
various other differences:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proj.html
The attached patch modifies debian/rules to pass
-
On 6/9/23 08:52, Antonio Valentino (@antonio.valentino) wrote:
de321d71 by Antonio Valentino at 2023-06-09T06:49:14+00:00
Set distribution to unstable
This is a bit premature, the bookworm release is not until tomorrow.
Also don't forget to push the tags.
Kind Regards,
Bas
--
GPG Key ID: 4
On 6/10/23 11:15, Antonio Valentino wrote:
Il 09/06/23 09:04, Sebastiaan Couwenberg ha scritto:
On 6/9/23 08:52, Antonio Valentino (@antonio.valentino) wrote:
de321d71 by Antonio Valentino at 2023-06-09T06:49:14+00:00
Set distribution to unstable
This is a bit premature, the bookworm release
On 6/11/23 15:43, Antonio Valentino wrote:
Right now I'm keeping debelper-compat (=12).
Do we already have a plan for updating it?
Debian bullseye and bookworm have debhelper 13.
Ubuntu bionic has debhelper 11 (and 13 in backports), but it goes EOL
this month.
Ubuntu focal has debhelper 12
On 6/11/23 16:12, Antonio Valentino wrote:
Il 11/06/23 16:04, Sebastiaan Couwenberg ha scritto:
On 6/11/23 15:43, Antonio Valentino wrote:
Right now I'm keeping debelper-compat (=12).
Do we already have a plan for updating it?
Debian bullseye and bookworm have debhelper 13.
Ubuntu b
On 6/12/23 23:23, Rainer Dorsch wrote:
I see that routino 3.4 contains an important bugfix for its users. According to
Andrew serveral users from Germany contacted him for this issue. Is there a
chance to get 3.4 into backports for bookworm?
Yes, once it migrates to testing.
https://qa.debian
1 - 100 of 996 matches
Mail list logo
