Re: Ssh access on salsa denied

On Sun, 07 Jan 2018, Andreas Tille wrote: > Hi, > > I verified in the web interface on Salsa that my public ssh key > from alioth was imported and to be very sure I uploaded it again. > Unfortunately this does not changed anything > >$ ssh -i ~/.ssh/id_rsa_debian2 ti...@salsa.debian.org >

Re: Salsa Beta - Updates

On Sat, 06 Jan 2018, Martín Ferrari wrote: > On 06/01/18 00:30, Joerg Jaspert wrote: > > > > Alexander (formorer) is running an Irker instance on one of its own > > VMs. Irker can send push events to an IRC channel. Please check the > > wiki[2] for details on how to use it. > > > > We are not

Re: Naming of teams on salsa.debian.org

On Fri, 05 Jan 2018, Philipp Huebner wrote: > Hi > > Am 04.01.2018 um 16:57 schrieb Ximin Luo: > > I think it's preferable not to look at this from the point-of-view of > > individual teams, but from the perspective of the project as a whole. > > When non-Debian people navigate salsa.d.o it

Re: Problem with Git Push

On Thu, 04 Jan 2018, Gianfranco Costamagna wrote: > Hello, > > > >Afterclone, I add the new changes and I try to make a push origin but I have > >this error:The requested URL returned error: 403. > > > this is a private repo > > please push there > git remote add upstream >

Re: Marking bugs as pending for salsa.d.o

On Thu, 04 Jan 2018, Byung-Hee HWANG (황병희, 黃炳熙) wrote: Hi, > In Article <87mv1um3bd@delenn.ganneff.de>, > Joerg Jaspert writes: > > > I'm on it, code lives in https://salsa.debian.org/salsa/webhook > > Your code looks so beautiful, i am a fan for Ruby. > > So we

Re: Marking bugs as pending for salsa.d.o

On Thu, 04 Jan 2018, Rafael Laboissière wrote: > In the Git repositories of packages that I maintain at alioth.d.o, a > script [*] is called in the post-receive hook for tagging the bugs listed in > the meta tag "Closes:" of gbp-dch as "pending". > > Is there a way to have a similar integration

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

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

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

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

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

On Sat, 30 Dec 2017, Marco d'Itri wrote: > On Dec 30, Alexander Wirt <formo...@debian.org> wrote: > > > > Anyway, looking forward to your map thing :-) > > First draft is on https://salsa.debian.org/salsa/AliothRewriter > Can you first apply some regexp-bas

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

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 F

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

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 wor

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

On Fri, 29 Dec 2017, Alexander Wirt wrote: > On Fri, 29 Dec 2017, Marco d'Itri wrote: > > > On Dec 29, Alexander Wirt <formo...@debian.org> wrote: > > > > > Please propose a solution for reusing the name without breaking renamed > > > and > > &

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

On Fri, 29 Dec 2017, Marco d'Itri wrote: > On Dec 29, Alexander Wirt <formo...@debian.org> wrote: > > > Please propose a solution for reusing the name without breaking renamed and > > not yet migrated repos. > Ignore the renamed repositories: if somebody renamed

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

On Fri, 29 Dec 2017, Philipp Kern wrote: > On 12/29/2017 12:51 PM, Marco d'Itri wrote: > > On Dec 29, Alexander Wirt <formo...@debian.org> wrote: > >> Please propose a solution for reusing the name without breaking renamed and > >> not yet migrated repos. &g

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

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: salsa.debian.org (git.debian.org replacement) going into beta

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 <oleb...@debian.org>: > > > > Maintainer: Debian

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

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

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

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

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

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 <oleb...@debian.org>: > > > > Maintainer: Debian

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

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

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

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

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

On Tue, 26 Dec 2017, Marco d'Itri wrote: > On Dec 26, Alexander Wirt <formo...@debian.org> 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

Re: Team naming policy on salsa.debian.org

On Tue, 26 Dec 2017, Jonathan McDowell wrote: > On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote: > > > Teams > > - > > > > For larger projects you can also create a group to host your projects. > > To avoid clashes with usernames (that sh

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

On Tue, 26 Dec 2017, Arturo Borrero Gonzalez wrote: > On 26 December 2017 at 11:03, Alexander Wirt <formo...@debian.org> wrote: > > On Tue, 26 Dec 2017, Arturo Borrero Gonzalez wrote: > > > >> On 26 December 2017 at 10:22, Alexander Wirt <formo...@debian.org&g

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

On Tue, 26 Dec 2017, Arturo Borrero Gonzalez wrote: > On 26 December 2017 at 10:22, Alexander Wirt <formo...@debian.org> wrote: > > On Tue, 26 Dec 2017, Jonathan Dowland wrote: > > > >> On Tue, Dec 26, 2017 at 08:16:41AM +0100, Alexander Wirt wrote: > >> &g

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

On Tue, 26 Dec 2017, Jonathan Dowland wrote: > On Tue, Dec 26, 2017 at 08:16:41AM +0100, Alexander Wirt wrote: > > On Mon, 25 Dec 2017, Marco d'Itri wrote: > > > I am not looking forward to update all Vcs-Git and Vcs-Browser headers > > > currently ref

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

On Mon, 25 Dec 2017, Marco d'Itri wrote: > On Dec 25, Alexander Wirt <formo...@debian.org> 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

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

On Mon, 25 Dec 2017, Holger Levsen wrote: Hi, > first of all: thanks a lot for all your work on this! > > On Mon, Dec 25, 2017 at 11:45:37AM +0100, Alexander Wirt wrote: > > External users are invited to create an account on salsa. > > do you plan importing the current

Bug#884966: lists.debian.org: Add an onion address to every Debian address in every email by bots (if available in onion.debian.org)

On Fri, 22 Dec 2017, TemTem wrote: > Oh no, I fucking revealed my real name in my attachment. Can someone who has > access delete the attachment? Please, ASAP. I am very uncomfortable revealing > my real name especially in large communities like Debian. If you are reading > this, if you are

Re: Iproute2 for Debian testing and backports

On Sun, 17 Dec 2017, Luca Boccassi wrote: > On Sat, 2017-12-16 at 17:14 +0100, Alexander Wirt wrote: > > On Sat, 16 Dec 2017, Luca Boccassi wrote: > > > > Hi,  > > > > *snip*  > > > > > > Your help is really welcome, do you have an alioth ac

Bug#884573: RM: torbrowser-launcher/0.2.6-2~bpo8+1

On Sun, 17 Dec 2017, Adam D. Barratt wrote: > Control: reassign -1 ftp.debian.org > > On Sun, 2017-12-17 at 14:15 +0900, Roger Shimizu wrote: > > The old version of torbrowser-launcher cannot work properly anymore, > > because it uses the embedded old key. > > That's also the reason why it also

Re: Iproute2 for Debian testing and backports

On Sat, 16 Dec 2017, Luca Boccassi wrote: Hi, *snip* > > Your help is really welcome, do you have an alioth account?  > > > > Alex > > Yes I do (DD :-) ) argh, my bad. Since pkg-iproute is collab-maint you should already be able to commit. > > I propose the following: > > - upload 4.13

Re: Iproute2 for Debian testing and backports

On Fri, 15 Dec 2017, Luca Boccassi wrote: > On Thu, 14 Dec 2017, Alexander Wirt wrote: > > On Wed, 13 Dec 2017, Stephen Hemminger wrote: > >  > > > Iproute2 gains new features every release to keep up with the > upstream kernel. > > >  > > > How

Re: Iproute2 for Debian testing and backports

On Wed, 13 Dec 2017, Stephen Hemminger wrote: > On Thu, 14 Dec 2017 08:26:07 +0100 > Alexander Wirt <formo...@formorer.de> wrote: > > > On Wed, 13 Dec 2017, Stephen Hemminger wrote: > > > > > Iproute2 gains new features every release to keep up with the upst

Re: Iproute2 for Debian testing and backports

On Wed, 13 Dec 2017, Stephen Hemminger wrote: > Iproute2 gains new features every release to keep up with the upstream kernel. > > How do I request that iproute for Debian testing (buster) and backports > (stretch-backports) > be kept in sync? > kernel iproute >

Re: Amavis doesn't mark mail as spam, and doesn't set spam headers

On Fri, 01 Dec 2017, chaouche yacine wrote: > Hello Alxander, > This log entry seems to show that spam checking was done : > Nov 28 16:33:16 messagerie amavis[46130]: (46130-07) Passed SPAMMY > {RelayedOpenRelay}, [101.55.71.90]:53783 [101.55.71.90] >

Bug#882128: bulk subscription of a single address to multiple lists

On Sun, 19 Nov 2017, Daniel Pocock wrote: > Package: lists.debian.org > Severity: wishlist > > It would be useful to provide a way for a single person to quickly > subscribe to multiple lists. > > An example of this is for new participants in Outreachy and GSoC. > > There could be a few

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Nov 2017 09:23:16 +0100 Source: keepalived Binary: keepalived Architecture: source amd64 Version: 1:1.3.9-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexande

Re: Auto-update for sid? Auto-backport?

On Wed, 15 Nov 2017, Didier 'OdyX' Raboud wrote: > Le mercredi, 15 novembre 2017, 16.43:17 h CET Steffen Möller a écrit : > > I would really like to see updates performed in some automated fashion. > > Debian updates are in fact different steps: > * inclusion of upstream changes; > * packaging

debconf-team moved to lists.debian.org

Again with a proper subject, sorry for the noise. Hi, if you received that mail I successfully moved the debconf-team list to lists.debian.org. That means it isn't hosted by mailman anymore, but by smartmail - please check our docs on how to manage yourself [1]. The posting address is now

Re: bendel (lists.debian.org) upgrade today

On Sat, 21 Oct 2017, Alexander Wirt wrote: > Hi, > > we will upgrade bendel to stretch this evening, expect problems and outages > of lists.debian.org until we are done. if you can read that mail we are probably done. If you find a (new) problem, please tell us (via mail or in #

Re: RFP: pgadmin4 -- Web administration tool for PostgreSQL

On Sat, 21 Oct 2017, Denis Briand wrote: Hi, > * Package name : pgadmin > * Version : 4 > * Upstream Author : Dave Page > * URL : https://www.pgadmin.org > * License : PostgreSQL/Artistic licence https://www.pgadmin.org/licence/ > * Description : Web administration tool for PostgreSQL > >

Re: [Pkg-javascript-devel] Concerns about infrastructure for Alioth replacement

l > > On Tue, Oct 17, 2017 at 11:32:55PM +0200, Alexander Wirt wrote: > > On Tue, 17 Oct 2017, Francesco Poli wrote: > > > > > On Mon, 16 Oct 2017 04:28:09 + Ondřej Surý wrote: > > > > > > [...] > > > > Francesco, great idea,

Re: Concerns about infrastructure for Alioth replacement

l > > On Tue, Oct 17, 2017 at 11:32:55PM +0200, Alexander Wirt wrote: > > On Tue, 17 Oct 2017, Francesco Poli wrote: > > > > > On Mon, 16 Oct 2017 04:28:09 + Ondřej Surý wrote: > > > > > > [...] > > > > Francesco, great idea,

Re: Concerns about infrastructure for Alioth replacement

On Tue, 17 Oct 2017, Francesco Poli wrote: > On Mon, 16 Oct 2017 04:28:09 + Ondřej Surý wrote: > > [...] > > Francesco, great idea, go ahead. You would be most welcome to help with > > Debian Ruby Extra packaging. > > Unfortunately, I have basically zero knowledge about Rails, JavaScript >

Bug#878894: lists.debian.org: Request for migration of mailing list: debconf-announce

tag 878894 moreinfo thanks On Tue, 17 Oct 2017, Daniel Lange wrote: > Package: lists.debian.org > Severity: wishlist > > Name: debconf-announce > > Rationale: > As per > https://www.mail-archive.com/debconf-team@lists.debconf.org/msg14555.html > Task #2 and DSA RT #6925: > We are migrating

Re: [Debconf-team] Debian RT - DebConf infra migration mailing lists (Task #2)

On Tue, 17 Oct 2017, Daniel Lange wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > As per > https://www.mail-archive.com/debconf-team@lists.debconf.or/msg14555.html Task > #2: Please create the correct bugs as per https://www.debian.org/MailingLists/HOWTO_start_list (one per

Re: Concerns about infrastructure for Alioth replacement

On Mon, 16 Oct 2017, Benjamin Drung wrote: > Am Montag, den 16.10.2017, 07:22 +0200 schrieb Alexander Wirt: > > On Mon, 16 Oct 2017, Francesco Poli wrote: > > > > > Hello, > > > I am a Debian contributor (and Alioth user). > > > > > > First

Re: Concerns about infrastructure for Alioth replacement

On Mon, 16 Oct 2017, Francesco Poli wrote: > Hello, > I am a Debian contributor (and Alioth user). > > First off, I think that [replacing] Alioth with something more > maintainable is a good thing to do and I am grateful to the people who > are working hard to make this happen. > > [replacing]:

Re: [Alioth-staff-replacement] Alioth: Concerns about git URLs and groups/teams

On Thu, 21 Sep 2017, Ondřej Surý wrote: > FWIW gitlab now supports groups, subgroups and projects + granular > permissions per those. Jupp, we will do teams as subgroups in a defined namespace with admin permissions to the team admin. Alex

Re: Alioth: Concerns about git URLs and groups/teams

On Thu, 21 Sep 2017, Guillem Jover wrote: > Hi! > > First off, and just to be clear, I think decomissioning Alioth is a > good thing given its current state! Thanks for that. > > One concern is whether we'll be needing to mass switch yet again git > repo URLs for the nth time? The nice thing

Re: [Debconf-team] DebConf lists migration to lists.debian.org

On Tue, 19 Sep 2017, Giacomo Catenazzi wrote: > On 17.09.2017 16:50, Daniel Lange wrote: > > Hi, > > > > the DebConf team is currently preparing another try to migrate the > > DebConf specific infrastructure to Debian, DSA supported, solutions. > > > > Along this we would like to migrate the

Re: Alioth: the future of mailing lists

On Tue, 19 Sep 2017, Marc Haber wrote: > On Tue, 19 Sep 2017 10:42:20 +0200, Martin Steigerwald > wrote: > >Would it be possible with reasonable effort to synchronize spam filtering > >configuration from lists.debian.org to that potential new mailing list > >server? > >

Re: Alioth: the future of mailing lists

On Tue, 19 Sep 2017, Marc Haber wrote: > On Mon, 18 Sep 2017 21:53:43 +0200, Alexander Wirt > <formo...@formorer.de> wrote: > >On Mon, 18 Sep 2017, Dominic Hargreaves wrote: > >> I have managed mailman installations for some time so I'm fairly familiar > >> w

Bug#876144: lists.debian.org: Request for new mailing list: pkg-gnupg-maint

On Tue, 19 Sep 2017, Daniel Kahn Gillmor wrote: > On Tue 2017-09-19 07:18:24 +0200, Alexander Wirt wrote: > > This is one of the examples we will probably not accept, > > thanks for the prompt response, Alex. > > > but we will discuss that internally again. > &g

Bug#876144: lists.debian.org: Request for new mailing list: pkg-gnupg-maint

On Mon, 18 Sep 2017, Daniel Kahn Gillmor wrote: > Package: lists.debian.org > Severity: wishlist > > pkg-gnupg-ma...@lists.alioth.debian.org currently mostly hosts bug > reports, but it is also the maintainer address for the packages > maintained by the GnuPG packaging team, and it hosts some

Re: Alioth: the future of mailing lists

On Mon, 18 Sep 2017, Dominic Hargreaves wrote: > On Mon, Sep 18, 2017 at 09:22:34AM +, Holger Levsen wrote: > > On Mon, Sep 18, 2017 at 01:57:31AM +0100, peter green wrote: > > > Just because a team isn't big or established doesn't mean they don't need > > > a place to discuss issues

Re: How to start a new packaging team now?

On Mon, 18 Sep 2017, Michael Biebl wrote: > Am 18.09.2017 um 18:00 schrieb Jonathan Carter (highvoltage): > > > Well, it's not official yet of course but salsa.debian.org is running > > GitLab and it seems like the likely Alioth replacement. > Do I need to create a new user account for

Re: [Debconf-team] DebConf lists migration to lists.debian.org

On Sun, 17 Sep 2017, Daniel Lange wrote: > Hi, > > the DebConf team is currently preparing another try to migrate the > DebConf specific infrastructure to Debian, DSA supported, solutions. > > Along this we would like to migrate the mailing lists > > Debconf-announce Debconf

Re: How to start a new packaging team now?

On Fri, 15 Sep 2017, PICCA Frederic-Emmanuel wrote: > > Now that Alioth is beginning to close down and its replacement is not > > yet ready, how would I start this team now? > > What is the status of this migration ? which solution was selected ? For mailinglists? None. Currently no one is

[Pkg-kde-extras] qtcurve_1.8.18+git20160320-3d8622c-5~bpo9+1_amd64.changes REJECTED

If the change below is the reason for uploading this package, please don't do that. Backports is not for fixing bugs in packages, please fix that via stable update. * Add patch replace-memcmp-with-strncmp. It fixes crash when using QtCurve widget style and Breeze preset. (Closes:

Re: Single Sign On for Debian

On Fri, 25 Aug 2017, Luca Filipozzi wrote: > On Wed, Aug 23, 2017 at 09:05:32AM +0200, Xavier wrote: > > Le 23/08/2017 à 08:46, Alexander Wirt a écrit : > > > On Wed, 23 Aug 2017, Philip Hands wrote: > > > > > >> Michael Lustfield <mich...@lustfield.ne

Re: Project and User creation is now disabled on alioth.d.o

On Thu, 24 Aug 2017, Daniel Baumann wrote: > On 08/22/2017 08:13 AM, Alexander Wirt wrote: > > as alioth is deprecated and will (more or less) get replaced with other > > services soon I disabled user creation and project creation on alioth. > > while I fully under

Accepted icinga2 2.7.0-1 (source amd64 all) into unstable

amd64 all Version: 2.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group <pkg-nagios-de...@lists.alioth.debian.org> Changed-By: Alexander Wirt <formo...@debian.org> Description: icinga2- host and network monitoring system icinga2-bin - host

Re: Single Sign On for Debian

On Wed, 23 Aug 2017, Philip Hands wrote: > Michael Lustfield writes: > > ... > > Using Gitlab (or any VCS) as the user db for guest accounts means adding a > > dependency that could block future upgrades... kinda like now. This is not a > > future-proof design and will

Re: Single Sign On for Debian

On Tue, 22 Aug 2017, Mathieu Parent wrote: > Hello, > > Le mardi 22 août 2017, Luca Filipozzi <lfili...@debian.org> a écrit : > > On Mon, Aug 21, 2017 at 04:35:59PM -0700, Raoul Snyman wrote: > >> On 2017-08-21 5:48, Alexander Wirt wrote: > >> > >

Re: Single Sign On for Debian

On Mon, 21 Aug 2017, Georg Faerber wrote: > On 17-08-21 11:18:05, Enrico Zini wrote: > > On Sun, Aug 20, 2017 at 04:28:05PM +, Luca Filipozzi wrote: > > > > > As expressed during the DC17 DSA and Cloud BoFs, I'm in favour of two > > > related but orthogonal things: > > > 1 collapsing user

Re: salsa.debian.net

On Mon, 21 Aug 2017, Marcin Kulisz wrote: > On 2017-08-21 07:03:42, Salvatore Bonaccorso wrote: > > > It looks this is the new collaboration server in replacement to > > alioth: https://wiki.debian.org/Salsa . > > Just to be clear is salsa.d.o (with gitlab) replacing alioth? I thought that >

Bug#872558: scripts and other tooling

On Fri, 18 Aug 2017, Geert Stappers wrote: > > from the minutes of the Alioth Successors sprint Hamburg 2017: > > TODO: can we prepare an automation for importing existing lists > (archive + subscribers; no settings) from alioth? <- formorer said no, there won't be any kind of automation.

Re: Fwd: alioth.debian.org terms and conditions

On Wed, 16 Aug 2017, Laura Arjona Reina wrote: > Hi > I'm resending the question below to the Debian Alioth admins. No idea. Alex

Bug#701200: ferm

On Fri, 04 Aug 2017, Adam McKenna wrote: > Alright I guess I'll have to take this to debian-security then, this may > even warrant a CVE I completly disagree, but lets see what -security says. Alex

Bug#701200: ferm

On Fri, 04 Aug 2017, Adam McKenna wrote: > Alright I guess I'll have to take this to debian-security then, this may > even warrant a CVE I completly disagree, but lets see what -security says. Alex

Bug#701200: ferm

On Fri, 04 Aug 2017, Adam McKenna wrote: > That makes no sense, if that's the case then why is a default ruleset > provided for ipv4 but not ipv6? > > More and more systems are running ipv6 these days and ferm users may not > even know their systems are exposed in this way. Thats why I fixed it,

Bug#701200: ferm

On Fri, 04 Aug 2017, Adam McKenna wrote: > That makes no sense, if that's the case then why is a default ruleset > provided for ipv4 but not ipv6? > > More and more systems are running ipv6 these days and ferm users may not > even know their systems are exposed in this way. Thats why I fixed it,

Bug#701200: ferm

fixed 701200 2.4-1 thanks On Fri, 04 Aug 2017, Adam McKenna wrote: > tag 701200 security > > This is not just a bug, this is a gaping security hole. The default > configuration is wide open on ipv6. > > Please add, at a minimum, the following default rules for ipv6: This was fixed in unstable

Bug#701200: ferm

fixed 701200 2.4-1 thanks On Fri, 04 Aug 2017, Adam McKenna wrote: > tag 701200 security > > This is not just a bug, this is a gaping security hole. The default > configuration is wide open on ipv6. > > Please add, at a minimum, the following default rules for ipv6: This was fixed in unstable

Re: what's the latest on the update of moving from alioth to pagure.

On Wed, 19 Jul 2017, Geert Stappers wrote: > On Mon, Jul 17, 2017 at 05:59:14AM +0200, Alexander Wirt wrote: > > On Mon, 17 Jul 2017, shirish ??? wrote: > > > > > Dear all, > > > > > > While I love and loved alioth, I know for probably new

Re: what's the latest on the update of moving from alioth to pagure.

re discussed. I was also able to > converse with Alexander Wirt and download the survey which wasn't > available anymore for public consumption. > > Can somebody tell/share which forge are the developers looking forward > to replace alioth with, pagure or something else . > &g

Bug#774553: exim4: Do not scan outgoing mail for spam

On Thu, 13 Jul 2017, Andreas Metzler wrote: > On 2017-07-13 Alexander Wirt <formo...@debian.org> wrote: > > On Thu, 13 Jul 2017, Marc Haber wrote: > > >> On Thu, Jul 13, 2017 at 08:47:56AM +0200, Alexander Wirt wrote: > >>> I am talking about the report: &

Bug#774553: exim4: Do not scan outgoing mail for spam

On Thu, 13 Jul 2017, Marc Haber wrote: > On Thu, Jul 13, 2017 at 08:47:56AM +0200, Alexander Wirt wrote: > > I am talking about the report: > > X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up > > entirely of whitespace (char 20 hex): X-Spam

Bug#774553: exim4: Do not scan outgoing mail for spam

On Thu, 13 Jul 2017, Marc Haber wrote: > On Thu, Jul 13, 2017 at 08:47:56AM +0200, Alexander Wirt wrote: > > I am talking about the report: > > X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up > > entirely of whitespace (char 20 hex): X-Spam

Bug#774553: exim4: Do not scan outgoing mail for spam

On Thu, 13 Jul 2017, Marc Haber wrote: > On Wed, Jul 12, 2017 at 10:59:22PM +0200, Alexander Wirt wrote: > > On Sun, 04 Jan 2015, Andreas Metzler wrote: > > > On 2015-01-04 Rainer Dorsch <m...@bokomoko.de> wrote: > > > > Package: exim4 > > >

Bug#774553: exim4: Do not scan outgoing mail for spam

On Sun, 04 Jan 2015, Andreas Metzler wrote: > On 2015-01-04 Rainer Dorsch wrote: > > Package: exim4 > > Version: 4.84-6 > > Severity: wishlist > > Tags: patch > > > Dear Maintainer, > > > I am running exim since a few years and scanned incoming and > > outgoing mails for

Accepted ferm 2.4-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 11 Jul 2017 14:52:19 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.4-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <al

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

On Mon, 10 Jul 2017, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Mon, 2017-07-10 at 19:44 +, David Given wrote: > > The version in jessie of my package WordGrinder is painfully old and has a > > number of showstopping bugs (document corruption and loss of data). The next > >

Bug#867973: jessie-pu: package wordgrinder/0.5.1-1

On Mon, 10 Jul 2017, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Mon, 2017-07-10 at 19:44 +, David Given wrote: > > The version in jessie of my package WordGrinder is painfully old and has a > > number of showstopping bugs (document corruption and loss of data). The next > >

Re: alioth replacement survey

On Wed, 28 Jun 2017, Alexander Wirt wrote: > On Mon, 19 Jun 2017, Wouter Verhelst wrote: > > Hi, > > On Mon, Jun 19, 2017 at 01:49:36PM +0500, Andrey Rahmatullin wrote: > > > On Mon, Jun 19, 2017 at 09:47:30AM +0100, Jonathan Dowland wrote: > > > > Is it po

Re: alioth replacement survey

On Mon, 19 Jun 2017, Wouter Verhelst wrote: Hi, > On Mon, Jun 19, 2017 at 01:49:36PM +0500, Andrey Rahmatullin wrote: > > On Mon, Jun 19, 2017 at 09:47:30AM +0100, Jonathan Dowland wrote: > > > Is it possible to share a link to the survey results? I saw it when I > > > submitted > > > my entry,

Re: [icinga-users] Icinga service failed

On Wed, 21 Jun 2017, Umar Draz wrote: > Hi > > I have installed icinga2 on Centos 7, but it is unable to start here is the > service status This is probably a problem with the centos security glibc fix. See https://github.com/Icinga/icinga2/issues/5367 for details and a workaround. Alex

alioth replacement survey

Hi, to get some idea about opinions and expectations for the alioth replacement I decided to create a survey. Please take part in it [1] if you are interested in it. If you need some background, I recommend to read the excellent LWN article [2] by anarcat first. Thanks for your help Alex [1]

Bug#863802: severity of 863802 is wishlist

severity 863802 wishlist thanks As discussed, I don't this is a bug.

Bug#863802: severity of 863802 is wishlist

severity 863802 wishlist thanks As discussed, I don't this is a bug.

Bug#864289: RM: schleuder/3.0.1-1

On Tue, 06 Jun 2017, Georg Faerber wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: rm > Severity: normal > > Hi all, > > Please remove schleuder from stretch. It's not yet ready to be included > in the stable suite; we plan to get it into s-bp

Bug#864289: RM: schleuder/3.0.1-1

On Tue, 06 Jun 2017, Georg Faerber wrote: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: rm > Severity: normal > > Hi all, > > Please remove schleuder from stretch. It's not yet ready to be included > in the stable suite; we plan to get it into s-bp

Bug#863864: [Pkg-nagios-devel] Bug#863864: release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)

On Thu, 01 Jun 2017, Johannes Ranke wrote: > Package: release-notes > Severity: normal > > I assume that switching to icinga is possible, but I am missing a hint in the > release notes. Will icinga use nagios configuration files? No, and those files are not fully compatible. You will have to

Bug#863864: [Pkg-nagios-devel] Bug#863864: release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)

On Thu, 01 Jun 2017, Johannes Ranke wrote: > Package: release-notes > Severity: normal > > I assume that switching to icinga is possible, but I am missing a hint in the > release notes. Will icinga use nagios configuration files? No, and those files are not fully compatible. You will have to

Bug#863802: systemd unit breaks ferm in some setups in jessie->stretch upgrade

On Wed, 31 May 2017, Moritz Muehlenhoff wrote: > Package: ferm > Version: 2.3-2 > Severity: grave > > Ferm is broken in stretch for any rule set which contains resolve() > statements. > (There might be others relying on network, didn't check). This got introduced > in 2.3-2, which now uses a

Bug#863802: systemd unit breaks ferm in some setups in jessie->stretch upgrade

On Wed, 31 May 2017, Moritz Muehlenhoff wrote: > Package: ferm > Version: 2.3-2 > Severity: grave > > Ferm is broken in stretch for any rule set which contains resolve() > statements. > (There might be others relying on network, didn't check). This got introduced > in 2.3-2, which now uses a

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Wed, 24 May 2017, Raphael Hertzog wrote: > On Wed, 24 May 2017, Alexander Wirt wrote: > > It is maybe a problem and maybe we should get the policy changed - I > > personally don't think too. I don't wan't software that isn't in testing in > > backports - but doin

Re: [Python-modules-team] python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED

On Tue, 23 May 2017, Scott Kitterman wrote: > > > On May 23, 2017 5:28:04 PM EDT, Alexander Wirt <formo...@formorer.de> wrote: > >On Tue, 23 May 2017, Raphael Hertzog wrote: > > > >> (please cc me on answers) > >> > >> On Tue, 23

<    1   2   3   4   5   6   7   8   9   10   >