RE:Packaging python-xrayutilities

2019-03-21 Thread MARIE Alexandre
> Hi, > > I didn't have time to look into issue, but may be looking on how other > people solve similar problems will give you a hint: > > https://codesearch.debian.net/search?q=path%3Adebian%2Frules+mathjax > > Best, > Alex Hello, Thanks for the hint, this is where I am looking to deal with

RE:Packaging python-xrayutilities

2019-03-21 Thread MARIE Alexandre
> Wild guessing: The files to be changed might reside in debian/tmp - thus > > > find debian ... > > could be the solution. I am trying to do so, thanks for your response. Cheers, Alex

RE:Packaging python-xrayutilities

2019-03-21 Thread MARIE Alexandre
> Is there really the leading tab only on the second line? In fact I am trying to figure out where should I install the doc, and how could I avoid the lintian tag : privacy-breach-generic. > What exactly doesn't seem to work? The code I paste before wasn't working because the path was not

RE:Packaging python-xrayutilities

2019-03-21 Thread MARIE Alexandre
Hello, I'm still working on the package python-xrayutilities for debian. I've come to a point where the package can be built but when generating the doc, lintian comes with a bunch of privacy-generic-breach tags like this :

RE:Packaging python-xrayutilities

2019-03-19 Thread MARIE Alexandre
Hello, I resolved my git issue, but when I build the package doc with sphinx-build : ``` make[1]: Entering directory '/<>' pybuild --build -s custom -p 3.7 --build-args="env PYTHONPATH={build_dir} sphinx-build -bhtml doc/source build/sphinx/html" I: pybuild base:217: env

RE:Packaging python-xrayutilities

2019-03-18 Thread MARIE Alexandre
> You need to find why there are conflicts and fix them. Good first steps > are running gbp with --no-rollback and/or finding what upstream files are > modified in the master branch in the current state. When I do so, I only have one conflict on the file .gitignore. I solved it and tried to

RE:Packaging python-xrayutilities

2019-03-18 Thread MARIE Alexandre
Thanks again for the response ! I am resending an answer as the first one was sent to Florian Pelgrim only. > Try to replace all http links to https in your package. Changing http to https didn't solve the issue. I still get this error :