I had occasion to install many packages from f31 today. The large majority of them installed successfully, but the packages in the attached file didn't. There are 411 of them, which is few for as many packages as there are in Fedora.
I'm curious why the same mechanism that dnf uses on install on a pc couldn't be used in the build process. When someone submits a build, wouldn't it be possible to see if it would break the existing state, and ask the submitter if they would like to build the dependencies with their new package? Too complex?
On Sun, 2019-06-09 at 17:54 -0700, stan via test wrote:
I had occasion to install many packages from f31 today. The large majority of them installed successfully, but the packages in the attached file didn't. There are 411 of them, which is few for as many packages as there are in Fedora.
I'm curious why the same mechanism that dnf uses on install on a pc couldn't be used in the build process. When someone submits a build, wouldn't it be possible to see if it would break the existing state, and ask the submitter if they would like to build the dependencies with their new package? Too complex?
Can you send results with `dnf install -b yourpackages ` please ?
to have some clues .
Thanks
On Mon, 10 Jun 2019 02:20:50 +0100 Sérgio Basto sergio@serjux.com wrote:
On Sun, 2019-06-09 at 17:54 -0700, stan via test wrote:
I had occasion to install many packages from f31 today. The large majority of them installed successfully, but the packages in the attached file didn't. There are 411 of them, which is few for as many packages as there are in Fedora.
I'm curious why the same mechanism that dnf uses on install on a pc couldn't be used in the build process. When someone submits a build, wouldn't it be possible to see if it would break the existing state, and ask the submitter if they would like to build the dependencies with their new package? Too complex?
Can you send results with `dnf install -b yourpackages ` please ?
to have some clues .
It's a bash file that runs dnf. The files are listed inside. All you have to do is edit the command line to change -y --skip-broken to -y -b, and you can run it using bash and see the results on your system if you have rawhide installed. That puts you in control of the output.
I've also attached the file.
Thanks , I don't have rawhide installed
for example : - nothing provides jchardet needed by eclipse-m2e-core- 1.11.0-1.fc31.noarch
and jchardet was retired on 2019-04-01 [1] which is bad
[1] https://src.fedoraproject.org/rpms/jchardet/commits/master
On Sun, 2019-06-09 at 19:45 -0700, stan via test wrote:
On Mon, 10 Jun 2019 02:20:50 +0100 Sérgio Basto sergio@serjux.com wrote:
On Sun, 2019-06-09 at 17:54 -0700, stan via test wrote:
I had occasion to install many packages from f31 today. The large majority of them installed successfully, but the packages in the attached file didn't. There are 411 of them, which is few for as many packages as there are in Fedora.
I'm curious why the same mechanism that dnf uses on install on a pc couldn't be used in the build process. When someone submits a build, wouldn't it be possible to see if it would break the existing state, and ask the submitter if they would like to build the dependencies with their new package? Too complex?
Can you send results with `dnf install -b yourpackages ` please ?
to have some clues .
It's a bash file that runs dnf. The files are listed inside. All you have to do is edit the command line to change -y --skip-broken to -y -b, and you can run it using bash and see the results on your system if you have rawhide installed. That puts you in control of the output.
I've also attached the file. _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
On Mon, 2019-06-10 at 03:54 +0100, Sérgio Basto wrote:
Thanks , I don't have rawhide installed
for example : - nothing provides jchardet needed by eclipse-m2e-core- 1.11.0-1.fc31.noarch
and jchardet was retired on 2019-04-01 [1] which is bad
[1] https://src.fedoraproject.org/rpms/jchardet/commits/master
I've been told that this is actually how the process is 'meant to work' - when packages are retired due to being orphaned for too long, their dependencies are not automatically retired at the same time. The idea is apparently that things downstream might be able to adjust their dependencies to keep working, so we shouldn't retire them right away.
On Sun, 2019-06-09 at 17:54 -0700, stan via test wrote:
I had occasion to install many packages from f31 today. The large majority of them installed successfully, but the packages in the attached file didn't. There are 411 of them, which is few for as many packages as there are in Fedora.
I'm curious why the same mechanism that dnf uses on install on a pc couldn't be used in the build process. When someone submits a build, wouldn't it be possible to see if it would break the existing state, and ask the submitter if they would like to build the dependencies with their new package? Too complex?
In a nutshell...yes.
This is what https://pagure.io/rpmdeplint is for, but it's a very hard problem to actually fully solve, and there are enough problems with false negatives that we've never been in a position to make it a gating check.
On Mon, 10 Jun 2019 09:40:20 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
In a nutshell...yes.
This is what https://pagure.io/rpmdeplint is for, but it's a very hard problem to actually fully solve, and there are enough problems with false negatives that we've never been in a position to make it a gating check.
Thanks, that makes sense.