Re: Bug#969942: ITP: tty-share -- Terminal sharing over the Internet

On Wed, Sep 09, 2020 at 07:56:51AM +, Holger Levsen wrote: > On Wed, Sep 09, 2020 at 06:27:28AM +, Francisco Vilmar Cardoso Ruviaro > wrote: > > * Package name: tty-share > > Version : 0.6.2 > > Upstream Author : Vasile Popescu > > * URL :

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Mon, 06 Jan 2020, Ulrike Uhlig wrote: > Hi formorer, > > > On 28.12.19 18:16, Alexander Wirt wrote: > >> On Thu, 26 Dec 2019, Otto Kekäläinen wrote: > >> I am sure there are many ways to help the team and it is not just > >> about Salsa/Gitlab admin s

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Mon, 06 Jan 2020, Sam Hartman wrote: > >>>>> "Alexander" == Alexander Wirt writes: > > Alexander> For everything else: we are working on it. > > I just want to confirm that part of the things that you are working on > is documenting th

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Wed, 01 Jan 2020, Otto Kekäläinen wrote: > Hello! > > ti 31. jouluk. 2019 klo 14.55 Alexander Wirt (formo...@debian.org) kirjoitti: > > On Mon, 30 Dec 2019, Bernd Zeimetz wrote: > > > Also, if resources are an issue: I've offered several times to see if I > >

Accepted ipvsadm 1:1.31-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jan 2020 21:33:49 +0100 Source: ipvsadm Binary: ipvsadm ipvsadm-dbgsym Architecture: source amd64 Version: 1:1.31-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description

Accepted keepalived 1:2.0.19-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Jan 2020 18:45:43 +0100 Source: keepalived Binary: keepalived keepalived-dbgsym Architecture: source amd64 Version: 1:2.0.19-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt

Accepted ferm 2.5-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Jan 2020 11:58:53 +0100 Source: ferm Binary: ferm Architecture: source all Version: 2.5-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: ferm - maintain

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Mon, 30 Dec 2019, Bernd Zeimetz wrote: > > > On 12/30/19 11:29 AM, Raphael Hertzog wrote: > > I don't think that salsa-ci is particularly problematic in terms of > > "efficiency". With the exception of the LXC usage, there's not much > > that can be "cut" to save resources. > > Also, if

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Mon, 30 Dec 2019, Raphael Hertzog wrote: > On Sat, 28 Dec 2019, Alexander Wirt wrote: > > On Thu, 26 Dec 2019, Otto Kekäläinen wrote: > > > > > Hello! > > > > > > I've seen many times before statements like these so I'd like to raise > > > s

Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)

On Thu, 26 Dec 2019, Otto Kekäläinen wrote: > Hello! > > I've seen many times before statements like these so I'd like to raise > some discussion around the topic: > > pe 13. syysk. 2019 klo 16.36 Bastian Blank (wa...@debian.org) kirjoitti: > > On Sun, Sep 08, 2019 at 05:35:10PM -0400, Sam

Re: When acting as a service admin, it's official, no really.

On Wed, 09 Oct 2019, Sam Hartman wrote: > >>>>> "Alexander" == Alexander Wirt writes: > > Alexander> On Sun, 15 Sep 2019, Jonas Meurer wrote: > >> Sam Hartman: >>>>>> "Bastian" == Bastian Blank > >>

Re: Git Packaging Round 2: When to Salsa

On Sun, 15 Sep 2019, Jonas Meurer wrote: > Sam Hartman: > >> "Bastian" == Bastian Blank writes: > > > > Bastian> Hi Sam > > Bastian> On Sun, Sep 08, 2019 at 05:35:10PM -0400, Sam Hartman wrote: > > >> The Salsa CA pipeline is recommended. > > > > Bastian> For this I need to

Re: salsa.debian.org partially down

On Fri, 16 Aug 2019, Raphael Hertzog wrote: > Hi, > > On Fri, 16 Aug 2019, gregor herrmann wrote: > > From what I know, this what not a "foolish user action" but an action > > by a dedicated maintainer who enabled salsa-ci for all packages > > ("projects") of a specific team; so they used a

Re: salsa.debian.org partially down

On Fri, 16 Aug 2019, Daniel Leidert wrote: > Am Freitag, den 16.08.2019, 08:58 +0200 schrieb Alexander Wirt: > > On Fri, 16 Aug 2019, gregor herrmann wrote: > > [..] > > > From what I know, this what not a "foolish user action" but an action > > > by

Re: salsa.debian.org partially down

On Fri, 16 Aug 2019, gregor herrmann wrote: > On Wed, 14 Aug 2019 08:39:22 +0100, Ian Jackson wrote: > > > Alexander Wirt writes ("Re: salsa.debian.org partially down"): > > > It is already recovered. We will investigate where we can extend the > > &

Re: salsa.debian.org partially down

On Tue, 13 Aug 2019, Hector Oron wrote: > Hello, > > Missatge de Bastian Blank del dia dt., 13 d’ag. > 2019 a les 11:51: > > > > Hi folks > > > > salsa.debian.org is partially down for now. Especially everything that > > concerns Salsa CI. > > > > Someone decided to inject a few thousand CI

Re: how to handle upstream orig tarball with git-lfs reference files?

On Mon, 12 Aug 2019, Andrej Shadura wrote: > Hi, > > On Sun, 11 Aug 2019 at 14:57, Daniel Leidert wrote: > > > > Am Sonntag, den 11.08.2019, 07:26 +0200 schrieb Andrej Shadura: > > > On Sun, 11 Aug 2019, 04:18 Drew Parsons, wrote: > > > > We have the policy of not pulling files from the

Re: Debian, so ugly and unwieldy!

On Fri, 07 Jun 2019, Wookey wrote: > On 2019-06-07 17:24 +0200, Adam Borowski wrote: > > * CSD is still a thing. No, your special program shouldn't get to ignore > > system theme, put controls in wrong order, miss some controls, not respond > > to minimize/etc if it's currently busy, etc.

Re: Salsa migration from foo-guest to foo [was: Bits from the DPL (May 2019)]

On Fri, 07 Jun 2019, Thomas Goirand wrote: > On 6/5/19 4:08 PM, Norbert Preining wrote: > > This should be > > completely independent from what one can do on salsa. > > So I propose that whatever one's level within Debian is, it should not > > change the status on salsa. > > I also find it

Re: Bits from the DPL (May 2019)

On Thu, 06 Jun 2019, Sam Hartman wrote: > > "Bastian" == Bastian Blank writes: > > Bastian> Hi Sam > Bastian> On Thu, Jun 06, 2019 at 11:57:41AM -0400, Sam Hartman wrote: > >> However, it's a lot easier to get a foo-guest account on salsa > >> than it is to get a foo guest

Re: Bits from the DPL (May 2019)

On Wed, 05 Jun 2019, Adrian Bunk wrote: > On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote: > > > "Norbert" == Norbert Preining writes: > > > > Norbert> I would propose something else: Debian rights are defined > > Norbert> by presence/absence of a GPG key in certain key

Re: Bits from the DPL (May 2019)

On Thu, 06 Jun 2019, Andreas Tille wrote: > On Wed, Jun 05, 2019 at 10:14:50AM -0400, Sam Hartman wrote: > > > "Norbert" == Norbert Preining writes: > > > > Norbert> I would propose something else: Debian rights are defined > > Norbert> by presence/absence of a GPG key in certain

Tell me about your salsa experience

Hi, I was invited to be a speaker at the drupal con to talk about the evolution of tooling in open source projects [1]. I will take part in a panel together with other open source projects like Gnome or Drupal, we talk about about the past - the tool we used, its history and so on. Then we want

Re: Removal of linux-base from jessie-backports broke Xen upstream CI

On Thu, 14 Feb 2019, Ian Jackson wrote: > Firstly, thanks for taking the time to read what I wrote. (Thanks > also for Sam for his helpful perspective.) > > > Stepping back a bit, and firmly putting my `user' hat on: > > My aim was to share my experience, because I guess the point of >

Re: Removal of linux-base from jessie-backports broke Xen upstream CI

On Wed, 13 Feb 2019, Ian Jackson wrote: > Alexander Wirt writes ("Re: Removal of linux-base from jessie-backports broke > Xen upstream CI"): > > Jessie backports doesn't exist anymore. For some time now. It is already on > > its way to archive.d.o. > > Thanks

Re: Removal of linux-base from jessie-backports broke Xen upstream CI

On Wed, 13 Feb 2019, Ian Jackson wrote: > Introduction > > > I would like to recount a situation. I'm not sure where, if anywhere, > the root bug(s) lie, but I am inclined to say that a big part of the > problem was a change to the contents of jessie-backports. I would be >

Re: Proposal: Repository for fast-paced package backports

On Wed, 26 Dec 2018, Dominik George wrote: > > >If there are other issues to solve than the lifespan of the package > > >version, they must be solved in another way. > > > > I agree with you, it is the best outcome. But when people with power > > (-backports ftp masters) are not willing to

Re: Proposal: Repository for fast-paced package backports

I agree with you, it is the best outcome. But when people with power > (-backports ftp masters) are not willing to consider it, we have to go with > plan B, which is less than ideal, but can move things forward. > > >On Wed, Dec 26, 2018 at 04:32:28PM +0100, Alexander Wirt wrote: > &g

Re: Proposal: Repository for fast-paced package backports

On Wed, 26 Dec 2018, Dominik George wrote: > > I don't want backports to contain things are are not suited for a > > release. > > That's why we are doing all this. It is NOT about anything to backports. > It is about adding something new that uses the same RULES as backports, > with a slight

Re: Proposal: Repository for fast-paced package backports

ng due to the exact one reason that hey have a shorter lifespan. No > single other thing qualifies a package for -volatile if it is not > qualified for -backports. And this is also solved. I emptied the NEW queue two or three days ago. If there are dependencies missing the backports wasn't test

Re: Proposal: Repository for fast-paced package backports

On Wed, 26 Dec 2018, Pirate Praveen wrote: > > > On 2018, ഡിസംബർ 26 2:16:07 AM IST, Dominik George > wrote: > >Heisann, alle sammen, > > > >as announced in the recent thread about maintaining, I hereby propose a > >repository that allows making “backports” of packages available to > >users >

Re: Proposal: Repository for fast-paced package backports

On Tue, 25 Dec 2018, Dominik George wrote: > > We already told you to build your own repo. > > You should probably start with identifying the senders of mail > correctly ☺. I am not the gitlab maintainer (and will never be). https://lists.debian.org/debian-backports/2018/12/msg00028.html This

Re: Proposal: Repository for fast-paced package backports

On Tue, 25 Dec 2018, Dominik George wrote: > Heisann, alle sammen, > > as announced in the recent thread about maintaining, I hereby propose a > repository that allows making “backports” of packages available to users > of the stable distribution, if those packages cannot be maintained in >

Re: Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

On Tue, 18 Dec 2018, Pirate Praveen wrote: > [adding -devel to cc] > > On 12/3/18 8:11 PM, Dominik George wrote: > >> well, Debian is using gitlab!!! so this sentence has no sense. The > >> problem here > >> is that is a complex software that depends of a lot of pieces and it's > >> not > >>

Accepted keepalived 1:2.0.10-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Nov 2018 21:20:05 +0100 Source: keepalived Binary: keepalived Architecture: source Version: 1:2.0.10-1 Distribution: unstable Urgency: high Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: keepalived

Re: I resigned in 2004

On Sun, 11 Nov 2018, Adam Borowski wrote: > On Sun, Nov 11, 2018 at 07:50:55PM +0100, Vincent Bernat wrote: > > Then, they should click on the button they are asked to click. This > > takes far less time than a long (and discourteous) rant. > > Yeah... you walk out without a word, and are upset

Re: salsa irker bot moved to ssl

On Thu, 23 Aug 2018, Raphael Hertzog wrote: > On Thu, 23 Aug 2018, Alexander Wirt wrote: > > > A simple SQL update query would save us a lot of time. Thank you for > > > considering it. > > Sure, do you have the query? And please ensure not to affect bots > > r

Re: salsa irker bot moved to ssl

On Thu, 23 Aug 2018, Raphael Hertzog wrote: Hi, > On Sun, 29 Jul 2018, Alexander Wirt wrote: > > in the face of the current spam attacks I implemented CertFP for my > > irker instance. I also updated the default irc link in gitlab. However, > > it is possible that every

Re: Specs? Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Mon, 20 Aug 2018, Jeremy Stanley wrote: > On 2018-08-20 20:05:42 +0200 (+0200), Alexander Wirt wrote: > > On Mon, 20 Aug 2018, Thomas Goirand wrote: > [...] > > > Could you please at least define what is "some of the large data stores" > > > and

Re: Specs? Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Mon, 20 Aug 2018, Thomas Goirand wrote: > On 08/20/2018 11:40 AM, Alexander Wirt wrote: > > On Mon, 20 Aug 2018, Ulrike Uhlig wrote: > > > >> Hi! > >> > >> Bastian Blank: > >>> On Sat, Aug 18, 2018 at 11:34:53PM +0200, Thomas Goirand wr

Re: Specs? Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Mon, 20 Aug 2018, Ulrike Uhlig wrote: > Hi! > > Bastian Blank: > > On Sat, Aug 18, 2018 at 11:34:53PM +0200, Thomas Goirand wrote: > >> Ok, I'm getting in touch with the DSA team to see how it can be done. > >> Let's see first if we have hardware, and then how I can help for the > >> setup

Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Sat, 18 Aug 2018, Thomas Goirand wrote: > On 08/18/2018 07:42 AM, Alexander Wirt wrote: > >> I also don't understand why we're not attempting to build a Ceph cluster > >> at UBC. Why not? > > go ahead. if it works well we can switch to it. > > >

Re: Notification of merge requests on Salsa

On Sat, 18 Aug 2018, Rene Engelhard wrote: > Hi, > > On Fri, Aug 17, 2018 at 11:13:11PM -0400, Jacob Adams wrote: > > I’m sure I’m not the only one to have missed a merge request for a while > > thanks to the lack of notifications, but also we don’t want DDs inboxes > > flooded with every

Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

t; this service? > > Do you really trust this? I don't... > > Also, have we ever thought that Google is completely banned in China? > Can users in China access the data? If it's direct access to things > hosted by Google, then the answer is probably that it's also blocked. > > On 0

Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Fri, 17 Aug 2018, Ulrike Uhlig wrote: > Hi! > > Jonas Meurer: > > Am 13.08.2018 um 20:36 schrieb Alexander Wirt: > >>> Hrmpf! I have to say that I was somewhat surprised by this announcement. > >>> To be honest, I don't like the idea of making our

Re: Notification of merge requests on Salsa

On Thu, 16 Aug 2018, Jacob Adams wrote: Hi, > I've just discovered that by default, salsa.d.o does not inform project > owners of merge requests opened against their projects. This seems like > a poorly chosen default, as it is quite easy to completely miss when a > user opens a merge request,

Re: salsa.debian.org maintenance (GitLab 11.1.4 upgrade, external storage migration)

On Mon, 13 Aug 2018, Jonas Meurer wrote: > Hello, > > Am 11.08.2018 um 16:20 schrieb Bastian Blank: > > We will do maintenance on salsa.debian.org today, 2018-08-11, between > > 1600 and 1800 UTC. > > > > We will upgrade the GitLab instance to 11.1.4. > > Thanks a ton for all your maintenance

Accepted ipvsadm 1:1.29-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Aug 2018 09:21:46 +0200 Source: ipvsadm Binary: ipvsadm Architecture: source amd64 Version: 1:1.29-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: ipvsadm

salsa irker bot moved to ssl

Hi, in the face of the current spam attacks I implemented CertFP for my irker instance. I also updated the default irc link in gitlab. However, it is possible that every project using the bot has to migrate the server setting to ssl. So if you miss messages from salsa bot, please check that you

Re: Test message

On Sun, 29 Jul 2018, Jonathan Busby wrote: > I have been having problems posting to this mailing list so I'm using > pobox.com instead of my Gmail to see if that helps as per the listmaster's > suggestion. Ehm, you asked about "getting" mails, not about sending mails to the list. Therefore I

Re: Please remove your obsolete repos from alioth *NOW*

On Tue, 12 Jun 2018, Wouter Verhelst wrote: Hi Wouter, > On Wed, May 30, 2018 at 10:24:33AM +0200, Alexander Wirt wrote: > > Hi, > > > > we still have 175GiB git repos left on alioth. Please remove them asap. > > Life has been busy recently, and I didn't see thi

Re: Debian 10 please update gimp to 2.10....

On Mon, 11 Jun 2018, DutchGigalo wrote: > Debian 10 (buster) please update gimp to 2.10 Debian 10 isn't even released. That packages are missing is expected and not a reason for sending mails. Alex

Re: salsa.debian.org (git.debian.org replacement) going into beta

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 project

Re: its dead jim - alioth is gone

On Mon, 11 Jun 2018, Paul Wise wrote: > On Mon, Jun 11, 2018 at 9:41 AM, أحمد المحمودي wrote: > > > What has happened to the data in users' home directories ? > > The data will still be available until the VM is deleted. > The public_git directories are in the alioth archive: Which will happen

Re: Renew SSO Cert (was: its dead jim - alioth is gone)

On Wed, 06 Jun 2018, kaliko wrote: > Hi, > > First, thanks Alexander and everyone involved in alioth/salsa migration! > > Le 05/06/2018 à 21:49, Alexander Wirt a écrit : > > […] > > Whats left? > > > > […] > > - deploy the new sso.debian.org back

Re: concerns about Salsa

On Tue, 05 Jun 2018, Dmitry Smirnov wrote: > On Tuesday, 5 June 2018 3:45:42 PM AEST Alexander Wirt wrote: > > We don't have root. > > That actually makes sense... I didn't realize that Salsa is locked so tightly > that even you don't have root access... That makes thing

Re: concerns about Salsa

On Tue, 05 Jun 2018, Dmitry Smirnov wrote: > On Monday, 4 June 2018 10:08:00 PM AEST Alexander Wirt wrote: > > It just doesn't packages - which were just not available at the > > time we needed them (the available package were several major versions > > behind). > >

Re: concerns about Salsa

On Tue, 05 Jun 2018, Dmitry Smirnov wrote: > On Monday, 4 June 2018 11:25:41 PM AEST Alexander Wirt wrote: > > Please don't expect us to ever switch to packages - that will not happen. > > That's an interesting statement. Why? > > Do you think Praveen did all the enormou

Re: concerns about Salsa

On Mon, 04 Jun 2018, Thomas Goirand wrote: > On 06/04/2018 12:29 PM, Dmitry Smirnov wrote: > > GitLab is the right technology for us and a good improvement comparing to > > Alioth. > > > > I think it is great that we've chosen GitLab as successor to Alioth but how > > would it make you feel if

Re: concerns about Salsa

On Mon, 04 Jun 2018, eamanu15 wrote: > El lun., 4 de jun. de 2018 a la(s) 09:08, Alexander Wirt < > formo...@debian.org> escribió: > > > On Mon, 04 Jun 2018, eamanu15 wrote: > > > > > I think it's a low blow to us. > > > > > > I think this s

Re: concerns about Salsa

On Mon, 04 Jun 2018, Ian Jackson wrote: > Dmitry Smirnov writes ("concerns about Salsa"): > > Imagine my surprise when I've found that Salsa is not using our own > > GitLab package at all. > > Salsa is hardly the first Debian production service to not be running > the packaged version of its

Re: concerns about Salsa

On Mon, 04 Jun 2018, eamanu15 wrote: > I think it's a low blow to us. > > I think this should have been known from the beginning. We need each of the > Debian projects, intervene the Debian itself. > > Why don't start a new Debian project similar to GitLab, but based on Debian > OS. of course

Re: Please remove your obsolete repos from alioth *NOW*

On Thu, 31 May 2018, Herbert Fortes wrote: > Hi, > > > On Wed, May 30, 2018 at 10:41:21PM +0200, Adam Borowski wrote: > > > On Wed, May 30, 2018 at 06:30:20PM +0200, Alexander Wirt wrote: > > > > There it doesn't make sense to keep anything on alioth which is

Re: Please remove your obsolete repos from alioth *NOW*

On Wed, 30 May 2018, Adam Borowski wrote: > On Wed, May 30, 2018 at 06:30:20PM +0200, Alexander Wirt wrote: > > There it doesn't make sense to keep anything on alioth which is also on > > salsa. Everything else gets archived for historical purposes. > > Every repo that i

Re: Please remove your obsolete repos from alioth *NOW*

On Wed, 30 May 2018, Sean Whitton wrote: Hi Sean, > On Wed, May 30 2018, Alexander Wirt wrote: > > > we still have 175GiB git repos left on alioth. Please remove them > > asap. > > Thank you for your efforts in this area. > > I take it we should leave repos on a

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Chris Lamb wrote: Hi, > > I am not a kindergarten teacher. I will just stop answering mails here. > > You must know I have the greatest of respect for the tireless work you > have done and continue to do so as part of the migration from Alioth > to salsa. > > You are

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Ian Jackson wrote: > Alexander Wirt writes ("Re: remote: GitLab: LFS objects are missing. Ensure > LFS is properly set up or try a manual "git lfs push --all"."): > > Alex - fed up with explaining the same things again and again an

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Ian Jackson wrote: > Alexander Wirt writes ("Re: remote: GitLab: LFS objects are missing. Ensure > LFS is properly set up or try a manual "git lfs push --all"."): > > Alex - fed up with explaining the same things again and again an

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Andreas Tille wrote: > Hi again, > > On Wed, May 30, 2018 at 07:50:01AM +0200, Alexander Wirt wrote: > > > > Your repo has lfs disabled. You should enable it. > > > > > > How can I do this? > > > I've just found[1]:

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Geert Stappers wrote: > On Wed, May 30, 2018 at 11:19:14AM +0200, Alexander Wirt wrote: > > On Wed, 30 May 2018, Andreas Tille wrote: > > > Hi again, > > :-) > > > > > On Wed, May 30, 2018 at 07:50:01AM +0200, Alexander Wirt wrote:

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Andreas Tille wrote: > Hi again, > > On Wed, May 30, 2018 at 07:50:01AM +0200, Alexander Wirt wrote: > > > > Your repo has lfs disabled. You should enable it. > > > > > > How can I do this? > > > I've just found[1]:

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Wed, 30 May 2018, Andreas Tille wrote: > Hi, > > On Tue, May 29, 2018 at 11:35:00PM +0200, Alexander Wirt wrote: > > > I intend to push a new version of gatk[1] which contains some large > > > files. I imported the new upstream package the usual way. But if

Re: remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all".

On Tue, 29 May 2018, Andreas Tille wrote: > Hi, > > I intend to push a new version of gatk[1] which contains some large > files. I imported the new upstream package the usual way. But if I > want to push I get: > > (master) $ LC_ALL=C git push > Counting objects: 4599, done. > Delta

Re: Want to make salsa advertise contact and source code details [and 1 more messages]

On Fri, 25 May 2018, Ian Jackson wrote: > Alexander Wirt writes ("Re: Want to make salsa advertise contact and source > code details [and 1 more messages]"): > > It was a decision by the team to disallow any patch that is not > > really really needed for functi

Re: Want to make salsa advertise contact and source code details

On Fri, 25 May 2018, Geert Stappers wrote: > On Fri, May 25, 2018 at 02:54:17PM +0200, Alexander Wirt wrote: > > On Fri, 25 May 2018, Ian Jackson wrote: > > > > > > > > > But, I find this response worrying. It makes me wonder whether Salsa > > > is

Re: Want to make salsa advertise contact and source code details [and 1 more messages]

On Fri, 25 May 2018, Ian Jackson wrote: > Alexander Wirt writes ("Re: Want to make salsa advertise contact and source > code details [and 1 more messages]"): > > > Can you point me to the source code for Salsa's gitlab instance, > > > please ? > > https:/

Re: Want to make salsa advertise contact and source code details [and 1 more messages]

On Fri, 25 May 2018, Ian Jackson wrote: > Quoting my own other mail for more context: > > Ian Jackson writes ("Re: Want to make salsa advertise contact and source code > details"): > > Alexander Wirt tells me that that feature is "EE only", ie AIUI

Re: Want to make salsa advertise contact and source code details

an. I have submitted: > > https://salsa.debian.org/salsa/webhook/merge_requests/7 >Improve emails slightly > > https://salsa.debian.org/salsa/support/issues/77 >Please provide web page footer on every page with service information > > In response to the latter, Ale

Re: Salsa Questions

On Wed, 02 May 2018, Jörg Frings-Fürst wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hello, > > some questions about salsa: > > - - Becomes salsa the permissions as an open system like Alioth or does > it stay so steady? > > The background to the question is that at the

Re: Salsa Questions

On Wed, 02 May 2018, Jörg Frings-Fürst wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hello, > > some questions about salsa: > > - - Becomes salsa the permissions as an open system like Alioth or does > it stay so steady? eh? by default all web created projects are public. >

Re: [alioth deprecation] Please remove your unused and/or migrated repositories

On Sat, 28 Apr 2018, Holger Levsen wrote: > On Fri, Apr 27, 2018 at 08:55:43AM +0200, Alexander Wirt wrote: > > please remove your old, unused repos on alioth, so that we don't have to > > archive them. > > > > For darcs, bzr and mecurial do this until 2018-05

Re: [Alioth-staff-replacement] alioth deprecation - next steps

On Fri, 27 Apr 2018, Mike Gabriel wrote: > Hi, > > On Do 26 Apr 2018 10:52:41 CEST, Alexander Wirt wrote: > > > On Thu, 26 Apr 2018, Andrej Shadura wrote: > > > > > On 26 April 2018 at 10:21, Alexander Wirt <formo...@formorer.de> wrote: > >

Re: [alioth deprecation] Please remove your unused and/or migrated repositories

On Fri, 27 Apr 2018, Arturo Borrero Gonzalez wrote: > On 27 April 2018 at 11:07, Alexander Wirt <formo...@debian.org> wrote: > > On Fri, 27 Apr 2018, Arturo Borrero Gonzalez wrote: > > > >> On 27 April 2018 at 08:55, Alexander Wirt <formo...@debian.org> wr

Re: [alioth deprecation] Please remove your unused and/or migrated repositories

On Fri, 27 Apr 2018, Arturo Borrero Gonzalez wrote: > On 27 April 2018 at 08:55, Alexander Wirt <formo...@debian.org> wrote: > > Hi, > > > > please remove your old, unused repos on alioth, so that we don't have to > > archive them. > > > > For dar

Re: [Alioth-staff-replacement] alioth deprecation - next steps

On Thu, 26 Apr 2018, Andrej Shadura wrote: > On 26 April 2018 at 10:21, Alexander Wirt <formo...@formorer.de> wrote: > > On Thu, 26 Apr 2018, Andrej Shadura wrote: > > > >> On 17 April 2018 at 13:00, Alexander Wirt <formo...@debian.org> wrote: > >&g

Re: [Alioth-staff-replacement] alioth deprecation - next steps

On Thu, 26 Apr 2018, Andrej Shadura wrote: > On 17 April 2018 at 13:00, Alexander Wirt <formo...@debian.org> wrote: > > Hi, > > > > as you should be aware, alioth.debian.org will be decommissioned with > > the EOL of wheezy, which is at the end of May. The

Re: Completed: lists.alioth.debian.org migration

On Fri, 20 Apr 2018, Adam Borowski wrote: > On Fri, Apr 20, 2018 at 09:24:48AM +0200, Raphael Hertzog wrote: > > On Fri, 20 Apr 2018, Christoph Biedl wrote: > > > On the other hand I fully agree doing dozens or hundreds of uploads just > > > because an address out of my control became invalid is

Re: alioth deprecation - next steps

On Wed, 18 Apr 2018, Alexander Wirt wrote: > On Tue, 17 Apr 2018, Bill Allombert wrote: > > > On Tue, Apr 17, 2018 at 10:31:58PM +0100, James Clarke wrote: > > > Even the wiki page you linked there states that GitLab "allows extra > > > files to be attache

Re: alioth deprecation - next steps

On Tue, 17 Apr 2018, Bill Allombert wrote: > On Tue, Apr 17, 2018 at 10:31:58PM +0100, James Clarke wrote: > > Even the wiki page you linked there states that GitLab "allows extra > > files to be attached to the tag". > > But it does not say how. > Research shows that while gitlab has plan to

Re: alioth deprecation - next steps

On Tue, 17 Apr 2018, Bill Allombert wrote: > On Tue, Apr 17, 2018 at 11:10:56PM +0200, Alexander Wirt wrote: > > On Tue, 17 Apr 2018, Bill Allombert wrote: > > > > > On Tue, Apr 17, 2018 at 01:00:56PM +0200, Alexander Wirt wrote: > > > > Hi, >

Re: alioth deprecation - next steps

On Tue, 17 Apr 2018, Bill Allombert wrote: > On Tue, Apr 17, 2018 at 01:00:56PM +0200, Alexander Wirt wrote: > > Hi, > > > > as you should be aware, alioth.debian.org will be decommissioned with > > the EOL of wheezy, which is at the end of May. The replacement for

Re: alioth deprecation - next steps

On Tue, 17 Apr 2018, Holger Levsen wrote: Hi Holger, > Alexander, thanks for the update on the alioth migration! > > On Tue, Apr 17, 2018 at 01:00:56PM +0200, Alexander Wirt wrote: > > 17.-20.05.18: During the Mini-DebConf Hamburg any existing cron jobs will > > be turne

Re: New lintian warning: vcs-deprecated-in-debian-infrastructure

On Sat, 24 Mar 2018, Ole Streicher wrote: > Joerg Jaspert writes: > > packages.d.o/packagename and you are there. Nothing else needed. > > packages.d.o does not provide a canonical URL for the repository. > > It is even more difficult: I have first to select the package name,

Re: New lintian warning: vcs-deprecated-in-debian-infrastructure

On Thu, 22 Mar 2018, Andreas Tille wrote: > On Thu, Mar 22, 2018 at 12:56:30PM +0100, Alexander Wirt wrote: > > > > > > On the other hand the current timing does not allow for a probably > > > complex implementation and a http redirect which is even implemen

Re: New lintian warning: vcs-deprecated-in-debian-infrastructure

On Thu, 22 Mar 2018, Andreas Tille wrote: > Hi Lars, > > On Thu, Mar 22, 2018 at 12:47:44PM +0200, Lars Wirzenius wrote: > > On Thu, 2018-03-22 at 09:58 +0100, Andreas Tille wrote: > > > I admit I do not agree with this and it was discussed here before. Can > > > we please agree that

Re: New lintian warning: vcs-deprecated-in-debian-infrastructure

On Thu, 22 Mar 2018, Andreas Tille wrote: > Hi, > > today I realised the lintian warning: > > W: libbpp-core source: vcs-deprecated-in-debian-infrastructure vcs-git > https://anonscm.debian.org/git/debian-med/libbpp-core.git > N: > N:The specified Vcs-* field points to an area within the

Re: Is there any policy for user accounts doing automatic updates on Salsa

On Sun, 11 Mar 2018, Andreas Tille wrote: > Hi, > > I had the idea to create a repository inside the r-pkg group which > should receive automatic updates (created from an UDD query). My idea > was to create some dedicated account that gets commit permissions to > this project. I'd like to use

Re: A proposal for improving transparency of the FTP NEW process

On Sun, 04 Mar 2018, Thomas Goirand wrote: > On 03/02/2018 01:00 PM, Gert Wollny wrote: > > Since ftp-master also sometimes sends messages like "I let it pass for > > now, but please fix it with the next upload", using the package issue > > tracker would also be a way to keep track of these minor

Re: salsa SSH fingerprint

On Wed, 28 Feb 2018, Alberto Luaces wrote: > Hello, > > I am unable to find a place where the SSH fingerprint of salsa is shown. > I want to compare it with the one displayed when I try to push some > changes. Just for the record weasel (thanks weasel!) implemented sshfp records [1] for salsa.

Re: Spam targeting nnn-done@bugs.d.o

On Sun, 25 Feb 2018, Sebastian Andrzej Siewior wrote: > On 2018-02-21 10:53:49 [-0800], Don Armstrong wrote: > > We basically already do this with our ZIPFILE, MSWORD, and ZIPCOMPRESSED > > rules: > > > >

  1   2   3   4   5   6   7   8   9   >