Package: sponsorship-requests
Severity: normal
Hi,
(Please Cc me in replies, I am not subscribed to debian-science mailing list)
I am looking for a sponsor for the package libquantum.
It builds those binary packages:
libquantum-dev - library for the simulation of a quantum computer
This is QA upload. I won't be the maintainer of this package.
I just want to improve its quality while it has no maintainer.
Well, you should ask to the QA team then, no ?
Hmm, you are right. Thanks.
--
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of
Hi,
I am looking for a sponsor for updated package elmerfem.
Direct link for download:
http://mentors.debian.net/debian/pool/main/q/qpxtool/qpxtool_0.7.1.002-6.dsc
Other links:
http://mentors.debian.net/package/qpxtool
Sorry for wrong links. Here are correct ones:
http://mentors.debian.net/package/elmerfem
http://mentors.debian.net/debian/pool/main/e/elmerfem/elmerfem_6.1.0.svn.5396.dfsg2-1.dsc
http://anonscm.debian.org/gitweb/?p=debian-science/packages/elmerfem.git
--
To UNSUBSCRIBE, email to
Hi Thomas,
And I can not check your GPG key I have noticed that your key is
signed by nobody.
If possible, please do key signing with other people.
Probably, it is better if it is Debian Developer.
Maybe you could recommend me a way to get my GPG key signed in Tokyo... ?
I am living
Hi,
will we request the package removing from wheezy as well?
I have no final decision yet. I need more opinions. (Cc'ing mailing list)
Problem affects only binary file ElmerGUI.real which provides modern
convenient GUI for pre-processing and post-processing FE models.
But package still
2013-01-27 18:28, D. Haley wrote:
Hello,
Can someone please have a look at the package OpticalRayTracer, and check to
see if it is OK to be uploaded? Im trying to close
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697899 . The git VCS can be
found here:
Hi Julien,
Now almost all salome-* packages from experimental cannot be installed due to
missing dependencies. I do not think that sending multiple bugs (for each
package) is a good idea, so could you comment the current situation in our
mailing list?
Thank you for your work.
Best regards,
Hi,
Now almost all salome-* packages from experimental cannot be installed due
to
missing dependencies. I do not think that sending multiple bugs (for each
package) is a good idea, so could you comment the current situation in our
mailing list?
I haven't had time to work on those
(Cc'ing team and unCc'ing specific bug report)
I fear I will myself forget about the thing, which would be a shame...
Could you add usertags for all your bug reports related to problem of linking
with OpenCASCADE libraries?
...
It should simplify your work in this direction and
will allow
Hi Igor,
This is not a full review, but just few quick notes.
I am looking for a sponsor for my package open-axiom
Have you thought about maintaining this package under umbrella of Debian
Science Team [1][2]? Package looks completely suitable for it.
I am not aware if this was already
Hi,
No need to Cc me: I am subscribed to d-m mailing list.
While Alioth is down, there are
http://cgit.osdyson.org/open-axiom.git/
and
https://github.com/ip1981/open-axiom-debian
Great! This helps.
Let's see.
$ uscan --report
Processing watchfile line for package open-axiom...
Newest
Hi,
Some files in the source tree are licensed under GPL-2+ and Expat licenses.
But I have checked only [1] output. Please have in mind that it includes not
full info and all blocks with Copyright: *No copyright* and
License: UNKNOWN should be checked manually.
[1] licensecheck
Hi,
>>> I will create a team on GitLab. How about "r-packages-team" ?
>> I consider r-pkg-team a more typical name.
>
> Thanks for the suggestion. I have just created the `r-pkg-team` group
> ("Debian R Packages Maintainers") on Salsa.
>
> https://salsa.debian.org/groups/r-pkg-team/
>
> For each
>> Sorry for a late reply to this thread. But I am wondering: why have you
>> decided to make a separate Salsa group instead of making of special
>> subgroup in Debian Science Team group?
>
> Some additional arguments in addition to what Charles said:
>
> * There were R packages from
Hi Andrius,
> I used to own a guest account on Alioth, and with this account I have
> created a few packaging GIT repositories. However, since the transition
> to GitLab-Salsa I am unable to push my commits:
>
> andrius@tasmanijos-velnias cod-tools $ git remote set-url origin
>
Hi,
>> It could be useful to add this link in the description of the team in
>> the salsa page.
>
> Done, thanks for the suggestion !
Sorry, but it looks ugly:
https://salsa.debian.org/explore/groups?utf8=%E2%9C%93=Debian+R+Packages+Maintainers
Please add the link in the end of description.
Hi,
>>> We are now supposed to use the email notifications from GitLab ("Emails on
>>> push" under "Settings -> Integrations").
>>
>> there is a script for this if you don't want to use the web interface (I
>>didn't
>> test it though)
>>
>>
Hi Joris,
> I am a member of the core team of JASP, we develop a GPL'd statistics
> program that aims to replace SPSS while adding bayesian statics to the mix.
> We would like to make this as widely available as possible and therefore
> would like to contribute it to the debian repositories.
>
>
> Use mailing list [1] for discussions with team members. Some info about
> joining to Debian Science team you may find at [2]. Also have in mind that
> git repositories for our packages were recently moved from Alioth [3][4] to
> Salsa [5], and I am not sure that our documentation have been
Hi,
> Bonus question: How can I get debian/changelog, debian/control and
> debian/upstream/metadata without cloning the whole repository?
https://salsa.debian.org/science-team/freecad/raw/master/debian/changelog
https://salsa.debian.org/science-team/freecad/raw/master/debian/control
etc.
Best
Hi Sebastian,
>>> I put the packaging repo on salsa [1], and I'd be happy to move it from
>>> my personal namespace to the Debian Science group, but my understanding
>>> is I don't have the authority to do that. (And I've not yet heard that
>>> Debian Science actually wants the package.)
>>
Hi team,
Tonight I have finally updated our policy manual.
Please check for typos, mistakes, etc..
[1] https://science-team.pages.debian.net/policy/
Best wishes,
Boris
Hi Pierre,
>> You need to register an account on salsa.debian.org and ask for
>> membership of Debian Science team. You also need to create your
>> personal Gitlab token.
>
> Ok, I'am asking for membership of Debian Science team
> together with an account on salsa.debian.org
> Who is managing
Hi Paride and Matteo,
Please do not use mailing list [1] in Maintainer field in debian/control.
There is special mailing list [2] for this purpose. Mailing list [1] is
used for communication between team members and should not be flooded by
automatic emails. There are more than 1000 packages [3]
Hi,
>> one of my friend just requested to join the Debian-science Team.
>> (Serge cohen), but I do not find where I can accep it into the
>> debian-science team ?
>>
> He was already accepted. I changed your status to "owner"
> so you can do it now on your own.
I think that members of group
>>> one of my friend just requested to join the Debian-science Team.
>>> (Serge cohen), but I do not find where I can accep it into the
>>> debian-science team ?
>>
>> He was already accepted. I changed your status to "owner"
>> so you can do it now on your own.
>
> I think that members of
Hi team,
>> Can't we have the Debian Science Maintainers just use
>> debian-science@l.d.o instead of the Alioth address then?
>
> The problem I would have with this (in general) is that d-science@l.d.o
> is then flooded by bug reports, maintenance mails ("package xy
> successfully uploaded to
>> I propose to change the Maintainer: for mpich from "Debian Science
>> Maintainers" which is an Alioth list, to debian-...@lists.debian.org.
>>
>> Any comments or objections?
>
> I would prefer to have all Debian Science package-related e-mails on a
> single list. Given the sort of traffic
29 matches
Mail list logo
