Description of problem: When trying to build the Fedora Scientific 27 ISO (https://pagure.io/fork/amitksaha/fedora-kickstarts/blob/f27/f/fedora-live-scientific_kde.ks), I get: Problem 1: conflicting requests - nothing provides libm17n-core.so.0()(64bit) needed by emacs-1:25.3-3.fc27.x86_64 Version-Release number of selected component (if applicable): emacs-1:25.3-3.fc27.x86_64 How reproducible: Always Steps to Reproduce: $ sudo livecd-creator --verbose --config=fedora-live-scientific_kde.ks --fslabel=Fedora-LiveCD --cache=/var/cache/live Actual results: Nothing provides libm17n-core.so.0()(64bit) needed by emacs-1:25.3-3.fc26.x86_64 Expected results: emacs installation succeeds Additional info:
(In reply to Amit Saha from comment #0) > Description of problem: > > When trying to build the Fedora Scientific 27 ISO > (https://pagure.io/fork/amitksaha/fedora-kickstarts/blob/f27/f/fedora-live- > scientific_kde.ks), I get: > > Problem 1: conflicting requests > - nothing provides libm17n-core.so.0()(64bit) needed by > emacs-1:25.3-3.fc27.x86_64 That means that the library is not present on the system. It seems to be coming from the package 'm17n-lib'. Emacs has 'BuildRequires: m17n-lib-devel' in the spec file. I doubt that this is an Emacs problem. It looks like the dependencies were not correctly installed, which can possibly be a bug in dnf or it the livecd-creator. Or maybe the system was altered by other means.
This is not livecd-tools. This is the fedora-kde-common kickstart excluding all input methods. See: https://pagure.io/fedora-kickstarts/blob/master/f/fedora-kde-common.ks#_60
(In reply to Neal Gompa from comment #2) > This is not livecd-tools. This is the fedora-kde-common kickstart excluding > all input methods. > > See: > https://pagure.io/fedora-kickstarts/blob/master/f/fedora-kde-common.ks#_60 :-(
This may be a change in behavior of the live compose tools... I seem to recall that excluded items would still get pulled into the compose when/if anything explicitly depended on them. If that's no longer the case, we (kde-sig) ought to revisit the decision to omit that stuff.
Is there a way to override this in the fedora scientific kickstart? Or can I do something to help fix this?
https://pagure.io/fedora-kickstarts/pull-request/309 I didn't see that referenced here yet
(In reply to Rex Dieter from comment #4) > This may be a change in behavior of the live compose tools... I seem to > recall that excluded items would still get pulled into the compose when/if > anything explicitly depended on them. This was deliberately changed because it was the only way to reliably exclude weak dependencies: https://github.com/livecd-tools/livecd-tools/commit/617e737474fb17da0e266422367e56ec54516bec (Note that the OP is using livecd-creator, not livemedia-creator. AFAICT, this was not changed in Anaconda, which is what is used by livemedia-creator.) I find the new livecd-creator behavior very handy for Kannolo.
(In reply to Kevin Kofler from comment #7) > (In reply to Rex Dieter from comment #4) > > This may be a change in behavior of the live compose tools... I seem to > > recall that excluded items would still get pulled into the compose when/if > > anything explicitly depended on them. > > This was deliberately changed because it was the only way to reliably > exclude weak dependencies: > https://github.com/livecd-tools/livecd-tools/commit/ > 617e737474fb17da0e266422367e56ec54516bec > > (Note that the OP is using livecd-creator, not livemedia-creator. AFAICT, > this was not changed in Anaconda, which is what is used by > livemedia-creator.) > > I find the new livecd-creator behavior very handy for Kannolo. This behavior is slated to go into Anaconda too, I just have to rework it a bit for the feedback I got from the developers.
I think the right solution to get rid of the error would be to bring the optional -minimization.ks back: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/message/Q6R4QEKRHVXTVKOW7KWEYDZ2YS3XTXQV/
Long term possibly, short-term we need minimalistic fixes (or workarounds)
This is the minimalistic fix, it does not change the contents of the KDE Spin at all unlike your approach, it only fixes the Scientific Spin.
(In reply to Kevin Kofler from comment #9) > I think the right solution to get rid of the error would be to bring the > optional -minimization.ks back: > https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/ > message/Q6R4QEKRHVXTVKOW7KWEYDZ2YS3XTXQV/ +1. Thanks all for this.
(In reply to Rex Dieter from comment #10) > Long term possibly, short-term we need minimalistic fixes (or workarounds) This is still an issue. Would you please be able to take a look when you get a chance?
(In reply to Amit Saha from comment #13) > (In reply to Rex Dieter from comment #10) > > Long term possibly, short-term we need minimalistic fixes (or workarounds) > > This is still an issue. Would you please be able to take a look when you get > a chance? Alternatively, i have added the workaround to the scientific spin instead: https://pagure.io/fedora-kickstarts/pull-request/321 Could you please merge it?
Well, that will select ALL m17n* packages, not just those that would have been selected by default.
(In reply to Kevin Kofler from comment #15) > Well, that will select ALL m17n* packages, not just those that would have > been selected by default. That's OK for a workaround right? Alternatively, if you could suggest a way to find(In reply to Kevin Kofler from comment #7) > (In reply to Rex Dieter from comment #4) > > This may be a change in behavior of the live compose tools... I seem to > > recall that excluded items would still get pulled into the compose when/if > > anything explicitly depended on them. > > This was deliberately changed because it was the only way to reliably > exclude weak dependencies: > https://github.com/livecd-tools/livecd-tools/commit/ > 617e737474fb17da0e266422367e56ec54516bec > > (Note that the OP is using livecd-creator, not livemedia-creator. AFAICT, > this was not changed in Anaconda, which is what is used by > livemedia-creator.) Hence, the rawhide
(In reply to Amit Saha from comment #16) > (In reply to Kevin Kofler from comment #15) > > Well, that will select ALL m17n* packages, not just those that would have > > been selected by default. > > That's OK for a workaround right? Alternatively, if you could suggest a way > to find(In reply to Kevin Kofler from comment #7) > > (In reply to Rex Dieter from comment #4) > > > This may be a change in behavior of the live compose tools... I seem to > > > recall that excluded items would still get pulled into the compose when/if > > > anything explicitly depended on them. > > > > This was deliberately changed because it was the only way to reliably > > exclude weak dependencies: > > https://github.com/livecd-tools/livecd-tools/commit/ > > 617e737474fb17da0e266422367e56ec54516bec > > > > (Note that the OP is using livecd-creator, not livemedia-creator. AFAICT, > > this was not changed in Anaconda, which is what is used by > > livemedia-creator.) > > Hence, the rawhide Sorry. The rawhide builds are passing for the last two weeks. I am not sure what changed between f27 and rawhide since there were no changes to the scientific kickstart. If `livemedia-creator` behavior was pulling in m17n-lib-devel package required by emacs, it shouldn't have been a problem on F27 as well.
(In reply to Amit Saha from comment #14) > (In reply to Amit Saha from comment #13) > > (In reply to Rex Dieter from comment #10) > > > Long term possibly, short-term we need minimalistic fixes (or workarounds) > > > > This is still an issue. Would you please be able to take a look when you get > > a chance? > > Alternatively, i have added the workaround to the scientific spin instead: > https://pagure.io/fedora-kickstarts/pull-request/321 Cancelled this PR. I am going to switch to livemedia-creator for my testing. However, what is the long-term fix once we make livemedia-creator behavior same as livecd-creator?
(In reply to Amit Saha from comment #18) > (In reply to Amit Saha from comment #14) > > (In reply to Amit Saha from comment #13) > > > (In reply to Rex Dieter from comment #10) > > > > Long term possibly, short-term we need minimalistic fixes (or workarounds) > > > > > > This is still an issue. Would you please be able to take a look when you get > > > a chance? > > > > Alternatively, i have added the workaround to the scientific spin instead: > > https://pagure.io/fedora-kickstarts/pull-request/321 > > Cancelled this PR. I am going to switch to livemedia-creator for my testing. > > However, what is the long-term fix once we make livemedia-creator behavior > same as livecd-creator? And that would be: https://bugzilla.redhat.com/show_bug.cgi?id=1506888#c9 I think?
Yes. As I wrote there, the minimization really needs to be separate from the kde-base kickstart.
Looks like this is happening again: https://kojipkgs.fedoraproject.org//work/tasks/6315/24056315/livemedia-out.log which is weried, since the livemedia-creator version hasn't changed since the last successful build.
When using livemedia-creator, this logic is in Anaconda, not in livemedia-creator itself.
(In reply to Kevin Kofler from comment #22) > When using livemedia-creator, this logic is in Anaconda, not in > livemedia-creator itself. Ah, so perhaps https://bugzilla.redhat.com/show_bug.cgi?id=1506888#c8 - this change has been made in anaconda as well?
(In reply to Kevin Kofler from comment #20) > Yes. As I wrote there, the minimization really needs to be separate from the > kde-base kickstart. I created a PR for this: https://pagure.io/fedora-kickstarts/pull-request/326 Please take a look.
fedora kickstarts are tested with and work using livemedia-creator I would rather see you use the same supported tools used to compose Fedora. given that anaconda however deals with things just fine I would say that livecd-creator is doing something wrong here.
According to comment #21, this now also happens with livemedia-creator.
(In reply to Dennis Gilmore from comment #25) > fedora kickstarts are tested with and work using livemedia-creator I would > rather see you use the same supported tools used to compose Fedora. given > that anaconda however deals with things just fine I would say that > livecd-creator is doing something wrong here. Indeed, this is still an issue: https://koji.fedoraproject.org/koji/taskinfo?taskID=24271728 In addition, https://pagure.io/fedora-kickstarts/pull-request/326 is probably a fair change as well (additional context: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/message/Q6R4QEKRHVXTVKOW7KWEYDZ2YS3XTXQV/)
https://pagure.io/fedora-kickstarts/pull-request/326 has been pushed and that has fixed the Fedora Scientific builds.