Bug#831745: [Pkg-nagios-devel] Bug#831745: icinga2: file/directory permission issues

Am 18.07.2016 um 23:33 schrieb Christoph Anton Mitterer: Oh and I've just noted: On Mon, 2016-07-18 at 23:21 +0200, Christoph Anton Mitterer wrote: But, AFAIU, this is set by DAEMON_USER, DAEMON_GROUP and DAEMON_CMDGROUP, which can be nicely configured in /etc/default/icinga2 . This is not

Bug#831745: [Pkg-nagios-devel] Bug#831745: icinga2: file/directory permission issues

tag 831745 moreinfo thanks Am 18.07.2016 um 23:21 schrieb Christoph Anton Mitterer: Source: icinga2 Version: 2.4.10-1 Severity: important Tags: security Hi. Several files in Icinga2 are shipped with owner www-data, namely at least these: /var/cache/icinga2 drwxr-x--- 2 nagios www-data

qtcreator_4.0.2-1~bpo8+1_amd64.changes REJECTED

Breaks stable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

qbs_1.5.1+dfsg-1~bpo8+1_amd64.changes REJECTED

Breaks stable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

Bug#831532: [Pkg-nagios-devel] Bug#831532: Bug#831532: icingaweb2: handle auth DB with dbconfig-common

On Sun, 17 Jul 2016, Christoph Anton Mitterer wrote: > Hey Alex. > > On Sun, 2016-07-17 at 08:28 +0200, Alexander Wirt wrote: > > given our experience with dbconfig in icinga2, this won't happen. > > Oh I wasn't aware that there were bigger troubles (other than those >

Bug#831532: [Pkg-nagios-devel] Bug#831532: icingaweb2: handle auth DB with dbconfig-common

tag 831532 wontfix thanks On Sun, 17 Jul 2016, Christoph Anton Mitterer wrote: > Source: icingaweb2 > Severity: wishlist > > > Hi. > > Currently, icingaweb2 doesn't set up/manage the Icinga Web 2 specific DBs > at all, it even doesn't depend on php-mysql|php-pgsql... > > This is of course

Bug#831059: lists.debian.org: Permanently banned users cannot send positive contributions to lists.debian.org

On Thu, 14 Jul 2016, Javier Serrano Polo wrote: > Package: lists.debian.org > Severity: wishlist > > Some users want to contribute to Debian, but they exceptionally make > disruptive contributions to lists.debian.org and are permanently banned. > > For instance, this banned user is helping with

Bug#830865: lists.debian.org: Message forwarding (still) breaks DKIM signatures

On Tue, 12 Jul 2016, Marco Solieri wrote: > Package: lists.debian.org > Severity: normal > > It seems that the email forward process still has problem preserving > integrity of messages, which guarantees DKIM signatures to be verifiable > by recipients' servers receiving such messages. Indeed,

Re: Thinking about a "jessie and a half" release

On Thu, 07 Jul 2016, Riku Voipio wrote: > On Mon, Jul 04, 2016 at 02:01:03PM +0100, Steve McIntyre wrote: > > There's something I've been pondering for a while, along with some > > other folks - it might be useful to do a "jessie and a half" release, > > similarly to what we did in the etch days.

Re: Thinking about a "jessie and a half" release

On Thu, 07 Jul 2016, Riku Voipio wrote: > On Mon, Jul 04, 2016 at 02:01:03PM +0100, Steve McIntyre wrote: > > There's something I've been pondering for a while, along with some > > other folks - it might be useful to do a "jessie and a half" release, > > similarly to what we did in the etch days.

Re: Thinking about a "jessie and a half" release

On Thu, 07 Jul 2016, Riku Voipio wrote: > On Mon, Jul 04, 2016 at 02:01:03PM +0100, Steve McIntyre wrote: > > There's something I've been pondering for a while, along with some > > other folks - it might be useful to do a "jessie and a half" release, > > similarly to what we did in the etch days.

Re: Thinking about a "jessie and a half" release

On Thu, 07 Jul 2016, Riku Voipio wrote: > On Mon, Jul 04, 2016 at 02:01:03PM +0100, Steve McIntyre wrote: > > There's something I've been pondering for a while, along with some > > other folks - it might be useful to do a "jessie and a half" release, > > similarly to what we did in the etch days.

Re: Neomutt packages available

On Fri, 24 Jun 2016, Elimar Riesebieter wrote: > * Jonathan Dowland [2016-06-24 09:24 +0100]: > > > On Thu, Jun 23, 2016 at 09:10:50PM +0200, Elimar Riesebieter wrote: > > > I am pleased to announce the availability of neomutt [0] packages for > > > Debian. Hints for

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 22 Jun 2016, Pirate Praveen wrote: > [adding gitlab folks in cc] > > On Saturday 11 June 2016 02:16 PM, Alexander Wirt wrote: > > On Sat, 11 Jun 2016, Ole Streicher wrote: > > > >> Pirate Praveen <prav...@onenetbeyond.org> writes: > >&g

Accepted icingaweb2 2.3.4-1 (source all) into unstable

: medium Maintainer: Debian Nagios Maintainer Group <pkg-nagios-de...@lists.alioth.debian.org> Changed-By: Alexander Wirt <formo...@debian.org> Description: icingacli - simple CLI tool for Icingaweb2 and its modules icingaweb2 - simple and responsive web interface for Icinga icing

Bug#827757: [Pkg-nagios-devel] Bug#827757: apt-get upgrade doesn't want to upgrade packages in need of an upgrade

On Mon, 20 Jun 2016, David Kalnischkies wrote: > Control: reassign -1 monitoring-plugins-basic > > On Mon, Jun 20, 2016 at 04:52:37PM +0200, Christoph Anton Mitterer wrote: > > apt however, doesn't upgade: > > # apt-get upgrade > > "apt-get upgrade" is documented to not install new (or remove)

Bug#827596: suricata: Illegal instruction issue in Raspberry Pi B [jessie-backports][Raspbian Jessie Lite]

On Sat, 18 Jun 2016, Arturo Borrero Gonzalez wrote: > Source: suricata > Version: 3.0.1-2~bpo8+1 > Severity: important > > A suricata user using Raspeberry Pi B with Raspbian Jessie Lite reports > problems when using the package from jessie-backports: > > pi@raspberrypi:~ $ suricata

Bug#826764: Co-maintaining cgit

On Wed, 15 Jun 2016, Peter Colberg wrote: > Hi Alex, > > I have pushed a new commit that Closes: #827405 in the changelog. Yeah, I am currently testing the package. Thanks for your work! Alex

Accepted ferm 2.3-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Jun 2016 19:48:04 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.3-2 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <formo...@d

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Sat, 11 Jun 2016, Ole Streicher wrote: > Pirate Praveen writes: > >> Debian needs feature X but it is already in the e.nterprise version. We > >> make > >> a patch and for commercial reasons it never gets merged (they already sell > >> it > >> in the enterprise

Re: Pagure and Gitolite for project+code hosting

On Thu, 09 Jun 2016, Ben Finney wrote: > Ben Finney writes: > > > Barry Warsaw writes: > > > > > Another possible option is Pagure > > > https://pagure.io/ > > > > Wow, that's an attractive option. Thanks! > > Recently reviewed at Linux Weekly

Bug#826764: Co-maintaining cgit

On Wed, 08 Jun 2016, Peter Colberg wrote: > On Wed, Jun 08, 2016 at 11:28:32PM +0200, Alexander Wirt wrote: > > I added pkg-cgit-devel and pkg-cgit-commits > > Thanks, I subscribed to pkg-cgit-devel. > > Would you mind if we rename the repository from pkg-cgit/pkg-c

Bug#826764: Co-maintaining cgit

On Wed, 08 Jun 2016, Peter Colberg wrote: > On Wed, Jun 08, 2016 at 10:29:18PM +0200, Alexander Wirt wrote: > > Here we are: https://alioth.debian.org/scm/?group_id=101009 > > > > I already pushed the existing repo to the new git repo. > > Please request to get

Bug#826764: Co-maintaining cgit

On Wed, 08 Jun 2016, Peter Colberg wrote: > On Wed, Jun 08, 2016 at 09:53:00PM +0200, Alexander Wirt wrote: > > I would be happy to accept you as co-maintainer, > > Great! > > > but I am not a big fan of collab-maint. Is github ok for you? > > Otherwise I would cr

Bug#826764: Co-maintaining cgit

On Wed, 08 Jun 2016, Peter Colberg wrote: > Source: cgit > Severity: wishlist > > Hi Alexander, > > I have been using cgit on a personal server for the better part of a > decade. Now that I have applied to become Debian maintainer [1–3], I > am interested in helping maintain cgit. I closely

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 08 Jun 2016, Jonathan Dowland wrote: > On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > > I am also not very keen on using a system with a "open core / enterprise" > > model. For such a crucial service I would really prefer a real open source &

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 08 Jun 2016, Alexandre Viau wrote: > On 08/06/16 07:57 AM, Alexander Wirt wrote: > > On Wed, 08 Jun 2016, Antonio Terceiro wrote: > > > >> On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > >> for authentication, I think you s

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 08 Jun 2016, Antonio Terceiro wrote: > On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > > On Wed, 08 Jun 2016, Pirate Praveen wrote: > > > > > On Wednesday 08 June 2016 01:07 AM, Bastian Blank wrote: > > > > [SN: trimmed Cc list

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

; On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > > >>> I am also not very keen on using a system with a "open core / > > >>> enterprise" > > >>> model. For such a crucial service I would really prefer a real open > > >

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 08 Jun 2016, Jonathan Dowland wrote: > On Tue, Jun 07, 2016 at 10:25:07AM +0530, Pirate Praveen wrote: > > Thanks for the offer. It would be great if I have more hands to help with > > migrating git.debian.org > > Whoah there. Running an official Debian gitlab instance is one thing, >

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Wed, 08 Jun 2016, Pirate Praveen wrote: > On Wednesday 08 June 2016 01:07 AM, Bastian Blank wrote: > > [SN: trimmed Cc list, as this is about what Debian wants] > > > > Hi Alex > > > > On Tue, Jun 07, 2016 at 08:06:41PM +0200, Alexander Wirt

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Tue, 07 Jun 2016, Pirate Praveen wrote: > > > On 2016, ജൂൺ 6 11:47:01 PM IST, Ean Schuessler wrote: > >We run GitLab on gitlab.brainfood.com and think it is really great. Let > >us > >know if there is some way we can help. > > Thanks for the offer. It would be great if

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Tue, 07 Jun 2016, Pirate Praveen wrote: > On Tuesday 07 June 2016 08:46 PM, Alexander Wirt wrote: > > On Tue, 07 Jun 2016, Pirate Praveen wrote: > > > >> On Tuesday 07 June 2016 10:31 AM, Luca Filipozzi wrote: > >>> On Tue, Jun 07, 2016 at 10

Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)

On Tue, 07 Jun 2016, Pirate Praveen wrote: > On Tuesday 07 June 2016 10:31 AM, Luca Filipozzi wrote: > > On Tue, Jun 07, 2016 at 10:19:48AM +0530, Pirate Praveen wrote: > >> On 2016, ജൂൺ 6 10:37:25 PM IST, Tollef Fog Heen wrote: > >>> Another prerequisite for d.o hosting is that

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

amd64 all Version: 2.4.10-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

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

amd64 all Version: 2.4.9-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

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 17 May 2016 13:25:05 +0200 Source: keepalived Binary: keepalived Architecture: source amd64 Version: 1:1.2.20-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexande

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

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

Bug#756479: [Pkg-nagios-devel] Bug#756479: Bug#756479: nagios-nrpe-server: Ignores dont_blame_nrpe=1

On Tue, 10 May 2016, Falk Brockerhoff wrote: > Alex, > > I understand that you aren’t happy as the maintainer of this package. > Unfortunately I don’t have any coding skills, so that I’m not able to support > you. Sorry for this. > > But I’m a user of this package and really do need the

Accepted ferm 2.3-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 30 Apr 2016 12:07:50 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.3-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <formo...@d

Bug#756479: [Pkg-nagios-devel] Bug#756479: nagios-nrpe-server: Ignores dont_blame_nrpe=1

On Sat, 23 Apr 2016, Jan Tomasek wrote: > Hi, > > I'm another one who spend some time examining why after upgrade is nrpe > not working. > > I've read whole thread about this Bug#756479 and can't find any > reference to description how to to exploit nagios-nrpe-server with > >

Accepted ferm 2.2-5 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 23 Apr 2016 07:54:53 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.2-5 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <formo...@d

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

amd64 all Version: 2.4.7-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

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

amd64 all Version: 2.4.6-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

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

amd64 all Version: 2.4.5-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

Accepted ferm 2.2-4 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 20 Apr 2016 11:31:54 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.2-4 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt <formo...@d

Bug#810506: Upload of linux-grsec to jessie-backports?

On Sat, 16 Apr 2016, Yves-Alexis Perez wrote: > On mar., 2016-03-22 at 13:30 +0100, Yves-Alexis Perez wrote: > > On mar., 2016-03-22 at 13:22 +0100, Alexander Wirt wrote: > > > > > > You - or better more than one person - promise to support this kernel for >

Bug#810506: Upload of linux-grsec to jessie-backports?

On Sat, 16 Apr 2016, Yves-Alexis Perez wrote: > On mar., 2016-03-22 at 13:30 +0100, Yves-Alexis Perez wrote: > > On mar., 2016-03-22 at 13:22 +0100, Alexander Wirt wrote: > > > > > > You - or better more than one person - promise to support this kernel for >

Bug#821113: Rethink d-s-a Reply-To to avoid frustrated users and administrivia/off-topic floods

On Fri, 15 Apr 2016, Drake Wilson wrote: > Package: lists.debian.org > Severity: important > > We seem to be having a recurring problem of people who want off > debian-security-announce > unintentionally bothering debian-security about it, or trying to unsubscribe > to the latter > list and

Bug#783495: amavisd-new: Typo in Recommends: should be libnet-patricia-perl instead of libnet-patricial-perl

On Wed, 13 Apr 2016, Salvatore Bonaccorso wrote: > Hi Brian, > > Can the typofix be included in the next uplaod to unstable? It > actually would be nice to have the Recommends correct as well back to > stable via a point release. > > The typo was there from the beginning when it was added,

[DRE-maint] ruby-trollop_2.0-2~bpo8+1_amd64.changes REJECTED

This is the same version as in stable. Are you just uploading every dependency of gitlab? Don't do this. Only upload things you really need. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our

Re: Minor issues with collab-maint

On Sat, 02 Apr 2016, Tiago Ilieve wrote: > Hi, > > I'm having some minor issues with collab-maint today and didn't found > where to report it properly. There's a "collab-maint-devel"[1] list, > but there isn't any activity in there since June/2009. Please point > me to the correct mailing list

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 08:24, Alexander Wirt <formo...@debian.org> wrote: > > On Tue, 29 Mar 2016, Felipe Sateler wrote: > > > >> On 29 Mar 2016 08:10, "Alexander Wirt" <formo...@debian.org> wrote: > >

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 08:24, Alexander Wirt <formo...@debian.org> wrote: > > On Tue, 29 Mar 2016, Felipe Sateler wrote: > > > >> On 29 Mar 2016 08:10, "Alexander Wirt" <formo...@debian.org> wrote: > >

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 Mar 2016 08:10, "Alexander Wirt" <formo...@debian.org> wrote: > > > > On Tue, 29 Mar 2016, Felipe Sateler wrote: > > > > > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrot

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 Mar 2016 08:10, "Alexander Wirt" <formo...@debian.org> wrote: > > > > On Tue, 29 Mar 2016, Felipe Sateler wrote: > > > > > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrot

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrote: > > On Mon, 28 Mar 2016, Felipe Sateler wrote: > > > >> On 5 March 2016 at 19:54, Sam Morris <s...@robots.org.uk> wrote: > &

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrote: > > On Mon, 28 Mar 2016, Felipe Sateler wrote: > > > >> On 5 March 2016 at 19:54, Sam Morris <s...@robots.org.uk> wrote: > &

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrote: > > On Mon, 28 Mar 2016, Felipe Sateler wrote: > > > >> On 5 March 2016 at 19:54, Sam Morris <s...@robots.org.uk> wrote: > &

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 March 2016 at 04:11, Alexander Wirt <formo...@debian.org> wrote: > > On Mon, 28 Mar 2016, Felipe Sateler wrote: > > > >> On 5 March 2016 at 19:54, Sam Morris <s...@robots.org.uk> wrote: > &

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 Mar 2016 04:03, "Felix Geyer" wrote: > > > > Hi Felipe, > > > > On Mon, 28 Mar 2016 20:56:48 -0300 Felipe Sateler > wrote: > > > I have uploaded an nmu. I have made the unit call out to the init > > >

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felipe Sateler wrote: > On 29 Mar 2016 04:03, "Felix Geyer" wrote: > > > > Hi Felipe, > > > > On Mon, 28 Mar 2016 20:56:48 -0300 Felipe Sateler > wrote: > > > I have uploaded an nmu. I have made the unit call out to the init > > >

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felix Geyer wrote: > Hi Felipe, > > On Mon, 28 Mar 2016 20:56:48 -0300 Felipe Sateler wrote: > > I have uploaded an nmu. I have made the unit call out to the init > > script, because it does more work than simply invoking ferm. > > > > Please find

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Tue, 29 Mar 2016, Felix Geyer wrote: > Hi Felipe, > > On Mon, 28 Mar 2016 20:56:48 -0300 Felipe Sateler wrote: > > I have uploaded an nmu. I have made the unit call out to the init > > script, because it does more work than simply invoking ferm. > > > > Please find

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Mon, 28 Mar 2016, Felipe Sateler wrote: > On 5 March 2016 at 19:54, Sam Morris wrote: > > severity 796611 grave > > thanks > > > > This is currently causing my system to boot without networking. I am > > increasing the severity since other (rather important!) packages are

Bug#796611: ferm causes a unit ordering cycle that breaks booting

On Mon, 28 Mar 2016, Felipe Sateler wrote: > On 5 March 2016 at 19:54, Sam Morris wrote: > > severity 796611 grave > > thanks > > > > This is currently causing my system to boot without networking. I am > > increasing the severity since other (rather important!) packages are

Re: Archive of squeeze-lts ?

On Thu, 24 Mar 2016, Luke Hall wrote: > Hi, > > I'm seeing this when trying to fetch lts packages from > archive.debian.org at the moment. Anyone know a good contact for them? > > E: Release file expired, ignoring > http://archive.debian.org/debian/dists/squeeze-lts/Release (invalid > since 9d

Bug#810506: Upload of linux-grsec to jessie-backports?

On Tue, 22 Mar 2016, Yves-Alexis Perez wrote: Hi, > On mar., 2016-03-22 at 11:57 +0100, Alexander Wirt wrote: > > On Tue, 22 Mar 2016, Julien Cristau wrote: > > > It won't be in testing if it's not suitable for stable.  That would > > > defeat the purpose of t

Bug#810506: Upload of linux-grsec to jessie-backports?

On Tue, 22 Mar 2016, Yves-Alexis Perez wrote: Hi, > On mar., 2016-03-22 at 11:57 +0100, Alexander Wirt wrote: > > On Tue, 22 Mar 2016, Julien Cristau wrote: > > > It won't be in testing if it's not suitable for stable.  That would > > > defeat the purpose of t

Re: [icinga-users] Icinga2 master/sattelite communication direction?

On Mon, 21 Mar 2016, Bauknecht, Sven wrote: > Hi Alex, > > Ok - just to get it right for my brain ;) - I am using the example from the > docs how to configure distributed zones > ## Original example: > object Endpoint "nuremberg-master" { > host = "nuremberg.icinga.org" > } > > object

Re: [icinga-users] Icinga2 master/sattelite communication direction?

On Mon, 21 Mar 2016, Bauknecht, Sven wrote: > This sounds great! - is there any detail in the docs I oviously missed/did > not find yet? If an endpoint objects has assigned a host attribute [1] icinga2 will try to connect to it. If there is no host attribute, no connection is attempted. If

Re: [icinga-users] Icinga2 master/sattelite communication direction?

On Mon, 21 Mar 2016, Bauknecht, Sven wrote: > Hello list, > > I am finally back to Icinga again and I am looking for detailed information > how the master <-> sattelite communication on Icinga2 works. I have the > requirement (security topolgy of the network), that connection initiation is >

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

amd64 all Version: 2.4.4-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: Changing the "Reply-To:" for debian-security-announce (Was: "[SECURITY] [DSA 3501-1] perl security update")

On Wed, 02 Mar 2016, Grond wrote: > I'll second this motion. > > A good proportion of the traffic I get from debian-security > is simply silly people trying to unsubscribe themselves from > debian-security-announce by replying to DSAs. > > And while most of them do not respond with empty

Accepted cgit 0.12.0.git2.7.0-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 01 Mar 2016 14:10:45 +0100 Source: cgit Binary: cgit Architecture: source amd64 Version: 0.12.0.git2.7.0-1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt <formo...@debian.org> Changed-By: Alexander Wirt

Re: [icinga-users] Icinga2 2.4.3 trusty missing?

On Thu, 25 Feb 2016, Zachary McGibbon wrote: > Looking on http://packages.icinga.org/ubuntu/pool/main/i/icinga2/ I only > see builds for precise and not for other versions of ubuntu? > > Are the other builds coming? Of course. Please learn to be more patient. Alex

forensics-all_1.0~bpo8+1_amd64.changes REJECTED

Package is not in testing. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ forensics-devel mailing list

Re: [icinga-users] Still having issues with configuration

On Fri, 12 Feb 2016, Laura DiMauro wrote: > > Hi Michael, > I apologize. I thought I included the log detail. Here it is. > The log states the following: > > [2016-02-12 03:43:29 -0700] critical/IdoMysqlConnection: Exception during > database operation: Verify that your database is

Re: amavis database

On Tue, 09 Feb 2016, Michael H wrote: > Hi All, > > I'm having trouble connecting to the mysql database for amavis, I've got > a lot of quarantined mail that I would like to clean up. > > What is the default username / password / database name for amavis? I > didn't set any username or password

Bug#813969: O: eyed3

Package: wnpp Severity: normal Hi, I don't use eyed3 anymore, nor do I python anymore. The new eyed3 buildsystem is also fishy and I wasn't able to release a package based on recent versions. Therefore it would be best if I orphan this package and give it to someone more familiar with python.

Bug#812411: cgit: diff for NMU version 0.11.2.git2.3.2-1.1

On Sun, 07 Feb 2016, Salvatore Bonaccorso wrote: > Control: tags 812411 + pending > > Hi Alexander, > > I've prepared an NMU for cgit (versioned as 0.11.2.git2.3.2-1.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Thats wonderful. Thanks for your

Bug#813969: O: eyed3

Package: wnpp Severity: normal Hi, I don't use eyed3 anymore, nor do I python anymore. The new eyed3 buildsystem is also fishy and I wasn't able to release a package based on recent versions. Therefore it would be best if I orphan this package and give it to someone more familiar with python.

Re: [icinga-users] include_once(HTMLPurifier.php): failed to open stream: No such file or directory

On Wed, 03 Feb 2016, Eric Lippmann wrote: > Hi, > > Debian / Ubuntu packages are broken atm. Please run > > apt-get install php-htmlpurifier Its more that the embedded version is broken and not the package. Not all ubuntu versions have a recent php-htmlpurifier. Alex

Re: [icinga-users] include_once(HTMLPurifier.php): failed to open stream: No such file or directory

On Wed, 03 Feb 2016, Eric Lippmann wrote: > Hi Alex, > > It is the package. Markus and me will take care of that tomorrow. what about telling me - one of the packagers - the details? Alex ___ icinga-users mailing list icinga-users@lists.icinga.org

Re: [icinga-users] New installation, per instructions, "Backend icinga is not running"

On Thu, 28 Jan 2016, Simpson Lachlan wrote: > Hi All, > > Just installed Icinga2 and Icinga2 web on Centos 7.2. Looks great. > > On the System->Monitoring Health page I see a red button and the notice: > > Backend icinga is not running > > How do I fix this? Thats a known bug, just ignore it

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

On Fri, 22 Jan 2016, Fabien COELHO wrote: > > Hello Alexander, > > > ISTM that you did not answer about my point that the current configuration > file is misleading, as the 'dont_blame_nrpe' option is ignored but there is > no warning about that fact in the file nor in the log. If it had been

Bug#756479: [Pkg-nagios-devel] Bug#756479: (no subject)

On Fri, 22 Jan 2016, Fabien COELHO wrote: > > Sigh. I've lost 1 hour on this "improvement". > > Please note that there is still a bug: the installed "/etc/nagios/nrpe.cfg" > configuration file now contains a option which is ignored, but AFAICS there > is no warning about that fact in the file

Re: [icinga-users] No historical data with Icinga2 Web2 and IDO

On Thu, 21 Jan 2016, Eric Lippmann wrote: > Hi, > > Which versions of Web 2 and Icinga 2 are you using? Why IDO PostgreSQL and > IDO MySQL? You may only have one. > > Please post which Icinga 2 features are enabled. That one was already solved in IRC (wrong categories setting) Alex

Re: [icinga-users] Service check already exists

On Thu, 14 Jan 2016, Rob DeSanno wrote: > I’m trying to configure a check in icinga to validate the age of our hourly, > daily, and monthly backups on server “backup” but icinga doesn’t like the way > I have it configured. I am pasting the error message as well as lines 131 - > 158 for

Bug#807452: Backporting ikiwiki

On Sun, 10 Jan 2016, Sean Whitton wrote: > Dear Simon, > > Thanks for getting back to me on this. > > On Sun, Jan 10, 2016 at 01:34:59PM +, Simon McVittie wrote: > > The .deb of ikiwiki in testing/unstable is installable on stable, and I > > intend to keep that true (it doesn't contain any

Re: Fwd: git URL wrong on anonscm.debian.org

On Sat, 09 Jan 2016, Roger Shimizu wrote: > On Sat, Jan 9, 2016 at 12:19 AM, Alexander Wirt <formo...@debian.org> wrote: > > On Sat, 09 Jan 2016, Roger Shimizu wrote: > >> https://anonscm.debian.org/git/kernel/linux.git > > All those urls work for cloning. > >

Re: Fwd: git URL wrong on anonscm.debian.org

On Sat, 09 Jan 2016, Roger Shimizu wrote: > I want to report a bug regarding to {anonscm,git}.debian.org, but I > don't find a pseudo package to file bugreport to, so I contacted > ad...@alioth.debian.org, but no reply yet for nearly 1 month. > > I hope maybe someone here can help. Thank you! >

Re: Bug#807019: tracking bin-num - broken unison due to binnmu upload

On Tue, 29 Dec 2015, Alexandre Rossi wrote: > Hi, > > >> The change done in unison 2.48 to overcome this looks pretty big... I'm > >> not sure I'll be able/willing to provide a unison2.40.102 any more. > >> Moreover, this package was created to provide compatibility with > >> previous Debian

Bug#807019: tracking bin-num - broken unison due to binnmu upload

On Tue, 29 Dec 2015, Alexandre Rossi wrote: > Hi, > > >> The change done in unison 2.48 to overcome this looks pretty big... I'm > >> not sure I'll be able/willing to provide a unison2.40.102 any more. > >> Moreover, this package was created to provide compatibility with > >> previous Debian

Bug#807019: tracking bin-num - broken unison due to binnmu upload

On Tue, 29 Dec 2015, Alexandre Rossi wrote: > Hi, > > >> The change done in unison 2.48 to overcome this looks pretty big... I'm > >> not sure I'll be able/willing to provide a unison2.40.102 any more. > >> Moreover, this package was created to provide compatibility with > >> previous Debian

Bug#807019: tracking bin-num - broken unison due to binnmu upload

On Tue, 29 Dec 2015, Alexandre Rossi wrote: > Hi, > > >> The change done in unison 2.48 to overcome this looks pretty big... I'm > >> not sure I'll be able/willing to provide a unison2.40.102 any more. > >> Moreover, this package was created to provide compatibility with > >> previous Debian

Re: [DRE-maint] Updating ruby-minitar / ruby-archive-tar-minitar

On Wed, 16 Dec 2015, Markus Frosch wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 16.12.2015 02:22, Sebastien Badia wrote: > > Hum, and it's seems a bit more complicated > > https://github.com/atoulme/minitar/issues/3 (but the upstream doesn't have > > any release…) > >

Re: [DRE-maint] Updating ruby-minitar / ruby-archive-tar-minitar

On Wed, 16 Dec 2015, Markus Frosch wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 16.12.2015 02:22, Sebastien Badia wrote: > > Hum, and it's seems a bit more complicated > > https://github.com/atoulme/minitar/issues/3 (but the upstream doesn't have > > any release…) > >

Re: Administrators and moderators of ubuntu-devel list, please erase all the messages that I not should have posted here in debian-devel list!

On Thu, 10 Dec 2015, françai s wrote: > Please excuse me, I want say "Administrators and moderators of debian-devel > list", I not want say "Administrators and moderators of ubuntu-devel list. > > 2015-12-10 13:42 GMT-02:00 françai s : > > > Administrators and moderators

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

Version: 2.4.1-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 and network monit

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