Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

HI Georges,

Thanks a lot.

I think all we have to do now is to wait for 5 days.

Yours Dirk

On 16.02.24 08:48, Georges Khaznadar wrote:

Dirk Hünniger a écrit :

chromium-sandbox [!armel !mips64el !s390x],

Done.

Best regards,   Georges.

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Georges Khaznadar]

Dirk Hünniger a écrit :
> chromium-sandbox [!armel !mips64el !s390x],

Done.

Best regards,   Georges.



signature.asc
Description: PGP signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Georges,

I forgot to metion that that the line 52 (chromium-sandbox) should be 
change in the same manner as line 51. So it should look like:


chromium-sandbox [!armel !mips64el !s390x],

Yours Dirk

On 15.02.24 16:03, Paul Gevers wrote:

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on how to do that. 
Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] 
https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Paul, Georges

thanks a lot Paul for explanation on the syntax. Georges, could you 
please follow the instruction given below.


Yours Dirk

On 15.02.24 16:03, Paul Gevers wrote:

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on how to do that. 
Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] 
https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 15-02-2024 15:56, Dirk Hünniger wrote:
So could you Paul please post some information on 
how to do that. Maybe an example.


See [1] after the first example. Replace [2] with
 chromium [!armel !mips64el !s390x],

Paul

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
[2] https://sources.debian.org/src/mediawiki2latex/8.7-2/debian/control/#L51



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi,

If I have the choice, I would go for the second solution. So tell the 
system to build on all architectures and remove the runtime dependency 
to chromium on s390x armel and mips64el . I think mediawiki2latex can 
still be used in a practical way even if chromium is not available. For 
many years mediawiki2latex was used without any option to use chromium 
any way. I am not sure if Georges knows the syntax to add such an 
architecture qualified depends on chromium. I didn't find any out in a 
quick internet search. So could you Paul please post some information on 
how to do that. Maybe an example.


Yours Dirk

On 15.02.24 15:33, Paul Gevers wrote:

Hi,

On 15-02-2024 08:40, Dirk Hünniger wrote:
So it still wants to build on s390x armel and mips64el. Possibly its 
not possible to drop support for an architecture that once was 
supported.


This is not the solution *I* had in mind. I was thinking about just 
adding an architecture qualified depends on chromium, not only build 
on the non-chromium architectures. If you want to continue the current 
route, instead of hardcoding the architectures, I would add a 
*build*-depends on chromium to prevent building on architectures where 
it's not available. Then the package automatically builds on those 
once chromium becomes available.


Once an architecture builds successfully, it requires actions from 
ftp-master to remove the binaries. So, $(reportbug ftp.debian.org) if 
the architectures are fully unsupported.


So possible we need to tell the system that it can still build on all 
architectures, but the the dependency to chromium is only needed on 
all architectures but s390x armel and mips64el


That's what I had in mind indeed.

Paul

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 15-02-2024 08:40, Dirk Hünniger wrote:
So it still wants to build on s390x armel and mips64el. Possibly its not 
possible to drop support for an architecture that once was supported.


This is not the solution *I* had in mind. I was thinking about just 
adding an architecture qualified depends on chromium, not only build on 
the non-chromium architectures. If you want to continue the current 
route, instead of hardcoding the architectures, I would add a 
*build*-depends on chromium to prevent building on architectures where 
it's not available. Then the package automatically builds on those once 
chromium becomes available.


Once an architecture builds successfully, it requires actions from 
ftp-master to remove the binaries. So, $(reportbug ftp.debian.org) if 
the architectures are fully unsupported.


So possible we need to tell the system that it can still build on all 
architectures, but the the dependency to chromium is only needed on all 
architectures but  s390x armel and mips64el


That's what I had in mind indeed.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

HI Georges, Paul,

thank you for uploading the package. Unfortunately the system still says

https://qa.debian.org/excuses.php?package=mediawiki2latex

 * Issues preventing migration:
 o missing build on armel
   

 o missing build on mips64el
   

 o missing build on s390x
   

 o arch:armel not built yet, autopkgtest delayed there
 o arch:s390x not built yet, autopkgtest delayed there
 o Too young, only 0 of 5 days old

So it still wants to build on s390x armel and mips64el. Possibly its not 
possible to drop support for an architecture that once was supported.


So possible we need to tell the system that it can still build on all 
architectures, but the the dependency to chromium is only needed on all 
architectures but  s390x armel and mips64el



Yours Dirk

On 14.02.24 17:01, Dirk Hünniger wrote:

Hi,

Ok.

So if I understood correctly all that has to be done is to add an 
architecture qualifier. And the person who has can do it is Georges. 
So I herewith ask him to do so.


Yours Dirk

On 14.02.24 16:58, Paul Gevers wrote:

Hi,

On 14-02-2024 16:53, Dirk Hünniger wrote:
If it helps to change the dependency to chromium and 
chromium-sandbox from Depends to Recommends I would like to ask 
Georges to do so.


If you think the Depends is best, make it conditional on the 
architecture, because ideally also Recommends can be installed (so 
would benefit from the architecture qualifier).


Paul

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi,

Ok.

So if I understood correctly all that has to be done is to add an 
architecture qualifier. And the person who has can do it is Georges. So 
I herewith ask him to do so.


Yours Dirk

On 14.02.24 16:58, Paul Gevers wrote:

Hi,

On 14-02-2024 16:53, Dirk Hünniger wrote:
If it helps to change the dependency to chromium and chromium-sandbox 
from Depends to Recommends I would like to ask Georges to do so.


If you think the Depends is best, make it conditional on the 
architecture, because ideally also Recommends can be installed (so 
would benefit from the architecture qualifier).


Paul

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 14-02-2024 16:53, Dirk Hünniger wrote:
If it helps to change the dependency to chromium and chromium-sandbox 
from Depends to Recommends I would like to ask Georges to do so.


If you think the Depends is best, make it conditional on the 
architecture, because ideally also Recommends can be installed (so would 
benefit from the architecture qualifier).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Paul,

thank you for the explanation. So the dependency on chromium is the 
problem on these architectures.


Chromium is used to render tables in tables to pdf if command line 
option -a is given.


Otherwise Chromium is not used.

If it helps to change the dependency to chromium and chromium-sandbox 
from Depends to Recommends I would like to ask Georges to do so.


Yours Dirk

On 14.02.24 16:47, Paul Gevers wrote:

Hi,

On 14-02-2024 14:27, Georges Khaznadar wrote:
At the same time, 
https://buildd.debian.org/status/package.php?p=mediawiki2latex

says that the package could be installed,


I understand the confusing but the word "installed" on buildd.d.o 
means something else than that you can install the binaries. It means 
that the packages were incorporated (installed) into the archive.



so its runtime dependencies
are correct, on architectures: amd64, arm64, armel, armhf, i386, 
mips64el,

ppc64el, riscv64, s390x, alpha, hurd-i386, ia64, ppc64, sparc64.


Maybe you can try to install the binaries in a clean environment (I've 
done so, pasted below).


Paul

root@autopkgtest-lxc-vtalsf:/tmp/autopkgtest-lxc.c47fu43n/downtmp/build.Nel/src# 
apt install mediawiki2latex

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:
 mediawiki2latex : Depends: chromium but it is not installable
   Depends: chromium-sandbox but it is not installable
   Recommends: calibre but it is not going to be 
installed
   Recommends: latex2rtf but it is not going to be 
installed
   Recommends: libreoffice but it is not going to be 
installed

E: Unable to correct problems, you have held broken packages.

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Hi,

On 14-02-2024 14:27, Georges Khaznadar wrote:

At the same time, https://buildd.debian.org/status/package.php?p=mediawiki2latex
says that the package could be installed,


I understand the confusing but the word "installed" on buildd.d.o means 
something else than that you can install the binaries. It means that the 
packages were incorporated (installed) into the archive.



so its runtime dependencies
are correct, on architectures: amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x, alpha, hurd-i386, ia64, ppc64, sparc64.


Maybe you can try to install the binaries in a clean environment (I've 
done so, pasted below).


Paul

root@autopkgtest-lxc-vtalsf:/tmp/autopkgtest-lxc.c47fu43n/downtmp/build.Nel/src# 
apt install mediawiki2latex

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:
 mediawiki2latex : Depends: chromium but it is not installable
   Depends: chromium-sandbox but it is not installable
   Recommends: calibre but it is not going to be installed
   Recommends: latex2rtf but it is not going to be 
installed
   Recommends: libreoffice but it is not going to be 
installed

E: Unable to correct problems, you have held broken packages.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Georges,

I think its a good idea to wait for 24 hours. I am not sure if I will be 
available during the next few weeks. So just take the decisions you 
consider useful and don't bother about me.


Yours Dirk

On 14.02.24 14:27, Georges Khaznadar wrote:

Hello Paul, Dirk,

Dirk Hünniger a écrit :

https://qa.debian.org/excuses.php?package=mediawiki2latex
says:

Issues preventing migration:

  * mediawiki2latex/armel has unsatisfiable dependency
  * mediawiki2latex/mips64el has unsatisfiable dependency
  * mediawiki2latex/s390x has unsatisfiable dependency

At the same time, https://buildd.debian.org/status/package.php?p=mediawiki2latex
says that the package could be installed, so its runtime dependencies
are correct, on architectures: amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x, alpha, hurd-i386, ia64, ppc64, sparc64.

I have no precise idea about this misbehavior, unfortunately.
However the excuses page tells that the package is 5 days old (needing 5
days), maybe we should wait 24 hours longer ?

If the migrations keeps failing, I can make some trivial change and make
another source upload.

Best regards,   Georges.

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Georges Khaznadar]

Hello Paul, Dirk,

Dirk Hünniger a écrit :
> https://qa.debian.org/excuses.php?package=mediawiki2latex
> says:
> 
> Issues preventing migration:
> 
>  * mediawiki2latex/armel has unsatisfiable dependency
>  * mediawiki2latex/mips64el has unsatisfiable dependency
>  * mediawiki2latex/s390x has unsatisfiable dependency

At the same time, https://buildd.debian.org/status/package.php?p=mediawiki2latex
says that the package could be installed, so its runtime dependencies
are correct, on architectures: amd64, arm64, armel, armhf, i386, mips64el,
ppc64el, riscv64, s390x, alpha, hurd-i386, ia64, ppc64, sparc64.

I have no precise idea about this misbehavior, unfortunately.
However the excuses page tells that the package is 5 days old (needing 5
days), maybe we should wait 24 hours longer ?

If the migrations keeps failing, I can make some trivial change and make
another source upload.

Best regards,   Georges.



signature.asc
Description: PGP signature

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Dirk Hünniger]

Hi Paul, Georges,

This site

https://qa.debian.org/excuses.php?package=mediawiki2latex

says:

Issues preventing migration:

 * mediawiki2latex/armel has unsatisfiable dependency
 * mediawiki2latex/mips64el has unsatisfiable dependency
 * mediawiki2latex/s390x has unsatisfiable dependency

So I think its a problem in the packages I depend on and thus cannot fix 
myself.


What is even more strange is that this site

https://buildd.debian.org/status/package.php?p=mediawiki2latex

says that is it installed on armel misp64el and s390x.

Happy to hear about you explanations.

Yours Dirk

On 13.02.24 20:08, Paul Gevers wrote:

Source: mediawiki2latex
Version: 8.0-1
Severity: serious
Control: close -1 8.7-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between 
testing and unstable for more than 30 days as having a Release 
Critical bug in testing [1]. Your package src:mediawiki2latex has been 
trying to migrate for 31 days [2]. Hence, I am filing this bug. The 
version can't be installed on armel, mips64el and s390x while the 
package builds on those architectures.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot 
be fixed via unstable. Additionally, blocked packages can have impact 
on other packages, which makes preparing for the release more 
difficult. Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer 
affect testing. I have also tagged this bug to only affect sid and 
trixie, so it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=mediawiki2latex

Bug#1063864: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

[Paul Gevers]

Source: mediawiki2latex
Version: 8.0-1
Severity: serious
Control: close -1 8.7-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:mediawiki2latex has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version can't be 
installed on armel, mips64el and s390x while the package builds on those 
architectures.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=mediawiki2latex



OpenPGP_signature.asc
Description: OpenPGP digital signature