robot-testing-framework / Re: Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

Hello,

I added the robot-testing-framework package to salsa:

  https://salsa.debian.org/science-team/robot-testing-framework/

This time it is a bit more difficult, since it is a set of small libraries.

Can anyone review it, please?


Cheers,
 Daniele

Re: ycm-cmake-modules / Re: Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

Hello again,

is there any other comment about the ycm-cmake-modules package? Do you
think it could be uploaded? What is the proper way to proceed now?
Should upload it to mentors and ask for a sponsor?


Cheers,
 Daniele

Re: ycm-cmake-modules / Re: Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

Hi Joost,

Thanks again...

On 31/08/2020 11:27, Joost van Baal-Ilić wrote:
> I've found some explanation at
> https://lintian.debian.org/tags/file-references-package-build-path.html

I already tried adding

  export DEB_BUILD_MAINT_OPTIONS = buildinfo=+path

and

  export DEB_BUILD_MAINT_OPTIONS = reproducible=+fixfilepath

to debian/rules, but neither of them helped. If I understand it
correctly, the both just add a few c/c++ build flags...

I might try fixing the file manually with `sed`, but I don't know if
that's the right way to do it.

> I'm pretty sure this issue has occured in lots of other packages but
> my websearch skills fail it now...
> 
> There's also https://tests.reproducible-builds.org/debian/reproducible.html
> and lots of documentation supplied @ reproducible-builds.org .
> 
> Does this help?  I _might_ have time to search a bit more later.


I think this is the page that should contain the related documentation
is this one: https://reproducible-builds.org/docs/build-path/

I couldn't find anything working there, though.

I managed to fix the lintian warning in this way:

https://salsa.debian.org/science-team/ycm-cmake-modules/-/commit/6218fcf5a14095b2a34c7f85b780979ac76499b7

I couldn't find a better way to do it, does this seem a proper fix?

Anyway the reprotest is still failing, the problem seems to be the
searchindex.js file (generated by sphinx) that has some different
content, but it is not a path. I don't think this can be fixed in the
package, it should probably be fixed in sphinx.





Cheers,
 Daniele

Re: ycm-cmake-modules / Re: Introduction and joining the debian-science/robotics team

[Joost van Baal-Ilić]

Hi Daniele,

On Mon, Aug 31, 2020 at 11:15:41AM +0200, Daniele E. Domenichelli wrote:
> On 28/08/2020 14:02, Joost van Baal-Ilić wrote:
> > I had a quick look at it and I didn't find any obvious flaws, apart
> > from
> > 
> >  Now running lintian ycm-cmake-modules_0.11.3-3_amd64.changes ...
> >  W: ycm-cmake-modules: embedded-javascript-library 
> > usr/share/doc/ycm-cmake-modules/html/_static/language_data.js please use 
> > sphinx
> >  N: 23 tags overridden (23 info)
> >  Finished running lintian.
> > 
> > .  Could you look into that?
> 
> 
> Thanks for the review.
> The warning should be fixed now.

Nice!


> I was also able to enable salsa-ci, see
> https://salsa.debian.org/science-team/ycm-cmake-modules/-/pipelines/170272/builds
> 
> Unfortunately the "reprotest" (that if I understand it correctly is a
> reproducibility test) is failing, probably for this lintian warning:
> 
> I: ycm-cmake-modules: file-references-package-build-path
> usr/share/doc/ycm-cmake-modules/html/todo.html
> 
> This file contains entries like
> 
> ```
> (The  href="manual/ycm-superbuild.7.html#id2">original entry is
> located in
> /build/ycm-cmake-modules-0.11.3/help/manual/ycm-superbuild.7.rst, line
> 215.)
> ```
> 
> for each `.. todo::` line in the sphinx documentation.
> 
> Unfortunately I don't know what is the proper fix it, since it is a file
> generated by sphinx... Do you have any suggestion?

I think you're right that /build/... in sphinx generated docs causes problems.

I've found some explanation at
https://lintian.debian.org/tags/file-references-package-build-path.html

I'm pretty sure this issue has occured in lots of other packages but
my websearch skills fail it now...

There's also https://tests.reproducible-builds.org/debian/reproducible.html
and lots of documentation supplied @ reproducible-builds.org .

Does this help?  I _might_ have time to search a bit more later.

Thanks, Bye,

Joost

Re: ycm-cmake-modules / Re: Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

On 28/08/2020 14:02, Joost van Baal-Ilić wrote:
> I had a quick look at it and I didn't find any obvious flaws, apart
> from
> 
>  Now running lintian ycm-cmake-modules_0.11.3-3_amd64.changes ...
>  W: ycm-cmake-modules: embedded-javascript-library 
> usr/share/doc/ycm-cmake-modules/html/_static/language_data.js please use 
> sphinx
>  N: 23 tags overridden (23 info)
>  Finished running lintian.
> 
> .  Could you look into that?


Thanks for the review.
The warning should be fixed now.

I was also able to enable salsa-ci, see
https://salsa.debian.org/science-team/ycm-cmake-modules/-/pipelines/170272/builds

Unfortunately the "reprotest" (that if I understand it correctly is a
reproducibility test) is failing, probably for this lintian warning:

I: ycm-cmake-modules: file-references-package-build-path
usr/share/doc/ycm-cmake-modules/html/todo.html

This file contains entries like

```
(The original entry is
located in
/build/ycm-cmake-modules-0.11.3/help/manual/ycm-superbuild.7.rst, line
215.)
```

for each `.. todo::` line in the sphinx documentation.

Unfortunately I don't know what is the proper fix it, since it is a file
generated by sphinx... Do you have any suggestion?


Thanks.

Cheers,
 Daniele

ycm-cmake-modules / Re: Introduction and joining the debian-science/robotics team

[Joost van Baal-Ilić]

Hi Daniele,

On Fri, Aug 28, 2020 at 11:32:48AM +0200, Daniele E. Domenichelli wrote:
> 
> I added the first package to salsa:
> 
>   https://salsa.debian.org/science-team/ycm-cmake-modules/
> 
> This is basically just a collection of CMake modules that is a
> dependency for most of our packages.
> 
> Can anyone review it please?

I had a quick look at it and I didn't find any obvious flaws, apart
from

 Now running lintian ycm-cmake-modules_0.11.3-3_amd64.changes ...
 W: ycm-cmake-modules: embedded-javascript-library 
usr/share/doc/ycm-cmake-modules/html/_static/language_data.js please use sphinx
 N: 23 tags overridden (23 info)
 Finished running lintian.

.  Could you look into that?

Thanks for your work!

Bye,

Joost

Re: Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

Hello Anton,

I added the first package to salsa:

  https://salsa.debian.org/science-team/ycm-cmake-modules/

This is basically just a collection of CMake modules that is a
dependency for most of our packages.

Can anyone review it please?


Thanks,
 Daniele


On 27/08/2020 20:22, Anton Gladky wrote:
> Hello Daniele,
> 
> welcome to the team! 
> 
> Feel free to create an account on salsa, request an access to the
> Science team and you can safely work on your packages there.
> 
> When you are ready or have a question, you can always ask in a team. You
> will definitely find someone to communicate. Almost all robotics
> packages are successfully maintained in the science team.
> 
> Please add your packages on salsa and ask for sponsoring, when you
> think, they are ready to be reviewed or/and uploaded.
> 
> Best regards
> 
> Anton
> 
> 
> Daniele E. Domenichelli  > schrieb am Mi., 26. Aug. 2020, 17:53:
> 
> Hello everyone,
> 
> I'm a technician/developer at Istituto Italiano di Tecnologia (IIT)[1],
> and I'm working mostly on YARP (an open source middleware for
> robotics)[2,3] and in general on the on the software developed in the
> "robotology" GitHub organization[4] and running on the iCub[5] and R1[6]
> robots.
> 
> I've been around Debian for a very long time, mostly as a user,
> reporting random bugs and in a few cases helping with a couple of
> packages. I'm also the maintainer of nifti2dicom[7] (which I haven't
> really updated in the last few years, since I'm no longer working in the
> neuroimaging field, but it is still working), and the former maintainer
> of gtkdataboxmm[8] which is no longer in Debian repositories.
> 
> I was at the debian-science and debian-med BoFs at DebConf (drdanz),
> since I'm interested in packaging and maintaining a few packages from
> the "robotology" github organization (mostly developed here at IIT), and
> perhaps helping with some other robotics-related packages.
> 
> I started working on a few of them but the YARP package turned out to be
> a lot more complicated than what I was expecting (I actually opened the
> original ITP in 2012, and I worked upstream little by little on fixing
> the issues that I found while trying to create the package).
> I now have a few working packages on an Ubuntu PPA[9], but I'm a bit
> stuck because I could not find any sponsor, I have lots of questions,
> and I'm still a bit confused by the Debian workflow.
> 
> Therefore I was wondering if there is someone that would be available
> to mentor me through the process.
> 
> These are the related bugs that I opened so far:
> 
> * #682756: ITP: yarp -- middleware for humanoid robots
> * #934757: ITP: ycm-cmake-modules -- Extra CMake Modules for YARP and
>   friends
> * #966342: RFS: ycm-cmake-modules/0.11.3-1 [ITP] -- Extra CMake Modules
>   for YARP and friends
> * #969037: ITP: robot-testing-framework -- Robot Testing Framework
> 
> 
> 
> I'm also looking for someone that would like to make a talk here at IIT
> (unfortunately online, due to the coronavirus, but we can eventually try
> to organize a visit later, when the pandemic is over), about
> Debian Science, Debian in general, and eventually make a
> small tutorial for beginners about how to start packaging.
> We produce a lot of software and libraries, but unfortunately we tend to
> build everything from sources on all our computers, therefore my goal is
> to persuade the people working here that proper packaging could help a
> lot our workflow.
> 
> 
> By the way, in case you have never heard about them, iCub is an open
> source (both hardware and software) humanoid robotic platform that we
> produce mostly for research and R1 is a recent effort to produce a "low
> cost" humanoid robot (unfortunately for this robot the hardware is not
> open).
> All the computers onboard and of the cluster connected to the robots run
> either Debian or in same cases ubuntu, with a few exceptions for
> computers running some specific software that runs only on windows,
> and researcher laptops that run whatever operating system the researcher
> chooses.
> 
> 
> Thanks in advance to anyone who will reply and will help me with the
> packaging.
> 
> 
> Cheers,
>  Daniele
> 
> 
> [1]https://www.iit.it/
> [2]http://yarp.it/
> [3]https://github.com/robotology/yarp/
> [4]https://github.com/robotology
> [5]https://icub.iit.it/
> [6]https://icub.iit.it/products/r1-robot
> [7]https://tracker.debian.org/pkg/nifti2dicom
> [8]https://tracker.debian.org/pkg/gtkdataboxmm
> [9]https://launchpad.net/~robotology/+archive/ubuntu/test/+packages
> 

Re: Introduction and joining the debian-science/robotics team

[Anton Gladky]

Hello Daniele,

welcome to the team!

Feel free to create an account on salsa, request an access to the Science
team and you can safely work on your packages there.

When you are ready or have a question, you can always ask in a team. You
will definitely find someone to communicate. Almost all robotics packages
are successfully maintained in the science team.

Please add your packages on salsa and ask for sponsoring, when you think,
they are ready to be reviewed or/and uploaded.

Best regards

Anton


Daniele E. Domenichelli  schrieb am Mi., 26. Aug.
2020, 17:53:

> Hello everyone,
>
> I'm a technician/developer at Istituto Italiano di Tecnologia (IIT)[1],
> and I'm working mostly on YARP (an open source middleware for
> robotics)[2,3] and in general on the on the software developed in the
> "robotology" GitHub organization[4] and running on the iCub[5] and R1[6]
> robots.
>
> I've been around Debian for a very long time, mostly as a user,
> reporting random bugs and in a few cases helping with a couple of
> packages. I'm also the maintainer of nifti2dicom[7] (which I haven't
> really updated in the last few years, since I'm no longer working in the
> neuroimaging field, but it is still working), and the former maintainer
> of gtkdataboxmm[8] which is no longer in Debian repositories.
>
> I was at the debian-science and debian-med BoFs at DebConf (drdanz),
> since I'm interested in packaging and maintaining a few packages from
> the "robotology" github organization (mostly developed here at IIT), and
> perhaps helping with some other robotics-related packages.
>
> I started working on a few of them but the YARP package turned out to be
> a lot more complicated than what I was expecting (I actually opened the
> original ITP in 2012, and I worked upstream little by little on fixing
> the issues that I found while trying to create the package).
> I now have a few working packages on an Ubuntu PPA[9], but I'm a bit
> stuck because I could not find any sponsor, I have lots of questions,
> and I'm still a bit confused by the Debian workflow.
>
> Therefore I was wondering if there is someone that would be available
> to mentor me through the process.
>
> These are the related bugs that I opened so far:
>
> * #682756: ITP: yarp -- middleware for humanoid robots
> * #934757: ITP: ycm-cmake-modules -- Extra CMake Modules for YARP and
>   friends
> * #966342: RFS: ycm-cmake-modules/0.11.3-1 [ITP] -- Extra CMake Modules
>   for YARP and friends
> * #969037: ITP: robot-testing-framework -- Robot Testing Framework
>
>
>
> I'm also looking for someone that would like to make a talk here at IIT
> (unfortunately online, due to the coronavirus, but we can eventually try
> to organize a visit later, when the pandemic is over), about
> Debian Science, Debian in general, and eventually make a
> small tutorial for beginners about how to start packaging.
> We produce a lot of software and libraries, but unfortunately we tend to
> build everything from sources on all our computers, therefore my goal is
> to persuade the people working here that proper packaging could help a
> lot our workflow.
>
>
> By the way, in case you have never heard about them, iCub is an open
> source (both hardware and software) humanoid robotic platform that we
> produce mostly for research and R1 is a recent effort to produce a "low
> cost" humanoid robot (unfortunately for this robot the hardware is not
> open).
> All the computers onboard and of the cluster connected to the robots run
> either Debian or in same cases ubuntu, with a few exceptions for
> computers running some specific software that runs only on windows,
> and researcher laptops that run whatever operating system the researcher
> chooses.
>
>
> Thanks in advance to anyone who will reply and will help me with the
> packaging.
>
>
> Cheers,
>  Daniele
>
>
> [1]https://www.iit.it/
> [2]http://yarp.it/
> [3]https://github.com/robotology/yarp/
> [4]https://github.com/robotology
> [5]https://icub.iit.it/
> [6]https://icub.iit.it/products/r1-robot
> [7]https://tracker.debian.org/pkg/nifti2dicom
> [8]https://tracker.debian.org/pkg/gtkdataboxmm
> [9]https://launchpad.net/~robotology/+archive/ubuntu/test/+packages
>
>

Introduction and joining the debian-science/robotics team

[Daniele E. Domenichelli]

Hello everyone,

I'm a technician/developer at Istituto Italiano di Tecnologia (IIT)[1],
and I'm working mostly on YARP (an open source middleware for
robotics)[2,3] and in general on the on the software developed in the
"robotology" GitHub organization[4] and running on the iCub[5] and R1[6]
robots.

I've been around Debian for a very long time, mostly as a user,
reporting random bugs and in a few cases helping with a couple of
packages. I'm also the maintainer of nifti2dicom[7] (which I haven't
really updated in the last few years, since I'm no longer working in the
neuroimaging field, but it is still working), and the former maintainer
of gtkdataboxmm[8] which is no longer in Debian repositories.

I was at the debian-science and debian-med BoFs at DebConf (drdanz),
since I'm interested in packaging and maintaining a few packages from
the "robotology" github organization (mostly developed here at IIT), and
perhaps helping with some other robotics-related packages.

I started working on a few of them but the YARP package turned out to be
a lot more complicated than what I was expecting (I actually opened the
original ITP in 2012, and I worked upstream little by little on fixing
the issues that I found while trying to create the package).
I now have a few working packages on an Ubuntu PPA[9], but I'm a bit
stuck because I could not find any sponsor, I have lots of questions,
and I'm still a bit confused by the Debian workflow.

Therefore I was wondering if there is someone that would be available
to mentor me through the process.

These are the related bugs that I opened so far:

* #682756: ITP: yarp -- middleware for humanoid robots
* #934757: ITP: ycm-cmake-modules -- Extra CMake Modules for YARP and
  friends
* #966342: RFS: ycm-cmake-modules/0.11.3-1 [ITP] -- Extra CMake Modules
  for YARP and friends
* #969037: ITP: robot-testing-framework -- Robot Testing Framework



I'm also looking for someone that would like to make a talk here at IIT
(unfortunately online, due to the coronavirus, but we can eventually try
to organize a visit later, when the pandemic is over), about
Debian Science, Debian in general, and eventually make a
small tutorial for beginners about how to start packaging.
We produce a lot of software and libraries, but unfortunately we tend to
build everything from sources on all our computers, therefore my goal is
to persuade the people working here that proper packaging could help a
lot our workflow.


By the way, in case you have never heard about them, iCub is an open
source (both hardware and software) humanoid robotic platform that we
produce mostly for research and R1 is a recent effort to produce a "low
cost" humanoid robot (unfortunately for this robot the hardware is not
open).
All the computers onboard and of the cluster connected to the robots run
either Debian or in same cases ubuntu, with a few exceptions for
computers running some specific software that runs only on windows,
and researcher laptops that run whatever operating system the researcher
chooses.


Thanks in advance to anyone who will reply and will help me with the
packaging.


Cheers,
 Daniele


[1]https://www.iit.it/
[2]http://yarp.it/
[3]https://github.com/robotology/yarp/
[4]https://github.com/robotology
[5]https://icub.iit.it/
[6]https://icub.iit.it/products/r1-robot
[7]https://tracker.debian.org/pkg/nifti2dicom
[8]https://tracker.debian.org/pkg/gtkdataboxmm
[9]https://launchpad.net/~robotology/+archive/ubuntu/test/+packages