Bug#574391: udev: same serial number on different disks

Package: udev Version: 0.105 There are two USB disks for back up the system, all disks has cryptfs. When I plug one of them (it doesn't matter which) udev gives same serial number. I have tested I plug all two disks at simultaneously, here is the output: # udevinfo -a -p /sys/block/sdb | grep

Bug#574391: udev: same serial number on different disks

Hello, When I plug one of them (it doesn't matter which) udev gives same serial number. This looks wrong on multiple levels. Anyway, please try to reproduce this with udev from unstable. unstable package depends for recent libc6, dpkg-buildpackage also... (and another ones too) I don't want

Bug#855171: RFS: tlf/1.3.0-1

Hi Adam, On Thu, Feb 16, 2017 at 01:40:32AM +0100, Adam Borowski wrote: > On Tue, Feb 14, 2017 at 11:17:46PM +0100, Ervin Hegedüs wrote: > > I am looking for a sponsor for my package "tlf" > > > > Package name: tlf > > Version : 1.3.0-1

Bug#855171: RFS: tlf/1.3.0-1

xes.patch, based on the lintian's messages. * Added all copyright owners from sources. Regards, Ervin Hegedüs -- I � UTF-8

Bug#855171: RFS: tlf/1.3.0-1

Hi Andrey, On Thu, Feb 16, 2017 at 01:33:25PM +0500, Andrey Rahmatullin wrote: > On Thu, Feb 16, 2017 at 09:29:02AM +0100, Ervin Hegedüs wrote: > > > > I'm working on another (hamradio related) package(s)... Also > > > > should I wait with them? > > > With all

Bug#855171: RFS: tlf/1.3.0-1

Hi Andrey, thanks for the helpful answer, On Thu, Feb 16, 2017 at 12:30:23PM +0500, Andrey Rahmatullin wrote: > On Thu, Feb 16, 2017 at 08:18:44AM +0100, Ervin Hegedüs wrote: > > > However, are you sure you want this uploaded to unstable during freeze? > > > It >

Bug#855171: RFS: tlf/1.3.0-1

Hi, On Thu, Feb 16, 2017 at 01:47:23PM +0500, Andrey Rahmatullin wrote: > On Thu, Feb 16, 2017 at 09:41:13AM +0100, Ervin Hegedüs wrote: > > > > > > I'm working on another (hamradio related) package(s)... Also > > > > > > should I wait with them? >

Bug#855171: RFS: tlf/1.3.0-1

Hi, On Thu, Feb 16, 2017 at 01:53:59PM +0500, Andrey Rahmatullin wrote: > On Thu, Feb 16, 2017 at 09:50:32AM +0100, Ervin Hegedüs wrote: > > > > > > > > I'm working on another (hamradio related) package(s)... Also > > > > > > > > should I wait

Bug#855171: closed by Adam Borowski <kilob...@angband.pl> (Re: Bug#855171: RFS: tlf/1.3.0-1)

ease contact Adam Borowski > <kilob...@angband.pl> by > replying to this email. > Date: Fri, 17 Feb 2017 03:03:27 +0100 > From: Adam Borowski <kilob...@angband.pl> > To: 855171-d...@bugs.debian.org > Subject: Re: Bug#855171: RFS: tlf/1.3.0-1 > > On Thu, F

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

inding * Fixed broken libhamlib2-tcl package * Bump Standards-version to 3.9.8 Regards, Ervin Hegedüs

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi Adrey, On Wed, Jan 18, 2017 at 08:35:50PM +0500, Andrey Rahmatullin wrote: > On Wed, Jan 18, 2017 at 04:29:43PM +0100, Ervin Hegedüs wrote: > > > Why are doing this NMU? > > because lintian indicated that I must give NMU as version to that > > package > I've meant wh

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi Adrey, On Wed, Jan 18, 2017 at 11:16:16PM +0500, Andrey Rahmatullin wrote: > On Wed, Jan 18, 2017 at 04:57:44PM +0100, Ervin Hegedüs wrote: > > I'm member of the team (as guest: > > https://alioth.debian.org/users/airween-guest/). As I wrote, I > > noticed the

Bug#851762: RFS: hamlib/3.1.0-1+nmu1 [NMU]

Hi, On Wed, Jan 18, 2017 at 08:15:53PM +0500, Andrey Rahmatullin wrote: > Control: tags -1 + moreinfo > > Why are doing this NMU? because lintian indicated that I must give NMU as version to that package > Does it fix any bugs? yes, till I worked on the package, I've found a bug (a binary

Bug#851799: RFS: hamlib/3.1.0-1

Bump Standards-version to 3.9.8 Regards, Ervin Hegedüs -- I � UTF-8

Bug#888682: hamlib uses deprecated Tcl 8.5

Hi Sergei, thanks for your feedback, On Sun, Jan 28, 2018 at 07:12:26PM +0300, Sergei Golovan wrote: > Source: hamlib > Version: 3.1-7 > Severity: important > Tags: patch > > Dear Maintainer, > > Since Tcl 8.5 has reached its end-of-life we are planning to remove > it from Debian before the

Bug#906775: hamlib: FTBFS in buster/sid (makeinfo: command not found)

Hi Santiago, On Mon, Aug 20, 2018 at 10:50:13PM +, Santiago Vila wrote: > Package: src:hamlib > Version: 3.1-8 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > >

Bug#906899: wsjtx: Upstream 1.9.1 available

Hi Paul, On Thu, Aug 23, 2018 at 08:30:41AM -0400, Paul Stoetzer wrote: > 1.9.1 should be the targeted version to package. Why spend any effort on > packaging an outdated version that lacks features many stations need to use > to communicate with other stations? we've discussed it before, I've

Bug#892472: please refer to nftables

Hi, Debian Policy allows to use the | (pipe) symbol in case of some fields: https://www.debian.org/doc/debian-policy/#syntax-of-relationship-fields a. On Sat, Mar 10, 2018 at 2:04 PM, Yaroslav Halchenko wrote: > There is no | for recommends afaik > > On March 10, 2018

Bug#888682: hamlib uses deprecated Tcl 8.5

Hi Sergei, On Fri, Mar 16, 2018 at 02:27:18PM +0300, Sergei Golovan wrote: > Hi Ervin, > > On Mon, Jan 29, 2018 at 5:10 PM, Ervin Hegedüs <airw...@gmail.com> wrote: > > Hi Sergei, > > > > thanks for your feedback, > > > > On Sun, Jan 28, 2

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

Hi Andreas, On Wed, Oct 24, 2018 at 07:17:21PM +0200, Andreas Beckmann wrote: > Package: psk31lx > Version: 2.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > lenny had the following binary package (from src:twpsk): [...]

Bug#912402: RFS: tlf/1.3.1-1

Removed dh-autoreconf and autotools-dev packages (not required since compat lev 10) * Replaced Priority from extra to optional * Changed upstream source in d/rules to https * Removed d/README.source - contained old reference Regards, Ervin Hegedüs

Bug#912313: RFS: tlf/1.3.1-1

Hi Adam, thanks for review, On Tue, Oct 30, 2018 at 11:48:29PM +0100, Adam Borowski wrote: > On Tue, Oct 30, 2018 at 09:09:27AM +0100, Ervin Hegedüs wrote: > > * Package name: tlf > >Version : 1.3.1-1 > [...] > > diff -Nru tlf-1.3.0/debian/source/inclu

Bug#912313: RFS: tlf/1.3.1-1

Removed dh-autoreconf and autotools-dev packages (not required since compat lev 10) * Replaced Priority from extra to optional Regards, Ervin Hegedüs

Bug#912314: RFS: psk31lx/2.2-1

ds-Version to 4.2.1 * Removed trailing whitespaces from d/control, d/rules, d/copyright * Bump debhelper version to 11.0.0 * Changed Debian copyright URL to https scheme Regards, Ervin Hegedüs

Bug#911780: psk31lx: version monotony violation: lenny had 2.1+2.2beta1-8

Hi Andreas, On Fri, Oct 26, 2018 at 10:00:34AM +0200, Andreas Beckmann wrote: > On 2018-10-24 22:32, Ervin Hegedüs wrote: > > $ apt-get source psk31lx > > correct, this is the source you want right, > > So looks like the avaliable source and binary packages are

Bug#916420: RFS: tlf/1.3.2-1

w upstream release * Removed spelling-fixes.patch, all modifications had been merged to upstream Regards, Ervin Hegedüs

Bug#934939: RFS: xlog/2.0.17-1

ast upload: * Team upload. * New upstream release (Closes: #925864). * Bump Standards-Version to 4.4.0. Regards, Ervin Hegedüs

Bug#939395: ocfs2-tools - FS can't mount at boot on drbd device

Package: ocfs2-tools Version: 1.8.5-7 Severity: normal Hi, I have two up-to-date Debian systems, with drbd and ocfs2. There is only one drbd device, which configured as Primary/Primary. Everything works as well, except one thing: the system can't mount the drbd device at boot, I have to do it

Bug#939395: [Debian-ha-maintainers] Bug#939395: ocfs2-tools - FS can't mount at boot on drbd device

Hi Valentin, thanks for quick reply, On Wed, Sep 04, 2019 at 07:42:46PM +0200, Valentin Vidić wrote: > > You might want to try configuring systemd to start the > services sequentially (Requires+After): > > 1. drbd.service > 2. o2cb.service > 3. ocfs2.service or drbd.mount (they both try to

Bug#994099: twclock: improve .desktop file

Hi folks, On Sat, Sep 11, 2021 at 10:54:44PM +0200, Christoph Berg wrote: > Re: Daniele Forsi > > > --- twclock.desktop.orig2020-05-22 15:57:34.0 +0200 > > +++ twclock.desktop 2021-09-11 20:13:41.033571003 +0200 > > @@ -3,8 +3,10 @@ > > Name[en_US]=twclock > > Comment=World Clock

Bug#994099: twclock: improve .desktop file

Hi Daniele, On Sun, Sep 12, 2021 at 10:02:47PM +0200, Daniele Forsi wrote: > Ervin Hegedüs wrote: > > > this was the lintian tag why I removed the Exec: > > > > https://lintian.debian.org/tags/command-in-menu-file-and-desktop-file > > that lintian pages tells

Bug#994099: twclock: improve .desktop file

Hi Christoph, On Sat, Sep 11, 2021 at 10:54:44PM +0200, Christoph Berg wrote: > > Exec was actually removed in the last upload. > > Ervin, do you remember why that was done? Afaict without "Exec", the > program won't be launched. (But I'm not a .desktop user) this was the lintian tag why I

Bug#994099: twclock: improve .desktop file

Hi there, On Mon, Sep 13, 2021 at 06:32:02AM +0200, Ervin Hegedüs wrote: > Hi Daniele, > > On Sun, Sep 12, 2021 at 10:02:47PM +0200, Daniele Forsi wrote: > > that lintian pages tells to remove the menu file > > /usr/share/menu/twclock not the Exec line > > thanks - th

Bug#1051157: Apparmor blocks Apache's network trafic

Package: apparmor Version: 3.0.8-3 # dpkg -l "*apparmor*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture

Bug#1051157: Possible solution (?)

The file /etc/apparmor.d/abstractions/apache2-common contains these rules: 22# Apache 23network inet stream, 24network inet6 stream, which (I guess) needs to enable the trafic. Seems like the profiles need to include this file too, so the added this line to the profile

Bug#1012495: [Pkg-nginx-maintainers] Bug#1012495: RFP: libnginx-mod-http-modsecurity - ModSecurity v3 Nginx Connector

hi there, On Wed, Jun 08, 2022 at 11:29:58AM +, Patrick Schleizer wrote: > Package: wnpp > Severity: wishlist > X-Debbugs-CC: pkg-nginx-maintain...@alioth-lists.debian.net > > The maintainer of the custom libnginx-mod-http-modsecurity deb package > is Ervin Hegedüs. He is

Bug#1040799: nmu: libnginx-mod-http-modsecurity_1.0.3-1+b1

Hi, > > The BTS metadata for #1037226 indicates that it also affects unstable > > and testing. Is that correct? sorry I forget to mention the testing - this package blocks the migration of Nginx to testing: https://qa.debian.org/excuses.php?package=nginx I think we should fix this issue in

Bug#1040858: nmu: libnginx-mod-http-modsecurity_1.0.3-1+b1

On Tue, Jul 11, 2023 at 05:01:11PM +0200, Tobias Frost wrote: > > The situation is explained in more details in #1040799, but the gist > is that src:libnginx-mod-http-modsecurity is currently compiled against "old" > PCRE3 instead > of "new" PCRE2, and thus is broken in unstable, testing and

Bug#1040799: nmu: libnginx-mod-http-modsecurity_1.0.3-1+b1

Package: release.debian.org Control: affects -1 + src:libnginx-mod-http-modsecurity X-Debbugs-Cc: libnginx-mod-http-modsecur...@packages.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal nmu libnginx-mod-http-modsecurity_1.0.3-1+b1 . ANY . bookworm . -m

Bug#1035748: unblock: modsecurity/3.0.9-1

hi there, sorry to join this conversation :), On Thu, Jun 01, 2023 at 09:52:06PM +0200, Paul Gevers wrote: > control: tags -1 moreinfo > > Hi, > > On 28-05-2023 21:30, Alberto Gonzalez Iniesta wrote: > > 2) The risks on the release quality are almost zero. Only > >

Bug#1035748: unblock: modsecurity/3.0.9-1

Hi Salvatore, On Thu, Jun 01, 2023 at 10:24:28PM +0200, Salvatore Bonaccorso wrote: > Hi Paul, > > > Yet there is a huge amount of white space changes and other changes that > > look gratuitous. This is really not looking like a targeted fix. @Salvatore, > > can we do a targeted security upload

Bug#1037024: nmu: modsecurity-apache_2.9.7-1

Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hello, we uploaded the package modsecurity_apache (libapache2-mod-security2) after the new upstream release, but meanwhile an other package on which this package depends has a new version

Bug#1035748: unblock: modsecurity/3.0.9-1

On Fri, Jun 02, 2023 at 09:46:19PM +0200, Paul Gevers wrote: > Hi, > > On 01-06-2023 22:39, Ervin Hegedüs wrote: > > > On Thu, Jun 01, 2023 at 09:52:06PM +0200, Paul Gevers wrote: > > I think there is absolutely no risk. Bot package (libmodsecurity3 > > and

Bug#1037024: nmu: modsecurity-apache_2.9.7-1

Hi Paul, On Fri, Jun 02, 2023 at 10:16:09PM +0200, Paul Gevers wrote: > Hi Ervin, > > On 01-06-2023 22:54, Ervin Hegedüs wrote: > > Now the module complains during the startup process, and users > > wondering why. > > I wonder why too. because of this messages:

Bug#1037226: libnginx-mod-http-modsecurity fails to start after update libmodsecurity3 to v3.0.9

Hi Daniel, thanks for reporting. On Thu, Jun 08, 2023 at 01:47:55PM +0200, Daniel Suchy wrote: > Package: libnginx-mod-http-modsecurity > Version: 1.0.3-1+b1 > > libmodsecurity3 was upgraded to version v3.0.9 and after that, nginx > integration/module fails to start: > > [emerg] 348194#348194:

Bug#1037226: libnginx-mod-http-modsecurity dependency

Hi, On Thu, Jun 08, 2023 at 08:34:00PM +0200, Paul Gevers wrote: > > > > sure, but the package itself has not changed. I think without > > tests we could't have discovered this. > > Sure. That's very common with c-libraries that change their ABI but not > their API. The SONAME of the library

Bug#1036353: modsecurity-crs: also include the "plugins"

Hi Mattia, CRS plugins is a new feature and it will be available from version 4.0: https://coreruleset.org/docs/concepts/plugins/#how-to-install-a-plugin "CRS 4.x will come with a plugins folder next to the rules folder." If you take a look at the existing plugins (

Bug#1029836: Should reload apache2 in updates / package install

Hi Tobias, thanks for your patches. As you know :) since Bookworm Nginx is also able to work as WAF with libmodsecurity3, and can use modsecurity-crs. This means the package modsecurity-crs does not need to depend on Apache in the future. And this implies that after install/upgrade the package

Bug#949415: modsecurity-apache: Bugs fixed in version 2.9.7

>> > Can/should this bug be closed? > > Yes, I think it could be. Uhhmm... sorry, now I reviewed the whole issue and realised that the first and second posts are about different problems. PCRE2 dependency (second post) has been solved, but I think the first one is not about the package

Bug#1029838: src:modsecurity-apache: Please provide working default configuration

Hi Tobias, thanks for your report and other notes. The mentioned configuration file (modsecurity.conf(.recommended)) is part of ModSecurity2. But the package itself (modsecurity-apache) depends on modsecurity-crs, and this package uses the same directory (/etc/modsecurity), so there is a strong

Bug#950075: modsecurity-apache FTCBFS: does not pass --host to ./configure

Hi, thanks for report and the patch. I've picked up your modification and added it to package's Git repository. The next version of the package will build with that method: https://salsa.debian.org/modsecurity-packaging-team/modsecurity-apache/-/blob/master/debian/rules#L19 Thanks, a.

Bug#851587: libapache2-modsecurity: prompting due to modified conffiles which were not modified by the user: /etc/apache2/mods-available/security2.conf

> I guess this is fixed, isn't it? Yes, I think we can close this. a.

Bug#949415: modsecurity-apache: Bugs fixed in version 2.9.7

> has this been fixed indeed? yes: https://salsa.debian.org/modsecurity-packaging-team/modsecurity-apache/-/blob/master/debian/rules#L19 modsecurity-apache is shipped with `--with-pcre2` since 2.9.7. > Can/should this bug be closed? Yes, I think it could be. a.

Bug#1037226:

Seems like this bug is fixed. # apt install libnginx-mod-http-modsecurity --default-release bookworm Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libnginx-mod-http-modsecurity 0 upgraded, 1 newly

Bug#1037226:

Hi, as the previous message says ("Prepare a fixed package for the first point release (after ensuring it's fixed in unstable)."), the next release will contain the fix. If you need the updated version, you can compile it manually, or you can use the unofficial ModSecurity repository:

Bug#1067364: Probably bug is elsewhere

I made an investigation and maybe the problem is in another package: libnginx-mod-http-ndk-dev 1:0.3.3-1. The report is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068207 I'll inform you here about the result of the investigation. Regards, a.

Bug#1068207: Missing header from ngx_feature_test='printf("hello");'

Package: libnginx-mod-http-ndk-dev Version: 1:0.3.3-1 There is a module package for Nginx, which worked as well since this FTBFS bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067364 The upstream contains this section in config:

Bug#1068207: Problem appeared in other architecture

The mentioned problem has appeared in other architecture too: https://buildd.debian.org/status/fetch.php?pkg=libnginx-mod-http-modsecurity=riscv64=1.0.3-1%2Bb1=1712870226=log a.

Bug#1068797: modsecurity-crs: IncludeOptional in file owasp-crs.load is incompatible with nginx

Hi Salil, Thanks for reporting. Unfortunately this is a known bug of libmodsecurity3 + Nginx: this installation does not support the `IncludeOptional` directive. The workaround is that you change it manually. Note, that CRS team suggest (since CRS 4) to use the `Include` form in all cases -

Bug#1068207: [Pkg-nginx-maintainers] Bug#1068207:

Hi Jan, On Tue, Apr 23, 2024 at 07:29:37PM +0200, Jan Mojzis wrote: > Hi, > > 'https://wiki.debian.org/qa.debian.org/FTBFS' > see: > 2024-03-13 -Werror=implicit-function-declaration > ... In dpkg version 1.22.6, the compiler flag > -Werror=implicit-function-declaration was enabled by default

Bug#1070465: nmu: libnginx-mod-http-modsecurity_1.0.3-2

Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hello, the ABI has changed in Nginx package, and the maintainer asked all 3rd party modules need to rebuild. See bug #1070321. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070321