[RESOLVED] Dependency added automatically

[Balem]

Hello,

we have several packages to install sequentially, but without any dependencies.

The first package in the list has been updated, adding all the other packages as dependencies.

However, internally, no one seems to have touched this package.

Have you ever encountered a case of dependencies being added automatically?

Or do you know of a way to log actions performed on a package?

Thank you for your help.

[sfonteneau]

The first package in the list has been updated with all other packages as dependencies.

Is this a group package where all the packages have been made dependent? I didn't quite understand.

So who is the signatory of the problematic version?

[Balem]

Hello,

The three packages are 'Package templates' named XXX-step1, XXX-step2, and XXX-step3 respectively.

These three packages have no dependencies.

Package XXX-step1 is in a 'group' package applied to a set of machines.

All packages have the same signer, namely the WAPT certificate.

Recently, packages XXX-step2 and XXX-step3 were added as dependencies to package XXX-step1 Version 0.1-2 (see attached file).

Is there a log that would allow me to find the name of the user who pushed version 0.1-2 of package XXX-step1?

Is a 'Modified by' field planned in the package control file?

Thank you

[blemoigne]

Hello,
your colleague Maxime opened a ticket about this yesterday and seemed to have found the answers to his questions.
Good afternoon,
Bertrand

[sfonteneau]

Hello,

if you go to "tools -> view authentication logs" and search for "/api/v3/upload_packages", you should find who uploaded a package at that time

(ideally, each technician should have a certificate in their own name). That way, you just need to see who signed the package.

[Balem]

Thank you for your help

[dcardon]

Hi Emin,

were you able to find the information you were looking for? Just so we can mark the topic as resolved.

Regards,

Denis

[Balem]

Hello,
No, but you can mark the ticket as 'resolved'.
Thank you.