Bug#1061432: Add OrangePI PC Plus to sunxi platforms

2024-01-24 Thread Лухнов Андрей Олегович
Vagrant,

I, eventually, will be able to perform basic tests, at least as long as our org 
is producing Orange PC Plus-based devices.
I should have included contact info in the debian/targets.mk file, sorry.

Here is my contact address: Andrey Loukhnov 

Best,
Andrey

P.S.: my previous mail did not make it to the BTS for unknown reason, sorry for 
spam if both will arrive someday ;)

- Original Message -
From: "Vagrant Cascadian" 
To: "Андрей Лухнов" , 1061...@bugs.debian.org
Sent: Wednesday, January 24, 2024 8:27:25 PM
Subject: Re: Bug#1061432: Add OrangePI PC Plus to sunxi platforms

On 2024-01-24, Лухнов Андрей Олегович wrote:
> please consider adding OrangePI PC Plus to sunxi platforms. Changes
> are trivial, proposed platform is buildable without errors and tested
> bootable on target hardware.
>
> Required changes attached.

Would you or someone else be willing to regularly test new versions of
u-boot as they land in the archive?

  https://wiki.debian.org/U-boot/Status

I prefer to list at least one person with contact information in the
debian/targets.mk file so we know who to ask if problems arise.

Because it supports over a thousand boards, board-specific regressions
are unfortunately all too common in u-boot and it is helpful to find
those regressions early.

live well,
  vagrant



Bug#1061432: Add OrangePI PC Plus to sunxi platforms

2024-01-24 Thread Лухнов Андрей Олегович
Source: u-boot 
Severity: minor 
Tags: patch

Dear Maintainer,

please consider adding OrangePI PC Plus to sunxi platforms. Changes are 
trivial, proposed platform is buildable without errors and tested bootable on 
target hardware.

Required changes attached.

Thank you,
Andrey



0001-debian-targets.mk-add-orangepi_pc_plus-to-sunxi-plat.patch
Description: application/mbox


Bug#1061431: Do not act on packages for subarchs excluded by build profiles

2024-01-24 Thread Лухнов Андрей Олегович
Source: u-boot 
Severity: normal
Tags: patch

Dear Maintaner,

I've noticed that while cross-building u-boot 2024.01+dfsg-1 for armhf on 
Debian Trixie amd64 with pkg.uboot.subarch.XXX or pkg.uboot.platform.YYY,
empty .deb packages are created for subarchs that were not selected.

I've improved debian/rules so, that:
1) makefile targets are not created for not selected subarchs
2) no actions are performed for packages of not selected subarchs while 
executing standard dh sequence, so empty packages are not created

Please find the proposed changes attached. I'd really love seeing them 
incorporated.

I'm open to discussion as the whole debian/rules + debian/targets.mk thing 
seemed a bit of a magic at the first sight. I hope, I understood everything 
correct and proposing appropriate changes.

Thank you in advance,
Andrey


P.S.: patch is created against 9434edeb of 
https://salsa.debian.org/debian/u-boot.git

0001-Do-not-act-on-packages-for-subarchs-excluded-by-buil.patch
Description: application/mbox


Bug#1061298: u-boot: refresh patches

2024-01-22 Thread Лухнов Андрей Олегович
Thanks for the prompt reply, Vagrant!

May be, I chose wrong wordings and mislead you a bit.

It happened so, that I applied patches one by one and observed following info:

```
# quilt push
Applying patch debian/patches/arndale/board-spl-rule.diff
patching file Makefile
Hunk #1 succeeded at 2056 (offset -52 lines).
```

or

```
Applying patch debian/patches/rockchip/rockchip-inno-usb.patch
patching file drivers/phy/rockchip/phy-rockchip-inno-usb2.c
Hunk #1 succeeded at 64 (offset 2 lines).
Hunk #2 succeeded at 108 (offset 14 lines).
Hunk #3 succeeded at 126 (offset 14 lines).
Hunk #4 succeeded at 142 (offset 14 lines).
Hunk #5 succeeded at 168 (offset 14 lines).
Hunk #6 succeeded at 312 (offset 82 lines).
```

So, I decided to issue `quilt refresh` for each patch, that has such reports.

I'm not a seasoned Debian maintainer, so sorry for the noise if those actions 
are unneeded. :)

I understand that patches still apply well, but they are already "not perfectly 
in place". So, it appears, the policy is to wait till they are not applicable 
with `--fuzz=0`.
Understood. Thank you for the clarification!

Andrey

- Original Message -
From: "Vagrant Cascadian" 
To: "Андрей Лухнов" , 1061...@bugs.debian.org
Sent: Monday, January 22, 2024 10:32:40 PM
Subject: Re: Bug#1061298: u-boot: refresh patches

On 2024-01-22, Лухнов Андрей Олегович wrote:
> I've quilt-refreshed patches in u-boot 2024.01+dfsg-1 to apply them
> without fuzzyness.
>
> Please find, ahem, a patch for that attached. :) (I'm not sure, if it
> is a correct method to propose a fix, though, or you could just run
> quilt refresh yourself)

Since the patches apply with "quilt push --fuzz=0 -a" I do not think
this is currently needed.

Is there something I am missing?

live well,
  vagrant



Bug#1061298: u-boot: refresh patches

2024-01-22 Thread Лухнов Андрей Олегович
Source: u-boot 
Severity: minor 
Tags: patch 
X-Debbugs-Cc: loukh...@lotes-tm.ru

Dear Maintainer,

I've quilt-refreshed patches in u-boot 2024.01+dfsg-1 to apply them without 
fuzzyness.

Please find, ahem, a patch for that attached. :) (I'm not sure, if it is a 
correct method to propose a fix, though, or you could just run quilt refresh 
yourself)


Best,
Andrey


0001-quilt-refresh-patches.patch
Description: application/mbox


Bug#1061057: clang-16 fails to install as build-dep during cross-build

2024-01-16 Thread Лухнов Андрей Олегович
Package: clang-16 
Severity: normal 

Dear Maintainer, 

the problem initially was described in # 1060887 but postgres maintainer told 
me, it's a clang problem. So, here I am. 


The minimal reproducible example of debian/control follows: 

Source: cross-deps-problem 
Build-Depends: debhelper (>= 13.3.4), postgresql-server-dev-16 
Section: libs 
Priority: optional 
Standards-Version: 4.3.0 

So I start with official debian:trixie docker image on amd64 host with the 
following commands: 

# dpkg --add-architecture armhf 
# apt-get update 
# apt-get dist-upgrade 
# apt-get -o APT::Get::Build-Dep-Automatic=yes -o Debug::pkgProblemResolver=yes 
build-dep --host-architecture=armhf -y . 

which yields: 

Note, using directory '.' to get the build dependencies 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Starting pkgProblemResolver with broken count: 1 
Starting 2 pkgProblemResolver with broken count: 1 
Investigating (0) clang-16:armhf < none -> 1:16.0.6-19 @un puN Ib > 
Broken clang-16:armhf Depends on binutils:armhf < none @un pH > 
Considering binutils:armhf 0 as a solution to clang-16:armhf 0 
Done 
Some packages could not be installed. This may mean that you have 
requested an impossible situation or if you are using the unstable 
distribution that some required packages have not yet been created 
or been moved out of Incoming. 
The following information may help to resolve the situation: 

The following packages have unmet dependencies: 
clang-16:armhf : Depends: binutils:armhf but it is not installable 
E: Unable to correct problems, you have held broken packages. 

Manual installation (i.e. apt-get install clang-16:armhf binutils:armhf) 
succeeds, but it does not help to resolve build-dep issue...

Worth to mention, it also happens in bookworm with clang-14 and bullseye with 
clang-11 (you can find apt diagnostics in #1060887 for that cases too) 

Please help me diagnose and resolve this issue at least in bookworm 

Best, 
Andrey



Bug#1060887: postgresql-server-dev-16 fails to install as build-dep during cross-build

2024-01-15 Thread Лухнов Андрей Олегович
Package: postgresql-server-dev-16 
Severity: normal 
X-Debbugs-Cc: loukh...@lotes-tm.ru 

Dear Maintainer, 

I have postgresql-server-dev-16 as a build dependency in my package, minimal 
debian/control file to reproduce the problem is as follows: 

Source: cross-deps-problem 
Build-Depends: debhelper (>= 13.3.4), 
postgresql-server-dev-16 
Section: libs 
Priority: optional 
Standards-Version: 4.3.0 

I'm using official debian:trixie docker image and issuing the following 
commands to prepare build: 

root@e93cc49d3bff:/code/dep-problem-tracking# dpkg --add-architecture armhf 
root@e93cc49d3bff:/code/dep-problem-tracking# apt-get update 
[ mailto:root@e93cc49d3bff:/code/dep-problem-tracking# | 
root@e93cc49d3bff:/code/dep-problem-tracking#  ] apt-get dist-upgrade 
root@e93cc49d3bff:/code/dep-problem-tracking# apt-get build-dep -aarmhf . 
Note, using directory '.' to get the build dependencies 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Some packages could not be installed. This may mean that you have 
requested an impossible situation or if you are using the unstable 
distribution that some required packages have not yet been created 
or been moved out of Incoming. 
The following information may help to resolve the situation: 

The following packages have unmet dependencies: 
clang-16:armhf : Depends: binutils:armhf but it is not installable 
E: Unable to correct problems, you have held broken packages. 

Full apt diagnostics follows: 

root@e93cc49d3bff:/code/dep-problem-tracking# apt-get -o 
APT::Get::Build-Dep-Automatic=yes -o Debug::pkgProblemResolver=yes build-dep 
--host-architecture=armhf -y . 
Note, using directory '.' to get the build dependencies 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Starting pkgProblemResolver with broken count: 1 
Starting 2 pkgProblemResolver with broken count: 1 
Investigating (0) clang-16:armhf < none -> 1:16.0.6-19 @un puN Ib > 
Broken clang-16:armhf Depends on binutils:armhf < none @un pH > 
Considering binutils:armhf 0 as a solution to clang-16:armhf 0 
Done 
Some packages could not be installed. This may mean that you have 
requested an impossible situation or if you are using the unstable 
distribution that some required packages have not yet been created 
or been moved out of Incoming. 
The following information may help to resolve the situation: 

The following packages have unmet dependencies: 
clang-16:armhf : Depends: binutils:armhf but it is not installable 
E: Unable to correct problems, you have held broken packages. 
root@e93cc49d3bff:/code/dep-problem-tracking# 

Despite that, if I issue `apt-get install postgresql-server-dev-16:armhf` 
command everythins resolves and installs just fine, but `apt-get build-dep 
-aarmhf .` still fails with the following (same) diagnostics: 

root@e93cc49d3bff:/code/dep-problem-tracking# apt-get -o 
APT::Get::Build-Dep-Automatic=yes -o Debug::pkgProblemResolver=yes build-dep 
--host-architecture=armhf -y . 
Note, using directory '.' to get the build dependencies 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Starting pkgProblemResolver with broken count: 1 
Starting 2 pkgProblemResolver with broken count: 1 
Investigating (0) clang-16:armhf < 1:16.0.6-19 @ii pK Ib > 
Broken clang-16:armhf Depends on binutils:armhf < 2.41.50.20231227-1 @ii pR > 
Considering binutils:armhf 0 as a solution to clang-16:armhf 2 
Added binutils:armhf to the remove list 
Investigating (1) clang-16:armhf < 1:16.0.6-19 @ii pK Ib > 
Broken clang-16:armhf Depends on binutils:armhf < 2.41.50.20231227-1 @ii pR > 
Considering binutils:armhf 2 as a solution to clang-16:armhf 2 
Done 
Some packages could not be installed. This may mean that you have 
requested an impossible situation or if you are using the unstable 
distribution that some required packages have not yet been created 
or been moved out of Incoming. 
The following information may help to resolve the situation: 

The following packages have unmet dependencies: 
clang-16:armhf : Depends: binutils:armhf but it is not installable 
E: Unable to correct problems, you have held broken packages. 

root@e93cc49d3bff:/code/dep-problem-tracking# apt-cache policy 
postgresql-server-dev-16:armhf 
postgresql-server-dev-16:armhf: 
Installed: 16.1-1 
Candidate: 16.1-1 
Version table: 
*** 16.1-1 500 
500 http://deb.debian.org/debian trixie/main armhf Packages 
100 /var/lib/dpkg/status 
root@e93cc49d3bff:/code/dep-problem-tracking# 

It is worth to mention, this issue also exists in earlier releases. I'm having 
similar issue with postgresql-server-dev-15 in bookworm, but it is failing with 
another dependencies: 

root@f4a15821be16:/code/dep-problem-tracking# cat /etc/debian_version 
12.4 
root@f4a15821be16:/code/dep-problem-tracking# apt-get build-dep -aarmhf . 
Note, using directory '.' to get the build dependencies 
Reading package 

Bug#942016: libopencv3.2-java is archtecture: all, but not M-A: foreign

2019-10-08 Thread Лухнов Андрей Олегович
Package: libopencv3.2-java
Version: 3.2.0+dfsg-6
Severity: important

Dear Maintainer,

for some reason libopencv3.2-java is archtecture: all, but not marked as M-A:
foreign.

this blocks cross-building of packages (or I'm doing something totally wrong).

My package (a private one) depends on libgstreamer-plugins-bad1.0-dev and
everything compiles just fine if I compile for native arch.

but during cross-compilation build-deps installation fails with the following:

The following packages have unmet dependencies:
 libgstreamer-plugins-bad1.0-dev:armel : Depends: libopencv-dev:armel (>=
2.3.0) but it is not going to be installed

which leads me to:

libopencv-dev:armel : Depends: libopencv3.2-java:armel (= 3.2.0+dfsg-6) but it
is not installable
   Recommends: opencv-data:armel but it is not installable

and...

E: Package 'libopencv3.2-java:armel' has no installation candidate

able to reproduce it on buster, bullseye and sid.

May be, it wasn't marked for a reason, but I haven't found it yet.
Any hints would be appreciated!

Best,
Andrey



Bug#916856: d-shlibs: d-devlibdeps fails in docker due to /etc/apt/apt.conf.d/docker-clean

2018-12-19 Thread Лухнов Андрей Олегович
Jonas,

apt is perfectly working inside that docker container.

And the contents of /etc/apt/apt.conf.d/docker-clean is as follows:

DPkg::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb 
/var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb 
/var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };

Dir::Cache::pkgcache "";
Dir::Cache::srcpkgcache "";

So, apt is not broken either.

Also, there is no "my tool" in this process - I was using standart devscripts.

I think, it worth to mention, that if I edit d-devlibdeps remove --no-generate 
flag from apt-cache, everything works fine.

At https://hub.docker.com/_/debian it reads as "Docker Official Images", so I 
thought, that debian image is provided by Debian team...

- Original Message -
From: "Jonas Smedegaard" 
To: "916856" <916...@bugs.debian.org>, "Андрей Лухнов" 
Sent: Wednesday, December 19, 2018 7:33:50 PM
Subject: Re: Bug#916856: d-shlibs: d-devlibdeps fails in docker due to 
/etc/apt/apt.conf.d/docker-clean

Hi Лухнов Андрей,

Quoting Лухнов Андрей Олегович (2018-12-19 16:29:49)
> sorry, missed to fill in the details..
> 
> while building pjproject inside official debian:9.6 container d-devlibdeps 
> failed.
> after some digging it appeared that apt is cleaning cache after each 
> invocation, which makes apt-cache --no-generate to fail.

Thanks for reporting - and for adding these additional notes.

d-shlibs require a properly working apt. That's not a bug in d-shlibs.

Seems to me your containerizing framework needs to ensure the 
environment is properly bootstrapped ahead of building packages.

I am not familiar with using containerizing frameworks for building 
packages so cannot tell if this is a bug in your tool or you needing to 
configure the framework differently.  If it is the former and your 
framework is packaged for Debian, then this bugreport should be 
reassigned to that other tool.  Otherwise unfortunately it is on you, 
and this bugreport should be closed.


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



Bug#916856: d-shlibs: d-devlibdeps fails in docker due to /etc/apt/apt.conf.d/docker-clean

2018-12-19 Thread Лухнов Андрей Олегович
sorry, missed to fill in the details..

while building pjproject inside official debian:9.6 container d-devlibdeps 
failed.
after some digging it appeared that apt is cleaning cache after each 
invocation, which makes apt-cache --no-generate to fail.

- Original Message -
From: "Андрей Лухнов" 
To: "Debian Bug Tracking System" 
Sent: Wednesday, December 19, 2018 6:26:20 PM
Subject: Bug#916856: d-shlibs: d-devlibdeps fails in docker due to 
/etc/apt/apt.conf.d/docker-clean

Package: d-shlibs
Version: 0.79
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.13.0-37-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages d-shlibs depends on:
ii  apt   1.4.8
ii  binutils  2.28-5

d-shlibs recommends no packages.

d-shlibs suggests no packages.

-- no debconf information