Dne 17. 07. 20 v 23:14 Aleksei Bavshin napsal(a):
Yes, that's something I already accepted.
The real question is how to do the change in f33 considering that f32
and f33 modules must be built from the same modulemd file. I only see
the ability to disable module stream build for f33.
Hmm, it seem
Petr and Daniel, thanks a lot for your replies.
I hope some of mentioned limitations could be reflected in the
modularity documentation. I read through most of it (including the
drafts for f33 change) and I don't feel that the consequences of adding
package to the module are clearly communicated.
On Fri, Jul 17, 2020 at 02:14:49PM -0700, Aleksei Bavshin wrote:
> The real question is how to do the change in f33 considering that f32
> and f33 modules must be built from the same modulemd file.
You wrap a %files section of the package you want to remove with a condition
based on the Fedora ver
On 7/17/20 1:50 PM, Daniel Mach wrote:
>
>
> Dne 17. 07. 20 v 14:15 Aleksei Bavshin napsal(a):
>> On 7/17/20 3:27 AM, Daniel Mach wrote:
>>> Dne 17. 07. 20 v 11:04 Miro Hrončok napsal(a):
If the package was part of the module during the release of Fedora 32,
dnf will see 2 versions/bu
Dne 17. 07. 20 v 14:15 Aleksei Bavshin napsal(a):
On 7/17/20 3:27 AM, Daniel Mach wrote:
Dne 17. 07. 20 v 11:04 Miro Hrončok napsal(a):
If the package was part of the module during the release of Fedora 32,
dnf will see 2 versions/builds of the module-stream:
- the one that existed during
On 7/17/20 3:27 AM, Daniel Mach wrote:
> Dne 17. 07. 20 v 11:04 Miro Hrončok napsal(a):
>> If the package was part of the module during the release of Fedora 32,
>> dnf will see 2 versions/builds of the module-stream:
>>
>> - the one that existed during the release (containing the package)
>> -
Dne 17. 07. 20 v 11:04 Miro Hrončok napsal(a):
On 17. 07. 20 6:47, Aleksei Bavshin wrote:
In an optimistic case I'd like to believe that once the package is
removed from the modulemd file and a new module update is published, the
override magic hacked into dnf would stop masking package from
non
On 17. 07. 20 6:47, Aleksei Bavshin wrote:
In an optimistic case I'd like to believe that once the package is
removed from the modulemd file and a new module update is published, the
override magic hacked into dnf would stop masking package from
non-modular repository. NEVRA would be the only fac
Hi,
I'm considering dropping some packages from sway:rolling modulemd
definition, however I don't clearly understand what would be the
resulting upgrade behavior.
Let's assume that the module is already enabled and all the packages are
installed in the user's system. Also, the module was containi
