Dne 06. 04. 20 v 18:28 James Cassell napsal(a):
> My understanding of current policy is that it would not be permitted to have
> such a module in current fedora.
"is permitted in Fedora" vs. "is technically possible" are two different things.
Technical specification should think about layered app
On Thu, Apr 9, 2020, at 10:00 AM, Petr Pisar wrote:
> On Thu, Apr 09, 2020 at 12:05:07PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > if the module EOL is before a given Fedora version goes EOL, it should
> > never be proposed for installation in that Fedora version. In other words,
> > if foo:3.
On Thu, Apr 09, 2020 at 12:05:07PM +, Zbigniew Jędrzejewski-Szmek wrote:
> if the module EOL is before a given Fedora version goes EOL, it should
> never be proposed for installation in that Fedora version. In other words,
> if foo:3.15 stream has EOL of 1/4/2020, it should be shown in
> 'dnf m
On Mon, Apr 06, 2020 at 12:28:15PM -0400, James Cassell wrote:
> On Mon, Apr 6, 2020, at 12:05 PM, Petr Pisar wrote:
> > On Mon, Apr 06, 2020 at 03:02:02PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Mar 31, 2020 at 12:13:16PM +0200, Daniel Mach wrote:
> [snip]
> > > > Setting eol_date
On Mon, Apr 6, 2020, at 12:05 PM, Petr Pisar wrote:
> On Mon, Apr 06, 2020 at 03:02:02PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Mar 31, 2020 at 12:13:16PM +0200, Daniel Mach wrote:
[snip]
> > > Setting eol_date to the future allows informing a user about
> > > upcoming obsoleting ev
On Mon, Apr 06, 2020 at 03:02:02PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Mar 31, 2020 at 12:13:16PM +0200, Daniel Mach wrote:
> > >> # A string representing a Name of a module that is EOLed
> > >> # MANDATORY
> > >> module: nodejs
> > >>
> > >> # A string representing a Stream
On Tue, Mar 31, 2020 at 12:13:16PM +0200, Daniel Mach wrote:
> >> # A string representing a Name of a module that is EOLed
> >> # MANDATORY
> >> module: nodejs
> >>
> >> # A string representing a Stream of a module that is EOLed
> >> # MANDATORY
> >> stream: 11
> >>
> >> # A string re
Dne 31. 03. 20 v 10:14 Zbigniew Jędrzejewski-Szmek napsal(a):
On Tue, Mar 31, 2020 at 09:25:45AM +0200, Vít Ondruch wrote:
Wouldn't be easier to use something we already have? E.g.
https://src.fedoraproject.org/rpms/fedora-obsolete-packages
Obsoletes in individual rpms have no effect on module
Dne 31. 03. 20 v 10:00 Petr Pisar napsal(a):
On Tue, Mar 31, 2020 at 09:25:45AM +0200, Vít Ondruch wrote:
Wouldn't be easier to use something we already have? E.g.
https://src.fedoraproject.org/rpms/fedora-obsolete-packages
DNF implements modules as an layer above RPM packages. Thus you cannot
Dne 30. 03. 20 v 19:20 Zbigniew Jędrzejewski-Szmek napsal(a):
On Mon, Mar 30, 2020 at 10:30:51AM -0400, Ben Cotton wrote:
document: TBD
version: 1
data:
# A string representing UTC date in ISO 8601 format: -MM-DD[T ]HH:MMZ
# When merging, entries with a newer 'modified' value will o
Dne 30. 03. 20 v 17:10 Petr Pisar napsal(a):
On Mon, Mar 30, 2020 at 10:30:51AM -0400, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL
[...]
*** When a module stream gets removed from a Fedora release, the
maintainer of the module stream must provide a modul
On Tue, Mar 31, 2020 at 09:25:45AM +0200, Vít Ondruch wrote:
> Wouldn't be easier to use something we already have? E.g.
> https://src.fedoraproject.org/rpms/fedora-obsolete-packages
Obsoletes in individual rpms have no effect on modules, and any
enabled module "shadows" non-modular rpms that the
Le mardi 31 mars 2020 à 10:00 +0200, Petr Pisar a écrit :
>
> And not for a fresh new installation or an upgrade from an non-up-to-
> date system
Because, it’s better to make usupported configurations work, at the
expense of stuff Fedora commited to support?
Modular priorities are strange.
Rega
On Tue, Mar 31, 2020 at 09:25:45AM +0200, Vít Ondruch wrote:
> Wouldn't be easier to use something we already have? E.g.
> https://src.fedoraproject.org/rpms/fedora-obsolete-packages
>
DNF implements modules as an layer above RPM packages. Thus you cannot control
modules metadata from an RPM metada
Wouldn't be easier to use something we already have? E.g.
https://src.fedoraproject.org/rpms/fedora-obsolete-packages
Vít
Dne 30. 03. 20 v 16:30 Ben Cotton napsal(a):
> https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL
>
> == Summary ==
> Fix Fedora upgradability issues when upgra
On Mon, Mar 30, 2020 at 10:30:51AM -0400, Ben Cotton wrote:
>
> document: TBD
> version: 1
> data:
> # A string representing UTC date in ISO 8601 format: -MM-DD[T ]HH:MMZ
> # When merging, entries with a newer 'modified' value will override
> any earlier values.
> # MANDATORY
> modifie
On Mon, Mar 30, 2020 at 10:30:51AM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL
[...]
> *** When a module stream gets removed from a Fedora release, the
> maintainer of the module stream must provide a modulemd document with
> Obsoletes or EOL data.
>
17 matches
Mail list logo
