Hi
On Sat, Dec 22, 2012 at 11:48:33AM +0100, Ivo De Decker wrote:
> Control: fixed -1 2.9.2.2-3
>
> Hi Salvatore,
>
> On Sat, Dec 22, 2012 at 11:13:26AM +0100, Salvatore Bonaccorso wrote:
> > Control: tags -1 + squeeze
> > Control: notfound -1 2.9.2.2-3
>
> [...]
>
> > But I tried too to check
Control: fixed -1 2.9.2.2-3
Hi Salvatore,
On Sat, Dec 22, 2012 at 11:13:26AM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + squeeze
> Control: notfound -1 2.9.2.2-3
[...]
> But I tried too to check the Squeeze -> Wheezy update, and like you
> was not able to repoduce.
> Does the above
Control: tags -1 + squeeze
Control: notfound -1 2.9.2.2-3
Hi Gregor
On Thu, Dec 20, 2012 at 10:11:43PM +0100, gregor herrmann wrote:
> On Thu, 20 Dec 2012 04:35:52 +0100, Andreas Beckmann wrote:
>
> > The problem is still reproducible in a lenny->squeeze upgrade.
>
> Hm, at least _I_ don't care
Package: snort-pgsql,snort-mysql
Followup-For: Bug #603428
Control: found -1 2.8.5.2-8
The problem is still reproducible in a lenny->squeeze upgrade.
Setting up snort-common (2.8.5.2-8) ...
Installing new version of config file /etc/snort/threshold.conf ...
Configuration file `/etc/snort
On Tue, Dec 21, 2010 at 05:23:39PM +0100, Julien Cristau wrote:
> On Tue, Dec 21, 2010 at 17:07:09 +0100, Javier Fernandez-Sanguino wrote:
>
> > Becas right now, with the current code, changes gets overwritten by debconf
> > on package (re)configuration.
> >
> That sounds like a serious bug in th
On Tue, Dec 21, 2010 at 17:07:09 +0100, Javier Fernandez-Sanguino wrote:
> Becas right now, with the current code, changes gets overwritten by debconf
> on package (re)configuration.
>
That sounds like a serious bug in the maintainer scripts then. Why not
fix that?
Cheers,
Julien
signature.as
Becas right now, with the current code, changes gets overwritten by debconf
on package (re)configuration.
Just like it previously happened with a given section of the config file.
Regards
Javier
El 20/12/2010 22:22, "Julien Cristau" escribió:
On Mon, Dec 20, 2010 at 22:20:35 +0100, Javier Fer
On Mon, Dec 20, 2010 at 22:20:35 +0100, Javier Fernandez-Sanguino wrote:
> Which warning? The NEWS file or the header in the autogenerated config file?
>
> I do not see any harm in either. Can you please elaborate?
>
The config file. Why would you want to discourage editing that
directly?
Chee
Which warning? The NEWS file or the header in the autogenerated config file?
I do not see any harm in either. Can you please elaborate?
Javier
El 20/12/2010 16:48, "Julien Cristau" escribió:
On Mon, Dec 20, 2010 at 15:57:17 +0100, Javier Fernández-Sanguino Peña
wrote:
> On Mon, Dec 20, 201...
On Mon, Dec 20, 2010 at 15:57:17 +0100, Javier Fernández-Sanguino Peña wrote:
> On Mon, Dec 20, 2010 at 03:24:57PM +0100, Javier Fernández-Sanguino Peña
> wrote:
> > I see some issues with this bug. Some are minor (typos in the changelog and
> > the text) but the most important thing is: there is
On Mon, Dec 20, 2010 at 03:24:57PM +0100, Javier Fernández-Sanguino Peña wrote:
> I see some issues with this bug. Some are minor (typos in the changelog and
> the text) but the most important thing is: there is no NEWS file so
> that users are forewarned of this (important) change.
Upon review, I
Hi!
* Javier Fernández-Sanguino Peña [101220 15:24]:
> I would like to pick it up and carry it over from here... if I may.
Sure, I'm glad I could be of help :)
> It seems you already did a NMU, so I might overwrite it with a new
> release (using your patch).
Yes, I tried to do an NMU, but it
On Fri, Dec 17, 2010 at 02:57:39PM +0100, Alexander Reichle-Schmehl wrote:
> * Alexander Reichle-Schmehl [101216 14:14]:
>
> > The only part missing would to make sure, snort-{mysql,pgsql} write into
> > the new file instead of the old one, and purge the new file. But the
> > main part taking ca
tags 603428 +patch
tags 603428 +penting
thanks
Hi!
* Alexander Reichle-Schmehl [101216 14:14]:
> The only part missing would to make sure, snort-{mysql,pgsql} write into
> the new file instead of the old one, and purge the new file. But the
> main part taking care of this bug can already be r
Hi!
* Alexander Reichle-Schmehl [101208 10:37]:
> It seems that upon installation of snort-pgsql or snort-mysql
> /etc/snort/snort.conf is changed. As this file actually belongs to
> snort-common, upgrade of that package fails.
>
> So, to solve this bug, snort-common should remove these entrie
Hi!
* Holger Levsen [101114 01:02]:
> But this is not the real problem, the real problem is that this prompt
> shows up in the first place, as there was nobody modifying this
> conffile at all, the package has just been installed and upgraded...
It seems that upon installation of snort-pgsql o
16 matches
Mail list logo
