Bonjour,
le synchrotron-Soleil propose un stage[1] de 3 à 6 rémunéré, afin de mettre en
place des tests unitaires et d’intégration sur un ensemble de logiciels [2]
considérés comme prioritaires pour l’exploitation des données scientifiques.
Bonne journée
Frédéric
[1]
My standard workflow
I use gbp and dgit
gbp import-orig --pristine-tar --uscan
gbp dch
lintian-brush
dgit --gbp sbuild (build and autopkgtest)
...work until it is ok on my computer
gbp dch
... hand edit the changelog
gbp push
git push (to push the UNRELEASE master branch)
... wait for salsa
I tried it on one of my package silx
warning: File: ./debian/tests/control:22:14:22:19: It is possible that the
value is a typo of "i386". [Correctable via --auto-fix]
22: Architecture: !i386
It seems wrong to me, the test control file allow !i386
Cheers
Frederic
One missing piece for me in order to migrate to meson is the integration
between flymake and the autotools.
https://www.emacswiki.org/emacs/FlyMake#h5o-7
> Installation and setup guide can be found in docs/.
Is it planed to package transformers in Debian instead of using conda/mamba
venv for this installation ?
* It would be great to help with the Debian patch workflow.
- upstream status
- find upstream bug equivalent to a Debian bug
I second this idea, and also the salsa pipeline should check this also.
- Le 5 Aoû 23, à 21:07, Timo Röhling roehl...@debian.org a écrit :
> Hi Lucas,
>
> * Lucas Nussbaum [2023-08-05 17:06]:
>>An example sbuild invocation to reproduce failures is:
> [omitted the command line equivalent
> Hi Charles,
>
> On Tue, Aug 01, 2023 at 04:43:59PM +0900, Charles Plessy wrote:
>> In the course of generating singularity/apptainer Debian images at work,
>> I wanted to make all locales available to the users.
I sthere a maliling list where we can speak about these singuarity/apptainer
thanks for this very precise explanation.
Fredric
- Le 20 Juil 23, à 15:58, David Kalnischkies da...@kalnischkies.de a écrit :
> Hi,
>
> On Thu, Jul 20, 2023 at 10:01:54AM +0200, PICCA Frederic-Emmanuel wrote:
>> I am working on two packages pyfai[4] and python-fabio
> Touch the generated files in d/rules as Aurelien suggested in the bug report?
Yes as a workaround, I can touch all files during the build
Nevertheless do we have an explanation of FTPMaster why files with timestamp
1/1/1970 are not allow in the Debian archive (at least for binary package) ?
Hello,
I am working on two packages pyfai[4] and python-fabio[3], I have got a
rejection based on the file timestamp which seems too old.
the bug report is here [1] and [2].
If you lool at python-fabio status page, it seems that they all failed [5], but
if you only look at the build log the
Hello, I try to write a really simple script in perl which allows me to rebuild
a bunch of packages using a file with a really simple syntax
backport hkl
git haskell-hkl https://repo.or.cz/hkl.git contrib/haskell
...
I setup a chroot with the sbuild-debian-developer-setup -> ok
Now I can build
> > In case #1000435 (matplotlib crashes on mips64el) is not already on
> > your radar, would you please take a look?
> >
>
> Thank you. I will work on it right now.
Hello, I just added some information about this problem on this bug
thanks a lot.
cheers
Fred
Hello, I am trying to understand a problem in matplotlib on the mips64el arch
https://buildd.debian.org/status/logs.php?pkg=matplotlib=3.3.4-2%2Bb1=sid
between 3.3.4-2 and 3.3.4-2+b1 the tests started to failed.
So I would like to know why this package was binNMU and the difference between
https://en.wikipedia.org/wiki/X-ray_absorption_fine_structure
See you
cme should not use wrap-and-sort instead of implementing its own logic ?
What about doing something similar to sphinx.
Create a package with the doxygen jquery and link to files of this package for
all documentations generated via doxygen.
provide a dh_doxygen to do this link like dh_sphinxdoc
Cheers
Fred
what about the git mode of uscan
then you would have all the tags ?
> If you use ssh, you can create an own account for the ssh key and give
> it very special permissions, if you need it for automatic pushes or
> similar things.
In fact I would like to use the salsa command from devscripts but without the
token.
My private ssh key was generated from my private
Is it possible to use it's ssh key in order to have acces to the salsa api ?
I mean instead of the token, which looks to me quite fragile compare to ssh via
a gpg card and the gpg agent.
cheers
Frederic
do we have some documentation explaining how to use a nitrokey PRO in order to
do
2FA authentication for salsa ? It seesm that ybikey is suppoprted out of the
box, but inevertheless is it possible to use a nitrokey pro 2 for the same
purpose ?
> That is mostly upstream's job -- ICD packagers should just verify that the
> package still runs "Hello World" on their hardware, i.e. the ICD
> integration works, and then we assume that it works.
ok, so in that case it would be nice to provide a computer with a GPU as
porterbox to test this
It would be nice also to be able to test the OpenCL icd implementations and
work with real hardware.
Hello
> Debian has from time to time funded hardware for people doing important
> work.
> I'd definitely be happy to receive a reimbursement request for such
> hardware from Debian developrs. For non DDs, I would want a DD involved
> in our GPU ecosystem (like yourself) to confirm the people
And what about
dgit --gbp push-source ?
perle 5.30 transition whcih was announced here
https://lists.debian.org/debian-devel-announce/2019/10/msg0.html
did you tried this
https://codesearch.debian.net/search?q=machine-id=1=1
> the configuration file to debian/gitlab-ci.yml. Therefor some time ago it had
it seems that now the name should be
debian/salsa-ci.yml
Frederic
> $ origtargz # since I use pristine-tar
what is the difference with
git deborig
> $ dgit --gbp build
> $ dgit --gbp push-source
or dgit --gbp sbuild
to build via sbuild in a clean chroot,
everythongs setup via propellor indeed thanks to sean and joeyh :))
> Getting started with dgit felt
Same here... with WXX100 cards.
what about rocm packaging ?
De : Steffen Möller [steffen_moel...@gmx.de]
Envoyé : lundi 17 juin 2019 20:14
À : debian-devel@lists.debian.org
Objet : AMDGPU+OpenCL with Debian?
Hello,
Running Debian unstable, I failed to set
> This thread reminded me the Debian User Repository thread:
> https://lists.debian.org/debian-devel/2019/04/msg00064.html
> Such a repository can be a "easy" packaging zone, possibly attracting
> more contributing people. Eventually some people will try to improve the
> packages and get them
[...]
> packages. While my Perl is a bit rusty, I can propose some "dh_fetch"
> helper for this if there is no huge opposition against this approach.
why not a dh_uscan ?
what is the fundamental difference between dh_fetch and what you can achieve by
using uscan from the rules file ?
Cheers
What about ibm power9 with pocl ?
it seems that this is better than the latest NVIDIA GPU.
Cheers
Hello,
I am also the upstream of a bunch of project.
what is the right way to use dgit when upstream contain the debian directory.
source format etc...
thanks
Frederic
After a build, you get this
https://salsa.debian.org/science-team/python-xrayutilities/-/jobs/147913/artifacts/browse/debian/output/
Is it enought for you.
Mayve you can discuss with the salsa pipeline team and request a target in
order to produce a better repo.
cheers
now we have the salsa pipeline.
does it fit your needs ?
> Well the point is that the need to create system users can be avoided
> entirely by running services using only dynamic UIDs.
Except that some services rely on Database granted access ...
Cheers
Frederic
> You can still use SSH to do repository operation. But I don't know what
> kind of automation you are doing.
I just want to configure CI parameters especially the .gitlab.yaml location
used by the CI.
for a bunch of packages.
> You talked about automation. Such tasks usualy run on a
Hello,
I was using a nitrokey pro + gpg-agent in order to connect via ssh to the
debian infrastructure.
Now that we have salsa, it seems that the way to go is to use salsa token in
order to automake a bunch of tasks.
So now I need to put somewhere on a disk my salsa token, in fact on every
> from the maintainer. Please request your package to be removed from the
> arch it doesn't build for anymore (bug against ftp.debian.org, use
> reportbug) in unstable and britney will migrate that.
done
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905348
thanks for your feedback
Fred
Hello,
I hope that I use the right mailing list for this.
Here my problem:
I just updated the pymca package and this new version dependes on the
python[3]-silx modules.
silx depends on pyopenCL which is only available on a limited amount of
architecture.
So now the migration of pymca is
>> It just comes to my mind that Maybe it does not fit well with my convention
>> for exeprimental numbering whcih is
>> blablab_x.y.z-t~exp1
>> so maybe the best way would be to use
>> blalbla_x.y.z-t~~alba+1
>So, you would not use the "bpo9" part for the packages built for stretch?
Not at
Hello Ian
> I didn't have a massive amount of time to review this in detail, but
> it sounds cool. I looked at the slides in the pdf [5] above.
> (Shame there isn't a technical report...)
the technical part is in the gitlab-ci.yml file :).
> I reviewed the version number proposal and it seems
Hello,
the Alba[1] synchrotron radiation facilities, recently switch to
Debian for their OS. They are part of the Tango[2] control system
community which contain most of the European Synchrotron Radiation
Facilities and others[3]. At least three instituts have already
choosen Debian (partially
> If an upstream author knows their code will go straight into an active
> Debian suite when they push a git tag to GitHub, the trust dynamic is
> changed, I think for the worse.
this is the model of travis no ?, the upstream could become also the debian
maintainer.
And check that his package
> Now that Alioth is beginning to close down and its replacement is not
> yet ready, how would I start this team now?
What is the status of this migration ? which solution was selected ?
thanks
Frederic
> Also renaming a user is actually trivial:
> usermod -l _something Debian-something
In my case (tango-db package), We need also to take care of the user database
access privilege.
granted by dbconfig-common.
So when moving from tango -> _tango users, they should be availalbe a sort of
hook
Hello,
first thanks for your hard work.
I am using fglrx-driver for OpenCL on my W5100 and W7100 amd GPUs.
Do you know if there will be a plan in order to support OpenCL on amd for
strech ?
Cheers
Frederic
Hello,
I did a source upload yesterday of the 9.2.2-1~exp1 into experimental and since
then the all part of the package do not build with a strange error [1].
This package contain a Build-Depends-Indep part.
I tested it with sbuild and and it was ok last week. (unstable sbuild not
> please file bugs if you find other packages which try to access $HOME during
> the build process.
ok,I will do a bug report.
Cheers
Fred
Hello,
I am preparing the next tango package, so I need to build the doc with lyx.
But then I get this error message.
make[5]: Entering directory '/<>/tango-9.2.0~a+dfsg/build/doc/src'
cd ../../../doc/src; /usr/bin/lyx --export pdf2 tango.lyx
LyX: Creating directory /sbuild-nonexistent/.lyx/
Hello Paul
> Can you please point me to the relevant discussion?
I speak about this [1]
> Actually, I don't think that is in scope of dbconfig-common. I would
> rather expect that MariaDB would provide that functionality. It is
> required for more packages and situations than just those
Hello
thanks a lot for your work on dbconfig-common.
I am the maintainer of tango-db which use dbconfig-common and a mysql database.
It seems that there is currently a discussion about he support of mysql and
mariadb for Debian 9
Do you know if dbconfig-common will integrate a way to switch
Ok, I used dcut
dcut -k 4696e015 rm clblas_2.6-2_amd64.changes
in order to remove the offending file
Cheers
Fred
dgit is a step in this direction.
Yes and it is nice to have meta data (the dgit things) rerpresenting the
packages which can be shared between derivatives.
I'm not sure I entirely understand your situation, but:
Yes I was a bit laid at this moment :)
If you are a downstream, there is no
Hello Ian,
Since we are speaking about workflow.
I work with instituts who want to maintain internaly their own debian packages
and repositories.
The objectif is to maintain sort of 'PPA' in order to be as reactive as
possible when deploying the code internally.
Now from time to time it would
Hi
Wouldn't a p2p system scale better than any server based solution? Also in
regards to cost...
gittorrent[1] would be great for this.
[1]
http://blog.printf.net/articles/2015/05/29/announcing-gittorrent-a-decentralized-github/
Cheers
--
To UNSUBSCRIBE, email to
I do, it's about time we had a decent scripting language in the base
system.
What about haskell as a decent scripting language ?
It seems to me that haskell is a clear win when it comes to put things all
together.
type checking etc...
Fred
--
To UNSUBSCRIBE, email to
Hello, I am the maintainer of python-scientific
How does this differ from the existing python-netcdf package?
I CC the upstream autor of python-scientific, maybe he can clarify this point
but before a question to the netcdf4-python guyes.
Does netcdf4-python will support python3 ?
@Konrad do
Hello,
I am preparing a package for a scientific camera andor3.
This package contain a kernel module for the video grabber.
From the constructor documentation, I need to add the nopat option to the
linux command line.
So I would like to know what is the proper way to customize this command
Hello, I got an FTBFS due to an internal compiler error.
should I fill a bug against gcc ?
should I fill also an RC bug for my package ?
thanks for your help
Frederic
[1]
https://buildd.debian.org/status/fetch.php?pkg=pytangoarch=mipselver=8.1.5-1stamp=1412309891
--
To UNSUBSCRIBE, email to
This has the advantage of being short and downstreams not having lots of
Debian-*
users on their systems possibly confusing users not familiar with
Debian. I'd be nice to standardize on this.
I have the same problem in one of my package. #737956
I would like to rename the system user tango -
Fake it.
UID=$(id -u tango)
GID=$(id -g tango)
deluser tango
adduser tango --uid $UID --gid $GID
I like this fake rename because it cause no troubles to the files already owned
by the tango user
BÙT
in case of an idempotent pre/post scripts.
what happend if I delete the tango users before
# usermod -l newname oldname
(Other things can also be modified at the same time, see the man page.)
thanks a lot
Frederic
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hello Charles
Peer review can help, by making sure that the final controllers (the FTP
Master
team) do not waste their time reporting defects that others could have found.
You can find a process for peer review at the URL below.
https://wiki.debian.org/CopyrightReview
I like a lot the
Thanks a lot for this package.
I would like to maintain inside Debian Python Modules Team,
this package is relevant since is needed by the new binwalk release
(don't know if other packages needs it)
I know at least about two package that could be interested by this dependency.
pyfai and in
Reverse dependencies are anything but unrelated.
Hello julien, from the point of view of the release team.
What should be do now ?
to my opinion, all we have to do is to upload
zeromq3 with this ugly but necessary +really versionnumber
4.0.3+really-3.2.4-1
then the problem should be fixed
Hello,
the zeromq upstream forgot to do an so bump when releasing the 4.x series.
The breakage was discovers quite late so it is now in testing.
the package should be revert to the 3.2.4 version.
you can find all the information about this breakage in the bug #743508.
So my question is how to
It may be that libgc upstream's autogen.sh script is not really 'right' in
some way. But there may well be a lot of upstreams like that, which is
why maintainers need clear guidance on how to deal with this, without
having to become autotools experts. i.e how to determine when they can
just
Hello,
I am the maintainer of the tango package which contain the tango-db binary.
This tango-db provide a service called tango-db which connect to a mysql
database.
I follow the debian-policy to create a dedicated system user for this services.
So I used the tango user which is the name of the
I don't think there is much that can reall be done to fix the
fundamental problem which is that system users and regular users have to
live in the same namespace causing a risk of conflicts.
There are two things I can see you could do to impreove the situation
with your package.
1: Fail
Just use a generic name and be done with it.
sorry, what do you mean by generic ?
The name should not be hardcoded - if it is, patch upstream in each
case and fix it. Don't waste your time and user time on a hacky
workaround - fix the code.
no, the name is not hard coded by the upstream. I
Hello,
I dig a little bit in the debian documentation, and I found this snipset
in the section 9.2 of securing-debian-howto [1]
It is interesting to see the code used to create a system user.
But the step 4 bother me
usermod -c $SERVER_NAME \
-d $SERVER_HOME \
Bonjour,
Je suis en train de travailler sur le paquet spyder. Pour l'ajout du support
python3, j'ai crée un patch qui contient un fichier binaire (une icone).
L'idée pour moi est de préparer un patch contenant tout le necessaire pour que
je puisse ensuite l'envoyer à l'upstream.
J'utilise
Package: wnpp
Severity: wishlist
Owner: Picca Frederic-Emmanuel pi...@synchrotron-soleil.fr
* Package name: guidata
Version : 1.2.2
Upstream Author : pierre.rayb...@cea.fr pierre.rayb...@cea.fr
* URL : http://sourceforge.net/projects/guidata/
* License
Package: wnpp
Severity: wishlist
Owner: Picca Frederic-Emmanuel pi...@synchrotron-soleil.fr
* Package name: guiqwt
Version : 2.0.4
Upstream Author : pierre.rayb...@cea.fr pierre.rayb...@cea.fr
* URL : http://sourceforge.net/projects/guiqwt/
* License
Package: wnpp
Severity: wishlist
Owner: Picca Frederic-Emmanuel pi...@synchrotron-soleil.fr
* Package name: libhkl
Version : 4.0.0
Upstream Author : Picca Frédéric-Emmanuel pi...@synchrotorn-soleil.fr
* URL : http://repo.or.cz/w/hkl.git
* License : (GPL
77 matches
Mail list logo
