>> You need to add Obsoletes: foo < 2
>Sorry, hit send too early. You need to add such obsoletes BOTH to foo and foo-
>bar.
>Sorry, hit send too early. You need to add such obsoletes BOTH to foo and foo-
>bar.
Adding obsoletes foo < 2 on both packages worked. Thanks much.
On Saturday, December 2, 2017 4:28 AM, Igor Gnatenko <ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sat, 2017-12-02 at 10:25 +0100, Igor Gnatenko wrote:
> On Sat, 2017-12-02 at 09:24 +0100, Mattia Verga wrote:
> > Il 01/12/2017 20:20, Philip Kovacs ha scritto:
> > > If I have version 1 of package foo, containing items bar, xxx, yyy,
> > > zzz, i.e.
> > >
> > > foo-1
> > > -----
> > > bar
> > > xxx
> > > yyy
> > > zzz
> > >
> > > and, for version 2, bar is split off to its own sub-package, foo-bar,
> > > so that
> > > the desired packaging becomes:
> > >
> > > foo-2 foo-bar-2
> > > ----- ---------
> > > xxx bar
> > > yyy
> > > zzz
> > >
> > > with foo-bar permanently requiring foo going forward. How does one
> > > structure the
> > > Obsoletes/Requires such that foo-2 pulls in foo-bar-2 only once,
> > > during the upgrade
> > > from 1 to 2?
> > >
> > > What is the best practice for this?
>
> You need to add Obsoletes: foo < 2
Sorry, hit send too early. You need to add such obsoletes BOTH to foo and foo-
bar.
- --
- -Igor Gnatenko
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAloicagACgkQaVcUvRu8
X0wmsg/9HpU/b7rm2FjfV296awFOc+TlLyoIFNJNshoeWm44WvGOu+wGOXHpfjQ6
JUE+NtZTR/DRIr7IMsXDuHfNoHa4oAH2VxIbwq/PjmPZDPdmxq0D9I/JOwhZX3yI
BUhqiDd9W5sB9Rv9ZWuuS359UnOgkSbrYKWUgYX2dlzP4oZGBij10RRU8KyLcTP7
NFcgyV4rkUnWUCndqP8rZLKyRR+vMc0ABiF8jXe8MoKOSDJdxaopgz/kaaxLyWBg
2Uvnn2gLanwIL/iaYWYabCG88pEq0JrR68HpeXFDChFGJGmiumJEoSsPois8WI9t
r+DoZAfNDNowBsG69HyrPmRgZHVT26+/f1UsX+EwX0siEGyuoqowcpabDTdmQ6gW
qTcDMZ6zQ5xLs/57GyrN/auE6kTmCyFsdaGHE6pUoL9vlna9NNBvqNFIItMMhhpO
ffqeedxpRGQRsA0EaR/1kOEGpxJZkQEXW3/AheA0Yzb/O9O8McT4XwxfJPe/5uLg
sr9+AYRkd2Akpz25IjIOIHhws9ienOiqZl0JI0mw/R24PPUmdVXTehNNh/NvJzDf
nqrFcp8+XXpgsD2qakpwq9xbDTVIFIr7RHRMz5kohuy4cJuetim6e3onC/8Mej8O
itLTGAcoK+XR8YOiIoxAbbAM05VA7SauAFv0DejUOvmFPeGR9S0=
=1qgG
-----END PGP SIGNATURE-----
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Hash: SHA256
On Sat, 2017-12-02 at 10:25 +0100, Igor Gnatenko wrote:
> On Sat, 2017-12-02 at 09:24 +0100, Mattia Verga wrote:
> > Il 01/12/2017 20:20, Philip Kovacs ha scritto:
> > > If I have version 1 of package foo, containing items bar, xxx, yyy,
> > > zzz, i.e.
> > >
> > > foo-1
> > > -----
> > > bar
> > > xxx
> > > yyy
> > > zzz
> > >
> > > and, for version 2, bar is split off to its own sub-package, foo-bar,
> > > so that
> > > the desired packaging becomes:
> > >
> > > foo-2 foo-bar-2
> > > ----- ---------
> > > xxx bar
> > > yyy
> > > zzz
> > >
> > > with foo-bar permanently requiring foo going forward. How does one
> > > structure the
> > > Obsoletes/Requires such that foo-2 pulls in foo-bar-2 only once,
> > > during the upgrade
> > > from 1 to 2?
> > >
> > > What is the best practice for this?
>
> You need to add Obsoletes: foo < 2
Sorry, hit send too early. You need to add such obsoletes BOTH to foo and foo-
bar.
- --
- -Igor Gnatenko
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAloicagACgkQaVcUvRu8
X0wmsg/9HpU/b7rm2FjfV296awFOc+TlLyoIFNJNshoeWm44WvGOu+wGOXHpfjQ6
JUE+NtZTR/DRIr7IMsXDuHfNoHa4oAH2VxIbwq/PjmPZDPdmxq0D9I/JOwhZX3yI
BUhqiDd9W5sB9Rv9ZWuuS359UnOgkSbrYKWUgYX2dlzP4oZGBij10RRU8KyLcTP7
NFcgyV4rkUnWUCndqP8rZLKyRR+vMc0ABiF8jXe8MoKOSDJdxaopgz/kaaxLyWBg
2Uvnn2gLanwIL/iaYWYabCG88pEq0JrR68HpeXFDChFGJGmiumJEoSsPois8WI9t
r+DoZAfNDNowBsG69HyrPmRgZHVT26+/f1UsX+EwX0siEGyuoqowcpabDTdmQ6gW
qTcDMZ6zQ5xLs/57GyrN/auE6kTmCyFsdaGHE6pUoL9vlna9NNBvqNFIItMMhhpO
ffqeedxpRGQRsA0EaR/1kOEGpxJZkQEXW3/AheA0Yzb/O9O8McT4XwxfJPe/5uLg
sr9+AYRkd2Akpz25IjIOIHhws9ienOiqZl0JI0mw/R24PPUmdVXTehNNh/NvJzDf
nqrFcp8+XXpgsD2qakpwq9xbDTVIFIr7RHRMz5kohuy4cJuetim6e3onC/8Mej8O
itLTGAcoK+XR8YOiIoxAbbAM05VA7SauAFv0DejUOvmFPeGR9S0=
=1qgG
-----END PGP SIGNATURE-----
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
