Bug#1042896: transition: armadillo

2023-08-30 Thread Kumar Appaiah
Dear Graham,

On Wed, Aug 30, 2023 at 07:35:46AM +, Graham Inggs wrote:
> 
> Please go ahead.

I just did a source-only upload. Will keep an eye on the buildds.

Thanks.

Kumar
-- 
Kumar Appaiah



Bug#1042896: transition: armadillo

2023-08-30 Thread Sebastiaan Couwenberg

Control: block -1 by 1028633

On 8/30/23 09:13, Kumar Appaiah wrote:

I could not build mlpack since the build failed, but I am sure it's
not due to pip. Here is the extract from the failed build log:

-- After much of the build
mkdir: cannot create directory '/usr/lib/python3.11/site-packages/':
Permission denied /usr/bin/python3: No module named pip
CMake Error at
/build/mlpack-4.1.0/src/mlpack/bindings/python/PythonInstall.cmake:23
(message):
   Error installing Python bindings!
Call Stack (most recent call first):
   src/mlpack/bindings/python/cmake_install.cmake:66 (include)
   src/mlpack/bindings/cmake_install.cmake:50 (include)
   src/mlpack/cmake_install.cmake:68 (include)
   cmake_install.cmake:55 (include)


That's a known issue: #1028633

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1042896: transition: armadillo

2023-08-30 Thread Graham Inggs
Control: tags -1 confirmed

Hi Kumar

On Wed, 30 Aug 2023 at 07:22, Kumar Appaiah  wrote:
> Thanks for the response. I have build the following packages
> successfully using the new Armadillo:
>
> gdal
> gnss-sdr
> phyx
> seer
> tvc

Great!

> I could not build mlpack since the build failed, but I am sure it's
> not due to pip. Here is the extract from the failed build log:

That's fine, mlpack has not been in testing for some time already.

Please go ahead.

Regards
Graham



Bug#1042896: transition: armadillo

2023-08-30 Thread Kumar Appaiah
Dear Graham,

On Sat, Aug 26, 2023 at 10:53:47AM +, Graham Inggs wrote:
> Hi Kumar
> 
> On Wed, 2 Aug 2023 at 13:48, Kumar Appaiah  wrote:
> > I have uploaded the new Armadillo to experimental. I would like your
> > permission to upload it to unstable. binNMUs should be sufficient for
> > the reverse dependencies.
> 
> Have you checked that all the reverse-build-dependencies build with
> the new version of armadillo?

Thanks for the response. I have build the following packages
successfully using the new Armadillo:

gdal
gnss-sdr
phyx
seer
tvc

I could not build mlpack since the build failed, but I am sure it's
not due to pip. Here is the extract from the failed build log:

-- After much of the build
mkdir: cannot create directory '/usr/lib/python3.11/site-packages/':
Permission denied /usr/bin/python3: No module named pip
CMake Error at
/build/mlpack-4.1.0/src/mlpack/bindings/python/PythonInstall.cmake:23
(message):
  Error installing Python bindings!
Call Stack (most recent call first):
  src/mlpack/bindings/python/cmake_install.cmake:66 (include)
  src/mlpack/bindings/cmake_install.cmake:50 (include)
  src/mlpack/cmake_install.cmake:68 (include)
  cmake_install.cmake:55 (include)

Please let me know if any other information is needed.

Thanks.

Kumar
  



Bug#1042896: transition: armadillo

2023-08-26 Thread Graham Inggs
Hi Kumar

On Wed, 2 Aug 2023 at 13:48, Kumar Appaiah  wrote:
> I have uploaded the new Armadillo to experimental. I would like your
> permission to upload it to unstable. binNMUs should be sufficient for
> the reverse dependencies.

Have you checked that all the reverse-build-dependencies build with
the new version of armadillo?

Regards
Graham



Bug#1042896: transition: armadillo

2023-08-02 Thread Kumar Appaiah
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: armadi...@packages.debian.org
Control: affects -1 + src:armadillo

Dear Release Team,

I have uploaded the new Armadillo to experimental. I would like your
permission to upload it to unstable. binNMUs should be sufficient for
the reverse dependencies.

Please let me know if you have any questions.

Thank you.

Kumar

Ben file:

title = "armadillo";
is_affected = .depends ~ "libarmadillo11" | .depends ~ "libarmadillo12";
is_good = .depends ~ "libarmadillo12";
is_bad = .depends ~ "libarmadillo11";