On Fri, 15 Sep 2023 16:02:04 +0200 Frantisek Lachman <flach...@redhat.com> wrote:
> Thanks Dan and Daniel for the responses. You both are right. For our > defence, this is always setup by an existing Fedora user (=human). > > I can't speak of rel-eng (and honestly don't know) how problematic > this "physical removal" on request is. it's a process that at least 2 people must go thru, one opening a ticket, second doing the removal and closing the ticket ... > We can at least promote the licence check more > and provide instructions on what to do if something does not fulfil the rules. > (E.g. as a part of the issue Ankur created and mentioned > (https://github.com/packit/packit/issues/2035)) > > Does anyone have any realistic solution (or an improvement) to this > for Packit itself? > > We can also stop uploading the source to the lookaside cache (or make > it configurable), > but the benefit of such automation is significantly reduced. I think making it configurable could be the way, for example an upstream project where I am the developer can have the upload enabled, because I control my licensing situation, but it shouldn't be the default for a "random" project. Dan > František > > > On Fri, Sep 15, 2023 at 3:39 PM Dan Horák <d...@danny.cz> wrote: > > > > On Fri, 15 Sep 2023 15:13:58 +0200 > > Frantisek Lachman <flach...@redhat.com> wrote: > > > > > Hi Petr, > > > > > > we would like to avoid storing the archive in the lookaside cache before > > > approving but the problem is that the CI on the PR (mainly the scratch > > > build) does not work without the archive being in the lookaside cache > > > already. Once this becomes possible, we (=Packit) would be happy to do > > > this > > > only when approved. > > > > > > But thanks to the archive hash, we don't build anything to Fedora that is > > > not approved. > > > > but this is the problem, once uploaded, it can be reached and > > downloaded, making Fedora distributing the content. It then needs > > a rel-eng action to "physically" remove problematic source archive. > > > > > > Dan > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@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 > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
