On Wed, 7 Nov 2012 00:32:36 Paul Chitescu wrote:
> > unblock yate/4.1.0-1~dfsg-3
> >
> > [...]
>
> Does this require any more action?
Hi Paul,
Yes we are awaiting a decision from debian-release.
Mark
signature.asc
Description: This is a digitally signed message part.
Processing commands for cont...@bugs.debian.org:
> affects 691552 yate
Bug #691552 [release.debian.org] unblock: yate/4.1.0-1~dfsg-3
Added indication that 691552 affects yate
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
691552: http://bugs.debian.org/cgi-bin/bu
On Tue, Nov 06, 2012 at 01:43:58PM +, Neil Williams wrote:
> Hopefully because people are working on the release so that uploads to
> unstable can be opened again. The quicker we release Wheezy, the quicker
> this and other packages get into unstable. It's much better to work on
> RC bugs than
On Tue, Nov 06, 2012 at 02:17:05PM +0100, Thibaut VARENE wrote:
> Noted. The package was in experimental for several weeks and got zero
> attention. My general understanding is that nobody looks at
> experimental anyway.
I have a lot of sympathy with this point, personally. OTOH I've just made an
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
I've just uploaded chocolate-doom/1.7.0-2, with one fix, a documentation
fix only:
> * Add myself back to uploaders.
1.7.0-1 has no humans in Maintainer and no Uploaders which is a po
* Thibaut VARENE [121106 15:03]:
> That being said, I'd like to point out again that all this fuss was
> made for nothing, since none of the packages listed in the initial
> email are being blocked from entering wheezy because of this upload,
> since none of them are unfrozen, and wheezy is unaffe
On Wednesday 07 November 2012 01:39 AM, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
>
> On Wed, 2012-11-07 at 01:24 +0530, Ritesh Raj Sarraf wrote:
>> > Please unblock package sysprof
> Just to clarify, this hasn't been uploaded yet?
No. Sorry. That is just the diff. I will not upload un
Processing control commands:
> tags -1 + moreinfo
Bug #692495 [release.debian.org] unblock: sysprof/1.1.8-1
Added tag(s) moreinfo.
--
692495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email
Control: tags -1 + moreinfo
On Wed, 2012-11-07 at 01:24 +0530, Ritesh Raj Sarraf wrote:
> Please unblock package sysprof
Just to clarify, this hasn't been uploaded yet?
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Your message dated Tue, 06 Nov 2012 21:08:01 +0100
with message-id <50996e21.7020...@thykier.net>
and subject line Re: Bug#692494: unblock: roundup/1.4.20-1.1
has caused the Debian Bug report #692494,
regarding unblock: roundup/1.4.20-1.1
to be marked as done.
This means that you claim that the pr
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Release-Team
Please unblock package couriergraph
I did a NMU upload for couriergraph.
The upload addresses two RC bugs: One was opened
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package sysprof
(explain the reason for the unblock here)
This request is in regard to debian bug #692372. As mentioned in the bug
report, sysprof version 1.1.8 reads the CR
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Release-Team
Please unblock package roundup
The upload of roundup 1.4.20-1.1 adresses RC bug #689257 "deletes
conffiles during postrm re
Your message dated Tue, 06 Nov 2012 18:19:30 +
with message-id <8a99603d6019edfa96780f7ac87b5...@mail.adsl.funky-badger.org>
and subject line Re: Bug#691464: unblock: systemd/44-5
has caused the Debian Bug report #691464,
regarding unblock: systemd/44-5
to be marked as done.
This means that yo
Your message dated Tue, 06 Nov 2012 17:34:37 +0100
with message-id <50993c1d.7080...@thykier.net>
and subject line Re: Bug#690895: unblock: giflib/4.1.6-10
has caused the Debian Bug report #690895,
regarding unblock: giflib/4.1.6-10
to be marked as done.
This means that you claim that the problem
On Tue, Nov 06, 2012 at 02:59:11PM +0100, Thibaut VARENE wrote:
> And I see nothing wrong with breaking packages in unstable, but maybe
> there too I'm mistaken.
>
Yes, as you breaking a package in unstable may:
a) Break other packages
b) Remove the ability to update via unstable if a RC bug does
On Saturday 27 October 2012 07:18:17 am Mark Purcell wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package yate
>
> This release fixes three RC bugs and includes missing core modules.
>
>
> Thanks,
> Mar
On Tue, Nov 6, 2012 at 2:43 PM, Neil Williams wrote:
> Having a freeze simply means that some package changes *must* be
> delayed until after the freeze. Experimental works for some, if it
> doesn't work for you then you cannot update the package in Debian until
> the release, so maybe help get t
On 05.11.2012 22:28, Aníbal Monsalve Salazar wrote:
On Wed, Oct 31, 2012 at 08:51:29PM -0700, Matt Taggart wrote:
So the libglib2.0-dev build-dep needs to be versioned. I ran into
this
attempting to backport to squeeze.
[...]
I would like to upload irqbalance/1.0.3-4 to fix Bug#691999. Is it
Your message dated Tue, 06 Nov 2012 13:48:34 +
with message-id <753253af3810b78f547d2b3f7da19...@mail.adsl.funky-badger.org>
and subject line Re: Bug#692449: unblock: bliss/0.72-4
has caused the Debian Bug report #692449,
regarding unblock: bliss/0.72-4
to be marked as done.
This means that yo
Your message dated Tue, 06 Nov 2012 13:46:46 +
with message-id <77a905c4f1cca1c6b727546bccb4d...@mail.adsl.funky-badger.org>
and subject line Re: Bug#692461: unblock radsecproxy/1.6.2-1
has caused the Debian Bug report #692461,
regarding unblock radsecproxy/1.6.2-1
to be marked as done.
This m
On Tue, 6 Nov 2012 14:17:05 +0100
Thibaut VARENE wrote:
> On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams wrote:
> > On Tue, 6 Nov 2012 10:59:42 +0100
> > Thibaut VARENE wrote:
> > If you want it in Debian now, push it into experimental. If you want it
> > Jessie (the next testing), then wait fo
Package: release.debian.org
Severity: normal
Hi,
Please unblock radsecproxy 1.6.2-1. It's a security upload, complementing
1.4-1+squeeze1 and fixing two CVEs. Security team is aware and has reviewed the
upstream fixes for those -- in fact, the second vulnerability was found by
Raphael during the
On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams wrote:
> On Tue, 6 Nov 2012 10:59:42 +0100
> Thibaut VARENE wrote:
>
>> On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern wrote:
>> > On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
>> >> I thought that Wheezy having been frozen for quite
On Tue, 6 Nov 2012 10:59:42 +0100
Thibaut VARENE wrote:
> On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern wrote:
> > On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
> >> I thought that Wheezy having been frozen for quite some time, it was okay
> >> to upload new packages to unstabl
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package bliss
There are two simple fixes (one line in -3 and two lines in -4).
The RCish fix is in 0.72-4. In versions 0.72-2 and 0.72-3, if the user
neglects to define the
On Tue, Nov 6, 2012 at 10:48 AM, Philipp Kern wrote:
> On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
>> I thought that Wheezy having been frozen for quite some time, it was okay
>> to upload new packages to unstable again.
>
> I'm sure we would've communicated that on d-d-a if th
On Mon, Nov 05, 2012 at 03:04:21PM +0100, Thibaut VARENE wrote:
> I thought that Wheezy having been frozen for quite some time, it was okay
> to upload new packages to unstable again.
I'm sure we would've communicated that on d-d-a if this would've been
the case.
(Also please don't put a ">" befo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ignace,
thanks for your fast reply.
Am 06.11.2012 09:11, schrieb Ignace Mouzannar:
> On Tue, Nov 6, 2012 at 9:05 AM, Jan Wagner
> wrote:
>> is there a chance to get that fixed in wheezy?
>
> I will fix this ASAP.
>
>> On the first view it looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Am 14.04.2012 12:36, schrieb Raf Czlonka:
> When logrotate runs it generates an error message:
>
> error: skipping "/var/log/lshell/*.log" because parent directory
> has insecure permissions (It's world writable or writable by group
> which
On Tue, Nov 6, 2012 at 9:05 AM, Jan Wagner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi there,
>
> Am 14.04.2012 12:36, schrieb Raf Czlonka:
>> When logrotate runs it generates an error message:
>>
>> error: skipping "/var/log/lshell/*.log" because parent directory
>> has insecu
31 matches
Mail list logo
