Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package clamav
In keeping with the insanity that is clamav, there is another new clamav
release which both has security fixes and increases the funcitonality level
so that th
severity 703290 important
stop
On Tue, 2013-03-19 at 10:20 +1300, Andrew McMillan wrote:
> Is there any way to do an XSS exploit in 12 characters? If not, then I
> don't think this is 'grave'.
Unless someone from the security or release team complains I've set the
severity to important.
Some DD
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package hsqldb
> Changes:
> hsqldb (1.8.0.10+dfsg-1) unstable; urgency=low
> .
>* remove lib/servlet.jar and make the build actually use
> /usr/share/java/servlet
On Mon, 2013-03-18 at 18:46 +0100, Moritz Muehlenhoff wrote:
> On Mon, Mar 18, 2013 at 07:43:09PM +1300, Andrew McMillan wrote:
> > I guess I'm listed as 'upstream' for DAViCal as well as being the DD
> > responsible for the package. Unfortunately I have no time to do either
> > job for the forese
Hello Julien,
Julien Cristau wrote on 2013-03-18 20:42:
> The debdiff and the above is rather short on explanations (and I'd
> rather not read the whole bug log for 661482)... Care to explain why
> these directories must be created in postinst rather than shipped in the
> package?
hylafax itsel
Your message dated Mon, 18 Mar 2013 20:45:05 +
with message-id <1363639505.15207.3.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#703360: unblock: zbar/0.10+doc-8
has caused the Debian Bug report #703360,
regarding unblock: zbar/0.10+doc-8
to be marked as done.
This means that
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock openssl/1.0.1e-2, it fixes a bunch of issues fixed
in upstream git since the 1.0.1e release.
debdiff attached.
Kurt
diff -Nru openssl-1.0.1e/debian/changelog openssl-1.0.1
On Mon, Jan 28, 2013 at 15:11:42 +0100, Joachim Wiedorn wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: pre-approval
>
> Hello release team,
>
> I ask for pre-approval for package capi4hylafax.
>
> There is a difficult RC bug (#
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi release team,
please unblock the package zbar as the last upload makes the Python
extension actually work on arm* (and maybe other architectures).
See #702499 for details.
I'm also fixin
Your message dated Mon, 18 Mar 2013 20:27:47 +0100
with message-id <20130318192747.gx5...@radis.cristau.org>
and subject line Re: Bug#702796: unblock: haskell-certificate et. al.
has caused the Debian Bug report #702796,
regarding unblock: haskell-certificate et. al.
to be marked as done.
This mea
On Sun, Mar 17, 2013 at 19:26:10 +0100, Andreas Metzler wrote:
> On 2013-03-17 Julien Cristau wrote:
> > On Sun, Mar 17, 2013 at 16:00:29 +0100, Andreas Metzler wrote:
> [...]
> > > 2. If armel armhf mipsel break due to --disable-largefile stop using
> > > --disable-largefile there and stop provi
On Mon, 2013-03-18 at 18:46 +0100, Moritz Muehlenhoff wrote:
> Should we rather drop davical from Wheezy, then?
I personally would say this is not necessary...
First let me repeat... I've only reported these things in the Debian
BTS, as the "upstream" BTS is not working and as I knew that
up
On Mon, Mar 18, 2013 at 07:43:09PM +1300, Andrew McMillan wrote:
> I guess I'm listed as 'upstream' for DAViCal as well as being the DD
> responsible for the package. Unfortunately I have no time to do either
> job for the foreseeable future.
Should we rather drop davical from Wheezy, then?
We
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package ejabberd 2.1.10-4.
It fixes three important bugs:
* Broken import of JPEG images from users' vCards fetched from LDAP [1].
The patch is trivial as it merel
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package firebird2.5
The version in unstable fixes two security issues. One allows to overflow
server's stack before authentication, the other is more specific: it crashes
t
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
As per discussion on debian-cli, the C# lib version are incorrect:
http://lists.debian.org/debian-cli/2013/03/msg1.html
So please schedule a binNMU:
nmu libactiviz.net-cil_1:1.0~git201
On 2013-03-18 07:02, Guillem Jover wrote:
> On Sun, 2013-03-17 at 16:55:22 +0100, Niels Thykier wrote:
>> On 2013-03-06 03:26, Guillem Jover wrote:
>>> There appears to be something in my dpkg unblock requests that seems
>>> to make the list setup unhappy (previously in #690920), just sending
>>> t
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Release Team,
Please consider unblocking package navit.
The new release 0.5.0~svn5126+dfsg.1-3 introduces three segfault fixes
related t
On Sun, Mar 17, 2013 at 12:14:24AM +, Adam D. Barratt wrote:
> So, having procrastinated on this for far too long, I did some tests.
Thanks for looking into this.
> Starting from a freshly debootstrapped squeeze chroot with
> gnome-desktop-environment installed, I added a local repo containin
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock packages nvidia-graphics-drivers, nvidia-settings,
nvidia-graphics-modules
304.84 is a new upstream release (the only way we can get upstream
bugfixes for the blob) that fixe
Hi,
please do not understand this mail as an attempt to force you to some
action. I simply wonder whether there is some reason that the upload of
DebiChem metapackages (bug #702722) happened after four days (even with
a remark I do not really get) but #696387 is left without any comment
for three
Jack,
can you answer the question of our release manager, please? We are very
close to the next stable release and thus our release managers are very
picky what change they allow to go in.
I know that minor botan releases are meant to be API/ABI compatible, and
those changes don't seem to mangle
On 18/03/13 07:02, Thomas Goirand wrote:
> On 03/07/2013 04:23 AM, Daniel Pocock wrote:
>> Package: release.debian.org
>> Severity: normal
>>
>> The current README.Debian is quite old
>>
>> It gives some advice that will lead to people having a broken system
>> (e.g. no networking). It describes
23 matches
Mail list logo
