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 a lot
Processing control commands:
tags -1 + squeeze
Bug #603428 [snort-pgsql,snort-mysql] snort: prompting due to modified
conffiles which where not modified by the user
Added tag(s) squeeze.
notfound -1 2.9.2.2-3
Bug #603428 [snort-pgsql,snort-mysql] snort: prompting due to modified
conffiles
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
Processing control commands:
fixed -1 2.9.2.2-3
Bug #603428 [snort-pgsql,snort-mysql] snort: prompting due to modified
conffiles which where not modified by the user
Marked as fixed in versions snort/2.9.2.2-3.
--
603428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603428
Debian Bug
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 the Squeeze
On Sat, 22 Dec 2012 11:48:33 +0100, Ivo De Decker wrote:
But I tried too to check the Squeeze - Wheezy update, and like you
was not able to repoduce.
Does the above control changes reflect this correctly for the BTS?
I don't think so:
notfound removes a previous indication that the
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
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 the
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 jcris...@debian.org escribió:
On Mon, Dec 20, 2010 at 22:20:35
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.asc
On Fri, Dec 17, 2010 at 02:57:39PM +0100, Alexander Reichle-Schmehl wrote:
* Alexander Reichle-Schmehl toli...@debian.org [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
Hi!
* Javier Fernández-Sanguino Peña j...@computer.org [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
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,
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 no
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 jcris...@debian.org escribió:
On Mon, Dec 20, 2010 at 15:57:17 +0100, Javier Fernández-Sanguino Peña
wrote:
On
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?
Cheers,
tags 603428 +patch
tags 603428 +penting
thanks
Hi!
* Alexander Reichle-Schmehl toli...@debian.org [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
Processing commands for cont...@bugs.debian.org:
tags 603428 +patch
Bug #603428 [snort-pgsql,snort-mysql] snort: prompting due to modified
conffiles which where not modified by the user
Added tag(s) patch.
tags 603428 +penting
Unknown tag/s: penting.
Recognized are: patch wontfix moreinfo
Hi!
* Alexander Reichle-Schmehl toli...@debian.org [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
Hi!
* Holger Levsen hol...@layer-acht.org [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
20 matches
Mail list logo
