Dear Alexandre, thanks for your lots of work!
First of all, I'd like to reference some discussions in the upstream support forum: https://forum.seafile.com/t/what-about-reproducible-builds/3125/11 and https://forum.seafile.com/t/about-the-future-of-seafile-repository-packages/49/2 I'm adding my two cents on the stuff below: On 19.10.2017 23:12, Alexandre Rossi wrote: > Hi, > > I've done some proof of concept packaging which seems to be working. Thanks for that! > I'm also pondering moving most binaries out > of PATH as they feel useless to the user. I'd say that at least fsck, fuse and gc are quite important for an end user, so I think those should be kept. > I also chose to ignore seafile-controller and use systemd instead. I very much like that! :-D > So that means that my TODO list consists in the following, in order : > 1) send patches upstream > 2) use all this some time in order to fix seahub porting problems and > see if I want to use seafile myself > 3) coordinate with ccnet Debian maintainers to see how libccnet should > be packaged (ccnet or ccnet-server or both). Therefore, I created a new bug right here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887361 Although I actually just found this forum post: https://forum.seafile.com/t/seafile-server-and-seafile-client-packaging-guidelines/662/9 > 4) iron out admin scripts and associated documentation, document > seahub deployment in README.Debian> 5) cleanup seahub lintian errors (the > usual embedded or minified, or > both, js problems) > 6) fill out ITPs and find a sponsor. I know there is not upstream > commitment to security patches but I'm doing all this for myself > anyway so I'll try my best to finish the job. And maybe it won't go in > the archive but it may be of some interest to others. > 7) port seahub to python3 (I'v already ported one of my pet projects > and deps seem to be available so it should not be hard) Best regards, -- Moritz Schlarb Unix-Gruppe | Systembetreuung Zentrum für Datenverarbeitung Johannes Gutenberg-Universität Mainz Raum 01-331 - Tel. +49 6131 39-29441 OpenPGP Fingerprint: DF01 2247 BFC6 5501 AFF2 8445 0C24 B841 C7DD BAAF
<<attachment: schlarbm.vcf>>
signature.asc
Description: OpenPGP digital signature
