Re: Could you change CI/CD configuration file for gr-framework repository?

Hi, 2024年8月18日(日) 0:15 Nilesh Patra : > > Hi kentaro, > > > On 08/17/2024 10:43 AM IST Kentaro Hayashi wrote: > > I'm now working on packaging gr-framework, [1] then > > pushed recent WIP repository to salsa.d.o [2]. > > > > But I can

Re: Could you change CI/CD configuration file for gr-framework repository?

Hi kentaro, > On 08/17/2024 10:43 AM IST Kentaro Hayashi wrote: > I'm now working on packaging gr-framework, [1] then > pushed recent WIP repository to salsa.d.o [2]. > > But I can't finish to run CI/CD yet because path of CI/CD > configuration file is not s

Could you change CI/CD configuration file for gr-framework repository?

Hi, I'm now working on packaging gr-framework, [1] then pushed recent WIP repository to salsa.d.o [2]. But I can't finish to run CI/CD yet because path of CI/CD configuration file is not set. Could you set CI/CD configuration file to "debian/salsa-ci.yml" for gr-framework

Re: Broken package in testing repository

Hi Alexander, Hugo, Graham On Wed, 25 Mar 2020, 21:45 Alexander van der Meij, < vandermeij.t...@gmail.com> wrote: > > > > Hi Debian Science team, > > As described in bug 951634 > , Debian is > currently distributing a broken development b

Re: Broken package in testing repository

Control: severity -1 serious Hi Alexander On Wed, 25 Mar 2020 at 18:15, Alexander van der Meij wrote: > As described in bug 951634, Debian is currently distributing a broken > development build of the software of which I am the developer; gummi. > > Hereby my request to either bump the package

Broken package in testing repository

Hi Debian Science team, As described in bug 951634 , Debian is currently distributing a broken development build of the software of which I am the developer; gummi. Hereby my request to either bump the package to the stable (0.8.1) release

Re: Please push changes of qelectrotech 1:0.7.0-1 to Git repository

Oops, I missed that. Yes, the name should be "debian" or > "master" by team policy, not "debian/master". I wonder, > whether science team should adopt DEP-14 layout instead? If you give an estimation what time this would save / otherwise advantage we would gain

Re: Please push changes of qelectrotech 1:0.7.0-1 to Git repository

> debian/master. Salsa tells me, that debian/master were the default branch. Also, when I "git clone" the repo, I'm automatically in debian/master. Did you do something different maybe? > Its actually not "my fix" I simply realised long term unmerged merge > req

Re: Please push changes of qelectrotech 1:0.7.0-1 to Git repository

er looked for debian/master. If you have good reasons to stick to the current branch layout (where master IMHO is at best confusing) could you please at least make debian/master default branch to make sure random team members who might clone that repository do not trap into the same pitfall like I d

Re: Please push changes of qelectrotech 1:0.7.0-1 to Git repository

On 2020-03-06 12:10, Andreas Tille wrote: > when I went through some merge requests (also from you) I realised > that there is even a new upload of qelectrotech but its not pushed > to Git. Can you please push? What exactly is missing? It looks like everything is there, or not? PS: I believe, th

Re: Please push changes of qelectrotech 1:0.7.0-1 to Git repository

Quoting Andreas Tille : when I went through some merge requests (also from you) I realised that there is even a new upload of qelectrotech but its not pushed to Git. Can you please push? Thanks for the heads-up! I'll look into that when I'm at home! Cheers

Please push changes of qelectrotech 1:0.7.0-1 to Git repository

Hi Martin, when I went through some merge requests (also from you) I realised that there is even a new upload of qelectrotech but its not pushed to Git. Can you please push? Kind regards Andreas. PS: I have **NO** interest in this specific package at all - I was just astonished about the l

Re: admin needed to reset git repository: dlib

> done! thanks! :) cheers, Hugo -- Hugo Lefeuvre (hle)|www.owl.eu.com RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C signature.asc Description: PGP signature

Re: admin needed to reset git repository: dlib

Hi Hugo, done! Regards Anton Am Mi., 24. Juli 2019 um 03:09 Uhr schrieb Hugo Lefeuvre : > > Hi, > > I'm working on dlib packaging and messed up with the git repository. I > imported a badly repacked version a new upstream release and fixing it by > hand would be too l

admin needed to reset git repository: dlib

Hi, I'm working on dlib packaging and messed up with the git repository. I imported a badly repacked version a new upstream release and fixing it by hand would be too long. It would also make the git history very ugly. Since I can't force push on protected branches, I worked on m

Re: spaCy: Create repository, merge bugs

On Thu, Nov 29, 2018 at 03:06:14PM +0100, Andreas Tille wrote: > > The dependency chain is basically ready to be uploaded. Specifically, > > for thinc and spaCy, please drop my name from control if there is any. > (Uhmmm, I see I left it on thinc when uploading to new - I'll fix it in > Git meanwhi

Re: spaCy: Create repository, merge bugs

Hi Lumin, On Thu, Nov 29, 2018 at 02:05:33AM +, Mo Zhou wrote: > Hi Andreas, > > Please always search on Salsa before really starting to package any > dependency of spaCy. IIRC I've finished nearly all the dependencies, > except for thinc. There are around ten packages but I aborted the whole

Re: spaCy: Create repository, merge bugs

to be uploaded. Specifically, for thinc and spaCy, please drop my name from control if there is any. On Wed, Nov 28, 2018 at 09:42:30AM +0100, Andreas Tille wrote: > Control: merge 894629 835854 > > I have created a git repository for spacy at > > https://salsa.debian.org/science-team

spaCy: Create repository, merge bugs

Control: merge 894629 835854 I have created a git repository for spacy at https://salsa.debian.org/science-team/spacy since I might need python3-spacy for one of my target packages. Next step should probably be to package spaCy predependency https://github.com/explosion/cymem

Re: Git repository of kbibtex uses branches instead of tags and is most probably outdated

, 2018 at 11:08 AM Andreas Tille wrote: > > > > Hi again Bastien, > > > > since I think it is a good idea to fix Vcs fields in our packages and do > > a new upload of kbibtex I would volunteer to do this work. However, I > > admit since I'm confused by th

Re: Git repository of kbibtex uses branches instead of tags and is most probably outdated

confused by the current kbibtex repository I'm tempted > to recreate it via: > > gbp import-dscs --debsnap --pristine-tar kbibtex > > What do you think about this? > > Kind regards > >Andreas. > > On Mon, Sep 24, 2018 at 03:42:22PM +0200, Andreas

Re: Git repository of kbibtex uses branches instead of tags and is most probably outdated

Hi again Bastien, since I think it is a good idea to fix Vcs fields in our packages and do a new upload of kbibtex I would volunteer to do this work. However, I admit since I'm confused by the current kbibtex repository I'm tempted to recreate it via: gbp import-dscs --debsnap

Git repository of kbibtex uses branches instead of tags and is most probably outdated

Hi Bastien, I stumbled upon the Git repository of kbibtex on Salsa[1]. It is using branches where tags should be used. According to Debian Science policy[2] a repository should usually look like $ git branch * master pristine-tar upstream and package uploads should be marked by git tag

Re: Committing to a team-maintained package repository

Mattia Rizzolo wrote on 16/07/2018: > On Sat, Jul 14, 2018 at 07:56:08PM +0200, Paride Legovini wrote: >> One last question. Do we actually need these lines: >> >> include /usr/share/dpkg/architecture.mk >> ifeq ($(origin CC),default) >> CC := $(DEB_HOST_GNU_TYPE)-gcc >> endif >> >> in d/rules? >>

Re: Committing to a team-maintained package repository

On Sat, Jul 14, 2018 at 07:56:08PM +0200, Paride Legovini wrote: > One last question. Do we actually need these lines: > > include /usr/share/dpkg/architecture.mk > ifeq ($(origin CC),default) > CC := $(DEB_HOST_GNU_TYPE)-gcc > endif > > in d/rules? They are suggested here: > > https://wiki.debi

Re: Committing to a team-maintained package repository

Hi Andreas, thanks a lot for reviewing my changes. Andreas Tille wrote on 14/07/2018: > Hi Paride, > > On Wed, Jul 11, 2018 at 03:18:08PM +0200, Paride Legovini wrote: >>> just go for it push and sak for sponsoring here. >> >> I would be glad if you could review my commits here: >> >> https://sal

Re: Committing to a team-maintained package repository

Hi Paride, On Wed, Jul 11, 2018 at 03:18:08PM +0200, Paride Legovini wrote: > > just go for it push and sak for sponsoring here. > > I would be glad if you could review my commits here: > > https://salsa.debian.org/science-team/libmseed > > I did more changes than I initially thought, so I left

Re: ros-urdf repository in salsa

On Fri, Jul 13, 2018 at 01:53:15PM +0200, Andreas Tille wrote: > > Another question is if it's a bug in salsa, or just a mistake in the > > creation of > > the repo. > > It happened to me in the past when I was using an erroneous script to create > a repository.

Re: ros-urdf repository in salsa

public. > > Please could you change it? Done. > Another question is if it's a bug in salsa, or just a mistake in the creation > of > the repo. It happened to me in the past when I was using an erroneous script to create a repository. Since I've fixed that scri

ros-urdf repository in salsa

Hi Andreas and Anton, please could you help us in one stupid thing in salsa? Some of you, or me, or I don't know who, created a ros-urdf project. The debian science VIP people ;-) are the owners and we would like to change the visibility from private to public. Please could you change it? Anot

Re: Committing to a team-maintained package repository

Andreas Tille wrote on 04/07/2018: > Hi Paride, > > just go for it push and sak for sponsoring here. Hi Andreas, I would be glad if you could review my commits here: https://salsa.debian.org/science-team/libmseed I did more changes than I initially thought, so I left the package UNRELEASED for

Re: Committing to a team-maintained package repository

debian.org/science-team/libmseed > > and doing a (sponsored) team upload. As a group member ("Developer" > gitlab role), I have write access to the repository [1], but I am not > used to pushing commits for packages I do not (co)maintain. Should I > just proceed, or is

Committing to a team-maintained package repository

Hi, I'd like to fix #890571, and I think I know how [0]. This means committing to: https://salsa.debian.org/science-team/libmseed and doing a (sponsored) team upload. As a group member ("Developer" gitlab role), I have write access to the repository [1], but I am not used to push

Re: [Debichem-devel] Membership and permissions for repository creation on salsa

Dear Daniel, On 04/13/2018 01:34 PM, Daniel Leidert wrote: > We basically follow the same role principle as described in the debian- > science policy. To create a new project, you can simply ask. Another > possibility is to create the project in your personal workspace. As soon > as you find it re

Re: [Debichem-devel] Membership and permissions for repository creation on salsa

Hi Andrius, > I am a member of Debian Science Team and Debichem, and as a "Member" I had > permissions to create repositories on anonscm.debian.org in both projects. > However, on salsa.debian.org I am "Developer", therefore I can not create > new repositories in neither of the projects. How can I

Re: [Debichem-devel] Membership and permissions for repository creation on salsa

Dear Boris, On 04/12/2018 11:27 AM, Boris Pek wrote: > It is briefly described in Debian Science Policy Manual: > https://science-team.pages.debian.net/policy/#idm145 thanks for the link. I was not aware of this change of the policy. Best wishes, Andrius -- Andrius Merkys Vilnius University In

Re: Membership and permissions for repository creation on salsa

Hi Andrius, > I am a member of Debian Science Team and Debichem, and as a "Member" I had > permissions to create repositories on anonscm.debian.org in both projects. > However, on salsa.debian.org I am "Developer", therefore I can not create > new repositories in neither of the projects. How can I

Membership and permissions for repository creation on salsa

Hello, I am a member of Debian Science Team and Debichem, and as a "Member" I had permissions to create repositories on anonscm.debian.org in both projects. However, on salsa.debian.org I am "Developer", therefore I can not create new repositories in neither of the projects. How can I contribut

Re: What's the procedure to create a new repository of a package for Debian Science on Salsa

matters) and did > > $ curl -f > "https://salsa.debian.org/api/v4/projects?private_token=MY_SALSA_TOKEN"; > --data "path=ipe-tools&namespace_id=2136&description=convert FIG files to XML > files for ipe&visibility=public" > curl: (22) The request

Re: What's the procedure to create a new repository of a package for Debian Science on Salsa

quested URL returned error: 400 Bad Request Is there anything wrong with this call? (I intended to create a repository for ipe-tools - see #866435) Kind regards Andreas. -- http://fam-tille.de

Re: What's the procedure to create a new repository of a package for Debian Science on Salsa

description=DESCRIPTION&visibility=public" Best regards Anton 2018-01-07 21:33 GMT+01:00 Andreas Tille : > Hi, > > I'd like to create a new repository on Salsa. On Alioth we used > > ssh git.debian.org "cd /git/debian-science; ./setup-repository > $DEBPK

What's the procedure to create a new repository of a package for Debian Science on Salsa

Hi, I'd like to create a new repository on Salsa. On Alioth we used ssh git.debian.org "cd /git/debian-science; ./setup-repository $DEBPKGNAME \"$SHORTDESC\"" Is there some similar equivalent I could use in a script on Salsa? Kind regards Andreas. -- http://fam-tille.de

please push the changes done to src:mathgl to the git repository

As written in the subject. Please remember to always push what you do, especially what you upload. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : La

Re: packaging: is keeping debian/ files in an upstream repository a good idea?

On 30 June 2017 at 09:04, Kay F. Jahnke <_...@yahoo.com> wrote: > Is it a good idea to put the debian folder and it's contents under version > control in my upstream repository, or should I have these files exclusively > in the alioth repository? It is recommended to ke

packaging: is keeping debian/ files in an upstream repository a good idea?

│ └── format ├── vspline-dev.install ├── vspline-example.install └── watch Is it a good idea to put the debian folder and it's contents under version control in my upstream repository, or should I have these files exclusively in the alioth repository? with regards Kay F. Jahnke

Minsky DPKG repository

Please note that the information regarding the Minsky software on the page http://blends.debian.org/science/tasks/economics can be updated to note that there are Debian packages available. These can be found at http://download.opensuse.org/repositories/home:/hpcoder1/. The principal contact for the

Re: Please use Git repository layout as described in Debian Science policy

On Tue, Apr 05, 2016 at 12:22:46AM +0200, Thomas Schiex wrote: > Dear Andreas > > When I run the lintian command with a -I to get informational messages I think my advise was to use "-i" (lower case) to get more information how to fix the lintian issues. > and on both the binary and source chang

Re: Please use Git repository layout as described in Debian Science policy

Hi Thomas, On Tue, Apr 05, 2016 at 12:22:46AM +0200, Thomas Schiex wrote: > > When I run the lintian command with a -I to get informational messages > and on both the binary and source changes files, I still miss a > significant subset of the messages and more precisely these ones: > > >> I: tou

Re: Please use Git repository layout as described in Debian Science policy

Dear Andreas When I run the lintian command with a -I to get informational messages and on both the binary and source changes files, I still miss a significant subset of the messages and more precisely these ones: >> I: toulbar2 source: vcs-field-uses-insecure-uri vcs-git >> git://anonscm.debian

Re: Please use Git repository layout as described in Debian Science policy

On 04/04/16 17:21, Andreas Tille wrote: > Hi Thomas, > > On Mon, Apr 04, 2016 at 04:35:42PM +0200, Thomas Schiex wrote: >> Hello Andreas, >> >> I tried to scrupulously follow the debian-science git repository >> instructions. I modified the debian/control fil

Re: Please use Git repository layout as described in Debian Science policy

Hi Thomas, On Mon, Apr 04, 2016 at 04:35:42PM +0200, Thomas Schiex wrote: > Hello Andreas, > > I tried to scrupulously follow the debian-science git repository > instructions. I modified the debian/control file as indicated and setup > a new git repo on alioth at > > de

Please use Git repository layout as described in Debian Science policy

Hi Thomas, I had a look into the repository of toulbar2[1] since you asked for sponsering of the package. I noticed that it does not follow the repository layout as specified in the Debian Science policy[2] and also the control file diverges from Debian Science policy (Maintainer should be the

kbibtex Git repository is lacking debian packaging

Hi, I did gbo-clone git://git.debian.org/git/debian-science/packages/kbibtex.git and got just upstream code without any debian/ dir. I think that's not really helpful and I wonder whether anybody has a clone to restore the packaging work. If there is no chance to restore the packaging commit

Re: How to create a Git repository in Debian Science (Was: Jmol: Seeking new maintainer or considering removal)

run git-buildpackage without downloading the tarball themselves which would be stupid since nearly all information is in the Repository. This also will create the missing branch. > and as expected, there are new files (or deletions) to commit. > Which branch should I select for commits now?

How to create a Git repository in Debian Science (Was: Jmol: Seeking new maintainer or considering removal)

e last packaged version is available by the tag 'v3.1.7' > > I tried to watch the directory /git/debian-science in git.debian.org > It provides no script setup-repository, and applying blindly > ../debian-med/setup-repository would be a mistake since a few parts of > that sc

Re: Yet another broken git repository: isabelle

Hi, On Wed, Jun 13, 2012 at 04:44:07PM +0200, Lionel Elie Mamane wrote: > Yes: > > $ git clone > ssh://lmam...@vasks.debian.org/srv/git.debian.org/git/debian-science/packages/isabelle.git > Cloning into isabelle... > remote: Counting objects: 4079, done. > remote: Compressing objects: 100% (2566/

Re: Yet another broken git repository: isabelle

On Wed, Jun 13, 2012 at 04:08:55PM +0200, Andreas Tille wrote: > On Wed, Jun 13, 2012 at 03:44:36PM +0200, Lionel Elie Mamane wrote: >>> Would you mind fixing the Git repository anyway >> I don't know what's wrong with it. Your guess is as good as mine. > Are

Re: Yet another broken git repository: isabelle

ess. > > Yes, that's why the git repo is available. > > > Would you mind fixing the Git repository anyway > > I don't know what's wrong with it. Your guess is as good as mine. Are you able to commit the change I proposed (which is just mentioning author and date

Re: Yet another broken git repository: isabelle

to package Isabelle in Debian, and I've >> closed the associated ITP. > A closed ITP does not mean that the previous work becomes useless. Yes, that's why the git repo is available. > Would you mind fixing the Git repository anyway I don't know what's wrong wi

Re: Yet another broken git repository: isabelle

ackage / PPA whatever. Would you mind fixing the Git repository anyway or do you think it makes more sense to remove it at all? We are currently listing it as prospective package in the mathematics task. Do you think it might be an interesting hint for users anyway (we could add a remark menti

Re: Yet another broken git repository: isabelle

On Wed, Jun 13, 2012 at 11:17:46AM +0200, Andreas Tille wrote: > besides the fact that it seems questionable to work on some > packaging which was not touched for nearly 4 years (so some status > update of the maintainers would be welcome) Upstream is very opposed to any kind of packaging of Isab

Yet another broken git repository: isabelle

Hi, besides the fact that it seems questionable to work on some packaging which was not touched for nearly 4 years (so some status update of the maintainers would be welcome) I stumbled upon another broken Git repository when trying to fix things the machine readable gatherer was warning about

Re: Another broken Git repository

On 06/12/2012 08:39 AM, Charles Plessy wrote: > Le Tue, Jun 12, 2012 at 08:33:27AM +0200, Michael Wild a écrit : >> >> Ah, that would explain it. Just out of curiosity: where should I have >> found this information? > > http://wiki.debian.org/Alioth > > Cheers, > Thanks Michael -- To UNSUBS

Re: Another broken Git repository

Le Tue, Jun 12, 2012 at 08:33:27AM +0200, Michael Wild a écrit : > > Ah, that would explain it. Just out of curiosity: where should I have > found this information? http://wiki.debian.org/Alioth Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi

Re: Another broken Git repository

On 06/12/2012 08:20 AM, Charles Plessy wrote: > Le Tue, Jun 12, 2012 at 08:09:43AM +0200, Michael Wild a écrit : >> >> For some time now I can't do anything when I log in to alioth.debian.org >> since it seems that /srv/git.debian.org is mounted read-only. E.g. my >&

Re: Another broken Git repository

Le Tue, Jun 12, 2012 at 08:09:43AM +0200, Michael Wild a écrit : > > For some time now I can't do anything when I log in to alioth.debian.org > since it seems that /srv/git.debian.org is mounted read-only. E.g. my > repository (viennacl.git) is missing the cia-project hook entry,

Re: Another broken Git repository

On 06/10/2012 04:58 PM, David Bremner wrote: > Andreas Tille writes: > >> As a Git beginner I think there are many powerful features in Git but >> also many ways to end up with a broken repository. That's a bit >> frustrating, thought. Any hint? > > I gues

Re: Another broken Git repository

Andreas Tille writes: > As a Git beginner I think there are many powerful features in Git but > also many ways to end up with a broken repository. That's a bit > frustrating, thought. Any hint? I guess mycae-guest did not use the setup-repository script. I have run /usr/

Re: Yet another way to break a Git repository

Andreas Tille writes: > Hi, > > seems I can prove my point that Git might end up with broken repository > in several ways: > > $ git clone git+ssh://git.debian.org/git/debian-science/packages/vrr.git > As discussed previously, I have removed this repo. d -- To UNSUBSC

Re: Yet another way to break a Git repository

Andreas Tille writes: > Hi, > > seems I can prove my point that Git might end up with broken repository > in several ways: > > $ git clone git+ssh://git.debian.org/git/debian-science/packages/vrr.git Didn't we already discuss this repo? d -- To UNSUBSCRIBE, email

Re: Another broken Git repository

> > > and did some small cosmetic changes (Vcs fields are broken and thus the > > recently announced machine-readable gatherer stumbles upon it). Then I > > tried to push: > > > > remote: error: refusing to update checked out branch: refs/heads/master > > rem

Re: Another broken Git repository

d machine-readable gatherer stumbles upon it). Then I > tried to push: > > remote: error: refusing to update checked out branch: refs/heads/master > remote: error: By default, updating the current branch in a non-bare > repository > remote: error: is denied, because it will make the

Yet another way to break a Git repository

Hi, seems I can prove my point that Git might end up with broken repository in several ways: $ git clone git+ssh://git.debian.org/git/debian-science/packages/vrr.git some small changes $ git diff HEAD^^ HEAD diff --git a/debian/changelog b/debian/changelog index b8b0c1c..03d7721 100644 --- a

Another broken Git repository

non-bare repository remote: error: is denied, because it will make the index and work tree inconsistent remote: error: with what you pushed, and will require 'git reset --hard' to match remote: error: the work tree to HEAD. remote: error: remote: error: You can set 'receive.de

Re: udav in debian-science repository (was: Re: Re: mathgl upload)

Great! Will do! And then will look if I find some time to update to > newer upstream version (0.6.3) is available, but needs new mathgl. I just uploaded it (a few minutes ago). > btw, could need some help with commit-messages not showing up on > #debian-science channel. You have to configure y

Re: udav in debian-science repository (was: Re: Re: mathgl upload)

Le mercredi 11 août 2010 à 08:20 +0200, Salvatore Bonaccorso a écrit : > Hi Sylvestre > > On Wed, Aug 11, 2010 at 06:33:42AM +0200, Sylvestre Ledru wrote: > > @Salvatore > > Could you move this package under the Debian Science umbrella ? > > Yes I have. Is it done the correct way? I followd the

Re: udav in debian-science repository (was: Re: Re: mathgl upload)

Hi Sylvestre On Mon, Aug 16, 2010 at 08:22:40PM +0200, Sylvestre Ledru wrote: > Le mercredi 11 août 2010 à 08:20 +0200, Salvatore Bonaccorso a écrit : > > Hi Sylvestre > > > > On Wed, Aug 11, 2010 at 06:33:42AM +0200, Sylvestre Ledru wrote: > > > @Salvatore > > > Could you move this package unde

udav in debian-science repository (was: Re: Re: mathgl upload)

Hi Sylvestre On Wed, Aug 11, 2010 at 06:33:42AM +0200, Sylvestre Ledru wrote: > @Salvatore > Could you move this package under the Debian Science umbrella ? Yes I have. Is it done the correct way? I followd the workflow email on debian-science list, and it is available under packages/udav.git I

Re: created the tango.git repository

Le Mon, 17 Aug 2009 12:44:48 +0200, PICCA Frédéric-Emmanuel a écrit : Sorry I miss spell the name of the repository tanog.git -> tango.git I hope someone will give me good advices for this package. thanks Frederic -- GPG public key 1024D/A59B1171 2009-08-11 fingerprint = 1688 A

created the tanog.git repository

Hello I have just created the debian-science/packages/tango.git repository on git.debian.org to work on the Tango Control-System http://tango-controls.org which is part of the data-acquisition meta package. This software is not yet part of the official debian (it already needs some work to be

Added a Git setup-repository script

Hello, I've added a setup-repository script (based on pkg-perl's script) to easily add Git repositories for debian-science. The script resides in /git/debian-science/packages. -- ‎أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 (@ subke

Re: DebianScience Unofficial Repository

"Kevin B. McCarty" <[EMAIL PROTECTED]> writes: > > I did set up an unofficial repository for CERN-related not-quite-free > software recently in collaboration with Axel Naumann. The intent was [snip] > Geant4 and CLHEP. A web site for the repository

Re: DebianScience Unofficial Repository

On Tue, 5 Aug 2008, Frederic Lehobey wrote: As much as I know, mentors is only dealing with source packages (and not binary ones). Ahh, OK this is new to me. So you have some point. nothing that is not finally solved by time (interesting packages will end up in main in any case). Well, t

Re: DebianScience Unofficial Repository

n not to use mentors. As much as I know, mentors is only dealing with source packages (and not binary ones). The idea of the repository would have been more something like http://backports.org/ (that is running its own dak) where instead of been picked from unstable, the packages would have been pi

Re: DebianScience Unofficial Repository

maintainer of this additional repository becomes MIA for whatever reason. I have seen this kind of effort dying to often in the past to call it reasonable. Just try to stick to the existing infra structure as much as possible - it just saves your time. Mentors + mentioning the package as unofficial

Re: DebianScience Unofficial Repository

cience/UnofficialRepository. This >> proposes an unofficial repository for Debian Science. > No real work has been achieved on the repository idea yet. As one of the original people proposing the idea, guess I should chip in a few words. Unfortunately I'm way too busy to do much since sta

Re: DebianScience Unofficial Repository

Hi, Chris Walker <[EMAIL PROTECTED]> (2008-07-12 17:41:41) : > While trying to update the DebianScience wiki, I have come across > http://wiki.debian.org/DebianScience/UnofficialRepository. This > proposes an unofficial repository for Debian Science. [...] > So have we m

DebianScience Unofficial Repository

While trying to update the DebianScience wiki, I have come across http://wiki.debian.org/DebianScience/UnofficialRepository. This proposes an unofficial repository for Debian Science. On Sat, Jul 12, 2008 at 06:03:06PM +0200, Andreas Tille wrote: > On Sat, 12 Jul 2008, Chris Walker wr

Re: Debian-science: synthesis about VCS & repository structure

that this was case sensitive and > > so it was changed to > > > >DM-Upload-Allowed: yes > > > > automatically in the whole repository. This example might be weak > > Hi all, > > another example: [ Mass-update for menu and doc-base transition ] To be

Re: Debian-science: synthesis about VCS & repository structure

gt; > automatically in the whole repository. This example might be weak Hi all, another example: I happily performed the Debian menu transition and the doc-base transition on all the packages on our SVN, but would not have gone through the hassle of doing a separate checkout for > 100 pac

Re: Debian-science: synthesis about VCS & repository structure

hanges via script in the whole repository if there are some systematical changes. For instance I remember that we first had DM-Upload-Allowed: Yes in many control files. It turned out that this was case sensitive and so it was changed to DM-Upload-Allowed: yes automatically in the whole

Re: Debian-science: synthesis about VCS & repository structure

On Mon, May 19, 2008 at 12:20:48PM +0200, Andreas Tille wrote: > On Mon, 19 May 2008, Steve M. Robbins wrote: > >> Wait a minute. What's wrong with using svn for those who want to? >> I have some packages that I'd like to put into debian-science at some >> point, but I'm not about to learn the fav

Re: debian-science repository structure

On Mon, 19 May 2008, Manuel Prinz wrote: Maybe I'll find some time on the weekend or next week to write it. If someone else steps up, I'm fine with that too. As you say, I do not think it's urgent. You would most probably like to use http://svn.debian.org/wsvn/debian-med/trunk/community/in

Re: Debian-science: synthesis about VCS & repository structure

se. ;) ) It is the declared *intention* that these tools are widely used and I would like to encourage everybody to do so. Currently the tasks files are stored in the CDD repository under projects and I think this is a reasonable place to store them. Everybody who is interested to enhance this stu

Re: debian-science repository structure

Am Montag, den 19.05.2008, 13:41 +0200 schrieb Andreas Tille: > Ahh OK, so you mean the just existing tasks files at > > > http://svn.debian.org/wsvn/cdd/projects/science/trunk/debian-science/tasks/?rev=0&sc=0 > > right? Exactly! (Did not have the URL at hand.)  > On Mon, 19 May 2008, Manue

Re: Debian-science: synthesis about VCS & repository structure

On Mon, 19 May 2008, Manuel Prinz wrote: I'm not quite sure if documentation about how to use tools should be in a policy-like document. Right. Even if some SVN / Quilt usage is in the Debian Med policy I admit that this is not really a typical content for a policy. So I do not care whether

Re: debian-science repository structure

On Mon, 19 May 2008, Manuel Prinz wrote: Sorry for being unclear! As stated in my other email, I was talking about the task files. Those are (in my understanding) meta-information about which packages belong the task or category and therefore which tasks or categories a package belongs. For exam

Re: debian-science repository structure

Am Montag, den 19.05.2008, 00:18 +0200 schrieb Andreas Tille: > On Sun, 18 May 2008, David Bremner wrote: > > > At the moment I am preoccupied with deciding how to best transition > > my quilt based packages to git. Of course keeping using quilt is an > > option. > > Uhm, I hope so. I really hop

Re: debian-science repository structure

Am Montag, den 19.05.2008, 00:07 +0200 schrieb Andreas Tille: > On Sun, 18 May 2008, Sylvestre Ledru wrote: > >> Those are of course valid points, though I still think that is something > >> that > >> can be generated from the meta-information that is already available. > >> Writing > >> a script

Re: Debian-science: synthesis about VCS & repository structure

Am Montag, den 19.05.2008, 12:20 +0200 schrieb Andreas Tille: > This [Git being Debian's favorite VCS] could be supported by a well > written policy that contains step by step examples which might be a > good help for newcommers. If this is done I see using git more as a > chance to learn somethin

  1   2   3   >