[Dropping debian-devel-announce: please don't reply to the -announce maillist]
أحمد المحمودي 于2018年6月11日周一 下午10:48写道：
>
> On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote:
> > Collab-maint
> >
> >
> > If you want to allow other Debian Developers to work on your pac
On Mon, 11 Jun 2018, أحمد المحمودي wrote:
> On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote:
> > Collab-maint
> >
> >
> > If you want to allow other Debian Developers to work on your packages or
> > software, you can create projects within the
> > **Debian** group. Ev
On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote:
> Collab-maint
>
>
> If you want to allow other Debian Developers to work on your packages or
> software, you can create projects within the
> **Debian** group. Every Debian Developer has write access to projects created
Hello,
On Tue, 26 Dec 2017, Mehdi Dogguy wrote:
> For example, have a look at the following packages:
> - https://tracker.debian.org/pkg/siridb-server
> - https://tracker.debian.org/pkg/libcleri
>
> The maintainer box is not even shown. I guess this might be a bug to file
> against tracker.debian
Hello,
On Thu, 04 Jan 2018, Adam Borowski wrote:
> On Thu, Jan 04, 2018 at 01:01:15PM +0100, Raphael Hertzog wrote:
> > I agree. I have plans to create email addresses like
> > team+@tracker.debian.org that could be used for this purpose.
> > The package tracker would automatically add those packa
On Thu, Jan 4, 2018 at 7:01 AM, Raphael Hertzog wrote:
> I agree. I have plans to create email addresses like
> team+@tracker.debian.org that could be used for this purpose.
> The package tracker would automatically add those packages to the
> respective team.
>
> We could then expand the use of t
On Thu, Jan 04, 2018 at 01:01:15PM +0100, Raphael Hertzog wrote:
> On Thu, 28 Dec 2017, Adam Borowski wrote:
> > On Thu, Dec 28, 2017 at 09:38:11AM -0500, Jeremy Bicha wrote:
> > > On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote:
> > > > Question here is: how does the tracker identify which p
On Thu, 28 Dec 2017, Adam Borowski wrote:
> On Thu, Dec 28, 2017 at 09:38:11AM -0500, Jeremy Bicha wrote:
> > On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote:
> > > Question here is: how does the tracker identify which packages are team
> > > maintained? Currently, this is done with the maint
Hello,
On Tue, 26 Dec 2017, Boyuan Yang wrote:
> 在 2017年12月26日星期二 CST 下午9:48:50，Mattia Rizzolo 写道：
> > On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
> > > The time before the last time I asked about tracker, the answer was
> > > that this was not yet possible due to old lintian doing
On Tue, 2 Jan 2018 18:54:22 +0100, Raphael Hertzog
wrote:
>That said while it is possible to use @packages.debian.org email
>addresses in Maintainer fields it hat not been "validated" yet and you
>will likely see multiple problems. Some of them have been identified
>already (see Mehdi's mail in th
On Thu, 28 Dec 2017, Marc Haber wrote:
> On Tue, 26 Dec 2017 14:48:50 +0100, Mattia Rizzolo
> wrote:
> >On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
> >> The time before the last time I asked about tracker, the answer was
> >> that this was not yet possible due to old lintian doing
On Sat, 30 Dec 2017, Mathias Behrle wrote:
> * Alexander Wirt: " Re: salsa.debian.org (git.debian.org replacement) going
> into beta" (Sat, 30 Dec 2017 14:04:59 +0100):
>
> > On Sat, 30 Dec 2017, Wouter Verhelst wrote:
> >
> > > On Sat, Dec 30, 2017 a
Hi
On 31-12-17 06:56, Pirate Praveen wrote:
> On 12/30/2017 11:34 PM, Jeremy Bicha wrote:
>>> Besides: Is it possible to send mail to
>>> 'desktop-themes-t...@tracker.debian.org'? Where does it get forwarded?
>>
>> No. Email sent to that address won't go to anybody.
>
> Can't we allow people to s
On 12/30/2017 11:34 PM, Jeremy Bicha wrote:
>> Besides: Is it possible to send mail to
>> 'desktop-themes-t...@tracker.debian.org'? Where does it get forwarded?
>
> No. Email sent to that address won't go to anybody.
Can't we allow people to subscribe to teams just like subscribing to
individual
* Alexander Wirt: " Re: salsa.debian.org (git.debian.org replacement) going
into beta" (Sat, 30 Dec 2017 14:04:59 +0100):
> On Sat, 30 Dec 2017, Wouter Verhelst wrote:
>
> > On Sat, Dec 30, 2017 at 12:51:45PM +0100
On Sat, Dec 30, 2017 at 12:17 PM, Jonas Meurer wrote:
> That's great indeed. Funny enough, tobi, me and some others discussed
> this very topic at the 34c3 Debian meeting and came up with the idea to
> add groups functionality to tracker.debian.org. It's awesome to learn
> that it already exists :
Am 27.12.2017 um 20:49 schrieb Jeremy Bicha:
> On Wed, Dec 27, 2017 at 12:27 PM, Tobias Frost wrote:
>> How can one easily retrieve a list of packages from a specific team,
>
> The team can make a Tracker team and add their packages individually
> to the team like this:
> https://tracker.debian.o
On Sat, 30 Dec 2017, Mattia Rizzolo wrote:
> On Sat, Dec 30, 2017 at 02:04:59PM +0100, Alexander Wirt wrote:
> > First draft is on https://salsa.debian.org/salsa/AliothRewriter
>
> That seems to generate a list of 'RewriteRule's directives. May I
> recommend to instead use a RewriteMap? See
> ht
On Sat, 30 Dec 2017, Marco d'Itri wrote:
> On Dec 30, Alexander Wirt wrote:
>
> > > Anyway, looking forward to your map thing :-)
> > First draft is on https://salsa.debian.org/salsa/AliothRewriter
> Can you first apply some regexp-based mappings, like collab-maint to
> Debian? This would autom
On Dec 30, Alexander Wirt wrote:
> > Anyway, looking forward to your map thing :-)
> First draft is on https://salsa.debian.org/salsa/AliothRewriter
Can you first apply some regexp-based mappings, like collab-maint to
Debian? This would automatically solve most cases.
--
ciao,
Marco
signatur
On Sat, Dec 30, 2017 at 02:04:59PM +0100, Alexander Wirt wrote:
> First draft is on https://salsa.debian.org/salsa/AliothRewriter
That seems to generate a list of 'RewriteRule's directives. May I
recommend to instead use a RewriteMap? See
https://httpd.apache.org/docs/2.4/rewrite/rewritemap.html
On Sat, 30 Dec 2017, Wouter Verhelst wrote:
> On Sat, Dec 30, 2017 at 12:51:45PM +0100, Alexander Wirt wrote:
> > On Sat, 30 Dec 2017, Wouter Verhelst wrote:
> >
> > > On Fri, Dec 29, 2017 at 12:06:17PM +0100, Alexander Wirt wrote:
> > > > On Fri, 29 Dec 2017, Andreas Tille wrote:
> > > > > Or mo
On Sat, Dec 30, 2017 at 12:51:45PM +0100, Alexander Wirt wrote:
> On Sat, 30 Dec 2017, Wouter Verhelst wrote:
>
> > On Fri, Dec 29, 2017 at 12:06:17PM +0100, Alexander Wirt wrote:
> > > On Fri, 29 Dec 2017, Andreas Tille wrote:
> > > > Or more precisely it was a design flaw from the beginning whic
On Sat, 30 Dec 2017, Wouter Verhelst wrote:
> On Fri, Dec 29, 2017 at 12:06:17PM +0100, Alexander Wirt wrote:
> > On Fri, 29 Dec 2017, Andreas Tille wrote:
> > > Or more precisely it was a design flaw from the beginning which was
> > > intended to be cured with the workaround of annonscm and now i
On Fri, Dec 29, 2017 at 12:06:17PM +0100, Alexander Wirt wrote:
> On Fri, 29 Dec 2017, Andreas Tille wrote:
> > Or more precisely it was a design flaw from the beginning which was
> > intended to be cured with the workaround of annonscm and now it seems
> > even this will be broken for no good reas
Dr. Bas Wijnen wrote:
> On Fri, Dec 29, 2017 at 10:43:58PM +0100, Alexander Wirt wrote:
>> On Fri, 29 Dec 2017, Philipp Kern wrote:
>> > Put a mapping into a git repository that DDs can push to? Make sure that
>> > it is fast-forwarded always? Then let people deal with it?
>> I am currently workin
On Fri, Dec 29, 2017 at 10:43:58PM +0100, Alexander Wirt wrote:
> On Fri, 29 Dec 2017, Philipp Kern wrote:
> > Put a mapping into a git repository that DDs can push to? Make sure that
> > it is fast-forwarded always? Then let people deal with it?
> I am currently working on such a mapping.
I appr
On Fri, Dec 29, 2017 at 10:43:58PM +0100, Alexander Wirt wrote:
> > Put a mapping into a git repository that DDs can push to? Make sure that
> > it is fast-forwarded always? Then let people deal with it?
> I am currently working on such a mapping.
Thanks a lot
Andreas.
--
http://fam-tille
On Fri, 2017-12-29 at 12:32 +0100, W. Martin Borgert wrote:
> You are right. It is just not easy to solve this, because this
> information must be available on Debian systems. So it would be
> something in parallel to downloaded Packages files, right? And
> who generates this file(?) based on whic
On Fri, 29 Dec 2017, Alexander Wirt wrote:
> On Fri, 29 Dec 2017, Marco d'Itri wrote:
>
> > On Dec 29, Alexander Wirt wrote:
> >
> > > Please propose a solution for reusing the name without breaking renamed
> > > and
> > > not yet migrated repos.
> > Ignore the renamed repositories: if somebo
On Fri, 29 Dec 2017, Marco d'Itri wrote:
> On Dec 29, Alexander Wirt wrote:
>
> > Please propose a solution for reusing the name without breaking renamed and
> > not yet migrated repos.
> Ignore the renamed repositories: if somebody renamed them then they
> obviously expected to have to update
On Fri, 29 Dec 2017, Philipp Kern wrote:
> On 12/29/2017 12:51 PM, Marco d'Itri wrote:
> > On Dec 29, Alexander Wirt wrote:
> >> Please propose a solution for reusing the name without breaking renamed and
> >> not yet migrated repos.
> > Ignore the renamed repositories: if somebody renamed them
On Fri, 2017-12-29 at 12:32 +0100, W. Martin Borgert wrote:
> On 2017-12-29 12:42, Paul Wise wrote:
> > This is just a symptom of a Debian design flaw that dates back to
> > before we started using VCSen for packaging. We include information in
> > the source package that can change independently o
On Fri, Dec 29, 2017 at 04:11:29PM +0100, Thomas Goirand wrote:
> On 12/28/2017 02:33 AM, Jeremy Bicha wrote:
> > On Wed, Dec 27, 2017 at 7:07 PM, Manuel A. Fernandez Montecelo
> > wrote:
> >> If the idea is *not* to move those to @lists.d.o, I cannot see what we
> >> should be using instead.
> >>
On Fri, Dec 29, 2017 at 12:06:17PM +0100, Alexander Wirt wrote:
> On Fri, 29 Dec 2017, Andreas Tille wrote:
>
> > > This is just a symptom of a Debian design flaw that dates back to
> > > before we started using VCSen for packaging. We include information in
> > > the source package that can chang
On 12/28/2017 02:33 AM, Jeremy Bicha wrote:
> On Wed, Dec 27, 2017 at 7:07 PM, Manuel A. Fernandez Montecelo
> wrote:
>> If the idea is *not* to move those to @lists.d.o, I cannot see what we
>> should be using instead.
>>
>> Any recommendation?
>
> Someone on your team should create a Tracker Te
On 12/29/2017 12:51 PM, Marco d'Itri wrote:
> On Dec 29, Alexander Wirt wrote:
>> Please propose a solution for reusing the name without breaking renamed and
>> not yet migrated repos.
> Ignore the renamed repositories: if somebody renamed them then they
> obviously expected to have to update th
On Dec 29, Alexander Wirt wrote:
> Please propose a solution for reusing the name without breaking renamed and
> not yet migrated repos.
Ignore the renamed repositories: if somebody renamed them then they
obviously expected to have to update the VCS URLs anyway.
Switch the anonscm name when ali
On 2017-12-29 12:42, Paul Wise wrote:
> This is just a symptom of a Debian design flaw that dates back to
> before we started using VCSen for packaging. We include information in
> the source package that can change independently of the source package
> (such as Vcs-*, Homepage, debian/watch, Maint
On Fri, 29 Dec 2017, Andreas Tille wrote:
> Hi Paul,
>
> On Fri, Dec 29, 2017 at 12:42:28PM +0800, Paul Wise wrote:
> > On Fri, Dec 29, 2017 at 10:21 AM, Guillem Jover wrote:
> >
> > > I'm also growing some URL switching fatigue when it comes to Debian's
> > > git repos. And that's one of the re
Hi Paul,
On Fri, Dec 29, 2017 at 12:42:28PM +0800, Paul Wise wrote:
> On Fri, Dec 29, 2017 at 10:21 AM, Guillem Jover wrote:
>
> > I'm also growing some URL switching fatigue when it comes to Debian's
> > git repos. And that's one of the reasons I moved all my packaging to
> > my own server some
Hello,
On Wed, Dec 27 2017, Sean Whitton wrote:
> I think what would be ideal is having it disabled by default. People
> can turn it on again for their non-packaging repos.
>
> Upstream's bug tracker suggests GitLab can do this[1] so I've filed a
> request.[2]
... which has now been fulfilled.
On Fri, Dec 29, 2017 at 12:42:28PM +0800, Paul Wise wrote:
> On Fri, Dec 29, 2017 at 10:21 AM, Guillem Jover wrote:
>
> > I'm also growing some URL switching fatigue when it comes to Debian's
> > git repos. And that's one of the reasons I moved all my packaging to
> > my own server some time ago.
On Fri, Dec 29, 2017 at 10:21 AM, Guillem Jover wrote:
> I'm also growing some URL switching fatigue when it comes to Debian's
> git repos. And that's one of the reasons I moved all my packaging to
> my own server some time ago.
This is just a symptom of a Debian design flaw that dates back to
be
Guillem Jover writes:
> But this still leaves all checkouts that will also need to be updated,
> which is way way worse than the changes required in debian/control,
> documentation, wiki, etc. :( I also mentioned this when we moved from
> git.d.o to anonscm.d.o.
This is an issue I haven't seen a
On Mon, 2017-12-25 at 21:10:37 +0100, Marco d'Itri wrote:
> On Dec 25, Alexander Wirt wrote:
> > Every user can create projects in their own namespace (similar to GitHub).
> What about git repository URLs?
> I am not looking forward to update all Vcs-Git and Vcs-Browser headers
> currently refer
On Wed, 2017-12-27 at 01:35:50 +0100, Philip Rinn wrote:
> > Collab-maint
> >
> >
> > If you want to allow other Debian Developers to work on your packages or
> > software, you can create projects within the
> > **Debian** group. Every Debian Developer has write access to projects
>
On 14899 March 1977, Philip Rinn wrote:
> Is it true (and intended) that -guest users can't create projects within
> teams/groups they are member of? Or am I missing something? [I was not able to
> create a project within the Debian Science Team]
Those rights depend on the access level you have b
Adam Borowski writes:
> On Thu, Dec 28, 2017 at 09:38:11AM -0500, Jeremy Bicha wrote:
>> On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote:
>> > Question here is: how does the tracker identify which packages are team
>> > maintained? Currently, this is done with the maintainers mail address
>>
On Thu, Dec 28, 2017 at 09:38:11AM -0500, Jeremy Bicha wrote:
> On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote:
> > Question here is: how does the tracker identify which packages are team
> > maintained? Currently, this is done with the maintainers mail address
> > (which is f.e. debian-scie
On Thu, Dec 28, 2017 at 7:37 AM, Ole Streicher wrote:
> Question here is: how does the tracker identify which packages are team
> maintained? Currently, this is done with the maintainers mail address
> (which is f.e. debian-science-maintainers@alioth.d.o). However, when
> this address is gone, we
On 27.12.2017 12:02:49, Philip Rinn wrote:
> Mattia Rizzolo wrote:
> > So yes, you need to get a DD to do the one-off work of creating a
> > "collab-maint" project and grant you "master" powers in that projects
> > (so that you can add future members yourself). Now, is that really so
> > burdersom
"Manuel A. Fernandez Montecelo" writes:
> 2017-12-28 2:33 GMT+01:00 Jeremy Bicha :
>> Someone on your team should create a Tracker Team. Add the packages
>> your team maintains.
>>
>> https://tracker.debian.org/teams/
>>
>> Then anyone can simply join that tracker team to easily get
>> notificatio
Jeremy Bicha writes:
> On Wed, Dec 27, 2017 at 7:07 PM, Manuel A. Fernandez Montecelo
> wrote:
>> If the idea is *not* to move those to @lists.d.o, I cannot see what we
>> should be using instead.
>>
>> Any recommendation?
>
> Someone on your team should create a Tracker Team. Add the packages
>
On Wed, 27 Dec 2017 14:12:30 -0800, Russ Allbery
wrote:
>Alioth
>supports issues as well, but I'm not sure if any team ever used them, and
>I would be worried things would just disappear there, never to be seen by
>a human.
Alioth tickets were used by some teams, which got me confused like a
thou
On Wed, 27 Dec 2017 22:52:54 +0100, Adam Borowski
wrote:
>On Wed, Dec 27, 2017 at 08:51:12PM +, Sean Whitton wrote:
>> On Wed, Dec 27 2017, Jeremy Bicha wrote:
>>
>> > If a team stops using the BTS for bugs and just uses Salsa's Issues
>> > tracker, you can just go to a page like this (for th
On Tue, 26 Dec 2017 14:48:50 +0100, Mattia Rizzolo
wrote:
>On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
>> The time before the last time I asked about tracker, the answer was
>> that this was not yet possible due to old lintian doing automated
>> rejects on ftpmaster.
>
>That's now
2017-12-28 2:33 GMT+01:00 Jeremy Bicha :
> On Wed, Dec 27, 2017 at 7:07 PM, Manuel A. Fernandez Montecelo
> wrote:
>> If the idea is *not* to move those to @lists.d.o, I cannot see what we
>> should be using instead.
>>
>> Any recommendation?
>
> Someone on your team should create a Tracker Team.
On Thu, Dec 28, 2017 at 05:57:10AM +0100, gregor herrmann wrote:
> >
> > Then anyone can simply join that tracker team to easily get
> > notifications about bugs, commits, uploads, etc. Visit
> > https://tracker.debian.org/accounts/subscriptions/ and customize the
> > keywords to get the particula
On Wed, 27 Dec 2017 20:33:39 -0500, Jeremy Bicha wrote:
> Someone on your team should create a Tracker Team. Add the packages
> your team maintains.
>
> https://tracker.debian.org/teams/
>
> Then anyone can simply join that tracker team to easily get
> notifications about bugs, commits, uploads,
On Wed, Dec 27, 2017 at 7:07 PM, Manuel A. Fernandez Montecelo
wrote:
> If the idea is *not* to move those to @lists.d.o, I cannot see what we
> should be using instead.
>
> Any recommendation?
Someone on your team should create a Tracker Team. Add the packages
your team maintains.
https://track
Hi,
2017-12-27 21:27 Ole Streicher:
Andreas Tille writes:
I think it became clear what we do not want @lists.debian.org. However,
what we want is a common maintainer list for team maintenance.
I don't really see this need. This probably depends on the workflow,
therefore could you explain w
On Thu, Dec 28, 2017 at 12:33 AM, Anthony DeRobertis wrote:
> I haven't confirmed its available on salsa.d.o, and its unfortunately only
> one project at a time, but GitLab has an export under Project
> Settings→General.
github-backup is client side and works at any point in time without
needing
Adam Borowski writes:
> And it sounds bad enough that perhaps it'd be good to disable gitlab
> issues tracker on Salsa? Otherwise people would file bugs there and
> expect them to be handled instead of being more or less rudely
> redirected to the BTS.
The confusion potential of a second BTS do
Hello,
On Wed, Dec 27 2017, Adam Borowski wrote:
> And it sounds bad enough that perhaps it'd be good to disable gitlab
> issues tracker on Salsa? Otherwise people would file bugs there and
> expect them to be handled instead of being more or less rudely
> redirected to the BTS.
I think what wo
On Wed, Dec 27, 2017 at 08:51:12PM +, Sean Whitton wrote:
> On Wed, Dec 27 2017, Jeremy Bicha wrote:
>
> > If a team stops using the BTS for bugs and just uses Salsa's Issues
> > tracker, you can just go to a page like this (for the Salsa Team)
> > https://salsa.debian.org/groups/salsa/-/issue
Hello,
On Wed, Dec 27 2017, Jeremy Bicha wrote:
> If a team stops using the BTS for bugs and just uses Salsa's Issues
> tracker, you can just go to a page like this (for the Salsa Team)
> https://salsa.debian.org/groups/salsa/-/issues
Surely that's impossible because tools like britney need to k
Andreas Tille writes:
> I think it became clear what we do not want @lists.debian.org. However,
> what we want is a common maintainer list for team maintenance.
I don't really see this need. This probably depends on the workflow,
therefore could you explain why this is needed?
> I have not yet
On Wed, Dec 27, 2017 at 12:27 PM, Tobias Frost wrote:
> How can one easily retrieve a list of packages from a specific team,
The team can make a Tracker team and add their packages individually
to the team like this:
https://tracker.debian.org/teams/desktop-themes-team/
(This is a very new team
On Tue, Dec 26, 2017 at 02:48:50PM +0100, Mattia Rizzolo wrote:
> On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
> > The time before the last time I asked about tracker, the answer was
> > that this was not yet possible due to old lintian doing automated
> > rejects on ftpmaster.
>
>
On 12/27/2017 05:06 AM, Paul Wise wrote:
Does anyone know if there is a tool similar to github-backup that
supports gitlab?
I haven't confirmed its available on salsa.d.o, and its unfortunately
only one project at a time, but GitLab has an export under Project
Settings→General.
Hi,
On Tue, Dec 26, 2017 at 03:01:47PM +0100, Alexander Wirt wrote:
> > > Unfortunately that is something that has to be done. At least unless
> > > someone
> > > wants to write some kind of redirection map.
> > I am really surprised that this issue was not considered: I expect that
> > git hos
On Wed, Dec 27, 2017 at 02:49:18PM +0100, Thibaut Paumard wrote:
> > I fully agree here. It makes pages like
> >
> > https://qa.debian.org/developer.php?email=debian-astro-maintainers%40lists.alioth.debian.org
> >
> > quite nonfunctional. And they are even not simple to restore with the
> > name,
Hi Alexander,
On Tue, Dec 26, 2017 at 06:17:47PM +0100, Alexander Wirt wrote:
> > GNOME Team's current pkg-gnome-maintainers@lists.alioth and the Games
> > Team's pkg-games-devel@lists.alioth)?
> >
> > A few packages and pseudo-packages already have lists.d.o mailing lists
> > as their Maintainer
On Tue, Dec 26, 2017 at 07:12:06PM +0100, Sven Hoexter wrote:
> On Tue, Dec 26, 2017 at 06:42:42PM +0100, Anton Gladky wrote:
> > 2017-12-26 18:15 GMT+01:00 Alexander Wirt :
>
> Hi,
>
> > > The infrastructure and tools are not good in maintaining such a huge
> > > number
> > > of lists.
> >
> >
Le 26/12/2017 à 21:34, Ole Streicher a écrit :
I agree with your reasoning. I just wanted to highlight that the situation
is in fact worse with the "Team foo " schema: Our
tools do not seem ready for that yet.
I fully agree here. It makes pages like
https://qa.debian.org/developer.php?email=d
Mattia Rizzolo wrote:
> So yes, you need to get a DD to do the one-off work of creating a
> "collab-maint" project and grant you "master" powers in that projects
> (so that you can add future members yourself). Now, is that really so
> burdersome?
Well, probably not. Could you (or anyone else) pl
On 27.12.2017 08:33:12, Anton Gladky wrote:
> 2017-12-27 1:35 GMT+01:00 Philip Rinn :
>
> > Is it true (and intended) that -guest users can't create projects within
> > teams/groups they are member of? Or am I missing something? [I was not able
> > to
> > create a project within the Debian Scien
Mattia Rizzolo writes:
> On Wed, Dec 27, 2017 at 10:02:06AM +0100, Ole Streicher wrote:
>> Mattia Rizzolo writes:
>> > On Wed, Dec 27, 2017 at 01:35:50AM +0100, Philip Rinn wrote:
>> >> Is it true (and intended) that -guest users can't create projects
>> >> within teams/groups they are member of?
On Mon, Dec 25, 2017 at 6:45 PM, Alexander Wirt wrote:
> we have worked on our git.debian.org replacement based on GitLab.
Does anyone know if there is a tool similar to github-backup that
supports gitlab?
--
bye,
pabs
https://wiki.debian.org/PaulWise
On Wed, Dec 27, 2017 at 10:02:06AM +0100, Ole Streicher wrote:
> Mattia Rizzolo writes:
> > On Wed, Dec 27, 2017 at 01:35:50AM +0100, Philip Rinn wrote:
> >> Is it true (and intended) that -guest users can't create projects
> >> within teams/groups they are member of? Or am I missing something? [I
Mattia Rizzolo writes:
> On Wed, Dec 27, 2017 at 01:35:50AM +0100, Philip Rinn wrote:
>> Is it true (and intended) that -guest users can't create projects
>> within teams/groups they are member of? Or am I missing something? [I
>> was not able to create a project within the Debian Science Team]
>
On Wed, Dec 27, 2017 at 08:48:29AM +0100, Geert Stappers wrote:
> On Wed, Dec 27, 2017 at 08:33:12AM +0100, Anton Gladky wrote:
> > 2017-12-27 1:35 GMT+01:00 Philip Rinn :
> >
> > > Is it true (and intended) that -guest users can't create projects within
> > > teams/groups they are member of? Or a
على الأربعاء 27 كانون الأول 2017 02:46، كتب Mattia Rizzolo:
> On Wed, Dec 27, 2017 at 01:35:50AM +0100, Philip Rinn wrote:
>> Is it true (and intended) that -guest users can't create projects within
>> teams/groups they are member of? Or am I missing something? [I was not able
>> to
>> create a
On Wed, Dec 27, 2017 at 08:33:12AM +0100, Anton Gladky wrote:
> 2017-12-27 1:35 GMT+01:00 Philip Rinn :
>
> > Is it true (and intended) that -guest users can't create projects within
> > teams/groups they are member of? Or am I missing something? [I was not able
> > to
> > create a project within
On Wed, Dec 27, 2017 at 01:35:50AM +0100, Philip Rinn wrote:
> Is it true (and intended) that -guest users can't create projects within
> teams/groups they are member of? Or am I missing something? [I was not able to
> create a project within the Debian Science Team]
As Anton noted, you need to be
2017-12-27 1:35 GMT+01:00 Philip Rinn :
> Is it true (and intended) that -guest users can't create projects within
> teams/groups they are member of? Or am I missing something? [I was not able to
> create a project within the Debian Science Team]
Hmm, it is really so that the users with the role
Hi,
thanks for your work, salsa is really great!
Is it true (and intended) that -guest users can't create projects within
teams/groups they are member of? Or am I missing something? [I was not able to
create a project within the Debian Science Team]
> Collab-maint
>
>
> If you want
Mehdi Dogguy writes:
> On 26/12/2017 15:05, Ole Streicher wrote:
>> Mattia Rizzolo writes:
>>> On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
The time before the last time I asked about tracker, the answer was
that this was not yet possible due to old lintian doing automate
On 26/12/2017 15:05, Ole Streicher wrote:
> Mattia Rizzolo writes:
>> On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
>>> The time before the last time I asked about tracker, the answer was
>>> that this was not yet possible due to old lintian doing automated
>>> rejects on ftpmaster.
On Tue, Dec 26, 2017 at 06:42:42PM +0100, Anton Gladky wrote:
> 2017-12-26 18:15 GMT+01:00 Alexander Wirt :
Hi,
> > The infrastructure and tools are not good in maintaining such a huge number
> > of lists.
>
> That is OK, but can we then have @lists.alioth.debian.org running
> or it is planned t
2017-12-26 18:15 GMT+01:00 Alexander Wirt :
>> On Tue, 2017-12-26 at 16:02 +0100, Alexander Wirt wrote:
>> > We don't want maintainter lists on l.d.o
>>
>> Why not?
> The infrastructure and tools are not good in maintaining such a huge number
> of lists.
That is OK, but can we then have @lists.al
On Tue, 26 Dec 2017, Simon McVittie wrote:
> On Tue, 26 Dec 2017 at 16:02:08 +0100, Alexander Wirt wrote:
> > On Tue, 26 Dec 2017, Anton Gladky wrote:
> > > I think we should request the list something like
> > > debian-science-maintain...@lists.debian.org
> > > and use it instead of @lists.alioth
On Tue, 26 Dec 2017, Ben Hutchings wrote:
> On Tue, 2017-12-26 at 16:02 +0100, Alexander Wirt wrote:
> > On Tue, 26 Dec 2017, Anton Gladky wrote:
> >
> > > 2017-12-26 15:05 GMT+01:00 Ole Streicher :
> > > > Maintainer: Debian Science Team
> > >
> > > I think we should request the list something
On Tue, 2017-12-26 at 16:02 +0100, Alexander Wirt wrote:
> On Tue, 26 Dec 2017, Anton Gladky wrote:
>
> > 2017-12-26 15:05 GMT+01:00 Ole Streicher :
> > > Maintainer: Debian Science Team
> >
> > I think we should request the list something like
> > debian-science-maintain...@lists.debian.org
> >
On Tue, 26 Dec 2017 at 16:02:08 +0100, Alexander Wirt wrote:
> On Tue, 26 Dec 2017, Anton Gladky wrote:
> > I think we should request the list something like
> > debian-science-maintain...@lists.debian.org
> > and use it instead of @lists.alioth.debian.org
>
> We don't want maintainter lists on l.d
On Tue, 26 Dec 2017, Anton Gladky wrote:
> 2017-12-26 15:05 GMT+01:00 Ole Streicher :
> > Maintainer: Debian Science Team
>
> I think we should request the list something like
> debian-science-maintain...@lists.debian.org
> and use it instead of @lists.alioth.debian.org
We don't want maintainter
2017-12-26 15:05 GMT+01:00 Ole Streicher :
> Maintainer: Debian Science Team
I think we should request the list something like
debian-science-maintain...@lists.debian.org
and use it instead of @lists.alioth.debian.org
Cheers
Anton
Mattia Rizzolo writes:
> On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
>> The time before the last time I asked about tracker, the answer was
>> that this was not yet possible due to old lintian doing automated
>> rejects on ftpmaster.
>
> That's now fixed, and you can use $pack...@p
On Tue, 26 Dec 2017, Marco d'Itri wrote:
> On Dec 26, Alexander Wirt wrote:
>
> > Unfortunately that is something that has to be done. At least unless someone
> > wants to write some kind of redirection map.
> I am really surprised that this issue was not considered: I expect that
> git hostin
1 - 100 of 116 matches
Mail list logo
