Re: Debian Science Policy, update/migration

[Boris Pek]

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

Re: RFS: dxf2gcode/20170925-7

[Boris Pek]

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.)
>>
>>  If you set the Debian Science team as maintainer and since we agreed
>>  that it fits from the content it is perfectly fine to move it. Just
>>  apply for team membership and you get permission to do this.
>
> I tried to do this but failed.
>
> I don't know if i just missed the right place to click to make this
> happen, or if I as a "Developer" member of the Debian Science team don't
> have sufficient authority, or if there's something else going on...
>
> I went to the salsa page for my repo (listed above), clicked on the
> little gear on the left to go to Settings, clicked Expand on the
> Advanced Settings, and tried to select a new namespace in the Transfer
> Project tab that showed up, but when I searched for "science" it said
> "No matches found".
>
> I then tried to create a new project (by clicking the "+" at the top and
> selecting "New Project"), but again it won't let me pick any namespace
> other than seb_kuzminsky-guest.
>
> So I'm stuck!
>
> Also, I guess my old alioth username of seb_kuzminsky-guest got
> auto-transfered to salsa. Does anyone know if i can change that to just
> seb_kuzminsky, or do i have to remove my account and create a new one
> with a less silly name?

Debian Science Policy Manual was finally updated tonight.
I believe you will find an answer at [1].

[1] https://science-team.pages.debian.net/policy/#idm179

Best wishes,
Boris

Re: Maintaining a package (JASP)

[Boris Pek]

> 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 updated...

As I see now our policy manual is (partially) updated [6], but some pages on
wiki are very outdated [7]. So just write to mailing list when you will have
specific questions.

[6] https://science-team.pages.debian.net/policy/
[7] https://wiki.debian.org/DebianScience/ContributingToDebianScience

Best wishes,
Boris

Re: Maintaining a package (JASP)

[Boris Pek]

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.
>
> To this end I have entered an intent-to-package in the wnpp
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887598) and tried to
> make the software adhere to the standards set by debian-policy.
>
> To actually get it into the repositories we would need to have a sponsor
> is what i've understood. Maybe there is someone in the debian-science team
> that would be willing to assist somewhat in that field?

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 updated...

[1] 
[2] https://wiki.debian.org/DebianScience#How_to_join
[3] https://alioth.debian.org/projects/debian-science/
[4] https://anonscm.debian.org/cgit/debian-science/
[5] https://salsa.debian.org/science-team

Best wishes,
Boris

Re: Question about Salsa API: How to get all projects (including in subgroups) of a team

[Boris Pek]

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 wishes,
Boris

Re: mseed2sac_2.2+ds1-1_amd64.changes is NEW

[Boris Pek]

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] maintained by our
team...

[1] 
[2] 
[3] 
https://qa.debian.org/developer.php?email=debian-science-maintain...@lists.alioth.debian.org

Best regards,
Boris


08.02.2018, 18:24, "Debian FTP Masters" :
> binary:mseed2sac is NEW.
> binary:mseed2sac is NEW.
> source:mseed2sac is NEW.
>
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
>
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
>
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
>
> If you have any questions, you may reply to this email.
>
> [1]: https://ftp-master.debian.org/new.html
>  or https://ftp-master.debian.org/backports-new.html for *-backports

Re: Rheolef moved to Git : problem to download/edit the debian files

[Boris Pek]

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 this ?

First, you are using a wrong mailing list: write to
 instead of
.

Next, read our documentation please:
https://wiki.debian.org/Salsa/Doc#Users:_Login_and_Registration
https://wiki.debian.org/DebianScience#How_to_join

It should decrease the number of questions.

Best wishes,
Boris

Re: Changing maintainer for mpich to debian-hpc

[Boris Pek]

>>  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 that we have on debian-science
> (mostly packaging-related already), I would vote for using
> debian-science as the maintainer address.

There are too huge amount of packages related to Debian Science team. And as
far as I know the most of maintainers are interested only in limited amount of
them. Thus all extra emails will be perceived as a flood. People who do not
have enough free time to sort such flood manually just will stop usage of this
mailing list.

I vote for not mixing of ML for communication with team members with ML for
automatic emails related to packaging activity.

Best wishes,
Boris

Re: Changing maintainer for mpich to debian-hpc

[Boris Pek]

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 localhost", "package xy accepted").
>
> This would make d-science much less readable than with a separated
> mailing list.

Do not be in a hurry to replace MLs at Alioth to anything else until
the proper replacement will be ready. Also have in mind that there
is some work for continuation of Alioth mailing lists:
https://wiki.debian.org/Alioth/MailingListContinuation#Announcement

Best wishes,
Boris

Re: r-pkg-team page on wiki.d.o.

[Boris Pek]

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.

Also you may use two newline symbols to split strings to paragraphs
for better look of: https://salsa.debian.org/r-pkg-team

Best wishes,
Boris

Re: How to get some replacement for a commit list

[Boris Pek]

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)
>>
>> https://salsa.debian.org/mehdi/salsa-scripts/blob/master/emails_on_push.sh
>
> Did this worked for you?
>
>  $ emails_on_push.sh r-pkg-team ti...@debian.org
> Project r-pkg-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service
>
>  $ emails_on_push.sh science-team ti...@debian.org
> Project science-team not found among your owned projects on 
> https://salsa.debian.org/api/v4 service

Just fix the script using idea from:
https://lists.debian.org/debian-devel-games/2018/01/msg00010.html

Best wishes,
Boris

Re: A common group on salsa.debian.org for R packages ?

[Boris Pek]

>>  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 different teams (Debian Science and
> Debian Med currently, DebiChem also has R packages which are
> not yet merged). We want to have a common R team.
>
>   * In Debian there are somehow topic based teams (some are organised
> as Blends like Debian Science and Debian Med) and technique (mostly
> programming language) based teams (Python, Perl, etc.) In many
> cases you can argue whether a package belongs to a certain topic
> (or in which of the several potential topics) or the technical team.
> While R is clearly science oriented Debian Science might be the
> natural place but R is also a programming language. The people who
> contributed to the decision (including me) consider the advantage
> to maintain R packages in a technical team higher than to keep
> everything in Debian Science.

I see. Thanks for an explanation.

Best regards,
Boris

Re: A common group on salsa.debian.org for R packages ?

[Boris Pek]

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 package in the `r-pkg-team`, I propose to give Developer access
> to all the members of the groups Debian, science-team and the future
> Debian med team (no name chosen yet).
>
> It can be done programatically as follows.
>
> curl -X POST --header "Private-Token: $(cat gitlabtoken.txt)" 
> 'https://salsa.debian.org/api/v4/projects/$project_ID/share?group_id=$group_id_access=$access_level'
>
> (See https://docs.gitlab.com/ce/api/projects.html#share-project-with-group
>  and https://salsa.debian.org/help/user/permissions )
>
> It is not possible to make a group member of a group.
>
> Thus, people would only need to ask for membership if they want to
> create a new project (needs Master level), or if they have a guest
> account and are not member of the Science or Med team (that would be
> Developer level).

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?

Best regards,
Boris

Re: Pushing commits to GitLab-Salsa not allowed

[Boris Pek]

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
> g...@salsa.debian.org:science-team/cod-tools.git
> andrius@tasmanijos-velnias cod-tools $ git push
> GitLab: You are not allowed to push code to this project.
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
>
> I have signed up on salsa.debian.org (@merkys-guest) and set up my SSH
> key. Could this be because of me being absent from 'Project members' of
> my package's project
> (https://salsa.debian.org/science-team/cod-tools/project_members)?

Yes.

> If so, could I be added?

Just join to Debian Science Team group:
https://salsa.debian.org/science-team
as a member with Developer level of access:
https://docs.gitlab.com/ee/user/permissions.html

Best wishes,
Boris

Re: how to accept a new memeber.

[Boris Pek]

>>>  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 with Master level of access should not receive
> emails about requests for joining group because they do not have permissions
> to accept these requests. And such emails become just a noise...
>
> Could you report issue to Salsa support team?

https://salsa.debian.org/salsa/support/issues/12

-- 
Boris

Re: how to accept a new memeber.

[Boris Pek]

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 with Master level of access should not receive
emails about requests for joining group because they do not have permissions
to accept these requests. And such emails become just a noise...

Could you report issue to Salsa support team?

Best regards,
Boris

Re: Bug#728360: RFS: open-axiom/1.5.0~svn3056-1

[Boris Pek]

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 --copyright -c . -r . | /usr/lib/cdbs/licensecheck2dep5  
 ../copyright_

 BTW, how should I refer to these terms:
 # As a special exception to the GNU General Public License, if you
 # distribute this file as part of a program that contains a
 # configuration script generated by Autoconf, you may include it under
 # the same distribution terms that you use for the rest of that program.
 ?

You may write something like this:

Files: config/*
Copyright: 1992-2013, Free Software Foundation, Inc
License: GPL-2+ or BSD-3-clause
 These files are free software; you can redistribute them and/or modify
 them under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 2 of the License, or
 (at your option) any later version.
 .
 This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 .
 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
 Foundation, Inc., 51 Franklin Street - Fifth Floor, Boston, MA
 02110-1301, USA.
 .
 As a special exception to the GNU General Public License, if you
 distribute this file as part of a program that contains a
 configuration script generated by Autoconf, you may include it under
 the same distribution terms that you use for the rest of that program.


I have looked at your debian/copyright in git repo. It may be much simpler:
http://paste.debian.net/plain/67414
As you see, all blocks were sorted by license, instead of specific files or
copyright holders.
 
  And how about maintaining this package under umbrella of Debian Science 
 Team?

 I don't mind. What should I do?

Send the join request from [1]. Once admin add you to Alioth team, your name
will appear in the list of members [2]. Have in mind that you will not receive
an email about this, unfortunately.

[1] https://alioth.debian.org/projects/debian-science/
[2] https://alioth.debian.org/project/memberlist.php?group_id=100159

When you will have push access to Debian Science Team repos, we will move your
old git repo to new location and will make a symlink at old location to new
one.

And finally, you should update debian/control in according to Debian Science
Policy Manual [3]. See requirements about Maintainer, Uploaders and Vcs-*
fields.

[3] http://debian-science.alioth.debian.org/debian-science-policy.html
(Have in mind that some information is a bit outdated here.)

That is all, if I have not missed anything.

Best regards,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1061385246...@web10j.yandex.ru

Re: Bug#728360: RFS: open-axiom/1.5.0~svn3056-1

[Boris Pek]

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 version on remote site is 3058, local version is 1.5.0~svn3056+ds
 (mangled local version number 056)
open-axiom: Newer version (3058) available on remote site:
  http://sourceforge.net/p/open-axiom/code/3058/
  (local version is 1.5.0~svn3056+ds, mangled local version number 056)

It looks as a typo in debian/watch file.
Just replace string:
opts=dversionmangle=s/.*svn.(\d+)(.ds.*)?/$1/ \
by string:
opts=dversionmangle=s/.*svn(\d+)(.ds.*)?/$1/ \
And it will work fine.

https://github.com/ip1981/open-axiom-debian/commit/ae0ede2

 Files: debian/*
-Copyright: 2011, Igor Pashev pashev.i...@gmail.com
+Copyright: 2013, Igor Pashev pashev.i...@gmail.com

I suppose it should be:
+Copyright: 2011-2013, Igor Pashev pashev.i...@gmail.com

Also why did you choose WTFPL-2 license for the package?
Usually it is good idea to use the same license as program uses,
especially in cases with permissive licenses like BSD.
This is just a question. But if you change it, your d/copyright
will be a bit simpler and shorter.

These copyright holders are still not listed in your d/copyright:
Leslie Lamport
Free Software Foundation, Inc
X Consortium
M.Bronstein and INRIA

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 --copyright -c . -r . | /usr/lib/cdbs/licensecheck2dep5  
../copyright_

Except small notes above your package looks fine for uploading.


And how about maintaining this package under umbrella of Debian Science Team?
Do not think that I am asking something strange. Debian has a very good
tendency of increasing the number of team-maintained packages [2].

If you choose to maintain this package in the team, it will not change your
workflow too much. You may just move your VCS repo and update d/control a bit,
and ignore other team-related features. As a bonus you will find many DDs
interested in sponsoring your package, in helping with patches, etc.

[2] http://www.lucas-nussbaum.net/blog/wp-content/uploads/2013/03/comaint.png

Best regards,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/207801384456...@web20m.yandex.ru

Re: Bug#728360: RFS: open-axiom/1.5.0~svn3056-1

[Boris Pek]

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 discussed earlier. If yes, please give me a
link to that thread. If not, consider this mail as an official invitation. =)

[1] https://wiki.debian.org/DebianScience
[2] http://debian-science.alioth.debian.org/debian-science-policy.html

   Changes since the last upload:

   * New upstream version.
   * Use xz compression for both source tarball and packages
   * Require g++ = 4.7 for C++11
   * Refreshed patches
   * touch aclocal.m4 -r configure.ac to avoid rebuilding aclocal.m4 which
 requires aclocal 1.13
   * Do not patch configure.ac, but override variables in Makefiles (due to
 automake 1.13 too)
   * Require SBCL
   * Enable hardening (include /usr/share/dpkg/buildflags.mk for build flags)
   * Use dh-buildinfo
   * Override hardening-no-relro on usr/lib/open-axiom/bin/AXIOMsys
   * Build depends on autotools-dev to update config.*
   * Bump standards version 3.9.3 → 3.9.4, no changes

Personally I prefer to look at commits in git repo. But git repo [3] of this
package is outdated. Please push your recent changes there.

Also it would be nice if you added git tags for package versions which were
uploaded to Debian archive earlier. Usually they looks like debian/${VER}.
Signed tags are welcome.

[3] http://anonscm.debian.org/gitweb/?p=pkg-open-axiom/pkg-open-axiom.git

Please add few screenshots with examples of using open-axiom to [4]. Even
screenshots of console applications are useful.

[4] http://screenshots.debian.net/

You have never used tarballs with stable releases for this package, so your
current debian/watch file is useless. Please update it for checking svn
revision. You may find examples at [5] or at [6].

[5] https://wiki.debian.org/debian/watch/
[6] 
http://anonscm.debian.org/gitweb/?p=debian-science/packages/elmerfem.git;a=blob;f=debian/watch;hb=HEAD

Your get-orig-source in debian/rules violates Debian Policy §4.9:
This target may be invoked in any directory...

Just replace:
SRC_VERSION  := $(shell dpkg-parsechangelog | awk '/^Version:/ {sub(/-[^-]*/, 
, $$2); print $$2}')
by something like this:
DEBIAN_PATH  := $(abspath $(dir $(firstword $(MAKEFILE_LIST
SRC_VERSION  := $(shell dpkg-parsechangelog -l$(DEBIAN_PATH)/changelog | awk 
'/^Version:/ {sub(/-[^-]*/, , $$2); print $$2}')

String README* in debian/open-axiom.docs is quite useless. Did you have
debian/README* in mind or anything else?

Please use lintian with `-ivIE --pedantic` options for checking packages.

These lintian tags may be easily fixed:
I: open-axiom source: vcs-field-not-canonical 
http://git.debian.org/git/pkg-open-axiom/pkg-open-axiom.git 
http://anonscm.debian.org/git/pkg-open-axiom/pkg-open-axiom.git
I: open-axiom source: vcs-field-not-canonical 
http://git.debian.org/?p=pkg-open-axiom/pkg-open-axiom.git 
http://anonscm.debian.org/gitweb/?p=pkg-open-axiom/pkg-open-axiom.git
I: open-axiom: desktop-entry-lacks-keywords-entry 
usr/share/applications/open-axiom.desktop

Please use [DEP-3] to fix these lintian notes:
I: open-axiom source: quilt-patch-missing-description no-missing-messages.patch
I: open-axiom source: quilt-patch-missing-description 
non-static-open-axiom-binary.patch

[DEP-3] http://dep.debian.net/deps/dep3/

You may want to fix as well:
I: open-axiom: hardening-no-fortify-functions usr/lib/open-axiom/bin/AXIOMsys
But this is optional.

Please update your debian/copyright file in according to Copyright format 1.0:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
You have already made a preliminary work, so just finish it.
Also some copyright holders are not listed in this file now.
This file is very important and should be always in actual state.

I have not looked into source code and debdiff between versions yet.
More remarks are possible.

Best regards,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/185291383220...@web26m.yandex.ru

Re: usertags for problem of linking with OpenCASCADE libraries

[Boris Pek]

(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 to observe the scale of problem in whole.

 This is true and is in itself a good reason for adding usertags.

 Which e-mail address do you suggest as user?

debian-science-maintain...@lists.alioth.debian.org

 Which usertag name do you propose?

opencascade-linking-issues

 Something like opencascade-incomp?

Looks good for me as well.

Best wishes,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/325881375694...@web5g.yandex.ru

Re: salome-* packages in experimental

[Boris Pek]

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 packages in the last few months.  I
 suspect they'd at least need a rebuild against newer opencascade and
 paraview, but don't know how many changes (if any) would be required for
 that.

Thanks for the explanation.

 I'll probably have to focus on #680738 at some point soon, and then
 update the packages.

Yes, I am aware of this problem. Unfortunately, I do not see how it could be
solved now. I have faced with the same problem in the package elmerfem and
have posted a message on their forum [1]. But there are no progress yet...

[1] http://dev.opencascade.org/index.php?q=node/525

Best wishes,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/522651372171...@web12e.yandex.ru

salome-* packages in experimental

[Boris Pek]

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,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/248781371499...@web21h.yandex.ru

Re: Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries

[Boris Pek]

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 includes old binaries ElmerFront and ElmerPost with
ugly graphical interfaces based on Tk library. I have not tested them
myself, but they should provide similar functionality.

Solver and libraries do not use graphical toolkits at all.

So if we remove problematic binary from the package, program will become
very inconvenient but not useless.

Any votes to do this?

Best regards,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/31491359285...@web28h.yandex.ru

Re: OpticalRayTracer upload

[Boris Pek]

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:
  
 http://anonscm.debian.org/gitweb/?p=debian-science/packages/opticalraytracer.git

  Thanks.

Hi,

I believe that this message should be send to debian-science mailing list
instead of debian-science-maintainers.

Best wishes,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1790981359306...@web29e.yandex.ru

Re: Looking for a sponsor for the ViSP package

[Boris Pek]

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 in Ibaraki-ken right now.
 I am in the process of having my key signed by a non Debian developer 
 although.

These links should be useful for you:
http://wiki.debian.org/Keysigning/Coordination
http://wiki.debian.org/Keysigning/Offers#JP

Best wishes,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51711355992...@web30g.yandex.ru

RFS: elmerfem/6.1.0.svn.5396.dfsg2-1 [RC] -- Open Source Finite Element Software for Multiphysical Problems

[Boris Pek]

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
  http://anonscm.debian.org/gitweb/?p=debian-science/packages/elmerfem.git

Changes in the package:

elmerfem (6.1.0.svn.5396.dfsg2-1) unstable; urgency=low

  * Team upload.
  * Delete non-free and unnecessary files from tarball:
- ElmerGUI/Application/plugins/tetgen.h
- misc/tetgen_plugin/plugin/*
(Closes: #687954)
  * Add debian/patches/no-tetgen.patch: fix build without tetgen plugin.
  * Update debian/copyright:
- update debian/copyright in according to Copyright format 1.0
- add missed copyright holders and licenses

I would be glad if someone uploaded this package for me.

When package is uploaded I'll send unblock request.

Best regards,
Boris


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/92961348172...@web26d.yandex.ru

Re: RFS: elmerfem/6.1.0.svn.5396.dfsg2-1 [RC] -- Open Source Finite Element Software for Multiphysical Problems

[Boris Pek]

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 debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/99251348173...@web12e.yandex.ru

Re: RFS: libquantum/1.1.0-2 [QA] -- library for the simulation of a quantum computer

[Boris Pek]

  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 unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/392931340090...@web14g.yandex.ru

RFS: libquantum/1.1.0-2 [QA] -- library for the simulation of a quantum computer

[Boris Pek]

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 
(development files)
  libquantum7 - library for the simulation of a quantum computer

To access further information about this package, please visit the following 
URL:
  http://mentors.debian.net/package/libquantum

Direct link for download:
  
http://mentors.debian.net/debian/pool/main/libq/libquantum/libquantum_1.1.0-2.dsc

Changes in the package:

libquantum (1.1.0-2) unstable; urgency=low

  * QA upload.
  * Set maintainer to Debian QA Group (see #674883).
  * Deleted Vcs-* fields from debian/control.
  * Package was switched to source format 3.0 (quilt).
  * Added build dependency from autotools-dev.
  * Bumped Standards-Version to 3.9.3.
  * debian/rules was updated:
- now dh is used instead of direct dh_* commands
- used hardening flags in compiler options
- added section get-orig-source (uscan is used)
- fixed FTBFS because of outdated config.{sub,guess} (Closes: #572527)
  * Fixed such lintian errors, warnings and wishes:
+ libquantum source:
  - binary-control-field-duplicates-source field section in package
libquantum7
  - duplicate-short-description libquantum-dev libquantum7
  - outdated-autotools-helper-file config.sub 2004-11-30
  - outdated-autotools-helper-file config.guess 2004-11-12
  - debhelper-but-no-misc-depends libquantum-dev
  - debhelper-but-no-misc-depends libquantum7
  - missing-debian-source-format
  - debian-rules-missing-recommended-target build-arch
  - debian-rules-missing-recommended-target build-indep
  - ancient-standards-version 3.8.1 (current is 3.9.3)
+ libquantum7:
  - hardening-no-fortify-functions usr/lib/libquantum.so.7.0.0
+ libquantum-dev:
  - non-empty-dependency_libs-in-la-file usr/lib/libquantum.la

I would be glad if someone uploaded this package for me.

Also I need DD's help to create git repository for this package in collab-maint.
I followed instructions from [1] and sent the request to join. Now I am waiting
for reply.

Best regards,
Boris

[1] http://wiki.debian.org/Alioth/PackagingProject


-- 
To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/307501340060...@web28e.yandex.ru