for libccp4, just do it :).
I personnaly do not have time now to do the upload.
thanks a lot
Fred
- Le 10 Mai 24, à 7:29, Andrius Merkys mer...@debian.org a écrit :
> Hello,
>
> I care for tree packages which still have open "NMU diff for 64-bit
> time_t transition" bugs: libccp4,
> [...]
>
> The first time `debian/rules clean` runs, dh_autoreconf has not run, so
> dh_autoreconf_clean has nothing to do and is silent. The second time,
> after dh_autoreconf has run, you can see it doing stuff.
ok, in that case it would be nice to display a message saying I do nothing :),
)
> make[1]: Leaving directory '/<>'
>
> G.
>
>
>
>
>
> Il venerdì 19 aprile 2024 alle ore 14:45:15 CEST, PICCA Frederic-Emmanuel
> ha scritto:
>
>
>
>
>
> Hello,
>
> In this build, I do not see a call to dh_autoreconf_clean
Hello,
In this build, I do not see a call to dh_autoreconf_clean
https://buildd.debian.org/status/fetch.php?pkg=hkl=amd64=5.0.0.3434-1=1713518550=0
this package override_dh_clean like this
override_dh_clean:
rm -f Documentation/api/hkl-docs.sgml
dh_clean
so my question is: is
Hello, I have some failures depending on the architecture.
If I remember correctly I was affected by an ipv6 / ipv4 vs ipv6 only
configuration.
so my question is simple:
What should be the right snipset in order to display network information in the
autopkgtest before running the test.
Do yu know If we have a Debian bug, so I can refer to this bug in mine ?
I prefer to not hide the problem and wait u til mesa is fixed (if this is not
too long).
Do you have a idea of when this issue should be integrated into Debian mesa ?
Hello, I am affected by this error in the autopkgtest of silx[1]
487s autopkgtest [22:01:24]: test gui: [---
489s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
489s glx: failed to create drisw screen
489s failed to load driver: zink
493s autopkgtest
I found this solution.
execute_before_dh_missing-arch:
# rm remaining files (workaround FTBFS...)
rm -rf debian/tmp/usr/share
execute_before_dh_missing-indep:
# rm remaining files (workaround FTBFS...)
rm -f debian/tmp/usr/bin/bornagain
rm -rf
> I see you are currently using a bunch of "dh_install -p"
> calls in your execute_before_dh_install target.
When I update a package I prefer a lot to edit one file (rules) instead of
opening multiples files...
>
> Maybe the next logical step would be to use debian/*.install
> files.
maybe...
> Hi. Have you tried splitting override_dh_auto_install into
> override_dh_auto_install-arch
> and override_dh_auto_install-indep?
no effect at all..., it is especially difficult to deal with the
nopython, nodoc, nocheck profiles if dh_missing does not take into account all
the
dh_install
Hello, I am working on the bornagain package
the arch all build failed with this error mesage
dh_missing: warning: usr/bin/bornagain exists in debian/tmp but is not
installed to anywhere
dh_missing: warning: usr/lib/python3/dist-packages/bornagain/__init__.py exists
in debian/tmp but is not
thanks a lot !
- Le 27 Nov 23, à 15:55, Daniel Gröber d...@darkboxed.org a écrit :
> Hi Frederic,
>
> On Mon, Nov 27, 2023 at 02:30:28PM +0100, PICCA Frederic-Emmanuel wrote:
>> Hello, I would like to know if there is command line tool usable from
>> bash , whi
Hello, I would like to know if there is command line tool usable from bash ,
which allows to list all the artefacts of a given .changes file.
thanks
Frederic
It seems to me that this is due to the python-defaults removal of python3.7
there is no more python3.7 python extensions but the test are still running.
I think that this should be solved once python3-defaults will had migrated to
testing and the autopkgtest was re-run for these packages.
maybe this : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831870
Maybe a hint.
tar.gz generated via github, seems to cause troubles during the import process.
just try to extract the tar.gz via tar and regenerate it from the extracted
files.
Maybe it should solve your problem.
Hello,
I am preparing the new vitables, but I get this error message from piuparts.
Preparing to unpack /tmp/vitables_3.0.0-1_all.deb ...
Unpacking vitables (3.0.0-1) over (2.1-1) ...
dpkg: warning: unable to delete old directory
'/usr/share/vitables/vitables/htmldocs/_static': Directory
> Can you reproduce the problem with:
> $ cat tango-9.3.3-rc2.tar | tar --delete > \
> tango-9.3.3-rc2-excluded.tar
> ?
here
:~/Debian/tango$ cat tango-9.3.3-rc2.tar | tar --delete
tango-9.3.3/lib/java/RestServer-1.14.jar > tango-9.3.3-rc2-excluded.tar
tar:
> Please confirm that
> > LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar")
> > < tango-9.3.3-rc2.tar > tango.tar
> is inspired by `mk-origtargz`.
not at all, I found this in #869087, which is a tar bug with --delete.
It is not clear to me what is the cmd executed by
I tryed to reproduce the issue like this
LANG=C tar --delete $(tar tf tango-9.3.3-rc2.tar | grep "lib/java/R.*jar") <
tango-9.3.3-rc2.tar > tango.tar
tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in archive
tar: Exiting with failure status due to previous errors
Is it the right way
> mk-origtargz just calls tar --delete < file > newfile and as you can
> easily check this indeed gives the same error message.
the listed files are the right files as extracted by tar from the upstream
tar.gz, so
this is an issue with tar ?
Is it possible to display the exact tar command line
looking at the directroy, I find this
drwxr-xr-x 11 picca picca 4096 août 20 17:23 tango-9.3.3
-rw-r--r-- 1 picca picca 282982400 août 25 08:37
tango_9.3.3~rc2+dfsg1.orig.tar
-rw-r--r-- 1 picca picca 232776497 août 25 08:36 tango-9.3.3-rc2.tar.gz
what is strange it that the extracted
Hello
> Found jar deletion instruction
> at https://salsa.debian.org/science-team/tango/blob/master/debian/copyright#L5
yes I use
Files-Excluded: lib/java/*.jar
from DEP-5 (it was find until now)
> I assume that upstream has stopped shipping jars in there .tar.gz
> If so, then it is a good
Hello,
When I try to import the new tango[1] sources with
gbp import-orig -uscan
I get this error
:~/Debian/tango/tango$ LANG=C gbp import-orig --uscan
gbp:info: Launching uscan...
tar: tango-9.3.3/lib/java/RestServer-1.14.jar: Not found in archive
tar:
> Must?
by must , I just express that the upsteam says in the documentation, that we
can import bornagain from python.
so it is a public module.
> In that case I find it strange that the librray API is published as a
> Python binding but not as underlying C lib.
Yes the python module and the
(First of all, is there a typo in "_libBorAgainFit.so"?)
yes I forgot the n of born :)
[...]
> I expect that in the case of bornagain, libBornAgainFit.py looks for
> _libBornAgainFit.so in the same directory,
> /usr/lib/python3/dist-packages/bornagain/.
yes and /usr/bin/bornagain also look for
Hello,
I am preparing a package knows as bornagain.
this software provide a GUI application and a python modules generated via swig.
part of the code is shared between the binary and the modules.
the upstream put the library
_libBornAgainCore.so
_libBorAgainFit.so
_libbornagainGUI.so
under
with buster, I will check if this is the same on unstable.
thanks
Fred
Hello, I am woriking on a new package called bornagain.
I switched to compat level 12 and now I have this error message.
I do not know how to fix this ?
thanks for your help.
Frederic
dh_dwz
install -d debian/bornagain/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz -q
> I tried but I couldn't (probably because of not having enough permissions in
> science-team group)
> So I just invited you to be a maintainer of the project so that you can do the
> transfer
I do not know how to do this transfer.
I am wondering if it is not necessary to open a tick to the
Hello carlos,
> All tests are passed except for piuparts which fails due to unavailability of
> the python3-taurus dependency (provided by taurus_4.5.0+dfsg-2 which is
> already in salsa, but not yet uploaded)
> What should I do now?
I can not access the lintian artefacts [1]
looking at the
Hello carlos,
If your package provide this pyhton module
taurus.pyqtgraph,
then the binary package should be named
python-taurus.pyqtgraph.
Cheers
Frederic
Hello, I would like to create a watch file for this package
http://xds.mpimf-heidelberg.mpg.de/
as explained in page a new version is when the laast line of the page change.
then we can download the binaries from here
http://xds.mpimf-heidelberg.mpg.de/html_doc/downloading.html
so do you
Hello Andrius,
You can use sbuild or pbuilder, cowbuilder in order to build in a clean room.
Cheers
Frédéric
Hello,
I am preparing the new silx package and I get this error message during the
build
WARNING: autodoc: failed to import module 'silx.opencl.codec.byte_offset'; the
following exception was raised:
Traceback (most recent call last):
File
Hello guyes,
look at here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873921
:((
to late ;)
De : PICCA Frederic-Emmanuel
Envoyé : mercredi 25 janvier 2017 19:10
À : Ghislain Vaillant; 852...@bugs.debian.org; sub...@bugs.debian.org
Objet : Bug#852626: RFS: h5py/2.7.0~rc3-1 [RC]
I am on it :)
Cheers
I am on it :)
Cheers
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mercredi 25 janvier 2017 19:00
À : sub...@bugs.debian.org
Objet : Bug#852626: RFS: h5py/2.7.0~rc3-1 [RC]
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking
Hello Ghislain.
do you know if this version is compatible with the reverse dependencies already
in Debian ?
python-qtpy
Reverse Depends:
python-spyder
python-ginga
python-qtawesome
python-glue
We are close from the freeze and I do not want to end up with a bunch of autorm
packages due
> This has nothing to do with that you have multiple download URLs.
> You are simply missing to replace - with ~ to sort RCs before final versions.
> uversionmangle=s/-rc/~rc/
I will do this change and see if with two URL, uscan upload only one .tar.gz.
I do not want to download two times the
> uscan works out of the box with both URLs as far as I can tell.
you I uncomment everythongs and uscan check at bothe URL compares the version
and at the end download the most recent package from the right URL ?
ok, I uncomment both URL and now I get this
version=4
> Just uncommenting both seems to work for me, what issue do you get?
No issues, I just wanted to know if I could have something with uscan which
work out of the box with both URL's.
So I would like something without the comment / uncomment trick.
Cheers
Hello,
for one of my package, I need to check at two location for new upstream release.
the official release are usually located on sourceforge.
but rc's are usually provided via their internal ftp.
This is important for me to be able to prepare experimental upload of the rc's.
so I would like
Hello Sean,
in flycheck-doc, you put this
+Depends: www-browser, elpa-flycheck (= ${source:Version})
+Suggests: elpa-flycheck
why this dependency to elpa-flycheck ?
done
thanks a lot for this package ;)
Fred
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mardi 14 juin 2016 16:13
À : Debian Bug Tracking System
Objet : Bug#827273: RFS: python-vispy/0.4.0-1 [ITP]
Package: sponsorship-requests
Severity: wishlist
uploaded
Cheers
Fred
Hello Ghislain.
I see only one problem you did not repackage the source with a +dfsg in order
to remove the font files.
If you let the files inside the source package you need to add the copyright
information of these files.
the best is to repackge using the Files-Excludes in the copyright
> I don't know enough about the python-qtawesome package to tell whether
> python-xstatic-font-awesome is equivalent functionality-wise.
Me too :)
> I don't expect it to be an easy pitch to ask the Spyder team to
> rethink their dependency chain just for the sake of re-usability.
> Unless you
Hello Ghislain,
I am wondering it this python-qtawesome package should not be replace by the
already available one [1]
python-xstatic-font-awesome.
It would be great if we could convince the spyder upstream to use the
python-xstatic system instead of embeding third party solutions.
Cheers
> The Spyder Development Team is not upstream of this font actually. So I
> don't think creating a font package from this source package is the
> right solution, is it?
No you are right
I looked at the elusive content
/tmp$ unzip elusive-icons-2.0.0.zip
Archive: elusive-icons-2.0.0.zip
Hello Ghislain
>* The -common package contains 2 fonts, one of which is not available
> for Debian (elusive-iconfont, SIL OFL 1.1). The other one (fontawesome)
> is symlinked from its corresponding package.
in that case can you create a real fonts package in order to be consistant with
all
uploaded.
thanks a lot
Fred
Done :)
thanks for your work.
Fred
Uploaded
thanks for your work
Frederic
Thanks to Picca Frederic-Emmanuel (Closes: #793789)
* d/control: cme fix, wrap and sort, update descriptions.
* Add examples to doc package.
* Move documentation generation to arch-indep targets.
* Add autopkgtest testsuite.
* Simplify clean target.
Best regards,
Ghislain Vaillant
accepted :)
uploaded.
thanks for your work :)
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : mercredi 13 janvier 2016 04:19
À : sub...@bugs.debian.org
Objet : Bug#810870: RFS: propellor/2.15.3-1 -- property-based host
configuration management in haskell
done :)
Thanks
Fred
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : lundi 4 janvier 2016 13:58
À : sub...@bugs.debian.org
Objet : Bug#809826: RFS: propellor/2.15.2-1 -- property-based host
configuration management in haskell
Package:
done.
thanks for your contribution :))
De : Sean Whitton [spwhit...@spwhitton.name]
Envoyé : dimanche 3 janvier 2016 18:28
À : sub...@bugs.debian.org
Objet : Bug#809747: RFS: propellor/2.15.1-1 -- property-based host
configuration management in haskell
> https://wiki.debian.org/PackageTransition
I know about this wiki page (very valuable), but my case is not described in
here.
Cheers
Fred
Hello, I would like to solve a circular dependency with the python-fabio package
before (N) binaries
python-fabio
after (N+1) binaries
fabio_viewer
python-fabio
python-fabio-dbg
python3-fabio
python3-fabio-dbg
for this new version, I move the /usr/bin files from python-fabio (N) into
Hello,
I am on it.
Cheers
I will take care of this.
Cheers
It is in the pipe :)
Cheers
done :)
Thanks
Fred
Ok, I used dcut
dcut -k 4696e015 rm clblas_2.6-2_amd64.changes
in order to remove the offending file
Cheers
Fred
I'll take care of this one then I need to leave so if you come with clblas
after do not hesitate to ask Andreas.
Cheers
Fred
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mercredi 19 août 2015 11:15
À : sub...@bugs.debian.org
Objet : Bug#796079:
done.
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mardi 18 août 2015 21:44
À : sub...@bugs.debian.org
Objet : Bug#796043: RFS: clblas/2.6-2
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package
Hello Ghislain,
I get this error when building with sbuild (unstable)
[ 62%] Building CXX object library/CMakeFiles/clFFT.dir/fft_binary_lookup.cpp.o
cd /«PKGBUILDDIR»/obj-i586-linux-gnu/library /usr/bin/c++ -DCLFFT_EXPORTS
-DclFFT_EXPORTS -pthread -g -O2 -fstack-protector-strong -Wformat
idem 2.6 is out and can you fix most of the lintian warnings :)
Cheers.
Fred
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hello, sorry but I am in VAC until mid August.
can you find another sponsor or wait until I come back from holidays ?
the 2.6 version is also available :p
Cheers
Fred
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hello,
I am working on a python package fabio, for the new verison I will add the
python3 pacakge and a pacakge which will contain only the scripts.
so
beffor
python-fabio (with the scripts moved into fabio-viewer)
python-fabio-dbg
python-fabio-doc
after
fabio-viewer
python-fabio
done
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mardi 21 juillet 2015 08:54
À : sub...@bugs.debian.org
Objet : Bug#793078: RFS: arrayfire/3.0.2-1
Package: sponsorship-requests
Severity: normal
Dear Mentors,
I am looking for a sponsor for the
Let me give you an example here. Let us assume we have a special target
'my_super_test' in the upstream Makefile which should be called by
dh_auto_test and let us further assume we do not want or cannot change
the upstream Makefile.
In this case I would do something like this
In order to run the tests in my package I first have to build them (they
are not built by the 'all' target). This requires a non-standard target
(build-tests) of the upstream Makefile to be invoked.
I have two solutions how I can deal with this:
1.) I change to the build directory (the
Hello Eugen
In order to run the tests in my package I first have to build them (they
are not built by the 'all' target). This requires a non-standard target
(build-tests) of the upstream Makefile to be invoked.
I have two solutions how I can deal with this:
1.) I change to the build
--build-dep-resolver=aptitude
Is it possible to configure this per chroot in order to avoir passing this
command line each time ?
Thanks
Frédéric
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
FFTW is required for the test suite to run. However, their GTest
detection is flawed which makes the test suite not runnable. To fix this
would require heavy patching.
I'd rather talk with upstream first and ask them to provide more freedom
with regards to GTest handling.
Does it sound ok to
Done
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53b2175...@sun-dag3.synchrotron-soleil.fr
Hello Gislain,
I will upload the package ;)
During the build I saw this
-- Could NOT find FFTW (missing: FFTW_LIBRARIES FFTW_INCLUDE_DIRS)
-- FindFFTW looked for single precision libraries named: fftw3f or libfftw3f-3
-- FindFFTW looked for double precision libraries named: fftw3 or
uploaded
Fred
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53b2172...@sun-dag3.synchrotron-soleil.fr
Hello Ghislain,
please upload to mentors then I will upload :)
wrong url in the next message ;)
De : Ghislain Vaillant [ghisv...@gmail.com]
Envoyé : mercredi 1 juillet 2015 18:09
À : sub...@bugs.debian.org
Objet : Bug#790771: RFS: clblas/2.4-2 -- OpenCL
look at the title ;)
RFS for the 2.4-1 version :)
no worry upload to mentors en I will take care of the sponsoring.
Cheers
Fred
#790771: RFS: clblas/2.4-1 -- OpenCL BLAS library
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hello, upload
but I have a few remarks.
here the rules file
# see EXAMPLES in dpkg-buildflags(1) and read /usr/share/dpkg/*
DPKG_EXPORT_BUILDFLAGS = 1
include /usr/share/dpkg/default.mk
why is it necessary to export the symbols since you are using compat level 9 ?
%:
dh $@
I have updated both clBLAS and clFFT with a patch that suppresses the
offending flags.
You can build the most recent version of the package from the d-science
repositories with:
gbp buildpackage --git-upstream-tag=v2.4 --git-upstream-branch=master \
--git-debian-branch=debian/sid
Hello Ghislain, I am trying to build your package with sbuild and I got htis
error message.
make[3]: Entering directory '/«PKGBUILDDIR»/obj-i586-linux-gnu'
/usr/bin/cmake -E cmake_progress_report
/«PKGBUILDDIR»/obj-i586-linux-gnu/CMakeFiles 4
[ 8%] Building CXX object
Hello,
I go thtese lintian errors
lintian
───
E: clblas source: missing-build-dependency dpkg-dev (= 1.16.1~)
N:
N:The package doesn't specify a build dependency on a package that is used
N:in debian/rules.
N:
N:lintian intentionally does not take into account transitive
N:
Hello Ghislain,
It seems to me thaht I already saw this problem with Jerome... I built my
package on a 32bit system.
cd /«PKGBUILDDIR»/obj-i586-linux-gnu/library /usr/bin/c++
-DCLFFT_EXPORTS -DclFFT_EXPORTS -m64 -pthread -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security
Hi Fred,
Thanks for checking my package out.
Sorry for the noise I realize thaht I ran lintian on my wheezy machine
This is why I have theses messages.
I'll send a patch upstream, but I don't think it is worth adding a patch to
the packaging for
such a harmless issue.
quality ;)
So
2015-06-17 10:25 GMT+01:00 PICCA Frederic-Emmanuel
frederic-emmanuel.pi...@synchrotron-soleil.frmailto:frederic-emmanuel.pi...@synchrotron-soleil.fr:
Hello Ghislain,
It seems to me thaht I already saw this problem with Jerome... I built my
package on a 32bit system.
cd /«PKGBUILDDIR»/obj
I checked it out and both clBLAS and clFFT actually suffer from the same
problem. It seems upstream is rolling its own
multiarch detection / selection mechanism. The detection is based on the
result of CMAKE_SIZEOF_VOID_P, and the
selection can be overriden via a cmake option.
obviously it
Hello, I can not sponsor your package, my computer can not boot anymore... I
will try to solve the problem...
Cheers
Frederic
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hello Andreas,
It seems that you do not have numpy installed on your machine.
can you try after
apt-get install python-numpy python3-numpy
cheers
fred
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Frederic, it seems you have a sponsoring look as well - so I'll stay in
fall-back mode. Just ping me if I should do the final sponsoring
upload.
No problem Andreas,
I will tell you.
Except that today I will be mostly off (- music :) until this evening
cheers
Fred
--
To UNSUBSCRIBE, email
Hell andreas,
I have this kind of problem with git import-orig when I forgot to synchronize
the upstream branch with the origin/upstream branch
this way the merge is done between master and your local upstream branch which
is not the origin upstream branch.
cheers
Frederic
--
To
Debian is (slowly, as ever, help very welcome) working on PPA-equivalents.
It's mostly designed, but is waiting for the tuits to implement it.
doc pointer, DEP ?
do we imagine something more decentrallize where we can imaging thaht an
institutA has an instance of this PPA want to work with
Done
Cheers
Frédéric
thanks for your work
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53b1fb7...@sun-dag3.synchrotron-soleil.fr
Hello
Please considere joining the debian-science team. [1]
These is a dedicated task page for astronomy softwares[2]
Cheers
Frederic
[1] http://wiki.debian.org/DebianScience
[2] http://blends.debian.org/science/tasks/astronomy
--
To UNSUBSCRIBE, email to
Hell andreas
for numexpr we are doing like this.
you need to set the PYTHONPATh in order to find the extension
override_dh_auto_test:
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
set -e -x;\
for py in $(PY2VERS) $(PY3VERS); do \
cd $(CURDIR)/build/lib.*-$$py;\
99 matches
Mail list logo
