Hi Eric, > On Jul 18, 2023, at 3:31 PM, Eric Auer via Freedos-user > <freedos-user@lists.sourceforge.net> wrote: > > > Hi! > > Today I have gotten more than 60 notifications about packet updates, > NONE of which mentioned why the affected package got updated.
First, sorry about all the notification messages. Earlier today, I did some general maintenance on about 1/3 of the project repositories. There are couple reasons for adding a copy of the project’s LICENSE files there. First it makes it very easy to find and view. Also, GitLab will display the type of license in its button bar. I had previously copied a bunch of the LICENSES and today did several more. About 125 projects now have a copy of their LICENSE that is quick and easy to find. There are still about 250 more that need done. While doing this, I also updated those projects to the latest version of the CI/CD pipeline files. That is what pushes out a “Package Release” when a project is updated. However, it creates those based on the LSM metadata Version number. If a “Package Release” for that version already exists, it aborts without creating a duplicate release. Of the roughly 125 projects that were updated today, about half did not have existing “Package Release” files. So, ones would have been automatically generated by the CI/CD. > > I would REALLY like those notifications to include more details and > metadata. This would also allow looking up update details in the > archives later. I agree. :-) > > In this context I remember that this is a bug in some sort of an > automated package update script: It lacks the feature to pass ANY > information about the update reason, so there is none. But this > would be valuable information, so please improve that process :-) It is not a bug. But, it is problematic. With some exceptions, most of the projects live elsewhere and get updated after a new version is released. For those, it is not practical to provide a change log excerpt or summary of what is new. It would be far labor intensive and time consuming. But, it should be possible to update the CI/CD to include some recent commit messages. Possibly just the messages since the previous “Release.” For the projects that live elsewhere, this would mostly be just ‘updated to v1.2.3’ or the occasional general maintenance related messages like ‘added copy of LICENSE to project root’ Anything would be better than the current “created by release-ci” message. It’s just something I will eventually need to find the time to improve. > > Thank you! Regards, Eric :-) Jerome > > PS: Below is an example of an update notification, current style. > >> A new Release v6.00a for unzip was published. Visit the Releases page to >> read more about it: https://gitlab.com/FreeDOS/archiver/unzip/-/releases >> Assets: >> - unzip - v6.00a for FreeDOS: >> https://gitlab.com/FreeDOS/archiver/unzip/-/jobs/4679018030/artifacts/file/package/unzip.zip >> - Download zip: >> https://gitlab.com/FreeDOS/archiver/unzip/-/archive/v6.00a/unzip-v6.00a.zip >> - Download tar.gz: >> https://gitlab.com/FreeDOS/archiver/unzip/-/archive/v6.00a/unzip-v6.00a.tar.gz >> - Download tar.bz2: >> https://gitlab.com/FreeDOS/archiver/unzip/-/archive/v6.00a/unzip-v6.00a.tar.bz2 >> - Download tar: >> https://gitlab.com/FreeDOS/archiver/unzip/-/archive/v6.00a/unzip-v6.00a.tar >> Release notes: >> Created using the release-cli > > (the linked release website does not provide ANY details either) > > > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
