On Mon, Feb 06, 2023 at 07:56:50AM -0800, Gordon Messmer wrote:
> On 2023-02-06 07:27, Richard W.M. Jones wrote:
> > Why was this line added?
> >
> > + Requires: (fedora-release > 38-0.23 if fedora-release)
> >
> > I suppose it's related to this change in fedora-release:
> >
> >
On 2023-02-06 07:27, Richard W.M. Jones wrote:
Why was this line added?
+ Requires: (fedora-release > 38-0.23 if fedora-release)
I suppose it's related to this change in fedora-release:
https://src.fedoraproject.org/rpms/fedora-release/c/096fc7da49de5655db7aad17057e32191f2afe59?branch=rawhide
So I think related to this thread, libvirt is now uninstallable in
Rawhide:
DEBUG util.py:443: Error:
DEBUG util.py:443: Problem: problem with installed package
fedora-release-38-0.23.noarch
DEBUG util.py:443:- package
iscsi-initiator-utils-6.2.1.4-8.git2a8f9d8.fc38.x86_64 requires
On Sun, Jan 22, 2023 at 02:48:31PM -0800, Gordon Messmer wrote:
> On 2023-01-22 14:35, Gordon Messmer wrote:
> > What do I misunderstand about systemd presets?
>
> ... actually, the systemd presets look like they *don't* need to be
> adjusted. I reverted the change I thought the presets needed,
On Fr, 20.01.23 14:04, Colin Walters (walt...@verbum.org) wrote:
>
>
> On Thu, Jan 19, 2023, at 11:53 AM, Gordon Messmer wrote:
> > On 2023-01-19 00:55, Lennart Poettering wrote:
> >>
> >> What you could do is split up the problem: have iscsi-starter.service
> >> or so, that is separate from the
On 2023-01-22 14:35, Gordon Messmer wrote:
What do I misunderstand about systemd presets?
... actually, the systemd presets look like they *don't* need to be
adjusted. I reverted the change I thought the presets needed, removed
the packages, reinstalled, and iscsi-starter ended up enabled.
On 2023-01-22 10:14, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jan 19, 2023 at 01:48:16PM -0800, Gordon Messmer wrote:
On 2023-01-19 00:55, Lennart Poettering wrote:
hat you could do is split up the problem: have iscsi-starter.service
or so, that is separate from the iscsi.service main
(replying here to avoid multiple emails)
On Thu, Jan 19, 2023 at 01:48:16PM -0800, Gordon Messmer wrote:
> On 2023-01-19 00:55, Lennart Poettering wrote:
> > hat you could do is split up the problem: have iscsi-starter.service
> > or so, that is separate from the iscsi.service main service.
I
On Thu, Jan 19, 2023 at 2:32 PM Gordon Messmer wrote:
>
> On 2023-01-19 09:48, Daniel P. Berrangé wrote:
> > The idea is that an application will put a dep on the
> > specific libvirt-daemon-driver-XXX that its functionality
> > requires. If Boxes requires storage APIs, then add a
> > Requires:
On Thu, Jan 19, 2023 at 11:32:24AM -0800, Gordon Messmer wrote:
> On 2023-01-19 09:48, Daniel P. Berrangé wrote:
> > The idea is that an application will put a dep on the
> > specific libvirt-daemon-driver-XXX that its functionality
> > requires. If Boxes requires storage APIs, then add a
> >
On Thu, Jan 19, 2023, at 11:53 AM, Gordon Messmer wrote:
> On 2023-01-19 00:55, Lennart Poettering wrote:
>>
>> What you could do is split up the problem: have iscsi-starter.service
>> or so, that is separate from the iscsi.service main service. The
>> former's job would be to scan if iscsi
On 2023-01-19 00:55, Lennart Poettering wrote:
hat you could do is split up the problem: have iscsi-starter.service
or so, that is separate from the iscsi.service main service.
If I'm not mistaken, this approach would also probably need approval by
FESCo, since it'd involve reverting the
On 2023-01-19 09:48, Daniel P. Berrangé wrote:
The idea is that an application will put a dep on the
specific libvirt-daemon-driver-XXX that its functionality
requires. If Boxes requires storage APIs, then add a
Requires: libvirt-daemon-driver-storage-core, along with
any of the storage backends
On Thu, Jan 19, 2023 at 09:40:24AM -0800, Gordon Messmer wrote:
> On 2023-01-19 09:07, Daniel P. Berrange wrote:
> > berrange commented on the pull-request: `Permit an installation of only
> > core storage drivers.` that you are following:
> > ``
> > THis isn't really required. If someone wants
On 2023-01-19 09:07, Daniel P. Berrange wrote:
berrange commented on the pull-request: `Permit an installation of only core
storage drivers.` that you are following:
``
THis isn't really required. If someone wants to have a fully minimal install of
QEMU/KVM, then install
On 2023-01-19 09:07, Daniel P. Berrange wrote:
berrange commented on the pull-request: `Permit an installation of only core
storage drivers.` that you are following:
``
THis isn't really required. If someone wants to have a fully minimal install of
QEMU/KVM, then install
On 2023-01-19 08:57, Lennart Poettering wrote:
On Do, 19.01.23 08:53, Gordon Messmer (gordon.mess...@gmail.com) wrote:
Something like that was suggested last year, and Colin Walters objected, for
what that's worth.
have a link?
Last year's thread is here:
On Do, 19.01.23 08:53, Gordon Messmer (gordon.mess...@gmail.com) wrote:
> On 2023-01-19 00:55, Lennart Poettering wrote:
> >
> > What you could do is split up the problem: have iscsi-starter.service
> > or so, that is separate from the iscsi.service main service. The
> > former's job would be to
On 2023-01-19 00:55, Lennart Poettering wrote:
What you could do is split up the problem: have iscsi-starter.service
or so, that is separate from the iscsi.service main service. The
former's job would be to scan if iscsi volumes are configured. If it
finds configured ones, it would then issue
On 2023-01-19 01:25, Daniel P. Berrangé wrote:
The libvirt packaging is already modular. The 'libvirt-daemon-driver-storage'
package is intended to bring in/all/ storage backends libvirt supports. To
avoid that, it is possible to depend on 'libvirt-daemon-drive-storage-core'
instead which pulls
On Wed, Jan 18, 2023 at 10:19:24AM -0800, Gordon Messmer wrote:
> (apologies for the long-ish message, but I'd like to save people the trouble
> of re-reading a year-old very long email thread)
>
> Early last year there was a thread on this list (Re: "Is
> NetworkManager-wait-online.service
On Mi, 18.01.23 10:19, Gordon Messmer (gordon.mess...@gmail.com) wrote:
> There was also discussion of disabling the service by default and using a
> generator to enable the service, and Lennart thought this was the best
> solution. I started work to add a simple generator, but the documentation
On Wed, Jan 18 2023 at 08:27:02 PM +0100, Fabio Valentini
wrote:
Suggests are useful for the case where multiple packages (let's say
packages A and B) provide "foo", a package C depends on something that
provides "foo" (i.e. works with both A and B), but C prefers A over B
if neither of them
On 2023-01-18 11:20, Michael Catanzaro wrote:
Several people suggested using a weak dependency (Suggests:) on the
iscsi driver, but I don't think that would solve the problem for most
users because weak dependencies are installed by default and nothing
really communicates to users that unless
On 2023-01-18 11:20, Michael Catanzaro wrote:
No, Suggests basically does nothing. See this table here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/WeakDependencies/
Recommends and Supplements are real dependencies that are installed
automatically but which you can opt out
On Wed, Jan 18, 2023 at 8:20 PM Michael Catanzaro wrote:
>
> On Wed, Jan 18 2023 at 10:19:24 AM -0800, Gordon Messmer
> wrote:
> > Several people suggested using a weak dependency (Suggests:) on the
> > iscsi driver, but I don't think that would solve the problem for most
> > users because weak
On Wed, Jan 18 2023 at 10:19:24 AM -0800, Gordon Messmer
wrote:
Several people suggested using a weak dependency (Suggests:) on the
iscsi driver, but I don't think that would solve the problem for most
users because weak dependencies are installed by default and nothing
really communicates to
(apologies for the long-ish message, but I'd like to save people the
trouble of re-reading a year-old very long email thread)
Early last year there was a thread on this list (Re: "Is
NetworkManager-wait-online.service necessary by default?") in which
maintainers discussed the issue of boot
28 matches
Mail list logo
