On Tue, Apr 16, 2024 00:40:33 GMT, Randy Barlow via devel wrote:
> As a tangent on this thread, it would be cool if there were a mechanism in
> dnf to tell users when an upgrade needs special attention/instructions.
> Another example like this is postgresql updates, which also require manual
>
On Mon, Apr 15, 2024 16:40:50 GMT, Michel Lind wrote:
> Hi Ankur,
Hi Michel,
Sorry, I missed your reply before.
>
> What you can probably do now is to introduce the compat package
> *first* into all stable releases - and make it obsolete the task
> package at the current NEVRA.
> Then for
As a tangent on this thread, it would be cool if there were a mechanism
in dnf to tell users when an upgrade needs special
attention/instructions. Another example like this is postgresql updates,
which also require manual intervention.
--
___
devel
Hi Ankur,
On 4/15/24 07:59, Ankur Sinha wrote:
On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote:
On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote:
Hrm, but the problem here is that a user that currently has the task
package installed (currently v2) will end up with v3 if
On Mon, Apr 15, 2024 14:18:59 +0200, Jos Vos wrote:
> On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote:
>
>Hrm, but the problem here is that a user that currently has the task
>package installed (currently v2) will end up with v3 if I update the
>task package to v3---which
On Mon, Apr 15, 2024 at 12:15:55PM +0100, Ankur Sinha wrote:
Hrm, but the problem here is that a user that currently has the task
package installed (currently v2) will end up with v3 if I update the
task package to v3---which is something we'd like to avoid here.
Just a side question:
On Mon, Apr 15, 2024 12:50:48 +0200, Jos Vos wrote:
> Hi,
>
> On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote:
>
>They are not designed to be installed in parallel, so task3 will
>obsolete task. However, task3 will not provide the task package, so that
>task will not be
On Mon, Apr 15, 2024 12:53:06 +0200, Vít Ondruch wrote:
> Our guidelines suggest that the "main" package should be unversioned, while
> if needed, the "compat" packages should include version:
>
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple
>
> So if you want to
Our guidelines suggest that the "main" package should be unversioned,
while if needed, the "compat" packages should include version:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple
So if you want to introduce new package, then please introduce `task2`
and update the
Hi,
On Mon, Apr 15, 2024 at 11:04:22AM +0100, Ankur Sinha wrote:
They are not designed to be installed in parallel, so task3 will
obsolete task. However, task3 will not provide the task package, so that
task will not be updated to task3 during normal upgrades. Users will
have to
On Mon, Apr 15, 2024 09:41:05 -, Onuralp SEZER wrote:
>
> +1 to create task3 but the CLI command is "task". It either needs to
> rename both like "task2,task3" or conflict old and new ones and
> prevent installing both of them.
They are not designed to be installed in parallel, so task3 will
+1 to create task3 but the CLI command is "task". It either needs to rename
both like "task2,task3" or conflict old and new ones and prevent installing
both of them.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
12 matches
Mail list logo
