Re: OMICS ID
Hi Dylan I noticed several commits of yours doing something like: - Entry: OMIC_04161 + Entry: OMICS_04161 I wonder whether we should check our IDs (may be not only the OMIC ones?) with some regexpes. For a first shot I could issue an error in the UDD importer logs (but I'm not frequently observing these). We could also consider lintian. Another option would be to write some own Debian Med checker and add it may be to our helper-scripts[1]. This checker should definitely call yamllint (may be ignoring some issues we do not care about - for me to long lines are a non-issue and also the missing "---" is perfectly tolerated by all our tools). We could add some useful regexp checks and everybody who commits metadata files that are failing this checker will offer a beer to the one who wrote the checker at the next sprint. ;-) Kind regards Andreas. [1] https://salsa.debian.org/med-team/community/helper-scripts -- http://fam-tille.de
Re: NDEBUG and CMake
Am Mittwoch, den 25.04.2018, 12:32 +0200 schrieb Sébastien Jodogne: > > cmake -DCMAKE_C_FLAGS=-DNDEBUG -DCMAKE_CXX_FLAGS=-DNDEBUG [...] > > Please someone could validate this approach? TIA! Add this at the top of d/rules: export DEB_CFLAGS_MAINT_APPEND=-DNDEBUG export DEB_CXXFLAGS_MAINT_APPEND=-DNDEBUG Best, Gert
Seeking for source code of CatchAll
Hi John, I'm writing you on behalf of the Debian Med team which is a group inside Debian with the objective to package free software in the field of life sciences and medicine for official Debian. Here you can see a list[1] of packages we just packaged (also featuring some todo list at bottom). Since we have a close cooperation with Bio-Linux which has a package of CatchAll we intend to provide it directly in Debian. To do this we need the source code of each software we want to distribute. I was checking the download page[2] of CatchAll but this only contains executable programs but no source code nor any license statement. Could you please point us to the source to enable us building the executables for Debian (which hopefully works with the recently packaged mono development stack)? We also need some license - preferably something like GPL or BSD - to be able to distribute the code. Kind regards Andreas. PS: I tried the link to the mailing list on the contacts page but it is throwing 404 - no idea whether this is known yet. [1] https://blends.debian.org/med/tasks/bio [2] http://www.northeastern.edu/catchall/downloads.html -- http://fam-tille.de
Re: OMICS ID
Hi Andreas, 2018-04-26 9:10 GMT+02:00 Andreas Tille : > I noticed several commits of yours doing something like: > > - Entry: OMIC_04161 > + Entry: OMICS_04161 I did it when I tried to sort out which packages should be reported in the OMICtools newsletter. I think, all OMICtools IDs in our database are correct now. No new incorrect OMICtools ID should appear, they were used at the beginning when the OMICtools website incorrectly reported them. > > I wonder whether we should check our IDs (may be not only the OMIC > ones?) with some regexpes. For a first shot I could issue an error > in the UDD importer logs (but I'm not frequently observing these). > Yes, of course, we should check other IDs (I am thinking, at least, about the "RRID -> SciCrunch" currently manually corrected by Steffen) I don't know how to use the UDD importer logs but I will be happy to learn. > We could also consider lintian. > The lintian checks (including #731340) are somewhere on my todo list but I need to find time :-) > Another option would be to write some own Debian Med checker and add it > may be to our helper-scripts[1]. This checker should definitely call > yamllint (may be ignoring some issues we do not care about - for me to > long lines are a non-issue and also the missing "---" is perfectly > tolerated by all our tools). We could add some useful regexp checks and > everybody who commits metadata files that are failing this checker will > offer a beer to the one who wrote the checker at the next sprint. ;-) > I will think about this kind of checker but definitely you know how to motivate me :-) Best, Dylan
Re: OMICS ID
Hi Dylan, On Thu, Apr 26, 2018 at 10:14:14AM +0200, Dylan Aïssi wrote: > > - Entry: OMIC_04161 > > + Entry: OMICS_04161 > > I did it when I tried to sort out which packages should be reported in > the OMICtools newsletter. > I think, all OMICtools IDs in our database are correct now. No new > incorrect OMICtools ID should appear, they were used at the beginning > when the OMICtools website incorrectly reported them. Thanks again for your work on this. > > I wonder whether we should check our IDs (may be not only the OMIC > > ones?) with some regexpes. For a first shot I could issue an error > > in the UDD importer logs (but I'm not frequently observing these). > > Yes, of course, we should check other IDs (I am thinking, at least, > about the "RRID -> SciCrunch" currently manually corrected by Steffen) > I don't know how to use the UDD importer logs but I will be happy to learn. They are not really usable. I'm running an UDD clone, test / run my importer script locally and read the logs. The logs of the official UDD are not published and only readable for users on udd.debian.org. So if you really want to "learn how to use" a local clone is the only chance I see. I do not know if this is an acceptable effort for you. For sure I could publish the log at request from time to time somewhere. > > We could also consider lintian. > > The lintian checks (including #731340) are somewhere on my todo list > but I need to find time :-) Cool. Both is very valuable. > > Another option would be to write some own Debian Med checker and add it > > may be to our helper-scripts[1]. This checker should definitely call > > yamllint (may be ignoring some issues we do not care about - for me to > > long lines are a non-issue and also the missing "---" is perfectly > > tolerated by all our tools). We could add some useful regexp checks and > > everybody who commits metadata files that are failing this checker will > > offer a beer to the one who wrote the checker at the next sprint. ;-) > > I will think about this kind of checker but definitely you know how to > motivate me :-) Its nice to have people around who are easy to motivate. ;-) Kind regards Andreas. -- http://fam-tille.de
adding to salsa debian-med group
Hi I was part of the debian-med group in alioth and was an uploader for imagej. I want to update the debian package. Could I also be added to salsa? My username there is the same 'carandraug-guest' [1] Thank you Carnë [1] https://salsa.debian.org/carandraug-guest