Re: Transition to new mirror infrastructure
On Mon, Nov 9, 2020 at 11:02 PM Gilles Caulier wrote: > Hi all, > Hi Gilles, > > Until milonia to deino transition stage, we can access to milonia with > ssh to transfer weekly build of digiKam bundles, available at this > url: > > https://files.kde.org/digikam/ > > Now, we get this error message: > > [gilles@pc-gilles mxe]$ ssh digi...@deino.kde.org > Welcome to Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-52-generic x86_64) > > * Documentation: https://help.ubuntu.com > * Management: https://landscape.canonical.com > * Support:https://ubuntu.com/advantage > You do not have interactive login access to this machine. > Contact the systems administrator for further assistance. > Connection to deino.kde.org closed. > > On of the scripts to manage remote files (Windows bundles in this > case) is this one : > > > https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/mxe/04-build-installer.sh#L297 > > As you can see, it use ssh, scp, and rsync. > You will need to port your scripts to use sftp in place of the existing 'ssh' commands present in that script. Please note that you do not need to upload hashes manually (the .sum files you currently upload). These will be automatically generated for you by Mirrorbits - which detects new files and generates them automatically (subject to approximately a five minute delay as that is when it rescans the directory tree). The hashes it generates will be served directly and securely to users (not guaranteed for other files, where they may be redirected to a mirror instead) Those hashes can be accessed at $fileUrl.sha256 or $fileUrl.sha1 for any file on files.kde.org or download.kde.org. > > We have the same for MacOS, and Linux AppImage... > > Best regards > > Gilles Caulier > Regards, Ben > > Le ven. 30 oct. 2020 à 09:56, Ben Cooksley a écrit : > > > > Hi all, > > > > Just a heads up that over the weekend we're going to be migrating from > the existing mirror master server (known as milonia.kde.org) to the new > master server (which can be found under the name deino.kde.org). > > > > While this is not expected to have any impact on public access (as both > systems will continue to serve download.kde.org and files.kde.org in the > same form), it does mean that it may not be possible to upload new files > for a short period of time. > > > > For those who are looking to upload files or perform releases over the > weekend, it would be appreciated if you could please contact us so we can > ensure that you are guided to the correct system. > > > > Thanks, > > Ben Cooksley > > KDE Sysadmin >
Re: Transition to new mirror infrastructure
Hi all, Until milonia to deino transition stage, we can access to milonia with ssh to transfer weekly build of digiKam bundles, available at this url: https://files.kde.org/digikam/ Now, we get this error message: [gilles@pc-gilles mxe]$ ssh digi...@deino.kde.org Welcome to Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-52-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage You do not have interactive login access to this machine. Contact the systems administrator for further assistance. Connection to deino.kde.org closed. On of the scripts to manage remote files (Windows bundles in this case) is this one : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/mxe/04-build-installer.sh#L297 As you can see, it use ssh, scp, and rsync. We have the same for MacOS, and Linux AppImage... Best regards Gilles Caulier Le ven. 30 oct. 2020 à 09:56, Ben Cooksley a écrit : > > Hi all, > > Just a heads up that over the weekend we're going to be migrating from the > existing mirror master server (known as milonia.kde.org) to the new master > server (which can be found under the name deino.kde.org). > > While this is not expected to have any impact on public access (as both > systems will continue to serve download.kde.org and files.kde.org in the same > form), it does mean that it may not be possible to upload new files for a > short period of time. > > For those who are looking to upload files or perform releases over the > weekend, it would be appreciated if you could please contact us so we can > ensure that you are guided to the correct system. > > Thanks, > Ben Cooksley > KDE Sysadmin
Re: Getting involved in SoK
On Fri, Nov 6, 2020 at 7:37 PM Mariam Fahmy wrote: > > Hello, > Thanks alot for your advice. > I have installed the project locally and I start discovering how backends > work with codebase. > I have understood but I am missing things. > After doing some research and gathering information, here's what I can't > clearly understand: (Sorry if questions are little bit silly) Hi Mariam, No need to worry, feel free to ask away. > 1- what does it mean by resource? > When I searched about it, I found that resources may be data required by user > or requests from clients, is it right ? You can see here the class that defines a resource, should help you see what it represents: https://invent.kde.org/plasma/discover/-/blob/master/libdiscover/resources/AbstractResource.h In general, it's an asset: be it an application, a wallpaper or anything that can be listed and installed. > 2- to create a new resources backend we need to implement two classes, > The first class is the basic class which saves all created resources and > install & remove application or cancel transactions. > The second class, I didn't understand it's functionality, I found that it is > related to plugins but didn't understand it. The second important one is the resource I just mentioned above. Please explain a bit more what you don't understand. > 3-Filters in the base class: its target to filter the new requested resources? filters we just use when searching, to see what's being searched. In the case of this project it shouldn't be very important, since we will just be listing a system image. > 4- for each new resource backend, it should include all the methods of base > class, right? > As these methods acts as properties for each new resource. You need to implement all the abstract (i.e. virtual = 0) methods. The rest of virtuals you can override if you want to give it a different functionality. > 5- I have searched about plugins, but I didn't fully understand it, plugins > enable programmers to update host program while keeping the user within the > program's environment, but I can't understand what is the role of plugins > here if we receive new requests and make new resources? > It is meant that while creating a new resource, we need plugin in order to > keep the user with the program's environment without altering it or affecting > it while creating new resources? It's just a way to build the applications so the whole project doesn't depend on a specific technology. You can see the ones we implement right now here: https://invent.kde.org/plasma/discover/-/tree/master/libdiscover/backends This project should be adding a new OSTreeRPMBackend folder in here that will only take care of this one implementation. I hope this helps, Aleix
