Re: What are the benefits of default modular streams over
non-modular packages?
by Petr Pisar
On 2019-11-14, Miro Hrončok <mhroncok(a)redhat.com> wrote:
> I've asked whether it wouldn't be in fact much easier to keep the
> default versions of our packages non-modular.
[...]
> Arguments were made that default modular streams are planned to
> deliver the exact same experience as non-modular packages, yet it was
> not said if it wouldn't be easier to just deliver non-modular packages
> for default versions.
>
> Maybe it would be helpful to try to reformulate the question:
>
> **What are the benefits of default modular streams over non-modular
> packages?**
[...]
> Considering we have 6 default modular streams, let me acknowledge that
> for the maintainers who decided to deliver default modular streams
> instead of non-modular packages, there clearly are some benefits.
> While some of us might not understand them, let's not say there are
> none. But even if there are clear benefits for the maintainers of
> those modules, I'm asking about the benefits for everybody else.
>
You answered yourself: "default modular streams are planned to deliver
the exact same experience as non-modular packages." If they provide the
same experience, they provide the same set of benefits. Hence there
cannot be any "benefits of default modular streams over non-modular
packages". Q.E.D.
If you want a disuccion, then you should not have stripped all
modularity features and than ask what are the benefits of modularity
without modularity.
-- Petr
2 years, 7 months
Re: What are the benefits of default modular streams over non-modular
packages?
by Miro Hrončok
On 15. 11. 19 14:03, Petr Pisar wrote:
> On 2019-11-14, Miro Hrončok <mhroncok(a)redhat.com> wrote:
>> I've asked whether it wouldn't be in fact much easier to keep the
>> default versions of our packages non-modular.
> [...]
>> Arguments were made that default modular streams are planned to
>> deliver the exact same experience as non-modular packages, yet it was
>> not said if it wouldn't be easier to just deliver non-modular packages
>> for default versions.
>>
>> Maybe it would be helpful to try to reformulate the question:
>>
>> **What are the benefits of default modular streams over non-modular
>> packages?**
> [...]
>> Considering we have 6 default modular streams, let me acknowledge that
>> for the maintainers who decided to deliver default modular streams
>> instead of non-modular packages, there clearly are some benefits.
>> While some of us might not understand them, let's not say there are
>> none. But even if there are clear benefits for the maintainers of
>> those modules, I'm asking about the benefits for everybody else.
>>
> You answered yourself: "default modular streams are planned to deliver
> the exact same experience as non-modular packages." If they provide the
> same experience, they provide the same set of benefits. Hence there
> cannot be any "benefits of default modular streams over non-modular
> packages". Q.E.D.
That is indeed how I understand it.
> If you want a disuccion, then you should not have stripped all
> modularity features and than ask what are the benefits of modularity
> without modularity.
What features have I stripped?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
2 years, 7 months
Fedora Modular 27 compose report: 20171124.n.0 changes
by Fedora Branched Report
OLD: Fedora-Modular-27-20171123.n.1
NEW: Fedora-Modular-27-20171124.n.0
===== SUMMARY =====
Added images: 12
Dropped images: 2
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0.00 B
Size of dropped packages: 0.00 B
Size of upgraded packages: 0.00 B
Size of downgraded packages: 0.00 B
Size change of upgraded packages: 0.00 B
Size change of downgraded packages: 0.00 B
===== ADDED IMAGES =====
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171124.n.0.aarch64.raw.xz
Image: Container_Minimal docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.0.x86_64.tar.xz
Image: Container_Minimal docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.0.aarch64.tar.xz
Image: Server qcow2 x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171124.n.0.x86_64.qcow2
Image: Container_Base docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.0.aarch64.tar.xz
Image: Server raw-xz x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171124.n.0.x86_64.raw.xz
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Modular-Server-dvd-s390x-27-20171124.n.0.iso
Image: Container_Minimal docker armhfp
Path: Server/armhfp/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.0.armhfp.tar.xz
Image: Server qcow2 aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171124.n.0.aarch64.qcow2
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Modular-Server-netinst-s390x-27-20171124.n.0.iso
Image: Container_Base docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.0.x86_64.tar.xz
Image: Container_Base docker armhfp
Path: Server/armhfp/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.0.armhfp.tar.xz
===== DROPPED IMAGES =====
Image: Server raw-xz ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.raw.xz
Image: Server qcow2 ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.qcow2
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
4 years, 7 months
Fedora Modular 27 compose report: 20171124.n.1 changes
by Fedora Branched Report
OLD: Fedora-Modular-27-20171123.n.1
NEW: Fedora-Modular-27-20171124.n.1
===== SUMMARY =====
Added images: 12
Dropped images: 2
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0.00 B
Size of dropped packages: 0.00 B
Size of upgraded packages: 0.00 B
Size of downgraded packages: 0.00 B
Size change of upgraded packages: 0.00 B
Size change of downgraded packages: 0.00 B
===== ADDED IMAGES =====
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171124.n.1.aarch64.raw.xz
Image: Container_Minimal docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.1.x86_64.tar.xz
Image: Container_Minimal docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.1.aarch64.tar.xz
Image: Server qcow2 x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171124.n.1.x86_64.qcow2
Image: Container_Base docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.1.aarch64.tar.xz
Image: Server raw-xz x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171124.n.1.x86_64.raw.xz
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Modular-Server-dvd-s390x-27-20171124.n.1.iso
Image: Container_Minimal docker armhfp
Path: Server/armhfp/images/Fedora-Modular-Container-Minimal-27_Modular-20171124.n.1.armhfp.tar.xz
Image: Server qcow2 aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171124.n.1.aarch64.qcow2
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Modular-Server-netinst-s390x-27-20171124.n.1.iso
Image: Container_Base docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.1.x86_64.tar.xz
Image: Container_Base docker armhfp
Path: Server/armhfp/images/Fedora-Modular-Container-Base-27_Modular-20171124.n.1.armhfp.tar.xz
===== DROPPED IMAGES =====
Image: Server raw-xz ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.raw.xz
Image: Server qcow2 ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.qcow2
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
4 years, 7 months
Fedora 28 compose report: 20180316.n.0 changes
by Fedora Branched Report
OLD: Fedora-28-20180315.n.0
NEW: Fedora-28-20180316.n.0
===== SUMMARY =====
Added images: 0
Dropped images: 8
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
Image: Modular boot x86_64
Path: Modular/x86_64/iso/Fedora-Modular-netinst-x86_64-28-20180315.n.0.iso
Image: Jam_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Jam_KDE-Live-x86_64-28-20180315.n.0.iso
Image: Container_Minimal_Base docker s390x
Path: Container/s390x/images/Fedora-Container-Minimal-Base-28-20180315.n.0.s390x.tar.xz
Image: Modular boot aarch64
Path: Modular/aarch64/iso/Fedora-Modular-netinst-aarch64-28-20180315.n.0.iso
Image: Modular boot i386
Path: Modular/i386/iso/Fedora-Modular-netinst-i386-28-20180315.n.0.iso
Image: Modular boot ppc64
Path: Modular/ppc64/iso/Fedora-Modular-netinst-ppc64-28-20180315.n.0.iso
Image: Modular boot ppc64le
Path: Modular/ppc64le/iso/Fedora-Modular-netinst-ppc64le-28-20180315.n.0.iso
Image: Modular boot s390x
Path: Modular/s390x/iso/Fedora-Modular-netinst-s390x-28-20180315.n.0.iso
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
4 years, 3 months
Agenda for Tuesday's Modularity Working Group Meeting (2019-01-15)
by Nils Philippsen
Find below a list of topics which are planned to be discussed in the
Fedora Modularity Working Group meeting on Tuesday at 15:00 UTC in
#fedora-meeting-3 on irc.freenode.net.
To find out when this is in your local time zone, check the Fedora
Calendar (if you've set it and are logged in):
https://apps.fedoraproject.org/calendar/modularity/#m5249
Alternatively, to convert UTC to your local time zone, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d 'Tuesday 15:00 UTC'
Links to all issues below can be found at:
https://pagure.io/modularity/report/meeting_agenda
= Discussed and Voted =
Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)
= Followups =
#topic #112 Discussion: Module lifecycles
#link https://pagure.io/modularity/issue/112
.modularity 112
#link https://pagure.io/fesco/issue/2027
#topic #115 Discussion: Stream branch ownership for packages & modules
#link https://pagure.io/modularity/issue/115
.modularity 115
#link https://pagure.io/fesco/issue/2028
#topic #119 Modularity WG Charter (contd.)
#link https://pagure.io/modularity/issue/119
.modularity 119
= New business =
#topic #123 & #124 Service Levels, EOLs
#link https://pagure.io/modularity/issue/123
#link https://pagure.io/modularity/issue/124
.modularity 123
.modularity 124
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/modularity/report/meeting_agenda
If you would like to add something to this agenda, you can file a new
issue at https://pagure.io/modularity/issues, or bring it up at the end
of the meeting during the open floor topic. Note that the meeting is
one hour long and issues we don't get around to discussing may be
deferred until the following meeting.
--
Nils Philippsen "Those who would give up Essential Liberty to
Software Engineer purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
3 years, 5 months
Re: How to obsolede module?
by Petr Pisar
On Tue, Jan 14, 2020 at 05:21:40AM -0500, Josef Ridky wrote:
> Hi folks,
>
> Does anyone know, how can I obsolete modular version of package?
>
> TL;DR
>
> I have one package (gimp) that is now available as RPM and Module at the
> same time in Fedora. Due of modular version makes issues to users during
> system upgrade, I've decided to remove (obsolete) modular version of gimp
> and keep the RPM version only.
>
> Question is, How can I set new RPM build to be the replacement for the
> modular one? Especially, is it possible, when someone with modular gimp
> installed types `dnf upgrade gimp`, that command will remove modular gimp
> and installs new RPM instead?
>
RPM Obsolets triggers a package removal and can be placed into any package.
However, you cannot obsolete a module (i.e. disable or reset it)
programatically. This is by design an action that needs an explicit user's
consent. If you need modularity to support marking modules end-of-life,
I recommend you contacting Modularity team (psabata) that has been requested
to implement this feature for a long time.
Since any active module content masks same-named non-modular packages, you
cannot uninstall the modular gimp package by putting an Obsoletes into the
non-modular gimp package. Until the user explicitly disables the module, your
non-modular gimp will be invisible and thus the Obsoletes should not take any
effect.
But there is an solution in Fedora if your module exists in updates repository
only. Because Fedora mirrors keep only the latest module version, it should
be possible to place another package into the module, make it Obsolete and
Provide the modular gimp package. This causes DNF to replace the modular
gimp package with the another package. After that DNF should make the
non-modular gimp visible. Then you can release a non-modular gimp with higher
release than the Provided "gimp" symbol and that will obsolete the another
package. This should DNF make to replace the modular another package with your
non-modular gimp package.
But this only a theory. Maybe it won't work because of a caching of the
modular metadata somewhere.
-- Petr
2 years, 5 months
Fedora Modular 27 compose report: 20171125.n.1 changes
by Fedora Branched Report
OLD: Fedora-Modular-27-20171123.n.1
NEW: Fedora-Modular-27-20171125.n.1
===== SUMMARY =====
Added images: 11
Dropped images: 2
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0.00 B
Size of dropped packages: 0.00 B
Size of upgraded packages: 0.00 B
Size of downgraded packages: 0.00 B
Size change of upgraded packages: 0.00 B
Size change of downgraded packages: 0.00 B
===== ADDED IMAGES =====
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171125.n.1.aarch64.raw.xz
Image: Container_Minimal docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Minimal-27_Modular-20171125.n.1.x86_64.tar.xz
Image: Container_Minimal docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Minimal-27_Modular-20171125.n.1.aarch64.tar.xz
Image: Server qcow2 x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171125.n.1.x86_64.qcow2
Image: Container_Base docker aarch64
Path: Server/aarch64/images/Fedora-Modular-Container-Base-27_Modular-20171125.n.1.aarch64.tar.xz
Image: Server raw-xz x86_64
Path: Server/x86_64/images/Fedora-Modular-Server-27_Modular-20171125.n.1.x86_64.raw.xz
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Modular-Server-dvd-s390x-27-20171125.n.1.iso
Image: Container_Minimal docker armhfp
Path: Server/armhfp/images/Fedora-Modular-Container-Minimal-27_Modular-20171125.n.1.armhfp.tar.xz
Image: Server qcow2 aarch64
Path: Server/aarch64/images/Fedora-Modular-Server-27_Modular-20171125.n.1.aarch64.qcow2
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Modular-Server-netinst-s390x-27-20171125.n.1.iso
Image: Container_Base docker x86_64
Path: Server/x86_64/images/Fedora-Modular-Container-Base-27_Modular-20171125.n.1.x86_64.tar.xz
===== DROPPED IMAGES =====
Image: Server raw-xz ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.raw.xz
Image: Server qcow2 ppc64le
Path: Server/ppc64le/images/Fedora-Modular-Server-27_Modular-20171123.n.1.ppc64le.qcow2
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
4 years, 7 months
[modularity] Meeting Minutes - Jan 14, 2020
by Langdon White
Minutes:
https://meetbot.fedoraproject.org/teams/modularity/modularity.2020-01-14-...
Minutes (text):
https://meetbot-raw.fedoraproject.org/teams/modularity/modularity.2020-01...
Log:
https://meetbot.fedoraproject.org/teams/modularity/modularity.2020-01-14-...
==========================================
#fedora-meeting-3: Modularity Team Meeting
==========================================
Meeting started by langdon at 15:00:37 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-3/2020-01-14/modularit...
.
Meeting summary
---------------
* Roll Call (langdon, 15:00:55)
* agenda (langdon, 15:03:04)
* reviewing issues tagged with "meeting" (langdon, 15:04:45)
* CI test to enforce no-replace-base-packages policy for default streams
(170) (langdon, 15:06:08)
* LINK: https://pagure.io/modularity/issue/170 (langdon, 15:06:16)
* ACTION: contyk will get in touch with the CI team to see who could
own and implement such checks, as well as provide test definitions
later. (contyk, 15:31:30)
* Issue #169: Security vulnerabilities (CVEs) are not properly tracked
in modular packages - modularity - Pagure.io -
https://pagure.io/modularity/issue/169 (langdon, 15:32:10)
* #169 blocked by #166 and #163, when resolved, we will follow up with
the security team (langdon, 15:58:37)
* Issue #168: some thoughts on modularity docs - modularity - Pagure.io
- https://pagure.io/modularity/issue/168 (langdon, 15:58:56)
* contyk and langdon to review #168 and associated docs next week (jan
20, 2020) (langdon, 16:09:08)
Meeting ended at 16:10:13 UTC.
Action Items
------------
* contyk will get in touch with the CI team to see who could own and
implement such checks, as well as provide test definitions later.
Action Items, by person
-----------------------
* contyk
* contyk will get in touch with the CI team to see who could own and
implement such checks, as well as provide test definitions later.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* langdon (97)
* contyk (75)
* mhroncok (38)
* asamalik (34)
* zbyszek (20)
* zodbot (17)
* sct (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
2 years, 5 months
modular and personal koji
by Didier Fabert
Hi all,
With my personal koji (on el8), I cannot build some packages for my el8
tag. All failures are about modular metadata packages which cannot be
installed.
DEBUG util.py:621: No available modular metadata for modular package
'httpd-2.4.37-21.module_el8.2.0+382+15b0afa8.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'httpd-devel-2.4.37-21.module_el8.2.0+382+15b0afa8.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'httpd-filesystem-2.4.37-21.module_el8.2.0+382+15b0afa8.noarch', it
cannot be installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'httpd-tools-2.4.37-21.module_el8.2.0+382+15b0afa8.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'mod_http2-1.11.3-3.module_el8.2.0+307+4d18d695.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'mysql-common-8.0.17-3.module_el8.0.0+181+899d6349.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'mysql-devel-8.0.17-3.module_el8.0.0+181+899d6349.x86_64', it cannot be
installed on the system
DEBUG util.py:621: No available modular metadata for modular package
'mysql-libs-8.0.17-3.module_el8.0.0+181+899d6349.x86_64', it cannot be
installed on the system
Any idea to solve this problem ? I miss somthing ?
I setup my el8 tag like this
koji add-tag centos-8
koji add-tag --parent "centos-8" --arches 'x86_64' centos-8-build
koji add-group centos-8-build build
koji add-group centos-8-build srpm-build
koji add-external-repo -t centos-8-build -p 10 centos-8-external-baseos
http://mirrors.ircam.fr/pub/CentOS/8/BaseOS/\$arch/os
koji add-external-repo -t centos-8-build -p 15 centos-8-external-epel
http://mirrors.ircam.fr/pub/fedora/epel/8/Everything/\$arch
koji add-external-repo -t centos-8-build -p 11
centos-8-external-appstream
http://mirrors.ircam.fr/pub/CentOS/8/AppStream/\$arch/os
koji add-external-repo -t centos-8-build -p 12
centos-8-external-powertools
http://mirrors.ircam.fr/pub/CentOS/8/PowerTools/\$arch/os
koji add-external-repo -t centos-8-build -p 13 centos-8-external-extras
http://mirrors.ircam.fr/pub/CentOS/8/extras/\$arch/os
koji add-target centos-8 centos-8-build
koji add-group-pkg centos-8-build build bash bash bzip2 coreutils cpio
diffutils findutils gawk gcc grep sed gcc-c++ gzip info patch
redhat-rpm-config rpm-build shadow-utils tar unzip util-linux which make
centos-release xz
koji add-group-pkg centos-8-build srpm-build bash redhat-release
centos-release make redhat-rpm-config rpm-build shadow-utils wget
rpmdevtools
Thanks,
Didier (tartare)
1 year, 11 months
