hi,
i would like to know how to remove a subpackage from the distribution. eg. there is a package X, which is in rawhide with version 1 and has subpackages a and b.
we have X-1 X-a-1 (dependent on X and Y) X-b-1 (dependent on X)
now the dependency Y is removed from rawhide and i create a new version 2 of package X without the dependency on Y and thus no subpackage X-a- 1.
now we have: X-2 (which obsoletes X-a-1) X-b-2
questions: a) do i have to add X-a-1 to fedora-obsolete-packages? b) is there a difference between rawhide and other branches?
the docs - at least those i found (mainly https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life#Obsole... )- are not too clear for me in that regard. besides: we should have a search-engine on docs.fedoraproject.org or even better over all our websites. google helps, but is not that great when it comes to not track users.
yours josef
Can you be more specific about the package structure (or provide a link to the spec)? Does the new package X-2 (or X-b-2) still contain the same functionality that was present inside X-a-1, so if a user installs one of those, they get the same program just without the dependency?
-Ian
On Fri, Jun 12, 2020 at 6:31 PM josef radinger cheese@nosuchhost.net wrote:
hi,
i would like to know how to remove a subpackage from the distribution. eg. there is a package X, which is in rawhide with version 1 and has subpackages a and b.
we have X-1 X-a-1 (dependent on X and Y) X-b-1 (dependent on X)
now the dependency Y is removed from rawhide and i create a new version 2 of package X without the dependency on Y and thus no subpackage X-a-
now we have: X-2 (which obsoletes X-a-1) X-b-2
questions: a) do i have to add X-a-1 to fedora-obsolete-packages? b) is there a difference between rawhide and other branches?
the docs - at least those i found (mainly
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life#Obsole... )- are not too clear for me in that regard. besides: we should have a search-engine on docs.fedoraproject.org or even better over all our websites. google helps, but is not that great when it comes to not track users.
yours josef _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
the package in question is tempest, which had a subpackage tempest- gnome-screensaver. gnome-screensaver is no more, therefore i would assume that obsoleting tempest-gnome-screensaver does no harm. josef On Fri, 2020-06-12 at 18:45 +0100, Ian McInerney wrote:
Can you be more specific about the package structure (or provide a link to the spec)? Does the new package X-2 (or X-b-2) still contain the same functionality that was present inside X-a-1, so if a user installs one of those, they get the same program just without the dependency? -Ian
On Fri, Jun 12, 2020 at 6:31 PM josef radinger <cheese@nosuchhost.net
wrote: hi,
i would like to know how to remove a subpackage from the distribution.
eg. there is a package X, which is in rawhide with version 1 and has
subpackages a and b.
we have
X-1
X-a-1 (dependent on X and Y)
X-b-1 (dependent on X)
now the dependency Y is removed from rawhide and i create a new version
2 of package X without the dependency on Y and thus no subpackage X-a-
now we have:
X-2 (which obsoletes X-a-1)
X-b-2
questions:
a) do i have to add X-a-1 to fedora-obsolete-packages?
b) is there a difference between rawhide and other branches?
the docs - at least those i found (mainly
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life#Obsole...
)- are not too clear for me in that regard. besides: we should have a
search-engine on docs.fedoraproject.org or even better over all our
websites. google helps, but is not that great when it comes to not
track users.
yours
josef
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
_______________________________________________devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Le vendredi 12 juin 2020 à 19:31 +0200, josef radinger a écrit : Hi,
we have X-1 X-a-1 (dependent on X and Y) X-b-1 (dependent on X)
now the dependency Y is removed from rawhide and i create a new version 2 of package X without the dependency on Y and thus no subpackage X- a-
now we have: X-2 (which obsoletes X-a-1) X-b-2
With that structure you do not need fedora-obsolete-packages since X ≥ 2 will eat X-a < 2. However, you may need a provides X-a in X ≥ 2 if something in the dependency graph depends on X-a < 2 (dnf repoquery may help you identify those). However, if X ≥ 2 does not actually provide the things dependants expect in X-a the provides will do more harm than good.
Those rules are independant of the fedora release and will work the same in devel and in previous releases.
Beware of people who request application of rpmlint messages without understanding their meaning will want you to add the provides even when the provide part is not actually provided in the new version.
Regards,