Shubhanshu Saxena
Shubhanshu Saxena
@nex3, is this issue still open to work?
This is what I understood from the issue comments and a few searches on my own: - We need to package the executable (present in the Releases) to a `.deb`...
Thanks for confirming.
@nex3 I had a question - Shall I take the Control file data as a single config variable like the GitHub release notes are taken as `pkg.githubReleaseNotes` or take individual...
Sure. As per this [article](https://www.debian.org/doc/debian-policy/ch-controlfields.html#binary-package-control-files-debian-control), the possible fields in the CONTROL file are: - Package (mandatory) - Source - Version (mandatory) - Section (recommended) - Priority (recommended) - Architecture (mandatory)...
I think we can keep it `ConfigVariable` since `ConfigVariable` seems more feasible for a JSON file which is indeed like a map.
Sure that looks good. I was thinking of the case when the user adds a control file (say version 1) for the package and then we use the same by...
> I guess we can fetch submission data from backend API, from /profile/{username} we get teams id's and Hackathons for every team user is part of, then we get submission...
Sure. This issue is a combination of changes in the backend and the frontend. In the first step, the database needs to be indexed for the participants on the backend...
Can you elaborate how are you planning to accomplish this task?