On Thu, 2013-05-02 at 00:25 +0200, Jonas Smedegaard wrote:
> Quoting Adam D. Barratt (2013-05-01 21:50:30)
> > No fixes have been forthcoming, so I think we have to accept at this
> > point that pyabiword is fundamentally broken in wheezy. On that basis,
> > unless someone comes up with an alternat
Your message dated Wed, 01 May 2013 22:47:44 +
with message-id
and subject line Bug#705560: fixed in pymongo 2.5-1
has caused the Debian Bug report #705560,
regarding pymongo-ext has no version dependency against pymongo
to be marked as done.
This means that you claim that the problem has bee
Quoting Adam D. Barratt (2013-05-01 21:50:30)
> user release.debian@packages.debian.org
> usertags 706017 + wheezy-will-remove
> usertags 706298 + wheezy-will-remove
> thanks
>
> On Sat, 2013-04-27 at 11:18 +0100, Adam D. Barratt wrote:
> > On Wed, 2013-04-24 at 12:01 +0700, Prach Pongpanich w
Hi,
I noticed (by chance) there is a problem with the squeeze-security patch
for #690319; it introduces a regression on kfreebsd and has not built.
I'm not sure where to find build logs of this, or if they are public,
but I think it is due to using a non-standard EBADFD errno ("file
descriptor i
Your message dated Wed, 01 May 2013 22:46:44 +0100
with message-id <1367444804.28602.47.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#706527: scribus: uninstallable on amd64, depends on
nonexistent libpodofo0.9.1
has caused the Debian Bug report #706527,
regarding scribus: uninsta
I need to remember exactly what we have done with grego last time. There were
at least two updates to try to fix this issue. It should not be that
complicated to fix since you have tracked down the package state which prevents
the package from upgrading smoothly.
Thanks for your feedback.
Rega
Processing commands for cont...@bugs.debian.org:
> # Not going to be fixed for r0
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 694252 + wheezy-can-defer
There were no usertags set.
Usertags are now:
On Sun, 2013-04-28 at 15:56 +0100, Adam D. Barratt wrote:
> On Sun, 2013-04-28 at 15:59 +0200, Kurt Roeckx wrote:
> > It seems that vmime 0.9.1-1 is not binary compatible with
> > the version 0.9.0-1.1 as available in squeeze.
>
> libvmime doesn't appear to have any reverse-dependencies in the ar
On Wed, 01 May 2013 20:55:35 +0100
"Adam D. Barratt" wrote:
> On Tue, 2013-04-30 at 19:23 +0200, Attila Kinali wrote:
> > The current interrupt table code definitions in the gcc-msp430 and
> > msp430mcu
> > packages will lead to generate tables that go far into a reserved region
> > of the MSP4
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 693577 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 693577
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 706045 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 706045
user release.debian@packages.debian.org
usertags 706045 + wheezy-can-defer
tags 706045 + wheezy-ignore
thanks
On Mon, 2013-04-29 at 07:16 +0200, Matthias Andree wrote:
> Am 28.04.2013 18:28, schrieb Adam D. Barratt:
>
> > Indeed. From the release perspective, however, the question we're
> > c
Hi,
On Tue, 2013-04-30 at 19:23 +0200, Attila Kinali wrote:
> The current interrupt table code definitions in the gcc-msp430 and msp430mcu
> packages will lead to generate tables that go far into a reserved region
> of the MSP430 devices in case of the MSP430FR5xxx devices.
> Apperantly this regi
user release.debian@packages.debian.org
usertags 706017 + wheezy-will-remove
usertags 706298 + wheezy-will-remove
thanks
On Sat, 2013-04-27 at 11:18 +0100, Adam D. Barratt wrote:
> On Wed, 2013-04-24 at 12:01 +0700, Prach Pongpanich wrote:
> > I think the jigsawpuzzle does not start because it
user release.debian@packages.debian.org
usertags 706484 + wheezy-can-defer
tags 706484 + wheezy-ignore
thanks
On Tue, 2013-04-30 at 12:12 -0400, Joern Engel wrote:
> Bug occurred with 3.7.8-6ubuntu3.1, but is present in Debian and all
> upstream versions up to and including 3.8.4. When writin
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 706484 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 706484
Processing commands for cont...@bugs.debian.org:
> # not blockers for the release
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 675231 + wheezy-can-defer
There were no usertags set.
Usertags are now:
On 01/05/13 17:32, micah wrote:
> Carlos Alberto Lopez Perez writes:
>
>> On 28/04/13 02:50, micah wrote:
I will happily sign for that. However I would like to migrate the
package scm from svn to git. I have not experience packaging with svn
and learning to do that now will be a ba
FYI I've filed the following JIRA to track this:
https://issues.apache.org/jira/browse/QPID-4798
--Rafael
On Tue, Apr 30, 2013 at 10:09 AM, Thomas Goirand wrote:
> Dear QPID maintainers,
>
> Jonas Smedegaard just sent a bug report on the Debian bug tracker,
> because he believes that the qpid-
Carlos Alberto Lopez Perez writes:
> On 28/04/13 02:50, micah wrote:
>>> I will happily sign for that. However I would like to migrate the
>>> package scm from svn to git. I have not experience packaging with svn
>>> and learning to do that now will be a backwards step IMHO.
>>
>> As I mentioned
Your message dated Wed, 01 May 2013 15:03:01 +
with message-id
and subject line Bug#702674: fixed in fritzing 0.7.12b-1
has caused the Debian Bug report #702674,
regarding fritzing: Fails to build on arm*
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: severity -1 important
On Wed, May 01, 2013 at 02:20:44PM +0200, Markus wrote:
> Justification: causes non-serious data loss
You did not show that.
> Would be thankful for any hints!
Please show the hypervisor log by running "xen dmesg".
Bastian
--
You're dead, Jim.
-
Processing control commands:
> severity -1 important
Bug #706543 [xen-hypervisor-4.1-amd64] xen-hypervisor-4.1-amd64: HVM PCI
Passthrough not working any more after last upgrade
Severity set to 'important' from 'grave'
--
706543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706543
Debian Bu
On 28/04/13 02:50, micah wrote:
>> I will happily sign for that. However I would like to migrate the
>> package scm from svn to git. I have not experience packaging with svn
>> and learning to do that now will be a backwards step IMHO.
>
> As I mentioned on IRC, I think that is a fantastic idea.
>
Florian Weimer writes:
> * Christoph Egger:
>
>> Packages will be in people.d.o:~christoph soon (or shall I upload to
>> security directly?
>
> Looks good. Please upload to security-master directly. You have to
> rebuild with -sa, though, so that the upstream tarball is included in
> the upload.
Followup-For: Bug #675231
Still reproducibl ein the sequence
setup squeeze
install psad/squeeze
remove psad (on't purge!)
distupgrade to wheezy
install psad/wheezy
Andreas
psad_2.2-3.1.log.gz
Description: GNU Zip compressed data
Processing commands for cont...@bugs.debian.org:
> unarchive 606781
Bug #606781 {Done: Andreas Beckmann } [viewvc] viewvc:
package fails to upgrade properly from lenny
Unarchived Bug 606781
> found 606781 1.1.5-1.1+squeeze2
Bug #606781 {Done: Andreas Beckmann } [viewvc] viewvc:
package fails to
Hi!
Steven Chamberlain writes:
> Is that the correct version number for a security upload? (9.0-10+deb70.1)
>
> I'm more used to seeing something like +wheezy1
As +wheezy actually is larger that +jessie the +deb$something are the
new style for stable version numbering as far as I understand
Is that the correct version number for a security upload? (9.0-10+deb70.1)
I'm more used to seeing something like +wheezy1
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
* Christoph Egger:
> Packages will be in people.d.o:~christoph soon (or shall I upload to
> security directly?
Looks good. Please upload to security-master directly. You have to
rebuild with -sa, though, so that the upstream tarball is included in
the upload.
--
To UNSUBSCRIBE, email to debi
Florian Weimer writes:
> * Christoph Egger:
>
>> Hi!
>>
>> Steven Chamberlain writes:
>>> tags 706414 + pending
>>> thanks
>>>
>>> I've applied upstream's patch in SVN, I'm running it now on my NFS
>>> server and seems okay.
>>>
>>> Christoph, would you be able to do an upload of this to unstable
Your message dated Wed, 01 May 2013 13:04:01 +
with message-id
and subject line Bug#706414: fixed in kfreebsd-9 9.0-11
has caused the Debian Bug report #706414,
regarding CVE-2013-3266: Insufficient input validation in the NFS server
to be marked as done.
This means that you claim that the pr
Package: xen-hypervisor-4.1-amd64
Version: 4.1.4-3
Followup-For: Bug #706543
Other people having the same problem here:
http://lists.xen.org/archives/html/xen-users/2013-05/msg4.html
Seems to be a problem with a path applied to Xen 4.1 and 4.2:
http://xen.crc.id.au/bugs/view.php?id=5
--
To
Package: samba4
Version: 4.0.3+dfsg1-0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.
>From the attached log (scroll
Package: xen-hypervisor-4.1-amd64
Version: 4.1.4-3
Severity: grave
Justification: causes non-serious data loss
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LAN
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
a...@adam-barratt.org.uk).
> usertags 706525 + wheezy-can-defer
There were no usertags set.
Usertags are now: wheezy-can-defer.
> tags 706525
user release.debian@packages.debian.org
usertags 706525 + wheezy-can-defer
tags 706525 + wheezy-ignore
thanks
On 2013-05-01 10:27, Salvatore Bonaccorso wrote:
@Release Team: This probably should not delay the release for wheezy,
as
chicken has other security relevant bugreport open (#702410
* Christoph Egger:
> Hi!
>
> Steven Chamberlain writes:
>> tags 706414 + pending
>> thanks
>>
>> I've applied upstream's patch in SVN, I'm running it now on my NFS
>> server and seems okay.
>>
>> Christoph, would you be able to do an upload of this to unstable please?
>
> I'm building right now.
Package: keystone
Version: 2013.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.
>From the attached log (scroll to th
Your message dated Wed, 01 May 2013 11:33:36 +
with message-id
and subject line Bug#706186: fixed in wims-moodle 4.0-4
has caused the Debian Bug report #706186,
regarding wims-moodle: modifies conffiles (policy 10.7.3):
/etc/moodle/wimsconf.php,
/usr/share/moodle/mod/assignment/type/wims/wim
On 01/05/13 11:14, Christoph Egger wrote:
> [...] As it is too late for wheezy r0 it seems we'll
> need to go through either security or stable-updates for wheezy
Yes, we need to fix it in sid anyway. I think this (in kfreebsd-9)
merits a DSA and the fix made available via security.d.o as soon as
Hi!
Steven Chamberlain writes:
> tags 706414 + pending
> thanks
>
> I've applied upstream's patch in SVN, I'm running it now on my NFS
> server and seems okay.
>
> Christoph, would you be able to do an upload of this to unstable please?
I'm building right now. As it is too late for wheezy r0 it
Your message dated Wed, 01 May 2013 09:48:27 +
with message-id
and subject line Bug#706389: fixed in libconfig-model-itself-perl 1.237-1
has caused the Debian Bug report #706389,
regarding FTBFS: Missing build-dependency on libany-moose-perl
to be marked as done.
This means that you claim tha
Package: scribus
Version: 1.4.2.dfsg+r18267-1
Severity: serious
Dear Maintainer,
The amd64 binary is uninstallable in sid, because it depends on nonexistent
libpodofo0.9.1 package.
Cheers,
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`-
Processing commands for cont...@bugs.debian.org:
> retitle 702410 chicken: CVE-2012-6122 CVE-2012-6123 CVE-2012-6124
> CVE-2012-6125 CVE-2013-1874
Bug #702410 [chicken] chicken: CVE-2012-6122 CVE-2012-6123 CVE-2012-6124
CVE-2012-6125
Changed Bug title to 'chicken: CVE-2012-6122 CVE-2012-6123 CVE
Package: chicken
Version: 4.5.0-1
Severity: grave
Tags: security patch
Hi,
@Release Team: This probably should not delay the release for wheezy, as
chicken has other security relevant bugreport open (#702410) with wheezy-ignore
tag. The same can be done here, IMO.
the following vulnerability was
Processing commands for cont...@bugs.debian.org:
> notfound 706516 wesnoth-1.10/1:1.10.3-3
Bug #706516 {Done: Vincent Cheng } [wesnoth-1.10-core]
[wesnoth-1.10-core] Text in Wesnoth dialogs is unreadable, as Wesnoth can't
access font
No longer marked as found in versions wesnoth-1.10/1:1.10.3-3.
Forwarding reply to #706516 (bug submitter forgot to cc bug report):
-- Forwarded message --
From: Meinert
Date: Wed, May 1, 2013 at 1:25 AM
Subject: Re: Bug#706516: [wesnoth-1.10-core] Text in Wesnoth dialogs
is unreadable, as Wesnoth can't access font
To: Vincent Cheng
Hi,
m
Source: squid-deb-proxy
Version: 0.7
Severity: serious
Tags: patch
Justification: fails to build from source
squid-deb-proxy calls lsb_release without build-depending on lsb-release.
I've attached a patch that uses dpkg-vendor so no new build-dependency is
necessary.
Build log:
# use hte right d
Your message dated Wed, 1 May 2013 01:31:30 -0700
with message-id
and subject line Re: Bug#706516: [wesnoth-1.10-core] Text in Wesnoth dialogs is
unreadable, as Wesnoth can't access font
has caused the Debian Bug report #706516,
regarding [wesnoth-1.10-core] Text in Wesnoth dialogs is unreadable
Hi,
my bad. I accidently installed ttf-dejavu version 2.33+svn2514-2 from
experimental at some point. Going back to version 2.33-3 from testing placed
all bits correctly.
So this one can be closed.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubsc
Processing commands for cont...@bugs.debian.org:
> tags 706516 + moreinfo unreproducible
Bug #706516 [wesnoth-1.10-core] [wesnoth-1.10-core] Text in Wesnoth dialogs is
unreadable, as Wesnoth can't access font
Added tag(s) unreproducible and moreinfo.
> On Wed, May 1, 2013 at 12:49 AM, Meinert wr
tags 706516 + moreinfo unreproducible
On Wed, May 1, 2013 at 12:49 AM, Meinert wrote:
> Package: wesnoth-1.10-core
> Version: 1:1.10.3-3
> Severity: grave
>
> --- Please enter the report below this line. ---
> Wesnoth can't access DejaVuSans.ttf as it uses a broken symlink.
> Therefore it display
Followup-For: Bug #694252
Control: found -1 2.88dsf-35
Hi,
the Breaks: bootchart is incorrectly versioned, so it does not work :-(
Either the Breaks should be unversioned or use (<< 0.10~svn407-4)
because 0.10~svn407-3.3 was the last existing and therefore "broken"
version in lenny (and on snaps
Processing control commands:
> found -1 2.88dsf-35
Bug #694252 {Done: Roger Leigh } [sysv-rc] sysv-rc:
migration to dependency based boot order fails if bootchart from lenny is still
installed
Marked as found in versions sysvinit/2.88dsf-35; no longer marked as fixed in
versions sysvinit/2.88ds
Processing commands for cont...@bugs.debian.org:
> unarchive 694252
Bug #694252 {Done: Roger Leigh } [sysv-rc] sysv-rc:
migration to dependency based boot order fails if bootchart from lenny is still
installed
Unarchived Bug 694252
> thanks
Stopping processing here.
Please contact me if you nee
Source: ruby-mini-magick
Version: 3.5.0-1
Severity: serious
Tags: patch
Justification: fails to build from source
This package requires internet connectivity for its test suite
to pass. Package builds should not rely on external network
connectivity, but should be self-contained.
I have attached
Package: wesnoth-1.10-core
Version: 1:1.10.3-3
Severity: grave
--- Please enter the report below this line. ---
Wesnoth can't access DejaVuSans.ttf as it uses a broken symlink.
Therefore it displays boxes for all letters in the dialogs.
This makes the game unusable. Correcting the link manual solv
58 matches
Mail list logo
