Bug#944282: stretch-pu: monit 1:5.20.0-6+deb9u1

2020-01-28 Thread Sergey B Kirpichev
On Tue, Jan 28, 2020 at 08:37:37AM +, Adam D. Barratt wrote: > On 2019-11-07 08:49, Sergey B Kirpichev wrote: > > I would like to make an upload to stable in order to fix bug > > #941895 (CSRF check) in the monit package. > > Please go ahead; sorry for the delay. Thanks, uploaded.

Bug#944282: stretch-pu: monit 1:5.20.0-6+deb9u1

2019-11-07 Thread Sergey B Kirpichev
-10-09 15:47:31.0 +0300 @@ -1,3 +1,9 @@ +monit (1:5.20.0-6+deb9u1) stretch; urgency=medium + + * Implement position independent CSRF cookie value (Closes: #941895). + + -- Sergey B Kirpichev Wed, 09 Oct 2019 15:47:31 +0300 + monit (1:5.20.0-6) unstable; urgency=medium * Fix regression

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-12 Thread Sergey B Kirpichev
On Sun, 7 Jul 2019 08:29:08 +0200 Sebastiaan Couwenberg wrote: > Please upload a new revision to unstable with source-only changes... Backport for Buster: https://mentors.debian.net/package/monit Please sponsor this package. Sponsorship request: https://bugs.debian.org/931972

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-07 Thread Sergey B Kirpichev
On Sun, Jul 07, 2019 at 08:29:08AM +0200, Sebastiaan Couwenberg wrote: > Please upload a new revision to unstable with source-only changes to I did just now (5.26.0).

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-04 Thread Sergey B Kirpichev
On Thu, Jul 04, 2019 at 02:13:03PM +0200, Bas Couwenberg wrote: > How often do you expect to need NEW processing for monit? Probably, once every major release. Backport is a frequent request. > Do you know any users of the package who have contributed patches or other > maintainer type bugreport

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-04 Thread Sergey B Kirpichev
On Thu, Jul 04, 2019 at 12:48:23PM +0200, Bas Couwenberg wrote: > The RT ticket show that you were added to the backports ACL It doesn't help too much: initial upload must be sponsored. > I guess Michal > wasn't available to sponsor your initial backports upload Unfortunately, nobody wasn't avai

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-04 Thread Sergey B Kirpichev
On Thu, Jul 04, 2019 at 10:31:07AM +0200, Bas Couwenberg wrote: > We rely on monit at $DAYJOB, so I want to help you get monit back in buster. Am afraid, there is no chance for monit to enter buster. Sorry for this situation, but I believe this is not just my fault (see this bug thread). Anyway,

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-07-04 Thread Sergey B Kirpichev
On Thu, Jul 04, 2019 at 10:54:10AM +0200, Paul Gevers wrote: > Once packages can migrate normally again (somewhere next week if > everything goes as expected), monit will be back in testing and > backports is a viable option. Feel free to do backport. Latest one was dated Fri, 21 Dec 2018 (https:

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-06-27 Thread Sergey B Kirpichev
On Thu, Jun 27, 2019 at 01:40:42PM +0200, Paul Gevers wrote: > We're sorry, but we'll be removing monit from buster shortly. Thanks for a great release menagement!

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-06-18 Thread Sergey B Kirpichev
On Tue, Jun 18, 2019 at 08:21:38PM +0200, Paul Gevers wrote: > Can you ask somebody else to upload it then? No.

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-06-18 Thread Sergey B Kirpichev
On Mon, 17 Jun 2019 21:19:07 +0200 Paul Gevers wrote: > we don't want packages going though it that don't need to. monit package going to be removed from buster. Maybe this justifies migration from t-p-u? I'm away from my build environment and hardly able to prepare in time that you require for

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-06-17 Thread Sergey B Kirpichev
On Mon, Jun 17, 2019 at 09:20:18PM +0200, Paul Gevers wrote: > > This debdiff looks good. Can you please upload it as > > 1:5.25.3-1+really5.25.2-1 (with the source tar ball of 1:5.25.2) to > > unstable as requested in bug 930313. tpu isn't covered well by QA, so we > > don't want packages going th

Bug#930637: unblock: monit/1:5.25.2-3+deb10u1

2019-06-17 Thread Sergey B Kirpichev
http/cervlet.c ++ CVE-2019-11455 A buffer over-read in Util_urlDecode in util.c + + -- Sergey B Kirpichev Mon, 17 Jun 2019 10:57:40 +0300 + monit (1:5.25.2-3) unstable; urgency=medium * Spelling fixes in manpage diff --git a/debian/patches/CVE-2019-11454.patch b/debian/patches/CVE-2019-11454.

Bug#798749: pu: package monit/1:5.9-1+jessie1

2015-09-14 Thread Sergey B Kirpichev
On Sun, Sep 13, 2015 at 10:49:59PM +0100, Adam D. Barratt wrote: > > Usually there is no need to run yacc while building > > the package: upstream maintainers provide tarball together > > with yacc-generated stuff. In this case, I did same. > > > > I hope, this is clear. > > Apparently I failed

Bug#798749: pu: package monit/1:5.9-1+jessie1

2015-09-12 Thread Sergey B Kirpichev
On Sat, Sep 12, 2015 at 04:56:19PM +0100, Adam D. Barratt wrote: > Please don't use -quiet@ when replying to release.debian.org bugs. > There's no good reason for the reply not to be sent to debian-release; > in fact, not doing so is actively harmful. Sorry. Ok. > I read that, and I know what "a

Bug#736467: unblock: libapache2-mod-rpaf/0.6-7+wheezy1

2014-01-23 Thread Sergey B Kirpichev
On Thu, Jan 23, 2014 at 11:24:40PM +, Adam D. Barratt wrote: > On Fri, 2014-01-24 at 03:13 +0400, Sergey B Kirpichev wrote: > > Usertags: unblock > Nope. Unblock implies unstable to testing transition. Sorry. > > This version fixes important regression in wheezy (#72

Bug#736467: unblock: libapache2-mod-rpaf/0.6-7+wheezy1

2014-01-23 Thread Sergey B Kirpichev
gency=low * Restore 030_ipv6.patch, removed by QA upload in 0.6-1 (Closes: #726529) -- Sergey B Kirpichev Mon, 20 Jan 2014 17:56:07 +0400 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb

Bug#724722: Bug#724598: php5-memcached: Does not build with libmemcached >= 1.0.9

2013-12-25 Thread Sergey B Kirpichev
reassign 724598 libmemcache notforwarded 724598 thanks Ok, after reading related bugs https://github.com/php-memcached-dev/php-memcached/pull/80 https://bugs.launchpad.net/libmemcached/+bug/1190240 > due to an API break in libmemcached 1.0.9 php-memcached does no longer build. Then, please try

Re: libapache2-mod-rpaf upload to stable-proposed-updates

2012-12-27 Thread Sergey B Kirpichev
On Thu, Dec 27, 2012 at 05:12:55PM +, Adam D. Barratt wrote: > If it's purely the yada build-dep, and to a version that's already > in stable, then that's preferable to the entire packaging rework; > particularly as the change abvoe is already in stable. Ok, got it. Hope, we'll not enter this

Re: libapache2-mod-rpaf upload to stable-proposed-updates

2012-12-27 Thread Sergey B Kirpichev
ian/control +++ libapache2-mod-rpaf-0.5/debian/control @@ -1,16 +1,16 @@ Source: libapache2-mod-rpaf -Maintainer: Piotr Roszatycki +Maintainer: Sergey B Kirpichev Section: web Priority: extra Standards-Version: 3.7.2 -Build-Depends: apache2-threaded-dev (>= 2.0.50-10), yada (>= 0.54) +Buil

Re: libapache2-mod-rpaf upload to stable-proposed-updates

2012-12-27 Thread Sergey B Kirpichev
On Thu, Dec 27, 2012 at 01:22:59PM +, Adam D. Barratt wrote: > + * Drop yada build-deps, use debhelper to build (Closes: #636893) > > Changing of packaging systems isn't generally appropriate for a > stable update. Assuming the package successfully builds in stable > and the build-dependencie

libapache2-mod-rpaf upload to stable-proposed-updates

2012-12-27 Thread Sergey B Kirpichev
TMPROOT="$$(pwd)/debian/tmp" \ - && export SOURCE="libapache2-mod-rpaf" \ - && export VERSION="$(VERSION)" \ - && export DEB_HOST_GNU_CPU="$(DEB_HOST_GNU_CPU)" \ - && export DEB_HOST_GNU_TYPE="$(DEB_HOST_GNU_TYPE)"

Re: php-memcached upload to stable-proposed-updates

2012-06-08 Thread Sergey B Kirpichev
On Thu, Jun 07, 2012 at 10:32:51PM +0100, Adam D. Barratt wrote: > The upload eventually happened, and I've flagged it for acceptance in to > proposed-updates. Thank you. > > Chasing up the reporter again would be appreciated. > Any news on that? Recent conversation with the reporter is attache

Re: php-memcached upload to stable-proposed-updates

2012-03-14 Thread Sergey B Kirpichev
On Wed, Mar 14, 2012 at 11:43:36AM +, Adam D. Barratt wrote: > It declares itself as source format "3.0 (quilt)", but is shipped as > tarball-in-tarball. In fact, it's not just tarball-in-tarball, but > the .orig.tar.gz contains nothing but another .tgz which is somewhat > boggling tbh. Yep.

Re: php-memcached upload to stable-proposed-updates

2012-03-14 Thread Sergey B Kirpichev
On Wed, Mar 14, 2012 at 10:43:24AM +, Adam D. Barratt wrote: > I wasn't suggesting modifying the upstream tarball. Yep, you do so. Please, just take look first on the package. > What I was suggesting was: start from an unpacked copy of the source > package (e.g. after "dpkg-source -x"); modi

Re: php-memcached upload to stable-proposed-updates

2012-03-14 Thread Sergey B Kirpichev
On Wed, Mar 14, 2012 at 06:28:06AM +, Adam D. Barratt wrote: > There's nothing wrong with /using/ a patch system. Introducing one, or > changing the system in use, as part of a stable update doesn't count as > a minimal fix with no unnecessary changes, however. Ok, I see your point. > What s

Re: php-memcached upload to stable-proposed-updates

2012-03-13 Thread Sergey B Kirpichev
On Tue, Mar 13, 2012 at 08:34:18PM +, Adam D. Barratt wrote: > > The full patch between this new package version and the version > > 1.0.2-1 currently in Squeeze is attached. > > +include /usr/share/cdbs/1/rules/simple-patchsys.mk > > Please could you prepare an update which doesn't introduce

php-memcached upload to stable-proposed-updates

2012-03-08 Thread Sergey B Kirpichev
+ + * Apply patch from upstream to fix double free in getServerByKey(). +Closes: #662662. + * New maintainer (See: #620030) + + -- Sergey B Kirpichev Mon, 05 Mar 2012 22:56:33 +0400 + php-memcached (1.0.2-1) unstable; urgency=low * New upstream release diff --git a/debian/control b/debian

Re: php-memcache upload to stable-proposed-updates

2012-01-24 Thread Sergey B Kirpichev
On Tue, Jan 24, 2012 at 11:11:28AM +0100, Cyril Brulebois wrote: > > +php-memcache (3.0.4-4~squeeze1) stable; urgency=low > > We currently have 3.0.4-4 in squeeze, and 3.0.4-4~squeeze1 is below it, > not above (see dpkg --compare-versions foo '<' bar). Please use > 3.0.4-4+squeeze1 instead. Yep.

php-memcache upload to stable-proposed-updates

2012-01-24 Thread Sergey B Kirpichev
from memcached +1.4.4+ (Closes: #620258) + * Maintainer change (See #620029) + + -- Sergey B Kirpichev Tue, 24 Jan 2012 13:01:06 +0400 + php-memcache (3.0.4-4) unstable; urgency=low * add memcached to suggests (Closes: #583109) diff --git a/debian/control b/debian/control index 3ef8cc0

Bug#607948: unblock: awstats/6.9.5~dfsg-5

2010-12-24 Thread Sergey B Kirpichev
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, Please unblock awstats to squeeze. It fixes #606263 (multiple security issues) and few minor bug's: * Fix bashism in buildstatic.sh (Closes: bug#582861). * Recommend versions of coreut